Related
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
OscarBrito said:
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
Click to expand...
Click to collapse
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
KingRoot
prdog1 said:
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
Click to expand...
Click to collapse
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
None of the unroot options put things back to 100% stock. They just remove root. The only way to remove all traces is to fastboot flash the system.img
If you're going to run rooted, forget about OTA and learn about fastboot.
General > sticky roll-up > adb and fastboot
Reset
prdog1 said:
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
Click to expand...
Click to collapse
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
OscarBrito said:
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
Click to expand...
Click to collapse
Nope. Have to flash stock image as posted above.
prdog1 said:
Nope. Have to flash stock image as posted above.
Click to expand...
Click to collapse
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
OscarBrito said:
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
Click to expand...
Click to collapse
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
danarama said:
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
Click to expand...
Click to collapse
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
Fastboot works with Linux also.
OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
danarama said:
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
Click to expand...
Click to collapse
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Better chance of bricking it with ToolKit than with manual fastboot. I run stock rooted with TWRP also. Takes 2-3 minutes to update with fastboot. If toolkit fails will most likely need fastboot to fix it anyway.
OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
danarama said:
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
Click to expand...
Click to collapse
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
OscarBrito said:
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
Click to expand...
Click to collapse
I can't see how any Linux user would be afraid of terminals
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
imor said:
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
Click to expand...
Click to collapse
You will lose root. Flash supersu from recovery before first boot
Ok, just confirming here before I mess up. I have an international N6 rooted with stock recovery running LMY47Z. I can't update OTA. So I should flash the full stock image and then run cf-auto-root before rebooting.
Is this correct? Will I lose my user data when I do this? If so, what's the easiest way to backup and restore? Can't I flash the 25MB update .zip instead?
Thanks!
Need a root method as soon as possible.
wleagle said:
Need a root method as soon as possible.
Click to expand...
Click to collapse
I am trying to search the tutorial but here i want to inform you that After rooting you will be lost your smartphone warranty.
If you want to boot the HTC One X9 Smartphone, Just follow the given process below:
Unlock your HTC One X9 smartphone
After that you need to install Android ADB & Fast boot drivers carefully.
Making sure that your mobile has at least 60% battery charge
Make sure that you have backed up all your important
After Install fast boot drivers, you will able to boot your smartphone quickly
If you wanna root your device, install the applications which rootable. ex : Super SU, Busy Box etc
molanjami said:
I am trying to search the tutorial but here i want to inform you that After rooting you will be lost your smartphone warranty.
Click to expand...
Click to collapse
Of course I know, but I prefer having more functions. I think it is easy to unlock the bootloader, but there is not any 3rd party recovery available. Maybe I should wait until update to 6.0
wleagle said:
Of course I know, but I prefer having more functions. I think it is easy to unlock the bootloader, but there is not any 3rd party recovery available. Maybe I should wait until update to 6.0
Click to expand...
Click to collapse
If you will find how to root it write me pls
Poma Nine said:
If you will find how to root it write me pls
Click to expand...
Click to collapse
Off course bro i am trying to find
Hey all,
Is this phone available in USA market?
Best Regards
Hey guys, I rebuild the TWRP 2.8.7.0 recovery from M9+
You can try it will work or not, but I have China's stock recovery only so far...
So, use it at your own risk
twrp-2.8.7.0-e56ml_dtul.img
https://www.androidfilehost.com/?fid=24411628330025819
BTW, if someone can provide me the hosd file, I can decrypt the RUU file and make stock ROM
sabpprook said:
Hey guys, I rebuild the TWRP 2.8.7.0 recovery from M9+
You can try it will work or not, but I have China's stock recovery only so far...
So, use it at your own risk
twrp-2.8.7.0-e56ml_dtul.img
https://www.androidfilehost.com/?fid=24411628330025819
BTW, if someone can provide me the hosd file, I can decrypt the RUU file and make stock ROM
Click to expand...
Click to collapse
Successfully flashed, but cannot mount /system partition. When flash this recovery again it returns "download for partition recovery is not allowed"
wleagle said:
Successfully flashed, but cannot mount /system partition. When flash this recovery again it returns "download for partition recovery is not allowed"
Click to expand...
Click to collapse
Or you can backup the boot image by TWRP revovery
and send it to me, I can make pre-root boot image for you
sabpprook said:
Or you can backup the boot image by TWRP revovery
and send it to me, I can make pre-root boot image for you
Click to expand...
Click to collapse
Okay, I'll do this after going back home, Thanks!
wleagle said:
Okay, I'll do this after going back home, Thanks!
Click to expand...
Click to collapse
flash boot image in download mode
https://www.androidfilehost.com/?fid=24415232478674992
install phhs superuser app
https://play.google.com/store/apps/details?id=me.phh.superuser
you could get root permission now
sabpprook said:
flash boot image in download mode
https://www.androidfilehost.com/?fid=24415232478674992
install phhs superuser app
https://play.google.com/store/apps/details?id=me.phh.superuser
you could get root permission now
Click to expand...
Click to collapse
I have followed your instruction. The modified boot image is successfully flashed , and phhs superuser is installed. But when I input su in terminal, it returns permission denied
wleagle said:
I have followed your instruction. The modified boot image is successfully flashed , and phhs superuser is installed. But when I input su in terminal, it returns permission denied
Click to expand...
Click to collapse
how about this file
https://www.androidfilehost.com/?fid=24415232478676396
sabpprook said:
how about this file
https://www.androidfilehost.com/?fid=24415232478676396
Click to expand...
Click to collapse
Still not work...
sabpprook said:
how about this file
https://www.androidfilehost.com/?fid=24415232478676396
Click to expand...
Click to collapse
Shall I wipe data before flashing the boot image?
wleagle said:
Shall I wipe data before flashing the boot image?
Click to expand...
Click to collapse
Maybe you should modify the boot image by yourself
1. flash the stock boot image that you've backup
2. flash the superuser.zip that provided in this thread in TWRP recovery
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Good luck, bro
sabpprook said:
Maybe you should modify the boot image by yourself
1. flash the stock boot image that you've backup
2. flash the superuser.zip that provided in this thread in TWRP recovery
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Good luck, bro
Click to expand...
Click to collapse
Great! It works!
Hello there you have x9 official rom or recovery.img
Hello there you have x9 official rom or recovery.img
Is there any way to root without TWRP? I'll be doing this for a family member, and want to keep it as stock as possible. I just want root to remove some stock apps they don't need, then probably unroot. Is there any way to do so? Otherwise I was thinking of flashing TWRP, rooting, then flashing back the stock recovery.
Purplezigar said:
Is there any way to root without TWRP? I'll be doing this for a family member, and want to keep it as stock as possible. I just want root to remove some stock apps they don't need, then probably unroot. Is there any way to do so? Otherwise I was thinking of flashing TWRP, rooting, then flashing back the stock recovery.
Click to expand...
Click to collapse
You can boot into twrp.
Use "fastboot boot twrp-recovery-file location"
Then you can just use the root shell from twrp to make changes, no need to flash SuperSU if you want the ROM unrooted.
mrmazak said:
You can boot into twrp.
Use "fastboot boot twrp-recovery-file location"
Then you can just use the root shell from twrp to make changes, no need to flash SuperSU if you want the ROM unrooted.
Click to expand...
Click to collapse
I'm not quite sure what you're saying, but it sounds like you're saying that I can boot into the TWRP image while I'm connected with fastboot, without actually installing TWRP?
Purplezigar said:
I'm not quite sure what you're saying, but it sounds like you're saying that I can boot into the TWRP image while I'm connected with fastboot, without actually installing TWRP?
Click to expand...
Click to collapse
That's right. You can just boot twrp instead of flashing it.
And when twrp is booted you can connect to phone with adb, you will have a shell with root privileges.
mrmazak said:
That's right. You can just boot twrp instead of flashing it.
And when twrp is booted you can connect to phone with adb, you will have a shell with root privileges.
Click to expand...
Click to collapse
Cool! So then I can just remove system installed apps that I don't want (e.g. Google Play Movies and Books)?
Purplezigar said:
Cool! So then I can just remove system installed apps that I don't want (e.g. Google Play Movies and Books)?
Click to expand...
Click to collapse
You could also read this thread as see if the twrp packages there are what you want to do.
They can all be run from the booted twrp.
https://forum.xda-developers.com/r1-hd/how-to/guide-ad-removal-debloat-block-ota-easy-t3429555
mrmazak said:
You could also read this thread as see if the twrp packages there are what you want to do.
They can all be run from the booted twrp.
https://forum.xda-developers.com/r1-hd/how-to/guide-ad-removal-debloat-block-ota-easy-t3429555
Click to expand...
Click to collapse
Awesome, thanks!
Wow no need for custom recovery...
http://www.androidpolice.com/2017/0...hout-root-installing-without-custom-recovery/
@ultramag69 Maybe he doesn't follow Magisk closely? I know I don't. Magisk is only on used my stepmom's OP3T H2OS (which I update but don't look at the change log since it's only there in case I need it in the future), the other 2 phones I support don't use Magisk they use LOS su add-on. Not everyone who uses root cares about all the bloated/"nifty" features that come out, some just want plain old root.
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
I'm letting people know that with 14 they can keep stock recovery and take OTAs
ultramag69 said:
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
Click to expand...
Click to collapse
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
lollyjay said:
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
Click to expand...
Click to collapse
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
ultramag69 said:
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
Click to expand...
Click to collapse
No need to do that now
Honestly, who roots a phone without flashing a custom recovery the very second after? Unless they are forced to use Flashfire without BL unlock, I guess.
lollyjay said:
No need to do that now
Click to expand...
Click to collapse
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
ultramag69 said:
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
Click to expand...
Click to collapse
No problems at all with my OP5
Magisk 14.0 breaks XPosed so had to go back to Magisk 13.3
Now where can we obtain a copy of the stock boot.img?
almostthere said:
Now where can we obtain a copy of the stock boot.img?
Click to expand...
Click to collapse
What you're supposed to do is make a backup of your boot partition any time you update your rom. So if you didn't do that then you can dirty flash your current Rom and that would give you the stock boot.img and again, go into recovery and make a backup of your boot partition. then if you want to flash a custom kernel you can.
Help the noobs
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
s_ofer said:
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
Click to expand...
Click to collapse
I have the stock 4.5.10 boot.img for download here:
https://drive.google.com/file/d/0B3gcDbDvV4Mkbm5EMEZ4dnpSbk0/view?usp=drivesdk
Sent from my OnePlus5 using XDA Labs
Thanks.
Do any of you think it is possible to FLASH anything without unlocking the bootloader?
There is a thread somewhere for OP3T that shows somehow that is possible to load TWRP on the phone without unlocking the bootloader or wiping data.
I only use for root too but every so often I open magisk manager as it updates also both the manager app and magisk itself. But using magisk to root my Axon 7 with unlocked bootloader.
My device has only ADB SU, can execute ADB Root and ADB Remount, can ADB shell setenforce 0. but cant unpack boot.img. I want to know if can get Root By Magisk.
That's not as straightforward a question as you might think... What do you mean when you say "can't unpack boot.img"? Are you trying to install Magisk and it fails, or what is it that you're asking?
I cant flash TWRP, how to install Magisk?
can install magisk by adb?
@topjohnwu has made some pretty detailed installation instructions that you might want to look at. You can find them on Github:
https://topjohnwu.github.io/Magisk/install.html
With no access to TWRP you need to use the boot/recovery image patching method.
If your "can't unpack boot.img" means that you do not have any kind of access to the device boot image you are probably out of luck...
Didgeridoohan said:
@topjohnwu has made some pretty detailed installation instructions that you might want to look at. You can find them on Github:
https://topjohnwu.github.io/Magisk/install.html
With no access to TWRP you need to use the boot/recovery image patching method.
If your "can't unpack boot.img" means that you do not have any kind of access to the device boot image you are probably out of luck...
Click to expand...
Click to collapse
if bootloader is locked, then flash the patched boot.img into device, can work?
yhyzhj said:
if bootloader is locked, then flash the patched boot.img into device, can work?
Click to expand...
Click to collapse
Generally: no. Not without using some serious exploits on that bootloader (assuming there even are exploits to use). And even then it would probably be a pretty risky endeavour...
i see, but i dont know that if device have BL, becase my device no fastboot mode.
What device is it we're talking about?
If it's even at all possible, installing Magisk on it sounds like way more work than it's worth...
Didgeridoohan said:
What device is it we're talking about?
If it's even at all possible, installing Magisk on it sounds like way more work than it's worth...
Click to expand...
Click to collapse
xiaomi box
From a very quick look, those boxes seem to be locked up pretty tight... You can search both XDA and the web in general and find more on this.