I think I'm ****ed here, but maybe someone can help.
My s4 is still running the MDK boot loader, I was running the gpe 5.0 ROM, and all was well. I installed the xposed framework, and that seemed to be working fine. I was playing with my device in bed that night and it died on me. I assumed I had missed a battery warning and put it on the charger. None of the buttons are responsive. By removing and replacing the battery I couldn't get it to boot past the samsung/custom screen. I put it on the charger and woke to a phone call, phone was working fine for a few minutes, then the screen went black and I'm in the same position.
If I attempt to boot into fastboot (holding the correct buttons while inserting the battery) , the fastboot warning screen shows for a couple seconds and then goes black. If I attempt to boot into recovery the small blue text will show up in the top right then the screen goes black again.
Assuming I'm ****ed since I can't get into recovery or download mode for Odin. Anyone have any ideas?
Also... If I have to replace, droid turbo or nexus 6?
My daughter had an issue with her S4 that looks like it matches closely/exactly to your situation.
What i had to do to clear the issue up is as follows:
Download the correct Factory Image tar/md5 file OR If you backed up the original Image, locate that file.
Download the "Odin_v3.09" software.
Note: Not all the Odin software versions play well with all phones and the v3.09 always worked for me.
Place the phone in Download Mode.
Flash the correct Factory Image tar/md5 file (Select the tar/md5 file using the "AP" button).
Note: Be sure that the "Auto Reboot" and the "F. Reset Time" are the only Options Selected.
Now select "Start" and let Odin do it's magic.
Note: It is important that you NEVER interrupt the process!!!
Interrupting it can potentially do irreversible damage so before you press "Start", double check everything.
Once the Factory Image file was correctly uploaded, Odin will restart your phone.
This is what worked for me but always keep in mind that there are no guarantees it will work.
I really wish you luck!!!
It still shuts itself off when put in download mode, won't stay on long enough for me to do anything with Odin.
Just a thought... Try it without the battery in...
It sounds like a little water may have made it's way in the phone.
It takes only 1/2 a drop or less to create issues like arching power/signal, a little bit or more corrosion, etc...
Some phones also throw a fir or just die for no reason at no fault to the user...:crying:
I hope someone else on the forum can provide some additional options you can try.
Related
Long story short, my Vibrant got saturated in Diet Coke (don't ask...). Dried it all off, here is where we are:
1. When off and plugged in via USB cord, the charging battery icon displays on screen.
2. When turned on, phone will display Vibrant screen for a few moments, then go dark, then loop back to Vibrant screen, rinse, repeat, etc...
3. I am able to get into Recovery mode, however it gives me an "Unable to mount sdcard" error msg when I select reinstall packages. (Hence have been thus unable to access my Nandroid backups.)
4. Phone loads into Download Mode just fine, have tried flashing various ROMs including one of the various "stock" images out there and Eugene's Froyo that will not brick. ODIN detects phone, flashing appears to go fine, but no joy on fixing the issue.
Ideas?
themoebius said:
Long story short, my Vibrant got saturated in Diet Coke (don't ask...). Dried it all off, here is where we are:
1. When off and plugged in via USB cord, the charging battery icon displays on screen.
2. When turned on, phone will display Vibrant screen for a few moments, then go dark, then loop back to Vibrant screen, rinse, repeat, etc...
3. I am able to get into Recovery mode, however it gives me an "Unable to mount sdcard" error msg when I select reinstall packages. (Hence have been thus unable to access my Nandroid backups.)
4. Phone loads into Download Mode just fine, have tried flashing various ROMs including one of the various "stock" images out there and Eugene's Froyo that will not brick. ODIN detects phone, flashing appears to go fine, but no joy on fixing the issue.
Ideas?
Click to expand...
Click to collapse
there might not be a solution here...
When you drop a electronic in water, DO NOT TURN IT ON, the water gets into the main core, and messes crap up, but put it in a bag full of rice for a few days to dry out.
In this case, you DID turn it on, and didn't put it in a bag full of rice.
I'd say this is more of a HARDWARE issue than a SOFTWARE, so... if you have warranty, yay, if you don't, awww.
Sorry thats all i can help you with.
Actually I deleted that part... I DID try to turn it on... BUT I DID also leave it in RICE for several days after that fact. It it helps...
Attempt this odin,
Pit file ONLY 512 (stock) check repartition drive. Wait till it does rebbot and odin clears. Go back into odin uncheck the partition box and flash the PDA Jfd (stock) only no ji6 no pit file. Wait till it cycles thru and odin says "passed" lemme know if you make any progress.
Sent from my SGH-T959 using XDA App
Hello. I'm new to the forum, and the issue that brought me here as had me fulling my hair out of the last three days.
I'll try my best to make this short as possible. I have (obviously) AT&T Lg Optimus G (E970) that was running 4.0.4. i rooted and unlocked it and flashed a cm 10.1 using TWRP. Yesterday tried to flash a zip for a transparent status bar mod. But the flash resulted in CM getting stuck on the splash screen. So i booted in TWRP recovery mode to restore from a recent backup. In the midst of wiping my rom and going to restore, i guess my phone died (which was weird because it had a substantial charge). Then it would no longer power on, and the only was i could get ANY response was by plugging it on the charger. All i get it the red indicator light. my phone will only turn on when plugged into the computer. from there the only two thing i can do is enter download mode and boot. and when i try to boot, i will get the lg logo for a moment and the the screen cuts out and goes back the the flashing red light.
so I trien the LGNPST method.
i downloaded the auto LGNPST and installed just fine. downloaded teenybin and lg stock bin. i've tried to flash both (put phone into download mode, select the dll and select the bin file). what happens is everything starts off fine, then when it gets to 67% the phone reboots, then goes back to the flashing red indicator light, and a message on LGNPST will pop up saying the phone has been disconnected, and to reconnect to continue. so i'll unplug the phone, plug it back in, and put it in download mode, and hit continue. LGNPST will say complete but the phone will still be just sitting in download mode. and if i unplug it, it's goes back to square one (red flashing indicator light)
EDIT: i was flashing the v11c stock bin. i just flashed the v20j bin and now we're boot looping while plugged in (lg logo for about 2 seconds, shut off, repeat) progress???
SO SO SORRY FOR THE LONG READ. Just trying to give as much info as possible hoping it helps.
My question is, is this a hard or a soft brick, and do i have any options left? after researching on here i'm hoping JTAG isn't my only option (I don't have the time or funds to go that route) and i saw someone mention taking it back to at&t, butIi don't think that would help me any since rooting the phone voids the warranty, correct?
I'd be eternally grateful for ANY advice. i'm at my wits end, and i've been google researching this for so long i'm starting not to even comprehend what i'm reading. PLEASE HELP!! And thank you so much in advance.
goplatinum said:
Hello. I'm new to the forum, and the issue that brought me here as had me fulling my hair out of the last three days.
I'll try my best to make this short as possible. I have (obviously) AT&T Lg Optimus G (E970) that was running 4.0.4. i rooted and unlocked it and flashed a cm 10.1 using TWRP. Yesterday tried to flash a zip for a transparent status bar mod. But the flash resulted in CM getting stuck on the splash screen. So i booted in TWRP recovery mode to restore from a recent backup. In the midst of wiping my rom and going to restore, i guess my phone died (which was weird because it had a substantial charge). Then it would no longer power on, and the only was i could get ANY response was by plugging it on the charger. All i get it the red indicator light. my phone will only turn on when plugged into the computer. from there the only two thing i can do is enter download mode and boot. and when i try to boot, i will get the lg logo for a moment and the the screen cuts out and goes back the the flashing red light.
so I trien the LGNPST method.
i downloaded the auto LGNPST and installed just fine. downloaded teenybin and lg stock bin. i've tried to flash both (put phone into download mode, select the dll and select the bin file). what happens is everything starts off fine, then when it gets to 67% the phone reboots, then goes back to the flashing red indicator light, and a message on LGNPST will pop up saying the phone has been disconnected, and to reconnect to continue. so i'll unplug the phone, plug it back in, and put it in download mode, and hit continue. LGNPST will say complete but the phone will still be just sitting in download mode. and if i unplug it, it's goes back to square one (red flashing indicator light)
EDIT: i was flashing the v11c stock bin. i just flashed the v20j bin and now we're boot looping while plugged in (lg logo for about 2 seconds, shut off, repeat) progress???
SO SO SORRY FOR THE LONG READ. Just trying to give as much info as possible hoping it helps.
My question is, is this a hard or a soft brick, and do i have any options left? after researching on here i'm hoping JTAG isn't my only option (I don't have the time or funds to go that route) and i saw someone mention taking it back to at&t, butIi don't think that would help me any since rooting the phone voids the warranty, correct?
I'd be eternally grateful for ANY advice. i'm at my wits end, and i've been google researching this for so long i'm starting not to even comprehend what i'm reading. PLEASE HELP!! And thank you so much in advance.
Click to expand...
Click to collapse
If it is hard bricked when connected to computer it will show up in device manager as QDUSB Device or something similar. You could try to do a factory reset with button combo, be sure phone is powered off then hold power and volume down until menu shows up.
You Can Also Try TeenyBin If Factory Reset Does Not Work
Regards,
acervenky,
XPT
thanks for the reply guys. it looks like my phone is showing up in the device manager under ports as "LGE AndroidNet USB Serial Port (COM3)" is that a good sign? i'm going to try flashing teenybin again.
goplatinum said:
thanks for the reply guys. it looks like my phone is showing up in the device manager under ports as "LGE AndroidNet USB Serial Port (COM3)" is that a good sign? i'm going to try flashing teenybin again.
Click to expand...
Click to collapse
Yes, you are not dead in the water. Proceed, young grasshopper.
Sent from my Optimus G using xda app-developers app
All the custom, unofficial 4.2.2 roms I found on XDA require that you be on the latest LG 4.1.2 OTA.
There are also links to stock rom and kernel so you don't have to mess with LGPT whatever. No need to do OTA etc, if you flash this.
http://forum.xda-developers.com/showthread.php?t=2219953
I also found TWRP to be far easier to install, which is installed by default I think with FreeGee. But you can find thread for the latest TWRP 2.6. TWRP makes flashing and wiping cache/dalvik super easy.
Ok, so i'm starting to think this is a battery issue as opposed to a hardware issue. i could still be wrong. I've flashed the stcok rom after stock rom. When i plug my phone into a computer usb port it LG logo boot loops (and this is the only way i can get to download mode), but when i plug it into the usb wall charger, i just get the red flashing light and no other response. when it's not plugged in i get nothing.It's still showing up as "LGE AndroidNet USB Serial Port" in my device manager and i can still get to dpownload mode just fine, so i know all isn't "according to what i've read and been told". So i'm running out of fixes. I did come accross a thread on here suggesting i unplug the battery and plug it back up. So i'll be getting the tools and praying that works.
I did also come across an interesting thread on another forum. They were saying how id you allowed your battery to drain all the way to true zero (which i think might be possible because my phone died in recovery mode), it wouldn't have enough juice to initiate and monitor the charging process. If this is the case, can the batter be brought back to life? a jump start or something (lol)? or will i have to just replace the battery?
THANK YOU SO MUCH FOR THE HELP SO FAR GUYS.
When you used lgnpst to go to 11c it boot looped because you tried to go backwards from cm. If you did a factory reset afterwards with button combo it should boot. Also can you get into recovery after flashing teenybin to do a reset and flash a ROM?
adfurgerson said:
When you used lgnpst to go to 11c it boot looped because you tried to go backwards from cm. If you did a factory reset afterwards with button combo it should boot. Also can you get into recovery after flashing teenybin to do a reset and flash a ROM?
Click to expand...
Click to collapse
i did a factory reset a few times, but it still never booted. and whenever i LGNPST, when it hits 67% the phone reboots and just starts bootlooping (if i flash a stock rom) if i LGNPST teenybin, at 67% the phone will shut off and the flashing red light will just come up. and after each a message will say phone was unplugged or lost connection. after both instances ill plug it back up and put it in download mode again to finish and it will complete, but the phone will just be sitting there in download mode. and if i reboot.... bootloop city.
i cam across this thread that seems to detail my issue perfectly. so i'm going to attempt a teenybin flash one more time to tryt to get recovery mode (havent been able to get it at all), and if that doesn't work i'm going to do a battery pull..
http://forum.xda-developers.com/showthread.php?t=2261803&highlight=battery
BATTERY UNPLUG WORK LIKE A CHARM. again, i followed the method [r.]GimP laid out here http://forum.xda-developers.com/showthread.php?p=43732147#post43732147
i was nervous because i've never opened my (or any other) phone before.
and thanks to the tot link provided by zymphad above, i'm now running jb 4.1.2
THANK YOU GUYS :highfive:
I found LG's camera lacking, but 4.2 has an update for that, plus the camera mod, much improved I think.
Running RootBox great now with 124mhz idle, GPU downclocked to 200 and CPU undervolted to 85, stable and cool. I don't 3d game on phones.
Glad you fixed it, I just hope someone makes a high capacity internal battery for us since taking it apart isn't that difficult.
Sent from my Optimus G using Tapatalk 4 Beta
Hi All,
I've run into an odd problem. My S4 completely died on me last Saturday. I can access recovery and Odin Mode, but only if the phone is plugged in. No response from any combination of buttons should I try them without the plug in.
When I plug the phone in, it brings me to a boot loop of the battery icon with a circle indicator through it. Leave it long enough, and it'll turn off, vibrate, and do the same thing again. From what I understand, this is a problem with the main board, or the PBA. However, I figure I should try everything before I send it into Samsung for a repair.
I want to flash a factory image through Odin, just in case that could possibly be an issue. If the phone flashes correctly, but still won't boot, is that dangerous? (i.e. the phone needs a complete boot after flashing with Odin).
If I can freely flash without any side effects due to my issue, what would be the safest image to flash to it? I don't remember the name of it off-hand, but I think there were three I knew about.
My phone does come up as COM9 through Odin, so it recognizes there's a device.
Are there any risks to doing this, or should I skip all this work and just send it to Samsung?
Thanks in advance.
Odin help
buckoman said:
Hi All,
I've run into an odd problem. My S4 completely died on me last Saturday. I can access recovery and Odin Mode, but only if the phone is plugged in. No response from any combination of buttons should I try them without the plug in.
When I plug the phone in, it brings me to a boot loop of the battery icon with a circle indicator through it. Leave it long enough, and it'll turn off, vibrate, and do the same thing again. From what I understand, this is a problem with the main board, or the PBA. However, I figure I should try everything before I send it into Samsung for a repair.
I want to flash a factory image through Odin, just in case that could possibly be an issue. If the phone flashes correctly, but still won't boot, is that dangerous? (i.e. the phone needs a complete boot after flashing with Odin).
If I can freely flash without any side effects due to my issue, what would be the safest image to flash to it? I don't remember the name of it off-hand, but I think there were three I knew about.
My phone does come up as COM9 through Odin, so it recognizes there's a device.
Are there any risks to doing this, or should I skip all this work and just send it to Samsung?
Thanks in advance.
Click to expand...
Click to collapse
In the past the only time when I odin back to stock and It did not boot up I went to the stock recovery and did a factory wipe and started like a charm
OK I screwed up. I would appreciate any help here. Rogers S6 Edge, G925W8. It was stock 5.0.2.
Wanted to try a ROM so flashed TWRP, then flashed Kingfisher ROM v1.1 (it seemed the safest / W8-friendly). ROM was fantastic (much better battery), but GPS would never lock.
Tried to start over by flashing stock Rogers 5.0.2 via Odin but it wouldn't flash. I read (a little too late) that downgrading isn't something Samsung enjoys. Argh!
Then out of desperation, I flashed the BL (BL_G925W8VLU2BOH8_5.1.1.tar) from http://forum.xda-developers.com/galaxy-s6-edge/general/canadian-odin-5-1-1-bootloader-twrp-t3196595 , which was a very bad move, I assume because I wasn't on 5.1.1 to begin with. Crap!!
So now the phone gets to the Galaxy S6 edge splash screen, with "KERNEL IS NOT SEANDROID ENFORCING", and it stays there. The phone also gets very warm, and I can't shut it off. Using VolDown+Power+Home reboots it (showing the same message) but doesn't shut it off. Using VolUp+Power+Home reboots it but only says the same thing about Recovery.
Please tell me that I didn't just brick this phone!!
UPDATE:
Am able to get the phone into Download/Odin mode by holding the 3 buttons (voldown+power+home) while plugging the phone into USB. The stock Rogers image refuses to flash (Odin says fail immediately), but I am a step closer thanks to @brar.arsh's thread ( http://forum.xda-developers.com/galaxy-s6-edge/general/canada-galaxy-s6-edge-canadian-users-t3069314 )
From there I grabbed the "S6 Edge Stock Firmware OG2" which comes in 4 parts (BL, AP, CP, and CSC). I added all 4 pieces to Odin and started flash. Boot.img and recovery flashed, but then during the system.img flash, it failed about half-way through. Right after that failure, something changed because the device now became "Unknown Device" to windows, and it complained that "a USB device has malfunctioned, and Windows no longer recognizes it".
This gave me hope that I could get into Recovery (since that flash was successful), but the phone likes to boot directly to the "The update failed so please launch Smart Switch" message - regardless of starting with VOLUP+PWR+HOME button combination. So no recovery access... but making progress.
I belive I initiated a flash that contained JUST the BL, CP, and CSC portions, and it passed quickly. This, of course, isn't enough to get the system going. I just wanted to see if it would fail in other areas.
Trying the emergency flash via Smart Switch: Smart Switch said it required the phone to be in Recovery mode, but it still attempted the fix even though I was in Odin/Download mode. Good news, but unfortunately it gave the same result - a failure at around 50% of the entire flash operation.
I have tried re-flashing the AP portion several times and it fails at different progressions (50%, 75%, 90%)... so close.
I was thinking that it was maybe a power issue (since the battery was completely dead during the "kernel is not seandroid enforcing" period, with no way to turn the phone off or pull battery), I wondered if the battery just needed a little juice before starting the operation. I let it stay plugged in for a few minutes after one of the many failed flash attempts (screen was illuminated with the progress bar frozen at the point of failure). I noticed that when I unplugged it, it didn't die immediately, so I plugged it back in (getting the "USB device has malfunctioned" message again), and forced it to restart by holding the VOLDOWN+PWR+HOME buttons). It got back into Odin mode and the PC recognized it again. Loaded up just the AP portion in Odin, hit Start, left the room, and when I came back it said PASS! I cannot prove that it had any battery power from this method... or if it even helped. This could have just been a fluke.
The phone automatically rebooted into Recovery mode (which scared me) so I hit Power Down.
Rebooted the phone - I hear the lame Samsung startup song, and it is booting. Hallelujah.
Hi all,
This is a brief guide on what are some things that could go wrong if you decide to flash a new ROM especially GSI as they are quite buggy at the time of writing this post. I'll try to mention as many issues as I can but if something remains, please feel free to write them in the reply.
The guide is aimed for complete beginners who were trying to flash something and are now stuck OR who just want to know what to be prepared for and not to panic. if you are experienced you might not need it but it might just help you with something.
also, as always, I AM NOT RESPONSIBLE IF SOMETHING DOES NOT WORK. YOU ARE RESPONSIBLE FOR YOUR OWN ACTIONS.
So let's start with the most common problem. Bootloops!
1 - Bootloops :
What happens? : The title is pretty self-explanatory. You know you are in a bootloop if your phone turns off automatically as soon as it turned on. This generally happens BEFORE the phone actually boots up i.e. in the booting screen but could also happen after the phone completely turned on. There are various causes for this it may be due to a bug in the ROM or missing system files.
How to fix? : If you are flashing a custom ROM then you may want to reboot back to TWRP, wipe and flash it again. It works sometimes if there was an issue with the files.
I am unable to reboot to TWRP my phone is stuck even long pressing the power button does not shut it down! :crying::crying: : well if you are stuck you don't actually need to open the back panel to remove the battery or wait for it to die those won't help. all you need to do is wait for the phone to turn off and IMMEDIATELY press and hold the VOLUME UP and POWER button that should get you into TWRP if that doesn't work then you can try pressing and holding the VOLUME UP + DOWN + POWER key as the phone is about to turn on. it might boot you into download mode. if that does not work as well then as the phone is about to turn on, press and hold VOLUME UP + DOWN and plug the phone into PC that will get you booted into download mode eventually. Once you have access to one of these you can continue doing whatever you were doing. To reset everything back to normal (stock, like a new phone) checkout the solution listed below.
2 - I was doing something and now my phone is stuck at charging mode :
What happens? : This has happened to me while flashing PHH GSI. My phone was plugged into the charger and I restarted the phone. turns out it was a fatal mistake for the bugged gsi. The phone now only showed a battery icon that was charging very similar to the one that you would see if your phone is out of battery and you put it to charge. This happens before the phone actually turns on. usually, once you unplug the charger the phone automatically restarts but in my case it didn't. It was stuck at that screen with no way out.
How to fix? : turns out it's pretty easy, it might seem like its doing NOTHING, not responding to power buttons or anything but internally it is. Surprisingly, if you press and hold the VOL UP + DOWN + plug it into the PC it would get you into the download mode.
3 - I flashed GSI and ... :
What happens? : There are MANY things that can go wrong with GSI if you are a beginner I would suggest you stay away from GSI until it supports the device better. For me, I flashed PHH gsi and it went smoothly I booted in but as soon as I was finishing the setup adding fingerprint the ROM went into bootloop. you know how to fix this now. if nothing works, just refer to the reset solution listed below.
4 - "Custom binary blocked by FRP lock" :
What happens? : This usually (at least with me) happens when you are trying to flash something but forget to flash the DmVerity thing. The phone won't turn on and going to download mode will throw you with a line saying FRP lock.
How to fix? : At this point, trying to install custom binaries with Odin probably won't help as for me it simply stated that you cant install custom binaries only Samsung official updates are allowed or something similar. There might be a better/easy solution to this but I found doing a stock reset with Odin worked great. It is given below refer to that.
5 - Phone is in "Emergency firmware recovery" Mode :
What happens? : Turning on the phone throws you into a cyan screen saying that your phone needs emergency firmware recovery which can be done using Samsung smart switch
How to fix? : I believe it is a fantasy way of Samsung saying that your phone is almost dead and nothing remains on it. Fear not, turns out that cyan screen is actually the download mode. so that's a win you don't even have to boot to download mode just connect your phone to pc odin and follow the reset to stock firmware as mentioned below.
6 - I am back in some OS but my internal memory is shortened!!!
What happens? : well you are in the os you wanted but if you check the storage it appears to be shortened. i.e. if your phone has 64gb internal memory it might appear as 30gb or 20gb.
How to fix? : This is a problem caused by missing PIT file in odin. I would not suggest you to manually download the PIT file from somewhere and flash it using odin because doing so got me stuck in the FRP LOCK (4th) situation. I would suggest that you flash the stock firmware using the method given below.
MASTER SOLUTION/RESET TO STOCK FIRMWARE: if you are new to modding I would suggest that you download the stock firmware files from here BEFORE doing anything as the files exceed more than 3GB in size and not everyone has fast internet. if anything goes wrong and you have access to download mode you can follow this and get everything back to stock. Download the stock file AFH given at the link. once you download the stock firmware you just need to extract it and put the respective files in odin and begin flash. it will RESET everything and make it a new phone. I've tried this method and it works always for me.
That concludes my guide. if anyone knows any better solutions to these problems or think I've written something wrong please feel free to correct me. I've faced all of these issues back to back when I tried flashing a GSI and was able to fix all of them so this is just my personal experience.
Lastly, don't panic if something happens wrong happens there is probably a way to fix it.
Depends on many things, but now that we have a working TWRP, life is much easier, and also we have kitchen tools which help as well.
thvardhan said:
Hi all,
This is a brief guide on what are some things that could go wrong if you decide to flash a new ROM especially GSI as they are quite buggy at the time of writing this post. I'll try to mention as many issues as I can but if something remains, please feel free to write them in the reply.
The guide is aimed for complete beginners who were trying to flash something and are now stuck OR who just want to know what to be prepared for and not to panic. if you are experienced you might not need it but it might just help you with something.
also, as always, I AM NOT RESPONSIBLE IF SOMETHING DOES NOT WORK. YOU ARE RESPONSIBLE FOR YOUR OWN ACTIONS.
So let's start with the most common problem. Bootloops!
1 - Bootloops :
What happens? : The title is pretty self-explanatory. You know you are in a bootloop if your phone turns off automatically as soon as it turned on. This generally happens BEFORE the phone actually boots up i.e. in the booting screen but could also happen after the phone completely turned on. There are various causes for this it may be due to a bug in the ROM or missing system files.
How to fix? : If you are flashing a custom ROM then you may want to reboot back to TWRP, wipe and flash it again. It works sometimes if there was an issue with the files.
I am unable to reboot to TWRP my phone is stuck even long pressing the power button does not shut it down! :crying::crying: : well if you are stuck you don't actually need to open the back panel to remove the battery or wait for it to die those won't help. all you need to do is wait for the phone to turn off and IMMEDIATELY press and hold the VOLUME UP and POWER button that should get you into TWRP if that doesn't work then you can try pressing and holding the VOLUME UP + DOWN + POWER key as the phone is about to turn on. it might boot you into download mode. if that does not work as well then as the phone is about to turn on, press and hold VOLUME UP + DOWN and plug the phone into PC that will get you booted into download mode eventually. Once you have access to one of these you can continue doing whatever you were doing. To reset everything back to normal (stock, like a new phone) checkout the solution listed below.
2 - I was doing something and now my phone is stuck at charging mode :
What happens? : This has happened to me while flashing PHH GSI. My phone was plugged into the charger and I restarted the phone. turns out it was a fatal mistake for the bugged gsi. The phone now only showed a battery icon that was charging very similar to the one that you would see if your phone is out of battery and you put it to charge. This happens before the phone actually turns on. usually, once you unplug the charger the phone automatically restarts but in my case it didn't. It was stuck at that screen with no way out.
How to fix? : turns out it's pretty easy, it might seem like its doing NOTHING, not responding to power buttons or anything but internally it is. Surprisingly, if you press and hold the VOL UP + DOWN + plug it into the PC it would get you into the download mode.
3 - I flashed GSI and ... :
What happens? : There are MANY things that can go wrong with GSI if you are a beginner I would suggest you stay away from GSI until it supports the device better. For me, I flashed PHH gsi and it went smoothly I booted in but as soon as I was finishing the setup adding fingerprint the ROM went into bootloop. you know how to fix this now. if nothing works, just refer to the reset solution listed below.
4 - "Custom binary blocked by FRP lock" :
What happens? : This usually (at least with me) happens when you are trying to flash something but forget to flash the DmVerity thing. The phone won't turn on and going to download mode will throw you with a line saying FRP lock.
How to fix? : At this point, trying to install custom binaries with Odin probably won't help as for me it simply stated that you cant install custom binaries only Samsung official updates are allowed or something similar. There might be a better/easy solution to this but I found doing a stock reset with Odin worked great. It is given below refer to that.
5 - Phone is in "Emergency firmware recovery" Mode :
What happens? : Turning on the phone throws you into a cyan screen saying that your phone needs emergency firmware recovery which can be done using Samsung smart switch
How to fix? : I believe it is a fantasy way of Samsung saying that your phone is almost dead and nothing remains on it. Fear not, turns out that cyan screen is actually the download mode. so that's a win you don't even have to boot to download mode just connect your phone to pc odin and follow the reset to stock firmware as mentioned below.
6 - I am back in some OS but my internal memory is shortened!!!
What happens? : well you are in the os you wanted but if you check the storage it appears to be shortened. i.e. if your phone has 64gb internal memory it might appear as 30gb or 20gb.
How to fix? : This is a problem caused by missing PIT file in odin. I would not suggest you to manually download the PIT file from somewhere and flash it using odin because doing so got me stuck in the FRP LOCK (4th) situation. I would suggest that you flash the stock firmware using the method given below.
MASTER SOLUTION/RESET TO STOCK FIRMWARE: if you are new to modding I would suggest that you download the stock firmware files from here BEFORE doing anything as the files exceed more than 3GB in size and not everyone has fast internet. if anything goes wrong and you have access to download mode you can follow this and get everything back to stock. Download the stock file AFH given at the link. once you download the stock firmware you just need to extract it and put the respective files in odin and begin flash. it will RESET everything and make it a new phone. I've tried this method and it works always for me.
That concludes my guide. if anyone knows any better solutions to these problems or think I've written something wrong please feel free to correct me. I've faced all of these issues back to back when I tried flashing a GSI and was able to fix all of them so this is just my personal experience.
Lastly, don't panic if something happens wrong happens there is probably a way to fix it.
Click to expand...
Click to collapse
Absolutely well written for new users who wish to get into the world of Android on their Samsung. Might I suggest a few corrections?
Akhil99 said:
Absolutely well written for new users who wish to get into the world of Android on their Samsung. Might I suggest a few corrections?
Click to expand...
Click to collapse
Sure by all means, feel free to suggest any modifications/corrections.:highfive: