I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
brasstongue said:
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
Click to expand...
Click to collapse
Can u get into bootloader?? Press power + vol down??
brasstongue said:
After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols.
Click to expand...
Click to collapse
that means your firmware is either in a state of limbo, or you corrupted one of your partitions.
so I decided to try to reflash the stock ROM, using the RUU zip found here. Due to some problem
Click to expand...
Click to collapse
which ruu, and what was the problem
But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM.
Click to expand...
Click to collapse
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Thanks for the reply.
nkk71 said:
which ruu, and what was the problem
Click to expand...
Click to collapse
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
nkk71 said:
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
Click to expand...
Click to collapse
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
nkk71 said:
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
Click to expand...
Click to collapse
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
nkk71 said:
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
Click to expand...
Click to collapse
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
nkk71 said:
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Click to expand...
Click to collapse
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
brasstongue said:
Thanks for the reply.
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
Click to expand...
Click to collapse
my bad, thought I read Sprint, not sure if Sprint and Verizon use same recovery, but that doesn't really matter now
unless you can get to bootloader, you're stuck, sorry.
If your pc does see "fastboot devices" then it must be in bootloader and flashing a ruu.zip (if available) could (that's a very big could) get the device working again.
Related
...Brick an *UNROOTED* G1...?!
I attempted a soft factory reset (which I have done on many occasions previously successfully) but on this occasion I've run into the bootloop. Hitting Camera+Power button results in bootloop also.
One thing to mention is I removed my SD card before running the factory reset?
I've tried leaving the battery out over night and trying again in the morning.
I've tried placing the SD card back in and booting up the phone.
I've tried holding Home+Power to get into recovery but results in bootloop
I've tried holding Camera+Power to get into Bootloader but results in bootloop.
Any suggestions please?
Thanks!
No, this should not happen. With Bootloop do you mean there is just the G1 logo and nothing else, or does it get past the logo and reboots then?
Another thought, has this phone ever been rooted and unrooted again?
If you are still under warranty and the phone is completely stock, I'd return it.
Nope. Phone has never been rooted then unrooted.
By bootloop, I mean, G1 T-Mobile logo shows followed by a picture of a open box with the phone just outside animation and then seconds later the phone reboots itself running into this loop again and again.
Warranty is only for a single year, right? So then that's not an option.
Thanks for suggestions.
Jignesh Sutar said:
Warranty is only for a single year, right? So then that's not an option.
Click to expand...
Click to collapse
Depends on where you are: http://www.htc.com/www/support/warranty.html
It looks like you phone either fails to boot, thus tries to boot recovery (box picture is the background of the recovery) and then reboots (best case, i guess) or the boot to recovery flag is set, recovery fails, reboot (you might seriously be screwed).
You are sure that you can't enter the bootloader? Also try Back+PowerOn. That would make things alot more easy.
How long does it stay with the box picture? Long enough to get adb connected? If yes you could try "adb shell reboot bootloader".
Tried all combinations of buttons to try get into bootloader or recovery, nothing!
Definitely no chance of being able to ADB, the phone switches off very quickly...
Also, have ensured the battery is fully charged, in case that has an impact?
I really looks like you are the first all stock bricked guy I ever heard of.
The boot recovery flag seems to be set for some reason (is this set during a normal hardreset?) as all boottime commands are ignored.
The recovery fails improperly (sounds strange, but if it failed properly, you would end up in bootloader or your system).
-> That really looks like a brick...
Options:
- Warrenty
- JTAG
- perhaps someone else has another idea / sees something I missed...
Good luck with it.
Jignesh Sutar said:
By bootloop, I mean, G1 T-Mobile logo shows followed by a picture of a open box with the phone just outside animation and then seconds later the phone reboots itself running into this loop again and again.
Click to expand...
Click to collapse
What where you flashing? It probably had a radio and something got copied incorrectly into the staging area of ram.. if the radio passes recovery's validation but not the current radios validation you can get stuck.. this shouldn't be possible but I've seen it before.. my bet is a bit error at the wrong point in time.
Hi all,
I have had my N1 for 1year and two weeks now (yes, warranty just expired). I was charging the device and it seemed to overheat and reboot. I unplugged it, took the battery out, let it rest for a bit and tried to boot it again. The phone now gets stuck on the X logo (not moving) and never boots.
I'm currently abroad (in the UK) and can't have it sent back for repair (I'd have to pay the repair too).
Will rooting the phone and installing an alternate OS fix my phone?
Is there any way to get HTC to honor the warranty after two weeks of expiration (I've been getting this problem for a while now, but that was only an issue if I made extensive use of the device while charging, which I almost never do so I didn't bother.)
Is there any way to fix this issue without messing with rooting? I'm abroad right now and all I want is my phone to work.
Any suggestions are welcome.
Try booting into bootloader from power off (vol- pwr) if that doesn't work then try the 3 figure salute (pwr vol- tb) your phone should boot into fastboot then just select bootloader.
If either of these work the your good you can get the static x fixed all you need to do is passimg (search wiki if you don't know what it is) as for the charging problem passimg will factory reset the phone so if that doesn't fix it then no you'll need to try rooting or it might be hardware.
Yes, I'm able to go into the bootloader.
I tried clearing the storage, choosing fastboot, etc. The phone seems to be working, just won't boot past the static X.
From your last reply, you're saying passimg has good chances to fix my phone. What does that involve? Do you have a link to a how-to that I could follow (it would really be a bad time for me to brick my phone, a good how-to would be really appreciated).
Cheers!
Yes passimg is used for many things it just reflashes a shipment ROM to the phone through bootloader. Like I said you can visit the wiki to have a how to here is a link http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials scroll down to "Unroot / Restore your Nexus" then follow the instructions. This should restore you to frg33 then you just need to update back to 2.3.4.
NOTE: this will wipe your data.
Ahh there's a way to unroot the nexus one now!
I had no idea! This is good to know (last time I checked was in December I think).
I will give that passimg a try as soon as I get home.
Can anyone confirm that this ("Attention: Latest stock ROMs don't flash using PASSIMG.ZIP method. Use the provided latest Froyo PASSIMG, and upgrade it after flashing.") means I can still reflash using this if I have the latest ROM (2.3.4) but will simply have to update again after (which I might not do given the issues I'm facing).
Cheers!
Confirmed - Dude is giving you good info... xD
Just to verify, unrooting is not the same as relocking. If you unlocked your bootloader (have a little lock symbol under the X screen), there is no way to relock it.
But the passimg is a good option. It will take you back to an older version of Android, and then you just let the system update itself.
Since you are out of your warranty, I can highly suggest looking into custom firmwares. These give you a lot more features and in many cases, perform better. CyanogenMod is probably the most popular one. These will fully replace your Android OS. CyanogenMod really doesn't even differ in look from stock all that much. Most people probably wouldn't even have a clue they are running something different, except for the stability and performance increases.
You can read up about this stuff in the wiki as well.
Oh, I see, thanks for the info.
I'm actually trying to get the FRG83 passimg file but the link is dead. Does anyone have an alternate one?
Use the FRG33 image
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Try the passimg, but it's possible that you are looking at hardware failure...
ldiamond2 said:
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Click to expand...
Click to collapse
If you are still running stock Android, you can't reboot between installing the recovery and getting into it. Stock Android will replace it. Try to go back to the bootloader and select recovery then, or fastboot to load the recovery, and then use fastboot to boot off of it.
Code:
fastboot flash recovery "c:\location to\recovery.img"
fastboot boot recovery "c:\location to\recovery.img"
Hopefully this will get you into Amon_RA so you can try again.
But the passimg method is used in the bootloader, not in recovery. You don't need a custom recovery to use the passimg method.
Amazing, thanks for pointing out my mistake, that give me a little bit of hope now . (I was at the point where I'd open the thing and look for a broken solder joint.)
I will try this as soon as I get home!
**Edit** I actually am not sure if I really rebooted or went straight to recovery. I'll update this thread tonight.
According to some other people, this would be a common issue with the internal memory dieing.
Is there a utility I can use to check the state of the memory?
None that I know of. Our phone internal memory uses the yaffs2 (Yet Another Flash File System v2) file system. I haven't heard of any programs that can check it.
Same situation
Hello, all. I haven't signed in on here in ages just because I've been so happy with how my Nexus has been running.
I ran into the same problem as OP stated.
I think I have some sort of hardware issue because my phone used to randomly freeze and couldn't be restarted unless I pulled the battery. Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Is there any way to check for hardware damage? My warranty is over as well so I'd have to pay for any repairs to my phone if I sent it in.
If it's running, you can try to pull a log, and see what error reports you get?
andythefan said:
Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Click to expand...
Click to collapse
Your power button might just be dead. Try having the phone plugged into a power source and removing and reinserting the battery. While you are doing that, hold the Volume Down button. This will get you into the bootloader which would allow a passimg to be performed. Hopefully your reboots aren't a hardware problem.
So , after pulling my battery, pulling the sim and the sd card, it finally turned on and went to recovery without freezing. I was able to wipe and reflash cyan 7. It's working well for now, but I'm really afraid this is going to happen again because this isn't the first time that it's just froze repeatedly.
Does anyone know what the problem could be?
Alright,
I did "fastboot flash recovery MYIMG" then "fastboot boot MYIMG", didn't work.
Then I tried "fastboot flash recovery MYIMG" then go to bootloader (without rebooting) and selected recovery.
Still no luck.
It always freezes on the static X logo. What else can I do? Will using passimg be any different (I don't have any way to put the file on the micro SD card but I can manage to do it if it's worth the shot).
Thanks
Hello everyone. In my attempt to experiment with custom ROMS yesterday, I seem to have sort of soft bricked my phone. When I install the stock OS, it installs fine, and I can start the phone. However, after it boots up, there are no apps. Just the clock at the top, the background, and the menu button in the bottom center (but pressing this button doesn't do anything). I can pull down the top menu and go to settings, but I don’t have access to anything else. Furthermore, after a couple minutes, the phone restarts itself. After this first restart, when its gets done booting, there is simply an empty black screen. The only way to get to the state mentioned before is to boot into bootloader, turn the phone off, and then turn it back on.
I’m wholly lost and out of ideas on how to go about troubleshooting this. Here is what I did yesterday to get to this point:
1. Unlocked the bootloader.
2. Flashed the latest Viper rom. It didn’t work; after booting up the phone was forever stuck on the Viper splash screen.
3. Flashed the stock Sprint HTC One rom. Again, after booting up the phone was forever stuck on the HTC splash screen.
4. Used TWRP to format all the data.
5. Flashed the stock Sprint HTC One rom again. This time it worked just fine. At this point, I thought I had discovered a valid method for fixing my soft bricked phone, so I decided to experiment with Viper and Android Revolutions roms to see if I could get them to work. I followed the process of installing a custom rom, getting stuck on the splash screen, formatting the data, then reinstalling the stock rom 3 times. On all three times the stock rom worked when I installed it. However, on the 4th iteration of this cycle, I reached the state I described above.
I tried using the RUU utility, but it doesn’t work (I get a signature verification error). I can enter bootloader and recovery without issue.
I've had this happen to me, Make sure that you re-lock your bootloader before the RUU
fastboot oem lock
I believe this will allow the RUU to start up right and repair. Lemme know how that goes.
jclark11 said:
I've had this happen to me, Make sure that you re-lock your bootloader before the RUU
fastboot oem lock
I believe this will allow the RUU to start up right and repair. Lemme know how that goes.
Click to expand...
Click to collapse
Do you mean you have had the same blank screen problam as well? Or RUU wouldn't work for you?
I'm pretty sure i relocked the bootloader when I tried doing the RUU, but I will definitely try again. Unfortunately, I'm on a trip at the moment, so I'm not sure when I'll be able to look at it again (hopefully Saturday or Tuesday).
I have had my HTC One M7 shortly after it was release. I got it from ATT. I immediately found a guide here and rooted it. I had TWRP and every time ATT tried to push an OTA I would refuse. I haven't bothered with it until a couple weeks ago when I wanted to put in KIT KAT. so I found m7_Stock_Rooted_4.18.502.7_odex.zip. I did a dirty upgrade, as the thread said it was okay. And it was. I am going on a trip so I purchased a sim unlock code in between upgrading to kitkat and today.
I got another OTA. I must not have read the bootloader correctly to refuse the install. I was no longer rooted. I come back to XDA and thought what the heck, I'll try out this ROM, it looks nice: Android_Revolution_HD-One_83.1.zip. I use TWRP to put the ROM in and now I am full of fail. After a little bit of Google I decided to try to do a factory reset. And now I am stuck in a boot loop. I have went back to Google but so far all I have seen is use adb or some other method to put things on the "sd card". But how would I do that when this phone doesn't have a sim card and I can't hook it up to my computer anymore? FWIW at some point in the boot loop my computer will recognize the phone, but it won't stay in that state long before it goes away. What happens is my phone starts too boot. Boot screen comes up. After about 10-15 seconds it restarts. This time saying entering recovery.... at the top. That lasts for about 2 seconds, phone goes black and reboots like normal. Over and over.
Best I can do is get to the android hard reset screen by holding power and reset screen. But that is saying "tampered" and "unlocked" at top. I chose the factory setting option and that doesn't do anything to alter the current state.
Edit:
When I went to flash Android Revolution ROM I chose wipe data. It gave some error that some files were not copied. So I ran it again, straight from TWRP. But that never installed right and I was stuck in a boot loop. I don't have many options with the android hard reset menu. But if choose restore, I will get to see the screen from TWRP flash for just a moment before it goes away and reboots.
Also I do see my phone when I have it plugged in the control panel (windows). Under devices and printers, it is listed as Android 1.0 under unspecified devices.
Budee80 said:
I have had my HTC One M7 shortly after it was release. I got it from ATT. I immediately found a guide here and rooted it. I had TWRP and every time ATT tried to push an OTA I would refuse. I haven't bothered with it until a couple weeks ago when I wanted to put in KIT KAT. so I found m7_Stock_Rooted_4.18.502.7_odex.zip. I did a dirty upgrade, as the thread said it was okay. And it was. I am going on a trip so I purchased a sim unlock code in between upgrading to kitkat and today.
I got another OTA. I must not have read the bootloader correctly to refuse the install. I was no longer rooted. I come back to XDA and thought what the heck, I'll try out this ROM, it looks nice: Android_Revolution_HD-One_83.1.zip. I use TWRP to put the ROM in and now I am full of fail. After a little bit of Google I decided to try to do a factory reset. And now I am stuck in a boot loop. I have went back to Google but so far all I have seen is use adb or some other method to put things on the "sd card". But how would I do that when this phone doesn't have a sim card and I can't hook it up to my computer anymore? FWIW at some point in the boot loop my computer will recognize the phone, but it won't stay in that state long before it goes away. What happens is my phone starts too boot. Boot screen comes up. After about 10-15 seconds it restarts. This time saying entering recovery.... at the top. That lasts for about 2 seconds, phone goes black and reboots like normal. Over and over.
Best I can do is get to the android hard reset screen by holding power and reset screen. But that is saying "tampered" and "unlocked" at top. I chose the factory setting option and that doesn't do anything to alter the current state.
Edit:
When I went to flash Android Revolution ROM I chose wipe data. It gave some error that some files were not copied. So I ran it again, straight from TWRP. But that never installed right and I was stuck in a boot loop. I don't have many options with the android hard reset menu. But if choose restore, I will get to see the screen from TWRP flash for just a moment before it goes away and reboots.
Also I do see my phone when I have it plugged in the control panel (windows). Under devices and printers, it is listed as Android 1.0 under unspecified devices.
Click to expand...
Click to collapse
which twrp version do you have installed?
little123 said:
which twrp version do you have installed?
Click to expand...
Click to collapse
Thanks dude. I had an older version, since I originally rooted this phone around 18 months ago and used a version from back then. I watched a youtube video how to push TWRP onto a soft bricked device using ADB. After that, I was able to install the ROM.
Budee80 said:
Thanks dude. I had an older version, since I originally rooted this phone around 18 months ago and used a version from back then. I watched a youtube video how to push TWRP onto a soft bricked device using ADB. After that, I was able to install the ROM.
Click to expand...
Click to collapse
glad i could help with just a question
Hello,
I fear my daughters european HTC Desire 510 is bricked. First of all, we have already given up on what is on the phone. So no worries if a solution means wiping EVERYTHING from the phone, as long as we can get it to start again.
For some unknown reason, possibly an update the phone went into an almost constant bootloop a month or so before christmas. It could eventually get to the login screen, after going in circles for anything between 20 mins and hours. So I thought I would try to tamper with it. I know how to get into the bootloader from rooting other phones, so I went there to try to reset the phone to the factory settings. The result was that the phone now wouldn't go there again. If I tried to do a second reset it went straight to boot, without any way to interrupt, same thing when trying to go into recovery, instant reboot in the blink of an eye.
What then happens when the phone reboots? It gets to the first screen, green HTC logo and "Powered by Android", it sits there for maybe 30 seconds, then it goes black, buzz and back to the previous HTC logo. And this goes on until the battery dies, I pull the battery or I quickly push the vol down and power buttons to go into HBOOT.
I usually don't give up this easily. I found another thread here on some european guy having trouble with his Desire 510, and one of the answers linked to a RUU for a european 510. So I thought, why not, I hadn't unlocked the bootloader yet. So I downloaded the RUU and tried to install it. It messed with me a little, aparently as expected, and then ran through the whole installation. Before the upgrade, well downgrade to be specific the OS was ver. 1.51.401.4 but now claims to be 1.51.401.1. Problem though is, absolutely no change in behaviour. I have restarted the phone after pulled the battery and waited for anything between seconds and an hour, and the phone does exactly the same thing. It happily goes into HBOOT but won't allow me to do a factory reset, nor will it allow me to access recovery.
It will allow me to access Fastboot though, so I thought, hmmm if I install ClockWorkMod or TWRP, maybe something will change. Since I'm more used to working with CWM I went down that road, went to htcdev.com, got the unlock code and unlocked the phone. It now says <<< UNLOCKED >>> and I ran the fastboot devices command, that happily returned some "CC4********7 fastboot". So I went ahead and installed CWM, the installation went all the way and in the end it happily stated that CWM was installed. But did that mean any difference, noooo. If I try to access either Recovery, that should start CWM or Factory reset and also Check smartsd, instant reboot. And I mean INSTANT. Fastboot works, as already stated. I can also get into Image CRC and Show barcode, but what good is that.
Any ideas. I'm beginning to think that something is physically broken inside the phone.