Hi,
I want to buy and root my new Nexus 5x. I know that your override the recovery and install supersu, which puts some files in the system partition.
Now I wonder if it's even possible to hard brick your phone during this process?
As far as I know a hardbrick appears only if you flash the wrong bootloader or delete your partition table.
So is it safe to root your Nexus 5X?
It's very safe. It's almost impossible to hard brick a nexus rooting it. Just unlock the bootloader, it will wipe the device. Then boot twrp 3.0.0-2 and flash supersu 2.76
Sent from my Nexus 9 using XDA Free mobile app
You wrote "boot twrp". So should I only boot twrp? And does that work?
You can flash it if you want. I usually just boot it, fastboot boot twrp.img, then flash supersu.
Sent from my Nexus 9 using XDA Free mobile app
OK that seems very save .
I wonder what to do if some part of the nexus will break (microphone etc.). I think the warranty is lost, isn't it?
It's a nexus so there shouldn't be any problems. You can just flash a factory image and that will remove root and bring the device back to stock if you're concerned.
Oh, also, using supersu 2.76 is systemless so doesn't change anything and you can still flash ota's.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
It's a nexus so there shouldn't be any problems. You can just flash a factory image and that will remove root and bring the device back to stock if you're concerned.
Oh, also, using supersu 2.76 is systemless so doesn't change anything and you can still flash ota's.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Isn't the systemless method more risky because it's modifying the boot partition and the initramfs?
I've been looking for a guide like this for a long time. Thanks for the writeup.
On a serious note, if you boot twrp over USB there is a bug where it won't be able to decrypt your user partition if it is encrypted.
The default SuperSU is systemless, which just means it put the files into boot.img and image file it puts in /data. You still won't be able to apply differential OTAs you get over the air. You'd need to flash stock boot.img prior to applying differential OTA, then reinstall root, but this is usually pretty simple to do. Rather than figuring out what files got inserted into /system to "unroot" where some fragments might be left, getting rid of root is as simple as flashing original boot.img. Still have the SU.img filesystem image in /data, but that is basically harmless and has not other effect unless mounted by SuperSU.
Related
I have added root (su & SuperSU free application) to the stock Nexus 10 JOP40C image (2012/11/10).
To be flashed on a Google Nexus 10 with bootloader unlocked.
From fastboot mode, flash with:
Code:
fastboot -w update Nexus10-image-mantaray-jop40c-rooted.zip
Download from http://www.arctablet.com/blog/forum...ware-image-android-4-2-build-jop40c-20121110/
You don't really need to flash all the partitions for root
You could also just replace boot.img with one that has changed default.prop values to allow for rooted/debuggable adb... and then install SuperSU with cwm-recovery... no need to re-flash the entire system just to root it.
Attached is my modified boot.img for jop40c
SuperSU is located here http://forum.xda-developers.com/showthread.php?t=1538053
This is the method I used to root my Nexus 10.
I also modified cwm-recovery 6.0.1.6 so that it doesn't reboot after 20 seconds: http://forum.xda-developers.com/showpost.php?p=34256732
what is the best way to backup your apps , widgets etc without root?
n1r0k said:
what is the best way to backup your apps , widgets etc without root?
Click to expand...
Click to collapse
Take a look at My Backup, does a great job backing up apps and data and no root access needed.
shimp208 said:
Take a look at My Backup, does a great job backing up apps and data and no root access needed.
Click to expand...
Click to collapse
Thanks, I have backed up my apps, but then how do you get them off the device? I cant see any obvious folders when I plug into my PC.
Sorry I'm used to Root and titanium backup!
n1r0k said:
Thanks, I have backed up my apps, but then how do you get them off the device? I cant see any obvious folders when I plug into my PC.
Sorry I'm used to Root and titanium backup!
Click to expand...
Click to collapse
You don't need to transfer it off the device it backs them up to the partition that acts as the "SD card" on the tablet. Then after you wipe your tablet from unlocking bootloader, etc. reinstall the My Backup app and then select the restore option and then the backup you made. Hope this clears things up for you .
Does this affect any infinite loop boot issues or anything like that? Clean free? Can we use stock recovery for this?
Does this mean I have to unlock the boot loader and with this command that's mentioned above I rooted then? Nothing more to do? No Cwm or anything else?
Gesendet von meinem Nexus 10 mit Tapatalk 2
Thanks for this. Exactly what I needed after my brand new Nexus 10 got stuck on loading screen after unlocking. I can kill two birds with one stone using this.
How would I install CWM recovery after using this. Currently have it installed but can't sideload Supersu or mount my device to flash it from recovery. I'm thinking this is my best bet.
update. it worked, except i dot have touch cwm recovery
still stuck in a bootloop after this, any suggestions? :crying:
For some reason I'm just not able to Google this answer or find it here on XDA.
I'm on 5.0.1 (LRX22C) and want to go to 5.0.2 (LRX22G). I have downloaded an OTA update capture and tried to adb sideload it.
It failed. After a sec I thought, "duh. I'm rooted with franco kernel installed." I then did the following:
* Used SuperSU to unroot
* Booted to bootloader
* Flashed stock recovery and kernel
* Rebooted to recovery
* Attempted adb sideload again
This still gave a failure message.
The only other post I've seen where anyone is attempting the same suggests to use Nexus Root Tookit. I'm running Xubuntu. I've loaded it through wine but all the files it downloads are failing hash checks (though the app).
Can anyone post how to go from rooted 5.0.1 to 5.0.2 (LRX22G from LRX22C) without loosing user land data? I'd really do not want to flash the recovery image.
Notes: When trying to sideload with latest CWM recovery the script says that I'm on 4.0.4 (I think) and with TWRP it says I'm on 4.3. With stock recovery it gives me an error about the recovery script (7) or something similar.
Thanks,
Mike G.
Make sure you have downloaded the proper OTA for Nexus 7(2013).
Hashcheck fails in Nexus Root Toolkit is common.After Hashfails,there will be a dialog box which contains the steps to do it manually with the Link to the files.Download it & follow the instruction.
I hope this helps
I'm having the exact same problem. I'm attaching what's appearing on TWRP.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
I just used wugfresh's toolbox to do it. A piece of cake. I enjoyed a cup of coffee while I watched being updated.
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
yosmokinman said:
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
So I can just ”fastboot flash system system.img" from the 5.0.2 image and not loose data?
That seems like it would be the easiest. I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Sent from my Nexus 7 using XDA Free mobile app
^Yes. It's a good idea to flash boot as well just to get in the habit of it, it didn't change this time I don't think but I could later. Only flash the bootloader if it's a new version no need otherwise.
I simply ran:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Done, flash su through twrp to get root back.
You probably don't need to format cache but theres no reason not to and it could save you some trouble.
newkydawg said:
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
Click to expand...
Click to collapse
that worked perfectly for me. thx
mikejr83 said:
I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Click to expand...
Click to collapse
NRT opens a terminal window (a real-time log) and tells you exactly what it's doing while it does its work.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
I have a n7 2013 I have already rooted and installed twrp and SuperSU. I'm currently running 4.4.2 and to update to 5.02. Currently I'm getting the ota update msg for 4.4.3 which I've continued to ignore. With google not messaging me to update to 5.02 makes me think it's required to go to 4.4.3,4.4.4,5,5.02 is that correct? Or can one jump directly to 5.02? I want to keep root and twrp and my existing data I see mentioning of restoring stock recovery first. Why would one do that? What's the point of installing a custom recovery in the first place?
Long time ago I read that ota will work when rooted, but you'll lose root which then can be restored with twrp without losing data. Is that no longer true? Or is it only true of KitKat but not lollipop?
My recent apps button is no longer working. And when I go to Developer Options, I see Developer Options are not available for this user. Anyone else seeing that?
I installed MHC19J first and that was the incorrect version. I then flashed MMB29V and then the problems above started. I couldn't access quick menu, the recent apps button didn't work, and Developer Options showed as not available for this user. I just did a factory data reset and that seemed to get everything working again, but always a pain to have set everything up again! Damn Google! :-/
Probably due to you flashing the wrong image before flashing the correct one. Had no such problems after flashing this morning
Skickat från min Nexus 5X via Tapatalk
I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V
granets said:
I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V
Click to expand...
Click to collapse
Only do that if you are not rooted etc. If you use TWRP recovery and are not prompted for a password when booting into recovery, then you have the right image. It does work, the problem is trying to use Custom Recovery to flash SuperSU. Check that thread below.
https://www.reddit.com/r/nexus5x/comments/49e0ij/601_mhc19j/
I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.
no issues here on 19J. modified boot image here
bobby janow said:
I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.
Click to expand...
Click to collapse
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
I'm sorry I don't know. I haven't decrypted in quite some time now. I also haven't used xposed in a long time either. I don't ever format userdata or flash the userdata.img unless I absolutely have to. I'm encrypted, systemless, 2.68 SU and twrp 3.0. I'm leery to do anything now until twrp gets fixed for the J build. Although I might flash a J kernel via OTG if there comes one.
mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?
mickey4mice said:
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?
Click to expand...
Click to collapse
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk
i had some trouble so i clicked the flash all batch file. Anyone know how to root this build? i cant get super su zip file i transfer to show up in twrp. The file is there but twrp doesnt see it.
SlimSnoopOS said:
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.
Bump
Dominicano2 said:
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.
Click to expand...
Click to collapse
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu
Dominicano2 said:
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu
Click to expand...
Click to collapse
Sweet, glad you got that figured out
How is the new update in terms of making the phone better?
gvsukids said:
How is the new update in terms of making the phone better?
Click to expand...
Click to collapse
Seems like the lag pulling down the notification window that happened time to time is gone. Feels a little snappier but will need a week of up time to know for sure.
Notice that the "keep WiFi on during sleep" setting for "never" still doesn't work on the 5x. Also still have an audio bug that duplicates the source a second behind on Bluetooth when a notification is received which is disappointing.
Is there any way to wipe everything non-stock (including supersu systemless, xposed, etc) from fasboot, without being able to enter recovery?
The normal cache, boot, bootloader, radio, recovery, vendor partitions can be flashed over, and flashing the userdata.img after erasing it in theory wipes /data/sdcard/0/ (or however it's called now). However, what about the other changes systemless supersu, xposed and other mods may have done? for example, supersu's partition would stay? How could I literally reset all this to pure stock?
Thanks!
RusherDude said:
Is there any way to wipe everything non-stock (including supersu systemless, xposed, etc) from fasboot, without being able to enter recovery?
The normal cache, boot, bootloader, radio, recovery, vendor partitions can be flashed over, and flashing the userdata.img after erasing it in theory wipes /data/sdcard/0/ (or however it's called now). However, what about the other changes systemless supersu, xposed and other mods may have done? for example, supersu's partition would stay? How could I literally reset all this to pure stock?
Thanks!
Click to expand...
Click to collapse
Uninstall Xposed first. Now enter the bootloader and fastboot flash boot (to remove SuperSU) then fastboot flash system (to remove SuperSU and Xposed modifications in /system). That's it. Please use the factory image that matches your stock rom.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Uninstall Xposed first. Now enter the bootloader and fastboot flash boot (to remove SuperSU) then fastboot flash system (to remove SuperSU and Xposed modifications in /system). That's it. Please use the factory image that matches your stock rom.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for the fast reply!
My problem is that I didn't disable Xposed before the problem happened, and now I can't entery recovery. I am with a bootlooping phone that can only enter fastboot (and even so sometimes crashes there), impossible to boot or enter recovery by all means (even after flashing stock recovery) .
After flashing the stock boot and system (and all others) partitions, SuperSU should be completely gone, but Xposed? If I wasn't able to disable it before, it would be hooking app_process and more stuff, but would this stuff be overwritten by the new boot and system?
Thanks a lot!! :good:
RusherDude said:
Thanks for the fast reply!
My problem is that I didn't disable Xposed before the problem happened, and now I can't entery recovery. I am with a bootlooping phone that can only enter fastboot (and even so sometimes crashes there), impossible to boot or enter recovery by all means (even after flashing stock recovery) .
After flashing the stock boot and system (and all others) partitions, SuperSU should be completely gone, but Xposed? If I wasn't able to disable it before, it would be hooking app_process and more stuff, but would this stuff be overwritten by the new boot and system?
Thanks a lot!! :good:
Click to expand...
Click to collapse
Yes, both are removed when you flash those files. Xposed modules would still be installed but you can uninstall those in Android. What did you do to bootloop?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Yes, both are removed when you flash those files. Xposed modules would still be installed but you can uninstall those in Android. What did you do to bootloop?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Nothing. I hadn't flashed anything since august lol.. i was setting up an alarm and it froze and since then bootloop and freezes on every screen (including orange warning from bootloader unlocked, google logo, start of bootanimation, fastboot, recovery (when by miracle it shows the first image or stock one for a frame..) and even the charging animation when trying to charge it offline crashes).
I have talked with a google rep and she menaced me with warranty void if the device software was not original, lol?? on a nexus? on Europe when software modifications can't void a hardware problem warranty?? is this normal on Google? I know people that in the past sent devices even rooted booting normally and there was no problem, I don't know if something changed with the Pixel approach now... the only semi-stable boot mode is fastboot, most of the time it boots with the hardware combination keys and only sometimes crashes, most of the time lets you flash stuff with no problem.
I have flashed all the stock partitions (including erasing userdata and flashing userdata from the factory images..) and I don't know if I should lock the bootloader or just send it unlocked like I told them I had lol..
Hello everyone,
Since I'm facing difficulties connecting my Nexus 5X to my PC (believe me, I have tried nearly everything), I was wondering if it is possible to flash Magisk to my phone without the use of a PC. The bootloader is still unlocked because i've rooted my phone previously (when it still could connect to my PC). All the possibilities I ran into require either root or a PC.
I hope one of you guys knows a way how to handle this without losing all my data.
Thanks in advance!
Assuming you don't have a custom recovery installed either?? What's the "difficulty with trying to hook to a PC?
No, I don't have a custom recovery installed. There are more people facing this problem: https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4. Solution is not working for me for some reason.
To install magisk you need a custom recovery. And to install a custom recovery you need a pc.
Sent from my [device_name] using XDA-Developers Legacy app
I was afraid of that. Maybe i'll go with a factory reset then. Thanks tot the help anyways.
jd1639 said:
To install magisk you need a custom recovery. And to install a custom recovery you need a pc.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
_Hitman47 said:
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
Click to expand...
Click to collapse
So..... The bottom line is..... You still need a PC.
_Hitman47 said:
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
Click to expand...
Click to collapse
You're right. You can flash a boot image with fastboot. Is there a boot image that has magisk as party of it?
Well, I have installed Magisk Manager, and it gives me the option to patch a boot image-file. When I choose this option it askes me to select te original boot image-dump (.img or .img.tar). Since I'm no expert and I don't know where to find this and what this does, I'm afraid of losing my data or bricking my phone.
bluesh4rk said:
Well, I have installed Magisk Manager, and it gives me the option to patch a boot image-file. When I choose this option it askes me to select te original boot image-dump (.img or .img.tar). Since I'm no expert and I don't know where to find this and what this does, I'm afraid of losing my data or bricking my phone.
Click to expand...
Click to collapse
You would use the boot.img from the factory image that your rom is based on. Find your device below and download the 1 GB zip. Inside this zip is another zip you'll need to open to find the boot image (boot.img). Flashing boot images doesn't wipe internal storage, but it does remove root if you had it installed.
Factory images:
https://developers.google.com/android/images?hl=en
There's not really a collection of stock boot images besides what's included in the factory image.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You would use the boot.img from the factory image that your rom is based on. Find your device below and download the 1 GB zip. Inside this zip is another zip you'll need to open to find the boot image (boot.img). Flashing boot images doesn't wipe internal storage, but it does remove root if you had it installed.
Factory images:
https://developers.google.com/android/images?hl=en
There's not really a collection of stock boot images besides what's included in the factory image.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Instead of downloading the entire ROM, you might find what you need here: https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169
bluesh4rk said:
Hello everyone,
Since I'm facing difficulties connecting my Nexus 5X to my PC (believe me, I have tried nearly everything), I was wondering if it is possible to flash Magisk to my phone without the use of a PC. The bootloader is still unlocked because i've rooted my phone previously (when it still could connect to my PC). All the possibilities I ran into require either root or a PC.
I hope one of you guys knows a way how to handle this without losing all my data.
Thanks in advance!
Click to expand...
Click to collapse
Hello there ,
I have same as your issue.
My pixel 2 xl non rooted with unlocked bootloader.
So, Is it possible to flash latest OTA update directly through the phone via stock recovery?
As you aware that with the known and common pixel 2 xl issue which you can't get it connected to PC.
I'm stuck on October update and I'd be glad if someone could help me out on this matter.
Hi I'm new to rooting. I have a ZTE n9137 tempo x looking to root .I can't get this done.no recovery no boot.img no custom recovery none what so ever .the olny I keep reading is that I have to have a PC I don't like I said I'm new to root but I'm trying anything to get this done I unlocked the oem but I don't thing that it is enabled.?.?and I don't think that the phone can do this ota so now what ?? If I'm wrong plzz tell me where at I'm wrong and how to gain root thanks for all the help
Update not got root
hi everybody i wanted to root a samsung a3 2018(idk what version it is because it is still my grandma's phone) and as i know there isn't any twrp version for that phone