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
Related
Hi
I got a problem with my CWM when i will flash a kernel or a rom.
When i install a kernel then my phone stuck at the yellow triangle and i need to root it again to start my phone. Then i try again to flash the kernel and i got this by cwm
E:Can't mount /cache/recovery/command
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
if i have this i need to install root again :/ and then i don't have my new kernel but i have the kernel of CF-root =(!
please help
Try manually mounting /cache in CWM (I think it's in mounts and storage) menu.
I have the same problem; this happens for all kernels which embed a CWM v5.
Also I' can't even downgrade my kernels earler than KI3 (same error). The only kernels that work are CF-root KI3, KI4 and KI8.
For the same problem I can't flash any customized rom which do not embed any of the working kernels above.
I tried already wiping and formatting every possible thing, but nothing helped. And manual mounting cache in CWM fails.
Those who have problems with cwm 5, (like some partitions not mounting, updater apps rebooting into samsung recovery, etc) flash cwm 4 zip from your cwm recovery!
http://www.mediafire.com/file/h1yia0gt1sbnbie/cwm-4.0.1.5.zip
This is the same problem I faced....you can see that there here http://forum.xda-developers.com/showthread.php?t=1311692
and till today no solution for it.
droidphile said:
Those who have problems with cwm 5, (like some partitions not mounting, updater apps rebooting into samsung recovery, etc) flash cwm 4 zip from your cwm recovery!
http://www.mediafire.com/file/h1yia0gt1sbnbie/cwm-4.0.1.5.zip
Click to expand...
Click to collapse
this will not work as phone is unable to mount anything see the OP. I tried every sort of thing but nothing works.
Ah, damn, then we're not alone...
I think it all started when I decided to give it a try to one latest stock roms (it was KI1 or KI4 i guess...) as I was on KE7.
Before that I installed several early MIUI roms without any problem. But now I'm stuck... hopefully there will be a fix anytime soon!
Funnily enough I bought the I9100 when I heard that it was planned a MIUI rom development (I had a Desire with MIUI for about a year), and now that's officially released I can't install it...
mcrisa said:
Ah, damn, then we're not alone...
I think it all started when I decided to give it a try to one latest stock roms (it was KI1 or KI4 i guess...) as I was on KE7.
Before that I installed several early MIUI roms without any problem. But now I'm stuck... hopefully there will be a fix anytime soon!
Funnily enough I bought the I9100 when I heard that it was planned a MIUI rom development (I had a Desire with MIUI for about a year), and now that's officially released I can't install it...
Click to expand...
Click to collapse
same problem i was facing two days back....i tried all things but it was still used to stuck at yellow triangle. i was able to flash kernal but as it was stuck at yellow triangle i was not able to flash custom ROM.
then i decided to give my last chance....i tried to flash with cf-root KI3....n FINALLY it was booted. Feww !!!. then i flashed custom ROM . hope it will work for you also.
I attached kernal with this post. Use this kernal if you are on Stock 2.3.5 KI3
Right, here's what i did:
1) Wiped everything (/data, /cache, /dalvik)
2) Reboot in download mode and installed KI3 with 3 parts (PDA, DATA and CSC)
3) Self reboots, some yellow scrips appear, no errors, than another self-reboot
4) First boot, the stock rom works fine.
5) Reboot in download mode and applied the CF-root patch, and first boot. Again the stock rom rooted works fine.
6) Reboot in recovery mode: wipe /data, /cache / dalvik
7) install zip from sdcard -> miuiandroid_sgs2-1.10.20.zip (the latest official MIUI rom)
8) Stuck at yellow triangles, with continuous self reboot...
9) Reboot in download mode, reapplied CF-root KI3
10) Stuck at black screen past the yellow triangle....
11) Reboot in recovery mode: wipe /data, /cache / dalvik
12) install zip from sdcard -> miuiscotland_I9100-1.10.20.zip (another official MIUI rom)
13) Stuck at yellow triangles, with continuous self reboot...
14) Reboot in download mode, reapplied CF-root KI3
15) Stuck at black screen past the yellow triangle....
That's what it happens with every rom I try to install. The only rom I managed to install was the Villainrom 3.0, all other roms fail.
The rom I'm using now is wanam KI4 stock dedoxeded non wipe on top of stock KI4.
---------- Post added at 10:04 AM ---------- Previous post was at 09:18 AM ----------
By the way: even restoring the nandroid backup of the original rom, which I did as soon as i rooted the phone, fails as it gets stuck at the yellow triangle.
If I enter recovery mode it gives:
E:Can't mount /cache/recovery/command
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
Could it be that either the latest stock ROM or CF-root, when installed, change permanently something?
I would know if this problem happens once you install CWM 5...is it right?
Red_Vex said:
I would know if this problem happens once you install CWM 5...is it right?
Click to expand...
Click to collapse
For sure it happens whenever I install CWM 5 or one of the older CF-Root kernels.
The only CF-Root kernels that don't give the /mount problems are KI2, KI3, KI4, KI8.
mcrisa said:
For sure it happens whenever I install CWM 5 or one of the older CF-Root kernels.
The only CF-Root kernels that don't give the /mount problems are KI2, KI3, KI4, KI8.
Click to expand...
Click to collapse
Cf root kernel (as i read from officiale thread) are stock one + cmw,busy and root.
Red_Vex said:
I would know if this problem happens once you install CWM 5...is it right?
Click to expand...
Click to collapse
I think to some extent this might be the problem ... ... ... bcoz I managed to flashed two custom roms namely RarityROM+v3.7+by+PFittech+-+WIPE & BezkeIce2 which I think have CWM 4 where else all other roms have CWM5 ... correct me if I am wrong.
zking said:
I think to some extent this might be the problem ... ... ... bcoz I managed to flashed two custom roms namely RarityROM+v3.7+by+PFittech+-+WIPE & BezkeIce2 which I think have CWM 4 where else all other roms have CWM5 ... correct me if I am wrong.
Click to expand...
Click to collapse
Sorry i don't u understand very well
Red_Vex said:
Sorry i don't u understand very well
Click to expand...
Click to collapse
I meant to say yes CWM5 can be a problem. as I was able to flash 2 custom roms which were having CWM4. But any other custom rom which was having CWM5 is not getting flashed.
zking said:
I meant to say yes CWM5 can be a problem. as I was able to flash 2 custom roms which were having CWM4. But any other custom rom which was having CWM5 is not getting flashed.
Click to expand...
Click to collapse
As i far i know the only rom that have cmw5 are Cyanogen & co and Miui & co.
Are there also stock based roms?
zking said:
I meant to say yes CWM5 can be a problem. as I was able to flash 2 custom roms which were having CWM4. But any other custom rom which was having CWM5 is not getting flashed.
Click to expand...
Click to collapse
CWM5 or CWM4 is not the problem. u need to use the 3 tar(PDA,CSC,MODEM) Odin flashing method. if you did it right there shouldn't be any yellow traingles at boot. and i had EXACTLY the same problem couple of weeks ago, now am on MIUI.
wish you guys goodluck.
henrychukx said:
CWM5 or CWM4 is not the problem. u need to use the 3 tar(PDA,CSC,MODEM) Odin flashing method. if you did it right there shouldn't be any yellow traingles at boot. and i had EXACTLY the same problem couple of weeks ago, now am on MIUI.
wish you guys goodluck.
Click to expand...
Click to collapse
I tried already with the 3 tar XXKI3. The stock rom boots nicely without any yellow triangle.
When I root it the yellow triangle appears (as expected) and the phone still boots nicely.
The problem comes when I try to install MIUI, as it bootloops at the yellow triangle.
I think I tried every possible thing, given my download count is at 126...
mcrisa said:
I tried already with the 3 tar XXKI3. The stock rom boots nicely without any yellow triangle.
When I root it the yellow triangle appears (as expected) and the phone still boots nicely.
The problem comes when I try to install MIUI, as it bootloops at the yellow triangle.
I think I tried every possible thing, given my download count is at 126...
Click to expand...
Click to collapse
lol 126! i thought i had the highest, but not anymore , try this way.how i fixed mine. first flash your bootable rom and root, then perform a hard reset ( i don't remember the code for hard reset but it was something like *#numbers*numbers*#) this will wipe all ur phone's data, including ur SD card files, so please make backup 1st.
after hard reset(not factory reset) reboot to CMW and wipe all again (factory reset, cache,dalvik, then go to mounts and storage> format system,cache, data, then COPY your flash-able zip (i would suggest CM7 first, same way i did mine) onto your sdcard and try flash(if CM7 flash it twice before rebooting) if it was successful you will get stuck on boot-up (not reboot loop) just go bact to CMW and wipe factory reset,cache and dalvik, reflash CM7 twice also then reboot, if your lucky it will work for u
cheers!
Ok, somewhow I managed to succeed!
I made some additional tests (also following henrychukx suggestions) and, at a certain point, I decided to remove the EXTERNAL SD card.
I think that was the key to the success (at least for me)!!
With the external SD card removed, i flashed the "speedmod-kernel-s2-k2-13" kernel then I flashed the 1.0.21 miui ROM, the I flashed again with ODIN the Siyah-v2.1rc3 kernel.
Magically MIUI booted!
I've also been able to boot into CWM 5 recovery (without any strange /mount error) and update MIUI to 1.10.28 (but had to flash again the Siyah-v2.1rc3 kernel)
Not sure how stable it is this setup, but so far it seem to work
henrychukx said:
then perform a hard reset ( i don't remember the code for hard reset but it was something like *#numbers*numbers*#) this will wipe all ur phone's data, including ur SD card files, so please make backup 1st.
after hard reset(not factory reset) reboot to CMW and wipe all again (factory reset, cache,dalvik, then go to mounts and storage> format system,cache, data,
Click to expand...
Click to collapse
First I did remove my external sd card and then:
While on stock, After following above steps my phone got stuck on Boot Screen, I again rebooted in CWM Recovery did the Factory reset, wipe cache, dalvik and rebooted again phone got stuck on Boot screen...any way I thought of flashing a kernel through odin I flashed Speedmod kernel but still phone hangs on boot screen. Now I am going back to flash stock again.
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)
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?
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!
Today i was trying to install custom rom 6.0+ or higher on my brother phone (i9100) I found a tutorial on this page:
https://forum.xda-developers.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601
I was doing the same and all went good i flash twrp
And there is... A point 4. After changing from ext4 to f2fs data and cache i saw an error e:/data cant mount same with cache.I decided to wipe cache but i couldnt, so i downloaded stock rom and i flashed it by odin after that i hear only samsung startup sound and bootlooping logo.When im going to recovery error with cache dissapered but with data its still visible. E:/data cannot mount (invalid argument)
And now there is a question can i do something to rescue my brother phone? Its really important for me guys pls help me.
And yes i tried factory reset.
I might have a solution
konrino said:
Hello!
Today i was trying to install custom rom 6.0+ or higher on my brother phone (i9100) I found a tutorial on this page:
https://forum.xda-developers.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601
I was doing the same and all went good i flash twrp
And there is... A point 4. After changing from ext4 to f2fs data and cache i saw an error e:/data cant mount same with cache.I decided to wipe cache but i couldnt, so i downloaded stock rom and i flashed it by odin after that i hear only samsung startup sound and bootlooping logo.When im going to recovery error with cache dissapered but with data its still visible. E:/data cannot mount (invalid argument)
And now there is a question can i do something to rescue my brother phone? Its really important for me guys pls help me.
And yes i tried factory reset.
Click to expand...
Click to collapse
Why don't you use a different odin version may be much older one or newer one and by the way did u download the right firmware from the right source? Verify whatever I mentioned and give it a try with older odin,or simply follow some YouTube video! Thank me if I had helped you!
Ok i repaired this errors in recovery i install right kernel agaim from this pack (link above) next i install twrp and wipe data cache and other stuff, and when i flashed resurection remix with gapps(and without) my phone get bootloop. I tried cachce data dalvik wipe- doesnt work i tried to flash again this room still bootloop.
How can i repair this? Should i flash by odin stock rom?
konrino said:
Ok i repaired this errors in recovery i install right kernel agaim from this pack (link above) next i install twrp and wipe data cache and other stuff, and when i flashed resurection remix with gapps(and without) my phone get bootloop. I tried cachce data dalvik wipe- doesnt work i tried to flash again this room still bootloop.
How can i repair this? Should i flash by odin stock rom?
Click to expand...
Click to collapse
Try going back to ext4 format instead of f2fs.
If that doesn't work, try flashing stock via Odin then start over with the guide, I believe there is an updated way to upgrade that has the rePIT built in, try finding it and use that guide.
Sent from my SCH-I535 using Tapatalk