Was successfull flashing ics rom to phone, but when phone comes on it states the setup wizard failed everytime. Any suggestions???
Have you tried reflashing to stock and installing safestrap?
Sent from my DROID BIONIC using Tapatalk
I am going to get the spearmint gummy when fresh non 509'd links are put up. I would suggest going to stock with a backup (You better have made one) putting on a safestrap instead of bootloader then reflash making sure that you have the complete file and not just part of it. Then if you continue to have problems pm/reply to the thread with your problem.
Related
Hey Guys, I don't think this has been posted before, so thought I'd share. I managed to get CM9 working with my Bell XT860 *without* needing to change up the phone using another country's fastboot file.
My phone was Bell 2.3.6, rooted, otherwise stock. I used Hashcode's safestrap to make a nandroid backup and install the latest patched CM9 from Rick#2 available here: http://forum.xda-developers.com/showthread.php?t=1465297
I actually didn't expect it to boot up, but thought I'd give it a go since even if it failed the worst that could happen is that I'd have to SBF anyways.
At first it was a black screen, I had to do a battery pull. After the battery went back in, it started booting up with the animation screen, which showed multiple times over about 5-10 minutes. Then the phone started up Ice Cream Sandwich!
I've been testing it out a bit.. not much yet, but Market is working, data 3g seems to be working 2700 kbps up / 1341 kbps down (with a server that's super far away, 321ms ping). GPS is working... Wifi good. Camera does not work.
Wow, I never expected this. I think this gives hope to those who want to try out Ice Cream Sandwich but still want the ability to go back to stock. Or am I missing something?
ncho2233 said:
Hey Guys, I don't think this has been posted before, so thought I'd share. I managed to get CM9 working with my Bell XT860 *without* needing to change up the phone using another country's fastboot file.
My phone was Bell 2.3.6, rooted, otherwise stock. I used Hashcode's safestrap to make a nandroid backup and install the latest patched CM9 from Rick#2 available here: http://forum.xda-developers.com/showthread.php?t=1465297
I actually didn't expect it to boot up, but thought I'd give it a go since even if it failed the worst that could happen is that I'd have to SBF anyways.
At first it was a black screen, I had to do a battery pull. After the battery went back in, it started booting up with the animation screen, which showed multiple times over about 5-10 minutes. Then the phone started up Ice Cream Sandwich!
I've been testing it out a bit.. not much yet, but Market is working, data 3g seems to be working 2700 kbps up / 1341 kbps down (with a server that's super far away, 321ms ping). GPS is working... Wifi good. Camera does not work.
Wow, I never expected this. I think this gives hope to those who want to try out Ice Cream Sandwich but still want the ability to go back to stock. Or am I missing something?
Click to expand...
Click to collapse
If you bootloop while in safe mode DON'T SBF. Safestrap works by renaming /system to /systemorig and making /preinstall your new /system.
This means when you're in safemode you can always access recovery. So if you bootloop just battery pull to get out of the loop and then you'll e able to hit menu and enter safestrap. Either flash a different rom or return to nonsafe. If you are using safestrap 1.08 and not 1.08d you can't even flash nonsafe mode (1.08d is tweaked to allow advanced user to flash over their nonsafe, for example I have both liberty and eclipse roms on my phone no stock at all)
Also first boot of a rom always takes a long time. After that it should boot much faster
As another note if you do manage to screw up /systemorig somehow you can use motofastboot utility to flash just the system.img part of the SBF package. This will only replace the rom, then you just reboot, install safestrap and restore you backup.
Sent from my XT860 using xda premium
Wow, thanks for the warning, very good information! It's so good to be able to try some custom roms again. I'm out of CM9 already for lack of camera but so far am really impressed with Liberty, it's like my phone has come to life again. Very quick and responsive, amazing ability to customize as well.
Endoroid said:
If you bootloop while in safe mode DON'T SBF. Safestrap works by renaming /system to /systemorig and making /preinstall your new /system.
This means when you're in safemode you can always access recovery. So if you bootloop just battery pull to get out of the loop and then you'll e able to hit menu and enter safestrap. Either flash a different rom or return to nonsafe. If you are using safestrap 1.08 and not 1.08d you can't even flash nonsafe mode (1.08d is tweaked to allow advanced user to flash over their nonsafe, for example I have both liberty and eclipse roms on my phone no stock at all)
Also first boot of a rom always takes a long time. After that it should boot much faster
As another note if you do manage to screw up /systemorig somehow you can use motofastboot utility to flash just the system.img part of the SBF package. This will only replace the rom, then you just reboot, install safestrap and restore you backup.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
hi there ,i using 1.08d and try to flash willis111's bell 2.3.6 rom ,and I want to flash it to the orig system ,not the preinstall ,but every I flashed it ,the my xt860 restart and into the ori rom(2.3.5 bra),not the bell 2.3.6.
here is what i do
1 restart my xt860,and press menu
2 in the safestrap,wipe date ,format system ,then in advance flash .zip nonsafe
3 restart my xt860,and still the 2.3.5 bra rom ..
sorry for my bad English ,and great thx
---------- Post added at 04:44 AM ---------- Previous post was at 04:29 AM ----------
Endoroid said:
(1.08d is tweaked to allow advanced user to flash over their nonsafe, for example I have both liberty and eclipse roms on my phone no stock at all)
Click to expand...
Click to collapse
all I want to know is how to ....thxxxxxxxxx
That's how it should be done
Last time I flashed my /systemorig was before 1.08d had been released so I did it co ming off a fresh fastboot flash using bootstrap to flash liberty, then installed safestrap. I haven't found a rom to replace liberty in my /systemorig yet so I haven't tried the advance flash yet. Sorry.
Sent from my XT860 using xda premium
newaxis said:
hi there ,i using 1.08d and try to flash willis111's bell 2.3.6 rom
Click to expand...
Click to collapse
Hi
i' desperate for willis111's bell 2.3.6 rom but can't download from rapidshar, there is a way you upload the file to non-repidsher site?
Thanks ahead
Current phone information should be attached. Short form is, I'm using the Gummi 1.2.0 rom, put onto my phone after using safestrap (and following the instructions to make a backup before doing so). Safesystem is enabled.
Two backups: located on my external SD card
nonsafe-2012-05-26.07.52.54/
safe-2012-05-27.08.06.28/
Safestrap recovery v1.09 (afraid to update to 2.0 without breaking more stuff)
What I'm looking to do is return my phone to working stock, which I believe was Gingerbread 2.3.6. That said, every time I've touched this thing trying to go back, I've black screened it. I don't live in an area with 4g (screw the mountains, and their 1x service), so any attempts to connect to the 4g network for any part of the process will require me driving into Pennsylvania, 30 minutes away. I've heard before that you can't return from the ICS leak to the Stock for the Droid 4, for various reasons (but i believe the important one was it was a later firmware and it isn't a process designed to go backwards)
I'd like to know if thats still the case currently, or if something has changed. I'm getting shaky wifi/data/cell reception up here, and its flawless back on stock. Hell, I've got an old razor as an emergency phone that's flawless up here. Next time I'll do more research for this stuff I was a proud OG droid owner, and ran cyanogenmod on it before the vid card fried one evening. Thought the droid 4 would be a good deal, but I've had nothing but trouble with the roms on it.
All that said, I can simply smash and return this droid if its the only way to get a stock one back, but I don't like destroying useful and good technology when I can help it. Besides, I like fixing the problems I create.
Thanks for the help XDA, either way.
-- TheChaoticDoctor
Did you flash the leak ICS from Motorola or did you use Safestrap and flash Gummy ICS?
If you flashed the leaked ICS, there is no going back. You will need to find get the files to flash the partial .219 system back so you can run the .206 leak update again.
If you just used safestrap to flash Gummy 1.2.0 then you can use the .219 flash files to completely re-do your phone.
Currently there are no ROMs to flash if you are on the leak, Hashcode just released his Safestrap 2.0 to do so but still nothing to flash. All the current ICS ROM builds are for the stock phone running the Gingerbread Kernel.
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
TheChaoticDoctor said:
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
Click to expand...
Click to collapse
You should probably go up to .208, that's the latest leak. Make sure to use rootkeeper, and follow all the instructions. So far I haven't lost root, but be aware I'm stuck on .206 because I don't want to lose root....
Look here for more info:
http://forum.xda-developers.com/showthread.php?p=26311439
Sent from my XT894 running ICS
First of all, it sounds to me like you've just flashed a ROM, not flashed the leak. If that is the case, you can just toggle the safe mode in safestrap to get back to stock. Safestrap lets you toggle between stock and the ROM. It is pretty awesome because you can play with the ROM and then go back to stock whenever you need to.
If you HAVE flashed the Motorola leak (as opposed to just a ROM) you are SOL.
If you haven't flashed the Motorola leak and just want to get back to factory conditions, you'll have to flash via RSDLite. That info you should be able to find here:
http://forum.xda-developers.com/showthread.php?t=1622256
Honestly I WOULD NOT flash the leak at this time. IMHO, it doesn't really offer enough to risk getting off the upgrade path forever, and losing the ability to flash back via RSDLite.
Hey everyone,
I'm new to this forum as far as registering goes, and i just have one simple question: Is it possible to completely remove the stock ROM on the droid bionic?
The reason i am asking is because i followed the rooting/flashing ROM guide
(http://forum.xda-developers.com/archive/index.php/t-1455888.html)
to a word, and after a couple of days of using my new ROM (eclipse 2.2 w/ fury x theme) i have been having problems.
ie: tried backing up stock rom with safestrap, says "error backing up android.secure.img/emmc skipping backup of application". then it says "error backing up android.secure.img/osh skipping backup of application"
Now my phone is back on the stock ROM, but even with ROM manager i cant even back up my stock ROM or flash a new ROM, i have also tried using the older versions of rom manager with no luck.The phone just reboots every time i do.
BTW= I am rooted (super user confirmed), and i have update ver 902.
I have everything backed up on my personal computer in case something goes horribly wrong
So i just wanted to know if i could skip this headache, and remove the stock rom completely and then flash my new "stock rom".
Does anyone know how to do something like this?
It almost sounds like you've got a bad flash in your phone that prevents the recovery utilities from being able to correctly identify all the partitioning at the block level like it should.
If I were in your situation, I'd definitely do a full FXZ flash back to 5.9.902 so that everything is rewritten, then you can try wiping and re-installing another ROM.
Awesome, i will give it a shot.thanks
I am running the most current version of Liquid ICS on my Droid Bionic and it is rooted and I use safestrap. However recently in the past couple of days when I have tried to flash it to a different ROM (i.e. AOKP, CM9, MIUI, etc) I get the motorola screen on reboot and then my screen goes and stays blank and does not load. I then have to pop my battery out and wipe wipe wipe and then restore.......Any advice??? (yes I also installed my gapps)
Motorola Droid Bionic / [AOSP]LiquidSmooth-ICS-v1.5mr1 ROM
SexyGermanChik said:
I am running the most current version of Liquid ICS on my Droid Bionic and it is rooted and I use safestrap. However recently in the past couple of days when I have tried to flash it to a different ROM (i.e. AOKP, CM9, MIUI, etc) I get the motorola screen on reboot and then my screen goes and stays blank and does not load. I then have to pop my battery out and wipe wipe wipe and then restore.......Any advice??? (yes I also installed my gapps)
Motorola Droid Bionic / [AOSP]LiquidSmooth-ICS-v1.5mr1 ROM
Click to expand...
Click to collapse
Hey man I have been having the same issue(s) as well. I have tried both CWM, and Safestrap following the typical clear cache/factory reset/wip dalvik etc(currently I am on .233). I suspect these roms (AOKP, and CM9, MIUI, etc) simply do not work on any of the other leaked based ROMS. From testing(I have tried everyone lol), they install fine on .902 based firmware some even work on .905, but installing over any of the ICS leaks seems to create boot loops(test in CWM, and Safestrap the results are the same). I would recommend flashing back to .902/905 and trying again. I am smelling a lot of bullshting come from people who say they are able to flash over any of the ICS Leaks. btw are you using CWM(4.x.x.x/5.x.x.x) or Safestrap?
Atheistnofaith said:
Hey man I have been having the same issue(s) as well. I have tried both CWM, and Safestrap following the typical clear cache/factory reset/wip dalvik etc(currently I am on .233). I suspect these roms (AOKP, and CM9, MIUI, etc) simply do not work on any of the other leaked based ROMS. From testing(I have tried everyone lol), they install fine on .902 based firmware some even work on .905, but installing over any of the ICS leaks seems to create boot loops(test in CWM, and Safestrap the results are the same). I would recommend flashing back to .902/905 and trying again. I am smelling a lot of bullshting come from people who say they are able to flash over any of the ICS Leaks. btw are you using CWM(4.x.x.x/5.x.x.x) or Safestrap?
Click to expand...
Click to collapse
I am using safestrap and never had a problem until last week flashing from my ICS leak to the other ROMS. Should I go back to stock and then install the leak again?
SexyGermanChik said:
I am using safestrap and never had a problem until last week flashing from my ICS leak to the other ROMS. Should I go back to stock and then install the leak again?
Click to expand...
Click to collapse
Yes, I would flash back the dev's are not putting correct information out most of these ROM'S (AOKP/CM9Gummy, etc) are not designed to be installed over any of the OTA Leaks(people keep insisting on it), and will cause boot loops like crazy. I have tested on two bionic's and the results where the same flashing over any ICS Leak to AOKP/CM9 etc will cause issues regardless of what 2nd stage boot loader you are using(Safestrap, or CWM via bootstrap). I would recommend flashing back to 902, or 905 using the SBF/FXZ method and installing eclipse 3.0(for .905 baseband), or sticking with the OTA Leaks untill the issues with flashing ROMS in both Safestrap, and CWM have been resolved or the dev's actually give solid advice(i.e. what firmware is actually needed, or what flashing requirements should be meet. Thanks again!!!
Atheistnofaith said:
Yes, I would flash back the dev's are not putting correct information out most of these ROM'S (AOKP/CM9Gummy, etc) are not designed to be installed over any of the OTA Leaks(people keep insisting on it), and will cause boot loops like crazy. I have tested on two bionic's and the results where the same flashing over any ICS Leak to AOKP/CM9 etc will cause issues regardless of what 2nd stage boot loader you are using(Safestrap, or CWM via bootstrap). I would recommend flashing back to 902, or 905 using the SBF/FXZ method and installing eclipse 3.0(for .905 baseband), or sticking with the OTA Leaks untill the issues with flashing ROMS in both Safestrap, and CWM have been resolved or the dev's actually give solid advice(i.e. what firmware is actually needed, or what flashing requirements should be meet. Thanks again!!!
Click to expand...
Click to collapse
So I wonder why it has worked for this long and just stopped flashing?
Hello all, I'm not new to rooting and flashing roms but am new to the Droid Bionic. I've been doing hours of research and haven't been able to find a solution to my problem yet although it is probably here somewhere. I have a Droid Bionic and have been on Gingerbread for some time. Im not sure of the official update im on but I decided Id like to try an ics leak. The one i tried had two files: one was called SpearmintGum_targa-Release-1.2, and the other was called speargapps-ics-20120304-signed. Now i had a friend help me out and we did it together but we both failed to read the instructions saying not to reboot before installation of the 2nd package. So now i have my Droid Bionic stuck in a bootloop and nothing ive tried works. Ive tried RSD Lite to go back to stock .902 and it didnt work. I tried rebooting into stock recovery and i just dont know what to do! If there is already an answer to my question Id really appreciate to be pointed in the right direction to the thread. If anyone knows what i can do to fix id really appreciate it. Thanks in advance
Need to find out what version you're on. Settings, scroll to bottom, about phone, and get it. Also, if you're not on a later build, no reason to fxz to 902 when 905 is out. Also need RSD 5.7 and latest moto drivers. Let me know when you get all that. I'll walk you through it.
Sent from my DROID BIONIC using Tapatalk 2
he said he gets boot loops, i'm guessing he can't get into settings, about, etc
Did you use as or BS to install? You should be able to pull battery if on BS, wipe all and restore nandroids. Otherwise post above has a valid point.
Sent from my DROID BIONIC using Tapatalk 2
Try this:
First download an ics leak for bionic. Then RSD to .905 gingerbread. Put the ics leak on your phone and boot into stock recovery. Install the leak from there and see if your phone boots up. Wait at least 10 minutes before seeing if it failed or not.
For the record you were trying to flash a ics rom not a ics leak
All ics leaks just require to flash 1 file in stock recovery
You can try to use this script to fxz back to 905 and then try a ics leak
http://www.droidforums.net/forum/droid-bionic-hacks/214902-downgrade-902-no-app-data-loss.html
AND MAKE SURE YOU READ THE OP AND UNDERSTAND THE INSTRUCTIONS BEFORE YOU DO ANYTHING
good luck
If your still having issues, I can help. PM me.