Database Info

[Q] Probably bricked P3113 - Need Confirmation

So, been running CM10 for a long time on tab. Decided to go back to stock, and downloaded the JB stock rom. Flashed via ODIN. Everything seemed to go OK, except that after the flash the screen went black for ages, and didn't reboot. So I hard powered it off. Probably what did it, but it wasn't going anywhere for about 15 minutes, so figured it was the next step.
Now, I get the battery charging icon. The system goes through the Galaxy Tab 2 7.0 white logo, the swirling then glowing Samsung logo, and then loops through that forever.
It wouldn't be such a problem if I could back into ODIN and do another flash, but I can't get into download mode (normally I do it via adb but that isn't working since there is no USB connection at all). Tried all combinations, power/up, power/down etc. It just boot loops as above. I'm pretty sure I bricked it, but just wanted some confirmation.
Been doing this on and off for a long time, and it's the first time I've ever got stuck like this.
Thanks in advance.

Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.

ketut.kumajaya said:
Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.
Click to expand...
Click to collapse
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.

sl0ttedpig said:
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.
Click to expand...
Click to collapse
You must pull usb cable before start.
You can try to re-flash.

tuxafgmur said:
You must pull usb cable before start.
You can try to re-flash.
Click to expand...
Click to collapse
Well, don't I feel like the idiot!
How did I not think to disconnect the USB before trying this? tuxafgmur, your first "Thanks" has been registered, I've got it from here!
P.S. Welcome to the forum!

it sounds strange. never heard of such a strange boot problem. anyway it could be that while transferring boot.img it became damaged due to some error. i know you probably tryed but you may try and connect it to linux or mac os x in order to check if you could retrive more data about the tab. for example the mac could find if it is totally corrupted. normally when i plug my samsung devices it ask me to add the samsung-modem also if they are turned off. meybe if it happens the same to you you can try to adb fastboot it also if i doubt myself about it working, but give it a shot
i hope my bad english is not preventing you to understand what i'm saying!
give us new feedback!

Unusual bootloop - can't access recovery OR fastboot but loops on "optimzing apps"

Unusual bootloop - can't access recovery OR fastboot but loops on "optimzing apps"
I had my US version OpO 64GB working with CM12 for quite a while, rooted and bootloader unlocked with TWRP (possibly 2.8.6) installed, then some months ago I tried upgrading to CM12.1 through CM updater. This failed miserably - The phone started bootlooping on "Optimizing apps n of N" - as soon as it finished optimizing apps, the phone would reboot and start optimizing again. Booting to safe-mode (Power + VolUpDown) also fails in the same way (though optimizing fewer apps).
I tried rebooting to recovery mode holding Power + VolDown but it just gives a quick buzz (vibration motor) at the "1+" screen and reboots. The same thing happens when I try to boot to fastboot mode with Power + VolUp. So I'm completely stuck. All the guides show being able to boot either to fastboot or recovery (soft-brick) or else the screen being completely black/unresponsive (hard-brick). My phone is neither of these!
I got frustrated enough that I've let it sit on the shelf for the past 6 months, but now I'd like to fix this. All help appreciated.
---danq989

Did you try clearing the cache and doing a factory reset ?

SpectreFang said:
Did you try clearing the cache and doing a factory reset ?
Click to expand...
Click to collapse
That's impossible for me to do since I can't get to launcher or recovery.

No acess to recovery?? Then better take it to service center... Atleast can u boot to fastboot mode or adb accesible then use oneplus one toolkits
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
Install oneplus tool kit, while optimising apps it gets dectected by pc, just make it reboot mode & do reset.... Dnt worry this can be fixed, if all these seems messy then take it to service center

danq989 said:
I had my US version OpO 64GB working with CM12 for quite a while, rooted and bootloader unlocked with TWRP (possibly 2.8.6) installed, then some months ago I tried upgrading to CM12.1 through CM updater. This failed miserably - The phone started bootlooping on "Optimizing apps n of N" - as soon as it finished optimizing apps, the phone would reboot and start optimizing again. Booting to safe-mode (Power + VolUpDown) also fails in the same way (though optimizing fewer apps).
I tried rebooting to recovery mode holding Power + VolDown but it just gives a quick buzz (vibration motor) at the "1+" screen and reboots. The same thing happens when I try to boot to fastboot mode with Power + VolUp. So I'm completely stuck. All the guides show being able to boot either to fastboot or recovery (soft-brick) or else the screen being completely black/unresponsive (hard-brick). My phone is neither of these!
I got frustrated enough that I've let it sit on the shelf for the past 6 months, but now I'd like to fix this. All help appreciated.
---danq989
Click to expand...
Click to collapse
while things are loading, have u tried to hold vol up + power for 10 seconds or until the screen turns off and then hold vol down + power button until the oneplus logo?

Bradl79 said:
while things are loading, have u tried to hold vol up + power for 10 seconds or until the screen turns off and then hold vol down + power button until the oneplus logo?
Click to expand...
Click to collapse
Yes, just tried it. Same thing as described in my original post. When I hold power+volup the screen goes blank. I switch to power+voldown until the 1+ logo. At that point:
1. If I continue to hold the power+voldown key through the 1+ logo, the screen goes blank briefly, the phone vibrates once and reboots. If I continue to hold the power+voldown key, the vibrate&reboot cycle continues indefinitely
2. If I let go of either the power button, the voldown button, or both at or before the 1+ logo, the phone boots normally and goes to "Android is starting... Optimizing app n of 119). When the optimization finishes, the phone instantly reboots.
It's like the phone recovery is gone or inaccessible. Could this have to do with the phone tampering setting? As I said, I had this phone rooted and bootloader unlocked, working fine with CM12 for some time before trying an in-place upgrade to 12.1. That's when things went south.
---danq989

Mi Note 3 Boot Loop

Hello,
My phone went into bootloop and I cannot do anything to open it. I cannot connect it to the computer or wipe all data from the phone. I have never done aything on it and the bootloop happened while i was sleeping. Woke up to find that the phone is constantly rebooting. Also the phone does not stay in fast boot mode. I managed to open the recovery mode and select wipe all data but the process interrupts and the phone reboots again. I also think that the power button might have a problem because when i only press the volume down button the device enters fast boot mode. Thanks in any help

Your power button may have been stuck. Try to press it harder or from one end.

zaqm said:
Your power button may have been stuck. Try to press it harder or from one end.
Click to expand...
Click to collapse
I have opened to phone to see that the power button was indeed stuck. Had to jam a piece of paper there to make it stop for now.

Install the Recovery ROM with MiPCSuite.

Redmi Y2 (Indian version of S2) randomly stuck on Mi logo. Please help!

Hey everyone, I hope this is the right place to ask for help. Something very weird happened yesterday. After removing my 2-year old Y2 from charging, I started using it normally. After a few minutes, it lagged somewhat and then stopped responding. Without thinking much, I pressed and held the power button to restart it like I have done many times before. But this time, it got stuck on the Mi logo. It kept getting stuck on the Mi logo (after switching off for about a second) no matter how many times I held the power button to restart again. I left it on the logo overnight and it stayed that way.
What I have tried yet:
1. As I said, I tried to restart it multiple times by holding the power button to no positive effect.
2. I tried to boot it up into recovery mode by holding Volume up and power button. That restarts the phone back to the Mi logo and it is stuck again. The "Main Menu" (which I think is the recovery mode) with options like Reboot, Wipe data, etc doesn't appear.
3. I tried to boot it into fastboot mode by holding Volume down and power button. It boots up to the fastboot logo so I guess it is working.
4. I followed the steps in this video. The phone stays in fastboot and nothing happens.
5. I let the phone discharge completely once, and tried charging and booting again. This also did not make any difference.
I could not find any information about something like this anywhere. Since it happened on its own, maybe it is a hardware problem? I did not install anything new in the past few days, not even a new app. Maybe it has got something to do with the battery or some other part?
I'd really appreciate any type of help in how to fix this, in particular the following issues:
1. Is there any way to know if it is a software or hardware problem without complicated tampering with the hardware?
2. Can I do anything to recover the data? I'd be really upset if I lost it all.
3. What all steps can I take to fix it if it is a software problem, preferably without losing the data?
4. If it is likely a hardware problem or a difficult to solve software problem, how I can I encrypt (or even wipe) the data before giving it to someone for repairs? (since I'm not able to boot into recovery mode)
Some extra information if you need it: my phone is not rooted, bootloader is locked, OS is Miui 11 (Miui 12 is also available for it but I haven't installed it yet. Maybe there's a way to install it externally which would boot up my phone?)
Thank you for your help! I'd really appreciate it

Same problem with me please suggest some best sort of solution

pcjha said:
Same problem with me please suggest some best sort of solution
Click to expand...
Click to collapse
Hi, I recommend you first of all back up your data if still possible.
Then, reboot into fastboot.
-fastboot erase system
-fastboot erase cache
- fastboot erase userdata
-fastboot erase recovery.
Then clean flash a rom.

Bootloop, Mi logo doesnt even show up

I've tried to install new system in my Xiaomi Redmi Note 4 MTK.
From the system that I downloaded (I downloaded the correct version) I picked in TWRP to install from boot.img.
Unfortunately the system didnt boot but I could still enter recovery or fastboot.
Then I chose preloader.img and clicked reboot because I thought that at the worst case I'd jsut enter fastboot and fix it.
After this the screen doesnt lit up at all.
The only response is the vibration.
It keeps rebooting over and over again.
Is there any way to save it?
It seems to stop bootlooping when I hold all the buttons at once for a while but when I hold the power button the bootloop starts again.

Re-flash Stock ROM

Is it possible in my situation when I can't access recovery and fastboot?
Can you please tell how can I do that?

Have you tried: With phone off, hold volume up, and insert usb cable. This should turn the phone on and go into download mode or something like that.

TouchOdeath said:
Have you tried: With phone off, hold volume up, and insert usb cable. This should turn the phone on and go into download mode or something like that.
Click to expand...
Click to collapse
I believe its called the fastboot mode and as I said I unfortunately can't go there :/

Yes, we are talking about Mi logo stuck problem during boot. ... OR mobile goes in bootloop where every time shows Mi logo on the screen and shut House Cleaning Services Dubai

While installing your stock rom for your mediatek phone using sp flash tool just click the format all + downlaod option. This may blank out your imei and personal phone specific info

guys plz, you're talking like if I had any access to my phone.
I think I wrote it quite clearly that the only response that I get are vibrations and I dont see Mi logo. It's on for like a split second. Can't go to fastboot or recovery.
I talked about it with a guy on discord and it's loading preloader before boot that should go first so it can't be helped without valid tools. Makes sense to me, already bought a new phone.