Related
I was trying to install The paranoid custom rom 6.0.1 to my OPT when I started to running into an issue with boot looping. The phone would run through the bootup animation and then say it way starting up the apps. Once it was done with all the apps it would just start rebooting again. I tried to get into recovery to flash an old rom but I couldnt get in to recovery (holding the volume down and power button just turns the screen on and then back off.) I then tried this firstaid script I found on here that would supposedly install an older twrp and allow me to get into recovery mode, but that has not worked. And now I cannot even get the phone to go to a boot animation, it just sits on the oneplus logo. Adb is not detecting my device on windows or mac, but fastboot is working. At this point I have no idea of what to do, becuase even if I get into recovery I dont have a backup rom stored on my phone. If anyone has any ideas, I please share, I am in desperate need of help here.
Flash fastboot images search and follow naman's unbrick guide, skip the data partition to keep your files
Sent from my ONE A2005 using Tapatalk
1439soccerdude said:
I was trying to install The paranoid custom rom 6.0.1 to my OPT when I started to running into an issue with boot looping. The phone would run through the bootup animation and then say it way starting up the apps. Once it was done with all the apps it would just start rebooting again. I tried to get into recovery to flash an old rom but I couldnt get in to recovery (holding the volume down and power button just turns the screen on and then back off.) I then tried this firstaid script I found on here that would supposedly install an older twrp and allow me to get into recovery mode, but that has not worked. And now I cannot even get the phone to go to a boot animation, it just sits on the oneplus logo. Adb is not detecting my device on windows or mac, but fastboot is working. At this point I have no idea of what to do, becuase even if I get into recovery I dont have a backup rom stored on my phone. If anyone has any ideas, I please share, I am in desperate need of help here.
Click to expand...
Click to collapse
This thread will help you, https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/
if you use twrp recovery and is not working on the Vol+ "-", try this way : RENAME your recovery file into twrp.img and flash it again.
If is not working,
following this thread first:
http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
Then repeat my rename recovery method.
SOFT brick
You are a happy owner of a SOFTbricked OP2, happends mostly when you corrupt the partions. It easy to recover by Oneplus guide. You can use the link provided above by colleague on oneplus forum or this one XDA http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543. GO step by step works 100%
Seimus said:
You are a happy owner of a SOFTbricked OP2, happends mostly when you corrupt the partions. It easy to recover by Oneplus guide. You can use the link provided above by colleague on oneplus forum or this one XDA http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543. GO step by step works 100%
Click to expand...
Click to collapse
Or you could use the updated version by @fareed_xtreme that @qingmui linked to in the post just above yours
Spannaa said:
Or you could use the updated version by @fareed_xtreme that @qingmui linked to in the post just above yours
Click to expand...
Click to collapse
Indeed but i prefer to go back to the previous build as per I know its stable. I like to do rollback and then the update. So I can better isolate any new caused issue
Hi all,
Sorry if this is covered elsewhere but I cannot find it.
I successfully installed the May 2016 updates and now I am trying to get root back. I followed the usual steps for installing TWRP
Code:
adb reboot-bootloader
fastboot flash recovery .\recovery\twrp-3.0.2-0-clark.img
fastboot reboot
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
user7743 said:
Hi all,
Sorry if this is covered elsewhere but I cannot find it.
I successfully installed the May 2016 updates and now I am trying to get root back. I followed the usual steps for installing TWRP
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
Click to expand...
Click to collapse
You have to immediately boot into TWRP after flashing or the system will overwrite it with the stock recovery.
Sent from my XT1575 using XDA Labs
Thanks for that. Exactly the hint I needed.
Question
Would you mind telling me what steps you took to get the May update? It's so small that I'm reluctant to do anything major to get it and I'm debating on whether to just flash the stock recovery to give that a try, or whether I'm going to have to flash the unrooted image I've saved using TWRP, then flash stock recovery, then get the OTA. Seems like a lot of work for a tiny update.
user7743 said:
Hi all,
Sorry if this is covered elsewhere but I cannot find it.
I successfully installed the May 2016 updates and now I am trying to get root back. I followed the usual steps for installing TWRP
Code:
adb reboot-bootloader
fastboot flash recovery .\recovery\twrp-3.0.2-0-clark.img
fastboot reboot
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
Click to expand...
Click to collapse
Marnina said:
Would you mind telling me what steps you took to get the May update? It's so small that I'm reluctant to do anything major to get it and I'm debating on whether to just flash the stock recovery to give that a try, or whether I'm going to have to flash the unrooted image I've saved using TWRP, then flash stock recovery, then get the OTA. Seems like a lot of work for a tiny update.
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
Click to expand...
Click to collapse
If you have modified the system in any form, such as using Xposed, then OTA will fail. If the system image is stock that has never been rooted, in theory you should have no issues with stock recovery installed. The OTA is the May security update. Whether you feel it is necessary or not is up to you.
I can't get any further than unlocked bootloader I get no command after trying to get straight into twrp after flash and always goes to factory recovery if that will even boot is there a secret way to boot into recovery directly after twrp flash cause I've been trying for days and days what is going on is there a way to root without twrp first please help it's the main reason I bought this damn thing
Sent from my XT1575 using XDA-Developers mobile app
Sherrillface said:
I can't get any further than unlocked bootloader I get no command after trying to get straight into twrp after flash and always goes to factory recovery if that will even boot is there a secret way to boot into recovery directly after twrp flash cause I've been trying for days and days what is going on is there a way to root without twrp first please help it's the main reason I bought this damn thing
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
Don't run the last command:
fastboot reboot
Select to reboot into recovery from the menu. If you're getting No command, you may need to flash the stock recovery then reboot the recovery. You should have the menu back. Flash TWRP and reboot into recovery to start TWRP.
HTH
Ooms
Sherrillface said:
I can't get any further than unlocked bootloader I get no command after trying to get straight into twrp after flash and always goes to factory recovery if that will even boot is there a secret way to boot into recovery directly after twrp flash cause I've been trying for days and days what is going on is there a way to root without twrp first please help it's the main reason I bought this damn thing
Click to expand...
Click to collapse
1. Periods, dude. Where are they?
2. Flash TWRP again.
3. In TWRP, mount /system (Advanced > Mount > system), and delete:
/system/etc/install-recovery.cfg
/system/etc/recovery-resource.dat
/system/recovery-from-boot.p
Click to expand...
Click to collapse
or add the .bak extension to the filenames.
/system/etc/install-recovery.cfg.bak
/system/etc/recovery-resource.dat.bak
/system/recovery-from-boot.p.bak
Click to expand...
Click to collapse
4. Reboot straight back into TWRP (Reboot > Recovery) to make sure TWRP sticks.
Can't get into twrp at all tried fastboot reboot and tried recovery mode directly after flash that's the whole issue just says no command upon trying to enter twrp directly after twrp.img flash.
Sent from my XT1575 using XDA-Developers mobile app
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
Says flash successful but I don't think it truly is
Sent from my XT1575 using XDA-Developers mobile app
Sherrillface said:
Can't get into twrp at all tried fastboot reboot and tried recovery mode directly after flash that's the whole issue just says no command upon trying to enter twrp directly after twrp.img flash.
Sent from my XT1575 using XDA-Developers mobile app
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
Says flash successful but I don't think it truly is
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
Sounds like it's not flashing... what is your bootloader state? Try to start it with fastboot boot recovery.img command.
acejavelin said:
Sounds like it's not flashing... what is your bootloader state? Try to start it with fastboot boot recovery.img command.
Click to expand...
Click to collapse
Got it a while ago wrong windroid version.
Sherrillface said:
Got it a while ago wrong windroid version.
Click to expand...
Click to collapse
Umm... OK... No offense to @Rapscallion16 but why are you using a generic toolkit on the Moto X??? It has been mentioned many times that using one click tools and other toolkits is not safe with this and most newer Moto devices, doing it manually is pretty simple.
Anyway, glad you got it working. Enjoy...
The instructions are updated as of 11-20-17. Win7 only cause Win10 sucks and uses powershell and the fastboot commands don't work in powershell.
These are the proper files and procedures for installing Root, the latest Kernel, the best Superuser version and TWRP.
This is for NOUGAT 7.1.1. (and possibly beyond) There is a special procedeur to make flashtool work with the latest firmwares for Nougat ..
Before you Root and install TWRP you need to go back to my link and unlock bootloader..
You also need to download and install Android Studio Software and install it. Back to this portion of the install later.
You also need a special kernel to allow things on the phone to keep working.
This will work only for Nougat firmware.
You will need to download Boot img, TWRP img, SuperSu
Save TWRP and boot img files to the Android Platform folder in your PC here C:\Users\enter the current pc users log in name here\AppData\Local\Android\sdk\platform-tools . Save the Kernel zip and SUperSU zip file to an SD card and put the card inside your phone to access it through TWRP later in the process. Keep in mind that the Kernel may be updated. Check for updates herel here. Do a "date last modified" list of the files on that page by clicking on the grid view box on the upper right portion of the screen just under the "sign in" button. This helps you see what files have been updated in most recent order.
You will need to download the special Flashtool file here Install it.
Download the .jar patch file that makes the software version updated to the latest 9.23.2 and place it in this location C:\flashtools.
Now, download the special .fsc file and paste it in C:\Users"current user that is logged in"\.flashTool\devices\F81XX. Without this file you will not beable to update the device to nougat.
Goto C:\Flashtool\drivers and click on this file which was installed during the Flashtool installation.
Check off these boxes to install the drivers for the device you will be rooting. "Flash Boot Drivers, Flash Mode Drivers"
Now download and install these special ADB drivers to allow it to perform the Firmware update. Without it you wont beable to install the FTF file.
Open Sony Flash tool. Click on XI button. A window open. Click on Xperia Performance and then a small menu open under that. Choose F8132 ( i choose dual for my device)
If you can not get the newest firmware to show up for your device.( mine is 41.2.A.7.8 aka Nougat 7.1.1) then you can download it here Close Sony Flashtool.
Copy this FTF file and place it in folder C:\Users"The user you are currently logged into your pc with"\.flashTool\firmwares. Open Sony flash tool. Click on lightning bolt. Choose Flash mode in the small popup box. Window opens and shows your formware in the "firmwares" box. Click on plus symbol to the left of that firmware and it opens to the bottom to show the device model ( mine is F8132)/ Click on that plus symbol to the left of the model number to show the location of your firmware origination. Click on plus symbol and it then shows the firmware number 41.2.A.7.8. Click on the firmware and the entire window will populate a bunch of new options. If you want to wipe everythign on your phone then you need to check off the boxes "SSD and UserData" in the "wipe" box. Leave everythign else unchecked. Click the flash button at the bottom and it will start to prepare the files for installation onto yout device.
A window pops up that tells you to turn off your phone.
Turn your phone off. After its turned off, hold the volume down button while plugging the phone into your pc to get into fastboot mode. Your computer should be looking for the correct drivers to allow the device to work in this Flashboot mode. Once the flashing is done just close the flashtool. Turn your phone on. Go into settings and scroll down to "about phone then click on "build number" about 7 times. You will get a new optioon back in settings menu called "developer option". Click on that tabturn on "usb debugging" and turn off "verify apps over usb". Turn off phone.
Hold volum button UP this time while plugging phone back into pc.
Now go back to the folder C:\Users" name of user that is logged into the pc"\AppData\Local\Android\Sdk\platform-tools. You will open a cmd prompt in this folder by holding down your right mouse button and click on the shift key then release the mouse button. This will open a pop up window where you can choose to " open command window here" when the cmd window opens, copy and paste this "fastboot devices" press enter button, your computer should respond with this ......CB512A697c fastboot.......This lets you know that your phone is in the correct mode and ready to be programmed.
Now you will install the boot img by copy and pasting this in cmd line "fastboot flash boot boot.img" The PC should tell you OKAY with some other irrelevant info.
Now you will install the twrp img by copy and pasting this in cmd line "fastboot flash recovery TWRP-3.0.3-0-dora.img" The PC should tell you OKAY with some other irrelevant info.
Now you will install Kernel, and SuperSU. Turn on phone while pushing power button holding volume down button for about 5 secnds then release the bottom volum button then after 5 seconds release the power button to initiate TWRP.
Swipe to allow modifications then choose "Install" to install the zip files. Navigate to the SD card that has the kernel and SU zip files. Click on them to install. Reboot. TWRP might ask if you want to install the TWRP app before the phone starts to reboot. Just say no. After that, a few seconds later, the device reboots and then the Phone might go throw optimization process which takes some time. You will notice the counting of optimized files. Be patient.
When phone is booted and running, you might have to reinstall SuperSU via the Operating system as a APK like you would a normal app just to get root going. No big deal.
A caution...
When doing a backup with Twrp you should only backup System and Data
When doing a full restore, wipe only System, Data and the cache files. Do not ever delete your SDcard with the backups on it.
THIS IS THE VERY LAST UPDATE FOR ROOTING THE X Performance. IT IS NOUGAT 7.1.1
FORGET ABOUT ROOTING OREO>> ITS NOT GOING TO HAPPEN. PLUS IT IS NOT A DECENT UPDATE TO BE HONEST> IT JUST CHANGES A BUNCH OF MENUS AROUND AND LOCKS DOWN YOUR PHONE MORE>
Please do not upload my kernel to other hostings!
Official website for my kernel is
https://kernel.andro.plus/tone.html
So, if I was to relock my bootloader after installing TWRP and rooting, what would happen? Would TWRP go away? I'd like to let the phone OTA update to nougat, and you can't do that with an unlocked bootloader....
jakebriggs said:
So, if I was to relock my bootloader after installing TWRP and rooting, what would happen? Would TWRP go away? I'd like to let the phone OTA update to nougat, and you can't do that with an unlocked bootloader....
Click to expand...
Click to collapse
your phone will soft brick..or rather bootloop..if you're still on MM,do a nandroid backup..& here's what you do:
-relock phone using Flashtool.
-repair device using Xperia Companion(it will update automatically to Nougat).
-unlock phone again using Flashtool.
-install AndroPlus Kernel through command prompt(or you can also use Flashtool to do it.however you prefer).
-install TWRP recovery..you're all set!
P.S.
on steps i said(this is optional),you may not turn on your device along the process..that's what i do & i find it easier that way..goodluck!
Arturiuz! said:
your phone will soft brick..or rather bootloop..if you're still on MM,do a nandroid backup..& here's what you do:
-relock phone using Flashtool.
-repair device using Xperia Companion(it will update automatically to Nougat).
-unlock phone again using Flashtool.
-install AndroPlus Kernel through command prompt(or you can also use Flashtool to do it.however you prefer).
-install TWRP recovery..you're all set!
P.S.
on steps i said(this is optional),you may not turn on your device along the process..that's what i do & i find it easier that way..goodluck!
Click to expand...
Click to collapse
Thanks heaps! Now, to find a couple hours spare
Arturiuz! said:
your phone will soft brick..or rather bootloop..if you're still on MM,do a nandroid backup..& here's what you do:
-relock phone using Flashtool.
-repair device using Xperia Companion(it will update automatically to Nougat).
-unlock phone again using Flashtool.
-install AndroPlus Kernel through command prompt(or you can also use Flashtool to do it.however you prefer).
-install TWRP recovery..you're all set!
P.S.
on steps i said(this is optional),you may not turn on your device along the process..that's what i do & i find it easier that way..goodluck!
Click to expand...
Click to collapse
Following this left me with a phone that boots to a screen "To start Android, enter your password". I don't have a password to enter :/
jakebriggs said:
Following this left me with a phone that boots to a screen "To start Android, enter your password". I don't have a password to enter :/
Click to expand...
Click to collapse
that occured to me too!my apologies but i forgot mention about that..but you could try again that after you fixed/updated your phone using Xperia Companion to turn your phone first & set up everything.then unlock using Flashtool.install kernel & recovery.. :good:
Arturiuz! said:
that occured to me too!my apologies but i forgot mention about that..but you could try again that after you fixed/updated your phone using Xperia Companion to turn your phone first & set up everything.then unlock using Flashtool.install kernel & recovery.. :good:
Click to expand...
Click to collapse
I did try that - although, I set it up with a pin rather than a password. It didn't accept my pin when asking for the password.
Now I have a phone with a locked bootloader, running nougat, and I set it up with a password. I wonder if that password you use on the lock screen is the same password that Android is asking for when I unlock my bootloader?
I also could not seem to get the phone to boot into recovery after rebooting when I got the password screen. So weird....
jakebriggs said:
I did try that - although, I set it up with a pin rather than a password. It didn't accept my pin when asking for the password.
Now I have a phone with a locked bootloader, running nougat, and I set it up with a password. I wonder if that password you use on the lock screen is the same password that Android is asking for when I unlock my bootloader?
I also could not seem to get the phone to boot into recovery after rebooting when I got the password screen. So weird....
Click to expand...
Click to collapse
you can't use recovery or root your phone when bootloader is locked..could you try now unlock your phone using Flashtool?then install kernel & recovery?mind that data will be wiped..
Arturiuz! said:
you can't use recovery or root your phone when bootloader is locked..could you try now unlock your phone using Flashtool?then install kernel & recovery?mind that data will be wiped..
Click to expand...
Click to collapse
So if unlocking the boot loader wipes data, how can android ask for my password when I reboot? I am a little mystified at how this is supposed to work Rooting Marshmellow was easier than Nougat....
jakebriggs said:
So if unlocking the boot loader wipes data, how can android ask for my password when I reboot? I am a little mystified at how this is supposed to work Rooting Marshmellow was easier than Nougat....
Click to expand...
Click to collapse
true!MM was easier but Nougat is a bit complicated..however,you could still make changes on Nougat when phone is rooted.anyway,try again from the very beginning then this time after fixing phone using Xperia Companion,do the steps i mentioned..i myself couldn't figure out how it's asking for any password at first.AndroPlus also mentioned it before but didn't explain further.but it's alright coz i got it working now.
Arturiuz! said:
true!MM was easier but Nougat is a bit complicated..however,you could still make changes on Nougat when phone is rooted.anyway,try again from the very beginning then this time after fixing phone using Xperia Companion,do the steps i mentioned..i myself couldn't figure out how it's asking for any password at first.AndroPlus also mentioned it before but didn't explain further.but it's alright coz i got it working now.
Click to expand...
Click to collapse
I think my issue with the unknowable password after unlocking the bootloader on Nougat could have been fixed by wiping data+dalvik cache. I was having issues with the camera under nougat so I flagged trying to get it going and flashed MarshMellow. Once that was done, I got the bloody password prompt again, so I wiped data + cache and it booted correctly.
Anyway, gonna ignore Nougat until fastboot supports nougat
Issues with passwords kept / unknown and blocked are due to the fact the security portion is stored
next to the data partition area, in what we call the footer, and that area was wrong for you.
By wiping data completely (most reliably, a factory reset which will format the data partition),
the footer is also erased instead of simply deleting the files like a Wipe would do.
lost system?
I got as far as getting boot.img and twrp.img in my phone, and then appeared to lose my system since it stuck on the Sony logo and wouldn't boot into the system despite several tries. Idiot that I am, I panicked and come onto the forum to post a plead for help. I've managed to get my system back on now and feel very foolish, so just editing the post to remove the request for help. Thank you so much for the guide, very greatly appreciated! Looking forward to upgrading to Nougat.
Will this guide work with Nougat? I have a F8132 with 39.2.A.0.327
mongastein said:
I got as far as getting boot.img and twrp.img in my phone, and then appeared to lose my system since it stuck on the Sony logo and wouldn't boot into the system despite several tries. Idiot that I am, I panicked and come onto the forum to post a plead for help. I've managed to get my system back on now and feel very foolish, so just editing the post to remove the request for help. Thank you so much for the guide, very greatly appreciated! Looking forward to upgrading to Nougat.
Click to expand...
Click to collapse
Don't feel like a fool. I'm panicing right now.
Can flash boot.img and twrp.img and even enter twrp to flash su and kernel. But thats it. When done i reboot and i can pass SONY logo and enter bootanimation but it stucks here forever. Been trying with everything exept flashing official MM.
You did get the system back. So I'm the fool
---------- Post added at 07:45 AM ---------- Previous post was at 07:40 AM ----------
chiobesek said:
Will this guide work with Nougat? I have a F8132 with 39.2.A.0.327
Click to expand...
Click to collapse
Didn't for me. Have a softbricked phone in front of me since yesterday. Going to try to flash MM soon but my internet is terrible slow. Won't give up.
chiobesek said:
Will this guide work with Nougat? I have a F8132 with 39.2.A.0.327
Click to expand...
Click to collapse
It works if you get updated files. I struggled a bit before I finally extracted the boot.img from the AndroPlusKernel for my version which I flashed in fastboot and flashed the kernel and supersu in twrp. I think that's what did it. I was so eager to root that I missed that I was using MM-files at first. :silly:
Edit: oh I answered a pretty old post. Anyway, this is another way https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148
Wimz3n said:
Don't feel like a fool. I'm panicing right now.
Can flash boot.img and twrp.img and even enter twrp to flash su and kernel. But thats it. When done i reboot and i can pass SONY logo and enter bootanimation but it stucks here forever. Been trying with everything exept flashing official MM.
You did get the system back. So I'm the fool
---------- Post added at 07:45 AM ---------- Previous post was at 07:40 AM ----------
Didn't for me. Have a softbricked phone in front of me since yesterday. Going to try to flash MM soon but my internet is terrible slow. Won't give up.
Click to expand...
Click to collapse
I ended up finding a way to downgrade to marshmallow following some instructions from from @sdugoten
The instructions are updated.. With proper files for the latest and greatest kernel and SuperSU and TWRP. NOUGAT Only .. Will not work for any other OS versions
AS flashtool does not work for 7.1.1 how to proceed to install nougat 7.1.1 and enable root and install twrp?
EDIT: Fixed! Big thanks to @S0wL , @bkores , @tamahouse02 and @tron1 for the help. I made a guide to help other people with the same problem:
Guide to get TWRP again HERE
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Try the menu on the boot screen.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Sounds like the issue is with the ROM like it is somehow blocking you from accessing bootloader mode. It's definitely not my toolkit.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Choose an username... said:
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Click to expand...
Click to collapse
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
tamahouse02 said:
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
Click to expand...
Click to collapse
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Choose an username... said:
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Click to expand...
Click to collapse
Not same my axon7tool. I use this https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
DrakenFX said:
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
Click to expand...
Click to collapse
I was thinking about that, but does mifavor let you roll back from an SD update? I'll try later, but i doubt it.
Besides from that is there any way to flash stuff from the stock recovery? It tells me that ZIPs have to be signed only
tamahouse02 said:
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
Click to expand...
Click to collapse
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
dnlilas said:
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
Click to expand...
Click to collapse
Official 3.0.4.1
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
dnlilas said:
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
Click to expand...
Click to collapse
I use 3.0.4.1 because I flash plenty things before without any issue, so I keep using it.
After write recovery by axon7tool, it's reboot automatically and override the recovery, that why I have to unplug to stop the reboot, and also flash all I can - fortunaeally​ it also stop recovery be overrided
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
I've been in the same situation like you @Choose an username... Updated to nougat on G model and I had not bootloader. This is what I did :
1. Downloaded the tool from here https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
2. Installed the driver using the install driver option that you can choose once you connect you phone to your computer
3. Use the tool to perform the unlock bootloader command again even though you have unlocked it before
4. Use the tool to install twrp, it will boot the phone in twrp
5. Flash Supersu before you boot the system first time after flashing twrp
5. Install whatever version of android want after
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Choose an username... said:
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Click to expand...
Click to collapse
Use Zadig then and let me know if it worked
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Choose an username... said:
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
Click to expand...
Click to collapse
I try your version once, but it seems not work for me, so I keep using the old one.
---------- Post added at 03:42 AM ---------- Previous post was at 03:39 AM ----------
Choose an username... said:
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Click to expand...
Click to collapse
I thought you had already unlocked bootloader? Why have you done it twice?
Hey everyone,
I've been looking for options to Install a custom Rom or root since I bought the Tablet several month ago. It seems like there are some options for the Full Hd Version, but I have a hard time finding anything useful for the 125FU. Are there any recommendations like compatible GSI roms or TWRP/magisk?
Thanks in advance for your help!
You should just be able to install matiek form my understanding
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
holmesmalone said:
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
Click to expand...
Click to collapse
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
art99 said:
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
Click to expand...
Click to collapse
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
I installed corvus os gsi on it. i have no custom recovery.
peteonu said:
I installed corvus os gsi on it. i have no custom recovery.
Click to expand...
Click to collapse
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
holmesmalone said:
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
Click to expand...
Click to collapse
Agreed. I've been looking into compiling TWRP myself but this is all new to me. The only device with TWRP with this chipset is the Redmi 9. I've compared both boot.img's and they are both setup differently. If I had more knowledge ont he subject I could easily achieve this I believe.
If I have time I'll compare Gen 2 vs Gen 3 boot.img's, that may help understand the folder and file structure better.
holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
el7145 said:
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
Click to expand...
Click to collapse
The same process worked for me.
holmesmalone said:
The same process worked for me.
Click to expand...
Click to collapse
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
el7145 said:
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
Click to expand...
Click to collapse
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
holmesmalone said:
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
Click to expand...
Click to collapse
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
el7145 said:
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
Click to expand...
Click to collapse
LMSA. https://pcsupport.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
Use this tool. Install and explore the file and folder structure it creates. Interrupt the process before it flashes your tablet for it will erase the files you need from your computer if you don't. Use trial and error here.
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
el7145 said:
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
Click to expand...
Click to collapse
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Siege9929 said:
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Click to expand...
Click to collapse
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
el7145 said:
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
Click to expand...
Click to collapse
Manually selecting the "Android Bootloader" driver fixed it. Thanks!
I just got my TB125FU to replace my 7-year-old Google Pixel C on its last legs.
Its Hardware ID is USB\VID_0E8D&PID_201C&REV_0100
I found a pack of Mediatek drivers here.
It's a bloated pack, so I extracted just the files needed for the TB125FU and attached to this post.
Once installed, my tablet appeared with a "fastboot devices" command.
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
hugehead83 said:
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
Click to expand...
Click to collapse
just an fyi: thats not the most recent firmware, the lenovo rescue tool had the latest, which at the moment for my device a few days ago was TB125FU_S000118_220927_ROW