5 replies to this topic

[wake4x4ptball]

i followed instructions from liberty 2.0 and wipe data, factory, cache divlak then install zip successful installed then stuck on "liberty" so i SBF back to .340 then try Apex with .602 built in and do same thing then stuck on "google" what have i done wrong?

so im start all over what i have right now is SBF back to .340 and z4root and use Droid 2 bootstrap so tell me what to do

-should i use different kind bootstrap ?

[Sponsored Links]

• Back to top

[#27265]

After you sbf'd your device to 340 or 602, at either time did you enter stock recovery and wipe data/factory restore and cache?

It is a good practice to prevent boot loops and other errors. I would start my trouble shooting from that point.

sbf, wipe everything in stock recovery, bootstrap, backup, flash rom.

As far as why roms do not install, on froyo use dxbootstrap, on gingerbread use d2bootstrap.

Hope that helps.

Sent from my DROIDX using Tapatalk

[wake4x4ptball]

is there a way to get AKP for bootstrap on froyo cuz i already had D2 or i should update to gingerbread then use D2 but what method i use to upgrade from .340 to .602 my droid x dont have service its deactivated im using on WIFI

[wake4x4ptball]

i SBF to .340 then can i SBF again to .602 wipe data again or just add on?

[#27265]

wake4x4ptball, on 27 January 2012 - 01:00 PM, said:

i SBF to .340 then can i SBF again to .602 wipe data again or just add on?

just use rsdlite to flash your dx to 340 or 602.

No need to flash one then the other. The sbf file is not a rom, firmware or ota.

The sbf file is an img file to restore the device to 100% stock as it would be when purchased.

If you want a froyo based system flash 340 (older). If you want a GB based system (newer) flash the 602.

But after every sbf, wipe cache and factory restore from STOCK recovery.

Sent from my DROIDX using Tapatalk

Edited by cdexsw, 27 January 2012 - 02:10 PM.

[ZeroOne]

Make sure your battery is charged to %90+ or if you get force closes on a new rom just reboot into recovery reflash the rom again to correct that issue you do not have to wipe data/factory reset, wipe cache, etc..