Hi guys I really need help at this point,
I have an AT&T HTC One M8 originally I was on Skydragon rom rooted till I found out MM was finally available. I then relocked my phone and flashed original firmware to get back to origianal. I tried The OTA at that time but no luck. So I downloaded the MM ruu file from HTC.com and still no luck. I tried like 5 times and it would get stuck step 2 of 2 sending rom to phone... After a few times and calling htc still no luck. The rep said it would be ok to just disconnect and everything was fine I guess. Today I came across a thread here on xda in which a member mentioned flashing the MM firmware first then try the ruu again. The firmware updated but the ruu is still not working. Still stuck on step 2 of 2 sending rom to phone for almost 3 hours now... The biggest problem now is unlike the last times when I tried disconnecting this time my phone would not start. it just gets stuck on white HTC logo screen and that's it... so frustrating... so now I am without phone - please help!
it allowed me to try to run the ruu again but still stuck at the same spot and still wont startup.
someone anyone please help!
side not everyone mentioned memory possibly being the issue - well I checked and I have 21 gb of internal memory:crying: available so...
last thing: I also tried flashing back to stock ruu and now it wont let me after flashing the firmware so i have no idea what to do now.
My responses below in red font:
rsuarez74 said:
I then relocked my phone and flashed original firmware to get back to origianal. What exactly did you flash (file name, I assume an RUU?)?
I tried The OTA at that time but no luck. What does that mean "no luck"? Any error messages, how far did it get, what were the specific results?
So I downloaded the MM ruu file from HTC.com and still no luck.
I tried like 5 times and it would get stuck step 2 of 2 sending rom to phone... Today I came across a thread here on xda in which a member mentioned flashing the MM firmware first then try the ruu again. The firmware updated but the ruu is still not working. Still stuck on step 2 of 2 sending rom to phone for almost 3 hours now... There is a connectivity issue, probably due to PC configuration. Win7 and USB2.0 have the best compatibility. If Win10, you can try to run the RUU in Win7 compatibility mode, and see if that helps. Try another USB port, try another cable. You may have to resort to another PC, if you have access to one.
side not everyone mentioned memory possibly being the issue - well I checked and I have 21 gb of internal memory:crying: available so... The free storage issue (need 14 GB free, maybe more) only applies to the OTA, from what I've seen. It doesn't apply to the RUU.
last thing: I also tried flashing back to stock ruu and now it wont let me after flashing the firmware so i have no idea what to do now. "Stock firmware" meaning what (exact filename)? I assume you mean Lollipop (LP) RUU as "stock" means different things to different folks - so you need to be specific. Once you've flashed the MM firmware, you can't run the LP RUU, unless you find and flash the LP firmware first. The firmware needs to match the RUU, in other words (thanks to some new requirement HTC added with the MM RUU). But seeing as the goal it to RUU to MM, I'd not mess with going backwards at this point, and focus on getting the MM RUU to work.
Click to expand...
Click to collapse
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
1. RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2
2. got to "2/2 sending rom image to android phone" (black htc logo screen) hung for like 3 hours.
3. I am using windows 7 with usb 2.0 and all proper drivers installed
4. I tried installing the mm firmware before installing th mm ruu but still no luck - same results
rsuarez74 said:
1. RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2
2. got to "2/2 sending rom image to android phone" (black htc logo screen) hung for like 3 hours.
3. I am using windows 7 with usb 2.0 and all proper drivers installed
4. I tried installing the mm firmware before installing th mm ruu but still no luck - same results
Click to expand...
Click to collapse
You really need to stop posting "no luck" without giving any details. I advised you on that earlier, and I don't like repeating myself. What does that mean "no luck"? Please give as much detail as possible. You didn't specify whether the firmware actually installed or not. How far did the firmware install get? What was the output on the screen? Any error messages? Did you flash the firmware twice (which is usually required)?
Its clear you have some general connectivity issue. Until you solve it, you can run RUUs forever, and they will still fail.
Did you try a different cable (as I previously advised)? Is the phone in fastboot mode when you try to RUU? Any response to command: fastboot devices
redpoint73 said:
You really need to stop posting "no luck" without giving any details. I advised you on that earlier, and I don't like repeating myself. What does that mean "no luck"? Please give as much detail as possible. You didn't specify whether the firmware actually installed or not. How far did the firmware install get? What was the output on the screen? Any error messages? Did you flash the firmware twice (which is usually required)?
Its clear you have some general connectivity issue. Until you solve it, you can run RUUs forever, and they will still fail.
Did you try a different cable (as I previously advised)? Is the phone in fastboot mode when you try to RUU? Any response to command: fastboot devices
Click to expand...
Click to collapse
ok I apologize. The mm firmware did install correctly as far as I can tell. Then tied the mm ruu again but still hung at step 2/2 sending rom image. Only difference hat time s when I tried to disconnect I was stuck on white htc screen. I also tried new cable. and yes I did mostly everything in fastbot mode. fastboot seems to be working ok.
Could you boot a TWRP recovery img from fastboot and then use it to restore a NANDroid backup? This assumes you're still having problems.
Related
About a month ago I rooted a HTC EVO 4G LTE, installed the recovery with touch screen and Cyanogenmod nighties.
It worked great, including tethering on Sprint.
Last week an update to latest Cyanogenmod was made. Phone worked normally, until today when screen stopped responding completely (physical buttons were working), including after rebooting. On a second reboot phone was stuck on a boot loop.
Went into bootloader mode and tried to go to recovery. It would boot loop again. Noted that it said UNLOCKED S-ON (I thought it was supposed to be S-OFF). I tried flashing the boot.img from latest Cyanogenmod. Nothing. Tried reseting from the menu. Tried more things. Nothing worked. So I downloaded and used the latest version of RUU after fastboot oem lock. RUU was successful (no error, phone no longer displays HTC developer message), however it's still stuck on the boot loop. I thought RUU would restore it completely.
What am I missing?
Read here
http://forum.xda-developers.com/showthread.php?t=2084633
And here
http://forum.xda-developers.com/showthread.php?t=2097150
#Root-Hack_Mod*Always=SG3
I followed the instructions.
Then I tried all RUU that I had and always got Error 140.
Finally, found in a rooting pack RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe which worked to restore.
However, the phone is still in the same state. What do I do?
How long did you give the phone to boot.? Also did you flash the firmware zip after you relocked your boot loader?
#Root-Hack_Mod*Always=SG3
Phone is RELOCKED.
What I did:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
Then used that RUU to restore. After this I left the phone without touching it for about ten minutes, but it keeps restarting (never passes booting stage).
Try this. Remove your sd. Then back up all your data. Then format it threw your PC and return it to factory defaults. Then put it back in your phone and redo the steps. Also were did you get the ruu your using from ?? Also if that fails to work look here
http://forum.xda-developers.com/showthread.php?t=2045935
And try the firmware zip with the stock recovery. Then run the ruu. Hope this helps.
#Root-Hack_Mod*Always=SG3
Does it matter if the SD is in?
So, I took out the SD card, repeated those three steps and I should use RUU again.
The RUU is from 3.15_RUU_PLUS_ROOT.zip.
I'm going to try again now with no SD.
Same result after trying without SD card. Also I did flashboot flash zip
Code:
PJ75IMG_3.15.651.6-firmware.zip
from the link you provided without help.
PepeJones said:
Does it matter if the SD is in?
So, I took out the SD card, repeated those three steps and I should use RUU again.
The RUU is from 3.15_RUU_PLUS_ROOT.zip.
I'm going to try again now with no SD.
Click to expand...
Click to collapse
Yes the sd card should be in your phone. Also your trying to go back to stock so using the ruu that's stock with root might be the issue given your phones current state. I'll try and find you just the stock ruu with no root, unless you have one or if you know were one is download it and run it. Also when I posted about the SD card you were only supposed to remove it to "back up your data" and then "format" it. After you have formatted it then place it back into your phone. I'm not aware of any potential issues with running a ruu without the SD card being in the phone, however I would strongly suggest always running the ruu with the SD in the phone. Its what I've always done. Also make sure that your battery is over 75%. And did you flash the one with the stock recovery? There are several firmware zips on that thread but the one with the stock recovery is the one I suggested you try. And I'm not sure what the "without help" post is about. I'll help you as much as I can and I'm sure if I don't reply to you right away that there are more than enough knowledgeable members in this forum to help you as well. Take in mind that phones are so easy to screw up but it might take some time to get it back up and running. But troubleshooting is all part of the process.
#Root-Hack_Mod*Always=SG3
I'll try it again with the SD card in the phone. No, the RUU I'm using it's in a pack for rooting and updating. I don't think it's modified at all. I don't even think RUU can be altered and signed anyway. I'll search for another RUU again.
Yes, the one that I flashed is
Code:
PJ75IMG - Firmware zip with hBoot and stock recovery (signature intact)
http://d-h.st/sKO (MD5: 0d8f9d65e29c1c824654bf88b9438f15)
and I had enough battery. (It was supposed to be without luck not without help).
So, I'll flash the above mentioned PJ75IMG, then use the RUU (I'll search for one that's in no pack, but I'm confident it's not altered) - all this with the SD card inside.
Thanks for your help.
laie1472 said:
Yes the sd card should be in your phone. Also your trying to go back to stock so using the ruu that's stock with root might be the issue given your phones current state. I'll try and find you just the stock ruu with no root, unless you have one or if you know were one is download it and run it. Also when I posted about the SD card you were only supposed to remove it to "back up your data" and then "format" it. After you have formatted it then place it back into your phone. I'm not aware of any potential issues with running a ruu without the SD card being in the phone, however I would strongly suggest always running the ruu with the SD in the phone. Its what I've always done. Also make sure that your battery is over 75%. And did you flash the one with the stock recovery? There are several firmware zips on that thread but the one with the stock recovery is the one I suggested you try. And I'm not sure what the "without help" post is about. I'll help you as much as I can and I'm sure if I don't reply to you right away that there are more than enough knowledgeable members in this forum to help you as well. Take in mind that phones are so easy to screw up but it might take some time to get it back up and running. But troubleshooting is all part of the process.
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
PepeJones said:
I'll try it again with the SD card in the phone. No, the RUU I'm using it's in a pack for rooting and updating. I don't think it's modified at all. I don't even think RUU can be altered and signed anyway. I'll search for another RUU again.
Yes, the one that I flashed is
Code:
PJ75IMG - Firmware zip with hBoot and stock recovery (signature intact)
http://d-h.st/sKO (MD5: 0d8f9d65e29c1c824654bf88b9438f15)
and I had enough battery. (It was supposed to be without luck not without help).
So, I'll flash the above mentioned PJ75IMG, then use the RUU (I'll search for one that's in no pack, but I'm confident it's not altered) - all this with the SD card inside.
Thanks for your help.
Click to expand...
Click to collapse
You can't flash a PJ75IMG.zip unless you are S-OFF and the file you posted above is not an RUU it's just the updated firmware
It didn't work.
So I followed the steps from this link.
After using HTCDev to unlock the phone and I try to open RabiesShot, it reboots the phone but it's not able to connect. Sometimes the phone goes in a loop, sometimes the phone boots (it did boot twice). However, even when it booted, the screen didn't work at all, which is the original problem.
Right now the phone is ON but the only thing that works is the power and volume buttons (screen and soft buttons do not work). I've also noticed the phone reboots alone.
Any ideas left?
(This is my friend's phone. Anyway, I'll convince anyone to stay away from HTC. Nexus is so much better than this...)
Its not the phone its the user. I've never heard of a phone hacking itself. So usually the fault is the owner of the device and not the device itself. And In this case I'd say its user error. Also I'm lost as in what your doing at the moment. I thought you were trying to go back to stock? Now you post says your basically trying to obtain s-off. If this is the case then you make it extremely difficult to try and pin point what's actually the issue with your firends phone because you jump methods. So at this point exactly what are you trying to do ? Are you trying to go back to stock to gain s-off ?? Also if you come here to receive help with your issue you should always try the posted methods first so the member that's helping you is aware of what steps your taking and what your going to do. If not then it becomes difficult to help you.
#Root-Hack_Mod*Always=SG3
laie1472 said:
Its not the phone its the user. I've never heard of a phone hacking itself. So usually the fault is the owner of the device and not the device itself. And In this case I'd say its user error. Also I'm lost as in what your doing at the moment. I thought you were trying to go back to stock? Now you post says your basically trying to obtain s-off. If this is the case then you make it extremely difficult to try and pin point what's actually the issue with your firends phone because you jump methods. So at this point exactly what are you trying to do ? Are you trying to go back to stock to gain s-off ?? Also if you come here to receive help with your issue you should always try the posted methods first so the member that's helping you is aware of what steps your taking and what your going to do. If not then it becomes difficult to help you.
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
Not hacked itself, just not working. At least, that's what I've been told. Right now I'm trying to make it stock, but since what you proposed didn't work I tried different things such as obtaining S-OFF (no success).
The comment regarding HTC wasn't necessarily related to this case but in general. Just look how miserably is the process to just obtain root and unlock the bootloader. And in many cases is not even possible until some exploit is found. Why...? HTC used to be great.
I'm just trying to get this phone work again. Initial idea was to go stock, since it seems logical that it should be straight forward.
So I tried everything you have posted, including the last instructions you left me (backup everything off SD, deleted everything and inserted SD in the phone, then repeated the process).
Thanks for your help.
I understand your frustration about the issues with the phone in its current state. However if done correctly gaining root/s-off can be achieved in less that an hour. I do realize the fact that even if guides are followed to the exact directions that issues still occur. But that's the risk you take when you modify you phone. Your aware of this I'm sure. However that's why xda is a great website. Not only can you get the software to modify your phone, you can also get help in case the process didn't go the way it should have. You can't dispute the fact that there are more than a few members with the evo-lte who had no problems at all with gaining root or s-off. As far as the steps I suggested there was no guarantee that they would work its just the process of trouble shooting to see what will work. If you don't mind can you post the exacts steps you took before you tried to achieve s-off ? Also can you post the links to the exact ruu and firmware you last used as well.? Also if the phone is on try powering it down and attempt to boot into the boot loader. If your successful then try factory reset.
#Root-Hack_Mod*Always=SG3
Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.
Hi,
I'm a bit new here and running a good old-fashioned stock Inc 4G LTE, never rooted or flashed to new ROM. It DOES have the latest OTA update from Verizon a couple months ago.
This morning my phone suddenly went off after working OK. Then when trying to restart, I get an infinite boot loop and it won't get past the red Droid screen. I've searched various threads and tried what I think are the most obvious things, and nothing seems to help. But I want to make sure there are no other options before I throw it in the trash.
Here's what I tried:
- Tried entering Safe Mode by holding down volume key after HTC screen comes on. Makes no difference, does not enter Safe Mode.
- Get to HBOOT OK. Says 'LOCKED' and I am running HBOOT v.1.15.0000.
- - In HBOOT, I've tried running Recovery a couple times. Seems to go OK, but just starts looping when restarting.
- - In HBOOT, tried running Recovery > Wipe Cache Partition. Says cache is cleared.
- - In HBOOT, tried running Recovery > Wipe data/factory reset. Seem to go through OK.
- - In HBOOT, tried running Factory Reset.
- - In HBOOT, tried running Clear Storage.
- Pulled battery and tried spare.
- Removed SD card.
Some history - this phone has always been very sluggish. A few months ago started shutting down when doing camera intensive things (would jump to battery at critical level). So I did a factory reset a couple weeks ago and was slowly adding some of the essential apps back in. It crashed trying to upload photos to Facebook. Last night I had just moved some apps to the Phone storage and set my Sound Profile app to change profiles in the morning. This is about the time the phone crashed.
Anything else I should try before giving up?
Can I try to root and install a custom ROM to fix when in this state? Is this now possible with latest OTA update?
If custom ROM is last chance, is there a really solid one running 4.3 and Sense?
THANKS! May be time to get a HTC One or iPhoney, as I'm just not into huge phones that are coming out...
iRunNaked said:
If your on bootloader 1.15.0000 and now 1.16.0000, try using the stock Ruu and restoring the phone. If not, try rebooting in bootloader and factory reset.
If that doesn't work, gain root (if you haven't) and get s-off/unlock bootloader/CID set to 111111, and try a custom rom. If all else fails, take it back to stock and unroot/s-on/CID back to VZW/Relocked.
Call Verizon and tell them you need a replacement. The phone randomly gets real hot and reboots. They should send you a new one no problem.
I girlfriend had the random reboots, ending up getting it replaced. Now shes on her 4th or 5th incredible lte. (data Issues & random reboots)
Click to expand...
Click to collapse
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
jethrodesign said:
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
Click to expand...
Click to collapse
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
jethrodesign said:
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
Click to expand...
Click to collapse
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
stringedonbass said:
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
Click to expand...
Click to collapse
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
jethrodesign said:
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
Click to expand...
Click to collapse
Yes, my understanding is that to use adb, you need to be able to boot into the OS with usb debugging turned on. Hopefully someone will come along with a worthwhile response!
Is anyone aware of more current RUU's than are menteioned here?
http://forum.xda-developers.com/showthread.php?t=1770978
---------- Post added at 05:19 PM ---------- Previous post was at 05:07 PM ----------
If the phone failed as a completely stocked phone, why not try returning as opposed to figuring out how to root a broken phone?
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Altom85 said:
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Click to expand...
Click to collapse
Try using the TWRP found here:
http://forum.xda-developers.com/showthread.php?t=2639180
Sent from my Nexus 5 using XDA Premium 4 mobile app
download this twrp http://d-h.st/7Cr
name it properly and fastboot flash it. after that mount your device to you pc and transfer a rom zip to storage.
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Altom85 said:
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Click to expand...
Click to collapse
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
FesterCluck said:
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
Click to expand...
Click to collapse
Ok it's not stuck anymore, I can get into recovery and bootloader, so I'm not in a panic anymore at least However, my computer is not detecting my phone, nor is VipeRUU. If I try to mount to the computer via TWRP, nothing comes up. BTW my recovery is 2.7.8.0b now. Still no OS, still gets stuck on the HTC screen until I boot to recovery or bootloader
Edit: Now the computer tries to install drivers for my phone whenever I plug it in. It pops up as HTC MTP Device, always fails to install, then has a warning in the device manager. So I uninstalled the drivers, uninstalled HTC Sync, reinstalled HTC Sync. Didn't help. This is beyond frustrating...
Edit 2: After scouring the internet someone said to lock the bootloader and that'll allow my PC to see my phone. Well, now i have a RELOCKED (that's what it says on top) bootloader and I'm no closer to the solution methinks. I'm ready to just throw this phone out the window.
Edit 3: I actually discovered ViperRUU has a way to bypass the initial screen so I can use it in bootloader. Great, except now it's stuck on "Flashing..." and has been for half an hour. I really might throw this phone out the window.
5th and final edit: VipeRUU just would not work at all, so I had to go back to an older stock RUU, which sucks but at least my phone is working now Thanks for your help guys!
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
OK, no one is helping....ive tried some things, learned a few but this seems to be over my head....can anyone really help ? I managed to get past the white HTC screen by fastboot flashing a new recovery (philz then dees troy version of twrp)....I got a bootable commotio build....I also flashbooted 2.22.401.5, i thought it had fixed everything but in recovery i am getting the following errors.....
unable to mount /cache
failed to wipe dalvik
did I somehow mess up my partitions ? I need to wipe dalvik cache and cache in order to get a working rom on this damn phone.....
The issue has been fixed....
jxcorex28 said:
The issue has been fixed....
Click to expand...
Click to collapse
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
redpoint73 said:
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
Click to expand...
Click to collapse
Im not exactly sure what went wrong in the first place. I never pulled a logcat (from an app or through adp) since the problem no longer exists it looks like I never will unless I go through another similar thing. I wish I did know because it's killing me to know. I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
I have flashed atleast 500 times over a 8 year period on 4 different android phones, and Ive never once experienced the problem I had 2 days ago. Ive had 2 HTC phones, although, the experience with basebands were similar they were actually very different in every aspect. I had a TMO HTC G1 back in the day ( I had to learn how to do everything back when scripts or programs werent doing the grunt work (root)...
I had a TWRP backup of beanstalk saved (so kiddies, do your backups) that is what saved my ass. I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
I actually had to repartition my computer's hard-drive and reinstall windows 7 home edition, so I had to start over with practically everything...Im not going to use toolkits anymore. As you said earlier, it's just the easy way out. You wont learn anything about how to use ADB or Fastboot (although I applaud the one's who make the scripts or toolkits for those of us on the go).....
P.S.......If I can ever manage to break away from my dueling school schedule and my other priorities in life I plan on learning more about starting from the ground up and building roms, and not just throwing a few things together in the kitchen.....
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
jxcorex28 said:
I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
Click to expand...
Click to collapse
Yeah, I'm going to pull back on my previous statement that "3.28 will likely cause reception issues on AT&T's network" to instead say "may cause issues". And feel free to try it at your own discretion.
Reason being, I've seen maybe 3 reports now of this firmware working ok on AT&T, and no reports to the contrary so far.
Although, when folks tried the 2.22.401 "international" firmware on AT&T, there were several (even numerous reports) of signal issues, even NO SIGNAL. No reports of this so far on 3.28, so I'll be cautiously optimistic for the time being (until I see reports otherwise). Haven't personally tried it, and not sure I will as I don't really have time ATM to mess around with the possibility of signal issues or no signal.
jxcorex28 said:
I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
Click to expand...
Click to collapse
Did you try fastboot erase cache before trying to re-install recovery, or a different recovery? I've seen this simple step alleviate some pretty drastic issues with recovery.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
jxcorex28 said:
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
Click to expand...
Click to collapse
I can't speak personally, I'm not a Linux PC person. But my friends that are, seem to split among various distros: Ubuntu, Kubuntu, and Arch. One friend that is a particular Linux aficionado is on Arch, and said he was very happy with it.
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
jxcorex28 said:
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
Click to expand...
Click to collapse
Id highly rrecommend Linux Mint 17 Qiana MATE Edition .I use it with Windows 7. It is my favorite Linux OS. Not to mention that its perfect for Linux beginners.
That info would of been great a few days ago, but my laptop is screwed up now. Earlier I tried logging on,and couldn't because of some kind of remote error near the password field box on win7 HE...So I tried a system restore,and it failed so I f8 into recovery options and try using HP Recovery..everything went smooth into the first boot. I ended up getting a recovery installation incomplete and a 205 UIA failed 3 times. I believe my laptops recovery partition is corrupt,and I don't have a HP recovery disk, a win7 recovery DVD / Win7 recovery USB stick... I found what I need on HPs website, but its 30 bucks...BestBuy GS wants to charge me $69.99 for a diagnostics test and a retail version of win7 cost like 130
Its a 2011 HP Pavilion G-series laptop with windows 7 Home edition. What makes matters worse is I just partitioned the system a few weeks ago by using the recovery option HP makes for their devices...
Everything was great til about 10pm tonight...FML...now I actually gotta go to school to do my damn school work
jxcorex28 said:
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
Click to expand...
Click to collapse
I had that exact same issue yesterday... Twrp couldn't wipe anything and eventually kept rebooting after 20 or 30 sec in recovery.
I had to download the 1.58 RUU and run that, then flash Twrp back, reroot, then restore one of my backups from earlier in the day.
As far as fw goes, I had updated to 2.22.401.4, had that for a couple days, then updated to the 3.xx fw to install arhd 20.3. I liked it, but decided I love my dirty unicorns rom so decided to go back to the 2.xx fw. I tried to flash renovate 4.5.0, and that's when all the issues in twrp started. From what you're saying, it sounds like the issue could be caused from the fw updates.
How did you end up restoring your backup when they issue happened? I tried to restore mine with fastboot, but it was compressed and I couldn't extract the img files from the win files
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
jxcorex28 said:
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
Click to expand...
Click to collapse
I got it from skulldreamz thread on flashing fw by renaming it and putting it on root of ext SD card
Did you look into the contents of that zip to see if there was a recovery.img or boot.img file ? Those files usually overwrite the custom recovery (ie...TWRP or CWM). There are two ways to correct those red error messages you get in TWRP...
1. by flashing partition-fixer.zip (I have a copy if you need it)
2. By using a terminal emulator,and typing this command...
mke2fs /dev/block/mmcblk0p46
I believe this command is essentially what's included in the flashable partition fixer ( I haven't actually taken a look in that zip,so I could be wrong)...
I haven't had any problems as of late...either I'm starting to get back in the hang of dealing with HTC devices or I'm just lucky...
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
jxcorex28 said:
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
Click to expand...
Click to collapse
With the ones I got from skulldreamz' thread, I believe they were modified bc I didn't have to flash a custom recovery again after I flashed the fw. I never fastboot flashed them, I've always just renamed it 0P6BIMG.zip and put it on the root of the ext SD card
That's probably because skull removes those 2 files before uploading for download. I'm not sure if he does that for every zip....