So just come across the cyanogeninstaller and notice no one is talking about it here.
The program will walk you through how to unlock the boot loader, gain root, install a recovery and install the latest cyanogen mod. All in a nice little ui.
http://androidandme.com/2013/11/new...-the-play-store-desktop-client-along-with-it/
According to the faq the HTC one is supported too!
Sent from my HTC One using xda app-developers app
ratykat said:
So just come across the cyanogeninstaller and notice no one is talking about it here.
The program will walk you through how to unlock the boot loader, gain root, install a recovery and install the latest cyanogen mod. All in a nice little ui.
http://androidandme.com/2013/11/new...-the-play-store-desktop-client-along-with-it/
According to the faq the HTC one is supported too!
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
There's an article on xda's front page today
http://www.xda-developers.com/android/cyanogenmod-installer-now-available-in-the-play-store/
The one thing I wish it didn't do was wipe SD. I was going to test it out but that's a deal breaker for me. I don't want to sit around and wait for those transfers.
does it use htcdev to unlock or an exploit?
I ran this and it did what it said. Only problem I had is after it unlocked my bootloader installation failed and I had to run again and it installed cwm and then installed CyanogenMod 10.2 snapshot. I am curious of what they use to unlock bootloader as well. During the process it said waiting on unlock code then I was prompted on phone to unlock yes or no.
Sent from my One using XDA Premium 4 mobile app
So once this is done are you free to flash any custom Rom because this seems like an easy way to root and unlock boot loader . Also does this offer a way of relocking boot loader.
Sent from my HTC One using xda app-developers app
It'd be great if it could also s-off our the device I've tried every method and no luck
Sent from my HTC One using xda app-developers app
So, did anyone try this tool? Any feedback?
I can't findout the unlock method either.
Is there no one the knows how it is done?
I can't imagine the installer unlocking via htcdev, how many phonez can you unlock on one account?
And don't you think HTC would found out and block the installer unlocker?
Iam thinking of going for this once my warranty is up but not until.
Sent from my HTC One using xda app-developers app
I am possibly interested in this if safe, though probably not to stay on CM.
Only Im afraid of the 'Wipe SD' part. On my previous One I wiped SD when flashing a custom ROM and it killed the phone, was unfixable.
I am not going to destroy another phone, love the One as it is and not worth trying if not a safe option..
cokey77 said:
Iam thinking of going for this once my warranty is up but not until.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well, my warranty expires in two years. I won't even have this phone in two years. I'm waiting to complete 5 complete battery cycles and going for it :silly:
works well
So I've now got my second One back (wife got a S800 S4) so used the CM unlocking tool.
Ran perfectly except for one small glitch, it did not recognise the phone momentarily until a reboot of PC and new USB cable was used.
Now have a rooted One on CM11 and I actually like it on the handset.
There is more free ram, is smoother than Sense, not one single FC, everything works, using ART and that has not been an issue. It feels faster though have limited CPU to 1.5ghz.
Only issue with the mobile is the camera module, the purple crap. My main One is unaffected and in perfect stock condition and will stay that way. My second can be for the custom ROMs, only that I feel I'll probably use it more lol than the stock, want to get Miui on to it.
Was such as safe and easy process one day will be used on the stock One.
Would recommend this tool for unlocking as saves all the unnecessary work by using normal means, only issue is you can't back up the stock ROM as gets wiped..
Related
You guys have prob seen a thread like this a million times, but I am getting my nexus 4 soon and I wasn't sure if i should root it or not. I have rooted before (droid x2, galaxy nexus, nexus 7) so I am fairly familiar with how the process works. I will not loose my updates from Google if I root and stay on stock ROM? That's what I would plan on doing anyways if I did. Thanks for the help!
Sent from my Nexus 7 using xda app-developers app
Just Google some of the benefits of having root.. if any of those sound appealing to you then... root it. If not, don't. Buuuut since you've already been rooted with several devices, you should already know if you should root or not. But thanks for making a new thread for this personal decision that you've made 3 times before
Sent from my X909 using Tapatalk 2
In his defense this is a different devices I rooted and flashed rooms on my gs3 and gs2 but have not rooted or anything to this device but the key is yet right now haven't found a huge reason to do so this rom works perfectly for me and I get a days use out of it
Sent from my Nexus 4 using xda premium
I just couldn't stand it no more and rooted after 1 month. Also flashed clockworkmod.
Went to Nightly Mako.
I love the device but feel the new Clockwork mod's blobs folder, unable to access backups so easy, and the dam memory size...
I hesitate and hope Nightlies are flawless. Frankly its awesome. So are is the Stock ROM.
I just prefer CM10.1
ROOT!!
If I were to flash nexus 4 PA would I need to wipe system as well as do a factory reset in recovery? The directions just say factory reset.
Sent from my Nexus 7 using xda app-developers app
You had better gain root... Gaining root denotes a gain not a loss. Unlocking the bootloader means your unbacked data would be lost. So back up data and root and enjoy. And yes you may wipe system I recommend it.
Sent from my rooted Stock Nexus 4 using xda premium
Hi,
http://forum.xda-developers.com/showthread.php?t=2180999&highlight=root+or+not+root
http://forum.xda-developers.com/showthread.php?t=2194992&highlight=root+or+not+root
And: http://lmgtfy.com/?q=root+or+not+root,+why?
Original thread, what`s next: Wich rom should i choose?, please tell me all about while i wait for your answers because i`am too lazy to look for myself
gee2012 said:
Original thread, what`s next: Wich rom should i choose?, please tell me all about while i wait for your answers because i`am too lazy to look for myself
Click to expand...
Click to collapse
Hi,
LOL... That's what I thought, like all these kind of threads...
Locked soon... ?
viking37 said:
Hi,
LOL... That's what I thought, like all these kind of threads...
Locked soon... ?
Click to expand...
Click to collapse
Yes.
So last night I decided (against my better judgment) to install TWRP recovery and flash the OTA. I did it, then had trouble rooting it. I decided to just say screw it and then restore my Nandroid backup (which I made like a good boy). Then I got a failed message on the restore. Booted back up to a fresh boot. Brand new "please select your language" .. Wtf? So then I went back to TWRP wiped everything tried to restore again. Now... Fail. So now I can't boot up because I wiped my ROM and I'm freaking stuck all over this 4.3 update. Really?
So now I will try to wait until WUGS toolkit gets updated and see if I can use it to flash a stock 4.3 image to the device then root it. I don't know if i can even use that toolkit if I don't have a ROM on the device. Anyone had experience with such a cluster and have advice? Any thoughts on why the nandroid didn't restore?
:banghead:
Sent from my Nexus 7 using xda app-developers app
Start again, using the 4.3 factory image, and do it MANUALLY - none of this BS toolkit rubbish
EddyOS said:
Start again, using the 4.3 factory image, and do it MANUALLY - none of this BS toolkit rubbish
Click to expand...
Click to collapse
I haven't had any trouble with the toolkits personally and Wugs kit is very nice and easy to use. This whole mess does not stem from the use of a toolkit. Really something screwed up with TWRP I just don't know what caused it.
Sent from my Nexus 7 using xda app-developers app
Here's a guide made by me... It's really straight forward. And no waiting for toolkits
https://www.youtube.com/watch?v=uO7HkTrRzwM&feature=youtube_gdata_player
Sent from my Nexus 4 using Tapatalk 4 Beta
italia0101 said:
Here's a guide made by me... It's really straight forward. And no waiting for toolkits
https://www.youtube.com/watch?v=uO7HkTrRzwM&feature=youtube_gdata_player
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
To follow your guide do i need to be stock or can i use flash-all.bat even if i'm on sabermod and have twrp installed?
Federico_96 said:
To follow your guide do i need to be stock or can i use flash-all.bat even if i'm on sabermod and have twrp installed?
Click to expand...
Click to collapse
Yep anything you want. Doesn't matter, I was on pa and matrix
Sent from my Nexus 4 using Tapatalk 4 Beta
Well thanks. I will look forward to watching this. Again this will flash stock img, root, and unlock bootloader? And I don't have a rom on my device at all. Is that okay?
Sent from my Nexus 7 using xda app-developers app
jcnbama said:
So last night I decided (against my better judgment) to install TWRP recovery and flash the OTA. ...
Click to expand...
Click to collapse
I could tell this was going downhill after reading this first sentence. Why would you install a custom recovery in order to flash an OTA? I don't mean to offend you but you have a lot of reading to do before you continue flashing anything.
I was in the same boat and confused as hell back in my Nexus One/Galaxy Nexus days. What I've discovered after a lot of trial and error as well as A LOT of reading, is that once you become extremely familiar with using ADB and Fastboot commands you realize how unbelievably simple this stuff really is. Even soft bricks are just small hiccups that won't stress you out anymore.
Learn how to properly use ADB/Fastboot commands through terminal (in OSX) or command prompt (n Windows) and you will realize that the toolkits are silly and do exactly the same thing.
Again, I mean this in the least offensive way possible. This is coming from someone who thought he bricked his Nexus 7 and let it sit in a drawer for 5 months before finally understanding ADB/Fastboot, pulling it out of the drawer and having it back up and running within 10 minutes...
jcnbama said:
Well thanks. I will look forward to watching this. Again this will flash stock img, root, and unlock bootloader? And I don't have a rom on my device at all. Is that okay?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
This is completely OK. Follow THIS guide (just one of many) to learn how to setup your computer for ADB/Fastboot. Then follow THIS guide to learn how to flash back to completely stock. No current ROM is required on your phone to do any of this.
I swear this is a nightmare. I don't have TBU or anything. I literally have to start over. I am always VERY careful to read and make back ups that's why I use TWRP it's why I make Nandroids and this just sucks. Ugh. I have to piss and moan I don't know where to start lol. Thanks for letting me vent..
Sent from my Nexus 7 using xda app-developers app
jcnbama said:
I haven't had any trouble with the toolkits personally and Wugs kit is very nice and easy to use. This whole mess does not stem from the use of a toolkit. Really something screwed up with TWRP I just don't know what caused it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
its not that there is trouble using root toolkits(even though there is occasionally), it the fact that you dont learn to do things the right way. and when little issues come up, the knowledge isnt there to fix things yourself. and those little minor things turn into major headaches/issues.
simms22 said:
its not that there is trouble using root toolkits(even though there is occasionally), it the fact that you dont learn to do things the right way. and when little issues come up, the knowledge isnt there to fix things yourself. and those little minor things turn into major headaches/issues.
Click to expand...
Click to collapse
Well I do understand that point. It's a good one. I honestly don't know how to use ADB like I should. But at the same time it's a lot easier and if used properly can prevent mistakes. And good Devs make good money in donations so everyone is happy.. Lol :beer:
Sent from my Nexus 7 using xda app-developers app
I was wondering if there was any work being done with a pure AOSP rom or any other roms that will theme with a locked bootloader.
The answer is sort-of...
No, you cannot unlock the boot loader if you the latest ota.
Yes, you can root and install safestrap, then look for a desirable ROM.
The third option I played with is replace as many of the Motorola apps as you can with the aosp versions. It is dangerous, I only tried it with email and that worked great, but I moved on to contacts and totally screwed up the ROM forcing me to flash back to stock and redo everything.
Sent from my Nexus 10 using Tapatalk 2
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Has this method been tested and confirmed?
CrocadileUT78 said:
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
I didnt think one could downgrade if they had a locked boot loader?! Anyone who had actually achieved this please chime in here.
lukkypuggy said:
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Curious as well how did you go about this? I thought it was impossible to unlock on latest ota. If this is the case, why has this not been brought up earlier?
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I might be able to test this, but can you explain, by steps, how you did this?
Sent from my XT907 using Tapatalk 2
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you buy it used? If so, when? If you did, it may have already been unlocked...
Sent from my XT907 using Tapatalk 4
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
"Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 System, Kernel, and Radio as well we wipe your data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 Stock Recovery.
Number 3 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash TWRP Recovery by Hashcode.
Number 4 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash CWM Recovery by Hashcode.
Number 5 Explained -- This is Dan Rosenberg's root exploit called 'Motochopper'. This option requires your phone to be booted normally, with USB Debugging enabled.
Number 6 Explained -- This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters."
Click to expand...
Click to collapse
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
lukkypuggy said:
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
Click to expand...
Click to collapse
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
MistPhoenix said:
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
Click to expand...
Click to collapse
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
Thank you for the response. I do plan on testing this later on today on a locked, new M so I will be able to verify completely. Everyone sit tight
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
BTW I never did get the unlock app to actually work (just remembered).
http://forum.xda-developers.com/showthread.php?t=2226729
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Download this .zip file once you have flashed the compatible stock version and have root.
As long as it says status code: 3 in the bootloader you are unlocked
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
MistPhoenix said:
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
Click to expand...
Click to collapse
Mine had the -11 error also but it also said status code 3 in the actually bootloader, Then I flashed CWM and that was it, now I have CM10.1.3 STABLE.
Maybe double check?
Hi guys.
Confession: I'm really hesitatant about rooting my g2. I have a couple of reasons for doing so, like xposed and bigfaus split view mod along with greenify but I am afraid of not being able to return to stock in case anything should happen to my phone. I prefer a stock, working phone over a brick any day.
Any advice or recommendations are really appreciated and I won't hesitate pressing the thanks button
Sent from my LG-D802 using xda app-developers app
same..root is easy but why we cant just uninstall root?why we need all that diffecult restore to stock proccess?
Sent from my LG-D802 using xda app-developers app
The benefits out weigh the drawbacks by quite a bit. There are more than several threads how to return to stock and unroot. The root process was by far the easiest I've done of the 8 devices I've done. I'd say if there is a legitimate reason to return for warranty work it'd pop up within a week or two.
Sent from my VS980 4G using xda app-developers app
If you only root, then it's a simple process to get back to stock. Installing a custom recovery is where you run into a more complicated process for restoring to stock. Fortunately, you only need to install a custom recovery if you plan on installing custom ROMs. It's not necessary if you only want to install apps that require root.
Sent from my LG-D800 using Tapatalk
ffejy462 said:
The benefits out weigh the drawbacks by quite a bit. There are more than several threads how to return to stock and unroot. The root process was by far the easiest I've done of the 8 devices I've done. I'd say if there is a legitimate reason to return for warranty work it'd pop up within a week or two.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
I've now had it for three weeks and there has been no bugs whatsoever. In fact, defect phones are really rare in Denmark as they undergo an even stricter control than in the US and the warranty is 2 years as opposed to one year elsewhere. That only covers defects that shows up over time though. I am well aware of the Go back to stock thread, but people seem to be getting it wrong despite the fact that they follow the guidelines.
kashk5 said:
If you only root, then it's a simple process to get back to stock. Installing a custom recovery is where you run into a more complicated process for restoring to stock. Fortunately, you only need to install a custom recovery if you plan on installing custom ROMs. It's not necessary if you only want to install apps that require root.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
I am familiar with rooting on a chinese tablet and using TWRP, but that is the only experience I have. I soft-bricked my tablet the second day I got it because i messed around with firmware and so on.
I will be needing a custom recovery for adding the split view mod from bigfau
Just wondering if it is safe. I have never heard of it and been rooting phones since forever but found a page on it. I used it and love rooting a phone from the phone and not needing adb. I have supersu installed and it seems to be working fine just wondering if it was safe. Thanks
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
dragon2777 said:
Just wondering if it is safe. I have never heard of it and been rooting phones since forever but found a page on it. I used it and love rooting a phone from the phone and not needing adb. I have supersu installed and it seems to be working fine just wondering if it was safe. Thanks
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure what your definition of "safe" is, but asking this question before using something you deem questionable would've been the route to go.
dragon2777 said:
Just wondering if it is safe. I have never heard of it and been rooting phones since forever but found a page on it. I used it and love rooting a phone from the phone and not needing adb. I have supersu installed and it seems to be working fine just wondering if it was safe. Thanks
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah the above guy is right. Asking before doing is the way to go.
In this case, the exploit was constructed by geohot, the guy who hacked the PS3 and the first iPhone, as well as making -ra1n exploits for most of the iPhones.
Yes, I would say it's 'safe'.
If you meant by geohot releasing the exploit to the public and raising awareness that the kernel on the Samsung devices are bugged, then yeah it wouldn't be safe.
not only that is safe, but also no restart needed, no knox trip( at least on my 4.3 rom), root ok.
After restart all apps work, no reset needed, i just install supersu from gplay and good to go.
My favorite root method of all time, no computer needed. I did everything pc-free... Got root, custom recovery, and everything else you can imagine that usually requires a pc. Towel root, mobile Odin, cwm recovery, xposed modules, all work perfectly for me... Even if I did get stuck in a boot loop or two, was always able to recover without use of a pc.
nicholaschum said:
Yeah the above guy is right. Asking before doing is the way to go.
In this case, the exploit was constructed by geohot, the guy who hacked the PS3 and the first iPhone, as well as making -ra1n exploits for most of the iPhones.
Yes, I would say it's 'safe'.
If you meant by geohot releasing the exploit to the public and raising awareness that the kernel on the Samsung devices are bugged, then yeah it wouldn't be safe.
Click to expand...
Click to collapse
Yup I meant no malware or anything installed Thanks for the info
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Confirmed to work for 4.4.2 as well.
I just did it a few minutes ago, and again no KNOX trip.