Hi
I've got a SmartQ Q8 for 4 weeks. When I recieved it I updated the firmware to the custom rom by D3BA. Everything has been running smoothly until today. While syncing Google Currents, the system crashed and rebooted. This happens sometimes, but this time it hasn't restarted. It shows SmartDevices logo for a time and then goes blank.
I can boot into CWM, so I have tried to restore D3BA firmware and I've also tried the official firmware, version 3.0. With the official I don't see any problem, but it keep on failing. When I install the custom server, I've seen some errors wiping the data partition and also some installing the zip. This are the messages
/data
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p9
and
/cache
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
I don't know what has happened. After googling the error, it seems like the partition is corrupted, and some directories are missing?? Is there a way to access a console? Maybe using fdisk this could be solved.
Can anyone help me with this?
Best Regards
trustno12003 said:
Hi
I've got a SmartQ Q8 for 4 weeks. When I recieved it I updated the firmware to the custom rom by D3BA. Everything has been running smoothly until today. While syncing Google Currents, the system crashed and rebooted. This happens sometimes, but this time it hasn't restarted. It shows SmartDevices logo for a time and then goes blank.
I can boot into CWM, so I have tried to restore D3BA firmware and I've also tried the official firmware, version 3.0. With the official I don't see any problem, but it keep on failing. When I install the custom server, I've seen some errors wiping the data partition and also some installing the zip. This are the messages
/data
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p9
and
/cache
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
I don't know what has happened. After googling the error, it seems like the partition is corrupted, and some directories are missing?? Is there a way to access a console? Maybe using fdisk this could be solved.
Can anyone help me with this?
Best Regards
Click to expand...
Click to collapse
You can enter in BOOTLOADER Mode and flash the STOCK ROM.
Best regards from Mr.Indigo!
Hello
I think i've tried that. I put the Stock Rom v1 (SMARTQQ8 file) in the root of my SD Card and then I booted with the Power + Vol+ buttons, so it shows a logo and starts doing something, with a progress bar. Once it finishes, the screen goes blank again. Is that what you meant?
Best Regards
EDIT: After flashing the stock rom, I've enter Recovery again (With Power+Ctrl-) and now I can wipe data. I've install the stock again and now everything seems to be OK. Thank you Mr. Indigo, you save my day.
Best Regards
trustno12003 said:
Hello
I think i've tried that. I put the Stock Rom v1 (SMARTQQ8 file) in the root of my SD Card and then I booted with the Power + Vol+ buttons, so it shows a logo and starts doing something, with a progress bar. Once it finishes, the screen goes blank again. Is that what you meant?
Best Regards
EDIT: After flashing the stock rom, I've enter Recovery again (With Power+Ctrl-) and now I can wipe data. I've install the stock again and now everything seems to be OK. Thank you Mr. Indigo, you save my day.
Best Regards
Click to expand...
Click to collapse
Hey, would you mind letting me know which method you used to flash stock firmware? I am having a similar case with an S3 (Gt-i9300)
Related
I just tried reverting back to stock 2.3.5 rom and after I flash it goes to stock recovery.
I get this:
--Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
E:format_volume: rfs format failed on /dev/block/stl10
Formatting /cache...
E:format_volume: rfs format failed on /dev/block/stl11
Deleting Meta Data
Data wipe failed.
I just hit "reboot system now" and now i just get the Samsung logo bootloop. Tried reflashing it multiple times but end up with the same result.
What device is it?
Seems to be a 5.0 and may be the comon memory formating issue.
Did you flash something "wrong" before you try to revert to stock?
lolo9393 said:
What device is it?
Seems to be a 5.0 and may be the comon memory formating issue.
Did you flash something "wrong" before you try to revert to stock?
Click to expand...
Click to collapse
It's a 4.0 US
I think my files may be corrupted. They flashed in Odin and passed, but keep getting problems.
When I flash Steves kernel 3.0 I can access CWM. I then get no errors but can't load my system.
axvk97 said:
It's a 4.0 US
I think my files may be corrupted. They flashed in Odin and passed, but keep getting problems.
When I flash Steves kernel 3.0 I can access CWM. I then get no errors but can't load my system.
Click to expand...
Click to collapse
Never seen anybody asking for this issue on a 4.0, we were only a group of 5.0 GB70 owners having faced this before. I do not want to direct you to a wrong way, in mean time waiting for any other advise or remedy, take time to read the related korean GB70 memory problem.
http://forum.xda-developers.com/showthread.php?t=1716277
I got the errors to go away but I still cannot access the system. In CWM it says:
ClockworkMod Recovery v3.0.0.5
Checking for ext4 partitions...
Checking /system...
Checking /data...
Checking /datadata...
Checking /cache...
Done!
I have had this same thing happen before but was able to revert to stock firmware.
EDIT: Finally fixed it i just didn't go into recovery until after I flashed everything.
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
I have a Samsung Galaxy Ace GT-S5830i which is rooted but on stock rom. I recently installed a live wallpaper "Exodus live wallpaper" from the play store and after going through the options it provided my phone just shutdown. I tried turning it back on and it started boot looping. I had a nandroid backup ready from CWM recovery but that would stop at data saying "Error while restoring /data!". I found this a bit odd so I factory reset it but with no luck. The next step I thought would be to flash back the stock using Odin. Again, no luck. After it says successful it reboots the phone which goes straight into recovery saying:
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
Reebooting...
and boot loop again.
I've tried re-partitioning, wiping cache, wiping dalvik cache, factory resets, formatting everything, using adb but with no luck (couldn't get root), tried restoring previous backups, trying different roms and copying the files directly to the directories using a root file manager.
I am now exhausted after 4 days of near sleepless nights trying to fix it and with nothing to show for it :crying: .
Please Help!!!!!
You haven't look into FAQ!
faq was one of the first things i checked and i've tried repartitioning with pit and i still get the same
lew101 said:
faq was one of the first things i checked and i've tried repartitioning with pit and i still get the same
Click to expand...
Click to collapse
Use CWM to format everything except sdcard
Then flash firmware with Odin 3.07 with pit file and after flashing, go to recovery and wipe data
Try this and report. I've been in the situation and dozens more. We can always find a way out
iamareebjamal said:
Use CWM to format everything except sdcard
Then flash firmware with Odin 3.07 with pit file and after flashing, go to recovery and wipe data
Try this and report. I've been in the situation and dozens more. We can always find a way out
Click to expand...
Click to collapse
Just tried it. On leaving recovery after flash it was still showing:
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
and it still boot loops
lew101 said:
Just tried it. On leaving recovery after flash it was still showing:
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
and it still boot loops
Click to expand...
Click to collapse
Flash a stock rom which is splitted into 4 parts ie including bootloader file using Odin v1.87.
Sent from my GT-S5830i using xda app-developers app
andy.acei said:
Flash a stock rom which is splitted into 4 parts ie including bootloader file using Odin v1.87.
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
still doing the same thing
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
and still boot looping :crying:
P.S. sorry about the late reply
lew101 said:
still doing the same thing
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
and still boot looping :crying:
P.S. sorry about the late reply
Click to expand...
Click to collapse
UPDATE
I've used Aroma file manager to see if I can find these files and they are exactly where they should be with read/write permissions for root and system (rw-rw-r--) so I have no idea why recovery can't open them.
also is there any way to force android to read them or to copy "recovery_kernal_log.txt" manually?
I'm thinking of taking it to samsung for repairs as nothing has worked so far so if anyone has some additional advice please post it before thursday 15th of august
First clear cache data from stock recovery. Than use cwm format system and data then enter download mode and use odin with pit file. U must use your country spesific firmware. If problem persists after all you may have a faulty phone.
Ps: take out sd card after odin flashes successfully in case problem related to sd card.
:: Freedom... ::
ChelebiTech said:
First clear cache data from stock recovery. Than use cwm format system and data then enter download mode and use odin with pit file. U must use your country spesific firmware. If problem persists after all you may have a faulty phone.
Ps: take out sd card after odin flashes successfully in case problem related to sd card.
:: Freedom... ::
Click to expand...
Click to collapse
Looks like I have a faulty phone then.
I wonder how that would have happened from using the live wallpaper as it was perfectly fine before that.
lew101 said:
Looks like I have a faulty phone then.
I wonder how that would have happened from using the live wallpaper as it was perfectly fine before that.
Click to expand...
Click to collapse
Probably its the last drop makes phone dead! Usually high powered magnets or heat may cause the error. If you use your phone while charging it gets really hot. Hope phone service can repair it.
:: Freedom... ::
same issue
Hi everyone, im having the same problem with my samsung galaxy ace gt5830i, after installing a playstore app, the phone just freezed and now its looping at start, the same error messege
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
also tryed flashing, and re - installing with odin, but nothing works, its a failure in the phone? isnt there is a way to install the bios firmware again?
sorry for my writing , my english is not very good, thanks to anyone who can guive an answer.
Radnico9 said:
Hi everyone, im having the same problem with my samsung galaxy ace gt5830i, after installing a playstore app, the phone just freezed and now its looping at start, the same error messege
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
also tryed flashing, and re - installing with odin, but nothing works, its a failure in the phone? isnt there is a way to install the bios firmware again?
sorry for my writing , my english is not very good, thanks to anyone who can guive an answer.
Click to expand...
Click to collapse
Just goto CWM wipe data/cache goto mount and storage do format system and data
And then Goto samsung's stock recovery Do wipe data / cache and then Flash Stock ROM That's it if
the problem is still so again do wipe/data in stock recovery
Sent from my Ace-i
I fixed it
lew101 said:
I have a Samsung Galaxy Ace GT-S5830i which is rooted but on stock rom. I recently installed a live wallpaper "Exodus live wallpaper" from the play store and after going through the options it provided my phone just shutdown. I tried turning it back on and it started boot looping. I had a nandroid backup ready from CWM recovery but that would stop at data saying "Error while restoring /data!". I found this a bit odd so I factory reset it but with no luck. The next step I thought would be to flash back the stock using Odin. Again, no luck. After it says successful it reboots the phone which goes straight into recovery saying:
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
Reebooting...
and boot loop again.
I've tried re-partitioning, wiping cache, wiping dalvik cache, factory resets, formatting everything, using adb but with no luck (couldn't get root), tried restoring previous backups, trying different roms and copying the files directly to the directories using a root file manager.
I am now exhausted after 4 days of near sleepless nights trying to fix it and with nothing to show for it :crying: .
Please Help!!!!!
Click to expand...
Click to collapse
Hello,
Well i have the same phone as you and have just fixed my boot loop well today i have found how to do it first turn on your phone until you get the boot loop then remove the back of your phone then remove your battery and place it back in and then put your back of your phone back on and the hold power home and volume up until it says the first words of load ing up (Samsung Galaxy Ace GT-S5830i) then let go. when it turns up with the red writing press volume down until you get to factory reset then press power wait until it resets then press volume up until you get to reboot then press power wait until it reboots GIVE IT TIME IT WILL BOOT LOOP BUT THEN LOAD go through with it all sign in with you google account wait until it loads up your phone and there
hell
i have also same problem just some different, my cell phone can,t access boot
Please Help!!!!![/QUOTE]
i was also facing the same problem
lew101 said:
I have a Samsung Galaxy Ace GT-S5830i which is rooted but on stock rom. I recently installed a live wallpaper "Exodus live wallpaper" from the play store and after going through the options it provided my phone just shutdown. I tried turning it back on and it started boot looping. I had a nandroid backup ready from CWM recovery but that would stop at data saying "Error while restoring /data!". I found this a bit odd so I factory reset it but with no luck. The next step I thought would be to flash back the stock using Odin. Again, no luck. After it says successful it reboots the phone which goes straight into recovery saying:
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
Reebooting...
and boot loop again.
I've tried re-partitioning, wiping cache, wiping dalvik cache, factory resets, formatting everything, using adb but with no luck (couldn't get root), tried restoring previous backups, trying different roms and copying the files directly to the directories using a root file manager.
I am now exhausted after 4 days of near sleepless nights trying to fix it and with nothing to show for it :crying: .
Please Help!!!!!
Click to expand...
Click to collapse
if your are still faceing this problem ..here is my skype ID :dotusman...i will tell you the whole procedure to update your firmware.and im sure it will fixed it..soryy for my english..
lew101 said:
I have a Samsung Galaxy Ace GT-S5830i which is rooted but on stock rom. I recently installed a live wallpaper "Exodus live wallpaper" from the play store and after going through the options it provided my phone just shutdown. I tried turning it back on and it started boot looping. I had a nandroid backup ready from CWM recovery but that would stop at data saying "Error while restoring /data!". I found this a bit odd so I factory reset it but with no luck. The next step I thought would be to flash back the stock using Odin. Again, no luck. After it says successful it reboots the phone which goes straight into recovery saying:
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
Reebooting...
and boot loop again.
I've tried re-partitioning, wiping cache, wiping dalvik cache, factory resets, formatting everything, using adb but with no luck (couldn't get root), tried restoring previous backups, trying different roms and copying the files directly to the directories using a root file manager.
I am now exhausted after 4 days of near sleepless nights trying to fix it and with nothing to show for it :crying: .
Please Help!!!!!
Click to expand...
Click to collapse
Follow every word given http://forum.xda-developers.com/showthread.php?t=1840645 and use the files downloaded from that thread . It will work[emoji2] [emoji2]
In the end i had to take it back to where i purchased the phone originally and they replaced free of charge.
help
Hey can I ask? How much did you pay for to fix your phone? We have the same phone and we have the same problem. im just playing modded game and it restarts and saying cant open copykernel file etc...
please help me ! I've try to reflash it . And its not fix. Ive been searching for almost two weeks . But I cant see other solution for how to fix it . Please help me.
Thank you.
Hello,
I'm trying to flash an old Samsung Galaxy Ace GT-S5830i with Cyanogenmod. Installing a new Recovery (CWM, tried several versions for the S5830i) works as expected. But unfortunately I'm unable to access (mount, format) the /system partition from any of those CWM recoveries.
If I go to 'mounts and storage' and try to 'mount /system', CWM says:
Code:
Error mounting /system!
If I try to 'format /system', it says:
Code:
Formatting /system...
E:format_volume: make_ext4fs failed on /dev/block/stl9
Error formatting /system!
I searched this forum and the web for answers, but so far were unable to find a sufficient one. Is this a known problem?
I tried to flash CM 9.1 unofficial port from http://forum.xda-developers.com/showthread.php?t=2118645 nevertheless. The installation seems to succeed (no obvious error messages), but afterwards the phone hangs at the 'Samsung Galaxy Ace GT-S5830i' splash screen in boot process forever. I guess that this is related to the unaccessable /system partition, right? If the partition is not accessible, then flashing the new ROM must have failed to write data to it as well.
Thanks in advance for any help.
Seems like the phone was bricked. I managed to fix it by flashing the stock ROM using Odin. Afterwards flashing CM 9.1 worked like a charm.
Hi all,
I have Samsung A5 2016 and I tried to update my phone through latest Naugat official firmware using by Odin however it turned out something wrong. My first problem is when I enter the boot screen, ''installing update'' screen pops up and then ''no comment screen'' afterward. Second problem is that boot screen shows an error says E: failed to find /misc partition. I've read tons of post however I couldn't figure this out.
I would greatly appreciate it if you could help me.
Thank you & Best!
Hi
My message has been moved here
https://forum.xda-developers.com/samsung-a-series/help/sm-a510f-rom-stock-entering-mode-t3653121
Thanks
Anybody know how to deal with the E: failed to find /misc partition? I saw this come up on my SM-J700T after I tried to flash TWRP. The flash passed but TWRP was not successfully installed. Probably because I did not prevent reboot and reboot in a proper way . But now I have been all around the barn trying to recover and eventually get twrp and root. I flashed several stock roms with lots of errors and finally got the phone running with Nougat 7.1.1 but the E: failed to find /misc partition error remained on the phone all the while. I was unable to use Odin to re-partition due to errors and have been trying to figure out how to use adb, also with errors (yesterday I launch "abd devices" and get a listing for my device (I think- it is not properly identified) and it lists the device properly, today it lists the same device as unauthorized. So what I really would like to do is completely wipe the phone and start fresh but I only have access to the stock bootloader which allows cache wipe and data wipe- factory reset, which does not wipe the Missing partition. So 1)completely wipe phone 2)install twrp 3)root