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.
Related
Hello all,
I have G1 holiday edition that was given to an employee of google.
current image on this phone isn't rooted.
Can I flash image at http://www.htc.com/www/support/android/adp.html to my phone knowing this my phone has tag "test-keys"? I think yes. am I correct?
my questions are
1. Can I do this without need to wipe all my settings?
2. Is there a way to keep my current image before flashing so that I can return to it in case I am not satisfied with results?
thanks in advance.
minashokry said:
Hello all,
I have G1 holiday edition that was given to an employee of google.
current image on this phone isn't rooted.
Can I flash image at http://www.htc.com/www/support/android/adp.html to my phone knowing this my phone has tag "test-keys"? I think yes. am I correct?
my questions are
1. Can I do this without need to wipe all my settings?
2. Is there a way to keep my current image before flashing so that I can return to it in case I am not satisfied with results?
thanks in advance.
Click to expand...
Click to collapse
No, you have to wipe. If you want to take advantage of root you should get used to the idea of wiping your phone. However once root is achieved you can get the switchrom script that makes wiping a non issue.
You can always unroot and wait for the OTA update if you decide you don't like it.
Also, this thread belongs in Q&A so don't be surprised when it gets locked.
ADP
minashokry said:
Hello all,
I have G1 holiday edition that was given to an employee of google.
current image on this phone isn't rooted.
Can I flash image at http://www.htc.com/www/support/android/adp.html to my phone knowing this my phone has tag "test-keys"? I think yes. am I correct?
my questions are
1. Can I do this without need to wipe all my settings?
2. Is there a way to keep my current image before flashing so that I can return to it in case I am not satisfied with results?
thanks in advance.
Click to expand...
Click to collapse
yes .. you should be able to flash .. go ahead and try it out .. the "holiday edition" as i know it to be is the dev phone so technically you already have root on the phone .. i could be mistaken .. if you flash and it fails then no harm done .. if you flash and it completes then you're good to go
Do NOT change the bootloader on it. It has the engineering bootloader (though it *looks* like the lockdown bootloader -- version number and rainbow stripes). It *does* have fastboot and does NOT enforce firmware signatures.
Also, it *does* have root, just not from within the phone itself. Log in to it using usb/adb and it will have root there, then you can create an su command if you want.
You do NOT need to wipe -- anybody who says so is on crack. You should be able to install a cyanogen or jf mod firmware to it easy -- update.zip to /sdcard/, "reboot recovery", alt-l, alt-s, done.
To keep your current image, "reboot bootloader", then from your computer "fastboot boot recovery.img" <-- use some modified recovery image that includes "nandroid" -- like the "pimp" cyanogen recovery file. This will create a backup that can be restored in the same way as it was created.
Don't Forget To Wipe
lbcoder said:
You do NOT need to wipe -- anybody who says so is on crack.
Click to expand...
Click to collapse
poetry in motion .. LOL .. no better way to put it
lbcoder said:
Also, it *does* have root, just not from within the phone itself. Log in to it using usb/adb and it will have root there, then you can create an su command if you want.
Click to expand...
Click to collapse
are you sure this phone is rooted?
when I issue "adb root" I get "adbd cannot run as root in production builds" and if it rooted, how can I create the su command?
lbcoder said:
You do NOT need to wipe -- anybody who says so is on crack. You should be able to install a cyanogen or jf mod firmware to it easy -- update.zip to /sdcard/, "reboot recovery", alt-l, alt-s, done.
Click to expand...
Click to collapse
I prefer using official images.
lbcoder said:
To keep your current image, "reboot bootloader", then from your computer "fastboot boot recovery.img" <-- use some modified recovery image that includes "nandroid" -- like the "pimp" cyanogen recovery file. This will create a backup that can be restored in the same way as it was created.
Click to expand...
Click to collapse
may you please give more details how could I do this?
what is meaning of "reboot bootloader"? is it a command I have to issue from adb or what?
how to use a modified recovery image? I want to copy the currently installed image to recover to it in case of problems or I don't like the results?
please tell me full details as I am quite beginner in these stuff
thanks again
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
the exclamation point is the stock recovery. once you take in an ota, it removes both root and your custom recovery. to get your custom recovery back so that you can flash a bootloader(and the supersu root binaries). you can flash a custom recovery while youre in your bootloader via fastboot on your desktop.
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Yeah just realised that. Sorry its my first post
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
why don't you try twrp maybe you can flash twrp then remove the file then go back to cwm
Sent from my Nexus 5 using Tapatalk
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
luppas said:
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
Click to expand...
Click to collapse
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
simms22 said:
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
luppas said:
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
Click to expand...
Click to collapse
adb version and fastboot devices is different. adb is not fastboot and you can not use adb as fastboot. fastboot is fastboot.
simms22 said:
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
Click to expand...
Click to collapse
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
luppas said:
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
Click to expand...
Click to collapse
glad you got it
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!
Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
roadblock217 said:
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!
Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
Click to expand...
Click to collapse
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Dragbike Racer said:
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Click to expand...
Click to collapse
Tried..doesnt work for me
I can get it to boot past the recovery area, but only stays on the white screen with the green HTC logo...
EDIT:::
I want to try it again, but now somehow I have S ON....and it says TAMPERED, below that UNLOCKED in fastboot..
Really frustrated..
Dragbike Racer said:
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Click to expand...
Click to collapse
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
You can get into recovery...it won't let you restore a back up or nothing ?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
---------- Post added at 12:22 AM ---------- Previous post was at 12:17 AM ----------
roadblock217 said:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
Click to expand...
Click to collapse
Maybe sonic can get you s-off if all else fails with his java card. I'm not sure in your situation but I know he can do it as I used it. But I would use that as last resort
Sent from my HTC6525LVW using XDA Premium 4 mobile app
roadblock217 said:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
Click to expand...
Click to collapse
So you were S-OFF and you somehow got turned to S-ON...??
I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..
best bet?
get into fastboot/bootloader, and put on a custom recovery.
then, get the TWRP nandroid of the OTA, restore to that.
then, weaksauce/S-OFF
and then you should be back to normal.
If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.
opion 2
get TWRP on with fastboot
then
adb sideload any ROM to it and then get back to S-OFF
since you are unlocked you should be ok to do this without being htc dev unlocked.
you could also try htc dev, but i think that is locked.
sorry trying to think of anything else.
andybones said:
So you were S-OFF and you somehow got turned to S-ON...??
I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..
best bet?
get into fastboot/bootloader, and put on a custom recovery.
then, get the TWRP nandroid of the OTA, restore to that.
then, weaksauce/S-OFF
and then you should be back to normal.
If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.
opion 2
get TWRP on with fastboot
then
adb sideload any ROM to it and then get back to S-OFF
since you are unlocked you should be ok to do this without being htc dev unlocked.
you could also try htc dev, but i think that is locked.
sorry trying to think of anything else.
Click to expand...
Click to collapse
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
roadblock217 said:
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2725001
andybones said:
http://forum.xda-developers.com/showthread.php?t=2725001
Click to expand...
Click to collapse
Thanks...just downloaded and am going to try...
What I'm concerned about is not being able to mount /system now...this is so weird
roadblock217 said:
Thanks...just downloaded and am going to try...
What I'm concerned about is not being able to mount /system now...this is so weird
Click to expand...
Click to collapse
because of this, it most likely will not flash the nandroid then as system is a big part of the ROM and needs to be mounted.
you may have to do what was explained earlier and wipe the Internal, and then you may be able to re-do these steps.
so first try it out.
if it doesnt work, I would then wipe the 5 things instead of the 4
1) data
2) cache
3) dalvik cache
4) system
5) Internal storage (this will remove all your internal storage!)
then reboot from recovery into bootloader, then back into recovery and see if system is mounted, if it is, you can go ahead and either do the nandroid backup or an adb sideload. -- your choice
now,
if NONE of that works,
download the "RUU" that was put together and that *should* fix you right up.
andybones said:
http://forum.xda-developers.com/showthread.php?t=2725001
Click to expand...
Click to collapse
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
roadblock217 said:
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
Click to expand...
Click to collapse
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...
this is something you should have had backed up..
but, make yourself a dummy nand backup to create the folder..
just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..
the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
andybones said:
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...
this is something you should have had backed up..
but, make yourself a dummy nand backup to create the folder..
just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..
the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
Click to expand...
Click to collapse
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
roadblock217 said:
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
Click to expand...
Click to collapse
Awesome!
Very welcome.
So what was the result fix?
Did you have to wipe Internal from system not mounting?
Or did the adb sideload work?
Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?
Glad that your back up and running.
andybones said:
Awesome!
Very welcome.
So what was the result fix?
Did you have to wipe Internal from system not mounting?
Or did the adb sideload work?
Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?
Glad that your back up and running.
Click to expand...
Click to collapse
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!
Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
roadblock217 said:
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!
Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
Click to expand...
Click to collapse
It's possible after so long you didn't give the ROM long enough to boot up?
Sounds like RUU might be a cause from flashing AOSP, threads like this are good to warn people, and for when it happens to others, they can read this and know what to do. Maybe think of a new title that could help those in a search to find this thread?
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!! ?
Well, I've gotten myself into quite a pickle. Root was finally gained for the T-Mobile D6616 model over the weekend. The method works great and I had no trouble with it at all. I then installed Nut's Dual Recovery without any issue. Rebooted into TWRP multiple times over the next day or so and took a backup.
Next, I installed Xposed and started loading up all the modules I have missed since I got this phone. Everything was working great until.... I decided to edit the build.prop in order to silence the camera shutter sound. It's a pretty simple edit; I've done it a dozen times before:
Code:
ro.camera.sound.forced=0
For some reason that didn't look right to me. I thought I remembered the line being slightly different. But whatever, I threw it in there, saved it, and rebooted.
And now I'm stuck in a boot loop.
Even that is not usually a problem. My plan was to boot into TWRP, replace build.prop with the backup, reboot and be on my merry way. But.. Now my custom recovery seems to be gone. No idea why. When I boot into recovery, it seems to be stock and gives only the options: 1) continue powering up, 2) safe mode, 3) factory reset, 4) power off.
1) Powering up obviously doesn't work.
2) Safe mode doesn't work - boot loop continues
3) Tried factory reset. The little Android dude showed up, a progress bar worked on restoring to factory, and then.. still boot loop continues.
I have successfully gotten the phone to show up in adb ONCE since the boot loop appeared. I have no idea how I did it, and I haven't been able to replicate it. My plan was try to pull and edit the build.prop from adb if I can get it to show up again. But no joy so far.
Bootloader is still locked on this device, so no fastboot options.
So now I'm really at a loss for what to try next. Any ideas?
Reflash with stock rom.
electrash said:
Reflash with stock rom.
Click to expand...
Click to collapse
Yes, but... How do I do this with no custom recovery and no access to fastboot?
SportingChap said:
Yes, but... How do I do this with no custom recovery and no access to fastboot?
Click to expand...
Click to collapse
Use flashtool and a stock FTF
gregbradley said:
Use flashtool and a stock FTF
Click to expand...
Click to collapse
D6616 is not listed as being supported.
This flash tool can only be used by Xperia™ devices having an unlocked boot loader
Click to expand...
Click to collapse
Again... D6616 bootloader is not unlocked.
SportingChap said:
D6616 is not listed as being supported.
Click to expand...
Click to collapse
All xperia devices are supported by flashtool
You are talking about Sony's flashtool that only works with unlocked bootloaders
I am talking about the original flashtool developed here on XDA
Check flashtool.net
gregbradley said:
All xperia devices are supported by flashtool
You are talking about Sony's flashtool that only works with unlocked bootloaders
I am talking about the original flashtool developed here on XDA
Check flashtool.net
Click to expand...
Click to collapse
I see now. Looking into it, thanks.
I wish I could thank you more than once, gregbradley! Everything flashed and restored back to the way it was - except I lost internal storage. Bummer. Oh, well. Life goes on.
For anyone else who stumbles across this thread:
Use this thread to download the stock .ftf file for your particular Z3
Use the instructions here to download, install, and use Flashtool
Use these instructions to root (or re-root) and install TWRP recovery if you have the T-Mobile variant (D6616) Note: The link to recovery in that post is broken. You can find the latest version here: http://nut.xperia-files.com/ -- click on XZDualRecovery
If the root instructions seem to work but you don't see SuperSU after reboot, delete the contents of data/local/tmp and try again:
Code:
adb shell rm -R /data/local/tmp/*
So it' s not exactly the way it was.
SportingChap said:
except I lost internal storage. Bummer. Oh, well. Life goes on.
Click to expand...
Click to collapse
That's a learning curve, always make a backup of everything you want to keep, or keep it on the external SD card.
But glad to hear you are back up and running.
gregbradley said:
That's a learning curve, always make a backup of everything you want to keep, or keep it on the external SD card.
But glad to hear you are back up and running.
Click to expand...
Click to collapse
Yeah, didn't anticipate this one. When I took the nandroid backup in TWRP, it didn't click that there was no "internal storage" option to back up - only system, data, trim area, boot, and cache. Must be different on other devices, because I know I've backed up internal storage in the past.
A lot, if not most, of what I had on internal storage is backed up on my desktop in various folders. So I'm not at a total loss.
And.. I hear you on using external. I always did use it for most things prior to getting this Z3. I have a 64gb sdcard and use it for nandroid and TB backups (and mp3s). I had to make the decision to go along with KitKat's insistence on using internal with no external write access for apps. Now that I have root, I patched it via FolderMount and might redo my symlinks for the Pictures folder, etc. We'll see.
Sigh.. Isn't Android fun?