If im running the 2.2 leak version and am having bootlooping issues and am unable to get into clockwork, can I just SBF to official 2.2?
yes you can
Cool reason I asked is because I did it last night and it just keeps boot looping now tried to flash it about 3 different times. Any suggestions as to how i can get it going? The SBF file fully flashes to the phone RSD doesn't give any errors and reboots phone as it normally would but when it starts up it just boot loops I actually left it going for about 30mins last night to see if it would strat up, so far it has not.
Just to make sure- and I know this is a lame question - but just to make sure - you are using the new 2.2 SBF...
VRZ_MB810_2.3.15_1FF_01
Yeah the SBF im using matches that file name. It was late last night so only really got to try and flash it a few times and im stuck at work now just trying to see if anyone else had any similar issues really. Also im on windows 7 64bit if that may cause any issues.
You may want to try wiping the data and cache from the default recovery. Power on your phone with the home key pressed and press the search key. You'll have options for wiping data and cache. Maybe you could still have remnants of the 2.2 leaks in there?
Sent from my DROIDX using XDA App
I think I tried that last night will do again to be sure though and thanks for all the help.
when I SBF'd back to stock 2.2 I had to boot back into recovery and apply the update.zip, once I did that it booted back up without issue.
Lol facepalm. The update.zip heh, did not try that yet. Gonna try it as soon as I get home and ill update when I do. Thanks for all the suggestions.
Got it to boot after doing factory reset thanks again for all the help
Related
Hey guys,
I recently got a new phone so haven't been using my milestone anymore and a friend offered to buy it from me.
So I of course was going to flash a stock sbf back on for him, i chose to flash 2.2.1.
I immediately ran into problems.
First off it worked fine, rsd (ver 5.3.1) gave me a pass, i disconnected the phone and rebooted, the android logo shows up and all is joyful in the world.
This is where the problems arise...
I rebooted into recovery to do a full wipe, and a cache and dalvik wipe, then i rebooted once more.
Instead of rebooting normally the phone now just goes immediately to bootloader.
No matter what i try it jsut alays goes back to bootloader straight away. there is no error message it just says ok to program blah blah like normal.
i've since flashed all the different bootloaders, the vulnerable recovery, every single moto sbf i could find, i even tried removing the volume buttons and keyboard to make sure the buttons weren't broken and automatically taking me there due to a short.
no luck.
did i kill this milestone? seriously, any ideas would be appreciated because i am totally stumped now.
Cheers.
Please someone help. I still havent gotten any further with this.
Sent from my LG-P920 using XDA Premium App
Did you try restoring a stock nandroid, that is if you can enter recovery mode.
Sent from my GT-I9100 using Tapatalk
No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request
Shwaguy said:
No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request
Click to expand...
Click to collapse
In safe strap did you ever change to 'safe system' before you started wiping?
/Droid3
Yes sir. I followed Hashcode's procedures from his site. I am sure it is just something small and easy that will get me going in the right direction.
I have it back on the "non-safe" mode at the moment and now all I have is a wifi connection. I checked the APN and nothing was listed. Entered the Telus APN info and it doesn't save so I grabbed an APN manager from the market. It says it is active but still no connection. I am thinking of doing a factory reset to see if that will help.
I just turned 40 today and getting my phone working again would be a great gift.
Shwaguy said:
Yes sir. I followed Hashcode's procedures from his site. I am sure it is just something small and easy that will get me going in the right direction.
I have it back on the "non-safe" mode at the moment and now all I have is a wifi connection. I checked the APN and nothing was listed. Entered the Telus APN info and it doesn't save so I grabbed an APN manager from the market. It says it is active but still no connection. I am thinking of doing a factory reset to see if that will help.
I just turned 40 today and getting my phone working again would be a great gift.
Click to expand...
Click to collapse
My suggestion is to start over then..sbf your phone if you have one so you have atleast stock..then reroot it and do not install bootstrap or anything else..just instal safestrap..then go to nonsafe system..I don't think you need to wipe anything if its your first time but you can wipe anyway if you want lol then flash a rom (say cm9 or steeldroid or whatever) then reboot..it will take a while for your first boot but it should boot..let me know if this helps! Just don't boot up until after you flash a rom lol and remember safe rom is your stock rom and nonsafe is you're new rom that you're trying to flash
/Droid3
beard0 said:
My suggestion is to start over then..sbf your phone if you have one so you have atleast stock..then reroot it and do not install bootstrap or anything else..just instal safestrap..then go to nonsafe system..I don't think you need to wipe anything if its your first time but you can wipe anyway if you want lol then flash a rom (say cm9 or steeldroid or whatever) then reboot..it will take a while for your first boot but it should boot..let me know if this helps! Just don't boot up until after you flash a rom lol and remember safe rom is your stock rom and nonsafe is you're new rom that you're trying to flash
/Droid3
Click to expand...
Click to collapse
Non safe is the stock. Safe is the one you're flashing.
Sent from my XT862 using xda premium
Thanks beard0, I have not seen a sbf file for the 860 Bell. Found a system dump but thanks to the fbi it is unavailable.
Another problem popped up unfortunately. I lost connectivity. I just have wifi now. Last month when I got the phone I entered the apn info from the Telus website and everything was fine. Now when I try it I get a message saying that "mmc field must be 3 digits" I thought that info was grabbed from the sim? Regardless, I added the rest of the info required, saved, but it doesn't save the info?? I tried apn manager and it had Telus listed, selected that but still no luck. After much searching I just did the factory reset, added apn info and still have no connectivity.
I have spent so many hours on these problems and really don't know where to go from here. Going to root/safestrap etc now.
Out of curiosity I tried turning on simlock. It says no simcard detected. It worked fine for over a month and still works in my backflip though. I think the gf has a simcard in her phone so I am going to see if it reads hers when she gets here.
Shwaguy said:
No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request
Click to expand...
Click to collapse
Maybe dumb question..
After rthe steps did you Flashed the actual ROM????
Just askbecause i dont see it. Mentioned
Also, If you disable safe systemthen youshould be able to go back to regular stock.....
Enviado desde mi XT862 usando Tapatalk
Ya, I flashed the rom, tried the alpha 6 ics one also. It was after doing this then rebooting (still in safe) that i got the bootloop issue. I disabled safe system and went back.
Seems it doesn't really matter now though. It doesn't seem to be reading my simcard. No service (except wifi), Tried enabling simlock, says there is no card in it. Card works in my Backflip. I tried the g/f's Bell card and still no service, etc. Going to search around a bit and see if anything pops up but I may be sending it back. lol
I am really hoping that I dint screw big time myself by trying SimplyAOKP 6 FULL ~ ODEXED !!! But I know am !
I HAD Galaxy Captivate and loaded Talon Kernel with Continnum6.1 for a while and as it was having performance issues and very slow response, thought of trying ICS. Thus I ended up with SimplyAOKP 6 FULL ~ ODEXED. Downloaded the latest version as of yesterday and did factory reset, cleared dalvik cache and everything mentioned in the site. Then flashed from the sd card. It just stayed at Devilkernel picture. It wont move further and wont respond to the keys/buttons.
Took the battery out and restarted, it boots up and stays at the screen which shows Devilkernel Galaxy S and thats it, stayed there for a day!!!
It wont respond to any button and I have to take out the battery to even come out of that screen. It wont show up in the laptop if I connect thru USB.
Please let me know if theres anything I can do or I just am done?
I am soo sad that I tried this, I should I have atleast waited for my contract to be over with ATT to try anything, now am really f-d up?
Please let me know (what ever be the reply)!
Thanks
B
Take a look at the "Captivate Connection Issues" thread for ways to get into recovery or download mode.
If you had backed up all your stuff before flashing, you can just flash a stock rom and try to install ICS again.
You are in no way screwed at all. You can probably still get into recovery mode. If not, download mode will be there.
Sent from my SGH-I897 using XDA
Firstly, this device has never been rooted or had anything flashed to it. It is completely stock.
My step-daughter has been having issues with her Droid 4. About a month back or so, she started noticing that it wouldn't boot. It would flash the Motorola logo, and then the screen would just hang on the bootanimation. Eventually if we rebooted (power+vol down) enough times it would boot up.
Last night however, this happened again and it would not boot at all. I tried rebooting many times and it would never get past the bootanimation. After about 20 or so reboots I figured it was time for a Factory Reset. After the reset however, it wouldn't even display the bootanimation. It would still display the Motorola splash screen, but after that the screen would just go black with the display is still on. I Factory Reset several more times and nothing. Eventually after a number of times rebooting, it finally booted up. Well that was yesterday. Today she had to reboot it and it wouldn't boot again. Would just hang on a black screen.
I'm about ready to send it back since it's still under warranty, but figured I would check here to see if any of the amazing XDA guru's had experienced this and found a solution. I searched Google and this forum and didn't really see anything. Any help would be greatly appreciated!
jdiamond7 said:
Firstly, this device has never been rooted or had anything flashed to it. It is completely stock.
My step-daughter has been having issues with her Droid 4. About a month back or so, she started noticing that it wouldn't boot. It would flash the Motorola logo, and then the screen would just hang on the bootanimation. Eventually if we rebooted (power+vol down) enough times it would boot up.
Last night however, this happened again and it would not boot at all. I tried rebooting many times and it would never get past the bootanimation. After about 20 or so reboots I figured it was time for a Factory Reset. After the reset however, it wouldn't even display the bootanimation. It would still display the Motorola splash screen, but after that the screen would just go black with the display is still on. I Factory Reset several more times and nothing. Eventually after a number of times rebooting, it finally booted up. Well that was yesterday. Today she had to reboot it and it wouldn't boot again. Would just hang on a black screen.
I'm about ready to send it back since it's still under warranty, but figured I would check here to see if any of the amazing XDA guru's had experienced this and found a solution. I searched Google and this forum and didn't really see anything. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Only other I can think to do would be to flash the fastboot files. A factory reset basically just wipes data while fastbooting it should reset the system itself to complete bone stock. You can do this using rsdlite or download a utility like jsnweitzel's ICS Only Utility in the Dev section.
Really sounds like a hardware issue to me since it's not rooted or anything but still might be worth a shot.
Sent from my Droid 4 - LiquidSmooth
kwyrt said:
Only other I can think to do would be to flash the fastboot files. A factory reset basically just wipes data while fastbooting it should reset the system itself to complete bone stock. You can do this using rsdlite or download a utility like jsnweitzel's ICS Only Utility in the Dev section.
Really sounds like a hardware issue to me since it's not rooted or anything but still might be worth a shot.
Click to expand...
Click to collapse
Thank you very much for the quick reply. I've downloaded jsnweitzel's ICS Only Utility and am charging up the phones battery so I can use it.
Just a quick question before I do this. I'm assuming that running the restore through ICS Only Utility is flashing a stock system image. That image is not rooted is it? Not that I would typically care, but if I do have to bring it back to Verizon I don't want them hassling me for rooting the device.
jdiamond7 said:
Thank you very much for the quick reply. I've downloaded jsnweitzel's ICS Only Utility and am charging up the phones battery so I can use it.
Just a quick question before I do this. I'm assuming that running the restore through ICS Only Utility is flashing a stock system image. That image is not rooted is it? Not that I would typically care, but if I do have to bring it back to Verizon I don't want them hassling me for rooting the device.
Click to expand...
Click to collapse
The image flashed in the fastboot process is completly stock, unrooted.
Sent from my Droid 4 - LiquidSmooth
Thanks for the help but that didn't do it. Guess I'll be taking it back to Verizon!
Sent from my SCH-I535 using xda app-developers app
Let me start by saying,this isn't my first rodeo,i've been rooting since the beginning of the G1,but this one has me stumped.
Ive got a Moto Atrix HD, rooted and bootloader unlocked running Batakangs Deodexed stock. It started feeling kinda laggy so I decided to jump into recovery (CWM 6) and delete the Devlik cache Battery stats etc. basically everything but user data so I didn't have to start from scratch. Ive done it in the past and it speed things up considerably with no ill side effects. So I did it thins time and immediately got the "unable to access recovery log/command" error. So I decided to reboot recovery and try it again and the same error came up as soon as it booted into it. I decided to just use rsd and do a complete fresh stock att install,but it wouldn't go to fastboot and rsd didn't see the phone neither did adb.So I tried a full wipe. Didn't work. So idecided to do a rom reinstall and see if that fixed it.nothing. So I tried another wipe and this time it wouldn't boot back into recovery,stays stuck on the first boot screen. I even went through the trouble to remove the back and unscrew the battery and do a battery pull with no luck. During all this I had RSD pulled up and it never saw the phone to give me something to work with. Im kinda stumped on this one,i can normally figure it out without issues,searched here and I didn't see anyone with the same issue exactly. Im open for ideas. Thanks
Updatek so I managed to get PhilzTouch recovery installed,and got Carbon installed. But still getting the error in recovery.Its finally booting at least tho....Finally got to use MythTools to reinstall the recovery and all is fixed..
TabascoTX said:
Let me start by saying,this isn't my first rodeo,i've been rooting since the beginning of the G1,but this one has me stumped.
Ive got a Moto Atrix HD, rooted and bootloader unlocked running Batakangs Deodexed stock. It started feeling kinda laggy so I decided to jump into recovery (CWM 6) and delete the Devlik cache Battery stats etc. basically everything but user data so I didn't have to start from scratch. Ive done it in the past and it speed things up considerably with no ill side effects. So I did it thins time and immediately got the "unable to access recovery log/command" error. So I decided to reboot recovery and try it again and the same error came up as soon as it booted into it. I decided to just use rsd and do a complete fresh stock att install,but it wouldn't go to fastboot and rsd didn't see the phone neither did adb.So I tried a full wipe. Didn't work. So idecided to do a rom reinstall and see if that fixed it.nothing. So I tried another wipe and this time it wouldn't boot back into recovery,stays stuck on the first boot screen. I even went through the trouble to remove the back and unscrew the battery and do a battery pull with no luck. During all this I had RSD pulled up and it never saw the phone to give me something to work with. Im kinda stumped on this one,i can normally figure it out without issues,searched here and I didn't see anyone with the same issue exactly. Im open for ideas. Thanks
Updatek so I managed to get PhilzTouch recovery installed,and got Carbon installed. But still getting the error in recovery.Its finally booting at least tho....Finally got to use MythTools to reinstall the recovery and all is fixed..
Click to expand...
Click to collapse
I just jumped in and read your post. unfortunately, I had no chance to reply to you after I read the last line But it's nice to know my tools is helpful.