Develop Bugs

Red LED, No Boot Because of My Idiot Moment

Just happened today, I root the phone with kingroot, then installed XZDualRecovery to remove the kingroot and replaced them with SuperSU. One thing led to another, instead of flashing the SuperSU package, I end up formatting the internal storage. Nothing left there. Luckily I managed to realized my mistake in time, before rebooting the phone. So I download the flashable stock rom, planning to copied via MTP, then flash it to restore my phone. Two hours later, the download finished - yes, sadly, it took that much time here to download 1++ GB, and I still considered it fast - That 2 hours of being bored unfortunately led to another stupid mistake. I rebooted the phone before I copied and flashed the downloaded stock rom :crying:
TWRP only only offers me to flash the SuperSU package, then rebooted. Needless to say, the phone is dead. Just the red LED laughing constantly of my stupidity.
Quick Googling tells me the symptom pretty much the same with hardbricked ZL. Red LED, no Fastboot, No Flashmode. Pressing the button at the side of SDCard slot only make the phone vibrates, show Sony Logo, then blank. Okay, time to get panic, time to light a cigarette and take a distance for a bit to cleared out my head.
That done, I start googling to troubleshoot the problem. Quick search reveal the tools I need to recover the phone. I need Flashtool, ftf stock rom, good cable data, probably EMMA too. Unfortunately, the Flashtool only available through torrent, which has no peers, so I have to look somewhere else to get it. Wasn't ideal, but what a heck, I need to recover this phone.
Once all the tool in place, time to execute. Several guides I've found tells me I need to flashed the stock ftf with flashtool. But even with the cable plugged and constant pressing on the all available button (power, vol up, down and sdcard side button) can't make the phone recognized by the computer. I've tried every combination of cable plugged/unplugged, button pressed/depressed, all to no availed. Desperation seeps in.
Okay, time to take another break, another cigarette, and charge the phone for a bit. Afterward, I choose to tried to work on the phone recovery using linux. Maybe windows messed up somehow with the driver thingy that prevent me to fix the phone. No such luck unfortunately. Linux also failed to detect the phone. Hmmpppphhhh... Back to windows then.
I fired up the flashtool, pressed to lightning button, choose flashmode, pick the ftf files, then pressed the yellow button on the side of sdcard slot continually. The phone vibrates, 3x, I keep pressing, then it vibrates again 1x, but no respond from the computer, so I keep on pressing it. It vibrates again in 3x, paused, 1x, long paused rhythm. Then something happened, the LED turn green, and the windows notifying something happened. The log column of the flashtool start filling with lines, but end up in lost connection with the phone. Its a progress though, so I turned the phone off for a bit, to restart the process again. What I've done:
1. Start the flashtool.
2. Wait till it finished the initial detection.
3. Pressed the lightning button in flashtool.
4. Choose the Flashmode.
5. Choose the ftf files to be flashed, then pressed the flash button.
6. Pressed the button at the side of the sdcard slot continually - using a bamboo toothpick - until the LED turn green.
7. Let the flashing process done.
8. Restart the phone.
Voila, the phone boot normally, showing the sony logo, then the blue wave then it boot to the wizard screen with low batt warning. So I plugged it to a charger, then proceed with the wizard. The funny thing is, I swear I had more than 90% battery before I entered my special idiot mode. Apparently all of that red led period drained the battery fast. So after I finished the wizard, I put the phone on airplane mode to accumulate enough juice (till 9%) then I test to reboot the phone to make sure it really work. And it does. So I turned it off, to charge faster so I can start updating the firmware (I used C6502_10.5.A.0.230_10.5.A.0.230.ftf) and sets the phone straight again.
So that's how I spend my quality time today. Not much, but hopes it can help anyone out there with the similar problem. Cheers.

Very informativ.
Thank you for sharing your experience. I've found it very useful.

seriously a big thanks. thats a lot of effort. cheers to you. even though i dont need it now (hoping i dont end up like that) its still a great gesture from you.

Galaxy Tab 3 NO Power, boot loops when plugged in. Otherwise nothing Video attached.

Hi all, I've been using XDA for years since the original O2 XDA's and I have never had to post anything as I've always found my solution. I'm hoping somebody can assist me with a problem I have on this stock galaxy tab 3.
The device was brought to me after being thrown down the stairs. I replaced the screen and built it back up,
Removed battery connector and reconnected = nothing happens
Press power = nothing happens
press download mode = nothing happens
press recovery mode = nothing happens
Plug USB into PC = nothing happens on PC or tablet
Plug in USB mains charger and it displays battery charging logo but it doesn't fill or animate the fill then it starts the samsung boot screen. It reboots and continues to do this constantly and never ends.
I've tried two batteries and both batteries work in another tab 3 but neither batteries changed how the device works.
Thank you for any advice in advanced!!

I just received a Tab 3 lite (SM-T110) for repair, it's having a similar problem.
It does automatically turn on when plugged into charger or computer.. It is stuck on a bootloop, requiesting a Kies recovery. It does reboot when given the three finger salute (center button, volume down, and power) - it will not enter recovery mode though - same firmware error message). The device is also full off or full on, no indication of it's it's recharging or no - let the battery run out, it's off - else it's on (does not turn on or off with power button). I don't have any info how it got into this state - most likely power loss during a firmware update, but haven't ruled out other possibilities (ie bad rooting job, a custom ROM upgrade went wrong, etc). I'm not 100% concerned about cause, but hopefully I can unbrick the thing.
Anyways, I loaded Kies onto my computer and put it into recovery mode and plugged it in - nothing. Exit the recovery mode of Kies, and all of a sudden the program goes nuts trying to connect and disconnect from the device. Hmm... Okay, disconnect it, uninstall Kies, install Kies3 and try again - same thing except it complains the device is too old when the program leaves recovery mode - but same thing otherwise - does not show up in recovery mode, connects and disconnects at huge rate when not in recovery mode....
Hmmm...
Now looking at the screen, it does indicate (in the upper left hand corner) that it's in ODIN mode... So my next step I figure I'll try ODIN (although I'm researching ODIN at the moment as I haven't used it before (never had to unbrick anything from Samsung prior to now).

Okay, that was painless - downloaded and installed ODIN 3.10.7, and then downloaded the latest firmware from Samsung, extracted the firmware, added it to ODIN's AP line, then hit start to push the latest firmware onto the tablet. Good as new again.

Samsung Galaxy Tab 3 7 Kids T2105 T-2105 can't access recovery mode

I have three (3) Samsung Galaxy Tab Kids T2105 tablets. All are running the latest firmware, T2105UEAOE1.
None of them will boot into recovery. The tabs work, they will boot normally, and then will boot into Download mode. But they will not boot into recovery.
* If I hold down Power+VolUp+Home, or Power+VolUp, continuously, the Tab turns on, and then, about 5 seconds later, turns back off.
* If I hold down Power+VolUp+Home, or Power+VolUp, and release them when the Samsung Logo appears, the device boots normally.
* If I hold down Power+VolUp+Home, or Power+VolUp, and release Power when the Samsung Logo appears, and then continue to hold VolUp and/or Home, the device sits on the Samsung Logo for 20 seconds, then the screen goes blank for a second, then the logo comes back on and sits for 20 seconds, then the screen goes blank... and this cycle repeats until I release the buttons, at which point the device boots normally.
I have done factory resets (through the normal mode settings menus). I have reflashed the latest firmware with Odin3. Nothing seems to fix this problem.
I've been searching the net for hours for this. I see a number of other people who have reported this problem. But nobody has offered a solution. One person stated that he uses "adb reboot recovery" - which is a fine, if ugly, hack - but the fact remains that, for many people, apparently, Stock Android Recovery is not accessible from the Samsung Galaxy Tab Kids T2105.
Does anyone know of an actual solution for this, to restore recovery functionality to this tablet?

Hello,
I have the same tablet, same problem (no stock recovery). None of the button combinations work, and the logo just keeps repeating. My situations is that my 9 yr old daughter locked herself out and can't remember her lock screen password. It's a totally stock tablet (never been rooted or flashed). Because I can't get into the tablet, I'm not sure what firmware version it has, and it does not have USB debugging enabled.
I tried booting into the stock recovery to do a factory reset (since we can't do it in the Settings). I tried flashing the same firmware you mentioned using Odin. It goes through the motions successfully and reboots. But it boots back to the lock screen and its still "locked" (we still see her personal wall paper) - which tells me the flash is not taking. Even though my Odin set up is fine, it does not work (even though everything passed with green lights). I tried going into Safe Mode to try bypassing the lock screen, but even in Safe Mode it still asks for the password. My thinking was to go into Settings and initiate a new password or do a factory reset.
(BTW - the Safe Mode button combination was different for me. Holding Power + Volume Up did not work. Instead I had to hold Power + Volume Up & Down until the logo showed up. Once the logo disapeared, then I had to let go of the Power button only - but continue holding the Volume Up & Down until it fully booted into Safe Mode).
I tried ADB in order to use a password reset/erase command line. But because the USB debugging is not enabled, ADB doesn't see the tablet. There is no other way to enable it via Odin or ADB. And I can't even sideload any Lock Screen Hack apps becuase the table is not rooted, or not USB debugging enabled, or can't get into recovery to flash an .apk or image.
So I am stuck. Why would Samsung block recovery mode??? I have been trying for more than 8 hours. If anyone can help, me and my 9 yr old daughter will greatly appreciate it. My last attempt will be to try Google Device Manager and see if it can somehow unlocks it. Or try Kies (although everything I have read so far says that these have not worked either).
HELPPPPPPPPPP!!!!!!!
ggee

wfire said:
I have three (3) Samsung Galaxy Tab Kids T2105 tablets. All are running the latest firmware, T2105UEAOE1.
Does anyone know of an actual solution for this, to restore recovery functionality to this tablet?
Click to expand...
Click to collapse
Hello,
I'm not sure which one of these did the trick for me, but I was able to get into recovery mode. I'm not sure if your three tables are rooted or not, but I don't think it matters. Try these two methods:
Method #1:
Technically, I think I just stumbled on to this one after successfully completing Method #2 (below). But it's worth trying it first before moving on to Method #2.
-Hold the Home + Volume Up + Power buttons together at the same time (just like the normal process).
-Now, you will probably need to try this next step a couple of time before you get it right. This is because it happens pretty fast and you need to time it perfectly.
-Notice that when the screen turns on, the actual first thing that happens is that the the screen backlight turns on and glows first. This happens first and a split second later the first Samsung logo flashes.
-You need to let go of all three buttons at the same time as soon as you see the backlight turn on, but before the Samsung logo flashes.
This is the sweet spot, and it happens pretty fast. But once you do it at the right time, the tablet will go black again and then the recovey mode will show up. It works for me every time.
Method #2:
I thought somehow the recovey mode portion of the firmware had become corrupter somehow. So I decided to flash a custom recovery using Odin (since at that time I hadn't stumbled onto Method #1 yet). Make sure to use gr8nole's custom recovery version for the SM-T210 and SM-T210R (these are the equivalent wifi versions of our Kids tablet). His versions have fixed some known bugs that CWM/TWRP have with the wifi version of our tablets. Make sure to download and flash the CWM or TWRP .tar file for Odin (I personally have always liked CWM over TWRP).
Here is his link: http://gr8nole.blogspot.com/
Also mentioned here: http://forum.xda-developers.com/showthread.php?t=2437219
-Make sure you have all the correct USB drivers for the tablet installed on your computer.
-Open Odin and load the .tar file that you downloaded from gr8nole into the PDA or AP slot (depending on your Odin version).
-Let Odin check the m5d verification for successful authorization.
-Once Odin is ready, then boot the tablet into Download Mode (Home + Volume Down + Power button)
-Connect the table to a USB cable that is attached to your computer's main USB port.
-Odin should now recognize that the table it connected to a valid COM port.
-Click <Start> button on Odin and it should flash the costum recovey .tar file pretty quickly.
-The tablet will simultaneously flash a progress bar and start to automatically reboot (also pretty quickly).
-Disconnect the tablet from the USB cable now.
If the tablet does not automatically reboot to the new custom recovery screen, then just power off the tablet completely. Wait 30 seconds, and then boot the table to recovery mode use the Method #1 shown above. You should now be able to go into the new custom recovery mode you flashed with Odin (CMW or TWRP). It should all work now.
From this point you can download and install SuperSU to add root (if you want to).
Let me know if this works for you.
ggee

N7100 boot stuck

Hello.
I own a Note II which lately seemed to have some problems.
In the last few months, it used to restart somewhat spontaneously (it seemed that it rebooted when its processor or RAM were too busy, but this wasn't a rule). During one night it probably rebooted and next morning I found it stuck on the first boot screen (the one with "Samsung Galaxy Note II").
When stuck on the boot screen, if I press the power button for a few seconds, it turns off. If closed, it gets to the boot screen and gets stuck there when I press the power button. When plugged to power, it gets stuck at the screen with the empty battery that has a loading icon in the middle.
I manage however to get it into recovery mode, however, in this situation, it can't be seen by the PC, unless I put it in adb sideload mode. When stuck on the logo screen, it is seen as mtp device.
In the recovery mode screen, there are many errors (can't/failed to mount /efs, /system, /cache, /cache/recovery/last_recovery, /data, /data/log/recoverylog.txt, /cache, /cache/recovery/log, last_log, last_install.
In Windows, the PC doesn't recognize the model, however, in a virtual machine that runs Linux, it is correctly seen as Note II when in adb sideload mode, but Linux is not able to mount its storage.
I have also deleted cache, tried Samsung Kies and Note II Toolkit.
What I would like to do is recover the data on it. Do you think it is possible, and if yes, how?
Thank you.

Sounds like a failed memory chip to me.

any answer now?
i want get ROM-not2-7100

Can you make it more clean and what do you want ? I want help to you but i dont understand what are you talking about So can you have acces to twrp ?

same problem
hi
i have same problem
i can go download mode but cant go recovery mode
using odin to flash twrp and cwm it said pass but problem exist

DarkMountain said:
Can you make it more clean and what do you want ? I want help to you but i dont understand what are you talking about So can you have acces to twrp ?
Click to expand...
Click to collapse
No, I don't have access. What I want is to recover the files on it, if possible.

This may be a problem with the power button. if you can go into download by pressing only the menu button + volume down is because the power button is always pressed.

eton3 said:
This may be a problem with the power button. if you can go into download by pressing only the menu button + volume down is because the power button is always pressed.
Click to expand...
Click to collapse
No, I need to use the power button too.

calindiaconu said:
No, I don't have access. What I want is to recover the files on it, if possible.
Click to expand...
Click to collapse
Sorry i think your partitions broked. I think you cant recover your data. There is has only one solution. Odin and Format....
My device too has pc cant detect my phone. I tried different cable without samsung usb drivers. Pc succesfully detected the my device.
By the way i installed lg usb driver because of someone's phone is lg and they need format.

I think there's no way to recover your data now.
BTW what recovery are you using?

Question S21 FE - endless bootloop and download mode/recovery not working (properly)

Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯

I would just like to reply here and add my own potential fix and also would like confirmation that it would work.
So I have a SM-G996B in a boot loop which returns a 'fs_mgr_mount_all' error. Possible to reboot into recovery mode, cleared cache and restarted bootloader etc with the same boot loop. Powered off and connected to PC for Download mode for ODIN recovery but upon pressing volume up, it then restarts again so Download mode recovery is impossible.
I know however that Developer options and USB debugging was enabled on the device as well as unlocked boot loader. I was able to download the correct original stock OS based on the PDA , CSC and Android version.
I have then installed the latest ADB software on my PC and Samsung USB drivers.
By then rebooting into recovery mode, I have the option of 'Apply update from ADB'. I have then confirmed the device connects using the ADB devices command.
I would like to clarify one thing however. I want to keep the user data at all costs. By using the stock firmware and renaming as update.zip, will it use the HOME_CSC and not the CSC file? If not would it work if I open the zip and remove the CSC before re-zipping to make sure?
Thanks

Reebee said:
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Similar issue with same phone. In a bootloop after trying to root. None of the button combinations have worked for me, for the past several days.
Tried powering the phone off for the whole night.
When connected to the PC shows phone is in recovery mode via adb (blank screen though).
Want to know how to get into DL-mode, guaranteed.

Got to DL mode by pressing vol up + down + power + usb cable connected in PC and phone. However, couldn't do anything there, but maybe you can
Also, phone is still working and I still have no clue what was the problem and what fixed it.