Related
Hi, I recently got an update notice for my Nexus 7 (2013), previous to this I hadn't rooted or done anything weird with the unit at all. During the update something must have gone wrong because I was left with the robot with a red triangle, and its not in a continuous bootloop.
I've done lots of reading around to try and fix my unit, and because i didn't enable usb debugging I'm unable to use the ADB toolkit fixes so I have to rule these out.
I have been able to get into the bootloader menu and can use fastboot commands to try and unlock my unit. I follow the commands on the unit and select unlock with the volume control but when it gets to erase userdata it just hangs and does nothing.
Every command I try usually gives me the error FAILED (command write failed (Unknown error).
I've tried different USB ports and different cables, and I've tried using a PC and a MAC.
I have tried erase cache/user data in the recovery menu, but this does nothing.
I have emailed Asus UK to try and arrange a warranty return, but because the unit was bought in the USA as a gift for me, I'm not covered and will have to pay.
Is there anything I could try to fix my unit? I really wish I hadn't bothered clicking update now!! I've spent about 10 hours trying to fix this thing now. Any advice would be appreciated - my wife bought it for me and she is quite upset that an update has made it completely useless and Asus don't want to help.
If it is beyond repair, does anyone have any idea what ASUS charge to fix these things?
Thanks for reading
as long as you can access the bootloader and fast boot commands, it can be saved. You need to download the full image from Google. Search for "nexus 7 images" or something of the sort and you should find a code.Google link with images to download. Grab the ones for your device and you can extract the files and run the "flash all.bat" to flash all the needed images. If you need help feel free to pm me and I can get you fixed up.
prshosting.org
prsterero said:
as long as you can access the bootloader and fast boot commands, it can be saved. You need to download the full image from Google. Search for "nexus 7 images" or something of the sort and you should find a code.Google link with images to download. Grab the ones for your device and you can extract the files and run the "flash all.bat" to flash all the needed images. If you need help feel free to pm me and I can get you fixed up.
prshosting.org
Click to expand...
Click to collapse
Thanks for your help and for giving me hope!
I have downloaded images and tried to flash all.bat, but they all seem to rely on being able to unlock the bootloader, and when I try and do that it always hangs on "erasing userdata". I've left it for 5 or 6 hours and it just doesn't work.
I'm able to access ADB sideload functionality - will that give me another chance of fixing this thing?
taviboy said:
Thanks for your help and for giving me hope!
I have downloaded images and tried to flash all.bat, but they all seem to rely on being able to unlock the bootloader, and when I try and do that it always hangs on "erasing userdata". I've left it for 5 or 6 hours and it just doesn't work.
I'm able to access ADB sideload functionality - will that give me another chance of fixing this thing?
Click to expand...
Click to collapse
I don't really have experience with adb sideload, but i do know the factory images should flash fine. How much memory do you have available when trying to do the unlock? Maybe your system can't supply enough. Another thing you can try is reloading the drivers from scratch, but i would try the memory part first. You can also use "fastboot -w" to erase userdata manually then try flashing the images again.
prsterero said:
I don't really have experience with adb sideload, but i do know the factory images should flash fine. How much memory do you have available when trying to do the unlock? Maybe your system can't supply enough. Another thing you can try is reloading the drivers from scratch, but i would try the memory part first. You can also use "fastboot -w" to erase userdata manually then try flashing the images again.
Click to expand...
Click to collapse
Okay, will give it go once more. I think the drivers are okay because i get fastboot devices showing me my unit, so its communicating with it ok I think.
What do you mean when you say how much memory do I have available? On my laptop? How could i change that?
Tried fastboot -w
It still hangs on erasing 'userdata'...
There is something funny about userdata for some reason - when I try and unlock the boatloader it hangs on the same thing.
Is there any way of unlocking without erasing userdata?
Try go to Stock Recovery (you said you hadnt rooted your phone yet), do a factory reset and see if it works.
taviboy said:
Tried fastboot -w
It still hangs on erasing 'userdata'...
There is something funny about userdata for some reason - when I try and unlock the boatloader it hangs on the same thing.
Is there any way of unlocking without erasing userdata?
Click to expand...
Click to collapse
Unlocking automatically erases userdata, so i don't believe there is. I can try and help you out via teamviewer if you want. If nothing works then it may be a bad EMMC flash chip, which means there's nothing we can do and would have to be sent for warranty, which i know is an issue for you.
edit: I got another idea. What about overriding the data partition with the one included with the factory images then trying the unlock?
opticaldh said:
Try go to Stock Recovery (you said you hadnt rooted your phone yet), do a factory reset and see if it works.
Click to expand...
Click to collapse
How do I do that?
I've tried to flash a factory image, and I get command write failed (invalid argument) come up - it really doesn't want to play ball.
taviboy said:
How do I do that?
I've tried to flash a factory image, and I get command write failed (invalid argument) come up - it really doesn't want to play ball.
Click to expand...
Click to collapse
when you are at bootloader, choose Recovery. If you are on stock Recover, there should be an android guy lying with an red triangle on his belly. You will have to press the combination Power + Volume up (power first then volme up), then you should see the option to do a factory reset.
opticaldh said:
when you are at bootloader, choose Recovery. If you are on stock Recover, there should be an android guy lying with an red triangle on his belly. You will have to press the combination Power + Volume up (power first then volme up), then you should see the option to do a factory reset.
Click to expand...
Click to collapse
Okay, tried to flash back to factory, not working - says command write failed.
When I go into recovery I have 4 options: Reboot, Apply update (sideload), WipeData/Factory reset, Wipe Cache
Choosing wipe/factory reset:
Says formatting /data...
formatting cache...
Data wipe complete
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/log etc etc
E:failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (i/o error)
E:failed to mount /cache (invalid argument)
Nothing seems to work...
prsterero said:
edit: I got another idea. What about overriding the data partition with the one included with the factory images then trying the unlock?
Click to expand...
Click to collapse
How would I go about doing that?
taviboy said:
Okay, tried to flash back to factory, not working - says command write failed.
When I go into recovery I have 4 options: Reboot, Apply update (sideload), WipeData/Factory reset, Wipe Cache
Choosing wipe/factory reset:
Says formatting /data...
formatting cache...
Data wipe complete
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/log etc etc
E:failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (i/o error)
E:failed to mount /cache (invalid argument)
Nothing seems to work...
Click to expand...
Click to collapse
It seems a lot of people that get the invalid argument are because of a USB port or jacked up stock recovery image. Can you manually flash the recovery image then userdata image?
---------- Post added at 07:04 PM ---------- Previous post was at 07:00 PM ----------
taviboy said:
How would I go about doing that?
Click to expand...
Click to collapse
Like when you did "fastboot -w" except in this case you would do "fastboot flash imagename.img" provided that the image file is in the same directory as where you're running cmd from. I'm telling you teamviewer could get this done a lot faster
prsterero mention of USB port got me looking and this sounds like something worth a try, try a different PC, different USB port, don't use a hub, or extension cable, last resort, buy a new known-to-be compatible cable.
mdamaged said:
prsterero mention of USB port got me looking and this sounds like something worth a try, try a different PC, different USB port, don't use a hub, or extension cable, last resort, buy a new known-to-be compatible cable.
Click to expand...
Click to collapse
We did a team viewer session and no additional cables, USB ports, or different computers solved the errors. So it has to be a hardware defect with the EMMC.
Sent from my Nexus 7 using XDA Premium HD app
prsterero said:
(...)So it has to be a hardware defect with the EMMC.(...)
Click to expand...
Click to collapse
Oh, that's weak. Good luck to the OP then.
taviboy said:
E:failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (i/o error)
Click to expand...
Click to collapse
I'm getting the same error, except that wipe cache partition, or wipe data/factory reset, both give errors as well.
The "(i/o error)" suggests to me that there's a hardware issue. Not really sure what to do, other than RMA the thing.
jmasur said:
I'm getting the same error, except that wipe cache partition, or wipe data/factory reset, both give errors as well.
The "(i/o error)" suggests to me that there's a hardware issue. Not really sure what to do, other than RMA the thing.
Click to expand...
Click to collapse
Follow the instructions in this thread to check if your EMMC is fried http://forum.xda-developers.com/showthread.php?t=1284196
Hi.So I used to have Cyanogenmod installed on my rooted Kindle Fire, along with FFF and TWRP recovery. I was not satisfied with the performance of Cyangogenmod, so I wanted to install the Stock Amazon ROM back onto the Fire. First, I booted into TWRP, and erased everything with the 'wipe' option (might not have been a good idea). I have downloaded the Amazon ROM from here: http://kindle-fire-updates.s3.amazonaws.com/update-kindle-6.3_D01E_4019920.bin, and renamed the file 'update.zip'. I mount the Fire, and drag over the update.zip, and then I go to 'install' in TWRP and select the update.zip, but after I start it, the install just fails, seconds after it's started. There are a couple errors, such as "Error executing updater binary in zip '/sdcard/update.zip'". I have ADB installed, and Kindle Fire Utility, which detects the device as 'online', boot status 4000. I have tried install COTR recovery with KFU, but it hangs at 'Activating Fastboot (4002)'. I would really appreciate any help with this, because it would really suck if it turns out that I bricked my Fire. Thanks!
Also having trouble taking my KF back to factory...
I am also having trouble taking my KF back to factory specs.
I am using TWRP recovery.
Wipes go just fine.
Install gives me this error...
Skipping MD5 check: no MD5 file found.
assert failed: getprop ("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/kindle/update.zip'
Error flashing zip '/sdcard/kindle/update.zip'
Updating partition details...
I am trying to go back to stock because I am now having TONS of trouble keeping files running without them crashing. Also, every time I try to read a book now, the Kindle app crashes before it ever really opens. I have tried uninstalling that app, then reinstalling even. No help at all.
Any help in this matter would be HUGELY APPRECIATED!!!!
Thanks,
me
BriteLeaf said:
I am also having trouble taking my KF back to factory specs.
I am using TWRP recovery.
Wipes go just fine.
Install gives me this error...
Skipping MD5 check: no MD5 file found.
assert failed: getprop ("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/kindle/update.zip'
Error flashing zip '/sdcard/kindle/update.zip'
Updating partition details...
I am trying to go back to stock because I am now having TONS of trouble keeping files running without them crashing. Also, every time I try to read a book now, the Kindle app crashes before it ever really opens. I have tried uninstalling that app, then reinstalling even. No help at all.
Any help in this matter would be HUGELY APPRECIATED!!!!
Thanks,
me
Click to expand...
Click to collapse
Yes I am getting almost the exact same error. I would really like a solution to this.
Ethanzh said:
Yes I am getting almost the exact same error. I would really like a solution to this.
Click to expand...
Click to collapse
So would I. I am glad that I am not the only one.
I am guessing...
I am guessing either us 3 are the only ones with this problem, or just no one wants to, or knows how to fix this problem =(
If a flash does not complete, it has to be a bad download. Get the file again and push it to the sdcard via twrp. But if you are having trouble, why flash factory? If it is some corruption, flash a rom. Kindle store and reader fail because of the app, generally. Notice my device says Nexus 7? That is how to fool the kindle apps on a fully functioning kindle fire.
Sent from my Nexus 7 using xda app-developers app
Ixthusdan said:
If a flash does not complete, it has to be a bad download. Get the file again and push it to the sdcard via twrp. But if you are having trouble, why flash factory? If it is some corruption, flash a rom. Kindle store and reader fail because of the app, generally. Notice my device says Nexus 7? That is how to fool the kindle apps on a fully functioning kindle fire.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have redownloaded the flash from Amazon at least five times, all with the same results.
As far as pushing it to the sdcard via twrp, I guess I for one don't know how to do that.
As to why I would want to go back to factory with it, I guess for me, it is what I prefer.
Thank you for answering though. I do appreciate it.
Same here, fixed!
Ethanzh said:
Hi.So I used to have Cyanogenmod installed on my rooted Kindle Fire, along with FFF and TWRP recovery. I was not satisfied with the performance of Cyangogenmod, so I wanted to install the Stock Amazon ROM back onto the Fire. First, I booted into TWRP, and erased everything with the 'wipe' option (might not have been a good idea). I have downloaded the Amazon ROM from here: , and renamed the file 'update.zip'. I mount the Fire, and drag over the update.zip, and then I go to 'install' in TWRP and select the update.zip, but after I start it, the install just fails, seconds after it's started. There are a couple errors, such as "Error executing updater binary in zip '/sdcard/update.zip'". I have ADB installed, and Kindle Fire Utility, which detects the device as 'online', boot status 4000. I have tried install COTR recovery with KFU, but it hangs at 'Activating Fastboot (4002)'. I would really appreciate any help with this, because it would really suck if it turns out that I bricked my Fire. Thanks!
Click to expand...
Click to collapse
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
mpeterso said:
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
Click to expand...
Click to collapse
Thanks, trying this now.
TWRP 2.2.2.1 Worked
mpeterso said:
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
Click to expand...
Click to collapse
Thanks for the tip. Worked like a champ.
mpeterso said:
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
Click to expand...
Click to collapse
I just get stuck at < waiting for device > on my command prompt. Where am I supposed to open the cmd?
I just wanted to say, after several hours of searching through Google and messing with my Kindle, this thread finally helped me fix it.
My biggest issue was, I was unable to flash any thing, even the twrp. So what I had to do was this,
I googled the twrp 2.2.2.1 blaze img as mentioned here, then I renamed it to twrp.img and put it in the folder inside KFU -> Recovery
My other issue was with my Kindle being stuck at the Boot Logo saying, "Booting" and I noticed through trial and error, before the kindle goes to try to boot (When you can select Normal, Recovery, Reset Boot) that if I kept pressing the power button to cycle through the options, I could keep the Kindle in a Fastboot mode so I could use the KFU to install the TWRP 2.2.2.1
After that it was simple, booted into twrp, mounted the drive and stuck the Stock Rom from Amazon on there and installed it.
So I really just wanted to say thank you to this thread and hopefully I can contribute a small bit to someone if they have my issue.
Bump
Having the exact same issue when using KFU it just hangs there on activating fast boot
Cronus3166 said:
I just wanted to say, after several hours of searching through Google and messing with my Kindle, this thread finally helped me fix it.
My biggest issue was, I was unable to flash any thing, even the twrp. So what I had to do was this,
I googled the twrp 2.2.2.1 blaze img as mentioned here, then I renamed it to twrp.img and put it in the folder inside KFU -> Recovery
My other issue was with my Kindle being stuck at the Boot Logo saying, "Booting" and I noticed through trial and error, before the kindle goes to try to boot (When you can select Normal, Recovery, Reset Boot) that if I kept pressing the power button to cycle through the options, I could keep the Kindle in a Fastboot mode so I could use the KFU to install the TWRP 2.2.2.1
After that it was simple, booted into twrp, mounted the drive and stuck the Stock Rom from Amazon on there and installed it.
So I really just wanted to say thank you to this thread and hopefully I can contribute a small bit to someone if they have my issue.
Click to expand...
Click to collapse
This worked perfectly for me. Felt a little weird sitting there repeatedly pressing the power button as KFU searched for my device, but it worked. Thanks.
Hello,
i just unlocked bootloader and installed twrp and it all went fine..
until i wanted to fully wipe my device, i did this via twrp.
after 20Minuts, nothing happend, the bar was still white and gray (not even a little bit blue)
and it kept stuck on ''twrp formatting data using make_ext4fs function''.
i knew this wasn't a good idea, but i decided to turn off my phone,
and now, everytime when i turn it on on the normal way it just redirrects me to TeamWin in a bootloop.
even if i want to go to recovery mode i keep stuck in that bootloop, so there is nothing i can do right now, i only can stick at Fastboot Mode but nothing else,
Is there any way to fix this problem?
Using ASUS ZENFONE 2 551ML
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
TheSSJ said:
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
Click to expand...
Click to collapse
How to he flash stock rom by twrp?
Download and flash this via twrp http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
Make sure you flash Supersu before you flash the rom.
mr_gourav2000 said:
How to he flash stock rom by twrp?
Click to expand...
Click to collapse
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
TheSSJ said:
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
Click to expand...
Click to collapse
but i cant use twrp on my phone because its stuck in bootloop, or what do you mean? (english not my main language)
please give me some proper step by step instructions, i would really apreciate that!
thanks anyway your awesome!
Man, I misread your post, sorry...I thought you could boot only into twrp
If you still have fastboot, why not flashing twrp 2.8.x.x?
Code:
Fastboot flash recovery nameofrecovery.img
Fastboot reboot recovery
Otherwise you could flash stock system with this guide: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
It's a lot to read
wow, that is something really helpfull, there is still hope to revive my phone
i'll let you know how it turnt out xd
thanks alot!!
i fixed recovery mode, so thats already one step further. Oefff @TheSSJ thanks for the help.
But now i get some other problems, when i try to wipe my phone i get the error like ''unable to mount /data'' and ''unable to wipe dalvik''
and all other kinds of these errors, i get the same problem when i was installing rom. isn't there anything or a way to fully wipe all this **** so i can install a fresh rom.
i flashed custom rom and this is error log i get. its all full written down.
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed
Seems you don't have a WW image installed, do you have a CN Software? Then you need another Software of course
what do you mean with ww & cn software?
sorry but im new in this.. but im really interested so can you please explain a little bit?
how can i get this other software! thanks!!!
Where did you buy your Phone? what does the packaging state? WW, CN, TW, etc? These 2 letters must be written in uppercase somewhere, then we will know which software to flash, there is a check where your phone's software is compared to the zip you are trying to flash:
assert failed: getprop ("ro.build.asus.sku") == ''WW''
Which TWRP did you flash?
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
colldor200 said:
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
Click to expand...
Click to collapse
There you go: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-CN-2.20.40.159-user.zip
I think flashing will still fail though...but pls try first,maybe it'll work
i tryed it, i get the same error :/
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there ?
colldor200 said:
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there
Click to expand...
Click to collapse
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
Click to expand...
Click to collapse
sorry for the kinda late answer, but yes i followed your instructions, and it works completely, after cm13 i also immediately installed gapps.
i skipped xaosp im fine with cm13
Thanks alot @TheSSJ for all the help my phone is fully fixed now and even working faster then before its like super fast.
thanks again your great!
Hey guys,
I was googling for the past few days who else might experience such problem, but I haven't stumbled upon such case. The problem is, I'm stuck on the bootloader part.
The initial goal was to root the device, so:
- I unlocked the bootloader,
- installed clockwork-touch-6.0.4.7
- wiped everything
- when I try to install SuperSU & new ROM I'm getting errors like
Code:
Can't mount /cache/recovery
Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (No such file or directory)
Can't mount /cache/recovery/log
and a few other errors in this fashion about cache.
When I actually run the
Code:
abd sideload aicp_flo_n-12.0-UNOFFICIAL-20161020.zip
the installation tries to mount folders like /data but gets an error.
Finally it says
Code:
E1001: Failed to update system image
Installation aborted
Is there a way to re-format everything to FAT using fastboot and then begin everything from scratch? I have a feeling this is filesystem problem that it can't read properly or something... Maybe I'm wrong? What would be your suggestions?
Thanks!
I had a similar issue on mine a few days ago. I was completely stock and wanted to unlock bootloader, flash a custom recovery and then finally a custom ROM. I was successfully able to unlock the bootloader and flash the recovery (latest TWRP). But, when I tried to boot into recovery, it went past the recovery logo and then showed me errors like yours inside the recovery and rebooted. It then automatically booted into the recovery, showed the same errors and rebooted again. I wasn't able to do anything apart from booting into bootloader by sending an adb command.
Now coming to the part which fixed my errors. What I did was used the "fastboot -w" command (without the quotes) while I was in bootloader to wipe everything and after that, flashed the recovery again. Then I was able to successfully boot into recovery and everything has been fine since then.
I have a FTV 2 that can get into TWRP but can't boot up normally. I've tried flashing prerooted images, unbrick script, and wiping everything. I am stuck.
In TWRP I keep getting unable to mount Cache Invalid Argument. When trying to flash a pre-rooted image, it just hangs forever on copying system image.
Is there anything I can do? If I need to get a replacement device from Amazon, can I remove TWRP, even if it won't boot?
sbddude said:
I have a FTV 2 that can get into TWRP but can't boot up normally. I've tried flashing prerooted images, unbrick script, and wiping everything. I am stuck.
In TWRP I keep getting unable to mount Cache Invalid Argument. When trying to flash a pre-rooted image, it just hangs forever on copying system image.
Is there anything I can do? If I need to get a replacement device from Amazon, can I remove TWRP, even if it won't boot?
Click to expand...
Click to collapse
https://forum.xda-developers.com/fire-tv/development/firetv-2-recovery-t3309780
There is a section that talks about how to recovery from a cache loop.
Hi Mr. rbox
This is my post and I think I have the same problem: https://forum.xda-developers.com/showpost.php?p=73210074&postcount=17
Where I should run this "mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache" in terminal? I am newbie and I really dont know. Please help me
Edit:
I followed your steps and made it to work.
Thank you
Thank you for responding rbox.
I already tried the cache clearing steps you mentioned, and just tried it again just in case. I still get the hang on "copying system image" when trying to flash a prerooted image, and I see "failed to mount '/cache' (invalid argument)".
At this point all I want to do is remove TWRP. Can I do that from the terminal in TWRP?
1 way to fix
sbddude said:
I have a FTV 2 that can get into TWRP but can't boot up normally. I've tried flashing prerooted images, unbrick script, and wiping everything. I am stuck.
In TWRP I keep getting unable to mount Cache Invalid Argument. When trying to flash a pre-rooted image, it just hangs forever on copying system image.
Is there anything I can do? If I need to get a replacement device from Amazon, can I remove TWRP, even if it won't boot?
Click to expand...
Click to collapse
you can fix trying to format cache ext4