Hello, I'm new here. I have rooted my new fire 7in 5th gen tablet. I used the flashfire beta app to flash a rom which I found out that the rom had bugs, so I decided to install cm12.1 using the same app, but the app glitch when it started installing the rom meaning it didn't finish and kept installing. I decided to power it down and reboot it back up. It showed the cyanogemod logo booting with animation but nothing booted up. It kept booting like a bootloop. I restarted it multiple times and the same errors keep happening. I tried go into recovery mode by holding the volume up + power button at the same time when i was boot it up. it only went to amazon logo and not recovery. I also plugged in the device to the computer using my factory cable to see if I'm able to enter fastboot mode. It worked, but it wouldn't allow me to flash anything. The tablet greeted me a message saying flash not allow, but the commands were able communicate with fast-boot and cant get it into adb because the boot loop. I had actually enter fastboot mode using commands which worked. Sometimes when i type a different command it said failed remote. Some commands actually worked but I don't what other commands to use to fix it. It has been 10 months since this happened to me. I'm not willing to give up on it because their has to be alternative ways of bypassing these issues. Is their any way you guys can tell me how to fix this? Thank you.
Related
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
whitechameleon said:
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
Click to expand...
Click to collapse
i have now tried to flash the firmware while in download mode using a less than legitimately obtained lg R&D tool. however, i need V10F_00.kdz and i am facing a bit of censorship. any kind soul willing to host this file on dropbox or similar so i can download it?
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
J2270A said:
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
Click to expand...
Click to collapse
believe me i have. the only combo i can get to is download mode. there is a combo for a hard reset, but my touch buttons arent active during boot.
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
KeybladePaladin said:
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
Click to expand...
Click to collapse
Please help.... I see you random viewer >.>
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
DoLooper said:
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
Click to expand...
Click to collapse
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
KeybladePaladin said:
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
Click to expand...
Click to collapse
Bootloader screen doesn't indicate fastboot mode. Getvar doesn't return anything. If flash commands worked, I'm sure someone would have reported it.
If you haven't tried all button combinations, you should. (You know, hold down power; try power and vol down; try all three.) Without recovery that's all I can suggest. Sorry this happened.
I got the same problem too.
I tried to root and install gapps follow this tutorial. Everything work perfectly.
One day, my Fire's battery was empty and it turned off. I charged it and when it started, it falt in bootloop. The screen show amazon about 8sec and reboot.
I booted into twrp and flashed only 2 files update-kindle-full_ariel-20.5.2.2_user_522053520 and supersu, try to make it work but it didn't
Now, when i hold power button , "Amazon" and then "Fire" appear and it stuck there.
I tried to get into recovery by power and volume+ but didn't work, the screen show "Amazon" and reboot and stuck on "Fire" again.
What should I do now?
Sorry about my English.
My wife was using her phone (completely stock, no mods whatsoever) and it started shutting down processes (contacts, calendar, etc). She held the power button down to manually shutdown and then rebooted shortly after. The next day, it started to do it again, so she did the same thing only this time it stuck on the "M" logo screen. When she brought it home, I held the power & vol down buttons in for 2 minutes and the phone began to reboot but still stuck on the "M" logo screen.
I began searching vigorously online for a solution and have tried everything. **NOTE** - I am completely unsure what version of software the phone was running before this happened. The first thing I tried was RSD Lite with the JB Stock file from Team US Cellular. The flashing fails during certain lines of the .XML file. I took suggestions from other users to delete the lines it fails on and let the file continue the flash. Once it reboots, it is still stuck on the "M" logo screen. I then tried all the other stock firmware files I could and the same result each time.
Next, I tried using ADB and Fastboot tools. My PC recognizes the phone when plugged in and running command "adb devices" shows the phone listed, but whenever I try to run a pull or other command, I get error:closed. I've tried all the solutions of making sure ADB files are updated, running the list of commands to get the daemon connection reset, etc. I can't push/pull anything using adb. I tried using mFastboot with no luck either.
I tried the above steps over and over for 3 days straight, hoping I missed something simple. My final option was to boot into Recovery Mode and run Wipe Data/Factory Reset. When I select that option, about 3 lines of command begin to run and the phone reboots and goes back to being stuck on the "M" logo screen. The command lines and reboot literally happen within 2 seconds. That tells me Factory Reset is corrupted, but I'm not 100% at this point.
Does anyone have any insight on if there is anything I can do at this point? It wouldn't be such a big deal to lose the phone, but we have pics/videos of our 2 year old that we never got backed up at home or in the cloud and they're very important to us. Unfortunately, the phone did not have and SD card. I'm honestly out of ideas at this point and have never felt so defeated.
I got brave and decided to just unlock the phone and attempt to install TWRP on it and that doesn't even work. It says it flashed it, but whenever I choose Recovery, it never boots to TWRP. It continues to use the stock recovery screen. I'm assuming this thing is just completely done for?
Hello,
I have a Wileyfox Spark since few months. At the beggining it was running with CM. Two weeks ago, I made the update from CM to Android Nougat, but after giving a try I dislike it. So I have tried (for the first time) to flash another ROM (CM or Lineage) but it is a pain.
As I was unable to root my device, I have used adb and fastboot to install twrp.
Here are the commands I enter :
Code:
adb reboot-recovery
fastboot flash recovery twrp.img
fastboot reboot
Then I press to volume down button to display the recovery menu but, instead of displaying the menu, the device boot again and again until I'm tired and I release the button. Then the phone boot normaly on Android...
For information, if I apply all these actions except the fastboot flash I can enter the recovery menu.
Am I wrong or missing something ?
Thanks for your help.
Slepwobo said:
Hello,
I have a Wileyfox Spark since few months. At the beggining it was running with CM. Two weeks ago, I made the update from CM to Android Nougat, but after giving a try I dislike it. So I have tried (for the first time) to flash another ROM (CM or Lineage) but it is a pain.
As I was unable to root my device, I have used adb and fastboot to install twrp.
Here are the commands I enter :
Code:
adb reboot-recovery
fastboot flash recovery twrp.img
fastboot reboot
Then I press to volume down button to display the recovery menu but, instead of displaying the menu, the device boot again and again until I'm tired and I release the button. Then the phone boot normaly on Android...
For information, if I apply all these actions except the fastboot flash I can enter the recovery menu.
Am I wrong or missing something ?
Thanks for your help.
Click to expand...
Click to collapse
Same here,but try releasing the Power-Button once it starts, helped for me booting into TWRP anyways.
BTW, how'd you manage to root that thing before? I am not able to do jacksh**t.
thanks a lot!
I can help you to get back booting up that phone again as it was. Is it still with that problem? I suspect you entered fastboot, unlocked bootloader and flashed TWRP on bootup the phone needed the stock recovery in order to factory reset due to the unlocking of bootloader. This way it boots to TWRP and runs the Open Recovery Script to decrypt and reset the device. This becomes impossible at certain progress and thus phone keeps on going to TWRP instead of booting. I shall address the issue well if you're still in need of this. I'm using the same phone also here
Sent from my Wileyfox Spark using XDA mobile app
Dear Community,
I am a real noob when it comes to Android, flashing ROM, root and so on.
I got a Oneplus here where supposedly root rights are on it and another ROM.
Current problem, as soon as I turn it on it hangs when booting. (Bootloop - red dot with 2 running white dots)
I already tried it with power + volume+. Unfortunately unsuccessful.
Is it correct when I press Power + Volume- that you get into fastboot?
I can't get into the recovery mode either.
I would like to get the device running, but without root rights, OEM lock and the Oxygen OS from Oneplus.
So far my attempts to get it running have been unsuccessful.
Update: after 4h in the bootloop, it booted successfully. *yeah*
So how i can see, if the phone is rooted and how can i lock it?
I tried it with adb, i can find the phone with adb devices.
Then adb reboot fastboot, after that i tried to find it with fastboot devices but then he finds nothing more. the drivers are installed. also fastboot oem lock doesnt work, because the phone is not found.