Develop Bugs

[Q] help! - this auto-downloaded OTA is about to screw me! - lol

OK, here is what I did so far:
1. unboxed a brand new G2 (no cell service set up yet)
2. applied manual OTA (the one from November 2010 - version 1.22.531.8)
3. followed the wiki and applied new hboot, rooted via gfree07, S-OFF, etc. using adb
was enjoying new rooted phone, everything working nice, have no T-mobile service yet, so decided to connect via wifi and surf around a bit
suddenly I realized that this phone has fully auto-downloaded and is ready to install OTA update Gingerbread 2.3.4
Yikes, it hasn't done the install yet, so everything is cool for the moment, but I am afraid to reboot or turn off phone, because I am afraid it will auto-install the downloaded OTA and I will be screwed!
how can I erase this downloaded OTA without a reboot or am I worried about nothing?
PS - the only backups of any kind I have are backups of partitions 7,18,21
PPS: beer is the reason I forgot to turn off the auto updating - lol

WTF? said:
OK, here is what I did so far:
1. unboxed a brand new G2 (no cell service set up yet)
2. applied manual OTA (the one from November 2010 - version 1.22.531.8)
3. followed the wiki and applied new hboot, rooted via gfree07, S-OFF, etc. using adb
was enjoying new rooted phone, everything working nice, have no T-mobile service yet, so decided to connect via wifi and surf around a bit
suddenly I realized that this phone has fully auto-downloaded and is ready to install OTA update Gingerbread 2.3.4
Yikes, it hasn't done the install yet, so everything is cool for the moment, but I am afraid to reboot or turn off phone, because I am afraid it will auto-install the downloaded OTA and I will be screwed!
how can I erase this downloaded OTA without a reboot or am I worried about nothing?
PS - the only backups of any kind I have are backups of partitions 7,18,21
PPS: beer is the reason I forgot to turn off the auto updating - lol
Click to expand...
Click to collapse
The update won't apply unless you tell it to apply; where it downloads to is beyond me though. Even if the update does get applied however, you can still downgrade and re-root.
Sent from my HTC Vision using XDA App

I think this did the trick, I had a brainfreeze earlier, but this should get rid of that bad-boy
su over to /cache
# rm f4d11a64d2df.OTA_Vision_Gingerbread_S_TMOUS_2.15.531.3-1.22.531.8_release_197463.zip
and stop the checkin service
sound good?

or delete a system app and it will never update lmao!

Why don't u updat with the offical 2.3rom for the g2 that arpund here its the same as ota but with root and super user..
Sent from my T-Mobile G2 using XDA App

Couldn't you try making a Nandroid backup just to be sure ? I do suspect you have ClockworkMod installed, since you are rooted.

bogdan5844 said:
Couldn't you try making a Nandroid backup just to be sure ? I do suspect you have ClockworkMod installed, since you are rooted.
Click to expand...
Click to collapse
A nandroid backup will be no help as if you flash the OTA update it will return your phone to S-ON and you will lose root.

Troubleshooting Guide & FAQ: Updating stock ROM

Hi guys,
I saw many threads popping up in the Q & A section about applying updates on a stock rooted ROM. So i though it would be helpul if i shared my experiences and also clear some misconceptions.
This Thread mainly applies for those looking to upgrade from 2.09 to the recent 2.22/2.24 ! It may or may not work for any previous updates.
Q) My phone is rooted, Bootloader unlocked and CWM installed. How do i update to 2.22?
Ans.)
1) Backup your root using Voodoo OTA Rootkeeper.
2) Flash the stock recovery for your area using the All in one kit (or you can use the command line if you're familiar).
3) Download the update, click install, sit back and enjoy !
ITS that simple.
Q) What do i do if i cant find stock recovery for my latest version?
Ans) The recovery does not seem to have changed from version 1.56 to 2.09. You can flash the older recovery provided, you've checked your region is correct.
Q) Do i need to re-lock my bootloader for the update to take place?
Ans) NO! You don't need to re-lock anything. It updates perfectly fine with unlocked bootloader. Just flash Stock recovery !
Q) Do i lose my apps/settings/cache?
Ans) Since its an OTA from HTC, you retain everyhting!
Q) Will i lose my root if i update?
Ans) You will! Thats exactly why you're advised to backup your root.
Q) My updates fails with a red triangle and exclamation mark, what did i do wrong?
Ans) You need to understand that during the update, several stock apps are patched. If any of these STOCK APPS ( the ones that came with ya new phone) are uninstalled/frozen/meddled with, an error will pop up.
Q) How do i identify the cause of the error?
Ans) When the red triangle pops up, press the Volume UP, Volume DOWN and LOCK keys at the same time for a second and release. You should see the cause of your error. Try to restore/unfreeze the app thats causing the error. If that is not possible, try posting your error here to see if experts here can help.
All the stock recoveries can be found on this forum. If however u've a doubt, i'd be happy to help.
This guide is not perfect and may contain errors ( i've tried to make it complete to the best of my knowledge). I'm open to suggestions and questions

shubhamsizzles said:
Hi guys,
I saw many threads popping up in the Q & A section about applying updates on a stock rooted ROM. So i though it would be helpul if i shared my experiences and also clear some misconceptions.
This Thread mainly applies for those looking to upgrade from 2.09 to the recent 2.22/2.24 ! It may or may not work for any previous updates.
Q) My phone is rooted, Bootloader unlocked and CWM installed. How do i update to 2.22?
Ans.)
1) Backup your root using Voodoo OTA Rootkeeper.
2) Flash the stock recovery for your area using the All in one kit (or you can use the command line if you're familiar).
3) Download the update, click install, sit back and enjoy !
ITS that simple.
Q) What do i do if i cant find stock recovery for my latest version?
Ans) The recovery does not seem to have changed from version 1.56 to 2.09. You can flash the older recovery provided, you've checked your region is correct.
Q) Do i need to re-lock my bootloader for the update to take place?
Ans) NO! You don't need to re-lock anything. It updates perfectly fine with unlocked bootloader. Just flash Stock recovery !
Q) Do i lose my apps/settings/cache?
Ans) Since its an OTA from HTC, you retain everyhting!
Q) Will i lose my root if i update?
Ans) You will! Thats exactly why you're advised to backup your root.
Q) My updates fails with a red triangle and exclamation mark, what did i do wrong?
Ans) You need to understand that during the update, several stock apps are patched. If any of these STOCK APPS ( the ones that came with ya new phone) are uninstalled/frozen/meddled with, an error will pop up.
Q) How do i identify the cause of the error?
Ans) When the red triangle pops up, press the Volume UP, Volume DOWN and LOCK keys at the same time for a second and release. You should see the cause of your error. Try to restore/unfreeze the app thats causing the error. If that is not possible, try posting your error here to see if experts here can help.
All the stock recoveries can be found on this forum. If however u've a doubt, i'd be happy to help.
This guide is not perfect and may contain errors ( i've tried to make it complete to the best of my knowledge). I'm open to suggestions and questions
Click to expand...
Click to collapse
Hi, thanks for the super explanations - last two really helped me - at least I found the reason why my phone does not want to Updates.
I send thanks to your instructions displayed mistake - I phone from T-Mobile Czech and the application of course I deleted it - it is useless.
Do you know if this can be downloaded somewhere, possibly where I got all this ROM mentioned in the error? I deleted more applications, so it probably will want to install these
I watched a lot of the internet, but I found none.
Sorry for my English ...

Well, if you made a backup if the current Rom/apps, then just extract and install the apps. Or else, I think you can extract the app from ruu if your version. You'll have to do it for each of the apps you uninstalled. That's gonna be a hell of a job, if u ask me.
I think its better you stick to the current software, or of you really wanna update, reset your phone via ruu. And then update.
Sent from my HTC One V using xda app-developers app

[Q] Scenarios around root and OTA updates

Hello,
I've got a couple of scenarios regarding the LG G Pad 8.3 GPE (V510) that I wanted to run passed you. This is based on my understanding on what is required for OTA updates to work properly and basically I just want some confirmation that I'm right, or correction if I'm wrong.
Scenario 1:
- Start with stock android/kernel/recovery etc
- Root device to make backup of platform.xml file and then edit the platform.xml to allow full SD card write access
- When new OTA update becomes available I wait until I can confirm that I can get root access on the new android version
- Then replace my edited platform.xml with the original backup to return all files to stock state
- Download and install OTA update like normal
- Re apply root and SD card write access
This should work, correct?
Scenario 2:
- Start with stock android/kernel/recovery etc
- Root device to make backup of platform.xml file and then edit the platform.xml to allow full SD card write access
- Using stock recovery, flash my kernel to the SleekAI one for gamma, battery life, and other optimisations (http://forum.xda-developers.com/showthread.php?t=2647119)
- When new OTA update becomes available I wait until I can confirm that I can get root access on the new android version
- Use the stock kernel provided on the SleekAI thread to return to stock kernel
- Replace my edited platform.xml with the original backup to return all files to stock state
- Download and install OTA update like normal
- Re apply root and SD card write access
- Reinstall SleekAI kernel
This should also work, correct?
Essentially both are just applying changes that would break OTA updates, and then reversing those changes so everything is stock again (apart from no unrooting) so that the OTA update applies like normal.
Thanks for the help,
OtterNZ

OtterNZ said:
Hello,
I've got a couple of scenarios regarding the LG G Pad 8.3 GPE (V510) that I wanted to run passed you. This is based on my understanding on what is required for OTA updates to work properly and basically I just want some confirmation that I'm right, or correction if I'm wrong.
Scenario 1:
- Start with stock android/kernel/recovery etc
- Root device to make backup of platform.xml file and then edit the platform.xml to allow full SD card write access
- When new OTA update becomes available I wait until I can confirm that I can get root access on the new android version
- Then replace my edited platform.xml with the original backup to return all files to stock state
- Download and install OTA update like normal
- Re apply root and SD card write access
This should work, correct?
Scenario 2:
- Start with stock android/kernel/recovery etc
- Root device to make backup of platform.xml file and then edit the platform.xml to allow full SD card write access
- Using stock recovery, flash my kernel to the SleekAI one for gamma, battery life, and other optimisations (http://forum.xda-developers.com/showthread.php?t=2647119)
- When new OTA update becomes available I wait until I can confirm that I can get root access on the new android version
- Use the stock kernel provided on the SleekAI thread to return to stock kernel
- Replace my edited platform.xml with the original backup to return all files to stock state
- Download and install OTA update like normal
- Re apply root and SD card write access
- Reinstall SleekAI kernel
This should also work, correct?
Essentially both are just applying changes that would break OTA updates, and then reversing those changes so everything is stock again (apart from no unrooting) so that the OTA update applies like normal.
Thanks for the help,
OtterNZ
Click to expand...
Click to collapse
Rather than use the stock image in the kernel thread, make a backup boot image and keep that handy. The stock image in the kernel thread was for the 4.4.2 base that came with the gpad when it first came out, and while it will serve to allow upgrade to 4.4.4, it won't do anybody any good for the next round
There is already a complete image available to flash for update if you want...

sleekmason said:
Rather than use the stock image in the kernel thread, make a backup boot image and keep that handy. The stock image in the kernel thread was for the 4.4.2 base that came with the gpad when it first came out, and while it will serve to allow upgrade to 4.4.4, it won't do anybody any good for the next round
There is already a complete image available to flash for update if you want...
Click to expand...
Click to collapse
I don't have enough posts to be allowed to post to thank you on your kernel thread so...Thank You
Easy to follow instructions, and the yellow tint is less noticeable, making videos seem lighter (although there is still a bit of yellow on my tablet). Got to play around with some of the other kernel features at some point.

Recently updated to A5FMB19

I purchased the tablet online in China about two months ago, so I got a tablet running CN system. (A5CN51C as I got it.)
So I followed a manual and immediately flashed a A5FM51C system.img to my tablet.
When the OTA A5FM91E came, I checked up this forum, only found high risk of updating.
While today, while I consulted a Chinese forum, there is a method to safely update the tablet to a newer version of system without converting back to CN systems ( meanwhile the boot is still lost after updating ! )
Basically, for all who initially has a CN system installed and successfully converted to TW version, there is a way to update your system while keeping all google frameworks.
Method is listed below.
1. Enable developper mode and USB debugging, and connect to PC using adb.
2. Flash the corresponding boot.img and recovery.img to the tablet. (By saying corresponding, it's the boot.img and recovery.img must match the version you're using. For eg, I'm updating from a A5FM51C version, so I should at least have a boot.img and recovery.img of A5FM51C.)
Below you can find the boot.img and recovery.img of A5FM51C.
HTML:
http://pan.baidu.com/s/1gdwKN7P
Password 2jwi
or https://www.dropbox.com/sh/drmfv30k54jgb35/AABc9uPxpOSUNHsV1lSD-k_1a?dl=0
command on adb shell should be like :
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/pci/pci0000:00/0000:00:01.0/by-name/recovery
dd if=/sdcard/boot.img of=/dev/block/pci/pci0000:00/0000:00:01.0/by-name/boot
3. After rebooting once and rebooting into recovery mode, check if the recovery is converted to the targeted version.
As I am updating to a system with Google applications, I should check if the version is marked FM.
4. In the recovery mode, side load the updating zip files, after a patient waiting, the system should be successfully updated.
ATTENTION ! [/SIZE]the zip file should be a full updating file, NOT A PATCH zip. So the file you are side loading is at least 300+ M.
If you are updating from A5FM51C, you can directly download from the links below two files.
HTML:
A5FM91E 848.38M
http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-tw2015/A5FM91E_update.zip
A5FMB19 816.04M
http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-tw2015/A5FMB19_update.zip
5. The first time booting the updated system could be time consuming, so take a cup of coffee and be patient.
All credits should be given to the Baidu Tieba user "遇上咨询", and if you happened to be capable to read Chinese, you can visit http://tieba.baidu.com/p/4174802149 for further consult.
PS.
I updated from A5FM51C firstly to A5FM91E, after once rebooting normally into the system, I then updated again to A5FMB19, just being careful not to cause any damage.
And after updating there could be several applications crash unconditionally, since I've been using the system for less than 24 hours, I am not sure if this situation can be optimised after a period of time.
So the update only brought the Android version to 5.1.1, and Nokia added a "Close all app" button in the overview. Consider again if you are willing to spend one hour to update the tablet into a very similar system !
Wish you luck.

Update
As soon as I finished updating the "System Webview" app to newest version at Play, all those apps started running again

Neegola said:
Update
As soon as I finished updating the "System Webview" app to newest version at Play, all those apps started running again
Click to expand...
Click to collapse
i'm update to A5CNB19 today. How can move Chinese to Taiwan?

thanks for your post, is there any chance to make it rooted in A5FMB19 ??
thanks

p233 said:
i'm update to A5CNB19 today. How can move Chinese to Taiwan?
Click to expand...
Click to collapse
Originally, I converted my tablet at A5CN51C, with root. Following this manual.
http://forum.xda-developers.com/nokia-n1/general/n1-taiwan-release-t3083115/post62313790
So using this method to convert, you should guarantee a valid root state executing DD command on adb shell.
So I personally think that at least you should wait for a root method, then there would be a chance for converting system.

I directly updated from A5FM51C to A5FMB19 (not went through A5FM91E . confirmed it's okie with this method

Thanks a lot. I confirm that we can directly update from A5FM51C to A5FMB19. I just have a question, if an update release can i do the update by the ota ? Sorry for my bad english.

Xiware said:
Thanks a lot. I confirm that we can directly update from A5FM51C to A5FMB19. I just have a question, if an update release can i do the update by the ota ? Sorry for my bad english.
Click to expand...
Click to collapse
After converting the recovery and boot partitions to FM version, there should not be a problem in updating directly by OTA.
Before, when I execute OTA, it will pop up a message read "Could not download the update, please check the storage". And after, I could successfully start the download. It was because the limited network speed, I've chosen to side load the update package.
But it's merely my guess. Since the tablet has at least 20 partitions, and I don't know if there's any other which could influence this process. Maybe we could invite a real expert to join in this discussion.

Are you update with OTA?

gazziandrea said:
Are you update with OTA?
Click to expand...
Click to collapse
No.
But technically I did use the ota package to update. Given it was a whole system compressed file.

Neegola said:
No.
But technically I did use the ota package to update. Given it was a whole system compressed file.
Click to expand...
Click to collapse
I did rootare the devise to other people ( chinese guys) and i dnot have many experience in modding, only with TWRP in Xiaomi Redmi Note 2, so I can update via OTA diretly ?

gazziandrea said:
I did rootare the devise to other people ( chinese guys) and i dnot have many experience in modding, only with TWRP in Xiaomi Redmi Note 2, so I can update via OTA diretly ?
Click to expand...
Click to collapse
Hi, I'm afraid I don't understand what you are asking.
Do you speak any other languages like Chinese or French, or your native language so I can do a google translate ?

Thanks for these updated information.

Hi, guys, thank you for help with moving from CN to TW. I've done this from rooted A5CN51C to A5FMB19.
But, now I've got system reboot every 15 min. Uptime no more than 30-35 min. It's very unstable during watching video (e.g. youtube app). Do you have the same? Model: n1s.
Hard reset doesn't solve this problem.

Flash stock software update through TWRP?

First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.

ast00 said:
First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.
Click to expand...
Click to collapse
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.

sdembiske said:
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.
Click to expand...
Click to collapse
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.

ast00 said:
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.
Click to expand...
Click to collapse
It helps if you include your phone model when looking for specific firmware updates.
If you're Dad's phone is an H815, there are some v20p downloads available here: https://lg-firmwares.com/lg-h815-firmwares/firmwares/
In order to flash in TWRP without losing TWRP, you would have to remove the stock recovery and create a flashable zip ...
Easiest is to simply freeze or remove the lg Software Update app as I indicated - the annoying update notification should then disappear ...
Note: XDA courtesy is to hit the Thanks button (bottom right of post), when members are trying to help and solve your issues. As a Senior Member you know this.

This update does not contain any security fixes it's just for the new European data protection law..
First thing you should try is:
Upgrade TWRP.
Do a full TWRP backup!
Test android update again.
Second thing:
Have you tried the LG bridge windows software to update?
If so and it fails there too you can find the update when you try to Flash it within the LG folder of your Windows PC afterwards use this KDZ file and lgup to flash it.
There is a chance that when using the internal updater that you can find the update file when in TWRP in /cache in a folder fota but it will likely be in a LG specific format so may don't help you much.
Third thing :
Disable the LG updater within TWRP (search for a howto)
Sent from my LG-H815 using XDA Labs