Related
Hi guys,
I'm afraid my emmc is fried. After occasional crashes/freezes/FC's in different apps/Android modules in CM7 over a few months, one day I opened this site in the browser, and the browser FC'ed and then kept FC'ing when opened. When rebooting, the phone gets stuck looping in the CM7 animated start-up logo. When I boot in Clockworkmod (v4.0.1.0) , I get this error:
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
and I can't use Clockworkmod. Cannot mount/wipe cache, cannot install anything. I tried checking the eMMC with ADB and FASTBOOT, but they can't see the device, though Heimdall does see it as I was able to flash recovery.bin again in d/l mode (but without fixing the problem). Please help, I've run out of ideas and have no phone...
bollorr said:
Hi guys,
I'm afraid my emmc is fried. After occasional crashes/freezes/FC's in different apps/Android modules in CM7 over a few months, one day I opened this site in the browser, and the browser FC'ed and then kept FC'ing when opened. When rebooting, the phone gets stuck looping in the CM7 animated start-up logo. When I boot in Clockworkmod (v4.0.1.0) , I get this error:
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
and I can't use Clockworkmod. Cannot mount/wipe cache, cannot install anything. I tried checking the eMMC with ADB and FASTBOOT, but they can't see the device, though Heimdall does see it as I was able to flash recovery.bin again in d/l mode (but without fixing the problem). Please help, I've run out of ideas and have no phone...
Click to expand...
Click to collapse
you need to get into recovery via the power menu...depending on what kernel version your running, three fingering into recovery will cause a bootloop. the same thing applies to all ICS roms. If you can no longer get the phone to boot up then simply odin cwm4 fixed for cm7, three finger into recovery, wipe data, then reflash the rom. Make sure everything is backed up first. More information can be found in section 3 here:
http://forum.xda-developers.com/showthread.php?t=1238070
Thanks for your reply. I explained that the phone doesn't boot up anymore (gets stuck in a loop), and while booting into ClockworkMod works (3 fingers), I get these errors, so even though the up/down/power buttons work (I can scroll through the recovery menus/options), certain things don't work, like wiping the cache (it cannot mount or open the cache) or re-flashing CM7 from SD-card... I get errors.
I've had problems with Odin before (it said it flashed stuff, but stuff didn't work), so I've been using Heimdall for a while instead. Like I said, I was able to successfully re-upload ClockworkMod to the phone (in d/l mode) with Heimdall, but it doesn't fix the problem. The problem seems to be that the cache partition is corrupted, and I can't do much from within ClockworkMod (though it worked without problems in the past).
I've found tips on here (http://forum.xda-developers.com/showthread.php?t=1284196) that the errors I get are sometimes (though not always) because of physical corruption of eMMC. Is it possible to flash CM7 or CM9 using Heimdall or (Heimdall-frontend), are there instructions on this, though I doubt it will work...I'm new to this lol. I want to at least have a working phone, until I can figure out how to fix the cache problem and make Clockworkmod work again. Thanks.
Is it possible to just fix the cache partition or re-partition using a program like Heimdall?
bollorr said:
Hi guys,
I'm afraid my emmc is fried. After occasional crashes/freezes/FC's in different apps/Android modules in CM7 over a few months, one day I opened this site in the browser, and the browser FC'ed and then kept FC'ing when opened. When rebooting, the phone gets stuck looping in the CM7 animated start-up logo. When I boot in Clockworkmod (v4.0.1.0) , I get this error:
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
and I can't use Clockworkmod. Cannot mount/wipe cache, cannot install anything. I tried checking the eMMC with ADB and FASTBOOT, but they can't see the device, though Heimdall does see it as I was able to flash recovery.bin again in d/l mode (but without fixing the problem). Please help, I've run out of ideas and have no phone...
Click to expand...
Click to collapse
i have the exact same problem with my fascinate i would think that if i could get odin to flash a new rom to it it would boot but im not intirely sure
I've found others who have the same problem... in my opinion it's clear that the cache partition got corrupted for some reason, either software (fixable) or hardware (the internal memory/eMMC which then it would need replacement or a new phone lol).
bollorr said:
I've found others who have the same problem... in my opinion it's clear that the cache partition got corrupted for some reason, either software (fixable) or hardware (the internal memory/eMMC which then it would need replacement or a new phone lol).
Click to expand...
Click to collapse
you need to flash back to a stock rom via odin, heimdall, or adb...thats the only way to fix it at this point. if you can get odin to recognize the device try section 5 of my guide.
Thanks. I'll give it a try. Odin doesn't see my device, so I'm using Heimdall Frontend which is a little bit different. Do you have instructions for it? I load atlas.pit, but then in order to load the GB rom (which is .tar.md5), it asks for a BIN file, and I also have to add a partition and it's got a lot of options there. Why doesn't Odin see my device, but Heimdall does?
I got Odin to recognize my device (stupid USB ports), I followed the instructions, phone says downloading, do not turn off target, Odin says the same... it's been more than 5 minutes, the same...does it mean I have a bricked device now?
and I forgot, Odin says in top left corner, SET PARTITION...it's been 15 minutes now, maybe it cannot set the partition
Update...I rebooted the phone into Recovery after 20 mins or so of Odin not being able to flash (set partition)... of course Odin detected it and a big red FAIL appeared in the top left corner, and the bottom log said Re-partition operation failed, so, is there anything else I can try or the memory chip fried?
http://rootzwiki.com/topic/8867-romsch-i500-vzw-ed05-froyo-heimdall-linux-friendly/
Thanks, I tried what you said, and just like I thought, Heimdall (like Odin) gave this error:
Uploading PIT
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
ERROR: Failed to send end session packet!
please help, I have no phone
Is Re-Partition checked in Odin? If it is, try unchecking it. If it isn't, try checking it. If it's unchecked, it won't fix the corrupted cache partition, but it should at least let you flash the OS
yes, I tried that in odin, doesn't work
Yikes. You seem to be stuck between a rock and a hard place. Honestly, it seems that the only possible option here is to get a new phone. It seems as though there must be physical damage to the chip, otherwise Odin/Heimdall would have worked.
bollorr said:
Thanks, I tried what you said, and just like I thought, Heimdall (like Odin) gave this error:
Uploading PIT
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
ERROR: Failed to send end session packet!
please help, I have no phone
Click to expand...
Click to collapse
your last option is to try adb.
MultipleMonomials said:
Yikes. You seem to be stuck between a rock and a hard place. Honestly, it seems that the only possible option here is to get a new phone. It seems as though there must be physical damage to the chip, otherwise Odin/Heimdall would have worked.
Click to expand...
Click to collapse
that's usually the diagnostic (fried eMMC chip) for these error messages (though not always) and that's what I thought, and I was looking for ways to determine for sure whether the chip is fried or not, as to know what to do and not waste my time and the time of the people on this board...for some reason adb doesn't work, or I don't know how to use it (first time using it)...I type adb devices, I get error, no devices, adb shell, error again
droidstyle,
do you have instructions anywhere on how to use adb, it was one of the first things I tried, but it doesn't see the devices, I cannot start shell (adb shell)...thanks
I made an ADB for Noobs guide about a year ago. It never gained much traction but it should still be current. Anywhere it says CM7, the same goes for CM9.
Previously, I had this phone rooted, and running CM12 with an open source gapps setup, with no problems. I also had TWRP installed, and an SD card with a copy of my ROM as I liked it, and my data.
Everything worked, and I was able to update my Android version and expand functionality quite a bit, which was useful while traveling abroad.
The other day however, when seconds before I had been using it as my hotspot, I tripped over the charging cord and dropped the phone quite hard on tile.
It broke into pieces, with the back coming off and the battery coming out.. The display is fine. I thought I killed it entirely, but I took the battery out and left it alone for half a day, and when I came home, I realized that it would:
1. Charge
2. Boot to recovery
3. Boot to download
This gave me some hope.
However, doing anything else would result in a bootloop.
I booted into recovery in preparation to re-flash my rom, and TWRP was not able to mount my SD card, and would not recognize my data there.
Additionally, when I tried to wipe everything but my SD card, TWRP failed to mount all partitions, as if something got corrupted.
When I tried to repair or change the file system type, this too failed. I cannot seem to get TWRP to recognize any storage. It says the phone is empty, with no internal, no external, and no OS.
Just a bunch of red "failed" lines every time I try to do something through the recovery.
I checked my SD card externally using an adapter on my mac, to make sure it was not corrupted. All my data is still there, including the backup of my ROM. However, since the phone will not recognize it, it's useless, and I can't find an Odin flashable .tar version of the CM12 ROM for this phone, plus when I tried to convert a copy to the correct file type, it failed to flash.
I tried to flash a copy of the stock rom (metroPCS version) to begin with, that I had saved on my computer.... which worked before when I messed up my initial flash. This time, It will flash successfully per Odin, but cause a bootloop.
Odin will still recognize my device... but adb from my mac terminal will not recognize it when I have the device connected or I would try to rebuild the file system that way.
I feel like I am going in circles and running out of options, or missing something..(possibly several things) but... I don't want to give up on this phone just yet, even if I had to demote it from daily driver use in the end ... any advice would be appreciated.... Thank you sooooo much!
Edited to add: I got ADB to recognize the device and ran a restore command, based on a file I had locally. This is what happened:
localhost:~ user$ adb restore ~/Downloads/cm-12-20150319-UNOFFICIAL-gardalte.zip
Now unlock your device and confirm the restore operation.
/sbin/sh: /sbin/bu: not found
Also adb remount resulted in a failed output.
Lastly, it appears abd only works in terms of recognizing my device when I am in recovery.
Preparing for a clean (with loss of data) installation LineageOS 14.1 + TWRP-3.1.0-0
Attention! The warranty is now invalid.
It's to delete all your data (programs, contacts, SMS ...)
Make a backup to external media or PC first.
Preparation:
- First you need to install the drivers. The phone must be determined by the computer.
- Kies must be stopped (if it is installed on the computer).
- It is desirable to disable antiviruses, firewalls and similar software.
- Use only USB rear ports (for a laptop it does not matter).
- It is desirable to use the original cable (why - I do not know, but many so advise).
- It is desirable to charge the battery by at least 50%, full charging is welcomed.
Instruction:
1. Install Samsung_USB_Drivers_for_Mobile_Phones
2. Unzip the folder Odin3_v3.09 and transfer it to the root directory C:
Run Odin3 v3.09.exe as administrator and select all as the screenshot :
- In the PIT field, insert the file - I9100_1.5GB-System_6GB-Data_512MB-Preload_by-the.gangster.pit.zip
- In the PDA field, insert the file - lp-kernel-14-03-CWM-for + ODIN.tar
Turn off the phone. Enter the device into the boot mode by pressing simultaneously the Volume Down, OK, Power ON / OFF buttons, confirming with the Volume Up key the desire to flash.
Then, we connect the phone to the computer, the ID field: COM should light up in blue, then press the START button.
A successful solution, you will see the word "Pass"
3. Disconnect the phone from the PC, transfer it to the CWM recovery mode.
That there were no problems with the internal memory (SDcard0), we format it:
- mounts and storage -> format / storage / sdcard0 -> default
Do a full system cleaning:
- wipe data / factory reset
- mounts and storage -> format / system
4. In the recovery process, install the files:
- TWRP-3.1.0-0-recovery-the.gangster-IsoRec-i9100.zip
+
- kernel-Lanchon-20160406-i9100.zip
5. Reboot and log in to TWRP.
6. Do not forget:
ROM - https://download.lineageos.org/i9100
+
OpenGApps - http://opengapps.org/
The following files were used in this manual:
- @arnab
- @the.gangster
- @Lanchon
THANKS!
Teams of : TWRP, Lineage OS.
Do all the credits to them.
I just wrote the instructions.
Good luck.
hello .. i followed your tutorial and i am on lineageOS now
however is there any method to cancel the sdcard0 entirely ?
i added a 64 GB SDcard and used the adoptable memory to increase my internal storage .. however whataspp still uses sdcard0 to store its folder !
any clues ??
how to root ????
hadid90 said:
how to root ????
Click to expand...
Click to collapse
Look here - https://forum.xda-developers.com/showpost.php?p=71684593&postcount=21
Set in TWRP: addonsu-14.1-arm-signed.zip
Follow the path:
Settings - Developer options - Root access - choose Apps and ABD
Check root access.
toy_story said:
Look here - https://forum.xda-developers.com/showpost.php?p=71684593&postcount=21
Set in TWRP: addonsu-14.1-arm-signed.zip
Follow the path:
Settings - Developer options - Root access - choose Apps and ABD
Check root access.
Click to expand...
Click to collapse
i didnt know i had to go to develoeper options and enable it thank you
about the sdcard0 .. i found my answer here
https://forum.xda-developers.com/galaxy-s2/orig-development/mod-switch-emulated-to-emulated-t3539651
hadid90 said:
about the sdcard0 .. i found my answer here
https://forum.xda-developers.com/galaxy-s2/orig-development/mod-switch-emulated-to-emulated-t3539651
Click to expand...
Click to collapse
I'm glad that you are doing well.
Be careful with "[MOD] Switch from non-emulated to emulated internal SD card", first read the entire stream.
I used it before, but because of certain problems, I stopped using it, and did not advise it on your question asked above.
toy_story said:
I'm glad that you are doing well.
Be careful with "[MOD] Switch from non-emulated to emulated internal SD card", first read the entire stream.
I used it before, but because of certain problems, I stopped using it, and did not advise it on your question asked above.
Click to expand...
Click to collapse
It's working very well here.. but you need to be careful on how to install the ROM .. i also used my external sd card to put the zip of lineage and gapps on.. it's the only way. I also used 50% of my sd card as an internal storage .. it s working pretty well
I followed the descriptions but my S2 won't get over the startingscreen of Lineage OS. There is always just this circle going from right to left on this arc. How long should I wait?
Thanks guy, very useful for someone who wants to install LOS on his S2 in 2017
Hi,
I tried to copy the files (TWRP-3.1.0-0-recovery-the.gangster-IsoRec-i9100.zip, kernel-Lanchon-20160406-i9100.zip, ROM lineageos.org/i9100 & OpenGApps) to the SD using my computer but my SD card adapter had a problem. I now have a new adaptor that works but am now stuck with all the files on the SD card ready to go but I can not boot into recovery to install the file. When I boot the phone I just get the startup screen with the Samsung logo and a yellow triangle. If I do the key presses to get to recovery with the phone connected to the computer and running odin then I can connect and reflash CWM but after that I cant boot into recovery to do step 5.
Any help appreciated,
Thanks,
Mark
ok i have done playing with my moms old S2 .. i need to return it back to its orginial latest stock rom .. any guides on how to do that ? i flashed the stock rom using odin but the S2 boots and stays on samsung logo animation for hours haha .. should i use the stock pit file and use the repartition option ? i heard that may brick the device .. any guides ? i ve searched but all threads are very old with dead links etc
hadid90 said:
ok i have done playing with my moms old S2 .. i need to return it back to its orginial latest stock rom .. any guides on how to do that ?
Click to expand...
Click to collapse
Look here:
- https://forum.xda-developers.com/showpost.php?p=71481676&postcount=587
- https://forum.xda-developers.com/showpost.php?p=73126683&postcount=48
Phone bricked! Help!
Bricked my phone for the first time while following the steps here!
Need help!
This was an old phone. I had Sentinel ROM installed. I had smashed the display years ago and just got it fixed a month ago. Since it was old so I did a factory reset from the Android settings. After that I got stuck in bootloop.
Didn't get much time to tinker with it for some time, till few days ago.
I had CWM installed. So at first I tried installing LineageOS by using option "installing from sdcard" from CWM recovery(This was before coming across this tutorial). It failed that time (I had tried a few times). I tried doing factory reset, wipe dalvik, format /system etc etc couple of times.
I think it always used to come out with some error:
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
Then after that I tried flashing TWRP ([RECOVERY] [ISOREC] [TWRP 3.0.2-1] [OFFICIAL] [26/04/2016]) following the 2nd installation instructions (Flash via HeimdallSuite (Windows only)) from this thread: https://forum.xda-developers.com/galaxy-s2/development-derivatives/recovery-twrp-3-0-0-0-t3330457
This also failed with this error:
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!
Then I came across this present tutorial. I had a lot of trouble trying to get ODIN to detect the phone plugged in via USB in download mode (i.e. to get ID field: COM in blue)
Somehow after a lot of tries with different USB cables, and reinstalling drivers and restarting Windows, finally it got detected. So I carried out the instructions ditto as in guide but I faced another error:
<ID:0/014> Added!!
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Set PIT file..
<ID:0/014> DO NOT TURN OFF TARGET!!
<ID:0/014>
<ID:0/014> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I unplugged the phone, closed ODIN and tried to retrace the same steps (I'm not sure if I restarted the phone during this time).
Now again it wasn't getting detected in the download mode.
So finally I switched off the phone and tried to get into Download mode. I couldn't do it. Then I realized that nothing was working. It wasn't even starting normally to the "Sentinel ROM" logo. Tried charging the phone and realized that even the charging battery icon doesn't show/indicate it is being charged.
That's when I realized that it was hard bricked (totally dead). If I plug it in charger, it gets heated up.
Can somebody please help unbrick my phone?
That was a misstake !
<ID:0/014> Re-Partition operation failed.
This Tutorial @toy_story is great, so you cannot do wrong.
You have to come in download mode. Do not give up. Try it several times. If you can not make it, get a USB-JIG and try it out. You can buy it on the internet, but you can also do it yourself. For that you need quiet hands and a soldering iron.
bersem said:
That was a misstake !
<ID:0/014> Re-Partition operation failed.
This Tutorial @toy_story is great, so you cannot do wrong.
You have to come in download mode. Do not give up. Try it several times. If you can not make it, get a USB-JIG and try it out. You can buy it on the internet, but you can also do it yourself. For that you need quiet hands and a soldering iron.
Click to expand...
Click to collapse
Yea I know the re-partition was the part where things broke.
Can't enter download mode anymore.
I guess will have to try getting a USB Jig. The only hope left I think, unless somebody has some other suggestions..
Endless boot
EDIT: Never mind -- I fixed it by restoring to the stock ROM and PIT file then trying again. All works perfectly now!
-----------------------------------------------------------
I followed the instructions here, and everything seemed to work fine with no errors. But when I finally boot the phone into Lineage OS for the first time, the animated loading image appears but the phone never boots.
I waited over 2hrs yesterday. Today I restored the original PIT, wiped the phone and tried again. The phone has been "trying" to boot for an hour now, but the boot animation just keeps on going.
:crying:
FWIW, the phone already had Lineage OS on it, but I wanted to use this installation method as it seems to increase the partition used for installed apps.
I'm not sure what to try next or how to figure out what went wrong. Can anyone help?
Notifications LED
Hello,
After performing this install, the LED that lights up when charging and whent there's notifications does not work.
Instead, the touch buttons light up. I haven't seen any options in settings to change this.
Is there any app that where I can tweak these settings? Or is it something with the recovery/kernel?
Apart from that, it works good so far!
Thanks
EDIT:
Just realized galaxy s2 has no notification led, I was thinking of my other phone
--edited--
Sry, nvm..
@toy_story At point 5, or better at the beginning (what is needed for this procedure) you should add that you need a micro SD card on hand. Wasn't obvious for me, and I didn't have one....
Other thing, my GT-I9100 just hangs at the splash screen with the yellow exclamation sign now I must admit that I was a bit tired yesterday while I wanted to follow the instructions (connecting it to Odin and putting all files in the designated slots worked the first time, and it also booted into the CWM recovery, I did all wipes also)... After trying to figure out how to follow step 5 I stumbled through the CWM menue and activated some option by accident (kinda annoying way to navigate it I must admit), causing the phone to reboot. And now, I'm stuck with the above mentioned scheme. At least it turns off when I hold the power button longer, turning it back on will again produce the same scheme.
I connected it again to Odin and started over from point 1 but the problem retains. What can I do?
scragnothh said:
@toy_story What can I do?
Click to expand...
Click to collapse
Look here -
https://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
So I'm stuck at this blue screen in my Samsung Tab A 8.0 with the message: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
See what had happened was...
I was having problems with the battery and when I booted into recovery it said a message (can't remember it now) along the lines of: E: can't load bitmaps /poc0008 No such file or directory! & successfully verified DM-Verity hash & E: can't load /dev/block/(something) No such file or directory!
So here went I, Mrs. Pseudo-developer and I upgraded the firmware via Odin ver 3.13.1 Previously I think it was N7.0.1 and then it became N7.1.1. It was a much smoother experience and my battery didn't die as quick. Yay!
But there I had to go tinkering... Again, via Odin (which I'm comfortable with, btw. I have all my devices firmwares' backed-up. All my devices are rooted) tried to flash cf-autoroot and something happened, I couldn't read the argument and I booted into recovery and then into bootloader and started to reflash my firmware only for my usb to get unplugged in the midst of it. This sucks and does anybody has a tissue, because my tablet just died.
dilcia said:
So I'm stuck at this blue screen in my Samsung Tab A 8.0 with the message: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
See what had happened was...
I was having problems with the battery and when I booted into recovery it said a message (can't remember it now) along the lines of: E: can't load bitmaps /poc0008 No such file or directory! & successfully verified DM-Verity hash & E: can't load /dev/block/(something) No such file or directory!
So here went I, Mrs. Pseudo-developer and I upgraded the firmware via Odin ver 3.13.1 Previously I think it was N7.0.1 and then it became N7.1.1. It was a much smoother experience and my battery didn't die as quick. Yay!
But there I had to go tinkering... Again, via Odin (which I'm comfortable with, btw. I have all my devices firmwares' backed-up. All my devices are rooted) tried to flash cf-autoroot and something happened, I couldn't read the argument and I booted into recovery and then into bootloader and started to reflash my firmware only for my usb to get unplugged in the midst of it. This sucks and does anybody has a tissue, because my tablet just died.
Click to expand...
Click to collapse
Can you still go into recovery mode? Or the device was hard bricked? If the device is not booting you can try to patch boot.img
Hello, today I was trying to restart my phone after it was updating an app from the google play store for several hours and since then it gets stuck on the Samsung Galaxy Note 8 logo. My phone is rooted and has TWRP installed.
I still can enter TWRP recovery mode but literally everything I can do there fails. I get the "unable to mount storage" message whenever I try to wipe or format something and it is showing 0MB for all partitions.
I tried flashing the stock firmware using adb sideload but I am still just getting unable to mount storage/cache/data messages after a second. I also tried flashing the .zip file through USB OTG cable but got the same result.
When I tried flashing the file with JOdin3 (Odin for Linux) I got this message: "A corrupted file was detected. In order to continue, you must select a valid Odin File" (Still got this message after I redownloaded the file)
If anyone has any suggestions, please leave a comment.
Edit: Tried flashing with Heimdall and it somewhat worked but if I boot my phone now I get "fail to open recovery cause no such file or directory" error for a split second and then it reboots...
Please can anyone help me?