Bootlooped and can't charge - Xiaomi Redmi 3s Questions & Answers

Hi.
So, I decided to root my 3s. Googled some instructions, everything went fine and I installed TWRP and SuperSU. Well, it turned out that a certain app won't work on a rooted device, and simply unrooting via SuperSU isn't good enough either - it seemed that the only way to make it work again is to flash a new ROM.
I downloaded an (official) recovery one, tried to flash it with TWRP... bootloop. I probably messed up and did something incorrectly; even recovery mode stopped working. Fastboot, thankfully, still did, so I got another (bootloader) ROM and tried MiFlash.
Except it didn't work that great either, eventually getting stuck on 100% and never finishing. What's even worse, when I was about to try again with EDL, the phone ran out of charge - now, when connected to a charger, it automatically powers on, shows the same bootlooped MI logo for about half a minute, then seemingly runs out of power and turns off - only to reboot again and repeat the process. Fastboot still works, but with so little time it's nigh impossible to do anything with. It feels like I'm out of options.
Any advice would be really appreciated.
EDIT: Managed to get into TWRP directly and can charge the phone now, so situation looks far less grim. Advice would still be helpful, but I'm pretty confident I can handle it now. Thanks for reading anyway!

Related

[Q] How to reboot into recovery?

I rooted my G2 about two months ago. I'm currently using MIUI, not the latest but the one before it. Somehow, my phone got turned off and when I tried to turn it back on, it was stuck in a bootloop. I have a custom recovery image so I don't know if that affects anything. I tried to reboot into recovery by pressing volume down and power, nothing happened. I then did volume up and power. It vibrated three times and the orange light started flashing. I pulled the battery and now when I try to turn it on, nothing happens. So how do I reboot into recovery and so I can restore my backup? Any help/suggestions would be greatly appreciated.
Never pull the battery during something like that. It sounds like your bricked. Someone else confirm?
I don't think it's bricked. I plugged it up and then Clockwork came up so I selected reboot now. Clockwork came up again so I tried to restore my latest backup and the screen went black. I'm going to let it charge and then give it another try.
Ok good. That's lucky because whenever you pull on a boot like that, it usually bricks. If you have the option, try to re-flash your ROM. Maybe even try stock. If you were getting a black screen, it's most likely you flashed incorrectly.
Ok, I was able to boot into recovery and now I'm restoring my backup. I don't think I had a custom recovery image with this one so hopefully I won't get stuck in a bootloop. When you say stock, do you mean before I flashed MIUI (it was the first rom I flashed)? Thank you for your suggestions and all of your help.
first install adb on you PC, it helps a lot in these kind of cases.
1. try "adb logcat", it would tell you about what's going on in your machine.
2. once you get your adb working, try "adb reboot recovery" to see if it could boot your phone in recovery.
3. if after doing everything you fail to boot either your phone or in recovery then try using PC10IMG to boot a stock rom and then re-root your phone.
I got it back working. For some reason, I'm just starting to think that it needed charging (the battery had been out for about a day or two). I do have adb installed and configured on my computer since I needed it to root. Thank you for your suggestions, I will definitely rember them if this happens again.
lol of course when you get black screen and led blnking means your battery begging for juice, you're lucky that when the phone booted back in recovery and you tried to restore a backup the phone went off before actually starting to restore, that would've bricked your phone
DO NOT FLASH ANYTHING WITHOUT AT LEAST 40% OF JUICE LEFT

sph_l720 [rooted] locked up

here is the problem, hope someone can help, cuz im driving myself crazy trying to fix this....
so, i flashed a custom rom (m.o.a.r.) and everything seemed to be going fine. the installation went off without a hitch, insisted i was in the clear and that the rom took. soon as it was done and auto rebooted my device tho, everything went sour.
it remained frozen on the samsung screen for approximately 2 hours then just shut off.... battery life was good so it didnt just die. (oh, might i mention i have had numerous roms on this device so its not my first time) i tried to turn it on but it remained stuck. so i pulled the battery and booted it into recovery (twrpv2.8.1.0) where i wasnt able to do anything. my sd card refused to mount and 3/4 of my internals were bare.
so i decided id try to throw it in download mode and use odin... at this point it warned me that i had no o.s. installed...... my phone goes into download mode but no matter what i do i can not get it to connect to me pc...
what do i do? is there anything i can do?
please help...

Help! Asus ZenPad 10 Z300 series stuck on logo screen

Hi, my wife got an Asus Zenpad 10 (Z300 series) tablet not too long ago, and recently it seemed to be acting up. It didn't seem to know what its battery level was so it'd suddenly shut down and would rarely stay on for a few hours if that.
I've been reading these forums and Google searching every evening for days now to no avail.
The the other day when i turned it on, it was in a bootloop. I had this happen on my own tablet so I was aware of using ADB and the recovery menu to wipe the davlik cache.
Except, that this Asus tablet only has fastboot screen (which I'd not seen before - my Samsung went to a different recovery mode), so I've been researching that more recently.
I got ADB and Fastboot working, erased the cache via Fastboot which stopped the bootloop, but it would only go as far as the logo with the little spinner circle. After messing around with fastboot trying to do a factory reset and put a custom recovery on it (TWRP) it now will only boot to the Asus logo and not even have a spinner anymore!
The flashing of anything - recovery, stock rom from ASUS (this file as I found elsewhere on these forums: UL-P01M-WW-3.3.8.0-user.zip -- although I'm not entirely sure i'm flashing correctly).
Anyway, I'm stuck with only an Asus logo or fastboot mode screen and am not that good with fastboot/adb since I only had to delve into it once to fix my own tablet over a year ago.
If anyone can help that'd be very much appreciated! :good:
[update]
OK so after failing to flash any zips (or anything!) to the device, I left it on in fastboot mode while I went to work. Now upon coming home the tablet is just a black screen! The laptop recognises it because Windows makes that chime sound when its plugged in via USB. But other than that, I can't get a response out of it Button combinations don't seem to help so now I'm not sure what to do!
Can anyone help me please? :crying:
Unless the bootloader is locked, you may have made a mistake trying to flash the ROM and trying to install a custom recovery. Anyways, if you hadn't made any changes yet to the system, I would have said check the battery first because it may be malfunctioning and not the phone it's self. I know from experience that it may have been the battery considering the way you said it was not reading the battery percentage right and shutting down. And that "bootloop", this was probably happening because it didn't have any power to start up the device as this is exactly what my device did when I had a faulty battery. My best bet is to 1 try to get a new battery, and then 2 see if your system is still intact otherwise try and reflash with the stock ROM (through adb or any computer to android debugger) and then reinstalling the right recovery that goes with the device or that of which is c-o-m-p-a-t-a-b-l-e.
Using CM12.1 on my SGH-T999
I exactly got the same issue, nothing I particularly have done as far I know, my tablet suddenly rebooted and now is stuck on Asus logo with the little circle that keeps turning.
I tried to let it go till my tablet get completely discharged and also tried to charge it completely, nothing change.
And when I wanna access to the recovery, I just get the green android mascot with the message "ERROR!". So I can't even access the recovery to reset my tablet :crying:
Edit: Tried a fastboot erase userdata and an erase cache, still bootlooping
Sorted
The only way I fixed this was by returning it to the shop and having the device replaced! Not the ideal solution, but it worked. :good:
MrLewk said:
The only way I fixed this was by returning it to the ship and having the device replaced! Not the ideal solution, but it worked. :good:
Click to expand...
Click to collapse
I guess I will have to do the same
MrLewk said:
Hi, my wife got an Asus Zenpad 10 (Z300 series) tablet not too long ago, and recently it seemed to be acting up. It didn't seem to know what its battery level was so it'd suddenly shut down and would rarely stay on for a few hours if that.
I've been reading these forums and Google searching every evening for days now to no avail.
The the other day when i turned it on, it was in a bootloop. I had this happen on my own tablet so I was aware of using ADB and the recovery menu to wipe the davlik cache.
Except, that this Asus tablet only has fastboot screen (which I'd not seen before - my Samsung went to a different recovery mode), so I've been researching that more recently.
I got ADB and Fastboot working, erased the cache via Fastboot which stopped the bootloop, but it would only go as far as the logo with the little spinner circle. After messing around with fastboot trying to do a factory reset and put a custom recovery on it (TWRP) it now will only boot to the Asus logo and not even have a spinner anymore!
The flashing of anything - recovery, stock rom from ASUS (this file as I found elsewhere on these forums: UL-P01M-WW-3.3.8.0-user.zip -- although I'm not entirely sure i'm flashing correctly).
Anyway, I'm stuck with only an Asus logo or fastboot mode screen and am not that good with fastboot/adb since I only had to delve into it once to fix my own tablet over a year ago.
If anyone can help that'd be very much appreciated! :good:
Click to expand...
Click to collapse
Asus has the firmware (Nougat) for this Z300M but I've no idea how you would get this loaded. Something to learn but as long as the OS is available you should be able to get back stock, latest OS............
zls

Can someone please help me?

I have a mojo that will not boot properly. I have flashed many of these boxes and never had any issues. This was fully working 12.1 that I gave to a friend about a year ago. When plugged in it does absolutely nothing I found with USB plugged in and rapidly plugging and unplugging the power I can get into fastboot. Through fastboot I can get to TWRP and from there I have re flashed rom tried 202ww 205 and even restored backup no matter what it will not boot not even back to TWRP without fast boot command also have to do the rapid plug and unplug of the power I have found that I can boot into the ROMs by loading the boot.img through fast boot. I have even tried factory reset through Android but it does nothing everything still appears. This is now over my head and I'm not sure what to do. I do have another fully-working unit here but I don't even know what files would help me or if they would. Thank you all in advance this is a great forum and I would not have gotten anywhere without it
Hi Kal357, it sounds similar to an issue i had with a phone, where in a nutshell the storage became corrupt, and ran in write protect mode. So I could boot to TWRP, flash a ROM, reboot, but be back at square one... was a bit like ground hog day... the end result was binning it unfortunately. That said I do hope that this isn't your problem.
Thank you for replying. I kind of hoped more people would respond buy now. As far as write protect wouldn't make much sense as I have flashed different ROMs and been able to fully boot into the rom. Then again I don't even know what to think anymore? does anyone think I should be posting this somewhere else? I do not have any social media Accounts.

Nexus 10 bricked, bootloader possibly corrupted: fix?

I just aquired a used Nexus 10 that I wanted to flash with Lineage. Before that, I had successfully flashed every android device I have ever owned, so I thought there'd be no problem. After unlocking the bootloader I tried flashing TWRP recovery (on Linux using fastboot in the terminal), but it took several minutes and when suddenly the sreen started flickering and the flash still wasn't done, I tried to CTRL+C to no avail. I figured that I'd at most corrupt the recovery which would be quite fixable, so I unplugged the cable and tried restarting the tablet. I could still select the options in the bootloader, but when I selected anything, it didn't work (not even shutdown).
Whenever I try to start the tablet now, nothing happens. When it is plugged in to the wall, it shortly shows the "full battery" symbol and the goes black again. No combinations for bootloader or recovery work anymore. I suspect that the unsuccessful flash corrupted the bootloader, so how could I fix that. I do have FTDI and STM32 flashing devices, if that is any help.
P.S.: I already tried removing the battery in case there was anything in volatile memory preventing the boot.
I kind of jumped the gun on this one. As I had suspected, aborting the recovery flash did not corrupt the bootloader. The solution was simply an empty battery. I didn't notice, because it showed me a full 100% when I initially tested it, so it might be a broken battery, after all.
But still, got it to work now. Thanks for this great community, I could not have learned all the android stuff without it.
Atreus said:
I kind of jumped the gun on this one. As I had suspected, aborting the recovery flash did not corrupt the bootloader. The solution was simply an empty battery. I didn't notice, because it showed me a full 100% when I initially tested it, so it might be a broken battery, after all.
But still, got it to work now. Thanks for this great community, I could not have learned all the android stuff without it.
Click to expand...
Click to collapse
Good to hear:good:
Please mark your thread as [SOLVED] if it is, or give us an update on how did you go about the battery perhaps?
Cheers

Categories

Resources