Related
How to get Stock kernel back to get nexus 7 ota updates
i once used DR BEATS audio mod it is not installed now but still i cannot install OTA update which i still repent installing that mod
The easiest way for you would be to do the update manually:
- Get the factory image and extract the following files:
- bootloader-grouper-4.23.img
- boot.img
- system.img
If you want to keep root, get
- UPDATE-SuperSU-v1.51.zip
and copy it to /sdcard and be sure, that you have a custom recovery installed.
Do a nandroid backup before starting and then do a
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
reboot into recovery and flash UPDATE-SuperSU-v1.51.zip
Do a reboot system and, congrats, you should be on Android 4.3 without loosing any data.
AndDiSa said:
The easiest way for you would be to do the update manually:
- Get the factory image and extract the following files:
- bootloader-grouper-4.23.img
- boot.img
- system.img
If you want to keep root, get
- UPDATE-SuperSU-v1.51.zip
and copy it to /sdcard and be sure, that you have a custom recovery installed.
Do a nandroid backup before starting and then do a
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
reboot into recovery and flash UPDATE-SuperSU-v1.51.zip
Do a reboot system and, congrats, you should be on Android 4.3 without loosing any data.
Click to expand...
Click to collapse
Can you guide me how to fastboot flash is it in cwm custom recovery or i need to do that with wugfresh toolkit
Sent from my Nexus 7 using Tapatalk HD
Neither you need a PC to do it. Read about both adb and fastboot instead of having everything spoon fed. That way when something goes wrong you have some idea what to do.
Sent from my Nexus 7 using Tapatalk 4 Beta
Hi all,
on my Nexus 9, update to LRX21Q failed: After reboot, the android icon was shown with "error" below.
I suppose, update failed as my system is rooted with the method Chainfire posted in the development forum.
After an additional reboot, the previous firmware is still shown. The system does not offer the update anymore but claims to be up-to-date.
Any hints? Thanks in advance.
Maybe it's the modified kernel from Chainfire. Try to get back to the stock kernel and try again.
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
I got the same error from OTA with no root. Only had 9 for 2 days, got OTA rite out of box no issue.
Yesterday for new build i get little error android icon upon reboot/install.
Obviously, something that is being changed by the "root" process is being checked DURING the update process. Probably a checksum on the boot partition. If it doesn't match, it bails on the update.
The likely reason for this is they acknowledge that you don't want to lose your root.
All it means is that you need to do the update manually.
It may be possible for a modified recovery to bypass this check, or possibly even be made to auto-root new boot images.
Thanks, guys. Will try as suggest above and post results.
Update: worked perfectly, needed to root again though.
StuMcBill said:
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
Click to expand...
Click to collapse
has anyone tried this? i would like to update without losing data...
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
mk92595 said:
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
Click to expand...
Click to collapse
What's the fastboot command for the img? Do you flash as boot, system, etc?
zeebone said:
What's the fastboot command for the img? Do you flash as boot, system, etc?
Click to expand...
Click to collapse
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
mk92595 said:
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
Click to expand...
Click to collapse
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
pantmunu said:
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
Click to expand...
Click to collapse
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
mk92595 said:
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
Click to expand...
Click to collapse
Thank you sir .
Where can i find the images for download. Thx
Google for nexus factory image.
Sent from my Nexus 9 using XDA Premium HD app
Update failed on me too. Completely stock
UPDATE:
Apparently *some* devices didn't get the recovery updated with the last update (LRX21L).
The new update (LRX21Q) requires the newer version of the recovery to install.
Google really messed up the launch of the Nexus 9 with all the HW/SW quality control issues
Serious f#ck-up from Google really
Interesting thing I noticed: I restored factory images manually in order to unroot and the OTA was no longer available. I verified I was still running on L. I manually installed the update and it went in just fine.
Now waiting on the root package to be updated for the Q kernel. You can re-root but you will be running on the L kernel, not the Q kernel.
maarten08 said:
Update failed on me too. Completely stock
Click to expand...
Click to collapse
My too fck Google
Mine failed and Im not even rooted
And im not sure if it did the update as its not showing a new one. Im on L
I am looking for a clear explanation of how to flash Android 6.0.1 with root and encryption disabled without wiping data. With all the explanations through the forum, all the "if's" and "but's" get confusing and can be clear as mud. Thanks for your help.
i'm on 6.0 with a stock kernel with encryption disabled and an unlocked bootloader as well.
As far as i can tell you need 2 things.. Flash the System.IMG manually and then we need to wait for someone to post a modified stock 6.0.1 kernel that has encryption disabled too. you can get away with just flashing system.IMG and stay on your older 6.0 de encrypted kernel but I have seen online that wonky things happen when you dont stay up to date on your kernel sometimes.
I
nextelbuddy said:
i'm on 6.0 with a stock kernel with encryption disabled and an unlocked bootloader as well.
As far as i can tell you need 2 things.. Flash the System.IMG manually and then we need to wait for someone to post a modified stock 6.0.1 kernel that has encryption disabled too. you can get away with just flashing system.IMG and stay on your older 6.0 de encrypted kernel but I have seen online that wonky things happen when you dont stay up to date on your kernel sometimes.
I
Click to expand...
Click to collapse
I know there is a new boot.img file that has encryption disabled but I'm not sure how or where to install it properly.
how_to_flash_update_images_without_wiping_data
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
ShaunWinSC said:
I know there is a new boot.img file that has encryption disabled but I'm not sure how or where to install it properly.
Click to expand...
Click to collapse
Where did you find or see this new 6.0.1 modified boot.img that has encryption disabled?
all you need is wugfresh tool kit and go into the Advanced settings and choose to flash individual files. and flash the boot.img to your device.
so flash the 6.0.1 system.img first and then flash the 6.0.1 modified boot.img 2nd.
remember that when you flash anything from fastboot, after the item is finished, the device reboots so you need to watch the device and have your fingers prepared to hold down power and volume down so the device goes back into fastboot and doesnt start booting again on its own.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
Ovrclck said:
how_to_flash_update_images_without_wiping_data
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
Click to expand...
Click to collapse
that works too!
now just to find the modified 6.0.1 boot.img that has encryption disabled.
nextelbuddy said:
Where did you find or see this new 6.0.1 modified boot.img that has encryption disabled?
all you need is wugfresh tool kit and go into the Advanced settings and choose to flash individual files. and flash the boot.img to your device.
so flash the 6.0.1 system.img first and then flash the 6.0.1 modified boot.img 2nd.
remember that when you flash anything from fastboot, after the item is finished, the device reboots so you need to watch the device and have your fingers prepared to hold down power and volume down so the device goes back into fastboot and doesnt start booting again on its own.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
that works too!
now just to find the modified 6.0.1 boot.img that has encryption disabled.
Click to expand...
Click to collapse
Doughnut643 posted it in Android 6.0.1 thread, post #61.
https://www.dropbox.com/s/la4c6f8o5z...e-new.img?dl=0
It's been my understanding that Wug Fresh Tool Kit has been having some issues.
What about recovery, will it have to re-flashed? And what about root?
ShaunWinSC said:
Doughnut643 posted it in Android 6.0.1 thread, post #61.
https://www.dropbox.com/s/la4c6f8o5z...e-new.img?dl=0
It's been my understanding that Wug Fresh Tool Kit has been having some issues.
What about recovery, will it have to re-flashed? And what about root?
Click to expand...
Click to collapse
your recovery should remain as long as oy only flash the system.img and boot.img. you will need to reroot but I cant help you there unfortunately as I am not rooted myself since I need Androidpay to work.
i h avent had any issues with wugfrsh tool kit but if anything you dont have to use it. you can just go to the wugfresh tool kit folder and run the ADB and manually flash with the flash commands manually.
nextelbuddy said:
your recovery should remain as long as oy only flash the system.img and boot.img. you will need to reroot but I cant help you there unfortunately as I am not rooted myself since I need Androidpay to work.
i h avent had any issues with wugfrsh tool kit but if anything you dont have to use it. you can just go to the wugfresh tool kit folder and run the ADB and manually flash with the flash commands manually.
Click to expand...
Click to collapse
So you don't think I will need flash TWRP after flashing everthing.
I am hoping enough people chime in on how to do this so I can make a clear set of instructions.
I will let you know in a few min.
I just finished flashing 6.0.1 system.img, bootloader.img, cache.img, modified boot.img you posted and the device is at the android is upgrading screen.
if its successful, I will reboot into my recovery which had TWRP previously. if thats good i will let you know.
---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------
ShaunWinSC said:
So you don't think I will need flash TWRP after flashing everthing.
I am hoping enough people chime in on how to do this so I can make a clear set of instructions.
Click to expand...
Click to collapse
so I have one problem now.
when My device fully boots up it now says :
"there's an internal problem with your device"
the only reference I can find to this is in regards to the Nexus 9 and flashing the Vendor.IMG file but nothing for phone devices.
any one know anything about this?
I h ave a feeling its because i flashed the stock 6.0.1 bootloader.IMG over my modified bootloader.IMG and I have TWRP installed AND a modified boot.img...
if i could find a new modified bootloader.img for 6.0.1 that would be awesome.
BTW my TWRP is still installed and launches fine.
nextelbuddy said:
I will let you know in a few min.
I just finished flashing 6.0.1 system.img, bootloader.img, cache.img, modified boot.img you posted and the device is at the android is upgrading screen.
if its successful, I will reboot into my recovery which had TWRP previously. if thats good i will let you know.
---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------
so I have one problem now.
when My device fully boots up it now says :
"there's an internal problem with your device"
the only reference I can find to this is in regards to the Nexus 9 and flashing the Vendor.IMG file but nothing for phone devices.
any one know anything about this?
I h ave a feeling its because i flashed the stock 6.0.1 bootloader.IMG over my modified bootloader.IMG and I have TWRP installed AND a modified boot.img...
if i could find a new modified bootloader.img for 6.0.1 that would be awesome.
BTW my TWRP is still installed and launches fine.
Click to expand...
Click to collapse
Have u flashed vendor.img ???
That's probably the problem :silly:
kauemelhado said:
Have u flashed vendor.img ???
That's probably the problem :silly:
Click to expand...
Click to collapse
I did not. i thought that was only for the nexus 9 since the toolkit had that button disabled unless I set my device to Nexus 9. i flashed vendor.IMG and good to go now thanks lol
nextelbuddy said:
I did not. i thought that was only for the nexus 9 since the toolkit had that button disabled unless I set my device to Nexus 9. i flashed vendor.IMG and good to go now thanks lol
Click to expand...
Click to collapse
I saw a yt video today (https://www.youtube.com/watch?v=i6Gpi1ruLgM)
He showed that if you don't flash vendor.img, you'll get this error message
kauemelhado said:
I saw a yt video today (https://www.youtube.com/watch?v=i6Gpi1ruLgM)
He showed that if you don't flash vendor.img, you'll get this error message
Click to expand...
Click to collapse
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
I have flashed these three Files via the readme commands(fastboot flashing) and did not have my data partition wiped. and now FC's on ubermallow custom rom.
nextelbuddy said:
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
Click to expand...
Click to collapse
Some people are having this problem with EX kernel. But I guess the kernel is not the problem.
I'll flash the update later on today, then i'll tell you how that work for me hehe
nextelbuddy said:
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
Click to expand...
Click to collapse
I flashed all the imgs last night (had some troubles with being dumb installing twrp :silly:
But other than that, everything works perfeclty. LTE is fine. (here in brazil at least)
I'm currently on Stock 6.0.1 + EX Kernel + SuperSu 2.61
kauemelhado said:
I flashed all the imgs last night (had some troubles with being dumb installing twrp :silly:
But other than that, everything works perfeclty. LTE is fine. (here in brazil at least)
I'm currently on Stock 6.0.1 + EX Kernel + SuperSu 2.61
Click to expand...
Click to collapse
Nice, how did you made it? Did you leave the recovery.img?
Martini3001 said:
Nice, how did you made it? Did you leave the recovery.img?
Click to expand...
Click to collapse
I flashed stock recovery and later on flashed twrp.
I was getting the android of death when booting into TWRP.
So, I did this:
-fasboot flash recovery *twrp*
-fastboot reboot-bootloader
*on your fone* using the volume buttons search for "RECOVERY"
-boot into recovery
-thank me!
lololol
I am facing the same problem. After flashing the files manually as below -
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
I rebooted the phone into bootloader and flashed TWRP. After flashing I could boot into TWRP, but if I reboot and try to boot into TWRP little android guy appears.
What am I doing wrong?
MPAI said:
I am facing the same problem. After flashing the files manually as below -
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
I rebooted the phone into bootloader and flashed TWRP. After flashing I could boot into TWRP, but if I reboot and try to boot into TWRP little android guy appears.
What am I doing wrong?
Click to expand...
Click to collapse
after you flash TWRP, if you reboot, the system will flash the stock recovery back if its not the original
after u flash TWRP, u need to boot into recovery, and then flash the expected SuperSU.zip
the supersu zip script will edit the system and disable the flashing of stock recovery
Hi guys
I forget to do a nandroid backup accidentally before test a build of cm12.1 that i make, the problem now installation stuck at 90%, and no progress after that, many tries on internal and external sdcard and with 2 different firmware, (perhaps was for dual sim verison) any solution for that before bring to assistance?
P.S: each day did new progress for cm12.1, hope to got booted rom.
Can't you flash the B052 version with Fastboot?
https://mega.nz/#!lEcGQZCC!X2fmOZ-ShY-Kx-9lwnSUN16Vo52_aU0i4K1KmdBW64Q
Normally you will then be on stock boot, recovery and system images.
olrak said:
Can't you flash the B052 version with Fastboot?
https://mega.nz/#!lEcGQZCC!X2fmOZ-ShY-Kx-9lwnSUN16Vo52_aU0i4K1KmdBW64Q
Normally you will then be on stock boot, recovery and system images.
Click to expand...
Click to collapse
Yes fastboot is working, will report if work, with the following order?
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
???
services in italy are really slow like one month for a stupid reparation.
No, all the commands are normally in a FLASH-ALL.bat file (yeah windows )
Commands are:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash cust cust.img
mfastboot flash system system.img
olrak said:
No, all the commands are normally in a FLASH-ALL.bat file (yeah windows )
Commands are:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash cust cust.img
mfastboot flash system system.img
Click to expand...
Click to collapse
alright, so should use mfastboot instead of fastboot?
Problem solved, thanx a lot :good::good::good::good::good:
hows your progress on that cm12.1 build that youre workin on?
ruben parra said:
hows your progress on that cm12.1 build that youre workin on?
Click to expand...
Click to collapse
i got progress on boot.img, we have hope
haky 86 said:
i got progress on boot.img, we have hope
Click to expand...
Click to collapse
Good luck man , I hope we get a custom rom soon
AmINoS007 said:
Good luck man , I hope we get a custom rom soon
Click to expand...
Click to collapse
I almost finish a cm-12.1 and doesn't boot due to blobs issue and still cannot copy them to the build :/
Probs
Hi everyone
What can I do to upgrade from b052 (after flash with fastboot ) because this Rom cause too much problems to my Huawei p8 lite so if you have a link for download an upgrade to replace B052
Then
haky 86 said:
Problem solved, thanx a lot :good::good::good::good::good:
Click to expand...
Click to collapse
Then did you uptade you're android system?is it possible to install new firmware from B052
as the tittle says... i am soft-bricked, stuck on google animation.. I did a install of the full android rom 1.4 from zulu99 and everything worked like a champ but i wanted to go back to stock for the kids and now i am stuck
I can access fastboot and recovery on the device and compute recognizes it also..
I downloaded the stock image for marsh 3.2.0 and i flashed all the required files:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
it reboots and goes to the google animation and it just stays there!!!(left it there for a day!!!) i also tried to flashing fastboot flash tegra210-foster-e-p2530-0930-e02-00.dtb and did not fix it..
also tried to flash 3.1.0 same steps and no go... i know my adb files are up to date... any ideas?
I was able to flash full android 1.4 from zulu again and works like a champ but i need stock for the kiddos.
try flashing twrp recovery from there wipe system and data partition then reboot into fastboot flash 3.2 again
i was stuck at the boot animation about a month ago after the 3.2 update.... see my post in this thread:
http://forum.xda-developers.com/shi...ion-screen-t3263143/post67564062#post67564062
please note: i used the 3.1 recovery image because the 3.2 image had not been released yet. have not tried it with the newer 3.2 image
also, if you follow my post and install the 3.1 image....be sure to flash the files in the order posted! some will flash quickly, but one or two took awhile to complete, so be patient and wait for each step to finish before moving on to the next.
yes, i saw ur post and how you solved it and i did try the same thing and it did not fix it.. it just gets me to the animation screen... i am gonna try to load twrp from fastboot, wipe.. then re install everything and once done, i will try to fastboot -w and see if that helps me...
foomanjackel said:
i was stuck at the boot animation about a month ago after the 3.2 update.... see my post in this thread:
http://forum.xda-developers.com/shi...ion-screen-t3263143/post67564062#post67564062
please note: i used the 3.1 recovery image because the 3.2 image had not been released yet. have not tried it with the newer 3.2 image
also, if you follow my post and install the 3.1 image....be sure to flash the files in the order posted! some will flash quickly, but one or two took awhile to complete, so be patient and wait for each step to finish before moving on to the next.
Click to expand...
Click to collapse
lalord69 said:
yes, i saw ur post and how you solved it and i did try the same thing and it did not fix it.. it just gets me to the animation screen... i am gonna try to load twrp from fastboot, wipe.. then re install everything and once done, i will try to fastboot -w and see if that helps me...
Click to expand...
Click to collapse
if you un pack the nvidia recovery image there is a scipt inside caled flashall.bat one of the steps run in there is a reboot to fastboot after you flash the boot.image
flash staging blob
fastboot flash boot boot.img
fastboot reboot
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
echo Press any key to exit...
pause >nul
exit