My Wifi tab is stuck on the Samsung Galaxy Tab 8.9 Screen. I used odin to flash back to factory rom. Osin said pass and rebooted but still stuck on Samsung galaxy tab 8.9 screen. What do I need to do next? In recovery mode it says: E: failed to mount /system (invalid argument) E: install_application_for_customer:Can't mount. /system copy application failed.
--Appling Multi-CSC...
E: failed to mount /system (invalad argumenrt)
E: install_application_for_customer:Can't mount. /system
E: multi_csc:Can't mount/system
Did you format system? Try loading another ROM, seems to me your tablet is without any rom now.
cdc120 said:
My Wifi tab is stuck on the Samsung Galaxy Tab 8.9 Screen. I used odin to flash back to factory rom. Osin said pass and rebooted but still stuck on Samsung galaxy tab 8.9 screen. What do I need to do next? In recovery mode it says: E: failed to mount /system (invalid argument) E: install_application_for_customer:Can't mount. /system copy application failed.
--Appling Multi-CSC...
E: failed to mount /system (invalad argumenrt)
E: install_application_for_customer:Can't mount. /system
E: multi_csc:Can't mount/system
Click to expand...
Click to collapse
If you're using the clockworkmod, try to flash with Odin the stock recovery and the format your device from there, i was having serious problems with clockwork =/
Also managed to brick the GT7300
Hell_LordBR said:
If you're using the clockworkmod, try to flash with Odin the stock recovery and the format your device from there, i was having serious problems with clockwork =/
Click to expand...
Click to collapse
I can't even get into either recovery or download mode! Neither does the 'charging' screen shows when hooking up to power.
I first installed CWM 6.0.1.2 which went fine. Then I installed a new ROM and immediately GAPPS. That last install hung at approx 80% according the progress bar. After a while (more than 5min) I pressed the power button to shut the device down. Now it wont boot at all, not even into any download or recovery mode.
Any ideas?
I might have completely ruined my galaxy p7300 !
efoppen said:
I can't even get into either recovery or download mode! Neither does the 'charging' screen shows when hooking up to power.
I first installed CWM 6.0.1.2 which went fine. Then I installed a new ROM and immediately GAPPS. That last install hung at approx 80% according the progress bar. After a while (more than 5min) I pressed the power button to shut the device down. Now it wont boot at all, not even into any download or recovery mode.
Any ideas?
Click to expand...
Click to collapse
I have the exact same problem! I installed CWM 6.0.1.2. I started installed a new ROM...it couldn't see any program so I hit the power button...Now it is not starting into recovery mode...completely dark!!!
Did you figure out how to sort this?
salimb said:
I have the exact same problem! I installed CWM 6.0.1.2. I started installed a new ROM...it couldn't see any program so I hit the power button...Now it is not starting into recovery mode...completely dark!!!
Did you figure out how to sort this?
Click to expand...
Click to collapse
Same issue here, it wont do anything, screen stays black, tried Power + Vol Down, also Power + Vol Up. Nothing.
My PC is seeing it as APX, which was a broken driver, after some searching I came across NVIDIA USB Boot-recovery driver for mobile devices which my PC now recognises it as.
But it's still not doing anything.
Hi
I had the same. Did a wipe cache and factory reset and everything worked fine again.
Go to this by pressing power and volume up
Verstuurd van mijn GT-I9300 met Tapatalk
jeroenraij said:
Hi
I had the same. Did a wipe cache and factory reset and everything worked fine again.
Go to this by pressing power and volume up
Verstuurd van mijn GT-I9300 met Tapatalk
Click to expand...
Click to collapse
Pressing power & volume up doesn't do anything...the tablet stays black. I am in the same shoes as WodgeFW and others on this forum!
Guys, it seems we're doomed!
See this instruction for hard reset and empty cache
http://m.youtube.com/watch?v=iHNs43oRuo4
Verstuurd van mijn GT-I9300 met Tapatalk
efoppen said:
I can't even get into either recovery or download mode! Neither does the 'charging' screen shows when hooking up to power.
I first installed CWM 6.0.1.2 which went fine. Then I installed a new ROM and immediately GAPPS. That last install hung at approx 80% according the progress bar. After a while (more than 5min) I pressed the power button to shut the device down. Now it wont boot at all, not even into any download or recovery mode.
Any ideas?
Click to expand...
Click to collapse
Same for me. also after flashing CWM 6.0.1.2 and CM9 with ICS kernel. Flash was ok, but boot never ended. So i hit the power button.
Now only apx mode and bootloader seems to be locked - can't use nvflash. Also tried to drain battery - but that doesn't help.
Same problem here, after update of clockworkmod recovery to 6.0 my rom installation froze and i pressed the power button after 15 min.
Now all is black, Considering taking a chance with a warranty claim but unsure if it will accepted.
If anyone finds a solution to this it would make my day, if not then i guess its lesson learned.
grape_tonic said:
Same problem here, after update of clockworkmod recovery to 6.0 my rom installation froze and i pressed the power button after 15 min.
Now all is black, Considering taking a chance with a warranty claim but unsure if it will accepted.
If anyone finds a solution to this it would make my day, if not then i guess its lesson learned.
Click to expand...
Click to collapse
Run odin on your pc hold volume up and power check if odin reads the tablet it will show com 1-20 depends on port if so you can recover. Even if your screen is blank give it a go.its worth a try.
Thanks for the suggestion but no luck.
Am currently trying to drain battery by power cycling with constantly pressed power button. After checking other threads with similar issues it seems. To be related to a certain version of CWM. Hopefully a total drain of battery will solve my problem.
Sent from my HTC Vision using xda app-developers app
grape_tonic said:
Thanks for the suggestion but no luck.
Am currently trying to drain battery by power cycling with constantly pressed power button. After checking other threads with similar issues it seems. To be related to a certain version of CWM. Hopefully a total drain of battery will solve my problem.
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Hi, could you tell us what kernel/ROM did you use before brick your tab? Also what CWM version did you use? From what I have read, it has to have both bad kernel and CWM in combination to cause this. Thanks
nexus_g said:
Hi, could you tell us what kernel/ROM did you use before brick your tab? Also what CWM version did you use? From what I have read, it has to have both bad kernel and CWM in combination to cause this. Thanks
Click to expand...
Click to collapse
I have same problem, now i wait full drain of battery. Tab 8.9 32gb-3g. cwm version 6.0.1.2, firmware cm9-2012-09-03-experimental with A1-V1.6.2 kernel. That was nice combination - but google maps reboot my tab. i go to recovery, wipe all(data+cache+dalvik) and try to install latest cm9-nightly. when progress bar was at 60-70% tab freeze. after 10 minutes i press power button for reboot and get black screen, like topic-starter. Maybe that will be helpfull
nexus_g said:
Hi, could you tell us what kernel/ROM did you use before brick your tab? Also what CWM version did you use? From what I have read, it has to have both bad kernel and CWM in combination to cause this. Thanks
Click to expand...
Click to collapse
It's a little more subtle than that. There are essentially 2 kernels on the system: 1 in the recovery image (e.g. CWM) and 1 in the boot image (what is usually called 'the kernel'). Either one of these could cause the problem if it doesn't use the right calls (or, conversely, uses the wrong calls) into the eMMC driver. Since most of us use the recovery to do wipes & resets that is the one most likely to cause the problem. However, it has also been known to be caused by doing factory resets and wipes via the ROM (which uses the boot image kernel).
So, for this to happen you could have: a safe recovery and a bad boot; a bad recovery and a safe boot; or have both be bad.
As has been mentioned, the last 'safe' CWM appears to be 6.0.0.8.
Since the various threads indicate that Samsung is aware of this I'd assume the Stock recovery and boot images use a kernel that is 'safe'. That may be a bad assumption, but it only seems to be the use of non-Stock components that causes this, at least from what I've read so far.
Somewhere along the line a kernel that didn't have this defensive code in it made it into the source trees and then into our lives.
Thanks for explaining that so clearly.
Did anybody using other than cwm 6.0.1.2 and got brick too? Just wondering if other cwm version has problem with ICS kernel. Because apparently we suddenly have many deadbrick tabs appearing after we get the ICS kernel for our tab. Thanks
---------- Post added at 03:22 AM ---------- Previous post was at 03:14 AM ----------
boscorama said:
It's a little more subtle than that. There are essentially 2 kernels on the system: 1 in the recovery image (e.g. CWM) and 1 in the boot image (what is usually called 'the kernel'). Either one of these could cause the problem if it doesn't use the right calls (or, conversely, uses the wrong calls) into the eMMC driver. Since most of us use the recovery to do wipes & resets that is the one most likely to cause the problem. However, it has also been known to be caused by doing factory resets and wipes via the ROM (which uses the boot image kernel).
So, for this to happen you could have: a safe recovery and a bad boot; a bad recovery and a safe boot; or have both be bad.
As has been mentioned, the last 'safe' CWM appears to be 6.0.0.8.
Since the various threads indicate that Samsung is aware of this I'd assume the Stock recovery and boot images use a kernel that is 'safe'. That may be a bad assumption, but it only seems to be the use of non-Stock components that causes this, at least from what I've read so far.
Somewhere along the line a kernel that didn't have this defensive code in it made it into the source trees and then into our lives
.
Click to expand...
Click to collapse
persoot recommend using cwm 6.0.1.1 on his website http://droidbasement.com. wondering this cwm is safe also? Have someone used this version before?
nexus_g said:
persoot recommend using cwm 6.0.1.1 on his website http://droidbasement.com. wondering this cwm is safe also? Have someone used this version before?
Click to expand...
Click to collapse
I think that only exists for the 10.1, and was not released for the 8.9...
cdc120 said:
My Wifi tab is stuck on the Samsung Galaxy Tab 8.9 Screen. I used odin to flash back to factory rom. Osin said pass and rebooted but still stuck on Samsung galaxy tab 8.9 screen. What do I need to do next? In recovery mode it says: E: failed to mount /system (invalid argument) E: install_application_for_customer:Can't mount. /system copy application failed.
--Appling Multi-CSC...
E: failed to mount /system (invalad argumenrt)
E: install_application_for_customer:Can't mount. /system
E: multi_csc:Can't mount/system
Click to expand...
Click to collapse
Can you get it to download mode by pressing start+volume down buttons simultaneously and flash original HC ROM and start from there? I believe yours is not caused by the brickbug. If you have brick bug your tab will have black screen (someone correct me if I am wrong about this).
Related
Hello everyone,
I've been having a really bad time with my Spring GTab in the last few days... to keep it simple:
1. Had a stock GTab that was showing problems, most of the applications were crashing (force closed), but it was still usable after a reboot. On one of those reboots it did not came up any more and got stuck at the Samsung logo.
2. After researching on the forums, tried to install 2.3.3 following this procedure:
http://androidadvices.com/how-to-update-samsung-galaxy-tab-to-stable-gingerbread-2-3-3-firmware/
Odin successfully installed the ROM, got to recovery mode and tried to factory/clear cache. Showed errors... Stuck at Samsung logo again.
3. Tried to install the stock sprint EA24 following these steps:
http://forum.xda-developers.com/showthread.php?t=1009926
No matter what I do, Odin stops at recovery.bin and fails.
4. Following the suggestions there I then installed nomodem EJ30 successfully, but again got stuck at samsung logo. Tried to install the EA24 from there with no luck, still failing at recovery.bin.
So as of now, I am at the same point as at the beginning, stuck at the Samsung logo...
Guys this is driving me crazy... any help will be highly appreciated!!!!!!
Try to enter recovery and wipe everything.
aibo said:
Try to enter recovery and wipe everything.
Click to expand...
Click to collapse
Thanks for the reply, already did.... same results... something that I'm seeing in recovery is:
E:Can't mount /dev/block/mmcblk0p1
Not sure if that's the problem....
Do a little search(there's a search botton) on this forum it's a common problem, already answered if I remember correctly. Hope it helps.
aibo said:
Do a little search(there's a search botton) on this forum it's a common problem, already answered if I remember correctly. Hope it helps.
Click to expand...
Click to collapse
As I mentioned above... already did, followed the instructions of every post I found... still at samsung logo...
http://forum.xda-developers.com/sho...ght=E:Can't+mount+/dev/block/mmcblk0p1&page=2
Did you try this ? The first boot always takes a little longer, be sure to let it boot long enough.
I already answer this in other treat. Anyway, i answer it again.
"you can always go back to the right path each time you lost your way"
lol
My meaning, flash back to stock rom that originally come with your tab and see how its going on.
Sent from my GT-P1000 using XDA App
naimmkassim said:
I already answer this in other treat. Anyway, i answer it again.
"you can always go back to the right path each time you lost your way"
lol
My meaning, flash back to stock rom that originally come with your tab and see how its going on.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Hi, I tried SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar, which is the stock rom, it loaded correcty using Heimdall, but removing the modem, but it is still stuck at the samsung logo, I left it on during all the night yesterday but it did not loaded...
I am seeing the following errors in the recovery mode:
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
Not sure if this is the problem... what do you think?
Can I load any of these firmwares? I want to test but trying to avoid making the problem bigger...
P1000LVJJJ3
P1000LVJJM9
P1000NUBJM2
This is my first post, go easy on me! I own a few Android devices, all rooted, and flashed over probably hundreds of times. I know all the risks associated with it, and I take full responsibility for anything that happens to my devices. I've never had any problems in the past getting around recovery and dealing with custom ROMS...nothing that can't be fixed anyway (boot loops, force closes, ect...).
I've never seen so many problems with recovery than I have with the Galaxy Note, however. I mean, if you can't depend on a recovery to work, what are you to depend on? I had a bit of a panic flashing some of the ICS leaks, but all was resolved. No biggie. Everything was running smoothly, and somehow my recovery became fully operational again. I was able to mount /system...and was fully able to flash from CWM again, as opposed to Redpill.
Okay, long winded I know...but here I am. I just flashed angelom's newest kernel with touch recovery. "Cool" I thought. Couldn't hurt. So I went in to do a wipe of /cache and it hung up. No biggie again. I held down the magic three buttons, and when I rebooted back into recovery, I get this....over and over again.
"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
No files found."
I've tried flashing Redpill again and installing, restoring stock back up, powering down and taking my battery out for a while...bashing my head on the wall. No matter what I do, it doesn't get past the Samsung logo. It was hanging up on booting before, but now it won't even go that far. Do I venture down the path of Odin (which I still am not entirely sure how to use)...or do I have a full brick on my hands? Looks like I might have fried the internal storage. If that's the case, I'm ****ed...simply put.
Anyway, ANY help would be greatly appreciated. Hopefully someone else has run into a similar problem and has a fix...no matter how complicated. Thank you for your time!
Try getting into Download mode (Volume down + Home + Power). If you can do this, then just flash any of the older stock Roms with PC Odin - these are easily rootable using zergrush method - and keep on flashing.
chasmodo said:
Try getting into Download mode (Volume down + Home + Power). If you can do this, then just flash any of the older stock Roms with PC Odin - these are easily rootable using zergrush method - and keep on flashing.
Click to expand...
Click to collapse
I can do that! I was always skeptical of ODIN, but it might be a life saver now.
Okay, so I get the little green Android guy and it says "Downloading...Do not turn off target!" So then I download PC Odin, connect USB cable and flash away? Sounds simple enough. I'd really hate to think I have a 700 dollar paperweight. I'll do some homework first. Thank you, by the way!
smalmagal said:
Okay, so I get the little green Android guy and it says "Downloading...Do not turn off target!" So then I download PC Odin, connect USB cable and flash away? Sounds simple enough. I'd really hate to think I have a 700 dollar paperweight. I'll do some homework first. Thank you, by the way!
Click to expand...
Click to collapse
Yes. Go here, download N7000XXKK9 stock Rom and flash it with PC Odin.
Then go here, and root it using Method 2: Root + CWM recovery.
I use Linux, so I'll have to wait to use my friends Windows PC. Installing a virtual box is more trouble than anything. This is how I rooted my device the first time. They don't make things simple for us Linux users! Anyway, I'll let you know how it goes tomorrow. Thanks again!
chasmodo said:
Yes. Go here, download N7000XXKK9 stock Rom and flash it with PC Odin.
Then go here, and root it using Method 2: Root + CWM recovery.
Click to expand...
Click to collapse
Edited: Sometimes after flashing stock Rom you get into bootloop when Odin restarts the phone. Don't panic if this happens. Pull out your battery, wait a bit, put it back, boot into stock Recovery (Volume up + Home + Power), and do factory reset and cache wipe. Reboot and enjoy.
I got the same thing tonight!!! Damn!
I can't do anything with /data partition in any version of CWM - RedPill too. It just hangs. It can't be wiped or formatted. And phone doesn't boot. I flashed KKA 1 file firmware via odin, but the phone still doesn't boot. I'm now downloading KK9 in hope that it is 3 file (because I can't find info whether it is 1 or 3 file) to try to flash it. Also using pit and repartition could fix it, but I am frightened by messages "do not ever tick repartition or you get brick".
Very sad.
guys, i need help please. My Note not work in download mode and cwm recovery. I made a homemade JIG, but not works, too. I tested the homemade JIG in a galaxy ace and in a galaxy S2 and enter instantly in download mode but in galaxy note no. my pc and other pc does not recognize the phone either. Can I do anything?
Thanks
eliot_11 said:
guys, i need help please. My Note not work in download mode and cwm recovery. I made a homemade JIG, but not works, too. I tested the homemade JIG in a galaxy ace and in a galaxy S2 and enter instantly in download mode but in galaxy note no. my pc and other pc does not recognize the phone either. Can I do anything?
Thanks
Click to expand...
Click to collapse
plug phone into usb to pc. Take battery out, wait 30 sec, while holding volume down put battery in and keep holding until download screen comes up
see if this helps
or do this if that doesn't help
http://forum.xda-developers.com/showpost.php?p=13856913&postcount=5
B.Maximenko said:
I got the same thing tonight!!! Damn!
I can't do anything with /data partition in any version of CWM - RedPill too. It just hangs. It can't be wiped or formatted. And phone doesn't boot. I flashed KKA 1 file firmware via odin, but the phone still doesn't boot. I'm now downloading KK9 in hope that it is 3 file (because I can't find info whether it is 1 or 3 file) to try to flash it. Also using pit and repartition could fix it, but I am frightened by messages "do not ever tick repartition or you get brick".
Very sad.
Click to expand...
Click to collapse
Yup...exactly...my /cache partition seems fine now...but it's hanging on /data too! Did you flash the new touch kernel from angelom too? I don't want to point fingers, but I would at least like to know what the "root" cause is. Anyway, instead of using ODIN, I used Heimdall. I'm at pretty much the same place I was before, except now I have Samsung's recovery....
Anyway, I'll keep flashing different firmwares, and I'll see where we get.
Edit: I used a .pit file as well. Was I not supposed to do that? I don't think it did any harm, as my phone still turns on!
eliot_11 said:
guys, i need help please. My Note not work in download mode and cwm recovery. I made a homemade JIG, but not works, too. I tested the homemade JIG in a galaxy ace and in a galaxy S2 and enter instantly in download mode but in galaxy note no. my pc and other pc does not recognize the phone either. Can I do anything?
Thanks
Click to expand...
Click to collapse
see my signature
Okay, so I have an idea. I flashed the repack kernel and got CWM back...but obviously my /data partition is still ****ed. Would it be possible to do a repartition of it? Do I need an ICS pit file to do this?...because I noticed the Chainfire repack has a data.img, and I tried flashing it using a GB .pit file, and it hung up...so, I think this might be my last hope!
Hey I also flashed the new ICS kernel posted by angelom...
And having same problem....
getting errors like this while entering CWM
E:can't mount/cache/recovery/command
E:can't mount/cache/recovery/log
E:can't open/cache/recovery/log
E:can't mount/cache/recovery/last_log
E:can't open/cache/recovery/last_log
Okay, so I feel a little better that it's not just me! Obviously no one, including the developer, is to blame...but the kernel is definitely the cause, and I'm having trouble with the fact that I might be spending 650 on another phone, just for the simple fact that I thought it would be intuitive to have a touch recovery. Grrrrrrr.....
thanks for your help, but my note not have signals of life. Thanks
eliot_11 said:
thanks for your help, but my note not have signals of life. Thanks
Click to expand...
Click to collapse
Sorry to hear that elliot. Is it under warranty/ensured?
Sent from my GT-N7000 using Tapatalk
I went in to wipe /cache as well, and that's when it all happened. I don't have a complete brick, but it might as well be. If I can get into recovery and download mode, but nothing works, then what good is it? A constat bootlooping phone is no phone at all. I don't insurance, and as far as I can tell my warranty is void. So I think my best option would be to send the phone directly to Samsung and see what they can do. It's better than nothing.
smalmagal said:
Yup...exactly...my /cache partition seems fine now...but it's hanging on /data too! Did you flash the new touch kernel from angelom too? I don't want to point fingers, but I would at least like to know what the "root" cause is.
Click to expand...
Click to collapse
Yes, it happened right after I flashed angelom 1.1. I used ver 1.0 for some time, didn't try to wipe data, but rom was running OK. Then I flashed imilka's v0.3 and angelom 1.1 on top, tried to wipe data and got that error message. After that, my phone hangs on boot logo and can't do anything with /data partition, and I can't restore any of my backups - it says error in /data. I flashed stock KKA firmware with odin, it didn't fix /data - stock recovery also can't wipe it.
Samsung galaxy note completely dead !!
my rooted galaxy note was on rocket rom which i updated to ics theme, and without rebooting i flashed the zip file to reset binary data count.
all this was happening in cwm.
then i opted to reboot to system and my galaxy note never rebooted.
what to do? where do i go?
phone s rooted but wont go into cwm mode, nor into flashing mode,,, does not even charge...
smalmagal said:
This is my first post, go easy on me! I own a few Android devices, all rooted, and flashed over probably hundreds of times. I know all the risks associated with it, and I take full responsibility for anything that happens to my devices. I've never had any problems in the past getting around recovery and dealing with custom ROMS...nothing that can't be fixed anyway (boot loops, force closes, ect...).
I've never seen so many problems with recovery than I have with the Galaxy Note, however. I mean, if you can't depend on a recovery to work, what are you to depend on? I had a bit of a panic flashing some of the ICS leaks, but all was resolved. No biggie. Everything was running smoothly, and somehow my recovery became fully operational again. I was able to mount /system...and was fully able to flash from CWM again, as opposed to Redpill.
Okay, long winded I know...but here I am. I just flashed angelom's newest kernel with touch recovery. "Cool" I thought. Couldn't hurt. So I went in to do a wipe of /cache and it hung up. No biggie again. I held down the magic three buttons, and when I rebooted back into recovery, I get this....over and over again.
"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
No files found."
I've tried flashing Redpill again and installing, restoring stock back up, powering down and taking my battery out for a while...bashing my head on the wall. No matter what I do, it doesn't get past the Samsung logo. It was hanging up on booting before, but now it won't even go that far. Do I venture down the path of Odin (which I still am not entirely sure how to use)...or do I have a full brick on my hands? Looks like I might have fried the internal storage. If that's the case, I'm ****ed...simply put.
Anyway, ANY help would be greatly appreciated. Hopefully someone else has run into a similar problem and has a fix...no matter how complicated. Thank you for your time!
Click to expand...
Click to collapse
sometimes it doesnt recover, i had it with the hd2 aswell, it isnt a note specific issue, as for the title, it is misleading, a brick is not being able to turn the phone on, seeing as you coudl where did you get the notion it was bricked?
the errors in the recovery are standard if no rom is installed
First thank you for all the wonderful work there to help us make the best out of this phone.
Yesterday, I tried to install the CM10 ROM (cm-10-20121126-UNOFFICIAL-ancora_tmo) but encountered a serious problem. Since I flashed a custom ROM last time in Aug., I haven't updated the recovery (CWM-base Recovery v5.5.0.4b). When I booted into the recovery, I found it lost all its functionality. To be specific, any selection on menu options (reboot system now, ROMwipe, wipe cache, etc.) yielded no result but a screen with a circling arrow covered by a hat. After that only the power button worked and it would simply bring you back to the main menu. I tried to communicate with the phone in ADB mode and it worked (by that I mean I can reboot it from windows command shell: adb reboot recovery). Now I have no way to update the recovery and install new ROM from there.
Any help would be highly appreciated.
If you can communicate via windows then install Odin and flash from it. Full instructions is on the wiki page
http://forum.xda-developers.com/wiki/Samsung_Exhibit_II_4G
Sent from my CM10 Linero Odexed Powered by Evil
ywhui30 said:
First thank you for all the wonderful work there to help us make the best out of this phone.
Yesterday, I tried to install the CM10 ROM (cm-10-20121126-UNOFFICIAL-ancora_tmo) but encountered a serious problem. Since I flashed a custom ROM last time in Aug., I haven't updated the recovery (CWM-base Recovery v5.5.0.4b). When I booted into the recovery, I found it lost all its functionality. To be specific, any selection on menu options (reboot system now, ROMwipe, wipe cache, etc.) yielded no result but a screen with a circling arrow covered by a hat. After that only the power button worked and it would simply bring you back to the main menu. I tried to communicate with the phone in ADB mode and it worked (by that I mean I can reboot it from windows command shell: adb reboot recovery). Now I have no way to update the recovery and install new ROM from there.
Any help would be highly appreciated.
Click to expand...
Click to collapse
This may seem stupid but how are you selecting something? You should use home capacitive not the power to select. This symptom is the result of tapping the power button, its kinda like sleep
Sent from my Nexus 7 using xda app-developers app
afwolfpacked said:
If you can communicate via windows then install Odin and flash from it. Full instructions is on the wiki page
http://forum.xda-developers.com/wiki/Samsung_Exhibit_II_4G
Sent from my CM10 Linero Odexed Powered by Evil
Click to expand...
Click to collapse
I'd followed the instruction and found the Odin rebooted to the exact recovery! There it showed a few lines like:
Galaxy Exhibit CWM-based Recovery v5.5.0.4b
Finding update package ...
Opening update package ...
Verifying update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Now the phone can not boot into the original ROM.
When booted into recovery use volume keys to navigate in cwm. Also retry to download the ROM and try cwm before Odin.
Odin is on computer and phone is hooked via USB cable. It cannot boot into cwm if followed Odin. You ha e to download Odin and drivers for cell to be recognized.
Do a YouTube search for Odin and watch the vid it will show you. Be it noted that cell will need to be set into download mode and USB enabled.
Sent from my CM10 Linero Odexed Powered by Evil and or DemonsBlood
theAPANT said:
This may seem stupid but how are you selecting something? You should use home capacitive not the power to select. This symptom is the result of tapping the power button, its kinda like sleep
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I used the home capacitive to select those options on the main menu. No matter what I choose, however, the power button can get me the circling arrow with a hat. Another push on the button, you are back on the main menu.
You are deffeinitly booted into cwm so I suspect from the install error that the signature verification is what's failing. Try another ROM or redownload and try again
Sent from my CM10 Linero Odexed Powered by Evil and or DemonsBlood
afwolfpacked said:
You are deffeinitly booted into cwm so I suspect from the install error that the signature verification is what's failing. Try another ROM or redownload and try again
Sent from my CM10 Linero Odexed Powered by Evil and or DemonsBlood
Click to expand...
Click to collapse
I've redownloaded the uvlg3.odin.zip package and checked its MD5. Everything is OK. Then followed the instruction on the Wiki page, but ended on the same CWM recovery screen with the same error message.
The problem is: it seems like the phone boots successfully into the recovery, but it only shows the main menu with no option functioning (like I described before).
Has anyone read about similar problem anywhere before?
ywhui30 said:
I've redownloaded the uvlg3.odin.zip package and checked its MD5. Everything is OK. Then followed the instruction on the Wiki page, but ended on the same CWM recovery screen with the same error message.
The problem is: it seems like the phone boots successfully into the recovery, but it only shows the main menu with no option functioning (like I described before).
Has anyone read about similar problem anywhere before?
Click to expand...
Click to collapse
Are you running Odin with your phone in Download mode? Like they said, Odin shouldn't re/boot into recovery automatically.
Also make sure the auto reboot option in odin is cleared.
Sent from my GT-P5110 using XDA Premium HD app
Hello,
I have with this phone really big problem. Namely, I had preloaded on it CyanogenMod in version 10.1. Unfortunately, the phone broke (guts inside) and did not react to anything, nothing will even launch the DownloadMode, so I said I'd send him to the site Samsung'a, I know that it automatically breaks the warranty, but I found it difficult, can make a ball . I was right, even though I got papers to break the warranty, however, they fixed it in 50% because now it turns on Download mode, and before anything, no reaction, no vibration, and charging the phone until jumping out logos "Samsung Galaxy Mini 2 GT-S6500D. " Unfortunately, this is over.
I tried to upload the ROM to the phone on the version of the GT-S6500D (because the bought) and here surprise, jumped an error that the model number is not right, I checked and the very surprising fact is that everywhere in the papers, and under the battery, I have written a model "GT-S6500D", while the entrance to the Download Mode in the "PRODUCT" I have written "GT-S6500" (without the letters D). Well, but as good as he wanted it done, I uploaded ROM for GT-S6500 and the kind of work, because there hangs on the log Samsung just goes on. But freezes a moment later, some error recovery , where it opens the installer Android'a and suddenly error:
Failed to mount / cache (no such file or directory)
Can not mount / cache / recovery / command
Failed to mount / system (no such file or directory)
No strange, yet this is not met, but good, I wanted to do so as they write, "go to recovery and make wipy", ok, I'm trying, VOL + HOME + POWER i .. Enables the message "RAMDUMP ARM9." Hmm .. I think wgram ClockWorkMod'a can help. I have uploaded ... I run ... RAMDUMP ... I'm trying to package a "live recovery" (or something like that - is to install the recovery on the phone and immediately turn it on), installed ... I'm waiting ... been activated .. . phew ... I'm trying to upload CyanogenMod 'on the SD card error:
Failed to mount / sdcard
... It is difficult, upload again the standard ROM Recovery on it still does not start, instead RAMDUMP, the installer stops ... And now I'm here, that's the end of my story.
I was looking for, I found a lot, but not enough. Happened same RAMDUMP, recommending Superuser.apk (I can not upload does not start the system), occurred Failed Load recommend Wipy ( Recovery will not start) ... And when we tried all these tips ... Nothing worked ... Time the following questions:
1.At the beginning, I would like to know (out of curiosity) how is it possible that before the service had S6500D and now I have S6500.
2.How to fix that instead RAMDUMP'a will load the Recovery .
3.What is the use of RAMDUMP'a because Odin in this mode is not phone me:?
4.How to fix this phone to work again, or at least a "sufficient walked"?
5.What could be causing this strange behavior?
My guess is that the answer will not be too simple, but I would be very grateful if somebody advised something, because I after two days of ideas is over :/
Thank you in advance, sorry for my bad English and best regards!
Now I am trying to solve your problems.
Reserved for solutions.
1.At the beginning, I would like to know (out of curiosity) how is it possible that before the service had S6500D and now I have S6500.
2.How to fix that instead RAMDUMP'a will load the Recovery .
3.What is the use of RAMDUMP'a because Odin in this mode is not phone me:?
4.How to fix this phone to work again, or at least a "sufficient walked"?
5.What could be causing this strange behavior?
Click to expand...
Click to collapse
I will try to solve it step by step.
1. To tell you more about this, please tell me if you see an nfc app on the launcher's app drawer. ( I mean, after service, with the s6500 rom)
Click to expand...
Click to collapse
2. To fix it see my solution there http://forum.xda-developers.com/showthread.php?t=2707219
Click to expand...
Click to collapse
3. After your device crashes, RAMDUMP creates ramdump*.log files in the root storage. This is useful for developers.
Click to expand...
Click to collapse
4. To restore your phone to original baseband, you need to acces recovery an wipe data,system,cache,dalvik cache. Then flash an S6500d rom with odin from www.samfirmware.com
Click to expand...
Click to collapse
When I tried to wipe data,cache,system,dalvik I got error: "Failed to mount (/data,/system/,etc.)"...
blahax2g said:
When I tried to wipe data,cache,system,dalvik I got error: "Failed to mount (/data,/system/,etc.)"...
Click to expand...
Click to collapse
I am glad that you can now acces recovery. But now you need to try to reflash it, and see what happens, I mean, if you can mount something.
My friend have this kind of issue but he just flash it
Firstly, I apologize if this is in the wrong spot.
I'll just get to the point.
So about 6 months ago I was using the Galaxy Ace GT-S5830 (Aus) and as it has a terrible internal memory, I decided to root it and try to get some of the unwanted apps off. Worked like a charm, nothing wrong until I had to take the battery out as it froze one time and now I am stuck with a boot loop -.-
I tried looking into trying to fix it like I had in the past but I got frustrated and gave up. Now in current time, I want to try to fix it and get it working again. So I got the stock firmware as well as the latest version of CWM for it and the recommended version of Odin, I get the phone into download mode and then come across an issue where my laptop says that it's connected (while I have Odin up) but is an unrecognizable device. First thing I do is try to factory reset it through the recovery menu but I get the error- E:format_volume: make_extf4fs failed on /dev/block.mmcblk0p2
I did a google search on both the boot loop and the error but I can't do anything people have said to do/try as my laptop isn't letting it be a recognizable device
I have done everything I've read in the past and have learned from past experiences but no luck. So what can I do to get the phone to work again?
If anyone can, give the method with pictures as well as I can do it better through pictures rather than reading it and hoping all goes well
Thanks
Samsung Galaxy Ace GT - S5830 boot loop and error
Bigdanzo51196 said:
Firstly, I apologize if this is in the wrong spot.
I'll just get to the point.
So about 6 months ago I was using the Galaxy Ace GT-S5830 (Aus) and as it has a terrible internal memory, I decided to root it and try to get some of the unwanted apps off. Worked like a charm, nothing wrong until I had to take the battery out as it froze one time and now I am stuck with a boot loop -.-
I tried looking into trying to fix it like I had in the past but I got frustrated and gave up. Now in current time, I want to try to fix it and get it working again. So I got the stock firmware as well as the latest version of CWM for it and the recommended version of Odin, I get the phone into download mode and then come across an issue where my laptop says that it's connected (while I have Odin up) but is an unrecognizable device. First thing I do is try to factory reset it through the recovery menu but I get the error- E:format_volume: make_extf4fs failed on /dev/block.mmcblk0p2
I did a google search on both the boot loop and the error but I can't do anything people have said to do/try as my laptop isn't letting it be a recognizable device
I have done everything I've read in the past and have learned from past experiences but no luck. So what can I do to get the phone to work again?
If anyone can, give the method with pictures as well as I can do it better through pictures rather than reading it and hoping all goes well
Thanks
Click to expand...
Click to collapse
Try to carry out the sd card, then use odin to flash ROM Stock again;
after that do in recovery stock a factory rest and wipe cache partition.
daniga74
daniga74 said:
Try to carry out the sd card, then use odin to flash ROM Stock again;
after that do in recovery stock a factory rest and wipe cache partition.
daniga74
Click to expand...
Click to collapse
What do you mean by carry out the sd card? That's all I'm not understanding, sorry.
And I apologise for the lack of reply, haven't had any wifi since I made this post.
remove the sd card and flash the stock rom
I've done that but my laptop just says USB device not recognized and because of that, Odin can't pick up the phone. This is the only issue I'm having now.
Samsung Galaxy Ace GT - S5830 boot loop and error.
Bigdanzo51196 said:
I've done that but my laptop just says USB device not recognized and because of that, Odin can't pick up the phone. This is the only issue I'm having now.
Click to expand...
Click to collapse
It means that your laptop doesn't recognize your Galaxy Ace, try to install usb drivers again.
alternatively, if you are able to go in revovery mode (CWM):
format the sd-card from the laptop; create a new fat32 partition (primary) and copy on it Cyanogenmod 7.2;
inser the card in your ACE and flash it from recovery;
later you can re-install usb driver on laptop and flash stock rom.
daniga74
Bigdanzo51196 said:
Firstly, I apologize if this is in the wrong spot.
I'll just get to the point.
So about 6 months ago I was using the Galaxy Ace GT-S5830 (Aus) and as it has a terrible internal memory, I decided to root it and try to get some of the unwanted apps off. Worked like a charm, nothing wrong until I had to take the battery out as it froze one time and now I am stuck with a boot loop -.-
I tried looking into trying to fix it like I had in the past but I got frustrated and gave up. Now in current time, I want to try to fix it and get it working again. So I got the stock firmware as well as the latest version of CWM for it and the recommended version of Odin, I get the phone into download mode and then come across an issue where my laptop says that it's connected (while I have Odin up) but is an unrecognizable device. First thing I do is try to factory reset it through the recovery menu but I get the error- E:format_volume: make_extf4fs failed on /dev/block.mmcblk0p2
I did a google search on both the boot loop and the error but I can't do anything people have said to do/try as my laptop isn't letting it be a recognizable device
I have done everything I've read in the past and have learned from past experiences but no luck. So what can I do to get the phone to work again?
If anyone can, give the method with pictures as well as I can do it better through pictures rather than reading it and hoping all goes well
Thanks
Click to expand...
Click to collapse
Well from what you said above it seems that somethings wrong with the phones internal memory and not the sd-card. If you are having CWM recovery(the latest one) you can do this-
I assume that your phone is rooted and with CWM installed.
Download any custom rom
Boot into CWM.
Select wipe data reset and you ll see an option saying 'clean wipe to install a new rom' (something like this)
Install zip from sdcard and select the downloaded rom.
Report back if any problem.
All the best.
Sent from my GT-I9500 using XDA Free mobile app
Mandark52 said:
Well from what you said above it seems that somethings wrong with the phones internal memory and not the sd-card. If you are having CWM recovery(the latest one) you can do this-
I assume that your phone is rooted and with CWM installed.
Download any custom rom
Boot into CWM.
Select wipe data reset and you ll see an option saying 'clean wipe to install a new rom' (something like this)
Install zip from sdcard and select the downloaded rom.
Report back if any problem.
All the best.
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
I've done the custom ROM part, I used Cyanogenmod 7.2 as daniga74 suggested.
But I'm still getting this error message when I tried to wipe data/factory reset in the CWM recovery menu: E:format_volume: make_extf4fs failed on /dev/block.mmcblk0p2
Here's a picture of it.
I apologize for it being rotated, the original picture isn't.
Bigdanzo51196 said:
I've done the custom ROM part, I used Cyanogenmod 7.2 as daniga74 suggested.
But I'm still getting this error message when I tried to wipe data/factory reset in the CWM recovery menu: E:format_volume: make_extf4fs failed on /dev/block.mmcblk0p2
Here's a picture of it.
I apologize for it being rotated, the original picture isn't.
Click to expand...
Click to collapse
Maybe your internal partitions are corrupted, try to flash a fresh STOCK rom via Odin and start again (Root+CWM5.0.2.6+Custom ROM)
Samsung Galaxy Ace GT - S5830 boot loop and error
Bigdanzo51196 said:
I've done the custom ROM part, I used Cyanogenmod 7.2 as daniga74 suggested.
But I'm still getting this error message when I tried to wipe data/factory reset in the CWM recovery menu: E:format_volume: make_extf4fs failed on /dev/block.mmcblk0p2
Here's a picture of it.
I apologize for it being rotated, the original picture isn't.
Click to expand...
Click to collapse
Before flash CM 7.2, try to format system and data partition from CWM (advanced menu);
if the operation was successfully flash the rom.
daniga74
Bigdanzo51196 said:
I've done the custom ROM part, I used Cyanogenmod 7.2 as daniga74 suggested.
But I'm still getting this error message when I tried to wipe data/factory reset in the CWM recovery menu: E:format_volume: make_extf4fs failed on /dev/block.mmcblk0p2
Here's a picture of it.
I apologize for it being rotated, the original picture isn't.
Click to expand...
Click to collapse
The error says "It fails to format sdext". Because, you don't have a sdext partition. Don't worry about it. It is normal.
Mandark52 said:
Well from what you said above it seems that somethings wrong with the phones internal memory and not the sd-card. If you are having CWM recovery(the latest one) you can do this-
I assume that your phone is rooted and with CWM installed.
Download any custom rom
Boot into CWM.
Select wipe data reset and you ll see an option saying 'clean wipe to install a new rom' (something like this)
Install zip from sdcard and select the downloaded rom.
Report back if any problem.
All the best.
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
Viper The Ripper said:
Maybe your internal partitions are corrupted, try to flash a fresh STOCK rom via Odin and start again (Root+CWM5.0.2.6+Custom ROM)
Click to expand...
Click to collapse
Sent from my GT-S5570 using XDA Free mobile app
USB not recognized
are you using Win 8 or 8.1 on your laptop? Because win 8 / 8.1 cant work with samsung driver for s5830 via Odin. You must try it on older OS like win 7 to flash stock ROM.
Late reply/update
Sorry about the reply, haven't had much time to check on this as I've been moving and now have to use public wifi -.-
I have seemed to be able to get the Cyanogenmod to work and act as an OS for now, it's not what I was hoping for but it's letting me use the phone for now and that's good enough for me. Will have to properly flash it when I get the chance to and when I have a Win 7 computer to use, thank you gaineeg for pointing that out. It now makes more sense as to why it never picked up on my laptop (Win 8.1) but it did on my dads computer (Win 7).
Bigdanzo51196 said:
Firstly, I apologize if this is in the wrong spot.
I'll just get to the point.
So about 6 months ago I was using the Galaxy Ace GT-S5830 (Aus) and as it has a terrible internal memory, I decided to root it and try to get some of the unwanted apps off. Worked like a charm, nothing wrong until I had to take the battery out as it froze one time and now I am stuck with a boot loop -.-
I tried looking into trying to fix it like I had in the past but I got frustrated and gave up. Now in current time, I want to try to fix it and get it working again. So I got the stock firmware as well as the latest version of CWM for it and the recommended version of Odin, I get the phone into download mode and then come across an issue where my laptop says that it's connected (while I have Odin up) but is an unrecognizable device. First thing I do is try to factory reset it through the recovery menu but I get the error- E:format_volume: make_extf4fs failed on /dev/block.mmcblk0p2
I did a google search on both the boot loop and the error but I can't do anything people have said to do/try as my laptop isn't letting it be a recognizable device
I have done everything I've read in the past and have learned from past experiences but no luck. So what can I do to get the phone to work again?
If anyone can, give the method with pictures as well as I can do it better through pictures rather than reading it and hoping all goes well
Thanks
Click to expand...
Click to collapse
Well if your laptop doesnt recognize the device you will need to install the latest drivers of samsung device drivers. And then manually update device drivers from unknown device to adb sooner device. Then try flashing using odin.