Database Info

[Q] something like CMInstaller for my TF700?

Hi guys,
I'm a total noob regarding ROMs, root, etc..
My Infinity is getting really laggy, and I really need to bring it to a new life..
I was looking for an ideal CMInstaller situation like i used on my Galaxy Note N7000.. This little app is great cuz it does everything for us and noob users like myself don't need to be afraid to brick their devices..
Is there any really easy solution like this so I can safely flash my TF700?
TIA.

I think the answer is yes and no
I run CROMI-X on this tablet, but recently I download the latest CM and the link provided kept bouncing me to the Playstore to dl an installer app. I prefer to use my recovery, so I did not use it. But that's probably what you are looking for.
The thing is, on this device first you need to unlock the bootloader and push a custom recovery to it before you can even use an installer app. You also need to make sure that you have the correct bootloader installed before you flash the CM rom.
Check out the CM thread in the Development section.

CMInstaller so far is only compatible to most common Galaxy and nexus devices, and htc one.
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer#Supported_Devices
I am honestly afraid to flash my device without assistance because there are so many things to do and none of it seems easy.. I'm bootloader unlocked running stock 4.1.2, and the steps needed to take scare me..
1 - update to stock 4.2.1 (according to what I've read..)
2 - Root
3 - NVFlash
4 - Custom recovery
5 - Custom ROM
I don't even know if these steps are in proper order, but seems that so many things could go wrong.. Could you help me doing this easily and problem free? I need to do something to take full advantage of my TF700.. It clearly isn't working properly on stock.
Thanks.

madz78 said:
CMInstaller so far is only compatible to most common Galaxy and nexus devices, and htc one.
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer#Supported_Devices
I am honestly afraid to flash my device without assistance because there are so many things to do and none of it seems easy.. I'm bootloader unlocked running stock 4.1.2, and the steps needed to take scare me..
1 - update to stock 4.2.1 (according to what I've read..)
2 - Root
3 - NVFlash
4 - Custom recovery
5 - Custom ROM
I don't even know if these steps are in proper order, but seems that so many things could go wrong.. Could you help me doing this easily and problem free? I need to do something to take full advantage of my TF700.. It clearly isn't working properly on stock.
Thanks.
Click to expand...
Click to collapse
I recently wrote a tutorial on Android Central for people who are new to flashing. Check it out and if anything is left unclear - ask
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html

Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.

madz78 said:
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
Click to expand...
Click to collapse
You don't need to be rooted to flash a custom ROM. You can root from 14.8 as you don't need to go to 14.10. If you are on 10.4.4.18 you are on a really old boot loader for 4.1 and will need to upgrade if you want to unlock and flash the latest ROMs.

madz78 said:
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
Click to expand...
Click to collapse
Jeez - where did you dig up this version? I believe that was one of the first JB versions? Yes, Motochopper should work, but: Why root if you can't use Goo Manager to get a custom recovery installed? If that is your goal....
Yes, you can just root the stock ROM, but it does not give you that many options to improve the performance of this tablet. And any custom rom is rooted - so why bother?
To have NVflash is great and a wonderful reassurance and I do flash with greater abandon since I got them, but generating the blobs was the most stressful procedure in my limited flashing experience.
I don't know how comfortable you are with using cmd and fastboot - but I sure was glad to have some experience with flashing recoveries and such before I started it!
Generating the NVflash blobs involves flashing a bootloader and recovery build just for that procedure, so you need to know how to flash those in the first place (and how to flash back to your daily driver recovery/bootloader afterrwards).
There's nowhere for you to go without a custom recovery. Start with that.
I have no idea if the recovery most of us use (TWRP 2.6.1 or 2.6.3.1 - both are fine) works with the BL you currently have.
So I would update to the latest firmware, fastboot TWRP and then install CROMi-X.
You can dive into getting your NVflash blobs as soon as you have TWRP installed - that's up to you.
Edit: sbdags was faster - as usual
So there you have it: You have to update your stock firmware before you install TWRP

Wow guys.. This is why i never flash anything since bada on my Wave..
It's all so technical, confusing and intimidating.. God!!
Ok. I really need to start understanding this, so, if I got it right, I don't need to root because the custom ROM is already rooted.. Good!
Now the hard part. Please be patient and gentle, explain me like I'm 5 yo child.
- If I understood correctly first thing is upgrade FW, but to which FW should i upgrade? 10.6.1.14.10 or 10.6.1.14.8? If custom ROM is rooted, does the FW matter or not?
- Next comes recovery. Again, which one should I choose? (sdbags your opinion would be really important for me here, considering CROMi-X 5.2.2 is developed by you and the ROM i chose)
- I think I'll leave any ROM questions for later, after i finally understand these first 2 steps.
Also, regarding NVFlash, what the bleep is blobs? I'm comfortable with cmd but never used fastboot.
Thanks again!

madz78 said:
Wow guys.. This is why i never flash anything since bada on my Wave..
It's all so technical, confusing and intimidating.. God!!
Click to expand...
Click to collapse
Naaah - if I understood it, it can't be technical Just take your time, read - Google is your friend.
Ok. I really need to start understanding this, so, if I got it right, I don't need to root because the custom ROM is already rooted.. Good!
Click to expand...
Click to collapse
See? You got that right already.
Now the hard part. Please be patient and gentle, explain me like I'm 5 yo child.
- If I understood correctly first thing is upgrade FW, but to which FW should i upgrade? 10.6.1.14.10 or 10.6.1.14.8? If custom ROM is rooted, does the FW matter or not?
Click to expand...
Click to collapse
It does not matter. As long as you upgrade to a 10.6.1.x version, your bootloader will be compatible with TWRP 2.6.1 or 2.6.3.1 - see below.
- Next comes recovery. Again, which one should I choose? (sdbags your opinion would be really important for me here, considering CROMi-X 5.2.2 is developed by you and the ROM i chose)
- I think I'll leave any ROM questions for later, after i finally understand these first 2 steps.
Click to expand...
Click to collapse
sbdags is currently recommending TWRP 2.6.1. That is the version he included in the bootloader/TWRP package he provides in the OP (Original Post) of the CROMi-X thread.
To elaborate: In flashing custom roms the most important aspect is that you always have a compatible bootloader/recovery combination. You use your recovery to flash roms, bootloaders, kernels, wipe all or part of your SD card - the works.
If your recovery gets corrupted but you can still boot into the bootloader, you can install a new recovery using the fastboot protocol (which provides low level access from your computer). If your bootloader gets corrupted (and the most common cause is the wrong recovery) and you cannot boot into recovery, NVflash is your last chance to recover the tablet because: no bootloader = no fastboot access.
The easiest way to get a current bootloader in your situation would be to upgrade your stock firmware. The risk for something to go wrong is close to negative 1
Then you would download TWRP 2.6.1 for the TF700 from the Teamwin website and use the fastboot protocol to install it to it's proper partition.
Risk level is very low if you can follow the instructions in my little tutorial or in the Minimal ADB Fastboot Tool thread.
Once you have TWRP installed (and you tested that it's working) you could - and this is totally optional - flash the bootloader/TWRP package from sbdags OP. Just to make 100% sure you are on the correct combo.....
Also, regarding NVFlash, what the bleep is blobs? I'm comfortable with cmd but never used fast boot.
Thanks again!
Click to expand...
Click to collapse
A blob is a file - better: an image. Binary Large Object is the origin, I believe. For a technical explanation don't ask me! Go here:
http://en.m.wikipedia.org/wiki/Binary_large_object
If you look into the Asus firmware zip file, inside is a blob and a meta data file (if memory serves me right). The blob is the system image.

What if while you are flashing a firmware and your power supply is reaching 0%, could it be a high risk? :silly:

LetMeKnow said:
What if while you are flashing a firmware and your power supply is reaching 0%, could it be a high risk? :silly:
Click to expand...
Click to collapse
Damn you! I was trying to reassure this chap! LOL
There's no remedy for stupidity - so as a scientist you just ignore what you can't account for, right?

berndblb said:
Damn you! I was trying to reassure this chap! LOL
There's no remedy for stupidity - so as a scientist you just ignore what you can't account for, right?
Click to expand...
Click to collapse
Just asked a question and thanks for helping... Hahaha:laugh:

LetMeKnow said:
Just asked a question and thanks for helping... Hahaha:laugh:
Click to expand...
Click to collapse
Yes, a just a little, totally correct but diabolical question.....
Didn't know you had that evil streak in you, friend

berndblb said:
Yes, a just a little, totally correct but diabolical question.....
Didn't know you had that evil streak in you, friend
Click to expand...
Click to collapse
I am trying to relax from a long day of work and tiring of tweaking my device... I am looking for someone to talk to.. Maybe, I need to give up my device and back to my normal boring life...

berndblb said:
Naaah - if I understood it, it can't be technical Just take your time, read - Google is your friend.
See? You got that right already.
It does not matter. As long as you upgrade to a 10.6.1.x version, your bootloader will be compatible with TWRP 2.6.1 or 2.6.3.1 - see below.
sbdags is currently recommending TWRP 2.6.1. That is the version he included in the bootloader/TWRP package he provides in the OP (Original Post) of the CROMi-X thread.
To elaborate: In flashing custom roms the most important aspect is that you always have a compatible bootloader/recovery combination. You use your recovery to flash roms, bootloaders, kernels, wipe all or part of your SD card - the works.
If your recovery gets corrupted but you can still boot into the bootloader, you can install a new recovery using the fastboot protocol (which provides low level access from your computer). If your bootloader gets corrupted (and the most common cause is the wrong recovery) and you cannot boot into recovery, NVflash is your last chance to recover the tablet because: no bootloader = no fastboot access.
The easiest way to get a current bootloader in your situation would be to upgrade your stock firmware. The risk for something to go wrong is close to negative 1
Then you would download TWRP 2.6.1 for the TF700 from the Teamwin website and use the fastboot protocol to install it to it's proper partition.
Risk level is very low if you can follow the instructions in my little tutorial or in the Minimal ADB Fastboot Tool thread.
Once you have TWRP installed (and you tested that it's working) you could - and this is totally optional - flash the bootloader/TWRP package from sbdags OP. Just to make 100% sure you are on the correct combo.....
A blob is a file - better: an image. Binary Large Object is the origin, I believe. For a technical explanation don't ask me! Go here:
http://en.m.wikipedia.org/wiki/Binary_large_object
If you look into the Asus firmware zip file, inside is a blob and a meta data file (if memory serves me right). The blob is the system image.
Click to expand...
Click to collapse
The Asus blob actually contains the system image, kernel, recovery, bootloader and partition table.

unlocking bootloader zenfone ultra

Hi all
ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago,
my friend wanted to see if my phone could be charged with a dash charger,
where others wouldnt
my battery was already low and overnight it ran out
and when i was charging it and tried to boot
it ran into the dm-verity in eio mode issue
apparently the device is corrupt now
so i want to flash it, but it wont work
probably bcs the device is still locked
and for the life of mine, i dont know how to unlock it
my phone only has fastboot, recovery, adb, sd options now
so .apk wont help i think
i did manage to get twrp on it
who knows how i can get it unlocked?
and perhaps how to flash my phone all together?
i have the firmware from asus themselves
source code too
but their unlocker is in .apk, so of little help

Hi, is there anyone have their AZ3U with unlocked bootloader?
Thank you

bbmuje said:
Hi, is there anyone have their AZ3U with unlocked bootloader?
Thank you
Click to expand...
Click to collapse
I'm in the same situation...for some reason, I can't even get the Bootloader interface or the Composite ADB interface drivers to run properly on Win10.
There is a way to, supposedly, unlock without the .apk tool (that no longer seems to work).
fastboot flash all unlock_ ZU680KL.raw
I have no idea if that works at all, but all you'd need is a working fastboot interface...

Dm-verity
dennizunsal said:
Hi all
ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago,
my friend wanted to see if my phone could be charged with a dash charger,
where others wouldnt
my battery was already low and overnight it ran out
and when i was charging it and tried to boot
it ran into the dm-verity in eio mode issue
apparently the device is corrupt now
so i want to flash it, but it wont work
probably bcs the device is still locked
and for the life of mine, i dont know how to unlock it
my phone only has fastboot, recovery, adb, sd options now
so .apk wont help i think
i did manage to get twrp on it
who knows how i can get it unlocked?
and perhaps how to flash my phone all together?
i have the firmware from asus themselves
source code too
but their unlocker is in .apk, so of little help
Click to expand...
Click to collapse
From my experience -
You'll need to first unbrick your locked phone with the dm-verity in EIO mode. YT has video with a procedure that worked for me with a couple of tweaks which I posted a reply to. It uses some images and ADB in sideload mode.
Link to YT video tutorial that worked for me:
See my comment under John C in the YT video for slight differences for my experience.
Bootloader locked for this phone is an issue from ASUS. It no longer works and is not worth pursuing IMO. However you don't need the bootloader unlocked to install TWRP and to gain Root - contrary to many posts here in XDA.
I successfully installed TWRP via ADB and my bootloader is still Locked. See other OP posts here on XDA for root of this device. You'll find a procedure that used TWRP and SuperSu, however I used TWRP and Magisk and that is what I recommend. Also helpful to get an SD card format it for FAT-32 (not ex-FAT).
You'll need to acquire the TWRP image for this device. You'll also need to acquire Magisk flash Zip and the Magisk apk images. Basically procedure is factory reset, boot into recovery mode, fastboot flash recovery TWRP image.
After you gain TWRP install flash Magisk from Zip.
Hopefully this helps you and others. YMMV of course and proceed at your own risk. It is best to do your own research, and gather all of the files you need ahead of time.

jrchester said:
Dm-verity
From my experience -
You'll need to first unbrick your locked phone with the dm-verity in EIO mode. YT has video with a procedure that worked for me with a couple of tweaks which I posted a reply to. It uses some images and ADB in sideload mode.
Bootloader locked for this phone is an issue from ASUS. It no longer works and is not worth pursuing IMO. However you don't need the bootloader unlocked to install TWRP and to gain Root - contrary to many posts here in XDA.
I successfully installed TWRP via ADB and my bootloader is still Locked. See other OP posts here on XDA for root of this device. You'll find a procedure that used TWRP and SuperSu, however I used TWRP and Magisk and that is what I recommend. Also helpful to get an SD card format it for FAT-32 (not ex-FAT).
You'll need to acquire the TWRP image for this device. You'll also need to acquire Magisk flash Zip and the Magisk apk images. Basically procedure is factory reset, boot into recovery mode, fastboot flash recovery TWRP image.
After you gain TWRP install flash Magisk from Zip.
Hopefully this helps you and others. YMMV of course and proceed at your own risk. It is best to do your own research, and gather all of the files you need ahead of time.
Click to expand...
Click to collapse
Hi, tried to find post introducing root with bootloader locked in this forum but with no luck. Could you kindly share a link to that post with me? I also wonder which YouTube video tutorial you watched is specifically about the bootloader unlock on Zenfone 3 ultra. Thank you in advance!

kenarp said:
Hi, tried to find post introducing root with bootloader locked in this forum but with no luck. Could you kindly share a link to that post with me? I also wonder which YouTube video tutorial you watched is specifically about the bootloader unlock on Zenfone 3 ultra. Thank you in advance!
Click to expand...
Click to collapse
Updated my OP to add link to the YT video, which is about unbricking the Zenfone 3 Ultra.
Other info my post discusses how I obtained root (not on YT video) without modifying bootloader.
As always, "Use at your own risk" and YMMV.
Good luck.

@kenarp – did you manage to get root without using the unlock tool? If yes, could you share your steps (and what may have went wrong during your procedure) in a little more detail than jrchester did? That would be great!
I am somewhat reluctant to simply give it a try because I already spent days with this some time ago, without any success...

neophilos said:
@kenarp – did you manage to get root without using the unlock tool? If yes, could you share your steps (and what may have went wrong during your procedure) in a little more detail than jrchester did? That would be great!
I am somewhat reluctant to simply give it a try because I already spent days with this some time ago, without any success...
Click to expand...
Click to collapse
“Basically procedure is factory reset, boot into recovery mode, fastboot flash recovery TWRP image.” This part from jrchester's reply didn't work for me. The bootloader is locked which prevents me from doing any fastboot flash operations, have no idea how jrchester achieved.
I have no idea what could be helpful from the YouTube video he posted either, I just want to either unlock the bootloader or (if possible)flash the recovery+moded rom with the bootloader locked, while my phone is not bricked.
I also had no luck to find any posts as he mentioned "See other OP posts here on XDA for root of this device. You'll find a procedure that used TWRP and SuperSu, however I used TWRP and Magisk and that is what I recommend."

neophilos said:
@kenarp – did you manage to get root without using the unlock tool? If yes, could you share your steps (and what may have went wrong during your procedure) in a little more detail than jrchester did? That would be great!
I am somewhat reluctant to simply give it a try because I already spent days with this some time ago, without any success...
Click to expand...
Click to collapse
See my previous posts on XDA developer forum. Two separate Ultra 3 issues are discussed, both Unbricking phone (Yt link in OP added with procedure given), and then root and TWRP without unlocking bootloader. Both completed successfully. Still using my Ultra 3 today (rooted and still bootloader locked) with no issues. No special unlock tools used other than listed procedure with ADB Sideload, TWRP, and Magisk. Use at your own risk and YMMV.

kenarp said:
“Basically procedure is factory reset, boot into recovery mode, fastboot flash recovery TWRP image.” This part from jrchester's reply didn't work for me. The bootloader is locked which prevents me from doing any fastboot flash operations, have no idea how jrchester achieved.
I have no idea what could be helpful from the YouTube video he posted either, I just want to either unlock the bootloader or (if possible)flash the recovery+moded rom with the bootloader locked, while my phone is not bricked.
I also had no luck to find any posts as he mentioned "See other OP posts here on XDA for root of this device. You'll find a procedure that used TWRP and SuperSu, however I used TWRP and Magisk and that is what I recommend."
Click to expand...
Click to collapse
Thanks for your reply. As far as I understand the info on this in other threads about this non device-specific question the verity check at boot will not allow booting from an altered boot partition (compared to OEM). If you flash Magisk it will always alter the OEM boot partition which is why the bootloader needs to be unlocked to allow for the boot to happen.
@jrchester, I guess you are quite lucky that your phone works with root eventhough the bootloader status says locked. However, this can probably not be reproduced from what I know and from what @kenarp reports.

Definitely incorrect. See more recent posts of mine on another XDA Forum Developer thread. Two other users recently confirmed the exact same process worked for them.
Ref: https://forum.xda-developers.com/t/...zenfone-3-ultra-zu680kl.3565595/post-86634507

Unable to Root/Flash TWRP on OnePlus 7 Pro

Greetings to anyone that may see this - I am new to the android root thingy, so I apologize in advance if I have a stupid question. I have only rooted an old tablet with Kingoroot which used SuperSU as the root manager. First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.) I tried the regular guacamole image, but the phone didn't seem to want to boot the image. I am going to try guacamoleb. If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!

UrAverageNerd said:
First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.)
Click to expand...
Click to collapse
Haven't seen guacomoleb (different code name to me implies a different device, but I'm not sure in this case). Just use the file from the dev's TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Unofficial version -75 is the current version. Use the version ( Q versus Pie) for your current Android/OOS version. Might be obvious, but some folks have asked about that.
UrAverageNerd said:
If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
Click to expand...
Click to collapse
Per the developer in his thread I linked above, for a stock device, if you flash TWRP, you should root (with Magisk) or the phone might not boot. Some folks have reported that they can flash TWRP and not Magisk and still boot. But there is not point in risking it, since your intent is to root anyway. Fastboot boot TWRP img, then flash TWRP installer zip, and just flash Magisk right away at the same time, then reboot. It's pretty easy.
Also note that installing TWRP is somewhat optional. You can just fastboot boot TWRP img, then flash Magisk to root. It is a matter of preference whether to have TWRP installed or not, and folks are pretty split on this. My opinion, TWRP installed (while not required) does give some potentially useful features if things ever go wrong. I personally don't see much advantage to not installing TWRP, but just my opinion.

Hi there. I ran into similar problems when I was a Root noobie (which I still am). Try the All In One Tool that can be found in this forum. That will help you flash TWRP. It got me there when I was struggling to Flash TWRP.

redpoint73 said:
Haven't seen guacomoleb (different code name to me implies a different device, but I'm not sure in this case). Just use the file from the dev's TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Unofficial version -75 is the current version. Use the version ( Q versus Pie) for your current Android/OOS version. Might be obvious, but some folks have asked about that.
Per the developer in his thread I linked above, for a stock device, if you flash TWRP, you should root (with Magisk) or the phone might not boot. Some folks have reported that they can flash TWRP and not Magisk and still boot. But there is not point in risking it, since your intent is to root anyway. Fastboot boot TWRP img, then flash TWRP installer zip, and just flash Magisk right away at the same time, then reboot. It's pretty easy.
Also note that installing TWRP is somewhat optional. You can just fastboot boot TWRP img, then flash Magisk to root. It is a matter of preference whether to have TWRP installed or not, and folks are pretty split on this. My opinion, TWRP installed (while not required) does give some potentially useful features if things ever go wrong. I personally don't see much advantage to not installing TWRP, but just my opinion.
Click to expand...
Click to collapse
Thanks for your help. Apparently the Android Q unofficial build -75 doesn't have any mirrors. It's still searching. I like using TWRP because it's convenient if I wan't to flash something else without a PC or Mac.:laugh:

UrAverageNerd said:
Apparently the Android Q unofficial build -75 doesn't have any mirrors. It's still searching.
Click to expand...
Click to collapse
Something wrong with the "main" download link (androidfilehost)?

UrAverageNerd said:
Greetings to anyone that may see this - I am new to the android root thingy, so I apologize in advance if I have a stupid question. I have only rooted an old tablet with Kingoroot which used SuperSU as the root manager. First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.) I tried the regular guacamole image, but the phone didn't seem to want to boot the image. I am going to try guacamoleb. If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
Click to expand...
Click to collapse
Use adb & fastboot via powershell
Get the adb files in a folder
Copy the twrp.img to the adb folder and on phone /storage/emulated/0/
Get a copy of the twrp installer on your phone anywhere works
Open adb folder
Hold shift and right click a empty space
Open powershell & type
Adb boot bootloader
Fastboot boot twrp.img (you can drag and drop the file into powershell if your lazy like me)
Flash the twrp installer on your phone
Done?
Reboot and go back into recovery to see if it works
Tip for updates:
After you get the update
Flash via twrp
Then flash twrp (so you don't need your computer)
Flash magisk if you want superuser
Reboot
Reboot recovery
Flash magisk again (seems it takes two flashes)
None of the tools work for my devices anymore just powershell
All in one doesn't read my fastboot
Cmd has a remote error after attempting to boot it.

UrAverageNerd said:
First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.)
Click to expand...
Click to collapse
Just noticed that the TWRP "guacomoleb" is the "unified" version that works with both the OnePlus 7 and the 7 Pro. Shouldn't make a difference whether you use the "unified" version or the 7 Pro specific TWRP.

General Oneplus 9 and / 9 Pro TWRP

Just a reminder for people who only read the oneplus 9 forum and not oneplus 9 pro one:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
I tested it and flashed it on my oneplus 9 LE2110 and it works.
Again, as i always have to write to people.
Be careful, only do something you can undo.
Before you "Flash Current TWRP" do a full BACKUP!

Does said recovery perform full back-ups of partitions and restore features ?
Edit
I booted it up . Decrypts perfectly. Backed up modem just to see for myself. Rebooted back onto system . Booted twrp again and it found saved partition to restore. This makes life so much easier. Time to go get a full system backup !! Cool

Exactly. I'm super happy. Now the OnePlus 9 Is finally a good phone. Without TWRP it's just risky.
Im sure some bugs are still there but it looks very promising.

noname122414 said:
Exactly. I'm super happy. Now the OnePlus 9 Is finally a good phone. Without TWRP it's just risky.
Im sure some bugs are still there but it looks very promising.
Click to expand...
Click to collapse
And this is huge for many people roaming around here on carrier variants . Now super easy to restore modems to make switch to global.or eu or whatever.

Hi there, I have a question:
When you have a new device, would the following work:
1. Unlock bootloader
In fastboot mode:
2.
Code:
fastboot boot c:\twrp.img
In TWRP
3. Install TWRP
4. Install Magisk
5. Reboot - then you have Root, TWRP?
6. Upgrades can than be done in TWRP by installing the files and than intalling again TWRP and afterwards Magisk?
Best
Axel

It appears you are asking. If I am incorrect, my apologies. With the 6t (also a a/b OP device)
The process I always used was
1) reboot to bootloader
2) boot twrp.img
3) install twro zip
4) reboot recovery
5) upon TWRP reboot, install magisk
6) profit.
Anytime I tried to go ahead and install Magisk in the same round as installing TWRP, it would install to the opposite slot making me have to do the whole process over again. Ymmv

XDA is Great, and, yet, at the same time: XDA is very challenging.
With so many able to contribute, and the lack of external editing capacity ( unlike SO ),
it's difficult to distill the information.
Okay, Great! There's a TWRP for the OnePlus 9 !
I used TWRP 3.5 and Magisk to root a Lenovo Tab M10, without any need for external input.
The Answer I'm looking for here is: Am I able to install / root / whatever my T-Mo OP 9 with TWRP ?
Does anyone have any definitive solutions ?
Thank You, in Advance, for any assistance !

barguybrady said:
XDA is Great, and, yet, at the same time: XDA is very challenging.
With so many able to contribute, and the lack of external editing capacity ( unlike SO ),
it's difficult to distill the information.
Okay, Great! There's a TWRP for the OnePlus 9 !
I used TWRP 3.5 and Magisk to root a Lenovo Tab M10, without any need for external input.
The Answer I'm looking for here is: Am I able to install / root / whatever my T-Mo OP 9 with TWRP ?
Does anyone have any definitive solutions ?
Thank You, in Advance, for any assistance !
Click to expand...
Click to collapse
Is your bootloader unlocked? If yes then you could boot to fastboot and fastboot boot twrp.img. You will have your answer then.

MrSteelX said:
Is your bootloader unlocked? If yes then you could boot to fastboot and fastboot boot twrp.img. You will have your answer then.
Click to expand...
Click to collapse
Sadly, No, boot-loader is locked. Never encountered this on both previous OP 6t's.
Hence my confusion. When I walked out of the t-Mo store with my 6t, I had No issues.
I used the wonderful mauronofios tool, to do it All with no troubles.
crash my 6t, forced to take a "9 5g" from t-Mo, and now I am regretting it.
Wondering what has changed, and by whom..? t-Mo change policies, or OnePlus ?
Actually, I've been a t-Mo customer for 16 Years ! First time I've ever had to "Ask Permission" to have my phone, or my SIM unlocked...

barguybrady said:
Sadly, No, boot-loader is locked. Never encountered this on both previous OP 6t's.
Hence my confusion. When I walked out of the t-Mo store with my 6t, I had No issues.
I used the wonderful mauronofios tool, to do it All with no troubles.
crash my 6t, forced to take a "9 5g" from t-Mo, and now I am regretting it.
Wondering what has changed, and by whom..? t-Mo change policies, or OnePlus ?
Actually, I've been a t-Mo customer for 16 Years ! First time I've ever had to "Ask Permission" to have my phone, or my SIM unlocked...
Click to expand...
Click to collapse
You should start a separate thread for all that. Kinda want to keep on topic to make it less confusing for everyone

Has anyone been able to mount a usb drive? ive tried everything and it just looks to not be functional.
strangely enough, i heard TWRP backups are iffy right now but have already restored from one using this release in the past week. happy that works

mattie_49 said:
And this is huge for many people roaming around here on carrier variants . Now super easy to restore modems to make switch to global.or eu or whatever.
Click to expand...
Click to collapse
Just installed it - thanks OP.
Does anyone know if I can jdirtyflash the global rom 11.2.7.7 over the EU rom which is currently on 11.2.7.7 in twrp?
I was originally on global (le2110) but flashed EU via update. Now I want to go back to global.

applyscience said:
Has anyone been able to mount a usb drive? ive tried everything and it just looks to not be functional.
strangely enough, i heard TWRP backups are iffy right now but have already restored from one using this release in the past week. happy that works
Click to expand...
Click to collapse
Full system everything. User data. ? Did it work

mattie_49 said:
Full system everything. User data. ? Did it work
Click to expand...
Click to collapse
i dont know i have been bricked for 5 days ever since i attempted the lineage release

applyscience said:
i dont know i have been bricked for 5 days ever since i attempted the lineage release
Click to expand...
Click to collapse
Just lineage no kernel no special cam?

mattie_49 said:
Just lineage no kernel no special cam?
Click to expand...
Click to collapse
nah. just lineage. pretty sure i deal with support again tomorrow. fun...

Need help...
I typed Fastboot boot twrp.img instead of fastboot flash boot twrp.img
And that was to boot_a
So then i tried fastboot flash boot_b twrp.img
It wont load the recovery now. Phone wont boot up unless i
fastboot boot patched11.2.7.7DA.img
I even try to install Magisk directly and it fails.
Can I get some help. Dont even wanna restart my phone.
Thank you
All Good Now..... I Figured It Out!

How to fix this

id avoid TWRP if on 11.2.8.8 already. it can boot from fastboot and even install itself as your recovery but it will not mount data. i tried the refresh sizes trick in backup and then the default_password for password to decrypt and nothing. pretty sure twrp mishaps are what bricked my phone last too . thankfully it still boots, just the recovry section is effected
ill try and flash the OTA zip tomorrow. sick of messing with it for now lol

Are we still avoiding twrp

Pixel Experience 13 questions

Hey y'all,
I'm switching back to Android after 3 years on iOS and I'm a bit stuck on some changes.
First off, battery life on OOS was terrible and they ended support for OP7Pro this year, with no more major (or even security updates) so I decided to get a custom ROM, and I got this Pixel Experience ROM from here. I'm stuck with a few things:
Trying to root it, looks like the procedure is as simple as patch the boot image in that link with Magisk and flash it from the bootloader via "fastboot flash boot patched.img" but every time I do that and reboot, I get the 1+ splash screen and then nothing, black screen. If I boot back in bootloader and flash the original boot image via "fastboot flash boot original.img" it boots again. Same happens if I just run "fastboot boot patched.img", completely black until I reboot. Does anyone know what could be going wrong here?
Is there any way to install TWRP and make a NAND backup with this ROM? I've been out of the game for a while and I'm confused about why there's no recovery partition but there's A and B partitions, and I keep reading that TWRP can't decrypt data or something like that (I'm pretty sure it could 3 years ago tho)
Thanks!

I would never switch to an iphone for a personal phone because I can't stand it.
I have'nt had to root op7 pro till now because I had enough options. now with support ending I'm on 12.
If you have already upgraded to 12 like me you will probably have to downgrade to 11 first to unlock the bootloader if you haven't unlocked it already. I will not try till may when I get back from my vacation because I can't afford for the phone to go crazy right now. before you attempt to downgrade if you do make sure you back up everything to another spare phone or tablet and make sure you have a backup plan in case you soft brick before you attempt it. https://droidwin.com/downgrade-oneplus-7-7t-7t-pro-android-12-to-android-11-2-methods/ . Man if there is a new way to not have to first downgrade to android 11 someone please chime in, as it would reduce my headaches. Also I need someone to clarify if after I unlock the bootloader, I'll have to flash back to 12 via twrp and reformat the phone again to install Pixel experience?

dragancla said:
boot image in that link
Click to expand...
Click to collapse
That is probably where the problem is.
Which boot image to use depends on exactly which OS version you’re using, and the exact model number of your device.
A lot has changed in the Android world in the last 3 years.

TheMystic said:
That is probably where the problem is.
Which boot image to use depends on exactly which OS version you’re using, and the exact model number of your device.
A lot has changed in the Android world in the last 3 years.
Click to expand...
Click to collapse
Yeah, but that IS the boot image for that OS version and that device, that's why you can download both the ROM and the boot image for that ROM from the same link I posted. If I boot that specific image the device works fine. If I patch that same boot image and boot it, it doesn't work.

dragancla said:
Yeah, but that IS the boot image for that OS version and that device, that's why you can download both the ROM and the boot image for that ROM from the same link I posted. If I boot that specific image the device works fine. If I patch that same boot image and boot it, it doesn't work.
Click to expand...
Click to collapse
Then it means that the patching is not happening properly. Something is not right with the patched image, even if you don't get any errors. Search for this problem on Google. Also see if you can extract the boot image of your device yourself, instead of using the one you have in that link.

billperrotta said:
I would never switch to an iphone for a personal phone because I can't stand it.
I have'nt had to root op7 pro till now because I had enough options. now with support ending I'm on 12.
If you have already upgraded to 12 like me you will probably have to downgrade to 11 first to unlock the bootloader if you haven't unlocked it already. I will not try till may when I get back from my vacation because I can't afford for the phone to go crazy right now. before you attempt to downgrade if you do make sure you back up everything to another spare phone or tablet and make sure you have a backup plan in case you soft brick before you attempt it. https://droidwin.com/downgrade-oneplus-7-7t-7t-pro-android-12-to-android-11-2-methods/ . Man if there is a new way to not have to first downgrade to android 11 someone please chime in, as it would reduce my headaches. Also I need someone to clarify if after I unlock the bootloader, I'll have to flash back to 12 via twrp and reformat the phone again to install Pixel experience?
Click to expand...
Click to collapse
I already have Pixel Experience installed, so my bootloader is unlocked. Has been since I bought the phone 3 years ago

TheMystic said:
Then it means that the patching is not happening properly. Something is not right with the patched image, even if you don't get any errors. Search for this problem on Google. Also see if you can extract the boot image of your device yourself, instead of using the one you have in that link.
Click to expand...
Click to collapse
Google yielded no results, decided to post here to see if anyone else ran into this, I'll try to extract it myself somehow.

Coming out of left field but maybe you need to return to stock with bootloader unlocked. Flash 12 ota then rewipe for PE to get 12 latest firmware? https://www.xda-developers.com/oneplus-7-7t-end-of-life-final-update/
used to flash otas through TWRP when I had a rooted op5T with an unlocked bootloader. So Sad, Oxygen was so good till this last crummy update. Now they are forcing my hand to return to custom roms since OP insists on abandoning Support for the best phone they ever made.

Nothing worked, so I fixed it by wiping the phone and starting from scratch. Guess something bugged out.

thats usually the end all solution. but I have seen situations where you have to be on latest stock firmware to continue. I assume you don't have to copy any partitions because this software is already past Android 10 where treble was first introduced? I'm just asking as many questions as possible because I'm planning to overhaul in may. Did you use the pixel experience flashing instructions from pixel experience.org?

ill probably flash the ota back to twelve through twrp. then flash pixel experience recovery over that when I wipe and start over after the downgrade and bootloader unlock.

billperrotta said:
thats usually the end all solution. but I have seen situations where you have to be on latest stock firmware to continue. I assume you don't have to copy any partitions because this software is already past Android 10 where treble was first introduced? I'm just asking as many questions as possible because I'm planning to overhaul in may. Did you use the pixel experience flashing instructions from pixel experience.org?
Click to expand...
Click to collapse
I was on latest stock (12) before I started doing this. Had my bootloader unlocked since Android 9. Since it's impossible to do anything without unlocking it, that's your first step. I posted the link to PE website in my first post. Didn't copy any partitions. I just installed it and rooted it with a few commands from terminal (with the phone connected):
adb reboot bootloader
fastboot flash boot BOOT.img
fastboot reboot recovery
-- on the phone: wipe data, select install from sideload --
adb sideload ROM.zip
adb reboot
-- on the phone: wait for it to boot, enable developer options --
adb install MAGISK.apk
adb push BOOT.img sdcard/Download
-- on the phone: patch the boot image with Magisk --
adb pull sdcard/Download/magisk_patched-25200_xxxxx.img
adb reboot bootloader
fastboot flash boot magisk_patched-25200_xxxxx.img
fastboot reboot
That's it, installed and rooted. Stop at step 6 if you don't want root.