Hi everyone,
Let me present my situation.
After flashing a CM10-based rom (using cwm), I was able to use the phone for a few minutes. Then, the screen suddenly went black and I had to reboot it. Since then, my phone can no longer pass the phone logo (on stock rom) or cm9 boot screen. My attempts to flash stock GB & ICS (using Odin) were all successful but again it was not able to pass phone logo.
I suspect that my phone was bricked because of mmc_cap_erase bug (afaik, my phone model is vulnerable to this bug). However, emmc_find_brick_start script of hg42 was able to finish after ~23 hours of scanning . Furthermore, I can mount /efs /system /data /cache /emmc using cwm without problem. I can also browse these partitions using Aroma file manager easily.
So, I'm confused now. I'm not sure whether it's an effect of mmc_cap_erase bug or something else wrong with my phone. Any suggestion to tackle this problem is greatly appreciated.
As I'm still able to browse the mmc, let me know whatever file I should pull to assist with debugging.
Thanks
Alan
alansmith_xda said:
Hi everyone,
Let me present my situation.
After flashing a CM10-based rom (using cwm), I was able to use the phone for a few minutes. Then, the screen suddenly went black and I had to reboot it. Since then, my phone can no longer pass the phone logo (on stock rom) or cm9 boot screen. My attempts to flash stock GB & ICS (using Odin) were all successful but again it was not able to pass phone logo.
I suspect that my phone was bricked because of mmc_cap_erase bug (afaik, my phone model is vulnerable to this bug). However, emmc_find_brick_start script of hg42 was able to finish after ~23 hours of scanning . Furthermore, I can mount /efs /system /data /cache /emmc using cwm without problem. I can also browse these partitions using Aroma file manager easily.
So, I'm confused now. I'm not sure whether it's an effect of mmc_cap_erase bug or something else wrong with my phone. Any suggestion to tackle this problem is greatly appreciated.
As I'm still able to browse the mmc, let me know whatever file I should pull to assist with debugging.
Thanks
Alan
Click to expand...
Click to collapse
Do this now
-Boot to recovery mode
-Factory data reset
-Reboot phone
Swyped from my Samsung Galaxy SII
Jokesy said:
Do this now
-Boot to recovery mode
-Factory data reset
-Reboot phone
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
Hi Jokesy
On trying to "factory data reset" I got
-- Wiping data...
Formating /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
Formating /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
Formating /sd-ext...
Formating /sdcard/.android_secure...
Data wipe complete.
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Thanks
Alan
alansmith_xda said:
Hi Jokesy
On trying to "factory data reset" I got
-- Wiping data...
Formating /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
Formating /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
Formating /sd-ext...
Formating /sdcard/.android_secure...
Data wipe complete.
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Thanks
Alan
Click to expand...
Click to collapse
have you rebooted your phone yet? any news?
Jokesy said:
have you rebooted your phone yet? any news?
Click to expand...
Click to collapse
Hi Jokesy,
Yes, I already rebooted it (as I have to use key combo to enter cwm), but still cannot wipe.
It's getting late on my side now. I'll come back tomorrow instead.
Thanks for helping me out.
Alan
alansmith_xda said:
Hi Jokesy,
Yes, I already rebooted it (as I have to use key combo to enter cwm), but still cannot wipe.
It's getting late on my side now. I'll come back tomorrow instead.
Thanks for helping me out.
Alan
Click to expand...
Click to collapse
Reflashing via Odin can help...
Isn't it Jokesy?
Peace
Hit Thanks & It will Disappear
Sent from S II Running Official ICS 4.0.4 with Siyah 4.1 [/size]
Omaxe said:
Reflashing via Odin can help...
Isn't it Jokesy?
Peace
Hit Thanks & It will Disappear
Sent from S II Running Official ICS 4.0.4 with Siyah 4.1 [/size]
Click to expand...
Click to collapse
Sure, Odin will help.
I'm just waiting for him to come back before i post what's next for him
Swyped from my Samsung Galaxy SII
Hello,
So, now my current situation is
_I'm still able flash stock successfully using Odin (at least that was what Odin reported)
_Booting always stuck. On stock kernel, my phone shows 3 different splashes: Samsung logo, SHV-E120L logo with progress bar & distributor logo. Sometimes my phone stuck at SHV-E120L screen (with 100% progress) until I reboot it, sometimes it can reach distributor logo but it will automatically restart (just like a boot loop)
_Wipe data/factory reset always result in make_extf4fs failed on /data
Is there anything else I should provide to narrow down my problem?
Thanks
Alan
alansmith_xda said:
Hello,
So, now my current situation is
_I'm still able flash stock successfully using Odin (at least that was what Odin reported)
_Booting always stuck. On stock kernel, my phone shows 3 different splashes: Samsung logo, SHV-E120L logo with progress bar & distributor logo. Sometimes my phone stuck at SHV-E120L screen (with 100% progress) until I reboot it, sometimes it can reach distributor logo but it will automatically restart (just like a boot loop)
_Wipe data/factory reset always result in make_extf4fs failed on /data
Is there anything else I should provide to narrow down my problem?
Thanks
Alan
Click to expand...
Click to collapse
Don't seems like just Software/Firmware Problem.
Its more than that...
Is there any strange effect like overheating...
Edit: I really loved the way you post thread...
Peace
Hit Thanks & It will Disappear
Sent from S II Running Official ICS 4.0.4 with Siyah 4.1 [/size]
Omaxe said:
Don't seems like just Software/Firmware Problem.
Its more than that...
Is there any strange effect like overheating...
Edit: I really loved the way you post thread...
Click to expand...
Click to collapse
Glad that you like the way I posted
Except for being shutdown after upgrading to CM10, my phone hasn't shown any strange symptom. After couple attempts to wipe data/factory reset and re-flashing stock rom, CWM appears to stuck now
Thanks
Alan
alansmith_xda said:
Hi everyone,
Let me present my situation.
After flashing a CM10-based rom (using cwm), I was able to use the phone for a few minutes. Then, the screen suddenly went black and I had to reboot it. Since then, my phone can no longer pass the phone logo (on stock rom) or cm9 boot screen. My attempts to flash stock GB & ICS (using Odin) were all successful but again it was not able to pass phone logo.
I suspect that my phone was bricked because of mmc_cap_erase bug (afaik, my phone model is vulnerable to this bug). However, emmc_find_brick_start script of hg42 was able to finish after ~23 hours of scanning . Furthermore, I can mount /efs /system /data /cache /emmc using cwm without problem. I can also browse these partitions using Aroma file manager easily.
So, I'm confused now. I'm not sure whether it's an effect of mmc_cap_erase bug or something else wrong with my phone. Any suggestion to tackle this problem is greatly appreciated.
As I'm still able to browse the mmc, let me know whatever file I should pull to assist with debugging.
Thanks
Alan
Click to expand...
Click to collapse
Hi, I have exactly same problem as you. I didn´t try browsing these weird files you posted here but I have same symptoms as you.
My device work perfectly with flashed Rootbox ICS ROM but when I flash new ROM like PA JB or ressurection JB i´ll end up with bootloops.
Robotr0n said:
Hi, I have exactly same problem as you. I didn´t try browsing these weird files you posted here but I have same symptoms as you.
My device work perfectly with flashed Rootbox ICS ROM but when I flash new ROM like PA JB or ressurection JB i´ll end up with bootloops.
Click to expand...
Click to collapse
Hi Robotr0n,
Have you tried flashing any stock rom yet. In most case that should help. I heard that some custom JB rom have different partition layout and might introduce bootloop.
Mine is in more severe situation. One or more partitions are corrupted so I cannot wipe nor new rom cannot write data (even though Odin can successfully flash the new rom).
So, keep hoping for the best. I guess you still have chance to recover your phone :fingers-crossed:
In case a stock rom cannot help, I suggest making a backup of your /efs partition as soon as possible.
Thanks
Alan
alansmith_xda said:
Hi Robotr0n,
Have you tried flashing any stock rom yet. In most case that should help. I heard that some custom JB rom have different partition layout and might introduce bootloop.
Mine is in more severe situation. One or more partitions are corrupted so I cannot wipe nor new rom cannot write data (even though Odin can successfully flash the new rom).
So, keep hoping for the best. I guess you still have chance to recover your phone :fingers-crossed:
In case a stock rom cannot help, I suggest making a backup of your /efs partition as soon as possible.
Thanks
Alan
Click to expand...
Click to collapse
Hi alansmith_xda !
I´m hardly searching for solution of my problem.
I tried stock ROM but after installing stock ROM my problem persists. Only one thing helped me - flashing litening 6.1 ROM .tar via ODIN. Only after flashing this ROM I was able to flash ICS Rootbox ROM. But I wasn´t able to instal my desired ROM - Paranoid Android JB or Ressurection ROM - still have these f***n bootloops.
Now I´m running on Rootbox ICS ROM and I´m happy that atleast at this ROM is everything working perfectly, but you know, I still want PA ROM.
Anyway, check my thread where I´m tryin to solve my problem: http://forum.xda-developers.com/showthread.php?t=1870567
I have a simular problem. When i install a rom any rom my phone turns on the first time then after reboot it can't boot up.
I reseted the phone the it booted up but after i tryed to reboot it again i had the same problem. What to do?
Sorry for the bad english
Hi All,
i think i just softbricked my S3. i was running Omega rom 33.2 and found the phone was unstable. Hence i wiped data, factory reset, clear dalvik cache and etc. after flashing the rom, it got stucked at samsung boot screen.
i even tried to reflash the rom but still failed to boot up. after that i decided to flash stock rom using Odin (I9300ZSDLK2). it managed to boot in but then it got stucked at recovery (failed to mount /system (Invalid argument). i thought it could be something wrong with the /system, i then flash CWM to format /system. obvious i wont be asking for help if that step succeeded. i basically got pawned because i am not able to mount /system. anybody can help me?
HI all... i have a Verion Note 2. Running Sophisticated 3.1 on 4.3.1
TWRP 2.6.3.1
Fails on backing up /data partition
Give me a E: Error tarring split files when i try to backup
Tried updating to 2.7 and it sees the data partition as 1300 GB so that wont work
Tried updating TWRP to latest version 2.8.1 and 2.8.4 then it gives me Unable to STAT
My rom is getting all kinds of problems, so time for a new one anyways.... I'm just worried if i dont have a backup and i wipe... etc. and then i cant flash a new rom...
Should i be worried about this? should i just wipe this and try flashing a new rom? Or is my /data partition corrupted? How do i fix this?
Suggestions??
FIXED - Factory reset.... duh
Before I ask, I have very limited knowledge of ADB and have been using "interface" like programs like WugFresh for all my Android root/flashing/pushing.
This is on my Nexus 6
I wanted a custom ROM. I settled on Cyanogenmod. Somewhere during the process I messed up and had to start over. I must have unchecked/checked a box I should/shouldn't have because I kept getting the E: Unable to mount Storage and cannot see my phone in Windows Explorer as an MTP device. So I did a complete factory reset, flashed the stock ROM and it seemed to resolve the error. I then flashed CM 12.1 again and started the daunting process of reconfiguring my phone. I chose not to restore my backup because I wasn't sure if the error would come back too (n00bie, I know). Then I also made the mistake of allowing the OTA CM update. Well I lost root as a result. So I attempted to root again but it got stuck at the boot logo. In a panic I booted into TWRP and dirty flashed CM 12.1 using ADB sideload. All was good, I re-rooted again successfully, but now I am getting the same E: Unable to mount Storage error again.
So I guess my question is, how do I do a backup so I do not have to reconfigure everything again and still be able to flash the stock ROM. Or do I even need to flash the stock ROM again, can I do a factory reset and flash CM 12.1 or will my error not be resolved?
Thanks in advance.
Hello guys.
My phone has just stopped working for no apparent reason. I can enter in CWM recovery. I tried wiping everything I can (except the system of course), but that didn't help. I searched on line but I couldn't find a ROM or anything else that I can flash. So if any of you have a backup of the system could you possibly share it with me. I'll be very grateful for any assistance you could offer.