Help! I have just installed the Android 4.3 update on my Nexus 7 which is rooted with a vanilla kernel with TWRP installed. It rebooted after the update and it booted straight into TWRP so I rebooted again and then it booted into Android as normal but the OS is still on 4.2.2 and not 4.3. I have tried going into About This Tablet then pressing Update and its saying its not on the latest version... Help!
The update will fail if you're not running the stock kernel. Flash it back, or just flash a complete factory image.
Related
Phone: Samsung Galaxy S4 ATT I337UCUAMDL
Model Number in settings on 4.4 ROM = GT-I9505G
As the title says, I installed dandroid's newest 4.4 ROM from WICKED v5 4.2.2 and lost root. So I attempted to update my CWM Recovery from Odus 1x to the newest using Odin which failed do to write protected I suppose all though others says that doesnt effect their installs.
Where I'm at:
Cannot boot into recovery, says booting recovery the just reboots and enters Dandroid's ROM w/o root.
I'm now lost and have been reading the forums for hours. Currently downloading STOCK Samsung firmware for my device I337UCUAMDL_I337ATTAMDL_ATT.zip
CASUAL failed.
What do I need to do to get back to WORKING custom recovery w/ rooted dandriod 4.4 kitkat rom. Should I use Odin and flash stock rom then motochopper to root and try to reinstall working CWM recovery?
Please advise best course of action. My phone had been working properly with every ROM I tried before update to 4.4 ROM and attempted CWM recovery update (thinking that would fix my root issue). Thanks all!
If you have a nandroid, and I hope you do, just restore that in your custom recovery. If you don't, then you're going to have to return to stock with odin
Tried motochopper on the phone as it sits and it fails as well.
I have a stock backup but the problem is I no longer have access to any recovery. Guess I'm just gonna have to flash the stock firmware with Odin when its finished downloading and start over.
Just finished Odin flash back to samsung factory firmware. Phone stuck at att world logo on bootup, still can't access recovery. Any ideas?
GSXRspike said:
Just finished Odin flash back to samsung factory firmware. Phone stuck at att world logo on bootup, still can't access recovery. Any ideas?
Click to expand...
Click to collapse
If you flashed Odin successfully you can get into recovery.
Finally got into recovery it rebooted 3 times but just holding the req. buttons finally got me in.
Back on factory firmware and rooted w/ cwm recovery all back in place properly worrking.
I would like to use the Dandroid 4.4 ROM with this device. When I install am I going to lose root again and if so, how I do I get it back on this device since the model in the settings is going to change from I337 to I9505G after installing this ROM?
Figured it all out last night, re-flashed Dandroid's latest ROM which still caused me to loose root, then flashed SuperSU 1.51 instead of 1.80 and regained root. All is right in the world now.
GSXRspike said:
Figured it all out last night, re-flashed Dandroid's latest ROM which still caused me to loose root, then flashed SuperSU 1.51 instead of 1.80 and regained root. All is right in the world now.
Click to expand...
Click to collapse
Hey, if you dont mind me asking where did you get the 1.51 zip to flash? I'm having a similar issues with same ROM where i lost root but have recovery access.
Thanks
Update: Found the file. Flashed it. Root is back. Have you let market update it automatically? If so did you lose root afterwords?
I'm having difficulties updating from 4.3 to 4.4.
So, bear with me as I am a noob at this stuff, but when I got my Nexus, I rooted and flashed LTE onto the phone. I did not install TWRP, I just did a temporary custom recovery. Now, when I receive the OTA update, it stops around 25% of the way through, with an Error! and the red yield sign and the Android laying on its side.
I reset my phone, however, that didn't do anything. I think I have to undo the LTE before 4.4 can install. Maybe.
Could anyone offer suggestions/help me with this?
Thanks in advance.
To make the OTA update work you have to be unrooted running stock kernel and stock recovery. Otherwise you will get an error when updating OTA. First backup all your files to a computer.
- Download 4.4 custom ROM and flash it via recovery. Make sure to flash the latest boot loader and kernel.
OR
- Download stock 4.4 image file; unzip and run the flash all file. This will wipe everything in your phone and install stock 4.4.
OR
- Download N4 toolkit and flash 4.4 via that.
Sent from my Nexus 4 using Tapatalk
For the life of me I cant get 4.4.2 to install/boot on my nexus 7 2012 wifi
Wondering if there is a stock rooted zip out there so i can just flash it and be done with it.
Ive:
wiped
locked/unlocked bootloader
flashed the stock image (installs/boots but doesnt start) 'com.google.settings' fails at start.
flashed 4.4 image and tried to update via OTA (fails)
flash 4.4 and tried to sideload the update in stock recovery (failed, unexpected contents in system/google email)
flash 4.4 and tried to install update viz TWRP...failed
running out of ideas. My last hope is a 4,4,2 stock rooted rom i can just flash via twrp. but there doent seem to be one.
found one for my n10/n5, but not my n7 (2012 wifi)
any leads?
I am on 5.0.1 rooted with stock ROM and stock kernel. I recently got 5.1 upgrade notification.
After downloading the data and restarting the phone, it started installing updates and after a while it showed "error" and stopped.
Now I m on 5.0.1 with no 5.1 upgrade notice.
What is wrong and what should I do for this?
Thank you.
Do I need to unroot? I am on stock kernel and ROM.
mike_24_11 said:
Do I need to unroot? I am on stock kernel and ROM.
Click to expand...
Click to collapse
Yes, you need to unroot before you can apply the OTA upgrade. Look for the Nexus Root Toolkit, and it should be able to clean up for you.
But prior I didn't need to unroot to upgrade anytime! To upgrade JB to KK or KK to LP, I didn't unroot before installation.
you need stock recovery to update via OTA
Yeah I was on pure stock. Stock ROM kernel and recovery.
Btw, I unrooted my phone with simply unroot and then OTA update went well.
So now I am on stock 5.1 unrooted.
Thank u all.
i have troubles as well. i unrooted, installed stock recovery (via n4 toolkit) and tryed to install. it takes longer then before but i stell get an error. SuperSU is gone in my app drawer.. any other help?
PS: i am on stock rom 5.0.1
i tryed to use sideload ADB update. it says: "/system/bin/app_process32" has unexpected contents. Error in sideload/package.zip. Status 7
any tipps?
I have a Nexus 4 (8GB version), unrooted. I had 5.1.1 running on it, which was flashed manually as the OTA update failed. After having some stability issues I decided to perform a "clean" flash to "start from scratch". So I tryed flashing 5.1.1 and... It ended up in a bootloop (boot animation going on for ever). So I tryed to flash other versions, but everything above 4.4.2 is not working. I first flashed with the "flash-all" scripts (under Window 7 and under Linux), and now am using the "SkipSoft Android Toolkit". So this is how it looks like:
-4.2.2 flash successfull.
-4.3 flash successfull. The phone detects OTA update to 4.4, but the update fails - I get android lying on its back with a red explanation mark. After that, the phone reboots to 4.2.2.
-4.4 flash successfull. The phone detects OTA update to 4.4.2, but the download fails.
-4.4.2 flash successfull. The phone detects OTA update to 4.4.3, but the update fails - I get android lying on its back with a red explanation mark. After that, the phone reboots to 4.4.2.
-Flashing to 4.4.3 and 4.4.4 fails as the phone does not pass the "Google"-sign (before the boot animation).
-Flashing to 5.x fails as the phone end up in a bootloop. I tryed to wipe system/cache after installing, but it does not help.
Sideload of OTAs fails with "Status 7" error, which is strange because I flash stock ROMs. So everything higher then 4.4.2 cannot be installed.
Is there a way to fix this? Getting OTAs to work (even by sideload) would be a start. Or is it a hardware problem and the phone is hopeless?
I hope someone has an answer or at least a direction to dig into.
Thanks
Pavel