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.
I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
did you install any mods, kernels, change any files? if so its been documented all over the forums.
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
danielvago said:
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
Click to expand...
Click to collapse
It didn't work. I have no idea what to do, can I sideload the APK?
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
danielvago said:
It didn't work. I have no idea what to do, can I sideload the APK?
Click to expand...
Click to collapse
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
Theory said:
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
Click to expand...
Click to collapse
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
wantabe said:
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
Click to expand...
Click to collapse
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
What is the error when the OTA fails?
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
try incremental install
danielvago said:
I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
Click to expand...
Click to collapse
try sideloading 4.4.1 first. .and then sideload 4.4.2 after that. see if that works.
EddyOS said:
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
Click to expand...
Click to collapse
I just updated a new 2012 N7 from 4.1 to 4.4.2 and I couldn't get removing the -w flag to work. I think the script needs more editing than just removing the -w part. Something new I had never tried before which I actually don't personally have much use for because it still flashes the stock recovery over a custom recovery if you are using one. Anyway.. flashing the bootloader and radio separately and then flashing the update zip with "fastboot update image-hammerhead-kot49h.zip" would be a little bit of a shortcut versus flashing ALL of the images and you don't lose data.
Never had an issue myself, but I always prefer to flash each image manually one at a time
EddyOS said:
Never had an issue myself, but I always prefer to flash each image manually one at a time
Click to expand...
Click to collapse
I've always flashed each image separately also, I was just being lazy and experimenting. Removing the -w from the .bat and/or the .sh wouldn't work for me.
---------- Post added at 10:33 AM ---------- Previous post was at 10:27 AM ----------
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
wantabe said:
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
Click to expand...
Click to collapse
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
danielvago said:
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
Click to expand...
Click to collapse
Your path to adb isn't correct. Put the zip file in the same folder as adb
jd1639 said:
Your path to adb isn't correct. Put the zip file in the same folder as adb
Click to expand...
Click to collapse
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
danielvago said:
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
Click to expand...
Click to collapse
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
jd1639 said:
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
Click to expand...
Click to collapse
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
danielvago said:
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
Click to expand...
Click to collapse
Ok, so you're doing an adb sideload while in recovery?
jd1639 said:
Ok, so you're doing an adb sideload while in recovery?
Click to expand...
Click to collapse
Yes.
Hi everyone. I saw that Google released the factory image for the Nexus 5. I read on a lot of posts that the XDA members usually release a zip file that you just flash on your Nexus 5 through the recovery and it will install the bootanimation and the rom for you. I have no idea where that is. I want the final version of Lollipop and I want to flash it, not wait for the OTA update. Is there already a zip file like this or do I have to wait for some more time? Thank you.
Thread below you lol
Most of the flashing is described by google themselves: https://developers.google.com/android/nexus/images
But do read more about it elsewhere and don't forget to backup everything before you flash, if your bootloader is locked then unlocking it in order to flash the image will wipe your phone.
Sent from my Nexus 5 using XDA Premium 4 mobile app
There's an OTA Zip over there on AndroidPolice.
You can also flash the Factory Image like most of us did.
It'll be like a brand new Nexus.
maxell505 said:
Hi everyone. I saw that Google released the factory image for the Nexus 5. I read on a lot of posts that the XDA members usually release a zip file that you just flash on your Nexus 5 through the recovery and it will install the bootanimation and the rom for you. I have no idea where that is. I want the final version of Lollipop and I want to flash it, not wait for the OTA update. Is there already a zip file like this or do I have to wait for some more time? Thank you.
Click to expand...
Click to collapse
you can go look in the android development section of the nexus 5, there you will find recovery flashable stock and aosp roms. here a flash in recovery stock lollipop rom http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Curiousn00b said:
There's an OTA Zip over there on AndroidPolice.
You can also flash the Factory Image like most of us did.
It'll be like a brand new Nexus.
Click to expand...
Click to collapse
simms22 said:
you can go look in the android development section of the nexus 5, there you will find recovery flashable stock and aosp roms. here a flash in recovery stock lollipop rom http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Click to expand...
Click to collapse
Ok so I have CWM recovery and I have the stock 4.4.4 rom with xposed framework installed. So can I just put the factory image on my nexus 5 and than go on CWM recovery and flash it?
maxell505 said:
Ok so I have CWM recovery and I have the stock 4.4.4 rom with xposed framework installed. So can I just put the factory image on my nexus 5 and than go on CWM recovery and flash it?
Click to expand...
Click to collapse
What I did:
Backed up my files.
Used WUGFrsh to restore the factory image.
Curiousn00b said:
What I did:
Backed up my files.
Used WUGFrsh to restore the factory image.
Click to expand...
Click to collapse
Ok but WUGFrsh is a rooting toolkit and it is only for people who need to root their device. I am looking to just flash the system image onto my device.
maxell505 said:
Ok but WUGFrsh is a rooting toolkit and it is only for people who need to root their device. I am looking to just flash the system image onto my device.
Click to expand...
Click to collapse
So just use fastboot....?
#stayparanoid
maxell505 said:
Ok but WUGFrsh is a rooting toolkit and it is only for people who need to root their device. I am looking to just flash the system image onto my device.
Click to expand...
Click to collapse
Have you seen any of the other options?
Wugfresh Nexus Root Toolkit, contains options to restore completely to stock, flashing recoveries, boot images, you name it.
It's like an organized version for people who don't do fastboot command typings through CMD.
You could always flash the factory image yourself by Google Instructions, or download the OTA file on Android Police. The choice is yours. :/
Curiousn00b said:
What I did:
Backed up my files.
Used WUGFrsh to restore the factory image.
Click to expand...
Click to collapse
Curiousn00b said:
Have you seen any of the other options?
Wugfresh Nexus Root Toolkit, contains options to restore completely to stock, flashing recoveries, boot images, you name it.
It's like an organized version for people who don't do fastboot command typings through CMD.
You could always flash the factory image yourself by Google Instructions, or download the OTA file on Android Police. The choice is yours. :/
Click to expand...
Click to collapse
Ok so using WugFrsh, I have to restore back to complete stock and get the stock recovery also and than I have to flash the system image?
maxell505 said:
Ok so using WugFrsh, I have to restore back to complete stock and get the stock recovery also and than I have to flash the system image?
Click to expand...
Click to collapse
Not exactly.
Download the factory image, and if you want to use Wugfresh, you go to restore to stock, select your own downloaded factory image, insert the MD5 from the Google Page, and it'll guide you through the rest. It's safer to wipe before doing this, but either way, it does it by itself.
Curiousn00b said:
Not exactly.
Download the factory image, and if you want to use Wugfresh, you go to restore to stock, select your own downloaded factory image, insert the MD5 from the Google Page, and it'll guide you through the rest. It's safer to wipe before doing this, but either way, it does it by itself.
Click to expand...
Click to collapse
Ok so I am going to make this clear so I can understand better and not mess up( because I tend to do that A LOT)
*Before I do anything I have to factory reset my device.*
1. Download the factory image from here: https://developers.google.com/android/nexus/images
2. Open WugFresh and click on the "Flash Stock + Unroot" option.
3. I do not understand the MD5 part.
4. WugFresh will guide me through the rest.
P.S: I do want to be rooted when on Lollipop so I can just root again after I install Lollipop right?
maxell505 said:
Ok so I am going to make this clear so I can understand better and not mess up( because I tend to do that A LOT)
*Before I do anything I have to factory reset my device.*
1. Download the factory image from here: https://developers.google.com/android/nexus/images
2. Open WugFresh and click on the "Flash Stock + Unroot" option.
3. I do not understand the MD5 part.
4. WugFresh will guide me through the rest.
P.S: I do want to be rooted when on Lollipop so I can just root again after I install Lollipop right?
Click to expand...
Click to collapse
The MD5 part, next to the " Download " button on the Google page. You see MD5:yadayadayada. In Wugfresh, it'll need the MD5 to confirm the zip.
You can root by installing a custom recovery, flashing SuperSU and a modified kernel.
Curiousn00b said:
Not exactly.
Download the factory image, and if you want to use Wugfresh, you go to restore to stock, select your own downloaded factory image, insert the MD5 from the Google Page, and it'll guide you through the rest. It's safer to wipe before doing this, but either way, it does it by itself.
Click to expand...
Click to collapse
Curiousn00b said:
The MD5 part, next to the " Download " button on the Google page. You see MD5:yadayadayada. In Wugfresh, it'll need the MD5 to confirm the zip.
You can root by installing a custom recovery, flashing SuperSU and a modified kernel.
Click to expand...
Click to collapse
Ok thank you. I just have to factory reset my phone, flash stock and unroot, and insert the MD5. Once I get Lollipop installed, than I root.
maxell505 said:
Ok thank you. I just have to factory reset my phone, flash stock and unroot, and insert the MD5. Once I get Lollipop installed, than I root.
Click to expand...
Click to collapse
It said it is recommended to use force flash mode. Should I say yes to this?
maxell505 said:
It said it is recommended to use force flash mode. Should I say yes to this?
Click to expand...
Click to collapse
I did anyway and it worked! I am setting up Lollipop as I type this. Right now it is activating my cellular service. Hopefully everything works fine!
I am new to rooting, and decided to root my Galaxy Note II SGH-i317m a few days ago. I used a method with no adb access...i think. Here's the reference thread, just in case I'm wrong: http://forum.xda-developers.com/showthread.php?t=1980644
I got a bit overenthusiastic, and got TWRP while forgetting to unlock my bootloader first. Now, my phone will only boot into TWRP. All 4 reboot options go back to TWRP. What is the best way to get my phone back to working? I understand that I may have to lose my data. It doesn't matter: my top priority is getting my phone to work again.
Thanks in advance!
EDIT: I'm sorry if this is in the wrong place. I'm new here.
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
EMONESSboy said:
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I just tried that, and no change. Just to clarify, the only thing I can boot into at the moment is recovery mode.
I think what I need to do is flash the stock recovery back onto my phone. Is this a possible solution? If so, how should I go about doing it? I currently cannot access download mode.
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
I Can Help
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
[email protected] said:
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
Click to expand...
Click to collapse
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Phoenix204 said:
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Click to expand...
Click to collapse
tried system restore with twrp?
try it first and if ur not sure that it will work just make backup of boot , efs , system and data(if necessary) via twrp to sd card copy the backup to pc via card reader or something and extract the system backup there should be a file named build.prop in system folder edit it and do it like this :
under #additional build properties
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.root_access=1
find the above lines and edit the parameters as i have shown to you use notepad++ to edit the file save it the last line will give ya root access by default and second last will make it debuggable just save it repack and flash with twrp cheers
hit thanks
Alright. Since I can't find another thread like this one, I will assume that I am one of the first to have this problem. Here is what I did.
I used samsung-firmware.org to find the latest firmware for my phone, which includes both ROM and recovery. Other brands probably also have a website like this.
I used Odin to flash the firmware onto my phone - this wiped my data, but removed TWRP, which is an acceptable solution to me. I might also have wiped my data while playing around with TWRP trying to fix my phone - I'm not sure.
Thanks to both EMONESSboy and [email protected] for their help. I ended up going with something similar to EMONESSboy's solution, since the commands seemed a little risky. Thanks anyways, your help is much appreciated!
IRIS Fuel50
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
mzn.facebook said:
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
Click to expand...
Click to collapse
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Kingaroot
Phoenix204 said:
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Click to expand...
Click to collapse
Actually, what happend was that i tried to root my phone through Kingaroot. It shows some error at 90%. After few seconds my phone gets rebooted and snce then, it is showing Mfr LOGO only.
I have tried Factory reset, wipe cache partition etc.
I had lollipop earlier on my phone.
it's a pretty long story but currently my system partition is wiped after it soft bricked, i also couldn't reflash stock roms with twrp so i tried to extract the recovery.img from the stock rom and flashing it over twrp to get the original recovery mode back to flash the update but for some reason it didn't work.
so now i can only boot into EMUI which keeps telling 'getting package info failed' meaning i can't update through it. i'm also able to reach the 'fastboot&rescue mode' screen but i know nothing about adb and even tho i watched 2-3 tutorial videos i couldn't really get it to work. all videos wanted me to boot up the phone and enable usb debugging which i can't. my phone was rooted before and i'm positive i've enabled it in the past but i'm not sure if it's still enabled or not, either way i'm not able to get it working.
is this salvageable?
i'd really appreciate some help if possible, thnx
nope. but even when i had twrp it wouldnt let me flash update.zip's
i still have fastboot screen so my guess is that i have to run it through adb, which i don't know how to do
Rommco05 said:
Hm, and which is your model and last function system?
edit: u can boot to system? If good understand u can
Click to expand...
Click to collapse
last update i had working was frd-l09c432b120
can't boot system
can't boot recovery mode (twrp)
i CAN boot to 'fastboot&recovery mode'
i CAN boot to EMUI (but EMUI keeps telling me 'Getting package info failed', it tries to connect and download but from what i can tell on the screen the download never starts)
Ok. Ive tried running 'adb devices' but i cant see my device, if i type 'fastboot devices' i find one device.
Dont know if im missing something or if this even matters.
But i'll try flashing twrp with fastboot
Rommco05 said:
This is right way
edit: frp is unlocked?
edit1: you need to flash old twrp 3.0.2.0 I think is right (if was your last firmware Marshmallow
Click to expand...
Click to collapse
TWRP is back!!
but how do i flash marshmallow with twrp? and what marshmallow file are you talking about, the one i mentioned above?
because i tried flashing these update.zip's with twrp before but it wouldn't let me.
i'm currently packaging the update.app files into a zip and moving it to the sdcard, that's the only way i can think of to flash these update files with twrp.
since it didn't work last time, i have my doubts but i'll give it a try
Rommco05 said:
Ok, just for clarification, your model is frd-l09c432, right?
Click to expand...
Click to collapse
yes. can't remember how to double check but way back when i downloaded these update files i was extremely careful to download the correct files.
and they worked and been working since they were the newest version, so i guess that has to be my model.
EDIT: and it's twrp-3.1.1-0
yea now it told me corrupt zip, last time i tried i got some other error, think it was some error about writing to system partition.
U can also flash this https://drive.google.com/file/d/0BwXB-CJiljwpS1o4UXo5b1JlRjQ/view and after
Dload this link once http://www.hihonor.com/uk/support/details/index.html?DOC_ID=92101
Rommco05 said:
Ok download this firmware B120 and flash via twrp https://www.androidfilehost.com/?w=files&flid=129477 after this go to reboot and tap reboot recovery. Now you should be in stock recovery and tap factory reset and after reboot. Now you hopefully will be able boot to ROM. (If u got some errors in twrp, don't care, installation must take about with minutes)
Click to expand...
Click to collapse
there's no B120 on that site, only B101 and B131. should i take B131 instead?
Any updates for your issue OP?
Sent from my Honor 8 using XDA Labs
Rommco05 said:
Sorry so flash B131 is better then B120
Click to expand...
Click to collapse
it's up and running again thank you so much, you're a life saver. i'd actually kiss you if you were here lol
i spent a few hours yesterday trying to find zipped update files ready for flashing in twrp, like the ones you linked.
do i have to do a factory reset after that? i haven't tried everything yet but my phone looks and works as if it never even stopped working in the first place.
i'm just happy i got all my files, numbers, photos etc back...
thank you so much once again
EDIT: yea sorry for the delayed response, i had to run an errand
Wow another one rommoco05 :highfive:
Add the fixed tag to the thread OP. Enjoy the device
You both are awesome ???
Rommco05 said:
lol. No u don't need to make factory reset, phone start from like factory reset. Upgrade to Nougat . If u want kiss me, kiss thanks button you're welcome
Click to expand...
Click to collapse
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
JimZiii said:
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
Click to expand...
Click to collapse
If you synced the contacts already then you can from google contacts.
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
JimZiii said:
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
Click to expand...
Click to collapse
Flash the backup of boot files
venugopalu007 said:
Flash the backup of boot files
Click to expand...
Click to collapse
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
JimZiii said:
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
Click to expand...
Click to collapse
For apps backup just download from playstore , because some apps are compitable with mm and some are nougat .so better to download again from playstore after updating to nougat.
Rommco05 said:
Huawei backup is pretty good I start saving my SMS on P8lite and now I have +15000 SMS saved and 2 years old calls logs
Click to expand...
Click to collapse
That was huge bro
Rommco05 said:
Yes, resume SMS take about 15 minutes
Click to expand...
Click to collapse
Bro can you make a guide how to backup and restore in Huawei.