Related
Hello
Yesterday i unlocked bootloader on htc one x. Then i tried to root it but when i finished my hox did reboot and then reboot all the time. It goes on start screen of android and then reboot again. I cant do anything. Any idea or help?
How did you root it?
Did you flash a ROM without flashing its boot.img and fastboot erase cache?
Did you install a custom recovery?
What screen are you stuck on? "htc quietly brilliant"?
I remember when this happened to me when I first tried to root my phone (First Android phone actually) lol I freaked out.. In my case it's because I didn't make a full wipe after unlocking bootloader and flashing Cyanogen, just booted into Recovery, full wipe/wipe cache and it worked.
Tell us what you did like BenPope said, did you flash the boot.img for the ROM you installed?
the first i did was to unlock bootloader from htcdev. Afther that i tried to root by a guide from this forum:
ALTERNATE ROOT METHOD - 'INSECURE BOOT AND ROOT'
This zip file contains an insecure boot image to flash to your device and a script which will then push the root (SuperSU) files to your device. This is only tested on 1.27.401.2 / 1.27.401.7. USE AT YOUR OWN RISK!
Download
InsecureBootAndRoot r3 - DOWNLOAD (ROMraid) - MD5: a16bff582cb0e25fd3b422652d753ca7
How to use InsecureBootAndRoot - Windows, Linux and OSX
- Download the InsecureBootAndRoot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-insecure-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-mac.sh' followed by './install-insecure-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-linux.sh' followed by './install-insecure-linux.sh'
The device will now flash the new boot image and reboot. Keep the device attached to USB and when it has rebooted, ensure USB debugging is enabled - the SuperSU files will then be installed.
CONVENTIONAL ROOT METHOD - 'SUPERBOOT' (currently not functioning on shippping devices).
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Download
Superboot r1 - DOWNLOAD (ROMraid) - MD5: c79821d5d75d57dff8a5ffe7493241fd
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
That was the steps. I didnt tried to put a custom rom yet. And the worst is that i need my number and i dont have an another device with micro sd. :/
It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.
BenPope said:
It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.
Click to expand...
Click to collapse
I tried the first one and after i saw that my hpox rr all the time i tried the second one.
You mean this method?
EASIEST ROOT METHOD - 'RECOVERY + SUPERSU'
The easiest way to get root is now to install the official ClockworkMod release and then flash the latest SuperSU zip file. This approach is highly recommended (I also recommend running a backup as soon as you've flashed clockworkmod!)
I do now and nothing. Cant get the command.
I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Edit: ahh, is it "command not found" when you try to run fastboot?
BenPope said:
I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Click to expand...
Click to collapse
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.
IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.
Click to expand...
Click to collapse
You could just flash a rooted rom and kernel now, it should work fine.
Flash this recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Install a rom from recovery, you can mount usb from recovery to copy rom to phone.
Then flash the kernel from fastboot that acompanies the rom.
IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
Click to expand...
Click to collapse
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.
BenPope said:
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.
Click to expand...
Click to collapse
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.
What I dont get is why you didn't just root/unlock bootloader via htcdev.com
RohinZaraki said:
What I dont get is why you didn't just root/unlock bootloader via htcdev.com
Click to expand...
Click to collapse
He did. Thanks for playing.
IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
The command you did was correct but you flashed the stock recovery, flash clockworkmod recovery to proceed.
BenPope said:
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.
Click to expand...
Click to collapse
I used that command fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
So i think i didnt something wrong.
I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.
BenPope said:
I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.
Click to expand...
Click to collapse
Ok sry. I mean i tried boath of them.
IoSpy said:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Click to expand...
Click to collapse
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.
BenPope said:
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.
Click to expand...
Click to collapse
Ok i did and i have this screen now.
Hi Everyone,
sorry in advance for what is probably a dumb question. I have a HOX on Orange UK. It is successfully rooted but still on stock firmware - Android 4.0.4, HTC Sense 4.1, Software 2.17.61.3.
When checking in about I am told that there is an update available. I have downloaded it and can see that the file is called OTA_ENDEAVOR_U_JB_45_S_ORANGE_UK_3.16.61.6-2.17.61.3_release_3015.zip. However when I click in stall the phone reboots into teamwin recovery project v2.3.3.0. I then select Install adn browse to theis file which is in /sdcard/Download but the install keeps failing MD5 check. Unckecking the MD5 check still results in a failure since the error message is that the signature verification fails. Unchecking that still results in a failure- this time because of an "assert failure" whatever that is.
So a few questions.
1) Is this update worth having?
2) I am new to Android (10 years on a blackberry). Am I on ICS now and is this update to JB?
3) I am interested in a custom room. I really like the look and feel of the HTC sense and I have seen here that there are a lot of Sense custom roms. I presume I should stick to one of those. My main question is which one to install and what are the advantages. The honest truth is that apart from the Orange boot up and shut down logo there isn't much bloatware on this phone.
Thanks in advance for helping out a noob...
Yes its worth it, you have to flash back the stock recovery ! After that you can update.
Download this file and rename it to recovery.zip and copy it to your fastboot folder on the pc
http://db.tt/U5CK4noo
After that you put the phone in the bootloader/fastboot usb mode
Open a command prompt inside the fastboot folder and flash the stock recovery with these commands
Fastboot erase cache
Fastboot flash recovery recovery.img
Fastboot erase cache
Reboot the phone and try to update again
Mr Hofs said:
Yes its worth it, you have to flash back the stock recovery ! After that you can update.
Download this file and rename it to recovery.zip and copy it to your fastboot folder on the pc
xxxx://db.tt/U5CK4noo
After that you put the phone in the bootloader/fastboot usb mode
Open a command prompt inside the fastboot folder and flash the stock recovery with these commands
Fastboot erase cache
Fastboot flash recovery recovery.img
Fastboot erase cache
Reboot the phone and try to update again
Click to expand...
Click to collapse
Thank you. I am afraid I need you to spell it out in a little more detail since I rooted my phone using the Hasoon toolkit so that did all the command prompt side of things. I do know how to launch command prompt but that is about it!!! Sorry
Well you can check if the toolkit you used is capable of flashing a self providided recovery.img
Otherwise you have to install the HTC drivers and download the fastboot files from me
http://db.tt/ldx3qOOU
Place the files in a folder just like this
C:\fastboot\fastboot files i gave you
Then you open a command dosprompt inside the fastboot folder
Then you keep the phone on the homescreen and type
adb reboot bootloader
This will reboot the phone into the bootloader and you should see there FASTBOOT USB (connect the phone to the pc)
Then you do the commands i posted earlier
(Make sure usb debugging is enabled in the settings menu of the phone)
after flashing the stock recovery and updating root is lost, but superSU still there. How can we obtain root back? thanx
You have to reroot the rom again just like you did on ICS
geomad said:
after flashing the stock recovery and updating root is lost, but superSU still there. How can we obtain root back? thanx
Click to expand...
Click to collapse
u have to unlock the bootloader again over at htcDev http://www.htcdev.com/bootloader
*happy new year Mr Hofs!
beanbean50 said:
u have to unlock the bootloader again over at htcDev http://www.htcdev.com/bootloader
*happy new year Mr Hofs!
Click to expand...
Click to collapse
Happy newyear Mr Bean
And if he had the unlock_code.bin file he can flash it with fastboot
Fastboot flash unlocktoken unlock_code.bin
Mr Hofs said:
Happy newyear Mr Bean
And if he had the unlock_code.bin file he can flash it with fastboot
Fastboot flash unlocktoken unlock_code.bin
Click to expand...
Click to collapse
Do I have to flash clockwork first or can it be done with stock recovery? Thanx!
Happy new year!
you can do this with the stock recovery because you flash directly from the bootloader and not from the recovery
Well im trying to flash via fastboot but I get :
Code:
C:\onexroot>Fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.078s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.292s
PS. when in fastboot the phone state at the top is *** UNLOCKED ***
When I type 'su' in terminal
Code:
[email protected]:/ $ su
1|[email protected]:/ $
but apps still doent have superuser privilages
geomad said:
Well im trying to flash via fastboot but I get :
Code:
C:\onexroot>Fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.078s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.292s
PS. when in fastboot the phone state at the top is *** UNLOCKED ***
When I type 'su' in terminal
Code:
[email protected]:/ $ su
1|[email protected]:/ $
but apps still doent have superuser privilages
Click to expand...
Click to collapse
So the bootloader is actually unlocked ! Then forget the unlocktoken step !!! Now you have to flash the custom recovery and from there the super user root.zip
Mr Hofs said:
So the bootloader is actually unlocked ! Then forget the unlocktoken step !!! Now you have to flash the custom recovery and from there the super user root.zip
Click to expand...
Click to collapse
Thank you! so my problem is I'm still in stock recovery? cause superSu is still in my apps from ICS.
Lets get it straight...you updated the phone to JB and after that you restored apps (titanium backup ?) You need to reroot the stock JB rom properly again like flashing the root script from a custom recovery
i updated from OTA , so i didnt restore any apps. and when i write 'su' at terminal i dont get any errors. doesnt that mean su is installed?
If SU is installed you should see the SU app in the apps list ... My recommendation would be to reflash the custom recovery and re-apply the root
Mr Hofs said:
If SU is installed you should see the SU app in the apps list ... My recommendation would be to reflash the custom recovery and re-apply the root
Click to expand...
Click to collapse
yes, i can see the SuperSU app. but it seems that the apps ingore it. Don't know.. I'll reflash recovery and root and let you know! Thanx anyway!!
Its the best thing i can think of at the moment
Done - everything works perfect now! Thanx guys
Nice !
CASE CLOSED
Hello,
I have a big problem with my H815.
My H815 bootloader is been unlocked.
II try to install TWRP, but without success:
Code:
C:\Users\~\Downloads\G4\platform-tools>adb reboot bootloader
C:\Users\~\Downloads\G4\platform-tools>fastboot flash recovery twrp-2.8.7.0-h
815.img
target reported max download size of 536870912 bytes
sending 'recovery' (32064 KB)...
OKAY [ 1.197s]
writing 'recovery'...
OKAY [ 0.317s]
finished. total time: 1.520s
C:\Users\~\Downloads\G4\platform-tools>fastboot boot twrp-2.8.7.0-h815.img
downloading 'boot.img'...
OKAY [ 1.189s]
booting...
OKAY [ 0.036s]
finished. total time: 1.230s
For me, it's ok, but after that, my G4 reboot directly to the system (Android 6.0 : V20A).
And when I run the command "adb reboot recovery" I get to a screen where there is only an Android slept with a red triangle and "No command."
Any idea please?
Kind regrards,
~~
Sylar
I have exactly the same problem. Then I just can take out the battery and put the phone in download mode and then to flash via LG UP the kdz marshmallow file again. it seems I cannot install TWRP or root. The bootloader is unlocked of course.
nfsolutions said:
I have exactly the same problem. Then I just can take out the battery and put the phone in download mode and then to flash via LG UP the kdz marshmallow file again. it seems I cannot install TWRP or root. The bootloader is unlocked of course.
Click to expand...
Click to collapse
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
This does not work for me. :'(
After this command : fastboot boot twrp-2.8.7.0-h815.img
My G4 boot imediatly to the System... :s
hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
thanks, now it works. My mistake was that I installed directly a supersu (not this from twrp) and this messed up the boot.
After installing twrp permanently, I used this method to get root:
http://forum.xda-developers.com/g4/general/guide-root-lg-marshmallow-rom-repacked-t3265497
now I have root and twrp
Can someone help me please ?
I tried to flash the KDZ 2 times but still nothing I parobleme always the same.
hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
Thank you Sir!
Got the same problem, installed TWRP but got bugdroid dead once booting recovery. Idk why TWRP isn't written.
Nothing to do I'm trying every way I could imagine. The result is always the same.
I can't find solution on any forum. Please, I need help. :'(
Kind Regards
Hmm...have you already had root before flashing TWRP?
I think you can use Flashify.apk
rjboy11223 said:
Hmm...have you already had root before flashing TWRP?
I think you can use Flashify.apk
Click to expand...
Click to collapse
No i'm not rooted atm. That why i wanna install a custom recovery ^.^
Try fastboot boot twrpblabla.img
then inside twrp just flash twrp.zip (or as img..)
bender_007 said:
Try fastboot boot twrpblabla.img
then inside twrp just flash twrp.zip (or as img..)
Click to expand...
Click to collapse
Thank you, but after that... :
Code:
C:\Users\~\Downloads\G4\platform-tools>fastboot boot twrp-2.8.7.0-h815.img
downloading 'boot.img'...
OKAY [ 1.189s]
booting...
OKAY [ 0.036s]
finished. total time: 1.230s
...my G4 reboot directly to the system (Android 6.0 : V20A).
And when I run the command "adb reboot recovery" I get to a screen where there is only an Android slept with a red triangle and "No command."
Got exactly the same problem
adb reboot bootloader
fastboot boot <nameoftheTWRPimage>.img
then flash the SuperSU zip in order to get root
install TWRP Manager app
launch the app and accept to give su rights
choose your G4 model and the latest recovery version
install and validate reboot
:good:
bel57 said:
Got exactly the same problem
adb reboot bootloader
fastboot boot <nameoftheTWRPimage>.img
then flash the SuperSU zip in order to get root
install TWRP Manager app
launch the app and accept to give su rights
choose your G4 model and the latest recovery version
install and validate reboot
:good:
Click to expand...
Click to collapse
Thank you, but same problème i can't boot to TWRP after the comand "fastboot boot twrp-2.8.7.0-h815.img" my G4 reboot directly to the system.
Might be stupid, but is your bootloader unlocked?
Android 6.0 V20A stock?
bel57 said:
Might be stupid, but is your bootloader unlocked?
Android 6.0 V20A stock?
Click to expand...
Click to collapse
Yes, my G4 is unlocked. And and it's Android 6.0 stock beacause I did the update by LG Bridge.
Ur phone is weird lol
Sylar37 said:
Yes, my G4 is unlocked. And and it's Android 6.0 stock beacause I did the update by LG Bridge.
Click to expand...
Click to collapse
try first fastboot erase recovery, then fastboot flash recovery twrp....img
then fastboot reboot recovery
I downloaded the v20b kdz and flashed via LGUP.. I don't know what's wrong mate, sorry. :silly:
Hi,
I want to install TWRP so I can Install nAOSP ROM 8.1 for Xperia S on my phone.
The phone's bootloader is unlocked and the phone is rooted. I downloaded the correct version of TWRP from here (nozomi).
I tried installing via ADB (I followed the instructions here), but the command:
Code:
fastboot flash recovery twrp-3.2.3-nozomi.img
Fails with:
Code:
Sending 'recovery' (12964 KB)
(bootloader) USB download speed was 33272kB/s
OKAY [ 0.415s]
Writing 'recovery'
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: 'Partition not found')
Finished. Total time: 0.437s
I understand that this is because Sony phones don't have separate recovery partition, and that their recovery is incorporated to the boot.img (see here).
I then tried using the dd install method as described on the project's homepage.
Code:
$ ./adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11
25929+1 records in
25929+1 records out
13275872 bytes transferred in 3.747 secs (3543066 bytes/sec)
Although this seems to work (i.e. I don't get an error message), I cannot, try what I might, make the phone boot into recovery.
Can anyone tell me what I'm missing?
Just for anyone that comes across this post, I ended up solving my problem by flashing TWRP to boot.
Don't know if this is recommended or not, but it worked like a charm. I am now running nAOSP ROM 8.1 on my Xperia S.
_jack said:
Just for anyone that comes across this post, I ended up solving my problem by flashing TWRP to boot.
Don't know if this is recommended or not, but it worked like a charm. I am now running nAOSP ROM 8.1 on my Xperia S.
Click to expand...
Click to collapse
How exactly did u do that...i have spent over a week trying to do it.
sweetbanana said:
How exactly did u do that...i have spent over a week trying to do it.
Click to expand...
Click to collapse
Just replace "recovery" with "boot".
Code:
sudo fastboot flash boot twrp-3.2.3-nozomi.img
_jack said:
Just replace "recovery" with "boot".
Code:
sudo fastboot flash boot twrp-3.2.3-nozomi.img
Click to expand...
Click to collapse
I did that to my Xperia S and it worked too, but after i reboot to system. It just puts me to Cyanogen recovery and idk how I have Cynaogen recovery but its there. And its just stuck there, and wouldnt let me boot to Android. The recovery mode for cyanogenmod is the only thing thats there. I flashed twrp to boot (when i was at the twrp fastboot) and it didnt anything at all. Which made my xperia bricked. I had to reflash the firmware 3 times to troubleshoot the problem.
ZebastianJV said:
I did that to my Xperia S and it worked too, but after i reboot to system. It just puts me to Cyanogen recovery and idk how I have Cynaogen recovery but its there. And its just stuck there, and wouldnt let me boot to Android. The recovery mode for cyanogenmod is the only thing thats there. I flashed twrp to boot (when i was at the twrp fastboot) and it didnt anything at all. Which made my xperia bricked. I had to reflash the firmware 3 times to troubleshoot the problem.
Click to expand...
Click to collapse
Try flashtool to install twrp. twrp link: https://androidfilehost.com/?fid=1322778262904003720
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
ZebastianJV said:
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
Click to expand...
Click to collapse
No, it won't be a problem.
ZebastianJV said:
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
Click to expand...
Click to collapse
i had the same issue i just flashed the firmware boot.img with flashtools 0.9.8.0
Extract with 7zip/winrar/winzip. Use this kernel via flashtool. has recovery. note for unlocked bootloaders only
Hey guys and girls,
This is a bit of copy and paste for from my guide for the HTC U12+. I thought it might be helpful to people here too.
If you find mentions of the HTC U12+ please notify me and I will correct them.
I couldn´t find any guide on how to root the Asus Zenfone 6 without twrp yet, so I thought maybe it´s good to have one. It´s also useful for people who don´t like to boot/flash the recovery but want root access.
I also decided now to do a little write up about the A/B slot partition system.
General Information about the A/B slot partition system and seamless updates
Google firstly introduced seamless updates on the Pixel Phones and with it the A/B partition system.
So this means, contrary to non A/B devices, there are two copys of most partitions except userdata.
We have two system (system_a and system_b), two boot (boot_a and boot_b) and two vendor (vendor_a and vendor_b) partitions, amongst others (can be found further down in the partition list but let´s concentrate on these).
When booted in the OS, one slot is actively used and the other is "inactive".
The main advantage that emerges now is, that in case an OTA arrives the "inactive" partitions get updated, while the OS is running. That means while the actual OTA is happening you can use your phone just like you always do.
The following reboot will boot into the former "inactive" slot and use the seamless updated partitions. This happens seamless and just with a reboot. So OTAs are much faster!
If you are interested further here are some links:
https://www.xda-developers.com/list-android-devices-seamless-updates/
https://source.android.com/devices/tech/ota/ab/
https://source.android.com/devices/tech/ota/ab/ab_faqs
Here’s another writeup from the XDA portal!
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
But here are a few tips and tricks:
How to reboot to bootloader to be able to use fastboot:
From booted OS with buttons: Press and hold power down until the screen goes black, then press and hold power and vol up to enter bootloader
non responding and the phone isn´t booting: press and hold power plus volume up to enter bootloader
From the OS or recovery via ADB (requires USB Debugging enabled in dev options):
Code:
adb reboot bootloader
How to get the active slot:
Code:
fastboot getvar current-slot
How to set the active slot:
A word of advice. If you don´t know what you´re doing you should probably not change slots. Because my U12+ only has a working A Slot. The B slot is without the first OTA or flashing a RUU unbootable.
Set active slot to a:
Code:
fastboot --set-active=a
Set active slot to b:
Code:
fastboot --set-active=b
How to extract the boot.img from a firmware.zip
1. Download the firmware zip from here : https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
2. Follow the steps described here: https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
3. Obtain your boot.img
How to root your phone without TWRP
Prerequisites:
- unlocked bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries (can always be found here
- working adb and fastboot environment
- magisk-patched boot.img
How to:
1. Download the latest magisk manager from here and install it on your phone: https://github.com/topjohnwu/MagiskManager/releases
2. Get a boot.img that fits your current firmware. Look at the point above, how to extract it from an Asus firmware zip.
Important: if you decide to use a pre-patched boot.img (available below), download it and place it in your fastboot folder, then skip to step 11!
3. Copy the extracted boot.img to your phone
4. Open the magisk manager app and tap two times on install
5. Now choose patch boot.img file and select the previously extracted boot.img you copied to your phone in the upcoming file chooser
6. Wait for the boot.img to be patched
7. Now connect your phone to your pc and make sure usb debugging is enabled in developer options
8. Open up a terminal in your fastboot folder and make sure adb is working by typing
Code:
adb devices
into terminal which should return your serial number
9. Pull the patches boot.img to your fastboot folder via:
Code:
adb pull /sdcard/Download/magisk_patched.img
10. Reboot to bootloader:
Code:
adb reboot bootloader
11. Flash the magisk patched boot.img:
Code:
fastboot flash boot magisk_patched.img
12. Congratulations you´re now rooted.
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609
Is it possible to do this and still get OTA updates from ASUS?
sidamos77 said:
Is it possible to do this and still get OTA updates from ASUS?
Click to expand...
Click to collapse
You need to unlock the bootloader for this which will prevent you from getting ota updates automatically from asus. But you can install updates manually.
Ok, great, thank you.
Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.
Any way to unofficially unlock the Bootloader?
vasra said:
Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.
Click to expand...
Click to collapse
In Europe unlocking the bootloader and rooting doesn't legally void warranty. It was ruled this way a few years ago.
Freak07 said:
[...]
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609
Click to expand...
Click to collapse
The folder WW_PHONE-16.1210.1904.75-0 which is the firmware my device has, is empty. Do you still have the prepatched boot.img of that version ? ASUS doesn't have that version for download anymore.
Thanks in advance.
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
GRöder said:
how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-26#post-2433773
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-37#post-2442236
Use Translator.
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
the getvar command returns the following output:
Do you have any advice for me ?
Edit:
After being curious and trying which worked, I tried to flash it at the active slot b explicitly: which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.
Freak07 said:
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.
Click to expand...
Click to collapse
That might have been the the point. In fact, I did download them, but I used (definately outdated, because on my pc since literally years) a minimal adb and fastboot installation.
I didn't think about it, as this is my first A/B device.
I won't try it now with the latest ones, because it worked and I don't want to destroy something (since we still dont have a working TWRP for backup & recovery) but I guess you're right, and the problem were the outdated binaries.
Thank you.
GRöder said:
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.
isthisadagger said:
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.
Click to expand...
Click to collapse
In fact, I tried that before I tried the stock-recovery-method (found it at the ASUS FAQ-pages), but it didn't work, even after a reboot, no notification showed up.
GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks
Ya how do we unlock the bootloader without asus knowing it
MirkoMirko9 said:
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks
Click to expand...
Click to collapse
nikhil18 said:
Ya how do we unlock the bootloader without asus knowing it
Click to expand...
Click to collapse
I used the official app, while the device was connected to the internet. So yes, ASUS knows that I unlocked the device.
The device was still at the -75 firmware, when I did it.
@MirkoMirko9 If you can live with asus knowing that you unlocked the device, try it again with active internet connection.
As far as I know, there is no other method yet.
unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?
QuazIqbal said:
unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79817571&postcount=31
magisk_patched boot.img for .156 firmware is uploaded to the patched boot.imgs folder