Database Develop

[Q] Rooting Questions and Advice

I am a root noob, i rooted my HTC Desire HD a few years ago, but then, it just seemed easier. Now i want to root and install a custom rom on my xperia Z, but it seems all the guides are made for experts? so i google'd and seemed to get hold of a guide, but not sure if its correct or outdated, i obviously dont wanna brick my phone.
So, first question, can someone link me to a valid, easy guide / tutorial, or atleast some reading material on how to root my Z? its the s6603, with Android version 4.4.2.
Secondly when it comes to custom roms, once again, it feels like there is no more guides for dummies like me, i know on my desire, i used to copy the zip over, erase a few things, and then install from zip, and it was flashed, but now i see things like this
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
Click to expand...
Click to collapse
This makes sense, except for the :
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
What is fastboot, googling a bit it seems its a program i should install on Windows?
the boot.img, do i copy that out of the cm10.zip file?
To where, the phones SD Card? to Windows?
fastboot reboot, does this mean reboot the phone from fastboot? or is that the command that should be typed in?
Sorry if i come off as dumb, i am not, im just a noob. And i dont want the info spoonfed to me, i like to do my own research before asking stupid questions, but the info on the internet, is just to much, no 2 articles are talking about the same method, programs, etc
Thanks,

To root use towelroot.
To flash firmware use flashtool.
You can find tutorial on flashtool here somewhere.

endlesslyonline said:
I am a root noob, i rooted my HTC Desire HD a few years ago, but then, it just seemed easier. Now i want to root and install a custom rom on my xperia Z, but it seems all the guides are made for experts? so i google'd and seemed to get hold of a guide, but not sure if its correct or outdated, i obviously dont wanna brick my phone.
So, first question, can someone link me to a valid, easy guide / tutorial, or atleast some reading material on how to root my Z? its the s6603, with Android version 4.4.2.
Secondly when it comes to custom roms, once again, it feels like there is no more guides for dummies like me, i know on my desire, i used to copy the zip over, erase a few things, and then install from zip, and it was flashed, but now i see things like this
This makes sense, except for the :
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
What is fastboot, googling a bit it seems its a program i should install on Windows?
the boot.img, do i copy that out of the cm10.zip file?
To where, the phones SD Card? to Windows?
fastboot reboot, does this mean reboot the phone from fastboot? or is that the command that should be typed in?
Sorry if i come off as dumb, i am not, im just a noob. And i dont want the info spoonfed to me, i like to do my own research before asking stupid questions, but the info on the internet, is just to much, no 2 articles are talking about the same method, programs, etc
Thanks,
Click to expand...
Click to collapse
Hi
To root your device first download app called TOWELROOT just install it and open it then click the button then go and install SUPER SU APP FROM HERE
and open it. You will get a popup window saying SuperSU binaries need to be updated. Click ok and then NORMAL wait until it's finish and you rooted your phone now
And the FASTBOOT:
fastboot is a boot mode that the device go into it to modifie some system things without need to permission from the device or rooting. BUT the fastboot flash boot boot.IMG is a command that you type in in the command prompt window (CMD) but you need to unlock the device's bootloader to do that or.. You will get COMMAND DID NOT SUCCESS error in CMD
Fastboot reboot command used to get the device out from fastboot mode. Use it instead of unplugging it
and as I told you fastboot not software or app. That zip file you download is drivers to make the PC recognise the device in the fastboot mode and you need to open the command prompt window in the folder you extract the fastboot drivers or it's can be also called ADB or Android debug bridge and the boot.IMG file you need to extract in from the the ROM you trying to flash and put it in the same folder you extracted fastboot drivers
Tapatalk'ed from my Xperia™ Z (C6602) running Dirty Unicorns ROM!

Sorry, but i am still stuck, i installed the tr.apk, that went fine, then i installed SuperSU, it asked me to update, then it asked a message about Normal or TRWM/CWM(?), i choose normal, but it said failed, and i had to reboot phone, i did this, and superSU was installed, so i tried to fastboot, i got into fastboot, it detected the device, but it said
Sending boot (10132 KB) ...
OKAY
writing 'boot'...
FAILED (remote: command not allowed)
finished
i then rebooted with fastboot, and thought maybe that superSU was not fully installed?
so i went into superSU, and saw there was an option to clean and reinstall, i did that, it asked for the same update again normal or TRWM/CWM, and i chose the second option TRWM/CWM, it said it will reboot phone, and so it did.
I then went to play and downloaded an app to see if i have root, when it opened superSU popped up and asked if i wanted to grant access, i accepted.
but the program came back and said i dont have root?
So where is the poblem, with tr.apk? or supeSU.
Thanks for helping the noobie

endlesslyonline said:
Sorry, but i am still stuck, i installed the tr.apk, that went fine, then i installed SuperSU, it asked me to update, then it asked a message about Normal or TRWM/CWM(?), i choose normal, but it said failed, and i had to reboot phone, i did this, and superSU was installed, so i tried to fastboot, i got into fastboot, it detected the device, but it said
Sending boot (10132 KB) ...
OKAY
writing 'boot'...
FAILED (remote: command not allowed)
finished
i then rebooted with fastboot, and thought maybe that superSU was not fully installed?
so i went into superSU, and saw there was an option to clean and reinstall, i did that, it asked for the same update again normal or TRWM/CWM, and i chose the second option TRWM/CWM, it said it will reboot phone, and so it did.
I then went to play and downloaded an app to see if i have root, when it opened superSU popped up and asked if i wanted to grant access, i accepted.
but the program came back and said i dont have root?
So where is the poblem, with tr.apk? or supeSU.
Thanks for helping the noobie
Click to expand...
Click to collapse
After installing towelroot you have to open it and click on the button. This will root your device. After that you can continue with supersu

endlesslyonline said:
Sorry, but i am still stuck, i installed the tr.apk, that went fine, then i installed SuperSU, it asked me to update, then it asked a message about Normal or TRWM/CWM(?), i choose normal, but it said failed, and i had to reboot phone, i did this, and superSU was installed, so i tried to fastboot, i got into fastboot, it detected the device, but it said
Sending boot (10132 KB) ...
OKAY
writing 'boot'...
FAILED (remote: command not allowed)
finished
i then rebooted with fastboot, and thought maybe that superSU was not fully installed?
so i went into superSU, and saw there was an option to clean and reinstall, i did that, it asked for the same update again normal or TRWM/CWM, and i chose the second option TRWM/CWM, it said it will reboot phone, and so it did.
I then went to play and downloaded an app to see if i have root, when it opened superSU popped up and asked if i wanted to grant access, i accepted.
but the program came back and said i dont have root?
So where is the poblem, with tr.apk? or supeSU.
Thanks for helping the noobie
Click to expand...
Click to collapse
To check whether you are rooted or not download root checker app from play store and install.
The app will show your root status.

Thats what I did?
After installing tr.apk, I clicked on the make it ra1n button. And root checker says im not rooted.
Will I mess up if I try the process again?
Should I maybe dona factory reset first? Before trying again
Thanks

endlesslyonline said:
Thats what I did?
After installing tr.apk, I clicked on the make it ra1n button. And root checker says im not rooted.
Will I mess up if I try the process again?
Should I maybe dona factory reset first? Before trying again
Thanks
Click to expand...
Click to collapse
Do you have recovery installed?

Excuse my ignorance, but what is recovery?
But i think it would be safe to say, if I dont know what it is , I dont have it installed

endlesslyonline said:
Excuse my ignorance, but what is recovery?
But i think it would be safe to say, if I dont know what it is , I dont have it installed
Click to expand...
Click to collapse
Do you have teamviewer installed on your PC?

androidtweaker1 said:
Do you have teamviewer installed on your PC?
Click to expand...
Click to collapse
I dont, but i am busy downloading it now
I checked again, I took the chance and re-ran tr.apk, and clicked on "make it ra1n" again, i then went RootChecker, and it confirms i have root access.
So, off to superSU again, and it asks again to "The SU binary needs to be updated. Continue?"
I then say yes, and I am confronted with the "If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary ..."
I obviously dont have a custom recovery installed, and if i understand correctly, the boot.img in the cm10.zip folder, would be the recovery right? If so, i wold then choose normal, because i dont have custom recovery.
If the boot.img is not the custom recovery, what is then? how do i get it?
i tried to fastboot flash boot.img, once again now, after making it rain, but before running superSU, but still gave the error, that it could not write.
What am i doing wrong? am i missing steps here?

endlesslyonline said:
I dont, but i am busy downloading it now
I checked again, I took the chance and re-ran tr.apk, and clicked on "make it ra1n" again, i then went RootChecker, and it confirms i have root access.
So, off to superSU again, and it asks again to "The SU binary needs to be updated. Continue?"
I then say yes, and I am confronted with the "If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary ..."
I obviously dont have a custom recovery installed, and if i understand correctly, the boot.img in the cm10.zip folder, would be the recovery right? If so, i wold then choose normal, because i dont have custom recovery.
If the boot.img is not the custom recovery, what is then? how do i get it?
i tried to fastboot flash boot.img, once again now, after making it rain, but before running superSU, but still gave the error, that it could not write.
What am i doing wrong? am i missing steps here?
Click to expand...
Click to collapse
That's because you have to unlock your bootloader first. Please use the search function and read about the risks etc of unlocking your bootloader.

St.Jimmy90 said:
That's because you have to unlock your bootloader first. Please use the search function and read about the risks etc of unlocking your bootloader.
Click to expand...
Click to collapse
Ugh, ok. Will do some research, this is not towards you, or any one in this thread, coz u are doing an awesome job helpimg me, and pointing me in the right direction. But why oh why was bootloader unlocking never even mentioned in the tutorials...
So what are my steps,
Download and run tr.apk
Then install and run supersu
Then unlock bootloader
Fastboot load boot.img
Then flash custom rom,
Or is the order wrong?

endlesslyonline said:
Ugh, ok. Will do some research, this is not towards you, or any one in this thread, coz u are doing an awesome job helpimg me, and pointing me in the right direction. But why oh why was bootloader unlocking never even mentioned in the tutorials...
So what are my steps,
Download and run tr.apk
Then install and run supersu
Then unlock bootloader
Fastboot load boot.img
Then flash custom rom,
Or is the order wrong?
Click to expand...
Click to collapse
You can flash stock based roms without unlocking the bootloader. Aosp based roms need an unlocked bootloader. If a rom needs an unlocked bootloader it is mentioned in the description like this [ub].
To unlock your bootloader root is NOT required.

Is there no all on one guide for the xperia z that includes, root, unlocking, flashing, etc. Im a tad scared to use part of this tutorial, part of that , etc

Second version towelroot (no need to restart) me also caused problems with the update of binaries, so suggest you First version.
Wysłane z mojego C6603 przy użyciu Tapatalka

OK, SUCCESS !!
Thanks to all that pointed me in the right direction. I ended up doing the following.
Downloading the SDK,
Went to sony's developer site, got the boot unlock code for my IMEI, fastboot, blah blah
flash'ed CM10 boot.img
and then installed CM10 from zip.
I am playing with the phone as i type this, so it worked
Now, one more noobie question, and i will leave you guys alone (for awhile)
If i decide to install CM11, do i just copy the zip over to the SDCard, wipe wipe install? or do i need to fastboot boot flash with the CM11 boot.img?
Same goes for any other rom, just wipe wipe flash, or fastboot everytime?
Thanks again

endlesslyonline said:
OK, SUCCESS !!
Thanks to all that pointed me in the right direction. I ended up doing the following.
Downloading the SDK,
Went to sony's developer site, got the boot unlock code for my IMEI, fastboot, blah blah
flash'ed CM10 boot.img
and then installed CM10 from zip.
I am playing with the phone as i type this, so it worked
Now, one more noobie question, and i will leave you guys alone (for awhile)
If i decide to install CM11, do i just copy the zip over to the SDCard, wipe wipe install? or do i need to fastboot boot flash with the CM11 boot.img?
Same goes for any other rom, just wipe wipe flash, or fastboot everytime?
Thanks again
Click to expand...
Click to collapse
At least that's the safe way. I hope you made a backup of your ta partition before unlocking the bootloader, otherwise your warranty is now void

St.Jimmy90 said:
At least that's the safe way. I hope you made a backup of your ta partition before unlocking the bootloader, otherwise your warranty is now void
Click to expand...
Click to collapse
Phone is out of warranty in any case, but yea, I did make a backup, or atleast I think I did. In clockworkmod, I went to backup and restore, and selected backup to sd card

endlesslyonline said:
Phone is out of warranty in any case, but yea, I did make a backup, or atleast I think I did. In clockworkmod, I went to backup and restore, and selected backup to sd card
Click to expand...
Click to collapse
He meant by partition back is backup your TA (trim area) PARTITION OR DRM KEYS TO RELOCK YOUR BOOTLOADER ANYTIME
Tapatalk'ed from my Xperia™ Z (C6602) running Dirty Unicorns ROM!

Bootloader flashfail

I made a mistake and did not turn on the debug mode. So when trying to unlock the bootloader using the tool here:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
it dint work. Now I keep getting "UTAG "flashfail" configured as fastboot" error. I have searched the forums and it seems I need to reflash the motorola boot img to get it to work.
Someone please help me out with it. I am on the latest 5.0.2 update for XT1068 - Indian version.

vicky_ag said:
I made a mistake and did not turn on the debug mode. So when trying to unlock the bootloader using the tool here:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
it dint work. Now I keep getting "UTAG "flashfail" configured as fastboot" error. I have searched the forums and it seems I need to reflash the motorola boot img to get it to work.
Someone please help me out with it. I am on the latest 5.0.2 update for XT1068 - Indian version.
Click to expand...
Click to collapse
ok download the boot.img and use mfastboot to flash

reefuge said:
ok download the boot.img and use mfastboot to flash
Click to expand...
Click to collapse
Links to the boot image please

vicky_ag said:
Links to the boot image please
Click to expand...
Click to collapse
heres a flashable zip if you have custom recovery, or just use the boot.img (5.0.2) from unzipped file
Code:
mfastboot.exe flash boot boot.img

That worked. But now having another issue
I have rooted a lot of phones but this is the first I am stumbling my way through it. I unlocked the bootloader by going to Motorola's site and then went ahead and tried to root the phone using the tool mentioned in original post.
So the tool pushes the boot.img and reboots the phone. Then even when the phones boots in TWRP, the computer keeps saying waiting for device.
Now when I try to do a normal boot, I get the warning from Motorola but then phone wont bootup. No matter how much I wait or even try to re-flash the above image.

vicky_ag said:
That worked. But now having another issue
I have rooted a lot of phones but this is the first I am stumbling my way through it. I unlocked the bootloader by going to Motorola's site and then went ahead and tried to root the phone using the tool mentioned in original post.
So the tool pushes the boot.img and reboots the phone. Then even when the phones boots in TWRP, the computer keeps saying waiting for device.
Now when I try to do a normal boot, I get the warning from Motorola but then phone wont bootup. No matter how much I wait or even try to re-flash the above image.
Click to expand...
Click to collapse
Please don't use mfastboot. It is known for having problems with latest Android versions. You can use Minimal adb and fastboot or the the latest Android SDK.
Next make sure you have flashed the latest TWRP 2.8.4.0.
Wipe everything in twrp. Cache, dalvik and data.
MTP is a bit messed up (not just on our devices). Go to mount, disable mtp, unmount everything, connect usb and enable MTP. Now your device should appear on your computers file manager.
One last thing. Unless you flash the latest SuperSU 2.4.5, stock Lollipop will automatically remove twrp and reinstall stock recovery on the next boot (Actually there is another way. But why would you want to install TWRP without rooting the phone).

doppelhelix said:
Please don't use mfastboot. It is known for having problems with latest Android versions. You can use Minimal adb and fastboot or the the latest Android SDK.
Next make sure you have flashed the latest TWRP 2.8.4.0.
Wipe everything in twrp. Cache, dalvik and data.
MTP is a bit messed up (not just on our devices). Go to mount, disable mtp, unmount everything, connect usb and enable MTP. Now your device should appear on your computers file manager.
One last thing. Unless you flash the latest SuperSU 2.4.5, stock Lollipop will automatically remove twrp and reinstall stock recovery on the next boot.
Click to expand...
Click to collapse
Oh. After many tries now I am stuck in a bootloop. The phones goes to the "warning" then reboots for 5-6 times before it actually starts up. So I am wondering what will be the correct way to go about rooting and clearing this mess. And I see only SuperSu 2.4.0 in play store. has there been a latest version?

vicky_ag said:
The phones goes to the "warning" then reboots for 5-6 times
Click to expand...
Click to collapse
That's because off the outdated SuperSU. Get the latest .zip here http://forum.xda-developers.com/showthread.php?p=23427715

doppelhelix said:
That's because off the outdated SuperSU. Get the latest .zip here http://forum.xda-developers.com/showthread.php?p=23427715
Click to expand...
Click to collapse
So I went this way. I installed the recovery using the tool mentioned in the op. Installed SuperSU latest. Still when I go to bootloader and try recovery, nothing happens. I booted up the phone to see if SuperSU is installed and it appears fine in the apps. But the recovery wont load no matter what.
Another strange thing even when I am connected on 3G, I am not getting the icon.

vicky_ag said:
So I went this way. I installed the recovery using the tool mentioned in the op. Installed SuperSU latest. Still when I go to bootloader and try recovery, nothing happens. I re-tried installing recovery, still no go.
Click to expand...
Click to collapse
Then how did you install SuperSU if you can't get into recovery?

doppelhelix said:
Then how did you install SuperSU if you can't get into recovery?
Click to expand...
Click to collapse
I got in the first time using the tool mentioned in the op. I checked and it uses the command:
fastboot.exe boot twrp.img
This causes the phone to boot into twrp and I can copy the SuperSU to install. But the recovery still doesn't work.

vicky_ag said:
I got in the first time using the tool mentioned in the op. I checked and it uses the command:
fastboot.exe boot twrp.img
This causes the phone to boot into twrp and I can copy the SuperSU to install. But the recovery still doesn't work.
Click to expand...
Click to collapse
What are you talking about. TWRP is the recovery.
---------- Post added at 10:08 ---------- Previous post was at 10:06 ----------
Oh sorry. Now I understand. Please use this commands:
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp.img

doppelhelix said:
What are you talking about. TWRP is the recovery.
Click to expand...
Click to collapse
Ok so this is what has happened:
1. I use the tool mentioned which uses the command:
fastboot.exe boot twrp.img
2. This causes the phone to boot into TWRP recovery. Then I installed SuperSU.
3. Rebooted the phone completely and checked the version of SuperSU.
4. Again went to the bootloader menu, selected TWRP. Nothing happens at this setup. phone doesn't boot at all. on clicking the power button it goes into normal boot
5. I tried going to the bootloader menu and running.
fastboot.exe flash recovery twrp.img
still no luck. Again trying to go from the bootloader menu to recoery yields no boot up.

vicky_ag said:
Ok so this is what has happened:
1. I use the tool mentioned which uses the command:
fastboot.exe boot twrp.img
2. This causes the phone to boot into TWRP recovery. Then I installed SuperSU.
3. Rebooted the phone completely and checked the version of SuperSU.
4. Again went to the bootloader menu, selected TWRP. Nothing happens at this setup. phone doesn't boot at all. on clicking the power button it goes into normal boot
5. I tried going to the bootloader menu and running.
fastboot.exe flash recovery twrp.img
still no luck. Again trying to go from the bootloader menu to recoery yields no boot up.
Click to expand...
Click to collapse
You are overriding the boot image with the recovery. The correct commands are
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp.img

doppelhelix said:
You are overriding the boot image with the recovery. The correct commands are
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Just tried that:
C:\fastboot>fastboot.exe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.496s]
writing 'boot'...
OKAY [ 0.438s]
finished. total time: 0.944s
C:\fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (9696 KB)...
OKAY [ 0.463s]
writing 'recovery'...
OKAY [ 0.433s]
finished. total time: 0.903s
Click to expand...
Click to collapse
Still when I go to the bootloader and select recovery, phone doesn't boot up at all.

vicky_ag said:
Just tried that:
Still when I go to the bootloader and select recovery, phone doesn't boot up at all.
Click to expand...
Click to collapse
Ok. Let's try this.
Can you boot normally into android? If so, please look if SuperSU is installed. If so, go to play store and install Android Terminal Emulator.
Open it and type
Code:
su
Supersu should pop up. Allow root.
Next type
Code:
reboot recovery
The device should boot into recovery. ( some people have this problem)

doppelhelix said:
Ok. Let's try this.
Can you boot normally into android? If so, please look if SuperSU is installed. If so, go to play store and install Android Terminal Emulator.
Open it and type
Code:
su
Supersu should pop up. Allow root.
Next type
Code:
reboot recovery
The device should boot into recovery. ( some people have this problem)
Click to expand...
Click to collapse
Thanks that works

vicky_ag said:
Thanks that works
Click to expand...
Click to collapse
Nice. Until you can go directly to the recovery, be very carefull not to leave the recovery without having flashed a rom and SuperSU. Also make sure that you grant adb access by accepting the RSA key when connecting the device with your computer. Just in case.

doppelhelix said:
Nice. Until you can go directly to the recovery, be very carefull not to leave the recovery without having flashed a rom and SuperSU. Also make sure that you grant adb access by accepting the RSA key when connecting the device with your computer. Just in case.
Click to expand...
Click to collapse
I am actually fine with a stock ROM on Motorola for now. They have lesser fluff than samsung et al. The major reason for trying to root the phone was to get TitanBackup working, I have been preserving some apps at a particular version in my last phone. The only way I found to restore the app and data was to use TitanBackup. The whole unlock the bootloader was because of Motorola adding a step to do this.
Adding recovery was an addition just in case Motorola forgets about us 1 year down the line. Then might flash to CM or something

[GUIDE] Fix TWRP Recovery Script Loop & Unable to boot

Hello!
This is actually a common "thing" across many devices so just because this thread is on the Oneplus 5 forum doesn't mean it won't work for your device!
So I know exactly what you're going through....
THE PROBLEM
You've flashed a Zip file, everything seemed to work fine, you pressed the reboot button.... But then... Black screen, blue LED (or something like that)....
You then try to reboot to recovery and then you see "Running Open Recovery Script" and you manage to decipher "Wiping Data", either you clean flashed your ZIP file and this is not a problem or you dirty flashed it and so you're screaming at your phone because it just wiped everything without you asking (I mean, this never happened to me or anything I'm just trying to imagine what it would look like :crying
You then try a few things but you're phone won't even get close to the Bootanimation and keeps trying to boot up into recovery and keeps on Wiping your data which is now non-existent.
THE FIX :fingers-crossed:
Method 1/
This is the most convenient and easiest method but it might not work for you, I'm not even entirely sure how I made it work for me... Anyway:
Once the phone has booted up into recovery and is flashing the ZIP, try the following:
WILL UPDATE AS SOON AS I FIND THE EXACT METHOD
-Taking a screenshot (Power+volume)
-Pressing the back, home and récents button as many times as you can
-Pressing the power button
Basically, for now until I'm certain on what gets you out of this script thing, press every button on the phone a few times (that's what I did)
Click to expand...
Click to collapse
Method 2 [FAILSAFE]/
This method will work no matter what (if your problem is the one this thread covers that is), but it's quite teedious!
Step1/ Boot into the Bootloader (Power+Volume up)
Step2/ Install ADB & Fastboot on your PC (Google)
Step3/Download Stock recovery & TWRP
Step 4/Move both files to the ADB folder for ease of access
Step5/Type in
Code:
fastboot flash recovery STOCK_RECOVERY.img
(change file name)
Step 6/Boot into this new recovery
Step 7/ Ponder for a minute at how useless it is
Step 8/Boot into Bootloader again
Step 9/Type into terminal
Code:
fastboot flash recovery TWRP_RECOVERY.img
(change file name)
Step 10/Boot into recovery and wipe everything except Internal storage
Step 11/Flash ROM again!
VOILA! :fingers-crossed:
Hope it helped, if you have any questions, feel free to ask me!
Cheers, Matt

I had this issue when I was flashing various roms, in my case it ended up being that some of the roms were incompatible with data being formatted as ext4 (mainly oos based ones, but a few others as well) since I went full f2fs, haven't seen this issue. That might be something to consider adding, it's pretty destructive, though, as going with f2fs on /data formats /sdcard, too

I had this issue when I was flashing various roms (xXx NoLimits, ExperienceOS) on the encrypted data partition. Only FreedomOS flashing and booting ok

dragynbane222 said:
I had this issue when I was flashing various roms, in my case it ended up being that some of the roms were incompatible with data being formatted as ext4 (mainly oos based ones, but a few others as well) since I went full f2fs, haven't seen this issue. That might be something to consider adding, it's pretty destructive, though, as going with f2fs on /data formats /sdcard, too
Click to expand...
Click to collapse
Ahh, that's interesting

R0iZ said:
I had this issue when I was flashing various roms (xXx NoLimits, ExperienceOS) on the encrypted data partition. Only FreedomOS flashing and booting ok
Click to expand...
Click to collapse
I had it on my old phone once (Oneplus X) so it's not rom/device specific... And I don't think it's a bug, more a compatibility issue...

first method doesnt work for me (and i have not expecting it to work)
second method should work but i have a little problem, i cant boot into bootloader
can someone help me with this
phone: Doogee X5

Fyzik753 said:
first method doesnt work for me (and i have not expecting it to work)
second method should work but i have a little problem, i cant boot into bootloader
can someone help me with this
phone: Doogee X5
Click to expand...
Click to collapse
You can't boot into bootloader? Are you sure? Long less power + Volume up

Fyzik753 said:
first method doesnt work for me (and i have not expecting it to work)
second method should work but i have a little problem, i cant boot into bootloader
can someone help me with this
phone: Doogee X5
Click to expand...
Click to collapse
Are you trying to install/fix TWRP designed for OnePlus 5 into a different phone? Good luck!

i have a problem with instaling twrp ...
example:
phone have bootloader unlocked
flashing original 4.5.14 firmware .... all good ... boot phone ... settings ... done
reboot to bootloader ... flash twrp (or blu_spark twrp) ... done ... reboot to twrp .. all good
reboot to system ... done. poweroff (or restart)...
boot to recovery ... surprise ... original recovery ... not twrp
flash again twrp ... done ... boot to system ... reboot to recovery ... original recovery ....
saw .. what is going on ?
thanks

aoprea said:
i have a problem with instaling twrp ...
example:
phone have bootloader unlocked
flashing original 4.5.14 firmware .... all good ... boot phone ... settings ... done
reboot to bootloader ... flash twrp (or blu_spark twrp) ... done ... reboot to twrp .. all good
reboot to system ... done. poweroff (or restart)...
boot to recovery ... surprise ... original recovery ... not twrp
flash again twrp ... done ... boot to system ... reboot to recovery ... original recovery ....
saw .. what is going on ?
thanks
Click to expand...
Click to collapse
OxygenOS overwrites the recovery with stock one when you boot into the OS..
to avoid this, after flashing twrp, (without rebooting to system) flash SuperSU or Magisk immediately..

iamelton said:
OxygenOS overwrites the recovery with stock one when you boot into the OS..
to avoid this, after flashing twrp, (without rebooting to system) flash SuperSU or Magisk immediately..
Click to expand...
Click to collapse
thanks ... solved with install magisk
ps. I was accustomed with samsung phones where this does not happen...

Hi, I hope there's somebody who can help me with this.
I think, method could help me, but when I try to flash the recovery, I get this message:
Code:
target reported max download size of 535822336 bytes
sending 'recovery' (27525 KB)...
OKAY [ 0.914s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.954s
Any Ideas to solve this?

iamelton said:
OxygenOS overwrites the recovery with stock one when you boot into the OS..
to avoid this, after flashing twrp, (without rebooting to system) flash SuperSU or Magisk immediately..
Click to expand...
Click to collapse
i have op5
i don't know what should i do - i install magisk and twrp - is it in the twrp i do that i wipe and i flash rom
but i find the some problem open and after boot i don't found the twrp and my recovery return to official recov
please help
my phone without root is worthless

Im_Mattgame said:
Hello!
This is actually a common "thing" across many devices so just because this thread is on the Oneplus 5 forum doesn't mean it won't work for your device!
So I know exactly what you're going through....
THE PROBLEM
You've flashed a Zip file, everything seemed to work fine, you pressed the reboot button.... But then... Black screen, blue LED (or something like that)....
You then try to reboot to recovery and then you see "Running Open Recovery Script" and you manage to decipher "Wiping Data", either you clean flashed your ZIP file and this is not a problem or you dirty flashed it and so you're screaming at your phone because it just wiped everything without you asking (I mean, this never happened to me or anything I'm just trying to imagine what it would look like :crying
You then try a few things but you're phone won't even get close to the Bootanimation and keeps trying to boot up into recovery and keeps on Wiping your data which is now non-existent.
THE FIX :fingers-crossed:
Method 1/
This is the most convenient and easiest method but it might not work for you, I'm not even entirely sure how I made it work for me... Anyway:
Once the phone has booted up into recovery and is flashing the ZIP, try the following:
Method 2 [FAILSAFE]/
This method will work no matter what (if your problem is the one this thread covers that is), but it's quite teedious!
Step1/ Boot into the Bootloader (Power+Volume up)
Step2/ Install ADB & Fastboot on your PC (Google)
Step3/Download Stock recovery & TWRP
Step 4/Move both files to the ADB folder for ease of access
Step5/Type in
Code:
fastboot flash recovery STOCK_RECOVERY.img
(change file name)
Step 6/Boot into this new recovery
Step 7/ Ponder for a minute at how useless it is
Step 8/Boot into Bootloader again
Step 9/Type into terminal
Code:
fastboot flash recovery TWRP_RECOVERY.img
(change file name)
Step 10/Boot into recovery and wipe everything except Internal storage
Step 11/Flash ROM again!
VOILA! :fingers-crossed:
Hope it helped, if you have any questions, feel free to ask me!
Cheers, Matt
Click to expand...
Click to collapse
You saved me bro my life is your from now thankyou love u♥

[Pie/Oreo/Nougat] How to root your Z2 [ALL]

Since no guide has been updated with information on official TWRP for root and backup reasons, I thought I'd create one.
DISCLAIMER:
To do this method requires you to unlock your bootloader. Your warranty is now void. This method assumes you have basic knowledge of ADB and Fastboot commands and know how to recover your device if you accidentally type a wrong command and now boot to TWRP and can't boot to system. If you cannot recover from this, Read up on guides to "return to stock" and familiarize yourself on how to recover your device should something go wrong.
There are two methods for root. You can flash TWRP to your boot image to be able to reboot to TWRP without a PC, or just a temp boot so you can just have root and not TWRP. I'll put in brackets the minor differences.
1: Get ready
Download latest build of TWRP img file from their website.(Previous link is to their instructions and device specific patches, download page is HERE.) {download the latest zip if you want to flash TWRP}
Download what you want on your phone (SU, Magisk, etc)
2:
Hook phone up to your PC, be sure you have latest adb/fastboot drivers. (I do not support windows related questions. If you have latest drivers, you'll have no issue with the below commands, Linux just works for this kind of thing)
3:
Navigate to your directory that has that img downloaded. (windows, shift right click and say "open command prompt here")
Type the below commands, and terminal output should be similar: (I.E. this is a copy/paste of terminal)
Main thing to remember is "Fastboot boot {filename}.img"
Code:
[email protected]:~$ adb reboot bootloader
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ fastboot boot twrp-3.2.1-1-nash.img
downloading 'boot.img'...
OKAY [ 0.841s]
booting...
OKAY [ 5.135s]
finished. total time: 5.976s
[email protected]:~/Downloads$
BE SURE TO DO BOOT AND NOT FLASH!!! (If you ask why you can no longer boot to system, I'll let you know you missed this line.)
5:
You're now in TWRP!
It will ask you for your password. This is your PIN or password to unlock your phone. Enter it.
TWRP has now decrypted your storage to read the zip file(s) you put on your phone!
Go to install and navigate to your directory where you put that file
Install Magisk/SU/TWRP/whatever you please.
(Note: some root zips require a factory reset)
6:
Reboot!
You're Done congratulations!
Attached are images if they help you see you're doing the right thing.
Special thanks @erfanoabdi @invisiblek @npjohnson @joemossjr @jbats
Without the above people a lot of what's above woudn't have been possible for this device specifically. Also, thanks to everyone who pitched in to get a device over to invisiblek. Leaps and bounds have been done since that donation. And thanks to the other devs who have invested in this phone and their time to help out.
(Quoted from Nathan Chance)
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, the Free Software Foundation, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.

Random issues post:
SU does some wonky edits to the ramdisk. It is highly suggested to flash Magisk for root.
Some have reported needing to wipe data after flashing Magisk. If you can't boot after flashing Magisk, just go back into recovery (can be twrp or stock) and wipe data/factory reset to boot again.

Note: we do not have a recovery partition. Never flash the img file! Download the flashable zip if you want twrp on your phone and flash per OP instructions.

Awesome thanks

I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo

droidgreg said:
I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo
Click to expand...
Click to collapse
Be sure to mount system under the "mount" button

I need the OCX27.1 oreo. I did a return to stock flashall to OCX27 and now reflashed TWRP and Magisk and boots fine but I lost baseband and IMEI

Added warning to OP that some root zips require a data wipe.

I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.

will4958 said:
I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.
Click to expand...
Click to collapse
This guide assumes you can unlock your bootloader. Since Verizon and AT&T feel they have a right to lock down their devices, this guide won't work. That is why I voted with my wallet and left Vz after my M7 due to them putting phone OEM's privates in a vice and forced them to lock out those carrier variants.

Has this method been tested with OCX27.1 Oreo on TMO?

droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
It probably hasn't been tested, but it should work in theory.

Uzephi said:
It probably hasn't been tested, but it should work in theory.
Click to expand...
Click to collapse
I was on 27.1 when I attempted to root and got into a bootloop and lost my baseband when I flashall back to stock OCX27. I have a feeling 27.1 update isn't compatible with this method and cannot be downgraded to even OCX 27 Oreo

so no go on 27.1 twrp? I have root on 27.1 TMO obtained post update. Obtained by fastbooting the nash twrp and running magisk 16.zip. No needing to format data or anything
I was just wondering about the installable twrp zip. I am coming from samsung development so all this A/B partitioning and some of the other partitions are new to me.
As soon as I can get twrp on the phone and feel comfortable recovering. The kernels and roms will start coming.
Feels strange not having odin to save my ass

droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
tested and working

mattlowry said:
tested and working
Click to expand...
Click to collapse
Have you actually flashed installer.zip to install TWRP or just booted TWRP and only flash magisk or SU for root without installing TWRP?

I fastboot booted the twrp. I didn't try the installer. What is it?

Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.

luponcooper said:
Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.
Click to expand...
Click to collapse
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).

Uzephi said:
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).
Click to expand...
Click to collapse
Thanks a lot uzephi for answering.
I have the 6gb ram and 64gb model, XT1789-05. I try whit no succes to install Magisk (Error1) so i made a factory reset but still doesn't boot, stays in M logo.
Im super noob, can you guide me? i dont know how to recover the boot.img.
excuse my english.

Fastboot Strangeness, Having Issues Rooting/Installing ROMS

Hello!
I've been enjoying my rooted Pixel 5 but today I saw that the first Pixel 5 ROM is available so I went to go try it. Just like the instructions asked I tried to flash the ROM like it was a standard stock image since we don't have TWRP yet. Everything was going fine until it got to the part where it sent boot.img, it would fail at that point saying the partition doesn't exist. The exact error was...
HTML:
FAILED (remote: Failed to write to partition Not Found)
I also did the 'fastboot -w' to wipe user data before rebooting as instructed, it just booted back into fastboot with the reason listed as "no valid slot to boot". After a while I figured out I could use 'fastboot flash boot_a /path/to/boot.img' to flash the slots manually and that booted me into stock Android, not the ROM. Even though I used the boot.img from the ROM, no ROM was installed.
After this I decided to go back to stock and flash Magisk again and wait until we have some more stable ROMs. annnnnnd that's where I realized I was in trouble. I tried doing 'flash-all.bat' like normal and it gave me the same error the ROM did. I then manually flashed the stock boot.img and set up the phone, once I was at the home screen I turned it off, flashed my prepared 'magisk_patched.img', all seemed to go just fine, but upon trying to reboot its stuck at fastboot again. I can get back to my homescreen by just flashing the stock boot.img but no matter what I try I cannot get it to reboot after flashing the patched image.
Things I have tried:
Updating ADB/Fastboot
Reinstalling ADB/Fastboot
Updating USB Drivers
Flash to Stock and Retry
Repatch a new image using Magisk Canary
Lots and Lots of reboots
Several attempts at all of the above (last time I rooted it gave me errors and then just worked for no reason after some reboots and tries)
Above steps in Linux Terminal (Ubuntu WSL)
For the night I'm just going to flash the Stock boot.img so I can have my alarms and receive messages, but I'd really like to return to stock as I use Tasker frequently as well as some other applications that require root access. If anyone has any tips for how to get more consistent results when rooting, I have no idea why it works sometimes and not other times. If anyone knows how to solve these errors please let me know.
Thanks y'all
***EDIT - FIXED, NOT SOLVED***: I'm still unsure what caused it in the first place, but I was able to regain root by flashing the October update, patching a new boot.img from that update, and then flashing. I was previously using the latest November update. I think that when I tried to flash the ROM something went wrong and it left things behind, and I don't think my original flash back to stock worked completely because flashing the October update took about 4 times as long. I used Pixel 5 unlocked stock images from Google's website for both attempts so im not sure why one worked and the other didn't, but I am rooted. If anyone else is experiencing similar issues, try flashing to a previous software update and rooting that.

this may be a stupid question but did you enable "Developer Options" and "OEM Unlocking"?
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-5-easy-follow-guide-0329550/

grisly grizzly said:
Hello!
I've been enjoying my rooted Pixel 5 but today I saw that the first Pixel 5 ROM is available so I went to go try it. Just like the instructions asked I tried to flash the ROM like it was a standard stock image since we don't have TWRP yet. Everything was going fine until it got to the part where it sent boot.img, it would fail at that point saying the partition doesn't exist. The exact error was...
HTML:
FAILED (remote: Failed to write to partition Not Found)
I also did the 'fastboot -w' to wipe user data before rebooting as instructed, it just booted back into fastboot with the reason listed as "no valid slot to boot". After a while I figured out I could use 'fastboot flash boot_a /path/to/boot.img' to flash the slots manually and that booted me into stock Android, not the ROM. Even though I used the boot.img from the ROM, no ROM was installed.
After this I decided to go back to stock and flash Magisk again and wait until we have some more stable ROMs. annnnnnd that's where I realized I was in trouble. I tried doing 'flash-all.bat' like normal and it gave me the same error the ROM did. I then manually flashed the stock boot.img and set up the phone, once I was at the home screen I turned it off, flashed my prepared 'magisk_patched.img', all seemed to go just fine, but upon trying to reboot its stuck at fastboot again. I can get back to my homescreen by just flashing the stock boot.img but no matter what I try I cannot get it to reboot after flashing the patched image.
Things I have tried:
Updating ADB/Fastboot
Reinstalling ADB/Fastboot
Updating USB Drivers
Flash to Stock and Retry
Repatch a new image using Magisk Canary
Lots and Lots of reboots
Several attempts at all of the above (last time I rooted it gave me errors and then just worked for no reason after some reboots and tries)
Above steps in Linux Terminal (Ubuntu WSL)
For the night I'm just going to flash the Stock boot.img so I can have my alarms and receive messages, but I'd really like to return to stock as I use Tasker frequently as well as some other applications that require root access. If anyone has any tips for how to get more consistent results when rooting, I have no idea why it works sometimes and not other times. If anyone knows how to solve these errors please let me know.
Thanks y'all
Click to expand...
Click to collapse
And you have usb debugging on

swangjang said:
this may be a stupid question but did you enable "Developer Options" and "OEM Unlocking"?
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-5-easy-follow-guide-0329550/
Click to expand...
Click to collapse
Hey, Yes OEM Unlocking is on and greyed out. It was giving me the option to turn it off again before, not sure why it isn't now.

jaythenut said:
And you have usb debugging on
Click to expand...
Click to collapse
I actually did not have USB debugging enabled, but after doing so I have the same problem. Just tried to flash magisk with the two custom .img files I made last night, and my last confirmed working one, same problem as before. It successfully flashes, then bootloops til I reflash the stock boot.img.

grisly grizzly said:
I actually did not have USB debugging enabled, but after doing so I have the same problem. Just tried to flash magisk with the two custom .img files I made last night, and my last confirmed working one, same problem as before. It successfully flashes, then bootloops til I reflash the stock boot.img.
Click to expand...
Click to collapse
Don't know if it will work but flash magisk on slot a and b
And just checking you done
fastboot flash boot magisk_patched.img

jaythenut said:
Don't know if it will work but flash magisk on slot a and b
And just checking you done
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
I think I tried that last night, but I tried again just now with a new patched.img just in case. Flashed successfully but same problem. Here's my exact powershell input/output. For powershell I gotta use ./fastboot but its the same as running 'fastboot' in cmd. And I've using powershell with and without admin access.
HTML:
PS C:\platform-tools> ./fastboot flash boot_a ".\patched.img"
Sending 'boot_a' (98304 KB) OKAY [ 0.469s]
Writing 'boot_a' OKAY [ 1.993s]
Finished. Total time: 2.725s
PS C:\platform-tools> ./fastboot flash boot_b ".\patched.img"
Sending 'boot_b' (98304 KB) OKAY [ 0.469s]
Writing 'boot_b' OKAY [ 1.981s]
Finished. Total time: 2.713s
Just gets me back to the fast boot menu saying boot partition not found, just flashed the stock boot.img and I'm back at my home screen again. If its of any importance, I only had to flash the stock boot.img to slot a in order to get back to my home screen. Slot B should still be flashed with the patched.img, no root access on slot a though.
Edit: Do you think it would be helpful to relock the bootloader (since it returns everything to stock) and then re-unlock and re-root? Nevermind I forgot that re-locking makes it so you can't re-unlock. Won't do that.

how exactly did you flash the stock rom bc im lost on this process.... Heres where im at bc i cant get any help from the ProtonAOSP thread or anywhere. ive never flashed a rom without twrp and im lost now:
BC This is what ive been getting:
C:\Users\james\AppData\Local\Android\Sdk\platform-tools>fastboot flash C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1.zip
unknown partition 'C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1.zip'
fastboot: error: cannot determine image filename for 'C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1.zip'
and now this fof Fastboot boot ZipFile
C:\Users\james\AppData\Local\Android\Sdk\platform-tools>fastboot boot C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1-gapps.zip
creating boot image...
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
but what im not understanding is do u unzip it to platform-tools and use flash-all, like reverting back to stock? bc this is what i get when i dont unzip it and just copy it to platform-tools directory from my downloads folder. this is my first time flashing a custom rom and i just cant seem to get anyone to tell me exactly what i need to do or what im doing wrong. PLEASE HELP