So, I periodically try different Root methods on this sm-n900v and tonight I tried Kingo Root (PC), and one time when it rebooted it showed the custom unlocked icon. Is this normal? I figure I'm going to try and repeat what I did until it shows that to me again...
Feedback is always appreciated!
When you say custom unlocked icon do you mean when the Galaxy screen comes on? I see that, but I used Towelroot instead of Kingo
I'm on 5.0 OB6.
Interesting. I don't think it's supposed to work like that
AlexanderJohn said:
I'm on 5.0 OB6.
Click to expand...
Click to collapse
You can try forever...but so far...there is NO way to root OB6
Sent from my Note 3 via Tapatalk
I know, but the custom unlock screen came up and I'm curious as to why. Sorry I didn't clarify that.
Sent from my SM-N900V using Tapatalk
AlexanderJohn said:
I know, but the custom unlock screen came up and I'm curious as to why. Sorry I didn't clarify that.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
All that means is you attempted to load a non standard system.....it obviously didn't mean it worked. It's your time, your effort, your phone...have at it.
But people who know a whole lot more about rooting and the issues involved than you or I have been trying for quite a while and have come up empty handed.
Sent from my Note 3 via Tapatalk
Useful and helpful
donc113 said:
All that means is you attempted to load a non standard system.....
Click to expand...
Click to collapse
neither useful or helpful
donc113 said:
it obviously didn't mean it worked. It's your time, your effort, your phone...have at it.
But people who know a whole lot more about rooting and the issues involved than you or I have been trying for quite a while and have come up empty handed.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Sent from my HTC6435LVW using Tapatalk
hey guys, i dont know much about root script but i got an idea. Cant we somehow brick out bootloiader partition so we can flash the old firmware and than root? tell me what you think.
kstoianov said:
hey guys, i dont know much about root script but i got an idea. Cant we somehow brick out bootloiader partition so we can flash the old firmware and than root? tell me what you think.
Click to expand...
Click to collapse
I've actually thought this same thing, maybe wipe the phone out 100% so it would be as if nothing was there then find a write program to put the older bootloader on their or maybe in that case could get into the bootloader and unlock it and flash the phone as new...hmm, I've had that thought many time but I think it would just completely mess the phone up beyond Bootable or working
Sent from my SM-N900V using Tapatalk
thunderblaster88 said:
I've actually thought this same thing, maybe wipe the phone out 100% so it would be as if nothing was there then find a write program to put the older bootloader on their or maybe in that case could get into the bootloader and unlock it and flash the phone as new...hmm, I've had that thought many time but I think it would just completely mess the phone up beyond Bootable or working
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I am ready to try but i need tool to wipe my aboot.img and a software to flash via qualcomm mode and old aboot.img
I'd be willing to do this stuff to if we can find the right tools
The thing about doing a full 100% wipe to reload say the inital factory firmware is what is called a jtag is needed it is a serial connection to the flash chips that is used in the factory to do the inital programming. The problem is this connection is cut off or more often not made accessible to assembled units.
there was with previous samsung phones a usb jtag kicking dongle that could kick a hard bricked phone into a sorta download mode.
this is not present on the note 3 and the note 3 has e fuses that permanently blow preventing some of these things. Additionally there is a built in check to prevent the loading of bootloaders that are unsigned or older than the current bootloader.
so in the end the only thing messing with wiping the boot loader is going to acomplish is hard or soft bricks...
it could be off topic but how they sign their updates? cant we fool the factory recovery?
mirrin said:
The thing about doing a full 100% wipe to reload say the inital factory firmware is what is called a jtag is needed it is a serial connection to the flash chips that is used in the factory to do the inital programming. The problem is this connection is cut off or more often not made accessible to assembled units.
there was with previous samsung phones a usb jtag kicking dongle that could kick a hard bricked phone into a sorta download mode.
this is not present on the note 3 and the note 3 has e fuses that permanently blow preventing some of these things. Additionally there is a built in check to prevent the loading of bootloaders that are unsigned or older than the current bootloader.
so in the end the only thing messing with wiping the boot loader is going to acomplish is hard or soft bricks...
Click to expand...
Click to collapse
That's kinda what I figured
kstoianov said:
it could be off topic but how they sign their updates? cant we fool the factory recovery?
Click to expand...
Click to collapse
Encrypted I know you guys are grasping as straws in desperate hope of the phone not being as locked down as previously thought. But if it were such a simple task of getting the dev device boot loader and fooling the system into thinking it is a legit update we would have an open phone.
the things with the nc2 and nc4 bootloaders was they for some reason did not use the check correctly and left it open for us.
Related
I admit it, I'm confused by the various different rooting threads at this point.
Which root method is the right one for the Sprint model?
Sent from my SPH-L720 using Tapatalk 2
I used this & it worked for me. Easy & quick: http://forum.xda-developers.com/showthread.php?t=2219803
I used the method mentioned above. Seemed to work perfectly. Very easy too.
Sent from my SPH-L720 using Tapatalk 2
Is the bootloader locked or unlocked on the Sprint version ?
Doesn't it have to be unlocked since they are reporting success rooting it?
mysongranhills said:
Doesn't it have to be unlocked since they are reporting success rooting it?
Click to expand...
Click to collapse
These threads are a bit confusing and i want to make sure before i decide to get one
No one really knows if the bootloader is locked or not. Some are able to obtain root, but when flashing certain things, bricked their s4. One dude tried flashing stock and bricked. So I wouldn't get too crazy yet until a dev or someone who knows what they're doing figures out exactly what's going on.
Wow thats crazy flashing something to your phone that isn't made for it.
opz187 said:
No one really knows if the bootloader is locked or not. Some are able to obtain root, but when flashing certain things, bricked their s4. One dude tried flashing stock and bricked. So I wouldn't get too crazy yet until a dev or someone who knows what they're doing figures out exactly what's going on.
Click to expand...
Click to collapse
We have a Stock (dump) build, which will be made available later today that flashes just fine.
If you're following the Engadget bootloader thread, i posted this earlier today..
http://forum.xda-developers.com/showpost.php?p=40844084&postcount=141
This method worked and was painless.
http://forum.xda-developers.com/showthread.php?t=2252248
With regards to the boot methods - we have found something interesting.
@crawrj Had used the Moto root method and couldn't use Solid Explorer properly (i.e. couldn't open init.rc to view, copy system files, etc)
He then used the CF autoroot method and functionality came back.
While not specific enough to point at anything (we don't have logs to look at) I would advise you to check your apps that need root to make sure they function properly.
Just FYI.
I used the AT&T root method and worked fine for me only took 20 seconds.
http://forum.xda-developers.com/showthread.php?t=2252248
Just follow the steps and you will be rooted.
Sent from my SPH-L720 using xda premium
---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------
Pheonix28 said:
This method worked and was painless.
http://forum.xda-developers.com/showthread.php?t=2252248
Click to expand...
Click to collapse
Sorry didn't see this post.
Sent from my SPH-L720 using xda premium
benny3 said:
Is the bootloader locked or unlocked on the Sprint version ?
Click to expand...
Click to collapse
The write protection is enabled in odin mode....don't know what that means as I haven't dived in yet :thumbup:
Sent from my SPH-L720 using Tapatalk 2
Shadow_God said:
The write protection is enabled in odin mode....don't know what that means as I haven't dived in yet :thumbup:
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
I have the HTC ONE and it has the Write Protection enabled also. We have a work around that can be flash through recovery, Not sure how you would implement it with Odin but here is the Link, Maybe you can look at it and may help
http://forum.xda-developers.com/showthread.php?t=2236849
JasonJoel said:
I admit it, I'm confused by the various different rooting threads at this point.
Which root method is the right one for the Sprint model?
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Motochopper, featured in you tube (http://www.youtube.com/watch?v=6fi1tYaoP0U) or (http://www.youtube.com/watch?v=GrvrXXFb2Uo) and be sure to Download the Drivers from the samsung website. For some reason, the drivers within XDA didn't work for me. Once I D/Ld the one specifically for Sprint, motochopper was able to communicate w/my s4 and rooted it:good:
I've not tried the motochopper stuff so I can't speak for that.
I can confirm that I had success the first time with no driver download needed when I used the CF auto-root method. I simply plugged the phone in, let Win7 download the drivers. I then put it in recovery mode (vol down, home and power button, release power button) and once win7 downloaded those (MHT etc) drivers I loaded the file through pda in odin and it went right through with no problems whatsoever.
The CF auto-root thread is here:
http://forum.xda-developers.com/showthread.php?p=39901375
I would suggest waiting until we figure out just what WRITE PROECTION: ENABLED means on the download screen.
Keep in mind that obtaining Root and bootloader lock status are two completely separate things. Typically, the bootloader being locked doesn't affect the ability to OBTAIN Root. But it will block certain partitions of the device being flashed, if it's indeed locked. And it can also affect the root from being permanent or not. (sticking after a reboot)
Root is an android system thing. An operating system thing. Bootloader is a low level boot thing, before android itself is even initialized. Think of it like the BIOS on a PC, it's the screen you see before you get to windows or linux or whatever operating system you're running.
It's sounding like they are having success with writing to many of the partitions that are ordinarily blocked by a locked bootloader. So it's sounding like the WRITE PROTECTION: ENABLED doesn't actually indicate whether or not the bootloader is locked. But we don't know that for sure yet. It's too early to tell.
Unknownforce said:
I would suggest waiting until we figure out just what WRITE PROECTION: ENABLED means on the download screen.
Keep in mind that obtaining Root and bootloader lock status are two completely separate things. Typically, the bootloader being locked doesn't affect the ability to OBTAIN Root. But it will block certain partitions of the device being flashed, if it's indeed locked. And it can also affect the root from being permanent or not. (sticking after a reboot)
Root is an android system thing. An operating system thing. Bootloader is a low level boot thing, before android itself is even initialized. Think of it like the BIOS on a PC, it's the screen you see before you get to windows or linux or whatever operating system you're running.
It's sounding like they are having success with writing to many of the partitions that are ordinarily blocked by a locked bootloader. So it's sounding like the WRITE PROTECTION: ENABLED doesn't actually indicate whether or not the bootloader is locked. But we don't know that for sure yet. It's too early to tell.
Click to expand...
Click to collapse
Our phone is not locked, at least not in the way we know it. We have flashed kernels, recovery and the system partition from Odin. CF Auto root is the best method of Root IMO. Although both rooting options install and stick. But as MoHoGalore stated I had trouble with an app that required root access using the Moto method. I switched to the CF method and everything was working perfectly. We have no idea what the Write Protection means yet but so far it has not inhibited us in any way.
If unknownforce tells me to wait, I wait. I trust his advice quite a bit, after seeing what he is capable of in the evo3d section.
Sent from my SPH-L900 using Tapatalk 2
k2buckley said:
If unknownforce tells me to wait, I wait. I trust his advice quite a bit, after seeing what he is capable of in the evo3d section.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
There is nothing wrong with staying with what you know.
Once we get a complete package, which may not be too far in the near future, we'll know more.
---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------
crawrj said:
Our phone is not locked, at least not in the way we know it. We have flashed kernels, recovery and the system partition from Odin. CF Auto root is the best method of Root IMO. Although both rooting options install and stick. But as MoHoGalore stated I had trouble with an app that required root access using the Moto method. I switched to the CF method and everything was working perfectly. We have no idea what the Write Protection means yet but so far it has not inhibited us in any way.
Click to expand...
Click to collapse
I can attest to this and I'm still functional.
But, for the masses, there are a few of us willing to try if you want to wait.
Here's hoping we know more very soon. :beer:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
I might be wrong here as im not the sharpest tool in the shed, but i do believe there is a new post like this every single day and all get the same response. There is no MF3 image available for flash through odin or otherwise. Search = Friend.
If you repeat three times "owaa tagoo siam" it might magically appear.
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
It seems useless
So did you try it or just say its useless? There are a couple other methods that have been shown to work as well.
Sent from my GT-I9505G using XDA Premium HD app
You are going to have to wait for Samsung to release the MF3 on kies or a leak of the tar to happen.
Sent from my GT-I9505G using Tapatalk 2
chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT
salwansk said:
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT
Click to expand...
Click to collapse
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.
scott14719 said:
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.
Click to expand...
Click to collapse
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ
salwansk said:
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ
Click to expand...
Click to collapse
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.
scott14719 said:
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.
Click to expand...
Click to collapse
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.
salwansk said:
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.
Click to expand...
Click to collapse
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.
scott14719 said:
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.
Click to expand...
Click to collapse
thanks bud, and yes i started read about this issue just today.
i know samsung is way easier than HTC when it comes to unlocking and flashing, thats why i didn't care at first. but what freaked me out when i tried to sim unlock galaxy s4 yesterday. today i found out about the MF3 and how is it pain in the axx :laugh: .... thanks for the info bro :good:
add myself to the thread for future fixes...
Scott that was probably the best explanation I have seen yet. You should have it pinned lol
Sent from my GT-I9505G using XDA Premium HD app
agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
Well Thank YOU ALOT.. you saved me TONS OF WORRIES. That trick got me out of a boot -> recovery -> odin mode loop. I thought I was going to have to confess to ATT and beg for them to fix my phone. I wont be touching my recovery again for a while. Not until a confirmed method and hugely tested recovery/custom rom method comes out.
Thank you! I knew that little bit of advice would help somebody one day.
and its on mf3, i really wanted to flash a gpe rom too.....
is there any way to flash it at all? i understand mf3 doesnt have a working recovery
Not at the moment. There is a root method, but no factory image to flash back to.
http://forum.xda-developers.com/showthread.php?p=43890414 check here for recovery updates.
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4
sheek360 said:
and its on mf3, i really wanted to flash a gpe rom too.....
is there any way to flash it at all? i understand mf3 doesnt have a working recovery
Click to expand...
Click to collapse
We all just have to be patient! It's not the end of the world, rooting it allows you to remove some bloatware, then you can install themes and launchers to make it a little better!~
You can still tweak the device so it's enjoyable!
Think hard before you root it. There is currently no way to unroot. There also is no odin flashable firmware should you get into trouble and need to recover from it. Read a lot in this forum before you attempt to root. Everyday there are multiple users who run into trouble and end up with a crippled phone at best.
jd1639 said:
Think hard before you root it. There is currently no way to unroot. There also is no odin flashable firmware should you get into trouble and need to recover from it. Read a lot in this forum before you attempt to root. Everyday there are multiple users who run into trouble and end up with a crippled phone at best.
Click to expand...
Click to collapse
You get around alot, have you seen any update to the MF3 bootloader issue?
TheAxman said:
You get around alot, have you seen any update to the MF3 bootloader issue?
Click to expand...
Click to collapse
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
jd1639 said:
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
Click to expand...
Click to collapse
Tons and tons of uninformed people are messing up their phones. You're right, it's sad.
It will be great when people can comfortably root their device knowing there is a way back when all is said and done.
In the mean time, to the OP, playing the waiting game will not kill anyone in this situation.
jd1639 said:
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
Click to expand...
Click to collapse
Agreed, if most would have read just a little, they would not be having this issue. For me, I always wait until a dev gets a hold of an update and does their thing, and then I update to the newest...I have NEVER updated direct on the phone, even with all the phones I have ever owned.
Not happening OP, do a search on MF3 in the search bar you will find all kinds of things related to it.
I just want to say, if you root your MF3 phone, do NOT modify anything in the system partition, which means files that require root to edit. If you happen to do some sort of mod that borks your system, it will be very difficult and perhaps impossible to recover. Don't do anything that can't be undone with a factory restore done in recovery.
I'm fairly certain that it is possible to unroot once rooted, however, your phone and system partition must be in full working order and unmodified in order to be at complete stock. If you are new to rooting and customizing the phone in that matter, you are probably best not rooting at the moment, since you will likely mess something up on accident while learning. I think most every single one of us has borked our OS while tinkering with root stuff and had to use some sort of recovery method. At the time, no recovery method is possible, so I repeat, don't root if you don't know what you're doing.
ThePerson98 said:
I just want to say, if you root your MF3 phone, do NOT modify anything in the system partition, which means files that require root to edit. If you happen to do some sort of mod that borks your system, it will be very difficult and perhaps impossible to recover. Don't do anything that can't be undone with a factory restore done in recovery.
I'm fairly certain that it is possible to unroot once rooted, however, your phone and system partition must be in full working order and unmodified in order to be at complete stock. If you are new to rooting and customizing the phone in that matter, you are probably best not rooting at the moment, since you will likely mess something up on accident while learning. I think most every single one of us has borked our OS while tinkering with root stuff and had to use some sort of recovery method. At the time, no recovery method is possible, so I repeat, don't root if you don't know what you're doing.
Click to expand...
Click to collapse
I just wanna plus 1 that for the OP
Sent from miPhone using XDA Premium HD app
As long as you're a smart cookie and don't go around attempting to mod your twframework and other important inner system files, I wouldn't get too disheartened and held back from touching the partition. Simply be intuitive and anything you intended on replacing, rename instead to the file with a *.temp extension. Wouldn't be that hard to roll back then (as long as you can still boot). Rooting itself mods the system, so people have already jumped ship in that regard.
Just don't go around trying to enable verbose boot or flash a recovery from some kind of mobile ODIN or GooManager.
BE SMART, not eccentric and living by the standards of yolo.
RETAIL NOTE 4
N910VVRU1ANI11 Firmware files to assist in your unexpected bricks. Use as you need them. I have flashed them to my phone and verify that it didn't blow up.
TO RESTORE with factory rom:
1. Download/Open Kies
2. Plug in Galaxy Note 4
3. Click Tools / Firmware upgrade and initialisation.
4. Follow prompt from there. This will completely wipe system and re-install stock rom.
If anyone is familiar with kies, I pulled the restore file from there. You can also flash your phone, reinstall system. If you are having problems, give kies a shot. Its a really heafty file weighing in at 3.15gb
*** NOTE *** Doing things to your phone can blow them up or turn them into paper weights. I take no responsibility for any thing that occurs to your device by doing anything I say or using anything I post.
Happy flashing.
I also have the files to make a semi-restore for the Developer Edition Note 4. I will work on that and see what I can get.
mrlaigle said:
RETAIL NOTE 4
*****UPLAODING***** ----- N910VVZW1ANI1 Firmware files to assist in your unexpected bricks. Use as you need them. I have flashed them to my phone and verify that it didn't blow up.
*** NOTE *** Doing things to your phone can blow them up or turn them into paper weights. I take no responsibility for any that occurs to your device by doing anything I say or using anything I post.
Happy flashing.
I also have the files to make a semi-restore for the Developer Edition Note 4. I will work on that and see what I can get.
Click to expand...
Click to collapse
Thanks a lot! Will this help with trying to achieve root?
Sent from my SM-N910V using XDA Free mobile app
shpotik said:
Thanks a lot! Will this help with trying to achieve root?
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
If you're speaking of obtaining root for the retail version of the Note 4 probably not.
Yeah most likely not. Would only be helpful if we could preinject root prior to flashing the tar with odin. With all the flags that woukd trip, the phone would never boot.
Do you have any estimate for when these files will be ready? I am having a number of issues with the stock install on my note 4, really hoping this will fix these issues. A number of other users have reported that it helped immensely.
Yeah I uploaded it before work. I'll post the link when I get home tonight. I'll have it up before 12pm est
What is it about the Note 4 software that will make it so much more difficult to root than the Note 3??
Nothing really other than they have patched all the pervious exploits
mrlaigle said:
Nothing really other than they have patched all the pervious exploits
Click to expand...
Click to collapse
Right!
That's the disappointing thing not much has changed
UPDATE : 40% be up within the hour... and back to zero browser crashed. If anyone is familure with kies, I pulled the restore file from there. You can also flash your phone, reinstall system. If you are having problems, give kies a shot.
Anyone want the aboot.mbn, boot.img, or recovery.img?
wow thanks for this man,
mrlaigle said:
Nothing really other than they have patched all the pervious exploits
Click to expand...
Click to collapse
then how is it that the Sprint version was rooted already?
I'm not understanding how they got root, but none of the other Note 4s did?
Simple answer....VERIZON!!! WELL attnt did the same thing locked the bootloader down and from the note 3 we had safestrap and a root exploit that has since been patched some say it took 6 months I think it was more like maybe a month after that root Dela vega came out so hopefully someone picks up where those left off I honestly don't think the 4 is that much better than the 3 I plan on jumping to the nexus 6
I thought I was a month for the root on the Note 3.
Added: How to restore with Kies
So until I up the base rom. Here is how to wipe system (and allot of other partitions for that matter, ie boot, recovery, system, and pretty much everything but your efs) and restore. This will provide you with the cleanest install. SO if your lag problems continue, its hardware. I have in the process of taking apart the ROM.
TO RESTORE with factory rom:
1. Download/Open Kies
2. Plug in Galaxy Note 4
3. Click Tools / Firmware upgrade and initialisation.
4. Follow prompt from there. This will completely wipe system and re-install stock rom
Any progress on the Developer Edition files? Mine is a total lag fest right now and I'd like to start over to see if that'll help.
wy1d said:
Any progress on the Developer Edition files? Mine is a total lag fest right now and I'd like to start over to see if that'll help.
Click to expand...
Click to collapse
Lag on your DE or retail? I can send you a clean DE system img that you could restore with TWRP.
I just hate the buttons that are on the screen on the htc's and Motorola. One reason why I choose the note 4
Sent from my SM-N910V using Tapatalk
mrlaigle said:
Lag on your DE or retail? I can send you a clean DE system img that you could restore with TWRP.
Click to expand...
Click to collapse
On DE. I tried flashing a T-Mobile ROM to clear up the lag and I didn't clear my fingerprints first so it locked up the fingerprint scanner. Sounds like I need to get a clean reset to stock in order to fix it. If you've got something that'd be great. Kies says my device model cannot be initialized so sounds like that route won't work.
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Scyntherei said:
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Click to expand...
Click to collapse
+1 the QFuse status didn't change when unlocking the bootloader. The media exaggerated about the qfuse and nothing has happened. Everything about the phone still works properly.
Thanks very much, I wasn't aware of this, I should read more. Awesome news.
But to answer the first question.
Very few people put in effort to root a phone with an unlocked bootloader, not matter what fuses are blown.
A phone with an unlocked bootloader has root by default.
Swatto86 said:
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
Click to expand...
Click to collapse
last i read you have to flash a kernel in order to root the phone therefore you need to unlock the bootloader to do so, i would like to just root myself but i don't know if you can.
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Why people are afraid to unlock the bootloader? Nexus devices don't lose the warranty when you unlock it, you can also lock it again.
Enviado desde mi Nexus 7 mediante Tapatalk
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
No
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
The answer is no.
To do what you want, someone would need to develop and exploit.
There is no motivation to do that when all one has to do is unlock the bootloader.
On phones where a bootloader unlock exists, root methods require unlocking the bootloader.
This is to install a custom recovery so yiou can flash SU.
Unlocked bootloader = root, no matter what.
You will need to invest the time and backup your device.
@TS, did you read the unlock/root guide in general section? It clearly states you need an unlocked bootloader + custom recovery to root your device..
Sent from my Nexus 5X using XDA-Developers mobile app
I think this should be possible now with Quadrooter vulnerabilities?
sushah23 said:
I think this should be possible now with Quadrooter vulnerabilities?
Click to expand...
Click to collapse
DOA.
But nobody is going to put in time and effort.
What is the point? Unlock the bootloader and flash. It does not void the warranty.
There is even a defined method to get the monthly security update.
With the exploit, it will only work until the next OTA patches it.
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
LiquidAlloy said:
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
Click to expand...
Click to collapse
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Jammol said:
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Click to expand...
Click to collapse
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
LiquidAlloy said:
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
Click to expand...
Click to collapse
In all honesty it's not even more convenient. Once you've used the command line you'll never go back to a toolkit. It's actually easier, much faster and you have way more control over what you do.
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
Use Helium app for individual apps backup. Worked great to backup a few apps/data when I changed from one Nexus 6P to another. Might be a bit buggy to get working to get the backup, but after that everything is fine.
you can do it with KINGROOT