I'm trying to root my phone to install CM 10.2. I've been searching for a few hours and am getting more and more frustrated. I've read that Firewater is the easiest way to unlock the bootloader on my phone. I've downloaded Firewater, but I don't know what to do with it. Its just a file called "Firewater" with no extension. I don't know how to run it.
I've also tried RumRunner, and have had no success.
I'm not sure what ADB and Fastboot are, but I think I have some ADB stuff installed on my comp [ C:\Program Files (x86)\Minimal ADB and Fastboot ] and I have that path in my Environment Variables>path directory. I don't know what to do with it.
Please help me get started. Step by step instructions would be great. I saw a thread that isn't very old where someone was having root trouble w/ KitKat but they were able to run Firewater. I need help getting that started at least. Thank you.
Edit: Fastboot is Off
USB Debugging Enabled
HTC Sync (can't find it anywhere on my comp, or in the programs list ((control panel)) so I assume its not installed)
Drivers are installed on my comp.
I've downloaded an ADB toolkit, and have it pathed. I opened the command prompt and ran "adb devices" to check. My phone showed up with no problem.
I then moved firewater to the current directory cmd was using c:\Users\MYNAME.
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
after this it displays:
127:[email protected]:/ $
I entered "su"
/system/bin/sh: su: not found
Could anyone explain what I'm doing exactly by following these directions, and explain what I can do next to correct the problem?
Edit: su means Super User, correct? I've tried installing SuperSU, but It says that there is no SU binary installed. I haven't found out how to install the binary.
Pharva said:
I've downloaded an ADB toolkit, and have it pathed. I opened the command prompt and ran "adb devices" to check. My phone showed up with no problem.
I then moved firewater to the current directory cmd was using c:\Users\MYNAME.
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
after this it displays:
127:[email protected]:/ $
I entered "su"
/system/bin/sh: su: not found
Could anyone explain what I'm doing exactly by following these directions, and explain what I can do next to correct the problem?
Edit: su means Super User, correct? I've tried installing SuperSU, but It says that there is no SU binary installed. I haven't found out how to install the binary.
Click to expand...
Click to collapse
you need temp root... goto http://firewater-soff.com/ everything is right there. If you have kitkat from the OTA the other day, i dont believe it works on kitkat yet.
Thanks. I've read that temproot doesn't work on KitKat either. For now, it would seem that my only option is to wait, right?
Pharva said:
Thanks. I've read that temproot doesn't work on KitKat either. For now, it would seem that my only option is to wait, right?
Click to expand...
Click to collapse
Yes you are correct temp root method does not work for the newest OTA update and unfortunately there is no method for the CDMA version of the htc one so hopefully we will see a new method soon!
S-Off not working
nty123 said:
Yes you are correct temp root method does not work for the newest OTA update and unfortunately there is no method for the CDMA version of the htc one so hopefully we will see a new method soon!
Click to expand...
Click to collapse
I am having this problem also. I am trying to s-off with firewater and can't get past the SU also...it tells me SU can't be found.
Debugging enabled
Developer Mode enabled
Network band set to LTE/CDMA
No passcode or other security lock
My Fastboot and ADB are working fine. I am able to run the Temproot instructions, but it stops at SU. WHY?
payrovi2 said:
I am having this problem also. I am trying to s-off with firewater and can't get past the SU also...it tells me SU can't be found.
Debugging enabled
Developer Mode enabled
Network band set to LTE/CDMA
No passcode or other security lock
My Fastboot and ADB are working fine. I am able to run the Temproot instructions, but it stops at SU. WHY?
Click to expand...
Click to collapse
just what the above post's stated, you need temp-root to, along with firewater. and if you are on the newest ota (kitkat 4.4.2) then you have no other choice but to wait. that mean's no downgrading either.
nty123 said:
just what the above post's stated, you need temp-root to, along with firewater. and if you are on the newest ota (kitkat 4.4.2) then you have no other choice but to wait. that mean's no downgrading either.
Click to expand...
Click to collapse
Thanks. Yes, I was able to temproot and firewater and get s-off.
I'm trying to load Cyanogenmod for my HTC One Verizon ( cm-10.2.0-RC1-m7vzw.zip ) through clockworkmod recovery 6.0.4.7
When I wiped the data/factory reset...it seemed to get stuck for >20minutes. I powered down and up...and it looked like some partial factory reset had happened.
I went ahead with the cyanogenmod zip update, through cwm recovery, and it seems to be stuck at Installing Update. Nothing is happening or moving.
Any thoughts?
Thanks for all the developer help.
payrovi2 said:
Thanks. Yes, I was able to temproot and firewater and get s-off.
I'm trying to load Cyanogenmod for my HTC One Verizon ( cm-10.2.0-RC1-m7vzw.zip ) through clockworkmod recovery 6.0.4.7
When I wiped the data/factory reset...it seemed to get stuck for >20minutes. I powered down and up...and it looked like some partial factory reset had happened.
I went ahead with the cyanogenmod zip update, through cwm recovery, and it seems to be stuck at Installing Update. Nothing is happening or moving.
Any thoughts?
Thanks for all the developer help.
Click to expand...
Click to collapse
can you power off device and boot into recovery? (not sure what the problem is yet but you could try using a different recovery, twrp instead of cwm. before you try out twrp (if you do) make sure you have the latest version of cwm installed
nty123 said:
can you power off device and boot into recovery? (not sure what the problem is yet but you could try using a different recovery, twrp instead of cwm. before you try out twrp (if you do) make sure you have the latest version of cwm installed
Click to expand...
Click to collapse
I can boot into recovery, but can't boot the phone up.
payrovi2 said:
I can boot into recovery, but can't boot the phone up.
Click to expand...
Click to collapse
ok, what i would try is backup to the rom you have before you tried installing CM( only if you made a backup). if you didn't then i would try clearing all data and that rom and try installing a different one, maybe the one you have has a bug and is not working properly.
nty123 said:
ok, what i would try is backup to the rom you have before you tried installing CM( only if you made a backup). if you didn't then i would try clearing all data and that rom and try installing a different one, maybe the one you have has a bug and is not working properly.
Click to expand...
Click to collapse
It kept getting stuck at "installing update" no matter whether it was a previous rom or the Cyanogenmod rom. I tried it numerous times...and then finally once it said "...update complete"
I'm rebooting and loading cyanogenmod now...hope that it moves past this CM boot screen.
payrovi2 said:
It kept getting stuck at "installing update" no matter whether it was a previous rom or the Cyanogenmod rom. I tried it numerous times...and then finally once it said "...update complete"
I'm rebooting and loading cyanogenmod now...hope that it moves past this CM boot screen.
Click to expand...
Click to collapse
Nope. still stuck at this boot loop.
Any ideas?
payrovi2 said:
Nope. still stuck at this boot loop.
Any ideas?
Click to expand...
Click to collapse
try restoring from you backup again but this time wipe all your data and factory reset before yo restore
payrovi2 said:
Nope. still stuck at this boot loop.
Any ideas?
Click to expand...
Click to collapse
I would do a decrypted RUU at this point, it will at least get you back on a sense rom (as long as you download the decrypted one, it wont break your SOFF and bootloader unlock). then from there i would reinstall PHILZ or TWRP, then make sure the MD5 is right on the rom you want to install
Related
i rooted my sisters white Evo yesterday.i followed up on Hboot 2.02 S-Off Like a Boss! guide, and it worked and everything. it flashed Stock 2.2 Rooted and i followed up on updating PRL/Profile and what not, but i was still in the process of picking a rom for her. i tried to enable wifi, wasnt working, 4G, wasnt working either. i was like wtf? then i got an update for 3.30 somehow and it was like 6mbs. my dumbass installed it, got wifi and eveyrthing to work, but! i lost my recovery and hboot aint pikcking up any PC36IMG file either.
djtoonjr said:
i rooted my sisters white Evo yesterday.i followed up on Hboot 2.02 S-Off Like a Boss! guide, and it worked and everything. it flashed Stock 2.2 Rooted and i followed up on updating PRL/Profile and what not, but i was still in the process of picking a rom for her. i tried to enable wifi, wasnt working, 4G, wasnt working either. i was like wtf? then i got an update for 3.30 somehow and it was like 6mbs. my dumbass installed it, got wifi and eveyrthing to work, but! i lost my recovery and hboot aint pikcking up any PC36IMG file either.
Click to expand...
Click to collapse
Have you tried using Rom Manager to install a recovery?
xNotta said:
Have you tried using Rom Manager to install a recovery?
Click to expand...
Click to collapse
i run rom Manager and get the following screen.
First Screen:
you must root your phone for ROM Manager to function Superuser was not found at "/system/bin/su" or system/xbin/su". Use google search on your computer to find instructions to root your phone.
superuser from the market is installed...
Then i go and click Flash Alternate Recovery(RA Recovery v1.8.0) and it force closes.
Then i try to flash clockwork and it takes a long time too and i get a message An error occured while attempting to run privileged commands.
If the phone downloaded the OTA update for 3.30, as your first post suggests, then it became unrooted and you'll have to root it again.
djtoonjr said:
i run rom Manager and get the following screen.
First Screen:
you must root your phone for ROM Manager to function Superuser was not found at "/system/bin/su" or system/xbin/su". Use google search on your computer to find instructions to root your phone.
superuser from the market is installed...
Then i go and click Flash Alternate Recovery(RA Recovery v1.8.0) and it force closes.
Then i try to flash clockwork and it takes a long time too and i get a message An error occured while attempting to run privileged commands.
Click to expand...
Click to collapse
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Scratch that, I just noticed you don't have a recovery to flash from. :-/
Is your HBoot S-Off?
xNotta said:
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Click to expand...
Click to collapse
i cant get to recovery lol
i go to the bootloader, scans for a PC36IMG file but it donesnt find it, even tho the file is there! lol. maybe i shold format my sdcard. hmm.
but i scroll down to recovery, and it senss me to the default recovery, not clockwork or amen ra. the stock htc recovery. lol.
xNotta said:
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Scratch that, I just noticed you don't have a recovery to flash from. :-/
Is your HBoot S-Off?
Click to expand...
Click to collapse
lmfao. yeah i have S-off.
drmacinyasha said:
If the phone downloaded the OTA update for 3.30, as your first post suggests, then it became unrooted and you'll have to root it again.
Click to expand...
Click to collapse
ive been trying dat but when it comes to the part to flash the first PC36IMG, it doesnt find it, i formatted my sdcard and trying it again.
I am really failing at reading tonight, lol.
Can you boot into the bootloader and use ADB?
Could try ADB Push-ing the files extracted from the Superuser's flashable .zip to their respective locations.
Not sure how that would work out though, never tried it.
Get files "su" from su-2.3.6.1-ef-signed.zip\system\bin
and "Superuser.apk" from su-2.3.6.1-ef-signed.zip\system\app
put both files in the folder with ADB.
open adb command prompt and
Code:
ADB push Superuser.apk /system/app (Press Enter)
ADB push su /system/bin (Press Enter)
Then reboot back into the rom.
You might need to use a file explorer to navigate to /system/app and click Superuser.apk to install it.
(Uninstall old SuperUser from the market before installing.)
Worth a try if no one else has any fixes.
xNotta said:
I am really failing at reading tonight, lol.
Can you boot into the bootloader and use ADB?
Could try ADB Push-ing the files extracted from the Superuser's flashable .zip to their respective locations.
Not sure how that would work out though, never tried it.
Get files "su" from su-2.3.6.1-ef-signed.zip\system\bin
and "Superuser.apk" from su-2.3.6.1-ef-signed.zip\system\app
put both files in the folder with ADB.
open adb command prompt and
Code:
ADB push Superuser.apk /system/app (Press Enter)
ADB push su /system/bin (Press Enter)
Then reboot back into the rom.
You might need to use a file explorer to navigate to /system/app and click Superuser.apk to install it.
(Uninstall old SuperUser from the market before installing.)
Worth a try if no one else has any fixes.
Click to expand...
Click to collapse
OMG! ORGASM! lolwell i didnt try ur method YET, but i formatted sdcard, and it picked up the PC36IMG file. so im re-rooting it against, hopefully trying to re-root it wont fk things up u know. will post bak on progress. thanks alot tho man. i know the last couple of times, couldnt get anyone to help me out lol
djtoonjr said:
OMG! ORGASM! lolwell i didnt try ur method YET, but i formatted sdcard, and it picked up the PC36IMG file. so im re-rooting it against, hopefully trying to re-root it wont fk things up u know. will post bak on progress. thanks alot tho man. i know the last couple of times, couldnt get anyone to help me out lol
Click to expand...
Click to collapse
if you are s-off all you have to do is flash a rooted pc36img in bootloader and then flash a recovery. no need for the entire process again.
t3project said:
if you are s-off all you have to do is flash a rooted pc36img in bootloader and then flash a recovery. no need for the entire process again.
Click to expand...
Click to collapse
lmfao. damn. now u tell me haha.
well i went ahead and re-rooted and got it woking now but thxs for the help.
if PC36IMG isnt getting picked up by boot loader, just format SDCARD and run it again lol
I've been toying around with my new Verizon HTC One (m8) and decided to permroot earlier today (I've had temproot via weaksauce for a month). This took me forever because the only s-off and bootloader unlocker that would work (after hours of trying firewater and HTCdev) was Sunshine. I eventually paid for it and tried to root. I installed CWM at first but didn't realize that Supersu had to be present on my sd-card, so I rebooted. I then flashed TWRP over CWM and tried to root with it instead. Unfortunately, I had downloaded Supersu off the Play Store and (of course) didn't achieve root from the bootloader. That was a few hours ago.
Now I'm stuck with TWRP and no matter what I do, I cannot figure out how to root. I've flashed 3 different versions of Supersu from recovery and none of the zips I install offer me the option to root. I've tried to flash Supersu through adb sideload. I've even tried using ROM manager to reboot and install a copy of Supersu downloaded off my phone's Chrome (probably didn't work because I'm not rooted - it tells me "an error occurred while trying to run privileged commands").
I was under the impression that after installing the Supersu zip from recovery, you would be asked to root either directly after installation or upon rebooting. However, when I reboot, TWRP warns me that "There is no OS installed, are you sure you wish to reboot?" From what I've read, that normally indicates a soft-brick, but my phone is definitely not bricked (yet).
How can I flash Supersu in a way that gives me root?
I'm fairly competent with adb, but nowhere on the internet have I found a problem even remotely similar to mine....
Are you able to boot into twrp and which version do you have? Twrp will automatically ask if you want to install the su binary the first time you reboot from within twrp.
When you reboot you should see the supersu app. All you need do is update it via play store.
harper3663 said:
I've been toying around with my new Verizon HTC One (m8) and decided to permroot earlier today (I've had temproot via weaksauce for a month). This took me forever because the only s-off and bootloader unlocker that would work (after hours of trying
I'm fairly competent with adb, but nowhere on the internet have I found a problem even remotely similar to mine....
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2265618 this is for m7 but works for m8 as well like a charm!
Jyotirdeb said:
Read this: http://forum.xda-developers.com/showthread.php?t=2265618 this is for m7 but works for m8 as well like a charm!
Click to expand...
Click to collapse
I downloaded and installed the Root Kit from recovery. It said install successful, but below that it said "Unable to mount /system." When I rebooted, I still didn't have root and Supersu hadn't downloaded. Do I need to do an ruu and just retry everything?
ashyx said:
Are you able to boot into twrp and which version do you have? Twrp will automatically ask if you want to install the su binary the first time you reboot from within twrp.
When you reboot you should see the supersu app. All you need do is update it via play store.
Click to expand...
Click to collapse
I can boot into twrp, and it's the most recent version from their website (for the Verizon HTC One). For some reason, it didn't ask me to install the su binary the first time I rebooted, and now I don't know how to do it.
harper3663 said:
I downloaded and installed the Root Kit from recovery. It said install successful, but below that it said "Unable to mount /system." When I rebooted, I still didn't have root and Supersu hadn't downloaded. Do I need to do an ruu and just retry everything?
Click to expand...
Click to collapse
Thats why u shouldnt use toolkit.Try an ruu then follow the link i have posted
Hi,
I have ZE551ML. I rooted using method 2 (temporary CWM). Before installing the latest OTA, I did full unroot in SuperSU and uninstalled Xposed. I proceeded with the normal OTA. Upon restart, it was stuck in bootloop. I can get to fastboot and select recovery mode there. My main problem is I can't see the device in ADB. Whenever I type adb devices, I just keep getting "list of devices attached" and my device is nowhere there. I'm pretty sure I have the Intel drivers and ADB tools since I used the same PC in flashing/rooting this device and an older Zenfone 5.
Is there any way I can unbrick my phone. Or is there any way I can fix the ADB not showing my device?
Jaymz123 said:
Hi,
I have ZE551ML. I rooted using method 2 (temporary CWM). Before installing the latest OTA, I did full unroot in SuperSU and uninstalled Xposed. I proceeded with the normal OTA. Upon restart, it was stuck in bootloop. I can get to fastboot and select recovery mode there. My main problem is I can't see the device in ADB. Whenever I type adb devices, I just keep getting "list of devices attached" and my device is nowhere there. I'm pretty sure I have the Intel drivers and ADB tools since I used the same PC in flashing/rooting this device and an older Zenfone 5.
Is there any way I can unbrick my phone. Or is there any way I can fix the ADB not showing my device?
Click to expand...
Click to collapse
maybe u didn't remove xposed framework files, that's the reason for bootloop/brick
Siddk007 said:
maybe u didn't remove xposed framework files, that's the reason for bootloop/brick
Click to expand...
Click to collapse
you mean the modules like greenify?
Jaymz123 said:
you mean the modules like greenify?
Click to expand...
Click to collapse
no, not modules. xposed framework which u installed using installxposedframework.bat from pc
Ok, I was able to recover my phone by flashing the pre-rooted system.img (method 1). I want to sideload the whole stock firmware but my problem remains. If I boot my phone normally, adb devices command shows my phone. But whenever I go to fastboot either by typing adb reboot bootloader or by holding ON/vol up, my phone is not showing up in ADB, therefore I can't sideload anything.
Is there any way I can unroot or revert back to a stock ROM? I'm kind afraid to unroot in SuperSU because I bootlooped yesterday (might have been the xposed though as suggested by Skid). Is there any stock system.img out there?
Jaymz123 said:
Ok, I was able to recover my phone by flashing the pre-rooted system.img (method 1). I want to sideload the whole stock firmware but my problem remains. If I boot my phone normally, adb devices command shows my phone. But whenever I go to fastboot either by typing adb reboot bootloader or by holding ON/vol up, my phone is not showing up in ADB, therefore I can't sideload anything.
Is there any way I can unroot or revert back to a stock ROM? I'm kind afraid to unroot in SuperSU because I bootlooped yesterday (might have been the xposed though as suggested by Skid). Is there any stock system.img out there?
Click to expand...
Click to collapse
Put the update file onto your sd card, rename to MOFD_SDUPDATE.zip.
Reboot and it should update as long as the pre-root image was 19.40.22 .
Reflash TWRP if the bootloader is unlocked and you have a rooted phone with custom recovery...
Yes it works, and yes I did it yesterday exactly like that...
I have a 64gb 2.3ghz 551ML with unlocked bootloader. Don't know if the unlocked bootloader might be the factor that allows this to work...
I just went on and made full unroot from SuperSU. It went smoothly. I guess the one that caused my bootloop was the uinstalled xposed framework.
Bootloader is locked now. The only problem I have now is the ADB thing. My phone is not detected when in recovery but works just fine when normally booted. I have the latest USB driver from Intel and the other one from ASUS. I also have installed ADB installer, the one with the blue screen and where you press Y few times to install.
Hi all,
I hope someone can help as I am at my wits and sanity's end.
I am trying to install twrp into my phone to make a factory backup before rooting. I have unlocked the boot loader via htcdev all OK, I have followed the guide online to install twrp but it just will not work, I have tried various methods and every one of them failed. ADB and fastboot are installed OK, when I type "fastboot devices" it shows the phone and serial number, HTC sync is installed and updated, SDK is installed, everything the guide said to do I have done but it just won't flash. Error when I try to flash twrp every time. It is the latest version etc (I think) the twrp image is in the adb/fastboot folder and the cmd was opened from the folder.
I really don't know what I am doing wrong, can anyone please advise?
Thanks in advance
Gary Nixon
Belaris said:
Hi all,
I hope someone can help as I am at my wits and sanity's end.
I am trying to install twrp into my phone to make a factory backup before rooting. I have unlocked the boot loader via htcdev all OK, I have followed the guide online to install twrp but it just will not work, I have tried various methods and every one of them failed. ADB and fastboot are installed OK, when I type "fastboot devices" it shows the phone and serial number, HTC sync is installed and updated, SDK is installed, everything the guide said to do I have done but it just won't flash. Error when I try to flash twrp every time. It is the latest version etc (I think) the twrp image is in the adb/fastboot folder and the cmd was opened from the folder.
I really don't know what I am doing wrong, can anyone please advise?
Thanks in advance
Gary Nixon
Click to expand...
Click to collapse
are you in bootloader or download mode, you have to be in download mode, what command are you typing to flash recovery.
fastboot flash recovery (name of recovery).img
Yep download mode black screen and that command
i have installed java SE development kit 7 and java 8 update 66 as per the guide
Do i need an SD card in the phone for this as i just saw this mentioned but it wasnt on the guide i was using?
Belaris said:
i have installed java SE development kit 7 and java 8 update 66 as per the guide
Do i need an SD card in the phone for this as i just saw this mentioned but it wasnt on the guide i was using?
Click to expand...
Click to collapse
hmmm, not sure on that one, put one in and see
I think i may know the problem - S-ON - would this prevent anything being flashed?
Have you tried re-downloading TWRP to make sure it isn't a corrupted download?
Belaris said:
I think i may know the problem - S-ON - would this prevent anything being flashed?
Click to expand...
Click to collapse
no, if your bootloader is unlocked you don't need to be s-off to flash recovery. Are you flashing the correct twrp for your phone
2.8.7.1_CPTB-B1-hima.img
its cool i got it to work, next question how do i get the custom rom zip file into the phone
Belaris said:
its cool i got it to work, next question how do i get the custom rom zip file into the phone
Click to expand...
Click to collapse
download it, connect tehphone to pc, move the rom zip to either extsd or internal sd, boot to recovery select the zip and flash.don't forget to make a backup, and to wipe dalvik cache, cache, system,and data,under advanced wipe. nothing else then install the rom
what was causing the problem before, that you couldn't get recovery to flash, just curious
tbh i actually used the m9 toolkit by Squabbi - did it in 5 minutes
donation on the way
Belaris said:
tbh i actually used the m9 toolkit by Squabbi - did it in 5 minutes
donation on the way
Click to expand...
Click to collapse
ok cool, glad you got it going.
Hi all, so I have Verizon's Pixel XL. I have unlocked it successfully and had rooted. I asked on the forums about upgrading the OTA update and was told it was fine. After doing so, I noticed my SuperSU was gone (although I might have lost it earlier and not noticed). So after trying to get it back and keeping getting stuck, I bit the bullet and ADB sideloaded the factory image from google (NDE63X) and got it able to boot up. Yay.
So then I ran the 'adb reboot bootloader' command, then verified my device was connected with 'fastboot devices' and finally I ran 'fastboot boot boot-to-root.img'. And here I am, stuck on the splash screen again.
So I looked around and saw some mentions of people that had used older versions of Chainfire's SuperSU. I tried the newer one (2.78 SR3) and the same thing happened. I do see that there is a SR5, but I also see Chainfire's comment "Do not use the SuperSU ZIP on work-in-progress TWRP releases for Pixel, it will not work - use the model specific links above instead.
I can get it to run just fine without using chainfire's supersu...but then I don't have the supersu app or any real gains from having rooted.
So, I feel like I must be doing something wrong. Any suggestions?
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
cam30era said:
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
Click to expand...
Click to collapse
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
smokeydriver said:
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
Click to expand...
Click to collapse
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
cam30era said:
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
Click to expand...
Click to collapse
The OTA update I took only got me to a new version of 7.1, not 7.1.1 (from NDE63P to NDE63X). It still shows an available update to 7.1.1 which I have *not* done.
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Nitemare3219 said:
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Click to expand...
Click to collapse
I've tried, but keep getting an error 21 code that it can't install...I tried this with SR5 and SR2.
How I Rooted
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb boot.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
Ok, I must be doing something wrong on a very basic level. It gave me error 21 (signature verification error) when trying to use the unified android tookit to install 7.1. Anyways, I'll just move on and skip that step and see what happens.
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Dees_Troy said:
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Click to expand...
Click to collapse
FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
I transferred those 2 files to my download folder on my phone, ran the twrp.img script, and then when I go in...the file names are not normal. Everything is random letters and numbers. Again, I feel like I'm making some stupid basic mistake that I don't understand (and I've rooted plenty of phones).
spotmark said:
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Click to expand...
Click to collapse
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
smokeydriver said:
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
Click to expand...
Click to collapse
You have TWRP RC1 installed?
spotmark said:
You have TWRP RC1 installed?
Click to expand...
Click to collapse
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Ah, I see. I misunderstood. I thought you were just under the impression that you couldn't flash SU with RC1. My apologies.
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
toknitup420 said:
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
Click to expand...
Click to collapse
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
smokeydriver said:
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
Click to expand...
Click to collapse
Never mind...it's my 4 digit password that's used when my finger unlock doesn't work. Ugh- I knew it was something simple and dumb I was doing!
smokeydriver said:
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
Click to expand...
Click to collapse
Can I ask you how you fixed this? I'm having the same issue and this post popped up on Google.