**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca. If you like his work, please make him a small donation for encouragement.
2. This is a systemless root. Yet you need to unlook Lollipop before upgrading to Marshmallow.
3. Flashing the attached SuperSU file modifies stock boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** to unroot before upgrading to official Android 6.0.
Root:
1. Unlock your device in Lollipop, then upgrade to Android 6.0
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. This TWRP is recommended.
HTML:
adb reboot-bootloader
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp. /OR install the SuperSU in twrp if you saved it in device storage.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Unroot:
Just flash back stock boot.img
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: Download Xposed Installer here
Downgrade to Lollipop:
In case you need to downgrade to Lollipop, follow the instructions with care. Do it at your risk.
Refer to Asus Zentalk Forum and grab the required files from there.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot reboot-bootloader
Now you are back in Lollipop. You can flash back stock recovery(.184 recommended), wipe the device(cache/userdata/system) and then sideload back stock LP or MM as you wish. OR, you can flash custom recovery/boot/system.img start from here.
Good luck!
It worked!Thank you master!I bow now....
I just need root on 6.0.1. Is this going to achieve that?
MikeyLee said:
I just need root on 6.0.1. Is this going to achieve that?
Click to expand...
Click to collapse
According to op it will
Sent from my ASUS_Z00AD using Tapatalk
It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.
pokey006 said:
It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.
Click to expand...
Click to collapse
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?
samcjtsai said:
1. All credits go to @shakalaca and I just try to recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum but, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Works like a charm !! Thanks !!
kamyk70 said:
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?
Click to expand...
Click to collapse
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
when update to 6.0. bootloader unlocked again ! how can i flash twrp ?
pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
No it does not
Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thank You for explaining that to me, appreciated!
To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.
euthic said:
To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.
Click to expand...
Click to collapse
You need to adb sideload all LP .184 images first then use Asus FlashTool to flash RAW Firmware.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
root works perfect along with systemless xposed, but i still cant pass safenet check..(super su disabled, and also xposed) so no AP.. is that normal ?
pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well
ponhei9502 said:
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well
Click to expand...
Click to collapse
Guess your ZF2 is not unlocked in LP first, so that you can't see twrp booting. Since you are in Android 6.0 now, try to downgrade to LP, Unlock it, upgrade to 6.0 and then root.
samcjtsai said:
**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca and I just recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Where are these files again? They aren't in the zip
thanks, works great, was able to downgrade to lollipop with no problem what so ever. Install twrp, gain root again, and rockin custom roms...
Related
I've seen posts requesting "how to" and posts of problems attempting to root after installing the 5.1 OTA update. This post outlines the steps to root with an UNLOCKED BOOTLOADER.
NOTE: This will only work if your bootloader is already unlocked. It is based on -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 but slightly updated.
Don't know if your bootloader can be unlocked? see -> HERE
Requirements...
the latest TWRP fastboot IMG file (Alternate Link) UPDATE: There is an issue with TWRP 2.8.7.0 (SEE THIS POST Thanks @jodaboda ). Please use TWRP 2.8.6.0 for now!
the latest Installable ZIP of SuperSU (Alternate: http://download.chainfire.eu/supersu )
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools will likely work, but Moto's fastboot is always suggested!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The steps...
NOTE: replace TWRP.IMG in the below steps, with the name of the file you downloaded!! Example: twrp-2.8.6.0-ghost.img
NOTE: failure to perform these steps EXACTLY as written can result in the apparence of the Android in distress (logo with Exclamation mark) with the caption "No Command" and the inability to enter recovery, OR it will enter STOCK recovery even though you have flashed TWRP!
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you downloaded your TWRP.IMG file.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery TWRP.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device should enter TWRP.
If your device is not rooted, TWRP may prompt you to root now or install SuperSU. Do it.
Use the menu options to Reboot to system.
You will likely be prompted to UPDATE SuperSU. Please update it, and reboot.
IF TWRP doesn't prompt you to root/install SuperSU.... (more exact instructions coming later...)
With your phone booted normally, connect it via USB cable to your PC.
Drag/Drop the SuperSU.zip you downloaded onto the phone's internal storage
Reboot the phone into TWRP
Use the menu option to install zip, navigate to and select the SuperSU zip.
Boot to System.
EDIT: 9-17-2015 edited first TWRP link.
KidJoe said:
I've seen posts requesting "how to" and posts of problems attempting to root after installing the 5.1 OTA update. This post outlines the steps to root with an UNLOCKED BOOTLOADER.
NOTE: This will only work if your bootloader is already unlocked. It is based on -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 but slightly updated.
Don't know if your bootloader can be unlocked? see -> HERE
Requirements...
the latest TWRP fastboot IMG file (Alternate Link)
the latest Installable ZIP of SuperSU (Alternate: http://download.chainfire.eu/supersu )
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools will likely work, but Moto's fastboot is always suggested!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The steps...
NOTE: replace TWRP.IMG in the below steps, with the name of the file you downloaded!! Example: twrp-2.8.6.0-ghost.img
NOTE: failure to perform these steps EXACTLY as written can result in the apparence of the Android in distress (logo with Exclamation mark) with the caption "No Command" and the inability to enter recovery, OR it will enter STOCK recovery even though you have flashed TWRP!
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you downloaded your TWRP.IMG file.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery TWRP.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device should enter TWRP.
If your device is not rooted, TWRP may prompt you to root now or install SuperSU. Do it.
Use the menu options to Reboot to system.
You will likely be prompted to UPDATE SuperSU. Please update it, and reboot.
IF TWRP doesn't prompt you to root/install SuperSU.... (more exact instructions coming later...)
With your phone booted normally, connect it via USB cable to your PC.
Drag/Drop the SuperSU.zip you downloaded onto the phone's internal storage
Reboot the phone into TWRP
Use the menu option to install zip, navigate to and select the SuperSU zip.
Boot to System.
Click to expand...
Click to collapse
I still haven't unlocked my Bootloader (being on 5.1). In the linked post it's been mentioned that "TWRP custom recovery for KitKat" - my question is, is there a TWRP Custom Recover for OTA 5.1 update? And I'm on XT1052, same procedure follows?
Do you know where I can find mfastboot for Mac OSX?
kidjoe, your a priceless resource!
i installed an older verison of twrp and had all the issues you speak off, installed 2.8.6 with success but would not root upon reboot, installed the super su zip in op via twrp, one last thing i had to enter the super su app and tap enable superuser and now all is good:good::good
Thanks, worked like a charm
Thanks.. It's been ages since I used I last used adb commands and flashed something. I couldn't figure out how to boot into recovery.
Vampirexox said:
I still haven't unlocked my Bootloader (being on 5.1). In the linked post it's been mentioned that "TWRP custom recovery for KitKat" - my question is, is there a TWRP Custom Recover for OTA 5.1 update? And I'm on XT1052, same procedure follows?
Click to expand...
Click to collapse
twrp-2.8.6.0-ghost.img works on Lollipop too. (just used it last night on my sister-in-law's GSM Dev Edition XT1053 that got the lollipop update)
jay_em said:
Do you know where I can find mfastboot for Mac OSX?
Click to expand...
Click to collapse
Here is a copy on my Box 'drive':
https://app.box.com/s/5nlgy2avccupw4box8z2be50ezt4qn7p
EDIT: I just got an e-mail saying it had been downloaded. :good:
---------- Post added at 08:54 AM ---------- Previous post was at 08:45 AM ----------
kyzn said:
Thanks.. It's been ages since I used I last used adb commands and flashed something. I couldn't figure out how to boot into recovery.
Click to expand...
Click to collapse
EDIT: [If you are still running the stock Recovery] You can also use:
Code:
adb reboot recovery
When you see the horizontal robot hold the Volume Up key for 3 seconds and then tap Power and the Recovery Menu will display.
Thanx for this how-to. Everyone has been getting confused in root process for 5.1 although it is nearly same as 4.4.4.
Sent from my XT1052
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
jodaboda said:
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
Click to expand...
Click to collapse
I had the same issue with my XT1053. Following your advice did the trick. Not being able to modify my dpi since upgrading has been killing me. Its the only thing i really want root for. Thanks for everything both you and op!
jodaboda said:
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
Click to expand...
Click to collapse
Ahh... 2.8.7 wasn't out when I tried.. 2.8.6 was the latest at that time. Maybe there is a bug in 2.8.7 that will get fixed in future versions?
Sunshine unlocked bootloader
Does anyone know if there are any issues resulting from a Sunshine unlocked bootloader? I saw one post that had a warning but it was a warning because there was no information at the time. Has this change?
i installed TWRP successful, but after normal reset, TWRP is gone, it's only stock recovery (Android down image). Please help me. My phone is running 5.1 update OTA, unlocked bootloader
md07 said:
i installed TWRP successful, but after normal reset, TWRP is gone, it's only stock recovery (Android down image). Please help me. My phone is running 5.1 update OTA, unlocked bootloader
Click to expand...
Click to collapse
When you say "installed TWRP successful"... do you mean that fastboot didn't error? or that fastboot completed the install, you did a mfastboot reboot-bootloader, and tried entering TWRP but it still gave you the "dead android" image?
Is there any unofficial way to unlock bootloader?
Sent from my Nexus 7 using Tapatalk
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
djibril13 said:
Is there any unofficial way to unlock bootloader?
Click to expand...
Click to collapse
Sunshine... IF you're phone has never been upgraded to 4.4.4.
BUT if you can get unlock code from Moto, while it can void your warranty (depending on your local laws), that is FREE, and the best way.
SX86 said:
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
Click to expand...
Click to collapse
help me understand your situation...
You are doing.. Mfastboot flash recovery -> mfastboot reboot-bootloader -> you get battery charging screen rather than fasboot/bootloader menu/screen?
or ??
SX86 said:
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
Click to expand...
Click to collapse
after flashing did you but to recovery befour booting system? with my experience i had to boot to recovery first befour system
Hope this helps.
1. Install android sdk and use the included install manager in the sdk to install the latest google usb drivers and platform tools (platform tools include fastboot and adb). Make sure adb and fastboot directory is in your Path variable as well.
2.Download latest stock image for Nexus 9 from google: https://developers.google.com/android/nexus/images?hl=en
3.Download latest twrp (here is the latest right now 10/6/2015): http://forum.xda-developers.com/nex...recovery-twrp-2-8-2-0-touch-recovery-t2944788
4.Download either a stock boot image with the no- forceencrypt flag set or a kernel with the no-forceencrypt flag set
a.I use the elementalx kernel (10/6/2015): http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657
b.A stock kernel for the MRA58K build with the no-forceencrypt flag set can be found here (boot.zip): http://forum.xda-developers.com/nexus-9/general/marshmallow-factory-images-available-t3218290/page3
5.Download the latest supersu that works with nexus (beta now) : http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
6.Make sure you have usb debugging enabled and ability to unlock bootloader (android developer options menu on nexus).
7.Unzip the 6.0 stock image into a folder and open a command window in the folder.
8.Type the following:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot oem unlock
c.flash-all, now wait a few minutes while the stock image flashes
9.At this point your nexus will reboot. Once you’re started, up you need to again enable usb debugging and the ability to unlock your bootloader in the android developer options menu. Now type the following to flash TWRP:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot flash recovery twrp.img (or whatever the image filename is from the twrp download).
10.Important: now make sure you boot DIRECTLY into TWRP via the button combination (power and volume down), a fastboot command, or the fastboot menu. If you don’t TWRP will be deleted and you’ll need to reflash using the last step.
11.Once in TWRP, hit “cancel” when asked for the password and then erase/wipe data and make sure MTP is enabled (dig around the menus in TWRP, it’s all in there somewhere). This erases the encrypted partition and allows you to use adb to push files to your sdcard.
12.Now type adb push supersufile.zip /sdcard/supersufile.zip, make sure you’re typing from the correct directory.
13.Install supersu via the install menu on TWRP.
14.You now need to install a kernel with the no-forceencrypt flag set:
a.If you want to install a custom kernel (like elementalx), type adb push elementalxfile.zip /sdcard/elementalxfile.zip, make sure you’re typing from the correct directory. Then use TWRP to install the zip from your sdcard.
b.If you want to install the modified stock boot.img then unzip the boot.zip, boot back into the bootloader and type: fastboot flash boot boot.img. Make sure you do NOT boot back into the android OS before doing this step or you'll have to reflash twrp.
Reboot and you’re good to go.
Didnt work for me.
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
typo
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you
Fda979 said:
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you
Click to expand...
Click to collapse
Fixed. Thanks.
Sent from my Nexus 9 using Tapatalk
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
I flashed the latest supersu and the latest elementalx kernel.... been running it since about an hour after elementalx kernel for 6.0 final was posted....... everything seems to be working fine. Are you sure? Maybe i'm having no problems with supersu because i'm using elementalx? let me know the reason, i'll check it out on my tablet and see if i can reproduce, and if so i'll modify the guide. But after about a day and a half use, i've had no issues. thx for quality checking.
gt
Am I missing something?
can I not just do a wipe and flash the img with twrp like a custom rom? Edit: Got it working. For me it was much easier to use this as opposed to the android sdk, because it would not detect my version of java. From there I followed your instructions, mostly. Putting the files you posted inside the directory the mini adb client allowed the flash-all command to work. From there I followed chainfire's instructions on the latest SU. Everything seems to be running smoothly. Thanks for the initiative, OP :good:
i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.
dkryder said:
i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.
Click to expand...
Click to collapse
Of course update binaries. Choose normal method.
Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
I was facing same issue, then updated fastboot(android-sdk) and flash-all script worked fine for me.
That should work as well. That sequence of commands should work with any fastboot version. Just make sure to flash the vendor.img, some scripts don't use that as it's only used for the Nexus 9.
Why so complicated? I just installed @wug's NRT toolkit(on a Venue8 pro) and it did everything for me. Now im on rooted stock 6.0 with disabled encryption. Only thing i needed to do is to flash latest super su beta 2.52, that's it.
Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
i did all this, no worries and no error messages
i did fastboot reboot
now I am in a weird loop of
- google screen
- your device is corrupt
- google screen
- twrp (it flashes quite quickly, error messages on mounting everything and last line says something about renaming and something about stock rom)
loop
any ideas ?
Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.
Verttex said:
Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.
Click to expand...
Click to collapse
yes, that seems to have been it
flashing TWRP seems to have been the problem so I have left everything as stock until root etc works on the stovk kernel
thanks for your help
Nice guide.
I install Busybox from Play, I assume that's needed? Everyone else doing this?
- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
added link to the latest beta supersu. thx.
All of these steps worked for me, but my battery doesn't charge right I don't think. It says battery life is at 3,745%. It runs out somewhere around 3,000%. Any ideas on how to fix that?
I've been trying for the last couple of days to root my MM G4 H815 v20e but all the guides I've tried to follow have either wanted TWRP installed before rooting, or root being required before installing TWRP. No matter which TWRP I tried, none would install. Yeah, the install would succeed ok, but when I tried rebooting into recovery all I got was the dead robot. Then I came across a method for running TWRP as a boot img and installing root from there. And it worked 100%, first time. So I'm putting this method on here so anyone else having the same problems as I had, can root their phone.
This is non-destructive but, as usual, I take no responsibility for you wandering from the path and breaking something. You will need an unlocked bootloader, instructions here, and your warranty will most definitely be invalidated after this. The original instructions were in Turkish, so many thanks to the original poster, and to Google Translate for at least making it understandable.
So I take it we're all sure what we're doing with adb, fastboot etc? This is serious stuff so if you don't think you're up to it, don't try it until you are. I'm just posting the method for rooting, the other stuff can be easily found. Plus it helps you understand the system of searching.
So when you're ready, connect your phone to your pc by USB cable, ensure USB Debugging is enabled, and off we go:
Step 1 - Visit https://dl.twrp.me/h815/ and download twrp-3.0.2-0-h815.img to your sdk/platform-tools folder. Rename it to "twrp.img". Copy this file to either the root of your internal memory or external sd card.
Step 2 - download SU zip from here https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip and rename it to "su.zip". Copy it to either the root of your phone's internal memory or sd card
Step 3 - switch to your sdk/platform-tools folder, shift and right-click on a white space and select "Open command window here"
Step 4 - type "adb reboot bootloader" [ENTER] then type "fastboot boot twrp.img" [ENTER]
TWRP will now run in memory
Step 5 - As TWRP isn't actually installed, you'll need to swipe the switch at the bottom to allow it to modify your phone
Step 6 - Tap Install and select su.zip. Select "Zip signature verification".
Step 7 - Swipe the switch at the bottom to flash the zip.
Step 8 - It would be a good idea at this point to also flash the TWRP. go back to the install screen. As it is an img file and not a zip you want to flash, tap the "Install Image" button at the bottom right, choose the twrp.img file you copied to the phone, and swipe to flash.
When complete, tap the Reboot button, choose Recovery and your phone should now boot into TWRP. Now choose to reboot to System and allow your phone to restart (it may take a while longer than normal and may reboot , mine did once).
And that's your phone rooted. Install Root Checker from the Play Store and run it to confirm your phone has been rooted.
Unlocked bootloader, I guess, yes?
cesedy said:
Unlocked bootloader, I guess, yes?
Click to expand...
Click to collapse
Without unlocking the bootloader he wouldn't be even able to boot the twrp img, since its unsigned by LG!
This is common sense
If I unlock the bootloader I´ll also fire up the twrp (not boot but simply flash twrp)
Root is just optional there
U rock man!!!
100% working!!!! i've been looking for this for so long and all tutorials were complicated and hard to follow and you came with this simple tutotial xD i have the same lg g4 h815 20e. You are the real MVP!!!:highfive:
But why? Why wouldn't you just install TWRP seeing as you've unlocked the bootloader, might as well make your life easier in the long run...
adb reboot bootloader
fastboot boot twrp.img
copy twrp.img to internal storage
in twrp -> install -> images -> twrp.img -> select recovery and swipe to install
Can't install TWRP via fastboot (fastboot flash recovery twrp.img doesn't work properly, have to flash the twrp.img inside TWRP itself).
dontpannic said:
But why? Why wouldn't you just install TWRP seeing as you've unlocked the bootloader, might as well make your life easier in the long run...
adb reboot bootloader
fastboot boot twrp.img
copy twrp.img to internal storage
in twrp -> install -> images -> twrp.img -> select recovery and swipe to install
Can't install TWRP via fastboot (fastboot flash recovery twrp.img doesn't work properly, have to flash the twrp.img inside TWRP itself).
Click to expand...
Click to collapse
Exactly, makes no sense
Sent from my LG-H815 using Tapatalk
Will it work on LG G4 H815 V10d ? anyone tried it ? I hate it not having root, thats the first phone i have so many problems rooting it...
already unlocked my bootloader...
thanks...
snail22 said:
Will it work on LG G4 H815 V10d ? anyone tried it ? I hate it not having root, thats the first phone i have so many problems rooting it...
already unlocked my bootloader...
thanks...
Click to expand...
Click to collapse
Since you have unlocked bootloader anything will work
you can simply boot the twrp (like the op shows) and flash supersu
or rather -> copy twrp img to the internal, boot twrp (look op) and flash the twrp img (tap first the zip/img checkbox) --it will ask where to flash -> select recovery, don´t tap boot...
Then you might also flash the supersu
and now you have twrp and root
bender_007 said:
or rather -> copy twrp img to the internal, boot twrp (look op) and flash the twrp img (tap first the zip/img checkbox) --it will ask where to flash -> select recovery, don´t tap boot...
Then you might also flash the supersu
and now you have twrp and root
Click to expand...
Click to collapse
Great, This looks like what I want, will try in the evening, if this work, I will be able to use TASKER AGAIN !! hooray :laugh:
The problem with the boot loop is only in the devices that are bootloader unlocked ? My H815 (506) is locked...and i was thinking at unlock the bootloader, but, i am "afraid" of the boot loop.
No, it's random
Sent from my LG-H815 using Tapatalk
Its because of a hardware problem, isnt?
Sent from my LG-H815 using XDA-Developers mobile app
Exactly, we have a poll about it but I see sone 505, 506 users wanted to re-vote because their phones died. :/
Sent from my LG-H815 using Tapatalk
Did work h815 TWN ? I need to root or unlock bootloader. Help me pl0x
Hey,
I have H815 6.0 with locked bootloader v20e
will this work for me? or i have to unlock the bootloader first? i just want root
can i use this method for v20d? thx.
After typing "adb reboot bootloader" phone restarts to bootloader. And thats it. Typing "fastboot boot twrp.img" does nothing but writes <...> is not recognized as and internal or external command, operable program or batch file. Whats going on? Also if i type adb devices there is empty list of devices attached
xyster13 said:
After typing "adb reboot bootloader" phone restarts to bootloader. And thats it. Typing "fastboot boot twrp.img" does nothing but writes <...> is not recognized as and internal or external command, operable program or batch file. Whats going on? Also if i type adb devices there is empty list of devices attached
Click to expand...
Click to collapse
You don't have fastboot installed, or you're typing the command wrong.
c:> adb reboot bootloader
c:> fastboot boot twrp.img
What happens if I want to go back to stock, will the device remain as it was before rooting and will receive OTAs and allow device encryption and all?
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work. Some even report success after 20 tries.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in the thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Added another instructions from another forumer who think my instructions is not complete:-
1. Install the moto driver and then plug in your device while running normal
2. Run the get_code.bat (from this link)
3. once unlock.code file is created, run "adb reboot bootloader". It will show [Fastboot] with the kf logo.
4. Once bootloader comes up, change driver in device manager for "Other Android" to use the Android -> Mot Adb Composite Driver. It should say "Ready" on the KF
5. Run the stuff from this post (do the bottom steps with fastboot erase first)
6. After you are done in bulk mode, hold the power button for 15 secs to reboot. It will automatically boot into Fastboot
7. When you run the unlock command, use the "unlock.code" file.. not the "0xmmssssssss.unlock" example from that link.
8. Now unplug and hold power again to shut down. Hold VolUp + Power. About 3 secs after you see the KF logo, you can let go of the power button (possibly both buttons) and you get TWRP
From here you can flash CM and gapps (5.1).
Click to expand...
Click to collapse
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
BatmanDC said:
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
Click to expand...
Click to collapse
You do not need to be on 4.5.5.2 or any specific version of FireOS for that matter. Is the device rooted?
BatmanDC said:
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
Click to expand...
Click to collapse
As Davey said, no. The reason I created this thread because 4.5.5.2 is the last OTA. My point is even last OTA can root and unlock bootloader.
kkcheong said:
As Davey said, no. The reason I created this thread because 4.5.5.2 is the last OTA. My point is even last OTA can root and unlock bootloader.
Click to expand...
Click to collapse
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
are those instructions as daunting as they sound?
it seems if you kingroot and wipe everything it negates any malware?
barrist said:
...it seems if you kingroot and wipe everything it negates any malware?
Click to expand...
Click to collapse
Correct. KingRoot is a borderline malware but does not appear to harvest personal info during the rooting process and is completely irradiated by a wipe of the system and data partitions.
draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
Davey126 said:
Correct. KingRoot is a borderline malware but does not appear to harvest personal info during the rooting process and is completely irradiated by a wipe of the system and data partitions.
Click to expand...
Click to collapse
Thanks
just picked up a used HDX off Kijiji, so i'm looking forward to tinkering.. can you suggest an initial stable rom to try? the KK based Nexus seems to be the safer one i'm gathering?
barrist said:
Thanks
just picked up a used HDX off Kijiji, so i'm looking forward to tinkering.. can you suggest an initial stable rom to try? the KK based Nexus seems to be the safer one i'm gathering?
Click to expand...
Click to collapse
There are no bad/unstable HDX ROMs. Fire Nexus has the advantage for those needed full Bluetooth and/or LTE support. Otherwise LineageOS 14.1 is a solid choice. Regardless of direction you'll want to unlock the bootloader and wipe the device immediately after rooting if KingRoot is utilized. Also know Amazon devices have their own set of quirks and don't behave like a typical Android gizmo.
Thanks maybe I'll give lineage a shot as I don't really don't need LTE or bt .. just hoping for stable app support and wifi
draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
Thanks for the awesome info. But noob like me would prefer Kingroot because it give the illusion of zero risk :laugh:
nice, instructions worked, running lineage 14.1 and no problems so far!
kkcheong said:
Thanks for the awesome info. But noob like me would prefer Kingroot because it give the illusion of zero risk :laugh:
Click to expand...
Click to collapse
No problem.
Given that you wipe 'data' (which I prefer not to, because I'm too lazy to make backups),
you should be fine with KingRoot, it just takes much longer, but that's your choice.
The real risk is making a mistake when flashing aboot and TWRP, which is the same on both paths.
kkcheong said:
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in this thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Click to expand...
Click to collapse
I tried to follow all steps but cannot go beyond Step 2c. When I try to flash cubed and aboot, i get "cannot access file : file or directory not present" error. How should I proceed?
xyluss0 said:
I tried to follow all steps but cannot go beyond Step 2c. When I try to flash cubed and aboot, i get "cannot access file : file or directory not present" error. How should I proceed?
Click to expand...
Click to collapse
Have you put both file in the adb directory?
Yes I did. Also, I tried to go ahead on the next step and run unlock.bat but I got the error "incorrect unlock code".
xyluss0 said:
Yes I did. Also, I tried to go ahead on the next step and run unlock.bat but I got the error "incorrect unlock code".
Click to expand...
Click to collapse
Please print screen. Did you cd to ADB directory?
Root hdx 7 (3rd Gen.), FireOS 4.5.5.2 with towelroot
Hi,
I am wondering if the towelroot rooting process is working with the 4.5.5.2 version of the fireOS.
Do you recommend the usage of APK-versions of Kingroot or Towelroot over the use of Windowsversion esp. for Kingroot.
Do i need working internet connection during rooting process with APKs ?
Thx in advance
Achimbub
Root fails
kkcheong said:
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in this thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Click to expand...
Click to collapse
I am on Fire OS 4.5.5.2 (HDX 8.9 Apollo) and Kingroot can not root(both apk and windows versions). I tried both ten times. What can I do to root this device now?
achimbub said:
Hi,
I am wondering if the towelroot rooting process is working with the 4.5.5.2 version of the fireOS.
Do you recommend the usage of APK-versions of Kingroot or Towelroot over the use of Windowsversion esp. for Kingroot.
Do i need working internet connection during rooting process with APKs ?
Thx in advance
Achimbub
Click to expand...
Click to collapse
- TowelRoot is ineffective on FireOS v4
- recommend desktop version of KingRoot for 4.5.5.2 (still may not work)
- device does not need an active internet connection with desktop version
---------- Post added at 04:58 AM ---------- Previous post was at 04:55 AM ----------
bobcat131 said:
I am on Fire OS 4.5.5.2 (HDX 8.9 Apollo) and Kingroot can not root(both apk and windows versions). I tried both ten times. What can I do to root this device now?
Click to expand...
Click to collapse
KingOroot is the only other tool that reportedly works on 4.5.5.2. It also has a reputation for screwing up devices. Risky choice.
hi guys, my computer ( wins10) donset read adb device.
but i i use fastboot commands its able to list my devices, but ' adb devices' shows none listed? i am suck, might have soft brick it, able to boot into stock recocery. any suggestions?
oneplus 5 phone.
What are you trying to do?
Rhoban said:
What are you trying to do?
Click to expand...
Click to collapse
Was trying to update , but got stuck at boot screen .
Just flash the stock ROM with the stock recovery.
I can’t sideload it, “ adb not working “
Rhoban said:
Just flash the stock ROM with the stock recovery.
Click to expand...
Click to collapse
Files all courupted
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
dladz said:
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
Click to expand...
Click to collapse
Hi ! USB debugging was turn on before boot loop happened. Can’t boot into OS , only recovery
lolitsryan96 said:
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
Click to expand...
Click to collapse
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Thanks bro, I shall update you on the situation once I done, at work now.
Do I need to “open command promt “ at my sdk folder/plat-form tools?
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
hi bro, sideload failed i think, i cant find sideload file. when the sideload end. its gave x1.00 something like that.
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
attach image, successfully sideload but phone still in bootloop?
lolitsryan96 said:
attach image, successfully sideload but phone still in bootloop?
Click to expand...
Click to collapse
you need to wipe everything before flashing
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
just wipe, now re-sideloading. how it works. bloody nightmare dude.
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
still stuck at the boot loop, any advice
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
lolitsryan96 said:
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
Click to expand...
Click to collapse
nice good to hear!
haha, well tourists like Amsterdam so do visit that and visit The Hague/Scheveningen. I like these 3 places the most I think. Look up TripAdvisor for good attractions once you're there. do visit 'The Amsterdam Dungeon' don't miss that, I liked it very very much!
how to install the drivers?
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Cannot adb to the phone in FASTBOOT. adb devices shows nothing when in FASTBOOT, but shows the device when in normal boot.
Hence I cannot upgrade TWRP from 3.2.1-1 to 3.2.3-0. Was trying this so to upgrade from beta23 to the beta 26, now 27 with which 3.2.1-1 seems to have problems.
A 2nd approach, just re-installing beta23 without Magisk18 gives the stock recovery which manages the beta27 install. But then I'm blocked from a Magisk18 install and still cannot use FASTBOOT mode to put TWRP back on.
Thought the adb drives could be old and sought new drivers, even assuming your link is to the most current I don't know how to get my Windows7 to use the zip file. Can you assist? This would let me put the latest TWRP, hence install Magisk18 and be rooted again!