Hy, im looking for some help here with my Fire HD 8 2018, im going to resume my problem in what i do, and miss the Recovery Mode:
1. Firsy ill unlock the bootloader, instal TWRM, and install Lineage OS
2. Later ill Install Stock Firmware version 6
3. Then in OS6 ill update to version 7
4. After that Im stuck on Boot Logo "AMAZON", and i cant enter in TWRM or even Recovery Mode.
ill look for some guides for unbrick, but i cant get to star TWRM, or even Recovery Mode so no way to flash.
Any guide or help? Thanks in advance!
I am in the same boat (except my was just after installing Lineage the first time)
I have the same problem - unfortunately, I haven't been able to get it to fully boot with the latest OS 7 version, but you can revert back to 6. You'll need to pull the cover, then disconnect the battery. You can then reboot the tablet into recovery mode and reinstall v6. As long as you block the update, you can at least use the tablet.
If anyone else has a fix, please share.
I've got an old one running OSMO for my kids, I just have to make sure it doesnt reboot and push an automatic update.
Related
EDIT:
UPDATED POST AT THE BOTTOM!
Hey guys,
flashed czechops CM 10.2 a while ago everything was running fine.
On Saturday i decided to let the battery drain completely to do a full recharge. That`s when the Problems started.
After booting the Phone up i was stuck in a Bootloop with the Cyanogenmod Logo turning around and around and around and so on.
Okay i thought let`s reboot and see what happens.
Still the same.
I then booted into recovery by holding the x button on the keyboard and power and then when the androind in the triangle showed up using vol + and vol - to get into recovery.
I then deleted the cache and rebooted again (No full wipe to factory default trying to avoid that).
After that the phone turned on saying Android is getting updated Updating Package x of y.
After its done its now stuck in Apps getting started.
After i found out to get to the Bootmenu i decided to check the Recovery Menu there.
I can choose between Motorola Stock Recovery (the normal one i already was on)
and Team Win Recovery.
So i choose Team Win Recovery and thought okay since its not working im gonna install the Update of czechops 10.2
Installing itself worked fine. But now im stuck in the same loops.
Currently im goind a Backup of the System with the Team Win Recovery in the hope i wont loose the data even if what im trying to avoid a full factory wipe.
What kinda poped in my eyes when i started the recovery was that it said E: Unable to locate '/boot' partition for backup.
Could this be the problem which is stopping the phone from booting correctly?
And if so how can i fix it?
Hope anyone can help me,
Kind Regards,
Invi
I had te same problem before doing a clean install.
I don't know why but, if you install the android 10.0 tezet and from there start the gapps, creating a account and installing your apps, you do not have problems to install the 10.2.
Good luck.
Sent from my A953 using xda app-developers app
jonasgitz said:
I had te same problem before doing a clean install.
I don't know why but, if you install the android 10.0 tezet and from there start the gapps, creating a account and installing your apps, you do not have problems to install the 10.2.
Good luck.
Sent from my A953 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the heads up jonas.
Unfortunately its too late its seems. My Milestone is just a stone now it seems.
After trying to install 10.2 12.03.14 and that not working correct after doing a full factory wipe i decided to install cm 11 from czechop.
Unfortunately it seems it failed.
My milestone just boots up and stops at the First Logo. No lights. No chance to get in any recovery mode except the normal one.
Bootloader was working some time but stopped cause the Battery is almost empty.
The Problem is i cant even load the Phone anymore cause as soon as i put it on a charger it boots up and wont get enough battery power to live for a few minutes.
So the only thing left working is the normal Android 3e Recovery. Hope i can do anything from there.
Don't give up.
Your problem it's normal, you fisrt need a global battery charger to recharge your battery.
After it, go to boot recovery, you must turn on the milestone holding " volume down + camera" or "volume up + camera", than you need to uses the RSD Lite to reflash your milestone 2.
Normaly, when do you came from another room, you stay in boot loop, so you need to entery in Miestone recovery, "x + volume down" than after it you do a factory reset. It will boot normaly after that.
To go to boot recovery, you must turn on.
Try harder.
(Guys, lets try to help a little)
Sorry about my poor english
I wont. Already ordered an global battery charger yesterday. In the mail from the store delivery is 7-10 Weekdays.
Good thing i have a second cellphone which i can use in the meantime.
i had a similar scenario
Invisan said:
Thanks for the heads up jonas.
Unfortunately its too late its seems. My Milestone is just a stone now it seems.
After trying to install 10.2 12.03.14 and that not working correct after doing a full factory wipe i decided to install cm 11 from czechop.
Unfortunately it seems it failed.
My milestone just boots up and stops at the First Logo. No lights. No chance to get in any recovery mode except the normal one.
Bootloader was working some time but stopped cause the Battery is almost empty.
The Problem is i cant even load the Phone anymore cause as soon as i put it on a charger it boots up and wont get enough battery power to live for a few minutes.
So the only thing left working is the normal Android 3e Recovery. Hope i can do anything from there.
Click to expand...
Click to collapse
hi, I had a similar situation to that earlier today, in that I got to the situation where on boot up I got the Motorola logo then nothing else (I was trying to install C.M. 11 from 10.2 but when it went to install got a message E;// error - verification signature installation aborted), after major panic thinking I'd bricked my milestone, I tried starting the phone in bootloader mode (press camera, volume up and power buttons at the same time) which gives a black screen saying boot loader 70.13 and towards the bottom says boot menu, connect USB, then on your pc find program MOTOROLA SOFTWARE UPDATER (hope you've got it) open the program, it'll say connect a device plug your phone in and let it do it's stuff, takes about an hour (charge your battery using a desktop battery charger beforehand) and your phone will be returned to the stock Motorola rom but at least your phone isn't a brick and you can always start again trying cyanogenmod.
hope this helps
mark13_2001 said:
hi, I had a similar situation to that earlier today, in that I got to the situation where on boot up I got the Motorola logo then nothing else (I was trying to install C.M. 11 from 10.2 but when it went to install got a message E;// error - verification signature installation aborted), after major panic thinking I'd bricked my milestone, I tried starting the phone in bootloader mode (press camera, volume up and power buttons at the same time) which gives a black screen saying boot loader 70.13 and towards the bottom says boot menu, connect USB, then on your pc find program MOTOROLA SOFTWARE UPDATER (hope you've got it) open the program, it'll say connect a device plug your phone in and let it do it's stuff, takes about an hour (charge your battery using a desktop battery charger beforehand) and your phone will be returned to the stock Motorola rom but at least your phone isn't a brick and you can always start again trying cyanogenmod.
hope this helps
Click to expand...
Click to collapse
So i downloaded Motorola Software Updater and RSD Lite + Motorola Device Manager newest Version
Unfortunately my Milestone seems not to be recognized by either Software updater nor RSD Lite.
In the Device Manager S Flash OMAP3630 shows up and is recognized.
Im running Windows 8.1 x64 and on a second Computer Windows 7 x64
What tool can i use ander Linux? Maybe the Phone will be recognized there.
EDIT:
K found it. Doing it with Linux at the Moment. Its working.
Only need to Root it then and after that flash my old Files and hope they are working.
At least i have an old Backup i made from Tezet before going up to 10.2 which i made with Clockworkmod
Hope it will work and not be broken like the one i made with Team Win Recovery.
Anyone knows how i can change stuff in a Team Win Backup?
Invisan said:
So i downloaded Motorola Software Updater and RSD Lite + Motorola Device Manager newest Version
Unfortunately my Milestone seems not to be recognized by either Software updater nor RSD Lite.
In the Device Manager S Flash OMAP3630 shows up and is recognized.
Im running Windows 8.1 x64 and on a second Computer Windows 7 x64
What tool can i use ander Linux? Maybe the Phone will be recognized there.
EDIT:
K found it. Doing it with Linux at the Moment. Its working.
Only need to Root it then and after that flash my old Files and hope they are working.
At least i have an old Backup i made from Tezet before going up to 10.2 which i made with Clockworkmod
Hope it will work and not be broken like the one i made with Team Win Recovery.
Anyone knows how i can change stuff in a Team Win Backup?
Click to expand...
Click to collapse
I did find it took a long time for the Motorola software updater (about 20 mins) to detect my milestone 2 (I'm using windows7 x64), I'm thinking the mistake I made when trying to upgrade to CM 11 was I didn't wipe data/cache before trying to install it
mark13_2001 said:
I did find it took a long time for the Motorola software updater (about 20 mins) to detect my milestone 2 (I'm using windows7 x64), I'm thinking the mistake I made when trying to upgrade to CM 11 was I didn't wipe data/cache before trying to install it
Click to expand...
Click to collapse
Hi mark,
well Windows popped up saying N/A
when it should show new Software.
It also couldnt recognize my Cellphone correctly it seemed.
But i flashed it with Linux anyways.
Flashing to tezet`s 10 worked also like a charm
and i could install my Backup i made in december before
updating to czechops 10.2.
Guess after i know what to do now i will try to update to cm11 now.
Invisan said:
Hi mark,
well Windows popped up saying N/A
when it should show new Software.
It also couldnt recognize my Cellphone correctly it seemed.
But i flashed it with Linux anyways.
Flashing to tezet`s 10 worked also like a charm
and i could install my Backup i made in december before
updating to czechops 10.2.
Guess after i know what to do now i will try to update to cm11 now.
Click to expand...
Click to collapse
let us know how you get on as I'm tempted to try again (I do like how CM10 gets rid of all the un-necessary apps but gives you control of all the system parameters) but want to step up to CM11 without having the same problem as before.
Hi,
Have a weird situation, but try as much as I may, I'm unable to resolve it.
My phone is rooted (international D802) and was running fine. Had a screen issue and got it replaced at the service center but their system identified my phone as a rooted device, and a couple of days later the problems started.
The issues I'm facing right now:
1. The phone doesn't charge when switched on, at all.
2. The phone doesn't reboot either.. not instantly anyways. If powered off, or rebooted, the phone doesn't turn back on, it just goes dead. It does boot again though if tried after a couple of hrs.
3. The phone charges when its off (shows no light or indicator though, like its bricked)
4. Cannot go into either recovery or download mode. Coz the phone doesn't boot when restarted or when i try to reboot into recovery.
5. When it does magically start after a few hrs (upon long pressing the power button), even if I try to go into download or recovery via the vol keys, it just boots to android.
6. The phone is recognized properly as LG G2 under windows and all the drivers install too.
7. The phone isn't recognized under Linux... tried both Ubuntu and Knoppix.
Travelling out of the country in a few days, really need to sort this out.
Any and all help/suggestions will be greatly appreciated.
Thanks in advance
Somebody... Anybody? :'(
When your phone rebooted I would recommend you firstly to activate USB Debugging in the developer settings. You said your device is rooted? So try to install the Auto Rec recovery here
https://www.androidfilehost.com/?w=files&flid=13763 - but make sure you are on Kitkat. Now, install the app normal and let the app install all things. After installation, the app asks you to reboot to recovery, now press reboot to recovery.
Maybe you have luck and the phone reboots to TWRP. In TWRP you can go to Reboot and then Reboot to Download mode.
Now (if all worked) you can flash the stock rom .kdz file of the d802 via the FlashTool 2014.
Hope you have luck, please keep me up to date if everything worked.
Yours, Flo
Good luck!!
Thanks a lot for the response Flo, but the problem is that i never got around to updating to a Kitkat rom... the rom i was never got updated and I was kinda happy with how things were working so didn't jump on to any other rom.
Anything I can do in my current situation?
Go back to stock via lg flash tool
_____________________________________Read more write less and be smart
siggey said:
Go back to stock via lg flash tool
Click to expand...
Click to collapse
As mentioned in my first post, can't get into download mode.
Try this
http://forum.xda-developers.com/showthread.php?p=56000637
LG G2 is UNBRICKABLE NOW! [FIX REAL HARD BRICK]
_____________________________________Read more write less and be smart
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Nexicovx said:
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Click to expand...
Click to collapse
Your recovery is not corrupt. That is the stock recovery boot that you are seeing.
Anyways, how come you can't access ADB or fastboot? Because right now, that would be the easiest and fastest way to install TWRP back.
Nexicovx said:
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Click to expand...
Click to collapse
I am guessing the android man image you can see in recovery is laying on its back with its front flap open? Also says No Command?
If so, when on that page, hold the power button in and while holding it click up volume.
You'll see the stock recovery then.
Good luck
dadvs1 said:
I am guessing the android man image you can see in recovery is laying on its back with its front flap open? Also says No Command?
If so, when on that page, hold the power button in and while holding it click up volume.
You'll see the stock recovery then.
Good luck
Click to expand...
Click to collapse
When you get that Android lying down, press the Power Button followed by Volume Up. That will put you into recovery.
Could you not live boot the recovery? fastboot boot twrp.img.
Nexicovx said:
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Click to expand...
Click to collapse
Maybe im not fully understanding you, but it sounds like you can boot recovery and you can boot Android to the welcome screen. If I was you I would try
1.) Take out your sim and skip the full setup process to get straight to your home screen. Then turn on debugging in dev options > adb reboot bootloader
2.) Boot to android welcome screen, turn off phone turn back on holding volume down and power to get to the bootloader.
Fastboot wont work while you're in recovery. The main idea is to get to the bootloader so you can fastboot flash stock ROM and start from scratch
tonystarks260 said:
Maybe im not fully understanding you, but it sounds like you can boot recovery and you can boot Android to the welcome screen. If I was you I would try
1.) Take out your sim and skip the full setup process to get straight to your home screen. Then turn on debugging in dev options > adb reboot bootloader
2.) Boot to android welcome screen, turn off phone turn back on holding volume down and power to get to the bootloader.
Fastboot wont work while you're in recovery. The main idea is to get to the bootloader so you can fastboot flash stock ROM and start from scratch
Click to expand...
Click to collapse
Hello, we appreciate your help
But from what I read and understand, the user, Nexicovx thinks that the Android bot with the exclamation mark, is a sign of corrupt recovery. While it is only the regular behaviour of the stock recovery.
When you boot into stock recovery, he would not be taken to it straight away. It will first show the screen, where the Android bot with some sort of warning sign appears. At that point, he would just have to press the Volume up key, and tap the power button once. This will trigger the stock recovery.
Now, to what you can do @Nexicovx. You need to access a PC and the USB cable. Boot your 6P into bootloader mode by powering it off first, and then press and hold the Volume Down and Power keys altogether until you see the bootloader mode. From there, you can flash the TWRP recovery. Download the latest image from here: https://dl.twrp.me/angler/
And now use the following command to flash it:
Code:
fastboot flash recovery twrp-3.0.2-0-angler.img
Once that is done, you can reboot into TWRP and flash your desired ROM.
Thanks everyone. I misunderstood what the stock recovery looked like and surprisingly I didn't see much information related to this. I have since gotten my phone up and running thanks to your replies.
I forgot exactly what the problem was but I did get it sorted. Thank you.
Nexicovx said:
Thanks everyone. I misunderstood what the stock recovery looked like and surprisingly I didn't see much information related to this. I have since gotten my phone up and running thanks to your replies.
I forgot exactly what the problem was but I did get it sorted. Thank you.
Click to expand...
Click to collapse
Good to know that. :highfive:
I do have one final issue that I haven't resolved yet but I'm going to do another test next week. I live in China and with the latest update I can't install GApps (when the phone reboots after flashing my phone can't connect to the internet even though I'm through a VPN Wifi connection which works perfectly if I don't install GApps).
I'm going to try the last known security update I was using on Pure Nexus from 2/18 and see if this works. I don't remember which Vendor image I used then but I'm not sure if it is too important. I'll post here if it fixes my troubles. I'm having wifi troubles on the latest build and this is what is making me think I'm having my GApps trouble.
Nexicovx said:
I do have one final issue that I haven't resolved yet but I'm going to do another test next week. I live in China and with the latest update I can't install GApps (when the phone reboots after flashing my phone can't connect to the internet even though I'm through a VPN Wifi connection which works perfectly if I don't install GApps).
I'm going to try the last known security update I was using on Pure Nexus from 2/18 and see if this works. I don't remember which Vendor image I used then but I'm not sure if it is too important. I'll post here if it fixes my troubles. I'm having wifi troubles on the latest build and this is what is making me think I'm having my GApps trouble.
Click to expand...
Click to collapse
It could be a vendor issue.
Good to know!
Ok so I was on a note 4/5 hybrid ROM and wanted to update to the latest stock unrooted ROM. Well it started off rough. I wiped it then tried to install QB3 via Odin but it didn't take so then I was stuck on download mode. I managed to get out of it by installing an OK1 ROM. I think that was the base of the hybrid ROM that I was on. That took and then I just used smart switch to update to the latest ROM and it worked. I tried to install TWRP via Odin but it doesn't take and I don't know why. Now every once in a while it will just turn off and I have to pull the battery out but then it goes to download mode. Sometimes I can reboot it and it will be fine. Other times it will go to download mode so I have to force it to boot into recovery. I select reboot system and then it goes back to download mode. I think the message at the top left of download mode says something about not being able to read mmc. Not sure what that means though. So it takes me several reboots going through the same process before it will finally boot normally. Has anyone else encountered this? I'd really like to get TWRP installed and root the phone but keep the ROM stock. I've tried installing a rooted stock ROM but it doesn't take. I don't know what else to do. Thanks in advance for any advice you guys have. If I don't reply it's because my phone rebooted and got stuck lol
If your getting the mmc message it's a bad sign. It usually means the board is going bad, it least that's what I've heard.
I actually found the cause of it. I had reactivation lock enabled so it wouldn't let me install TWRP or anything. Once I disabled it I was able to install TWRP and flash a rooted ROM. However it will still reboot at random times but it's not as much as before and it didn't get stuck in download mode.
Hello everyone, just wanted to say a quick thanks, after successfully rooting and installing custom roms on two phones thanks to the information on these forums, third time turns out to be a charm and I managed to hard brick my new P10 lite.
The situation right now:
no charge light, no combination of buttons will do anything, phone is dead and will not boot or vibrate.
my computer will recognize that a phone is connected, for example Hisuite will pop up when i connect the phone, and in device manager, it shows Lemobile android device and the submenu says Android bootloader interface.
how i got here:
i was trying to install lineage 14.1 from this haky86
https://forum.xda-developers.com/p8...m-lineageos-14-1-huawei-p8-lite-2017-t3649292
but before i did that, i used this guide to install twrp and supersu:
https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
everything went fine, on the stock operating system i had root and system was running.
when i installed lineage, i lost root and couldnt figure out how to get it back. so i used this guide to restore the stock system and was going to try again from the beginning.
https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
however, when i tried to reinstall lineage for the second, third and fourth time, i kept getting stuck in a bootloop with the lineage animation. it seemed to me that i needed to flash the vendor image, and i found a guide on xda how to do it, but it wouldnt let me flash to the vendor partition. (sorry, i dont recall the exact error and i cant get there anymore :/)
so in massive frustration and desperation, i tried to use this method:
https://forum.xda-developers.com/p8...uide-unbrick-huawei-p8-lite-2017-pra-t3713574
which i know is for a p8 and i never should have tried to install it, but it went through the whole download process and at about 50-60% on the recovery the phone went black and never turned on again.
i have read that perhaps disconnecting the battery for a few minutes might help? or is this something that dc unlocker can help with?
any advice would be greatly appreciated. if more information is needed, please let me know.
Hi,
Have you tried completely turning off your phone (pressing on/off button for roughly 20 seconds) and then booting into recovery (pressing Volume Up and Power key simultaneously for rouhgly 10 seconds)?
Best,
Kenny
Thanks for the reply, but as I said, no button combinations elicit any response. The only sign that the phone is not completely dead is that it will be recognized by my computer as an android phone, but adb (for example) says no device is connected.
lineage gives you bootloop due to wrong data partition format
bricked my p10 lite several times same ending
only way that always gets the phone back to life is flashing lineage, i took haazan's one
BUT BEFORE flashing the lineage 14.1 zip check partition format is ext4
when back on lineage and stock ROM is wanted boot into twrp and re change format to f2ts or how it is named and flash the stock zip
unbricked
edit:
saw your second post too late
if the phone does not response on any button(s) maybe adb sideload command for change partition format and then sideloading the lineage zip is a way?
I have a similar problem, I have a custom rom (Elemental) but I flash another custom rom, it was normal, in the reboot it not turn on, only is in fastboot mode, i flash original system, cust, boot, and another but it is the same, help me please