Related
Out of no where I got a message on my phone, saying that my sd card was unmounted. I wasn't doing anything other than I normally would. Now when I try to access my SD card, it's not even seen by the G2. I've formatted it to FAT32 and nothing, I've restarted the phone multiple times and no dice, and I have given it time to rest. I cannot seem to find the issue with this, but I have heard about some issue with the SD card latch thing. What can I do to fix this issue? Any advice would be greatly welcome
Have you tried another SD card to see if it is the phone or the SD card giving you problems?
Sent from my SilverBullet 'HTCDesireZ running CM7'
Fireflyz said:
Out of no where I got a message on my phone, saying that my sd card was unmounted. I wasn't doing anything other than I normally would. Now when I try to access my SD card, it's not even seen by the G2. I've formatted it to FAT32 and nothing, I've restarted the phone multiple times and no dice, and I have given it time to rest. I cannot seem to find the issue with this, but I have heard about some issue with the SD card latch thing. What can I do to fix this issue? Any advice would be greatly welcome
Click to expand...
Click to collapse
Is it the SD card that came with the g2 or a different one?
I had this happen with a 32GB patriot class 10 I put in my G2. It would corrupt and do the exact same until I full formatted it on a PC. (long story short it's a issue with the sdcard itself and has to be formatted a special way, but it's ONLY THIS CARD).
Try a different card, if a different card works then full format the nonworking card. If that still doesn't work then there may be a off chance (a very very off chance) that the card went bad.
Went to the T-mobile store and tried 2 different sd cards. Neither of them worked... any way to fix this on my own? If not, then can I un-root my G2 without an SD? If I call up costumer care, they'll probably want me to send my G2 in and will notice it has been rooted and such. I heard somewhere that as long as it looks stock, they won't do/say anything... not sure if this is true though..
Fireflyz said:
Went to the T-mobile store and tried 2 different sd cards. Neither of them worked... any way to fix this on my own? If not, then can I un-root my G2 without an SD? If I call up costumer care, they'll probably want me to send my G2 in and will notice it has been rooted and such. I heard somewhere that as long as it looks stock, they won't do/say anything... not sure if this is true though..
Click to expand...
Click to collapse
Yikes, I'm not sure if you can if it can't read a image off the sdcard to flash.
You do have a legit hardware issue that rooting couldn't cause though.
The sd slot is not fixable most likely.
But getting your phone back to stock is.
if you have an eng s-off bootloader you can usually fasboot update the PC10IM.zip if you rename it to update.zip and place it in your adb/fastboot fodler on your pc like so:
fastboot update
ot
fastboot update update.zip
not sure, it's been a while
if you have an s-on bootloader have no fear, you can still get to stock, it's a little more complicated.
find a PC10IMG.zip that has a stock recovery.img in it.
extract it and place it somwhere it is easy to locate and the path is short for ease. like c:\
download a flashable recovery update zip for the stock rom you want to load back on the device. keep it for later.
download this special recovery image:
View attachment CWM-3.0.2.4-sd-spoof.zip
extract the image and flash it from the OS, you'll need to boot your phone first then when it is up and running you need to enable usb debugging and use it to push the recovery image to your /data partition
adb push recovery.img /data
or the path is required if you put it elsewhere like c:\
adb push c:\recovery.img /data
it should be in /data/recovery.img
then open terminal or since you shoudl have adb open you can use 'adb shell' then type enter to enter a root shell
flash_image recovery /data/recovery.img
it should just spir out a
#
that means it's successful, reboot to recovery
now you will be able to push items to the root of your /data folder (or anywhere in /data really)
when you select the flash zip from recovery option it will spoof the /data folder as the /sdcard and display the contents of your /data folder rather than the /sdcard allowing you to flash without needing the sdcard to work.
now flash any stock rom from recovery.
while still in recovery you will need to flash the stock recovery image as well once you verify the stock rom is in place and boots. you will still have CWM but you wont be rooted so flashing from recovery is required. it can be flashed with the same commands you used to flash the other recovery from the OS
if you get a return of error -1 when you try to use the flash_iamge command to flash recovery PM me, i have a fix for that as well. it should be updated though not to do that any more.
ONCE YOU FLASH THE STOCK RECOVERY AND STOCK ROM, unless you manually root again, which will be tricky, you are stuck.
hope this has been helpful.
amazinglarry311 said:
The sd slot is not fixable most likely.
But getting your phone back to stock is.
if you have an eng s-off bootloader you can usually fasboot update the PC10IM.zip if you rename it to update.zip and place it in your adb/fastboot fodler on your pc like so:
fastboot update
ot
fastboot update update.zip
not sure, it's been a while
if you have an s-on bootloader have no fear, you can still get to stock, it's a little more complicated.
find a PC10IMG.zip that has a stock recovery.img in it.
extract it and place it somwhere it is easy to locate and the path is short for ease. like c:\
download a flashable recovery update zip for the stock rom you want to load back on the device. keep it for later.
download this special recovery image:
View attachment 582547
extract the image and flash it from the OS, you'll need to boot your phone first then when it is up and running you need to enable usb debugging and use it to push the recovery image to your /data partition
adb push recovery.img /data
or the path is required if you put it elsewhere like c:\
adb push c:\recovery.img /data
it should be in /data/recovery.img
then open terminal or since you shoudl have adb open you can use 'adb shell' then type enter to enter a root shell
flash_image recovery /data/recovery.img
it should just spir out a
#
that means it's successful, reboot to recovery
now you will be able to push items to the root of your /data folder (or anywhere in /data really)
when you select the flash zip from recovery option it will spoof the /data folder as the /sdcard and display the contents of your /data folder rather than the /sdcard allowing you to flash without needing the sdcard to work.
now flash any stock rom from recovery.
while still in recovery you will need to flash the stock recovery image as well once you verify the stock rom is in place and boots. you will still have CWM but you wont be rooted so flashing from recovery is required. it can be flashed with the same commands you used to flash the other recovery from the OS
if you get a return of error -1 when you try to use the flash_iamge command to flash recovery PM me, i have a fix for that as well. it should be updated though not to do that any more.
ONCE YOU FLASH THE STOCK RECOVERY AND STOCK ROM, unless you manually root again, which will be tricky, you are stuck.
hope this has been helpful.
Click to expand...
Click to collapse
S-off and S-on bootloader? Is that the same as having S-on/S-off in general?
Larry was banned this morning, apparently being helpful isnt something highly valued around here.
yeah, you achieve s-off using gfree and you can decide if you want to install the ENG bootloader.
If you did, it should say ENG S-OFF instead of SHIP S-OFF
if fastboot allows you to do anything remotely you're in a good shape and that means you probably have a ENG bootloader.
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.
Hello, I flashed PA 4.4.4 on my i9250 and now I wanted to go back to 4.3. Unfortunately I have a problem because my 4.3 backup isn't visible anymore, directories are messed up by 4.4.4. Found a way to make it visible (had to put an old backup to /data/media/clockworkmod/backup/) but I get an error while trying to restore it. I even flashed my previous cwm and installed cm 10 (the one that I've got my last backup from) but now all i get is a bootloop... I think it's caused by messed directories. How to get rid of those f***ing 0 emulated location?
1. Download JB factory image for your NExus from here: https://developers.google.com/android/nexus/images
2. In the recovery make swipe data/factory reset
3. power off and boot into fastboot mode...
3. Flash system partition through fastboot. (You need Fastboot drivers for Windows..) (system.img):
fastboot flash system system.img
and flash boot.img :
fastboot flash boot boot.img
4. Boot.
Nb. You have to extract the img files from the zip package.. if you want you can use flash all batch file (.bat) or script file (.sh) (depends of the OS...) but if you use it, then it'll flash everything automatically and wipes everything from the phone.
Hm I hoped that will do without going back to stock. I suppose this operation will relock my bootloader?
casioman1 said:
Hm I hoped that will do without going back to stock. I suppose this operation will relock my bootloader?
Click to expand...
Click to collapse
Only fastboot oem lock command locks your nexus's boot loader.
About "0" and some other directories, these are new on JB 4.2 or 4.3... you can remove them but it's useless... so I recommend to keep them.. 0 is like the current user,, for e.g 3 is the second user (multi user)...
CWM backups: I am not really sure... you can remove md5 stuff and maybe recovery lets you flash the files.. Also use the recovery with what you made the backup if newer CWM recoveries won't flash it
Hell yeah! Finally got it done. This it how:
1. flashed an old recovery (the one that I've got my last backup from) but still got a bootloop with an old cm10.
2. installed the newest working wersion of CM just to put my backup into different directory and make it visible (make sure you copy both folders with a date of your backup AND blobs because without the latter one it won't restore giving you an error)
3. voila, you've got a fully restored system
Thanks Carlos_Manuel for your help
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!
I have a Zenfone 2 (ZE551ML) with the latest WW firmware (2.20.40.97) which is obviously causing trouble with my phone. I want to revert back to the older firmware version (2.20.40.90 or even 2.20.40.63).
Is something like that possible on my phone? I've tried every resource that I could find online and nothing seems to work. It's not rooted - it's as is from the shop just with the latest update. I've tried sideloading but that obviously works only when updating firmware not downgrading. I've tried downloading recovery images and using fastboot to flash them but nothing happens.
So I ask again is it possible to downgrade stock firmware and if yes are there reliable tested instructions on how to do it?
Refer to http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 and follow the steps of root method 1 (pre-rooted image) to flash boot, droidboot and recovery images for the firmware version you want to revert to. However, DON'T download and flash the pre-rooted system image. Instead download the full firmware zip from ASUS, rename it as MOFD_SDUPDATE and place it on your external SD card. Erase your data and then boot back into the bootloader and then recovery mode. It should then install the firmware from your SD card.
kanagawaben said:
Refer to http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 and follow the steps of root method 1 (pre-rooted image) to flash boot, droidboot and recovery images for the firmware version you want to revert to. However, DON'T download and flash the pre-rooted system image. Instead download the full firmware zip from ASUS, rename it as MOFD_SDUPDATE and place it on your external SD card. Erase your data and then boot back into the bootloader and then recovery mode. It should then install the firmware from your SD card.
Click to expand...
Click to collapse
Thanks for the info! However I need help with the last part. I have no problem following up to the part about sending fastboot flash commands but what exactly does "Erase your data" mean? After I send the fastboot commands I am still in the bootloader screen. Do I proceed perhaps to the recovery mode to wipe/erase the cache? I am also wondering is it enough to just put the MOFD_SDUPDATE file in the root of the SD card? And do I need an unlocked bootloader to perform all these actions?
I understand that these questions might seem a bit noobish to experienced Android hackers but my experience on that field is limited to just doing one "unofficial" upgrade of my Nexus 4 to Lollipop so I would be grateful for any help.
EDIT: It seems I managed to figure out the correct order of things however when I reboot to bootloader I get the following error.
Code:
E:file path:/sdcard/MOFD_SDUPDATE.zip
E:failed to map file
SD installation aborted.
EDIT 2: It was actually an error on my end. I had my Windows set in a way to display file extensions so I accidentally named the file MOFD_SDUPDATE instead of MOFD_SDUPDATE.zip. Renaming the file did the trick.
I had to make a separate post just to thank you kanagawaben. Thanks! You are a life saver :victory: I've managed to successfully revert my phone to stock 2.20.40.90.
The best part is it resolves an issue with the proximity sensor which was obviously introduced with 2.20.40.97 (http://forum.xda-developers.com/zenfone2/help/proximity-sensor-inconsistently-t3224700/)