First of all, I gotta give props to Albinoman for getting the Incredible to where he has (Jellybean, on the Incredible!... wow!)
http://forum.xda-developers.com/showthread.php?t=1778190
I've been following Albinoman's progress and while I was trying to troubleshoot the "low space notification" we're all too familiar with, I made a HUGE mistake.... I was using Albinoman's Beta 2, which worked great, but I tried restoring a nandroid backup and it failed, due to a corrupt SD card. Then, I tried restoring to another backup, which also failed. I then set out to run a scandisk on the SD card, so I shut off my phone thinking I could just boot back into recovery no problem right?!? WRONG!
After fixing the SD card, I was unable to even boot into recovery, I was getting the scary 5 vibrates of death, and I found this thread, which was half-helpful:
[HOW-TO] Fix 5 vibrate and black screen
http://forum.xda-developers.com/showthread.php?t=1110865
It was able to get my SD card working (previously it didn't at all), but I still cannot boot without having a USB cable plugged in (otherwise I get the 5 vibrates and a blank screen).
The thread suggested using z4root to gain temporary root but when I try that, it just sits there for a very long time and times out.
Here's where my biggest problems come in...
I'm currently running Gingerbread 2.3.4, S-ON, and ADB is BROKEN on my phone
My HBoot is version 1.07.0000 (I was 0.92.0000, but now I flashed cmlusco's newer HTC rom, so it changed)
What I currently have to work with (what works):
Wifi, SD Card (new one of course), 3G, and I'm able to boot, and I got my bootloader unlocked!
I cannot find any way to root my phone based on my current situation.
I have found plenty of ways to root (I'm used unrevoked plenty of times but it wont help me now because ADB wont work with my phone because it's broken, but I can't fix ADB, because I can't get root, it's really a sad situation)
I've tried HTC's RUU official root method, other RUU's, and Unrevoked, but they all don't work because my ADB is messed up
Also, I don't know if this helps, I can use fastboot, and I was able to flash an image using fastboot commands, but it's been awhile since I've tried that, and I don't know of anything I can flash via fastboot to help my situation.
My main goal is, I just need to get rooted again so that I can re-flash Albinoman's sweet Beta 3 ROM which I've been unable to even try
Thanks for the help you guys are amazing!
UPDATE: It's FIXED!!!! Here's the short version of how (in case it happens to anyone else)
To start, my phone A: Would not boot B: Would not read the SD card, or EMMC, EVEN in recovery C: all USB was broken including ADB (but fastboot worked) and D: I managed to lose root by flashing like mad in hopes of fixing AB and C
Step 1: I flashed cmlusco's ROM that he suggested which got my hboot up to date etc...
Step 2: I went to http://htcdev.com/bootloader/ and unlocked my bootloader (BUT I skipped straight to step 8 (the fastboot part, since everything before that was a waste of my time since my USB/ADB was hosed))
Step 3: I flashed this recovery image and ran "fastboot flash recovery recovery.img"
Step 4: I downloaded superuser and loaded it through recovery, now that my SD card worked
Step 5: I then was able to do the following in order to fix the USB/ADB problem:
using this file and this file and running them in an android emulator app I downloaded from google play (since my USB was broken)
Terminal emulator & ADB commands:
Code:
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd-eng.img > /data/mtd-eng.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd-eng.img
reboot
(credits for this to this thread)
Step 6: I was now fixed, so I just wiped my phone and flashed Albinoman's Jellybean ROM because it rocks!
Thanks to tiny4579 and cmlusco for both of your help!
Two quick questions:
1. Does USB mass storage work? (do your sdcard and emmc get recognized as drive letters when it boots) - if it doesn't there MAY be a problem but question 2's suggestion may fix it.
2. Did you try uninstalling and reinstalling the adb drivers?
This is just off the top of my head. Oh, now I see that fastboot works so basic USB communication works so it may be a driver issue.
Oh, since fastboot works you should be able to flash CWM recovery and a superuser zip to root unless it says not allowed. But if you can flash and boot recovery at that point no point on rooting, just flash a rooted ROM like jellybean beta3.
meadowsjared said:
First of all, I gotta give props to Albinoman for getting the Incredible to where he has (Jellybean, on the Incredible!... wow!)
http://forum.xda-developers.com/showthread.php?t=1778190
I've been following Albinoman's progress and while I was trying to troubleshoot the "low space notification" we're all too familiar with, I made a HUGE mistake.... I was using Albinoman's Beta 2, which worked great, but I tried restoring a nandroid backup and it failed, due to a corrupt SD card. Then, I tried restoring to another backup, which also failed. I then set out to run a scandisk on the SD card, so I shut off my phone thinking I could just boot back into recovery no problem right?!? WRONG!
After fixing the SD card, I was unable to even boot into recovery, I was getting the scary 5 vibrates of death, and I found this thread, which was half-helpful:
[HOW-TO] Fix 5 vibrate and black screen
http://forum.xda-developers.com/showthread.php?t=1110865
It was able to get my SD card working (previously it didn't at all), but I still cannot boot without having a USB cable plugged in (otherwise I get the 5 vibrates and a blank screen).
The thread suggested using z4root to gain temporary root but when I try that, it just sits there for a very long time and times out.
Here's where my biggest problems come in...
I'm currently running Gingerbread 2.3.4, S-ON, and ADB is BROKEN on my phone
What I currently have to work with (what works):
Wifi, SD Card (new one of course), 3G, and I'm able to boot
I cannot find any way to root my phone based on my current situation.
I have found plenty of ways to root (I'm used unrevoked plenty of times but it wont help me now because ADB wont work with my phone because it's broken, but I can't fix ADB, because I can't get root, it's really a sad situation)
I've tried HTC's RUU official root method, other RUU's, and Unrevoked, but they all don't work because my ADB is messed up
Also, I don't know if this helps, I can use fastboot, and I was able to flash an image using fastboot commands, but it's been awhile since I've tried that, and I don't know of anything I can flash via fastboot to help my situation.
My main goal is, I just need to get rooted again so that I can re-flash Albinoman's sweet Beta 3 ROM which I've been unable to even try
Any help anybody could offer me would be GREAT! Thanks XDA, you guys are amazing!
Click to expand...
Click to collapse
What hboot version are you on? Have you tried an ruu thru hboot?
I would try an ruu thru hboot first. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
If that dosent let you boot, use the htcdev site to unlock your bootloader. And then fastboot flash cwm recovery, and then superuser thru cwm. Then you will be rooted and can try to wipe everything and flash a rom.
tiny4579 said:
Two quick questions:
1. Does USB mass storage work? (do your sdcard and emmc get recognized as drive letters when it boots) - if it doesn't there MAY be a problem but question 2's suggestion may fix it.
2. Did you try uninstalling and reinstalling the adb drivers?
This is just off the top of my head. Oh, now I see that fastboot works so basic USB communication works so it may be a driver issue.
Oh, since fastboot works you should be able to flash CWM recovery and a superuser zip to root unless it says not allowed. But if you can flash and boot recovery at that point no point on rooting, just flash a rooted ROM like jellybean beta3.
Click to expand...
Click to collapse
1st of all, thanks for getting back to me so quickly Tiny, you're amazing, and I appreciate all the work you've done with the Dinc, thanks for being so active!
1. No, mass storage doesn't work (I assume you mean plugging in the phone and having it mount the SD card as a drive on the computer)
However, I am able to now use both my SD card from within Gingerbread, and the recovery, but only after doing the "fastboot oem enableqxdm 0" trick
2. I haven't tried uninstalling and reinstalling the ADB drivers, but only because.... I'm a developer, and sometimes I develop on my home computer, and sometimes I develop at work, and they both exhibit the same behavior, so I don't think it can be that both computers, just happened to get messed up at the exact same time, right when my phone got hosed?
Also, I've used ADB plenty in the past, on both computers, so I'm certain they're set up right, just between having two computers to work with, AND the extensive use I've made of ADB in the past (I'm the office Root-er, I've rooted most of my co-worker's phone for them, so I've had quite a bit of experience (and should have known better than to turn off my phone when I did which got me in this pickle ))
Just to be clear though, basic USB communication works, but only in HBOOT, NOT from Gingerbread, actually, having the phone plugged into USB (whether or not USB debugging is turned on on the phone), WILL lock up my computer until I unplug it, and as soon as I unplug, my computer snaps back to normal So I think somehow something in the phone got hosed so the ADB is broken, however, I can't fix it because I can't get my root back because I'm stuck in the horrible stock gingerbread (no offense to anyone that likes it )
Also, yes, I've tried a ton of times to flash a superuser zip to root and it says it's not allowed/bad signature or whatever, because it's still S-ON
cmlusco said:
What hboot version are you on? Have you tried an ruu thru hboot?
I would try an ruu thru hboot first. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
If that dosent let you boot, use the htcdev site to unlock your bootloader. And then fastboot flash cwm recovery, and then superuser thru cwm. Then you will be rooted and can try to wipe everything and flash a rom.
Click to expand...
Click to collapse
@cmlusco
I didn't even know you could use RUU's through hboot, I'll try that, as well as using the HTC unlocker RUU with hboot.
I'd already tried those things normally, but with by USB being hosed, it didn't help much. :-\
I'll post back when I've given them a try
cmlusco said:
What hboot version are you on? Have you tried an ruu thru hboot?
I would try an ruu thru hboot first. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
If that dosent let you boot, use the htcdev site to unlock your bootloader. And then fastboot flash cwm recovery, and then superuser thru cwm. Then you will be rooted and can try to wipe everything and flash a rom.
Click to expand...
Click to collapse
I'm on HBoot 0.92.0000
and it seems to only allow me to flash newer, or the same version as what I've got (because I've tried downgrading)
I just tried the RUU from HTC to root my phone.
I ran the RUU, put the phone in hboot, and it sat and said "verifying phone information" or something like that and said "error 170, usb connection error"
I also put the phone in "fastboot" and tried again, it didn't seem to make a difference.
Now regarding flashing an RUU through hboot, how would I go about doing that? I'm assuming you're talking about throwing the PB31IMG.zip on my SD and booting into Hboot. Now that DOES work however, I'm still S-ON, so unless it's a factory image, it ain't gonna like it
That is, unless there's some kind of fastboot voodoo that can be done to get something on there to exploit it and get my back my root I once had and loved!
meadowsjared said:
I'm on HBoot 0.92.0000
and it seems to only allow me to flash newer, or the same version as what I've got (because I've tried downgrading)
I just tried the RUU from HTC to root my phone.
I ran the RUU, put the phone in hboot, and it sat and said "verifying phone information" or something like that and said "error 170, usb connection error"
I also put the phone in "fastboot" and tried again, it didn't seem to make a difference.
Now regarding flashing an RUU through hboot, how would I go about doing that? I'm assuming you're talking about throwing the PB31IMG.zip on my SD and booting into Hboot. Now that DOES work however, I'm still S-ON, so unless it's a factory image, it ain't gonna like it
That is, unless there's some kind of fastboot voodoo that can be done to get something on there to exploit it and get my back my root I once had and loved!
Click to expand...
Click to collapse
That PB31IMG.zip i posted is 4.08.605.15, the latest android version for our phone. It is official and signed by htc, so it should flash even if your s-on. Just place it on your sd in no folders and hboot should find it.
cmlusco said:
That PB31IMG.zip i posted is 4.08.605.15, the latest android version for our phone. It is official and signed by htc, so it should flash even if your s-on. Just place it on your sd in no folders and hboot should find it.
Click to expand...
Click to collapse
Yes, you're right, I was able to flash that image using hboot, but sadly... the adb is STILL broken and doing all the same things it was before (it doesn't work, and when I plug it into my computer, it freaks out my computer and the computer freezes until I unplug the phone, then everything is fine again)
It seems that all these images write everything to the phone... BUT what I need. I've found some things that "should" fix my problem, but they are all unsigned, and therefore they require root. Is there a chance that now with this newest RUU you gave me "z4root" will work cmlusco? (the reason I ask is, I'm hoping that an app that roots the phone without the computer will work, since every time I plug into a computer, it doesn't work, and just freaks out the computer)
Also, regarding the official HTC way to root, I tried running their "PB3120000_Incredible_C_hboot_1.02.0000_4.08.605.2.exe" file, however, that didn't work in the slightest (because it uses adb commands to talk to the phone). Is it possible that there's a way to extract the PB31IMG.zip file from that exe file and therefore I would be able to flash that using hboot, and the phone would like it because it's signed by HTC (I'm assuming)?
By the way, ever since I flashed that newer PB31IMG.zip ROM, now when I go into hboot, at the top it says "*** LOCKED ***", and it never said that before, I don't know if that matters at all? :-\
Also, if it helps any, here's what the update looked like....
*** LOCKED ***
INCREDIBLE XC SHIP S-ON
HBOOT-1.07.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.12.20
Apr 24 2012,22:58:40
HBOOT
Parsing... [SD ZIP]
[1] RADIO_V2 - OK
[2] BOOT - OK
[3] RECOVERY - OK
[4] SYSTEM - OK
[5] SPLASH1 - OK
Update Complete...
Then, after running the update, it asked me if I wanted to reboot, it showed the picture of the phone with the arrows in a circle around it, then when it wen to reboot, it did the usual (for me lately), and gave me the 5-vibrates of death and a black screen, the only way to get out of it is to do a battery pull. Then, after doing that, if I just plug in the cable, I can boot into the new rom just fine, but if the cable isn't plugged in, I just get the 5 vibrates of death, like this guy....
[HOW-TO] Fix 5 vibrate and black screen
http://forum.xda-developers.com/show....php?t=1110865
But sadly, in order to completely fix myself, I need root, and I can't seem to even get temporary root? :-\
I'm hoping maybe something there might help y'all to help me? :-\
tiny4579 said:
Two quick questions:
1. Does USB mass storage work? (do your sdcard and emmc get recognized as drive letters when it boots) - if it doesn't there MAY be a problem but question 2's suggestion may fix it.
2. Did you try uninstalling and reinstalling the adb drivers?
This is just off the top of my head. Oh, now I see that fastboot works so basic USB communication works so it may be a driver issue.
Oh, since fastboot works you should be able to flash CWM recovery and a superuser zip to root unless it says not allowed. But if you can flash and boot recovery at that point no point on rooting, just flash a rooted ROM like jellybean beta3.
Click to expand...
Click to collapse
@tiny4579
To be more clear, the basic USB communication doesn't work, the only way I can get anything that uses USB to work, is by booting into fastboot, and I have been able to do fastboot commands (like "fastboot oem enableqxdm 0"). So it seems that fastboot's USB works just fine (I've tested this on multiple computers), but anything after that, like trying to use the USB from the operating system, is totally broken. So I'm guessing that internally, the phone's drivers for USB are separate for hboot, and therefore still work, however, the phone's USB drivers for Gingerbread, are completely broken, even though I've been able to flash 2 different versions of signed gingerbread from HTC, they still don't seem to fix my USB problem even though it's writing the entire system all over again. Is it possible that there's a signed HTC zip that will fix my USB, that would fix me... the only question is.... does a signed HTC zip exist that will fix my USB??? :-\
Ok, I've got great news, I was able to finally unlock my bootloader! so now when I go into HBOOT, it says at the top "UNLOCKED", however, it still says S-ON, and I still don't have root, but I think we're getting there!
So now that my bootloader is unlocked, I'm assuming I should be able to either load a custom recovery (like clockworkmod), however, I still can't use ADB to do anything so things like unrevoked wont work for me sadly
Do you guys have any advice on what I can now do that my bootloader is unlocked? (I'm a little unclear about what the whole bootloader thing does for me). I think I understand rooting, at least enough, and I thought I understood the bootloader, and the unlocking. But now that my bootloader is unlocked, it still wont let me load anything like CM7.1, or clockworkmod (I tried both of those by going into recovery and trying to flash the update.zip).
Either way, I'm very encouraged by the fact that my bootloader is unlocked, I'm assuming it should help me to acheive my goal of rooting and eventually gettting Albioman's Jellybean on there?
meadowsjared said:
Ok, I've got great news, I was able to finally unlock my bootloader! so now when I go into HBOOT, it says at the top "UNLOCKED", however, it still says S-ON, and I still don't have root, but I think we're getting there!
So now that my bootloader is unlocked, I'm assuming I should be able to either load a custom recovery (like clockworkmod), however, I still can't use ADB to do anything so things like unrevoked wont work for me sadly
Do you guys have any advice on what I can now do that my bootloader is unlocked? (I'm a little unclear about what the whole bootloader thing does for me). I think I understand rooting, at least enough, and I thought I understood the bootloader, and the unlocking. But now that my bootloader is unlocked, it still wont let me load anything like CM7.1, or clockworkmod (I tried both of those by going into recovery and trying to flash the update.zip).
Either way, I'm very encouraged by the fact that my bootloader is unlocked, I'm assuming it should help me to acheive my goal of rooting and eventually gettting Albioman's Jellybean on there?
Click to expand...
Click to collapse
Now you need to fastboot flash cwm. Download this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, and place it on your pc in the same folder as the fastboot.exe file.
Open a cmd prompt on your pc to where fastboot.exe and recovery.img are. Type the folowing:
Code:
fastboot flash recovery recovery.img
If you get no errors, go to the maim hboot menu and select recovery. You should now be in cwm recovery.
Download superuser http://dinc.does-it.net/Superuser/SuperUser_3.0.7.zip, and place it on your sdcard by going to mounts and storrage and selecting mount usb storrage. If it freezes up the phone or the pc, you will need to take the sd out and use a card reader to put it on the sd with a pc.
Then flash it thru recovery like you would a rom. Now you will be rooted. Then flash a rom of your choosing and hope it boots.
Might as well load the ROM when you load superuser. But flashing superuser is silly if you're going to flash a ROM with root right after it but it's probably still a good zip to keep on your sdcard.
tiny4579 said:
Might as well load the ROM when you load superuser. But flashing superuser is silly if you're going to flash a ROM with root right after it but it's probably still a good zip to keep on your sdcard.
Click to expand...
Click to collapse
Yeah i guess it is pointless to flash su, then wipe it, then flash a rooted rom.
Thank you both of you, you were a HUGE HELP!!!!! I'm FIIIIIIXED!!!!!!!!!!!!!!
I'm going to update the original post to detail how I got fixed (the short version is, I just did what cmlusco said, and as soon as I had root, I followed this and it worked!!!!)
tiny4579 said:
Might as well load the ROM when you load superuser. But flashing superuser is silly if you're going to flash a ROM with root right after it but it's probably still a good zip to keep on your sdcard.
Click to expand...
Click to collapse
I wound up loading superuser like cmlusco suggested, only because I wanted to have everything fixed and perfect before loading Albinoman's new ROM, just in case there were issues, that way I'd know that it was the ROM or my phone, especially since my SD Card freaked out on me and that's how I got into this mess
....But, you are right, the only problem is, I'm super paranoid, and I like to be super-thorough
meadowsjared said:
I wound up loading superuser like cmlusco suggested, only because I wanted to have everything fixed and perfect before loading Albinoman's new ROM, just in case there were issues, that way I'd know that it was the ROM or my phone, especially since my SD Card freaked out on me and that's how I got into this mess
....But, you are right, the only problem is, I'm super paranoid, and I like to be super-thorough
Click to expand...
Click to collapse
Glad its working for you.
Sent from my Galaxy Nexus using Tapatalk 2
Okay it's been a few months since this has happened so I'll try to remember as best as I can; I had rooted my Nexus using WugFresh's kit, everything went fine. It was rooted for about 6 months and eventually got stuck in a boot loop (no clue how this happened, I hadn't installed any kernals, roms, even apps in months). I tried like 4 or 5 different methods to fix the issue; I finally was able to get the phone working again using ODIN mode, it completely restored it to stock (as far as I'm aware).
So I tried to re-root the phone; no luck, using ANY method I've been able to find. The main problem is I can't seem to get into TWRP, every time I try to it simply gives me the dead android with the red exclamation point. I'm not an advanced user by any means, but I'm not totally clueless and I can follow directions. If anyone has any advice for me on this I'd GREATLY appreciate it, I have an excellent 4G signal where I live and the only other internet option is AT&T basic DSL so I'd really like to be able to use my wifi hotspot again. Thanks in advance for your time, I appreciate anyone who takes the time to try to help.
1) android on its back is stock recovery.
2) follow this: http://forum.xda-developers.com/showthread.php?t=1529058
it works 100% of the time if you read and take your time.
it sounds like you have root but cant flash a recovery, let me know if im wrong but if this is the case I would just download goo manager from the market and go into settings and flash a custom recovery and that should fix your recovery problem but sometimes you have to download the recovery twice ive noticed that in the past, let me know if this works for you or you could go through the longer process above but your fix may be very simple
Thanks for the info, I will try this either tonight or tomorrow and get back to you; I certainly hope it works!
jaymazz13 said:
it sounds like you have root but cant flash a recovery, let me know if im wrong but if this is the case I would just download goo manager from the market and go into settings and flash a custom recovery and that should fix your recovery problem but sometimes you have to download the recovery twice ive noticed that in the past, let me know if this works for you or you could go through the longer process above but your fix may be very simple
Click to expand...
Click to collapse
I thought that too, but I tried installing super user and a couple of other root-only apps and it said that my device wasn't rooted. =P
Zepius said:
1) android on its back is stock recovery.
2) follow this: http://forum.xda-developers.com/showthread.php?t=1529058
it works 100% of the time if you read and take your time.
Click to expand...
Click to collapse
This is driving me insane. I'm trying this method; I followed the directions step by step, but my phone is showing that it is unlocked already (when I entered the fastboot oem unlock command in CP it returned FAILED: Invalid Command, but it is showing as unlocked in bootloader.
Now for the weird part; I rebooted to bootloader and tried fastboot flash recovery recovery-clockwork-6.0.2.3-toroplus.img and it returned immediately FAILED: Invalid Argument. I decided to start the process over, and now I can't reboot from CP, it's saying error: device not found.
I really want to just smash this f*%&ing thing into several hundred thousand pieces right about now, so I'm going to take a break for the moment. Are there different types of bootloaders, or is it possible the my bootloader is just corrupted or something?
There are different bootloaders, but the fastboot commands should work just the same. You're on Windows i'm assuming? You could also look at efrant's guide, http://forum.xda-developers.com/showthread.php?t=1626895, as well as his 101 in the general section stickies. It does not make sense that the device would become not found, and I would try reflashing the bootloader. Don't smash the phone!
Have you tried this method?
http://forum.xda-developers.com/showthread.php?t=1400871
lockehart12 said:
Now for the weird part; I rebooted to bootloader and tried fastboot flash recovery recovery-clockwork-6.0.2.3-toroplus.img and it returned immediately FAILED: Invalid Argument. I decided to start the process over, and now I can't reboot from CP, it's saying error: device not found.
Click to expand...
Click to collapse
your drivers are not installed correctly.
So I rooted my Nexus 7 (2013) a while back, and it was working fine. I have TWRP recovery installed, bootloader unlocked, and I thought it was rooted. Then (don't kill me, I can't remember what I did, it was so long ago - I think maybe I installed the official KitKat update, although I am pretty sure I sideloaded a rooted version of the stock KK ROM), root just stopped working. Root Checker says I'm not rooted, even though I have the SU app installed. So, I thought, I'll just flash the SU.zip from recovery. So I flash it. And literally nothing happens. It says it flashed successfully, but when I reboot, no root.
In fact, any time I flash anything, it appears to work, but doesn't actually do anything. I tried flashing a different ROM and no dice. I tried accepting the official 4.4.2 update and again, looked like it flashed, but was still 4.4 when I rebooted.
So I thought I'll just plug it into my PC and re-root and maybe flash everything if need be. Except, when I plug it in, it 1) isn't recognized by my computer at all, no matter how many times I uninstall and reinstall drivers, and 2) the ADB connected icon doesn't show up, even when I enable it in Developer Settings.
So basically I'm dead in the water: I can't do anything via recovery, and if recovery is messed up, I can't do anything because it won't connect to my computer (Windows 7, SP1, 64 bit). I have a Mac running OS X Mavericks, if anyone knows some Terminal tricks for stuff.
So…advice?
darnocs1 said:
So I rooted my Nexus 7 (2013) a while back, and it was working fine. I have TWRP recovery installed, bootloader unlocked, and I thought it was rooted. Then (don't kill me, I can't remember what I did, it was so long ago - I think maybe I installed the official KitKat update, although I am pretty sure I sideloaded a rooted version of the stock KK ROM), root just stopped working. Root Checker says I'm not rooted, even though I have the SU app installed. So, I thought, I'll just flash the SU.zip from recovery. So I flash it. And literally nothing happens. It says it flashed successfully, but when I reboot, no root.
In fact, any time I flash anything, it appears to work, but doesn't actually do anything. I tried flashing a different ROM and no dice. I tried accepting the official 4.4.2 update and again, looked like it flashed, but was still 4.4 when I rebooted.
So I thought I'll just plug it into my PC and re-root and maybe flash everything if need be. Except, when I plug it in, it 1) isn't recognized by my computer at all, no matter how many times I uninstall and reinstall drivers, and 2) the ADB connected icon doesn't show up, even when I enable it in Developer Settings.
So basically I'm dead in the water: I can't do anything via recovery, and if recovery is messed up, I can't do anything because it won't connect to my computer (Windows 7, SP1, 64 bit). I have a Mac running OS X Mavericks, if anyone knows some Terminal tricks for stuff.
So…advice?
Click to expand...
Click to collapse
Does it recognize your device when it's booted into the bootloader (aka fastboot mode)?
charesa39 said:
Does it recognize your device when it's booted into the bootloader (aka fastboot mode)?
Click to expand...
Click to collapse
It didn't, but I found I was using a bad USB cable. Swapped out, and now it works (yay). However, root still wouldn't work after I ran several rooting methods from the computer.
Finally, I went to the Play Store, downloaded Superuser from Clockworkmod, followed their link in that description to download the flashable zip, flashed that, and FINALLY got root working. So happy.
darnocs1 said:
It didn't, but I found I was using a bad USB cable. Swapped out, and now it works (yay). However, root still wouldn't work after I ran several rooting methods from the computer.
Finally, I went to the Play Store, downloaded Superuser from Clockworkmod, followed their link in that description to download the flashable zip, flashed that, and FINALLY got root working. So happy.
Click to expand...
Click to collapse
Cool. Glad it worked out for you. :good:
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
iSike said:
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
Click to expand...
Click to collapse
Open SuperSU->Settings->Unroot?
j to the 4n said:
Open SuperSU->Settings->Unroot?
Click to expand...
Click to collapse
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
iSike said:
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
Click to expand...
Click to collapse
When I unrooted using SuperSu it ruined my installation also. I was stuck in a bootloop until I installed TWRP and reinstalled SuperSu, terrible!!! It eventually unrooted and I relocked bootloader but nothing worked so I was forced to root and unlock bootloader again.
I am wondering though, how did you return to stock? I really want the latest AT&T stock but when I install that RUU .exe it gives me error 155 so I can't install it. I was using 1.32 stock AT&T and wanted to install 2.6 (I think that's what it is, it's Android 5.1).
I am S-On, and not S-off, could that be an issue? Bootloader is unlocked and I am rooted now.
You know how u r supposed to rename the ruu u want to flash (assuming you downloaded the stock ruu for your carrier and device). The problem for me was, I could never connect my device thought adb after I rooted it (fast boot worked when I put it in fastboot). Even when I could give a command , it could never load the ruu. So what I did, was right click the ruu and click run as admin. It should open up a page on the top saying something about a ruu/rom utility. Make sure you device is connected and had usb debugging( before you got stuck in the loop hopefully). Now click accept and all that good stuff on the utility, it should scan your phone and show u your current rom image, and then show you the latest rom image. Click update and it will boot your phone to boot loader and begin sending it to your phone. IMPORTANT: DO NOT TOUCH YOUR PHONE. Now here's the catch, if it said it failed or something about a USB error, close the program and start it up again. If your phone is stuck without the download bar moving(displayed on your phone), you are going to have to hard reset it. Google how to do it for your device (just a button holding combination). And start the program again. It will take a couple times for the program to work (mine took about 5-6 times). But it will work sooner or later. I am not home atm, but when I get home, I will find the link to the page where this info is displayed in a more orderly fashion and with pictures. It will be tonight, probably about 9 hours. Try this though, if it is too confusing, wait till I post the link. Good Luck!!
EDIT: Sorry just got back home from a long day haha, I'll be sure to look for the link tomorrow. But my directions above should be good, give it a try.