[SOLVED]Flashing Rom. Having an issue. - Kindle Fire General

Everytime I go to flash a rom it does this
-----------------
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext.'
E:Can't open /cache/recovery/log
E:Can't open /cache/rocovery/last_log
E:Cannot load volume /misc!
-- Verify md5 for /sdcard/Android/-name of rom-
-- No md5 file found. ignroing
-- Install -name of rom-
E:Cannot load volume /misc!
Finding update package...
Opening update package...
Installing update...
Starting -name of rom- installation.. Please Wait!
Formatting system...
Writing /data
Writing /system/
Writing kernel image
Rom Installation Complete!
Please reboot your device...
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Cannot load volume /misc!
-------------------------------
Then give me the options of reboot main menu wipe cache/dalvik I pick reboot then it reboots to triangle them back in to TWRP.
Any Ideas??

would uncheck the md5 check option - the roms usually don't include it
and don't worry about the error regarding volume misc - the kf don't have a volume misc - just ignore it
if it boots back into twrp use kfu option 1 - bootmode normal
or manually if in twrp:
adb shell idme bootmode 4000
adb reboot

b63 said:
would uncheck the md5 check option - the roms usually don't include it
and don't worry about the error regarding volume misc - the kf don't have a volume misc - just ignore it
Click to expand...
Click to collapse
I personally hadn't checked the box for the force md5 check if that's what your talking about. I just checked that and it didn't have a x on it so assuming that's not on. If it matters. I had to do the abd shell fast boot stuff earlier because it was stuck on the triangle. I haven't been able to get it back into a rom at all since. Just TWRP. This is the process I had to do [URL="http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4"Here.[/URL] However.. windows did not want to format it and it just came as what it was before. I have a stock rooted 6.2.2 rom to put on it.

at the install screen in twrp uncheck (no x) "force md5 check on all zips?"
would try again and tell the error messages
update: the error about sd-ext is also to ignore - it don't have it
the error about the logs could be a bad cache partition - would try "wipe" and then "cache" before you flash
in every case do a clear cache/dalvik at the screen where you return after flashing in the lower left
and set the bootmode to normal (4000) as described above

I figured it out. Thanks for your help. I really do try to figure it out befor I post but then it just happens to click right after I post. The problem was I being slow... didnt set the boot mode back to normal.

great that you got it running !!!

Related

phone does n't boot

Hello,
When I want to Install Stock ROM with ODIN error shows ""View attachment 1269407"" "Complete(write) operation failed"
and when I go to "Android System Recovery" (vol up + home bot + power bot) and choose Wipe data/factory reset OR wipe cache partition, Error Show "Failed to mount /Cache (invalid argument) " & "Can't mount /cache/recovery/lastlog"
What should I do?
Galaxy_young said:
Hello,
When I want to Install Stock ROM with ODIN error shows ""View attachment 1269407"" "Complete(write) operation failed"
and when I go to "Android System Recovery" (vol up + home bot + power bot) and choose Wipe data/factory reset OR wipe cache partition, Error Show "Failed to mount /Cache (invalid argument) " & "Can't mount /cache/recovery/lastlog"
What should I do?
Click to expand...
Click to collapse
Where did you get that single file firmware? Odin will not flash single file firmwares.Check docky73's thread for odin flashable firmwares.

[Q] Stuck in boot loop/recovery, can´t mount sdcard or cashe.

I have a LG G2 d802(Int.) and just updated from cm11 M3 to M4, and decided to wipe data/cashe and re-flash due to some force closing issues.
However, the phone just froze every time i tried. Couldn't do it from recovery or terminal or anything.
E: can´t mount /cashe/recovery/log
E: can´t open /cashe/recovery/log
E: can´t mount /cashe/recovery/last_log
E: can´t open /cashe/recovery/last_log
I think I went on to do something stupid as formatting cashe.
After this I´m stuck in boot loop or i can boot to recovery.
I thought I´d just flash the ROM .zip again(have worked before in similar situations) but now I got a E: can´t mount /sdcard
I cannot adb remount sdcard(internal) or cashe.
I´ve tried to sideload the .zip, but it freezes in "Installing package..."
How can I get out of this?
After reading post after post on forums, I haven't found any answers that helped me so far.
nrvld said:
I have a LG G2 d802(Int.) and just updated from cm11 M3 to M4, and decided to wipe data/cashe and re-flash due to some force closing issues.
However, the phone just froze every time i tried. Couldn't do it from recovery or terminal or anything.
E: can´t mount /cashe/recovery/log
E: can´t open /cashe/recovery/log
E: can´t mount /cashe/recovery/last_log
E: can´t open /cashe/recovery/last_log
I think I went on to do something stupid as formatting cashe.
After this I´m stuck in boot loop or i can boot to recovery.
I thought I´d just flash the ROM .zip again(have worked before in similar situations) but now I got a E: can´t mount /sdcard
I cannot adb remount sdcard(internal) or cashe.
I´ve tried to sideload the .zip, but it freezes in "Installing package..."
How can I get out of this?
After reading post after post on forums, I haven't found any answers that helped me so far.
Click to expand...
Click to collapse
Have you tried flashing back to stock? ( http://forum.xda-developers.com/showthread.php?t=2432476 )
Wiping data/cache should not have caused a boot loop.
Solved!
selivanow said:
Have you tried flashing back to stock? ( http://forum.xda-developers.com/showthread.php?t=2432476 )
Wiping data/cache should not have caused a boot loop.
Click to expand...
Click to collapse
I didn´t think it would either, but that whas the last thing I remember doing before it happened.
Anyway, I went on and formatted system, cashe, data and sdcard, and then after rebooting recovery, everything worked again and I could install the ROM without any problems.
Should have done that from the start

[Q] Bootloop on stock Nexus 4

Hi threre,
Yesterday, my WhatsApp kept crashing so I decided to reboot my stock Nexus 4 (4.4.4). Now my phone is stuck in a boot loop. I have access to the recovery menus.
The first thing I tried was wiping my cache. When I open the Android system recovery There is already an error on the bottom half of the screen.:
Code:
E: failed to mount /cache (Invalid argument
)
E: Can't mount /cache/recovery/log
E: Can't open cache/recovery/log
E: failed to mount /cache (Invalid argument
)
E: Can't mount /cache/recovery/log
E: Can't open cache/recovery/log
E: failed to mount /cache (Invalid argument
)
E: Can't mount /cache/recovery/log
E: Can't open cache/recovery/log
E: failed to mount /cache (Invalid argument
)
I have tried wiping the data and cache partitions but when I do that the same errors as above fill up my entire screen and it does not help anything at all.
Next thing I tried was to flash a stock image using this thread http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312. Since I am posting here you can probably guess that this did not work as well.
The problem is that my device is not rooted, and I can not get my bootloader to stay unlocked after a reboot. I have the bootloader drivers installed on my Windows 8.1 pc using the advanced reboot method so I have access to my phone in cmd. fastboot oem unlock does seem to work at first since the "'LOCK STATE" turns to UNLOCKED, but when I do the required reboot for flashing images it turns back to locked.
Perhaps this is a symptom of a bigger cache problem?
I am definitely not a pro at this but I have some experience with rooting phones from my Samsung Galaxy S II.
I really hope that anybody knows an answer other then try you warranty plan because then I will not have my phone for 5 days or more and I am not sure whether they really can fix this...
Lastly, here is the information displayed in my fastboot screen:
Code:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 16 GB
HW VERSION - rev_11
BOOTLOADER VERSION - MAKOZ30d
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1701.03
CARRIER INFO - None
SERIAL NUMBER - xxx wil post this if nescesarry
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - locked
Thanks in advance!
If you can't lock the bootloader that is a symptom of your emmc flash memory failure. Afraid there isn't much you can do. Are you still under warranty?
Sent from my Nexus 5 using XDA Free mobile app
I still have warranty but I'm a little worried that they will complain about the damage (unrelated to the crash) of my phone. Is there no way of repairing the flash memory?

Boot Loop Nexus 4 - dead eMMC?

Recently, my Nexus 4 has been crashing randomly - shutting off with no warning or notice. It has always rebooted back up without issues. Last night, however, it just got stuck in a boot loop - spinning balls for hours on end.
Bootloader and Recovery Mode come up with no trouble.
The phone is and always has been pure OEM/stock. I've only ever updated using built in OTA process.
I tried to reflash to stock using Wug's Nexus Toolkit, but it repeatedly failed saying the device was locked. I tried to unlock the bootloader, but that seems to require a reboot to take hold, and every time I tried the reboot it would loop again.
In Recovery Mode, I get the following:
E:failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:failed to mount /cache (Invalid argiument)
E:Can't mount /cache/recovery/last_log
E:can t open /cache/recovery/last_log
E:can t mount /cache/recovery/last_install
E:can t open /cache/recovery/last_install​
I have downloaded the full image and tried flashing the cache, and system with no effect. Toolkit doesn't show an error, but nothing changes.
Does anyone have any suggestions? I'm at a loss.
Did you try
fastboot erase cache.img
fastboot flash cache cache.img
Then perform wipe data/factory reset before booting into android.

[BUG][SOLVED][WORKAROUND] TWRP starts with no menu, runs script, crashes, repeat (Axon 7 mini)

Hello,
im new to this Forum. I try my best to give all the information i have.
What happened?
I tried to install the project /e/ os on my axon 7 mini. First I unlocked my phone with tuliptool in edl mode. I found the twrp recovery-image for my device in this guide (https://www.getdroidtips.com/root-twrp-zte-axon-7-mini-magisk/#Download-Files) flashed it with tuliptool to the recovery partition and it worked. But it broke my stock android rom. I only can boot intro twrp - i cant boot android (only shows zte android title screen). Then i installed the unofficial /e/ port for my device with twrp and it worked. Then i thought i could unroot my phone with tuliptool (i dont know why atm i thougt it will be a good idea) so i ran tupliptool lock unlock and my device was locked again. Now i only can access twrp so i undo the locking. After wiping the data partition with twrp, /e/ startet again. Then i thought that wiping the data partition would solve the issiue with not loading /e/ while locked, therefore i gave it an other try. Locking my phone again, wiping partition with twrp and... nothing. So i gave up and wanted to use my phone again so i unlocked it again.
Whats the problem?
Now I only can access twrp, but it wont show the menu. It just autostarts a script and there are no buttons. The script failes after ~10 seconds and the device crashes (error message below). It trys to boot up but fails, so it loads into recovery -> starts twrp -> runs this script -> crashes and so on. Now i cant do anything. It reboots all the time.
What can I do?
As said, twrp starts but with no menu. I have access to edl mode so i rewrote the recovery partition. This does not change anything. I can access my device with adb while it loads twrp. I have a time window about 10-15 seconds until it reboots. Fastboot does not work. (Not available or locked on Axon 7 mini?) If i try "adb reboot bootloader" my phone just reboots into android (well it did before flashing, now its stuck in the loop.) From searching this forum i think i should reformat the partitions, but i dont know how because i dont have access to the twrp menu. If you need more informations like a dump or something, tell me how to do it.
The Error:
As i dont know how i could dump it from my phone to my PC, i had to manual type the Error here...
$Begin
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
...done
Unable to mount storage
Successfully decrypted with default password.
Updating partition details...
...done
Unable to mount storage
Unable to mount '/data' (Invalid argument)
Full SELinux support is present.
wipe_data_via_recovery
Unable to mount /data/media/TWRP/.twrps
Running Recovery Commands
Failed to mount '/data' (Invalid argument)
Formatting Cache using make_ext4fs...
Done processing script file
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
$end
This runs fast until "Done processing script file". There it waits for ~3 Seconds. Then the last two lines show up and it crashes immediately.
Ok i found a solution - it worked for me but i dont know why. Its not intuitive but hey, its a workaround.
The problem was twrp couldnt startup anymore because the data partition was currupted (not confirmed, but i guess it was currupted). If you follow any guide, they tell you to go to wipe data inside of twrp and wipe (and reformat) the partition. This wont work in this case, because the corrupted partition causes twrp to crash. Its the script in the post above.
To fix this i used adb while twrp was starting up
Code:
adb shell recovery --wipe_data
This alone wouldnt solve the issue, but it will buy some time. After twrp loads again, you will see the main menu of twrp for a couple of seconds. The time you have on the menu is very limited (5 seconds max) before the script that will crash twrp starts executing. In this time window i managed to set twrp to write mode and initiated the wipe of /data. If you get this far, both scrips (wipe data and open recovery script) will execute, the screen will switch between both of them very fast. After a few seconds it will crash again, but the wipe data script could reformat the data partition properly. After this twrp will work like normal.
I don't know if this problem is specific to my device or model. I dont know if this is recreatable. Im glad i fixed it after five long days, im not willing to sacrifice my device again. I dont know if this is a twrp bug or what happened exactly. If anyone had a clue or needs more informations i will provide them. At least I found a workaround.

Categories

Resources