Related
I didnt think this was possible but I think I bricked my phone by using Visionary and permroot.
I clicked on the permroot, the icon went on, rebooted and got stuck at the HTC green screen.
After pulling the battery;
I tried doing a factory reset, nothing.
I tried a stock image of tmobile, nothing (at least I think I did this right)
ADB doesnt recognize the device in windows
I have only seen a red triangle and exclamation point after trying several posts suggestions.
I'm stuck on what to do, and have a replacement coming, but not soon enough.
Can I do anything with this? Like get the original Tmobile image back on? If so, how? I'm not the brightest bulb when it comes to this, as the g1 was so much easier. A bit of instructions would be great.
Thank you!
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
You didn't read the post which said you should not try to install the stock rom?
fastludeh22 said:
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
@ddgarcia05 - that should be ok if he wasn't at S-OFF with the eng hboot though, which I don't believe that Visionary applies.
ibemad1 said:
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I checked and it said S-On and this was in recovery
ddgarcia05 said:
You didn't read the post which said you should not try to install the stock rom?
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
ADB doesnt recognize the device in windows and this was also in recovery
Anyone? Bueller?
cwis said:
ADB doesnt recognize the device in windows and this was also in recovery
Click to expand...
Click to collapse
Check out the adb guide at http://forum.xda-developers.com/showthread.php?t=865685
If you install the HTC Sync software, as mentioned in that guide, that should give you the drivers that you need.
This looks bad. Being that you're new. this can be very bad.
You have three choices:
1: study each thread about Bricking G2.
2:find a more experienced person to help you unbrick your phone.
3:find a very strong magnet and place it on your phone leave it there for an hour and bring it back.
I've searched the forums and have not found a situation that really matches mine.
I've been running on a Cyanogen nightly build for probably two months with no problems. Out of nowhere this morning my phone reboots itself (while it was idle; I wasn't even touching it) and then gets stuck in a boot loop. I get the White HTC Evo 4G screen, then it powers off and comes back up to the white screen again. Over and over.
All I can get do is hboot. Even telling hboot to go into the recovery mode puts my back into the boot loop. Fastboot, clear storage, and hboot usb all seem to work though. I've tried downloading the PC36IMG.zip file (http://forum.xda-developers.com/showthread.php?t=780141) in that thread, but hboot loads it and tells me that it is older than my current version, and only gives me the option to reboot, or not to reboot. Doesn't load the image.
Here is the information on my hboot screen:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.97.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Aug 19 2010, 14:29:08
Anybody have any ideas? Thanks!
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
NewZJ said:
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
Click to expand...
Click to collapse
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
luck has been wished
Kuhmo said:
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
Click to expand...
Click to collapse
This didn't work. Everything is still the same, except that my hboot version is now 2.10.0001. Any other thoughts?
still won't not into any rom? did you get errors?
NewZJ said:
still won't not into any rom? did you get errors?
Click to expand...
Click to collapse
No, the app on the PC said everything was successful. The progress bar on the phone progressed without errors too.
what happens when you reboot the phone not going into bootloader?
Just the HTC EVO 4G splash screen. Over and over and over...
does it show the boot animation or just stuck on splash?
Just the splash. No animation.
pull the battery, remove your sdcard, put the battery back in, see if it gets to the animation
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Wrong button..
xHausx said:
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I asked my wife to check this thread from the car on the way to dinner. Saw the response. So I took my laptop inside with us and used the RUU one more time. No luck. I decided that it must be a hardware issue. I took the SD out and removed the evidence that the phone had been rooted, then took it to the sprint service center up the road. They just replaced it for me. Thanks for your time! I DO want to root my phone again, the ROMs are just so much better than the stock installation. Should I not install the OTA updates if I'm going to root it? Which guide should I follow for rooting?
never do OTA when rooted, use unrevoked to root, unrevoked.com
NewZJ said:
never do OTA when rooted, use unrevoked to root, unrevoked.com
Click to expand...
Click to collapse
Not when rooted. I meant should I update to the latest OTA UNTIL I decide to do the root again? Is the latest OTA unrootable?
Same deal.
Here is the post that I put in the wrong forum that I was about to post here until I saw this thread...
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...
2) Anyone know how to turn S-(back)ON in my current situation?
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )
run the ruu to s-on then trade for another
NewZJ said:
run the ruu to s-on then trade for another
Click to expand...
Click to collapse
Ack, sorry... didn't mention in previous post. I fired up windows to run the RUU (I don't trust wine to that stuff) but it couldn't detect the device.
I know theres probably a thousand topics on this but none of them seem to have the same exact problem or they do and dont have a solution. I can boot my ROM and i cant boot recovery. the only thing i can get to is HBOOT. I have tried many of the PB31IMG.zip files but none of them work. i have also tried the RUU exe program but that did not work either. im kinda graspin at straws here cuz i dont have a phone right now. im also wondering if i should just take it to verizon, but with that im worried about them finding out its rooted, because it still says "S-off" on the HBOOT menu. Any suggestions on what to do?
To my knowledge if you are in a bootloop with no secondary recovery such as Amon-Ra or CWR, the only other option is the RUU downgrade your Inc through the Android HBOOT Recovery. Use these guides here:
http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
I have tried that exact process, both options, to no avail...thanks though. Is there any way to revert S-Off back to S-on through HBOOT?
gdaysoccer said:
I have tried that exact process, both options, to no avail...thanks though. Is there any way to revert S-Off back to S-on through HBOOT?
Click to expand...
Click to collapse
For whatever it's worth, my phone was s-off when I took it in to Verizon. (I was having the vibrations-of-death)
They saw the phone wasn't booting up, and even saw my unrevoked splash screen, and that was good enough for them to send me a new phone.
Honestly, I don't think a majority of those sales reps would even know how to get into hboot, and really don't know a whole lot about Android. I'm not saying it'd be impossible to get someone that lurks XDA in their spare time, but... it's unlikely.
And if they did lurk xda they probably wouldn't make an issue of you being rooted
Sent from my ADR6300 using XDA App
I actually just had the same issue as you and spent around 21 hours trying to get things fixed with a few devs and we had no luck. basically the phone would act as if it would take the ruu flash and claim it did and update the hboot like it did but made no change in order to complete a boot cycle. I had no recovery no rom just hboot and fastboot worked. every other option failed. we chalked this up to a hardware failure of some sort. I flashed the lastest Ruu and called *611 explained the problem and they overnighted me a new inc. I still have S-off on the phone but every other item radio/hboot/kernal is all stock. I doubht they wil lreally notice the S-off. all in all the phone is back to stock full wipe. Good luck.
I ended up taking it to the Verizon store today and the rep thought it might have been the battery so he tried a new one of those, but that wasnt the issue. I'm pretty sure he booted into HBOOT because he was playing around with the power and volume buttons, but he didnt ask me anything about it being s-off or rooted or anything and so theyre sending me a new phone, because unluckily they didnt have any in stock at the store i went to, and i have to send this one back. So, so far, it looks like no one really cares or even knows where to check for it being rooted.
I am in desperate need of unrooting my phone now, but due to it being almost 2 years that I've owned this phone I can't remember how I rooted it in the beginning. Any way to figure this out?
Need to know your Hboot version and radio, and also is the phone S-ON or S-OFF (power off, then volume down and power buttons simultaeously).
HBOOT-2.18.0001
RADIO-2.15.00.12.19
Phone is S-OFF
Thanks for your help.
On a side note, my phone is in an infinite boot loop that only loads to the white evo screen, I can't flash custom recoveries, roms, or RUU. I think the problem is the fact that it says LOCKED in the pink label at the top of my bootloader. I tried using the command fastboot oem lock and it says it's already locked and doesn't unlock it or anything of the sort. If you know any way to aid my problem I thank you for the help.
Most infinite bootloops are never fixed, however;
The best advice that I can give you right now is to download these two files.
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
http://goo.im/stock/supersonic/ruu/...15.00.12.19_NV_2.33_release_234563_signed.exe
Connect your phone to your computer, then boot into your bootloader and click on FASTBOOT. The phone should be in FASTBOOT USB. Install the HTCDrivers exe file to your computer. Then try to run the RUU file with the phone still in FASTBOOT USB.
If that doesn't work, then the phone may already be permanently bricked. Interestingly, the phone was rooted nearly 2 years ago, but you have the latest everything. I hope you did not do that with OTA updates.
Thanks shortyydoggg, unfortunately I've tried that method with those exact files already and had no such luck. My last resort is that if I can change the LOCKED pink label to RELOCKED or UNLOCKED, I'll be able to flash through the bootloader again, and temporarily use my phone once more until i can get the EVO LTE. Also, there is basically no way to tell now which root method I used?
Yea, Unlocking the bootloader was going to be my other suggestion after trying the RUU. It's not much else you can do after that.
Sent from my PC36100 using xda premium
Ya the RUU unfortunately goes through successfully but then the phone restarts again. I can't help but feel this is all because my bootloader says LOCKED. The problem now is fastboot oem lock command doesn't work for me, and says the phone is locked and doesn't change the label to RELOCKED or anything else like it should? Do you know why this command isn't unlocking my bootloader or any other commands or ways to do this?
djs415 said:
Ya the RUU unfortunately goes through successfully but then the phone restarts again. I can't help but feel this is all because my bootloader says LOCKED. The problem now is fastboot oem lock command doesn't work for me, and says the phone is locked and doesn't change the label to RELOCKED or anything else like it should? Do you know why this command isn't unlocking my bootloader or any other commands or ways to do this?
Click to expand...
Click to collapse
That's the wrong command. You need to go to the htcdev site (www.htcdev.com), register, and unlock the bootloader. Since you're already S-OFF, have you tried running a PC36IMG file for a custom RECOVERY. You might not need to be unlocked to do that.
I'm almost positive I tried to flash a custom recovery through the bootloader and it didn't work... however, you were right and my bootloader is now unlocked so THANK YOU! Will post back after flashing the recovery you attached.
To answer your previous question about which root method you used, unrevoked-forever was used at some point to S-OFF the phone, since you are on Hboot 2.18 and still S-OFF and not on the old Engineering S-OFF Hboot. Whether the phone was rooted with Unrevoked, Toast Method 2, Simple Root or AutoRoot, there is no exact way to tell right now, but it can be guesstimated that it might have been Unrevoked.
Now for the confusion if you dare to read:
AutoRoot is Toast Method 1, unrevoked-forever, and a custom ROM inside a program, and Simple Root is Toast Method 1 and a custom ROM inside a program along with the engineering S-OFF bootloader. Unrevoked is uh, Unrevoked and Unrevoked forever inside a program. Toast method 2 is just a custom ROM flashed along with the same S-OFF bootloader as SimpleRoot. If you used Toast Method 2, then you did everything AutoRoot did in order to S-OFF the phone. You just needed unrevoked-forever to keep it S-OFF for any other and your bootloader. Toast Method 1 alone does not S-OFF the phone. If you used SimpleRoot, which does not use unrevoked-forever, you needed unrevoked-forever at some point again to keep the phone S-OFF on any other Hboot (your 2.18). So again, you would have done everything AutoRoot did.
So that brings it down to AutoRoot and Unrevoked, since everything else you did is the same thing that AutoRoot does. Since you rooted nearly 2 years ago, and Unrevoked-forever is inside AutoRoot, AutoRoot has to be newer than unrevoked-forever to contain it inside its program. Also Unrevoked is newer than AutoRoot and already contained Unrevoked-forever. So the likely-hood that you used Unrevoked is very great, but not for sure. It is also the easier method and the one that nearly everyone else used at that time.
Somehow, still no luck. Flashed that file you linked and it goes through successfully, asks to reboot and then back to white screen boot loop. How can this be possible at this point, with the bootloader unlocked it goes through with the process but the actual writing of the data seems to fail. Trying the RUU one last time now that it is unlocked, but if this doesn't work I'm stumped.
I thought the whole beauty of the the bootloader, and more importantly being able to reach it, was that it meant your phone couldn't be bricked. Last try, will report back.
Bootloader unlocked, RUU flashed this time through PC. Nothing, and completely out of ideas here.
Shortydoggs been doing a lot of help around here for similar situations. There have been cases (maybe a dozen I've seen) where people get into a situation like yours where bootloader is accessible , but that is about it. And from what I've read, in those cases, when the phone tries to boot, it does 4 or 5 short vibrates before going back to bootloader.
Your situation is also strange in that, you rooted 2yrs ago, but don't have S-off, a locked bootloader. Hboot 2.18, which is the latest but is unlockable thru HTC dev, but no S-off available for it yet. And your radios are latest, too (mostly irrelevant).
First there was toasts root for baseband 1.37 (which downgraded you to 1.17 with eng hboot to get s-off before bringing you back up to 1.37). Then there was simple root by jiqqaman, which worked for people who took the baseband 1.47 OTA. Then when froyo came out, anyone who took that OTA (baseband 3.25, or 3.26, I forget) had to wait for unrevoked to be developed. I think hboot at that point was 2.08 and 2.10. Unrevoked forever worked on that, and gave you S-off.
I know none of that info helps you necessarily. It's just puzzling how you rooted 2yrs ago, bit have the latest hboot with S-on. Maybe you didn't finish toasts part 2 S-off guide, then sometime recently updated your radio and hboot? No. You need S-off to flash radio. Were you recently on a stock rooted ROM and took an OTA (is that even possible) when you were still S-on (from not finishing toasts guide)?
Sorry, I know it's not a lot of help. Just trying to figure out how things could not match up so much, and if that's how you ended up in this situation (that could be helpful info for others). I hope you don't have the bootloop of death and can get it sorted. Between shortydogg and captain throwback, I HAVE seen some phones saved.
sent from 2yr old Evo on ICS
Yea, I'm not going to waste your time any further. There's not much else to do.
Ya unfortunately I'm quite confused myself... however, if this information helps you at all... For starters, I have S-OFF and until recently (2 weeks or so since my phone started acting up like this) I was running a ROM perfectly fine until one day it restarted into this never ending boot loop. I'm not sure how my HBOOT is the most up to date, seeing as I was always very careful not to do something stupid like change my HBOOT for no reason. The interesting thing is that I had never seen that pink label before on my bootloader saying unlocked or locked OOW until the problem started occuring 2 weeks ago.
Also something I'm realizing... are you telling me that the HBOOT I have does not have S-OFF yet, and therefore you can't flash roms or custom recoveries... but my bootloader still says I am S-OFF. So the problem is I am S-OFF for the most recent HBOOT which can't be changed to S-OFF yet? Could downgrading hboots work?
He did not realize that you were S-OFF. Your phone is set to stay S-OFF regardless of what Hboot you have or how that Hboot usually comes.
Also, your phone appears to have a hardware, and not software issue, so, changing Hboots, might not hurt to try, but may not help much. In case I'm wrong, do not try anything below Hboot 2.10. Here is one for 2.16.
What rom were you running up until the time the bootloops started happening? This sounds alot like the cyanogen mod bootloop of death which no one has ever fixed I believe.
I believe I was using some version of SOS or a sense rom, but I'm leaning more towards SOS.
Just tried using that HBOOT thought it's still not working. Would going to the engineering hboot make any difference?
What could be the hardware problem causing this?
I see that shortydogg is in here taking good care of you .
The bottom line is, if you can't flash/get into recovery from HBOOT, you're probably in an unrecoverable situation.
It's unclear after my review of the thread, but you have tried flashing a recovery through HBOOT using a PC36IMG.zip file, right? And then after flashing, you choose not to reboot, but to boot into Recovery?
If you can get into recovery, then we can resolve your issue (if in fact it is software related).
If the problem is bad NAND blocks on your recovery or boot partitions, then there's nothing that can be done.
Also, the watermark on your bootloader (LOCKED, UNLOCKED, etc) has nothing to do with your issue. That's just connected to the version you were running. As long as you're S-OFF, that's irrelevant.
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?