Related
I unlocked the boot loader using the easy unlocker (version 4.2) And everything went smoothly. I then pushed Clockworkmod onto it as well. Booted fine, no problems.
I put the .zip for Neutrino onto the internal storage of the phone, then installed via zip. The install went smoothly, but when I went to exit and reboot I get the following error:
Code:
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
I powered the phone off, and when I try to turn it on, the phone gets stuck at the Motorola screen. All it displays is "Unlocked" and hangs there until I pull the battery. I can access recovery, fastboot, etc. But, the phone won't load past there.
Any help would be greatly appreciated.
I started with a newly fixed Atrix, with 2.3.6. Unlocked fine, no problems. Also, sorry for posting here, and not the development thread, but I don't yet have permissions.
Have a great day.
EDIT: Tried doing a factory reset, wiping the cache, and reinstalling. Still getting the errors that I posted above, and it still won't boot.
EDIT 2: I'm allowed to post in the developers forum now. If I get a fix over there I'll update over here for anyone who may run into my problem in the future!
pink401k said:
I unlocked the boot loader using the easy unlocker (version 4.2) And everything went smoothly. I then pushed Clockworkmod onto it as well. Booted fine, no problems.
I put the .zip for Neutrino onto the internal storage of the phone, then installed via zip. The install went smoothly, but when I went to exit and reboot I get the following error:
Code:
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
I powered the phone off, and when I try to turn it on, the phone gets stuck at the Motorola screen. All it displays is "Unlocked" and hangs there until I pull the battery. I can access recovery, fastboot, etc. But, the phone won't load past there.
Any help would be greatly appreciated.
I started with a newly fixed Atrix, with 2.3.6. Unlocked fine, no problems. Also, sorry for posting here, and not the development thread, but I don't yet have permissions.
Have a great day.
EDIT: Tried doing a factory reset, wiping the cache, and reinstalling. Still getting the errors that I posted above, and it still won't boot.
EDIT 2: I'm allowed to post in the developers forum now. If I get a fix over there I'll update over here for anyone who may run into my problem in the future!
Click to expand...
Click to collapse
Do not post on the Development thread, this is the right place. Development is for Development of ROMs, Kernels and Modifications that is why is named so, not for asking questions. try rebooting into recovery, mounts and storage, format cache, format data, format system, wipe data/factory reset, then install/flash the ROM.
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
So i've posted pieces of this in other threads assuming i knew what the problem was, but nobody has been able to help me so far so i'm posting the whole saga anew.
First off, my phone:
LazyPanda S-OFF
HBOOT:1.12.111
RADIO-1.12.11.0809
I was running MeanRom 4.8 with TWRP 2.3.0.1
Like so many others i tried to OTA update just to get stuck at the recovery screen on reboot. I then found out that i had no ROM installed. I tried to wipe (cache, dalvik, system, etc) and flash a new ROM but i kept getting FAIL messages in TWRP.
"Formatting and mounting partition...
e:error in /sdcard/meanrom-ics-v49-jewel-ltevo.zip
(status 1)
error flashing zip '/sdcard/meanrom-ics-v49-jewel-ltevo.zip'
updating partition details"
I figured it might be a botched DL so i did it manually, MD5 checked out after copying to the mounted device. Attempted to flash the clean DL and i got the same error message. I nandroid restored an old stock rooted ROM I had and it installed just fine. After booting up to the system ROM for the first time I immediately got an "Internal storage is low" error. Checked and after a clean restore (no apps installed, fresh out of the box...) i only have ~200MB free in the app storage section (out of 1.92GB). I can't fathom what's taking up all the other space, nothing seems to be there. Because of this i can't install Titanium, Rom Toolbox, or anything else that may be remotely useful. I tried fixing permissions and re-wiping, re-restoring and i got the same thing.
I tried to flash the TWRP 2.2.2.0 image from recovery thinking this was the problem and got this message:
"updating partition details
E:unable to open ums lunfile 'sys/class/android_usb/android/f_mass_sto.....
Formatting cache...done
Formatting Data... done
Using rm -rf on .android_secure
Updating partition details
E:unable to open ums lunfile 'sys/class/android_usb/android/f_mass_sto.....
E:unable to open zip file."
And THEN i tried to ABD flash the TWRP image through fastboot with "fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img" then 'fastboot flash boot openrecovery-twrp-2.2.2.0-jewel.img' and got this error:
"FAILED (remote partition is not allowed to be flushed!)"
So, i'm stuck with a device that loads a stock ROM, cant flash a new recovery or ROM, and cant' install anything useful because it's full after a restore. Does anyone have any suggestions how to clean/resore my partitions through ADB or a script? Your advice is much appreciated.
I can't help, but I suspect you'd have better luck posting this in the TWRP thread.
I'm wondering if fastboot erase cache would help here. I've seen that command used I think to clean a partition, but it may have been for something else. Sorry, this is a bit over my head. Hope you get help.
hurled from my AOKP'd Evo LTE. Enjoy.
You might have to re lock and run the RUU and then unlock and flash twrp, 2.3 has issues with the partitions for some reason so stick to 2.2
Try updating to the latest twrp. The latest is 2.3.1.0 not 2.3.0.1.
2.3.0.1 had issues which you can read about here
http://www.pocketables.com/2012/10/...for-htc-evo-4g-lte-fixes-rom-flash-death.html
It's been updated already? Cool
om4 said:
It's been updated already? Cool
Click to expand...
Click to collapse
Yeah, it fixes the mounting of the sdcards and the flashing rom problem
You may also want to get the 1.12.2222 hboot from the unlimited site. It has fastboot commands enabled.
I noticed you tried flashing TWRP to both the recovery and boot partitions...Do you get the same error when you flash to just recovery? TWRP should not be on boot.
Sent from my EVO LTE
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.
Hboot: 2.10
Radio 1.13.11.1105
Recovery: Twrp 2.7.0.8
S-on
About a year ago I bricked my phone. Now I'm trying to salvage it to have something to play around with. Here's the run down
-Wiped entire phone by accident (no longer has an OS!)
-Phone was stuck in boot loop
-When trying to fastboot cm-11, I was getting E:unable to mount /sdcard
-Was unable to mount internal sdcard to format it in Windows
-Flashing cm-11 in TWRP would fail due to E:unable to mount /data
-Somehow I have gotten my phone back to where I have TWRP installed and can mount sdcard in adb and it is recognized in Winddows
-reformatted internal sdcard
-after reformat attempted to flash cm-11. Now i'm getting md5 error
-downloaded cm-12
-attempted to flash cm-12, it failed. Tried a second time, it was successful
-Now, when i flash a rom in Twrp it fails the first 1-2 times. Eventually the rom successfully flashes
-after the rom flashed, I choose to reboot system and install Su
-When booting into the rom, phone gets stuck at HTC boot screen
What am I doing wrong? What would cause the rom not to boot after successful install?
Take pics of the failed installs and post em. Try a RUU. That should get you back to a working phone from where you're at.
down2mars said:
Hboot: 2.10
Radio 1.13.11.1105
Recovery: Twrp 2.7.0.8
S-on
About a year ago I bricked my phone. Now I'm trying to salvage it to have something to play around with. Here's the run down
-Wiped entire phone by accident (no longer has an OS!)
-Phone was stuck in boot loop
-When trying to fastboot cm-11, I was getting E:unable to mount /sdcard
-Was unable to mount internal sdcard to format it in Windows
-Flashing cm-11 in TWRP would fail due to E:unable to mount /data
-Somehow I have gotten my phone back to where I have TWRP installed and can mount sdcard in adb and it is recognized in Winddows
-reformatted internal sdcard
-after reformat attempted to flash cm-11. Now i'm getting md5 error
-downloaded cm-12
-attempted to flash cm-12, it failed. Tried a second time, it was successful
-Now, when i flash a rom in Twrp it fails the first 1-2 times. Eventually the rom successfully flashes
-after the rom flashed, I choose to reboot system and install Su
-When booting into the rom, phone gets stuck at HTC boot screen
What am I doing wrong? What would cause the rom not to boot after successful install?
Click to expand...
Click to collapse
The reason you're getting hung up when you boot is due to being S-on. You have to install the kernel separately from the ROM, depending upon the ROM. Hit the top link in my sig and read the section on S-on kernel flashing. My recommendation would be to gain S-off.
Bingo!
Magnum_Enforcer said:
The reason you're getting hung up when you boot is due to being S-on. You have to install the kernel separately from the ROM, depending upon the ROM. Hit the top link in my sig and read the section on S-on kernel flashing. My recommendation would be to gain S-off.
Click to expand...
Click to collapse
Yeah, so it was a long day, but i'm finally up and running. It ended up being a combination of issue stemming from me flashing an unstable kernel. I was only able to get the stock RUU to flash. I flashed the boot.img separately like you said and then booted into recovery to flash the zip and, voila! I had to wipe and format my data partition to get rid of a "Decrypt Storage" lockscreen, but everything is up now.
Thanks!