Hello,
I have an LG Nexus 5X (Bullhead?) running PA 7.3.1-RELEASE (Android 7.1.2). It had PA installed on it when I purchased it from ebay some six months ago.
I really would like to go back to the original Google ROM but am struggling to do this.
I've downloaded SuperSU but when I run it I get "SuperSU SU Binary is occupied" and a "HOW TO SOLVE" button.
Clicking "HOW TO SOLVE" takes me to www supersu dot com faq subinaryoccupied which reassures me that: "Only needs a coffee's time to make it happen" and a Community link and Message Us link. Community Link returns a 502 Bad Gateway response (not very reassuring!), the Message Us link goes to a facebook group (SuperSUofficial). Is this route even worth entertaining? I feel I'm only at the tip of the iceberg in getting my phone returned to factory/OEM status.
Any advise would be most appreciated. (Sorry ,not allowed to post links as I'm under the 10 posts requirement)
Thanks, BloodBaz
Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.
Jacquestrapp said:
Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.
Click to expand...
Click to collapse
Thanks Jacquestrapp, that looks like exactly what I need. I'll give this a go this week and let you know how I get on. Thank you.
Jacquestrapp said:
Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.
Click to expand...
Click to collapse
Thanks Jacquestrapp. I'm struggling at the very first step.
Here's where I'm at:
Step 10 (How To Flash The Factory Images (And Return To Stock)) has the prerequsite that I have to unlock bootloader (section 1).
Gone to section 1
Enabled Developer mode (was already enabled)
Enabled OEM unlocking
Enabled USB debugging
Powered off phone
Booted into Bootloader (Power+Volume Down)
Connected phone to PC via USB cable
Opened command prompt, gone to platform tools but as you can see, I'm not connecting here:
Code:
C:\android\platform-tools>fastboot devices
C:\android\platform-tools>fastboot devices
C:\android\platform-tools>adb devices
List of devices attached
00cad250a0599972 device
C:\android\platform-tools>fastboot reboot
< waiting for any device >
My PC is the latest Windows 10 Pro (64-bit).
I have an LG Nexus 5X (Model LGH791).
And I'm guessing I've not got the right drivers installed but I'm struggling to find where to get them (I'm in the UK)
Here's where I've tried:
Attempt 1:
Followed the same guide to "Google USB Driver Install": https://developer.android.com/studio/run/win-usb.html
which takes me to: "Click here to download the Google USB Driver ZIP file (ZIP)" (latest_usb_driver_winodws.zip 8.3MB).
Downloaded, unzipped.
Gone to Device Manager but my phone doesn't appear under "Portable Devices" or anywhere else in device manager.
Attempt 2:
Gone to LG's website, entered model which lead to this page:
https://www.lg.com/uk/support/softw...00008356&subCateId=CT00008358&modelNum=LGH791
(but alas, no software!)
Can anyone advise on how to get the phone and PC to communicate?
Thanks
Chris
You mentioned that your phone has a custom ROM on it (Paranoid Android), which means it almost certainly has an unlocked bootloader. If you reboot the phone, the first thing you see when it reboots should be a message to this effect, advising you to lock the bootloader.
Jacquestrapp said:
You mentioned that your phone has a custom ROM on it (Paranoid Android), which means it almost certainly has an unlocked bootloader. If you reboot the phone, the first thing you see when it reboots should be a message to this effect, advising you to lock the bootloader.
Click to expand...
Click to collapse
Thanks, yes it does! Sorry, I not good at this. So the pre-req for section 10 is already done.
(I'm assuming I will still need to get adb / fastboot working at some point though).
I'll start looking into section 10 now. Thanks.
Are you connecting the phone to the PC through a USB hub? If so, try connecting directly to one of the PC's built-in USB ports. It's been a while since I first set up my PC for adb/fastboot so I'm not sure what to do about the fact that fastboot doesn't show the phone. I think I used the Android SDK manager, and not the ZIP file, to install the USB drivers.
Jacquestrapp said:
Are you connecting the phone to the PC through a USB hub? If so, try connecting directly to one of the PC's built-in USB ports. It's been a while since I first set up my PC for adb/fastboot so I'm not sure what to do about the fact that fastboot doesn't show the phone. I think I used the Android SDK manager, and not the ZIP file, to install the USB drivers.
Click to expand...
Click to collapse
No, directly onto USB port on top of PC. Tried both ports on top and a USB 3 port in the back. Still no sign of the phone in Device Manager.
I've got a laptop - I will try that next.
After that I will install the Android SDK manager (although I was hoping to avoid this for a one off job).
Thanks.
Okay, so I *think* my laptop is recognising the phone, however I still don't see the phone under Device Manager > Portable Devices or Device Manager > Other Devices (in fact, neither folder exists on my Laptop in Device Manager). However I have got "Nexus 5X" listed under Device Manager > USB Devices.
I'm now following instructions in section 10 of the guide you have given me:
"Download the latest build via the appropriate factory images for your model (Nexus 5X/Bullhead) here (https://developers.google.com/android/nexus/images?hl=en)".
For me this is 8.1.0 (OPM7.181005.003, Oct 2018) under "bullhead" (https://dl.google.com/dl/android/aosp/bullhead-opm7.181005.003-factory-e23fac1c.zip)
I've done the appropriate unzips and copies and I have the following folder set up:
Code:
Volume in drive C has no label.
Volume Serial Number is 1202-7717
Directory of C:\android\images
19/10/2018 22:55 <DIR> .
19/10/2018 22:55 <DIR> ..
01/01/2009 00:00 101 android-info.txt
01/01/2009 00:00 12,068,070 boot.img
21/09/2018 12:04 4,731,396 bootloader-bullhead-bhz31b.img
21/09/2018 12:04 57,989,632 radio-bullhead-m8994f-2.6.41.5.01.img
01/01/2009 00:00 17,847,530 recovery.img
01/01/2009 00:00 2,002,471,632 system.img
01/01/2009 00:00 194,892,768 vendor.img
7 File(s) 2,290,001,129 bytes
2 Dir(s) 136,452,927,488 bytes free
C:\android\images>
The next instruction is to "Boot into the bootloader and connect your phone to your PC via usb cable."
So I shut down my phone then booted it back up again using POWER +VOLUME DOWN buttons to get the screen with the big fat green START option and FASTBOOT mode showing
Connect USB cable to laptop and phone
BUT... now the device isn't showing anymore in Device Manager and running adb devices -l just says "List of devices attached" and nothing underneath!! Grrrrr!
Q1) Should the laptop still be able to communicate with the phone when the phone is booted into the bootloader?
Q2) Could there be something fundamentally wrong with the phone that is causing it not to be recognised?
Booting up the phone and disconnecting and connecting the phone a couple of times re-established the device. This time I was able to run adb reboot bootloader but as soon as the phone starts to shut down for the reboot, the connection to the laptop is lost and the laptop shows an error popup (temporarily) (wish I knew how to keep the popup visible but it was something about an error with the USB device).
Q3) Should I select RECOVERY MODE before I can expect the USB connection to reconnect? Documentation just says to go into bootloader (with the menu)
Any more advice is appreciated. Thanks, Chris
BloodBaz said:
The next instruction is to "Boot into the bootloader and connect your phone to your PC via usb cable."
So I shut down my phone then booted it back up again using POWER +VOLUME DOWN buttons to get the screen with the big fat green START option and FASTBOOT mode showing
Connect USB cable to laptop and phone
BUT... now the device isn't showing anymore in Device Manager and running adb devices -l just says "List of devices attached" and nothing underneath!! Grrrrr!
Click to expand...
Click to collapse
That last command should be fastboot devices, not adb devices.
BloodBaz said:
Q1) Should the laptop still be able to communicate with the phone when the phone is booted into the bootloader?
Click to expand...
Click to collapse
Yes, but using fastboot commands, not adb commands. With the phone in bootloader mode (the green screen with the big Start sign), you should see it listed after the fastboot devices command. Here's what I see:
Code:
C:\adb>fastboot devices
00bc94d02c6ab546 fastboot
BloodBaz said:
Q2) Could there be something fundamentally wrong with the phone that is causing it not to be recognised?
Click to expand...
Click to collapse
The phone's type-C port can collect lint, and plugging the connector into the phone compacts the lint. Over time, the lint layer can build up to the point where the connector no longer makes full contact with the port. I don't think that's your problem though.
@Jacquestrapp, thank you for your replies. You've been a life line.
After a couple of hours I think I've now managed to do it. I've tried two laptops, multiple USB ports and two USB cables. Whatever is happening, the PC/Phone connection seems very tempremental and I have to unplug and replug in the USB cable after each reboot. However, as you say, the fastboot commands did work after I figured this out, and from the fastboot screen. Also, whenever the phone rebooted or I disconnected the USB cable, the error message was as per attached screenshot.
So, I ran the following commands:
Code:
C:\android\platform-tools>adb devices -l
List of devices attached
00cad250a0599972 recovery product:omni_bullhead model:Nexus_5X device:bullhead transport_id:5
C:\android\platform-tools>fastboot flash bootloader C:\android\images\bootloader-bullhead-bhz31b.img
< waiting for any device >
Sending 'bootloader' (4620 KB) OKAY [ 0.212s]
Writing 'bootloader' OKAY [ 0.238s]
Finished. Total time: 0.493s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.009s]
Finished. Total time: 0.011s
C:\android\platform-tools>fastboot flash radio C:\android\images\radio-bullhead-m8994f-2.6.41.5.01.img
< waiting for any device >
Sending 'radio' (56630 KB) OKAY [ 1.633s]
Writing 'radio' OKAY [ 0.543s]
Finished. Total time: 2.300s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.013s]
Finished. Total time: 0.014s
C:\android\platform-tools>fastboot flash boot C:\android\images\boot.img
< waiting for any device >
Sending 'boot' (11785 KB) OKAY [ 0.538s]
Writing 'boot' OKAY [ 0.133s]
Finished. Total time: 0.786s
C:\android\platform-tools>
C:\android\platform-tools>fastboot flash recovery C:\android\images\recovery.img
Sending 'recovery' (17429 KB) OKAY [ 0.545s]
Writing 'recovery' OKAY [ 0.309s]
Finished. Total time: 0.900s
C:\android\platform-tools>fastboot flash system C:\android\images\system.img
Sending sparse 'system' 1/4 (508768 KB) OKAY [ 13.739s]
Writing sparse 'system' 1/4 OKAY [ 9.283s]
Sending sparse 'system' 2/4 (524230 KB) OKAY [ 14.787s]
Writing sparse 'system' 2/4 OKAY [ 8.650s]
Sending sparse 'system' 3/4 (501070 KB) OKAY [ 14.592s]
Writing sparse 'system' 3/4 OKAY [ 12.445s]
Sending sparse 'system' 4/4 (421469 KB) OKAY [ 11.842s]
Writing sparse 'system' 4/4 OKAY [ 16.174s]
Finished. Total time: 112.698s
C:\android\platform-tools>fastboot flash vendor C:\android\images\vendor.img
Sending 'vendor' (190324 KB) OKAY [ 5.424s]
Writing 'vendor' OKAY [ 5.682s]
Finished. Total time: 11.145s
C:\android\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.012s
The pre-google animation too ages and eventually talked about corruption on the filesystem. This is presumably because it had Paranoid Android installed on it previously. So I took the option to wipe everything (I don't have anything precious on the phone that isn't already backed up) and I've got myself back to stock Google and I'm very happy!
Thanks again for your support @Jacquestrapp.
The only thing I haven't done yet is relock the bootloader.
The guide states this warning:
"Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock"
Now that I am booting up fine in standard Google Android 8.1, is it okay for me to issue the fastboot oem lock command? I'm not going to kill my phone am I? If it's a "yes", then I'll probably leave it a few days before I actually do it.
Thanks
BloodBaz said:
[MENTION=301158]
The only thing I haven't done yet is relock the bootloader.
The guide states this warning:
"Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock"
Now that I am booting up fine in standard Google Android 8.1, is it okay for me to issue the fastboot oem lock command? I'm not going to kill my phone am I? If it's a "yes", then I'll probably leave it a few days before I actually do it.
Thanks
Click to expand...
Click to collapse
You're welcome. I *think* you are OK to re-lock the bootloader, but I've never done it, so I can't say with 100% certainty. Both of the 5Xs in my house have been running custom ROMs since I bought them. Also, if the USB connection is as temperamental as you say, take a toothpick (or something else thin and non-conductive) and poke around gently in the USB port to see if lint is the problem. It probably isn't, but it's easy enough to fix if it is: just dig all the lint out.
Related
NOTE: Bootloader should be unlocked for this method to work. Root not required.
1) Download the factory image relevant to your Galaxy Nexus from the below page.
https://developers.google.com/android/nexus/images#takju
2) Unzip the .tgz file and keep it under, say C:/
3) Edit the "flash-all.bat" and remove the "-w" parameter from "fastboot -w update image-takju-jwr66v.zip"
4) Delete "userdata.img" from "image-takju-jwr66v.zip".
5) Copy fastboot.exe file into the “takju-jwr66v” directory.
6) Reboot and keep the phone in fastboot mode. [ a) Turn on USB Debugging b) Turn off your Phone c) Hold down Volume UP + Volume Down + Power buttons ]
7) Issue the command "flash-all.bat".
8) Wait for the process to finish, and then the Galaxy Nexus will reboot upgraded with stock Android 4.3
9) Cheers and enjoy !!!
Logs below for even better understanding
=========================================
C:\gn4life\takju-jwr66v-factory-c2ef855e\takju-jwr66v>dir
Volume in drive C is OSDisk
Volume Serial Number is C49E-94F0
Directory of C:\gn4life\takju-jwr66v-factory-c2ef855e\takju-jwr66v
07/24/2013 11:25 PM <DIR> .
07/24/2013 11:25 PM <DIR> ..
05/07/2010 11:48 AM 578,611 adb.exe
05/07/2010 11:48 AM 96,256 AdbWinApi.dll
05/07/2010 11:48 AM 60,928 AdbWinUsbApi.dll
07/12/2013 03:56 AM 2,363,392 bootloader-maguro-primemd04.img
05/07/2010 11:48 AM 336,613 fastboot.exe
07/24/2013 11:08 PM 953 flash-all.bat
07/12/2013 03:56 AM 956 flash-all.bat.bak
07/12/2013 03:56 AM 827 flash-all.sh
07/12/2013 03:56 AM 785 flash-base.sh
07/24/2013 11:09 PM 295,614,131 image-takju-jwr66v.zip
07/12/2013 03:56 AM 12,583,168 radio-maguro-i9250xxlj1.img
11 File(s) 311,636,620 bytes
2 Dir(s) 7,925,932,032 bytes free
C:\gn4life\takju-jwr66v-factory-c2ef855e\takju-jwr66v>
C:\gn4life\takju-jwr66v-factory-c2ef855e\takju-jwr66v>flash-all.bat
sending 'bootloader' (2308 KB)... OKAY [ 0.314s]
writing 'bootloader'... OKAY [ 1.478s]
finished. total time: 1.793s
rebooting into bootloader... OKAY [ 0.006s]
finished. total time: 0.006s
< waiting for device >
sending 'radio' (12288 KB)... OKAY [ 1.675s]
writing 'radio'... OKAY [ 1.856s]
finished. total time: 3.532s
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: 0149BDCB0D012016
--------------------------------------------
checking product... OKAY [ 0.006s]
checking version-bootloader... OKAY [ 0.008s]
checking version-baseband... OKAY [ 0.007s]
sending 'boot' (4376 KB)... OKAY [ 0.709s]
writing 'boot'... OKAY [ 0.506s]
sending 'recovery' (4924 KB)... OKAY [ 0.662s]
writing 'recovery'... OKAY [ 0.689s]
sending 'system' (479244 KB)... OKAY [ 65.013s]
writing 'system'... OKAY [ 48.280s]
rebooting...
finished. total time: 115.913s
Press any key to exit...
So it's not just my bootloader that got slower. Yours also made you <waiting for device> each time the process rebooted the bootloader. It never happened before.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
beekay201 said:
So it's not just my bootloader that got slower. Yours also made you <waiting for device> each time the process rebooted the bootloader. It never happened before.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
yessssssssssss worked for me
Caused a bootloop for me and when I tried to reboot in recovery I got red triangle and Android. Didn't give any error messages.
Am just going to do full wipe now and retry.
Worked like a charm
Did what the post said and got 4.3 without losing any data.
Thanks!
Color me suspicious, but I bet there's a good reason that the -w is there...
flash successful without losing data.. but camera lag still exist on my gnex, and vitamio got multiple crash after rebooting. Anybody got the same experience?
I did get a bootloop by this method until I flashed by loosing data
omegagt said:
I did get a bootloop by this method until I flashed by loosing data
Click to expand...
Click to collapse
your gnex must be unlock to do this flashing process, maybe that's why you get the bootloop
banditnich said:
your gnex must be unlock to do this flashing process, maybe that's why you get the bootloop
Click to expand...
Click to collapse
I have updated my original post with this info. Thanks...
theillustratedlife said:
Color me suspicious, but I bet there's a good reason that the -w is there...
Click to expand...
Click to collapse
Got bootloop so I did full wipe and lost all data but all works fine.
omegagt said:
I did get a bootloop by this method until I flashed by loosing data
Click to expand...
Click to collapse
Same.
banditnich said:
your gnex must be unlock to do this flashing process, maybe that's why you get the bootloop
Click to expand...
Click to collapse
My GNex hasn't even been carrier locked(they don't do that in Belgium) and my bootloader has been unlocked since I got this phone.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
sui785 said:
Got bootloop so I did full wipe and lost all data but all works fine.
Same.
My GNex hasn't even been carrier locked(they don't do that in Belgium) and my bootloader has been unlocked since I got this phone.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Unlock refers to the bootloader not to carrier locking.
banditnich said:
flash successful without losing data.. but camera lag still exist on my gnex, and vitamio got multiple crash after rebooting. Anybody got the same experience?
Click to expand...
Click to collapse
Mine is still lagging when screen rotates, but if you deactivate screen rotation it works just fine.
I updated my UNLOCKED takju like this, and it seems to work ok:
- Download and unpack takju-jwr66v-factory-c2ef855e.tgz to some folder (gives you a subfolder called takju-jwr66v)
- Unpack file image-takju-jwr66v.zip (found in folder above, gives you files boot.img, recovery.img, system.img ..)
- Connect phone, make sure to activate debugging first
- Check with command adb devices , this should show you an id for your phone
Something like this:
List of devices attached
0149C25E0A011009 device
Go to folder takju-jwr66v and issue commands below
- fastboot flash bootloader bootloader-maguro-primemd04.img
- fastboot reboot-bootloader
- fastboot flash radio radio-maguro-i9250xxlj1.img
- fastboot reboot-bootloader
Go to folder image-takju-jwr66v
- fastboot flash boot boot.img
- fastboot flash recovery recovery.img
- fastboot flash system system.img
- fastboot reboot
DO NOT flash userdata.img !!
Gryph Lionheart said:
Mine is still lagging when screen rotates, but if you deactivate screen rotation it works just fine.
Click to expand...
Click to collapse
So I'm not the only one with the lagging camera bug, well camera work fine too with screen rotation disabled on 4.2.2.
Camera bug supposed to be fix in 4.3... maybe must do clean flash will do the trick...
But I'm too lazy to do backup and restore all apps and data on my phone right now, and already used to using another camera apps lately so the bug doesn't bother me that much to do clean flash all over again.
banditnich said:
So I'm not the only one with the lagging camera bug, well camera work fine too with screen rotation disabled on 4.2.2.
Camera bug supposed to be fix in 4.3... maybe must do clean flash will do the trick...
But I'm too lazy to do backup and restore all apps and data on my phone right now, and already used to using another camera apps lately so the bug doesn't bother me that much to do clean flash all over again.
Click to expand...
Click to collapse
Everything is working fine for me. No bugs.
This isn't working for me.
I typed in adb reboot bootloader to get into fast boot.
Then I ran the flash-all.bat file and it said "AdbWinApi.dll" not found. After adding this .dll to the folder a command shell opens with "waiting for device". Already turned on USB debugging and connected it to PC.
One issue though is that even though USB debugging is on, I can still connect to the phone as a media device and see all my files. I think you're not supposed to be able to access the phone's file while USB debugging is on.
So basically all the bat file does is has it stuck on "waiting for device." Although in fastboot if I type in "fastboot devices" it shows something like "X57U31581759 fastboot".
------------- Update ------------
So after watching a few youtube videos I found the problem: bad original instructions.
First the phone is to be on ANDROID, connected to the computer with USB debugging on. You can check to see if the device is connected using: adb devices
Then click the .bat file and it'll say "waiting for devices". Then I use another command shell and typed in : adb reboot bootloader to get into fastboot. This makes the .bat file work successfully.
If you start the procedure already rebooted into fastboot like steps 6 & 7 suggests, you'll be stuck on "waiting for devices" all day. Basically step 7 should be done before step 6.
Something wrong then, because I use flash-all.sh directly from fastboot, never had such an issue.
beekay201 said:
Something wrong then, because I use flash-all.sh directly from fastboot, never had such an issue.
Click to expand...
Click to collapse
Mine too, never had such issue. The flash all bat file executed from fastboot and its working flawlessly.
Sent from my Galaxy Nexus using Tapatalk 4
Didn't work for me either... Got bootloop... I had to wipe everything.
Q&A for Kindle Fire 2 7" Stock Restore
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Kindle Fire 2 7" Stock Restore. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Gen2 Kindle stock restore - stuck in a boot loop - following overlode's doc
Overlode - Huge thank you for the simple list for us NOOBS of how to get a stock Kindle stuck in a boot loop back up and running. I am having some problems though and was hoping for some help.
I am running Win7 on my PC. I've installed Android SDK, I have a factory cable and my gen 2 Kindle has the pretty "Fastboot" logo with the flashing green light and a non-flashing red light. When I go into my devices manager and see the "Otter2-***.***" it does have the yellow triangle. This is where I deviate from your instructions (in your .doc file). When I right click I do not see the simple "update driver software". I have to go through several windows to finally reach that option. No big deal. But... I clicked the option to "browse my computer for driver software" then "Let me pick from a list of device drivers on my computer". I do not have the option to select "Kindle". I went to have it list ALL DRIVERS and it is not in that list either.
I'm stuck. I don't know how to get the drivers up and working so I can continue with your instruction sheet. I REALLY appreciate all your efforts (with the drop box and everything). I've been fighting this boot loop for a month now and I'm scared to make a bigger mistake. I can build a pc from scratch- no problem... programming and mobile devices just make my brain hurt. Be kind. Everyone seems to throw around abbreviations like Halloween candy and this just makes me want to run for the hills. I'm learning but please don't just assume I know what you're talking about. Thanks in Advance!!
Myth421 said:
Overlode - Huge thank you for the simple list for us NOOBS of how to get a stock Kindle stuck in a boot loop back up and running. I am having some problems though and was hoping for some help.
I am running Win7 on my PC. I've installed Android SDK, I have a factory cable and my gen 2 Kindle has the pretty "Fastboot" logo with the flashing green light and a non-flashing red light. When I go into my devices manager and see the "Otter2-***.***" it does have the yellow triangle. This is where I deviate from your instructions (in your .doc file). When I right click I do not see the simple "update driver software". I have to go through several windows to finally reach that option. No big deal. But... I clicked the option to "browse my computer for driver software" then "Let me pick from a list of device drivers on my computer". I do not have the option to select "Kindle". I went to have it list ALL DRIVERS and it is not in that list either.
I'm stuck. I don't know how to get the drivers up and working so I can continue with your instruction sheet. I REALLY appreciate all your efforts (with the drop box and everything). I've been fighting this boot loop for a month now and I'm scared to make a bigger mistake. I can build a pc from scratch- no problem... programming and mobile devices just make my brain hurt. Be kind. Everyone seems to throw around abbreviations like Halloween candy and this just makes me want to run for the hills. I'm learning but please don't just assume I know what you're talking about. Thanks in Advance!!
Click to expand...
Click to collapse
EDIT: (a day or so later) Hey.. Nevermind. I was able to finally figure things out and downloaded KindleFireFirstAid and was able to wipe it out back to stock using my factory cable. The boot loop was limiting my options. Thanks Anyway.
Fastboot
What would be stopping Fastboot from recognizing my device? I have a fastboot cable for my kindle fire 2, I plug it into my computer then into the kf2, the kf2 boots up into fastboot mode my computer see the kindle and it has the proper drivers installed, but fastboot can't see it for some reason.
I had this problem before when I installed CM10 onto my kf2 but that was a year ago and for the life of me I don't remember how I got fastboot to see my kf2.
All i want to do is downgrade my kf2 back to stock and sell it on ebay. PLEASE HELP! I'm dying here
Any other options?
Overlode-My wife;s KF2 was stuck in boot loop so I tried your stock restore method with a factory cable. Everything seemed to work fine. The drivers were installed, fastboot commands worked on the device, etc. When I did the last reboot step, the device never turned back on. Now the device will not power up with the factory cable or USB cable. Is there anything I can do to fix this KF2 or is it permanently screwed? Thanks.
Kindle Fire 2 - Bricked
Today I tried the procedure in post http://forum.xda-developers.com/kindle-fire-hd/fire-2-development/kindle-fire-2-7-stock-restore-t2840987 but as I use Linux and have the SDK installed I entered the commands from console.
A couple of days ago I flashed Cyanogenmod using very similar steps.
Here is my log for the attempt to restore the stock ROM:
Code:
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.060s]
writing 'bootloader'...
OKAY [ 0.060s]
finished. total time: 0.120s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash boot boot.img
sending 'boot' (4310 KB)...
OKAY [ 1.082s]
writing 'boot'...
OKAY [ 1.053s]
finished. total time: 2.134s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash recovery recovery.img
sending 'recovery' (4828 KB)...
OKAY [ 1.211s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 2.165s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [114.081s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 28.939s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 143.021s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash system system.img
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
(1)
What is worse, after the failure I rebooted in order to restart with the procedure that worked a couple of days ago and leave Cyanogenmod in the Kindle...
but...
No reboot, no lights, no USB detected....
It seems that the tablet is hard bricked.
Is there anything that can be done except using it as a paperweight?
Thanks in advance
KF2 - hardbricked and restored.......almost!!!
Hi,
I have a KF2, which I had previously rooted and installed CM10 custom ROM. Had no problems with it, but decided to try a few more custom ROMS. Forgot about NOT using the KFU program as it was for KF1 devices, and for some stupid reason went ahead and flashed the wrong bootloader.
Result is fairly predictable - HARD BRICKED KF2!!
Thought that was it - searched the forums and everyone was saying the same - no way back from that! Then I came across Kurohyou's post and brilliant guide about hacking a card reader and attaching direct to motherboard. Followed his guide and voila - managed to boot up into recovery (TWRP). However after pushing the ROM files etc to try and install CM ROM again just kept getting "error flashing ROM" . I left the thing after trying various methods and different PC's etc to push the files across and gave up. When I went back to it this morning I couldn't get it to boot into recovery - which I thought was a bit strange. However FASTBOOT mode is ok - I have made a fastboot cable myself which works fine. Kindle was booting up with orange logo, quick flash, orange kindle logo again and repeat. It would not boot into recovery even though I had flashed the correct files via fastboot.
Again almost giving up when I came across Overlode's instructions. Followed them to the letter, and what I am left with now is the standard Kindle Fire logo (orange) which blinks after about 5 seconds and just stays there - left it for about an hour just in case....
I can post screenshots of me flashing the files as per Overlode's instructions if it helps. I get a few errors when using the wipe command, response is "erase successful, but not automatically formatting. File system type not supported" everything else is ok.
I still have the hacked card reader attached which through Ubuntu can see the EMMC directly so don't know if might be worth copying the files directly instead of flashing via fastboot?
Any suggestions gratefully received...... I'm at my wits end with this thing - I know I should have left well alone!!! but I feel like I have run a marathon with this thing only to have fallen flat on my face 5 metres from the finish line!!
Thanks in advance for any help.
lmayala said:
Today I tried the procedure in post http://forum.xda-developers.com/kin...opment/kindle-fire-2-7-stock-restore-t2840987 but as I use Linux and have the SDK installed I entered the commands from console.
A couple of days ago I flashed Cyanogenmod using very similar steps.
Here is my log for the attempt to restore the stock ROM:
Code:
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.060s]
writing 'bootloader'...
OKAY [ 0.060s]
finished. total time: 0.120s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash boot boot.img
sending 'boot' (4310 KB)...
OKAY [ 1.082s]
writing 'boot'...
OKAY [ 1.053s]
finished. total time: 2.134s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash recovery recovery.img
sending 'recovery' (4828 KB)...
OKAY [ 1.211s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 2.165s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [114.081s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 28.939s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 143.021s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash system system.img
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
(1)
What is worse, after the failure I rebooted in order to restart with the procedure that worked a couple of days ago and leave Cyanogenmod in the Kindle...
but...
No reboot, no lights, no USB detected....
It seems that the tablet is hard bricked.
Is there anything that can be done except using it as a paperweight?
Thanks in advance
Click to expand...
Click to collapse
Hi - see my last post - I too have a hard bricked kindle. if you're handy with a soldering iron you can try it - I can confirm it does work.
details here -
http://forum.xda-developers.com/showthread.php?t=2415870
I managed to get my kindle from nothing (not even charging light) to back up and running with TWRP installed. I couldn't get a custom ROM installed, kept getting errors - but I think my board has other issues. While I was putting it back together I managed to stick my screwdriver through the battery (don't ask!!!) Since then I think I have caused other damage and it was never the same again I think I may have damaged the memory or the EMMC..... on the hunt for new motherboard at present!
Good luck!
registered an account just to thank you. You saved my KF2.
Download script: HERE
Download Factory Images: HERE
Download ADB/Fastboot: Platform Tools
Download USB Drivers: USB Drivers -- Driver Installation Video
-----------------------------------------------------------------------------------------------------------------------------------------------------------
This script is for the UNLOCKED BOOTLOADER pixel2 / pixel2 XL, and will help:
Fix Bootloops
Flash both Slots A and B
Work with any Google-provided factory image
Detect bootloader and radio special *.img names automagically
(Optional): Unlock Bootloader and Critical
(Optional): Format Userdata
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Instructions:
Extract factory image zip file, as well as the image zip file within it!
This will lead to ~21 .img files in the same folder, with the deuce-flash-all script!
SEE SCREENSHOT!!.
Once you have all these together, run the Deuce-Flash-All script. ( .bat for Windows, .sh for Linux)
-----------------------------------------------------------------------------------------------------------------------------------------------------------
If you are having issues with this script:
Verify you have the environment variable (path) set for adb and fastboot
Try a different USB port
Try a different cable (preferably USB A -> USB C)
Format Userdata in Stock Recovery
Boot plain factory image before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
This was built for the 2 xl but I have modified it to work with the pixel 2.
The main thread, which has lots of troubleshooting Q/A is here:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Changelog:
06-13-2018: Added support for latest platform tools
01-14-2018: Fixed bug. Made unlocking optional to speed it up, combined scripts for taimen & walleye
01-09-2018: Removed support for locking bootloader, added hard-coded slot selections
12-26-2017: Added support for Pixel 2 (Walleye)
I have been using this on my walleye since v4, guess now we no longer get the errors for the critical unlock status.
Makes sense, thanks as always most beneficial tool besides adb itself for a pixel device!
Hey. When I boot my Pixel 2 XL I get a can’t find valid OS. Will this fix it?
It's possible ton unlock bootloader, install magisk / root without wipe the phone ?
Anyway, thanks for your great work !
Matt17000 said:
It's possible ton unlock bootloader, install magisk / root without wipe the phone ?
Anyway, thanks for your great work !
Click to expand...
Click to collapse
Unlocking the bootloader always wipes. Magisk, recovery, and other things will not.
You've saved me twice from a brick. Thank you.
Dude you are a freaking god send! THANK YOU!
Had anyone tested this with January 8.1 release? Just asking so I can update the top post. Working fine on XL
Deuces said:
Had anyone tested this with January 8.1 release? Just asking so I can update the top post. Working fine on XL
Click to expand...
Click to collapse
I am about to use it in 3 hrs. I am currently running dec patch with twrp and magisk. Ill try to sideload january patch soon.
I used it to recover from a softbrick, had an error on mac address 02:00 etc and fingerprint hardware, not sure if related to your Tool, but it did let me Boot back into system after everything else failed, all working again after factory flash with wipe
I modified the script to take away the locking section, as people can't seem to RTFM
Also included changes to hard-select the slot A/B and further warnings on relocking bootloader
Deuces said:
I modified the script to take away the locking section, as people can't seem to RTFM
Also included changes to hard-select the slot A/B and further warnings on relocking bootloader
Click to expand...
Click to collapse
Hi @Deuces, I wonder if you could take a look at this. I just tried running your script (third time so far). I used the latest Walleye script, made sure I had the latest fastboot and adb. Please see below...it looks like the script got as far as trying to write bootloader_b...then it got stuck at "waiting for any device" with the display blank. Eventually (after a long time) I gave up and unplugged the phone. I can't get it to turn on at ALL. Not by holding down power, not by using the key combo to get into fastboot...the phone just seems DEAD. I plug it into a charger, and nothing happens. Plug it back into PC, and the computer doesn't know that the phone has been plugged in. It's just not there in the Device Manager.
I tried following Google's steps to troubleshoot a phone that doesn't turn on. I did find that if I hold the power button down for about 30 seconds, I do feel the phone vibrate, and see a line across the display, like the few times that I've had to hard reboot. But that was it. Trying to get into fastboot mode, even holding the buttons for a long time, doesn't work.
Any idea what could have happened, or what I can do? The battery wasn't 100% full when I started, but it was at least at 85%. I'm sure the battery didn't die. I'm a bit freaked out, as I can't even get it to power on. Thanks in advance.
Deuces-flash-all-script-V4.3-Windows
for Walleye - Google Pixel 2
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Running Unlock
Look at your device,
press up arrow and Power to confirm
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.006s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
Setting current slot to 'a'...
OKAY [ 0.012s]
finished. total time: 0.014s
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 1.189s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.206s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.851s]
writing 'radio_a'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.690s]
finished. total time: 2.545s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
Setting current slot to 'b'...
OKAY [ 0.015s]
finished. total time: 0.017s
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 1.051s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.069s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
< waiting for any device >
JayBlack_686 said:
Hi @Deuces, I wonder if you could take a look at this. I just tried running your script (third time so far). I used the latest Walleye script, made sure I had the latest fastboot and adb. Please see below...it looks like the script got as far as trying to write bootloader_b...then it got stuck at "waiting for any device" with the display blank. Eventually (after a long time) I gave up and unplugged the phone. I can't get it to turn on at ALL. Not by holding down power, not by using the key combo to get into fastboot...the phone just seems DEAD. I plug it into a charger, and nothing happens. Plug it back into PC, and the computer doesn't know that the phone has been plugged in. It's just not there in the Device Manager.
I tried following Google's steps to troubleshoot a phone that doesn't turn on. I did find that if I hold the power button down for about 30 seconds, I do feel the phone vibrate, and see a line across the display, like the few times that I've had to hard reboot. But that was it. Trying to get into fastboot mode, even holding the buttons for a long time, doesn't work.
Any idea what could have happened, or what I can do? The battery wasn't 100% full when I started, but it was at least at 85%. I'm sure the battery didn't die. I'm a bit freaked out, as I can't even get it to power on. Thanks in advance.
Deuces-flash-all-script-V4.3-Windows
for Walleye - Google Pixel 2
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Running Unlock
Look at your device,
press up arrow and Power to confirm
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.006s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
Setting current slot to 'a'...
OKAY [ 0.012s]
finished. total time: 0.014s
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 1.189s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.206s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.851s]
writing 'radio_a'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.690s]
finished. total time: 2.545s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
Setting current slot to 'b'...
OKAY [ 0.015s]
finished. total time: 0.017s
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 1.051s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.069s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
< waiting for any device >
Click to expand...
Click to collapse
I've seen something similar as far as the phone not powering on. Technically tho, it was on but with a black screen.
Try holding VOL- and POWER for 30+ seconds to see if it powers off, then again to see if it comes back on.
I did read thoroughly and read that you've kinda tried this already, but after you get it to "power on" - do you get any return on the command:
fastboot devices
or
adb devices
?
Then, maybe try the new script i just updated - or tell me what OS you are running? if it's MAC / OSX, might wanna hold off.
Deuces said:
I've seen something similar as far as the phone not powering on. Technically tho, it was on but with a black screen.
Try holding VOL- and POWER for 30+ seconds to see if it powers off, then again to see if it comes back on.
I did read thoroughly and read that you've kinda tried this already, but after you get it to "power on" - do you get any return on the command:
fastboot devices
or
adb devices
?
Then, maybe try the new script i just updated - or tell me what OS you are running? if it's MAC / OSX, might wanna hold off.
Click to expand...
Click to collapse
Hi, thanks. I did try holding VOL - and power down for 30 seconds+. Actually, I did feel a vibration, but...nothing after. Couldn't get it to act like it was turning back on. Now that you mention it...I wonder if I did get it to turn on at some point during trying this over and over, because at times I saw the "scan line" appear across the screen briefly, like when I hard power off the device. But I've never seen the display light up at all, and nothing I've done has shown a device when issuing the "devices" command, either via fastboot or adb. I guess I need to screw around until I see that scan line, then it's "off." Then I've gotta get the thing to vibrate again, so it's "on." Then try seeing if I can run your script.
Boy am I glad I didn't try this late at night.
Oh, sorry, I'm on Windows 10.
Based on the return it looks like your bootloader got jacked up. I haven't seen that issue before. May want to get on chat with Google about an RMA.
Deuces said:
Based on the return it looks like your bootloader got jacked up. I haven't seen that issue before. May want to get on chat with Google about an RMA.
Click to expand...
Click to collapse
Sheeeeeeeit, just did that. Man...honestly, I might just go stock when I get this new one. Too much risk of mishaps, since I only keep the one phone around. Was just hoping to recover this one, as I'll be phone-less for a few days.
Side question - let's say I get the new phone, unlock the bootloader just in case, then don't do anything else, no rooting, etc. Do you know if that'll affect my ability to get OTAs actually over the air? I'm just bummed that every time there's an update, I've gotta go manually flash stuff and risk some shenanigans like this (and there's that persistent notification that doesn't go away unless I do so!). Should be easy, but I never had any luck with Google's flash-all script and always had to use yours to recover. Your script worked great...except for this time, something clearly went wrong (not pointing fingers, it's just how it goes).
Anyway, if you've got any other ideas, I'd try them out. Thanks for the responses thus far.
JayBlack_686 said:
Sheeeeeeeit, just did that. Man...honestly, I might just go stock when I get this new one. Too much risk of mishaps, since I only keep the one phone around. Was just hoping to recover this one, as I'll be phone-less for a few days.
Side question - let's say I get the new phone, unlock the bootloader just in case, then don't do anything else, no rooting, etc. Do you know if that'll affect my ability to get OTAs actually over the air? I'm just bummed that every time there's an update, I've gotta go manually flash stuff and risk some shenanigans like this (and there's that persistent notification that doesn't go away unless I do so!). Should be easy, but I never had any luck with Google's flash-all script and always had to use yours to recover. Your script worked great...except for this time, something clearly went wrong (not pointing fingers, it's just how it goes).
Anyway, if you've got any other ideas, I'd try them out. Thanks for the responses thus far.
Click to expand...
Click to collapse
If you can't get into bootloader, there's nothing I can do. There's some talk about using LG's downloader mode but LG has not released an image for it that I know of.
You can see this download mode by: Powered Off. Hold Vol+, insert USB cable connected from laptop.
If you have an unlocked bootloader, play store knows it - and some apps (netflix for example) - won't allow you to download their app from the play store. You could sideload the apk and it works fine, but still no updates from play store.. All of the apps I have work fine unlocked, minus Netflix.
You could disable OTA updates via developer options so that the notification goes away.
If you decide to stay stock, you could technically leave the bootloader locked, but the "allow oem unlocking" enabled in developer options. However, if something corrupts your OS, it's unlikely you'd be able to issue the unlocking commands from bootloader. That's the main reason I stay unlocked.
I've got the process down for upgrades myself. Download image, unzip, unzip the image within that, run my deuce-flash-all script. Boot up to Android once. Reboot to bootloader, fastboot boot twrp img, install magisk, reboot.
I do not flash twrp zip b/c it has been problematic for touchscreen drivers, and I'm around a computer anyway when doing these things.
The only reason I root is to use adaway. Every time I try to get used to stock, I hate using my phone because of ads.
I've tried the no-root-required VPN adblockers, but they drain battery.
Deuces said:
If you can't get into bootloader, there's nothing I can do.
...
If you have an unlocked bootloader, play store knows it - and some apps (netflix for example) - won't allow you to download their app from the play store. You could sideload the apk and it works fine, but still no updates from play store.. All of the apps I have work fine unlocked, minus Netflix.
...
The only reason I root is to use adaway. Every time I try to get used to stock, I hate using my phone because of ads.
I've tried the no-root-required VPN adblockers, but they drain battery.
Click to expand...
Click to collapse
Hey, thanks. I hear you. Oddly, I could've sworn that I had Netflix installed and updating on my bootloader-unlocked Pixel 2. Can't verify, sadly!
JayBlack_686 said:
Hey, thanks. I hear you. Oddly, I could've sworn that I had Netflix installed and updating on my bootloader-unlocked Pixel 2. Can't verify, sadly!
Click to expand...
Click to collapse
I can verify! I watch Netflix on my phone at work, downloaded from the play store on a pixel 2 unlocked, twrp installed and rooted with magisk. Not sure why everyone is having problems with it.
Hi everyone.
As many here i have some problem with a huawei watch, in my case the watch is not recognize by any O.S. (i try windows and linux), and i already download the driver and it was recognize by windows before i change the boot of the system.
Now the full history, The watch was restore to factory, but when it was trying to pair with a phone it was not recognize by wear os on the phone, and the synchronization with bluethooth was always aborted, i try with different phones but the result it was the same. Then i try to use the recovery by the fastboot menu of the watch, but it was not possible the watch didn't allow me to access.
Note : i'm using windows 7 for the flashing, and already try removing the battery, but it didn't work
The next step was to flash the watch with the original firmware, then i install adb, and the drivers, after that it was possible to establish connection with the watch, then i try again the recovery with the command.
Code:
adb reboot recovery
But it didn't work, then i use
Code:
adb reboot bootloader
The watch allow me now to use fastboot commands, then i try to download the firmware and i have and error when it was downloading the bootloader image.
Code:
C:\Watch_Gen\Platform-tolls\fastboot oem unlock
OKAY [ 0.029s]
C:\Watch_Gen\Platform-tolls\fastboot flash bootloader bootloader-sturgeon-m6e69f.img
sending 'boot' (1 KB)...
OKAY [ 0.009s]
writing 'boot'...
OKAY [ 0.513s]
sending 'booloadert' (13747 KB)...
OKAY [ 0.893s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.633s
in a guide that i found says that i only have to download the boot and the recovery then i used like this.
Code:
C:\Watch_Gen\Platform-tolls\fastboot flash boot boot.img
C:\Watch_Gen\Platform-tolls\fastboot flash recovery recovery.img
then i finish for that day, today i resume, but now the watch is not recognize for the system.
i press the power button to turn on the watch, and the screen turn on
Then the computer recognize the watch for a second and after that is like is disconnected form the computer.
after that the watch vibrate and don't do anything after that independent if i press the power button or not
In this point i don't know what can i do for establish some kind of communication with the watch, if someone can help me please, any suggestion are welcome
I tried an software update to the newst prerooted image from rbox but unfortunatelly installed Magisk V20 directly after it (without reboot).
After reboot my Fire TV 1 stopps now at the first white Amazon logo.
Fastboot via USB-A-to-A is working
dḿesg shows the follwing:
[10671.732229] usb 1-2: new high-speed USB device number 44 using xhci_hcd
[10671.887334] usb 1-2: New USB device found, idVendor=1949, idProduct=0401
[10671.887339] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10671.887343] usb 1-2: Product: FireTV
[10671.887346] usb 1-2: Manufacturer: Lab126
[10671.887348] usb 1-2: SerialNumber: xxxxxxxxxxxx
When I try to flash something I get the following message:
target reported max download size of 805306368 bytes
sending 'recovery' (9544 KB)...
OKAY [ 0.303s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.314s
This is strange since I unlocked the bootloader years ago.
Is there hope for my Fire TV 1 or did I finally brick it?
Update:
"fastboot getvar unlocked" gives me:
"unlocked: "
veeroohre said:
This is strange since I unlocked the bootloader years ago
Click to expand...
Click to collapse
Magisk won't work on the first fireTV
Flash a clean boot.img (the unlocked one in the prerooted rom zip) with fastboot onto boot partition.
Sus_i said:
Flash a clean boot.img (the unlocked one in the prerooted rom zip) with fastboot onto boot partition.
Click to expand...
Click to collapse
Would love to do that, but as mentioned I get the error message "flashing not allowed for locked hw".
I read that sometimes fastboot is the problem and not the hardware. Could that be? I'm on Ubuntu LTS 18.04.
You need to reflash the boot. Extract the boot_unlocked.img from bueller-5.2.7.3-rooted_r1.zip and flash it from the command line when you have the FireTV connected with the USB A-A cable.
fastboot flash boot boot_unlocked.img
EDIT: Here's my thread about it: https://forum.xda-developers.com/fire-tv/help/warning-attempting-to-flassh-magisk-16-t3778096
Sizzlechest said:
fastboot flash boot boot_unlocked.img
Click to expand...
Click to collapse
As I wrote, unfortunately this does not work:
< waiting for any device >
target reported max download size of 805306368 bytes
sending 'boot' (6460 KB)...
OKAY [ 0.206s]
writing 'boot'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.217s
Any other ideas?
Update:
Under Windows "fastboot devices" is not listing anything.
veeroohre said:
When I try to flash something I get the following message:
target reported max download size of 805306368 bytes
sending 'recovery' (9544 KB)...
OKAY [ 0.303s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.314s
Click to expand...
Click to collapse
Maybe try 'fastboot boot recovery.img' instead of a flash.
veeroohre said:
Any other ideas?
Click to expand...
Click to collapse
Connect the box via usb a-a cable to linux, boot the box and watch out if any mounted partitions pop up.
If yes, you may be able to follow this Guide.
Take a look here too.
Sus_i said:
Maybe try 'fastboot boot recovery.img' instead of a flash.
Click to expand...
Click to collapse
Doesn't work:
Code:
downloading 'boot.img'...
OKAY [ 0.304s]
booting...
FAILED (remote: Restricted command
)
finished. total time: 0.312s
Sus_i said:
Connect the box via usb a-a cable to linux, boot the box and watch out if any mounted partitions pop up.
Click to expand...
Click to collapse
With "fdisk -l" no partition shows up.
I think my box is dead :crying:
veeroohre said:
Doesn't work:
Code:
downloading 'boot.img'...
OKAY [ 0.304s]
booting...
FAILED (remote: Restricted command
)
finished. total time: 0.312s
With "fdisk -l" no partition shows up.
I think my box is dead :crying:
Click to expand...
Click to collapse
It seems so.
Writing a new boot.img to the fireTVs eMMC via hardware mod is probably a solution, but that's a bit overkill
Sus_i said:
Writing a new boot.img to the fireTVs eMMC via hardware mod is probably a solution, but that's a bit overkill
Click to expand...
Click to collapse
You're right. I thought about it, too. But too expensive and time consuming for such an old device. Probably I'll buy a new one. Although I hate to dump hardware which in principle still works .