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
Related
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
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.
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
Okay so basically yesterday I got my lovely spanking HTC ONE (m7) and quickly proceeded to downloading the One_All-In-One_Kit, uncloked the bootloader and rooted the phone successfully.
I then proceeded to download ARHD and flash it accordingly, everything went swimmingly, the ROM installed via Aroma as it should, yep all nice and dandy. NO! After the installation, I rebooted, get to the HTC bootscreen, I'm presented with a nice new red message at the bottom and then the phone restarts itself, tries to enter recovery, that doesn't work, then it tries booting up again and does the same thing over and over.
I've flashed the ROM several times and get the same thing each time. I've tried RGUI and get the same sort of thing with that only with RGUI the phone doesn't try rebooting into recovery it just stays on the HTC bootscreen.
I'm desperate for help on this so please, if anyone has any insight it would be highly appreciated.
I hope you're not also flashing any of the custom kernels on here....cos they're not compatible with 4.2.2
Nope not flashing anything else but the ROM itself..
after flashing did you try "fastboot erase cache" ?
sometimes that helps when phones get stuck on the HTC logo after a rom flash.
Use the toolkit to erase cache
Sent from my HTC One using xda premium
Yeah done that several times too. Can't seem to work out why it isn't working and I too can't find the correct RUU for my device meaning I can't even take it back to stock
try to hold power + volume down to get into the bootloader to get back into recovery. Once in recovery factory reset, erase cache, erase dalvik, and reflash the rom.
also download the andorid SDK for fastboot and adb, then try "adb reboot bootloader" if you can not get back into the bootloader to get into recovery
My friend had his do this loop as well, we had trouble getting it into recovery, but held the button combo of power and vol down several times (probably 10) and it FINALLY booted into the custom Clockwork recovery, then we reflashed and it worked like a charm.
Also try redownloading... it could be a bad download
Sent from my Nexus 10 using Tapatalk HD
rilee said:
Okay so basically yesterday I got my lovely spanking HTC ONE (m7) and quickly proceeded to downloading the One_All-In-One_Kit, uncloked the bootloader and rooted the phone successfully.
I then proceeded to download ARHD and flash it accordingly, everything went swimmingly, the ROM installed via Aroma as it should, yep all nice and dandy. NO! After the installation, I rebooted, get to the HTC bootscreen, I'm presented with a nice new red message at the bottom and then the phone restarts itself, tries to enter recovery, that doesn't work, then it tries booting up again and does the same thing over and over.
I've flashed the ROM several times and get the same thing each time. I've tried RGUI and get the same sort of thing with that only with RGUI the phone doesn't try rebooting into recovery it just stays on the HTC bootscreen.
I'm desperate for help on this so please, if anyone has any insight it would be highly appreciated.
Click to expand...
Click to collapse
Just a word of advice. Update your profile to say your country and carrier. It helps people identify which device model and carrier you use.
Thanks for the help so far guys, basically I can get into recovery, that's not the problem, the problem is the phone gets stuck on the HTC screen after the ROM has been installed. I'll try downloading the ROM again when I can, in the hope that it is just a bad download. Hopefully this is the case and re-flashing a newly downloaded ROM will solve all my issues.
I'll post back with the result as and when I can.
rilee said:
Thanks for the help so far guys, basically I can get into recovery, that's not the problem, the problem is the phone gets stuck on the HTC screen after the ROM has been installed. I'll try downloading the ROM again when I can, in the hope that it is just a bad download. Hopefully this is the case and re-flashing a newly downloaded ROM will solve all my issues.
I'll post back with the result as and when I can.
Click to expand...
Click to collapse
I would be restoring my nandroid backup and make sure the phones that way first and then start again
Thanks again for the help guys, went to phones 4 u this afternoon and he exchanged the device for me.
Long story short: Phone won't boot past "Unlocked Bootloader" warning; Recoveries won't stick; Unknown Error & Freezing when trying to Flash System.img
I own an ATT Locked Moto X, but went ahead and unlocked it by purchasing the oem code. No issues there.
I decided to go ahead and try rooting it too, and was able to flash TWRP as my recovery. Still, everything seemed to be looking good, until I tried hard rebooting (to see if root would last). Upon rebooting, I could not get past the warning sign, notifying me that the bootloader was unlocked. I waited, and waited, and restarted again, but all progress stopped there. I would be the first to admit that whatever happened was probably my fault; perhaps I flashed some files in the wrong order, or entered a wrong command into fastboot. I don't know, and frankly don't care. My only question is how to get out of this mess and back to rooting, or at the very least, back to stock ROM now that I'm unlocked.
Booting into recovery only leads to the red triangle over an open android mascot, with the "Android Recovery" title. So clearly TWRP didn't stick; I tried reflashing, but nothing lasts past reboot. Then I tried flashing Philz Touch instead, which, upon exit, notified me that root was not enabled. So I rooted, rebooted, and was finally able to see Philz Tough again, even though I still can't boot normally. That time, both Philz Touch as well as root seemed to have stuck.
With that minor victory I downloaded the latest firmware for my model and tried to flash the components over, thinking I had somehow corrupted the existing OS files, but here's where it gets particularly frustrating. I am able to flash every file except for system.img, even though I am using moto-fastboot, which I understand is a common mistake. I get no specific error code, simply "Unknown Error," upon which the phone is frozen in fastboot. The phone remains unresponsive until I hard reboot [back into fastboot], and see that, once again, Recovery is back to stock. So now I'm baffled. I can't seem to find a way to flash the system file, factory resetting doesn't work, and my recoveries are constantly reverted back to stock. Does anyone have any advice, or suggestions for what I could try next?
You try RSD lite?
Sent from my XT1058 using xda app-developers app
southern87 said:
You try RSD lite?
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I was already downloading it just as I saw your post, as my last-ditch effort. It also failed, but it gave me "Unknown USB Error," which is all I needed, it seems. I tried a different USB slot on another side of the computer, and lo-and-behold, the flash finished.
I'm not sure what saddens me more, the fact that I pushed off making this post for hours, only to have the solution less than an hour after I do, or the fact that I never thought to try a different USB port... In any case, sorry for the uselessness of this post. I think I'll save rooting for another day though...