Related
Specs: I had Galaxy Nexus LTE 4.0.4 w/ unlocked bootloader and root access. I have the GN toolkit if that helps.
Cause: I used the Font Installer app to change system font. I now know that not all of the fonts are working properly and emailed the developer about it. However, I am currently stuck in a boot loop after changing to one of the fonts.
I would prefer to not lose everything and if I didn't care about that, then I would just go for it and I think that I could get it working again. But since it was just a font change, I thought it might be possible to fix it without going through all of that. I am hoping I can just change some system files or something and get it to boot then select a different .tff font that I know works. THANKS!
If I reload the 4.04 update.zip that I still can access, will that wipe everything/will I have to re-setup a bunch of things? Is it OK to clear cache partition and Dalvik Cache? Thank you.
Did you take a nandroid backup of this ROM at any point? If so, you could do an advanced restore of system only.
Sent from my Galaxy Nexus using Tapatalk
cmstlist said:
Did you take a nandroid backup of this ROM at any point? If so, you could do an advanced restore of system only.
Click to expand...
Click to collapse
No, unfortunately I did not, but I will look into that once I am back up and running.
**EDIT: I have CWM Recovery v5.5.0.4 running now. Is it possible to do a backup at THIS point in time and then restore everything but system?
Druas said:
No, unfortunately I did not, but I will look into that once I am back up and running.
**EDIT: I have CWM Recovery v5.5.0.4 running now. Is it possible to do a backup at THIS point in time and then only restore system?
Click to expand...
Click to collapse
Okay. In that case, flashing the ROM's update.zip should work and shouldn't wipe your data. Best to take a nandroid backup first, just in case of trouble.
Sent from my Galaxy Nexus using Tapatalk
cmstlist said:
Okay. In that case, flashing the ROM's update.zip should work and shouldn't wipe your data. Best to take a nandroid backup first, just in case of trouble.
Click to expand...
Click to collapse
Ok I made the backup first. When I try to load the update.zip though, it says, "assert failed: appy_patch_check("/system/fonts/Roboto-Regular.ttf" <then a whole BUNCH of numbers and letters which I can type out if they will actually be helpful> "E:Error in /sdcard/Download/update.zip (Status 7) Installation aborted."
Is that an incremental update.zip for upgrading? What you need is a zip containing the entire ROM.
Alternately use fastboot to flash system.img from the stock ROM if you were already using stock.
Sent from my Galaxy Nexus using Tapatalk
cmstlist said:
Is that an incremental update.zip for upgrading? What you need is a zip containing the entire ROM.
Click to expand...
Click to collapse
Yeah I used: http://forum.xda-developers.com/showthread.php?t=1481044 So I need to install 4.0.2 first? Unfortunately that is the only upgrade.zip I have on my phone and I don't know how to load new ones on there without booting into Android.
cmstlist said:
Alternately use fastboot to flash system.i mg from the stock ROM if you were already using stock.
Click to expand...
Click to collapse
What? Can you explain further? I was using stock 4.0.4
Druas said:
Yeah I used: http://forum.xda-developers.com/showthread.php?t=1481044 So I need to install 4.0.2 first? Unfortunately that is the only upgrade.zip I have on my phone and I don't know how to load new ones on there without booting into Android.
What? Can you explain further? I was using stock 4.0.4
Click to expand...
Click to collapse
You can download another zip to your computer and use adb push to get it onto the GN's internal storage.
I don't have the CDMA version but here's what I am able to find. Check this thread:
http://forum.xda-developers.com/showthread.php?t=1481613
A completely stock 4.0.4 (aside from root, busybox, de-odex) from that thread is here:
http://dev-host.org/uMJ
So you download that to your computer and put it in the same folder as adb. Boot the phone into Clockwork Recovery and then plug it into your computer. (There are other guides to getting adb to work on your phone so I won't cover that here.) Run adb devices to make sure it sees your phone. In Clockwork you also have to go to mounts and storage and make sure /data is mounted.
Then:
adb push GalaxyNexusCDMA-4.0.4-StockRootedNoRadio.zip /sdcard/stock.zip
Subsequently in Clockwork, you will be able to find that stock.zip in the list of zips you can apply. After applying that zip, any damage caused by messing with the fonts should be reverted.
---- or ----
The alternative would be to download the factory 4.0.2 image from here:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
Inside that archive is a system.img file which you can flash to the phone by fastboot over USB. Immediately afterwards, you would then boot into CWM and apply the incremental update.zip you already have on there. This will take you to stock 4.0.4 unrooted and hopefully bootable!
cmstlist said:
The alternative would be to download the factory 4.0.2 image from here:
Inside that archive is a system.img file which you can flash to the phone by fastboot over USB. Immediately afterwards, you would then boot into CWM and apply the incremental update.zip you already have on there. This will take you to stock 4.0.4 unrooted and hopefully bootable!
Click to expand...
Click to collapse
While your instructions were good, I tried some things on my own about 20 min before you made that post and screwed up and erased userdata. So, I cannot say for sure if it would have worked, but I bet it would have and I wish I had been more patient.
Sorry to hear. Is it bootable now at least?
The userdata erase problem is why I now have to remember in every phone recovery situation - adb pull the entire contents of internal storage from within CWM before doing anything risky.
Sent from my Galaxy Nexus using Tapatalk
Yeah the phone has booted, I just have to spend some time recovering what I can. I will hopefully make better backups for the future. At least I learned some stuff. I still can't believe this was all caused by changing a FONT in a program designed to change fonts.
Druas said:
Yeah the phone has booted, I just have to spend some time recovering what I can. I will hopefully make better backups for the future. At least I learned some stuff. I still can't believe this was all caused by changing a FONT in a program designed to change fonts.
Click to expand...
Click to collapse
Right, well this font changer program edits the system partition of your phone, which makes it risky. In the future, the best course of action with any "risky" change is:
- Take a nandroid backup first.
- Copy the nandroid backup out of the phone (it's in a subfolder of clockworkmod on internal storage).
- If you are doing anything that leads you to fear that the whole internal storage could get blanked, copy all of that out of the phone too.
- Now if you can't boot, you can selectively restore the system partition or the whole thing to try and fix it.
- And now if your internal storage gets blanked, your backup is safe.
cmstlist said:
Right, well this font changer program edits the system partition of your phone, which makes it risky. In the future, the best course of action with any "risky" change is:
- Take a nandroid backup first.
- Copy the nandroid backup out of the phone (it's in a subfolder of clockworkmod on internal storage).
- If you are doing anything that leads you to fear that the whole internal storage could get blanked, copy all of that out of the phone too.
- Now if you can't boot, you can selectively restore the system partition or the whole thing to try and fix it.
- And now if your internal storage gets blanked, your backup is safe.
Click to expand...
Click to collapse
Yeah I had no idea that there was a significant risk involved, otherwise I would have been more cautious. Some questions I have:
-With Titanium Backup, the only thing I need to be running batch backups of is all user apps + system data correct? And only restore apps not system data unless I am on the exact same ROM as before?
-Again with TB, is there stuff it consistently misses that I should backup manually?
-I always launched CWM Recovery through the GN toolkit using "6. Flash CWM Recovery, Standard." And sometimes I would select Recovery from the Fastboot menu and it would be back at the regular recovery. Is there a different way I should have been going about getting to the nandroid backup?
-I have now installed ROM Manager and hit "Flash CWM Recovery" and I have a nandroid backup when I reboot into recovery. Does this mean any time I choose Recovery from the Fastboot menu that it will boot into CWM Recovery?
Thanks again for all your help and advice!
Dear users,
I recently got the update to 4.2.2 with HTC Sense 5 (i downloaded it of course).
My phone was rooted, so i flashed the stock recovery back. I also had some system bloatware apps removed using Titanium Backup. I also restored them, finally i created an root backup with Voodo Rootkeeper.
The download was complete so it wen't in to "updating" mode. And about half way i get a phone with a red triangle in the center. The update fails.
I have installed Avast! Anti-Theft with Hardreset protection. Do i need to turn that off?
I also have installed some mods, do i need to also delete them?
Btw. Avast! Anti-Theft Hardreset protection has also some files flashed trough CMW Recovery.
What did i do wrong?
I have Nandroid Manager installed.
Which images do i need to restore without losing all my data, and still successfully update my phone to 4.2.2?
Big thanks in advance for all the help!
Tim
First, wrong section. This thread belongs to Q&A...
Removing system apps will certain caused OTA failure, but this should not your case if you had restore them correctly.
Hmm.. did antivirus running when you aplly OTA? Avast! Anti-Theft has nothing to do on failure OTA.
The main culprit most probably be the mods. Most mods changes system/framewark files. Don't try to deleting them directly unless you can identify the changes and revert to the stock version correctly
Also, no one here on xda can tell how many nandroid images you own and when you backup them. The are several ways to get back to stock and applying OTA and non of them will cause the lost of apps data. There are also multiple ways to backup your apps data too. Just remebered don't restore system related data after OTA.
Root backup is not useful for the HTC One X. You need to fully remove root (delete the su binary, the super user apk). I don't know if the mods cause the problem of the update. You may better remove them. I recommend you to backup important datas (telephone, sms...) and then fully wipe your phone. Did you make a nandroid backup before you installed any mods? If yes restore this backup using advanced mode in CWM and only choose system restore. If you don't have the backup, look for RUU suits your phone CID number and Android version and look for tutorials to make your phone completely stock. It's also recommended to remove this Avast thing.
Gesendet von meinem ME172V mit Tapatalk 4
Moved to Q&A.
I don't get why you posted it in General when you even added a [Q] to thread title .
jotha said:
Moved to Q&A.
I don't get why you posted it in General when you even added a [Q] to thread title .
Click to expand...
Click to collapse
I checked the question box
ChiDi9901 said:
Root backup is not useful for the HTC One X. You need to fully remove root (delete the su binary, the super user apk). I don't know if the mods cause the problem of the update. You may better remove them. I recommend you to backup important datas (telephone, sms...) and then fully wipe your phone. Did you make a nandroid backup before you installed any mods? If yes restore this backup using advanced mode in CWM and only choose system restore. If you don't have the backup, look for RUU suits your phone CID number and Android version and look for tutorials to make your phone completely stock. It's also recommended to remove this Avast thing.
Gesendet von meinem ME172V mit Tapatalk 4
Click to expand...
Click to collapse
I'll remove the full root access, can i flash it back after the update?
Yes i made a backup before any mods, will this also remove the SU binary's etc.?
And do i need to remove busybox too?
Thanks,
Tim
EDIT/UPDATE:
It looks like the restore system only in the advanced restore settings did the trick. Thanks for the suggestion!
I'll keep this in mind next time i'm going to flash something. Is there a tool that backups the things that are going to be flashed before the actual mod is flashed?
Thanks,
Tim
Never seen a tool like this. It is really only your job to remember to do a nandroid backup before flashing any mod. This is a must. It is a rule!
Gesendet von meinem ME172V mit Tapatalk 4
I totally agree with that, and i do it all the time. Thanks for the support. Now i'll try to install root again. Keep you updated!!
I think I have the same issue as tim687 ...
I want to revert back to the stock HTC Sense OS.
Before installing CM I made a nandroid backup and now I restored that backup (tried normal backup and system backup in the advanced options).
Now I would like to install the update by HTC, but when installing the update I am getting
E: unkown volume for path [internalsdcard: download/ota_endeavor....[filename}.zip
E: cant mount internalsdcard: download/ota_endeavor....[filename}.zip
Installation aborted.
Any help please?
Flash back the stock HTC recovery. You can't update via a custom recovery !
Sent from my HTC One X using XDA Premium 4 mobile app
I was attempted to install 4.2.2 in my HTC One X phone and the HTC One w/ Beats Audio logo is stuck on the screen. I had a pain to wait to work with the ROM. I always use an original 4.1.1 ROM, and sometimes some apps are stuck while playing The Simpsons Tapped Out and Family Guy The Quest For Stuff.
ApprenPlayer said:
I was attempted to install 4.2.2 in my HTC One X phone and the HTC One w/ Beats Audio logo is stuck on the screen. I had a pain to wait to work with the ROM. I always use an original 4.1.1 ROM, and sometimes some apps are stuck while playing The Simpsons Tapped Out and Family Guy The Quest For Stuff.
Click to expand...
Click to collapse
That's strange I've been running it like that for months or even years
Hi, when I got the phone I rooted it by installing TWP recovery, it was all working fine after that until an OTA update popped up, after some research I learned that in order to install OTA updates you need to install stock recovery. Firstly, not knowing entirely what I was doing I installed the stock recovery for the wrong software version. The phone booted however and I tried to install the OTA update, upon restarting I was met with the "red triangle" error screen. I restarted the phone and it booted up fine.
Then having found the correct stock recovery (4.16.401.10) I installed it and ran the update again. It seemed to be going fine with the loading bars moving along nicely when it got stuck on the HTC bootup logo. From here I restarted it and now the phone turns on, shows the htc logo, then gets stuck on a black screen,
Please help, Thanks.
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
ckpv5 said:
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
Click to expand...
Click to collapse
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
DarwinW said:
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
Click to expand...
Click to collapse
2 options :
1.
In step 8, select dalvik cache, cache, system but don't select data
In step 9, tick only boot & system and don't tick data
or
2.
Make a nandroid backup of your current ROM
Do all the steps, once completed the OTA reinstall TWRP and restore only data from your earlier made nandroid backup
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
DarwinW said:
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
Click to expand...
Click to collapse
That's almost same as option 1 above. You need stock recovery for OTA to work.
Most important is the system part must be stock with nothing changed.
Personally, I always do option 2 to make sure OTA is successfully done .. then restore data.
One thing to note ... you don't need to relock bootloader doing all these process.
Also, now that I've created the backup (stored to the phones storage), how do I transfer that to my PC, since the phone doesn't boot, the computer doesn't recognize the storage.
Thanks.
In TWRP you have option to enable MTP then both your internal storage and microSD can be opened on PC
Make sure to use TWRP 2.8.4.0 or newer or latest. I'm still on TWRP 2.8.6.0
It seems I'm on an older version of twrp (2.7.0.2), I made the backup using this version. If I update to a newer version now will the restore work properly?
Thanks.
Usually yes we can restore a backup made with older TWRP version but I'm not so sure about 2.7.0.2 as that is the buggiest TWRP among all versions but very popular because it is included in one very old and not updated toolkit.
Why don't install latest/newer TWRP then redo the backup then transfer to PC.
I'm having trouble viewing files on my pc, I select "mount" from the main twrp menu, it then shows a screen to select which partitions to mount, I tick them, then nothing happens. There's no button to actually start the mount.
I did mentioned enable MTP function ... see below on the right side you should see Disable MTP or Enable MTP (beside Mount USB Storage) .. not those partitions to mount (but in the same screen)
I think you were right about that version being buggy. Those buttons on the bottom were missing. Just installed the latest twrp and I can mount now as the buttons to mount are showing up. Hopefully all will be fine now
Thanks.
Hi, I'm following the guide now and when I try to wipe the phone it doesn't work, I get:
Wipe Complete
Failed
"Unable to mount /cache
failed to wipe dalvik"
This error repeats a few times.
Thanks.
EDIT** scratch that, sorted it
Horray! Everything has now worked out and my phone is back to it's old self with the update, thank you so much ckpv5! you're the best.
Everyday my m9 asks me to install the new OTA update and I am sure I can't because I am rooted. Have TWRP, and have an unlocked bootloader. While my rom is the default rom the phone came with, I have modified a couple things in /system. Is there way to permanently disable OTAs without installing a custom rom? If not, is there a way to install this update without doing any data wipes or anything overly complicated? Any help would be EXTREMELY appreciated!!
wrozengfx said:
Everyday my m9 asks me to install the new OTA update and I am sure I can't because I am rooted. Have TWRP, and have an unlocked bootloader. While my rom is the default rom the phone came with, I have modified a couple things in /system. Is there way to permanently disable OTAs without installing a custom rom? If not, is there a way to install this update without doing any data wipes or anything overly complicated? Any help would be EXTREMELY appreciated!!
Click to expand...
Click to collapse
All you need is an untouched System and stock recovery to take the OTA.
their are many threads that explain how to do it. Just look around you'll figure it out.
clsA said:
All you need is an untouched System and stock recovery to take the OTA.
their are many threads that explain how to do it. Just look around you'll figure it out.
Click to expand...
Click to collapse
Like I said, my system isn't untouched, I have edited permissions.xml and removed some bloatware. And if I can do this, Will I still be rooted if I update or at least still S-off?
wrozengfx said:
Like I said, my system isn't untouched, I have edited permissions.xml and removed some bloatware. And if I can do this, Will I still be rooted if I update or at least still S-off?
Click to expand...
Click to collapse
Once s-off, you will stay that way unless you manually change it.
You can't be rooted and take an OTA anyway. You have to be 100% stock. You can root again once it's updated.
iElvis said:
Once s-off, you will stay that way unless you manually change it.
You can't be rooted and take an OTA anyway. You have to be 100% stock. You can root again once it's updated.
Click to expand...
Click to collapse
But that other guy just said all I need is a stock recovery. So which is it? 100% stock or just stock recovery
wrozengfx said:
But that other guy just said all I need is a stock recovery. So which is it? 100% stock or just stock recovery
Click to expand...
Click to collapse
Here > http://forum.xda-developers.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354
Steps 3 - 5
and the "other guy" said Untouched System + Stock Recovery
Also worth reading >> http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
6. So what's the proper procedure to root without breaking OTA?
There is no way to take an OTA after you root. However, prior to rooting, you can take a fully untouched system image backup with TWRP, which can be used to restore a fully stock system to the device in order to take an OTA.
7. How do I backup stock recovery prior to flashing TWRP?
You can't. The "fastboot boot" command appears to be disabled on the M9's ABOOT, so TWRP must be fastboot flashed over stock recovery. The firmware zip included in the OTA will include a usable stock recovery image. That can be extracted and flashed after stock system is restored so that the OTA can be applied.
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
Click to expand...
Click to collapse
If you want to disable, try freezing HtcDm.
mike.s said:
If you want to disable, try freezing HtcDm.
Click to expand...
Click to collapse
This helped me out nearly a year later. I am rooted and have a custom stock rom loaded but was still able to download the system update somehow and needed a way so that it would quit bugging me every day to not install it. By using Titanium Backup I was able to freeze 3 HtcDM processes.
Currently I'm using a OnePlus 3 on 6.0.1 (OOS 3.1.1) but I would like to update to Oreo (OOS 5.0). How do I do this when my device is rooted?
I've downloaded the latest OS off the oneplus website. Is it as simple as uninstalling SuperSU and then flashing the latest OS through recovery?
I also have TWRP recovery and Xposed installed.
Would appreciate any help.
Just flash the new OS in recovery, no need to unroot as it will get overwritten anyways. You'll need to root again after updating, of course.
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Just flash the new OS in recovery, no need to unroot as it will get overwritten anyways. You'll need to root again after updating, of course.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
The full zip of oxygen OS will overwrite the TWRP recovery with the stock one?
I can update with the zip in the recovery and root whenever i want or i have to do this at the same time?
Explorer23 said:
Just flash the new OS in recovery, no need to unroot as it will get overwritten anyways. You'll need to root again after updating, of course.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
It's as easy as that? It's not a problem that I have xposed installed or anything?
What should I wipe before I install the new OS?
Sorry for all the questions, newbie here.
@Edo 91
I'm not sure about overwriting recovery, it's been a long time since I've used OOS (currently on PA, before than on LOS). If I remember correctly the recovery should stay if you DON'T boot into system right after flashing. So, flash the ROM, reboot into recovery first, then boot into system. Can't say if anything changed with Oreo, but that's how I remember it from Nougat and Marshmallow. You can however flash recovery again right after ROM, just to be sure.
You can root later down the road, no need to do everything at once.
@scalliant
Generally yes, it as easy as that. Xposed and root methods modify system partition - and that gets overwritten when you flash new ROM. That's why those modifications have to be flashed again after every update (some custom ROMs are exception, but rest assured the stock one will nuke all mods).
Anyways, we're talking about Android version upgrade here and not just a minor system update, so I'd recommend a clean installation (but you can try dirty first and then do a clean one in case you experience issues).
First of all, make a full nandroid backup (check everything except "system image" in TWRP). Copy all of your media content (pictures, videos, music ... whatever you don't wanna lose) to another device - better safe than sorry. Optionally, backup apps with Titanium or something similar.
To do it clean: wipe /system, /data and /cache. That means losing all apps and settings, but you'll keep stuff that was stored on the phone. After successfully booting into system you can restore app backups or install them and set up everything again.
To do it dirty: wipe just /system and /cache. You'll lose just system settings, but will keep apps and everything else. Less hassle, but higher chance of something going south.
Explorer23 said:
@Edo 91
To do it clean: wipe /system, /data and /cache. That means losing all apps and settings, but you'll keep stuff that was stored on the phone. After successfully booting into system you can restore app backups or install them and set up everything again.
Click to expand...
Click to collapse
I thought you loose everything when you do a clean install. So photos and files are preserved using this method? I assume text messages will be lost?
shobuddy said:
I thought you loose everything when you do a clean install. So photos and files are preserved using this method? I assume text messages will be lost?
Click to expand...
Click to collapse
Media is on a (virtually) separate partition and is preserved unless while internal storage is formated. Still, it's never a bad idea to have a backup.
Yes, text messages are lost if not backed up. There are many apps that do that (and can be set to upload to cloud regularly).
Sent from my OnePlus 3 using Tapatalk