Yesterday, I got a little too excited with rom flashing, and I ended up bricking my galaxy player. (Please note that I have The Galaxy Player 5.0 YP-G70) When I was done with screwing around with my player, I decided to try re-flashing the stock rom onto it. On odin, I got an error, so I unplugged the phone while it was still in download mode (with the android logo shoveling something) and I came to this screen:
{
"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"
}
After trying to go into recovery mode and pressing the side buttons in different combinations to see if it would go into recovery mode or download mode, my galaxy player turned off completely and will not turn back on at all now, even after plugging it into the computer and through the wall charger, it will no longer turn on at all. I'm assuming the battery died, but when I plug it in, nothing happens, it doesn't go back to that screen.
I'm hoping for some help. I can return it to best buy, according to what they told me when I bought it (that the warranty covers ANYTHING except for being lost or stolen)
BrassZeppelin said:
Yesterday, I got a little too excited with rom flashing, and I ended up bricking my galaxy player. (Please note that I have The Galaxy Player 5.0 YP-G70) When I was done with screwing around with my player, I decided to try re-flashing the stock rom onto it. On odin, I got an error, so I unplugged the phone while it was still in download mode (with the android logo shoveling something) and I came to this screen:
After trying to go into recovery mode and pressing the side buttons in different combinations to see if it would go into recovery mode or download mode, my galaxy player turned off completely and will not turn back on at all now, even after plugging it into the computer and through the wall charger, it will no longer turn on at all. I'm assuming the battery died, but when I plug it in, nothing happens, it doesn't go back to that screen.
I'm hoping for some help. I can return it to best buy, according to what they told me when I bought it (that the warranty covers ANYTHING except for being lost or stolen)
Click to expand...
Click to collapse
Hi there, I have exactly the same problem, but my player can turn on and just shows the phone -- ! -- computer logo. On my galaxy s i would take the battery out and then boot into download mode. But i cant figure out how to take out the battery... Any1 help us???
NamNamNom said:
Hi there, I have exactly the same problem, but my player can turn on and just shows the phone -- ! -- computer logo. On my galaxy s i would take the battery out and then boot into download mode. But i cant figure out how to take out the battery... Any1 help us???
Click to expand...
Click to collapse
The phone -- ! -- computer is forced download mode.
Sent from my YP-G70 using xda app-developers app
To ensure its now power, I would recommend leaving it connected to a power source for a day. It could be that since the device is low of power, it won't boot, simply because it might not have enough power to.
Considering how you've installed new roms, it could also be that the device won't charge and want to boot(ie teh firmware doesn't show the charge logo but boots the rom) when its connected to a power source. In doing so, it notices that it can't and loops, unknowingly
Not sure if this helps but hope you resolve it someway.
Please tell me how did you fixed your Galaxy Player 5 Ive the exact the same
UnsignedZero said:
To ensure its now power, I would recommend leaving it connected to a power source for a day. It could be that since the device is low of power, it won't boot, simply because it might not have enough power to.
Considering how you've installed new roms, it could also be that the device won't charge and want to boot(ie teh firmware doesn't show the charge logo but boots the rom) when its connected to a power source. In doing so, it notices that it can't and loops, unknowingly
Not sure if this helps but hope you resolve it someway.
Click to expand...
Click to collapse
Please, my friends, help me!
Samsung Galaxy Player 5.0 YP-G70 (with phisycal home button) bricked.
I accidentally flashed the rom to SGS-I9000B to the SGP 5.0 so it got bricked.
It's status is: doesn't turn on, doesn't enter in dowload mode (Volume down + Home + Power), doesn't show charging icon.
After weeks of exaustive researche, the only way I was able to enter in download mode was using the Adam's Outler procedure: Instaling Linux, Java, Oracle Virtual Box a version of Windows under VBOX, to run Samsung drivers and Odin after using Unbrickable Resurrector R40.
Well, using this procedure SGP 5.0 enters in downloading mode and when I use the PIT file and BootloadersOnly provided by Adam the result in Odin is PASS! Despite that SGP doesn't reboot and keeps the same way: doesn't turn on, doesn't enter in dowload mode (Volume down + Home + Power), doesn't show charging icon.
So I enter in download mode using Unbrickable Resurrector R40 again and try to flash several SGP 5.0 YP-G70 Intl ROMs: Stock Froyo, Stock Ginger Bread and some Customs ROMs most of them PASS in the Odin result BUT SGP 5.0 never reboots or turn on after the procedure.
I have a doubt of marking or not Re-partition in Odin, but the procedure just works if I mark it.
I feel I was close to resurrect it and make it work again but all I've got is frustration.
I'm not an expert as the major of you so I beg some enlightned soul show me the way to make it works: step by step and share with me the right files I have to use to make it works.
I also have installed Heimdall but I was not able to find the appropriate files to use it and SGP 5.0 can not have the batery removed. Someone wrote Adam has developed a tool for SGP full recovery but I didnt find it.
Please, folks, help me and I will share the solution with other people in the same situation.
Thanks and best regards.
Related
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...
I have tried everything on my wife's I9001 but I cannot get Odin to get past SetupConnection.
Here is a picture:
{
"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"
}
I have tried:
Redownloading Odin 1.3 and 1.85 and also tried using Multi Downloader 4. (Which says that the .md5 file isn't supported).
Changing USB ports.
Using a Jig to boot Download mode.
Booting into Download mode normally.
Installing MobileODin except that I9001 is not supported.
Trying to flash a different rom other than 'I9001XXKQ1_I9001XXKPI_I9001DBTKP1_HOME.tar.md5'
Rebooting the computer over 9000 times.
Rebooting the phone over 9000 times.
Pulling the battery over 9000 times.
Reinstalling the drivers from Kies.
Turning USB Debugging mode off (was worth a try)
Using a different computer.
Reinstalling my OS (seriously, I had to do that anyway)
Leaving the phone plugged in for 30 minutes anyway just to see if it was working but not updating.
I am unable to boot into 'Recovery Mode' also the phone sh!ts itself and boots into 'RAM Dump' instead... where it requires a battery pull to reboot. So I can't even put the rom file on the internal memory and use recovery mode to flash it from there...
Basically nothing works at all. Odin 1.35 fails, Odin 1.85 fails, Multidownloader fails. I have tried rebooting, restart, and re-bloody everything I can. I have no idea why it won't get past setup connection. I've even tried using my second USB cable. It used to work fine, I used to be able to flash the phone fine.
Kies is NOT running in the background... there are no processes open or anything. I have googled and yahooed and everything to find a solution to this. NOTHING works..
Please help. I need to flash this dhfshfgdshgfshs phone as soon as possible. It's not working properly and it's really unstable..
If someone has any suggestions I am so willing to hear them..
Thanks a lot. - From a really frustrated dude
leijonasisu said:
I have tried everything on my wife's I9001 but I cannot get Odin to get past SetupConnection.
Click to expand...
Click to collapse
When you booted your phone, are you REALLY sure that you go into Download-mode?
When i was doing the same thing as you, i just enter Android Recovery (pressed Home+Vol Up+Power instead of pressing Home-Vol DOWN+Power)
Im not sure what buttons on your phone because im having a Note.
If you find this helpful, you could click Thanks
Thanks mate but I worked it all out. For some reason my I9001 wasn't being flashed in Odin properly like I explained. I accidentally screwed up my download mode. Sometimes I could get into Download mode by holding the corresponding keys. Volume Down + Home + Power. Sometimes the phone would just go black with a white dot at the top left corner.
Using a Jig I was able to boot into download mode without hassle. I then used Multi Flasher 4 to flash my phone seeing as no matter what Odin 1.85 and 1.3 would not work.
After that I did a factory reset so the phone was basically flashed twice. Everything seems to work well now. Before the factory reset the phone would just get into a boot loop.
Thanks anything. FeMod or whatever the clockworkmod for the I9001 is, wasn't working either. It would just go blank when I chose an option.
It's ok now. Thanks anyway but this can be closed.
Make sure Kies is not running. That was preventing me from connecting. :good:
Odin and xdadevelopers suck
Odin is buggy. Works on and off.
xda sucks because the owners of the site will have a single applicatoins dependencies spread across as many pages as possible in order to increase views and click through rates and sell ads to say, Bell Telecom perhaps?
F*n dicks at xda far as I'm concerned.
Wasting everyone's time and polluting the search results space.
Amen.
just do that
just enable usb debbuging
thanks
edwin_chenyh said:
Make sure Kies is not running. That was preventing me from connecting. :good:
Click to expand...
Click to collapse
Thank you alot bro. i was searching problem about half a year. you saved my life
I have the same issue with my Samsung Galaxy s2 (GT-i9100).
- Yes, Its really in download mode
- Have tried alot of diffrent versions of odin
My phone suddenly stopped working, can't start recovery and it doesnt boot at all.
The only thing I can do with it now is to enter download mode.
I might have flash something bad... dont really remember at all.
Had kies installed both the first version and klies3, all uninstalled now without any change...
THX
you're great, thank you very much bro : Iyi:: Iyi:: Iyi:
Hi i have n915f samsonge note edge after last update very restart or frizz when i work whit and go on downloading mode with out i press any key.i go recovery mode and wipes cach drive and restart on factory but Dissolving problem.when i want flash whit odin and turn on debugging mode not turn on my phone but when put cabe onit and hold power+Home +and volum key go on downloading mode.and detects with odin but when start stuck on setup connection.
Please help me.
As this time-lapsed gif indicates, my phone is stuck in an endless boot logo - recovery loop.
I was on official Sammy 4.3 and decided to reboot to recovery when I encountered this. The recovery at that time was Philz 5.18.5 and I was incidentally rebooting to recovery to flash Philz 6.
The following has no effect:
1. Long press of power button (8 secs) for shutdown and reboot
2. Key combination for reboot to recovery
3. Pulling out the battery and then booting up the phone
4. Connecting the charger with the phone in off mode
I have been able to go in to Download mode which I suppose will enable me to use Odin, but I quite some time away from being able to do that. So any ideas anyone?
{
"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"
}
Sounds like a partition is corrupt, if it won't boot to recovery then nothing else to try except odin.
Sent from my GT-I9300 using Tapatalk
t3chg33k said:
As this time-lapsed gif indicates, my phone is stuck in an endless boot logo - recovery loop.
I was on official Sammy 4.3 and decided to reboot to recovery when I encountered this. The recovery at that time was Philz 5.18.5 and I was incidentally rebooting to recovery to flash Philz 6.
The following has no effect:
1. Long press of power button (8 secs) for shutdown and reboot
2. Key combination for reboot to recovery
3. Pulling out the battery and then booting up the phone
4. Connecting the charger with the phone in off mode
I have been able to go in to Download mode which I suppose will enable me to use Odin, but I quite some time away from being able to do that. So any ideas anyone?
Click to expand...
Click to collapse
Maybe this is SDS, its time to send your SGS3 to Samsung for repair(getting new motherboard)..
Can u go into download mode or not(i did't understood what you said earlier), if you can go into download mode can you please tell what is there in Product Name. if its GT-I9300 and everything else is fine there than try to flash firmware from odin..
suyash1629 said:
Maybe this is SDS, its time to send your SGS3 to Samsung for repair(getting new motherboard)..
Can u go into download mode or not(i did't understood what you said earlier), if you can go into download mode can you please tell what is there in Product Name. if its GT-I9300 and everything else is fine there than try to flash firmware from odin..
Click to expand...
Click to collapse
From what I had read about SDS, the phone ends up being so very dead that it doesn't even show the boot logo. In my case, Download mode is the just about the only thing that I can currently enter in to; so I guess there is no other option now.
t3chg33k said:
From what I had read about SDS, the phone ends up being so very dead that it doesn't even show the boot logo. In my case, Download mode is the just about the only thing that I can currently enter in to; so I guess there is no other option now.
Click to expand...
Click to collapse
In case of SDS boot loop also occurs some times and also some users are able to get into download mode but they find that the product name is blank or something else, have you checked your Product Name, that should be GT-I9300..
i just had the very same problem, although with philz 6.0....
Fortunately in my case (and i can bet in yours too) in download mode the phone model was correctly reported as gt i9300 so it wasn't sds (phew) and i could get my phone running again.
these are the steps i followed:
1) put the phone in download mode
2) open odin and connect the phone to the pc
3) load under pda stock rom of my country
4) let odin do it's magic till it says "pass"
5) at this stage my phone got stuck at the samsuing logo so
6) Turned the phone off and boot in to stock recovery
7) Cleared cache and data/factory reset
8) tada phone up and running again
9) Flashed custom recovery and custom rom again (we will never learn, will we???)
Hope this helped.
amigaoneit said:
i just had the very same problem, although with philz 6.0....
Fortunately in my case (and i can bet in yours too) in download mode the phone model was correctly reported as gt i9300 so it wasn't sds (phew) and i could get my phone running again.
these are the steps i followed:
1) put the phone in download mode
2) open odin and connect the phone to the pc
3) load under pda stock rom of my country
4) let odin do it's magic till it says "pass"
5) at this stage my phone got stuck at the samsuing logo so
6) Turned the phone off and boot in to stock recovery
7) Cleared cache and data/factory reset
8) tada phone up and running again
9) Flashed custom recovery and custom rom again (we will never learn, will we???)
Hope this helped.
Click to expand...
Click to collapse
Yeah, Odin saved the day. A simple flash got the phone going again without the problems that you had with the phone getting stuck at the boot logo. But yeah, we never learn; immediately flashed Philz 6 and Temasek's CM11.
Please help me
Hope your phone can boot into fastboot mode.
Download and Flash the TeamSpain 15S recovery from here
Boot into fastboot mode. Turn the Phone off -> Power on using (Power button + Volume down). Connect to your PC and make sure Fastboot drivers are installed.
Pass this command fastboot flash recovery TWRP5.8TeaMSpaiNRevolution_15s.img assuming the recovery img file and fastboot are in the same directory.
Boot into recovery by pressing (Power + Volume Up) button combo. If you get Blue Led of Death, keep Power + Volume Up buttons pressed till phone boots into recovery.
Download TeamSpain Revolution 15s EUI ROM from here
In TWRP, Adb sideload the above rom.
Thank you I will try
Thank you I will try. please help me.
Can you tell me any detail.
Can you tell me any detail.
jakkapongjames said:
Can you tell me any detail.
Click to expand...
Click to collapse
What detail?
I change rom from model china x820 to indian x821. I try install TWRP but my devices just booted to a black screen with the blue led. I can try many method but doesn't work. it's show only quadcomm driver. what should i do?
{
"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"
}
Hi my le max 821 is also soft bricked can any one help please? It is going to fast boot mode, i have tried installing TWRP. It has shown that twrp has been installed, but when i tried to get into recovery it is showing a flashing blue screen and immediately the entire screen is going dark. Please some one guide me. Thanks in advance.
AJJU1972 said:
Hi my le max 821 is also soft bricked can any one help please? It is going to fast boot mode, i have tried installing TWRP. It has shown that twrp has been installed, but when i tried to get into recovery it is showing a flashing blue screen and immediately the entire screen is going dark. Please some one guide me. Thanks in advance.
Click to expand...
Click to collapse
You need to flash the correct recovery for 15s firmware. It is from TeamSpain.
Follow the instructions from this post. Click here.
sanke1 said:
You need to flash the correct recovery for 15s firmware. It is from TeamSpain.
Follow the instructions from this post. Click here.
Click to expand...
Click to collapse
Thanks Mr. Snake 1, will try this one and let u know the result.thanks again.
AJJU1972 said:
Thanks Mr. Snake 1, will try this one and let u know the result.thanks again.
Hi snake i tried this but no luck. But the good thing happened to me is, that after a long time i am able to get into the recovery. the "twrp" is working fine. I have downloaded the CM13 rom from your 'mega' link and adb sideloaded it, but it is not booting into the system, rather getting into boot loop again. The same blue screen is flashing and going dark, as earlier.
Can you please guide me, what am i doing wrong. I tried formating the system partition also(lost the stock rom also). Waiting for your respond. Thanks.
Click to expand...
Click to collapse
Hi snake i tried this but no luck. But the good thing happened to me is, that after a long time i am able to get into the recovery. the "twrp" is working fine. I have downloaded the CM13 rom from your 'mega' link and adb sideloaded it, but it is not booting into the system, rather getting into boot loop again. The same blue screen is flashing and going dark, as earlier.
Can you please guide me, what am i doing wrong. I tried formating the system partition also(lost the stock rom also). Waiting for your respond. Thanks.
AJJU1972 said:
Hi snake i tried this but no luck. But the good thing happened to me is, that after a long time i am able to get into the recovery. the "twrp" is working fine. I have downloaded the CM13 rom from your 'mega' link and adb sideloaded it, but it is not booting into the system, rather getting into boot loop again. The same blue screen is flashing and going dark, as earlier.
Can you please guide me, what am i doing wrong. I tried formating the system partition also(lost the stock rom also). Waiting for your respond. Thanks.
Click to expand...
Click to collapse
You have flashed 15s recovery and booted into CM ROM which is based on 14s or vice versa.
If you have flashed 15s recovery from TeamSpain, make sure that you flash CM ROM which is based on 15s or 16s only.
sanke1 said:
You have flashed 15s recovery and booted into CM ROM which is based on 14s or vice versa.
If you have flashed 15s recovery from TeamSpain, make sure that you flash CM ROM which is based on 15s or 16s only.
Click to expand...
Click to collapse
Thanks Mr. Snake1 finally i got my mobile working after a long time. Testing weather or not all the features are working. Post again with the results. Thanks a lot for your support.
Leeco le max 2 dead without system ...
good personal afternoon, I'm new here and I need help, I have a le Leeco max 2 and he came into loop after a atualizção for rom cuoco92, there installed TWRP the temspain downloaded the rom also the teamspain 15s and do the procedure by adb sideload and sometimes the protocol fail or lock in 47% already tried in every way to recover the device, tried to at OTG more this TWRP does not recognize the OTG cable, can anyone help me give me a light please, I'm the device locked to 1 month ...
A fix for hard brick you can find here http://www.letv.re/topic/1471-unbrick-le-max-2-qfil-rom/
Got the same problem but much worst.
I kind of have the same problem. But its different in its own way. The phone would turn off on its own. And soft brick for maybe 2-3 hours. And then unbrick it self. Meanwhile when u turn it on, you can feel the vibration of the device turn on, but no life on screen. When It does turn of it has the chance to turn on, show the "super powered by ecosystem" and then a blue square would cover the center of the screen. After that ur forced to turn it off again. And turn it back on hoping it won't brick again. When it does turn on normally, there is a chance it would just randomly power off and brick.(even if you are playing a game or browsing the web), I don't know if its hardware problem or software problem. (Btw iam typing this on a note pad so if the phone does brick, I don't have to type again.) It be great if you guys can help me out
I think my device is pretty much done for, I suspect some hardware related issue, but maybe some of you wonderful people here (if there still is anyone here) could still help me.
So somehow my M4 Aqua suddenly bricked without my interference, I had been using it regularly in the morning and at noon time, when I wanted to check on it, it simply wouldn't turn on or display anything at all. Even after pressing all the buttons for a considerable amount of time, no reaction occurred, the screen remained black. When I forcibly shut it down using the button next to the SD card slot, I seem to could get it on by using the power button, but the device doesn't seem to boot at all. All it displays is the Sony Logo, no bootloop, just the Sony Logo even for hours, presumably until the battery runs out.
Yes, my phone was rooted (using files from maybe this or this guide, can't really remember) even though I haven't been taking advantage of it, all I basically did was automatically denying SU permission for Link2SD which I had installed. I also should have the custom TWRP recovery, but I cannot access it, it leads to the infinite Sony Logo every time. As I initially rooted the device, I had to flash a new stock firmware which might not be suited for my device. (I honestly had no clue what my exact model was, if it was a E2303 or E2306 or whatever, but didn't bother much since the new firmware worked just fine for months)
Even when I simply want to charge the device, the generic battery symbol won't appear anymore, instead being also replaced by the aforementioned infinite Sony Logo. If I unplug the USB, the red LED light and the Logo persists which lead me to think that the device somehow freezes mere seconds after startup.
I have also noticed that the M4 Aqua takes suspiciously long to force shut down, I have to press the little button for ~15 seconds for the screen to go black, when it really should be about 5. I have thus removed the back case to fasten the process by removing the battery directly. (Did that break something?)
I can connect my phone in fastboot mode to the PC, but it seems to freeze yet again. I can perform various actions in Flashtool, but it doesn't seem to affect the M4 Aqua, when I try to restart the phone into system for instance, Flashtool doesn't report any errors, but nothing happens to my phone. Just how the red LED persists, the blue light does too when disconnecting from the PC until I forcibly shut down the Xperia.
Flashing a new firmware is not possible as neither Flashtool nor Xperia Companion recognize the device in flashmode even if the green LED clearly lights up. Like the other LEDs, this one also persists after disconnecting from the PC. I have been using Flashtool Version 0.9.32.0 first and then downgraded to 0.9.23.1 since that one came with the firmware I had installed, but to no use.
All this leads me to suspect a hardware issue, likely with the RAM (both sticks failing simultaneously) as I gathered from other threads and posts on the internet that that is a problem with the M4 Aqua. The CPU overheating is also an often cited problem, but I think I can rule that out. I have tried to cover the back with my hand absorbing the heat, slightly bending the phone and even put it in the freezer, but nothing changed at all. I have removed the SD and SIM Card to check if they were faulty too.
Since you opened the rear casing from the device, can you find anything unplugged or odd inside the device?
No, at least to my inexperienced eye there is nothing in particular. (Maybe you could distinguish anything on these poor quality pictures.)
{
"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"
}
I have noticed, however, that there seem to be connectors on the case itself, but pressing the case harder from behind doesn't yield any different results.
The red cable is responsible for the display, as it won't turn on once removed. The phone won't do anything (no vibration, no display) once the blue cable is disconnected.
Can you try to not boot it with the sd card installed in the device? I had a similar issue but in a different phone and when I remove the sd card, it boots just fine.
Also it doesn't seem that anything is out of place in any of those photos.
As I have mentioned in the original post, I have already removed the SD card and also SIM card, but it still refuses to properly boot.
Since it tends to freeze when using flashtool, can you try disconnecting and reconnecting the charging port or inspect your cable to see whether the cable is the culprit since I also had the same issue regarding connecting to flashtool.
Nope, I've tried two different cables and every other USB port my PC has to offer, it's still not connecting.
I have noticed something however while charging my phone up. (The Battery was completely drained since I wanted to check if something would change if I just kept the device running) While on low Energy (I was also charging with a different cable), a generic low Battery symbol appeared occasionally. The red light also behaved as it should, turning off when the phone was unplugged. Flashmode as well as Fastboot were naturally unaccesable though and after the battery was charged a considerable amount, I ran into the same issues.
Unless you meant the USB port of the phone itself, that one I haven't touched yet (I haven't removed the screws, but it doesn't seem too disconnectable anyway).
Have you installed drivers for flash tool application? Because without those the device doesn't connect.
Yes, I have. I have just reinstalled them from the Flashtool-drivers.exe in the Flashtool files, still same behavior. Connects in Fastboot, but not in Flashmode.
Then can you try installing cubbins android 11 ROM for this phone? You need to have fastboot drivers and adb installed, but if it does manage to boot, then there is a good chance that you can revert it back to stock and also having your flashmode function working again. Not sure if it works, but do give it a try
Hm, everything is able to flash successfully except "boot.img". Seems like the boot sector is inaccessible, I get the following error:
"error: Couldn't parse partition size '0x'."
Edit:
Nevermind, using
fastboot flash:raw boot boot.img
I was able to successfully flash it too, however it still doesn't seem that anything has changed.
can you boot into the OS at least?
if it booted, then you can use fast boot to flash TWRP and from there wipe everything (except internal storage). Now try to see whether it can boot to flash. If it doesn't boot in to it, then try wiping internal storage I guess? And if that also doesn't work, I'm out of options to fix that issue, probably it was a hardware issue in the first place.
Yeah, the problem seems to persist. I have left it on for over an hour now and my phone still doesn't show a sign of booting or more than that Sony Logo on a white background at least...
Even if you couldn't solve the issue, thank you very much for trying to!
It isn't too big of an issue, I was hoping to save some internal data, but much of it is on the SD card anyway due to the very limited internal storage of my device.
Mimi1001 said:
Even if you couldn't solve the issue, thank you very much for trying to!
Click to expand...
Click to collapse
Your welcome
I have a similar problem with my ex-phone, it was practically unusable after installing a rom that screwed up my existence, almost everything stopped working, and my pc doesn't recognize the fastmode, I can't flash the original rom or anything like that. If you know of something that could help, would you do me a favor!
Same issue here. The phone suddenly refused to boot. This is not after flashing anything to the phone. I haven't modified the software in the last x years. I was running stock with root. As soon as it boots, it freezes.
Flashmode does not respond, the pc does not recognize any devices is being connected.
Fastboot is pretty similar. However, the pc promptly picks up fastboot from being connected and then disconnects again. I tried like +/-20 times with fastboot and was able to get it run fastboot -w (once) and then flash Cubbins A11 but no change. I had to type all commands at once. One by one didn't work, it disconnected after the first command you execute (if you get the chance to execute a command).
I still had a TWRP recovery on there but no button combination or command let's me boot to that. It freezes at the white Sony logo. There is also this 3 button press and hold combination where it vibrates 1/1/3 times if you hold it long enough. It does not seem to affect anything.