I have tried for several months now to get a gt-s5660 going. Not 24/7 apparebtly
I have tried everything, and more with guidance from several forum, mostly XDA.
Latest, what I have done:
1. ext4-formatter.zip
2. signed_cwm-5.0.2.7-flashablezip-ext4only.zip
3. cm-9-20130402-NIGHTLY-gio.zip
Now it starts, but I get:
Encryption unsuccessful.
"Reset phone"
Than this error when trying to wipe:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Anyone please help!
Hello,
Suddenly, my HTC Desire HD crashed.
I can not format /cache nor /data partitions.
I couldn't install a rom nor a backuped rom.
I can boot into bootloader / recovery.
can I resize these partitions ? how ?
Thanks for help
TF85 said:
Hello,
Suddenly, my HTC Desire HD crashed.
I can not format /cache nor /data partitions.
I couldn't install a rom nor a backuped rom.
I can boot into bootloader / recovery.
can I resize these partitions ? how ?
Thanks for help
Click to expand...
Click to collapse
We need more information. What ROM? What bootloader status? What happened when it crashed? What error messages are showing up when you try to flash a ROM or recovery?
Hello,
The bootloader informations : Unlocked / S-ON / 4EXT_Recovery_Touch
The rom installed : DHD_WWE_3.12.405.1_STOCK_rooted_by_nitr00.zip
I can flash another recovery (TWR, ..)
In wiping partitions (one hour waiting :
E:Unable to mount /cache
E:Unable to mount /data
E:Unable to mount /system
E: Failed to wipe dalvik
When trying the same rom :
the message error :
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error n /sdcard/DHD...._nitr00.zip (status 7)
Installation aborted.
After the TWR recovery i returned to 4Ext recovery, I did in 2 steps
1 - a wipe for factory reset/cache/dalvik,
2 - shutdown 5 minutes later
3 - i did a wipe for data/system and boot.
without shutdowning, i had an error failed to ...
I installed the RandomRom (145 and 5.00)
Firstly RandomRom145.zip
shutdown 5 minutes
secondly RandomRom5.00
then I flashed th boot.img
The rom was installed without errors.
When I booted it, I have the first white screen then I had a black screen for 1 or 2 minutes then the recovery tool was loaded.
Finally, I think that ma DHD is really dead.
I spent a day to arrive to this !!
Thanx for helps
TF85 said:
Hello,
The bootloader informations : Unlocked / S-ON / 4EXT_Recovery_Touch
The rom installed : DHD_WWE_3.12.405.1_STOCK_rooted_by_nitr00.zip
I can flash another recovery (TWR, ..)
In wiping partitions (one hour waiting :
E:Unable to mount /cache
E:Unable to mount /data
E:Unable to mount /system
E: Failed to wipe dalvik
When trying the same rom :
the message error :
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error n /sdcard/DHD...._nitr00.zip (status 7)
Installation aborted.
After the TWR recovery i returned to 4Ext recovery, I did in 2 steps
1 - a wipe for factory reset/cache/dalvik,
2 - shutdown 5 minutes later
3 - i did a wipe for data/system and boot.
without shutdowning, i had an error failed to ...
I installed the RandomRom (145 and 5.00)
Firstly RandomRom145.zip
shutdown 5 minutes
secondly RandomRom5.00
then I flashed th boot.img
The rom was installed without errors.
When I booted it, I have the first white screen then I had a black screen for 1 or 2 minutes then the recovery tool was loaded.
Finally, I think that ma DHD is really dead.
I spent a day to arrive to this !!
Thanx for helps
Click to expand...
Click to collapse
First your DHD in continuously reboot, than You were unable to make a call and now this.
All this in period in one mouth?
I think you have corrupted eMMC.
No
I have 3 HTC Desire HD
First : in a continuous reboot,
Second : unable to make a call,
Third : the actual problem.
Best regards
Did you wipe everything after last ROM instalation (ROM + boot.img)?
Hello,
Yes I do everything (using 4ext Recovery Touch).
It takes a long long time to wipe : wipe data/factory reset; cache; cache+dalvik; dalvik cache; battry.
I had errors when formatting system and/or data, like :
formatting /data
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p27
best regards
TF85 said:
Hello,
Yes I do everything (using 4ext Recovery Touch).
It takes a long long time to wipe : wipe data/factory reset; cache; cache+dalvik; dalvik cache; battry.
I had errors when formatting system and/or data, like :
formatting /data
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p27
best regards
Click to expand...
Click to collapse
I think it would be great to first check and to be shure if it's eMMC problem or not.
How to check this (one of example):
Try to install some other Recovery.
If you pass without errors turn off phone and pull out battery for few minutes. (if you get errors in installation, try few times, or try with different recovery, but just be shure that you not installing the same you allready have)
Put battery back on and turn on phone in recovery. Check is it really there and installed.
If you succesfuly installed diffrent recovery your emmc is working and you can fix it.
If you don't get errors, install it, and after restart you see that you have your old recovery, it's probably problem with your emmc. We can try more things to be shure.
TF85 said:
Hello,
Yes I do everything (using 4ext Recovery Touch).
It takes a long long time to wipe : wipe data/factory reset; cache; cache+dalvik; dalvik cache; battry.
I had errors when formatting system and/or data, like :
formatting /data
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p27
best regards
Click to expand...
Click to collapse
Or you could try booting into bootloader and try using the erase and format options
like this
Code:
fastboot erase system
Code:
fastboot erase data
Code:
fastboot erase cache
Code:
fastboot erase boot
Same to the format
Code:
fastboot format system
Code:
fastboot format data
Code:
fastboot format cache
Code:
fastboot format boot
If these dont work, then am afraid your emmc is f*cked.
Hello,
Yes the emmc is out, I can't :
- erase or format system
- erase or format data
- erase or ormat cache
Thank you very much for your helps
Hi all--apparently I "softbricked" (or "soft bricked") my unlocked at&t s3 (SGH-I747) that I rooted since, after I factory reset and cache wiped my 4.1.1, I get passes on Odin whenever I try to install 4.1.1 again, which is all I wanted to do so I could try to upgrade to 4.3, but I never got that far. I just can't get 4.1.1 working again after a factory reset cache wipe.
What happens, now, is that my phone just can't get past the pulsing blue samsung logo after rebooting into any new 4.1.1 firmware I load with Odin (and I tried a few options--both stock SGH-I747 4.1.1 and the one here), or root66, but my phone just gets stuck on the pulsing blue samsung logo and stops there every time. Kies can't connect to my phone any longer, either, and it won't recognize my phone for a firmware reset, and my computer will no longer recognize my phone nor successfully install drivers for it when it's trying to boot (when I connect my phone in recovery or download mode, however, my computer will install a driver to let the computer see the phone, but I can't actually do anything with the phone after that--and Kies doesn't connect after the computer installs these drivers, either).
So, in sum: I can successfully flash 4.1.1 stock/alternatives with Odin ("pass!") but that doesn't get me past the pulsing blue samsung icon. I think I've tried to flash a new boot partition during this process, but I'm not sure. Any advice would be much appreciated, since I've been working on trying to fix my phone for a day and a half now without any luck
Slight update: I installed CWM Recovery (PhilZ Touch) and wiped again but after loading the 4.1.1 stock/alternative (above link) my phone--still--won't get past the pulsing blue samsung logo still.
Additional info.: when I boot in recovery mode after flashing the above root66 rom, I get the following errors:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
Also, I just noticed when I try to factory reset again it says this:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p17
Data wipe complete.
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/last_log
etc.
Thanks for taking the time to read this. I appreciate it very much. I honestly can't do anything until I get help here.
Pfhyde said:
Hi all--apparently I "softbricked" (or "soft bricked") my unlocked at&t s3 (SGH-I747) that I rooted myself, later, since I get passes on Odin whenever I try to install new firmwares, so I don't have the same problem those trying to roll back to 4.1.1 after failing to get 4.3 going, since in my case, I just can't get 4.1.1 working again after a factory reset cache wipe. I wanted to put a stock 4.1.1 on so I could try to update to 4.3, but I never got far enough to even try that.
What happens, now, is that my phone just can't get past the pulsing blue samsung logo after rebooting into any new 4.1.1 firmware I load with Odin (and I tried a few options--both stock SGH-I747 4.1.1 and the one here), or root66, but my phone just gets stuck on the pulsing blue samsung logo and stops there every time. Kies can't connect to my phone any longer, either, and it won't recognize my phone for a firmware reset, and my computer will no longer recognize my phone nor successfully install drivers for it when it's trying to boot (when I connect my phone in recovery or download mode, however, my computer will install a driver to let the computer see the phone, but I can't actually do anything with the phone after that--and Kies doesn't connect after the computer installs these drivers, either).
So, in sum: I can successfully flash 4.1.1 stock/alternatives with Odin ("pass!") but that doesn't get me past the pulsing blue samsung icon. I think I've tried to flash a new boot partition during this process, but I'm not sure. Any advice would be much appreciated, since I've been working on trying to fix my phone for a day and a half now without any luck
Slight update: I installed CWM Recovery (PhilZ Touch) and wiped again but after loading the 4.1.1 stock/alternative (above link) my phone--still--won't get past the pulsing blue samsung logo still.
Additional info.: when I boot in recovery mode after flashing the above root66 rom, I get the following errors:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
Also, I just noticed when I try to factory reset again it says this:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p17
Data wipe complete.
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/last_log
etc.
Thanks for taking the time to read this. I appreciate it very much. I honestly can't do anything until I get help here.
Click to expand...
Click to collapse
If you're just looking to get back to stock 4.3, you can use this:
http://forum.xda-developers.com/showthread.php?t=2496425
You'll need the Heimdall suite:
http://glassechidna.com.au/heimdall/
Once the drivers and all are there, use the Flash tab in Heimdall and attach each file appropriately.
I had to do this same process recently so feel free to hit me up if you have an issue.
mstrswrd06 said:
If you're just looking to get back to stock 4.3, you can use this:
http://forum.xda-developers.com/showthread.php?t=2496425
You'll need the Heimdall suite:
http://glassechidna.com.au/heimdall/
Once the drivers and all are there, use the Flash tab in Heimdall and attach each file appropriately.
I had to do this same process recently so feel free to hit me up if you have an issue.
Click to expand...
Click to collapse
Well, I haven't ever had 4.3 on my phone, so there's nothing to 'get back' to. I was wanting to upgrade to 4.3, but then my factory reset/cache wipe made my phone unbootable after installing 4.1.1 firmware roms. If you think I should just try to install 4.3 in the state my phone's in now, then okay--but that seems to possibly introduce other problems, from what I've been reading elsewhere.
Did you get the stock 4.1.1 firmware from sammobile.com?
audit13 said:
Did you get the stock 4.1.1 firmware from sammobile.com?
Click to expand...
Click to collapse
Yes, as it turns out I did that already--I recognized the site immediately. I downloaded the default at&t rom again and will try flashing it (again) in the morning, but I doubt anything new will happen.
Try flashing 4.1.1 again in Odin, uncheck everything except F. Reset. When you see reset in the status windows, remove the USB cable, remove, the battery, replace the battery, go into recovery, perform a full wipe, then reboot. Do a full wipe before you first boot the newly-installed OS may fix the issue.
audit13 said:
Try flashing 4.1.1 again in Odin, uncheck everything except F. Reset. When you see reset in the status windows, remove the USB cable, remove, the battery, replace the battery, go into recovery, perform a full wipe, then reboot. Do a full wipe before you first boot the newly-installed OS may fix the issue.
Click to expand...
Click to collapse
First, when I go into recovery after flashing 4.1.1 default for at&t (though my phone is unlocked and was rooted--don't know if the root is still there after all that's happened) it says right away
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
#Manual MODE#
--Appling Multi-SCSC...
Applied the CSC-code:ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E: etc.
Then, when I try to wipe it gives me an error:
-- Wiping data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
Data wipe complete.
Then rebooting freezes on pulsing blue samsung logo--again
Did you flash an updated bootlaoder? Boot into download mode and let us know what it says on the screen.
audit13 said:
Did you flash an updated bootlaoder? Boot into download mode and let us know what it says on the screen.
Click to expand...
Click to collapse
It says
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Sorry for my belated responses, but I work late on the weekends in NZ.
audit13 said:
Did you flash an updated bootlaoder? Boot into download mode and let us know what it says on the screen.
Click to expand...
Click to collapse
Strange--I just booted up in recovery mode and wiped again; this time I got no errors, so I rebooted and--it works now in 4.1.1. Why it never wiped altogether before, when I didn't do anything different, is confusing; but there you have it. Now I'll venture into trying to get 4.2 or something.
Thanks all for your patience and help, even though in the end it worked on a fluke.
Glad you got your phone working. You do not have the 4.3 bootloader and, if I were you, I would not install the ATT 4.3 OTA update. This will install the 4.3 bootloader which makes it more difficult to get back to stock.
Pfhyde said:
Strange--I just booted up in recovery mode and wiped again; this time I got no errors, so I rebooted and--it works now in 4.1.1. Why it never wiped altogether before, when I didn't do anything different, is confusing; but there you have it. Now I'll venture into trying to get 4.2 or something.
Thanks all for your patience and help, even though in the end it worked on a fluke.
Click to expand...
Click to collapse
Some people have no problems at all, but CWM has a history of not wiping properly. That's why I don't using it anymore. There always came a point when it just would not wipe properly.
hello guys
i have a galaxy note 8 that i didn't use for a month and when start it goes in boot loop. i didn't flash any ROM. i try to reset factory but ended with error. any one can help please.:crying:
I am in the exact same circumstance; and i've never rooted it. All of a sudden it began to boot loop. The thing is -- is that I have data on there that I really need to preserve. Is there any way that I can reach the data on the hard drive? I've done a wipe cache partition function.
I'm also receiving some of the following error messages (among others):
failed to mount /efs (Invalid argument)
E: failed to mount /data (Invalid argument)
can't mount '/data (Invalid argument)
Please advise if you're familiar.
Thanks!
So I have a Galaxy S4 Mini (GT-i9091) stuck on boot loop.
On entering Recovery, I try "wipe data/factory reset" and get a failed message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TPA
Unable to open dst ' /system/app/VivaElFutbol_v1.03.apk' (No Such file or directory)
--Wiping data ...
Formatting /data
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc. 1/by-name/userdata
Formatting /cache
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc. 1/by-name/userdata
Flashing Stock ROM through ODIN gets a PASS (all threads completed, succeed 1 / failed 0), but on reboot it goes back to the Logo Boot Loop. I read elsewhere it may be a hardware issue rather than a software one. I'm looking for any advice or steps that I may be missing or is the phone doomed to be a shiny & fancy paperweight? Any info would be appreciated! :fingers-crossed:
Up? I have some problem
Enviado de meu SM-G800H usando Tapatalk
romTester14 said:
So I have a Galaxy S4 Mini (GT-i9091) stuck on boot loop.
On entering Recovery, I try "wipe data/factory reset" and get a failed message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TPA
Unable to open dst ' /system/app/VivaElFutbol_v1.03.apk' (No Such file or directory)
--Wiping data ...
Formatting /data
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc. 1/by-name/userdata
Formatting /cache
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc. 1/by-name/userdata
Flashing Stock ROM through ODIN gets a PASS (all threads completed, succeed 1 / failed 0), but on reboot it goes back to the Logo Boot Loop. I read elsewhere it may be a hardware issue rather than a software one. I'm looking for any advice or steps that I may be missing or is the phone doomed to be a shiny & fancy paperweight? Any info would be appreciated! :fingers-crossed:
Click to expand...
Click to collapse
Hi my friend!, I'm suffering now exactly the same problem as you...I can't erase that app and the phone goes back every time to the logo boot loop...Did you find any solution to your problem?? please any information would be useful...
Thanks,
really? nobody can help?
I am having same problem. any solution?
Hi there ..
I have the same problem for GT-i9192 with same problem message showed up after entering recovery menu :
Unable to open dst '/system/app/VivaElFutbol_v1.03apk' (No such file or directory)
did you fix this ?!
reply needed ^^
i am having the same problem but i cant even enter recovery mode
ODIN MODE
PRODUCT NAME: GT-i9195
CURRENT BINARY: CUSTOM
SYSTEM STATUS : CUSTOM
KNOX KERNEL LOCK : 0X0
KNOX WARRANTY VOID : 0X1
CSB-CONFIG-LSB : 0X30
BOOTLOADER AP SWREV : 2
WRITE PROTECTION : ENABLE