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.
is there a way to unroot and lock the bootloader again ?
quattro_rs said:
is there a way to unroot and lock the bootloader again ?
Click to expand...
Click to collapse
Yes.
Several discussions about it already in here.
To relock the bootloader is as simple as "fastboot oem lock" command.
There's a couple of different ways to get the root out, they're all mentioned in the thread for it.
but as of now no way to flash the stock recovery
slowz3r said:
but as of now no way to flash the stock recovery
Click to expand...
Click to collapse
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
distortedloop said:
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
Click to expand...
Click to collapse
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
slowz3r said:
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
Click to expand...
Click to collapse
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
can someone explain how to do it step by step im new at this ?
ok i managed to lock the bootloader but im still not sure how to unroot the device !
distortedloop said:
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
Oh, alright
google hasnt released a full OS for flashing have they?
quattro_rs said:
can someone explain how to do it step by step im new at this ?
Click to expand...
Click to collapse
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Click to expand...
Click to collapse
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
slowz3r said:
Oh, alright
google hasnt released a full OS for flashing have they?
Click to expand...
Click to collapse
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
distortedloop said:
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
Click to expand...
Click to collapse
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
slowz3r said:
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
Click to expand...
Click to collapse
Ditto.
Ditto.
Ditto (for the most part, CWM isn't bad, but I also prefer Amon_RA).
distortedloop said:
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
Click to expand...
Click to collapse
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Requirements:
-Clockwork recovery or other custom recovery
Click to expand...
Click to collapse
quattro_rs said:
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Click to expand...
Click to collapse
the stock recovery does not allow you to flash custom/unsigned roms or other files for that matter.
so a custom Recovery is required, as of now the only one I believe is available is ClockWorkMod
got it all working now thanks to you and distortedloop .
thanks a lot guys.
I got the 2.3.5 Update OTA on my One-click-root Nexus and applied the update, but now I'm stuck on the android/exclamation point screen.
What do I do??
gnuf99 said:
I got the 2.3.5 Update OTA on my One-click-root Nexus and applied the update, but now I'm stuck on the android/exclamation point screen.
What do I do??
Click to expand...
Click to collapse
That's the stock recovery - hold power and hit vol up to get the menu.
I've been doing that, but nothing happens.
I did a battery pull, and it rebooted in 2.3.4
So what am I doing wrong? Do I need to change something before trying the update again?
Hold power and slide from volume down to volume up. But that wont do u any good you need to flash a custom recovery and reflash super user.
Sent from my Nexus S 4G using Tapatalk
So I goofed something up on my phone?
Is there a way to do this without losing all my app info/game saves?
I was going to run a TItanium backup.
And sorry, I'm a total noob with this.
ROM Manager, would I flash an older ROM or the ClockworkMod Recovery?
At that point could i just install the update and re root with Shabby Penguin's one click and then get all my app data back from Titanium backup?
gnuf99 said:
So I goofed something up on my phone?
Is there a way to do this without losing all my app info/game saves?
I was going to run a TItanium backup.
And sorry, I'm a total noob with this.
ROM Manager, would I flash an older ROM or the ClockworkMod Recovery?
At that point could i just install the update and re root with Shabby Penguin's one click and then get all my app data back from Titanium backup?
Click to expand...
Click to collapse
Nothing is goofed up if you rebooted into 2.3.4.
The update did not apply. Did you receive the OTA or download it manually?
If you are unlocked just flash CWM via fastboot and apply it from there.
If you are locked then you can go back into the stock recovery, hold power down and hit vol up (in that order) to get the menu and apply the update. You may want to ensure it is in the root of the sdcard and named update.zip.
The OTA does not wipe nor is a wipe necessary, so you shouldn't be losing any data/apps.
I got the update OTA, but not it's not asking me if I want to apply it.
I'm sorry I'm such a noob here, but step wise.
If I boot up with Vol UP, I can then go to Recovery and get to ClockWork Recovery.
From there do I just hit update from SD card?
gnuf99 said:
I got the update OTA, but not it's not asking me if I want to apply it.
I'm sorry I'm such a noob here, but step wise.
If I boot up with Vol UP, I can then go to Recovery and get to ClockWork Recovery.
From there do I just hit update from SD card?
Click to expand...
Click to collapse
Yeah, choose apply update. Choose your zip from the SD card and apply.
It will go through a series of asserts and then apply if it passes. If you've modified any of the checked system files, boot image or kernel it's likely going to fail.
Well, I didn't alter any of them on purpose
I used Shabby Penguin's one click root so I could use Titanium Backup only. (Although now I'll probably add tethering to the list) So I don't think I changed any kernel files.
It's saying it can't find the file. Whatever downloaded must have gotten deleted somehow. I may just download the update and do it myself like everyone else.
Just to clarify. I place the update.zip in the root and select apply update on the ClockWorkMod Recovery, and that's it?
I was waiting to just get the update OTA organically hoping it would avoid these problems, lol.
gnuf99 said:
Well, I didn't alter any of them on purpose
I used Shabby Penguin's one click root so I could use Titanium Backup only. (Although now I'll probably add tethering to the list) So I don't think I changed any kernel files.
It's saying it can't find the file. Whatever downloaded must have gotten deleted somehow. I may just download the update and do it myself like everyone else.
Just to clarify. I place the update.zip in the root and select apply update on the ClockWorkMod Recovery, and that's it?
I was waiting to just get the update OTA organically hoping it would avoid these problems, lol.
Click to expand...
Click to collapse
In CWM use the choose zip file from SD card option, then you can pick the file regardless of it's name.
That's it - if you are stock (other than rooting) it should apply without any issues.
You may need to reflash CWM and delete /etc/install-recovery.sh to keep CWM installed. I haven't looked at the update itself to see if it is installing the script to reflash the stock recovery.
I had this problem too. I rebooted and its back to 2.3.4. I will attempt to go to 2.3.5 today once I have more time and post my findings here. If anyone has any success please keep updating this thread.
It looks like I have to reflash CWM in order to restore Super User.
My bootloader is still unlocked, but it won't let me run/install CWM. How do I do this?
Jagar, I did finally figure this out after reading through the code in the rooting .bat that Shabby Penguin put together.
basically his file has the Clockwork Recovery image that you need.
Boot up in bootloader.
then type
fastboot flash recovery ______.img whatever image you have.
Then select RECOVERY on the bootloader menu and now you can install the superuser.zip file to re-root.
you might wanna just run the new one click again, make sure its version 2.0.. it will do teh dirty work for ya
Seriously Shabby, big props to you for automating that process. I learned much more from your code than reading through all those other posts
@gnuf99 although you succeeded in getting root , please do read the guides abt adb and fastboot. This will be always handy for you, indifferent of the device you'll use later.
Sent from my Transformer TF101 using Tapatalk
this forum is here to help people and spread knowledge, not so we can talk down to those less experienced then us. everyone starts somewhere...
removed. unnecessary comment by me .
shabbypenguin said:
you might wanna just run the new one click again, make sure its version 2.0.. it will do teh dirty work for ya
Click to expand...
Click to collapse
*REMOVED* Looking on another thread.
First of all, I have been reading this forum for about two weeks and just registered in order to get some help as I do not want to break my one week old nexus 5.
From my reading, the updates can be done in quite different ways and because of that I want to be sure what I should do.
I started by:
- root the mobile with cf-auto root. It did everything for me, got the superuser icon automatically
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
- other than that, I have installed some root only apps like rom manager, greenify, root Explorer, etc. I supported those developers with purchase. Those guys deserve it.
Anyway, i am looking for the safe way to update to 4.4.1. I read some members saying they lost root after the update, others lost something else (I am referring to the thread on nexus 5 general forum).
Can you help me? What path shall I go? Thanks a lot.
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
cesar.maranhao said:
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
Click to expand...
Click to collapse
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
shotta35 said:
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
Click to expand...
Click to collapse
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
finistere said:
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
Click to expand...
Click to collapse
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
cesar.maranhao said:
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
Click to expand...
Click to collapse
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
cesar.maranhao said:
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
Click to expand...
Click to collapse
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
shotta35 said:
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
Click to expand...
Click to collapse
yes, i have been reading those topics and many others.. i managed to solve the adb device unauthorized anyway. just flashed the 4.4.1 zip file under clockwork mod recover.. android is upgrading at the moment. lets see if everything is work as it should.
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM.. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
cesar.maranhao said:
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
Click to expand...
Click to collapse
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
cesar.maranhao said:
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
Click to expand...
Click to collapse
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
cesar.maranhao said:
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
Click to expand...
Click to collapse
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
RusherDude said:
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
cesar.maranhao said:
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
Click to expand...
Click to collapse
done it! i now have root again and the clockworkmod custom recovery! nice!
:good:
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
from where can i get the flashable clokwork mod recovery zip file?
i am going to apply the 4.4.2 update now and will be doing it this way:
from the recovery apply the 4.4.2 zip. after this apply the supersu zip. i want to install the custom recovery zip too so when the phone restarts everything will be configured. is this possible?
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
well, it seems i haven't lost my custom recovery. was it because i installed the supersu before rebooting?
I'm S - offed through sunshine (gotta love them guys) and had temp root with stock recovery, I assumed the lollipop update would fail but late last night it updated and I lost root. Any idea how to root again?
Well u have s off so flash twrp then flash su
Sent from my Nexus 6 using Tapatalk
How to flash su
Sent from my Xperia U using XDA Free mobile app
The issue is I don't have access to my personal computer for the weekend. Any other way to flash twrp? Flashify says I need root so it won't do it. Twrp manager I'm leery of because I heard the partition it puts it in is wrong thereby bricking the phone.
Unfortunately I don't believe Jcase has Sunshine working for lollipop yet... But that doesn't mean all is lost, just means you have to go a different means and you need to know how to use adb commands. Follow this address below and you will have a custom recovery and then you can install whatever custom rom or a pre-rooted LP OTA if that's all you want.
http://www.teamw.in/project/twrp2/226
Scroll down and follow the instructions under either.... 'Download - ADB / Terminal method:' or 'Download - Fastboot Method:'
You might be able to try to install the Goo Manager app from the play store to do the recovery install for you. Just not sure if that works without having root. TMWN says it just needs s-off so you may be good. Wouldn't need a computer either for that method. Just make sure you get your download of whatever rom saved on your phone before you wipe your current rom.
beeper10 said:
The issue is I don't have access to my personal computer for the weekend. Any other way to flash twrp? Flashify says I need root so it won't do it. Twrp manager I'm leery of because I heard the partition it puts it in is wrong thereby bricking the phone.
Click to expand...
Click to collapse
Download this and move it to your ext-sd card (not in any folder) using htc file manager. Rename it to 0P6BIMG.zip
https://www.androidfilehost.com/?fid=95916177934537454
Then reboot to bootloader and allow it to flash. This will give you back the latest TWRP. Boot back up and delete that zip off your sd card. IF you don't delete or rename it you won't be able to get to recovery via bootloader (it will keep trying to load that zip).
Then download this (doesn't matter to where-just remember where).
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
REboot to TWRP manually and flash it. Bam... done.....
It's not flashing - hopefully the rename is OP6 and not zeroP6. When I go to recovery then bootloader nothing happens and if I apply from SD card from recovery it says "no package selected and access denied", I'm sure I'm doing something wrong but I don't know what.
beeper10 said:
It's not flashing - hopefully the rename is OP6 and not zeroP6. When I go to recovery then bootloader nothing happens and if I apply from SD card from recovery it says "no package selected and access denied", I'm sure I'm doing something wrong but I don't know what.
Click to expand...
Click to collapse
zero P it is...
Last question.... I hope, I can't get to twrp recovery. It just takes me to stock recovery with no option to get to a custom recovery.
beeper10 said:
Last question.... I hope, I can't get to twrp recovery. It just takes me to stock recovery with no option to get to a custom recovery.
Click to expand...
Click to collapse
Did you flash this in bootloader?
I power phone off, hold volume down and hit power. Usually at this point I have recovery, bootloader, etc, now I have no options just shows the zip running and a question to update or not.... Either option goes to not updating.
Ok - apparently sometimes I'm a little slow..... All worked incredibly well once user error was taken out of the equation. Thanks Mr. Dottat, you're truly an asset to this forum!!
beeper10 said:
Ok - apparently sometimes I'm a little slow..... All worked incredibly well once user error was taken out of the equation. Thanks Mr. Dottat, you're truly an asset to this forum!!
Click to expand...
Click to collapse
Missed the part about deleting eh? Lol.
Glad you got it sorted.
When it came to update or not to update, I assumed I had to use the volume rocker then hit the power button to invoke the action. I was trying to go volume down to get to update when in reality volume down was the action needed to deny the update!! ?