Need Help! No USB Cable. Stuck on boot screen - Samsung Epic 4G Touch

I tried to flash the ISC 1.4 theme over starburst 1.8, i wiped cache davlik and formated system then flashed the theme, went to reboot and its stuck on the galaxy s screen. I went back to recovery and im getting all kinds of errors. What can I do to fix this? I do not have a usb cable to fix it with odin because I just moved and lost my cable! I need help!
The error when i boot in recovery looks like this
E: failed to open /etc/recovery.fstab (no such file or directory)
e:unknown volume for path [/cache/recovery/command]
theres more but im in a rush right now

Can u restore a nand backup? You probably cause this by formatting system and then not flashing a rom. It wiped your system out.
Sent From My Evo Killer!!!

musclehead84 said:
Can u restore a nand backup? You probably cause this by formatting system and then not flashing a rom. It wiped your system out.
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
He won't be able to even restore a nand backup as is. I did this in error before myself. It can't even load the SD card when it gets wiped like that. You need odin and a USB cable. Sorry your out of luck until you get one.
Go to WorstBuy pick one up for $30, use it once then return it Then buy a replacement from monoprice for like $3.

haha sucks bro.. thats why i dont flash anything unless i have a pc to fix it when and if it messes up.. you did something wrong tho, like the other person said, formatted /system without flashing a rom so it has nothing to boot from.. put it in dl mode and flash a rom in odin borrow someones cable haha, there not hard to find.. lots of things use the same type cable..

Related

[Q] Always booting to Sys Recover (3e)

So I rooted with Odin using the "SPH-D710_Zedomax_Kernel.tar" and then unrooted with Odin using the "acs-eg30-stock-kernel-pulled.tar". Once I unrooted everytime I boot my phone up I get this error message:
'gaudi_bootimage.jpg' draw failed
and I boot into System Recovery (manual mode), and if my phone is plugged into laptop or wall charger when I power down I receive the following error message
'charging.jpg' draw failed
Even when I root back, it still always boots into recovery mode and boot up error message is replaced with the Galaxy S2 GT-I9100 splash screen, but I still get the 'charging.jpg' draw failed error.
On both occasions (root or unroot) I can still select reboot system now and the phone finally boots up fine, but I'm trying to eliminate the jpg boot and charge error messages and boot directly into he phone without having to select it in recovery. I have done a complete factory wipe with the same results as described above. Any suggestions?
try reflashing the stock pulled .tar file? and a nandroid backup/stock OS?
Looks like some files may be corrupt.
GH0 said:
try reflashing the stock pulled .tar file? and a nandroid backup/stock OS?
Looks like some files may be corrupt.
Click to expand...
Click to collapse
I have tried reflashing the stock pulled .tar file and resetting to factory defaults, neither of these worked. Are the files 'gaudi_bootimage.jpg' and 'charging.jpg' something I can place in a specific directory that will avoid this boot up into recovery problem? I'd like to overwrite those potential corrupt files with good ones.
They are in /mnt/.lfs
I'll see if I can pull them and post for you.
Oh wow!
There's a treasure trove of stuff in this directory. I think it's hidden but using Android Webkey I got to it. I'll post some other "boot" images from here. The initial "Samsung Galaxy S II" image isn't the only one. I like the Iron Droid one, though it doesn't seem complete.
Anyway, here's the .zip of all the images in that directory.
I saw you wiped fator reset. But dis you also wipe the cache and dalvik? Then do clean install with CWM 5.x.x.x ? I would recomend that id u haven't tried thus yet
eph5networks said:
So I rooted with Odin using the "SPH-D710_Zedomax_Kernel.tar" and then unrooted with Odin using the "acs-eg30-stock-kernel-pulled.tar". Once I unrooted everytime I boot my phone up I get this error message:
'gaudi_bootimage.jpg' draw failed
and I boot into System Recovery (manual mode), and if my phone is plugged into laptop or wall charger when I power down I receive the following error message
'charging.jpg' draw failed
Even when I root back, it still always boots into recovery mode and boot up error message is replaced with the Galaxy S2 GT-I9100 splash screen, but I still get the 'charging.jpg' draw failed error.
On both occasions (root or unroot) I can still select reboot system now and the phone finally boots up fine, but I'm trying to eliminate the jpg boot and charge error messages and boot directly into he phone without having to select it in recovery. I have done a complete factory wipe with the same results as described above. Any suggestions?
Click to expand...
Click to collapse
Hello, I got the same problem as you. I still don't know how to do it. please, Let me know if you know any way to fix it. Thanks
KCRic said:
They are in /mnt/.lfs
I'll see if I can pull them and post for you.
Oh wow!
There's a treasure trove of stuff in this directory. I think it's hidden but using Android Webkey I got to it. I'll post some other "boot" images from here. The initial "Samsung Galaxy S II" image isn't the only one. I like the Iron Droid one, though it doesn't seem complete.
Anyway, here's the .zip of all the images in that directory.
Click to expand...
Click to collapse
Alright a quick update (not positive):
I copied the files onto the /mnt folder, but unfortunately after I copy them they still don't appear in the directory. I reboot and I still receive the same 'gaudi_bootimage.jpg' draw failed & 'charging.jpg' draw failed. I do have root access by the way and I'm copying these to the directory using Root Explorer.
I also took the following steps:
Installed CWM 5.0.2.3
Performed a nanroid backup
formatted the system volume under 'mount and storage'
wiped data/factory reset
wiped cache partition
wiped dalvik cache
All that still with no success.
Another thing I'm noticing is when these error messages show (on boot & after power down while connected to charging source) it automatically boots into recovery. There has to be some way or place these files are being called for me to replace them to make this annoying issue go away. Any more suggestions?
So you have tried reinstalling CWM to see if it helps?
Seems (no expert here) that something is corrupted. Not sure exactly what but possibly part of the internal storage or the primary or secondary bootloader. I really hate to jump to something that extreme but i just don't see another reason it would be acting up like that.
I would download CWM one more time and check the MD5 before using ODIN to flash it. If it still does it - return to stock (remove the yellow triangle if you have it) and take it back to the store. Should be under warranty still.
Did you ever solve this problem as i have the same issue.
sscoleman said:
Did you ever solve this problem as i have the same issue.
Click to expand...
Click to collapse
Unfortunately none of these options resolved it. Still pending.
got d boot image running....
Hey i 1st got a stock samsung boot .zip file and den used sgs2 boot changer to apply d img it worked....!!!! Thank got for dat .... Still dont knw wat to do abt d charging. Jpg though... D app works for dis model too... Try it out....

[Q] DINC won't clear user data, after using every trick I know

So, I recently acquired an Incredible, the second one I've owned. The first one I rooted, turned S-off and installed CM7 with zero difficulties, after that I rooted/flashed my Xperia Play CDMA with all the issues that accompany that device. (after the ease with which I modded my first DINC, the hoops through which I had to jump to unlock my bootloader blew my mind)
This DINC, though, refuses to clear user data. Even after multiple wipes via CWM, and multiple updates using the PB31IMG method, user data remains. Attmepts to preform a factory reset via HBOOT result in a balck screen with a red triangle and exclamation point.
I tried to install MIUI, thinking maybe a fresh rom would fix it, but it gets stuck at the room splash screen.
I've even tried recovering a clean CM7 install from my old incredible, but it gets stuck in a bootloop at the rom splash, same story trying to flash the .zip in recovery.
I've seen a few threads that deal with a few of these symptoms, but not the issue as a whole
Thanks in advance for any answers you guys have!
Cheers
I found a solution, finally. Admittedly, it was a bit drastic, but it worked, nonetheless.
I ended up disassembling both DIncs and putting the motherboard of the working device (with the smashed screen) into the device that was unable to format /data.
It was a bit touch and go for a bit, but my new DIY refubished phone is up and running.
Thanks for the help guys!
What error do you get? Can you upload the logs from /cache/ recovery after trying to wipe?
Sent from my Galaxy Nexus using Tapatalk 2
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
mattdubuc said:
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
Click to expand...
Click to collapse
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
tiny4579 said:
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
The red triangle happens when you try to do a factory reset from hboot wile on cwm recovery. If you really need to do a factory reset, you will need to flash to the stock recovery first. http://dinc.does-it.net/Recoveries/Stock_4.08.605.15/PB31IMG.zip Then if it works or even if not flash back to cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.
The weird thing is, that even after flashing PBG31IMG via HBOOT I'm retaining all the previous user data. I've tried formatting the internal drive, using a few different versions of the image, even manual formatting of /data via CWM, which only gives me an error. the same error as when I tried to restore a nandroid from my functioning DINC.
tiny4579 said:
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
mattdubuc said:
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
Click to expand...
Click to collapse
That should be fine. Try to wipe data in cwm again just so it logs it.
Sent from my Galaxy Nexus using Tapatalk 2
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
zslashy said:
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
Click to expand...
Click to collapse
Same error if you flash stock GB sense and factory reset from recovery? You have the errors when booting and the apps are still there?
Sent from my Nexus 7 using Tapatalk 2
Thank you for reply, I solved reset issue by installing Amon Ra recovery. But the problem with apps still exists, it looks like system is restoring back up after reboot, I can do everything with system but after reboot it's like it was before with no changes made. Additionally, it seems that the problem is with emmc, just because when I delete EVERYTHING on it, after restart all files appear again!
I'm also getting an error when I try to manually format the data partition under >mounts and storage in CWM, I'm assuming that may be to blame for retained user data?
When I run show log after running only a manual /data format it displays:
6 black groups
32768 blocks per group. 32768 fragments per group
8112 inodes per group
superblock backups stored on blocks:
32768. 98304. 163840
The filesystem already has a journal,
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Failure while running mke2fs
Error formatting /data!
mtd: succesfully wrote block at 0
I:Set boot command ""
I have no idea what that means really, or even if it's pertinent.
I had to remove the user info (owner data, phone number, etc) from my inc after canceling my contract with verizon. After about 25 different attempts to wipe it, I finally found something that worked (at least for me)
Tried running the RUU, could not reboot into HBOOT (version error)
Tried the RUU again, this time starting it after manually booting the phone to HBOOT. Got a little farther than before, but still errored out. Did not work. Disconnected phone, pulled battery, rebooted to HBOOT.
Factory reset in HBOOT got me stuck on the stock recovery screen. Battery pulled, could not boot.
Flashed CWM in HBOOT (by renaming to PB31IMG.zip), was able to get into CWM recovery.
Tried to flash the 2nd GB OTA in CWM, did not take. Every option I clicked in CWM gave me about 7 errors after sitting on the logo for a moment. Battery pull, reboot. Boots into CM9. >.<
Booted to my rom, saw about 300 force closes. Tried to reflash CWM from Rom Manager, got a bunch of force closes. Updated Rom Manager from market, reflashed CWM, and this time it worked.
Rebooted to CWM, wipe data/cache/dalvik, reboot.
This time I booted in CM9, but to the initial ICS set up (click next to begin, wireframe pic of Andy)
After skipping thru initial setup, I checked Settings>About Phone>Status. My phone number was removed, network is Unknown, and all my data was removed. Activation prompt appears on each boot.
Not sure if this will help, but worth a try. I think that the HBOOT factory reset is what cleared my data, and then I just needed to fix CWM so I could get back to a working ROM.
Yeah that's what I did in june except I just got service on mine but I would think that would help getting your data out forever. If that does not work I wouldn't know what to tell u besides grab a magnet. Lol
Sent from my Droid Incredible using xda premium

cwm & twrp headaches again... pls help

Using cwm 6.0.3.1
trouble with /cache and /efs (.android_secure?)
if I attempt a full restore including all partitions, i get
md5sums
restore boot ok
restore system ok
restore data ok
restore .android_secure .... .... .... ... til reboot
get bootscreen but no boot!
can't flash rom
can't flash recovery
....... .... .......... ........ look like they're gonna work but hang til reboot
wipe cache ... never works ... ..... hang til reboot
wipe dalvik works
fix permissions works
infamous cache-wipe .... hang til reboot
infamous super-wipe.ext4 ....hang til reboot
wipe data & factory reset formatting /data ... formatting /cache... hang til reboot
wipe dalvik ...Dalvick cache wiped.
fixing permissions .... Done!
+*** go back ***+ ... hang til reboot
advanced restore from external_sd
checking md5sums...
erasing boot before restore...
restoring boot image ... hang til reboot
restore from external_sd
checking md5 sums...
erasing boot before restore...
restoring boot image...
restoring system...
...apps being restored....
restoring data...
...data & libs being restored... libredlaser.so
restoring .android_secure....
<automatic reboot>
...
<animated boot screen appears>
... hangs while bootscreen ani continues indefinitely...
leave 15 mins... boot ani .... need to force reboot
attempts to flash twrp 2.4.4.0 zip and other cwm's touch & non-touch lead to ...hang til reboot.
can individually mount, format, and unmount partitions except for /cache (...hang til reboot)
NOTE: my usb is borked. have sdk and hence adb - not sure if i can connect wirelessly to cwm6.0.3.1?
looking for any solution - to boot up to something other than recovery and go from there.
mobiusheron said:
Using cwm 6.0.3.1
trouble with /cache and /efs (.android_secure?)
if I attempt a full restore including all partitions, i get
md5sums
restore boot ok
restore system ok
restore data ok
restore .android_secure .... .... .... ... til reboot
get bootscreen but no boot!
can't flash rom
can't flash recovery
....... .... .......... ........ look like they're gonna work but hang til reboot
wipe cache ... never works ... ..... hang til reboot
wipe dalvik works
fix permissions works
infamous cache-wipe .... hang til reboot
infamous super-wipe.ext4 ....hang til reboot
wipe data & factory reset formatting /data ... formatting /cache... hang til reboot
wipe dalvik ...Dalvick cache wiped.
fixing permissions .... Done!
+*** go back ***+ ... hang til reboot
advanced restore from external_sd
checking md5sums...
erasing boot before restore...
restoring boot image ... hang til reboot
restore from external_sd
checking md5 sums...
erasing boot before restore...
restoring boot image...
restoring system...
...apps being restored....
restoring data...
...data & libs being restored... libredlaser.so
restoring .android_secure....
<automatic reboot>
...
<animated boot screen appears>
... hangs while bootscreen ani continues indefinitely...
leave 15 mins... boot ani .... need to force reboot
attempts to flash twrp 2.4.4.0 zip and other cwm's touch & non-touch lead to ...hang til reboot.
can individually mount, format, and unmount partitions except for /cache (...hang til reboot)
NOTE: my usb is borked. have sdk and hence adb - not sure if i can connect wirelessly to cwm6.0.3.1?
looking for any solution - to boot up to something other than recovery and go from there.
Click to expand...
Click to collapse
My friend had this issue with his S2, I just told him to buy the USB Port/Flex Cable from ebay or eTradSupply, then I replaced it, flashed to stock with Odin, the TWRP and finally updated his phone to UVMC6
SereneEnigma said:
My friend had this issue with his S2, I just told him to buy the USB Port/Flex Cable from ebay or eTradSupply, then I replaced it, flashed to stock with Odin, the TWRP and finally updated his phone to UVMC6
Click to expand...
Click to collapse
Nice thinking! Unfortunately, the sgh-t989 does not feature a port/flex cable. The microusb connector is soldered directly to the MLB.
mobiusheron said:
Nice thinking! Unfortunately, the sgh-t989 does not feature a port/flex cable. The microusb connector is soldered directly to the MLB.
Click to expand...
Click to collapse
What do you mean by that statement? Unless you have the international version, S2 should be the same as sgh-t989....
clikonco said:
What do you mean by that statement? Unless you have the international version, S2 should be the same as sgh-t989....
Click to expand...
Click to collapse
Suspect enigma was referring to a friend with an int'l s2. Regardless, the microusb connector is connected to a t989 main logic board in my stock t989d. ==> t989/t989d needs to have microusb connector desoldered and a new one soldered in place if it it to be replaced. The microusb connector is part of the main logic board ass'y and not a flex connected subass'y.
mobiusheron said:
Using cwm 6.0.3.1
trouble with /cache and /efs (.android_secure?)
if I attempt a full restore including all partitions, i get
md5sums
restore boot ok
restore system ok
restore data ok
restore .android_secure .... .... .... ... til reboot
get bootscreen but no boot!
can't flash rom
can't flash recovery
....... .... .......... ........ look like they're gonna work but hang til reboot
wipe cache ... never works ... ..... hang til reboot
wipe dalvik works
fix permissions works
infamous cache-wipe .... hang til reboot
infamous super-wipe.ext4 ....hang til reboot
wipe data & factory reset formatting /data ... formatting /cache... hang til reboot
wipe dalvik ...Dalvick cache wiped.
fixing permissions .... Done!
+*** go back ***+ ... hang til reboot
advanced restore from external_sd
checking md5sums...
erasing boot before restore...
restoring boot image ... hang til reboot
restore from external_sd
checking md5 sums...
erasing boot before restore...
restoring boot image...
restoring system...
...apps being restored....
restoring data...
...data & libs being restored... libredlaser.so
restoring .android_secure....
<automatic reboot>
...
<animated boot screen appears>
... hangs while bootscreen ani continues indefinitely...
leave 15 mins... boot ani .... need to force reboot
attempts to flash twrp 2.4.4.0 zip and other cwm's touch & non-touch lead to ...hang til reboot.
can individually mount, format, and unmount partitions except for /cache (...hang til reboot)
NOTE: my usb is borked. have sdk and hence adb - not sure if i can connect wirelessly to cwm6.0.3.1?
looking for any solution - to boot up to something other than recovery and go from there.
Click to expand...
Click to collapse
What rom are you trying to install, and what rom are you trying to restore?
Also when you try to flash a new recovery are doing a full reboot or just rebooting the recovery?
mobiusheron said:
Suspect enigma was referring to a friend with an int'l s2. Regardless, the microusb connector is connected to a t989 main logic board in my stock t989d. ==> t989/t989d needs to have microusb connector desoldered and a new one soldered in place if it it to be replaced. The microusb connector is part of the main logic board ass'y and not a flex connected subass'y.
Click to expand...
Click to collapse
oh 0.0 difficulty level just increased! You would think they would designed the same :/
Octane70 said:
What rom are you trying to install, and what rom are you trying to restore?
Also when you try to flash a new recovery are doing a full reboot or just rebooting the recovery?
Click to expand...
Click to collapse
would be happy to restore any working rom at this point. if i could simply reboot into twrp 2.5 it would be a huge improvement over cwm 6.0.3.1 >> at least then I could access my twrp backups.
as it is now, i can create an md5 checked complete backup (of a borked system) and restore from md5 checked backups. for some reason I am not able to "run" flashable zips; just restore (or advanced restore) backups from external_sd .... this seems to have the ability to restore some of the partitions needed ... i.e.,
/boot
/system
/data
/cache
/.android_secure
haven't seen any /preload as of yet. maybe all that's missing? all partitions need md5 sums though
have you tried mobile odin to flash a recovery,kernel,rom
Plz flash new recovery with odin.
Download cwm lastest version here
http://forum.xda-developers.com/showthread.php?p=40441169
I still using ok.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
skinsfanbdh said:
have you tried mobile odin to flash a recovery,kernel,rom
Click to expand...
Click to collapse
mobile odin does not work for the hercules
update: cwm 6.0.3.1 advanced restore & mobile odin & microusb
No usb
Local solder wizard balked. I unsoldered and removed the microusb connector. Don't have another to upside down type connector handy.
____________
No way to install apps
Though I cannot run a terminal or any program, {because installing a zip fails everytime}:
backup with md5 sums works
restore with md5 sums works
backup & restore to external_sd works
So if somebody can send me a complete, rooted, cwm 6+, or nandroid of any working t989 hercules rom, I should be able to copy it and restore a complete working system.
Before I forget, need to find out if there is a partition that needs to be excluded from backup and or restore. Seem to remember that one partition contains unique, sensitive phone, vendor, and service_provider info. Will edit when I can locate the specifics, (unless someone has that info handy; knows how to protect their privacy; and wants to pm or post their hercules backup)
_____________
without a working sytem, how do you run mobile odin?
mobile odin sounds great as would any working terminal. Have got the apk. now what? Only thing seems to work on my cwm 6.0.3.1 screen is backup or recovery. (mounting and formatting partions also works)
Is it available as a cwm6+ backup archive that can be restored into a system running mobile odin?

Absolutely Perplexed...

I currently have a T-Mobile Galaxy S2 with CM10.1.
I flashed my phone to the STOCK ROM recently, and flashed the UVLE1 radio along with it. However, after I flashed it with CWM, my phone went into a boot loop.
I decided to flash back to CM10.1 but it freezes every time it reaches the cache. I also tried to DARKSIDE SUPERWIPE everything, but it freezes at the cache as well. I think my cache partition is corrupted, but I have no idea as to how I can fix it...
I tried to purchase a USB Jig in order to reflash the phone with ODIN. I can get into Downloading mode, but neither ODIN nor Kies can recognize my computer. I just don't know what to do now.
I hope someone can help me.
Thanks!
FosuBoy said:
I currently have a T-Mobile Galaxy S2 with CM10.1.
I flashed my phone to the STOCK ROM recently, and flashed the UVLE1 radio along with it. However, after I flashed it with CWM, my phone went into a boot loop.
I decided to flash back to CM10.1 but it freezes every time it reaches the cache. I also tried to DARKSIDE SUPERWIPE everything, but it freezes at the cache as well. I think my cache partition is corrupted, but I have no idea as to how I can fix it...
I tried to purchase a USB Jig in order to reflash the phone with ODIN. I can get into Downloading mode, but neither ODIN nor Kies can recognize my computer. I just don't know what to do now.
I hope someone can help me.
Thanks!
Click to expand...
Click to collapse
Have you installed your phone drivers on your computer? Did you try to fix permissions or format system then flash back CM10.1 and proper radio / gapps?
jonmassot said:
Have you installed your phone drivers on your computer? Did you try to fix permissions or format system then flash back CM10.1 and proper radio / gapps?
Click to expand...
Click to collapse
Yes, I've installed the phone drivers. I've also tried to fix permissions. I've formatted the system and data many times with Darkside's Superwipe, but it always freezes at the cache. I've even tried to flash to CM10.1. No avail. It just places CM10.1 on a bootloop.
Bump.... I am desperate to fix this...
I also noted that every time I go on recovery, I see this.
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
Every now and then it posts an error saying that it can't mount the sd-ext itself, but i am able to access it just fine.
FosuBoy said:
Bump.... I am desperate to fix this...
I also noted that every time I go on recovery, I see this.
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
Every now and then it posts an error saying that it can't mount the sd-ext itself, but i am able to access it just fine.
Click to expand...
Click to collapse
Have you tried plugin it to another computer? I remember when my computer crashed while I was doing a ODIN install, after reboot, my computer didn't recognized my smartphone... Might help!
---------- Post added at 09:17 AM ---------- Previous post was at 08:53 AM ----------
FosuBoy said:
Bump.... I am desperate to fix this...
I also noted that every time I go on recovery, I see this.
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
Every now and then it posts an error saying that it can't mount the sd-ext itself, but i am able to access it just fine.
Click to expand...
Click to collapse
Also, did you try to completly erase your internal sd card and completly reinstall everything? And if I'm not wrong, with CM10.1, latest, you don't need to use darkside cachewipe...
jonmassot said:
Have you tried plugin it to another computer? I remember when my computer crashed while I was doing a ODIN install, after reboot, my computer didn't recognized my smartphone... Might help!
---------- Post added at 09:17 AM ---------- Previous post was at 08:53 AM ----------
Also, did you try to completly erase your internal sd card and completly reinstall everything? And if I'm not wrong, with CM10.1, latest, you don't need to use darkside cachewipe...
Click to expand...
Click to collapse
I'll try and plug it into another computer. But how exactly do I go about erasing my internal sd card?
Plug in your phone to your computer and open up kies. Select "emergency firmware recovery", Kies will probably say it can't detect your phone and ask you to enter serial number. Enter serial number from under the battery.
Don't use dark side wipe unless you know for sure that it is required!! Otherwise it can mess up your phone.
Sent from my Nexus 7 using xda app-developers app
gc84245 said:
Plug in your phone to your computer and open up kies. Select "emergency firmware recovery", Kies will probably say it can't detect your phone and ask you to enter serial number. Enter serial number from under the battery.
Don't use dark side wipe unless you know for sure that it is required!! Otherwise it can mess up your phone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Kies doesn't ask for my serial number... just a recovery code. Is it possible for me to mount my storage to the PC through the CWM? Every time I try to do that, it doesn't work at all either.
------------
UPDATE! I found where to put my serial number!
Will keep you posted...
gc84245 said:
Plug in your phone to your computer and open up kies. Select "emergency firmware recovery", Kies will probably say it can't detect your phone and ask you to enter serial number. Enter serial number from under the battery.
Don't use dark side wipe unless you know for sure that it is required!! Otherwise it can mess up your phone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It tells me that the "SGH-T989" does not support 'initialising.' I'm devastated.
That's too bad it didn't work. Something similar happened to me. I remember kies couldn't recognize my phone either and asked me to input serial number... That was a while ago though, so I cant remember all of the details. I still think kies is your best bet, it took a while to work for me too.
Sent from my Nexus 7 using xda app-developers app
I think the problem here is that my computers cannot recognize the phone, no matter what. I think some part of the phone is corrupted to the point where it does not even want to boot a ROM. I've attempted to narrow the corruption down to the cache partition.
Is there anyway I can re-format the cache without using a PC? CWM Recovery cannot access the cache without freezing. Is there a ZIP file I can download that can format everything?
Better yet, is there a ROM that I can flash that will re-flash the cache as well? I tried re-flashing CM10.1 and nothing happens. Even restoring different nandroids makes the CWM Recovery freeze at the cache!
I've also wiped the Dalvik cache countless times, no avail. Will a TWRP recovery work? I have no idea what it is.
FosuBoy said:
I'll try and plug it into another computer. But how exactly do I go about erasing my internal sd card?
Click to expand...
Click to collapse
With TWRP, you can just erase everything in tools or advanced, can't remember wich one, but I don't know about CMW.
Try re-installing all you drivers, meaning uninstall, reboot, re-install and see if your computer recognize it again.
Never use Darkside Superwipe with CWM 6.x.x.x, you get a bootloop.
I just reinstalled the drivers on my computer and followed the right protocol. Nothing. To set things straight, I've probably used every method possible to fix this thing. Nandroid Recovery, ROM Flashing, and Kies have all been fruitless attempts to get this thing to work.
------------------------------
nivekx9 said:
Never use Darkside Superwipe with CWM 6.x.x.x, you get a bootloop.
Click to expand...
Click to collapse
Ugh, I know this. I have CWM 5.x.x.x.
FosuBoy said:
I just reinstalled the drivers on my computer and followed the right protocol. Nothing. To set things straight, I've probably used every method possible to fix this thing. Nandroid Recovery, ROM Flashing, and Kies have all been fruitless attempts to get this thing to work.
------------------------------
Ugh, I know this. I have CWM 5.x.x.x.
Click to expand...
Click to collapse
The only thing left, is to try it on another computer, worked for me.
FosuBoy said:
I just reinstalled the drivers on my computer and followed the right protocol. Nothing. To set things straight, I've probably used every method possible to fix this thing. Nandroid Recovery, ROM Flashing, and Kies have all been fruitless attempts to get this thing to work.
.
Click to expand...
Click to collapse
Odin back to stock.
Edit: sorry just reread your OP and Odin isn't working. Try flashing TWRP and see if it helps at all.
I'll get you the link.
Update! My computer seems to recognize the device, but it says that the 'device is malfunctioned' and lists it as an unknown device. However, I know where the Samsung USB drivers are located. Could I just manually install a driver onto the 'unknown device?'
I'll try and get a picture of the drivers because it seems like there is more than one that I can install...
TWRP 2.5.0.0
I've flashed the TWRP.. now it freezes on the teamwin logo. 5 steps backwards now.. I can't access the ROM nor do I have a way to recover any files.
FosuBoy said:
I've flashed the TWRP.. now it freezes on the teamwin logo. 5 steps backwards now.. I can't access the ROM nor do I have a way to recover any files.
Click to expand...
Click to collapse
It sounds like you have a NAND problem. I am searching Google but haven't found anything helpful yet. Have you tried using Odin on all the different USB ports? Or like someone else said, another computer?

[Q] How to unbrick the note2 (n7100) ?

Guys my english is not that good so if you dont understand something tell me.
my friend gave me his phone becouse i had to fix it for him. i thought it was an usual brick, but when i try to flash the rom with odin it fails on the nand writing. when i get in to recovery mode i see that the device doesnt mount the system file (cache, efs etc...). I tried a nand erase + repartition but odin fails them too. i dont think that the nand is broken, just something doesnt allow me to access
what should i do?
Try this
Have u tried mounting external usb stick with otg cable? what version of odin re u using?
Alternatively try installing custom recovery like philz and then try flashing a rom.
let me know if that helps.
Hey, i have the same problem.
i took my phone out of my pocket and it was turned off. I tried to boot it but it got stuck at Galaxy Note II logo.
When i opened recovery (i use teamwin) , it shows in the log similar error messages to yours. It won't mount any of the partitions. I also tried repartition with odin, but it fails too.
I think the internal storage (the emmc) is broken in our phones and we can't really do anything about it. But i'm not sure.

Categories

Resources