Related
Fixed.
RusherDude said:
If I am on 4.4 stock rooted, with a custom recovery, and stuff modified on /system.. what I do when the update to 4.1.1 comes?
If I don't do nothing, the update will download automatically (which I don't want at all...), then try to patch and fail (I guess it won't even start since it detects that it's not stock system and recovery to flash the update) and it may even loop downloading and failing by what I readed being a bug on some 4.3 roms on the Nexus 4?
So how I should act in the following situations? First make a nandroid then..
a) I wanna flash it asap: I get the ota zip asap its posted and flash it on CWM and hope it goes ok. I may **** up stuff and have to revert to the nandroid, or 1it can go ok and just lose root and the system changes, right?
b) I wanna stay on 4.4 until all the stuff is ported to 4.1.1: It will at some point download the ota (****) by itself and spam me continuously to install it, right? If I wanna stay on 4.4 until all the stuff I use its compatible with 4.1.1, what I got to do to evade the auto-downloading of the ota and the spam about the update?
I don't know.. any way to stop the auto-update from working or so? That would be great!
Thanks in advance.
Click to expand...
Click to collapse
Here is what I just did, and it worked perfectly.
1. Take note of all the mods you installed so you can install them afterwards.
2. Put phone in bootloader mode / fastboot
3. Grab the 4.4 stock image from Google. Extract system.img file from it and flash that through fastboot (without the -w command) (fastboot flash system system.img). Don't worry you won't lose anything if you omit -w. Apps and data are preserved, it just set the \system area back to stock
4. Copy the OTA udpate zip to your phone, flash with TWRP. Since everything is 'back to stock' it should flash fine.
I had to re-root with TWRP after flashing before I rebooted. Everything was good to go. Then reflash your mods.
sonicdeth said:
Here is what I just did, and it worked perfectly.
1. Take note of all the mods you installed so you can install them afterwards.
2. Put phone in bootloader mode / fastboot
3. Grab the 4.4 stock image from Google. Extract system.img file from it and flash that through fastboot (without the -w command) (fastboot flash system system.img). Don't worry you won't lose anything if you omit -w. Apps and data are preserved, it just set the \system area back to stock
4. Copy the OTA udpate zip to your phone, flash with TWRP. Since everything is 'back to stock' it should flash fine.
I had to re-root with TWRP after flashing before I rebooted. Everything was good to go. Then reflash your mods.
Click to expand...
Click to collapse
Ok, that covers the a) situation where I want to flash it asap, thanks! (also note everyone, you got to disable xposed and all mods before flashing the ota)
PS: You can just flash the stock kernel and undo all the system changes, no need to flash the entire 4.4 stock zip.
What about the b) situation?
RusherDude said:
Ok, that covers the a) situation where I want to flash it asap, thanks! (also note everyone, you got to disable xposed and all mods before flashing the ota)
PS: You can just flash the stock kernel and undo all the system changes, no need to flash the entire 4.4 stock zip.
What about the b) situation?
Click to expand...
Click to collapse
Don't know why you'd want to go all the way back to 4.1.1. That's from July '12.
mattjorgs said:
Don't know why you'd want to go all the way back to 4.1.1. That's from July '12.
Click to expand...
Click to collapse
Wut? in the b) situation I just wanna STAY on 4.1 until all the stuff is ported to 4.1.1 (if something needs porting).
RusherDude said:
Wut? in the b) situation I just wanna STAY on 4.1 until all the stuff is ported to 4.1.1 (if something needs porting).
Click to expand...
Click to collapse
You mean 4.4? And 4.4.1? Lol
Sent from my Nexus 5 using Tapatalk
How to update to 4.4.1
I am rooted/bootloader unlocked with TWRP v2.6.3.1. When I try to flash in recovery manually with ota zip, I get a Failed error with error "E: error executing updater binary in zip"
What are step to update for a device like mine??
Cheeze[iT] said:
You mean 4.4? And 4.4.1? Lol
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Omg yea, 4.4 lol, fail haha
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.
scott_doyland said:
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.
Click to expand...
Click to collapse
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.
kieranc88 said:
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.
Click to expand...
Click to collapse
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').
scott_doyland said:
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').
Click to expand...
Click to collapse
Yeah,send it,I'll try copying it,unrooting and then trying the update
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
And will it matter what version of the stick recovery I'm using( if there are different versions)
kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx
tee_pot said:
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx
Click to expand...
Click to collapse
OK,well at the moment I'm trying out cm11 unofficial builds,I'll see how they go, I'll try the full unroot option when I restore my cwm backup and reflash stock recovery and see if that works ,as I only tried the temporary unroot option in supersu(which is probably leaving some root files behind so it can reinstall su ) if that don't work I'll flash back to stock and try again.
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I will send file tomorrow when I'm at my PC.
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I have attached the file /system/etc/install-recovery.sh file to this post (had to gzip it as couldnt upload when it was just called .sh)
Im not sure what the original persmissions of the file should be on your phone, but if you make it read/write/executable by everyone then should be OK I guess.
As I mentioned it'd be good if you unrooted and did a backup and extracted the file to see the contents (before copying over the file). That would first tell you for sure if the file does revert back to original or if it stays as a 'superSU' file when you unroot.
If its reverted back to original then my theory is wrong anyway so no need to copy over the file.
Re the stock recovery type/version being different from what is expected - I dont know if that makes a difference to the OTA working or not. Its an interesting question though so I may do some googling and find out.
I also have a UK retail stock recovery.img (taken with CWM) (my phone is 16GB from phones4u). So if you want that you can have it. Should rule out the recovery type as a problem.
FYI the install-recovery.sh original file actually flashes a new stock recovery when an OTA is performed. At least if you look in the comments of the file I attached above thats what it says.
I just got the OTA Update to Lollipop
and after i download the files, i press the install and reboot,then my nexus goes to recovery mode (CWM 6)
and then there appears :
. . . (theres still some description)
E:signature verification failed
then i just reboot and get my nexus still on 4.4
im actually forget which ROM im using right now
but in settings , it is KTU84P
FYI : I just unrooted this devices and this happened too when i was trying to upgrade with Nexus Update Checker.
Please help me guys
you need to be STOCK for OTA to work. Custom recovery, custom rom, any modifications to system etc will all prevent OTA from working.
jasonftfw said:
you need to be STOCK for OTA to work. Custom recovery, custom rom, any modifications to system etc will all prevent OTA from working.
Click to expand...
Click to collapse
how to make it sure/check it , that im using stock ROM or not
and how to uninstall CWM ?
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
jasonftfw said:
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
Click to expand...
Click to collapse
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
DarknessWarrior said:
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
Click to expand...
Click to collapse
Yeah, download ota file and sideload it, otherwise you're waiting for the ota to become available to you again via download on device.
jasonftfw said:
Yeah, download ota file and sideload it, otherwise you're waiting for the ota to become available to you again via download on device.
Click to expand...
Click to collapse
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
---------- Post added at 03:01 AM ---------- Previous post was at 02:56 AM ----------
DarknessWarrior said:
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
Click to expand...
Click to collapse
just got the OTA notification again, so I'll give it another shot (yeah, i just quoted myself)
DarknessWarrior said:
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
Click to expand...
Click to collapse
Use cmd prompt to use adb. You'll need android SDK if you don't have it. Navigate in cmd where your adb is (also have your update.zip in that directory). Run adb and then adb reboot boot loader, wait for boot loader, on device go to recovery. Once recovery is up, press vol up while holding power to access menu, go to apply update from adb then back in cmd run adb sideload update.zip
jasonftfw said:
Use cmd prompt to use adb. You'll need android SDK if you don't have it. Navigate in cmd where your adb is (also have your update.zip in that directory). Run adb and then adb reboot boot loader, wait for boot loader, on device go to recovery. Once recovery is up, press vol up while holding power to access menu, go to apply update from adb then back in cmd run adb sideload update.zip
Click to expand...
Click to collapse
thanks but I got the OTA notification again and is now installing without problems
DarknessWarrior said:
thanks but I got the OTA notification again and is now installing without problems
Click to expand...
Click to collapse
Never hurts to know how to sideload for future.
jasonftfw said:
Never hurts to know how to sideload for future.
Click to expand...
Click to collapse
agreed.
I just installed Android Sdk and downloaded the ota from google and im having problems it doesnt side load
jasonftfw said:
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
Click to expand...
Click to collapse
DarknessWarrior said:
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
Click to expand...
Click to collapse
sry i already forgot all about these things (flashing,etc.)
so how is the easiest way to flash stock Recovery ?
or should i direct flash the stock ROM ? but is it gonna delete all of my datas ?
Thanks for your answer btw
Falconite said:
sry i already forgot all about these things (flashing,etc.)
so how is the easiest way to flash stock Recovery ?
or should i direct flash the stock ROM ? but is it gonna delete all of my datas ?
Thanks for your answer btw
Click to expand...
Click to collapse
check out the toolkit from wugfresh, that might be the easiest way for you if you don't know what you're doing... maybe take some notes so that you do remember what you're doing for future.
Alright guys I have a question. I am having issues returning to stock using the lg flash tool. Errors out everytime no matter what computer/what cable I used. I have the TOT file and I have extracted it and there is a recovery.bin. I was wondering if there was anyway to use this .bin file to restore the stock recovery? I can't find any info on this from my google searches.
Issue Resolved
tenebris said:
Alright guys I have a question. I am having issues returning to stock using the lg flash tool. Errors out everytime no matter what computer/what cable I used. I have the TOT file and I have extracted it and there is a recovery.bin. I was wondering if there was anyway to use this .bin file to restore the stock recovery? I can't find any info on this from my google searches.
Click to expand...
Click to collapse
I decided to do some more digging around and I found http://downloads.codefi.re/autoprime/LG/LG_G3/D850/stock_partitions/10D by Team codefire. I downloaded the recovery.img for the D850. Flashed it using flashify. Once doing this, my phone reboot factory reset and now it is 100% stock. This was so much easier then actually setting up the lg flashtool
20f Recovery Name
tenebris said:
I decided to do some more digging around and I found http://downloads.codefi.re/autoprime/LG/LG_G3/D850/stock_partitions/10D by Team codefire. I downloaded the recovery.img for the D850. Flashed it using flashify. Once doing this, my phone reboot factory reset and now it is 100% stock. This was so much easier then actually setting up the lg flashtool
Click to expand...
Click to collapse
You used the 10d recovery image. Were you able to get OTAs after that? Also, with 10d, the name of the file is simply recovery.img. What is the name of the 20f recovery image and where is it?
glenn4466 said:
You used the 10d recovery image. Were you able to get OTAs after that? Also, with 10d, the name of the file is simply recovery.img. What is the name of the 20f recovery image and where is it?
Click to expand...
Click to collapse
The recovery name should be still recovery.img even for the 20f update. To answer your question about OTAs, yes I was able to take them.
You can find the files for 20F here. http://downloads.codefi.re/autoprime/LG/LG_G3/D850/stock_partitions/20F
The recovery might be in the Stock zip file, though I am not 100% sure.
Not There
tenebris said:
The recovery name should be still recovery.img even for the 20f update. To answer your question about OTAs, yes I was able to take them.
You can find the files for 20F here. http://downloads.codefi.re/autoprime/LG/LG_G3/D850/stock_partitions/20F
The recovery might be in the Stock zip file, though I am not 100% sure.
Click to expand...
Click to collapse
Unfortunately, in the stock zip file there is only a system.img and a boot.img.
tenebris said:
I decided to do some more digging around and I found http://downloads.codefi.re/autoprime/LG/LG_G3/D850/stock_partitions/10D by Team codefire. I downloaded the recovery.img for the D850. Flashed it using flashify. Once doing this, my phone reboot factory reset and now it is 100% stock. This was so much easier then actually setting up the lg flashtool
Click to expand...
Click to collapse
i had twrp and installed bumpd stock 5.0 rom. so if i hardreset the phone from backup and reset, will i stuck in bootloop or twrp recovery menu?
The latest update, it seems, can be rooted using the recowvery method. Dirtycow was patched by Google in a Dec. 5 security patch, but it seems LG didn't include that in their latest security update, which was created Dec 1! In any case, my phone is rooted with TWRP, and working just fine. So, for now we can still root with the update! I'd also like to point out, that this means we now have an official KDZ released version of rootable stock to roll-back to with LGUP!
Glad I forced ya to do it huh
How? I've tried multiple times and it would go through but upon booting into recovery i would get a 'no command' error
ahq1216 said:
How? I've tried multiple times and it would go through but upon booting into recovery i would get a 'no command' error
Click to expand...
Click to collapse
What method are you trying?
Follow instructions on this thread https://forum.xda-developers.com/v2...owvery-unlock-v20-root-shell-t3490594/page118
It works as kibmikey stated.
Norcal232001 said:
What method are you trying?
Follow instructions on this thread https://forum.xda-developers.com/v2...owvery-unlock-v20-root-shell-t3490594/page118
It works as kibmikey stated.
Click to expand...
Click to collapse
Ive been using easyrecowvery but ive tried that also. Maybe I messed up somewhere during the command line process thingy. Ill give it another go. Thanks
curious, if I'm currently rooted on H91810d, how can I get to a rooted H91810i? would like to make the move without getting my /data encrypted once root is lost...
dimm0k said:
curious, if I'm currently rooted on H91810d, how can I get to a rooted H91810i? would like to make the move without getting my /data encrypted once root is lost...
Click to expand...
Click to collapse
I was on 10i last week after i got phone back from service. I flashed NotSoStock Rom which said i was on the 10d base. Then flashed Overdrive Rom which put me back to 10i. I didnt have any problems switching basebands within custom roms if that helps.
ahq1216 said:
How? I've tried multiple times and it would go through but upon booting into recovery i would get a 'no command' error
Click to expand...
Click to collapse
I have same error even I tried to enter recovery using "adb reboot recovery"
---- edit ----
Done.
You must do it manually according to the instructions
https://github.com/jcadduono/android_external_dirtycow#running
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Note: make sure you rename your TWRP to twrp.img, and put SuperSU file into memory card (your TWRP cannot open internal storage).
how do you unroot and go to full stock
dudeawsome said:
how do you unroot and go to full stock
Click to expand...
Click to collapse
Since I have required 10i kdz and dll, I just flash it with LGUP as upgrade.
mingkee said:
Since I have required 10i kdz and dll, I just flash it with LGUP as upgrade.
Click to expand...
Click to collapse
Wil it remove twrp also and have you tested it
dudeawsome said:
Wil it remove twrp also and have you tested it
Click to expand...
Click to collapse
100% bone stock