I have an MDK S4. I have been running beanstown's rom for months with TWRP 2.5.0.2 with no issues. Today I decided to flash clockworkmod touch recovery in terminal emulator using the following command:
su
dd if=/sdcard/ recovery-clockwork-touch-6.0.4.4-jfltevzw.img of=/dev/block/mmcblk0p21
So now my phone won't boot at all. All I get is a screen that says:
Secure fail: kernel
System software not authorized by Verizon Wireless has been found on your phone...
UGH!!!! So now what? Do I need to do the following or is there another way around it?
http://forum.xda-developers.com/showthread.php?t=2301259
Please advise asap. Thanks.
mochamoo said:
I have an MDK S4. I have been running beanstown's rom for months with TWRP 2.5.0.2 with no issues. Today I decided to flash clockworkmod touch recovery in terminal emulator using the following command:
su
dd if=/sdcard/ recovery-clockwork-touch-6.0.4.4-jfltevzw.img of=/dev/block/mmcblk0p21
So now my phone won't boot at all. All I get is a screen that says:
Secure fail: kernel
System software not authorized by Verizon Wireless has been found on your phone...
UGH!!!! So now what? Do I need to do the following or is there another way around it?
http://forum.xda-developers.com/showthread.php?t=2301259
Please advise asap. Thanks.
Click to expand...
Click to collapse
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
k1mu said:
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Thank you. My s4 is rooted. I *think* that I have solved my issue. I was able to get it to go into Odin mode power+vol down. I didn't connect to a computer (am at work and all of my android tools are at home). I just cancelled out of Odin mode and it booted up just fine. Now I tried to go into recovery again and got the same error as above and was able to get out of it the same way. I was able to go into ROM manager and flash regular non-touch CWM recovery and was able to boot to it without issue.
I suspect that my flash of the touch via terminal emulator didn't work right. Can anyone who has done it this way let me know how long the flash should take? I was at the su prompt and entered the dd line above (copy and pasted to avoid typos). It appeared to do something...there were some numbers maybe 5 or 6 per line and then it went back to the prompt so thought it was done. This didn't take it more than about 15 seconds to do. What should I see here?
I know that I can just flash it via ROM manager but wanted to be able to do it myself without rom manager and also be able to flash the latest twrp img if I want to (goo.im seems broken at the moment). Maybe I will try to do it via Odin later.
TIA.
you rock
I just got this same error and your steps worked perfect
Same problem except on i545vrufnk1
k1mu said:
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Hello, I went to flash a recovery package with flashify and got the black screen with kernel fail. I was on the latest nk1 kernel.
please help
Hi! I'm really sorry to revive such an ancient thread but I've a similar problem.
I tried to use the dd command to update TWRP and wound up at this spot, but I was running a custom 5.1.1 system (jflte dev something or other from oct 2014 - recovery needed to be updated in order to install 7.1.1). So I tried to ODIN back to the old bootloader because I read it may have just become locked again, and now the system seems broken or missing, I'm not sure which. Phone no longer boots into the system and I get this error at recovery, so I'm hoping that if I flash an older factory image onto the phone, it'll restore it.
My question is, if I flash a stock image onto the phone, will it overwrite the bootloader and make my custom recovery dreams impossible? I went as far as to transplant the insides of this phone into a replacement when it first broke to maintain my MDK bootloader, so I'm really hoping I didn't **** myself here.
----
Edit:
So I've fixed my phone! The whole ordeal wasn't too too bad, but it was somewhat time consuming and difficult to divine on my own.
Now, I realize now I may have actually flashed the wrong .img file, which may have caused this whole issue. I'm actually not certain, because through the method that I fixed this problem with, I was able to flash what I would later find out was an incorrect .img for the recovery (jfltexx instead of jfltevzw ) but it did work properly, and I only found out when I got an error on trying to install the LineageOS zip.
I tried a bunch of things, but the one that worked was converting a twrp .img file to a .lok (loki) file. At the time of this writing, it happens that there's a bug in the latest twrp version that also prevents you from installing the system, but downgrading back to an older version will work, and I assume after 3.1.2 the bug will be fixed.
In order to do this, I wiped the system back to an MDK 4.2.2 system image I found here: https://forum.xda-developers.com/showthread.php?t=2301259
(dead link? Here's an archive: https://archive.is/LDnaY - I hit a bunch of dead links when I was figuring this process out and it was frustrating)
which preserved the mdk bootloader (because flashing anything newer than this will lock the bootloader, I've been told. I didn't dare try.)
I rooted that image by downgrading to the prerelease kernel and using motochopper to root, then upgraded back to the mdk kernel.
Then I grabbed the loki_tool from this thread:
https://forum.xda-developers.com/lg-g2/general/guide-how-to-flash-cwm-6-0-4-4-lokitool-t2813514
(Dead link? Here's an archive: https://archive.is/F7k29 )
and used a twrp .img file to create the recovery.lok file
Flashing through this method restored my custom recovery, and also made the samsung unlocked padlock bootscreen go away (I miss it already!). Having Android 7.1.2 on this phone is quite a treat though!
Hope that anyone else who winds up here in the future finds this useful! And I hope those links
Related
I'm trying to get into the bootloader to flash an older version of TWRP. I'm holding various combinations of buttons down when rebooting but the phone either goes to Recovery, Odin, or normal boot. The "bootloader" boot option in TWRP doesn't work either, it just goes to normal boot. What am I missing? I know for many phones the bootloader is accessed by holding VOL Down + Power when rebooting but that's not working on the Note 2.
Thanks.
slicknick27 said:
I'm trying to get into the bootloader to flash an older version of TWRP. I'm holding various combinations of buttons down when rebooting but the phone either goes to Recovery, Odin, or normal boot. The "bootloader" boot option in TWRP doesn't work either, it just goes to normal boot. What am I missing? I know for many phones the bootloader is accessed by holding VOL Down + Power when rebooting but that's not working on the Note 2.
Thanks.
Click to expand...
Click to collapse
I believe the reason why you can't boot into bootloader is because it has something to do with the Unlock Bootloader method/exploit. I'm going to take a shot in the dark and say the exploit is not the standard unlock method so therefore you can't boot into the bootloader.
Also, you can flash a recovery a different way. Download the Goo.im Manager app in the Google Play Store and when you go in the app, you can search the recoveries and it will flash them from the app for you.
DroidOnRoids said:
I believe the reason why you can't boot into bootloader is because it has something to do with the Unlock Bootloader method/exploit. I'm going to take a shot in the dark and say the exploit is not the standard unlock method so therefore you can't boot into the bootloader.
Also, you can flash a recovery a different way. Download the Goo.im Manager app in the Google Play Store and when you go in the app, you can search the recoveries and it will flash them from the app for you.
Click to expand...
Click to collapse
Hey, thanks for shedding some light on this. And I'm going to try flashing from the Goo.im manager, that sounds easier at this point, too.
slicknick27 said:
Hey, thanks for shedding some light on this. And I'm going to try flashing from the Goo.im manager, that sounds easier at this point, too.
Click to expand...
Click to collapse
No problem, man. Just make sure you flash the right recovery file because if you are broad on your search, it will give you a list of different recoveries for different devices. Search the version of TWRP you want with 'i605'.
DroidOnRoids said:
No problem, man. Just make sure you flash the right recovery file because if you are broad on your search, it will give you a list of different recoveries for different devices. Search the version of TWRP you want with 'i605'.
Click to expand...
Click to collapse
Unfortunately there are no older versions of TWRP in the Goo.im manager app. This is off-topic from my original question but it's the reason I was trying to get into the bootloader in the first place. Do you know of any way to downgrade TWRP to a previous version on this phone other than the flashing from bootloader method?
slicknick27 said:
Unfortunately there are no older versions of TWRP in the Goo.im manager app. This is off-topic from my original question but it's the reason I was trying to get into the bootloader in the first place. Do you know of any way to downgrade TWRP to a previous version on this phone other than the flashing from bootloader method?
Click to expand...
Click to collapse
Hm, you searched with i605, right? Well, I searched and found that on Goo.im, it is actually t0ltevzw.
Here are all the TWRP builds for the VZW Note 2 from Goo.im: http://goo.im/devs/OpenRecovery/t0ltevzw/
EDIT: Here's our device page on the TWRP website: http://teamw.in/project/twrp2/133
EDIT 2: If I were you, try not to flash a recovery using Odin. I wouldn't risk screwing up the unlocked bootloader exploit. Lastly, if you didn't know, do NOT in any way flash a custom rom using Odin. It's bad news for your phone.
Edited again because I forgot fastboot requires bootloader access lol
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
DroidOnRoids said:
Hm, you searched with i605, right? Well, I searched and found that on Goo.im, it is actually t0ltevzw.
Here are all the TWRP builds for the VZW Note 2 from Goo.im: http://goo.im/devs/OpenRecovery/t0ltevzw/
EDIT: Here's our device page on the TWRP website: http://teamw.in/project/twrp2/133
EDIT 2: If I were you, try not to flash a recovery using Odin. I wouldn't risk screwing up the unlocked bootloader exploit. Lastly, if you didn't know, do NOT in any way flash a custom rom using Odin. It's bad news for your phone.
Edited again because I forgot fastboot requires bootloader access lol
Click to expand...
Click to collapse
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
slicknick27 said:
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
Click to expand...
Click to collapse
So the 2.4.0.0 is the version you want, correct? And which file of this recovery version did you download? If you tried downloading and installing using the Goo.im app, try downloading the zip file from your computer and transferring it over to your SD Card. From there you can reboot to the existing recovery, install it, and reboot the recovery.
If that doesn't work either, tell me and I can figure out a different option.
DroidOnRoids said:
So the 2.4.0.0 is the version you want, correct? And which file of this recovery version did you download? If you tried downloading and installing using the Goo.im app, try downloading the zip file from your computer and transferring it over to your SD Card. From there you can reboot to the existing recovery, install it, and reboot the recovery.
If that doesn't work either, tell me and I can figure out a different option.
Click to expand...
Click to collapse
Actually, if I can I'd like to downgrade to TWRP 2.3.3.1, which was the version I installed back when I got the phone in December.
On Goo.im web site it is:
openrecovery-twrp-2.3.3.1-t0ltevzw.zip
It is my understanding though that you can't flash TWRP from within TWRP?
slicknick27 said:
Actually, if I can I'd like to downgrade to TWRP 2.3.3.1, which was the version I installed back when I got the phone in December.
On Goo.im web site it is:
openrecovery-twrp-2.3.3.1-t0ltevzw.zip
It is my understanding though that you can't flash TWRP from within TWRP?
Click to expand...
Click to collapse
You can flash CWM in TWRP, TWRP in CWM, TWRP in TWRP, or CWM in CWM. All you need to do is flash it and then go to the recovery options and hit Reboot Recovery.
Where did you hear that you can't flash TWRP in TWRP?
DroidOnRoids said:
You can flash CWM in TWRP, TWRP in CWM, TWRP in TWRP, or CWM in CWM. All you need to do is flash it and then go to the recovery options and hit Reboot Recovery.
Where did you hear that you can't flash TWRP in TWRP?
Click to expand...
Click to collapse
OK, yeah, I was told in another thread that I couldn't flash TWRP with TWRP.
So, I just want to clarify, I can flash an older version of TWRP over an newer version of TWRP already installed -- as if I was flashing any regular .zip?
slicknick27 said:
OK, yeah, I was told in another thread that I couldn't flash TWRP with TWRP.
So, I just want to clarify, I can flash an older version of TWRP over an newer version of TWRP already installed -- as if I would flash any regular .zip?
Click to expand...
Click to collapse
Yes, you can do that because it's going to completely overwrite the other version of TWRP. It doesn't matter what version you flash because it's going to be all on its own. The previous recovery doesn't benefit from a newer version of a recovery. You're safe to do it
EDIT: When I had my Galaxy Nexus, TWRP was brand spanking new so I had to downgrade a lot because of all the bugs presented in the later releases.
DroidOnRoids said:
Yes, you can do that because it's going to completely overwrite the other version of TWRP. It doesn't matter what version you flash because it's going to be all on it's own. The previous recovery doesn't benefit from a newer version of a recovery. You're safe to do it
EDIT: When I had my Galaxy Nexus, TWRP was brand spanking new so I had to downgrade a lot because of all the bugs presented in the later releases.
Click to expand...
Click to collapse
Phew. OK. Well again I thank you for sticking with me and clearing this up. I suspected I could do that in the first place but was confused by information I was given otherwise. Off I go to recovery!
slicknick27 said:
Phew. OK. Well again I thank you for sticking with me and clearing this up. I suspected I could do that in the first place but was confused by information I was given otherwise. Off I go to recovery!
Click to expand...
Click to collapse
Good luck! Let me know when it's a success.
DroidOnRoids said:
Good luck! Let me know when it's a success.
Click to expand...
Click to collapse
Well, TWRP verified the checksum and the modem installed successfully. But apparently it turns out the problem was not as it originally seemed.
When I downloaded the older version of TWRP, I opened its .MD5 file again just to check, and I noticed that the .MD5 files for the zips on Goo.im (or at least OpenRecovery's ZIPS) omitted the asterisk that precedes the filename:
Code:
d4624c4f8c9427b6137b2b97902e76b3 openrecovery-twrp-2.4.1.0-t0ltevzw.zip
Whereas with other .MD5 files that I've created (including the .MD5 file for the modem zip that was failing verification in TWRP), I've used an asterisk before the filename:
Code:
d4624c4f8c9427b6137b2b97902e76b3 [B][COLOR="Red"]*[/COLOR][/B]openrecovery-twrp-2.4.1.0-t0ltevzw.zip
So after the modem flashed successfully on TWRP 2.3, I decided to try flashing it again (with the asterisk omitted from the MD5 file) on the latest TWRP 2.4.1.0. It flashed just fine. So the issue seems to be TWRP getting hung up on the asterisk that precedes the filename in MD5 files -- though this doesn't happen all the time because I've flashed many MD5 files with the asterisk successfully.
A bug in TWRP? Or maybe I shouldn't be using the asterisk at all. In any case, I'm back on TWRP 2.4.1.0 with the modem flashed.
EDIT: And I learned that you can flash TWRP in TWRP
slicknick27 said:
Well, TWRP verified the checksum and the modem installed successfully. But apparently it turns out the problem was not as it originally seemed.
When I downloaded the older version of TWRP, I opened its .MD5 file again just to check, and I noticed that the .MD5 files for the zips on Goo.im (or at least OpenRecovery's ZIPS) omitted the asterisk that precedes the filename:
d4624c4f8c9427b6137b2b97902e76b3 openrecovery-twrp-2.4.1.0-t0ltevzw.zip
Whereas with other .MD5 files that I've created (including the .MD5 file for the modem zip that was failing verification in TWRP), I've used an asterisk before the filename:
d4624c4f8c9427b6137b2b97902e76b3 *openrecovery-twrp-2.4.1.0-t0ltevzw.zip
So after the modem flashed successfully on TWRP 2.3, I decided to try flashing it again (with the asterisk omitted from the MD5 file) on the latest TWRP 2.4.1.0. It flashed just fine. So the issue seems to be TWRP getting hung up on the asterisk that precedes the filename in MD5 files -- though this doesn't happen all the time because I've flashed many MD5 files with the asterisk successfully.
A bug in TWRP? Or maybe I shouldn't be using the asterisk at all. In any case, I'm back on TWRP 2.4.1.0 with the modem flashed.
EDIT: And I learned that you can flash TWRP in TWRP
Click to expand...
Click to collapse
I would bring that to their attention and see why that's the case on their recovery. Anyway, glad that everything is figured out and running perfectly. :good:
DroidOnRoids said:
I would bring that to their attention and see why that's the case on their recovery. Anyway, glad that everything is figured out and running perfectly. :good:
Click to expand...
Click to collapse
Yes I'm going to report it.
Take it easy.
Really didn't want to make a new thread about this but honestly people just jumped to conclusions without being helpful in my previous thread.
Long story short I'm trying to manually get 4.4.2: http://forum.xda-developers.com/showthread.php?t=2664561
I saw that I needed to get s-off, which requires root. Bootloader was already unlocked and so did everything here: http://forum.xda-developers.com/showthread.php?t=2273376
I installed CWM. It said to install a superuser tool so I installed SuperSU.
"You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead." was the next line. <-- I saw that message. Installed a kernel that he recommended: http://forum.xda-developers.com/showthread.php?t=2255900
After reboot I get SuperSU error: There is no SU binary installed and SuperSU cannot install it. If you just upgraded to Android 4.3, you need to manually re-root- consult the relevant forums for your device etc.
Can anyone help me get the proper SU Binary installed? Not a beginner to rooting as I've had had several previous phones before. Never encountered something as annoying as this.
On 4.3, 3.17.502.3.
I had the same issue when I installed 4.4.2 on my international One.
What I done to root was;
- downloaded SuperSU v1.80 zip from here.
- download SuperSu from the Play Store
- in SuperSU, select the option to install binaries via TWRP/CWM. (If it doesn't reboot to recovery, manually enter recovery)
- flash the supersu v1.80 zip and reboot
- open SuperSu and install the binaries using the normal option.
That then enabled my root. I'd tried quite a few different variations and this was the only method that worked for me.
Sent from my HTC One or Note 3 via XDA Premium 4
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
mch277 said:
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
Click to expand...
Click to collapse
You seem very confused about the whole rooting process ... what was the point in flashing the stock recovery ? Are you trying to install the OTAPkg.zip ?
what Rom are you wanting to install and whats flashing stock recovery have to do with it ?
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
mch277 said:
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
Click to expand...
Click to collapse
I wrote the thread you linked too
http://forum.xda-developers.com/showthread.php?t=2659374
and yes it is necessary to have stock recovery to take an OTA, but your post didn't mention taking OTA it said you had no SU installed.
to get into stock recovery
boot to bootloader
choose recovery
wait for black screen, hold vol up and then power
you will see something about sdcard fail .. ignore it till the menu comes up
then choose to flash OTAPkg.zip from sdcard
Feel free to haze me for what I'm sure is a stupid question.
After flashing the factory 5.1.1 image, is the Chainfire root method still the correct way to root? The 'fastboot flash boot' part made me wonder if it needs to be updated for the bootloader that shipped with the 5.1.1 image.
funkybside said:
Feel free to haze me for what I'm sure is a stupid question.
After flashing the factory 5.1.1 image, is the Chainfire root method still the correct way to root? The 'fastboot flash boot' part made me wonder if it needs to be updated for the bootloader that shipped with the 5.1.1 image.
Click to expand...
Click to collapse
Wrong question.
There is no "correct" or "incorrect" method. FWIW, it's a Nexus device. You don't need these automated tools. Just fastboot flash the TWRP image, boot to recovery and flash the latest SuperSU zip from recovery. Done.
cam30era said:
Wrong question.
There is no "correct" or "incorrect" method. FWIW, it's a Nexus device. You don't need these automated tools. Just fastboot flash the TWRP image, boot to recovery and flash the latest SuperSU zip from recovery. Done.
Click to expand...
Click to collapse
Thanks but that wasn't really my question and I hadn't planned to use the auto-root CF version. To clarify what I'm confused about: The manual CF Root process involves a step "fastboot flash boot {img}", and when checking the CF repository I see that this boot image was based on 5.0.x. From other threads I had understood the 5.1.1 factory image includes a new bootloader image, and this made me wonder if flashing the bootloader that ships with the chainfire root package would be a potential problem. I'm still curious about this, but now also:
Your response suggests I could avoid CF altogether if I'm willing to flash a non-stock recovery. Is that correct?
yeah I would skip CF and just do it the manual way. copy SuperSU to your device first.
@funkybside,
No. Flash all of the stock .img files except recovery. Fastboot flash TWRP.img instead. Then boot to recovery from fastboot on your device and flash the SuperSU.zip.
Alternatively, if you want to keep the stock recovery, you can
fastboot boot recovery "name of TWRP.img". Then flash the SuperSU.zip.
y2whisper said:
yeah I would skip CF and just do it the manual way. copy SuperSU to your device first.
Click to expand...
Click to collapse
That's the part that generated my question. Inside the SuperSU.zip are inject.img and patched.img. The readme states patched.img needs flashed with 'fastboot flash boot patched.img', and the package was made before the 5.1.1 drop. For all I know it's fine to do this, but since it's flashing a boot image I figured better safe than sorry and decided to post. I have searched here and all root threads/links seem pointed to videos using toolkits/CF-AutoRoot so I wasn't comfortable with following them. FWIW - At the moment I'm stock factory 5.1.1 image, stock recover, unlocked BL, not rooted.
Trying to be a self sufficient as I can...quickly becoming 'that guy'. ugh. The core question is does the patched.img inside SuperSU.zip cause any problems with a factory 5.1.1 unlocked device, due to potential differences between the factory 5.1.1 boot image and the one included in SuperSU.zip.
No you're just learning. I rooted my after without problems but I wonder if a new version will be done now that 5.1.1 is done for the N9
funkybside said:
That's the part that generated my question. Inside the SuperSU.zip are inject.img and patched.img. The readme states patched.img needs flashed with 'fastboot flash boot patched.img', and the package was made before the 5.1.1 drop. For all I know it's fine to do this, but since it's flashing a boot image I figured better safe than sorry and decided to post. I have searched here and all root threads/links seem pointed to videos using toolkits/CF-AutoRoot so I wasn't comfortable with following them. FWIW - At the moment I'm stock factory 5.1.1 image, stock recover, unlocked BL, not rooted.
Trying to be a self sufficient as I can...quickly becoming 'that guy'. ugh. The core question is does the patched.img inside SuperSU.zip cause any problems with a factory 5.1.1 unlocked device, due to potential differences between the factory 5.1.1 boot image and the one included in SuperSU.zip.
Click to expand...
Click to collapse
SuperSU is not device specific. 2.46 works fine on 5.1 on Nexus 6. I doubt the changes between 5.1 and 5.1.1 are significant enough to require a new version.
i use CF SuperSU Root Tool
1. Extract the earlier downloaded CF Auto zip folder on your computer.
2. Enable Developer Options on Nexus 9: in the About Device > tap Build Number multiple times until you see the new tab Developer Options. In here, check Enable OEM Unlock and USB Debugging.
3. Enter the Bootloader mode from your computer by running this command (open command prompt with Shift + Right Click > Open the command window here), adb reboot bootloader
4. Execute the root file,
Windows: run root-windows-bat
OS X: chmod +x root-mac.sh
run root-mac.sh
Linux: chmod +x root-linux.sh
run root-linux.sh
Once the command window finishes executing, your Nexus 9 will reboot.
Thanks to all of you. I guess I stop worrying and just give it a go. It seems like anyone who's had experience rooting 5.1.1 has not had any concerns or problems related to SuperSU.zip's patched.img being listed with a 5.0.x version on the CF site.
/me crosses fingers.
Edit: IT'S ALIVE! Thanks again folks.
In case anybody stumbles onto this thread, you might as well go with the "autoroot" method. Autoroot is smart enough to adapt to new boot images, and does not require installation of a custom recovery. What it is essentially, IS a custom recovery bundled with the root bits.
You "fastboot boot autoroot.img" the device. It loads the autoroot.img to memory, and executes it, and installs the internal root bits to the /system partition.
Also note: With a Nexus device, it is NEVER necessary to INSTALL a custom recovery image, since you can RUN a custom recovery image without actually installing it.
fastboot boot bootable.img
doitright said:
In case anybody stumbles onto this thread, you might as well go with the "autoroot" method. Autoroot is smart enough to adapt to new boot images, and does not require installation of a custom recovery. What it is essentially, IS a custom recovery bundled with the root bits.
You "fastboot boot autoroot.img" the device. It loads the autoroot.img to memory, and executes it, and installs the internal root bits to the /system partition.
Also note: With a Nexus device, it is NEVER necessary to INSTALL a custom recovery image, since you can RUN a custom recovery image without actually installing it.
fastboot boot bootable.img
Click to expand...
Click to collapse
I would only disagree on one point. This is fine as long as the user understands how to use ADB and fastboot, and how to get out of trouble if something goes wrong. We've seen too many inexperienced users get into trouble with automated tools who don't have the SDK installed on their PC and don't understand how to install drivers.
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
ganiman said:
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
Click to expand...
Click to collapse
Your understanding of TWRP is right. Basically, we dd the twrp image with OS 4.5.3 bootloaders (the only bootloaders that will boot unsigned recovery) and then before leaving TWRP flash back (almost) current bootloaders and recovery.
You should be able to adb-sideload the OS 5.1.2 update to fix the freeze. Was device rooted before it updated? Do you know what OS it was on? If you have adb access while device is frozen, run these commands for current OS info:
adb shell getprop ro.build.version.fireos
adb shell getprop ro.build.version.number
No CM12 available. Mostly-working CM11 is here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138
BTW, I assume you tried wiping cache and/or factory reset in recovery. If not, I'd do that first.
I am trying to flash TWRP on 10B (was running 23C and did KDZ flash back to 10B). Rooted via Stump, installed BusyBox, TWRP Mananger and Official TWRP App. Since TWRP didn't appear to install TWRP I did some more research I read people had success with 'Partitions Backup' to backup stock recovery partition and then use 'Flashify' to install TWRP. So I downloaded the twrp-3.0.2-0-vs985.img and installed that to recovery after backing up stock. Next reboot takes me into TWRP. If I then boot normally and then shutdown and enter recovery again I'm back in stock recovery. So it's like the flash is temporary.
Anybody care to educate me about what I am doing wrong. I'm sure this was easier in the days of the 'all-in-one' root/TWRP installer but can't download that anymore and I'm tired of the updates and poor performance so want to try custom ROM's.
Any help would be appreciated. I am thinking maybe I need to install recovery again when booted into TWRP? Not sure.
I am wondering if the flash doesn't work because I flashed a TWRP img without the "bump" designation? I am beginning to think the best way to install reliably is using the 'dd' command from adb over remote PC connection (or via su in a terminal shell if advisable)? Any thoughts on using this method and whether I can go right to the latest version of TWRP for the vs985 (twrp-3.0.2-0-vs985.img).
skay said:
I am wondering if the flash doesn't work because I flashed a TWRP img without the "bump" designation? I am beginning to think the best way to install reliably is using the 'dd' command from adb over remote PC connection (or via su in a terminal shell if advisable)? Any thoughts on using this method and whether I can go right to the latest version of TWRP for the vs985 (twrp-3.0.2-0-vs985.img).
Click to expand...
Click to collapse
I think you might have solved your own problem! You can't use just any TWRP image. It has to be specifically bumped for the G3.
iBolski said:
I think you might have solved your own problem! You can't use just any TWRP image. It has to be specifically bumped for the G3.
Click to expand...
Click to collapse
Thanks for the reply iB. I only tried flashing with the VS985 img files. But I didn't start with one that specifically had the "bump" or "bumped" designation in the filename. I am wondering if the later version that I used doesn't actually install bump to recovery but it intended to be installed as an updated version of TWRP on a previously "bumped" recovery image? Sorry for getting into the weeds here but I actually just stayed rooted on 23C for quite a while until I couldn't take it anymore. I looked at moving up to G4, G5, V10 and V20 but it seems like the G3 is the best value LG phone for custom ROMs and hardware is still not bad overall.
Anyone know of a way to determine if recovery has been flashed with TWRP img before attempting 'factory reset' option? I based my questions thus far on the assumption that if it flashed successfully I would see only the 'factory reset' and 'reboot' options in the new recovery, but I see all 5 options as before flashing TWRP.
skay said:
Anyone know of a way to determine if recovery has been flashed with TWRP img before attempting 'factory reset' option? I based my questions thus far on the assumption that if it flashed successfully I would see only the 'factory reset' and 'reboot' options in the new recovery, but I see all 5 options as before flashing TWRP.
Click to expand...
Click to collapse
It's been a long time (over a year) since I last used TWRP on my G3 (which is now in the cell phone cemetery as it died last December), but I believe if you boot normally, hook your phone to your PC and use adb reboot-recovery, it SHOULD go straight into TWRP, but I could be wrong. Otherwise, factory reset is the only way to get to it. The normal "recovery" screen shows up first, from what I remember and you have to go that route to get to TWRP. You should always, always back up your phone whenever doing things like this anyways. I don't know if there is a way to "verify" that it is installed, so once again, backup everything first. Just in case.
Thanks for the help and the confirmation that the standard recovery is expected once it's installed. Based on videos I expected something different. But I tried it after backing up and it works fine. Now time to flash!!