Related
i bought a phone on ebay thinking i was getting a deal come to find out the phone appears to be bricked it boot to bootloader straight away when i tryed to follow steps on trying to flash back to stock with PD98diag.zip on micro sd i get error message Main version is older ! update fail press <power> to reboot selecting reboot made no difference back to same boot loader when i try factory defaults reboots to the same boot loader , in recovery option selected i get ! with icon and reboots back to boot loader i cant seem to escape this !fast boot same thing back to this dreaded loader i even tryed ace hack 12.3 i get device is offline althought initialy it see's it at the main menu i tryed running Offical RUU and i get error 170 every singal time please help
HBOOT-0.85.0019
MICROP_0433
RADIO-26.06.06.30_M
eMMC-boot
dec 27 2010
Inspire 4g
Maybe this will help you get back to stock....
Here...
gmanunited said:
Maybe this will help you get back to stock....
Here...
Click to expand...
Click to collapse
no go it dosnt load a driver during charging mode
try this one... its the gingerbread ruu already in PD98IMG.zip... see if this works
http://www.multiupload.com/P13PZJ2JBN
marsdta said:
try this one... its the gingerbread ruu already in PD98IMG.zip... see if this works
i got it to magically to restore after 5 hours of messing around but as it booted it had a sign saying it was in safe mode on the bottem left corner so i rebooted and bam its back to bootloader screen so evidently there is something wrong with this phone .
Click to expand...
Click to collapse
I would personally run the ruu, to fully wipe and start from scratch. You never know what the previous owner did or did not do. If that doesn't help then I would say the phone does have an issue
tokoam said:
i bought a phone on ebay thinking i was getting a deal come to find out the phone appears to be bricked it boot to bootloader straight away when i tryed to follow steps on trying to flash back to stock with PD98diag.zip on micro sd i get error message Main version is older ! update fail press <power> to reboot selecting reboot made no difference back to same boot loader when i try factory defaults reboots to the same boot loader , in recovery option selected i get ! with icon and reboots back to boot loader i cant seem to escape this !fast boot same thing back to this dreaded loader i even tryed ace hack 12.3 i get device is offline althought initialy it see's it at the main menu i tryed running Offical RUU and i get error 170 every singal time please help
HBOOT-0.85.0019
MICROP_0433
RADIO-26.06.06.30_M
eMMC-boot
dec 27 2010
Inspire 4g
Click to expand...
Click to collapse
If you're getting that message, then you are trying to install an RUU that is older than the version reported by the phone. Try using the RUU just recently released for GB:
http://forum.xda-developers.com/showthread.php?t=1191959
Use the PD98IMG.zip linked at the bottom of the first post and try it exactly as you did above. If it still fails, then the device has likely been rooted in the past and used a DHD ROM with a later version number, then returned to S-ON. You'll need to re-root in this case. Use the Ace Hack Kit. It should still work even if your version is messed up since the first step is to "fake" and older version code:
http://forum.xda-developers.com/showthread.php?t=952352
i can get it to boot 3 out of 30 times after offical gingerbread ruu but when it boots it boots to safe mode everytime any ideas guy ?
Somebody was/is having the safemode problem
http://forum.xda-developers.com/showthread.php?t=1222646
Gene suggested that maybe the volume button might be stuck and that's what is causing the safemode
I ran into safe mode awhile ago, I somehow got out of it, made a post and no one responded.. lol
Sent from my Motorola StarTac using XDA App.
Hello,
I have an Evo Shift stuck in the boot loop. As soon as I put the battery in all it does is reset itself to the screen with the white background and green "HTC" logo, and will keep restarting until the battery dies.
If I hold volume down and turn it on, it does go into the bootloader, but picking ANYTHING, such as recovery or factory reset, does nothing but sending it back to the HTC screen.
I have tried flashing the RUU.exe (2.27.651.2) through Fastboot USB and it completed successfully, but it just restarts right back to the HTC screen. I have also put PG06img that I found on here on the root of my card, and it will never load it up.
Are there any other solutions anyone can think of? They would be much appreciated. I see a lot of these threads for regular Evos, but not for Shifts.
The only other thing I really know about the phone is that it is:
S-On
Hboot- 0.98.0001
Radio- 1.08.00.0506
Thank you so much for all of your help!
Seems to me you aren't rooted and that's more than likely your problem, boot into fastboot and use the ruu application for gingerbread.
Sent from my PG06100 using Tapatalk
Rooster85 said:
Seems to me you aren't rooted and that's more than likely your problem, boot into fastboot and use the ruu application for gingerbread.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
While I am pretty sure I am not rooted, if you are talking about the early RUU release; 1.17.651.1, the application starts and then ends up failing in the beginning of the process. Is this what you are talking about? The drivers should be all good, the application starts to flash and then dies though. Thanks!
samcrac said:
While I am pretty sure I am not rooted, if you are talking about the early RUU release; 1.17.651.1, the application starts and then ends up failing in the beginning of the process. Is this what you are talking about? The drivers should be all good, the application starts to flash and then dies though. Thanks!
Click to expand...
Click to collapse
Use the new RUU. But make sure your SD card is formatted to a FAT32 partition. (Stock 2gig sd card and some other store boughts are not)
You can format on your computer and then place the RUU on the root of sd card again
(Bootloader won't recognize the ruu zip if not partitioned)
Sent from my Supreme Shift
notsointeresting said:
Use the new RUU. But make sure your SD card is formatted to a FAT32 partition. (Stock 2gig sd card and some other store boughts are not)
You can format on your computer and then place the RUU on the root of sd card again
(Bootloader won't recognize the ruu zip if not partitioned)
Click to expand...
Click to collapse
Ok, I just did this, everything updated fine and all completeted on the bootloader. It then said "press power to reboot." I did so, and went right back into the same boot loop. Any other ideas. I figured running this, and the RUU.exe on the computer were the sure fire ways to get this thing working again???
samcrac said:
Ok, I just did this, everything updated fine and all completeted on the bootloader. It then said "press power to reboot." I did so, and went right back into the same boot loop. Any other ideas. I figured running this, and the RUU.exe on the computer were the sure fire ways to get this thing working again???
Click to expand...
Click to collapse
So just a little information.
you said your not rooted?
So that means you have no ability to flash anything because you have no custom recovery and the bootloader isnt unlocked (S-on)
So what DID you do before it bootlooped? there had to have been something you were trying to do.
Not trying to blame anything on you at all just want to make sure we are helping the most accurate way possible
notsointeresting said:
So just a little information.
you said your not rooted?
So that means you have no ability to flash anything because you have no custom recovery and the bootloader isnt unlocked (S-on)
So what DID you do before it bootlooped? there had to have been something you were trying to do.
Not trying to blame anything on you at all just want to make sure we are helping the most accurate way possible
Click to expand...
Click to collapse
No I hear ya. I was sold the phone fairly cheap and was told "all you need to do is to reinstall the RUU, that is all that is wrong." Obviously I was skeptical, but when I checked everything out, everything looked good, and again, for the price, I knew it was a gamble. That being said, I'm sure something was tried in order to modify the phone and this is how it got like this.
I have soft bricked my old Evo 4g a handful of times and an RUU or Rom flash would always solve the problem.
Anyway, there is no custom recovery, and I'm pretty sure theres no root because it is still "S-ON," I am just trying to see if anyone here has any more info before it goes in for repair.
The only last thing I would guess you MIGHT be able to do is to install a custom recovery, but is there ANY way to do this by just being in the bootloader and using FASTBOOT USB? Any more help is greatly appreciated. Thanks!
samcrac said:
No I hear ya. I was sold the phone fairly cheap and was told "all you need to do is to reinstall the RUU, that is all that is wrong." Obviously I was skeptical, but when I checked everything out, everything looked good, and again, for the price, I knew it was a gamble. That being said, I'm sure something was tried in order to modify the phone and this is how it got like this.
I have soft bricked my old Evo 4g a handful of times and an RUU or Rom flash would always solve the problem.
Anyway, there is no custom recovery, and I'm pretty sure theres no root because it is still "S-ON," I am just trying to see if anyone here has any more info before it goes in for repair.
The only last thing I would guess you MIGHT be able to do is to install a custom recovery, but is there ANY way to do this by just being in the bootloader and using FASTBOOT USB? Any more help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
It shouldn't have a custom recovery if it shows s-on.
I don't see why the RUU wouldn't work.
Honestly it doesn't sound like a softbrick- sounds like its just bricked (Which ive only heard of 1 Shift getting bricked completley)
notsointeresting said:
It shouldn't have a custom recovery if it shows s-on.
I don't see why the RUU wouldn't work.
Honestly it doesn't sound like a softbrick- sounds like its just bricked (Which ive only heard of 1 Shift getting bricked completley)
Click to expand...
Click to collapse
Make it 2! Thanks for your help though!!!
Also Stuck In A Bootloop
samcrac said:
Hello,
I have an Evo Shift stuck in the boot loop. As soon as I put the battery in all it does is reset itself to the screen with the white background and green "HTC" logo, and will keep restarting until the battery dies.
If I hold volume down and turn it on, it does go into the bootloader, but picking ANYTHING, such as recovery or factory reset, does nothing but sending it back to the HTC screen.
I have tried flashing the RUU.exe (2.27.651.2) through Fastboot USB and it completed successfully, but it just restarts right back to the HTC screen. I have also put PG06IMG that I found on here on the root of my card, and it will load it up (I'll see the blue loading bar and then the brown loading bar in the top right hand corner of the screen), but it then checks it again, and then goes back to the original screen for the bootloader.
Are there any other solutions anyone can think of? They would be much appreciated. I see a lot of these threads for regular Evos, but not for Shifts.
The only other thing I really know about the phone is that it is:
S-On
Hboot- 0.98.0001
Radio- 1.08.00.0506
Thank you so much for all of your help!
Click to expand...
Click to collapse
I'm trying to resolve a very similar problem as him, but I know of the history of my phone (since I'm the only owner), so hopefully an answer for me can assist him also.
The Story: One day, I'm playing Uno HD (downloaded from Android Market). I toss out a Draw 4, and then I see: "Google Infrastructure Failure" and a Triangle with an exclamation mark. I reset the phone, and it starts up fine. Then a few hours later, my phone randomly restarts itself into the bootloader screen after trying to reload the home screen (because the memory manager is overly aggressive).
I see no HTC Screen. It goes straight to the bootloader without any input. If I plug it to the charger from an off state, the amber light comes on, and 10 seconds later, bootloader screen. With a battery, it appears automatically after 45 seconds.
Fastboot can read my memory card just fine. It's already been re-formatted as FAT32 in my pitiful attempt to try to repair it. It's checked and read a PG06IMG file I placed on the SD Card's root, went through the entire process of reading it, but it doesn't ask me if I want to upgrade. It takes me back to the original screen. (Maybe I'm loading the wrong file).
Recovery and Factory Reset immediately restarts the bootloader after showing me the skateboarding android splash screen.
I've also tried to flash the newest stock RUU for it. (2.76.651.4), but after the RUU sends the command to start up in bootloader mode, the phone shuts off. Thus giving me the connection error.
(Maybe if someone could rewrite the .exe file to not send out the command to begin loading as if it was in the bootloader screen, it could work. I'd pay for that.)
Other Stuff:
ROM: Stock Sprint Gingerbread OTA ROM. I've been living the vanilla life. No root access. No funny stuff. Just a stock phone with apps (Third Blade, Uno HD, ASTRO File Manager, ect...)
Directly from bootloader screen:
SPEEDY XA SHIP S-ON
HBOOT-0.98.0001
RADIO-1.08.00.0506
eMMC-boot
April 11 2011, 22:32:34
Is there a way we can flash a file from the SD Card which will turn off the security and/or temp/perm root it? (forgive my noobness for such a question)
EDIT: I'm referring to a way that's outside of the adb push method. My device can't be found, and the device won't get past the bootloader screen, so that method doesn't help me too much. However, I do have the ADK Installed and the ADB Command Line works fine.
Ok .. HERE'S THE SOLUTION:
First off all if your S- ON it means you are NOT rooted
If you get stuck in a bootloop .. don't worry it can be fixed.
What you need to do is download PG06IMG.ZIP and place it on your sd card, you can access your sd card by going into recovery then mount section, then usb. This will allow you to move the file from your computer to the root of your sd card.
Once you do this be sure you back up any info you don't want to lose. Once you have the file in place, go back to fastboot ( hold vol down and power) it will read file and when it asks you to update press vol up. It will take a few minutes to update this will revert your phone back to stock but if you have an old recovery it will not do a full restore, it will only update the rom.
Once you get your phone back to working, I recommend updating your recovery by downloading Rom Manager and flashing the latest clockwork recovery. This problem happens usually due to an old recovery.
One other thing you can try if you do NOT want to reset your phone, you can try flashing a new kernal.
Sent from my PG06100 using Tapatalk
RUU won't work if your stuck in bootloop ..
Sent from my PG06100 using Tapatalk
If you want to root your phone use visionary to temp root then use shift rr .. you can then flash a custom recovery which is essential to avoid this from happening again
flylike2kites said:
I'm trying to resolve a very similar problem as him, but I know of the history of my phone (since I'm the only owner), so hopefully an answer for me can assist him also.
The Story: One day, I'm playing Uno HD (downloaded from Android Market). I toss out a Draw 4, and then I see: "Google Infrastructure Failure" and a Triangle with an exclamation mark. I reset the phone, and it starts up fine. Then a few hours later, my phone randomly restarts itself into the bootloader screen after trying to reload the home screen (because the memory manager is overly aggressive).
I see no HTC Screen. It goes straight to the bootloader without any input. If I plug it to the charger from an off state, the amber light comes on, and 10 seconds later, bootloader screen. With a battery, it appears automatically after 45 seconds.
Fastboot can read my memory card just fine. It's already been re-formatted as FAT32 in my pitiful attempt to try to repair it. It's checked and read a PG06IMG file I placed on the SD Card's root, went through the entire process of reading it, but it doesn't ask me if I want to upgrade. It takes me back to the original screen. (Maybe I'm loading the wrong file).
Recovery and Factory Reset immediately restarts the bootloader after showing me the skateboarding android splash screen.
I've also tried to flash the newest stock RUU for it. (2.76.651.4), but after the RUU sends the command to start up in bootloader mode, the phone shuts off. Thus giving me the connection error.
(Maybe if someone could rewrite the .exe file to not send out the command to begin loading as if it was in the bootloader screen, it could work. I'd pay for that.)
Other Stuff:
ROM: Stock Sprint Gingerbread OTA ROM. I've been living the vanilla life. No root access. No funny stuff. Just a stock phone with apps (Third Blade, Uno HD, ASTRO File Manager, ect...)
Directly from bootloader screen:
SPEEDY XA SHIP S-ON
HBOOT-0.98.0001
RADIO-1.08.00.0506
eMMC-boot
April 11 2011, 22:32:34
Is there a way we can flash a file from the SD Card which will turn off the security and/or temp/perm root it? (forgive my noobness for such a question)
EDIT: I'm referring to a way that's outside of the adb push method. My device can't be found, and the device won't get past the bootloader screen, so that method doesn't help me too much. However, I do have the ADK Installed and the ADB Command Line works fine.
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk
Also if your phone can't be found its b/c you need to put it into diag mode .. ##DATA .. if you need more help google
tech-9 said:
If you want to root your phone use visionary to temp root then use shift rr .. you can then flash a custom recovery which is essential to avoid this from happening again
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk
For the thread starter, the person that sold you the phone probably tried writing to the system partition with s-on. Since you can get to the bootloader, see if you can get into recovery. If you can, recovery can be seen in adb, even the stock recovery. From there, gingerbread root, plenty of guides out there, make sure you flash the misc.img, download the froyo downgrade zip (that pgimg09.zip or something like that, just search for it, but not with the numbers I just gave, those are made up.)
From there either flash the gingerbread zip or ruu, and goon with a unrooted life. Or follow one of the many guides to froyo root, and live the life of the rooted. Your choice.
For the second person with a similar issue, the same method will work for you (assuming you can get to recovery), gingerroot, froyo downgrade, and since you like being unrooted, just ruu or zip back to gingerbread.
Solution found enjoy, and just think, if root hadn't been discovered for gingerbread, you would be screwed right now, make sure to thank otaking.
I have the same boot loop problem. I tried using the PG06IMG.zip file and fastboot/bootloader screen says I have the wrong image. It's most likely because it's for 2.2 and I have 2.3. I also don't have any recovery. Is there a PG06IMG.zip for 2.3 or the like?
similar problem here
i'm fairly certain i tried recovery with the wrong or corrupt or incomplete PG06IMG.zip on my first attempt. i got the right one from here http://forum.xda-developers.com/showthread.php?t=1255474
i ran it, says update installed, but when i reboot i still get the loop
from bootloader
SPEEDY XE SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Nov 15 2010, 13:19:54
zdavidzz said:
i'm fairly certain i tried recovery with the wrong or corrupt or incomplete PG06IMG.zip on my first attempt. i got the right one from here http://forum.xda-developers.com/showthread.php?t=1255474
i ran it, says update installed, but when i reboot i still get the loop
from bootloader
SPEEDY XE SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Nov 15 2010, 13:19:54
Click to expand...
Click to collapse
Try downloading the zip again and re run it. Possibly a bad download?
Sent from my PG06100 using Tapatalk
also adb is telling me device not found. i think i might have to factory reset. is that crazy?
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
and... that didn't help
i'm downloading the zip again right now.
since i have s-on, will i be able to install it though?
i can get the file on the root of the sdcard with an adapter since i can't push from adb. and i can't temp root the phone because if i try a normal reboot i get this stupid boot loop. is there a way to get s-off through hboot on the phone?
i don't know why i didn't notice that first file was messed up, it was only 6MB.
hi,
Ive recently rooted my phone with no problems using the ace hack kit. i tried flashing the newest andriod revolution hd rom and was having problems with the superuser app force closing and the phone wasnt giving me root privledges. i decided to try and reroot the phone using the ace hack kit. (i realize this was my mistake). it stopped in the middle of the process. so i had to pull the battery. when i tried turning the phone back on the screen was black for about 6 or 7 mins. no vibrations or leds to indicate the phone was on. then the htc white screen comes on and the phone vibrates for 2 or 3 minutes straight and proceeds to come on. Ive tried to flash other roms using cwm recovery and itll load what ever rom i choose but i cant get into the hboot or anything and it does the the black screen everytime along with the vibration. is there anyway to fix this? ive tried over and over to boot into recovery through usb but it doesnt work.
so ive done a little research, could this be a eMMC problem? if so is it fixable... And if not would replacing the hboot help?
You've got a bad or corrupt hboot. The wrong hboot (ENG hboot included in a short-lived version of the hack kit on the newest run of Inspires) or a corrupt hboot from an interrupted hack kit run.
Thanks for the help. I tried replacing the eng hboot with the link provided on freenode and it work.
After a failed attempt at running the ace hack kit (could only get into hboot), and an ever worse failed attempt at restoring to a stock rom (my stupid mistake), I am seeing the same signature as jbryancs.
Would you share the link and instructions for replacing the hboot? Any assistance is much appreciated.
wleven said:
After a failed attempt at running the ace hack kit (could only get into hboot), and an ever worse failed attempt at restoring to a stock rom (my stupid mistake), I am seeing the same signature as jbryancs.
Would you share the link and instructions for replacing the hboot? Any assistance is much appreciated.
Click to expand...
Click to collapse
really? so jumping into the IRC channel is not your best move as instructed to the OP?
I was hoping not to disturb the IRC, but I will jump in tomorrow. Just for background, here's a rough list of what I've done and what I'm seeing now.
Setup: Linux Mint 11 (Ubuntu Derivative) Clean Install for ACE Hack Kit, WinXP for the rest.
1. Ran ACE Hack Kit first time -> stalled early in process
2. Rebooted phone and everything appeared normal
3. Rac ACE Hack Kit second time -> completed process, but noticed some errors/warnings along the way
4. Rebooted phone and it would be stuck at the white HTC logo screen
5. Rebooted to hboot, but none of the options there would restore the phone.
6. Downloaded original ACE firmware and copied ZIP to SD card. It recognized this and performed install, in all appearances successfully until the reboot.
7. On reboot, the phone appeared completely dead. Later discovered that it would spring to life after ~7mins, vibrate 2-3 min, and then boot into Froyo
Phase II
1. Downloaded gingerbread RUU from HTC and ran it. Gets stuck on "Waiting for bootloader"
2. Thought perhaps hboot was corrupted, so ran instructions here "wiki.cyanogenmod.com/wiki/HTC_Ace:_Rooting_%26_CyanogenMod" to install hboot-eng and clockworkmod
3. This did not fix the booting (still wait 7mins, vibrate 2-3), but I do have root now, as verified through su root on the phone's terminal console.
4. Tried the RUU again, stuck on "Waiting for bootloader"
5. Noticed that if I had the phone USB connected to the PC when power cycling, it would come to a black HTC screen after about 7mins. In this mode, the phone seems to connect in Android bootloader interface.
6. Tried the RUU again, and this time it makes it past "Waiting for bootloader", but hangs (no error message) on "Sending". I've left it for nearly an hour with no change -- just keeps showing the black HTC screen.
I still can't get the phone into HBOOT (using the volume down + power method).
Hello,
Could someone tell me if there's an enclosure or a solution to this problem?
I've searched a few forums, and it appear to me that the conclusion is the old (ENG) HBOOT is incompatible with newer hardware.
Thanks.
hchao said:
Hello,
Could someone tell me if there's an enclosure or a solution to this problem?
I've searched a few forums, and it appear to me that the conclusion is the old (ENG) HBOOT is incompatible with newer hardware.
Thanks.
Click to expand...
Click to collapse
You will have to flash the original RUU again and then try to root the cell with the Hack Kit. You can find the original RUU in the general section or go to the htc site and just run the .exe update from fastboot. Let your cell reboot (it will take about 30 minutes) and then flash it.
jbryancs said:
hi,
Ive recently rooted my phone with no problems using the ace hack kit. i tried flashing the newest andriod revolution hd rom and was having problems with the superuser app force closing and the phone wasnt giving me root privledges. i decided to try and reroot the phone using the ace hack kit. (i realize this was my mistake). it stopped in the middle of the process. so i had to pull the battery. when i tried turning the phone back on the screen was black for about 6 or 7 mins. no vibrations or leds to indicate the phone was on. then the htc white screen comes on and the phone vibrates for 2 or 3 minutes straight and proceeds to come on. Ive tried to flash other roms using cwm recovery and itll load what ever rom i choose but i cant get into the hboot or anything and it does the the black screen everytime along with the vibration. is there anyway to fix this? ive tried over and over to boot into recovery through usb but it doesnt work.
so ive done a little research, could this be a eMMC problem? if so is it fixable... And if not would replacing the hboot help?
Click to expand...
Click to collapse
I am having this same problem I have searched and searched and this post was the only one that had the same issue could someone please help me out on this and post the fix. Thanks
I have a razr hd. I can boot into ap fastboot but thats it. Anything else it sits on red m logo. Cant boot into recovery or anything. I can flash xml using one of matts utility without any fails but rebooting just sits on red m.Please help.
meat-rack said:
I have a razr hd. I can boot into ap fastboot but thats it. Anything else it sits on red m logo. Cant boot into recovery or anything. I can flash xml using one of matts utility without any fails but rebooting just sits on red m.Please help.
Click to expand...
Click to collapse
we are going to need a bit more information to possibly help you.
what did you do to get into this predicament?
are you locked or unlocked?
if locked, what was your system version prior to the issue?
bweN diorD said:
we are going to need a bit more information to possibly help you.
what did you do to get into this predicament?
are you locked or unlocked?
if locked, what was your system version prior to the issue?
Click to expand...
Click to collapse
Same issue for me after OTA. Just processed the OTA as normal and phone will not climb out of the Red M loop. Non rooted, locked device. Attempted to utilize RSD with a few flash files and no luck. Very inexperienced with this. Sorry to be so dense, just looking for any direction possible.
Slickville said:
Same issue for me after OTA. Just processed the OTA as normal and phone will not climb out of the Red M loop. Non rooted, locked device. Attempted to utilize RSD with a few flash files and no luck. Very inexperienced with this. Sorry to be so dense, just looking for any direction possible.
Click to expand...
Click to collapse
i wish i could help you but without knowing exactly what the ota flashed before failing, any advice i give has the real possibility of making your phone worse or possibly perma bricked. the problem is you are locked and we dont yet have a fxz for kk.
that being said, if you still want to try and fix it against my advice i will tell you what to try but I AM NOT RESPONSIBLE IF THIS BRICKS YOUR PHONE OR MAKES IT WORSE IN ANY WAY.
download this xml file http://www.mediafire.com/view/p217akcxwmijcr7/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC_DOWN.xml
download the 9.30.1 ota from sbf droid devs
extract it to a folder and DELETE the xml file, then copy the one above into the folder
make sure you have the latest rsd, i think its 6.1.5 (not positive)
load the xml file into rsd and flash as usual
if this does not work, there is no way to fix your phone until the kk fxz is leaked, assuming this doesnt make it worse.
6.1.6 is the newest RSDLite I've seen.
Go here if you haven't applied the OTA yet and your bootloader is locked.
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
If you have applied the OTA and you're locked, don't do it. You'll have to wait for the FXZ to come out. Otherwise, it will brick even further.
If you have applied the OTA AND your bootloader is UNLOCKED, then you can use the tool to flash back to stock 9.30.1.
I too am bricked. unrooted and locked. Ran the ota and when it reset, it now hangs at the red M. Can get into fast boot and recovery. Tried factory restore and wipe cache. Once I did that my phone now randomly boots to andy all opened up, waiting for me to press the buttons to go into recovery. If I leave it like that, it just reboots after a time and does it all over again . I'm going to assume the only way forward is the xfz file? Any body have an idea of when that might become available and where about I can pick it up? I.E. which forum might have it and will it be a new thread?
Grimaldus3320 said:
I too am bricked. unrooted and locked. Ran the ota and when it reset, it now hangs at the red M. Can get into fast boot and recovery. Tried factory restore and wipe cache. Once I did that my phone now randomly boots to andy all opened up, waiting for me to press the buttons to go into recovery. If I leave it like that, it just reboots after a time and does it all over again . I'm going to assume the only way forward is the xfz file? Any body have an idea of when that might become available and where about I can pick it up? I.E. which forum might have it and will it be a new thread?
Click to expand...
Click to collapse
This has been posted many times. When installing the OTA manually via recovery, a few things happen:
The first time you apply the OTA in recovery, it replaces the recovery with a new recovery and reboots the phone. This new recovery requires a new key combo to get into it. The new key combo is vol-up + power.
So, after you attempt to apply the OTA the first time, you need to be around so when it reboots into the Andy screen, you can use the new key combo. Otherwise, if you leave it alone, it will reboot and then you'll see the red Moto logo which means you'll have to reboot the phone and then hold vol-up + power to get the boot menu and select "Recovery" and then go to the next step.
After getting back into the new recovery, you must apply the OTA again so it can continue to upgrade your phone. After this, you'll be upgraded to Kit Kit.
iBolski said:
This has been posted many times. When installing the OTA manually via recovery, a few things happen:
The first time you apply the OTA in recovery, it replaces the recovery with a new recovery and reboots the phone. This new recovery requires a new key combo to get into it. The new key combo is vol-up + power.
So, after you attempt to apply the OTA the first time, you need to be around so when it reboots into the Andy screen, you can use the new key combo. Otherwise, if you leave it alone, it will reboot and then you'll see the red Moto logo which means you'll have to reboot the phone and then hold vol-up + power to get the boot menu and select "Recovery" and then go to the next step.
After getting back into the new recovery, you must apply the OTA again so it can continue to upgrade your phone. After this, you'll be upgraded to Kit Kit.
Click to expand...
Click to collapse
Right. By reading your earlier posts instructions I got into recovery. That is how I was able to factory reset and wipe cache. I'm talking about AFTER I did all that, instead of just being hung at red m screen, it hangs for a few seconds, then flickers, hangs a few more seconds, and then goes into andy screen. If I don't touch it for a few minutes, it reboots, and that same process starts over, ending with the andy screen again...Its like it WANTS me to be in recovery to fix it .
I noticed you also said to others that us lot are pretty much screwed until the fxz file is out, which I assume is this OTA as a zip so we can flash with recovery? Any idea when that will be coming out? and where should I look for it once its out?
Heck, because I was unrooted and locked and it was the official OTA from verizon, maybe I should go in to them and demand they replace my phone with the moto x. Though, I rather liked my razr hd and don't quite wanna give up on it...
Grimaldus3320 said:
Right. By reading your earlier posts instructions I got into recovery. That is how I was able to factory reset and wipe cache. I'm talking about AFTER I did all that, instead of just being hung at red m screen, it hangs for a few seconds, then flickers, hangs a few more seconds, and then goes into andy screen. If I don't touch it for a few minutes, it reboots, and that same process starts over, ending with the andy screen again...Its like it WANTS me to be in recovery to fix it .
I noticed you also said to others that us lot are pretty much screwed until the fxz file is out, which I assume is this OTA as a zip so we can flash with recovery? Any idea when that will be coming out? and where should I look for it once its out?
Heck, because I was unrooted and locked and it was the official OTA from verizon, maybe I should go in to them and demand they replace my phone with the moto x. Though, I rather liked my razr hd and don't quite wanna give up on it...
Click to expand...
Click to collapse
No, the FXZ is the full kit-kat image, not an update like the OTA. The FXZ can be used to flash your phone back to full stock, whether you are locked or not. If you are locked, then you can only flash the version that is currently on your phone or newer. You cannot flash back to a previous version unless your bootloader is unlocked.
The ota is used to only update a previous version to the current version, in this case from JB to KK, but once it's applied, you cannot apply it again since you are already upgraded to that version. It's only an upgrade, not a full image like an FXZ.
iBolski said:
No, the FXZ is the full kit-kat image, not an update like the OTA. The FXZ can be used to flash your phone back to full stock, whether you are locked or not. If you are locked, then you can only flash the version that is currently on your phone or newer. You cannot flash back to a previous version unless your bootloader is unlocked.
The ota is used to only update a previous version to the current version, in this case from JB to KK, but once it's applied, you cannot apply it again since you are already upgraded to that version. It's only an upgrade, not a full image like an FXZ.
Click to expand...
Click to collapse
I see, makes sense. Every days a school day I suppose. Thanks for the info. Guess I have to decide to either wait for the FXZ or go to verizon and see if they can get me a new phone.
Same thing happened to my wife, completely stock now stuck at red m. After calling verizon they suggested the factory reset which just gives you a boot to dead android guy to get into recovery on every boot. Then after a couple minutes just reboots and does the same thing, stuck in a loop. They then said it's not their software, rather Motorola's, so Verizon's only recourse is to sell me an overpriced refurb or upgrade to the edge plan. Screw them. I said unacceptable and they gave me a number for Motorola. Moto said that they put in a request to extend my factory warranty because it was the software update that caused the issue and they will let me know tomorrow. I understand stuff happens, but this is not acceptable when their harassing update causes thee issue. I knew I should've unlocked the boot loader on it when I had the chance.
al2fast said:
Same thing happened to my wife, completely stock now stuck at red m. After calling verizon they suggested the factory reset which just gives you a boot to dead android guy to get into recovery on every boot. Then after a couple minutes just reboots and does the same thing, stuck in a loop. They then said it's not their software, rather Motorola's, so Verizon's only recourse is to sell me an overpriced refurb or upgrade to the edge plan. Screw them. I said unacceptable and they gave me a number for Motorola. Moto said that they put in a request to extend my factory warranty because it was the software update that caused the issue and they will let me know tomorrow. I understand stuff happens, but this is not acceptable when their harassing update causes thee issue. I knew I should've unlocked the boot loader on it when I had the chance.
Click to expand...
Click to collapse
Then you're almost there. At the "dead android" screen, press and hold vol up and then press power and then release both buttons. This gets you into recovery.
At this point, reinstall the OTA via the recovery so it can start into the 2nd stage and then you'll be done.
iBolski said:
Then you're almost there. At the "dead android" screen, press and hold vol up and then press power and then release both buttons. This gets you into recovery.
At this point, reinstall the OTA via the recovery so it can start into the 2nd stage and then you'll be done.
Click to expand...
Click to collapse
I don't know how to reinstall the OTA via stock recovery. I tried it do the install update.zip option and nothing happened. Any pointers would be appreciated.
al2fast said:
I don't know how to reinstall the OTA via stock recovery. I tried it do the install update.zip option and nothing happened. Any pointers would be appreciated.
Click to expand...
Click to collapse
Did you download it to your phone? If so, it needs to be on your external SD card and you choose the option to install from there. You'll have to navigate to where you stored it on the external SD card.
If you didn't download it, then you should be able to push it via ADB PUSH when in the recovery. Just hook up your phone to your PC and do it that way. Just obtain the OTA from this thread. Somewhere, someone provided a link to it. Download it to your PC and then do an adb push to the external SD card of the OTA and then install it that way.
iBolski said:
Did you download it to your phone? If so, it needs to be on your external SD card and you choose the option to install from there. You'll have to navigate to where you stored it on the external SD card.
If you didn't download it, then you should be able to push it via ADB PUSH when in the recovery. Just hook up your phone to your PC and do it that way. Just obtain the OTA from this thread. Somewhere, someone provided a link to it. Download it to your PC and then do an adb push to the external SD card of the OTA and then install it that way.
Click to expand...
Click to collapse
Thanks for the tips. I must have done something wrong when I installed adb, I could not see the phone with the adb devices command, yet I could see the phone in the Matt utility as well as in RSD Lite. I'll give it a shot again, can't hurt. Called Moto and they escalated it and are sending me a replacement device.
I'm stuck in Bootloader/hboot. When I try to get into recovery it reboots back into hboot. I reinstalled a RUU of the latest 4.4.4 and I have reinstalled the recovery a couple of times. I am not getting an error when installing TWRP or the RUU.
The thing that's weird is that when its rebooting the HTC white screen does NOT have the red warning writing on the bottom.
Hboot states all the usual: Software status modified, S-Off, hboot 3.19, Radio 1.09.20.0926
I'm really at a loss. Please Help :crying:
mentallo said:
I'm stuck in Bootloader/hboot. When I try to get into recovery it reboots back into hboot. I reinstalled a RUU of the latest 4.4.4 and I have reinstalled the recovery a couple of times. I am not getting an error when installing TWRP or the RUU.
The thing that's weird is that when its rebooting the HTC white screen does NOT have the red warning writing on the bottom.
Hboot states all the usual: Software status modified, S-Off, hboot 3.19, Radio 1.09.20.0926
I'm really at a loss. Please Help :crying:
Click to expand...
Click to collapse
You sure the ruu completed?
When I "fastboot oem rebootRUU" in cmd it reboots but goes back into the Bootloader and doesn't go into the Black screen/Transfer screen.
The way I did the RUU was by placing it on the sdcard. It finished installing.
BTW is it normal that it says "Software Status: Modified"? I see some Screenshots from people where it doesn say that.
(The weird thing about all this is that the phone was working fine up until it started doing this. I was running Viper with the occasional Black Screen issue that plagues the rom right now.)
mentallo said:
When I "fastboot oem rebootRUU" in cmd it reboots but goes back into the Bootloader and doesn't go into the Black screen/Transfer screen.
The way I did the RUU was by placing it on the sdcard. It finished installing.
BTW is it normal that it says "Software Status: Modified"? I see some Screenshots from people where it doesn say that.
(The weird thing about all this is that the phone was working fine up until it started doing this. I was running Viper with the occasional Black Screen issue that plagues the rom right now.)
Click to expand...
Click to collapse
Does your phone work at this point?
Nope, I am searching for the answer but I am coming up empty. I'm at a loss. Could it be that the internal memory is fried or something? But in that case I wouldn't be able to install the RUU right?
same thing happened to me yesterday. I tried for hours yesterday and today doing anything to get Some sort of response out of it, as all that it would do is boot into hboot. I could use fastboot commands but I was never able to flash anything, usually said not allowed... I was on Digital High 5.0.1 from like 12/11 or something like that. So strange. Everything was running so smoothly, then it's like it just imploded. I'd be interested if you find a solution, but I ended up ordering a replacement phone from Verizon. Looks like I'm starting over...
Apparently the internal flash memory. {emmc} just died and nothing can be flashed to it. Phone is dead. There is nothing you can do to fix it.
thanks for the update. I was holding on to my broken phone before returning it to vzw in hopes that I could restore it; I guess I'll send it back today.
lazyboy0172 said:
thanks for the update. I was holding on to my broken phone before returning it to vzw in hopes that I could restore it; I guess I'll send it back today.
Click to expand...
Click to collapse
What commands did you run on it after it broke?
dottat, you helped with it remember? lol
mentallo said:
dottat, you helped with it remember? lol
Click to expand...
Click to collapse
Across four devices and a couple carriers I start to lose my marbles some. Or perhaps lollipops