Develop Bugs

any way to revert back to stock rom?

installed CM7 port 7.2 yesterday, and it seemed to all go fine, but whenever i need to reboot the phone, i get loads of FC's, the calendar doesn't work, my FB and twitter accounts don't get any notifications sync'd, and their accounts are actually totally removed from the sync and accounts section upon every reboot.
overall, considering this is supposed to be the most "stable" of the custom roms, i'd rather just go back to the stock, at least it works, even if i have less space and it eats up battery a bit quicker...at the moment, the phone is pretty useless :s

go to http://forum.xda-developers.com/showthread.php?t=1074445, choose the stock rom for your device and flash it.

it's that simple? awesome! thanks so much
::EDIT::
not working
it keeps bringing up an error when trying to install the rom :s
also tried to install using the rom.zip by choosing install from zip in recovery menu...no joy
::EDIT::
trying a completely fresh install of CM7, wipe everything, format and repartition Sd card, totally start from scratch...as this is the only thing i seem to be able to do at this point....none of the RRU's are installing....wish I hadn't tried this CM7 now :s

My cm7 is completely stable and much more responsive and less bloated than any stock rom
Dunno where your problems are coming from but I don't have any.

I'd recommend doing a full wipe and reflash of CM7. Some bugs appear at first.
Make sure you wipe dalvik, cache and full wipe before flashing.

ok guys, just completely restarted everything from scratch, wiped everything, reformated everything, cleared every possible option.
this time i installed CM7, then the google pack, then DATA2SD (before anything i partitioned the sd card 1GB/256MB)...
seems to be working a bit better...my facebook and twitter accounts are still signed in and show under the sync and accounts settings etc...
i haven't got all those FC's at boot so far....but then i didn't initially yesterday either....so we'll see how it plays out tomorrow :s
however the calendar still doesn't work well, and infact if i open it, goto menu then select calendars, i still get FC on that app :s
maybe i should just get another calendar app?
i think alot of the preview errors might have been due to the fact that i had just manually chose the "move to sd" option for all my apps instead of installing data2sd (which tricks the phone into thinking the 1gb partition on the sd card is the internal memory?)
so fingers crossed it will hold up a bit better now. like i said, i actually can't go back from CM7 now, since none of the RUU's will install. but so far so good, hopefully it will last more than a day this time :s

Gloris said:
installed CM7 port 7.2 yesterday, and it seemed to all go fine, but whenever i need to reboot the phone, i get loads of FC's, the calendar doesn't work, my FB and twitter accounts don't get any notifications sync'd, and their accounts are actually totally removed from the sync and accounts section upon every reboot.
overall, considering this is supposed to be the most "stable" of the custom roms, i'd rather just go back to the stock, at least it works, even if i have less space and it eats up battery a bit quicker...at the moment, the phone is pretty useless :s
Click to expand...
Click to collapse
Give it one more shot but in CWM do this:
Factory reset
Then Mounts/ Format System
Then Advanced/Wipe Dalvik Cache
Then install zip and gapps zip.
See if that clears up any ghosts in the machine. That behaviour shouldn't happen Gloris. I can assure you I've been running the release 1218 since well...1218 and it's been a pleasure.

Same as d33ps1x this is a great rom.
Everything's working fine with no force closing
If your problems continue follow d33ps1x instructions carefully and all should be fine.
Are you using the latest nightly or RC version?

using the nightly version....was all going ok, but now, not only is the calendar still FCing, but i can no longer download ANYTHING from the market...i just get error 492....
I wish i'd never tried this damned CM7, totadl waste of time.
Yes, i've got 1GB of "internal storage", but what's the use if i can't add any more apps???
anyone got any more suggestions for how to go back to stock?
I've tried the RUU, and tried it with goldcard via the .exe installed and via recovery (install from .zip), both with no luck.
I wish i could just go back to stock, these custom roms are a total waste of time

Gloris said:
using the nightly version....was all going ok, but now, not only is the calendar still FCing, but i can no longer download ANYTHING from the market...i just get error 492....
I wish i'd never tried this damned CM7, totadl waste of time.
Yes, i've got 1GB of "internal storage", but what's the use if i can't add any more apps???
anyone got any more suggestions for how to go back to stock?
I've tried the RUU, and tried it with goldcard via the .exe installed and via recovery (install from .zip), both with no luck.
I wish i could just go back to stock, these custom roms are a total waste of time
Click to expand...
Click to collapse
this is the reason why you should have made a nand backup of your rom with cwm BEFORE installing a custom rom.

Gloris said:
using the nightly version....was all going ok, but now, not only is the calendar still FCing, but i can no longer download ANYTHING from the market...i just get error 492....
I wish i'd never tried this damned CM7, totadl waste of time.
Yes, i've got 1GB of "internal storage", but what's the use if i can't add any more apps???
anyone got any more suggestions for how to go back to stock?
I've tried the RUU, and tried it with goldcard via the .exe installed and via recovery (install from .zip), both with no luck.
I wish i could just go back to stock, these custom roms are a total waste of time
Click to expand...
Click to collapse
Have you got the unlocked bootloader if so extract the ruu an flash the boot and system images via fastboot
Sent from my HTC Wildfire S using xda premium

eoghan2t7 said:
Have you got the unlocked bootloader if so extract the ruu an flash the boot and system images via fastboot
Sent from my HTC Wildfire S using xda premium
Click to expand...
Click to collapse
can you elaborate on that and give the exact commands

Gloris said:
can you elaborate on that and give the exact commands
Click to expand...
Click to collapse
Downloaded my PG76IMG.zip version.
Unzip it with 7zzip.
put the boot.img and system.img in the same directory as fastboot
Start your phone with vol down/power after removing and replacing the battery
Choose fastboot
Connect usb cable
issue fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img

dont forget fastboot -w to wipe the data of the previous rom

d33ps1x said:
Downloaded my PG76IMG.zip version.
Unzip it with 7zzip.
put the boot.img and system.img in the same directory as fastboot
Start your phone with vol down/power after removing and replacing the battery
Choose fastboot
Connect usb cable
issue fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
I can confirm this working.
if you flash recovery, too from the zip, you can return to stock from cwm.
then apply "fastboot oem lock" and the bootloader will be locked again.
This can be used as a way back to warranty maybe, since then everything is stock again

d33ps1x said:
Downloaded my PG76IMG.zip version.
Unzip it with 7zzip.
put the boot.img and system.img in the same directory as fastboot
Start your phone with vol down/power after removing and replacing the battery
Choose fastboot
Connect usb cable
issue fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
thanks, do you have the link?

eoghan2t7 said:
dont forget fastboot -w to wipe the data of the previous rom
Click to expand...
Click to collapse
fastboot -w is not allowed.
>fastboot -w
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.004s
Click to expand...
Click to collapse

also, the only RUU i have in rom.zip format is the gingerbread 2.3.5 update....the others are all .exe only...how do i extract those? as i'm not sure the zip i have will work as it's 151Mb (i think the phone only has a genuine 150Mb total internal storage?)

for extracting from ruu exe:
- clear temp folder on windows
- run ruu.exe until first dialog
- go to temp files
- search in the folders for a rom.zip
- extract
- flash

this method is definitely not working
tried flashing the using fastboot, and not my phone won't even boot, it just starts up in recovery mode (it's actually lucky the recovery mode is there or else i'd have a definite brick on my hands).....for those that are wanting to back to stock, DO NOT TRY THIS....NOT WORKING!

[Q] Can not restore /data using cwm recoveries; no access to fastboot. Help?

UPDATE: PROBLEM SOLVED
Hello,
I recently flashed a rom with a custom gapps that had themes, but one of the apps, G+, did not work since it was outdated. In an attempt to take the easy way out, I installed a "system app uninstaller"-app and used it to remove G+. It removed it, but I could not install G+. I decided to reboot the phone, but it took an abnormally long time amount to turn back on, stuck at the "Google" logo screen. I decided to reflash one of my previous backups.
My phone uses ClockworkMod Recovery v6.0.1.0 currently. After wiping data/factory reset and wiping the cache partition, I decided to restore one of my recoveries. It restored boot, system, but then failed to restore the /data with "Error while restoring /data!" popping up. I tried these steps again but with another backup, and the previous one before that, and none of them worked.
I did some research online, and learned that I could flashboot a stock recovery to my phone, so I attempted to do that; I noticed that when using the "adb devices" in the command prompt, no devices were listed.
If it makes a difference, I did not install the proper drivers for use of ADB since this computer is new. As of now, I can not boot my phone, and I can not access the files on my phone when connected through USB when attempting to use the "Mounts and Storage Menu" in CWM. Because of this, I can't use Fastboot to flash a stock recovery image from my current knowledge and self-research.
I now come to you guys for assistance; what other steps can I take that I haven't tried? Or perhaps have I done something incorrectly in my method?
If there is any other info needed, please let me know so I can reply with that information.
TL;DR - Can not use CWM to restore my backups (stuck at /data), cannot use fastboot because my GNex isn't listed on the adb devices, what should I do now?
Thank you for your time. (And sorry if this is not in the correct section)

Okay, so, first we need to fix your driver issue. I'm assuming you're on windows.
1. Boot to recovery, connect your device to the computer.
2. Download the driver here http://forum.xda-developers.com/showthread.php?t=1766220
3. Start menu>Right click computer> Properties> Device manager>Find your phone, right click, properties> Uninstall driver if any, then install the driver you downloaded.
4. Your phone should now appear as an ADB interface. Try ADB devices.
5. Now that ADB should be working, backup your SDcard. Type "adb pull /data/media/ SD". This will backup your SDcard to a folder named "SD" in the directory your ADB file is.
6. Now it's time to reflash the phone. Use ODIN. I'm sure someone can link you to ODIN images. If not, I can let you directly download them from me in the morning. I used the 4.0.2 images
7. Boot to odin (Phone powered off, hold Volume Down and power. Phone will say "Downloading...."
8. Flash the ODIN images with the ODIN program. Flash a PDA and PHONE file.
9. Once the phone boots up, turn it off, boot to the bootloader (Phone off, then Vol up and down, with power).
10. in your CMD, use "Fastboot devices". If the phone isn't detected, then update the driver of the device detected to the driver you downloaded.
11. If fastboot works, type "Fastboot oem lock", then reboot the phone.
12. Allow the 4.0.4 OTA to install.
13. Go back into the bootloader, and do "Fastboot oem unlock", then flash your recovery to CWM. (Download the .img from the website, and use "Fastboot flash recovery <filename>")
14. Boot the phone. Let it fully boot, then shut down and load bootloader again.
15. Boot to recovery, and restore your SDcard by typing "adb push SD /data/media/"
Once that wall of text is done, your phone should be fully functional, and ready to flash. That is how I solved all of my issues when I experienced the same thing.
I know I was short with a how-to on ODIN, but I'm super tired. ODIN is easy, and I'm sure you can find guides.

With your help I have managed to fix the drivers and my phone is now listed in adb devices. I downloaded Odin3 v.1.85 and I have downloaded the odin 4.0.4 images from the sticky'd threads. What I downloaded was a .tgz and contains a .tar. I do not know how to use these files with Odin however; when I try using ODIN with the .tar file the ODIN executible crashes.
Also, "adb pull /data/media/ SD" yields "remote object '/data/media/sd; does not exist". Is it correct to assume this is because the Galaxy Nexus does not have a removable SD card? Or is this method supposed to back up the internal storage?
I'm really appreciative of your help, thank you.

"ADB_Pull_/data/media/_SD" You have a space where the underscores are, right? And this is a method to backup the internal storage. It is located in /data/media/. Whenever you "Factory reset", the phone's /data/ partition is wiped, but the media folder is exempt. Always.
And as for ODIN crashing.. that's weird. I haven't had an issue. I'll upload my 4.0.2 images and executable to mediafire and PM it to you.
You'll want to make sure you backup your SD data, because ODIN will erase it.
---------- Post added at 09:36 AM ---------- Previous post was at 09:25 AM ----------
Oh wait. I just remembered there are multiple variants of the phone. What Gnex do you have? Maguro, Toro, or Toroplus? I'm uploaded images for Toro.

Looking at this thread is making my head spin.
What are you trying to do exactly? Flash a stock ROM without losing your files stored in /sdcard?
If so, then:
1) If you don't care about losing your files in /sdcard, just follow the steps in this thread.
2) If you DO want to keep the files in /sdcard, then follow the same steps, but skip flashing the userdata partition and the recovery partition. Instead of flashing the stock recovery, flash CWM 5.5.0.x. Once you have flashed all the partitions (except userdata), just reboot into CWM, and wipe data and cache. Done.
Other suggestions:
1) you should not use Odin unless you really need it. You can brick your device with Odin. Fastboot will do everything you need in most cases, and you canNOT brick your device.
2) Use CWM 5.5.0.x instead of the newer ones. The 5.5.0.x recoveries are extremely stable, and won't mess anything up.
3) You should read up a bit on fastboot and ADB. They are not related, as you seem to be implying in your OP (and they also need separate drivers). See here for a little introduction.

efrant said:
1) you should not use Odin unless you really need it. You can brick your device with Odin. Fastboot will do everything you need in most cases, and you canNOT brick your device.
Click to expand...
Click to collapse
People have bricked with ODIN? I haven't heard of that. Also, I experienced the same issue when I tried going over to JellyBean for the first time. I ****ed my Jellybean up, and my data partition was not functional. There were other users who had the issues too. We were only able to fix it through ODIN.
Edit: Adding that we experienced our issues after flashing the non-AOSP Jellybean.

Ryands991 said:
People have bricked with ODIN? I haven't heard of that.
Click to expand...
Click to collapse
Yup, they have. If you'd like, I can search and post the links.
But if your bootloader is messed up and you can no longer use fastboot, you have no choice but to use Odin.

Nah don't worry about searching for it. I'll take a peak later. I'm interested. Thank you!
---------- Post added at 10:32 AM ---------- Previous post was at 09:57 AM ----------
If you still want to try ODIN, here is a mirror of the Toro 4.0.2 files
http://www.mediafire.com/?31kevti8p2pnb62
Again, this is for Verizon/Toro/SCH i515
Don't use with any other version. If you don't have Verizon, this isn't the file you need.

efrant said:
Looking at this thread is making my head spin.
What are you trying to do exactly? Flash a stock ROM without losing your files stored in /sdcard?
If so, then:
1) If you don't care about losing your files in /sdcard, just follow the steps in this thread.
2) If you DO want to keep the files in /sdcard, then follow the same steps, but skip flashing the userdata partition and the recovery partition. Instead of flashing the stock recovery, flash CWM 5.5.0.x. Once you have flashed all the partitions (except userdata), just reboot into CWM, and wipe data and cache. Done.
Other suggestions:
1) you should not use Odin unless you really need it. You can brick your device with Odin. Fastboot will do everything you need in most cases, and you canNOT brick your device.
2) Use CWM 5.5.0.x instead of the newer ones. The 5.5.0.x recoveries are extremely stable, and won't mess anything up.
3) You should read up a bit on fastboot and ADB. They are not related, as you seem to be implying in your OP (and they also need separate drivers). See here for a little introduction.
Click to expand...
Click to collapse
I didn't manage to save my userdata but I did manage to return my phone to stock w/root using the method described in the thread you directed me too. Thank you efrant for your help
And thank Ryands991; I'll keep the ODIN method in mind if I ever encounter a problem using fastboot. Oh, and with regards to the spaces; I did have them, but it was stuck at 0% and never pushed my userdata. I am fine with losing my userdata however, so I went ahead and did a full wipe.

[Q] help flashing MIUI, my first rom flash

hi
i already unlock the bootloader, install custom recovery TWRP, and done a backup
i also copy my backup to PC
now i'm confuse
- i need to root the phone or can i just flash the new room?
- if i need to root the phone i found an italian guide on 4.0 and attach file, can i use that? i have 4.1.1 on mine now
i'm not interested to have HTC stock with root but what i want is to install MIUI ROM
this is the only guide i found in english that explains how to install the rom
external link (i can't post it) miuiandroid.com/community/threads/installing-the-htc-one-x-required-s-on-steps.16592/
what i understand is:
- boot my device power + menu down, to see the FASTBOOT USB i have to select FASTBOOT
- flash the boot.img
- press the power button once (HBOOT i guess), click volume down, highlight recovery & press power
- Flash the downloaded ROM via recovery normally and it followup at this link
external link (i can't post it) miuiandroid.com/community/threads/how-to-update-upgrade-miui.15424/
i need to copy the img rom in SD ROOT before starting with all this process
- now i need to Wipe data/factory reset, Cache Wipe & Dalvik Cache Wipe in all tutorial i found this is done with clockworkmod
in TWRP under menu WIPE i guess are System, Cache, Dalvik buttons
after that i'm note sure if i need to flash italian language, if i don't need and i can just download it later i tihink is not a big deal
unless is all in chinese
is the metod correct?
do i have to copy ROM file in .zip format as i download?
here where i found ROM
from official site grey button miui.com/download-7.html
OR
from UK web site miuiandroid.com/community/threads/3-4-28.20232/
the boot.img is here
point 3 miuiandroid.com/community/threads/installing-the-htc-one-x-required-s-on-steps.16592/
i'm not sure if would be better to use clockworkmod, since most tutorials use that..
thanks

Doesn't matter which recovery you use. Yes just place the zip file on your sd card. Flash boot.img as you already said. Perform a full wipe and then flash the Rom zip. Reboot and its done.
The Roms are pre-rooted so you dont need to worry about that. Italian language should be included i guess.
Sent from my HTC One X using xda app-developers app

Heres what i do :
1) Put Rom.zip on SD card
2) Put boot.img in fastboot folder
3) fastboot erase cache
4) fastboot flash boot boot.img
5) fastboot erase cache
6) Reboot into recovery
7) Full wipe (except sd card)
8) Install rom
9) Enjoy new rom
Andy

i did my first mess but fortunally i could restore since i had copy the backup on my mac too
i don't know what went wrong but this is what happened:
- i did how was told before, but actually i download boot.img and rom from 2 different sites
- after reboot it didn't move from first screena waited for 15 minutes almost, so i did reboot in recovery tri to wipe but nothing happened
- so i decide to restore... but it did boot even if it was successful
- i thought that if i flashed the boot.img first time i may need to do it again, i found boot.emmc.win, rename it to boot.img, flash it and then i restored successfully
:victory:
now, to try a different rom i need to restore (maybe is safer)? can i copy the rom from recovery or fastboot?
what can it be wrong with my miui rom? could it be boot.img and rom file mismatch? can't find where to download both

al404 said:
i did my first mess but fortunally i could restore since i had copy the backup on my mac too
i don't know what went wrong but this is what happened:
- i did how was told before, but actually i download boot.img and rom from 2 different sites
- after reboot it didn't move from first screena waited for 15 minutes almost, so i did reboot in recovery tri to wipe but nothing happened
- so i decide to restore... but it did boot even if it was successful
- i thought that if i flashed the boot.img first time i may need to do it again, i found boot.emmc.win, rename it to boot.img, flash it and then i restored successfully
:victory:
now, to try a different rom i need to restore (maybe is safer)? can i copy the rom from recovery or fastboot?
what can it be wrong with my miui rom? could it be boot.img and rom file mismatch? can't find where to download both
Click to expand...
Click to collapse
extract the boot image from the rom you are going to use

ok, i tryed again but now it get stack on Mi black screen
i waited 8 minutes but nothing happens, i also tried to wipe cache and davik, nothing happens
at list i get to black Mi screen
do i need to delete the boot.img from ROM zip?
what could it be?

1st u didn't mention which phone u r using
2nd dn't get confuse while downloading rom n .img file
Type in google
(Ur phone model) android development xda
U'll find all the stuffs related to ur phone
So try this 1 n remember before updating or rooting or anythg related to ur which can mess ur phone or can brick ur phone
I suggest u read twice the thread n procedures n also check thrice the stuff which u gonna need to perform ur act.
Sent from my GT-N7100 using xda premium

al404 said:
ok, i tryed again but now it get stack on Mi black screen
i waited 8 minutes but nothing happens, i also tried to wipe cache and davik, nothing happens
at list i get to black Mi screen
do i need to delete the boot.img from ROM zip?
what could it be?
Click to expand...
Click to collapse
i would try a different rom for now, viperx perhaps. and the boot image is in the rom zip, extract the boot img from the rom and put it in your fastboot folder then copy the rom to your sdcard. once you have done that, fastboot erase cache, flash the boot image, fastboot erase cache again, then back into recovery, wipe cache and dalvik just to be sure then use recovery to flash the rom and hey presto. all of the above is assuming you have the one x international tegra 3

I have htc one x european terga 3, as far as I know mini is only for tegra 3
what you describe is exactly what I did:
- I leave the rom zip ad it is, I didn't remove boot.imf that I extract, correct?
- when I flash I hit hoot fastboot, connect USB and fastboot change in fastboot USB, to go back I select Hboot and and hit power, prom there recovery
- I did unlock bootloader but did not get rooted my phone, could it be that?

al404 said:
I have htc one x european terga 3, as far as I know mini is only for tegra 3
what you describe is exactly what I did:
- I leave the rom zip ad it is, I didn't remove boot.imf that I extract, correct?
- when I flash I hit hoot fastboot, connect USB and fastboot change in fastboot USB, to go back I select Hboot and and hit power, prom there recovery
- I did unlock bootloader but did not get rooted my phone, could it be that?
Click to expand...
Click to collapse
read this post. at least twice!! http://forum.xda-developers.com/showthread.php?t=2069904 do not do the "unlock bootloader" section as you already did that

@nogotaclue sorry i read so many, and some of them sayed that root was not necessary if you flash a new rom, other sayed it could still be necessary... now i rooted with the app and did a new backup that i'm coping on PC
reading further it says: to wipe, install rom, and flash boot.img after
"Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it."

al404 said:
@nogotaclue sorry i read so many, and some of them sayed that root was not necessary if you flash a new rom, other sayed it could still be necessary... now i rooted with the app and did a new backup that i'm coping on PC
reading further it says: to wipe, install rom, and flash boot.img after
"Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it."
Click to expand...
Click to collapse
yes you can do it that way, i usually flash first but sometimes it does not work, so just flash it last as it says in the tutorial

after root, with the same steps, the ROM starts... but
touch screen is not working :crying:
now i'm gonna look arond to see if i found some post about that

this (kernel patch) solved my last issue
http://miuiandroid.com/community/threads/hox-miui-v5-official-release.20215/page-2

al404 said:
this (kernel patch) solved my last issue
http://miuiandroid.com/community/threads/hox-miui-v5-official-release.20215/page-2
Click to expand...
Click to collapse
So everything working now ?
Sent from my underpants using Daz and Lenor summertime

YES :good: without that path touchscreen wasn't working :victory:
hope is not going to mess all up with first update

[Q] Fastboot.exe Crash Nexus 7 2013

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!

Really need help, google flash gone bad

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!!