Related
Hi guys, sorry for my english
I have a nexus rooted, stock room and cwm installed but i didint recive the ota update to 4.2.2
Its normal?
Enviado desde mi Nexus 7 usando Tapatalk 2
I concur, precisely the same situation, stock ROM, stock kernel but rooted
Have also tried to flash using the downloaded .zip but fails with an error code of 7.
Any ideas guys?
Sent from my Nexus 7 using XDA Premium HD app
AW: I cant recive ota update
It depends on which country you're in. I live in Germany and I still haven't got the update
Sent from my Nexus 7 using xda app-developers app
I live in chile, but the nexus was buy in EEUU
Enviado desde mi Nexus 7 usando Tapatalk 2
UK. Sat next to my sister who had received the update...
Could rooting be causing as problem because that's threw only difference between our devices, besides storage sizes, mine being a 16gb, hers being a 32gb.
I'm sure that won't matter, would it?
Sent from my Nexus 7 using XDA Premium HD app
Force stop and clear data in google play services a couple times. ( I think that's what it is) worked for me.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Numerous threads popping up all over asking the same questions, Mods are going to shut & lock many of these out soon - suggest that one read and use the SEARCH button. My OTA was downloaded already and ready to install but choose to wait 48 hours first.
4.2.2 rollout is for USA / North America now - gradually - and OTA if you are essentially running stock rom & kernel - simple update without losing Apps or data (CWM backup, always, as best practices) - took me 15 minutes from downloading, prep & backup to actual flashing and reboot, etc.
I opted to take a shortcut and went from 4.1.2 directly to 4.2.2 using the zipped, deodexed rooted version w busy box - bootloader stayed on 3.41 running JDQ39 now, smooth. I uninstalled the DSP/Beats Audio/Noozxoide EIZO-rewire audio Apps, just in case - and reinstalled EIZO from Play Store afterward, freeze Chrome browser & switched back on Boat Browser w. Flash Player, OTG mount is working for external USB, etc.
Using N7 from other regions of the world, download using the links here on XDA, check MD5's and then go thru the steps - profit & enjoy.
Just to confirm then, and this will help a lot of other users:
Being on a stock but rooted rom with a stock kernel would make no hindrance to receiving the ota update, and the advice for people experiencing this situation would be to just be patient and wait?
Sent from my Nexus 7 using XDA Premium HD app
licaxda said:
I concur, precisely the same situation, stock ROM, stock kernel but rooted
Have also tried to flash using the downloaded .zip but fails with an error code of 7.
Any ideas guys?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I had same problem, I downloaded stock image of 4.1.2, flashed and found my n7 going in to the bootloop. Downloaded stock image of 4.2.2, flashed and everything is ok. Restored with carbon backup. That is all.
Sent from my Nexus 7 using Tapatalk HD
licaxda said:
Just to confirm then, and this will help a lot of other users:
Being on a stock but rooted rom with a stock kernel would make no hindrance to receiving the ota update, and the advice for people experiencing this situation would be to just be patient and wait?
Click to expand...
Click to collapse
Yes, my N7 was on rooted 4.1.2 factory rom & stock kernel, with minor tweaks for audio, Chrome browser frozen but no major mods otherwise, and the OTA file was downloaded already on the device when I checked yesterday, ready to install. From various threads posted in the last 48 hours, it's a mixed bags - some install easily while others ran into problems, reasons varied & solutions simple to unknown. I opted for a safer approach - reverse some of my tweaks/uninstalled the audio tweaks, unfreeze Chrome, rebooted & then wipe, before using CWM to flash. It was easy, rebooted and up & running in less than 10 minutes, ALL of the apps & data intact and no FC'd.
For (folks in Europe or Asia, etc.) not willing to wait or access to OTA and prepared to do it on your own (thus, taking the risks, however - small, do your backup first and save your data/settings/etc. with CWM or TWRP and Titanium Backup - to a HDD or USB drive (suggested: 8GB & up) or PC - just in case, for restoration in the "unlikely event" that something go wrong.
Here's the XDA-linked Factory IMG 4.2.2 Nakasi file links, either odexed or deodexed (rooted, insecure boot, etc.) that I used - also, download the bootloader zip in post #2 (not required or needed, but in case you needed it or wanted to use it as the latest bootloader) - http://forum.xda-developers.com/showthread.php?t=2148337
Download, check MD5's and transfer to the N7. Next - launch into bootloader (make sure USB debugging is enabled & unknown source is allowed too) and WIPE dalvik cache and cache (2 times or 3 times each) - then selected the zip to flash. Once done, exit & reboot and wait for it to boot up for the 1st. time and allow it to settle for a few minutes. Click Settings & confirmed that I'm on 4.2.2 and check a few Apps for functionality. Let it sit & shutdown, reboot & proceed to restore most of my tweaks, played videos & music, surf the web to reconfirm that it's running smooth - next, do a new baseline CWM Backup.
Of course, YMMV - if it doesn't work for you, re-trace your steps and take your time, do not RUSH. If all else failed, go back to stock first 4.1 or 4.2 - then, update to 4.2.1 in its rooted state - your saved Apps & data, settings, etc. saved to your PC or USB/portable drive will eventually help you "rebuild" - just a matter of time. (If my other 2 HTC's are that easy to update from GB to JB, I would be very, very happy)
Please give credit for "thanks" to "teshxx" for preparing the Roms and refer to that thread for future questions ...
Good Luck to all.
Great information, thanks for the hefty reply, may be worth stickying for a few weeks I'm sure others will have the same questions.
I believe installing Beats audio can screw things up too? Can some one confirm?
Sent from my Nexus 7 using XDA Premium HD app
Hi,
I've just upgraded the OS of my HTC One to 4.4 with Sense 5.5 and rooted the handset.
I took the majority of information and downloads from here:
http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/
while the rooting stuff I grabbed from here:
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
So ok this is my 3rd OS upgrade with root so in a basic sense I did this:
- Updated TWRP to version 2.7.x
- Used TWRP recovery WIPE option to format / (root)
- Installed the 4.4 stock ROM from above link
- TWRP then asked me if I would like to root the device and so I said ok to that
- Booting into the OS everything was fine and I had the SU-Root icon in the Apps menu
I'm not sure what happened if the battery got drained or so but in anycase after a restart the handset was no longer rooted??
As I have the 2.65 SU-ROOT Zip file on my storage partition I went back to TWRP and Install then clicked on the Zip file and re-rooted the device; then wiped the cache and booted back into the OS.
For some reason now the phone isn't able to be rooted at all? I am pretty sure I had similar behavior with Android 4.3, though the initial stock build was absolutely fine.... I think I managed to get from 4.1 to 4.2 successfully.
Will I need to format the handset again then re-install the ROM and re-root or is something else going on which I'm unaware of??
I've also noticed that the device becomes un-rooted each time the battery goes low or dies for some reason... a persistent root would be nice as I have many apps needing full root access; not to mention being able to work with the full Android system too.
Would anyone be able to suggest anything? Thanks!
JohnnySSH said:
Hi,
I've just upgraded the OS of my HTC One to 4.4 with Sense 5.5 and rooted the handset.
I took the majority of information and downloads from here:
http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/
while the rooting stuff I grabbed from here:
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
So ok this is my 3rd OS upgrade with root so in a basic sense I did this:
- Updated TWRP to version 2.7.x
- Used TWRP recovery WIPE option to format / (root)
- Installed the 4.4 stock ROM from above link
- TWRP then asked me if I would like to root the device and so I said ok to that
- Booting into the OS everything was fine and I had the SU-Root icon in the Apps menu
I'm not sure what happened if the battery got drained or so but in anycase after a restart the handset was no longer rooted??
As I have the 2.65 SU-ROOT Zip file on my storage partition I went back to TWRP and Install then clicked on the Zip file and re-rooted the device; then wiped the cache and booted back into the OS.
For some reason now the phone isn't able to be rooted at all? I am pretty sure I had similar behavior with Android 4.3, though the initial stock build was absolutely fine.... I think I managed to get from 4.1 to 4.2 successfully.
Will I need to format the handset again then re-install the ROM and re-root or is something else going on which I'm unaware of??
I've also noticed that the device becomes un-rooted each time the battery goes low or dies for some reason... a persistent root would be nice as I have many apps needing full root access; not to mention being able to work with the full Android system too.
Would anyone be able to suggest anything? Thanks!
Click to expand...
Click to collapse
I think there is an update for supersu
please google it
if yes than move it to your phone and flash it in the recovery
Thanks I managed to find version 1.94 which worked fine:
http://download.chainfire.eu/396/
Ok soo i have the a30 from samsung
And it's rooted using magisk
And i have some questions i will be glad
To hear they answer
1 - how i can fully backup every thing from my wallpaper to the rom itself
2 - is it ok to install a rom that made for deferent
Country like the new samsung update with android 10 and one ui 2.0 the Chinese version
3 - can i relock my boot loader and get every thing back to normal i have the original rom
And it for my country
4 - i want to install the TWRP
What is the best way to install it
My baseband A305FXXU2ASF3
And thats all thanks
Note :- my English is not that good soo try to imagine
And i am from Egypt
1. For full backup open TWRP recovery and select backup option. Tick system,data and everything (for full backup).
System and data is necessary.
2.i installed chinese rom android 10 one but somehow i can't able to flash it. Give a try to hongkong one and lete know if it is successfully flashed. Before flashing via odin plz unlock bootloader and usb debugging option.
3.yes you can relock bootloader (let me know if you wanna know more)
4.my phone is not rooted since i use too much banking and upi and its bootloader is unlocked. A latest version of TWRP should be considered to install if it has minimal bug.
Hope you like it.
Updating from an update fileI have been seeing a lot of posts about people not receiving the OTA on their phone, and got tired of linking my instructions, so I decided to make a separate post
Download the version that you need from the Asus Zenfone 8 Support page (Note that if you are not on the latest Android 11 firmware (30.12.112.72), you will not be able to Android 12. So you need to do these steps with the latest Android 11, and then re-do them for the Android 12 firmware)
Plug in your phone to your computer, make sure the computer is trusted and that you can transfer files from the PC to the phone.
Move the zip file of the update in the base directory of the phone (The same directory as Alarms, Downloads, etc).
Wait for the transfer to finish, then you can unplug your phone if you want.
Reboot the phone
After the reboot, the phone will take a few seconds/minutes and will notify you that an update file was found, select the option to update the phone
It will then extract the update and install it all by itself, the normal update procedure starts from there
not work for me :/
I've spent a couple of hours yesterday to get this thing working. Basically, the Android 12 update will only update from specific image. I will try to describe the whole process below.
You have to do this process to upgrade all the way up to 30.12.112.7. If you have anything else, it won't work.
First, I've reverted back to stock, using
WW-ZS590KS-31.0803.0403.54-user_20210831-release.zip
... which contains the full flash scripts.
In my case, I had to do these delta upgrades manually (so copying the zip to root of sdcard memory).
UL-I006D-ASUS-30.12.112.56-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.62-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.72-1.1.31-user.zip
UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip
Number 4 is actual android 12 update. Hope this helps anyone.
eVen123 said:
I've spent a couple of hours yesterday to get this thing working. Basically, the Android 12 update will only update from specific image. I will try to describe the whole process below.
You have to do this process to upgrade all the way up to 30.12.112.7. If you have anything else, it won't work.
First, I've reverted back to stock, using
WW-ZS590KS-31.0803.0403.54-user_20210831-release.zip
... which contains the full flash scripts.
In my case, I had to do these delta upgrades manually (so copying the zip to root of sdcard memory).
UL-I006D-ASUS-30.12.112.56-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.62-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.72-1.1.31-user.zip
UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip
Number 4 is actual android 12 update. Hope this helps anyone.
Click to expand...
Click to collapse
I think that what is needed is to update to the latest firmware, then Android 12. So if you are already on Android 11, but not latest firmware, install it with the instructions, then do the same to update to Android 12's latest version.
drum94 said:
not work for me :/
Click to expand...
Click to collapse
What part does not work? Please be more specific and also, you should re-read the steps more carefully, in case you missed something
The android version I currently have is 30.12.112.72
I downloaded version 31.1004.0404.81 from the asus site to have android 12 on my zenfone 8.
I copied the folder without extracting it and put it in my phone's internal storage next to the other folders.
Once the copy was finished I restarted my phone so that it offered me the update but it did not offer it to me.
I do not understand why .
drum94 said:
The android version I currently have is 30.12.112.72
I downloaded version 31.1004.0404.81 from the asus site to have android 12 on my zenfone 8.
I copied the folder without extracting it and put it in my phone's internal storage next to the other folders.
Once the copy was finished I restarted my phone so that it offered me the update but it did not offer it to me.
I do not understand why .
Click to expand...
Click to collapse
It also depends what prefix your installation has. See the first letters
UL-...
If you are from some other region, it could be that UL- is not a fitting upgrade option for you. As far as I can tell, it's not possible to tell which of the versions you have.
I give you the build number which is marked in the software information:
RKQ1.2021022.002.30.12.112.72
I have the right version or not suddenly?
Thank you for the quick tutorial. I was doing this via fastboot till now.
However: I upgraded to the latest firmware BEFORE Android 12. No issues.
Then I upgraded to the Android 12 firmware: stuck. Gave me some kind of ram dump, reboot returned me to the same error: bootloop. I was able to reboot and get to the bootloader. After selecting "recovery" it actually booted Android. And now for the weird part: it looks like I have a mix of Android 11 and Android 12 now! The phone is all but unusable for how slow it is. But the main UI looks like Android 11 still, but things like the reboot screen now look like Android 12. Bizarre...
I was at least able to enable ADB debug again, so I think I will be able to recover the phone. Still a weird issue though. Don't know if flashing with fastboot would have prevented it...
If anything fails, you can always try the Asus flash script it will solve most of the issues with your phone, just note that it installs Android 11 (30.11.51.115)
https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/
EDIT: nvm, I saw your other reply, you alreay tried that. Were you able to get it working again?
Going from WW-30.12.112.82 to WW-31.1004.0404.107 worked flawlessly, i did not lose settings or data on that upgrade (but I want to stress that a good backup is STILL a very good thing to have!) It then started downloading the 31.1010.0410.43 upgrade on its own. (shown in the ui as SKQ1.210821.001.31.1010.0410.43)
Why didn't I upgrade to the latest one myself? Simple: I goofed up and downloaded the older one.
change the name in UL-ASUS_I006D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Hi, has anyone tried to upgrade a firmware that has Magisk and TWRP installed? Today Android 13 has been released for the Zenfone 8, but I wouldn't really like to do something really dumb such as upgrading, rebooting to recovery to reinstall Magisk only to discover that TWRP has been replaced by the stock recovery and the phone completely erases any data it has stored.
You can update by putting the fw in sdcard folder, while keeping magisk (you need to restore images before updating and reinstalling magisk in the inactive slot after updating, then reboot). Otherwise, you can just update through system or through twrp, and after that, boot/flash twrp and install magisk again. In both ways you won't lose any data
Rokcy98 said:
You can update by putting the fw in sdcard folder, while keeping magisk (you need to restore images before updating and reinstalling magisk in the inactive slot after updating, then reboot). Otherwise, you can just update through system or through twrp, and after that, boot/flash twrp and install magisk again. In both ways you won't lose any data
Click to expand...
Click to collapse
Thank you! As this is my first phone with A/B slots, I wasn't completely sure about how to proceed. I'll follow your instructions! The only thing I don't get is where is TWRP stored and why it won't be overwritten by the update.
EDIT: installed successfully, thanks!
Help - my S20FE is driving me to the point where I'll reactivate my 15 year old nokia...
Here's what I have:
S20FE (german t-mobile, SM-G780G DS), latest OS image (G780GXXU3DVK5), rooted with the latest Magisk version.
What I'm experiencing: the UI freezes up, then eventually restarts, every 5 to 10 minutes. Visually the only indication that it's not an actual reboot is the fact that it goes directly to the screen that only has "SAMSUNG" on it, without the screen with the "bootloader is unlocked" warning that you'd normally see first.
I'm pretty sure it is not a hardware issue, when it first started I did a full wipe / reflash, and then the phone worked fine for about a week or two, now it's doing it again.
Is there ANY way to actually see WHAT is crashing, and maybe even why? I already wiped the cache of that oneUI, and the whole cache from recovery, that did not help.
I guess I'm the only one here who has a S20FE.
Hi, did you manage to solve the issue? I'm currently on Android 11 One UI 3.1 but thinking about updating but I want to know everything first. I was reading that you can update without loosing root but I want to know that is safe first.
I am not completely sure yet but I believe I have it narrowed down to two apps.
I actually went back to the previous major version which was a pain all in itself, it's not easy to find downloads for older Samsung images... anyway, I am back on Android 12, and one UI 4.1, when the crashes start again....
eventually, I uninstalled greenify and kde-connect and the crashes have stopped so far.
kaliko1991 said:
Hi, did you manage to solve the issue? I'm currently on Android 11 One UI 3.1 but thinking about updating but I want to know everything first. I was reading that you can update without loosing root but I want to know that is safe first.
Click to expand...
Click to collapse
I have done updates w/o loosing root or data on magisk-rooted samsung devices, but it is a manual process.
1. use samfirm or frija to get the latest rom image zipfile for your device
2. unpack the firmware zip, you'll get 5 image files.
3. update the magisk app on your device
4. out of the 5 files from the firmware zip, copy the one that starts with AP_ to your device
5. use the magisk app on your device to apply magisk to that file
6. copy the file resulting in that patch back to your computer
up to here the process is the same as the initial install of magisk on a samsung, minus the unlocking of the bootloader.
7. get your device into download mode, and use odin to flash all four parts (BL, CP, AP, and this is important HOME_CSC). by flashing HOME_CSC instead of CSC into the appropriate slot you retain all user data!!
So far this was worked for me on a Tab S2, and a S20fe. Haven't tried on any other yet. YMMV.
I did everything just as described and I'm currently with a boot loop and eventually boots into stock recovery and ask me to do a factory reset. I guess it's over then, I'm loosing all my data.