Database Users

Is it Unlocking, rooting, or both that wipes my device?

TD;DR Since I already have the bootloder unlocked, would re-rooting my N7 wipe it?
I know it's a noobish question, I've already rooted my device once, but it was fresh out of the box, I had nothing important on it.
I accidentally updated to 4.2.2 and it screwed up my Bluetooth.
I rooted on 4.2.2 and rolled back to 4.1.2.
Decided that Bluetooth wasn't such a huge deal (got tired of carrying around a Wiimote and Nunchuck everywhere,) so I updated back to 4.2.2, which made me lose my root.
(I even used a root protecting app, didn't work :/ )
So yeah, It's unlocked, I can get to the bootloader and all that jazz.
So does Rooting wipe the N7, or is it just when you first unlock it?

Exact same happened to me I would appreciate an answer too.
Sent from my Nexus 7 using XDA Premium HD app

blahman179 said:
TD;DR Since I already have the bootloder unlocked, would re-rooting my N7 wipe it?
I know it's a noobish question, I've already rooted my device once, but it was fresh out of the box, I had nothing important on it.
I accidentally updated to 4.2.2 and it screwed up my Bluetooth.
I rooted on 4.2.2 and rolled back to 4.1.2.
Decided that Bluetooth wasn't such a huge deal (got tired of carrying around a Wiimote and Nunchuck everywhere,) so I updated back to 4.2.2, which made me lose my root.
(I even used a root protecting app, didn't work :/ )
So yeah, It's unlocked, I can get to the bootloader and all that jazz.
So does Rooting wipe the N7, or is it just when you first unlock it?
Click to expand...
Click to collapse
javajava14 said:
Exact same happened to me I would appreciate an answer too.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Rooting wipes data, its best you make a nandroid backup or backup to PC......correct if I'm wrong hope this helps

I don't think so.
The unlocking generally wipes it.
I've rooted many a device (that weren't locked) and they weren't wiped.
Now, installing a ROM generally calls for a wipe unless you're updating the same....

If you use a root method that calls for an unlocked bootloader, unlocking the bootloader wipes. Any root method that does not require an unlocked bootloader will not wipe the device.
Sent from my SPH-D710 using xda premium

graydiggy said:
If you use a root method that calls for an unlocked bootloader, unlocking the bootloader wipes. Any root method that does not require an unlocked bootloader will not wipe the device.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
This is very correct that's why I just throw in the.......correct me if I'm wrong!

Unlocking bootloader wipes data, not rooting....

dalanik said:
Unlocking bootloader wipes data, not rooting....
Click to expand...
Click to collapse
Yep. Agreed.
Rooting and Unlocking the Bootloader have seemingly become synonymous with each other, and confusion has crept in. Because the 'traditional' method of Rooting the Nexus 7 necessitates an unlocked Bootloader (in order to run the required Fastboot commands).
Unlocking the Bootloader (which for security reasons wipes the device) and Rooting are two completely different procedures (but the success of one, is contingent upon the success of the other).
And of course you can now Root the N7 without unlocking the Bootloader at all (and thus no wipe), with this 'exploit'...
http://forum.xda-developers.com/showthread.php?t=2233852
Rgrds,
Ged.

although if you want to install a different rom, a wipe is highly suggested for stability. not 100% required, but much better if you wipe. i highly suggest Helium (also known as Carbon) to back everything up, along with a nandroid just in case. enjoy ur n7!

You certainly should be wiping between ROM flashes, but keep in mind that OP's bootloader is already unlocked. At this point, more or less any root exploit will work without OP losing data, since they can skip unlocking the bootloader.
All you should have to do, OP, is download a custom recovery and root zip, put your device into fastboot, and then run fastboot flash recovery <path-to-recovery-img>, then flash your root zip.

Rirere said:
You certainly should be wiping between ROM flashes, but keep in mind that OP's bootloader is already unlocked. At this point, more or less any root exploit will work without OP losing data, since they can skip unlocking the bootloader.
All you should have to do, OP, is download a custom recovery and root zip, put your device into fastboot, and then run fastboot flash recovery <path-to-recovery-img>, then flash your root zip.
Click to expand...
Click to collapse
Edit: Tried that one-click root that was referenced earlier, didn't work.
It hung up on "daemon started successfully," for like, 10 minutes before I stopped.
It can't be that it doesn't see my tablet, so.
I'm trying it again right now, but I doubt it'll do anything.

Drivers.
Sent from my Nexus 7 using xda premium

graydiggy said:
Drivers.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
NOPE.
No root access, Superuser fails to gain it to update it's binary...
BUT.
I go into the Terminal Emulator, type "su," and it sends back a #, which signifies that I have this thing Rooted, as shown here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: Left the Checker running, and it says, after all this BS, that I don't have proper root access...

[NOOB FRIENDLY] Sprint Galaxy S4 Questions Thread - ALL Are Welcome!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Credits to @Disturbed™ for the awesome picture!)
I saw this on another part of the forum, so I thought I might as well expand it here! Credits to @malybru for inspiration and help!
Useful links will be in the 2nd post.
Personal recommendations will be in the 3rd post.​
BEFORE POSTING ANYTHING, PLEASE READ THIS:
BEGINNER'S GUIDE AND FORUM RULES
YOU ARE FREE TO ASK ANY QUESTIONS ON THIS THREAD! I WILL TRY TO PROVIDE AN ANSWER OR I WILL DO MY BEST TO PUT YOU ON THE RIGHT TRACK! THERE IS NO ABUSE OR FLAMING TO NOOBS/NEWBS HERE! ​
Always remember to search before posting! There most likely is SOMEONE out there with a similar problem to yours!​Make sure that you have a SPRINT SAMSUNG GALAXY S4. If you do not, you are in the wrong section of the forum! Try out this link and see which model you have and add it to your signature - Useful Signatures​
There are other variants of the Galaxy S4 here:
International GS4 (Help Thread)
T-Mobile GS4 (Help Thread)
Verizon GS4
AT&T GS4
South Korean Help Thread
​​
Please hit the Thanks button if I (or anyone else) helped you out!
Also, I don't take credit for ANY of the links I have posted! They are all from the helpful developers of XDA and the moderators!
MY STORY:
So I was also a newb at one point (weren't we all), and I really didn't know who to go too. XDA came into my life and I was so happy. The problem, however, is that sometimes the terminology and that "new person" feeling was making me feel on edge. That, however, was a while ago. I know a lot more, but I wanted to make this thread to try and help out some of the newer people who are entering the Android world.

[NOOB FRIENDLY] SPH-L720 Questions Thread - ALL Are Welcome!
Quick update guys...
09/09/2013
So as many of you know, school has started and I've hit the books. I barely get any time for XDA (which I am very, very sorry for!), so I won't be updating as often. I will try to update as much as I can, but with a pretty rough schedule this year, I'll see what I can do.

[NOOB FRIENDLY] SPH-L720 Questions Thread - ALL Are Welcome!
Here are some quick useful links that you can use!​
Link to Galaxy S4 root - Galaxy S4 Root HOW TO
Stock Firmware - Stock Firmwares
Directory of *almost* every mod, tweak, ROM and Kernel for Sprint Galaxy S4 - Roms/Kernels/Recoveries/Mods/Themes/Games/Apps
WiFi Hotspot Mod - Hotspot Mod
Consumer Guide - Sprint S4 User Guide
*Will add more as things continue to develop!*

I have a question about kernels I want to get a new kernel but if I don't like the new one how would I go back to the old one
Sent from my SPH-L720 using xda app-developers app

Glad to see someone had the guts to start this thread.
I too, for one, get tired of the condescending attitude of people who forget that they were once noobs.
Congrats!

danzelcool said:
I have a question about kernels I want to get a new kernel but if I don't like the new one how would I go back to the old one
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Easiest way is to do a backup before flashing any kernel, rom, or mod. Then you can always revert should there be an issue or problem.
Sent from my SPH-L720 using Tapatalk 4 Beta

MF9 hotspot mod issues
I was running rooted MDL on my sprint gs4 but wanted to update to MF9 so i unrooted then updated to stock MF9 i then used cfautoroot to root the stock MF9 which worked just fine.... i attempted the hotspot mod using the odexed MF9 "system.jar" and "system.odex" files then did a reboot.....the replaced files soft bricked my phone....it was stuck on the sprint splash screen it would not go any further....i had to re-flash back to stock MDL to get my phone booted up again....I'm not sure what the issue is with the MF9 hotspot mod because the MDL hotspot mod works like a charm. If anyone has any insight into this problem all help would be greatly appreciated....because i would much rather be updated to the latest software but i still need my hotspot feature to work

twisclone said:
I was running rooted MDL on my sprint gs4 but wanted to update to MF9 so i unrooted then updated to stock MF9 i then used cfautoroot to root the stock MF9 which worked just fine.... i attempted the hotspot mod using the odexed MF9 "system.jar" and "system.odex" files then did a reboot.....the replaced files soft bricked my phone....it was stuck on the sprint splash screen it would not go any further....i had to re-flash back to stock MDL to get my phone booted up again....I'm not sure what the issue is with the MF9 hotspot mod because the MDL hotspot mod works like a charm. If anyone has any insight into this problem all help would be greatly appreciated....because i would much rather be updated to the latest software but i still need my hotspot feature to work
Click to expand...
Click to collapse
I would suggest you to take a look here: MF9 Hotspot Mod

I have a question too, actually.
Flashing to a new kernel is the same way as flashing a ROM, right? I heard that you need to fix permissions, but some say you shouldn't...
So after flashing to a new kernel, is fixing permissions required?

twisclone said:
I was running rooted MDL on my sprint gs4 but wanted to update to MF9 so i unrooted then updated to stock MF9 i then used cfautoroot to root the stock MF9 which worked just fine.... i attempted the hotspot mod using the odexed MF9 "system.jar" and "system.odex" files then did a reboot.....the replaced files soft bricked my phone....it was stuck on the sprint splash screen it would not go any further....i had to re-flash back to stock MDL to get my phone booted up again....I'm not sure what the issue is with the MF9 hotspot mod because the MDL hotspot mod works like a charm. If anyone has any insight into this problem all help would be greatly appreciated....because i would much rather be updated to the latest software but i still need my hotspot feature to work
Click to expand...
Click to collapse
I did the exact same thing, but it worked perfectly the only thing. I'm not sure what mod caused it xposed,prl enabler, probably one of these that made my phome so slow to boot. It takes twice as long as before. Anyway, I'm guessing you probably downloaded the incorrect file.

I've heard several cases where the new mf9 update reduces boot speed.
Sent from my SPH-L720

Alright, here goes:
I am rooted (TWRP Recovery which I boot to through Goo Manager), SuperSU, Rom Toolbox, Adblock Plus, Hotspot Mod.
I achieved root via CF-Autoroot a while back, pre-MF9 update. As such, I am still running on MDL.
Now, let's assume I wanted to update to MF9 and then install an MF9-based ROM.
I'm a bit confused as to the steps. I think they go something like:
1) Uninstall any Root only apps (or move them somewhere? freeze? something else?)(And I can't very well remove SuperSu or TWRP Recovery can I?)
2) Boot into recovery and do a factory wipe?
3) Move the OTA update file back from SD card to /cache.
4) Unroot (no idea how to safely do this)
5) Install OTA update.
6) Re-root (does the method change with MF9? If so, what do I need to do?)
7) Flash Rom via recovery (which installs as part of the rooting process, right?)
8) If necessary, install any SU apps not otherwise baked into my newly selected rom.
Is that about right? And can you clarify the specific execution of some of the above steps, as inquired about parenthetically?
I appreciate your help in advance (though I certainly understand, given that I am asking a bunch of questions, thus requiring a fairly substantial reply) if you don't wind up answering.

ok first of all i have a t mobile s4, i got a used s4 for my girl but she has sprint how do i deleted the info from the other person in the setting/more/about devise/ status/user name and phone number ,i rooted format all ,data cache ,dalvik put 3 different roms ,and it keeps showing the other person info and number is there other thing im missing?

walliester said:
ok first of all i have a t mobile s4, i got a used s4 for my girl but she has sprint how do i deleted the info from the other person in the setting/more/about devise/ status/user name and phone number ,i rooted format all ,data cache ,dalvik put 3 different roms ,and it keeps showing the other person info and number is there other thing im missing?
Click to expand...
Click to collapse
Sounds like the phone was never activated in your girls name and it is still under the previous owners info. You can't wipe that away. You need to switch the user info by calling Sprint, sounds like you were scammed and you are going to have a phone with a bad ESN that cannot be used. Good luck.
Sent from my Sprint Galaxy S4 using Tapatalk 2
---------- Post added at 08:33 PM ---------- Previous post was at 08:32 PM ----------
GiantJay said:
Sounds like the phone was never activated in your girls name and it is still under the previous owners info. You can't wipe that away. You need to switch the user info by calling Sprint or getting a hold of the previous owner to deactivate it in their name. Sounds like you were scammed and you are going to have a phone with a bad ESN that cannot be used. Good luck.
Sent from my Sprint Galaxy S4 using Tapatalk 2
Click to expand...
Click to collapse
Sent from my Sprint Galaxy S4 using Tapatalk 2

beerindex said:
Alright, here goes:
I am rooted (TWRP Recovery which I boot to through Goo Manager), SuperSU, Rom Toolbox, Adblock Plus, Hotspot Mod.
I achieved root via CF-Autoroot a while back, pre-MF9 update. As such, I am still running on MDL.
Now, let's assume I wanted to update to MF9 and then install an MF9-based ROM.
I'm a bit confused as to the steps. I think they go something like:
1) Uninstall any Root only apps (or move them somewhere? freeze? something else?)(And I can't very well remove SuperSu or TWRP Recovery can I?)
2) Boot into recovery and do a factory wipe?
3) Move the OTA update file back from SD card to /cache.
4) Unroot (no idea how to safely do this)
5) Install OTA update.
6) Re-root (does the method change with MF9? If so, what do I need to do?)
7) Flash Rom via recovery (which installs as part of the rooting process, right?)
8) If necessary, install any SU apps not otherwise baked into my newly selected rom.
Is that about right? And can you clarify the specific execution of some of the above steps, as inquired about parenthetically?
I appreciate your help in advance (though I certainly understand, given that I am asking a bunch of questions, thus requiring a fairly substantial reply) if you don't wind up answering.
Click to expand...
Click to collapse
For 1&4:
Also, you can remove root access if you would like too! In superSU, there is an option to unroot the phone in the settings area. As for recovery, I would NOT remove TWRP if I were you. If anything were to happen to your phone, you could use TWRP to restore it. Speaking of that, MAKE SURE you back up your data! Must people recommend nandroid, but I find TWRP back up to be just as good.
For 2:
TWRP gives you an option to wipe your data. When you but recovery, just go into wipe. A screen will pop up and will ask you to slide the slider to confirm the back up. You will lose your data, but it will get any updating/ROM issues resolved.
For 5&6:
I would recommend reading this! http://forum.xda-developers.com/showthread.php?t=2277480
For 7:
You don't need to flash any ROM if you're running on stock (stock means you're running the ROM that came with the device)
For 8:
Make sure you double check with the compatibility of everything you install! Some things are not ready for mf9, so be cautious!
Just hit the thanks if I helped at all!
Sent from my SPH-L720

beerindex said:
Alright, here goes:
I am rooted (TWRP Recovery which I boot to through Goo Manager), SuperSU, Rom Toolbox, Adblock Plus, Hotspot Mod.
I achieved root via CF-Autoroot a while back, pre-MF9 update. As such, I am still running on MDL.
Now, let's assume I wanted to update to MF9 and then install an MF9-based ROM.
I'm a bit confused as to the steps. I think they go something like:
1) Uninstall any Root only apps (or move them somewhere? freeze? something else?)(And I can't very well remove SuperSu or TWRP Recovery can I?)
2) Boot into recovery and do a factory wipe?
3) Move the OTA update file back from SD card to /cache.
4) Unroot (no idea how to safely do this)
5) Install OTA update.
6) Re-root (does the method change with MF9? If so, what do I need to do?)
7) Flash Rom via recovery (which installs as part of the rooting process, right?)
8) If necessary, install any SU apps not otherwise baked into my newly selected rom.
Is that about right? And can you clarify the specific execution of some of the above steps, as inquired about parenthetically?
I appreciate your help in advance (though I certainly understand, given that I am asking a bunch of questions, thus requiring a fairly substantial reply) if you don't wind up answering.
Click to expand...
Click to collapse
You don't have to Unroot to update to MF9. Follow this: http://forum.xda-developers.com/showthread.php?t=2357471
Its a little complicated but you will learn a ton and everything after will be easy

With ROMs like blue Kuban that have a hacked hotspot, do you have to install a third party hotspot app or can you just use the toggle they provide to turn on hotspot without being charged from Sprint?

FlyHighCrue said:
With ROMs like blue Kuban that have a hacked hotspot, do you have to install a third party hotspot app or can you just use the toggle they provide to turn on hotspot without being charged from Sprint?
Click to expand...
Click to collapse
Not sure about Blue Kuban but, the normal hack doesn't require a 3rd party app.
You do want to be careful about not over doing it on your data plan.

Salil999 said:
I have a question too, actually.
Flashing to a new kernel is the same way as flashing a ROM, right? I heard that you need to fix permissions, but some say you shouldn't...
So after flashing to a new kernel, is fixing permissions required?
Click to expand...
Click to collapse
Fixing permissions never hurts anything...

ObrienDave said:
Not sure about Blue Kuban but, the normal hack doesn't require a 3rd party app.
You do want to be careful about not over doing it on your data plan.
Click to expand...
Click to collapse
Well I have unlimited data I just don't have a plan for hotspot.

About disabling "Secure Boot" (S-ON) on the N5X.

Secure Boot (aka S-ON, aka other names) is the responsible for checking and validating the entire chain of trust from the psychical bootloader (BootRom) to the Android Bootloader (aboot). From there on, validating boot.img (kernels) and recoveries are checked via the lock/unlock state of the device, and validating system is duty of the Verified Boot (dm-verity) feature on the kernel.
Unlike the old days with the Nexus One and its S-OFF achievement (for reformatting the nand and others), I haven't seen any S-OFF or bootloader/radio development on any Nexus device from that point. Has been any exception for the N5X for some rare chance?
I know that disabling Secure Boot wouldn't be much useful considering there doesn't seem to be any radio or bootloader development at all, but the truth is that without the chance to flash and test it no development can appear from the nothing either. I honestly do not have any idea if by chance secure boot was disabled, anyone will jump into developing a better radio or more feature rich bootloader..
Just wondering, has this been ever attempted or anything? It seems that any HTC is attacked in this sense, but others aren't, even if Nexus are considered development freely, the truth is that they're all S-ON by default and no development of a radio or a bootloader seems to be in place ever. If It was able to happen with the Nexus One, why not for latter nexus devices?
And I don't agree to the point of "we don't need Secure Boot disabled because we would be able to really brick our Nexuses!!", because you can still brick any nexus by flashing any (signed) bootloader or radio from another device, for example N5 bootloader into a N5X (and a ton of more examples with other signed images, and let's not talk about inside android with root.. literally the first Nexus 5/5X were bricked by kernel auto uploaders because they had hardcoded the partition for the kernel, and it happened to be the bootloader one on the new device..). The S-ON check is only to guarantee you don't flash unauthorized stuff from the point of view of Google, not for your security of not bricking the device at all.

Agree
Sent from my Pixel using Tapatalk

there is really no point here because we can actually flash anything without any problem...
on htc devices (I had last 5 year's flagships, so I know something about it) you need it to flash unsigned factory images, zips with firmware files, change your phone's id and in some cases (htc one x) even flash a kernel from recovery! yes, you had to flash manually boot.img every time you change kernel/rom
but here...really....no need, unless some really crazy guy wants to make a bootloader from scratch and load something like windows phone

throcker said:
there is really no point here because we can actually flash anything without any problem...
on htc devices (I had last 5 year's flagships, so I know something about it) you need it to flash unsigned factory images, zips with firmware files, change your phone's id and in some cases (htc one x) even flash a kernel from recovery! yes, you had to flash manually boot.img every time you change kernel/rom
but here...really....no need, unless some really crazy guy wants to make a bootloader from scratch and load something like windows phone
Click to expand...
Click to collapse
I agree on that we don't "need" it for basic rom flashing stuff, but your last line defines why it would be awesome to have it. It would give out options not only to "boot Windows", but also add features to the bootloader, repartition as we please (reduce system partition after debloating), adding a mechanism to prevent any bricking by adding a safe first bootloader sequence (like it was done for the N7 2012, via nv flashing if I don't remember bad), stuff like removing the damn bootloader unlock orange or other warnings (not only changing the images but also deleting the damn timeouts at boot), being able to add passwords for bootloaders, and a ton more **** could be done.
And let's not talk about "Radios". That garbage partition is a GIANT security hole and for the worse it boots BEFORE the main cpu and controls everything, from the application cpu to the memory it's using. Literally the radio controls the phone, it's the most important partition, it's FULL of backdoors (like the Replicant guys demonstrated for the Nexus S/Galaxy S2), it's FULL of unintended security holes (because no one develops for it decently, there have been some hacking conferences having fun at them) and it's the worst we all having running on the phone right now. It doesn't matter your Android Version or security patch date, you have security holes that date from years ago opened and being probably exploited by goverments as we speak.
There are great devs around, the bootloaders are usually decompiled to find exploits to be unlocked, for S-OFF and a lot of stuff. I'm sure people could jump on radio cleaning and fixing. There is a great community and great potential unused.
Until we fix the radio and the BL, "our" N5X is not our phone. Secure Boot should be killed and development would take place.

Really interesting ! Thanks

Aww, no one is interested in this .
Sometimes I wish that the Nexus weren't so unlocked and that we would need S-OFF to even flash custom roms, so a lot more development would appear, like it did for the Nexus One.

Well, I really dont see such a point of locking down the choice. If I buy something, then its mine. So what I do with mine should really be mine choice, dispite warranty. If I break it, its still mine.
Sent from my Pixel using Tapatalk

jugoslavpetrovic said:
Well, I really dont see such a point of locking down the choice. If I buy something, then its mine. So what I do with mine should really be mine choice, dispite warranty. If I break it, its still mine.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yes, this is the point, but we are accepting nowdays devices that are full-locked except some partitions for us to play with. All is good while the bootloader is completely locked on and the radio is even more untouchable, literally making everyone able to spy on us.
The funniest part is that only "we", the users, are locked. Because I am expecting malware to grow up to the point that it will be able to get root, then unlock, then turn secure boot OFF, and then overwrite the bootloader and radio in a ransomware form blocking the boot of the device until payment is done or something like that.

RusherDude said:
Yes, this is the point, but we are accepting nowdays devices that are full-locked except some partitions for us to play with. All is good while the bootloader is completely locked on and the radio is even more untouchable, literally making everyone able to spy on us.
The funniest part is that only "we", the users, are locked. Because I am expecting malware to grow up to the point that it will be able to get root, then unlock, then turn secure boot OFF, and then overwrite the bootloader and radio in a ransomware form blocking the boot of the device until payment is done or something like that.
Click to expand...
Click to collapse
Exactly. Scary. That reminded me of a movie I have seen recently called Zero Day.
Sent from my Pixel using Tapatalk

jugoslavpetrovic said:
Exactly. Scary. That reminded me of a movie I have seen recently called Zero Day.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I wonder if it's as easy as flipping some bits like for unlocking bootloader..
@segv11 @osm0sis , hey guys! you both worked for BootUnlocker, so you may know something about this : do you know if a value is stored in memory to control "Secure Boot enabled" or "Secure boot disabled" like for bootloader locked or unlocked? Have you ever found this or something related by accident? Thanks!

RusherDude said:
I wonder if it's as easy as flipping some bits like for unlocking bootloader..
@segv11 @osm0sis , hey guys! you both worked for BootUnlocker, so you may know something about this : do you know if a value is stored in memory to control "Secure Boot enabled" or "Secure boot disabled" like for bootloader locked or unlocked? Have you ever found this or something related by accident? Thanks!
Click to expand...
Click to collapse
Don't think so.. that's all secure bootchain stuff.. some is open source and some is not.
Google the following: lk bootloader
That's what the LG devices use if I recall correctly. Checking out some of the public source will be your best bet of finding if it even possibly can be disabled.

osm0sis said:
Don't think so.. that's all secure bootchain stuff.. some is open source and some is not.
Google the following: lk bootloader
That's what the LG devices use if I recall correctly. Checking out some of the public source will be your best bet of finding if it even possibly can be disabled.
Click to expand...
Click to collapse
Thanks a lot for the input! I think it can be disabled because apparently some N5 users made it, and considering that the N5 is the N5X's brother from LG, it should be doable too:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The image is from http://bbs.gfan.com/android-7753460-1-1.html , apparently a chinese site about a tool? for disabling secure boot? no idea honestly
So it probably is doable on N5X too, the question is how . If its a bit flip for unlock, it is probably just another value for secure boot, I wonder if adjacent to the unlock one or something like that. I'll search for lk bootloader stuff but I have not the bootloaders knowledge (or tools like IDA2 pro to get it done anyway, which sucks ) for making it anyway
Thanks a lot!

I definitely think it can be disabled and I found some rather interesting things by reading up on a site, where someone has actually spent time reverse engineering what's most likely a signed and compiled version of ABoot (LK Bootloader). I thought it was interesting as it covers the actual process of disassembling the image, which may expose the values that need to be changed to actually achieve a true state of disabled secureboot.
http://newandroidbook.com/Articles/aboot.html
What worries me however, is if the signature is checked upon flashing, as if that's the case then replacing the bootloader may in fact be next to impossible. I'm not all that interested to try it out either, as I simply don't want to risk ending up with a hardbricked phone as that wouldn't be all that great so to say. However, if someone is successful making a patch that really works and release it, I'll definitely give it a go after it has been comfirmed to work.

Doenms't the PixelROM flash a custom bootloader?
So what's the "fastboot unlock bootloader" command for?

LazerL0rd said:
Doenms't the PixelROM flash a custom bootloader?
So what's the "fastboot unlock bootloader" command for?
Click to expand...
Click to collapse
No it doesn't.
Unlocking the bootloader is the ability to ask the bootloader it self to boot a different/custom rom.

scr60 said:
No it doesn't.
Unlocking the bootloader is the ability to ask the bootloader it self to boot a different/custom rom.
Click to expand...
Click to collapse
Well, actually it does. It's using the Google Pixel Bootloader. Check is files. It's a custom bootloader.

LazerL0rd said:
Well, actually it does. It's using the Google Pixel Bootloader. Check is files. It's a custom bootloader.
Click to expand...
Click to collapse
It's not a custom bootloader, it only changes the imagdata, the graphical aspect of it that you see when the phone boots. Iit's far from being a custom bootloader

Gr0vk said:
It's not a custom bootloader, it only changes the imagdata, the graphical aspect of it that you see when the phone boots. Iit's far from being a custom bootloader
Click to expand...
Click to collapse
Okay. Thank you for correcting me there!

LazerL0rd said:
Okay. Thank you for correcting me there!
Click to expand...
Click to collapse
Should exist more people like you on the internet

I haven't been able to find a way. Probably have to burn your own bootloader onto the emmc board.

free XZP Pie rooting on Mac, is it possible without CS degree?

At the risk of being barked at by the spirited young hackers on this forum:
After days of searching the interwebs, I am close to resetting to factory settings and returning this thing, even though I really like the phone itself.
Admittedly, I'm a total Android virgin and know only what many hours of googl'ing have left behind (it's all a blur, at this point), but after all of my attempts to use the common rooting suspects (KingoRoot, King Root, iRoot, etc.), I sit here more confused than I can handle.
First attempts at figuring out adb and fastboot made me realise I am in way over my head.
Anyone know of a way to root my XZP running Pie, from my Mac, for free (if at all possible), without first having to get a degree in computer science. I can stumble my way around Terminal, if given clear instructions, but that's where it ends.
hope someone can help.
I really want to get the EU firmware flashed onto this thing, with the modem working as designed for the US market, and hopefully use this thing as a router and many other things that require root access.
But I also read the thread about people like me, who don't know much about Android, ruining their bootloaders and then coming here for help/support...so the question for me arises is: reset to factory settings and return it, before I get myself into quicksand territory, or do whatever it takes to figure it out (with the help of the esteemed community).
It's just such a nice phone, and I miss the iOS jailbreaking days so much, that this would be the perfect antidote.
Anyone care to help?

About the reason, that you are post in this forum thread, I guess you've make your choice of phone. Isn't ir?
In this case, there is a very good manual how to save your TA partition, root the phone and so on...
If you are unsure, which phone you will buy...... Make first of all your choices... Look in xda if the device is supported and following the thread

mad0701 said:
About the reason, that you are post in this forum thread, I guess you've make your choice of phone. Isn't ir?
In this case, there is a very good manual how to save your TA partition, root the phone and so on...
If you are unsure, which phone you will buy...... Make first of all your choices... Look in xda if the device is supported and following the thread
Click to expand...
Click to collapse
thanks for that first heads-up, mad0701.
yeah, I am set on the XZP, as my first Android phone. It serves my primary purpose of being a little presentation device for my 4K video and photography work perfectly, I already enjoy it as a very good Hi-Res music player, it will hopefully serve me as a little portable router/VPN, etc. once I figure out how to root it, and it was a great deal, for a used one, for so much power. But I also want to be able to use its fingerprint sensor, here in the USA, and for that...
So when you say that "a very good manual" is out there, would you be so kind as to share a link? I tried to follow so many methods, at this point, that I am at the end of my wits.

Check this thread... There is a manual available... Step by step... Only give attention, that you flash the TWRP version for your device...
https://r.tapatalk.com/shareLink?ur...share_tid=3795510&share_fid=3793&share_type=t
[XZ1c/XZ1/XZp] temp root exploit to backup drm keys implemented

mad0701 said:
Check this thread... There is a manual available... Step by step... Only give attention, that you flash the TWRP version for your device...
[XZ1c/XZ1/XZp] temp root exploit to backup drm keys implemented
Click to expand...
Click to collapse
thanks again, mad0701...I was out riding all day and just skimmed over that link...first reaction: this is more advanced than I feel confident tackling...I fear that a one wrong action on my part might leave me in a situation where I can't even get the phone back to factory settings, and won't be able to return it anymore (for which I have one week left).
I'll read through the manual in more detail, maybe tomorrow, and if it seems that I can actually do all that, successfully, then maybe I will give it a try. But since I don't even know what the TA is, or the TWRP version, it may be something I may not wanna get into at this time...only so many hours in the day.
but thanks for showing me the manual!

tillkrueger said:
but thanks for showing me the manual!
Click to expand...
Click to collapse
mad0701 said:
[XZ1c/XZ1/XZp] temp root exploit to backup drm keys implemented
Click to expand...
Click to collapse
Lots of people keep pointing at this thread without actually reading it. There still isn't a way to relock your bootloader with your saved TA partition. Yes you can save your individualy encrypted key, but then what?
You still need to unlock your phone to get permanent root, with no way of putting the key back in place, so you still need a 'fixed' kernel
If you want an easy way to root your phone, as you admit yourself your android experience is limited., then I would recomend Xperifix
@sToRm// wrote a one stop shop program that did everything, but then took his work to a private website as he wanted to charge for all the hours that he put into it.
The original thread is here, this would tell you what to do and the drivers you need to install (important). Then the go to the Xperiafix website and pay your $20.
I used it to root my XZ1 compact and it really was as easy as plug it in and follow instructions.
The only probelm with this is that there still isn't a root available for Pie firmware, so his fix is based on Oreo builds.
Lots of people speak badly of Xperiafix 'why pay for a fix when you can get it for free?'
Yea, but free is complicated and I'm happy to pay for easy.
Edit: To answer your original question, I'm not sure there is a Pie root kenel for a stock rom available yet, I know @janjan posted a Pie kernel on the XZ1compact thread, so it's just a matter of time before he updates the XZ premium
You could go with a custom rom to get rooted Pie, read the instructions and decide if you're up for it.

Didgesteve said:
Lots of people keep pointing at this thread without actually reading it. There still isn't a way to relock your bootloader with your saved TA partition. Yes you can save your individualy encrypted key, but then what?
You still need to unlock your phone to get permanent root, with no way of putting the key back in place, so you still need a 'fixed' kernel
If you want an easy way to root your phone, as you admit yourself your android experience is limited., then I would recomend Xperifix
@sToRm// wrote a one stop shop program that did everything, but then took his work to a private website as he wanted to charge for all the hours that he put into it.
The original thread is here, this would tell you what to do and the drivers you need to install (important). Then the go to the Xperiafix website and pay your $20.
I used it to root my XZ1 compact and it really was as easy as plug it in and follow instructions.
The only probelm with this is that there still isn't a root available for Pie firmware, so his fix is based on Oreo builds.
Lots of people speak badly of Xperiafix 'why pay for a fix when you can get it for free?'
Yea, but free is complicated and I'm happy to pay for easy.
Edit: To answer your original question, I'm not sure there is a Pie root kenel available yet, I know @janjan posted a Pie kernel on the XZ1compact thread, so it's just a matter of time before he updates the XZ premium
Click to expand...
Click to collapse
Theres no need for a kernel for pie, flash pie, flash twrp flash magisk. That's it.

Beetle84 said:
Theres no need for a kernel for pie, flash pie, flash twrp flash magisk. That's it.
Click to expand...
Click to collapse
I just realised that Xperiafix is a windows program anyway Doh

Didgesteve said:
I just realised that Xperiafix is a windows program anyway Doh
Click to expand...
Click to collapse
I totally missed the Mac part....

Alright, u need adb and fastboot for mac.
If you will find newer instructions use it, here is the first thing I found.
Unlock ur device here using fastboot, it clearly written there how to do it.
Find latest twrp recovery in this forum.
Use fastboot again.
"fastboot flash recovery your.recovery.img"
Then, using this recovery u need to flash latest magisc.
I've gave u enough information, with minimum efforts u will be able to find everything u need to do it. Plus u will learn something useful.
Goodluck

tillkrueger said:
thanks again, mad0701...I was out riding all day and just skimmed over that link...first reaction: this is more advanced than I feel confident tackling...I fear that a one wrong action on my part might leave me in a situation where I can't even get the phone back to factory settings, and won't be able to return it anymore (for which I have one week left).
I'll read through the manual in more detail, maybe tomorrow, and if it seems that I can actually do all that, successfully, then maybe I will give it a try. But since I don't even know what the TA is, or the TWRP version, it may be something I may not wanna get into at this time...only so many hours in the day.
but thanks for showing me the manual!
Click to expand...
Click to collapse
the manual looking complicated but it only took 2 hours for me, and if u backup and restore your TA partition, u dont need any drm fix for all firmwares, and dont pay for any useless programs like xperifix(the guy on upper comments always advertise this useless windows program)
for rooting, its very easy on pie

I really appreciate all of y'all's input...but, to be honest, I understand too little of it, at the moment, to feel inclined to dive into executing some of those instructions.
I mean, it looks like I was given enough info to have a chance to root and flash my XZP successfully, but I may just hold off for a bit, maybe return this one and wait until I can either score an XZP that's already been rooted and flashed with the mixed EU/US firmware, or wait until I can afford to get a newer device, which has all of the features I am looking for already working: 4K screen, fingerprint sensor, and preferably being a Sony...if such a device exists now.
But truly, thank you all, for now!

Can I root using Magisk Delta?

Can I root my phone (SM-G930V) using Magisk Delta? I'm asking because I don't want to brick my phone.

ego-lay-atman-bay said:
Can I root my phone (SM-G930V) using Magisk Delta? I'm asking because I don't want to brick my phone.
Click to expand...
Click to collapse
What makes you think Magisk would brick your device?

Because of this post
Magisk on SM-G930V?
Is it at all possible to root using Magisk on a US variant Galaxy S7? I have found no support for SM-G930V and need something that can hide root from apps like Snapchat.
forum.xda-developers.com

ego-lay-atman-bay said:
Because of this post
Magisk on SM-G930V?
Is it at all possible to root using Magisk on a US variant Galaxy S7? I have found no support for SM-G930V and need something that can hide root from apps like Snapchat.
forum.xda-developers.com
Click to expand...
Click to collapse
What does that have to do with bricking? That post is 5 years ago.
Looks to me like they're talking about bootloader unlock - it is true that most US market Samsung Qualcomm devices are not bootloader unlockable.
If however you have unlocked yours, you can just use Magisk Stable.

V0latyle said:
What does that have to do with bricking? That post is 5 years ago.
Looks to me like they're talking about bootloader unlock - it is true that most US market Samsung Qualcomm devices are not bootloader unlockable.
If however you have unlocked yours, you can just use Magisk Stable.
Click to expand...
Click to collapse
Then I guess I'll try to root my phone.

ego-lay-atman-bay said:
Then I guess I'll try to root my phone.
Click to expand...
Click to collapse
Do you need help with that?

V0latyle said:
Do you need help with that?
Click to expand...
Click to collapse
It would be great if you could give me a guide. I am in an android root discord server, so I can also ask there.
I do have one question, how do I tell if my bootloader is unlocked?

ego-lay-atman-bay said:
It would be great if you could give me a guide. I am in an android root discord server, so I can also ask there.
I do have one question, how do I tell if my bootloader is unlocked?
Click to expand...
Click to collapse
There's two ways.
One, enable Developer Options, look for the OEM Unlock toggle. If your bootloader is unlocked, the toggle should be grayed out with the message "Bootloader is already unlocked"
Two, go into download mode and look for OEM LOCK. If this is OFF, bootloader is unlocked.
As for rooting your device, it depends on how you want to do it. If you want to use Magisk with the stock firmware, you can either patch the AP.tar in Magisk then flash using Odin, or you can install TWRP (if available for your device) and flash Magisk there. If on the other hand you intend to run a custom ROM or a GSI, you'll have to see whether the ROM already has root built in.

V0latyle said:
There's two ways.
One, enable Developer Options, look for the OEM Unlock toggle. If your bootloader is unlocked, the toggle should be grayed out with the message "Bootloader is already unlocked"
Two, go into download mode and look for OEM LOCK. If this is OFF, bootloader is unlocked.
As for rooting your device, it depends on how you want to do it. If you want to use Magisk with the stock firmware, you can either patch the AP.tar in Magisk then flash using Odin, or you can install TWRP (if available for your device) and flash Magisk there. If on the other hand you intend to run a custom ROM or a GSI, you'll have to see whether the ROM already has root built in.
Click to expand...
Click to collapse
The OEM toggle is on, but it's not greyed out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ego-lay-atman-bay said:
The OEM toggle is on, but it's not greyed out.
View attachment 5794949
Click to expand...
Click to collapse
Okay. Reboot into download mode and see what OEM LOCK says. If it says ON, you need to unlock the bootloader:
Unplug any USB cable from the device and power it off
Wait at least 30 seconds
Hold both Volume buttons (do not press Power) and plug in the USB cable from your PC.
Device should immediately start into download mode. Release both volume buttons. If you did this step correctly you should see a prompt: Volume Up to continue, long press Volume Up to unlock, Volume Down to reboot.
Hold Volume Up until the device unlock prompt appears, and follow the instructions. This unlocks your bootloader, which will wipe your device.

V0latyle said:
Okay. Reboot into download mode and see what OEM LOCK says. If it says ON, you need to unlock the bootloader:
Unplug any USB cable from the device and power it off
Wait at least 30 seconds
Hold both Volume buttons (do not press Power) and plug in the USB cable from your PC.
Device should immediately start into download mode. Release both volume buttons. If you did this step correctly you should see a prompt: Volume Up to continue, long press Volume Up to unlock, Volume Down to reboot.
Hold Volume Up until the device unlock prompt appears, and follow the instructions. This unlocks your bootloader, which will wipe your device.
Click to expand...
Click to collapse
whenever I do that, I just get to the charging screen. I did also find this article https://nerdschalk.com/unlock-bootloader-via-fastboot-android/

ego-lay-atman-bay said:
whenever I do that, I just get to the charging screen. I did also find this article https://nerdschalk.com/unlock-bootloader-via-fastboot-android/
Click to expand...
Click to collapse
Samsung doesn't have a fastboot mode. If you're getting the charging screen, you're doing something wrong - either you're leaving the USB cable plugged in, or you aren't holding both Volume buttons while plugging it in

V0latyle said:
Samsung doesn't have a fastboot mode. If you're getting the charging screen, you're doing something wrong - either you're leaving the USB cable plugged in, or you aren't holding both Volume buttons while plugging it in
Click to expand...
Click to collapse
I'm doing exactly what you said to do. I'm holding both volume buttons while plugged in.
I've also been doing a bit of research, and from what I've seen, you don't need to unlock the bootloader in order to root. Is that true?
People also tell me that I can't unlock the bootloader.

ego-lay-atman-bay said:
I'm doing exactly what you said to do. I'm holding both volume buttons while plugged in.
Click to expand...
Click to collapse
You have to start with the phone unplugged and powered completely off. Hold both Volume buttons THEN plug the USB cable in, and do not press Power.
ego-lay-atman-bay said:
I've also been doing a bit of research, and from what I've seen, you don't need to unlock the bootloader in order to root. Is that true?
Click to expand...
Click to collapse
Completely false. A locked bootloader will reject any custom images, meaning you cannot make any modifications to /system or anything else. Root is either system-as-root (where the su binary lives in /system) or systemless root (where the su binary is patched into ramdisk)
ego-lay-atman-bay said:
People also tell me that I can't unlock the bootloader.
Click to expand...
Click to collapse
It's possible - the G930V is the Verizon Galaxy S7, yes? US market Samsung Snapdragon devices are generally not bootloader unlockable, although if that's the case, the OEM Unlock toggle should be invisible.

V0latyle said:
You have to start with the phone unplugged and powered completely off. Hold both Volume buttons THEN plug the USB cable in, and do not press Power.
Click to expand...
Click to collapse
That's exactly what I'm doing
V0latyle said:
Completely false. A locked bootloader will reject any custom images, meaning you cannot make any modifications to /system or anything else. Root is either system-as-root (where the su binary lives in /system) or systemless root (where the su binary is patched into ramdisk)
Click to expand...
Click to collapse
Thanks for the clarification
V0latyle said:
It's possible - the G930V is the Verizon Galaxy S7, yes? US market Samsung Snapdragon devices are generally not bootloader unlockable, although if that's the case, the OEM Unlock toggle should be invisible.
Click to expand...
Click to collapse
well, it's visible, so I'm guessing I can unlock it. I did find this video
, so I'm gonna try and see if that works.
edit: maybe I won't, since I can't find a twrp image for my device
And just to clarify, I have made a backup of all my data on my phone before all this.

Well, best of luck!
By the way, I completely missed this when you first posted: Questions should go in the Questions and Answers section. Development sections are for development projects ONLY, per the Forum Rules:
15. Keep threads / posts on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.
General Forums - For news and announcements relating to your device.
Q&A Help & Troubleshooting Forums - For all question / request threads and posts. If there is no Q&A Help & Troubleshooting forum, use the General Forum of the relevant device
Accessories Forum - For posts related to accessories relevant to the device
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Themes and Apps Forums - For the posting of Themes and / or Apps as well as announcements & discussions including modifications made to Themes and Apps.
Click to expand...
Click to collapse
As a courtesy I have moved this thread to the correct section.

V0latyle said:
Well, best of luck!
By the way, I completely missed this when you first posted: Questions should go in the Questions and Answers section. Development sections are for development projects ONLY, per the Forum Rules:
As a courtesy I have moved this thread to the correct section.
Click to expand...
Click to collapse
I thought I put it in questions and answers... I must've misclicked.
Also, I've decided I'm gonna follow this https://forum.xda-developers.com/t/...method-rev11-b-_using-combo_firmware.3819616/
I guess I won't be using magisk.

ego-lay-atman-bay said:
I thought I put it in questions and answers... I must've misclicked.
Also, I've decided I'm gonna follow this https://forum.xda-developers.com/t/...method-rev11-b-_using-combo_firmware.3819616/
I guess I won't be using magisk.
Click to expand...
Click to collapse
I believe if you flash that engineering boot image, it may allow you to unlock the bootloader, or at least flash TWRP, and from there Bob is indeed your uncle.

V0latyle said:
I believe if you flash that engineering boot image, it may allow you to unlock the bootloader, or at least flash TWRP, and from there Bob is indeed your uncle.
Click to expand...
Click to collapse
well, with some research from my dad, we've discovered that it has been patched on my device. I can't root it. Man I wish I could downgrade.

ego-lay-atman-bay said:
well, with some research from my dad, we've discovered that it has been patched on my device. I can't root it. Man I wish I could downgrade.
Click to expand...
Click to collapse
That's unfortunate.
That's also why I left Samsung behind a long time ago and went Pixel. I've never looked back.