Related
How close are we to having a no-wipe root?
its not like u have to root and wipe everyday
EXACTLY
johnxjets said:
its not like u have to root and wipe everyday
Click to expand...
Click to collapse
lol the phone had root within hours of launch so chances are your phone will be BRAND NEW when you root it. I don't see how much stuff you could possibly put on your phone in a couple hours before you have the chance to do it. all you should have to do is sign into gmail. Apps, WIFI settings, passwords, all of it now restore when you log in automatically. i love it!
I rooted the phone last night while it was on and it didn't wipe anything. To have root, you just need to have the right files in the right places. It wipes absolutely nothing
jroid said:
I rooted the phone last night while it was on and it didn't wipe anything. To have root, you just need to have the right files in the right places. It wipes absolutely nothing
Click to expand...
Click to collapse
Every other post on the forum disagrees with you.
seriouslyjeff said:
lol the phone had root within hours of launch so chances are your phone will be BRAND NEW when you root it. I don't see how much stuff you could possibly put on your phone in a couple hours before you have the chance to do it. all you should have to do is sign into gmail. Apps, WIFI settings, passwords, all of it now restore when you log in automatically. i love it!
Click to expand...
Click to collapse
Well how about that since this stupid thing doesn't have a memory card, all of my pix, vids, etc are now in internal memory....
hah2110 said:
Every other post on the forum disagrees with you.
Click to expand...
Click to collapse
The "rooting" does not wipe - unlocking the boot loader wipes. The actually placement of the SU binary through custom recovery doesn't wipe. Unfortunately if you don't have a custom recovery loaded you need to unlock in order to proceed (thus wiping).
hah2110 said:
Well how about that since this stupid thing doesn't have a memory card, all of my pix, vids, etc are now in internal memory....
Click to expand...
Click to collapse
Does it wipe the entire internal storage or only the ~ 1G allocated for apps and such? Has anyone tried this to verify?
krohnjw said:
Does it wipe the entire internal storage or only the ~ 1G allocated for apps and such? Has anyone tried this to verify?
Click to expand...
Click to collapse
The fastboot oem unlock wipes EVERYTHING. The app storage and internal sd storage. So make sure to back up everything. When roms start coming out, if it's like the Galaxy S phone, it will only do factory reset wipe and not the internal sd partition.
krohnjw said:
The "rooting" does not wipe - unlocking the boot loader wipes. The actually placement of the SU binary through custom recovery doesn't wipe. Unfortunately if you don't have a custom recovery loaded you need to unlock in order to proceed (thus wiping).
Click to expand...
Click to collapse
Exactly
hah2110 said:
Every other post on the forum disagrees with you.
Well how about that since this stupid thing doesn't have a memory card, all of my pix, vids, etc are now in internal memory....
Click to expand...
Click to collapse
What I meant by this was the phone has only been on the market for a day so It couldn't be too hard to redo or reput back on what you already have. But once boot is unlocked it shouldn't ever be an issue again. Wasn't the n1 the same when you unlocked boot?
N1 didn't wipe SD though. Since this has no SD card wiping will wipe far more content.
Non-unlocking root possible?
Ok. Ive been playing around with the nexus s for sometime now. Im starting to think on rooting the phone. The problem is that unlocking the boot wipes the phone, something i do not want to happen.
If i understood these posts right i can get root if i boot with a custom recovery. So connecting to adb in fastboot mode and executing:
fastboot boot recovery-clockwork-crespo.img
Should do that.
If i then flash the superuser zip, will i get the phone rooted and still locked (not wiped).
Am i missing something? Almost certain i am.
Could any of you provide a guide on how to do it, please?
Thanxs,
Iñaki
Your method is worth a try. I thought you couldn't flash the custom recovery without unlocking the bootloader, but I've seen posts saying you could (but none saying they did, if you see the difference).
Sounds like you know what to do. I'd use the 3.0.0.5 recovery image, it's linked a couple of places here.
As soon as i have some free time to do it, i will test it. Though i still think i am missing something. Just wanted to confirm i was not overlooking something obvious.
fastboot won't work unless you have unlocked it.
distortedloop said:
Your method is worth a try. I thought you couldn't flash the custom recovery without unlocking the bootloader, but I've seen posts saying you could.
Click to expand...
Click to collapse
Don't flash the recovery, just boot directly from the file.
mazodude said:
fastboot won't work unless you have unlocked it.
Click to expand...
Click to collapse
Yes it does.
Edit:
I just tried this:
First I copied the su-2.3.6.1-ef-signed.zip to /sdcard, then I booted into fastboot mode with (power + volume up). The phone said
LOCK STATE - LOCKED
Click to expand...
Click to collapse
I then booted into Clockwork recovery with
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
I mounted /system and installed su-2.3.6.1-ef-signed.zip. No errors.
Of course, I noticed no differences at all, because I was already rooted. But nandroid backup obviously worked.
Edit 2:
/system/bin/su didn't have the exact permissions as defined in the install script, but I definitely had root. Was it a new version of su, or the old one? The /system/xbin/su -> /system/bin/su symlink was new, though.
I'm new to the whole thing and in fact still haven't got my phone. I'm just excited and would like to prepare myself.
As I understand it, it is the unlocking / locking of the bootloader that does the wipe. Therefore:
a) As soon as I get my phone, can I unlock the bootloader and then can I go about as if nothing has happened keeping the stock as is for a while to enjoy it that way? When I feel comfortable enough, go about rooting ... later.
b) Would leaving it unlocked cause any problem?
c) will I get updates if I leave the bootloader unlocked and so long as I don't flash custom roms?
Thanks
Paparasee said:
I'm new to the whole thing and in fact still haven't got my phone. I'm just excited and would like to prepare myself.
As I understand it, it is the unlocking / locking of the bootloader that does the wipe. Therefore:
a) As soon as I get my phone, can I unlock the bootloader and then can I go about as if nothing has happened keeping the stock as is for a while to enjoy it that way? When I feel comfortable enough, go about rooting ... later.
b) Would leaving it unlocked cause any problem?
c) will I get updates if I leave the bootloader unlocked and so long as I don't flash custom roms?
Thanks
Click to expand...
Click to collapse
a- yes
b- none that I am aware of. I've left mine unlocked. On other devices, like the Nexus One, you can't re-lock it.
c- yes
Also, there are some posts here lately saying they've been able to root without unlocking by using "fastboot boot recovery.img" (replace recovery.img" with whichever version of clockwork you've downloaded. Then use clockwork to flash the su zip that you'd put on your sdcard before fastboot.
The only post I've only seen where someone says that particular process actually worked is the one right above yours. Note that he was already rooted, but apparently had re-locked his bootloader. I've got no reason to doubt the process if he says it worked...it would be interesting to see someone with a fresh new phone report it works.
On the other hand, since I don't know of any reason to leave your bootloader locked, the only real advantage to that method is not wiping the phone with the oem unlock. If you're on a new phone, there's nothing lost with the wipe.
shrivelfig said:
Don't flash the recovery, just boot directly from the file.
Edit:
I just tried this:
First I copied the su-2.3.6.1-ef-signed.zip to /sdcard, then I booted into fastboot mode with (power + volume up). The phone said
I then booted into Clockwork recovery with
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
I mounted /system and installed su-2.3.6.1-ef-signed.zip. No errors.
Of course, I noticed no differences at all, because I was already rooted. But nandroid backup obviously worked.
Click to expand...
Click to collapse
That's a good find. First I've ever read of just booting from the recovery image. Does the recovery image file need to be on the phone to do this?
shrivelfig said:
Edit 2:
/system/bin/su didn't have the exact permissions as defined in the install script, but I definitely had root. Was it a new version of su, or the old one? The /system/xbin/su -> /system/bin/su symlink was new, though.
Click to expand...
Click to collapse
The 2.3.2 update changes the permissions of the /system/bin files. Maybe you'd applied that and didn't notice it had changed them?
Fastboot oem unlock, does this do anything else except for rooting your phone, unlocking the bootloader and wiping all your data?
If it doesn't do anything else, there is no harm of rooting your device when you get it, right? You won't notice it?
distortedloop said:
That's a good find. First I've ever read of just booting from the recovery image. Does the recovery image file need to be on the phone to do this?
Click to expand...
Click to collapse
Nope. I think the fastboot command copies the image to the phone first, and then boots it, apparently without any flashing.
The 2.3.2 update changes the permissions of the /system/bin files.
Click to expand...
Click to collapse
Yes, I discovered that when I lost root
When I applied 2.3.2 I did the whole shebang with backup, unlock, flash, su, busybox, relock and restore. After all that I discovered that I could boot the phone directly into Clockwork from a Windows command prompt. I did a nandroid backup and fix permissions just to test. Hard to tell who fingered the su permission last
I'd test more, but right now I'm loath to unroot.
Androyed said:
Fastboot oem unlock, does this do anything else except for rooting your phone, unlocking the bootloader and wiping all your data?
Click to expand...
Click to collapse
It doesn't actually root. It just unlocks (so that you can flash non-standard stuff, like root) and wipes.
Hi Guys, as subject really! Is it possible to get the phone in a "Google" state to pull down updates, obviously meaning the impending ICS one!
B
I'm implying that you're on a custom ROM at the moment. You'll have to flash one of the stock ROM images, then you can get OTA's again.
It doesn't matter if you're rooted or have an unlocked bootloader.
Greetz
frutelaken said:
I'm implying that you're on a custom ROM at the moment. You'll have to flash one of the stock ROM images, then you can get OTA's again.
It doesn't matter if you're rooted or have an unlocked bootloader.
Greetz
Click to expand...
Click to collapse
Hey mate, thankyou for helping. I've not actually received it yet, bought one off ebay and I am just pre-empting - If you flash stock does the root and unlocked bootloader become standard again??
(I'm upgrading from an old Galaxy 3, so am reasonably familiar with flashing, but want a simple life now and am going stock Google )
B
Nope, flashing a stock image will not affect your bootloader being unlocked. You'll have to run the "fastboot oem lock" command to lock the bootloader again. Check one of the turorials here
Greetz
//edit: Actually, I'm suddenly not sure of this. Sunday evenings' got me confused. Please wait for someone else to verify.
Thankyou I'll have a look round
I have been flashing several ROMs using ROM Manager and the bootloader wasn't affected by this. The stock OTAs kept unrooting the phone though.
n00bfuscator said:
I have been flashing several ROMs using ROM Manager and the bootloader wasn't affected by this. The stock OTAs kept unrooting the phone though.
Click to expand...
Click to collapse
That's normal, the OTA's reset the permissions on key folders, effectively SU looses it's execute permissions, removing root. What i do now is download the OTA to the SD card, apply it, re-apply the SU.zip to keep root, modify the restore-recovery script so i can keep CWM, then reboot.
I'm not sure how it's going to go with ICS, but we shall see.
So I have a ns4g that I attempted to root but got hung up and am now stuck with a unlocked bootloader but no super user. So as I see it I have 3 options (if you see others PLEASE TELL ME)
1. somehow get my bootloader locked again and go back to stock (unroot)
2. keep unlocked bootloader and eventually accept ics ota (will this be ok or will having an unlocked bootloader much things up with the ota?)
3. figure out a way to finish the root process I'm sort of in the middle of (aka get super user)
If it matters I am running 2.3.7 and using a macbook running 10.7.2
What would you guys suggest?
jmelick07 said:
So I have a ns4g that I attempted to root but got hung up and am now stuck with a unlocked bootloader but no super user. So as I see it I have 3 options (if you see others PLEASE TELL ME)
1. somehow get my bootloader locked again and go back to stock (unroot)
2. keep unlocked bootloader and eventually accept ics ota (will this be ok or will having an unlocked bootloader much things up with the ota?)
3. figure out a way to finish the root process I'm sort of in the middle of (aka get super user)
If it matters I am running 2.3.7 and using a macbook running 10.7.2
What would you guys suggest?
Click to expand...
Click to collapse
flash a custom recovery(cwm or twrp) via fastboot, then flash a custom rom(and gapps). thats all you need. all the custom roms out there have root. you dont have to flash superuser.
How do I flash cwm? I think when I did this before I had the wrong version as it didn't allow for me to mount after I unlocked the bootloader
Use http://forum.xda-developers.com/showthread.php?t=1250583 to root! It will recognize that your bootloader is already unlocked and skips to flashing CMW and giving you root! There's a youtube video showing it in action if you get stuck by qbking!
Will this work with osx?
jmelick07 said:
How do I flash cwm? I think when I did this before I had the wrong version as it didn't allow for me to mount after I unlocked the bootloader
Click to expand...
Click to collapse
heres the latest version of cwm recovery for the nexus s(not ns4G) http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img
heres where all the cwm recoveries can be found, including the ns4g http://clockworkmod.com/rommanager
Ok, now how do I get that img on my phone?
The cwm for ns4g that I just downloaded that is
I'm fairly content just waiting for the google ics ota... when that comes will it mess my phone up because of my unlocked bootloader?
or even better can someone write me instructions to lock my bootloader?
I found this forum http://forum.xda-developers.com/showthread.php?t=875630
But obviously there are steps before this to have the terminal put these commands towards the phone.
jmelick07 said:
Ok, now how do I get that img on my phone?
The cwm for ns4g that I just downloaded that is
Click to expand...
Click to collapse
look at part 3 http://forum.xda-developers.com/showthread.php?t=1007782
only you dont need superuser, any custom rom has root.
Ok, I think I just want to relock my phone and wait for the ota...
I've tried just going into terminal and typing "fastboot oem lock" and it says that the command is not found... what did I do wrong?
You don't need to lock bootoader to get ota.
I've read before that accepting an ota with an unlocked bootloader will brick your phone... Can anyone else confirm that it's ok to accept the eventual ota with an unlocked bootloader?
Hey Everyone
I have an HTC Sensation, HBOOT 1.27.0000 with 3.32 ICS Firmware, sim unlocked. I have decided to upgrade it to Kitkat, I'm noobe, So I'm just searching to gather information by now. I think I must install CyanogenMod 11.
I think the progress should be:
Unlock bootloader (using fastboot)
Get root access
S-OFF (Using Juopunutbear S-OFF for HBOOT 1.27.0000)
Wipe data, cache, and dalvik cache (I don't have enough information about this step, that what will happen after this step)
Flashing Rom (Which will be CyanogenMod 11)
Flashing GAPPS (which will be an extra step, but I will do it)
I need to know that what are the possible risks, and how can I prevent them. will I loose SIM unlock? (Here in XDA, many people said no, but a few people mentioned that it can be possible. So which one is true?) How can I backup SIM unlock? How can I backup current Rom on my phone and be able to restore that backup.
Any kind of help will be appreciated
shahverdy said:
Hey Everyone
I have an HTC Sensation, HBOOT 1.27.0000 with 3.32 ICS Firmware, sim unlocked. I have decided to upgrade it to Kitkat, I'm noobe, So I'm just searching to gather information by now. I think I must install CyanogenMod 11.
I think the progress should be:
Unlock bootloader (using fastboot)
Get root access
S-OFF (Using Juopunutbear S-OFF for HBOOT 1.27.0000)
Wipe data, cache, and dalvik cache (I don't have enough information about this step, that what will happen after this step)
Flashing Rom (Which will be CyanogenMod 11)
Flashing GAPPS (which will be an extra step, but I will do it)
I need to know that what are the possible risks, and how can I prevent them. will I loose SIM unlock? (Here in XDA, many people said no, but a few people mentioned that it can be possible. So which one is true?) How can I backup SIM unlock? How can I backup current Rom on my phone and be able to restore that backup.
Any kind of help will be appreciated
Click to expand...
Click to collapse
After s-off you need to flash custom recovery and do backup form your stock rom
sent from HTC Sensation 4G
make sure you don't have HTC sync or something like that on your pc when trying to s-off, best to not even have HTC driver at all - use "universal android driver".
It's how I ruined my sd card. Also, make sure you back up ALL your sdcard content because you can lose it during s-off (I did). If you get past s-off without a hitch, then everything else will be easy. Do note that 4.4 ROMS are still buggy relative to the older ones
stillsober said:
make sure you don't have HTC sync or something like that on your pc when trying to s-off, best to not even have HTC driver at all - use "universal android driver".
It's how I ruined my sd card. Also, make sure you back up ALL your sdcard content because you can lose it during s-off (I did). If you get past s-off without a hitch, then everything else will be easy. Do note that 4.4 ROMS are still buggy relative to the older ones
Click to expand...
Click to collapse
What about SIM unlock, how can I back it up? Currently I've made a backup of my ROM with "clockworkmod" using and app named "Rom Manager".
I don't know what sim unlock is sorry. If it's a physical unlock, then s-off or a ROM change won't change it. If it's something within your ROM like an app then changing your ROM will remove it, you have to get it again, but as I said I don't know what a sim unlock is (google something like "sim unlock, rom" - if its not removed when you change roms then it won't be removed in this scenario)
You should use 4ext recovery or twrp recovery instead of clockworkmod, they both can do more and go wrong less often.
Once in 4ext recovery, do a backup (this is called a nandroid backup),
copy that backup from your sd card and whatever else to somewhere else safe (you can lose the data in your card during s-off) as long as you have that nandroid you can always return your phone to the state it's in when the backup took place.
stillsober said:
... as long as you have that nandroid you can always return your phone to the state it's in when the backup took place.
Click to expand...
Click to collapse
Thank you.
So, If I mess everything and my phone isn't booting/loading, then I can always go into recovery mode using "fastboot"?
shahverdy said:
Thank you.
So, If I mess everything and my phone isn't booting/loading, then I can always go into recovery mode using "fastboot"?
Click to expand...
Click to collapse
yes you can
shahverdy said:
Thank you.
So, If I mess everything and my phone isn't booting/loading, then I can always go into recovery mode using "fastboot"?
Click to expand...
Click to collapse
Well, i lost my recovery when i tried to s-off this last sensation. BUT as long as you can get into fastboot/hboot (the white screen when you press power+volume down) you can flash recovery.img from your computer there, so you will always be able to get into recovery
Even if you can't get to fastboot using power+volume down for whatever reason, you may still be able to get to fastboot if you can get adb or fastboot command(s) respond from command prompt (this is what happened to me, can't get to fastboot using volume+power, but can send adb commands from computer)
you should be ok, just make sure ASK IF YOU'RE UNSURE, DON'T JUST ASSUME THINGS THAT YOU'RE REALLY NOT SURE OF, ESPECIALLY REGARDING S-OFF METHOD/SDCARD, it's how I bricked my sdcard(well lost data)
stillsober said:
I don't know what sim unlock is sorry. If it's a physical unlock, then s-off or a ROM change won't change it. If it's something within your ROM like an app then changing your ROM will remove it, you have to get it again, but as I said I don't know what a sim unlock is (google something like "sim unlock, rom" - if its not removed when you change roms then it won't be removed in this scenario)
You should use 4ext recovery or twrp recovery instead of clockworkmod, they both can do more and go wrong less often.
Once in 4ext recovery, do a backup (this is called a nandroid backup),
copy that backup from your sd card and whatever else to somewhere else safe (you can lose the data in your card during s-off) as long as you have that nandroid you can always return your phone to the state it's in when the backup took place.
Click to expand...
Click to collapse
stillsober said:
Well, i lost my recovery when i tried to s-off this last sensation. BUT as long as you can get into fastboot/hboot (the white screen when you press power+volume down) you can flash recovery.img from your computer there, so you will always be able to get into recovery
Even if you can't get to fastboot using power+volume down for whatever reason, you may still be able to get to fastboot if you can get adb or fastboot command(s) respond from command prompt (this is what happened to me, can't get to fastboot using volume+power, but can send adb commands from computer)
you should be ok, just make sure ASK IF YOU'RE UNSURE, DON'T JUST ASSUME THINGS THAT YOU'RE REALLY NOT SURE OF, ESPECIALLY REGARDING S-OFF METHOD/SDCARD, it's how I bricked my sdcard(well lost data)
Click to expand...
Click to collapse
Thanks.
So, I think my biggest concern must be loosing SIM Unlock. SIM unlock process is not supported in my country because we can not pay, so I can't have the unlock code.
shahverdy said:
Thanks.
So, I think my biggest concern must be loosing SIM Unlock. SIM unlock process is not supported in my country because we can not pay, so I can't have the unlock code.
Click to expand...
Click to collapse
If you do s-off you can try with this.
http://forum.xda-developers.com/showthread.php?t=1232107
nlooooo said:
If you do s-off you can try with this.
http://forum.xda-developers.com/showthread.php?t=1232107
Click to expand...
Click to collapse
Thank you, but it is now unlocked, I want to keep it unlocked, even after flashing ROMs. I just don't want to risk.
shahverdy said:
Thank you, but it is now unlocked, I want to keep it unlocked, even after flashing ROMs. I just don't want to risk.
Click to expand...
Click to collapse
Flashing roms has nothing to do with SIM lock.
S-Off not necessary to flash CM 11
Getting S-Off is not really required if you're just looking at flashing ROM's. I've been using my phone with S-On since more than a year and no problem in flashing any ROM yet. You just need to flash 4ext recovery and enable smart flash. Just follow this awesome guide
http://forum.xda-developers.com/showthread.php?t=1631861
And you may go for S-Off after you get to know more about your phone...
Just my input here but you cannot lose sim unlock pal it's a hardware lock that once removed cannot be undone
Sent from my HTC Sensation using Tapatalk
From my experience, once you SIM unlock you won't lose it after you s-off, root, and flash... But as everybody has said, make sure you backup just in case you need to go back or do something wrong
Sent from my HTCSensation using xda app-developers app
Thanks everyone. Finally, with your helps, I flashed Cyanogenmod 11 on my HTC Sensation, and all the progress went well, without loosing anything important! But, After a few hours of testing, I found some problems, that made me go back to official Rom. I think I'd better write a review about it for other people too.
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.