Related
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!
I see lots of confusion going on in many Roms & other threads for rooting 6.0 specially due to that System-less SuperSU.
so i'm sharing what i have done to root 6.0 & update SuperSU through 2.61 to 2.64.
now before we begin be clear on that System-less SuperSU patches only kernel & ramdisk for root.
Still making Full Backup/nandroid is always a good thing before trying something new, it'll save you if anything goes wrong.
Rooting Marshmallow 6.0+ 1st time
1) Be on Marshmallow Rom ( stock / custom) with unlocked boot loader..... i have tested this stock & Cataclysm.
Click below to see how to Unlock Bootloader.
Beware : it'll wipe your device entierly to factory reset state ( all things will be wiped out : contacts , apps , music, videos & your personal files etc. so backup every thing.
reboot into boot loader & use bellow command for unlocking boot loader
Code:
fastboot oem unlock
2) Download latest version of SuperSU ( currently 2.64) from Here & Place it in Phone Storage
2B) (optional) if you want to use Custom kernel (like ElementalX) then download it's falshable zip & pace it in Phone Storage as well
3) Download TWRP 2.8.7.1 from Here. & flash it with fastboot command.
Code:
fastboot flash recovery twrp-2.8.7.1-hammerhead.img
4) after flashing TWRP inter into recovery without Rebooting Phone . ( why ? open hidden content ) {PS: smart people make nandroid backup at this step}
if you reboot phone just after flashing twrp & then try to enter in to recovery mode, you will see stock recovery instead of TWRP. bcz TWRP was flashed only as temporary recovery without root.
4B) (optional) if you want to use custom kernel then flash it now ! ( yes before rooting bcz it needs to be patched) ( not needed.... you can flash custom kernel after completing entire root process bcz it turns out that SuperSU just patch ramdisk, not kernel so custom kernel can be flashed after rooting without any problem. btw i still flash custom kernel before rooting and never had problem so it's your call when to flash custom kernel )
5) Now Flash SuperSU.zip in TWRP which you have from link in 2nd point.
6) Click Reboot System in TWRP. It will tell you your device isn't rooted & ask your permission for rooting it. DO NOT ( I repeat Do not) swipe to grant it, always Select NO ( it says so bcz twrp still don't detect system-less root )
7) Remember 6th point after Flashing any other zip in future as well.
PS: If you change your kernel after rooting you need to flash SuperSU.zip again after it
Updating SuperSU for already rooted Marshmallow 6.0+
all steps are important for properly updating SuperSu so don't skip any of them. Otherwise already patched Kernel or ramdisk will give you an error while flashing updated SuperSu!
1) Open SuperSU app. Click "Full Unroot" & wait until auto reboot completes. ( this step will remove root & restore your original kernel that was auto backup while rooting 1st time.)
2) Flash Stock boot.img from factory image via fastboot command. ( important step for those who used custom kernel while/after rooting )
Code:
fastboot flash boot boot.img
(you can get boot.img by extracting image-hammerhead-xxxxx, from factory image.)
3)Reboot Phone.
4) Now follow Rooting Marshmallow 6.0+ 1st time method from step 2. ( you can skip step 3 if you already have TWRP )
.........................................................................................................................
Cataclysm specific info
( reserved for future SuperSU changes )
A major change in setup is that the ZIP installer will try to detect 6.0 firmwares that can be rooted without doing a systemless install. In other words, a root that modifies only /system, but not the boot image. If this is possible, the installer will install into /system (unless you override via "echo SYSTEMLESS=true>>/data/.supersu").
Click to expand...
Click to collapse
what does above statement from Chainfire's SuperSU 2.64 mean ?
Well, it means on Android 6.0+ if you are using Custom Rom & Custom kernel which are already patched for SELinux Policies for root on /system partition then from v2.64 SuperSU script will check it & if they seems fine then Su binary will be placed in /system instead in installing Root as system-less mode & patching kernel & all.
(correct me if i'm wrong )
Thanks for this. Makes things clear for me.
Maybe you can add something about Android Pay. Like, does it work? Or, how to make it work. I see a lot of confusion on that when discussing the new SuperSU as well.
Sent from my Nexus 5
bmcgarry84 said:
Thanks for this. Makes things clear for me.
Maybe you can add something about Android Pay. Like, does it work? Or, how to make it work. I see a lot of confusion on that when discussing the new SuperSU as well.
Sent from my Nexus 5
Click to expand...
Click to collapse
No Android Pay will Not work if you root your device in any way.
Some users reported earlier that "system-less" root helped them to keep Android Pay working.. But itt was just placebo & luck. It stopped working for most of them after some time.
So for now there is no way to keep Android Pay working with root. ( atleast not to the my knowledge)
(Actually Android Pay isn't working with Root is Good security feature..one can argue that other pay works even after rooting but there's chance (may be just a little) to interfere it by thieves. & Google won't risk it until they find complete secure solution. )
Hmmm. Android Pay has been working for me on 6.01 with both 2.63 & 2.64 su. Used it only twice in the last week, so that may not pass the "it's working permanently" test. It is working though (at Whole Foods). I had to delete the xbin file mentioned in the supersu thread. I even have Viper4Android installed, which modifies system.
first boot after point 6. everything was fine.
then i opened Busybox and " It looks like bb is installed, but it does not appear to be the versionthay you selected to have installed, you may want to try the installation again, but this time using a differentinstallation location."
then I made restart and I have lost root. SuperSu " There is no SU binary installed, and SuperSu cannot install it............"
Edit. Second attempt whitout custom kernel ( hellscore ) and looks like everything is working now. ( i unistalled and reistalled busybox )
Mairo said:
first boot after point 6. everything was fine.
then i opened Busybox and " It looks like bb is installed, but it does not appear to be the versionthay you selected to have installed, you may want to try the installation again, but this time using a differentinstallation location."
then I made restart and I have lost root. SuperSu " There is no SU binary installed, and SuperSu cannot install it............"
Edit. Second attempt whitout custom kernel ( hellscore ) and looks like everything is working now. ( i unistalled and reistalled busybox )
Click to expand...
Click to collapse
may be custom kernel related.. most of custom kernel for nexus 5 comes with busy box. so you don't need to flash it again.
If you want to update busybox use /xbin installation method. ( it'll modify your /system but it's easy)
( if you don't want to modify your /system at all you can use /bin location for BB installation. it should work fine ( though i never used this.) )
personally i use ElementalX which comes with busybox so i don't go to hassle to update it again..it works just fine without anything
lynnux said:
Hmmm. Android Pay has been working for me on 6.01 with both 2.63 & 2.64 su. Used it only twice in the last week, so that may not pass the "it's working permanently" test. It is working though (at Whole Foods). I had to delete the xbin file mentioned in the supersu thread. I even have Viper4Android installed, which modifies system.
Click to expand...
Click to collapse
personally i don't have any experience with Android Pay bcz it's not available in my country & i don't think i''l be any soon.
so if it's working for you then it's good
in future if it stop working, let us know how it stopped (if you can figure it out) it'll be helpful for other people.
there is something with hellscore kernel and su2.64. I tried 2 different ways right now.
First i flashed under twrp hells b16 ( it says successfully )and then su.2.64. ( succesfull) then I boot up and no hellscore kerne.
Then I just tried to flash only hellscore whitout SU2.64. then I get hellscore kernel but then no root. Then I just went to back TWRP and flashed Su.264 and I got root and stock kernel .
I think I need talk with Hellscore about this b16 version and su2.64.
Mairo said:
there is something with hellscore kernel and su2.64. I tried 2 different ways right now.
First i flashed under twrp hells b16 ( it says successfully )and then su.2.64. ( succesfull) then I boot up and no hellscore kerne.
Then I just tried to flash only hellscore whitout SU2.64. then I get hellscore kernel but then no root. Then I just went to back TWRP and flashed Su.264 and I got root and stock kernel .
I think I need talk with Hellscore about this b16 version and su2.64.
Click to expand...
Click to collapse
What your recovery log says when you flash SuperSU after hellscore ?
Can you attach it, i want to check it out.
(i think there is option to save log after flashing zip in twrp )
jineshpatel30 said:
What your recovery log says when you flash SuperSU after hellscore ?
Can you attach it, i want to check it out.
(i think there is option to save log after flashing zip in twrp )
Click to expand...
Click to collapse
sorry cant give it right now. I restored everything from nandroid backup. befor I used b16 with su2.62-3 and they worked great together. but after restoring same like 2.64.
my battery starting to get empty.. cant test it and send log right now.
Mairo said:
sorry cant give it right now. I restored everything from nandroid backup. befor I used b16 with su2.62-3 and they worked great together. but after restoring same like 2.64.
my battery starting to get empty.. cant test it and send log right now.
Click to expand...
Click to collapse
Okay no problem
If you give it try in future,plz save log file
jineshpatel30 said:
Okay no problem
If you give it try in future,plz save log file
Click to expand...
Click to collapse
here it is. I made a new istall also before . Then I used your guide and got root. Then I reboot back in twrp and flashed hellscore then su2.64 again. and then made reboot. And no Helscore kernel.
Mairo said:
here it is. I made a new istall also before . Then I used your guide and got root. Then I reboot back in twrp and flashed hellscore then su2.64 again. and then made reboot. And no Helscore kernel.
Click to expand...
Click to collapse
Well i'm not an expert in this matters but your log shows lots of errors while flashing SuperSu after hellscore.
It can't Mount partitions & can't create /su folder & errors while patching also.
I recommend you to show this log to Kernel Dev asap..he will know what to do exactly.
Btw you flashed stock boot.img before flashing hellscore right ?
If not now try bellow steps exactly.
Flash stock boot.img via fastboot (no need to flash system or anything else as you are flashing hellscore again )
Now reboot phone & then go to recovery.
Now flash hellscore & then SuperSU.
& reboot.
See & report result. (If you already done above steps property then no need to try again just report logs to Dev )
jineshpatel30 said:
Btw you flashed stock boot.img before flashing hellscore right ?
Click to expand...
Click to collapse
Jeap. Tried these steps. I sent this log to Hells dev.
fastboot flash recovery twrp-2.8.7.1 goes wrong
Hi, I try the root on nexus 5 with stock rom 6.01, when I flash recovery twrp, obtain this message:
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery twrp
-2.8.7.1-hammerhead.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14694 KB)...
OKAY [ 0.738s]
writing 'recovery'...
FAILED (remote: not supported in locked device)
finished. total time: 0.845s
so, when i go to recovery, without rebooting as suggested, I don't have twrp recovery.
Any suggestion?
Thanks
wiifan said:
Hi, I try the root on nexus 5 with stock rom 6.01, when I flash recovery twrp, obtain this message:
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery twrp
-2.8.7.1-hammerhead.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14694 KB)...
OKAY [ 0.738s]
writing 'recovery'...
FAILED (remote: not supported in locked device)
finished. total time: 0.845s
so, when i go to recovery, without rebooting as suggested, I don't have twrp recovery.
Any suggestion?
Thanks
Click to expand...
Click to collapse
You have to unlock your bootloader first. CAUTION! THIS WIPES YOUR PHONE!
Background information and how to unlock the bootloader read here: http://www.addictivetips.com/mobile/what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide/
wiifan said:
Hi, I try the root on nexus 5 with stock rom 6.01, when I flash recovery twrp, obtain this message:
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery twrp
-2.8.7.1-hammerhead.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14694 KB)...
OKAY [ 0.738s]
writing 'recovery'...
FAILED (remote: not supported in locked device)
finished. total time: 0.845s
so, when i go to recovery, without rebooting as suggested, I don't have twrp recovery.
Any suggestion?
Thanks
Click to expand...
Click to collapse
as suggested by Smoosh you need to Unlock Bootloader.
Beware : it'll wipe your device entierly to factory reset state ( all things will be wiped out : contacts , apps , music, videos your personal files etc. so backup every thing.
reboot into boot loader & use bellow command for unlocking boot loader
Code:
fastboot oem unlock
Smoosh1 said:
You have to unlock your bootloader first. CAUTION! THIS WIPES YOUR PHONE!
Background information and how to unlock the bootloader read here: http://www.addictivetips.com/mobile/what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide/
Click to expand...
Click to collapse
thank for replying him i thought people come to this thread already know about unlocking but now i need to add that as well in OP
Bootloop
My phone has entered into a bootloop after flashing on the TWRP recovery. TWRP opens, runs a script for like 5 seconds, and then my phone restarts, repeat. How do I fix this? I have tried to wipe the memory multiple times and even reflash twrp, with no success.
@jineshpatel30 Pls help
hi bro @jineshpatel30 pls help me out.
Im running on stock 6.0.0 and rooted with recovery twrp-2.8.7.1-hammerhead.img and hellscore hC-b11-M kernal. Im using cataclysm Nov release 6.0.0 as my daily driver in secondary rom (and its pre rooted by the rom builder) and stock 6.0.0 as my primary rom.
Recently cataclysm released its Dec 8 stable release 6.0.1, i have clean flashed the same in secondary and its working perfect but no root access, after going through too many forums in xda i have flashed SuperSU 2.61 on the same to root it. but its just showing patching ramdisk in twrp more than 30 mins and nothing is happening. :crying:
Now kindly help me to root the same(cataclysm Dec 8 stable release 6.0.1) in secondary... can i flash SuperSU-2.64 directly over cataclysm?? is that safe?? is that make any problem to primary stock??? pls guide me as im not getting any proper answre from any of the forum and there is too many members like me still confused flashing the SuperSu 2.64 in a multirom and its after effects. :fingers-crossed:
Primary Rom: Stock 6.0.0 as primary, Kernal : hC-b11-M
Seconary Rom: Cataclysm Nov release 6.0.0, Kernal : hC-b15-M
Recovery: TWRP 2.8.7.1
Baseband: M8974A -2.0.50.2.27
Booloader: hhz12k
awaiting for your valuable reply hope you will help me:fingers-crossed:
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.
Sorry if this seems like a dumb question - I'm a little green on the phone modding (last phone was a S3, rooted with oneclickroot I think) I have a bootloader unlockable XT1775 owens (bought from retail, no carrier lock) that I have been planning to bootloader unlock and root with TWRP & Magisk. I just got a notification that update "NPR26-58-45" is available. I downloaded it, but haven't installed yet - for fear that it might affect what I want to do for root.
What should I do? ie: - install it, and go forward with the root process? Root first, and then install?
jdsmn21 said:
Sorry if this seems like a dumb question - I'm a little green on the phone modding (last phone was a S3, rooted with oneclickroot I think) I have a bootloader unlockable XT1775 owens (bought from retail, no carrier lock) that I have been planning to bootloader unlock and root with TWRP & Magisk. I just got a notification that update "NPR26-58-45" is available. I downloaded it, but haven't installed yet - for fear that it might affect what I want to do for root.
What should I do? ie: - install it, and go forward with the root process? Root first, and then install?
Click to expand...
Click to collapse
Do NOT root first!
Edit: do me a favor and upload a system backup after you update, root and install twrp (if you do anyway), so I can make a twrp flashable ROM.
Edit-2: actually, if you could backup system before rooting or anything, that would be better.
You do not want to root first. Update then root as doing an ota while rooted may loose your root status or worse!
Goose03 said:
Do NOT root first!
Edit: do me a favor and upload a system backup after you update, root and install twrp (if you do anyway), so I can make a twrp flashable ROM.
Edit-2: actually, if you could backup system before rooting or anything, that would be better.
Click to expand...
Click to collapse
Thanks Goose. I will gladly upload that, but I will have to get back to you after the weekend - I apologize, heading out of town after work.
To clarify on the process, I would go through the step to unlock the bootloader (using the code I will get from Moto website and "fastboot oem unlock CODE"). After that is the TWRP step, right? If so, which command do I use: "fastboot boot recovery.img" or "fastboot flash recovery recovery.img" ??
jdsmn21 said:
Thanks Goose. I will gladly upload that, but I will have to get back to you after the weekend - I apologize, heading out of town after work.
To clarify on the process, I would go through the step to unlock the bootloader (using the code I will get from Moto website and "fastboot oem unlock CODE"). After that is the TWRP step, right? If so, which command do I use: "fastboot boot recovery.img" or "fastboot flash recovery recovery.img" ??
Click to expand...
Click to collapse
Np. Take your time. Thanks. Yes, that is what you do to unlock. Then for flashing twrp it's like you have but make sure to match the last part "recovery.img" to whatever the recovery is named. If your recovery is named twrp.img the command is:
fastboot flash recovery twrp.img
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
koop1955 said:
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
Click to expand...
Click to collapse
That's the one I had been following! I found that very helpful - that would make a good sticky post for guys like myself.
Since I have your attention too, I'd like to ask - is dmnoverity and phh's SU not needed at all? The only three files copied to the SD card (and then installed) are TWRP, Magisk zip, and Magiskmanager APK?
jdsmn21 said:
That's the one I had been following! I found that very helpful - that would make a good sticky post for guys like myself.
Since I have your attention too, I'd like to ask - is dmnoverity and phh's SU not needed at all? The only three files copied to the SD card (and then installed) are TWRP, Magisk zip, and Magiskmanager APK?
Click to expand...
Click to collapse
Phh SU is not needed since Magisk gives you all the necessary root and features. dmnoverity is not needed. I recommend you allow twrp system write access.
koop1955 said:
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
Click to expand...
Click to collapse
Well, I followed your instructions....with a minor tweak - and I'm having problems.
I unlocked the bootloader a couple days ago, but couldn't download the TWRP.bin file, so I used my phone through today. Formatted a 64gb card and loaded the magisk zip and apk on it. Flashed the TWRP on the phone, and used the wipe function to wipe data, cache, and dalvik, and then made a backup to my sd card. Flashed the magisk.zip, and then hit reboot "system". Now it just reboots to TWRP. I can reboot to bootloader, but hitting "start" goes to TWRP again.
What do I do? Where did I go wrong?
jdsmn21 said:
Well, I followed your instructions....with a minor tweak - and I'm having problems.
I unlocked the bootloader a couple days ago, but couldn't download the TWRP.bin file, so I used my phone through today. Formatted a 64gb card and loaded the magisk zip and apk on it. Flashed the TWRP on the phone, and used the wipe function to wipe data, cache, and dalvik, and then made a backup to my sd card. Flashed the magisk.zip, and then hit reboot "system". Now it just reboots to TWRP. I can reboot to bootloader, but hitting "start" goes to TWRP again.
What do I do? Where did I go wrong?
Click to expand...
Click to collapse
Try fastboot oem fb_mode_clear
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
Try fastboot oem fb_mode_clear
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Thank you. I tried the command, and it said OK, but it still boots to TWRP; i then reboot to bootloader, and select Start and it goes into the normal system. Is that how it is supposed to work?
Last night I was stuck in a TWRP loop, but i got it to go with formatting data and factory reset wipe in TWRP. After finally getting the system to boot, I installed the Magisk Manager and then Adaway. Now today I was playing with the Chase Pay app, which won't let me sign in due to being rooted. I then reverted my hosts file and uninstalled Adaway, and played with all the hide options in Magisk., to no avail. Root Checker app says that Safetynet is tripped.
Does Magisk effectively work for apps that look at Safetynet on this phone - apps like Chase Pay?
jdsmn21 said:
Thank you. I tried the command, and it said OK, but it still boots to TWRP; i then reboot to bootloader, and select Start and it goes into the normal system. Is that how it is supposed to work?
Last night I was stuck in a TWRP loop, but i got it to go with formatting data and factory reset wipe in TWRP. After finally getting the system to boot, I installed the Magisk Manager and then Adaway. Now today I was playing with the Chase Pay app, which won't let me sign in due to being rooted. I then reverted my hosts file and uninstalled Adaway, and played with all the hide options in Magisk., to no avail. Root Checker app says that Safetynet is tripped.
Does Magisk effectively work for apps that look at Safetynet on this phone - apps like Chase Pay?
Click to expand...
Click to collapse
It is not normal to have it boot straight to twrp or the bootloader rather than the rom unless you do so manually.
Have you triedbplaying with the settings in Magisk Manager? There is an option to hide Magisk from your choice of apps. There is also a couple other options in the settings to hide things as much as possible. If you have Xposed installed it won't pass a safteynet check.
Sent from my Moto E (4) Plus using XDA Labs
XT1775 rom's is possible install on XT1776 ?
almao11 said:
XT1775 rom's is possible install on XT1776 ?
Click to expand...
Click to collapse
You could. I've flashed xt1775 firmware to my xt1776 to get a backup of the system to make a twrp flashable from. I don't recommend it, but if you only flash the system and not the modem and oem it should provision data services. Why do you ask exactly?
Sent from my Moto E (4) Plus using XDA Labs
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