My fire was a bit lagging after the latest 5.6.2.0 update. So I thought of manually flashing the update using adb/fastboot method. I downloaded the stock firmware, which is 5.6.1.0) and flashed the firmware from recovery. After wiping the data cach I tried to reboot and unfortunately the device won't turn on. Looks like amazon anti roll back protection kicked in and bricked the device. Whenever I connect the device to my laptop the, I could see the popup for preloader drivers. Is there any way to save my device?
Bricked the Kindle. Do not make the mistake I did. Make sure you only inject the current version of software. Had to send it back, but they sent me a new one
Related
This is the second time it has happened. The first time was due to a Kindle Fire stock upgrade (but it shut down while in the middle of a game!), but after turning it back on the device no longer had a custom recovery, and it was unrooted.
It happened again today, and I'm pretty sure it's not from an update (it's already on the latest!)
No custom ROMs. What's the deal?
Note: The second time the shut down had occurred, the Kindle Fire kept the custom recovery and root.
I don't have anything out of the ordinary installed, a few games, a few apps, only MI Explorer which requires root. Does the Kindle Fire have an error log which may be reporting something, or do I have to connect it to my PC and monitor with adb log and hope the issue occurs while doing so?
Were you doing anything when it did that? or did you turn it on and find that it was starting over.
If the latter, that happens from time to time. Not indicative of a real problem, just happens.
If you were playing something, you might be having heat issues which is causing a reboot.
This issue happened to me on ICS ROM energy... I fixed it by flashing another ROM.. download kindle fire stock software or other rom from amazon.com or xda developers and flash using custom recovery... you will need to reroot.
My friend rooted his Galaxy Tab, and attempted to install a custom rom on it. For some reason, he flashed a jelly bean gapps zip, and now all of the google apps force close (still on the stock rom). This happens even after a full wipe and factory reset, since I would assume the wrong gapps has still been flashed. I downloaded ROM manager from the tablet's browser and tried flashing CWM recovery, but when I reboot into recovery, it just shuts off, and after a while, it's reverted back to the stock recovery (where I can't install zip from sdcard). In addition to this, for some reason, the tablet never gives the option to view files and folders on PC when connected via USB, so I can't even copy the zip files over (USB debugging is enabled). There isn't even any mount/unmount options in the storage settings.
What's going on here, and how can I fix this? As of now, it seems I can't do anything and I may just give it back to my friend.
adnana1024 said:
My friend rooted his Galaxy Tab, and attempted to install a custom rom on it. For some reason, he flashed a jelly bean gapps zip, and now all of the google apps force close (still on the stock rom). This happens even after a full wipe and factory reset, since I would assume the wrong gapps has still been flashed. I downloaded ROM manager from the tablet's browser and tried flashing CWM recovery, but when I reboot into recovery, it just shuts off, and after a while, it's reverted back to the stock recovery (where I can't install zip from sdcard). In addition to this, for some reason, the tablet never gives the option to view files and folders on PC when connected via USB, so I can't even copy the zip files over (USB debugging is enabled). There isn't even any mount/unmount options in the storage settings.
What's going on here, and how can I fix this? As of now, it seems I can't do anything and I may just give it back to my friend.
Click to expand...
Click to collapse
If you're looking to restore the tablet back to original purchased state then check out this thread here:
http://forum.xda-developers.com/showthread.php?t=1342995
Install Kies before using Odin as that will give you the proper drivers assuming you're using a Windows PC. The drivers will install the first time that you have Odin set up and you have the tablet in download mode. More than likely, even though you clicked start, Odin will sit or hang like it's waiting for something. If it sits for a while without doing anything at all, early on, close Odin and restart the setup process again. This time around the drivers are already installed and it should go smoothly from there. The tablet will restart on its own when its finished and after long boot you'll be greeted by the intial setup. It should naturally do about 3 software updates once setup is complete. That means that it will download the 1 update at a time and ask you if you want to install. After each reboot you should see more downloading activity until updates are complete I recommend after the very first boot you shut off mobile data and use Wifi only as these updates may munch up data...
Good luck.:fingers-crossed:
Wow, I really appreciate your response. I'll try this out later today, and post back with what happened (Can't right now as I'm at work). Thanks for your help!
My N7 16GB WiFi, rooted but stock, updated successfully to 4.3 some time ago. Basically, I used Voodoo OTA to save the root, let the OTA do its work, then restored root using Voodoo OTA. It's worked flawlessly since then.
Suddenly, after weeks with no issue, it started insisting it had to install 4.3 from a downloaded file. It nags constantly, which makes it hard to use the tablet. I've got CWM as the recovery so whatever file it's trying to install won't work from there. The only way I can find to go back to stock recovery involves wiping the tablet. I don't want to do that, unless there's no other alternative.
I looked for the update.zip file in the location that the tablet insists its stored at (root of SD card), but there's no file there by that name that I can find. It only shows up if I allow the nag screen to try and install it. Of course, CWM says that it can't verify the file and aborts the install. Which puts me right back at the ever-present nag screen.
Just to be clear, I am already running 4.3. This whole situation came up months after I'd upgraded. Is there anything I can do to stop the upgrade notices, short of running a factory reset and having to set up the tablet again from scratch?
May have found an answer. Used Wug's toolkit to force-restore the standard recovery. Had to do some old ADB driver removal for a bunch of other Android devices first. Appears to have deleted the unnecessary update file as part of the process. Will keep an eye on it going forwards, but think it's good.
Nope -- didn't work. Had to do a full factory reset/restore to out-of-the-box condition to get it to stop constantly trying to re-upgrade to 4.3. Annoying.
First time poster here.....in DESPERATE need of help!
So here's the rundown: After many attempts, I was finally able to update to KitKat 4.4.2 on my G2 with root intact. I wanted this for flashing the camera for 4k and 120fps modes. I attempted to install it today via TWRP but now I've basically bricked my phone.
Here's what I did:
- Installed FreeGee
- From inside FreeGee, I installed TWRP
- Installed TWRP Manager
- Copied .zip file to sdcard
- Booted into recovery mode
- Installed camera update
- Restarted and got a neverending LG Logo screen
I have since attempted every which way to recover from this. At this point, I don't even care about my data, I just want a working phone back! I am receiving no errors other than a frozen logo screen.
Here's what I've tried thus far with no success:
- ADB sideload (said phone was connected, got the dreaded "cannot read file" error no matter what I did).
- Factory reset
- Custom wipe of all but sdcard data
- LGFlashTools attempt to restore back down to 4.2.2 "o".....phone will not connect (read more below)
- Attempted fastboot flash from CMD prompt, just said "waiting for phone" forever
Some information......I CANNOT get the phone to be recognized on my PC when in "Download Mode". It never moves past the small Download Mode label into the "Firmware Update" with the big circular arrows circle. If I am in TWRP Recovery (which I get to by holding the Power and Volume Down button [original factory reset]), the PC does recognize the phone, but only under a new label called Android Phone, not Ports. I cannot change the COM ports at all as there is no option given under Properties.
I am at my wits end here. Any idea what I can do? It still appears to function normally under TWRP interface, but outside of that it's a brick. Please please PRETTY Please, anyone been in this situation and know what to do?
Thanks for any guidance.
Just wanted to give everybody an update here in case someone else is in the same situation.
So Sideload REFUSED to work even with the correct names typed. So I scratched that approach.
I anded up using the adb "push" method to send the zip file to the phone. I was having so much trouble with it at first, but I realized that was because I was going into sideload mode on the phone! You DO NOT turn on the sideload mode in TWRP if trying to push a file to the phone. You simply need the device recognized in the command prompt "adb devices" to say "23908hjf982j0e8jdf2 RECOVERY", or something to that effect. If you have sideload mode turned on, you will get the error, "error: closed". Well duh, it's closed for a sideload function! I should have caught this earlier.
ANYWAY, once I pushed a CyanogenMod 11 rom to the phone, it installed and booted right up! I didn't like it, however and wanted to go back to stock 4.2.2. So I downloaded the stock LG Jellybean rom and attempted to install it but it failed. Not sure why. I then downloaded KitKat 4.4.2 and installed it but that also failed, and this time it REALLY bricked it. I was getting loading errors on the LG Logo screen and it would shut off and act like it was turned off. At this point, I tried to restore to CyanogenMod from TWRP recovery, but it didn't work. Go figure.
I had a bricked phone. It wouldn't even boot into TWRP anymore due to the stock rom being partially installed (but failed).
Just when I thought all was lost, I attempted the old LGFlashTool reboot. I figured that maybe, just MAYBE....the Download Mode was fixed due to the partially installed stock ROM. I was right! I cleared all my old testing/configuration drivers on my PC and reinstalled the stock LGUnitedMobile 3.10.1 drivers, set the phone to download mode and VOILA! It FINALLY popped under a newly showing PORTS (COM & LPT) in my device manager. I configured it to COM41 as needed, configured LGFlashTool to load up the stock 4.2.2. jeallybean ROM, put the phone into Download Mode once again and LGFlashTool FINALLY recognized it and loaded up the stock ROM as it did the other day I tried it.
I am now on 4.2.2. rooted "q" (updated from "o" to "q" after installing SuperSU Pro and checked the Survival Mode option). I am moving up to KitKat 4.4.2. with Survival Mode on, which will keep my Root ability (Yes, it DOES work and have already verified it worked before all hell broke lose due to the xdabbeb's update on 4.4.2. (I probably did something wrong....not saying it's his fault!).
Anyway, just thought I would post this so that it may help someone else out.
Peace out gents.
goodlookin1 said:
I am now on 4.2.2. rooted "q" (updated from "o" to "q" after installing SuperSU Pro and checked the Survival Mode option). I am moving up to KitKat 4.4.2. with Survival Mode on, which will keep my Root ability (Yes, it DOES work and have already verified it worked before all hell broke lose due to the xdabbeb's update on 4.4.2. (I probably did something wrong....not saying it's his fault!).
Anyway, just thought I would post this so that it may help someone else out.
Peace out gents.
Click to expand...
Click to collapse
If you eventually want to have recovery as well you'll need to go back to 10d as later versions (o,q) break loki and are not compatible with the custom kernel needed to load stock based KK roms. But if you just want root until the next ota you're set.
I tried to flash xdabbebs mod on KK using flash gordon flasher and it worked fine for me.. http://forum.xda-developers.com/showthread.php?t=2250555
Sent from my LG-D800 using XDA Premium 4 mobile app
I have a Samsung s8 snapdragon 950U, T-mobile, running android 7.0, baseband - G950USQU2BQK5, build - nrd90m.G950USQS2BQL1. A couple weeks ago the mic stopped working so that I could not use speech-to-text which I rely on heavily. Nothing fixed it until I reflashed the phone with the same firmware. Before that I performed a ROM backup using clockworkmod and moved the backup files to my computer. I also used Titanium to backup system data like sms messages. After that, just as I was going to restore data, I get TMobile message that I’ve never seen before about a firmware update. I figured if it’s Oreo the update would fail because I have a custom ROM. Stupidly I chose to update and the next thing I know I have Android 8 – NOT rooted. That prevented me from using Titanium to restore settings.
Stupidly again, I decided to go back to the android 7 firmware and proceeded to root and flash the phone as I did before. This time it failed. I tried the SAMPWN and SAMFAIL methods repeatedly without success. Now I have bricked phone that just loops through a screen that says “Installing system update” followed immediately by another blue screen with a defunct android that says “no command.” I can get to download mode which Odin sees, but not to recovery, or anything that Smart Switch(which isn’t so smart) sees.
I have been downloading the Oreo firmware G950USQU4CRE9_G950UOYN4CRE9 for the past 4 hours hoping that I can maybe flash that. HELP! Can I somehow restore the nandroid backup using my computer? What should I do. I just need a working phone or I’m in big trouble.
frankygoes said:
I have a Samsung s8 snapdragon 950U, T-mobile, running android 7.0, baseband - G950USQU2BQK5, build - nrd90m.G950USQS2BQL1. A couple weeks ago the mic stopped working so that I could not use speech-to-text which I rely on heavily. Nothing fixed it until I reflashed the phone with the same firmware. Before that I performed a ROM backup using clockworkmod and moved the backup files to my computer. I also used Titanium to backup system data like sms messages. After that, just as I was going to restore data, I get TMobile message that I’ve never seen before about a firmware update. I figured if it’s Oreo the update would fail because I have a custom ROM. Stupidly I chose to update and the next thing I know I have Android 8 – NOT rooted. That prevented me from using Titanium to restore settings.
Stupidly again, I decided to go back to the android 7 firmware and proceeded to root and flash the phone as I did before. This time it failed. I tried the SAMPWN and SAMFAIL methods repeatedly without success. Now I have bricked phone that just loops through a screen that says “Installing system update” followed immediately by another blue screen with a defunct android that says “no command.” I can get to download mode which Odin sees, but not to recovery, or anything that Smart Switch(which isn’t so smart) sees.
I have been downloading the Oreo firmware G950USQU4CRE9_G950UOYN4CRE9 for the past 4 hours hoping that I can maybe flash that. HELP! Can I somehow restore the nandroid backup using my computer? What should I do. I just need a working phone or I’m in big trouble.
Click to expand...
Click to collapse
update: i was able to flash the oreo firmware basically puts me back at step 2. becasue i backed up when rooted my backups now cannot be restored, or can they, at least in part? Is there any way i can restore some of the data in either the nandroid or titanium backups to my nonrooted oreo s8?