Develop Bugs

PLEASE Help! Stuck on Startup screen after Odin

Hello all
I was updating my gf phone from rooted UVALJ4 or UVALH2 (Cant remember now, but it was an old Firmware) to root66 T999_UVUENC2 via Odin 3.09 on my Win 7 pc but after the odin install (which passed) I rebooted the phone and I got stuck on the Samsung logo on the start up screen. After about 10 mins I pulled the battery and tried to enter the Recovery mode, but nothing appears. Just a black screen.
So i Odin flashed the TWRP 2.6.3.1 to try to get to a recovery, but that didnt work. Still no Recovery.
I then used odin to flash the stock tmobile UVUENC2 4.3 firmware and it still gets stuck on the Samsung screen.
Next I tried to unbrick it via http://forum.xda-developers.com/showthread.php?t=2439367 using "SGH-T999 4.3 only Debrick Image" and reflashed the stock 4.3 rom, but that didnt work. :crying:
What can I try next? WHat should I do? I can still access download mode, thats about it.
Please help if you can.
Thx

I dont know how but I got the stock recovery to finally appear and now I get these errors (see Pic) what do these mean?
The recovery errors read: E:failed to mount /data ( Invalid argument) can't mount "/data" (invalid argument)
E: Can't mount /data/log/recovery_log.txt
again thx

synplex said:
I dont know how but I got the stock recovery to finally appear and now I get these errors (see Pic) what do these mean?
The recovery errors read: E:failed to mount /data ( Invalid argument) can't mount "/data" (invalid argument)
E: Can't mount /data/log/recovery_log.txt
again thx
Click to expand...
Click to collapse
Never Mind Used Unified Android Toolkit to fix recovery and flash stock rom.
Thank god for that toolkit.
...time to donate
:victory:

Mod Please delete Thread.
Thx

In the future, try a factory reset, almost all boot hangs are solved with this. Happens because of incompatible data between versions, which would make sense condidering the jump you made. Kind of makes sense with the error message too, but I'm not 100% certain there.
Be careful with the toolkit. There is no support for it and it has bricked phones in the past.

[Q] Unable to mount cache, system, data

Hey guys, I seem to have soft-bricked my AT&T S3.
I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.
Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.
When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).
Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?

ericmerl said:
Hey guys, I seem to have soft-bricked my AT&T S3.
I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.
Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.
When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).
Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?
Click to expand...
Click to collapse
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.
Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486

Stock ROMs
Larry2999 said:
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.
Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...
I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.

ericmerl said:
The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...
I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.
Click to expand...
Click to collapse
Sad times.
I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.
When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.
I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.

ericmerl said:
Sad times.
I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.
When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.
I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.
Click to expand...
Click to collapse
To follow up again, I was able to re-flash TWRP using Odin. Once that was done, the phone no longer tried to boot straight to recovery. I was able to three finger into TWRP, though it took a super long time for it to boot.
Here's the console log taken from TWRP once it boots:
Code:
E:Could not mount /data and unable to find crypto folder.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount internal storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
Running boot script...
Finished running boot script.
E:Unable to mount '/cache'
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E:Unable to mount '/data'

[Q] Can't mount any partition in twrp

I got my new Nexus 7 2013 the other day and tried to root it.
I successfully unlocked it and installed TWRP but when I enter TWRP it seem to not be able to mount any partition
HTML:
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount storage
I can't flash any zip and I can't do anything in the recovery, I'm using the latest TWRP version.
I tried installing android 5.0.2 and 5.1.1 and install TWRP but I keep getting the same error no matter the android version

tomer007 said:
I got my new Nexus 7 2013 the other day and tried to root it.
I successfully unlocked it and installed TWRP but when I enter TWRP it seem to not be able to mount any partition
HTML:
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount storage
I can't flash any zip and I can't do anything in the recovery, I'm using the latest TWRP version.
I tried installing android 5.0.2 and 5.1.1 and install TWRP but I keep getting the same error no matter the android version
Click to expand...
Click to collapse
Been there, there's a whole thread about this. You have to use a modified twrp (multiirom version here: https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img).
You may also be getting a message 'no os installed' when you try to boot. It freaked me out at first.
Here's the thread, multirom twrp info near end: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562

Thanks!
Downloading now.
Why is this happening?

Yes!
It worked!

It's a mystery to me why the regular twrp doesn't work. I'm just happy there's a solution.

I can't even get that version of twrp to install using the wugfresh nrt. Every time I try the regular one it reboots into twrp and it shows 0mb available and can't see any files and when I say reboot system it says no OS. It still reboots fine. Tried the multirom version suggested above and it doesn't even get that far.....
Sent from my Nexus 7 using Tapatalk

The multirom twrp installed fine for me via adb (there's an advantage to not having a pc I can install the toolkit on ☺).
If you can still boot into something, you should be able to install the multirom twrp using TWRP Manager or Flashify from the Play Store, I did that after I had everything running (and installed the regular twrp to see if it would work on mm, it didn't, so I had to reinstall multirom twrp).

TWRP failing to mount /data + bootloop

Hi all,
After spending all my morning looking at various solutions I've resulted in opening a new thread.
I was trying to install a stock rom this morning however was stuck in a bootloop on the LG logo.
Trying to go back into recovery resulted in a black screen after the TWRP logo.
I was attempting to re-install TWRP to see if that would fix the problem however I only managed to get into Download Mode (is this the same screen as the Bootloader?) and adb/fastboot couldn't find the device.
Magically, TWRP boots up now however in the log it states the following:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount /data
E: Unable to recreate /data/media folder
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
If anyone can point me in the right direction in how to resolve this I would be grateful.
Regards,
Ash

AshleyNG2 said:
Hi all,
After spending all my morning looking at various solutions I've resulted in opening a new thread.
I was trying to install a stock rom this morning however was stuck in a bootloop on the LG logo.
Trying to go back into recovery resulted in a black screen after the TWRP logo.
I was attempting to re-install TWRP to see if that would fix the problem however I only managed to get into Download Mode (is this the same screen as the Bootloader?) and adb/fastboot couldn't find the device.
Magically, TWRP boots up now however in the log it states the following:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount /data
E: Unable to recreate /data/media folder
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
If anyone can point me in the right direction in how to resolve this I would be grateful.
Regards,
Ash
Click to expand...
Click to collapse
Looks like you trying to install stock Rom, Given the account you used a flashable zip. It didnt install all the way. and now your stuck with a messed up unstable device......
If you can get into TWRP, wipe everything at least 2 times.. Then install a Flashable ROM/gapps ect..
If you cant get into TWRP and only into Download mode.. Then you will have to flash stock kdz file...............
you can find all types of guides on that around here............

Eliminater74 said:
Looks like you trying to install stock Rom, Given the account you used a flashable zip. It didnt install all the way. and now your stuck with a messed up unstable device......
Click to expand...
Click to collapse
Thanks for your response, once I got into TWRP I couldn't wipe anything as it couldn't mount any partition nor could I flash anything from the external sd.
When I plugged it in there was no internal memory so I decided to use the TOT restore method to go back to stock which was successful and now I've got my custom stock rom back on.

HTC ONE M9 Bricked?

Hi there, so I'm having a bit of a problem. I tried to revive my old M9. I remember flashing it with a custom ROM (Android HD Revolution) and everything was fine. I left it since I got a new phone and today wanted to play around with my M9 again.
However, it would be stuck with the HTC Logo while loading, and my TWRP was gone, could no longer boot into it and my download mode was also screwed, as it gave me the error (failed to boot to download mode).
Anyway so I tried restoring to one of my TWRP backups, by mounting a TWRP img file first using my PC. It went fine, after that I booted into system and the HTC logo would be on white background and preventing me from using the screen, although funnily enough the system was functionally normally i.e. the volume keys worked and I could see it change on screen but, it was just as if I had a some kind of overlay and couldn't use the screen itself by touching.
I then tried to flash with the same custom ROM, but after installing it and rebooting the phone it was stuck in a boot loop, where it would shutdown and try to boot again.
So I turned it off using power up and home button, and tried to wipe the partition to install another ROM, using the same TWRP method I did above.
Only this time, I can't do anything: wipe, install, format etc. I get the error "Failed to mount '/data' (Invalid Argument)" "Failed to mount '/cache' (Invalid Argument)" whenever I try doing anything within TWRP. I can't even mount cache, system or Data. It is if they're not there.
And now my phone is back to where it started, i.e. infinite boot screen with HTC Logo and "This build is for etc..." text.
Note: Trying to change file system from ext4 to ext2/3 and back to ext4 does not fix the problem ,as the same errors pop up when trying to change file system.

90% chance the nand is goosed. 10% chance of recovering by flashing a stock firmware in download mode (same version as currently installed, external sd card method).
Twrp has a known issue for bricking devices at random.