Related
I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
did you install any mods, kernels, change any files? if so its been documented all over the forums.
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
danielvago said:
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
Click to expand...
Click to collapse
It didn't work. I have no idea what to do, can I sideload the APK?
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
danielvago said:
It didn't work. I have no idea what to do, can I sideload the APK?
Click to expand...
Click to collapse
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
Theory said:
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
Click to expand...
Click to collapse
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
wantabe said:
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
Click to expand...
Click to collapse
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
What is the error when the OTA fails?
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
try incremental install
danielvago said:
I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
Click to expand...
Click to collapse
try sideloading 4.4.1 first. .and then sideload 4.4.2 after that. see if that works.
EddyOS said:
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
Click to expand...
Click to collapse
I just updated a new 2012 N7 from 4.1 to 4.4.2 and I couldn't get removing the -w flag to work. I think the script needs more editing than just removing the -w part. Something new I had never tried before which I actually don't personally have much use for because it still flashes the stock recovery over a custom recovery if you are using one. Anyway.. flashing the bootloader and radio separately and then flashing the update zip with "fastboot update image-hammerhead-kot49h.zip" would be a little bit of a shortcut versus flashing ALL of the images and you don't lose data.
Never had an issue myself, but I always prefer to flash each image manually one at a time
EddyOS said:
Never had an issue myself, but I always prefer to flash each image manually one at a time
Click to expand...
Click to collapse
I've always flashed each image separately also, I was just being lazy and experimenting. Removing the -w from the .bat and/or the .sh wouldn't work for me.
---------- Post added at 10:33 AM ---------- Previous post was at 10:27 AM ----------
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
wantabe said:
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
Click to expand...
Click to collapse
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
danielvago said:
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
Click to expand...
Click to collapse
Your path to adb isn't correct. Put the zip file in the same folder as adb
jd1639 said:
Your path to adb isn't correct. Put the zip file in the same folder as adb
Click to expand...
Click to collapse
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
danielvago said:
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
Click to expand...
Click to collapse
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
jd1639 said:
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
Click to expand...
Click to collapse
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
danielvago said:
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
Click to expand...
Click to collapse
Ok, so you're doing an adb sideload while in recovery?
jd1639 said:
Ok, so you're doing an adb sideload while in recovery?
Click to expand...
Click to collapse
Yes.
I successfully rooted and achieved an unlocked bootloader with S-OFF on my Verizon HTC One M8 and also flashed TWRP 2.7.0.2. I downloaded a rom (without an SD card). I booted into recovery and i made a backup (not noticing that one of the lines read "unable to mount '/system". I then wiped and attempted to flash the rom only to find out that i can't find it in my file system. So i put the rom on an SD card and mounted it and tried to flash it, i get this message:
E: Unable to mount '/system'
E: Unable to open zip file.
Error Flashing zip '/external_sd/Roms?ViperOneM*_1.2.0.zip'
Updating partition details...
E: Unable to mount '/system'
So i'm stuck with a boot loader, an unmountable file system, and unable to flash a rom.
I've tried Fix permissions, I've tried mounting the "system" but all that mounts is 'cache' 'data' and 'micro SDcard'.
I hope my nerves are getting the best of me and i can't see something that's right in front of me!
Edit: Flashed CWM Recovery. Trying to install ROM from SD Card results in "Installation Aborted". When i try to side load it hangs at 81%.
Did you flash TWRP using terminal emulator mode as described on the official website for 2.7.0.2? If so you overwrote the system partition. Try flashing the recovery using the fastboot method as this will put the recovery in the right place. Then boot into the bootloader, choose recovery. I think this will get you TWRP in the recovery partition. Once there try flashing a ROM (although o would suggest something closer to stock like Skyfall).
I think what is happening is since the instructions for flashing TWRP via terminal emulator list the wrong partition, when you boot up to system it seems like you are booting to recovery because TWRP shows up. But you're actually on the system partition so when you try to flash a ROM you get an error because you can't mount the partition you're in.
I'm far from an expert in any of this so anyone who is please correct me.
dsEVOlve said:
Did you flash TWRP using terminal emulator mode as described on the official website for 2.7.0.2? If so you overwrote the system partition. Try flashing the recovery using the fastboot method as this will put the recovery in the right place. Then boot into the bootloader, choose recovery. I think this will get you TWRP in the recovery partition. Once there try flashing a ROM (although o would suggest something closer to stock like Skyfall).
I think what is happening is since the instructions for flashing TWRP via terminal emulator list the wrong partition, when you boot up to system it seems like you are booting to recovery because TWRP shows up. But you're actually on the system partition so when you try to flash a ROM you get an error because you can't mount the partition you're in.
I'm far from an expert in any of this so anyone who is please correct me.
Click to expand...
Click to collapse
I did flash TWRP as described. I used Terminal from my Macbook. I did some researching and i did try flashing using the fast boot method. I'm just so stumped!
First of all you aren't bricked. Have you tried using side load to flash the ROM? Try flashing another recovery too.
Sent from my HTC6525LVW using Tapatalk
SimplyNando said:
I did flash TWRP as described. I used Terminal from my Macbook. I did some researching and i did try flashing using the fast boot method. I'm just so stumped!
Click to expand...
Click to collapse
The above suggestion to try and Sideload the ROM install is a good idea. Basically, put the ROM zip file in your platform-tools folder of adb. Then boot to TWRP recovery, choose "sideload" and then issue the command "adb sideload [filename.zip]" (Instructions are found HERE.)
If that doesn't work, have you tried flashing Clockwork Recovery? You may have better luck with that in regards to mounts and/or flashing the ROM...
There's always USB OTG as well
Sent from my HTC6525LVW using Tapatalk
I found THIS thread (for ASUS Transformer though).
What may have happened (if I'm reading the above thread correctly) is that your /system doesn't exist.
Taking a complete stab at a fix, you may be able to use fastboot to flash a working "system.img" file. (Anyone with more expertise, please confirm or refute this...)
EDIT: Found THIS post in the "Official" TWRP release 2.7.0.0 thread I wonder if perhaps this is what happened to you?
WorldOfJohnboy said:
I found THIS thread (for ASUS Transformer though).
What may have happened (if I'm reading the above thread correctly) is that your /system doesn't exist.
Taking a complete stab at a fix, you may be able to use fastboot to flash a working "system.img" file. (Anyone with more expertise, please confirm or refute this...)
EDIT: Found THIS post in the "Official" TWRP release 2.7.0.0 thread I wonder if perhaps this is what happened to you?
Click to expand...
Click to collapse
That does seem like it could be the problem. I just flashed CWM recovery instead but it's still the sam problem. Still can't flash a rom, i also tried using sideboot.
SimplyNando said:
That does seem like it could be the problem. I just flashed CWM recovery instead but it's still the sam problem. Still can't flash a rom, i also tried using sideboot.
Click to expand...
Click to collapse
You might have to find a factory image, an RUU I am not sure if one exists but it will write the partitions. I think somehow your actual system partition was erased which is why it cannot be mounted. Pretty much, your only hope is an RUU or a zipped factory image.
123421342 said:
You might have to find a factory image, an RUU I am not sure if one exists but it will write the partitions. I think somehow your actual system partition was erased which is why it cannot be mounted. Pretty much, your only hope is an RUU or a zipped factory image.
Click to expand...
Click to collapse
I wouldn't be able to get that from the system dump located http://forum.xda-developers.com/showthread.php?t=2695171 ? Is there any other possible explanation??
SimplyNando said:
I wouldn't be able to get that from the system dump located http://forum.xda-developers.com/showthread.php?t=2695171 ? Is there any other possible explanation??
Click to expand...
Click to collapse
no because it is not a flashable zip. Factory image or RUU means the bootloader will literally write the partition. Recovery will mount the partition and write information to it. It cannot create the partition itself which I think is your issue.
Assuming your recovery is fine..this is what I did to fix my self inflicted "soft brick" on Saturday...I mistakenly hit format system instead of just data and cache while trying to start over.
I am running cwm 6047..and for whatever reason the sideload failed with an error trying to sideload flash sky fall.
So I did an adb push skyfall.zip /sdcard/0 and was then able to flash the zip from internal storage.
Hope that helps with your situation.
bakemcbride21 said:
Assuming your recovery is fine..this is what I did to fix my self inflicted "soft brick" on Saturday...I mistakenly hit format system instead of just data and cache while trying to start over.
I am running cwm 6047..and for whatever reason the sideload failed with an error trying to sideload flash sky fall.
So I did an adb push skyfall.zip /sdcard/0 and was then able to flash the zip from internal storage.
Hope that helps with your situation.
Click to expand...
Click to collapse
Yep. You have a bad download. Download a new ROM on your computer...boot to recovery and do a adb sideload or push
Sent from my HTC One M8
Just had a thought... did you flash the insecure Kernel (found HERE) ever? You may not have a writeable /system?
Flash the Kernel, then reflash the official TWRP (both in Fastboot) and see if that works...
WorldOfJohnboy said:
Just had a thought... did you flash the insecure Kernel (found HERE) ever? You may not have a writeable /system?
Flash the Kernel, then reflash the official TWRP (both in Fastboot) and see if that works...
Click to expand...
Click to collapse
Kernel runs inside the rom and the system becomes writeable in the ROM so that won't do anything. I'm pretty convinced he is missing the partition.
Sent from my HTC6525LVW using Tapatalk
Hi did you manage to sort this issue out as i'm having the same issue. it won't install backups or open zip files of the rom's. no matter what i do it won't flash the rom's. i've tried side loading on both cwm and TWRP - as i just said swapped from both recoveries. Managed to mount the sd card and put a new rom on it but won't flash from there and I've tried to move it to internal but fails.
I can't find my stock recovery an a nandroid back up either. Any help would be great
thanks
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Oh it does let me flash a Kernal zip tho?
jerico9 said:
Hi did you manage to sort this issue out as i'm having the same issue. it won't install backups or open zip files of the rom's. no matter what i do it won't flash the rom's. i've tried side loading on both cwm and TWRP - as i just said swapped from both recoveries. Managed to mount the sd card and put a new rom on it but won't flash from there and I've tried to move it to internal but fails.
I can't find my stock recovery an a nandroid back up either. Any help would be great
thanks
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Oh it does let me flash a Kernal zip tho?
Click to expand...
Click to collapse
did you try formatting internal yet?
Just for anyone withthe same issue. It ended up being not dnough memory to flash the recovery or the new rom....deerrrrrrr!!!
Haha, cant believe it had me stumped for 5 days trying everything and anything. Formatting would have helped aswell So thanks for the suggestion
jerico9 said:
Just for anyone withthe same issue. It ended up being not dnough memory to flash the recovery or the new rom....deerrrrrrr!!!
Haha, cant believe it had me stumped for 5 days trying everything and anything. Formatting would have helped aswell So thanks for the suggestion
Click to expand...
Click to collapse
I have an HTC version of fastboot/adb that will work on a low memory pc. It's posted in my ruu thread.
dottat said:
I have an HTC version of fastboot/adb that will work on a low memory pc. It's posted in my ruu thread.
Click to expand...
Click to collapse
I mean the device memory was low, so couldn't flash as no room on the device
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!
Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
roadblock217 said:
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!
Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
Click to expand...
Click to collapse
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Dragbike Racer said:
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Click to expand...
Click to collapse
Tried..doesnt work for me
I can get it to boot past the recovery area, but only stays on the white screen with the green HTC logo...
EDIT:::
I want to try it again, but now somehow I have S ON....and it says TAMPERED, below that UNLOCKED in fastboot..
Really frustrated..
Dragbike Racer said:
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Click to expand...
Click to collapse
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
You can get into recovery...it won't let you restore a back up or nothing ?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
---------- Post added at 12:22 AM ---------- Previous post was at 12:17 AM ----------
roadblock217 said:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
Click to expand...
Click to collapse
Maybe sonic can get you s-off if all else fails with his java card. I'm not sure in your situation but I know he can do it as I used it. But I would use that as last resort
Sent from my HTC6525LVW using XDA Premium 4 mobile app
roadblock217 said:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
Click to expand...
Click to collapse
So you were S-OFF and you somehow got turned to S-ON...??
I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..
best bet?
get into fastboot/bootloader, and put on a custom recovery.
then, get the TWRP nandroid of the OTA, restore to that.
then, weaksauce/S-OFF
and then you should be back to normal.
If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.
opion 2
get TWRP on with fastboot
then
adb sideload any ROM to it and then get back to S-OFF
since you are unlocked you should be ok to do this without being htc dev unlocked.
you could also try htc dev, but i think that is locked.
sorry trying to think of anything else.
andybones said:
So you were S-OFF and you somehow got turned to S-ON...??
I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..
best bet?
get into fastboot/bootloader, and put on a custom recovery.
then, get the TWRP nandroid of the OTA, restore to that.
then, weaksauce/S-OFF
and then you should be back to normal.
If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.
opion 2
get TWRP on with fastboot
then
adb sideload any ROM to it and then get back to S-OFF
since you are unlocked you should be ok to do this without being htc dev unlocked.
you could also try htc dev, but i think that is locked.
sorry trying to think of anything else.
Click to expand...
Click to collapse
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
roadblock217 said:
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2725001
andybones said:
http://forum.xda-developers.com/showthread.php?t=2725001
Click to expand...
Click to collapse
Thanks...just downloaded and am going to try...
What I'm concerned about is not being able to mount /system now...this is so weird
roadblock217 said:
Thanks...just downloaded and am going to try...
What I'm concerned about is not being able to mount /system now...this is so weird
Click to expand...
Click to collapse
because of this, it most likely will not flash the nandroid then as system is a big part of the ROM and needs to be mounted.
you may have to do what was explained earlier and wipe the Internal, and then you may be able to re-do these steps.
so first try it out.
if it doesnt work, I would then wipe the 5 things instead of the 4
1) data
2) cache
3) dalvik cache
4) system
5) Internal storage (this will remove all your internal storage!)
then reboot from recovery into bootloader, then back into recovery and see if system is mounted, if it is, you can go ahead and either do the nandroid backup or an adb sideload. -- your choice
now,
if NONE of that works,
download the "RUU" that was put together and that *should* fix you right up.
andybones said:
http://forum.xda-developers.com/showthread.php?t=2725001
Click to expand...
Click to collapse
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
roadblock217 said:
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
Click to expand...
Click to collapse
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...
this is something you should have had backed up..
but, make yourself a dummy nand backup to create the folder..
just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..
the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
andybones said:
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...
this is something you should have had backed up..
but, make yourself a dummy nand backup to create the folder..
just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..
the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
Click to expand...
Click to collapse
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
roadblock217 said:
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
Click to expand...
Click to collapse
Awesome!
Very welcome.
So what was the result fix?
Did you have to wipe Internal from system not mounting?
Or did the adb sideload work?
Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?
Glad that your back up and running.
andybones said:
Awesome!
Very welcome.
So what was the result fix?
Did you have to wipe Internal from system not mounting?
Or did the adb sideload work?
Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?
Glad that your back up and running.
Click to expand...
Click to collapse
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!
Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
roadblock217 said:
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!
Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
Click to expand...
Click to collapse
It's possible after so long you didn't give the ROM long enough to boot up?
Sounds like RUU might be a cause from flashing AOSP, threads like this are good to warn people, and for when it happens to others, they can read this and know what to do. Maybe think of a new title that could help those in a search to find this thread?
Hello friends, I bought the ASUS Transformer Pad 300T and just a week later I had the great idea of instal TWRP for installing my appreciate CM11, but when I installed TWRP and I was abut to install the CM11, I see:
E:Unable to mount '/data' (tw_mount)
E:failed to mount /data (no such file or directory)
When I saw that messages I entered in panic and I wiped all
I'm afraid I'll have to send it to repair, and the fill will hurt. So I hope somebody help me. I'll upload a photo soon.
Thanks.
opamx said:
Hello friends, I bought the ASUS Transformer Pad 300T and just a week later I had the great idea of instal TWRP for installing my appreciate CM11, but when I installed TWRP and I was abut to install the CM11, I see:
E:Unable to mount '/data' (tw_mount)
E:failed to mount /data (no such file or directory)
When I saw that messages I entered in panic and I wiped all
I'm afraid I'll have to send it to repair, and the fill will hurt. So I hope somebody help me. I'll upload a photo soon.
Thanks.
Click to expand...
Click to collapse
In what way did you wipe it? From the bootloader or from TWRP?
cmendonc2 said:
In what way did you wipe it? From the bootloader or from TWRP?
Click to expand...
Click to collapse
I wiped the rom, in the site I downloaded the TWRP the instructions were to install the rom after cleaning cache, next I wiped the rom I searched for another recovery and I read this version is dangerous becouse it dont have any security advisements in the old posts, and if I wipe with that recovery y couldnt repair it becuse it dont have ADB or other methods for flashing another recvery.
opamx said:
I wiped the rom, in the site I downloaded the TWRP the instructions were to install the rom after cleaning cache, next I wiped the rom I searched for another recovery and I read this version is dangerous becouse it dont have any security advisements in the old posts, and if I wipe with that recovery y couldnt repair it becuse it dont have ADB or other methods for flashing another recvery.
Click to expand...
Click to collapse
So does the TWRP still work? You can put a ROM on the SDcard and flash it from there.
I think I'm in a similar boat with the OP. I'm getting rid of this intensely disappointing tablet in the next day or two. I booted into TWRP and selected the "Wipe Data" option, figuring that it'd be a good move to hand it over to new owner without any traces of my personal data on it. Well, since formatting it, I can't get Android to fully boot up. I installed PACman and Gapps from a microSD card, but it never gets past the splash screen where it says "LOADING". I really need to get this POS up and running ASAP, preferably with the least possible amount of downloading involved. My connection just got throttled down, so I'm hoping I don't have to download any huge programs. Any ideas?
But...
But the recovery can't mount /data folder and I can't install anything.
ApexPredatorBoids said:
I think I'm in a similar boat with the OP. I'm getting rid of this intensely disappointing tablet in the next day or two. I booted into TWRP and selected the "Wipe Data" option, figuring that it'd be a good move to hand it over to new owner without any traces of my personal data on it. Well, since formatting it, I can't get Android to fully boot up. I installed PACman and Gapps from a microSD card, but it never gets past the splash screen where it says "LOADING". I really need to get this POS up and running ASAP, preferably with the least possible amount of downloading involved. My connection just got throttled down, so I'm hoping I don't have to download any huge programs. Any ideas?
Click to expand...
Click to collapse
What bootloader version do you have and what twrp version?
---------- Post added at 11:25 AM ---------- Previous post was at 11:24 AM ----------
opamx said:
But the recovery can't mount /data folder and I can't install anything.
Click to expand...
Click to collapse
Did you try umounting everything and remounting everything in the twrp settings?
cmendonc2 said:
What bootloader version do you have and what twrp version?
---------- Post added at 11:25 AM ---------- Previous post was at 11:24 AM ----------
Did you try umounting everything and remounting everything in the twrp settings?
Click to expand...
Click to collapse
The option mount /Data is blocked, I can`t do anything, maybe with a backup will work. And my TWRP version is 2.2.1.5.
opamx said:
The option mount /Data is blocked, I can`t do anything, maybe with a backup will work. And my TWRP version is 2.2.1.5.
Click to expand...
Click to collapse
Hi
This may be a long shot but I encountered a similar problem and resolved it by flashing the recovery and kernel from here - http://forum.xda-developers.com/showthread.php?t=2625580. See the second post.
In my case I flashed the recovery from the above post, formatted data to f2fs from recovery, then installed the crombi-kk rom with the ”Don't install a kernel” option, then flashed the kernel from the above post.
Like I said, long shot, and this assumes you can run the format data option in twrp, but may be worth a crack...
Good luck.
Who has a Liunx PC ?
That is where I would start ....
There are ways to fix this .....
Thx Josh
lj50036 said:
Who has a Liunx PC ?
That is where I would start ....
There are ways to fix this .....
Thx Josh
Click to expand...
Click to collapse
I can't do anything with the /Data partition becouse the file is empty... maybe if somebody can upload the content of that file, maybe I'll be able to put a rom into the tablet.
Well if you cant mount it how are you going to write to it ?
Do you have a linux PC ?
Thx Josh
lj50036 said:
Well if you cant mount it how are you going to write to it ?
Do you have a linux PC ?
Thx Josh
Click to expand...
Click to collapse
I have Windows 8.1 PRO and if someone give me the files, maybe I'll be able to put them into the /Data file wih the file manager of the TWRP
Hi,
Because I couldn't wait until the cos13 ota hit my area.
I downloaded the cos13 incremental update zip file (link from this thread) https://forums.oneplus.net/threads/cos-13-the-perfect-os-for-oneplus-one-i-love-it.441003/
I first confirmed that I was on the correct version for it to update (cos 12.1.1 YOG7DAS2K1)
Everything went well, it updated, but now the phone is stuck on the bootlogo really long, then starts optimising the apps reboots and does this again.
also the new bootlogo has this mod ready thing at the bottom now (not sure if that's normal)
I can still boot into the stock recovery and fastboot mode, but can't seem to acces the file system on my pc.
Any help on getting this thing working again would be great!
Thanks in advance
-Isaac
easiest way is to factory reset from recovery, if you can afford it.
First off it is stuck on boot animation, wipe data (factory reset) from recovery and you're good to go hopefully
Transmitted via BACON
ipsmaxes said:
Hi,
Because I couldn't wait until the cos13 ota hit my area.
I downloaded the cos13 incremental update zip file (link from this thread) https://forums.oneplus.net/threads/cos-13-the-perfect-os-for-oneplus-one-i-love-it.441003/
I first confirmed that I was on the correct version for it to update (cos 12.1.1 YOG7DAS2K1)
Everything went well, it updated, but now the phone is stuck on the bootlogo really long, then starts optimising the apps reboots and does this again.
also the new bootlogo has this mod ready thing at the bottom now (not sure if that's normal)
I can still boot into the stock recovery and fastboot mode, but can't seem to acces the file system on my pc.
Any help on getting this thing working again would be great!
Thanks in advance
-Isaac
Click to expand...
Click to collapse
For whatever reason...Cyanogen decided to make Google APP mandatory to run COS 13. If you remove the app or disable it you'll get a magnificiente bootloop. Maybe you removed Google App?
Hi it my case too. And I did disable some anoying Google apps.
mathsjob said:
Hi it my case too. And I did disable some anoying Google apps.
Click to expand...
Click to collapse
In my experience, it's Google App the only one causing problem, I removed Google Play Books, Play Videos, Play Music, Google+, etc. and not a problem
Any way to solve this issue ? Wipe data, partition and Media does nothing.
Is reflashing CM12 from ADB works ?
mathsjob said:
Any way to solve this issue ? Wipe data, partition and Media does nothing.
Is reflashing CM12 from ADB works ?
Click to expand...
Click to collapse
I fixed the problem dirty flashing again the ROM but if you already wiped data and flashed again the ROM, you may have another different problem causing the bootloop.
Maybe I can try to flash ROM again... But as I Wiped Data, I don't have the ROM available in my OPO and I don't know how to flash using another method
mathsjob said:
Maybe I can try to flash ROM again... But as I Wiped Data, I don't have the ROM available in my OPO and I don't know how to flash using another method
Click to expand...
Click to collapse
Did you wipe media storage??
Do you have TWRP installed?? There is an option to ABD sideload a ROM
brath23 said:
Did you wipe media storage??
Do you have TWRP installed?? There is an option to ABD sideload a ROM
Click to expand...
Click to collapse
Yes I wiped data, cache(first try) and media after that (was not a good idzea)... I don't have anything special installed, only stock software
mathsjob said:
Yes I wiped data, cache(first try) and media after that (was not a good idzea)... I don't have anything special installed, only stock software
Click to expand...
Click to collapse
If you don't have TWRP recovery, you could try to fastboot this ROM: http://builds.cyngn.com/factory/bacon/cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18.zip
There are plenty of guides to do this, even some scripts to make the process kind of automatic.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
More guides on XDA:
http://forum.xda-developers.com/showpost.php?p=63294096&postcount=4
And some script to make the process easier.
https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/
Make sure you choose your Oneplus ONE version correctly (16GB/64GB)
Thanks a lots for your quick answers, I will try using your ADB process.
Hey so yeah I already factory reset from recovery,
I didn't wipe my data yet because I still want to recover some files from the phone.
and yeah I did have almost every google app disabled (not removed).
after a factory reset these are normally activated again though? so idk what's up with that.
also does somebody know a way to retreive all files from the phone, through adb maybe? since I can't acces the file system on my pc rn
I'm gonna try to fastboot that rom you linked later (after I attempt to recover my files)
brath23 said:
For whatever reason...Cyanogen decided to make Google APP mandatory to run COS 13. If you remove the app or disable it you'll get a magnificiente bootloop. Maybe you removed Google App?
Click to expand...
Click to collapse
I did it yesterday
A disaster....
tommy92tc said:
I did it yesterday
A disaster....
Click to expand...
Click to collapse
Once you disable wake up, keep awake, Google Now, location history and a lot of permissions more for Google App, Cyanogen OS 13 runs pretty good
brath23 said:
Once you disable wake up, keep awake, Google Now, location history and a lot of permissions more for Google App, Cyanogen OS 13 runs pretty good
Click to expand...
Click to collapse
It's kinda 'mean' that they force you to have these on. Once I have my phone up and running again on cos13 and I disable the google app it's just instantly going to bootloop once I reboot?
if so, I imagine alot more people are gonna have trouble with this
ipsmaxes said:
It's kinda 'mean' that they force you to have these on. Once I have my phone up and running again on cos13 and I disable the google app it's just instantly going to bootloop once I reboot?
if so, I imagine alot more people are gonna have trouble with this
Click to expand...
Click to collapse
Same here, and no way to dirty flash the rom to get out of bootloop, I had to wipe everything
ipsmaxes said:
It's kinda 'mean' that they force you to have these on. Once I have my phone up and running again on cos13 and I disable the google app it's just instantly going to bootloop once I reboot?
if so, I imagine alot more people are gonna have trouble with this
Click to expand...
Click to collapse
Yes, it happened to me. Then I dirty flashed again the ROM, but I was having bootloop as well . I had to remove again Google APP from TWRP Explorer (I think it's called Velvet in /system/priv-app), reboot again in another bootloop and dirty flashed again the ROM. Lost a lot of time but I didn't want to lost /data and setup everything again.
Once you disable an APP is saved in some file in /data partition so simply dirty flashing ROM won't solve it.
---------- Post added at 05:04 PM ---------- Previous post was at 04:53 PM ----------
tommy92tc said:
Same here, and no way to dirty flash the rom to get out of bootloop, I had to wipe everything
Click to expand...
Click to collapse
I was able to fix it without wipe.
Steps to fix bootloop after disabling Google APP
Enter TWRP and remove /system/priv-app/Velvet folder in File Manager
Reboot system. It will go into bootloop again but at least it will remove Google APP from the list of disabled apps
Enter TWRP again and dirty flash ROM again.
Reboot and it should be ok
brath23 said:
Yes, it happened to me. Then I dirty flashed again the ROM, but I was having bootloop as well . I had to remove again Google APP from TWRP Explorer (I think it's called Velvet in /system/priv-app), reboot again in another bootloop and dirty flashed again the ROM. Lost a lot of time but I didn't want to lost /data and setup everything again.
Once you disable an APP is saved in some file in /data partition so simply dirty flashing ROM won't solve it.
---------- Post added at 05:04 PM ---------- Previous post was at 04:53 PM ----------
I was able to fix it without wipe.
Steps to fix bootloop after disabling Google APP
Enter TWRP and remove /system/priv-app/Velvet folder in File Manager
Reboot system. It will go into bootloop again but at least it will remove Google APP from the list of disabled apps
Enter TWRP again and dirty flash ROM again.
Reboot and it should be ok
Click to expand...
Click to collapse
Genius!!!!
Unfortunately it's too late, I already reinstalled all the apps and everything, now I have a clean system so I'll stay with that.
However it's a good way to restore, I'll remind it if anyone else will need it