[Q] Boot Loop, unable to mount data in Recovery

[jfran]

Hi

My GT-I9195 S4mini recently starting acting strangely recently, then suddenly 2 days ago would not boot up completely, there is the constant boot loop with the Samsung logo, then the blank screen and vibration.

As i had CWM recovery 6.0.3.3 (also fully rooted), I booted into recovery and tried to wipe date/reset, it attempted to do this errored with the failed to mount /data! and attempting to mount data or the external_sd via the advanced menu also failed to mount /data!.

I tried to install CM10 custom rom and i got a Status 7 error, edited the update scripts in the .zip file and the same thing happened

Tried to reinstall firmware with ODIN, tried the original H3G firmware (I'm on 3UK) and it failed to update, however eventhough the CHE firmware was successful, on rebooting the CWM 6.0.3.3 recovery was still there (its doesnt seem to allow me to update the recovery) and the same problems with boot loop and failed mounts.... Any further suggestions I would surely appreciate.

 

[arco68]

Try updating to the latest CWM, and also try with Odin 3.09 in case it was 3.07 you tried with.

 

[jfran]

i have tried that it seems successful on Odin, however when the device reboots, its still says 6.0.3.3, just redownloading the latest CWM

Odin error log for H3G firmware

<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> tz.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Odin Logs for CHE Firmware
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> tz.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

after the update, the CWM Recovery is still present which seems quite odd

 

[JMailuhu]

flashing ROMs does not remove cwm and thus its obvious that cwm is still present. (Though when flashing to stock ROM you can get the following message in cwm "Rebooting will change to stock recovery" or something along those lines.
Can be ignored by pressing NO when closing cwm.)
Try updating cwm with the new version (6.0.3.7) through Odin 3.9. And if you still have bootloop try to reflash your device.
Hope this works out for you.

Sent from my GT-I9195 CM10.1-Nightlies using xda app-developers app

 

[jfran]

flashing ROMs does not remove cwm and thus its obvious that cwm is still present. (Though when flashing to stock ROM you can get the following message in cwm "Rebooting will change to stock recovery" or something along those lines.
Can be ignored by pressing NO when closing cwm.)
Try updating cwm with the new version (6.0.3.7) through Odin 3.9. And if you still have bootloop try to reflash your device.
Hope this works out for you.

Sent from my GT-I9195 CM10.1-Nightlies using xda app-developers app

Hi Mate

Thanks for the advice, I have flashed firmwares not roms, hence the recovery should have changed unless I'm mistaken....anyway, I am unable to flash roms as I am unable to mount /data, so all attempts to install a rom through CWM have failed. wipe data has failed as the /data isnt mounting. I have flashed 3 firmwares via ODIN 3.09, the CHE and another have been successful but the boot loop continues, however the H3G which is my phones model has been unsuccessfully flashed for some strange reason.

I will try the latest CWM, howwever my challenge has been that I have a very slow net connection at present hence my inability to access firmwares easily.