Just to confirm one thing before i go smoke my NS's warranty away. If i nand backup the current stock rom and then flash the custom roms...i can always easily flash back to stock rom no?
Yes it is pretty easy to restore to your current build from a backup
Also, there are threads with stock images for the different models of the Nexus S here on XDA detailing how to go back to stock if that's something you choose to do so later
jackslim said:
Yes it is pretty easy to restore to your current build from a backup
Also, there are threads with stock images for the different models of the Nexus S here on XDA detailing how to go back to stock if that's something you choose to do so later
Click to expand...
Click to collapse
but wouldn't just recovering to backup takes to stock rom? and i believe the root can be deleted right? so that if i plan to send back the phone, i can do that...i'm only flashing roms over the weekend so that i can see if the wifi problem is fixed with different kernels...
I can't get my router to be shown in the network list and other networks have poor wifi signals :/ i'm really worried...
Yes recovering from your backup will return you to a rooted stock, and you can remove root by deleting su from /system/xbin/
can you direct me to clockworkmod apk? since i don't want to flash the .img
The recovery image isn't an .apk file, you are going to have to flash the .img from fastboot to get clockwork recovery installed.
jackslim said:
The recovery image isn't an .apk file, you are going to have to flash the .img from fastboot to get clockwork recovery installed.
Click to expand...
Click to collapse
yes i know it's not an apk but i believe, clockwork can be installed as apk and then rebooted into the clockwork recovery through the application as my motorola defy...
i don't want to flash the .img file or i won't be able to remove it if i had to...
You can flash a recovery image from ROM Manger which will install a custom reocovery
**However**
ROM Manager needs root access to install a recovery image, so therefor you need to install root permission, which in turn requires a custom recovery to flash the zip file to install the necessary file.
So... flashing the recovery image from fastboot is a necessary step in rooting on this phone
so apps like z4root and universal root don't work for nexus s?
I'm honestly not sure what exploits work with the Nexus S personally, feel free to browse through the guides that are stickied
In my opinion if you already had the intention of unlocking the bootloader, then you'll already have fastboot setup and you will already be in the bootloader so it's just one additional command to type to get your recovery image installed, pretty easy
Since the Nexus S comes with a bootloader that can be unlocked I don't think anyone would look for an expoit that works specifically for this phone because, but exploits that were built for other phones may work on this one, again you would have to browse around to see, I'm not sure about this
my main purpose is to have an option to revert back the phone to its orignal state...unlocking bootloader would be permanent no? also if i flash clockwork, that would be permanent or is there an easy way (excluding ADB) to delete clockwork ?
shad0wboss said:
so apps like z4root and universal root don't work for nexus s?
Click to expand...
Click to collapse
This phone has an unlockable bootloader. You don't need exploits like that. Just follow the directions on this forum for your specific model and you will be fine. Everything you will do can be reversed. So don't worry.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
This phone has an unlockable bootloader. You don't need exploits like that. Just follow the directions on this forum for your specific model and you will be fine. Everything you will do can be reversed. So don't worry.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
read my previous post...unlocking bootloader will be permanent thus messing up with my warranty.
You can lock the bootloader on this phone, just use the following command in fastboot
fastboot oem lock
You would have to flash over the original recovery image from fastboot before relocking the bootloader
This phone can be returned to complete stock fairly easily, if you were to find all stock images for your particular model of the Nexus S you could completely return it to stock from fastboot with a few easy commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Just look through root/unroot guides and find the images for your model, you will need to do this to at least get the recovery image for when you decide to return to stock
jackslim said:
You can lock the bootloader on this phone, just use the following command in fastboot
fastboot oem lock
You would have to flash over the original recovery image from fastboot before relocking the bootloader
This phone can be returned to complete stock fairly easily, if you were to find all stock images for your particular model of the Nexus S you could completely return it to stock from fastboot with a few easy commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Just look through root/unroot guides and find the images for your model, you will need to do this to at least get the recovery image for when you decide to return to stock
Click to expand...
Click to collapse
sorry i'm not with you here...so you're suggesting me to unlock my bootloader, flash rom? so for these purposes i won't have to install root? so how can i backup my current rom?
haha also i can't install ADB drivers :/ although i can access the phone memory lol
Yes, if you want to install custom ROM's then you should unlock your bootloader and install a custom recovery, these are both reversible.
To help getting adb/fastboot drivers you can get PDAnet from:
http://junefabrics.com/android/index.php
Setting up PDAnet usually fixes the driver problem, you can uninstall it once it's done
I think you should read through an root/unroot guide pertaining to your model, sounds like that would answer a lot of concerns and doubts
But mainly since you are concerned about your warranty, unlocking the bootloader and rooting your phone is completely reversible.
shad0wboss said:
read my previous post...unlocking bootloader will be permanent thus messing up with my warranty.
Click to expand...
Click to collapse
I don't think you get it. Nexus S is a development phone and comes with a factory built-in unlocker. This means you do NOT void your warranty when unlocking or rooting.
It is however recommended that you return to stock and lock the bootloader before returning the phone for any warranty needs because most idiots at sprint stores or service centers don't know any better even though the rules clearly tell them they must service the Nexus S even if rooted.
Now, to answer your question, when you restore back to stock and close bootloader the phone is indistinguishable from factory settings and data. So no, the bootloader unlocking is NOT permanent.
On a side note, you will have to use the Samsung exe to restore your phone to factory settings along with locking the bootloader if you want the original recovery. But I think there is an img of the original available somewhere.
Also, to replace the recovery you MUST use adb. There is a one click to do that but all it does is do all the steps you would do manually and still needs all drivers installed.
Sent from my Nexus S 4G
obsanity said:
I don't think you get it. Nexus S is a development phone and comes with a factory built-in unlocker. This means you do NOT void your warranty when unlocking or rooting.
Click to expand...
Click to collapse
It clearly states while unlocking your bootloader that by doing so your warranty is voided.
While Sprint's policy is to in fact service unlocked/rooted phones this is not the case for all carrier's.
Returning or attempting to return a phone that is unlocked can very well have you turned away since your warranty is voided in many cases, especially depending on the carrier of the phone.
jackslim said:
It clearly states while unlocking your bootloader that by doing so your warranty is voided.
While Sprint's policy is to in fact service unlocked/rooted phones this is not the case for all carrier's.
Returning or attempting to return a phone that is unlocked can very well have you turned away since your warranty is voided in many cases, especially depending on the carrier of the phone.
Click to expand...
Click to collapse
When I unlocked my phone the first time I had NO such disclaimer. This was something added later with an update. Therefore I did not void my warranty and anyone else can argue the same.
Sent from my Nexus S 4G
obsanity said:
When I unlocked my phone the first time I had NO such disclaimer. This was something added later with an update. Therefore I did not void my warranty and anyone else can argue the same.
Click to expand...
Click to collapse
I'm pretty sure that the screen has always had the warranty information on it after you type "fastboot oem unlock" in fastboot and then you have to acknowledge the unlock on the phone. It was part of the original Nexus One unlock screen and I'm sure part of the unlock on Nexus S. Especially if you're on the NS4G which came out months after the original NS. I know I had to acknowledge it when I unlocked mine. It only makes sense that if you willingly unlock your device and flash something you shouldn't in example a radio for a different model and brick your device the manufacturer isn't responsible for your mistake.
Related
Hi,
I recently unlocked my bootloader follow this tutorial: http://forum.xda-developers.com/showthread.php?t=1952038
It looks like I did it successfully, but my phone seems to have been restored. During the process the phone automatically made two backups, and I was wondering if it is possible to restore those, or if I just have to re-download everything.
Also now that my bootloader is unlocked, does that mean I'm rooted? What other steps do I need to do to get superuser or be actually rooted.
Thanks!
the backups are for you to remove the supercid. you need to hold onto those two backups[assuming they are mmcblk0p4MOD and mmcblk0p4ORIG] and your Unlock_code.bin you need to keep those 3 files. you will probably only ever use Unlock_code.bin if you need to run ruu at anytime. in order to restore the other two files you do this process [2.20 Firmware] Remove Pesky root.
what you actually need to do now is "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img" from TWRP 2.3 - HTC One X (ATT/evita) then flash this [29.08.2012] SuperSU v0.96 that will flash your twrp recovery and give you root. once you do that you can make modifications to your stock rom or ability to flash custom roms.
Remember to NEVER factory reset in bootloader or your will corrupt your sdcard.
DvineLord said:
the backups are for you to remove the supercid. you need to hold onto those two backups[assuming they are mmcblk0p4MOD and mmcblk0p4ORIG] and your Unlock_code.bin you need to keep those 3 files. you will probably only ever use Unlock_code.bin if you need to run ruu at anytime. in order to restore the other two files you do this process [2.20 Firmware] Remove Pesky root.
what you actually need to do now is "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img" from TWRP 2.3 - HTC One X (ATT/evita) then flash this [29.08.2012] SuperSU v0.96 that will flash your twrp recovery and give you root. once you do that you can make modifications to your stock rom or ability to flash custom roms.
Remember to NEVER factory reset in bootloader or your will corrupt your sdcard.
Click to expand...
Click to collapse
I did the "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img" using this tutorial: http://forum.xda-developers.com/showthread.php?t=1952076
but I don't notice any changes on the phone. Also, I'm unaware what the 'flashing' terminology is. Is there any way I can pay you a bit to show me how on teamviewer? I'm very unacknowledged with this topic and don't want to ruin a second HTC One X. :/
And also, is there no way to get my files back while keeping my bootloader unlocked? Or should I re-add all my songs and apps?
therealbzb said:
I did the "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img" using this tutorial: http://forum.xda-developers.com/showthread.php?t=1952076
but I don't notice any changes on the phone. Also, I'm unaware what the 'flashing' terminology is. Is there any way I can pay you a bit to show me how on teamviewer? I'm very unacknowledged with this topic and don't want to ruin a second HTC One X. :/
And also, is there no way to get my files back while keeping my bootloader unlocked? Or should I re-add all my songs and apps?
Click to expand...
Click to collapse
I'll help you out. PM your teamviewer stuff
Free of charge - your money's no good here.
you cant recover you data from unlock or wipe
Are there any return to stock instructions floating around out there? I'm unlocked, with cwm recovery, and rooted but am thinking if returning the phone and obviously would need to restore the original recovery, do a factory reset, and re lock. I did this recently on my evo shift and it was a two step process (re rooting took all day). Hopefully this is similarly simple?
Thanks in advance.
Sent from my XT897 using Tapatalk 2
You can flash the stock recovery and factory reset but to my knowledge motorola has not released a way to relock the phone
Sent from my XT897 using Tapatalk 2
Does "fastboot oem lock" not work? That's what the instructions say from Motorola in the unlock bootloader page.
Also, where can I find the stock recovery?
Are these what I'm looking for (from http://forum.xda-developers.com/showthread.php?t=2001226)?
drakeheart77 said:
http://db.tt/7p2Gv4cl
System
http://db.tt/qzu66AyF
System md5
http://db.tt/T2N0vYne
Stock recovery
http://db.tt/gbnt0Ddg
Boot
http://db.tt/oz8QPkP8
Boot md5
Sorry they are not clickable links, just copy & paste until I figure out the process lol.
Hope these files help!!
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
sixxt9 said:
You need the TWRP recovery installed. If you've never used it before, you'll need to make a backup in order to generate the correct folders necessary. The directory will be either on your memory card (/external1) or internal memory (/sdcard). The folder path will be TWRP/BACKUPS/**your**phone's**serial**number**/
Inside that folder, create a folder and name it "stock backup" or whatever you want to name it. Then put the *.win and the *.md5 files in there. Put the stock recover in whatever folder you have your adb installed.
Reboot to recovery.
Restore the boot and system partitions from this backup (will show as "stock backup" or whatever you named it)
Once the restore is complete, back out to the main menu ... go to reboot -> choose bootloader
Flash your stock recovery ( fastboot flash recovery **whatever you named your recovery file**.img )
I typically flash this twice one right after the other just in case
Reboot your system ( fastboot reboot )
From there you should be all set.
Click to expand...
Click to collapse
Or, can I just flash the stock recovery.img you provided, try to re-lock the bootloader, and perform a factory reset to be sufficient to return?
cmags said:
Does "fastboot oem lock" not work? That's what the instructions say from Motorola in the unlock bootloader page.
Also, where can I find the stock recovery?
Click to expand...
Click to collapse
To return to Original Software, you will need to reflash a Motorola signed software image to your device, or send it in to our service center to get reflashed. MOTOROLA reserves the right to charge for any assistance required by users during this process. At this time, we are not posting a recovery image for the Photon Q 4G LTE.
Source
stock images
Right, I understand that, but I'm still running Motorola Original Software (the stock ROM) because I never flashed either of the two in progress CM ports. I've got it back to a stock, still odexed, rooted with Motofail2go state with CWM recovery. So my plan is this:
Flash stock boot image (instead of the custom one which I used to replace the unlocked bootloader warning)
Flash stock recovery (which Moto claims they will not supply, but you just did), using:
Code:
fastboot flash recovery recovery.img
Then, perform a factory reset from recovery (that's an option in there, right?)
Then, relock the bootloader with:
Code:
fastboot oem lock
And other than the flag somewhere in Motorola's database somewhere, it should be "like new", correct?
Final question, I see two different stock recovery images.
In shabbypenguin's post from August which you just linked to, a 10mb image.
And in drakeheart's post from last week a 5.8mb image.
Anyone know which one is the right one to use with my updated 77.8.10 software?
I'm not sure if there's a stock updated recovery hosted somewhere. You might wanna revert back to the oem system and re-update from there to be safe.
I ended up flashing the earlier, 10mb recovery and it worked fine. Able to factory reset from it no problem. Couldn't relock though, the fastboot oem lock function requires you to flash OEM software along in the process.
Sent from my PG06100 using Tapatalk 2
I successfully return to stock using the method in this post
http://forum.xda-developers.com/showthread.php?t=1858959
the file link is broken , but you can find a dropbox link in following reply
The RSD flash method is currently the best for return to stock, previous post do not include system.img, I will make a full zip file for stock flash under RSD Lite.
Sent from my XT897 using Tapatalk 2
But even still, Moto has logged the device as unlocked assuming you followed the official unlock path...
Most stores probably won't check the phone thoroughly on returns. If you resell it to someone 3rd party, please tell them that you've unlocked it previously, as you have voided the manufacturers warranty.
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
You could read the guide in general (sticky thread) which answers all these questions
Sent from my Nexus 5 using Tapatalk
rootSU said:
You could read the guide in general (sticky thread) which answers all these questions
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, however the guide seems to use a separate flash step to reset tamper, I was specifically interested in using the app instead if possible.
Android.Addiction said:
Thanks, however the guide seems to use a separate flash step to reset tamper, I was specifically interested in using the app instead if possible.
Click to expand...
Click to collapse
Your steps look good to me. There are a couple ways to flash the stock firmware, make sure your userdata gets wiped. You could also go into stock recovery when you're finished and factory reset.
Aerowinder said:
Your steps look good to me. There are a couple ways to flash the stock firmware, make sure your userdata gets wiped. You could also go into stock recovery when you're finished and factory reset.
Click to expand...
Click to collapse
So far I've just been running the steps inside ./flash-all.sh manually:
Code:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-hammerhead-kot49h.zip
I can add this extra step before the above commands if needed:
fastboot erase userdata
Thanks man!
Android.Addiction said:
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
Click to expand...
Click to collapse
for the record: don't do this! it DANGEROUS to oem-lock without a working stock recovery corresponding to your bootloader version! its not mentioned often, but fastboot oem unlock uses the stock recovery to do the wipe plus unlock. this means: no stock recovery, no unlock!
yes, you can manually unlock THIS DEVICE because we know how to, IF YOU CAN BOOT AND BE ROOT. if you cant get root from android or recovery (say, recovery doesnt boot and android is not rooted) then you CANT UNLOCK EVER AGAIN.
Lanchon said:
for the record: don't do this! it DANGEROUS to oem-lock without a working stock recovery corresponding to your bootloader version! its not mentioned often, but fastboot oem unlock uses the stock recovery to do the wipe plus unlock. this means: no stock recovery, no unlock!
yes, you can manually unlock THIS DEVICE because we know how to, IF YOU CAN BOOT AND BE ROOT. if you cant get root from android or recovery (say, recovery doesnt boot and android is not rooted) then you CANT UNLOCK EVER AGAIN.
Click to expand...
Click to collapse
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
EddyOS said:
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
Click to expand...
Click to collapse
The steps the last guy quoted did flash factory images before locking.
rootSU said:
The steps the last guy quoted did flash factory images before locking.
Click to expand...
Click to collapse
Yeah, but the guy I was quoting was on about the issues present in the OPO where there are issues with the bootloader getting stuck locked if not using a stock recovery
rootSU said:
The steps the last guy quoted did flash factory images before locking.
Click to expand...
Click to collapse
lol yes he did, sorry! i thought he run the toggle-lock/reset-tamper script. my bad.
EddyOS said:
Yeah, but the guy I was quoting was on about the issues present in the OPO where there are issues with the bootloader getting stuck locked if not using a stock recovery
Click to expand...
Click to collapse
Sorry, to clarify -
Poster 1 - Outlines correct steps
Poster 2 - Don't do this this it's dangerous
You - yeah but its not dangerous. You're thinking of opo
Me - Actually the steps highlighted originally are correct and would work even on Opo!
rootSU said:
Sorry, to clarify -
Poster 1 - Outlines correct steps
Poster 2 - Don't do this this it's dangerous
You - yeah but its not dangerous. You're thinking of opo
Me - Actually the steps highlighted originally are correct and would work even on Opo!
Click to expand...
Click to collapse
In a nutshell, although the guide in my signature covers all bases with the OPO as I wrote it when I had one!
EddyOS said:
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
Click to expand...
Click to collapse
what makes you think its not the same? any source to that info? i have a nexus 5 with me here, and i remember that fastboot oem unlock ran something that looked liked a recovery. do you mean to tell me that the bootloader has its own independent recovery image built into part of its partition to boot to and do the unlocking? because otherwise i dont see how it would do it. please explain.
Android.Addiction said:
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
Click to expand...
Click to collapse
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Lanchon said:
what makes you think its not the same? any source to that info? i have a nexus 5 with me here, and i remember that fastboot oem unlock ran something that looked liked a recovery. do you mean to tell me that the bootloader has its own independent recovery image built into part of its partition to boot to and do the unlocking? because otherwise i dont see how it would do it. please explain.
Click to expand...
Click to collapse
What I mean is there's an issue with the OPO where you relock the bootloader without the stock recovery and you then can't unlock it again. It's not been documented that the same fault happens in the Nexus range, but if the OP follows the guides available on here it'll all be OK
gee2012 said:
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Click to expand...
Click to collapse
all N5 have tamper flag. it was introduced mid life of the N4 via a bootloader upgrade. i had an N4 at the time and thought that move was sh*tty.
gee2012 said:
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Click to expand...
Click to collapse
Yes it does
EddyOS said:
Yes it does
Click to expand...
Click to collapse
Where can you see it? Not in the bootloader menu as i see. So its reset tampered flag (BootUnlocker), flash the factory image and afterwards lock the bootloader in fastbooot?
EddyOS said:
What I mean is there's an issue with the OPO where you relock the bootloader without the stock recovery and you then can't unlock it again. It's not been documented that the same fault happens in the Nexus range, but if the OP follows the guides available on here it'll all be OK
Click to expand...
Click to collapse
yes, we've established the steps are ok and it was my misreading.
but regarding my warning about locking with non working stock recovery: its not been documented, but im sure it happens all the same! the bootloader uses a recovery (presumably the one recovery we know and not an image embedded in the bootloader itself) to wipe data. and it would be a mistake to unlock before wiping. so the bootloader does the wipe-then-unlock by delegating everything to the recovery. no recovery, no unlock.
gee2012 said:
Where can you see it? Not in the bootloader menu as i see. So its reset tampered flag (BootUnlocker), flash the factory image and afterwards lock the bootloader in fastbooot?
Click to expand...
Click to collapse
When connected in fastboot, type
fastboot oem device-info
And it'll show device tampered true or false
To get it all back to stock, flash the factory image completely then boot TWRP (don't flash it) and run the bootunlocker script found in the Nexus 5 unroot thread
are the modaco's rooting method still viable ? I'm seeing people saying it not work.
and can we root without having to flash other recovery, just using the default one (fastboot).
Nope, no rooting methods without unlocking bootloader yet. Most reliable method is to use custom recovery to root, and also some other fastboot (which will need unlocked bootloader)
hemanthmahesh said:
Nope, no rooting methods without unlocking bootloader yet. Most reliable method is to use custom recovery to root, and also some other fastboot (which will need unlocked bootloader)
Click to expand...
Click to collapse
root with unlocking bootloader is fine, my question is can we root without flashing other recovery (eg. cwm) ?
Recovery is not working in Moto g sometimes.. It's a known issue.. So better flash cwm to avoid bricking
Sent from my XT1033 using XDA Premium 4 mobile app
padhu1989 said:
Recovery is not working in Moto g sometimes.. It's a known issue.. So better flash cwm to avoid bricking
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
oh thank you for the info, then I root with cwm :good:
Stock recovery is pretty useless now, I hardly have any idea what it can even be used for other than those ota updates. Do you not want to move away from stock recovery cause you might not install firmware updates? You can install alternate recovery just for rooting and revert back to stock if you really want to.
hemanthmahesh said:
Stock recovery is pretty useless now, I hardly have any idea what it can even be used for other than those ota updates. Do you not want to move away from stock recovery cause you might not install firmware updates? You can install alternate recovery just for rooting and revert back to stock if you really want to.
Click to expand...
Click to collapse
I just being careful if not how to send warranty
Well, if you are unlocking the bootloader, you won't be able to claim warranty anyway.
hemanthmahesh said:
Well, if you are unlocking the bootloader, you won't be able to claim warranty anyway.
Click to expand...
Click to collapse
oh yeah forgot about that, but what if after root, I lock back the bootloader ?
is the root still there ?
To lock bootloader you have flash your stock firmware, which in a way would be a complete reset, so no root left. Also, whatever you do after with the phone, once you request the unlock code from the moto website, they will consider your phone unlocked, hence no warranty. You can relock to try your luck and they just might not care if you are lucky.
Be very careful with locking bootloader though, locking your bootloader in a wrong way (wrong firmware, not flashing all files, downgrading) will create a big mess. In my opinion, stay away from locking bootloader!
hemanthmahesh said:
To lock bootloader you have flash your stock firmware, which in a way would be a complete reset, so no root left. Also, whatever you do after with the phone, once you request the unlock code from the moto website, they will consider your phone unlocked, hence no warranty. You can relock to try your luck and they just might not care if you are lucky.
Be very careful with locking bootloader though, locking your bootloader in a wrong way (wrong firmware, not flashing all files, downgrading) will create a big mess. In my opinion, stay away from locking bootloader!
Click to expand...
Click to collapse
thank you man, btw can you help me with rooting by flashing cwm ?
You need working adb and fastboot drivers.
Download here:
http://www.mymotocast.com/download/MDM?platform=windows (drivers)
https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc (minimal adb and fastboot files)
http://forum.xda-developers.com/showthread.php?t=2563599 (cwm download)
Guide:
1. http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6 (For unlocking bootloader)
2. After unlocking (which will be equal to a complete reset, no files left in your "sd card"), boot into fastboot mode again and use this command:
fastboot flash recovery recovery-clockwork-6.0.4.7-falcon.img (or whatever is the name of recovery image file)
or use this tool:
http://forum.xda-developers.com/showthread.php?t=2635706
You can also use that too to push supersu to sd card or manually place it. Reboot to recovery (adb reboot recovery) and flash that zip file.
hemanthmahesh said:
You need working adb and fastboot drivers.
Download here:
http://www.mymotocast.com/download/MDM?platform=windows (drivers)
https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc (minimal adb and fastboot files)
http://forum.xda-developers.com/showthread.php?t=2563599 (cwm download)
Guide:
1. http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6 (For unlocking bootloader)
2. After unlocking (which will be equal to a complete reset, no files left in your "sd card"), boot into fastboot mode again and use this command:
fastboot flash recovery recovery-clockwork-6.0.4.7-falcon.img (or whatever is the name of recovery image file)
or use this tool:
http://forum.xda-developers.com/showthread.php?t=2635706
You can also use that too to push supersu to sd card or manually place it. Reboot to recovery (adb reboot recovery) and flash that zip file.
Click to expand...
Click to collapse
thanks man, seriously million of thanks
Hello,
trying to get root by unlocking the bootloader first (using preload recovery TWRP lastest + tamper bit mod) but I keep getting this error:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.406s
So I can't preload the custom recovery, is there any way of rooting on this oneplus firmware without wiping the whole device?
Any help would be much appreciated..
Edit: This isn't a reroot, this is first time root/unlock
Did you type fastboot oem unlock?
Your bootloader is locked and needs to be unlocked.
If fastboot oem unlock does not unlock it, then you need to fastboot boot into recovery.
Flash tamper, unlock, and then afterwords, adb sideload SuperSU.
zephiK said:
Did you type fastboot oem unlock?
Your bootloader is locked and needs to be unlocked.
If fastboot oem unlock does not unlock it, then you need to fastboot boot into recovery.
Flash tamper, unlock, and then afterwords, adb sideload SuperSU.
Click to expand...
Click to collapse
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
therightperson_630 said:
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
Click to expand...
Click to collapse
Yeah, I'm in the same boat as you. Unfortunately after all my reading, it seems impossible as CM did it as a preventative measure to secure your data.
I'm going to do a back up of everything and then a reflash to 25R where battery life was best, then unlock and reboot.
therightperson_630 said:
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
Click to expand...
Click to collapse
Well thats the whole point, the OnePlus One is a very developer friendly phone indeed. Thats why you get the "keys" to unlock the phone with a simple command instead of using a exploit to flash a custom recovery.
On 25R bootloader, it was possible but as of now there isn't a way to root without unlocking the bootloader. You can read the thread here, http://forum.xda-developers.com/oneplus-one/help/root-unlocking-bootloader-t2820628
This is why when people just now get a phone that has the ability to fastboot oem unlock, I suggest them to unlock their bootloaders as the first thing to do.
Backup all of your data and move forward. Best of luck.
therightperson_630 said:
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
Click to expand...
Click to collapse
if you truly want to restore everything there are apps that will zip up all your data and you can flash in one session after wiping your phone. If you are reloading the exact same software it should not be an issue. check google and playstore for such apps like app2zip
app2zip requires root, which I can't get if I've not unlocked the bootloader, which means wiping everything...app2zip won't help here but thanks for the suggestion
therightperson_630 said:
app2zip requires root, which I can't get if I've not unlocked the bootloader, which means wiping everything...app2zip won't help here but thanks for the suggestion
Click to expand...
Click to collapse
oh yea my bad I forgot about the root part. I usually root right away so my bad..
Sorry, but the only way is to unlock the bootloader. You could use Helium backup, also some Apps themselves have great backup functionality.
Yep. Gotta unlock it. No idea why people don't just do that in the first place.
Transmitted via Bacon
timmaaa said:
Yep. Gotta unlock it. No idea why people don't just do that in the first place.
Transmitted via Bacon
Click to expand...
Click to collapse
Because most people set up their phone before getting stuck into rooting and the like. Just as I did. I think locking the bootloader is good in theory, but the average user wouldn't know how to brick their phone even if the bootloader was already unlocked, so why do it?
therightperson_630 said:
Because most people set up their phone before getting stuck into rooting and the like. Just as I did. I think locking the bootloader is good in theory, but the average user wouldn't know how to brick their phone even if the bootloader was already unlocked, so why do it?
Click to expand...
Click to collapse
The difference between having a locked and unlocked bootloader is simply flashing custom recoveries or radios/etc. Theres no harm in doing leaving your bootloader unlocked.
The bootloader has to be locked out of the box, I believe its one of the criterias needed to be fulfilled in order to be approved for Google Apps (Play Store,etc). Also, it doesn't make sense to have a bootloader unlocked for average users.
Just unlock the bootloader and learn from your lesson.... either that or stick with stock ROM without root. Yeah it'll set you back because you'll have to redo your phone apps/settings but on the bright side you won't have to do it again because ur bootloader is already unlocked.
You need your bootloader unlocked to obtain root. See http://forum.xda-developers.com/showthread.php?t=2788632 on instructions on how to do so if you're unfamiliar. After once its unlocked, fastboot flash a custom recovery and flash supersu.
Trust me I'm familiar...had none of this trouble on the G1. Out of 5 android devices this is the second time I've had to unlock the bootloader...and the average user doesn't even know what a bootloader is, so not sure they'd be able to mess about with the radios.
therightperson_630 said:
Trust me I'm familiar...had none of this trouble on the G1. Out of 5 android devices this is the second time I've had to unlock the bootloader...and the average user doesn't even know what a bootloader is, so not sure they'd be able to mess about with the radios.
Click to expand...
Click to collapse
Thats because the G1 had a locked bootloader and the only way to flash a custom recovery was to gain a exploit to push a custom recovery. For the OnePlus/Nexus/HTC, we don't need a exploit because we have the ability to unlock our bootloaders. Think of it as Apple's iOS, in order to gain jailbreak you need a exploit to jailbreak your phone which can take a long time for it to happen. Whereas, on Nexus/OnePlus/HTC, we can simply just obtain access to do changes to the phone without having to wait for a exploit.
You keep mentioning average user but a average user wouldn't be attempting to obtain root access for their phone. The average user would just be using his/her phone as a phone and not tinkering with the deeper innings of the Operating System and if the average user wants to tinker with the deeper innings then they should really do their research and learn. There are a lot of good guides on XDA.
Couldn't agree more. There is no need for any exploit with this phone because you've been handed the keys.
Transmitted via Bacon
therightperson_630 said:
Hello,
trying to get root by unlocking the bootloader first (using preload recovery TWRP lastest + tamper bit mod) but I keep getting this error:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.406s
So I can't preload the custom recovery, is there any way of rooting on this oneplus firmware without wiping the whole device?
Any help would be much appreciated..
Edit: This isn't a reroot, this is first time root/unlock
Click to expand...
Click to collapse
have you considered the exploit devised in the following thread?:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
ondoy1943 said:
have you considered the exploit devised in the following thread?:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
That doesn't allow you to root while having a unlocked bootloader. It just changes the bits on whether or not your device has been tampered.
But then again,
This mod will allow you to unlock the bootloader without wiping the userdata as oppose to fastboot oem unlock command.
Click to expand...
Click to collapse
A little off topic but I unlock my boot loader and root as soon as I get the phone so I don't have to loose anything.
zephiK said:
That doesn't allow you to root while having a unlocked bootloader. It just changes the bits on whether or not your device has been tampered.
Click to expand...
Click to collapse
that's what you think, but in my case i was able to unlock the bootloader using the mod, hence rooting was a matter of course. the casual "fastboot oem unlock" command was not effective with my device. so.....
edit: then again, i unlocked the bootloader and rooted my phone while it was still at 30O firmware. i have no idea if the 33R firmware's bootloader is different from that of the 30O or not, that will render the mod ineffective.
It's fine, problem solved, went through the gruelling task of trying to back everything up without root = 40gb of stuff..
Already tried the tamper bit mod...it was stated in the first post (tamper bit mod) and the command screenshot was one of the steps when trying to boot the recovery, it still wouldn't boot because the bootloader wasn't unlocked..so, useless in my case.
Still lost some stuff but I got most of it back. I didn't have this problem on my xperia SP when unlocking the bootloader..if I remember correctly you could root, get recovery and custom rom all without unlocking bootloader. Unlocking the bootloader didn't erase the internal sd either..sure it might have been through an exploit rather than the proper way, but tbh I think I'd rather have that.
I'm not liking this "you've been given the keys" analogy...It's more like you've already settled into your new house and you're given the keys to unlock the front door when you're already inside...it's hassle more than anything.