Guys,
I got a new Nexus 5 before christmas and loved that phone! With my luck, it fell into the pool and got fried with no chance of repair. Figured I would wait a bit before getting a new phone and then the HTC M8 comes out. Steep price for GPE phone so I cheaped out and got my AT&T upgrade and proceeded to try the Stock Google Play Edition KOT49H.H16 - 1.16.1700.16 ROM.
Alas, I screwed up my new phone too. Followed the steps to unlock the bootloader, which worked fine and then proceeded to install Philz recovery which also worked fine. The instruction said to "Make sure you do a wipe if coming from another rom", so I did that using "Clean to Install a New ROM". Yet again, no issues. Proceeded to flash in recovery but my luck just ran out
Problem is when restarting it sits at the HTC white screen and nothing else! Cannot boot into bootloader with power + vol down, cannot address the device via adb or fastboot anymore! The device seems bricked and I hope you guys are smarter and can help get me out of this.
Only function that works is power + vol up which seems to reboot back to the HTC screen.
adb devices -> no devices are found
To me, it looks like no bootloader or ROM's are on the device after I erased. Please help - GRACIAS.
Vol up and power 10 sec or so. As soon as it blanks out, vol down and power to go to boot loader. Make sure phone is not plugged in. Don't worry. You're bootloader is fine. Recoveries are still beta atm. I would flash newest twrp.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 01:40 AM ---------- Previous post was at 01:39 AM ----------
Let go of power button too when it blanks.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 01:47 AM ---------- Previous post was at 01:40 AM ----------
Make sure you get ul_ca twrp. If you didn't make a backup you can adb sideload a rom.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
fazilosman said:
Guys,
I got a new Nexus 5 before christmas and loved that phone! With my luck, it fell into the pool and got fried with no chance of repair. Figured I would wait a bit before getting a new phone and then the HTC M8 comes out. Steep price for GPE phone so I cheaped out and got my AT&T upgrade and proceeded to try the Stock Google Play Edition KOT49H.H16 - 1.16.1700.16 ROM.
Alas, I screwed up my new phone too. Followed the steps to unlock the bootloader, which worked fine and then proceeded to install Philz recovery which also worked fine. The instruction said to "Make sure you do a wipe if coming from another rom", so I did that using "Clean to Install a New ROM". Yet again, no issues. Proceeded to flash in recovery but my luck just ran out
Problem is when restarting it sits at the HTC white screen and nothing else! Cannot boot into bootloader with power + vol down, cannot address the device via adb or fastboot anymore! The device seems bricked and I hope you guys are smarter and can help get me out of this.
Only function that works is power + vol up which seems to reboot back to the HTC screen.
adb devices -> no devices are found
To me, it looks like no bootloader or ROM's are on the device after I erased. Please help - GRACIAS.
Click to expand...
Click to collapse
Approx how long are you waiting for it to pass the htc white screen? It could take a while (can take up to a few minutes) to go past that screen especially on aq first boot of a new ROM.
If your phone reboots to the HTC white screen, its not bricked. Just go back into recovery by holding vol down after causing a reboot.
Related
Great!
Cause i'm stumped!
I am stuck on Locked Froyo,
"ADB reboot bootloader" just reboots regularly,
Power Volume Down boots straight to "Android System Recovery (3e)"
So, I cant get into fastboot to unlock.
I bought this phone 2nd hand.. It came this way.
I have been searching all day!
Can i update to say ICS and reach fastboot from there?
Update just HBoot?
I get no OTA updates.
Did I waste my money?
I figure if i can manually update stock first, i'll have a shot?
How do I do this?
I have no "Fast Boot" (not Fastboot) option to disable as i have no power options?
ADB finds device that took all morning...
I have flashed my old phone, my tablet, xbox360, xbox1, and psp... but this bugger...
Help?
- MiLO83
Try This...
Not an expert by any means, but I think you are trying to get to "Fast Boot" the wrong way...
Allow the phone to power on normally...
From your Home Screen, press the menu button (right next to the Home button)
Hit Settings...
Scroll screen up till you see "Power"...
Press Power, then uncheck "Fast boot" box.
Hopefully this will help you!
MiLO83 said:
Great!
Cause i'm stumped!
I am stuck on Locked Froyo,
"ADB reboot bootloader" just reboots regularly,
Power Volume Down boots straight to "Android System Recovery (3e)"
So, I cant get into fastboot to unlock.
I bought this phone 2nd hand.. It came this way.
I have been searching all day!
Can i update to say ICS and reach fastboot from there?
Update just HBoot?
I get no OTA updates.
Did I waste my money?
I figure if i can manually update stock first, i'll have a shot?
How do I do this?
I have no "Fast Boot" (not Fastboot) option to disable as i have no power options?
ADB finds device that took all morning...
I have flashed my old phone, my tablet, xbox360, xbox1, and psp... but this bugger...
Help?
- MiLO83
Click to expand...
Click to collapse
First, I think you mean Gingerbread 2.3 because that is what the phone shipped with.
Second, You've got to follow the how to root and unlock guides.
raptoro07 said:
First, I think you mean Gingerbread 2.3 because that is what the phone shipped with.
Second, You've got to follow the how to root and unlock guides.
Click to expand...
Click to collapse
You forgot about the official ics update if you have the Sprint version, I'm not sure about the other carrier branded phones having the ics update, officially anyway lol
Oh and make sure you have the diagnostic drivers and htc sync installed or you will have issues getting it to connect to the pc, at last that was my issue when I first got this phone lol
Sent from my PG86100 using xda app-developers app
If you have GB version , you probably can root it using revolutionary way, very easy and straight forward
Sent from my IdeaTabA2109A using Tapatalk HD
Yeah if it is still on GB (2.3.x) LEAVE IT ON GB! So much easier to deal with once you do some reading. And some in depth info about that might help, anything you can figure out.
You sure you have evo 3d or is it the evo 4g?
Hello all. I have searched far and wide on google and these forums, and so far haven't found anything regarding my specific 'brick'. Forgive me if it is right under my nose, and this has already been dealt with.
So I decided to install the new ZVB update for my OG, which went smoothly. I had it running JB for awhile when I read something about custom ROMs. I decided to try Lifelessv12 for OGJB. I followed the guide, and after the ROM had finished downloading, I unlocked my phone with FreeGee, and booted up into TWRP, and wiped everything. I followed what the guide said:
Factory Wipe
Wipe cache
Wipe dalvik cache
So after that, I copied the ROM zip to my device, and attempted to install it. Long story short, I found out that the zip I had downloaded was bunk.
So there I was, stuck with a phone in recovery mode, and no OS. Great. I powered it down to save battery, and left it overnight, as I downloaded the working ROM zip.
The next morning, however, the phone wouldn't turn on, and instead began doing this odd behavior, where the red light would flash, then after a few seconds the red light as well as the soft keys would alternately flash. At that point I was still able to boot into fastboot, but not recovery. So with fastboot working, I decided to run LGNPST on it, because maybe it was something I installed.
So I did, and that did nothing. It still did the red light/softkey alternating flash for awhile, but then something more serious happened
My phone shut off completely. [/drama] Plugging it in has done nothing, either computer or wall with original cables. I have let it sit plugged in for a few hours, and have seen nothing. It isn't even warm, indicating that there isn't any power flow at all.
Am I completely screwed?
My next course of action that I was going to try was:
Take off back
Unplug battery
Hold power for 10 seconds
Plug battery in
Plug USB in
Pray
I've heard this can work.
Also, for reasons not important, I cannot return my phone.
Thanks guys.
Major Tom said:
Hello all. I have searched far and wide on google and these forums, and so far haven't found anything regarding my specific 'brick'. Forgive me if it is right under my nose, and this has already been dealt with.
So I decided to install the new ZVB update for my OG, which went smoothly. I had it running JB for awhile when I read something about custom ROMs. I decided to try Lifelessv12 for OGJB. I followed the guide, and after the ROM had finished downloading, I unlocked my phone with FreeGee, and booted up into TWRP, and wiped everything. I followed what the guide said:
Factory Wipe
Wipe cache
Wipe dalvik cache
So after that, I copied the ROM zip to my device, and attempted to install it. Long story short, I found out that the zip I had downloaded was bunk.
So there I was, stuck with a phone in recovery mode, and no OS. Great. I powered it down to save battery, and left it overnight, as I downloaded the working ROM zip.
The next morning, however, the phone wouldn't turn on, and instead began doing this odd behavior, where the red light would flash, then after a few seconds the red light as well as the soft keys would alternately flash. At that point I was still able to boot into fastboot, but not recovery. So with fastboot working, I decided to run LGNPST on it, because maybe it was something I installed.
So I did, and that did nothing. It still did the red light/softkey alternating flash for awhile, but then something more serious happened
My phone shut off completely. [/drama] Plugging it in has done nothing, either computer or wall with original cables. I have let it sit plugged in for a few hours, and have seen nothing. It isn't even warm, indicating that there isn't any power flow at all.
Am I completely screwed?
My next course of action that I was going to try was:
Take off back
Unplug battery
Hold power for 10 seconds
Plug battery in
Plug USB in
Pray
I've heard this can work.
Also, for reasons not important, I cannot return my phone.
Thanks guys.
Click to expand...
Click to collapse
Battery does not come out sounds like a brick or dead battery
Sent from my LG-E970 using Tapatalk 2
---------- Post added at 07:46 PM ---------- Previous post was at 07:45 PM ----------
See this post http://forum.xda-developers.com/showthread.php?t=2039707
Sent from my LG-E970 using Tapatalk 2
justin860 said:
Battery does not come out sounds like a brick or dead battery
Sent from my LG-E970 using Tapatalk 2
---------- Post added at 07:46 PM ---------- Previous post was at 07:45 PM ----------
See this post http://forum.xda-developers.com/showthread.php?t=2039707
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your reply.
Please see this:
http://forum.xda-developers.com/showthread.php?t=2039707
Update: The taking apart and unseating battery worked. Fixed!
zvb is for Sprint, and this is the AT&T section. However, I'm glad you're back up and running!
Hi All,
I got my HTC one and was playing with it for some days and decided to root and make it a google play edition. I did the following steps
1. Unlocked BootLoader from HTCDEV
2. Rooted and did S-OFF (Using REVONE)
3. Was trying to update MID to the GPE and tried to flash the .zip having the MID, CID using HBOOT and phone froze at RUU
4. I did a reboot and now phone is not turning on.
When I connect it to my PC I could hear the sound of it recognizing my phone but nothing is showing up. ADB and FASTBOOT not recognizing the device.
Does it mean my phone is hard bricked>??
If so, is there a JTAG service for HTC one?? The bootloader is still unlocked and i wont get anything from HTC as my warranty is void
Please help!!
topgun1984 said:
Hi All,
I got my HTC one and was playing with it for some days and decided to root and make it a google play edition. I did the following steps
1. Unlocked BootLoader from HTCDEV
2. Rooted and did S-OFF (Using REVONE)
3. Was trying to update MID to the GPE and tried to flash the .zip having the MID, CID using HBOOT and phone froze at RUU
4. I did a reboot and now phone is not turning on.
When I connect it to my PC I could hear the sound of it recognizing my phone but nothing is showing up. ADB and FASTBOOT not recognizing the device.
Does it mean my phone is hard bricked>??
If so, is there a JTAG service for HTC one?? The bootloader is still unlocked and i wont get anything from HTC as my warranty is void
Please help!!
Click to expand...
Click to collapse
Bumping Please help!1
If it doesn't work, you can always hit him with it ... Boris the blade
Did you flash eng hboot?
Did you flash the eng hboot? Isn't that the only way to change MID? or no? if you can try to boot into fastboot that way. I did the same thing with mine and thought i screwed it up. you should be able to rebootRUU and reflash the tmobile firmware to get you back on your way
Mine did the exact same thing. In fact I never saw the gray spotted screen. You just have to do a combination of button holds while plugging it in.. and it will boot. I had to hold mine for almost 2 straight minutes
You have to manually boot back into RUU mode..it has very specific instructions when flashing ehboot. Why would you go through all the trouble of a MID change when there are many awesome gpe roms? When I changed my mid I could only tell it was doing anything was because my computer made that connection ping.. otherwise the phone screen stayed completely black!!
Sent from my HTC One using xda app-developers app
altimax98 said:
Mine did the exact same thing. In fact I never saw the gray spotted screen. You just have to do a combination of button holds while plugging it in.. and it will boot. I had to hold mine for almost 2 straight minutes
Click to expand...
Click to collapse
Hi,
Thank you responding back. Could you please let me know what that combination is? I have tried almost everything
handman29 said:
You have to manually boot back into RUU mode..it has very specific instructions when flashing ehboot. Why would you go through all the trouble of a MID change when there are many awesome gpe roms? When I changed my mid I could only tell it was doing anything was because my computer made that connection ping.. otherwise the phone screen stayed completely black!!
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hi handman29,
I wanted the stock GPE ROM mainly for the direct OTA's from google. Could you please let me know how to manually bring back RUU
Does your phone show up when you type fastboot devices? If so you should be able to get back.
Edit: sorry didn't realize you said already.
Sent from my HTC One using Tapatalk 4
Moved to proper section, please read and respect the rules before posting.
Thanks,
I tried every possible way and gave up. I sent my phone over to HTC and they fixed it for free. The phone is on its way back.
Thank you very much for all your inputs.
As I have frequently done without issues, I was flashing a ROM and got stuck into some sort of bootloop.
Here are some details..
I was on a 4.4.2 KitKat ROM (Gummy Nightly) and decided to try out SlimKat 4.4.2. I wiped (advanced wiped System, Data, Cache and Dalvik Cache). I proceeded to flash the ROM and then the gapps file. Nothing out of the ordinary.. I rebooted and noticed I was at the samsung custom screen for a little longer than normal.. I didn't begin to worry too much because sometimes this screen can appear for a little bit before continuing when first booting into a fresh ROM install. Well.. quite some time passed and it became apparent that it wasn't going to go any further, I restarted the phone and consistently got stuck. I tried booting into TWRP and couldn't/can't get past the TWRP Blue Loading screen. I tried letting it sit for a long ass time (1 hour +) and same with regular rebooting at the Samsung Custom screen (1-2 hours +) with no luck or change.
I have a backup but can't get to it obviously. I'm quite frustrated and am confused/worried about attempting any drastic measures because all of the different phone versions/bootloader discussions/issues. I don't want to mess up the phone by bricking it or something when trying to flash the wrong file. I believe that right now the only thing I can do, if anything, is connecting my phone to my computer via a usb cable and running that ODIN program? I'd be inexplicably grateful and appreciative if someone can just give me some steps/instructions so that I can get my phone back up and running. I'm without a phone right now and am stressed out, so I'm hoping that I haven't made too many people upset with me if there's already somewhere this is answered. I searched but can't find someone with the exact variables my situation contains.
To Recap:
Phone will not progress past samsung custom warning screen as well as TWRP Blue Logo screen no matter how much time passes (Have let sit at either screen for hours)
Was flashing SlimKat nightly (the most recent two days ago) coming from Gummy nightly (1-12, I believe).
The samsung custom screen comes up and then the phone reboots 2 seconds later and comes up again etc..
I never had to use 'safestrap' or whatever. When I got my s4, I was able to avoid the update and was always able to flash ROMs without any worry or concerns.
Please XDA, Help me out here.. I'm completely stressed and worried and don't know where to go from here.. What files to I manually push from my computer.. I don't see how I can solve this without a computer because recovery wont load and ROM won't either
Can you plug it into a pc and get Odin to see it? If so, you can odin back to your stock firmware and start over.
I am having this same problem
a.demarco said:
Can you plug it into a pc and get Odin to see it? If so, you can odin back to your stock firmware and start over.
Click to expand...
Click to collapse
Hey I am having the same problem after trying to flash the latest version of hyperdrive, and my phone got stuck on the Samsung custom screen and I'm not able to get back into recovery even. I saw what you said and plugged my phone into my pc to see if odin could see it, but odin didn't recognize it and I even tried on Kies and it wasnt able to connect to my device either. Is there anything else I can do? or any solution?
If anyone can help I would really appreciate it!
This happened to me several times when i was using Gummy a few weeks back. I just kept doing battery pulls and restarting and was eventually able to get into TWRP. Try this some more and then odin.....
I have been trying to get it working with your advice of battery pulls but no luck. I have downloaded ODIN and installed and also downloaded the two tar files (the kernel and pre-source kernels). I *think* it's good news that ODIN/computer DOES see/recognize that my s4 is connected and disconnected. The issue I'm having is that when flashing the kernel, it does the first green bar and says PASS but the phone restarts and enters the bootloop (it restarts right into the Samsung Custom screen and will stay for a minute and restart again and again)..
I feel like I'm so close but so far away... I know that there's someone reading this that may have the solution or advice to help me get on my way.
I'm still without a phone and I know that there is certainly no one else to blame for my situation then myself but regardless, I would like to see this problem solved! I have a backup on my external sd and there's obviously no way to get to it since my phone won't actually let me into the recovery. The blue TWRP screen just hangs...
Please HELP!!! what can I do????
ccert said:
Hey I am having the same problem after trying to flash the latest version of hyperdrive, and my phone got stuck on the Samsung custom screen and I'm not able to get back into recovery even. I saw what you said and plugged my phone into my pc to see if odin could see it, but odin didn't recognize it and I even tried on Kies and it wasnt able to connect to my device either. Is there anything else I can do? or any solution?
If anyone can help I would really appreciate it!
Click to expand...
Click to collapse
I'm having your same problem, except mine was with RLS 13.
fafinaf said:
I have been trying to get it working with your advice of battery pulls but no luck. I have downloaded ODIN and installed and also downloaded the two tar files (the kernel and pre-source kernels). I *think* it's good news that ODIN/computer DOES see/recognize that my s4 is connected and disconnected. The issue I'm having is that when flashing the kernel, it does the first green bar and says PASS but the phone restarts and enters the bootloop (it restarts right into the Samsung Custom screen and will stay for a minute and restart again and again)..
I feel like I'm so close but so far away... I know that there's someone reading this that may have the solution or advice to help me get on my way.
I'm still without a phone and I know that there is certainly no one else to blame for my situation then myself but regardless, I would like to see this problem solved! I have a backup on my external sd and there's obviously no way to get to it since my phone won't actually let me into the recovery. The blue TWRP screen just hangs...
Please HELP!!! what can I do????
Click to expand...
Click to collapse
Just picked up an mdk s4 which was doing the same thing. I odin back to stock and booted into the phone to make sure everything was good. Then I went back into odin and flashed the md2 pre release kernel then booted again into stock and proceeded to use motochopper.
You shouod have 3 files. The mdk tar file and the two kernel files. Worked like a charm for me you sure you're doing the steps correctly?
Sent from my SCH-I545 using XDA Premium 4 mobile app
---------- Post added at 10:12 AM ---------- Previous post was at 10:10 AM ----------
Also when mine was doing that it was TWRP 2.5.0 and I threw the newest TWRP on after rooting and its much faster rebooting .
Sent from my SCH-I545 using XDA Premium 4 mobile app
fafinaf said:
I have been trying to get it working with your advice of battery pulls but no luck. I have downloaded ODIN and installed and also downloaded the two tar files (the kernel and pre-source kernels). I *think* it's good news that ODIN/computer DOES see/recognize that my s4 is connected and disconnected. The issue I'm having is that when flashing the kernel, it does the first green bar and says PASS but the phone restarts and enters the bootloop (it restarts right into the Samsung Custom screen and will stay for a minute and restart again and again)..
I feel like I'm so close but so far away... I know that there's someone reading this that may have the solution or advice to help me get on my way.
I'm still without a phone and I know that there is certainly no one else to blame for my situation then myself but regardless, I would like to see this problem solved! I have a backup on my external sd and there's obviously no way to get to it since my phone won't actually let me into the recovery. The blue TWRP screen just hangs...
Please HELP!!! what can I do????
Click to expand...
Click to collapse
How are you trying to get into recovery?
Sent from my SCH-I545 using XDA Premium 4 mobile app
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
Power + home +volume up. Then as soon as the phone cuts on let go of Power. Continue to hold the other 2.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Mightycaptain said:
How are you trying to get into recovery?
Sent from my SCH-I545 using XDA Premium 4 mobile app
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
Power + home +volume up. Then as soon as the phone cuts on let go of Power. Continue to hold the other 2.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You don't have to to finger Olympics on s4 like other devices... Just vol up and power
Folks,
My son in law just picked up a used Note2 that was originally a Verizon phone. The seller had thoughtfully loaded it with a stock unlocked ROM as the son in law was planning to use it on Pagepluscellular not Verizon. After receiving the phone he decided to use it with his Verizon account for a few months and had it activated. It worked great until it tried to auto update.
Now the phone will not boot. It opens to the Samsung Galaxy Note II splash screen but will go no farther. Son in law is not tech savvy and I haven't modded a phone since my old Motorola Razr V3XX.
I have looked around this site and am struggling with the terminology but I think I have learned that:
The phone is considered bricked.
The only option I find is the I605 unbricker link which will require me to dis-assemble the phone and solder a switch to short a resistor.
It appears that this will unbrick the phone but it is not clear what I should do after that. He would be happy with a stock Verizon ROM image but
I don't see an obvious link to a stock file. And I am not clear as to what image loader version (Odin?) to use.
Please offer suggestions or advice. I need to fix the phone for him but really don't plan to get into modding it. It he want's to do that he can learn it for himself.
Thank you!
Try going into recovery.. pull battery. . Wait 5 sec and put battery back in (I usually hold the power button down when battery is pulled) then hold home button and volume down.. While holding those down hold down the power button. See if it will go into recovery
Sent from my SCH-I605 using Tapatalk
---------- Post added at 06:32 PM ---------- Previous post was at 06:31 PM ----------
If you can get to recovery you should be good..
Sent from my SCH-I605 using Tapatalk
Yes! It will go into recovery. Every where else I read it said to use volume up not down.
With it in Recovery what is next? Can you suggest an OEM Rom?
Thanks!
Fixed!
Gotta love the forums. I found the guide at http://forum.xda-developers.com/showthread.php?t=2024207
and was able to fix the phone. The update that bricked it was of course the 4.3 so I has to resort to the VRUEMJ9 4.3 rom to get ODIN to succeed with an install but the load completed successfully and the phone is working great.