Hi,
I had this problem before and I thought I did something wrong, but I can reproduce the problem.
I had a rooted phone with TWRP Recovery but I want to go back to the stock rom and lock the bootloader.
I reflashed stock rom A2017G_B10_NOUGAT_FULL_EDL with MiFlash. This is Android 7.1.1.
After the flash I entered Recovery Mode and deleted the cache partition and did a Wipe Data/Factory Reset, too.
Then I did a simple first Setup and looked for Updates.
It Downloaded and installed: A2017GV1.2.0B12, still Android 7.1.1 and after a reboot and another look for Updates it showed me Android 8.0 is available and after the upgrade I had Version A2017GV1.3.0B02. Till this point no problems.
Again I check for updates and it offers me to update to A2017GV1.3.0B04. Its a small one, 582 mb only.
It's downloading it, installing it, rebooting and continuing the installation before the whole Android system is booting. That initial
reboot installation takes very long. Perhaps as long as the big ones with more than 1 gb in size.
When it finally reboots I see the boot menu and wait to boot Android. But the screen only switches black and nothing happens. Even when I press the keys or hold the power key nothing happens. I can't get back to the bootmenu. I found out that the phone is visible over USB for the PC. I see the Qualcomm HS-USB QDloader 9008 on a COM-Port, but I can't flash the software with MiFlash: I see that it's trying to send a "Hello package" which fails. So I have to wait until the phone is empty several hours later. But even then when I power it up I can't enter the bootmenu. Only the red LED is flashing then. So I think it's in EDL Mode then. The Reflash works at this point.
What can cause the problem here? Of course my first idea was a corrupt update. But then it would be known.
regards
Related
Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.
Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.
danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!
I've had some problems with my phone. My first phone ended up getting bricked 2 weeks after i bought it.
I was lucky enough to get it replaced by the store. After that i was careful with unlocking the bootloader and rooting.
I had some issues with the rooting (i have posted this in other threads already, so i won't bring that up again) ending up with having to flash a stock version of 574 from a page with roms available.
I was happy to see that the phone was again working. But ever since i flashed the stock rom, things are becoming very strange.
I'm unable to flash TWRP. The only way to access Fastboot is by first connecting the phone to the computer. And then hold vol down and power.
I am able to access Huawei eRecovery (but only by doing like with Fastpass using the computer).
I'm not allowed to update eRecovery or run recovery from eRecovery.
If something require a reboot, i need to use the cable, fastboot, vol+ into eRecovery and then select reboot.
Today i was prompted to upgrade from 574 to 584 (OTA) and the download and installation begins normally.
Only to end up having to... you guessed it:
cable+fastboot+eRecovery.
And the update fails.
The phone is working great apart from these issues. And i do not know why.
And this is why it feels like it is in some Twilight Zone. Or Hybrid-mode. Bootloader is unlocked. Firmware is stock.
But i always need to use the cable to start the phone.
Does anyone have a clue what is going on?
What kind of error it gave when you tried to flash TWRP?
No error. When i do adb reboot the phone shuts down, but does not reboot into fastboot.
If i first go into fastboot and flash twrp everything appear to be ok. But when trying to reboot nothing happens.
I just tried to flash a new rom onto my XZP, and upon rebooting from TWRP, it didn't load the rom. Just boot looped. I restarted and tried to get back into TWRP with pow+vol down, but it still boot loops doing that and it doesn't vibrate on the boot like it did before. It still just gives me the "device is unlocked and cannot be trusted" but that's it. No Sony logo, or TWRP. I tried using the "adb devices" command but nothing shows up. I cannot find out why. In device manager on Windows 10, it shows up as "Android" under unknown devices, but I can't find a driver that actually works. Anyone know what to do?
Which rom did you want to flash? Looks like you did something really wrong dude. The best you can do is just flash a stock rom with "Newflasher". You can get the with "XperiFirm". The correct device drivers are ready to download on the Sony developer website. Here are some informations about drivers for XZP and other devices.
Maybe you can get the drivers working, then flash TWRP again and do what you planned to do. But I really recommend to flash a stock firmware instead.
Did you also try to power down the handset with the Vol+ and Power buttons? If you hold them for 3 seconds it just restarts the phone, but holding the Vol+ and Power for 6 seconds turns the phone off completely.
Good afternoon
I explain the whole situation. I planned to put an update, from 9 to 10 Android - at that time, it was relevant
During the update, a crash occurred. As a consequence, the phone does not boot into the system (not bootloop)
It hangs on the initial screen saver - I even tried to wait for the download.
He enters fastboot, works with it - but the loader is blocked.
In Recovery, it also comes in, but does not cling to adb sideload, that is, it is seen in fastboot, but not in recovery.
I also tried to flash it in edl mode - later I read that it does not know how to flash like that.
PS. Changing usb ports, nothing has led to anything
Ok, so... this is gonna be quite long to tell, but I need to explain the situation as carefully as possible because the problem I have seems to be very specific and potentially solutionless.
So, a week ago my Samung Galaxy Tab S6 Lite (SM-P610, CSC: ITV, which is the Italian Country Code and it's for unbranded devices, since my model is Wi-Fi only), suddenly started to restart itself and it's been stuck for days in a bootloop (i.e. it's stuck on the logo and if I hard restart it with Volume Down + Power, it gets stuck there again). Yesterday I found out that it's most likely a software problem, so re-installing the Android version should fix everything up... right? Well, I did just that but the device is still stuck on the bootloop.
Here I want to be more detailed: firstly, I'm 100% positive that the problem I have is NOT due to a virus, as I've never done ANYTHING that could potentially lead me to taking a virus (such as downloading apps outisde Google Play, visiting risky sites etc.); secondly, I followed a procedure that was supposed to repair my device without losing data. That's because I've stupidly never made a backup and I can't afford to make a factory reset. The procedure I followed consisted in finding the Android update I needed with Frija, and then downloading everything in the tablet with Odin. Also, I'm 100% positive that I made NO mistakes during the installation procedure. The only step that I did differently is HOW I installed the update: I did it with Download Mode, not with fastboot, because when I go into Recovery Mode and reboot the device into bootloader, the PC doesn't recognize my Tab, even if the PC does recognize that it's connected, as it makes the typical sound of when you plug something in a USB port (I have the USB drivers installed in my PC, I think it doesn't work because I never unlocked bootloader). What I get when I reboot into bootloader is "entering fastboot..." stuck screen and the PC and Odin aren't able to recognize it.
My questions are therefore these:
Is there a way to make a backup of the data of my device if I can't boot it (maybe via Download Mode)?
Is there a way to make fastboot work if I can't boot my device?
Is there some other way to repair my tablet that I can try?
Thank you for any help, this is my last hope to find a solution for my problem.
neo4458232 said:
When your device is stuck on an Android boot loop issue then you can fix it by simply doing a soft reset. Turn off your device and the problem will be resolved.
Here are the steps to follow:
First, switch off your device and take out your battery from the phone.
If your battery is non-removable then turn off the phone for 3 to 5 minutes and again turn it on.
This method works effectively to fix the error of the boot loop issue. But if a soft reset does not work for you to fix Android phones stuck in the boot loop issue then you should follow the next method.
Method 3: Reboot System in Recovery ModeRebooting a phone in the Recovery Mode is known for fixing several errors and issues on your Android phone. So, if you are unable to start your phone in normal mode or your Android is stuck in a reboot loop, then restart your phone in Recovery Mode.
Method 4: Remove and Reinsert SD CardYou may also try to remove the SD card to fix the boot loop in Android. According to several user reports, this trick worked for them. So, you should try this.
First, turn off your phone > remove the SD card > turn on your phone normally, and check if your phone is out from the boot loop or not.
If it is still stuck in the boot loop, then go for the other solution.
Method 5: Reboot the Phone in Safe ModeThis problem may also occur due to problematic 3rd party apps. If you have recently installed an app on your phone and then you started facing this issue, then remove it from your device.
Or, if you are not sure which app is responsible, then try rebooting your phone in safe mode. Doing this will disable all the third-party apps on your Android phone and then you can easily find out if this is the reason behind this issue or not.
To do this, you need to follow these steps:
Start rebooting your phone.
When the device logo appears on the screen, long-press the volume-down button at the same time.
Now, your phone will automatically switch to Safe mode.
If your phone is no more getting into the boot loop, then it means one of the third-party apps installed on the device was causing this issue.
Now, find out the problematic app and uninstall it to fix the Android boot loop without losing data.
Method 6: Use Custom Recovery ModeWhen you find your Android is stuck on the startup screen due to the boot loop issue, then you must try to restart the phone in the Custom Recovery mode. Here is the guide to do so:
To enter into the Custom Recovery mode press the Power + Volume down buttons simultaneously.
Select the “Advanced” option in the Custom Recovery menu.
Next, choose “Wipe Dalvik Cache”. Choose “Yes” when prompted for confirmation.
Move to the “Mounts and Storage” option and choose “format/cache”. It will clear the cache files completely.
Restart your device.
Method 7: Fix Android Bootloop Error Via CWM Recovery [For Rooted Phone]Maybe you are not aware of this method but it’s a useful way to fix the boot loop issue on Android after the update. Remember that this method is only for rooted phones. Here CWM means ClockworkMod and if your phone is stuck on the Android boot loop then it must be downloaded and installed on phone. Read me
Click to expand...
Click to collapse
Thanks for replying but I already tried every method listed here.
At this point it sounds like you need to bring it in to a local repair shop & see if they have a fix.
The solution is to wait on the turned on screen until the battery dies completely. Then put it to charge and after a bit using the reset combo (pwr+volume down) once the circular battery charging indicator with the green border comes. (It's a matter of luck, this keeps happening to my tablet and even the official samsung store can't fix it even though they took money to do the same)