Related
Just wanted to get this out there. I have been trying to root all night with no luck. Hoping others with same issue will come for an offer help. Free evo accessory for anyone that can get this solved for me.
You need to provide a few more details what you've done to try and achieve root. What method did you try? What are seeing on the screen at the various steps.
I used the long method listed Here. If you're using the .exe file in the other thread, its not as reliable.
I am having the sane issue. I have tried regaw's method, the manual method listed in the hboot S-off thread, and the automated method in the other hboot thread. Everything works except flashing pc36img.zip....it throws the error he mentioned when updating radio v2, plus it throws fail-ic when trying to update bootloader (it does not say "bootloader skipped" as indicated it should in the guide). From this point forward, it will not boot past white HTC splash w/o running ruu. You can even do the rest of the guide and get a custom recovery flashed (i have done both amon-ra, and clockwork). After running ruu, S-off sticks (meaning unrevoked worked, I suppose), but you obviously don't have root. If you try to flash a custom Rom, even just a rooted version of the ruu, it throws a symlink error (something like E:fail can't symlink bin/lsmod....can't remember exact syntax, I posted it in another thread though, I'll see if u can find it). I have tried doing this from custom recovery and from toast's pc-based recovery. Is there a way for me to pull a log of what is happening when the pc36img has its errors? That may be the only way for me to give you more info than I have.
funnyrocket said:
Just wanted to get this out there. I have been trying to root all night with no luck. Hoping others with same issue will come for an offer help. Free evo accessory for anyone that can get this solved for me.
Click to expand...
Click to collapse
Look at this guys thread and also ask them to move your thread to the right forum so you can get the proper views and help
http://forum.xda-developers.com/showthread.php?t=831915
i followed the manual method, it failed with the radio pu, i completed the method, my phone would not boot it was stuck at the "htc evo" screen. So after some research I found the correct file to make my phone boot, The manual steps worked and i rotted my phone but i am unable to put a custom rom on
dl this file rename it pc36img and push it to you phone and reboot in the hboot and let it install it should pass you will have root access and clockworks custom recovery but until someone fixes the roms or gives a answer they wont work they will fail but you will have a phone and root admin.
http://forum.xda-developers.com/showthread.php?t=791019
flipper12 said:
You need to provide a few more details what you've done to try and achieve root. What method did you try? What are seeing on the screen at the various steps.
Click to expand...
Click to collapse
I used Method 3 from this zikronix's [TOOL][GUIDE] HBoot 2.02 S-OFF thread. Everything works great until I have to flash PC36IMG. It starts but gives the Radio-V2 Fail-PU and Bootloader-Fail-IC. The screen shows updated failed. Upon restart I'm at the red triangle boot screen. Can't do anything else from there.
kc_sheets said:
i followed the manual method, it failed with the radio pu, i completed the method, my phone would not boot it was stuck at the "htc evo" screen. So after some research I found the correct file to make my phone boot, The manual steps worked and i rotted my phone but i am unable to put a custom rom on
dl this file rename it pc36img and push it to you phone and reboot in the hboot and let it install it should pass you will have root access and clockworks custom recovery but until someone fixes the roms or gives a answer they wont work they will fail but you will have a phone and root admin.
I don't see what this will do for me since I don't have S-Off status yet. I can't get that far. Plus, this isn't a comeplete root. I have another Evo here that has the exact same specs, right down to Hardware 003 and I just did the Method 3 root and it went through with flying colors. So...
Click to expand...
Click to collapse
I think it is the bad blocks issue popping up again. I read about it in toast's root thread, I believe. If I am right, toast figured out a fix before. We may have to find a way to use his fix again. It was for a different bootloader, though. Might not work straight out of the box. I'm no dev, but this seems to me to be what is happening.
tejasrichard, i didnt know you got an Evo.
Come see us in #HTC-EVO on irc.freenode.net
Alot of devs hang out in irc so you guys might be able to get help there.
Use clockwork.
For some reason, amon ra doesn't work right away. You'll get fail-pu with it.
OtisFeelgood said:
tejasrichard, i didnt know you got an Evo.
Come see us in #HTC-EVO on irc.freenode.net
Alot of devs hang out in irc so you guys might be able to get help there.
Click to expand...
Click to collapse
Sup Otis! Yeah, I finally got my upgrade, lol! I'm a little late to the party, but better late than never, right? I'll stop by tomorrow and say hi (promised the missus some quality time tonight). I've got a few more things I want to try, but I'm betting whatever toast did b4 to get around the bad blocks will work again. Need to pm him and see what he thinks.
Hi guys, I'm confused.
I have a stock HTC Desire on Orange with 2.10.405.2. I've been having problems with the radio (losing data connectivity but not showing it, text messages being delayed for hours, etc) and decided to root it with Unrevoked and put a new radio and RIL pack on. Well, I did that OK (although the connectivity problems persist).
The trouble is that now there's an OTA update to 2.29.405.2, which I would quite like to try out. When I tried to run it, Clockwork Recovery gave a signature check error.
Could someone explain how to fix this? I don't mind losing root, but I would very much prefer to run an update rather than flash a rom and lose everything on the phone! A clear description of what's going on would be appreciated, cheers!
I'm pretty sure, running the OTA would brick your phone,thats why it wont go through, what you need to do it, flash an Stock rom on your phone, then do OTA
Read the Wiki or Ask in the Desire forum for more help
Oh my, this reply came in just after I had managed to start an update (by moving/renaming the update file to update.zip in the root directory and using clockwork recovery). And as I read the update, the phone had been on the HTC splash screen for quite some time...
I almost had a heart attack.
But it's booted now The update failed due to not having enough free memory.
I suppose I'll just have to back up what I can and flash the stock rom. It's really annoying that rooting the phone in order to give me more flexibility has taken away the option to update painlessly.... That is, unless someone can point me towards a rooted update file?
Oh, the radio I updated to was Radio Froyo 5.11.05.27 (I flashed the RIL zip file separately), I am not sure how much that could affect things.
too bad that my phone had enough memory and now I'm trying to flash a stock rom.
The 1st one I tried was 2.09, and it failed saying kind of "invalid ruu version".
Now downloading 2.29.....
After installing unrevoked I am now having a problem with updates. It will start the update, the progress bar makes it about halfway thru, then the phone just locks and a soft reset to follow. I'm new to android, the phone is an EVO, and the only thing that has been done thus far is running unrevoked for the wireless tether. Please help out a noob.
From what I understand the update looks for the stock recovery image. Because your rooted via unrEVOked, your device has a custom recovery (ClockworkMod) installed. You have several options if you wanna do a little research but if your simply looking for an easy answer to your question I would recommend getting a copy of the latest RUU (ROM Update Utility) which will restore your EVO back to a factory fresh state and will allow you to install the update. You will loose root though so be warned. Look around in the EVO developement forum and grab the latest RUU, save to pc, connect your device via USB, run RUU and follow the prompts. Another option would be to find a ROM based off the lastest update. There really not hard to install and this is the perfect time to start learning the ins and outs of Android. If anything should go wrong you always have the RUU to fall back on. Here is the 3.70.651.1 RUU. NO need to manually check for the update, this will leave you with a clean install of the latest software. http://forum.xda-developers.com/showpost.php?p=9836069&postcount=67
Thanks for the info. I actually just moved off of an HD2, so its all greek to me, just not that familiar with it. But again, thanks for the useful info, will get on that right away.
I had the same issue ... Ended up flashing 2.1, OTA update, OTA update and then flashed superuser ... Of course I started out with unrevoked forever ...
If I'm correct the latest version of unrEVOked does the same thing as unrEVOked forever, I say this because I used unrEVOked 3 and after updating my device is still S-OFF but when I download the superuser app from the market I get errors when trying to install clockwork recovery via Rom manager. setCPU is also telling me I'm not rooted. Any advice?
http://unrevoked.com/rootwiki/doku.php/public/forever
Go down to the section that talks about reinstalling an official recovery ...
Thanks so much. Very simple yet so many people are looking for that exact solution. You saved me a ton of searching, thanks again.
I have an HTC One M8 from T-Mobile
S-ON and UNLOCKED
I was just wondering how to get to a point where my phone wont brick on me, soft brick or hard brick.
I have the Insertcoin mod, 3.0.6 and it keeps prompting for an update on 3.0.7. When I click download and install it, it says "installation aborted" and then it exits me out.
I tried Googling the issue, but someone said that they did it manually and it actually soft bricked their phone and they got stuck in a bootloop.
I don't want that to happen to me because I've been dealing with my friend's HTC One M7 for the last few weeks where he was doing a normal HTC Update to 4.4 and his phone got soft bricked, stuck in bootloop. Tried factory reset, flashing RUU, wiping dalvic cache, and normal cache. Put it in fastboot and tried flashing it, nothing worked.
I'm thinking the reason is because it's S-ON and LOCKED. It got to a point where I just don't know what to do with it, so I kind of gave up.
But what's a good way of getting out of soft brick if you do get stuck in it?
I figured it should be easier than this, but this is really difficult.
-Thanks
Those 2 cases are completely different from each other (OTA install on a stock M7 versus updating a custom ROM on a M8); so I would not lump the 2 together.
IMO, best way to get out of a brick is to practice some good sense preparation:
1) Achieve S-off before you try to flash the new ROM. This will give you a lot more recovery options if things go south.
2) Make sure adb and fastboot is working properly with your device
3) Make sure TWRP is up to date, and check if the latest version has any known issues of bugs
4) Make a nandroid, and keep it on the internal memory. Copy it to your computer to be safe. This is really important; and one of the easiest and most reliable way to get back up and running if you run into trouble (or simply don't like the new ROM and want to revert). Yet, a lot of folks flash ROM without making a nandroid backup. I have no idea why.
5) Have a known good ROM handy (such as InsertCoin 3.0.7 which you say has been working "perfect" for you) on your PC or possibly even on the phone's internal memory
"How to get out of a bootloop" depends on what is causing it, what errors your are getting, etc.. There isn't a silver bullet solution. I would normally say RUU is that silver bullet; but you have found that is not the case. In general, you were on the right track with your friends M7 (which I won't comment on, since I never owned that phone). But a few guidelines are given below. Its listed sequentially for the most part, meaning if a particular solution fails, proceed to the next one.
1) A "dirty flash" (wipe only Dalvik and cache, keep user data) is often possible when updating within a particular custom ROM. But check the InsertCoin thread to see what the dev recommends, or how this went for other user on 3.0.8. If a bootloop occurs, or any other random bugs, do a factory reset in TWRP (wipe user data, Dalvik and cache) and flash again.
2) Try to download the ROM again, if you're bootlooping maybe the download was corrupt. Check the MD5, if available
3) Boot into TWRP and restore your nandroid
4) Try to flash a known good ROM, or another ROM.
5) Use fastboot to wipe cache and flash recovery again. Try again to flash a known good ROM or nandroid
6) All else fails, run the RUU (requires you to relock bootloader if S-on)
7) Whatever you do, do not do a factory reset in bootloader (only within the OS Settings itself, or TWRP). There is a known bug where factory reset in bootloader on a modded phone will corrupt the phone's internal memory (including loss of nandroid and ROM zips on the memory).
Thanks!
I'll take a look at all of it.
And a nandroid backup is when you use your custom recovery to make a backup right? If so I already did that for my M8
I have S-ON for my M8, how do I get it off? And is it worth getting it off? I haven't had any problems with access or ROMS yet with it being on.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
technocrat7 said:
And a nandroid backup is when you use your custom recovery to make a backup right? If so I already did that for my M8
Click to expand...
Click to collapse
Yes, nandroid is just a generic term for TWRP or CWM backup. You'd be amazed at home many folks flash mods to their phones without making one. You're already a cut above those folks!
technocrat7 said:
I have S-ON for my M8, how do I get it off? And is it worth getting it off? I haven't had any problems with access or ROMS yet with it being on.
Click to expand...
Click to collapse
Firewater S-off: http://forum.xda-developers.com/showthread.php?t=2708464
I already told you why S-off is important in my previous response; so I don't know why you are asking "is it worth getting?"
S-off can be important for recovery as it lets you run previous ("downgrade") RUUs (perhaps not as relevant this early, as most M8 versions only have one RUU version, or none at all) and RUUs for other carrier versions (may need to change CID also).
S-off also eliminates the requirement to relock the bootloader to run RUUs. So this saves you the extra steps of relocking to run the RUU, then unlocking again. Plus, you save yourself from the position of being relocked and in a bootloop (if RUU fails), which is a bit complicated and scary situation.
Further (aside from recovery options), S-off also permits you to flash different radios, mod hboot, update firmware packages, and other things not normally permitted with S-on.
The only downside to S-off, is that it bypasses all security and safety checks. For the most part while modding, this is a good thing. But you just have to be extra careful you only flash mods meant for the M8. Since device check is bypassed with S-off, its possible to flash a mod meant for another device and damage your M8 (such as different partitioning, damage partition table, etc.). But as long as you only flash things in the M8 forum, you will be safe.
So S-off has lots of upsides, very few downsides. Of course, its up to you whether to do it or not. But to me, the choice is pretty clear.
Thanks! I'll work on getting S-OFF on my device.
Also if you do screw it up and damage your M8, can you run the nandroid backup and get to where you were or no?
Sent from my HTC One_M8 using XDA Free mobile app
technocrat7 said:
Thanks! I'll work on getting S-OFF on my device.
Also if you do screw it up and damage your M8, can you run the nandroid backup and get to where you were or no?
Click to expand...
Click to collapse
Are you talking specifically about the firewater s-off process? If so, then no, a nandroid will not reverse this. But there isn't much to "screw up". Its a very easy process, and I wouldn't worry too much about it.
Alright thanks! I'll do that and then report back later!
Sent from my HTC One_M8
I ran firewater, it says:
Whelp, this sucks, firewater cannot work on your device. No amount of refreshing, retrying, or ruuing will fix this...
Sorry it didn't work out
Okay so I found out the real issue, and for those who saw my other post, the reason it said it could not be completed is because after I launch "adb shell"
I type "su"
And nothing happens. It's supposed to prompt me for my SuperSU permission but it doesn't.
SuperSU is not listed as a device manager under my security too. And in the shell it shows a # and I've granted other applications permission before so I know I'm rooted. Any help?
I'm running InsertCoin if it matters.
Have u tried the new other s-off methods? They do cost around 20 bucks I thinm
Sent from my HTC One_M8
technocrat7 said:
Okay so I found out the real issue, and for those who saw my other post, the reason it said it could not be completed is because after I launch "adb shell"
I type "su"
And nothing happens. It's supposed to prompt me for my SuperSU permission but it doesn't.
SuperSU is not listed as a device manager under my security too. And in the shell it shows a # and I've granted other applications permission before so I know I'm rooted. Any help?
I'm running InsertCoin if it matters.
Click to expand...
Click to collapse
If it doesn't prompt you for su access and doesn't seem to do anything when running firewater it's probably because the rom is not "stock" enough. Running Maximus or other near stock roms is more likely to succeed. But anyway if you previously got the whelp message in firewater I suppose you're like many of us out of luck using that since it seems HTC has closed the exploit that firewater used on some phones.
So as MotoTurbo said, you'll probably need to use Sunshine (http://theroot.ninja) rather than Firewater. It's made by the same devs, but works on all M8's (even the ones that got whelped in Firewater). It does cost $25 but it was really simple to use and worked perfect on my phone. The newest version even seem to root your phone if it's not rooted already and then s-off's your phone after it has made sure it will work on your phone and paying using Paypal or creditcard from within the app...
The close to stock requirement also seem valid for Sunshine, but you can always try from your current rom since it won't allow you to pay until it's sure it can s-off your phone.
Ah I see.
Thank you. It sucks I'm out of luck but I think it's worth the $20. I am pretty sure I plan on keeping the phone around long enough.
One more question. The newest update for InsertCoin, or even some xposed modules are falling to work. It says "installation aborted" after not being able to extract to some directory or find it or something.
But I was installing updates fine a week ago. It's just the newest one giving me trouble. Someone said I have to go to the website manually and just put it in my SD card and zip install it through recovery.
I don't want to screw things up because I heard someone got stuck in a bootloop by doing this.
technocrat7 said:
I ran firewater, it says:
Whelp, this sucks, firewater cannot work on your device. No amount of refreshing, retrying, or ruuing will fix this...
Sorry it didn't work out
Click to expand...
Click to collapse
Later hboots don't work with firewater. What hboot version is your device on?
---------- Post added at 09:37 AM ---------- Previous post was at 09:30 AM ----------
technocrat7 said:
But I was installing updates fine a week ago. It's just the newest one giving me trouble. Someone said I have to go to the website manually and just put it in my SD card and zip install it through recovery.
I don't want to screw things up because I heard someone got stuck in a bootloop by doing this.
Click to expand...
Click to collapse
There is no reason to believe the new InsertCoin has any higher change to cause a bootloop than any other update or mod. I just manually flashed InsertCoin 3.0.8 and things went just fine. Side note: its funny I haven't been keeping up with the InsertCoin versions, and this thread made me realized how out of date I was . . . I was still on 3.0.4!
I'd relax on the "fear of a bootloop" thing. Bootloops happen, its just a fact of flashing mods. But the solution to recover is often an easy one; its just a matter of knowing or figuring out the exact trick to recover (different based on various causes). S-off is nice to have, but honestly its not an absolute necessity, as long as you've followed the other suggestions I gave previously, you are well equipped to recover from a bootloop, even in the unlikely event that one happens. S-off isn't necessary to flash ROMs, many folks do so S-on. S-off just gives you more options if you run into problems.
Ah I see.
And well, downloading 3.0.7 is aborting the installation so I guess I'll just do it manually or something haha
Also I forgot to mention..
Why doesn't SuperSU show up as a device administrator under security?
How can I fix this? Or is it not supposed to?
When doing firewater, I do "su" and there is no authentication, nothing. It's like SU doesn't exist
-----
EDIT:
also, whenever I download something from the marketplace or something it says "installation aborted" is there a reason for this?
So, I was on TWRP earlier and discovered I need to go back to stock recovery. I did that and tried applying the OTA. It downloads and starts installing in the stock recovery but after a while gives me the red exclamation symbol.
This is the Australian HTC 10 I'm using. 039 version. Neither the RUU Signed zip, nor the .exe exist for this version anywhere, as far as I've looked.
I also discovered that for this OTA to update - in the traditional method - I need to have S-OFF. Is this true? I never ended up getting S-OFF even after TWRP'ing and rooting my phone.
Any other method I can look into, to have the phone install updates as normal?
To save you the trouble of waiting for someone to answer, I'm going to let you know that no one is going to give you decent feedback, since these questions have been asked and answered thoroughly tons of times. You should go ahead and research the answers yourself. Cheers.
railpressureflip said:
So, I was on TWRP earlier and discovered I need to go back to stock recovery. I did that and tried applying the OTA. It downloads and starts installing in the stock recovery but after a while gives me the red exclamation symbol.
This is the Australian HTC 10 I'm using. 039 version. Neither the RUU Signed zip, nor the .exe exist for this version anywhere, as far as I've looked.
I also discovered that for this OTA to update - in the traditional method - I need to have S-OFF. Is this true? I never ended up getting S-OFF even after TWRP'ing and rooting my phone.
Any other method I can look into, to have the phone install updates as normal?
Click to expand...
Click to collapse
you modified your system partition which now since the m9 will not apply an ota if that happens. You need to flash an untouched system image or just ruu to a previous version and take the ota. As the other user mentioned this has been explained many time in many threads for the past 2 years now.
The red exclamation mark is the stock recovery.
samisax said:
To save you the trouble of waiting for someone to answer, I'm going to let you know that no one is going to give you decent feedback, since these questions have been asked and answered thoroughly tons of times. You should go ahead and research the answers yourself. Cheers.
Click to expand...
Click to collapse
Been doing that for days, wouldn't have posted this question if I had found the exact same issue as someone else. Thanks though!