Hi, I'm new to the HTC Evo 4G LTE, but I've been flashing roms through TWRP on multiple android devices and have had experience with it all. I've run into a problem though that I can't find a work around and have searched everywhere I know before posting here. I don't ever post so I can't post the URL link, but its the recommended guide through using HTC's unlocking method.
All seemed dandy till I got to the TWRP part. I flashed it over using the command prompt and the file. Then I selected Recovery. TWRP loads completely and everything looks like it works, except the touch screen. Obviously with this version of TWRP, touch is the only way to get the thing to function, so I'm stuck and can't flash superuser over. Can anyone help me out here?
Few Facts:
First time this phone has had the bootloader unlocked
When rebooting into the stock rom, the touch screen works just fine, so it isn't a hardware issue
I've taken the MicroSD card out so it is purely just the phone itself
Tried flashing over (seems older) clockworkmod recovery to see if it works, but I believe its outdated, considering this phone has 4.1.1 on it and the last update was back in August. It didn't work.
Any help would be much appreciated!
Did you try using volume buttons to move between the items, press home to select?
Sent from my lair.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
volk9029 said:
Did you try using volume buttons to move between the items, press home to select?
Sent from my lair.
Click to expand...
Click to collapse
Edit. You also did not mention what version of recovery you use. Did you try to downgrade to different version?
Sent from my lair.
Yes I tried using the volume buttons and they didn't work. The only thing that functions is the power button, but that locks TWRP, which is no use. For the versions, I tried the newest 2.4.0.0 and 2.1.8 and both had the same problem.
One thing to note also: I received the phone yesterday and while I was contemplating about rooting or not, I decided to update since it was still back at 4.0.4 ICS. Apparently, there was an update for the phone literally today, which I may have received since I'm not seeing the version of the RUU uploaded anywhere. My software version is 3.16.651.3 710RD.
Also, I'm on HBOOT 2.09 if that helps at all.
U flashed the new firmwear zip?
Sent from my EVO using Tapatalk 2
If you mean installed the new firmware via OTA, yes. After updating everything OTA, I started the rooting process.
I have same issue. Have stock/rooted/S-ON and have had no issues keeping root over the last few OTAs. The last OTA broke Voodoo Rootkeeper so I should have known this one was gonna be REALLY toxic. I rolled back to stock recovery to accept OTA and when I went to flash TWRP the touchscreen is non-responsive. TWRP is running because the clock progresses and the battery shows as charging. Power button, as OP describes, does nothing but lock TWRP. I know I take the risk of losing root with OTA acceptance but I depend on all you guys who are much smarter than I to figure those things out. Its why I try to lob donations at the most helpful devs out there...
Thanks in advance for figuring this out gents (and ladies?)...
~ScottWo
Wolosyks said:
I have same issue. Have stock/rooted/S-ON and have had no issues keeping root over the last few OTAs. The last OTA broke Voodoo Rootkeeper so I should have known this one was gonna be REALLY toxic. I rolled back to stock recovery to accept OTA and when I went to flash TWRP the touchscreen is non-responsive. TWRP is running because the clock progresses and the battery shows as charging. Power button, as OP describes, does nothing but lock TWRP. I know I take the risk of losing root with OTA acceptance but I depend on all you guys who are much smarter than I to figure those things out. Its why I try to lob donations at the most helpful devs out there...
Thanks in advance for figuring this out gents (and ladies?)...
~ScottWo
Click to expand...
Click to collapse
And THIS is why we recommend S-OFF to people, and tell people NEVER to take OTAs. At this point, I think you're stuck, unfortunately. You won't be able to access TWRP until someone figures out what the new touch panel image broke. You'll be able to use your ROM fine, but it seems this was something that was done intentionally by HTC to prevent custom firmware (or even software) from working properly.
I could be way off base, though, I guess . . . .
Inconceivable! HTC just pledged to continue supporting developers....wait they don't really support developers
Root
mr_krunchi said:
Hi, I'm new to the HTC Evo 4G LTE, but I've been flashing roms through TWRP on multiple android devices and have had experience with it all. I've run into a problem though that I can't find a work around and have searched everywhere I know before posting here. I don't ever post so I can't post the URL link, but its the recommended guide through using HTC's unlocking method.
All seemed dandy till I got to the TWRP part. I flashed it over using the command prompt and the file. Then I selected Recovery. TWRP loads completely and everything looks like it works, except the touch screen. Obviously with this version of TWRP, touch is the only way to get the thing to function, so I'm stuck and can't flash superuser over. Can anyone help me out here?
Few Facts:
First time this phone has had the bootloader unlocked
When rebooting into the stock rom, the touch screen works just fine, so it isn't a hardware issue
I've taken the MicroSD card out so it is purely just the phone itself
Tried flashing over (seems older) clockworkmod recovery to see if it works, but I believe its outdated, considering this phone has 4.1.1 on it and the last update was back in August. It didn't work.
Any help would be much appreciated!
Click to expand...
Click to collapse
Sorta the same problem, i dont flash roms but i like having my phone rooted. I had to redo the whole process because i lost my root access and i heard they were doing an update, so i did the 3.15 ruu and went back to complete stock, did the 3.16 update, unlocked the phone and it worked great up until i installed twrp 2.4.0.0, same problem touch screen not working. So i figured i would just run the 3.15 ruu again and just keep it there, unfortunately, the 3.16 version hboot which is 2.09 as well, will not let the 3.15 ruu run, says incompatible hboot, but it just restarts the phone, it did overwrite twrp somehow during the process of trying 3.15 the second time and removed it from the phone. From talking to some people, just have to wait until someone figures out how to fix that to get back up and running. I am pretty new to root but i like having those options to screw with the phone. Anxiously awaiting a fix though. Need to flash some roms soon, but never could get them to work, worked great on my Evo 4g...just not having the same luck with 4G LTE.
Same issue here
I never rooted my phone before and kept it updated up to the most recent 3.16.651.3 and it used to say "Locked" under Bootloader. I followed the instructions to the T from http://forum.xda-developers.com/showthread.php?t=2026938 with 2.09 Hboot files etc. All this and the problem I had is that when I got to the step where you load up TWRP, the touch screen didn't respond, nor did the volume rocker allow selection. Single pressing the power button, for some reason, showed "Slide to unlock" but I couldn't slide/unlock. Holding power still rebooted the phone.
Relocked and reloaded the original stock ROM, followed the procedure again, and it worked perfectly.
yeah I just got my phone back from RMA today ( parts of the screen were non responsive loose pin or something). when I sent it off I relocked it and Re S-ONed ( on H boot 1.19)it. as I read some places where they wont fix any hardware if the software has been S-OFFed.
when it came back it had the 3.16 stock firmware(Hboot 2.09) and now I cant S-OFF it ( dirty racoon gives errors about 3.16) cant downgrade it ( 3.15 RUU wont load) cant get roms on it( clockwork cant mount SD cards, and TWRP wont respond to touch)
needless to say I'm rather upset with HTC right now
Agreed
Totally agree, this kinda blows because if i could at least go back to 3.15 ruu it wouldn't be so bad, but i cant even do that. Hopefully someone way smarter at this will figure it out soon and get a fix going.
tonyevo52 said:
Totally agree, this kinda blows because if i could at least go back to 3.15 ruu it wouldn't be so bad, but i cant even do that. Hopefully someone way smarter at this will figure it out soon and get a fix going.
Click to expand...
Click to collapse
It's conceivably possible to change the main version on the /misc partition to match the previous OTA version (3.15.651.13), and then you should be able to flash the 3.15 RUU/PJ75IMG, since the HBOOT version didn't change.
But I'm S-OFF, so I don't have to worry about testing that theory.
I wish i was S-Off, i was rooted under 3.15 and everything was good, like a dumbass i updated my prl a couple weeks ago and totally forgot it would cause me to lose root, so i just never rerooted due to time, so when i saw the new 3.16 was out i figured i would relock, update, unlock and install twrp, worked good up to the twrp part where it would not respond to touch, and i tried to go back to the 3.15 ruu but wont let me. At least the phone still works, but a regular phone at this point and i just started rooting at the beginning of January so im still learing alot, actually don't mind screwing it up and learning from my mistakes, but my saving grace was always that i would go back to 3.15 if needed, not anymore, so now i will wait until someone figures it out, in the meantime though, learning alot more by reading on here. The only problem i seem to find is i understand most of the language here, but sometimes i see people trying to help people with step by step instructions and they miss a step or they explain it way technical and it puts people into panic mode, my eyes have glazed over a couple wonder what people are saying to do...but totally worth it and appreciate the help definitely.
Tony, updating your prl shouldn't take away your root.
Taking the ota could.
Sent from my EVO using xda app-developers app
I didn't even think about it taking away the root, but i lost root the same day i updated the prl a couple weeks ago. Never accepted any ota's while the phone was rooted, i just want root back...still learning though, fun messing with it!
Good news!
TWRP has been updated to version 2.4.1.0 that fixes the touchscreen issue in recovery. Please thank Dees_Troy for the fix at your earliest convenience .
Captain_Throwback said:
Good news!
TWRP has been updated to version 2.4.1.0 that fixes the touchscreen issue in recovery. Please thank Dees_Troy for the fix at your earliest convenience .
Click to expand...
Click to collapse
;
Link on the TWRP website is broken for the FastBoot version of 2.4.1.0 it takes you to an HTC page. The links goes to: htcDOTcom/www/help/htc-evo-3d/#download
Sorry, can't post URLs yet so I edited the link for viewing...
Anyone have a working link, or a way to advise the correct person of the misdirected link?
Thanks!!!!
sdax2 said:
;
Link on the TWRP website is broken for the FastBoot version of 2.4.1.0 it takes you to an HTC page. The links goes to: htcDOTcom/www/help/htc-evo-3d/#download
Sorry, can't post URLs yet so I edited the link for viewing...
Anyone have a working link, or a way to advise the correct person of the misdirected link?
Thanks!!!!
Click to expand...
Click to collapse
I don't know where you're looking, but this link is right there on the page:
http://techerrata.com/browse/twrp2/jewel
You seem to be looking at an EVO 3D version?
Captain_Throwback said:
I don't know where you're looking, but this link is right there on the page:
You seem to be looking at an EVO 3D version?
Click to expand...
Click to collapse
Victim of browsing because I've downloaded so many times before...
But in the "Download - Fastboot Method:" section there is a link that points to the drivers needed from HTC. Without reading carefully I just clicked on the link labeled HERE.
It does however point to an incorrect page for the HTC drivers. Sorry for the confusion, and thanks for the clarification Captain...
Related
I tried to flash a custom rom on my eris last night with unsuccessful results.
To begin, my phone had the newest 2.1 OTA update on it and is running HBOOT 1.47. I downloaded and ran the 1-click universal root app. I noticed that a few new apps showed up (Latitute), but the Superuser app did not. I re-ran it several times but it still wouldn't show up.
Getting ahead of myself, I decided that I probably *DID* root the phone and I flashed Kaosfroyo V29 through the recovery menu. As I rebooted, the phone hung at the loading screen. I then tried to flash the Cyanogen mod with the same results.
After looking around, it appeared that the HBOOT 1.47 was exploitable with the 1.5 PB00IMG.zip update. I loaded it to my sd card and booted the phone in quickboot. It recognized the image but did not give me the option to update.
So now I am left with a phone that won't boot and without a backup (I know, I know).
What are my options? Is it still rootable from the recovery menu? Should I take it back to verizon and see if they can reflash/replace it (Doubtful as I probably voided the warranty).
wolfpack10 said:
I tried to flash a custom rom on my eris last night with unsuccessful results.
To begin, my phone had the newest 2.1 OTA update on it and is running HBOOT 1.47. I downloaded and ran the 1-click universal root app. I noticed that a few new apps showed up (Latitute), but the Superuser app did not. I re-ran it several times but it still wouldn't show up.
Getting ahead of myself, I decided that I probably *DID* root the phone and I flashed Kaosfroyo V29 through the recovery menu. As I rebooted, the phone hung at the loading screen. I then tried to flash the Cyanogen mod with the same results.
After looking around, it appeared that the HBOOT 1.47 was exploitable with the 1.5 PB00IMG.zip update. I loaded it to my sd card and booted the phone in quickboot. It recognized the image but did not give me the option to update.
So now I am left with a phone that won't boot and without a backup (I know, I know).
What are my options? Is it still rootable from the recovery menu? Should I take it back to verizon and see if they can reflash/replace it (Doubtful as I probably voided the warranty).
Click to expand...
Click to collapse
Try installing the engineering Bootloader. Instructions can be found in a sticky called Eris roll-up in the Eris developement section. Even if you can't flash a custom Rom after this you can still flash the official 2.1 ruu which will put your phone back to 100% stock and you can try again.
If your rooted and can still boot to fastboot your not bricked.
Sent from my Eris using XDA App
If the bootloader still appears (power phone on with vol-down+end), your phone is not bricked.
If the recovery boot still appears (power phone on with vol-up+end), your phone is not bricked.
If you don't have a SD card reader on your PC, you can transfer a different ROM to your SD card by booting to recovery and using the USB-MS toggle.
Smart money says that all you failed to do when you installed the ROM was perform a wipe before you flashed the ROM.
Prove this to yourself by installing a conservative ROM such as PlainJane, and when you get it running, for Dog's sake, make an effing Nand backup.
bftb0
I know for a fact it isn't rooted though (It says S-UP on the Recovery Menu).
Can I actually install alternative bootloaders on an unrooted phone?
Also, I want to avoid flashing the official RUU because it updates the HBOOT to 1.49 which, to my knowledge, has not be exploited yet.
Do either of you know why the PB00img.zip didn't work? I read multiple places that it should work with my HBOOT version.
Also, why didn't the 1-click root work? I haven't done anything like this previously and I bought the phone new at version 1.5.
wolfpack10 said:
I know for a fact it isn't rooted though (It says S-UP on the Recovery Menu).
Can I actually install alternative bootloaders on an unrooted phone?
Also, I want to avoid flashing the official RUU because it updates the HBOOT to 1.49 which, to my knowledge, has not be exploited yet.
Do either of you know why the PB00img.zip didn't work? I read multiple places that it should work with my HBOOT version.
Also, why didn't the 1-click root work? I haven't done anything like this previously and I bought the phone new at version 1.5.
Click to expand...
Click to collapse
Do you still have ra recovery? If so simply boot to recovery, wipe data and cache and reflash the rom.
All the 1 click root does is flash the custom recovery, so it did work.
Fyi
The Eris can now be rooted no matter what Bootloader version you have so doing the ruu will not prevent you from rooting. I myself was a leaker and had no problem rooting with the 1.49 s-on Bootloader.
As stated by btfb0, ALWAYS wipe data and cache before flashing a new Rom. ALWAYS do or have a nand backup ready just in case.
Sent from my Eris using XDA App
wolfpack10 said:
I know for a fact it isn't rooted though (It says S-UP on the Recovery Menu).
Click to expand...
Click to collapse
If you see the text "S-OFF" at the top of the screen, that is the bootloader, not the recovery boot. The one-click rooting method does not touch the bootloader, so, after successfully using "one-click", you will still have the same bootloader (initially).
wolfpack10 said:
Can I actually install alternative bootloaders on an unrooted phone?
Click to expand...
Click to collapse
You can install the Root PB00IMG.ZIP file onto a 1.46.xxxx or 1.47.xxxx bootloader phone - but you don't need to, because your phone already has a custom recovery installed on it (Amon_RA). As I mentioned previously, you get to that recovery facility by one of two ways:
1) Power phone off. Press and hold Vol-Up and then End/Power; continue to hold both keys down until you see the three skating droids appear (Don't release the keys until you see that screen). A menu system should appear 10 seconds after that happens. It will say "Amon_RA" on the bottom of the screen.
2) Make sure there are no files named PB00IMG.ZIP in the root folder of the SD card; either that or eject the SD card. Power the phone off. Press and hold Vol-Down and then End/Power; continue to hold both keys down until you see the three skating droids appear (Don't release the keys until you see that screen). A menu will appear immediately. One of the items will indicate that if you press "Vol-Up", you will boot into recovery. Press Vol-Up, and wait 10 seconds. You should be at the Amon_RA menu. (At this point, you can re-insert the SD card if you previously ejected it).
If you can't get either of these things to work, report back with exactly what you observe - saying "it didn't work" might be correct, but it isn't very informative.
wolfpack10 said:
Also, I want to avoid flashing the official RUU because it updates the HBOOT to 1.49 which, to my knowledge, has not be exploited yet.
Click to expand...
Click to collapse
Not correct. Both the "one-click" and "Dummies" methods (see All Things Root forum over at AF) work for 1.47, 1.49.0000, and 1.49.2000 bootloaders.
wolfpack10 said:
Do either of you know why the PB00img.zip didn't work? I read multiple places that it should work with my HBOOT version.
Click to expand...
Click to collapse
The PB00IMG.ZIP files are not compatible with the Amon_RA "update"-style installs; they are signed using an entirely different method. Not compatible. That's why it didn't work when you tried it (using Amon_RA). They are installed by starting up the bootloader with the PB00IMG.ZIP file in the root folder of the SD card. I am recommending that until you understand things a little better, you avoid this method - it only works with certain combinations of bootloaders and PB00IMG.ZIP file versions.
wolfpack10 said:
Also, why didn't the 1-click root work? I haven't done anything like this previously and I bought the phone new at version 1.5.
Click to expand...
Click to collapse
It did work. You indicated in your first post that you used the Amon_RA recovery, which was installed by that method.
bftb0
Thanks for the detailed responses. I know I should have researched this stuff more before I started toying with it but I'll just have to pay the price.
I wiped and flashed KaosFroyo V29 from the recovery menu and it finally booted. Many thanks for that suggestion.
Hopefully this thread will be helpful for other people in the future.
In the mean time, I lost all my contacts so lesson learned.
wolfpack10 said:
Thanks for the detailed responses. I know I should have researched this stuff more before I started toying with it but I'll just have to pay the price.
I wiped and flashed KaosFroyo V29 from the recovery menu and it finally booted. Many thanks for that suggestion.
Hopefully this thread will be helpful for other people in the future.
In the mean time, I lost all my contacts so lesson learned.
Click to expand...
Click to collapse
Contacts should have been backed up through google. Although I have leaked and rooted some friends phone and their contacts never sync'd to their phones.
Sent from my Eris using XDA App
wolfpack10 said:
Thanks for the detailed responses. I know I should have researched this stuff more before I started toying with it but I'll just have to pay the price.
I wiped and flashed KaosFroyo V29 from the recovery menu and it finally booted. Many thanks for that suggestion.
Hopefully this thread will be helpful for other people in the future.
In the mean time, I lost all my contacts so lesson learned.
Click to expand...
Click to collapse
Glad you got it working.
If you were using Gmail instead of the HTC mail app for managing your contacts, all your contacts are still "in the cloud" (so long as you did not define them to be "phone only" when you added them).
If they were phone-only contacts, it would have been a simple matter to get your contacts back if you had made an initial Nandroid backup. I'm not saying that to add insult to injury, but rather (as you said) "Hopefully this thread will be helpful for other people in the future."
Backups are a really good thing.
BTW - You will find that Android Forums is a useful adjunct to this forum. The reason is that the ROM devs over here on XDA have their hands full trying to do both development work and interact with the users/testers reporting issues with their ROMs, so they don't spend much time in here (Q&A or General sub-forums). When they do announce a new hack, or patch, or rooting method, the descriptions are many times written tersely (for subject-matter experts, not newbs). There are a number of very helpful folks over on AF, and some good "sticky" posts that are quite a bit more detailed than what you will find here. I'm not ragging on XDA at all; just saying that by nature of the focus required for development work, the experts can't give much personal attention to individual users, even if they want to.
bftb0
How do you root the Thunderbolt after the 7/8/11 OTA?
Rooting using the old method doesn't work anymore?
flooritnfly said:
How do you root the Thunderbolt after the 7/8/11 OTA?
Click to expand...
Click to collapse
you would use the same process as before.
lostnuke said:
you would use the same process as before.
Click to expand...
Click to collapse
Yeah, use the same method. After your rooted, flash the rooted OTA stock Rom (google it) and also flash the its radio. That's what I did.
Sent from my rooted stock OTA MR2 Thunderbolt
So.... I can use this (http://forum.androidcentral.com/thu...unroot-windows-updated-5-20-w-mr1-update.html) like I did before then just flash the new radio that was released on 7/8 ?
Well now after 7/8, you have to flash while standing on your head. Yeah, its crazy like that.
bthomp21 said:
Well now after 7/8, you have to flash while standing on your head. Yeah, its crazy like that.
Click to expand...
Click to collapse
That is too funny.
I am unable to install the 7/8 Combo Radio package after installing DasBAMF Stripped 1.8.6
Constantly says "Installation Aborted."
Anyone else with this experience? I thought that I had read that this combo worked.
Got this sorted. I was using an MR1 package, not MR2, apparently. Using a different packaging of the OTA update flashed in via HBOOT.
BoulderGeek said:
I am unable to install the 7/8 Combo Radio package after installing DasBAMF Stripped 1.8.6
Constantly says "Installation Aborted."
Anyone else with this experience? I thought that I had read that this combo worked.
Click to expand...
Click to collapse
Your flashing it through the bootloader right? You can't use clockwork to flash it.
Sent from my rooted stock OTA MR2 Thunderbolt
Thunderbolt/Android Noob
OK .. I have this HTC Thunderbolt .. I want to root it .. I have read the forums up and down ... I saw the link above to AndroidCentral that shows how to root it, and one over in the Thunderbolt Development forum that says MR1 Perma Root ...
I would like to know the best route for me to go with minimal risk of bricking. I have flashed my wife's LG Ally a couple of times .. was easy enough, just ran an exe
All of the ones I have found for the thunderbolt seem to be a lot more complex. Is there a OneClick method I can run that will include the new radio (so i can get the latest fixes)?
If not, I am willing to go the ADB route (I have the Android SDK installed) but I dont know how to update the radio.
Thanks, and sorry to ask a question that seems to have already been answered, I am only asking b/c I did not understand your answers above ..
Use adb to root. Radio is done through hboot. Power off phone. Then hold vol key down and power on. Will bring you to hboot. Make sure radio is at root of SD card and is named properly. There is a sticky in the DEV section that will walk you through it.
courtesy of my rooted bolt
I just used the XDA development one. The key point is to read it carefully several times and be sure you understand each step. Ask questions beforehand if you are not sure about something. And be sure to follow each step exactly. Typos are the biggest risk, so go slow and read what you've typed on each line before hitting enter.
The radio file needs to be renamed to PG051IMG.zip and placed on the root of the SD card. Then power off and boot into bootloader. It'll load automatically after you hit +volume to confirm "yes ".
I had several flashes that resulted in the Exclamation Point warning triangle. Pulling the battery and USB cable and reinstalling power got me back to a running build.
It took me a while to do every step. I wanted to skip steps, not realizing that you needed the downgrade and RUU flashes to get S-OFF and unlock.
Once that was all done, I went to DasBAMF Stripped and found the OTA radio in this thread http://forum.xda-developers.com/showthread.php?t=1160346.
So far, so good. Calibrating battery now and trying to personalize and optimize to my best ability.
Ok so from what I gather there are no issues that would prevent any of the previous methods from working post 7/8 update? That includes the one click app thats been floating around for a few months right?
I've been holding off root for months, but my patience has finally run out, time to do what I should have done from the beginning.
EDIT
on second thought, I think I'll just do it the good old fashioned way
I did the 7/8 update, and was fine with it. I just wanted to get the Verizon bloatware off. I had problems installing the stock debloated ROMs, so i ran with BAMF to test, and since it worked, I kept it. My rooting came after the recent OTA.
The once-click and .bat methods didn't work so well for me, so I followed the full instructions in a CMD window (I can't call that POS in DOS a shell).
Most of my time was installing a correct Java JDK (had to use x86 instead of x64) and getting ADB dialled in.
KO'B said:
Ok so from what I gather there are no issues that would prevent any of the previous methods from working post 7/8 update? That includes the one click app thats been floating around for a few months right?
I've been holding off root for months, but my patience has finally run out, time to do what I should have done from the beginning.
EDIT
on second thought, I think I'll just do it the good old fashioned way
Click to expand...
Click to collapse
I had the same thinking and wanted it the quick and easy way. Doing the research and taking the time (and beers ) to do it manually was very informative and satisfying when i got done. It was said already but ive been able to apply any feature that an official OTA would give long before its normally released to verizon customers. I love my Tbolt and wouldnt have it any other way.
BryanB32 said:
I had the same thinking and wanted it the quick and easy way. Doing the research and taking the time (and beers ) to do it manually was very informative and satisfying when i got done. It was said already but ive been able to apply any feature that an official OTA would give long before its normally released to verizon customers. I love my Tbolt and wouldnt have it any other way.
Click to expand...
Click to collapse
Doing things the long way has never really scared me, but some of the horror stories I kept hearing a month or two back about instability of GB roms had me a bit hesitant to go for it.
It does appear to be a bit more involved than what I am accustomed to, but I have used ADB before, I was just trying not to this time.
Can someone give me a bit of advice actually.
I'm on the end of Step 4 found in the Developement section, and when I hit Bootloader, it brings up a second menu not mentioned in the posts, what do i do from here?
Nevermind once again, screwed up the name of the zip file
I used the auto root method 3 times so far and worked great. I did the full last update and lost root so I had to redo it load Rom and just added the radio file in hboot.
try auto root its fast and simple just follow the commands on the screen!
NOTE: I'M NOT REALLY GOOD AT THIS. I'M A REALLY GOOD STEP BY STEP-FOLLOW INSTRUCTION-GUY.
I'm a moderate phone user. One day I was trying to get rid of the carrier IQ, I rooted and unlocked my phone and successfully get rid of them.
Then somehow, I realized there was a software update which would update me from 1.27.531.8 to 1.27.531.11.
So I did an OTA and found out that I need a stock recovery to be able to get that OTA.
Before I found mugetsu666's post that includes the stock ROM, recovery, and kernel, I found Behold_this's post firmware packages.
So I flashed it with the newest OFFICIAL FIRMWARE PACKAGE by using "fastboot oem rebootRUU, fastboot flash zip firmware.zip"
After that, I noticed my wireless is gone/broken. And the software number remains the same which it didn't really update.
So I tried his(Behold_this) other stock custom firmware package by doing the same command but the other file trying to go back to the way it should.
Wireless is back this time, so I did an OTA. OTA stuck at the recovery screen and I press Power+Volume UP and get his message that it is doing Bug Fix. My phone just hang there for a good 30 mins and realizing it doesn't really bug fix anything.
So I found the other guy asking the same question on Behold_this's post, Behond_this stated that if the phones was rooted or unlocked, the OTA would not work.
So I relocked it, unrooted it, tried it again. The problem remains. Then I thought I have to "Lock it" instead of "relock" So I S-OFF by using revone and get that tampered down and also locked it.
Again, I unrooted it, locked it, the problem remains the same.
After that, I decided to give the mugetsu666's pure stock rom a try. I did a factory reset in TWRP (I already unlocked it again and flash a recovery), and flash mugetsu666's stock ROM and locked it and unrooted it again. OTA would not work still.
SO....... I decided to give a combination of both a try! I flash the stock rom, kernel, and stock recovery from mugetsu666's post and install the official1.27.531.11 firmware package from Behold_this. The problem remains....
Okay.. So What I was trying to do originally was to go back to an average user and use the convenient OTA when it's available. NOW!!! It's like a thing in my head that I must solve!!! It is driving me crazy now............ I spent more then 10 hours non-stop to just try to fix this thing...
I could probably return it to the carrier and get a new one since I just bought this about 3 days ago. But I already have the full body tech skin on the phone already. It took really long and some money to do it... Didn't want to just return the phone and get a new one.
If any of you can help me with this problem, I sincerely appreciate it!!!
Please help me!
Thanks everyone for the help in advance!
I'm having the exact same issue. Keep me posted on if you fix it.
Sent from my HTC One using Tapatalk 4 Beta
Have you tried the posted RUU on HTC's site?
https://support.htc.com/en-us/030-H..._Maintenance_Release_Instructions_|_7.23.2013
RUU is at the bottom of page. Refer to the Manual system update instructions.
gustav30 said:
Have you tried the posted RUU on HTC's site?
RUU is at the bottom of page. Refer to the Manual system update instructions.
Click to expand...
Click to collapse
Just about 10 mins ago. I tried it. The RUU file is somehow corrupt. I downloaded it several times and it didn't work.. People are having the same issue as well. Thanks though!
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
jaawerth said:
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
Click to expand...
Click to collapse
Exact same thing happened to me last evening...except I'm rooted with S-off.
grimmkt said:
Exact same thing happened to me last evening...except I'm rooted with S-off.
Click to expand...
Click to collapse
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
jaawerth said:
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
Click to expand...
Click to collapse
Sounds good! let us know!:good:
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
I can't get the phone to connect in fastboot. I keep getting a "driver failed to load" type error when I plug in the USB...the device is never visible.
Worked like a charm! The download took awhile, but once I had it downloaded it was easy.
For others searching for this issue:
Once you have the RUU, just install Android Development tools (specifically fastboot) and enter
>fastboot oem rebootRUU
>fastboot flash install IMAGEFILE.ZIP
Terminal/command prompt on the computer side told me it was finished but the phone was stuck at the very end of the progress bar. I waited a while few minutes, and when it didn't move I risked doing a
>fastboot reboot
and we were good to go.
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
jaawerth said:
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
Click to expand...
Click to collapse
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
jaawerth said:
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
Click to expand...
Click to collapse
It's a known hardware issue in the DNA. When they give you a new Sim tray it's thicker and it holds the Sim card in place better resulting with no more errors.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Hey friends, I am very new to the rooting scene. I have a at&t htc m8 and i made the mistake of trying to root the fast and easy way. I followed a guide by a user names Unlocker. I would post the link but am unable to at this current time because i am new here
That has it's readers use hasoon2000's all in one toolkit. Well I think I screwed up in that process. when my phone was off and charging , the screen would briefly flash the TWRP ui with their lock screen. So naturally I freaked out tried my best to unroot the damn thing by following a guide created by the same guy after he got many complaints of issues
Naturally I had problems with this aswell. Now where i'm at, at this current moment is
**tampered** ***unlocked**
I successfully (i think) removed super su and did my best to get back to stock firmware. well I failed at that aswell. I still have TWRP on my phone and managed to get security turned back on.
What I am asking is for any references or maybe even some fresh help on how i can either get my phone back to stock firmware so i can take the OTA updates and be on my merry way or maybe reccomend a custom rom I can use that has the new lolipop software.
Now i was looking to update my TWRP but I am unable to locate an AT&T verison. I see sprint , verizon, and GSM. I feel pretty helpless right now but if i can get some instruction I know I will be able to figure this out.
I'm still really new to this also, but I'll try my best (just take everything I say w/ a grain of salt...):
Krob189 said:
... when my phone was off and charging , the screen would briefly flash the TWRP ui with their lock screen. ...
Click to expand...
Click to collapse
Do you mean that you'd successfully done whatever you were doing and this was happening in normal use? AFAIK it is normal for the the screen to power off during long-running TWRP actions, and power button wakes it up.
Krob189 said:
...
I successfully (i think) removed super su and did my best to get back to stock firmware. well I failed at that aswell. I still have TWRP on my phone and managed to get security turned back on.
Click to expand...
Click to collapse
Which firmware do you have on it now? Do you have ADB installed? If so, it might be helpful if you post the output of the command
Code:
fastboot getvar all
. If not, I think you'll need ADB and fastboot to help recover.
Krob189 said:
...Now i was looking to update my TWRP but I am unable to locate an AT&T verison. I see sprint , verizon, and GSM ...
Click to expand...
Click to collapse
AT&T uses GSM. The GSM version should be correct. Depending on the firmware you have installed, specific versions of twrp may not work. In my case, twrp 2.8.4.0 wouldn't work on AT&T's stock 4.4.2 firmware, but would on the 4.4.4 firmware.
EDIT: Did you make a TWRP backup before attempting these changes? Depending on the state of your firmware, restoring that might be enough to fix things.
AT&T Stock 4.4.4 RUU
This should solve your problem, if you can achieve s-off again:
AT&T Stock 4.4.4 RUU
Krob189 said:
That has it's readers use hasoon2000's all in one toolkit. Well I think I screwed up in that process. when my phone was off and charging , the screen would briefly flash the TWRP ui with their lock screen. So naturally I freaked out tried my best to unroot the damn thing by following a guide created by the same guy after he got many complaints of issues
Click to expand...
Click to collapse
All the panic is for nothing. Its normal for the TWRP screen to appear for a brief moment when the device is powered off, and you connect the charger. At least on older versions of TWPR (and the version installed by Hasoon's toolkit is quite old).
Krob189 said:
Now i was looking to update my TWRP but I am unable to locate an AT&T verison. I see sprint , verizon, and GSM. I feel pretty helpless right now but if i can get some instruction I know I will be able to figure this out.
Click to expand...
Click to collapse
The TWRP version you want is the GSM. All versions of the M8 are essentially the same (and considered "GSM") except for the CDMA (Sprint & Verizon) and dual SIM variants.
---------- Post added at 12:47 PM ---------- Previous post was at 12:46 PM ----------
brasticstack said:
Do you mean that you'd successfully done whatever you were doing and this was happening in normal use? AFAIK it is normal for the the screen to power off during long-running TWRP actions, and power button wakes it up.
Click to expand...
Click to collapse
What the OP is describing was a known bug, and happened when outside of recovery and while the phone was powered off (and while connecting the charger).
Wow thank you for fast responses!
So from my understanding I have a outdated TWRP version. I suppose I need to read up on how to update this and also how to flash a new rom. I only rooted my phone so I could pair up my ps3 controller to my phone so I can play games on it. I regret doing it now to be honest because I have modded my 3ds to play the same games i was using on my phone
I would love to be on the lolipop update that launched yesterday I believe. Should I stick to a rooted rom or just flash a stock version? Can anyone recommend a good lolipop root that has some tweaks for battery life and overall performance?
Krob189 said:
So from my understanding I have a outdated TWRP version. I suppose I need to read up on how to update this and also how to flash a new rom.
Click to expand...
Click to collapse
Just get the latest version of TWRP from their website. As you are asking what version (CDMA vs. GSM) it sounds like you are already getting there.
It sounds like you have the version of TWRP that was installed by the toolkit. That version is many months old. But its a minor bug, anyway. How often do you charge the phone with it powered off, anyway. I also don't think you can do anything in TWRP in this condition (if a security risk is your concern). The TWRP appears for a split second, and that's it.
Krob189 said:
I would love to be on the lolipop update that launched yesterday I believe. Should I stick to a rooted rom or just flash a stock version? Can anyone recommend a good lolipop root that has some tweaks for battery life and overall performance?
Click to expand...
Click to collapse
Lollipop didn't launch for AT&T, its just a long-delayed 4.4.4 update for us. To update to 4.4.4, either return to stock ROM and stock recovery to get the OTA, or relock the bootloader and run the official RUU.
Lollipop (5.0) started to roll out for some Euro CIDs, and has been out for US Dev Edition for a while. But you can't get to Sense Lollipop unless you s-off (or until AT&T releases it).