I have tried the LG update software, nothing detects the phone, it instantly boots into emergency mode hoping I have not bricked the phone. This all happend while trying to downgrade the baseband and it just stopped at about 25% and stayed there for ten minutes, I attempted to reflash and the same failure happend, I then rebooted the phone and it has been in emergency mode since then with no detection at all.
did you flash a custom rom? or were you using the stock lg rom
try use other usb port ???
T_D_H said:
I have tried the LG update software, nothing detects the phone, it instantly boots into emergency mode hoping I have not bricked the phone. This all happend while trying to downgrade the baseband and it just stopped at about 25% and stayed there for ten minutes, I attempted to reflash and the same failure happend, I then rebooted the phone and it has been in emergency mode since then with no detection at all.
Click to expand...
Click to collapse
if using lgmdp the latest method or via kdz these link can help
http://forum.xda-developers.com/showthread.php?t=1038338
http://forum.xda-developers.com/showthread.php?t=883314
http://forum.xda-developers.com/showthread.php?t=1060121
check downgrading ur phone detail just flash ur desired android version.
if sucessfull via lgmdp(latest method) search threads for lgmdp method or use kdz which solved all probs.
Try to enter emergency mode with vol up + back key + power button (not just power button) and then connect it to usb.
I have tried the kdz(after emergency mode issue) and lgmpd method already as it was required for the baseband flash the first time, I have clockworkmod recovery installed and cannot boot to that, was downgrading the baseband so I could go back to using CM7, as we speak I tried using CDMA setting in KDZ and I seem to have gotten a response, will update with whatever method works to unbrick
well after using KDZ method in CDMA mode, with shaking the phone, crossing fingers toes arms legs and eyes, I flashed riginal firmware and unbricked my phone, thank you for the links, after about 8 different pages I managed to get it working thank you all
T_D_H said:
well after using KDZ method in CDMA mode, with shaking the phone, crossing fingers toes arms legs and eyes, I flashed riginal firmware and unbricked my phone, thank you for the links, after about 8 different pages I managed to get it working thank you all
Click to expand...
Click to collapse
glad u solved it I knew it will . enjoy flashing!
i was writing iho recovery and my phone stuck at lg logo, runing kdz, in emergency but pc can't find my phone...
afrey said:
i was writing iho recovery and my phone stuck at lg logo, runing kdz, in emergency but pc can't find my phone...
Click to expand...
Click to collapse
try 3 button combo home+vol down + power and see if it comes out of lg logo and boot
I'm stuck in the Emergency Mode!! yellow screen with my P500 too.
I tried with KDZ Updater in all possible combinations and got the error "Upgrade error WParam:100. LParam:502" at each attempt.
I tried these rom's: V10A_00.kdz, V10B_00.kdz, V10E_00.kdz, V20B_00.kdz.
With LGMDP THUNDER v1.5, but I run into this error, after pressing the Start (write ROM button): Error! Partition Table.
Help!
I opened a dedicated topic here http://forum.xda-developers.com/showthread.php?p=17307504#post17307504.
Try to skake it 10 20 times.
I know it sounds weird but it did for me.
Sent from my LG-P500 using XDA App
Hello, my P500 is not detected any more by computer!
I looked over the internet and it seems a hardware problem. The phone is charging but cannot be detected as hardware. Unfortunately to resend it to warranty I must first remove Superuser because I rooted my phone. Is there any way to install the firmware once again from the sd card? I cannot make it through a computer because as I said before is not detected. I have custom recovery installed: ClockWorkMode 5.0.2.0. I looked over this forum and found some custom Recovery Zips, but I don't know how to use it. Any idea please? I must get rid of root access so I can return my phone to warranty! Thanks!
Hi all,
On a regular P500 with stock Android 2.2, build FRF91, software version LG-P500-V10b, the yellow screen Emergency Mode!! appeared after a regular restart and would go any further. I couldn't connect this situation to any of the apps that were installed.
Also, on regular usage, the Emergency mode scrren may appear out of nowhere and the phone is off the network.
This phone is used by my wife, she's not a hacker, she just want's to sleep the baby with melodies from this phone.
If I let the battery out for more that 15min it will boot back the normal way, but it isn't seen by Windows, it senses the device when plugged in but it says "device unplugged"
I followed several guides in the forum, and I saw there are two ways of writing something to the device:
1. "downgrade" the phone to the original firmware, like here Guide for newbies - LG OPTIMUS P500
2. write a new ROM, like here [ROM] (OFFICIAL) [email protected]_2.3.3_v2- Power Menu +franco-kernel+New Boot+ How to Guide
My obvious problem is the phone not being seen by Windows. I started it on purpose in Emergency Mode with Vol up+back key+Power and it appeared in device manager as LGE Mobile USB modem #2.
First I tried to write a new ROM, like at point 2. above, with LGMDP THUNDER v1.5, but I run into this error, after pressing the Start (write ROM button): Error! Partition Table. Here is a screen shot.
The I tried the other option, to "downgrade" the phone to the original firmware, with KDZ Updater.
I found V10E_00.kdz, although I think I should use V10B but I didn't found it. Search on this forum is a pain because it works one time in a hundred (it says something about maintenance).
KDZUpdater did its job successfully but the phone rebooted and halted on "Android" screen, that's it. Then I removed the battery, powered it back up and, surprise, my friend the Emergency Mode!! is back again.
So this phone doesn't seem to be bricked, nor isn't stuck forever in emergency mode, but also is not reliable anymore because of the emergency mode appearing randomly.
Please, slap me in the face with a link saying "dude, search worked for me an here's the fix".
What I can tell you for sure is that I didn't saw the partition table error before on this forum.
hmm... try again with kdz with correct version and do all things again but wait until all works done. don't be so fast
and come here again and tell what happened
If it is stuck on android logo after flashing kdZ, take out battery and press voldown+home+power button to hard reset
Sent from my LG-P500
Indeed it was stuck on the android logo after flashing with KDZ. Hard reset worked!
Thank you! Thank you! Thank you!
After this I had Android 2.2.2 running, then I started LGMobile software updater Agent from LG PC Suite and it updated the OS to 2.3.3. After finishing, the phone rebooted to Emergency mode again, but I did another hard reset and now it works perfectly, it reboots properly.
I guess the root problem was a corrupt file system.
A little offtopic since we are at it. for you guys what proved to be the best rom/kernel combination for best battery life?
Thanks again!
Later edit:
New updates: the phone doesn't behave normally as it began above. Later after the update, I tried to connect the phone to Windows PC and surprise, it didn't saw it as it was supposed to, the problem encountered at the beginning of this post reappeared:
Device driver software was not successfully installed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Although I have the correct drivers, because when I connect a friend's LG P500 it is seen properly.
After this, I rebooted the device and, surprise again, it booted to Emergency Mode. I unplugged the battery and let it for a while, then it booted normally but still it isn't seen by Windows.
Is this a software (ROM/Kernel) issue or a hardware issue?
I mention the my friend's LG P500 has the same factory provided update with Android 2.3.3, build GRI40, soft version V20g, kernel 2.6.35.10-perf [email protected] #1 and it doesn't have any problems.
Update: I can not even charge the device after I power it down. When I insert the charger, the emergency screen appears right away and it stays that way. I don't know even if the device is charging.
The workaround is to unplug the battery and leave it for 15-30 min or more and then it starts properly, but the problem in the post above is still present.
lmihaila said:
Update: I can not even charge the device after I power it down. When I insert the charger, the emergency screen appears right away and it stays that way. I don't know even if the device is charging.
The workaround is to unplug the battery and leave it for 15-30 min or more and then it starts properly, but the problem in the post above is still present.
Click to expand...
Click to collapse
Just try using froyo, dont upgrade to gingerbread, and see the problem still persist.
aspee said:
hmm... try again with kdz with correct version and do all things again but wait until all works done. don't be so fast
and come here again and tell what happened
Click to expand...
Click to collapse
What is supposed to be the correct version? I tried these rom's: V10A_00.kdz, V10B_00.kdz, V10E_00.kdz, V20B_00.kdz with KDZ Updater in all possible combinations and got the error "Upgrade error WParam:100. LParam:502" at each attempt.
terratrix said:
If it is stuck on android logo after flashing kdZ, take out battery and press voldown+home+power button to hard reset
Sent from my LG-P500
Click to expand...
Click to collapse
Now this doesn't work anymore, it starts into the Emergency Mode each time.
terratrix said:
Just try using froyo, dont upgrade to gingerbread, and see the problem still persist.
Click to expand...
Click to collapse
I can not flash any rom on it, it stays in the Emergency Mode screen. It is the same thins I mentioned to Aspee above.
Is my phone bricked?!
Now what?
My phone was acting wack so I decided to reboot and all of a sudden I saw the same screen that you are experiencing, but I just battery pulled and everything went back to normal. I have yet to experience this yet again though. (Running 6.5.7? CM7/Franco's kernel v19.?) Happened a while ago don't remember versions. I know I'm not much help but just saying I got this problem as well .
lmihaila said:
What is supposed to be the correct version? I tried these rom's: V10A_00.kdz, V10B_00.kdz, V10E_00.kdz, V20B_00.kdz with KDZ Updater in all possible combinations and got the error "Upgrade error WParam:100. LParam:502" at each attempt.
Now this doesn't work anymore, it starts into the Emergency Mode each time.
I can not flash any rom on it, it stays in the Emergency Mode screen. It is the same thins I mentioned to Aspee above.
Is my phone bricked?!
Now what?
Click to expand...
Click to collapse
if you have emergency mode theres always a chance your phone flash by kdz delete all drivers follow the tutorial on kdz and install the drives they provide and try more then one time because when hi the 1 and last time hi use lg mobile updater to update my phone it stop in midlle and hi was stuck in emergency mode,i tried a lot of times some times windows dont detect my phone others it do but kdz dont i dont count but only several times of tryng the kdz works...
but emergency mode random i never read or see in my phone if you get it work on froyo or gingerbrad and that still happens hi think you should go to warranty and say that in a midle of update byLG software your phone stay that way they will fix it....
Reminder: my phone boots to Emergency Mode after you power it off. While in emergency mode, if you unplug the battery it will boot the same way. If you leave the battery out for more than aprox 15 min, it will bot the OS it has written on it. Why??
After more an more hours spent on it I can conclude to this: my phone is to be seen by Windows only in emergency mode. I was able to flash it with KDZ while in emergency mode but with errors (Upgrage error: Wparam:100 LParam:6).
I was able also to flash it once with LGMDP but it stayed in the emergency mode screen and didn't rebooted itself, so again with an error.
I flashed it with both V10B and V20G and it behaves the same: while in Android, it isn't seen by Windows (with or without USB debugging) and if you reboot, it boots to Emergency Mode. Why??
it´the first time hi read something similar but if you cant or if you have a chance to try in other pc do it but if you cant leave that way take to lg center service and tell them that was making oficial update from their program and phone stuck like that they will fix it for free i dont now how to help you
I tried to connect the phone on three different machines, two Windows Seven and one XP. On XP I had the most success with flashing the phone.
sir lmihaila, i have the same problem. exactly the same. been following this thread since you posted it, still no solutions, got this phone cheap from a friend, it was on LG stock rom, not sure what he did on it, but it already was doing the Emergency mode.
i update a month ago to CM7, tried different kernels and roms, it was still happening on all of them, was about to try kdz, but then i saw your post saying it didnt work..
so until we found a solution, i guess we never turn phone off, or if it did, leave battery out, mine works out of Emergency mode after 5 mins of battery out.
bajie23, I'm glad you posted.
Indeed there is no solution yet, but I did some progress today. I played with the phone with it's battery unlugged and plugged his power adapter.
On a normal P500 the LG logo would appear and it would tell you to put the back cover and battery back. On mine, guess what, the emergency screen appeared.
But with a little knack, I pressed vol down+home+power and plugged the power adapter at the same time and the LG logo appeared as at a normal P500.
Then I inserted the battery, the device showed another wired attention triangle and Android System Recovery logo popped up, then I pressed Home and the Android System Recovery menu appeared. See pictures:
http://imageshack.us/photo/my-images/846/20110915230511.jpg/
http://imageshack.us/photo/my-images/16/20110915233836.jpg/
I could move trough the items in there with vol up - vol down but I couldn't press OK because none of LG P500 button did anything regarding this. I prepared even a new ROM on the SD card, renamed it to update.zip like in the Android System Recovery menu, but in vain because I cannot validate an action.
I exited this mode by unplugging the battery and power adapter,
I tried once again to enter Android System Recovery but I couldn't pass over the emergency screen anymore.
Just for the record, when you shake your phone do you also hear a little piece of something moving in the upper part of the device, right behind the earpiece? Does your handset has dropped marks? Has it ever been dropped, hit?
On my friend's functional P500 this noise isn't heard.
LS: bajie23, you said you tried different kernels and roms, how did you flashed them?
that was my first post. registered here just for this issue.
no moving parts inside, haven't dropped phone yet, no damage showing it has been..
i used clockworkmod recovery to flash - try to google it, there are tutorials, but i cant post links yet on this forum.
i installed recovery mode using "rom manager v4.3.1.3" app..
it simply instals recovery mode on start up. you can go to it by holding volDown+home+power. then vol up and down to navigate, menu button to select.
you can instal. zip from your sd using recovery mode.
problem is with our phone, booting in recovery mode gets you to that F&*%In "Emergency mode!" screen. you need to keep battery detached for 3-5 mins, put battery back then hold volDown+home+power, do not let go until the recovery screen appears.
you can instal kernels and roms using recovery mode, there are options to wipe the cache and everything, tried all of them, but guess what? still F^&*% "Emergency mode"
looks like our problem is deeper than the start up..
*next thing i will try is to revert back to original rom, try to unroot, and see if it helps, even though it doesn't appear to be on the rom or kernel.. then i'll try your step to see if i can get partition table error as well..
**i remember seeing on a site saying Emergency mode is like a test mode for lg that they use to flash..
Hi folks,
I have a Optimus One in the same condition. I tried to update Android to Gingerbread using the LG software and now it's pretty much always in "Emergency mode". I'didn't find any way to flash it again even with the stock rom. It seems that the usb port is not working correctly...
I'm using this procedure to let my P500 boot in "normal" way, and so far it seems to be working:
1) while the O1 is in Emergency mode, and the battery is almost fully charged, connect the charger a few minutes, let's say, 3 -5 min.
2) after that, remove the charger plug AND the battery
3) replace the battery on the phone
4) press the power button for 1-2 sec.
The phone should boot normally.
This procedure doesn't solve the "emergency mode" issue, but at least makes the phone usable.
Update: this procedure isn't working now!
I got this problem, too.
Bought LG P500 on 12nd november, updated to GB 2.3.3, no problems for 20 days.
Then trying to connect to PC I notice that it couldn't see it, nor SD and the phone, too.
After connecting to USB if trying to reboot the device it goes into emergency mode.
After pulling off the battery for 5 minutes it reboot normally but it is still not seen by the Pc.
After removing the battery and booting normally if I try to reeboot again in goes normally.
So I suppose that there is something conflictting connecting to usb that avoid to boot until memory cleared (battery removed).
I sent the device to LG, yesterday, hope they solve the problem, usb issue?
What about you?
partition table error is due to missing of partition.mbn file during selection of files to flash.
to install custom recovery you can follow http://forum.xda-developers.com/showthread.php?t=1318750 (partition file is included here use it if u want for some other purpose, it will be same for p500/optimus one as far as i know)
then flash rom from recovery follow http://forum.xda-developers.com/showthread.php?t=1309744
And if you are stuck at boot logo after flashing rom then factoryreset/format from recovery.
aFTER booting into rom if you see no gsm signal then upgrade baseband using http://forum.xda-developers.com/showthread.php?t=1217504
or
flash any other stock rom http://forum.xda-developers.com/showthread.php?p=19006040#post19006040
or
http://forum.xda-developers.com/showthread.php?t=1324105
mak.3736 said:
partition table error is due to missing of partition.mbn file during selection of files to flash.
to install custom recovery you can follow http://forum.xda-developers.com/showthread.php?t=1318750 (partition file is included here use it if u want for some other purpose, it will be same for p500/optimus one as far as i know)
then flash rom from recovery follow http://forum.xda-developers.com/showthread.php?t=1309744
And if you are stuck at boot logo after flashing rom then factoryreset/format from recovery.
aFTER booting into rom if you see no gsm signal then upgrade baseband using http://forum.xda-developers.com/showthread.php?t=1217504
or
flash any other stock rom http://forum.xda-developers.com/showthread.php?p=19006040#post19006040
or
http://forum.xda-developers.com/showthread.php?t=1324105
Click to expand...
Click to collapse
I had this problem (not the partition table error) not after a flashing but after 20 days past the flashing, before everything was well.
What can be happened?
I realized that there is something wrong with some LG500 motherboards, regarding USB connections. I too tried to flash the phone using LGMDP but I always got the partition table error. My phone, either in Emergency or in normal mode, is always recognized by the PC thru the USB, but when it starts to communicate it locks ... I cannot flash anymore, and actually it seems that USB port is useless.
I know that there are some special cables, apparently suitable for LG500 too, that can set the device in "download" (emergency?) mode, they use a 130k resistor somehow. If this is real, probably some motherboards are faulty, putting randomly the device in emergency mode, even without the mentioned cable. Pullup/pulldown resistor missing on MB? At first attempt to communicate, the USB controller of the phone locks, probably getting an undefined state. This is my impression.
Since my phone is still under warranty I settled to bring the phone to LG repair service...
Hi, i've a strange (but i hope common and resolvable) problem.
After all, i say that i searched through the forum (with the search function) but with the solution that i found and tried i didn't solve anything.
I start saying that i got a p500 with a broken sdcard reader board (it simply doesn't have a microsd 'cause doesn't recognize).
That phone some days ago just shut down and went stuck on the LG Logo.
I tried at first the hard reset (home+vlm down+pwr), nothing happens.
I tried then the recovery mode and try to update with lg updater, and didn't work, lg doesn't recognize the phone on the updater (but on the main screen of the BBc app does).
The last thing that i noticed is that one time, powering on the phone, button's leds flashed about 4-5 times. but if i try to re-do the action, doesn't get anymore.
I would know if there is another way to exit from this stuck-screen.
I also post the log of error i get from kdz:
Upgrade error
WParam: 100
LParam: 500
Here is the log: http://pastebin.com/4SECdaT4
Other things i forgot to say:
I don't need to shake the phone, if kdz doesn't detect, i take off the battery, and turn on the phone in emergency mode (up+back+pwr).
Sometimes kdz works without that error, but it reboots the phone and it stucks again in the lg silver logo.
I read about a wipe of /system through adb, but if i try to mound /system, i get the command list.
I can't do adb devices, doesn't detect the phone, and in sequence to this, can't open the adb shell.
any suggestion?
You recovery got corrupt when it was stuck on LG logo, which could be easily solved by fastboot method of recovery flashing.
I was on the same situation like you are on now. Now follow this:
Try booting into fastboot mode by pressing "Power+ home buttons"
If it does then notify me here or at PM.
Between this is not the appropriate section for this thread.
I tried to fastboot, i did fastboot erase recovery and fastboot flash recovery recovery.img commands, no errors, but when i type fastboot reboot, on the screen i read: rebooting the device, but it doesn't reboot. If i take off the usb cable, (after a big time, 10 mins for example), a --suspend-- appears.
if i take off the battery, the lg logo is stuck again, and if i do home+vol down+pwr the clockwork mod doesn't appear.. any suggestion?
See your PM
Sent from my LG-P500 using Tapatalk
Hi everyone, I have this weird problem with my S6500, or rather my younger brother has.
He tried to put on his S6500 (not D, this phone is with NFC) Cyanogenmod 10.1, after some ups and downs, he finally got it to work, but... camera wasn't working, it was said on the cyanogenmod page to flash with the newest update, he did that, phone worked good... almost, after he was blocking his screen, he couldn't unlock it, because there was some kind of white screen stuff, weirder was the thing, that he could hear all the *clicking* sounds as he was trying to unlock. He had to restart the phone every time after he blocked the screen, so he wanted the phone to function normally and tried to put his stock ROM back again. Well the flashing went well (as Odin showed) but the phone stucked in bootloop.
The phone showed the Orange logo (he is using his original stock rom from Orange Poland, downloaded from sammymobile) and then it quickly changed to Samsung logo, after that the phone vibrates once, and after that it vibrates 3 times really fast and restarts from the Orange logo.
He tried to get into Recovery mode, but coul;dn't (the phone doesn't react to any of the combinations we found - vol+,vol-, home and power and many others), and as I forgot to mention before, after every flash (while the recovery was working) he cleared data in menu of the recovery.
We also tried the different method to boot the phone into recovery mode (put it in Download mode, which works and then instead of going further by pressing vol+ we pressed the down button and held vol+,vol- and home button, but instead of going into recovery the phone booted in weird screen with small letters RAMDUMP MODE (ARM9 mode).
We tried several times to flash new recovery with Odin, but it doesnt work, the PIT file also doesn't work, or can someone provide me with the stock s6500 PIT file as I couldn't find one, because I read in the Polish forum, that screen mentioned before only shows up if there is a SuperUser app in the phone, so we need the PIT file to flush it.
So the problem is after flashing it with numerous cwm and original stock roms we couldn't get it to boot or to get into recovery menu, or get it working.
Also the hardware is all ok, as the phone is almost brand-new ( he got it from the Orange few months ago).
So help plz?
I have the very SAME problem with my S6500D. Same as described above.
Anyone has managed to fix this problem ? I have all needed tools.
Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Varjo said:
Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Click to expand...
Click to collapse
You can Try this:
1.) Pull out battery
2.) Put it in again
3.) Press Vol up + home + power
4.) When the Samsung Logo appears let it off
I think you press the Buttons too long.
I had the same problem!
S1ay3r666 said:
I think you press the Buttons too long.
Click to expand...
Click to collapse
i really tried everything, it's not working. btw with i am stuck at the very first image, where it says "samsung Galaxy sII GT-I9300".
i dont think it's just the way i press the buttons because i can reach it on my s1 and s2 without a problem, it's just not working on this device.
could some setting like "nand erase all" in odin help? in other threads there is sometimes mentioned that the internal file system might be screwed up and in those cases a simple odin reflash does not help anymore...
Nand erase will usually hard brick it. Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Click to expand...
Click to collapse
thx, but i already did that (multiple times) and flashing via odin always succeeds. then the phone reboots and is stuck at the first samsung galaxy s.. screen. twice i managed somehow to get into recovery (after flashing cwm6) but it then randomly rebooted.
and i dont think that the power button is stuck because when i am in download mode it is perfectly fine it never reboots itself unexpectedly.
Had a similar issue on my tab2 p3100. It all happened when I tried flashing a custom recovery from rom manager.
A bad flash of anything related to recovery or bootloader could be a probable cause.
I remember a knowledge share on one of the threads describing this issue and as mentioned on it all I had to do is this:
1) switch off the device and plug in the charger. This would light up the display showing you the charging status. The status has to show if at least your bootloader part of the phone is fine.
2) plug out the charger and immediately press the three buttons (home + vol up + power) get into recovery mode. This step has to work and help you get to recovery mode.
***Note : the interval within which this step has to be performed is too short since the display would turn off immediately as soon as you plug out the charger. A bit tricky too so you have to be fast. If this misses getting you into recovery, pull out the battery and put it back again. Repeat step1 and 2 again.
3) upon successfully getting into recovery, perform wipe data, cache and select reboot phone from option available on recovery again.
Allow the device to boot. This could take a while since you have performed a data wipe and may prompt for first time set up.
I was able to restore functionality on my tab after these steps and like ppl learn from their mistakes, I then learnt that recoveries and bootloaders are things that needs to be done with a pc only.
Worth a try if you have tried other alternatives and found no go. may help. Who knows..
all the best.
thats also not working. i tried to get into recovery since two days now...
i also tried the steps from this thread: http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
but again, after i flash the cf-root (successfully) the phone does neither boot into recovery by itself nor can i do it by hand...
its crazy... in download mode i can see the model number (GT-I9300) and i thought as long as the model number is there and i can enter download mode there should be a way to recover the device.
but i cannot think of anything to try that i have not done yet
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Click to expand...
Click to collapse
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Varjo said:
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gala...-help-t2737707
Same here, still didn't found how to fix it.. I guess our motherboard just died..
Howewer I have a solution that "almost" worked for me.
Get a stock firmware in odin and turn on Nand erase and T-flash
When it's done phone reboots and you'll see just "Downloading..." mode when you turn it on.
Then got to Kies and Select firmware recovery...
Enter s/n and model name and wait for the flash to complete.
With it , I got past boot logo and actually booted into android but the phone crashed because I guess I have a memory issue..
Well , gl. If you don't find anything else helpful , try going with this method..