I'm not an expert in Android, nor am I an expert with computers, just an average joe in the Android world. Since the time I got myself into this community I never stopped learning something small. I was able to root my phone, install custom firmwares, unroot my device, do a NANDroid back up. All of this done with the help I got from an online source. Now, I'm looking forward to do further tweaks in my device's system. It might sound risky, but I'm enticed by how far an android device can be further improved. But before I do any of this, I'd like to know the appropriate steps to do when something goes wrong like what if device ends up on boot loop.
Questions:
1) What is boot loop?
2) What causes boot loop?
3) Is it the same with a bricked phone?
4) Can the phone be recovered from it (boot loop / brick)?
5) What should be done when a phone is on boot loop?
I humbly ask everone to share a bit of your knowledge about this.
Thank you.
1 - Is kinda of obvious. Bootloop is when your device is stuck at some of bootscreens (model screen, Samsung logo screen) and it doesn't boot properly. Even if you remove the battery and insert it again to turn it on, it doesn't turn on.
2 - There are various reasons: incompatible kernel, incompatible rom, edits on build.prop, rom poorly flashed. And, for our device, if you try to reboot into recovery directly and it has CWM installed, it may enter on recovery bootloop.
3 - I''d say it is a "soft bricked phone". If you has access to recovery or download mode, congrats, you can undo the mess. But if you can't, you got a hard brick. So, it will need repairs.
4 - As I said before, if you has access to recovery or download mode, it is possible to recover it.
5 - It depends. First I would undo my last actions. If I don't have success, I would reflash stock rom, it's almost guaranteed.
So, it happened to my phone when I attempted to do a "Recovery Back Up" using "[ROOT] Rashr" app. I had a Recovery Boot Loop, which boots only into Recovery Mode. But it's fixed now. Here's the thread: http://forum.xda-developers.com/grand-quattro/help/s-o-s-device-boots-cwm-t2981980
This is a reference for those who have the same problem.
Related
So a friend recently bought this spanish voxter tab 97 IPS (16GB) and after a few days of usage and several attempt to install a custom ROM, the tablet stopped booting. According to him, he tried loading a "compatibility bla bla bla.zip" file with CMW which I really do not know what it is, and since he did the installation, the tab stopped booting into system. Every time it's turned on, it just stops at the boot screen and nothing more. Although before this, he had installed a custom recovery and had also done a Nandroid backup with the recovery. However, what baffles me is, CMW is no longer accessible through the normal "power + volume up" key combo and I'm quite unsure of how to boot into fastboot.
That aside, I tried booting into recovery with adb because apparently, adb recognizes the device whenever it's stuck at boot screen, this also failed, neither did rebooting into fastboot via adb work. All I need to know is if this device is totally bricked, or if there's still something I can do. If there's any, I really would appreciate every help offered. Thanks..
I apologize if this is in the wrong place, and I've really tried searching around, but nothing seems to work/ is tailored to the m8.
So, I just got an M8 new out of the box, rooted it and successfully installed cyanogenmod. Problem is, I was playing around with it, trying to get the GApp store and somehow (did what i think was) deleted my roms completely. Now upon booting up the phone I just get the "This build is for dev..." screen, and with the volume down+Power button to access recovery mode I constantly get put back to the fastboot screen. I tried flashing a custom recovery as in "Phone arena CWM flash recovery" guide, but no luck because my computer is reading the device as offline. I honestly have no idea what to do, and if anyone could help me I would be so greatful...
TL;DR: Stuck on boot screen, can't enter recovery mode, think i deleted all my roms, help please
On a scale of 1 - bricked, how bricked is my phone?
HUGE DEVELOPMENTS, GUYS! I've been able to access recovery mode again by re-flashing ClockWorkMod.
ctran1 said:
On a scale of 1 - bricked, how bricked is my phone?
Click to expand...
Click to collapse
On that scale, you are zero. If the screen comes on, you aren't bricked.
I've followed these instructions to the tee but have not had any luck with getting this to work. The flash always just results in my phone getting stuck on the "recovery booting.... recover is not seandroid enforcing - Set Warranty Bit : Recovery" screen. Odin reads as "PASS!" but my phone seems like it's just stuck. I've scoured over dozens of forums searching for answers but what works for others just doesn't seem to be working for me.
The instructions all seems so clear, and multiple forums' instructions gave me confidence that this would work no problem as long as I followed the instructions precisely. I guess that wasn't the case. I can't afford a new phone right now, but I'm sure my phone isn't completely bricked. There's gotta be a way! Can you please help me, xda community?
EDIT: I forgot to mention that I also tried the "uncheck the Auto Reboot option" method, and I'm a little confused about the last sentence. See below:
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
I'm confused about the "This will start the install process" sentence. I flash, let it finish until Odin says "Pass!", remove the battery, boot into recovery, and then I have two options from there - I can either go into download mode again, or I can start the phone normally. Starting the phone normally just brings me right to the recovery mode which gets stuck there indefinitely. I've left it there for 15+ minutes and it still just stays stuck there.
EDIT 2: Exactly how long is it suppose to take to boot up after it's been flashed?
EDIT 3: IT WORKS. So, If you just sort of hold down all the buttons at the same time, the phone will restart a few times and eventually bring you into the TWRP menu. This is what I was unaware of before. I'm not exactly sure what the specific method or timing is for that, but just tinker with holding all the buttons, and I think you can let go when you see little blue letters on the top left that says recovery or something. Of course, being able to access the TWRP menu means you must first have flashed the TWRP thing, which I did using Odin. Just download the latest TWRP .tar file and flash it with Odin.
EDIT4: SUCCESS! I am now successfully rooted! I reflashed the twrp-3.0.2-2-klte.img.tar and then I was able to access the actual GUI. I guess what I had before was some super stripped down version of the TWRP that only gave me access to a command-line looking interphase in recovery mode, with very limited options. So there you go, if you find yourself looking at pictures on forums of a supposed TWRP with an actual GUI you can navigate, that's because it does exist! Download the one I just mentioned, flash it using Odin, and boot it up by holding VolumeUP, Home, and Power. From there you can flash Zip files, just put the zip files into an sd card. I put my zip right into the sd card, not even in it's own folder or anything.
that version (8/26/2016) does not work at all for g900t, Maybe Chainfire wants to shut down CF_auto_root method.
you need to try the previous version (02/28/2016), I doubt you can find the old version in their website, Try google it on internet.
goog888 said:
that version (8/26/2016) does not work at all for g900t, Maybe Chainfire wants to shut down CF_auto_root method.
you need to try the previous version (02/28/2016), I doubt you can find the old version in their website, Try google it on internet.
Click to expand...
Click to collapse
Interesting, thanks for the info! Funny enough, while I was at Best Buy last night, I decided "what the heck" and asked a Geek Squad guy about my phone, and told him how I attempted to root and now it wouldn't boot, etc. He took my phone, and just sort of held all the buttons together and it restarted a few times, and he just kept fidgeting with it until eventually it came up to the TWRP recovery menu! So, I did a factory reset and started up the phone. It is currently on 5.1.1. I have since been able to get myself into the TWRP recovery menu by fidgeting like he did, even though I'm not entirely sure what exactly the timing or button combos are. The Geek Squad guy said he just held down ALL buttons, even VolumeUp and VolumeDown at the same time. So whatever, TWRP menu IS accessible finally.
At this point, I'd prefer to flash CM13 to it, and apparently I can just put the CM13 file on my phone storage/sd card, and then flash it through the TWRP recovery menu. But since I factory reset my phone back to 5.1.1, should I first update my radios? A techy friend of mine introduced me to a new fear - that if you flash a ROM that is incompatible with an older radio, it could "hard brick" my device. So now that's where I'm at. I want to flash a rom to gain simple root access, but don't want to risk bricking my device.
Here is my phone's information:
SM-G900T
Android 5.1.1
Baseband version G900TUVU1FOG6
Build Number LMY47X.G900TUVU1FOG6
I don't know how to mark this solved, but it is, as described my my 4th edit in the original post.
Bootloop,no way out: MT8735, 8", Android 5.1 (Archos 80b Helium), need general advice
Hello,
While trying to root my tablet (MT8735, 8", Android 5.1 (Archos 80b Helium)) I messed up, and trying to fix it made it probably worse. The device is stuck in a bootloop, but I can still get into the bootloader (I guess that's the right term) by powering up with Volume+ pressed after force power down (10s power button). I have the alternatives "Recovery Mode", "Normal Boot" - which result in a bootloop again if chosen - and "Fastboot Mode". Fastboot works, and I can connect the device with fastboot.
I'm afraid there's nothing else functional left on the tablet.
Unfortunately there is no stock rom and recovery available. All I have is an "update.zip" which contains a "boot.img", but no "recovery.img". So I tried to port a recovery image for a similar device (or rather deviceS so far) by replacing the kernel and some binaries from the boot.img.
Didn't help, still boot loop. Since I have bricked the device anyway, I decided to take the opportunity to learn more about these android devices (which in the end might help me getting the tablet running again), and here are my questions:
- Is the device able to boot into recovery mode if the recovery.img is ok, but there is nothing at all or nothing working in the "normal boot" section?
- Is there any way in the current situation to find out what is going wrong during the boot process? I can't connect with adb, so is there any way to get some logfiles or so with fastboot?
- As I understand the boot process, the bootloader initializes the memory and loads a kernel, either from the boot section or the recovery section. Am I right to assume that this part is still working on my device? Since I am able to get into the menu where I can chose between normal or recovery mode and fastboot, I don't think that the bootloader itself is broken.
- Assuming that this is right, is it possible to flash a minimal kernel and system into the recovery section, for example? Which does nothing else than show a message and then sits there and waits for power off? What I want to find out this way is whether the basic functionality (bootloader -> kernel -> initialize) is still there.
- If such a thing is possible, are there any suggestions to where to find such a minimal system? As said, I have a kernel for my device, can I build something around it to just give a sign of life?
Thank you for any hints and tips. Though it is annoying to have a bricked device, it is also exciting to be able to learn something new, if possible
Hello,
ummm, no offence meant, please, but isn't this here supposed to be a developers' forum? But still there is noone who can give me any advice about how to find the information I need and requested?
First of all I would need a minimal system - or a way to create one - which can be booted into as (fake) recovery, and which just gives any sign of life, like some message on the screen or an output through the interface, or even a text-line in some file, which I then could extract through fastboot. Or if not possible, I might find on the SD-Card, which I then could read on my PC.
Thanks and kind regards
Model: SHT-AL09, shipped with C636 (Asia) firmware. It may have originally been C00. Bootloop became a no-boot (it doesn't get past 'this device is unlocked' and load animation) after I flashed some system.img files in an attempt to fix.
I am willing to start from scratch. Fastboot works and Multi-tool works. Bootloader remains unlocked. Stock recovery is currently of no help.
I would greatly appreciate assistance. In the mean time, I'd love to know if it is possible to turn the screen off without letting the battery die out.
What did I initially do? I wanted to test some small changes to my build.prop (which I had already successfully tweaked). They were conservative changes that I felt for sure would not give me a bootloop. Worst case, I had a good build.prop file I could push via adb.
Turns out - a.) bootloop, b.) if USB debugging is not enabled adb is useless.
Early on, the device auto-booted into recovery, and I don't know if I pressed the power button or what, but some recovery process began. I didn't want to risk a wipe at that time, so I booted into download mode while process was at maybe 8%. I don't know if anything was wiped.
I was successfully able to flash system.img from c00/c434 firmwares....as noted that didn't get me anywhere....