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
Related
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).
Hi
I think* i was trying to do a back up or custom recovery just before it went pear shaped, phone froze and i took the battery out and then ->
The phone doesn't get past boot image ( custom boot image of terminators from the movie ).
I have tried factory reset , trying different roms on sd card and then booting into recovery - but i only had the default recovery on the phone.
I have a kdz file image and a few dz files as well as zip but they don't 'work' , even if i rename them 'update'
The lg support tool gets to a point where it says ' super duper bad , your fxxxxd or fatal error or something so it wont even start a fix or update.
'Unkdzing' only gives me a dz file and .dll
I tried uptestEX ,dzextract,lgflashmuncher,expand,lgextract and extractor kdz - but on that it stops with some WMD warning - in spanish i think.
This is the 5th day ive tried to fix the prob but i fail.
After I un screw the phone can it be flashed/shocked with electricity on the part that holds the info ? ( thought id ask before going ahead and doing it anyways )
The phone is rooted
try this
Thiswilldo said:
Hi
I think* i was trying to do a back up or custom recovery just before it went pear shaped, phone froze and i took the battery out and then ->
The phone doesn't get past boot image ( custom boot image of terminators from the movie ).
I have tried factory reset , trying different roms on sd card and then booting into recovery - but i only had the default recovery on the phone.
I have a kdz file image and a few dz files as well as zip but they don't 'work' , even if i rename them 'update'
The lg support tool gets to a point where it says ' super duper bad , your fxxxxd or fatal error or something so it wont even start a fix or update.
'Unkdzing' only gives me a dz file and .dll
I tried uptestEX ,dzextract,lgflashmuncher,expand,lgextract and extractor kdz - but on that it stops with some WMD warning - in spanish i think.
This is the 5th day ive tried to fix the prob but i fail.
After I un screw the phone can it be flashed/shocked with electricity on the part that holds the info ? ( thought id ask before going ahead and doing it anyways )
The phone is rooted
Click to expand...
Click to collapse
have you tried all methods here
http://forum.xda-developers.com/showthread.php?t=2068321
Hi
Yeah I tried those and those led me to other links of people trying other methods but none of them worked out.
Basically I think I need to shelf the phone until there's a boot loader - that should fix most/all problems shouldn't it ?
I like the phone so I'll order another one same colour same place same bat channel :good:
did you change or reinstall busybox
busy box was changed days before
Thiswilldo said:
busy box was changed days before
Click to expand...
Click to collapse
but i am sure, you didn't rebooted before this after replacing busybox. Busybox takes effect after reboot.
yeah i agree as its exactly the same as happened to my phone, i had installed busybox 1.20 and didnt reboot then a while later the phone froze and when i rebooted it stuck at boot logo
I was doing a few things with the phone so yeah, you're probably right.
So is there a fix ?
Thiswilldo said:
I was doing a few things with the phone so yeah, you're probably right.
So is there a fix ?
Click to expand...
Click to collapse
hello
the way i fixed it is explained in the following link(the last post)
http://forum.xda-developers.com/showthread.php?t=2068321&page=3
good luck and feel free to ask if you become stuck,im certain that if its something i dont know then there will be someone here
friartuckme said:
hello
the way i fixed it is explained in the following link(the last post)
http://forum.xda-developers.com/showthread.php?t=2068321&page=3
good luck and feel free to ask if you become stuck,im certain that if its something i dont know then there will be someone here
Click to expand...
Click to collapse
I tried and it didn't work
What should the screen look like when its plugged in and turned on ? , I did the vol + power key and its statiky* and sometimes vibrates. So i tried vol - and power, vol + and home and power, vol - and home and power but total commander still didn't see the phone connected to it.
I extracted adb to total commander and i click on it when total commander is open then I have to click connect to device then a box pops up and i input COM4 ( matched it up with device manager ) but nothing happens.
The only 'normal' screen is when it is in sw update mode, other than that its either grey or pink or white and vibrates at times with all sometimes.
Ok I tried vol + and power with the battery in and when i click on adb the device ID is shown but when i click on that, its totally empty.. no folders or files , completely blank.
Also next to the network 3 pc image it still says [none]
When i try to copy the new busybox to the device id it says 'please remove the write protection'.. so I right click the busybox file and click unblock but same message again
It has full permissions.
you need to keep hold of the keys until it starts up.it will vibrate and screen will go blank about 2 times before it boots into the correct mode,sorry i didnt think of writing that into my other post
friartuckme said:
you need to keep hold of the keys until it starts up.it will vibrate and screen will go blank about 2 times before it boots into the correct mode,sorry i didnt think of writing that into my other post
Click to expand...
Click to collapse
yeah it takes like 5 seconds for it to reboot and then the 'notice' screen appears, but still it says ' please remove the write protection '
Also noticed on my pc under device manager that android adapter has yellow triangle.
I went to LG site and got the driver but it didn't install, even found generic driver but it didn't install, also let windows find one but it didn't install, also tried manually but android driver just wont install.
My understanding is without that android driver total command won't work.
hi sorry to hear your still having problems, all i can suggest is uninstall the drivers and reinstall without the device connected,also are you leaving it til it comes to the screen has a window with a phone and and cables with a red hand covering them,
the driver that you really need it too load is the called Android Sooner single ADB Interface, as far as im aware that when booting into this mode it doesnt load your currently corrupted system files maybe after you retry installing it should hopefully work also if you havent already installed the lg support tool then it would be easier for you to install that and install the drivers that way,they can be found through the following link
http://www.lg.com/uk/support/mobile-support
il have a good think and look at what could be the problem if you are still having problems
yeah I have that driver and two others, nothing is working unfortunately
Hi guys, i gonna tell you about how my i9001 was stuck in a bootloop. Maybe you could help me. I'm sick of it.
Cause: I installed cm10 and cwm5 or 6 as recovery and upgrade my device using Ota Updater. When I restarted my i9001, it got stuck in a bootloop.
What my i9001 can display: It can access to rampdump mode and download mode. In case I try to turn on my i9001 or access to recovery mode the Samsung logo/word is shown twice and stops showing anything else. It often gets stuck showing the typical grey battery flat (with a loading stopped) and the black screen alternately. This is caused when I a disconnect the USB cable from my computer/laptop.
Attempts: i've tried everything except for the right solution. Lots of forum threads and nothing works for me. I've tried:
1.- Boot_loader for device boot.
2.- I've flashed an stock rom: XXKQP, and 2 more: BVKPC y XXKQ1. Each one are official.
3.- And then recovery-clockwork-5.5.0.4 and -6.0.1.2.
4.- I've tried, then, flashing feamodrecovery 1.2.
5.- Nothing works for me.
I've been using Odin 4.43. AriesVE in OPS section and when flashing these roms: one package. For recovery packages: one package and pda (I tried these two options).
I can't reach at recovery mode. Any help would be greatly appreciated. Greetings!
have a look here http://forum.xda-developers.com/showpost.php?p=30415128&postcount=1
When phone boots there's nearlz always a solution
Sent from my GT-I9001 using xda app-developers app
slow--welder59, any of these solutions helped me. I tried with any other combination of combos but nothing happened. I didn't know to use adb method. I installed adb drivers but it didn't detect my device. When I entered to download mode and pressed Install (in the program) tried to download something but it stopped.
Any suggestion?
Can anyone help me? I want to exhaust all possible options.
zerohhorez said:
Can anyone help me? I want to exhaust all possible options.
Click to expand...
Click to collapse
What happens when you try to format data from recovery...?
If you get some errors, write them here...
If everything goes well, then it is not what im expecting (in that case problem is probably easier to solve)...
sava92ns said:
What happens when you try to format data from recovery...?
If you get some errors, write them here...
If everything goes well, then it is not what im expecting (in that case problem is probably easier to solve)...
Click to expand...
Click to collapse
The problem is just this. I cannot go to recovery mode. Just shows Samsung twice and powers off.
zerohhorez said:
The problem is just this. I cannot go to recovery mode. Just shows Samsung twice and powers off.
Click to expand...
Click to collapse
Can you open 'Download mode'?
sava92ns said:
Can you open 'Download mode'?
Click to expand...
Click to collapse
Yes I can, and that's the reason why I don't give up hope. However, I've tried installing some stock roms and recoveries and nothing worked for me.
Try one of the following (or both even if your desperate):
http://forum.xda-developers.com/showthread.php?t=1922505 (broodROM RC5 download link) [recomended]
http://broodplank.net/old/flashsamsungi9001.php (skip chapter 5 as it doesn't apply) [if that doesn't work]
edit:: USB Drivers: http://forum.xda-developers.com/showthread.php?t=961956
stepie22, thank you for your help. Nothing worked for me.
First link: another typical manual for installing a stock rom via Odin. During the process my device powered off. It was supposed to reboot. After the process ended, i disconnected it from PC and its screen showed a grey empty battery (with a loading in the middle) and word "Samsung" alternatively.
Second link: this was the solution for my first brick. Then, my device showed this yellow triangle. This second time is annoying me. I haven't found any solution to change, at least, the behaviour of my device.
Any other different solution? Thnks guys.
zerohhorez said:
Then, my device showed this yellow triangle.
Click to expand...
Click to collapse
See this ... if that is the triangle, find that part on the wiki page.
Maybe your device got the eMMC Bug?
Normally your Device would be hardbricked if you "over" flashed.
If nothing works out try this:
Have a look in this thread:
http://forum.xda-developers.com/showthread.php?t=2224029
Download CWM Recovery 6.0.2.8 ODIN Package and flash it in "Download Mode" the regular way (AriesVE.ops and onepackage).
Then maybe you are able to enter Recovery Mode again...
This might be not your problem, but you could give it a try:
Some people had issues with rebooting in recovery, so there is a fix in this post
http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330
Hopefully one helps you!
Greetings
My friend just gave me his Unbranded Samsung Galaxy S GT-i9000 to fix it.
I used the 3 button combo to access download mode then Odin it but when it boots to download mode it checks the internal mmc and returns an error exiting to stock recovery and I can't adb there no install from sdcard stuff. Need help with accessing download mode!
Error description:
E:failed to mount /dbdata (invalid Argument)
-- Verifying internal MMC block...
E:internal mmc : read fail
# MANUAL MODE #
Anyone can figure this out for me please?
Thank you.
akhrot91 said:
Unbranded Samsung Galaxy S GT-i9000
Click to expand...
Click to collapse
unbranded? check this
download mode is home + power for M110S
recovery ia vol down + home + power for M110S
xsenman said:
unbranded? check this
download mode is home + power for M110S
recovery ia vol down + home + power for M110S
Click to expand...
Click to collapse
Thank you brother, thanks so very much.
I just have another question, now how do I get back to stock ROM? Can you direct me to a guide that tells how to do it via heimdall?
I'm using Ubuntu 13.10 and don't want to run Odin from wine.
Thanks again.
akhrot91 said:
Thank you brother, thanks so very much.
I just have another question, now how do I get back to stock ROM? Can you direct me to a guide that tells how to do it via heimdall?
I'm using Ubuntu 13.10 and don't want to run Odin from wine.
Thanks again.
Click to expand...
Click to collapse
you need to flash Repair kit for M110S, download from PIT STOP link below and use this method
xsenman said:
you need to flash Repair kit for M110S, download from PIT STOP link below and use this method
Click to expand...
Click to collapse
I flashed Repair kit for M110S through heimdall suite. The Download mode has changed to korean language and now whatever combination I press it goes to download mode even by simply pressing the power button it goes to download mode.
Can you help me with that?
Should I try again on Windows OS with Odin?
akhrot91 said:
I flashed Repair kit for M110S through heimdall suite. The Download mode has changed to korean language and now whatever combination I press it goes to download mode even by simply pressing the power button it goes to download mode.
Can you help me with that?
Should I try again on Windows OS with Odin?
Click to expand...
Click to collapse
First I hope you had ensured that it was actually an M110S and not another variation of i9000
yes, Korean phones always have everything in Korean, but once having a boot-able ROM, you can use settings menu to change to English. which repair kit did you use? , as long as its in download mode you should be able to flash again, either with Odin3 or heimdall. also what stage of flashing did you complete .
just flash again but make sure you have ample battery charge, as power failure or pulling out usb connection can break the bootloader and you will have a big headache , hard bricking it and only a technician with JTAG can recover it.
xsenman said:
First I hope you had ensured that it was actually an M110S and not another variation of i9000
yes, Korean phones always have everything in Korean, but once having a boot-able ROM, you can use settings menu to change to English. which repair kit did you use? , as long as its in download mode you should be able to flash again, either with Odin3 or heimdall. also what stage of flashing did you complete .
just flash again but make sure you have ample battery charge, as power failure or pulling out usb connection can break the bootloader and you will have a big headache , hard bricking it and only a technician with JTAG can recover it.
Click to expand...
Click to collapse
I used the link from this under the 'first stage heading'. This is the repair kit.
Yes, I can only access download mode now it doesn't go anywhere else. I completed all four stages but as you have shown in the picture it didn't go to that update screen.
akhrot91 said:
I used the link from this under the 'first stage heading'. This is the repair kit.
Yes, I can only access download mode now it doesn't go anywhere else. I completed all four stages but as you have shown in the picture it didn't go to that update screen.
Click to expand...
Click to collapse
Ok, when you complete first stage does your phone boot up using the Eclair ROM? I normal circumstances it should? you say you completed all four stages, , was the flashing completed as successful in ODin3 and your phone rebooted into download mode?
If so try and check your USB port on your phone if you have any lint or anything that may be shorting them and did this phone got in contact with water?
cause what you say is rather strange for any unit as a successful flash can endup in some sort of boot process and never into download mode.
xsenman said:
Ok, when you complete first stage does your phone boot up using the Eclair ROM? I normal circumstances it should? you say you completed all four stages, , was the flashing completed as successful in ODin3 and your phone rebooted into download mode?
If so try and check your USB port on your phone if you have any lint or anything that may be shorting them and did this phone got in contact with water?
cause what you say is rather strange for any unit as a successful flash can endup in some sort of boot process and never into download mode.
Click to expand...
Click to collapse
Firstly I flashed all the files through heimdall in ubuntu not Odin3.
And at no stage it returned any error. At the first stage the download mode was in english on the phone, it had a yellow triangle and below it was saying "downloading" after I flashed the korean .pit file the phone rebooted back into download mode but the text below the yellow triangle was now in korean. After every flash the phone returned into download mode.
I checked as you said, the problem is before I knew the "Home + Power" button combo to access the download mode the phone booted to Samsung screen and hung there and now it goes no where except the korean download mode.
Deleted!
Okay I've figured out the problem with my phone.
When I was on the first stage when I entered the m110.pit file along with the PDA file. The PDA file had a movinand.mst file, while flashing with odin3 it got stuck on the movinand.mst part and remained stuck forever so I plugged out and restarted in download mode.
I did some googling and found out that this problem is related to internal memory damage or corruption or something like that.
Anyway I finally found out a GB file on some forum I don't remember and flashed it over my galaxy S and it kind of worked. When the phone is powered on it goes to the 'samsung anycall' screen and stays there for a while and at the bottom of the screen comes a progress bar, when it goes full the bootanimation comes up and the phone boots into the ROM. Now the problem is there is no internal memory so no apps are downloaded plus whenever I restart the phone it comes to that samsung anycall screen with the progress bar and then the bootanimation but the phone starts as if it were new, like the initial setup accounts and all and also reverted back to korean language. Is there anyway to fix the internal memory problem or any alternative?
Thanks once again for helping me out this much.
Can you tell me what actually is written under your battery ? as what you are indicating about this units behavior is rather strange and have not come across this on an M110S, and mind you I have help a lot of people to solve their problems on M110S units and tens of thousands had downloaded the repair kit from my upload site. Why I am asking is because I am in doubt as to what is your model? is it an M110S, or i9000 variation or a chinese clone?
this must be cleared , in order to get your phone functioning as remedies for it will vary
Hey. Now I tried flashing with odin3 and here's what happened:
1. After the first stage it should boot into eclair but instead samsung anycall screen comes up and then it goes into recovery with the following output:
E: can't mount /dev/block/st111 (invalid Argument)
# MANUAL MODE #
E: can't mount /dev/block/st111 (invalid Argument)
E: can't mount /dev/block/st111 (invalid Argument)
ok this means you have a cache partition problem , meaning stl11 is the cache partition that is not mounting as such you cannot boot, so lets try this ( remove external SD card, sim card etc and Flash the cache.rfs as below..flash it twice and let me know the result.
Problem:- Getting this when you boot
E:format_volume: rfs format failed on /dev/block/stl11
Solution:- Flash a cache.rfs file meant for your model as PDA with Odin. For i9000 i9000 cache.rfs file, For M110S M110s Cache.rfs
or Flash a Rescue Kit from My Android Collections
Click to expand...
Click to collapse
Click to expand...
Click to collapse
2. I proceeded to the next two stages and flashed the files but still the same.
well, when you get a problem like above, there is no way it can boot until it is resolved, but its has booted into recovery, that is what it should do, not go into download mode.
3. When I press the power button only it goes to the samsung anycall screen and then same happens what i described in 1.
Suggest you flash the cache.rfs for M110S, see if it solves it, If not repeat stage 1 again using the repair kit with the PIT and repartition TICKED using Odin3 see what happens.
---------- Post added at 07:32 AM ---------- Previous post was at 07:23 AM ----------
akhrot91 said:
Is there anyway to fix the internal memory problem or any alternative? Thanks once again for helping me out this much.
Click to expand...
Click to collapse
You need to read the posts on PIT STOP about ways to solve internal memory problem. Look under "Solutions for Android problems " also My Android Solutions, link below.
Click to expand...
Click to collapse
xsenman said:
Can you tell me what actually is written under your battery ? as what you are indicating about this units behavior is rather strange and have not come across this on an M110S, and mind you I have help a lot of people to solve their problems on M110S units and tens of thousands had downloaded the repair kit from my upload site. Why I am asking is because I am in doubt as to what is your model? is it an M110S, or i9000 variation or a chinese clone?
this must be cleared , in order to get your phone functioning as remedies for it will vary
Hey. Now I tried flashing with odin3 and here's what happened:
1. After the first stage it should boot into eclair but instead samsung anycall screen comes up and then it goes into recovery with the following output:
E: can't mount /dev/block/st111 (invalid Argument)
# MANUAL MODE #
E: can't mount /dev/block/st111 (invalid Argument)
E: can't mount /dev/block/st111 (invalid Argument)
ok this means you have a cache partition problem , meaning stl11 is the cache partition that is not mounting as such you cannot boot, so lets try this ( remove external SD card, sim card etc and Flash the cache.rfs as below..flash it twice and let me know the result.
Problem:- Getting this when you boot
E:format_volume: rfs format failed on /dev/block/stl11
Click to expand...
Click to collapse
2. I proceeded to the next two stages and flashed the files but still the same.
well, when you get a problem like above, there is no way it can boot until it is resolved, but its has booted into recovery, that is what it should do, not go into download mode.
3. When I press the power button only it goes to the samsung anycall screen and then same happens what i described in 1.
Suggest you flash the cache.rfs for M110S, see if it solves it, If not repeat stage 1 again using the repair kit with the PIT and repartition TICKED using Odin3 see what happens.
---------- Post added at 07:32 AM ---------- Previous post was at 07:23 AM ----------
You need to read the posts on PIT STOP about ways to solve internal memory problem. Look under "Solutions for Android problems " also My Android Solutions, link below.
Click to expand...
Click to collapse
The back of my phone behind the battery reads:
MODELO: GT-i9000
FCC ID: A3LGTI9000
SSN: I9000T GSMH
I think its a M110S.
The cache problem is over. I told that in my previous post.
Okay I've figured out the problem with my phone.
When I was on the first stage when I entered the m110.pit file along with the PDA file. The PDA file had a movinand.mst file, while flashing with odin3 it got stuck on the movinand.mst part and remained stuck forever so I plugged out and restarted in download mode.
I did some googling and found out that this problem is related to internal memory damage or corruption or something like that.
Anyway I finally found out a GB file on some forum I don't remember and flashed it over my galaxy S and it kind of worked. When the phone is powered on it goes to the 'samsung anycall' screen and stays there for a while and at the bottom of the screen comes a progress bar, when it goes full the bootanimation comes up and the phone boots into the ROM. Now the problem is there is no internal memory so no apps are downloaded plus whenever I restart the phone it comes to that samsung anycall screen with the progress bar and then the bootanimation but the phone starts as if it were new, like the initial setup accounts and all and also reverted back to korean language. Is there anyway to fix the internal memory problem or any alternative?
Thanks once again for helping me out this much.
Click to expand...
Click to collapse
akhrot91 said:
The back of my phone behind the battery reads:
MODELO: GT-i9000
FCC ID: A3LGTI9000
SSN: I9000T GSMH
I think its a M110S.
Click to expand...
Click to collapse
The scam artists who have converted M110S to i9000 use I9000GSMH and will not indicate the FCC or SSN
yours says its an i9000T and there is such a model, look http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/GT-I9000T
so best to check your IMEI number , follow this link to identify your model
anyway so long as your phone works its not a serious problem, but wrong ROMs can give you differing problems so ensure your unit is M110S before using solutions in PIT STOP
xsenman said:
The scam artists who have converted M110S to i9000 use I9000GSMH and will not indicate the FCC or SSN
yours says its an i9000T and there is such a model, look http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/GT-I9000T
so best to check your IMEI number , follow this link to identify your model
anyway so long as your phone works its not a serious problem, but wrong ROMs can give you differing problems so ensure your unit is M110S before using solutions in PIT STOP
Click to expand...
Click to collapse
The IMEI site says my IP is blocked. I tried proxying but still doesn't give me the result.
What about the internal memory problem? And sd-card not reading!!
How do I solve that?
akhrot91 said:
The IMEI site says my IP is blocked. I tried proxying but still doesn't give me the result.
What about the internal memory problem? And sd-card not reading!!
How do I solve that?
Click to expand...
Click to collapse
Already mentioned in earlier post, look in PIT STOP for guide to solve internal SD card problems
Try this links to check iMEI
xsenman said:
Already mentioned in earlier post, look in PIT STOP for guide to solve internal SD card problems
Try this links to check iMEI
Click to expand...
Click to collapse
Okay. And I went through your post in the PIT STOP for internal sd problem.
I just need help with installing CWM and getting root as I cannot install the kernel WF07 speedMode application on the phone as no internal or external card.
Thank you loads for your help!!
akhrot91 said:
I just need help with installing CWM and getting root as I cannot install the kernel WF07 speedMode application on the phone as no internal or external card. /QUOTE]
you need to post screen shots or the contents of
1) settings > about phone ??? all details
2) settings >storage ??? all details
for me to give you solutions
Click to expand...
Click to collapse
I hope the pictures are clear as I can't take screenshots because of Storage problems.
akhrot91 said:
I hope the pictures are clear as I can't take screenshots because of Storage problems.
Click to expand...
Click to collapse
ok, the ROM you had flashed is obsolete, you nee to flash WF07 ( download link in PIT STOP) but before you do that, go into settings>storage and erase SD card, and Format where possible also you must follow the instruction given in flashing guide ( First post concerning repair kit) to the dot, meaning you need to factory reset (settings >privacy) as well as wipe everything and format everything prior to flashing WF07 and also wipe again after flashing.
Only after this you should look at other problems ( Internal SD card)
Its also best to USE the repair kit again and after flashing Ist stage , flash the WF07 ROM ( its the best ROM for the M110S)
I write here to help me solve a problem with the mini s3 after turning not spend 30 seconds when powered down or rebooted ...
I did full wipes and reset from recovery and nothing .. I did the * 2767 * 3588 # either .. by odin I did a wipeI8190.md5 and nothing .. the cel turns back on as your last finished reboot .. in fact if I make a modification before they shut down or restart the phone back and not assumes the change .. and the USB debugging is not activated
I wonder if anyone happened to this and can help me.. the warranty is lost
thanks
First thing is to see if stock firmware in odin can help.
tys0n said:
First thing is to see if stock firmware in odin can help.
Click to expand...
Click to collapse
Yes is stock firmware.. theres no modificartion...
could manage to keep it active and enter the ram and select delete but when spend time the phone restart again, in fact delete all applications and messages and when I hes restart put everything back like used to be... and alsdo did the reset factory default and nothing hes restart over again with the same phone profile
flash http://megafiles.me/s/param_i8190-tar-md5 with Odin and reboot
JackoMJ said:
flash param_i8190-tar-md5 with Odin and reboot
Click to expand...
Click to collapse
also did that and still boot with the same configuration..
I'll make a video and I will upload to youtube
it seems is related to a material issue. i thought it's on your power button !
redomix said:
it seems is related to a material issue. i thought it's on your power button !
Click to expand...
Click to collapse
i dont think so.. i will post 2 videos showin the problem
here's the videos
is in spanish but i think is tunderstandable
youtube.com/watch?v=EZhKPInC5r4
and the second
youtube.com/watch?v=hT8e6T0ymJo
if you see in the last part of the second video i did the factory reset and the phone restart without nothing happend
i think you should flash TWRP or clockworkmod, make a backup of your files also the present rom,
After that, flash with a new rom like Cyanogenmod 10.2 from Maclaw and revert with the difference, maybe the problem will be fixed..
redomix said:
i think you should flash TWRP or clockworkmod, make a backup of your files also the present rom,
After that, flash with a new rom like Cyanogenmod 10.2 from Maclaw and revert with the difference, maybe the problem will be fixed..
Click to expand...
Click to collapse
i can not flash becouse the phone not assumes any changes.. with odin i flash in the PDA a recovery.img a CWM and nothing.. even im update from chache/fota upadte of recovery and he gave me this error...
img183.imagevenue.com/img.php?image=96227_20131210_231941_122_127lo.jpg
i think the problem that the phone no assumes anything with flashing is because is before hes broke or whatever happend to this F%$& is the USB debugging is not marked.. but i dont really now :S
try first flashing TWRP recovery.. can really help.. !
redomix said:
try first flashing TWRP recovery.. can really help.. !
Click to expand...
Click to collapse
can i do that without USB debbugin?
how can i see a tuto or something... im really new in this.. please...
you can do it with your android recovery, mount you internal or external sdcard with android recovery, download TWRP with zip format. and flash it within your android recovery with install.zip.
You can search on Youtube for tutorials.
redomix said:
you can do it with your android recovery, mount you internal or external sdcard with android recovery, download TWRP with zip format. and flash it within your android recovery with install.zip.
You can search on Youtube for tutorials.
Click to expand...
Click to collapse
men you see the videos? i cant put the USB debbugin mode plus everytime then i flash anything on the phone when he reboot the phone no make any change. still the same like you see in the 2 videos that i post on the other messages..
thanks for trying to help.. :good:
Hey Brother,
Very Welcome, yes i've seen the videos, try to mount the internal sdcard with android recovery and copy the twrp recovery, or use another phone and copy the twrp file onto external SD Card, there's an option on recovery called update.zip flash with it,
if there's no change at all, try to flash it with ODIN.. if it don't recognize due to absence of USB Debugging, there's a tool called Samsung GS3 Mini ToolKit. maybe can help you. if not try with samsung KIES .. if also nothing helped you at this point, search around the internet for your problem, maybe you can find some useful help..
Cordially, I.R.
redomix said:
Hey Brother,
Very Welcome, yes i've seen the videos, try to mount the internal sdcard with android recovery and copy the twrp recovery, or use another phone and copy the twrp file onto external SD Card, there's an option on recovery called update.zip flash with it,
if there's no change at all, try to flash it with ODIN.. if it don't recognize due to absence of USB Debugging, there's a tool called Samsung GS3 Mini ToolKit. maybe can help you. if not try with samsung KIES .. if also nothing helped you at this point, search around the internet for your problem, maybe you can find some useful help..
Cordially, I.R.
Click to expand...
Click to collapse
hey men.. take a look at thsi image
img183.imagevenue.com/img.php?image=96227_20131210_231941_122_127lo.jpg
this is what happend when i do the update.zip..
im searching all over the internet and anybody has put som help.. in fact this is the 3rd forum that i put this problem...
thanks again..
foxdie99 said:
hey men.. take a look at thsi image
img183.imagevenue.com/img.php?image=96227_20131210_231941_122_127lo.jpg
this is what happend when i do the update.zip..
im searching all over the internet and anybody has put som help.. in fact this is the 3rd forum that i put this problem...
thanks again..
Click to expand...
Click to collapse
actually its really simple to solve this problem...
1 - download and install the samsung drivers from here (http://get.maclaw.pl/?id=61)
2 - download odin here and install it.
3 - reboot your pc (this is the easy way to kill all kies processes and unwanted things) and make shure that kies dont start with windows.(if you have it installed)
4 - download this http://get.maclaw.pl/?id=301 (its the maclaw cm 4.4.2 for odin with the recovery twrp)
5 - flash the phone with odin(FOR THIS YOU NEED TO BOOT THE PHONE IN DOWNLOAD MODE, just boot the phone pressing POWER+VOLUME DOWN AND THE HOME BUTTON until a triangle and a warning appears follow maclaws guide -> http://maclaw.pl/installation-guide-golden/)... as soon as the flash finishes you'll be trapped in a boot loop (missing GAPPS)
just try to boot it the system should crash dont worry you're on the good way.
5.2 - remove the battery and put it back in (now you phone should be off)
6 - reboot on the new recovery that comes with the maclaw Rom you've just flashed for that you need to press POWER + VOLUME UP AND HOME BUTTON and mount you SD CARD.(you phone sould appear on you pc as a storage device or something like that)
7 - download this GAPPS here(http://get.maclaw.pl/?id=164)
8 - copy the downloaded GAPPS to you phone.
9 - go back to the 1st menu of the TWRP (a.k.a recovery) and you should see a thing saying install zip or flash zip (something like that)
9.2 - select the Gapps you've downloaded and flash it.
9.3 - after the flash finish select reboot system
9.4 - phone should start installing updates after the reboot
10 - wait until it finishes and the problem should be solved. now you can go back to the stock rom or stay with this rom.
the problem here is there's an app causing that problem. i had the same problem a few months ago.
the phone whould just crash or not function at all, rebooting all the time or from time to time...(it was one of the games i've installed from market)
after the phone is working dont install apps from unknow developers. even if it is from the market (believe wen i say you can get apps from the market that makes you're phone to malfunction).
PTGamer said:
actually its really simple to solve this problem...
1 - download and install the samsung drivers from here (http://get.maclaw.pl/?id=61)
2 - download odin here and install it.
3 - reboot your pc (this is the easy way to kill all kies processes and unwanted things) and make shure that kies dont start with windows.(if you have it installed)
4 - download this http://get.maclaw.pl/?id=301 (its the maclaw cm 4.4.2 for odin with the recovery twrp)
5 - flash the phone with odin(FOR THIS YOU NEED TO BOOT THE PHONE IN DOWNLOAD MODE, just boot the phone pressing POWER+VOLUME DOWN AND THE HOME BUTTON until a triangle and a warning appears follow maclaws guide -> http://maclaw.pl/installation-guide-golden/)... as soon as the flash finishes you'll be trapped in a boot loop (missing GAPPS)
just try to boot it the system should crash dont worry you're on the good way.
5.2 - remove the battery and put it back in (now you phone should be off)
6 - reboot on the new recovery that comes with the maclaw Rom you've just flashed for that you need to press POWER + VOLUME UP AND HOME BUTTON and mount you SD CARD.(you phone sould appear on you pc as a storage device or something like that)
7 - download this GAPPS here(http://get.maclaw.pl/?id=164)
8 - copy the downloaded GAPPS to you phone.
9 - go back to the 1st menu of the TWRP (a.k.a recovery) and you should see a thing saying install zip or flash zip (something like that)
9.2 - select the Gapps you've downloaded and flash it.
9.3 - after the flash finish select reboot system
9.4 - phone should start installing updates after the reboot
10 - wait until it finishes and the problem should be solved. now you can go back to the stock rom or stay with this rom.
the problem here is there's an app causing that problem. i had the same problem a few months ago.
the phone whould just crash or not function at all, rebooting all the time or from time to time...(it was one of the games i've installed from market)
after the phone is working dont install apps from unknow developers. even if it is from the market (believe wen i say you can get apps from the market that makes you're phone to malfunction).
Click to expand...
Click to collapse
Good tutorial bro, this is the same what i'm talking about.. it should work with these method.. waiting your reply.
PTGamer said:
actually its really simple to solve this problem...
1 - download and install the samsung drivers from here (http://get.maclaw.pl/?id=61)
2 - download odin here and install it.
3 - reboot your pc (this is the easy way to kill all kies processes and unwanted things) and make shure that kies dont start with windows.(if you have it installed)
4 - download this http://get.maclaw.pl/?id=301 (its the maclaw cm 4.4.2 for odin with the recovery twrp)
5 - flash the phone with odin(FOR THIS YOU NEED TO BOOT THE PHONE IN DOWNLOAD MODE, just boot the phone pressing POWER+VOLUME DOWN AND THE HOME BUTTON until a triangle and a warning appears follow maclaws guide -> http://maclaw.pl/installation-guide-golden/)... as soon as the flash finishes you'll be trapped in a boot loop (missing GAPPS)
just try to boot it the system should crash dont worry you're on the good way.
5.2 - remove the battery and put it back in (now you phone should be off)
6 - reboot on the new recovery that comes with the maclaw Rom you've just flashed for that you need to press POWER + VOLUME UP AND HOME BUTTON and mount you SD CARD.(you phone sould appear on you pc as a storage device or something like that)
7 - download this GAPPS here(http://get.maclaw.pl/?id=164)
8 - copy the downloaded GAPPS to you phone.
9 - go back to the 1st menu of the TWRP (a.k.a recovery) and you should see a thing saying install zip or flash zip (something like that)
9.2 - select the Gapps you've downloaded and flash it.
9.3 - after the flash finish select reboot system
9.4 - phone should start installing updates after the reboot
10 - wait until it finishes and the problem should be solved. now you can go back to the stock rom or stay with this rom.
the problem here is there's an app causing that problem. i had the same problem a few months ago.
the phone whould just crash or not function at all, rebooting all the time or from time to time...(it was one of the games i've installed from market)
after the phone is working dont install apps from unknow developers. even if it is from the market (believe wen i say you can get apps from the market that makes you're phone to malfunction).
Click to expand...
Click to collapse
well men let me tell you the phone laguh hes ass off to maclaw TWPR hes reboot like before.. hes no assumes anychange... im little impress with this little piece of S%&T...
thanks for the tuto but dont work for me right now
i think is a service from google.. NLplocationreceiver. thats is the only one who`s dont start.. and keeps searchin
foxdie99 said:
well men let me tell you the phone laguh hes ass off to maclaw TWPR hes reboot like before.. hes no assumes anychange... im little impress with this little piece of S%&T...
thanks for the tuto but dont work for me right now
i think is a service from google.. NLplocationreceiver. thats is the only one who`s dont start.. and keeps searchin
Click to expand...
Click to collapse
thats strange at least for me that worked...
meybe you have a faulty memory?