I have not had a lot of experience with SDK tools like adb and fastboot, but I have used them to Root my Nexus 7 (2013) with no problems. But now I am not able to update my Nexus from Kit kat 4.4.2. I have had no problems updateing before, and have not had problems rooting after updating. But when I try to update via the OTA update, it fails every time. I had the TWRP Recovery, and had no problems updating. When this update failed I tried useing the ClockworkMod recovory, but the update also failed. I tried to manually update useing the downloaded razor-ktu841.zip, and the platform tools fastboot. If I run the flash-all.bat, it will write the bootloader, and then restart the bootloader. After that Fastboot.exe crashes. I used Fastboot to flash the stock recovery for my device, and that worked flawlessly. But again, both the OTA update and updating manually failed. If I try to just update useing "fastboot -w update image-razor-ktu84l.zip" Fastboot.exe also crashes. I would leave my Nexus on 4.4.2, but I am having occasional issues with the touch screen, and frequent problems with the Gyroscope and Accelerometer that I hope will be fixed by updating. They will just stop working, and only a restart fixes them. I am compleatly stock as far as roms go. I stuck with stock android. I also believe I have the stock kernel as well, seeing as how I never touched it. I would rather not factory reset my tablet, because I have a lot of stuff on it. That would be a last resort for me.
Any help would be much appreciated.
Aremisalive said:
I have not had a lot of experience with SDK tools like adb and fastboot, but I have used them to Root my Nexus 7 (2013) with no problems. But now I am not able to update my Nexus from Kit kat 4.4.2. I have had no problems updateing before, and have not had problems rooting after updating. But when I try to update via the OTA update, it fails every time. I had the TWRP Recovery, and had no problems updating. When this update failed I tried useing the ClockworkMod recovory, but the update also failed. I tried to manually update useing the downloaded razor-ktu841.zip, and the platform tools fastboot. If I run the flash-all.bat, it will write the bootloader, and then restart the bootloader. After that Fastboot.exe crashes. I used Fastboot to flash the stock recovery for my device, and that worked flawlessly. But again, both the OTA update and updating manually failed. If I try to just update useing "fastboot -w update image-razor-ktu84l.zip" Fastboot.exe also crashes. I would leave my Nexus on 4.4.2, but I am having occasional issues with the touch screen, and frequent problems with the Gyroscope and Accelerometer that I hope will be fixed by updating. They will just stop working, and only a restart fixes them. I am compleatly stock as far as roms go. I stuck with stock android. I also believe I have the stock kernel as well, seeing as how I never touched it. I would rather not factory reset my tablet, because I have a lot of stuff on it. That would be a last resort for me.
Any help would be much appreciated.
Click to expand...
Click to collapse
I can't actually find a KTU841 zip on the Google Devs page, also stock images from said source are typically not .zip files, they are .tgz images. (https://developers.google.com/android/nexus/images). The reason you can't OTA update is because you rooted your device, once unlocked and rooted you need to sideload updates manually, a small price you pay for wanting that bit more.
To me it sounds as if a factory reset may be your best option in this case, that is certainly what I would do at this juncture. You can still connect your device to your computer and back up all your stuff before you wipe it though.
Aremisalive said:
I have not had a lot of experience with SDK tools like adb and fastboot, but I have used them to Root my Nexus 7 (2013) with no problems. But now I am not able to update my Nexus from Kit kat 4.4.2. I have had no problems updateing before, and have not had problems rooting after updating. But when I try to update via the OTA update, it fails every time. I had the TWRP Recovery, and had no problems updating. When this update failed I tried useing the ClockworkMod recovory, but the update also failed. I tried to manually update useing the downloaded razor-ktu841.zip, and the platform tools fastboot. If I run the flash-all.bat, it will write the bootloader, and then restart the bootloader. After that Fastboot.exe crashes. I used Fastboot to flash the stock recovery for my device, and that worked flawlessly. But again, both the OTA update and updating manually failed. If I try to just update useing "fastboot -w update image-razor-ktu84l.zip" Fastboot.exe also crashes. I would leave my Nexus on 4.4.2, but I am having occasional issues with the touch screen, and frequent problems with the Gyroscope and Accelerometer that I hope will be fixed by updating. They will just stop working, and only a restart fixes them. I am compleatly stock as far as roms go. I stuck with stock android. I also believe I have the stock kernel as well, seeing as how I never touched it. I would rather not factory reset my tablet, because I have a lot of stuff on it. That would be a last resort for me.
Any help would be much appreciated.
Click to expand...
Click to collapse
Sounds like you need to reinstall/update the SDK. You're missing a .dll or something. I know I have in the past deleted more than what I should have when cleaning out the platform tools folder after flashing images. If you run the flash-all.bat it will COMPLETELY wipe your device including whatever is in storage. You can modify the flash-all.bat with a text editor and then be able to use it without it doing a complete wipe. Open the flash-all.bat with notepad (I use editpad lite) and remove the -w from the text. Removing the -w will keep the flash-all.bat from flashing the userdata.img which is inside the image zip which is what wipes the device. The flash-all.bat will flash the stock recovery so any custom recovery will have to be reflashed if you use the bat file. Personally... after fixing your sdk install I would pull the boot.img and system.img from inside the image zip and put those in your platform tools folder so that you can fastboot flash them. Download a custom recovery (I use TWRP) and rename it to something shorter, put it inside your platform tools folder so that you can fastboot flash it also. Download the supersu installable zip and put it in your device storage. The bootloader image does not need to be flashed because it has not changed from 4.4.2 to 4.4.4.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery twrp.img
Use the buttons on device to boot into recovery. Install the super su zip. Then go to advanced wipe, wipe cache and dalvik. Reboot system. "IF" you run into any problems after updating you can do a factory reset from inside TWRP and it will not wipe your storage. Of course, doing a factory reset from your devices Settings/Backup & reset will wipe everything.
purephysics said:
I can't actually find a KTU841 zip on the Google Devs page, also stock images from said source are typically not .zip files, they are .tgz images. (https://developers.google.com/android/nexus/images). The reason you can't OTA update is because you rooted your device, once unlocked and rooted you need to sideload updates manually, a small price you pay for wanting that bit more.
Click to expand...
Click to collapse
The OP was correct. If you unzip the tgz far enough you will see:
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-ktu84l.zip
Inside image-razor-ktu84l.zip you will see the rest of the images:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Being rooted will not prevent you from being able to download and use an OTA like you can if not rooted. It's what you do after you are rooted that will make an OTA fail, a lot of the time even if you sideload it. Custom kernels, ANY mods to system files can and usually will throw an unexpected contents error or some other kind of error. The smaller the OTA is the more likely it will work, I wouldn't count on it but it is possible. If there are no modified files that the OTA is trying to update the OTA could work. Fact is, a couple of the KitKat updates were VERY small and I was able to get the OTA to work just fine (without sideloading) and I use a custom kernel, recovery, hosts file, media_profiles.xml, fonts, bootanimation and ui/audio sounds. I almost always fastboot flash the needed images separately but for grins tried those two small OTA's. Rarely do I even bother with an OTA.
Works!
wantabe said:
Sounds like you need to reinstall/update the SDK. You're missing a .dll or something. I know I have in the past deleted more than what I should have when cleaning out the platform tools folder after flashing images. If you run the flash-all.bat it will COMPLETELY wipe your device including whatever is in storage. You can modify the flash-all.bat with a text editor and then be able to use it without it doing a complete wipe. Open the flash-all.bat with notepad (I use editpad lite) and remove the -w from the text. Removing the -w will keep the flash-all.bat from flashing the userdata.img which is inside the image zip which is what wipes the device. The flash-all.bat will flash the stock recovery so any custom recovery will have to be reflashed if you use the bat file. Personally... after fixing your sdk install I would pull the boot.img and system.img from inside the image zip and put those in your platform tools folder so that you can fastboot flash them. Download a custom recovery (I use TWRP) and rename it to something shorter, put it inside your platform tools folder so that you can fastboot flash it also. Download the supersu installable zip and put it in your device storage. The bootloader image does not need to be flashed because it has not changed from 4.4.2 to 4.4.4.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery twrp.img
Use the buttons on device to boot into recovery. Install the super su zip. Then go to advanced wipe, wipe cache and dalvik. Reboot system. "IF" you run into any problems after updating you can do a factory reset from inside TWRP and it will not wipe your storage. Of course, doing a factory reset from your devices Settings/Backup & reset will wipe everything.
The OP was correct. If you unzip the tgz far enough you will see:
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-ktu84l.zip
Inside image-razor-ktu84l.zip you will see the rest of the images:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Being rooted will not prevent you from being able to download and use an OTA like you can if not rooted. It's what you do after you are rooted that will make an OTA fail, a lot of the time even if you sideload it. Custom kernels, ANY mods to system files can and usually will throw an unexpected contents error or some other kind of error. The smaller the OTA is the more likely it will work, I wouldn't count on it but it is possible. If there are no modified files that the OTA is trying to update the OTA could work. Fact is, a couple of the KitKat updates were VERY small and I was able to get the OTA to work just fine (without sideloading) and I use a custom kernel, recovery, hosts file, media_profiles.xml, fonts, bootanimation and ui/audio sounds. I almost always fastboot flash the needed images separately but for grins tried those two small OTA's. Rarely do I even bother with an OTA.
Click to expand...
Click to collapse
Thanks for your help, after re-downloading the SDK, and image (just to be safe) I was able to flash the boot, system, and recovery with no problems. It upgraded me to 4.4.3! I then was able to do an OTA update to 4.4.4 and then rooted it by installing the SuperSU installable zip with TWRP with no problems. Thank you very much!
Related
Hey together,
I hope you can help me. I have a strange problem.
Chronologically:
1) I had been running Xylon JB 4.2 ROM for 2 or 3 months on my GNexus. Everything was fine. Except that I noticed over the time a slight lag all over the OS. The general reaction time was not so fast as it should be (Note: My phone has not that memory unit which causes those extreme lags I read about somewhere in this forum).
2) So I decided to go back to stock. I did a full wipe and flashed a JOP40D 4.2.1 Odex Rooted Busybox FactoryImage which I took from this forum (don't know which thread). The good: Android was very fast again. The bad: Immediately after flashing it I encountered problems. At every boot I got the "Android is upgrading... XX of XX apps..." screen, even after a separate dalvik wipe, and really at every boot (not just the 1st after dalvik wipe). Furthermore, I noticed that some apps behave strange, for example Play Music couldn't play any music from my internal storage which worked fine under Xylon. Plus, system settings like the ring sound were not saved so that after reboot there was set a different ring tone. I thought, well, maybe something went wrong when I restored my apps via TB (apps via update.zip, data via TB app).
3) Due to the strange behaviour I decided to carry out a complete wipe via TWRP. I mean really a full storage wipe, this sort of wipe when TWRP warns you and says this was not needed most of the time. I thought it couldn't be wrong to wipe everything that can be wiped to fight the problem. After that, I flashed 4.1 factory image via the GNex Toolkit because there was no rom zip anymore on the internal storage. (4.1 because the Toolkit couldn't download any newer image correctly). Back in Android, I copied bigxie's JOP40D deodex ROM on the storage and flashed it (full wipe before). And yes I updated the SuperSU binaries as bigxie told. This time I didn't use Titanium Backup for restore, but installed the apps directly from Play Store, the cleanest method. And AGAIN, the phone is showing some strange behaviour! This time no problems with dalvik cache, but with some other part of the storage as it seems. Some apps refuse to start ("app XYZ was closed" - report - OK), even after uninstall and reinstall from Play Store, for example Öffi, DB Navigator, mehr-tanken which worked fine under Xylon. the Facebook app doesn't save data correctly. At nearly every start it asks me if I want to find friends (normally only 1st start). But other Facebook app settings (notification etc.) are saved correctly. Strange, isn't it?? Wipe cache and dalvik cache didn't change anything.
I'm completely desperate. What can be the cause for the strange behaviour? Maybe the storage or something broken?
I've flashed ROMs so often with several Android devices, so I think I'm not such a complete noob. But what could have happened?
I beg you to answer if you have any suggestions what I can try.
I could kick myself for touching my Xylon setup which had worked fine (just slightly slow), even considering that I'm facing my exams in 6 weeks and should learn day and night...
Thanks in advance!!!
it seems like everytime i read about someone having some kind of strange anomoly, its someone whos using a toolkit (not trashing you, but i keep seeing the correlation); which is why i havent touched them, plus fastboot is more fun. anyways this is how i would go about it, and get your stock image ready.
fastboot format system
fastboot format userdata
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot rebooot-bootloader
fastboot flash userdata userdata.img
fastboot reboot
try that, just make sure you have adb and fastboot set up right. its the most basic failsafe for sure method to get to 100% stock without any trash left behind on your phone
Hey, thanks for your detailed suggestion!
I'm not sure if the problem can be toolkit related as I didn't use the toolkit for the first flash (step 2 in my first posting). But nevertheless, I'll follow your suggestion as soon as I can manage it.
I have not much experience with fastboot as the only thing I did with fastboot was flashing custom recoveries.
So just to be safe I'd like to know what you mean exactly by
1) fastboot flash boot boot.img
2) fastboot flash system system.img
3) fastboot flash userdata userdata.img
I downloaded the JOP40D factory image and unzipped the RAR file. It contains:
bootloader-maguro-primelc03.img, flash-all.bat, flash-all.sh, flash-base.sh, image-yakju-jop40d.zip, radio-maguro-i9250xxlh1.img
Shall I take the boot.img, system.img and userdata.img from the zip file?
What shall I do then with all the other files except the zip file?
staud said:
Hey, thanks for your detailed suggestion!
I'm not sure if the problem can be toolkit related as I didn't use the toolkit for the first flash (step 2 in my first posting). But nevertheless, I'll follow your suggestion as soon as I can manage it.
I have not much experience with fastboot as the only thing I did with fastboot was flashing custom recoveries.
So just to be safe I'd like to know what you mean exactly by
1) fastboot flash boot boot.img
2) fastboot flash system system.img
3) fastboot flash userdata userdata.img
I downloaded the JOP40D factory image and unzipped the RAR file. It contains:
bootloader-maguro-primelc03.img, flash-all.bat, flash-all.sh, flash-base.sh, image-yakju-jop40d.zip, radio-maguro-i9250xxlh1.img
Shall I take the boot.img, system.img and userdata.img from the zip file?
What shall I do then with all the other files except the zip file?
Click to expand...
Click to collapse
what all is in the file image-yakju-jop40d.zip? you should have boot.img, recovery.img, system.img, userdata.img. if those are all in there, you can extract them to the folder you use to flash from in fastboot. for example, the command fastboot flash boot, is the command to flash the boot image. the second part is the file name you want it to flash, so fastboot flash boot boot.img. you shouldnt need to flash the bootloader or radios if they are working correctly. if you want to anyways, check efrant's nexus guide on here, i forget the commands to differentiate between the two different radios when you flash them.
if you do the bootloader and decided to erase and flash instead of just flashing over it, DO NOT use the command fastboot reboot-bootloader until after you flash the bootloader. otherwise it will try to reboot into a bootloader that doesnt exist, if that makes sense. someone correct me if im wrong about this part.
username8611 said:
what all is in the file image-yakju-jop40d.zip? you should have boot.img, recovery.img, system.img, userdata.img. if those are all in there, you can extract them to the folder you use to flash from in fastboot.
Click to expand...
Click to collapse
Yeah, those were in the zip. I followed your fastboot how-to within the last 10 minutes and it worked so far as the new stock Android has just booted. By now I can't tell if the strange things have really disappeared. I'll see how things go within in the next hours and days and repost if I encounter again any problems. By now - thanks dude! :good:
EDIT: You wrote reboot with 3 o once. I noticed it but maybe you might wish to correct that if some other desperate and help-searching guy follows your how-to
EDIT2: After 3 days I haven't encountered any strange behaviour. But I didn't root it again or any other modding stuff. Just stock Android. For the moment I'm happy that it runs without problems and I won't touch it again until my exams are done. It seems to me that your method was successful. Thanks again!
I've got an unlocked rooted Nexus 5x, encryption off, build MMB29K. I got a notification of OTA update. Looks like it's to upgrade to MMB29P. I'd like to do this without losing 'encryption off' and having to redo all data and apps.
Here's what worked:
cd </path/to/hammerhead-lrx22c>
fastboot flash bootloader bootloader-hammerhead-hhz12d.img
Reboot the bootloader.
fastboot flash radio radio-hammerhead-m8974a-*.img
cd <image-hammerhead-lrx22c>
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
If you DO NOT use a custom recovery (like TWRP or CWM), then also: fastboot flash recovery recovery.img
Don't worry if you see messages like "target reported max download size of 1073741824 bytes". Just wait and let it finish.
Reboot your phone and enjoy. It's normal for the first boot to take a while. Going from Kitkat to Lollipop took about 20 minutes. Going from 5.0 to 5.0.1 took 5-10, I think. YMMV.
Click to expand...
Click to collapse
flash:
radio-bullhead-xxxxxxx.img
bootloader-bullhead-xxxxx.img
boot.img (might be unnecessary, since we will flash a modified version later on.)
cache.img
system.img
vendor.img
While ignoring these:
recovery.img (would overwrite TWRP)
userdata.img (would erase your data)
Click to expand...
Click to collapse
from here
Any other ideas?
replace anything in the <>. From here
cd </path/to/hammerhead-lrx22c>
fastboot flash bootloader bootloader-<hammerhead-hhz12d>.img
Reboot the bootloader.
fastboot flash radio radio-<hammerhead-m8974a>-*.img
cd <image-hammerhead-lrx22c>
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
It worked. I opted to stick closer to the second set of instructions. I am on build MMB29P, still un-encrypted, and kept all data.
dkerlee said:
I've got an unlocked rooted Nexus 5x, encryption off, build MMB29K. I got a notification of OTA update. Looks like it's to upgrade to MMB29P. I'd like to do this without losing 'encryption off' and having to redo all data and apps.
from here
Any other ideas?
Click to expand...
Click to collapse
Flashing the bootloader is unnecessary. After following your steps, boot into TWRP and install SuperSU 2.6x (this is systemless root). This will auto patch the boot.img and keep encryption off.
If you boot into the rom before installing SuperSU, you will be encrypted.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Flashing the bootloader is unnecessary. After following your steps, boot into TWRP and install SuperSU 2.6x (this is systemless root). This will auto patch the boot.img and keep encryption off.
If you boot into the rom before installing SuperSU, you will be encrypted.
Click to expand...
Click to collapse
Thank you. I mis-read my settings, my phone is now encrypted BOOO. That means I'll have to wipe it to un-encrypt the thing.
When I go through "my steps" up there, boot into TWRP to install SuperSU 2.6x, do I need to download that and copy it over beforehand from https://plus.google.com/+Chainfire > latest Beta SuperSU? 2.66 beta at xda
dkerlee said:
Thank you. I mis-read my settings, my phone is now encrypted BOOO. That means I'll have to wipe it to un-encrypt the thing.
When I go through "my steps" up there, boot into TWRP to install SuperSU 2.6x, do I need to download that and copy it over beforehand from https://plus.google.com/+Chainfire > latest Beta SuperSU? 2.66 beta at xda
Click to expand...
Click to collapse
Since you installed the bullhead factory images, format data and decrypt is next. Yes, you'll want to have SuperSU downloaded on your computer. I have a Mac, so I used "ADB Push filename.zip /sdcard/filename.zip" to move it onto my phone after a data format. You must format data then move SuperSU onto your phone and install in TWRP before booting up.
Sent from my Nexus 5X using Tapatalk
Anyone has modified boot.img for MMB29P?
Hello, I'm needing some help with my 4gb 2.3 ghz rooted Asus after attempting to installing xposed framework. I'm certain it is bricked. Currently it is still able to charge and access the boot loader, but I am not able to flash the phone. The ADB shell just responds with "Access Denied". The phone was encrypted before I tried the xposed install so I'm guessing it messed up the process and is blocking my from using ADB. I did try factory resetting, but I guess that just covers the user app data. I also had debugging enabled within the developer options before everything went haywire. Any suggestions would be helpful, otherwise I'll just have to send it to Asus support for a pretty penny. It doesn't have warranty and I'm positive they don't really help you when your phone is rooted.
Try to wipe /cache. If it doesn't work, backup all your important data and wipe /data in recovery.
HungNgocPhat said:
Try to wipe /cache. If it doesn't work, backup all your important data and wipe /data in recovery.
Click to expand...
Click to collapse
Ok, I did a data factory reset and wiped the cache. The problem i'm encountering now is i get status 7 in ADB when attempting to push a new zip of firmware to the phone. I know status 7 means the firmware cannot be installed due to system modification and root. So i'm thinking i'll have to reflash a pre-rooted system.img with droidboot.img and boot.img (recovery is functioning properly so i don't believe that i will need to flash recovery.img) I am also having a hard time finding detailed guides concerning flashing images and getting the zenfone 2 into fast boot. I did try a fastboot reboot fastboot command, but i,m thinking i'm missing a few important details on prerequisites to flash the phone.
HungNgocPhat said:
Try to wipe /cache. If it doesn't work, backup all your important data and wipe /data in recovery.
Click to expand...
Click to collapse
Ok, I did a data factory reset and wiped the cache. The problem i'm encountering now is i get status 7 in ADB when attempting to push a new zip of firmware to the phone. I know status 7 means the firmware cannot be installed due to system modification and root. So i'm thinking i'll have to reflash a pre-rooted system.img with droidboot.img and boot.img (recovery is functioning properly so i don't believe that i will need to flash recovery.img) I am also having a hard time finding detailed guides concerning flashing images and getting the zenfone 2 into fast boot. I did try a fastboot reboot fastboot command, but i,m thinking i'm missing a few important details on prerequisites to flash the phone.
Asus enthusiast 12 said:
Ok, I did a data factory reset and wiped the cache. The problem i'm encountering now is i get status 7 in ADB when attempting to push a new zip of firmware to the phone. I know status 7 means the firmware cannot be installed due to system modification and root. So i'm thinking i'll have to reflash a pre-rooted system.img with droidboot.img and boot.img (recovery is functioning properly so i don't believe that i will need to flash recovery.img) I am also having a hard time finding detailed guides concerning flashing images and getting the zenfone 2 into fast boot. I did try a fastboot reboot fastboot command, but i,m thinking i'm missing a few important details on prerequisites to flash the phone.
Click to expand...
Click to collapse
What adb command you ran? It should be "adb sideload filename.zip"
If you can't, rename your firmware file to mofd_sdupdate.zip, copy to external sdcard, boot recovery then it will install install the zip automatically. Root using temp cwm/twrp.
If the above method doesn't work for you, flash a pre-rooted firmware.
I reinstalled the factory image to my Nexus 7 from Google's website. without any issue using ADB. My bootlogger is still unlocked.
I recall when I rooted my KitKat using TWRP, I didn't have to wipe out my data, it rooted just fine.
Now, I am uncertain if this is the case with Marshmallow as I have loaded all my 150+ apps (manually) back onto my tablet .
Also, what's the best site/link for rooting to Marshmallow. It's been quite sometime since I rooted. I just want to make sure I follow the sequence correctly.
Thanks
Gaining root access is very simple.
Flash twrp with fastboot.
Then from twrp flash the su zip of your choice, phh's superuser or SuperSU.
That's it. No loss of data. Of course make a nandroid first just in case of any problem.
Edit: In your other thread that you link to this one in (didn't see it earlier) you may not have needed the clean install. Either flashing the boot.img and system.img for that os version with fastboot OR deleting the "-w" from the flash-all script in the factory image would have kept your apps/data. Just for future reference if you choose to stay on 6.0.1 and something goes wrong.
I think there is some confusion and there are different variations on how to flash to TWRP. What is the most recommended flash process?
Michael Carleone said:
I think there is some confusion and there are different variations on how to flash to TWRP. What is the most recommended flash process?
Click to expand...
Click to collapse
I just did this the other night, though I did go from one MM build to another.
1a) Grab the factory image from Google in ZIP form from the developer site
1b) Grab the latest version of TWRP for the 2013 N7 Wifi (flo) from their website
1c) Grab an appropriate super user app flash-able from TWRP. I prefer SuperSU, but the choice is yours. Make sure it supports systemless installation, as traditional SU installs can run afoul of Marshmallow's new integrity checks. (Yes, there are permissive kernels available, but I prefer to stay as stock as possible)
2) Unpack ZIP from 1a into a folder on your PC. I tend to drop a minimal copy of fastboot/adb into the folder to make things easy, but you can just use whatever is in the path.
3) You can choose to use the batch file or not, but if you do, remember to remove the -w from the fastboot command that flashes the OS image unless you want truly clean install. I personally prefer to flash the bootloader separately, then flash the system, rather than using the batch file, but they are equivalent. The tablet will automatically restart after the image is uploaded.
4) Kick back and relax while all your apps get recompiled. When it finally comes up, make sure everything is working okay.
5) Copy your SU flashable image to the tablet. If you have ADB debugging turned on, you may have to toggle MTP mode in developer options to re-enable it.
6) After everything is nice and stable, and everything you need is on the tablet already, reboot to bootloader.
7) Flash the TWRP image from 1b using 'fastboot flash recovery twrp_<version>.img'
8) Reboot into your shiny new recovery and install the SU package from 1c
9) Reboot again into the new, newly rooted, system and verify SU works.
10) Enjoy!
At first I tried to update my existing TWRP (3.2.1-0) to the 3.2.1-2 variant. It flashed ok, but then the phone would only boot to TWRP (reason for upgrade is that 3.2.1-0 would hang). I was attempting initially to put myself on the path to a "custom rom". When this failed, I manually flashed the latest google firmware from their page and it still will not do anything other than fastboot mode. No recovery, no firmware load. When I try to do the flash-all.bat method now, all I get after it loads the archive contents is "error: Cannot generate image for userdata. Guess I got a $1000 brick at this point?? Image from the PC screen included.
See if this thread helps.
https://forum.xda-developers.com/pi...ory-image-flashing-fails-t3715350/post7649698
I am going to have to find another way to look at that thread. My ipad is getting directed to some HTC desire article about and orange and black theme.
I have tried so far very unsuccessfully to wipe everything by booting to twrp via fastboot method. Then I used the dueces script to reflash everything completely (both partitions). No matter whether I flash complete stock or flash magisk and verizon radio files, it just hangs on the white google screen now and that is as far as I have gotten. Left it at home in this mode hoping it will clear.
JoeNeckbone said:
See if this thread helps.
https://forum.xda-developers.com/pi...ory-image-flashing-fails-t3715350/post7649698
Click to expand...
Click to collapse
That link is bad. Three devices are going to an htc desire theming page.
remove the -w from the update line in flash-all.
I have got the same problem since yesterday and search for a solution.
ctradio said:
That link is bad. Three devices are going to an htc desire theming page.
Click to expand...
Click to collapse
Not sure what happened with link, https://forum.xda-developers.com/pi...ry-image-flashing-fails-t3715350/post74751631
new adb dont help for me. I cannot flash slot a and change to b and got the error message that no slot is supported.
Still need help? Have you tried Skipsoft? Sure its not been updated but it might beable to help ..
Where fastboot flashing failed for me one time it got me out of a hole....
Otherwise i can try and remote and help... BTW its not finding the userdata file in the fastboot side... Something isnt right hence why it cant create the userdata file...
I try to boot with skipsoft to temp twrp but stuck on boot.img loading. the flashed twrp stuck on twrp logo and before I have changed from slot b to a inside twrp i can boot. now I cannot flash inside fast boot or delete anything.
Have you guys tried Deuces Bootloop Recovery & Flashing Script? I'd imagine you'd run into the same issues as the script runs a lot of the same fastboot commands...but it has worked wonders for many other users so......
I also might try re-downloading the factory image and comparing the Checksums to make sure you have a whole exact download just in case that's getting in the way of properly generating the userdata image. I'd also suggest making sure you have more than 4GB of space on your C drive; I was getting similar messages about not finding or not generating system images because they couldn't be fully extracted (temporarily) because I didn't have sufficient temp space on my C drive.
But I had encountered this issue before. It was either userdata or system_other partition. I did attempt to fastboot erase and fastboot format those partitions and other tweaks; even messed with changing the size of the partition (you might have better luck). What I seemed to conclude is that I was flashing the wrong month's Full Factory image; i.e. I was manually flashing system_other image from February when the whole phone was still on January. But I believe what I ended up doing was flashing a Full Factory image with the "-w" intact; therefore, if you still have access, you should copybackcup (via TWRP or adb pull) your internal storage (/sdcard and-or /data/media) and simply flash a Full Factory image with wipe option enabled...
Just some thoughts and suggestions...hope this helps...
I figured it out finally. Even though my ADB/Fastboot tools were a later creation date than the ones posted online, the ones online worked great. Even used the dueces script to ensure the junk is gone. Thanks all! Hate pesky gotchas like that!!