Related
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
did you let it finish? the ic microchip and arrow pointing thing? or did you yank out the battery?
i panicked and yanked out the battery...i killed it, didnt i?
I think he didn't let the phone finish and restarted the phone cause it wasa taking too long if that's the case 99.0% the phone is bricked. It happend to somebody else here already. Jy
He just call tmobile and told them the wasn't turning on and they send him a replacement.
I think this is something that needs to be added to the flashing roominstructions.
slyfury said:
i panicked and yanked out the battery...i killed it, didnt i?
Click to expand...
Click to collapse
Im sorry man, you did the one thing you shouldnt have while flashing
Perrosky said:
I think he didn't let the phone finish and restarted the phone cause it wasa taking too long if that's the case 99.0% the phone is bricked. It happend to somebody else here already. Jy
He just call tmobile and told them the wasn't turning on and they send him a replacement.
I think this is something that needs to be added to the flashing roominstructions.
Click to expand...
Click to collapse
i agree 100% please add that to the instruction for noobs like me
oh well, i just hope i get a replacement quickly
that happened to me so i called t-mo and told them that my g1 wont turned on at all and tried the other battery so they send me a replacement. of course i was a noob back then. i learned my lesson in a hard way so i suffer a week without my precious g1 lol.
slyfury said:
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
Click to expand...
Click to collapse
also once you called t-mo do not let them know that youre modifying your phone otherwise they will not send you another handset.
slyfury said:
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
Click to expand...
Click to collapse
how about take out the sdcard and connect it to the computer, put the jfr33 in it, and flash your phone again. It works
also he could try getting into recovery mode using adb or sumthin...i am not too sure about it...but i think it can be done..!!!
tannyfiles said:
also he could try getting into recovery mode using adb or sumthin...i am not too sure about it...but i think it can be done..!!!
Click to expand...
Click to collapse
If the phone can't reach the bootloader or recovery console I don't think ADB is going to work but I could be wrong.
patience is a virtue
your topic title is misleading and could lead users who haven't tried yet to be too wary about flashing over to Haykuro's builds...
Ultimately...your phone didn't mess up after flashing 4.X..YOU messed up.
if you cant turn on youre g1 then it is dead, even if you connect it to pc or what if it cant be turned be on, it is dead cuz thats what happened to me so just call t-mo and tell them youre phone wont turn on and you tried another battery still wont turn and DO NOT tell them you modify or even saying you attemped to modify your g1's rom.
the best thing for him to do would be flash rc29 nbh and start from scratch...the phone is more than likely not bricked.
korndub said:
the best thing for him to do would be flash rc29 nbh and start from scratch...the phone is more than likely not bricked.
Click to expand...
Click to collapse
To my opinion, i do not think the phone is bricked since there is no hardware issue is involving, it's the software itself, if he can access to the root of the sd card, problem is solved.
but oh well, i would call Tmobile and request a new shinny phone . wait... they will send a refurbished one won't they? oh noo...
I have a similar problem, i was attempting to move apps to the sd card, partitioned it, installed the lucidrem rom and then started using his code and the flashing android loop started, turned it off and back on and still the flashing android, i used the fastboot method to restore my nandroid backup, and the phone is back to working, my problem is that i cant access recovery mode.
everything else is fine, just when i try to load the recovery mode it just stays on the boot screen, can anybody help a newbie out?
the bootloader works, and the phone can load normally, but the recovery mode wont start.
cueballv2 said:
I have a similar problem, i was attempting to move apps to the sd card, partitioned it, installed the lucidrem rom and then started using his code and the flashing android loop started, turned it off and back on and still the flashing android, i used the fastboot method to restore my nandroid backup, and the phone is back to working, my problem is that i cant access recovery mode.
everything else is fine, just when i try to load the recovery mode it just stays on the boot screen, can anybody help a newbie out?
the bootloader works, and the phone can load normally, but the recovery mode wont start.
Click to expand...
Click to collapse
That happened to me also. When I installed lucidrem's rom the recovery would work. What it actually was that when you first rooted your g1 do you rmr installing the recovery img? Well its pretty much the same thing lucidrems rom didn't have a recovery img command line attatched to it. I just installed recovery again from the terminal emulator just like it said in the root your g1 thread.
Atleast that is my side of the story. I don't anything about coding. So I could be wrong but that was just my experience.
bigballa said:
That happened to me also. When I installed lucidrem's rom the recovery would work. What it actually was that when you first rooted your g1 do you rmr installing the recovery img? Well its pretty much the same thing lucidrems rom didn't have a recovery img command line attatched to it. I just installed recovery again from the terminal emulator just like it said in the root your g1 thread.
Atleast that is my side of the story. I don't anything about coding. So I could be wrong but that was just my experience.
Click to expand...
Click to collapse
wow, thanks alot for your help, reflashed the recovery.img and it worked a treat, thought id bricked it good and proper, but your advice worked, thanks again.
My phone is looping (on and off) during the boot sequence. The boot screen (red green yellow) says code error then goes to the update screen. It starts to flash and then shuts off for a couple of minutes and does the same sequence again. I was running Nedidum v4 and activated the lock screen. Every since then I cant boot to this rom nor can I flash the stock sprint rom. Is my phone bricked? If i take it to sprint can they tell I was running a cooked rom? Note: I reported my touch pro lost through assurion to get this tp2. Can I do it again? Helpppppppppppppp!!!!!
jutaejrtouch said:
My phone is looping (on and off) during the boot sequence. The boot screen (red green yellow) says code error then goes to the update screen. It starts to flash and then shuts off for a couple of minutes and does the same sequence again. I was running Nedidum v4 and activated the lock screen. Every since then I cant boot to this rom nor can I flash the stock sprint rom. Is my phone bricked? If i take it to sprint can they tell I was running a cooked rom? Note: I reported my touch pro lost through assurion to get this tp2. Can I do it again? Helpppppppppppppp!!!!!
Click to expand...
Click to collapse
Perhaps this is karma hitting you in the ass?
Go to the boot loader by shutting the phone off, holding down the vol down button then turning the phone back on.
Once in the boot loader try flashing to the stock rom.
To answer your question, yes, Sprint could tell. That said, they aren't likely to check.
gamescan said:
Perhaps this is karma hitting you in the ass?
Go to the boot loader by shutting the phone off, holding down the vol down button then turning the phone back on.
Once in the boot loader try flashing to the stock rom.
To answer your question, yes, Sprint could tell. That said, they aren't likely to check.
Click to expand...
Click to collapse
it wont let me flash...it starts flashing and at about 10% phone shuts off...few minutes later it turns itself back on and goes to the boot--flash screen. i"ve tried 5 different roms including stock sprint. Only thing on card is the image file. You say sprint can't tell...I thought the boot screen says security unlocked or something like that?
jutaejrtouch said:
it wont let me flash...it starts flashing and at about 10% phone shuts off...few minutes later it turns itself back on and goes to the boot--flash screen. i"ve tried 5 different roms including stock sprint. Only thing on card is the image file. You say sprint can't tell...I thought the boot screen says security unlocked or something like that?
Click to expand...
Click to collapse
He is saying that sprint could figure out you flashed your phone, but it is more likely that they won't even check, as most users probably won't flash their phone. At the very least you could go through insurance.
jutaejrtouch said:
it wont let me flash...it starts flashing and at about 10% phone shuts off...few minutes later it turns itself back on and goes to the boot--flash screen. i"ve tried 5 different roms including stock sprint. Only thing on card is the image file. You say sprint can't tell...I thought the boot screen says security unlocked or something like that?
Click to expand...
Click to collapse
Yes, Sprint can tell if someone bothers to look. Chances are just low that someone will look.
Why are you flashing from a card? Ditch the card.
Flash the STOCK Sprint ROM over USB.
gamescan said:
Yes, Sprint can tell if someone bothers to look. Chances are just low that someone will look.
Why are you flashing from a card? Ditch the card.
Flash the STOCK Sprint ROM over USB.
Click to expand...
Click to collapse
I have Verizon but I agree, there are too many variables when flashing via sd card. A faulty or cheap card, bad sectors on the card itself, your card reader copying the rom file incorrectly, a bad format on the card, the list goes on and on with what can go wrong flashing via sd card. I only flash via USB. Then again I use buildos so I never had a problem with roms. Thats why I like cookin my own rom. No headaches.
Relax heres what you do.
bro heres what you gotta do to fix your pfoblem, first format your sd card to fat32 then copy the nbh file onto the card, rename it to RHODIMG insert the sd card then enter the boot loader menu by first taking out the battery, and reinserting it. now with the phone off hold the volume down button while pressing the power button this forces the device into bootloader mode. your screen WILL read RHODIMG os. now press the power button again to install whatever rom you want but I would recommend using a stock rom or one that you know works, ie- from past experience.
trust me bro do this and all will be fine again,
HAPPY FLASHING
oh dont forget to press the soft reset button once the rom installation is done when the screen says installation successful,
once again HAPPY Flashing>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
the nbh file can be found next to the RUU application of whatever rom you choose when you open the rom with winrar this is the rom that will be flashed onto the phone.
sapperpipo said:
bro heres what you gotta do to fix your pfoblem, first format your sd card to fat32 then copy the nbh file onto the card, rename it to RHODIMG insert the sd card then enter the boot loader menu by first taking out the battery, and reinserting it. now with the phone off hold the volume down button while pressing the power button this forces the device into bootloader mode. your screen WILL read RHODIMG os. now press the power button again to install whatever rom you want but I would recommend using a stock rom or one that you know works, ie- from past experience.
trust me bro do this and all will be fine again,
HAPPY FLASHING
oh dont forget to press the soft reset button once the rom installation is done when the screen says installation successful,
once again HAPPY Flashing>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Click to expand...
Click to collapse
Thanks all for your input...I've been flashing a year now, probably at least 500 times. Via sd card or activesync. I've tried everything..removing battery...formatting card...lada dada. cant connect via usb cause phone wont get past boot screen. I gave up and reported it missing o get a new one. It arrives today. I honestly think its the battery not holding a charge. Guess i find out for sure when the new tp2 arrives today. I'll post back here when i find out for sure.
Well got my new tp2 in this morning. I put the new battery in the old tp2 and it fired right up....to bad i had to waste my final insurance claim because of a battery.
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.
I never rooted or unlocked the bootloader, not sure what's up. I had a 32gb SD card in it if that matters.
Anyone know what I could try and do?
Try to flash stock from fastboot, maybe something on your system has been corrupted... Are you rooted or bootloader unlocked?
thegunrun said:
I never rooted or unlocked the bootloader, not sure what's up. I had a 32gb SD card in it if that matters.
Anyone know what I could try and do?
Click to expand...
Click to collapse
You can try to recover to the recovery image.
https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image.txt
You can find the boot, system and recovery .img's here
http://forum.xda-developers.com/showthread.php?t=2388870
The blob and tegra114-roth here
https://drive.google.com/?authuser=0#folders/0B7j6Imwr_sirRnl5MFRRR2sxRWM
I would upload the userdata.img, but it's too big for me to upload, and I don't think it is needed...
Guys, the OP mentioned that he has not unlocked/rooted his device, so he cannot flash the recovery image.
That should definitely not happen on an unlocked device. Can you at least see the splash animation? Things to try (in that order):
1) On the boot splash animation, connect SHIELD to your PC and try to run "adb logcat" to see if you can see what is crashing. Attach the log here if you can get it.
2) If you cannot use adb, reboot your SHIELD while holding the back and home buttons. This will bring you to the bootloader menu. Then connect to your PC and try to "fastboot erase userdata" and "fastboot erase cache" before doing "fastboot reboot". This will remove all your user data, so your SHIELD should boot again correctly provided the OTA went without any issue. You might not like the idea of losing your user data though.
3) Contact NVIDIA. You have not unlocked your SHIELD, just did a regular OTA. This is covered by the warranty so they should be able to help you.
Gnurou said:
....That should definitely not happen on an unlocked device. Can you at least see the splash animation? Things to try (in that order):....
Click to expand...
Click to collapse
Fixed that line for you.
If the device is locked getting Nvidia to fix the software should not be a problem.
I had the same problem. NVidia swapped out my Shield with a retail refurbished unit.
Happened to me but I shut it down using the nvidia button and let it sit for a few minutes and it booted.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
i have got the same problem
its impossible to boot in 4.3. the only few times i got it, it tooks 10 ton 15 minutes
i go back to 4.2 and i had the same problem. the only way to get the shield back to normal is to format all (system, data, etc..) through cwmr
when i trie to update to 4.3 trought ota, i got the same problem and i have to repeat the proccess again to come back to 4.2
in 4.2 boots ok, and everything works, but i cant update
any ideas?
My boot-up problem seemed to have been caused by my 64GB SanDisk MicroSD card. When I pulled it out to transfer it to my replacement Shield, the original came up. Try pulling out your SD card before powering on if you are still having trouble.
jdsemler said:
My boot-up problem seemed to have been caused by my 64GB SanDisk MicroSD card. When I pulled it out to transfer it to my replacement Shield, the original came up. Try pulling out your SD card before powering on if you are still having trouble.
Click to expand...
Click to collapse
hi, i tried to boot without the sd and i get the same result
stock in boot logo
i thing the problem its something related with the ota update an my boot.img
someone has access to boot, system and recovery img from update 63?
maybe if i install from bootloader i get something
thanks in advance
If you power on holding back and home, you will boot into a menu. If you go into Recovery, do you get any options? On mine, it would say "No Command" and be stuck there. If yours also says "No Command", you can't really load anything using recovery.
You should consider going here. You'll have to either login or create a login, but after that, you can submit your problem to NVidia. That's what I did, and they shipped me a new unit overnight with a prepaid label to send my unit back.
Hi, Thanks for your answer. Im able to update the shield throught fastboot. This is hoy i can downgrade from 4.3 to 4.2.
Moreover ,i cant get a new unit, cause i live in spain, (and i already unlock my bootloader)
cg_gm said:
Hi, Thanks for your answer. Im able to update the shield throught fastboot. This is hoy i can downgrade from 4.3 to 4.2.
Moreover ,i cant get a new unit, cause i live in spain, (and i already unlock my bootloader)
Click to expand...
Click to collapse
good news!!! last update (64) solve the problem. now im in 4.3 and all is working ok
thanks for your help, hope thath nvidia dont mess up with the updates again
Looking for some help please! My phone battery died the other day, I plugged it in to charge and turned it on at 3% battery life only to get stuck in a boot loop.
Did a factory reset and then successfully flashed with odin and current firmware G930TUVS9CSC1. After flashing it went to installing a system update screen only getting to about 32%, then it said erasing for a while and went back to the samsung startup screen stuck in apparently the same boot loop I started with.
Is my phone screwed or did I miss something? looking for any help, thanks.
vexcesban said:
Looking for some help please! My phone battery died the other day, I plugged it in to charge and turned it on at 3% battery life only to get stuck in a boot loop.
Did a factory reset and then successfully flashed with odin and current firmware G930TUVS9CSC1. After flashing it went to installing a system update screen only getting to about 32%, then it said erasing for a while and went back to the samsung startup screen stuck in apparently the same boot loop I started with.
Is my phone screwed or did I miss something? looking for any help, thanks.
Click to expand...
Click to collapse
It sometimes does this, make sure the firmware your using is correct for your device and flash again.
UNCHECK "auto reboot" in Odin
Disconnect when flash complete Do Not Turn The Phone On
Reboot into recovery volume up+home+power
Wipe cache/factory rest
Reboot
cooltt said:
It sometimes does this, make sure the firmware your using is correct for your device and flash again.
UNCHECK "auto reboot" in Odin
Disconnect when flash complete Do Not Turn The Phone On
Reboot into recovery volume up+home+power
Wipe cache/factory rest
Reboot
Click to expand...
Click to collapse
Thanks. Appreciate the input, but it didn't work for me after trying it twice. I am positive I have the right firmware.
It boots up with no led indicating light and continues to just flash the opening samsung screen for eternity.
Got the phone to boot up normally but now it wont read my sim card. sim works in my other phone. Any ideas?
vexcesban said:
Got the phone to boot up normally but now it wont read my sim card. sim works in my other phone. Any ideas?
Click to expand...
Click to collapse
SIM reader on phone, blow into hole to dislodge any dust and make sure sim is flat in adapter. Very rarely a software problem with sim not read.
cooltt said:
SIM reader on phone, blow into hole to dislodge any dust and make sure sim is flat in adapter. Very rarely a software problem with sim not read.
Click to expand...
Click to collapse
interesting, it worked fine before this started 2 days ago. I guess maybe the sim card reader broke? theres definitely no dirt in there and it seems to make a good connection (tried a new sim card had lying around and it etched lines into the sim card nicely).
Also I should mention that I had no clue what I was doing and flashed a dozen or so different versions of firmwares probably like 20 times, so maybe I caused it.
vexcesban said:
interesting, it worked fine before this started 2 days ago. I guess maybe the sim card reader broke? theres definitely no dirt in there and it seems to make a good connection (tried a new sim card had lying around and it etched lines into the sim card nicely).
Also I should mention that I had no clue what I was doing and flashed a dozen or so different versions of firmwares probably like 20 times, so maybe I caused it.
Click to expand...
Click to collapse
Er.... Yes!
You have to flash the correct region firmware for your device or you end up with problems like you have.
Search for the SamFirm tool on here it's great for getting the correct firmware direct from Samsung servers.
cooltt said:
Er.... Yes!
You have to flash the correct region firmware for your device or you end up with problems like you have.
Search for the SamFirm tool on here it's great for getting the correct firmware direct from Samsung servers.
Click to expand...
Click to collapse
Okay well that tool's forum post says it's deprecated so I followed the alternative link to updato and got stock 8.0 from there. Flashed phone, everything works 100% but still no sim detected.
I'm wondering If I broke my phone because I even tried some custom rom with a pit file and probably did that wrong as well.
vexcesban said:
Okay well that tool's forum post says it's deprecated so I followed the alternative link to updato and got stock 8.0 from there. Flashed phone, everything works 100% but still no sim detected.
I'm wondering If I broke my phone because I even tried some custom rom with a pit file and probably did that wrong as well.
Click to expand...
Click to collapse
PIT won't do anything to SIM.
Try all of these
Hey i am having the same problem odin flash with succes but the phone still only shows the first samsung glaxy s7 screen and then reboots.
Also i cant acces recovery.
i have the same problem
Huzalio said:
Hey i am having the same problem odin flash with succes but the phone still only shows the first samsung glaxy s7 screen and then reboots.
Also i cant acces recovery.
Click to expand...
Click to collapse
hi, did you find a way to fix it?
@cooltt I made an account here in order to thank you! I was stuck in a boot loop after flashing a stock ROM and your advice saved my phone. I thought I bricked it!!
q-l-p said:
@cooltt I made an account here in order to thank you! I was stuck in a boot loop after flashing a stock ROM and your advice saved my phone. I thought I bricked it!!
Click to expand...
Click to collapse
Glad I could help
cooltt said:
It sometimes does this, make sure the firmware your using is correct for your device and flash again.
UNCHECK "auto reboot" in Odin
Disconnect when flash complete Do Not Turn The Phone On
Reboot into recovery volume up+home+power
Wipe cache/factory rest
Reboot
Click to expand...
Click to collapse
I'm having this same issue but it won't boot into recovery at all, I don't know what to do.
iroveashe said:
I'm having this same issue but it won't boot into recovery at all, I don't know what to do.
Click to expand...
Click to collapse
First MAKE SURE you are flashing correct firmware for your device.
What device do you have and what country?
If you are sure it's correct. Flash again with Odin but uncheck "auto reboot" in options.
When pass appears just disconnect phone, it doesn't matter what it shows on the screen.
In this sequence press and hold the following... Volume down+home+power.
As soon as the screen goes black move your finger to Volume up while still pressing home+power. It may take several attempts.
When recovery menu appears wipe cache partition then reboot.
Leave phone go through boot sequence, ignore what appears on the screen during this time it is normal. This boot should take around 5 minutes.
EDIT: FIXED, I did what you did, but for that to work I had to flash it without the hidden.img. Then it rebooted and got stuck on the logo again, but i was able to boot into recovery. Thank you so much.
cooltt said:
First MAKE SURE you are flashing correct firmware for your device.
What device do you have and what country?
Click to expand...
Click to collapse
Hey, thank you for responding.
I'm not 100% sure it's the right one
Device: Samsung A510M
Country: Argentina
Carrier: Personal
I downloaded a firmware from sammobile matching those specifications, but it fails at the last step with hidden.img.
This morning I downloaded another firmware through samfirm, but that one fails at modem.img instead.
I will try your instructions with either of them.
---------- Post added at 07:01 PM ---------- Previous post was at 06:06 PM ----------
cooltt said:
As soon as the screen goes black move your finger to Volume up while still pressing home+power. It may take several attempts.
Click to expand...
Click to collapse
To be clear, I only need to repeat this part of the process, not reinstall the firmware every time, correct? I've been trying to do this for a while, but it just shows:
"An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."