Hey everybody,i have pulled out the image from HDX 7"(base on system version--13.3.2.5_user_325001120),it includes the "boot,recovery and system",i hope that it's useful for those who bricked their HDX 7".
if you need other image like “aboot,dkernel,modem,modemst” and so on,you can leave a message to me,although i think it not useful,it's enough for you having "boot,recovery and system".
By the way,i wanna know how to let the HDX 7" get into the fastboot mode?except of using the command--"adb reboot bootloader" ,it's useful when the HDX 7" in normal use,but in fact,if HDX 7" can't boot into the normal mode,you can't do anything about typing command,because computer can't recognise it as adb devices!
click the link to download the images! http://pan.baidu.com/s/1gd7VPib
Hey, thanks
It would be really nice if somebody came up with a solution to flash the firmware in fastboot mode (even in linux where u dont need any drivers).
I believe that would solve many bricked devices out there.
boom1212go said:
Hey everybody,i have pulled out the image from HDX 7"(base on system version--13.3.2.5_user_325001120),it includes the "boot,recovery and system",i hope that it's useful for those who bricked their HDX 7".
if you need other image like “aboot,dkernel,modem,modemst” and so on,you can leave a message to me,although i think it not useful,it's enough for you having "boot,recovery and system".
By the way,i wanna know how to let the HDX 7" get into the fastboot mode?except of using the command--"adb reboot bootloader" ,it's useful when the HDX 7" in normal use,but in fact,if HDX 7" can't boot into the normal mode,you can't do anything about typing command,because computer can't recognise it as adb devices!
click the link to download the images! http://pan.baidu.com/s/1gd7VPib
Click to expand...
Click to collapse
the question is how to unbrick the kindle if adb doesn't work ??
if using QPST , we need the xml files and how go to download mode
using pc only recognise QHSUSB_BULK, if install Qualcomm driver only detect as 9008, so need to change 9008 to 9006
so how to resolve this problem?? anyone can give some tutorial please.
thank you.
Check out this post, page 2 maybe has a solution for you. Good Luck!
http://forum.xda-developers.com/showthread.php?t=2795602
Hi friend,
I have a kindle hdx with fire os 13.3.2.5
I already rooted and installed safe trap
I already back up rom stock and flash your rom thor gapps 13.3.2.4 on rom slot
But when it go to first screen, it stop and reboot. And bootlop but can access safe trap.
I restore back up but similar can't boot.
I think i must flash rom stock 13.3.2.5 but i don't have zip file. Can you extract it ? please help. Thank. I hope your reply.
I know how to get into fastboot!!!
you just need to get a fastboot cable (the 2nd and 5th pins (or 1st and 4th?) are jumped. If you look up fastboot cable or factory cable you should be able to find it. I personally "made" one by taking a small piece of wire and sticking it under the proper pins in a semi-broken usb cable(wouldn't stay into device). I've had to use it many many times on my kindle fire hd 7"
CalebQ42 said:
you just need to get a fastboot cable (the 2nd and 5th pins (or 1st and 4th?) are jumped. If you look up fastboot cable or factory cable you should be able to find it. I personally "made" one by taking a small piece of wire and sticking it under the proper pins in a semi-broken usb cable(wouldn't stay into device). I've had to use it many many times on my kindle fire hd 7"
Click to expand...
Click to collapse
No, a fastboot cable doesn't do anything on the hdx
epicfailol said:
No, a fastboot cable doesn't do anything on the hdx
Click to expand...
Click to collapse
I've found it works if you first connect it to the device then connect it to the computer. Of course the device I'm working with for some reason has software version 11.3.2.5
umm
CalebQ42 said:
I've found it works if you first connect it to the device then connect it to the computer. Of course the device I'm working with for some reason has software version 11.3.2.5
Click to expand...
Click to collapse
Again again this is the HDX forum completely different from the HD different processor and everything .. If you plug a fast cable into the HDX it puts it in QUPST mode and takes a few minutes of messing with it to get it out of it so far we cannot use that either..so far.
jimyv said:
Again again this is the HDX forum completely different from the HD different processor and everything .. If you plug a fast cable into the HDX it puts it in QUPST mode and takes a few minutes of messing with it to get it out of it so far we cannot use that either..so far.
Click to expand...
Click to collapse
Sorry about that, I didn't know there was a 3rd generation kindle fire hd that looked exactly like the hdx. Been trying to root this thing for hours before I found that out
Sent from my Nexus 5 using XDA Premium HD app
boom1212go said:
Hey everybody,i have pulled out the image from HDX 7"(base on system version--13.3.2.5_user_325001120),it includes the "boot,recovery and system",i hope that it's useful for those who bricked their HDX 7".
if you need other image like “aboot,dkernel,modem,modemst” and so on,you can leave a message to me,although i think it not useful,it's enough for you having "boot,recovery and system".
By the way,i wanna know how to let the HDX 7" get into the fastboot mode?except of using the command--"adb reboot bootloader" ,it's useful when the HDX 7" in normal use,but in fact,if HDX 7" can't boot into the normal mode,you can't do anything about typing command,because computer can't recognise it as adb devices!
Hi Friend,
Flash boot & recovery is ok, but flash system is failed. It says FAILED (Remote: data too large)
Click to expand...
Click to collapse
Flash boot & recovery is ok, but flash system is failed. It says FAILED (Remote: data too large)
Click to expand...
Click to collapse
need special amazon fastboot binary for this
but you always can flash stock image wih twrp if you already unlocked.
ONYXis said:
need special amazon fastboot binary for this
but you always can flash stock image wih twrp if you already unlocked.
Click to expand...
Click to collapse
Thanks for your response. Yes, but in TWRP mode, I run "adb devices", the result is "13160d23................................unauthorized". Cannot push file.
It strange but anyway when you in TWRP you must see your device as MTP.
boom1212go said:
Hey everybody,i have pulled out the image from HDX 7"(base on system version--13.3.2.5_user_325001120),it includes the "boot,recovery and system",i hope that it's useful for those who bricked their HDX 7".
if you need other image like “aboot,dkernel,modem,modemst” and so on,you can leave a message to me,although i think it not useful,it's enough for you having "boot,recovery and system".
By the way,i wanna know how to let the HDX 7" get into the fastboot mode?except of using the command--"adb reboot bootloader" ,it's useful when the HDX 7" in normal use,but in fact,if HDX 7" can't boot into the normal mode,you can't do anything about typing command,because computer can't recognise it as adb devices!
click the link to download the images! http://pan.baidu.com/s/1gd7VPib
Click to expand...
Click to collapse
My device is 13.3.2.0. I follow this “http://forum.xda-developers.com/kin...to-unbrick-kindle-fire-hdx-firmware-t3277197” now in TWRP mode, but I don’t know how to flash the system.img.
By the way, I installed 13.3.2.3.2 stock firmware from TWRP, but it stick at Grey logo as well.
Samson Lau said:
By the way, I installed 13.3.2.3.2 stock firmware from TWRP, but it stick at Grey logo as well.
Click to expand...
Click to collapse
after flashing 13.3.2.3.2 go to TWRP - advanced - copy log to sd
and attach log that locatesd in the root of intrenal memory of your tablet.
ONYXis said:
after flashing 13.3.2.3.2 go to TWRP - advanced - copy log to sd
and attach log that locatesd in the root of intrenal memory of your tablet.
Click to expand...
Click to collapse
I did according to your advice, but it still stick at grey logo during reboot.
Please post your /sdcard/recovery.log here
or flash CM11 to be sure
ONYXis said:
Please post your /sdcard/recovery.log here
or flash CM11 to be sure
Click to expand...
Click to collapse
Good evening:
Are there any methods to get a Thor or Apollo running 4.2.5 or similar rolled back to the pre-3.2.5 as these posts seem to require? I have an Apollo running 14.3.2.5 which seems to be the lowest FW you can get to if you are running the higher than 3.2.5 FW.
I was wondering if the fastboot method would allow the flashing of a complete set of images from the earlier firmware series making an end run around the newer firmware?
Regards
galearned said:
Good evening:
Are there any methods to get a Thor or Apollo running 4.2.5 or similar rolled back to the pre-3.2.5 as these posts seem to require? I have an Apollo running 14.3.2.5 which seems to be the lowest FW you can get to if you are running the higher than 3.2.5 FW.
I was wondering if the fastboot method would allow the flashing of a complete set of images from the earlier firmware series making an end run around the newer firmware?
Regards
Click to expand...
Click to collapse
- can not roll back FireOS v4 below 3.2.8 due to anti-rollback barrier (intentional or inadvertent) that will brick device if further rollbacks are attempted
- 3.2.6 and below can be rolled back to 3.1.0 which can be rooted and unlocked. Rollback method contingent on starting point.
- native fastboot environment is crippled until bootloader unlocked
Related
Kindle fire came today with stock 6.2.2 firmware. Kindle Fire utility doesnt recongnize the kindle. I update driver that came with it, now its recognized as an android phone and no way to unistall that driver. I have mulitple pcs so I can just switch puters if need to.
All I need is a little help getting the pc to recognize it or someone to tell me I am screwed till a developer makes a update to the utility.
xFalkenx said:
Kindle fire came today with stock 6.2.2 firmware. Kindle Fire utility doesnt recongnize the kindle. I update driver that came with it, now its recognized as an android phone and no way to unistall that driver. I have mulitple pcs so I can just switch puters if need to.
All I need is a little help getting the pc to recognize it or someone to tell me I am screwed till a developer makes a update to the utility.
Click to expand...
Click to collapse
delivered with drivers ? that's completely new !
would try to use the drivers from kfu and kfu itself:
http://forum.xda-developers.com/showthread.php?t=1399889
extract and rename it to something like c:\kfu
win xp would be the best choice
edit: ahh i asume you meant the drivers from kfu
what is it telling under android phone (that's ok) ?
android composite adb interface ?
no the drivers that came with the fire utility is the drivers mentioned sorry. THe Utility tool just won't recognized it so it wont root.
just updated my last post
could you copy and paste the output of kfu ?
lemme switch back to my laptop thats what i was using. OS is windows 7 btw
EDIT: IT won't lemme copy the KFU text, can you quick post image? cause i don't see the option to
xFalkenx said:
lemme switch back to my laptop thats what i was using. OS is windows 7 btw
EDIT: IT won't lemme copy the KFU text, can you quick post image? cause i don't see the option to
Click to expand...
Click to collapse
try to pm me
edit: i assume the error message from kfu says "adbd cannot run in production builds"
error message tell me it can't locate and to make sure its connected which it is.
xFalkenx said:
error message tell me it can't locate and to make sure its connected which it is.
Click to expand...
Click to collapse
seems to be a driver issue in first case
allready watching my inbox - sorry for the delay - the popup notifcations don't seem to work at the time ...
b63 said:
seems to be a driver issue in first case
allready watching my inbox - sorry for the delay - the popup notifcations don't seem to work at the time ...
Click to expand...
Click to collapse
6.2.2 is not rootable right now. Jcase is working on it.
Sent from my Kindle Fire using Tapatalk
well i just rooted it btw or atlestmy kindle says it say so. got go launcher up and it says superuser when i open that app. TWRP doesn't install cause when it tries to reboot in fastboot mode the kindle just sits there. but i got it rooted
EDIT. I installed the drivers then rolled them back then the KFU recognized the kindle enough to root it.
b63 said:
try to pm me
edit: i assume the error message from kfu says "adbd cannot run in production builds"
Click to expand...
Click to collapse
mine does that....why?
arceangel said:
mine does that....why?
Click to expand...
Click to collapse
in the meantime kfu 0.9.3 is out - this should resolve the problem
http://forum.xda-developers.com/showthread.php?t=1399889
I rooted my kindle fire 6.2.2 last nite with burritoroot3 (the latest version) and also installed twrp with kfu 0.9.1 (older version of kfu).
I had problems installing with kfu 0.9.3 (the latest), so I used kfu 0.9.1 and it was successfull
ill check it out thanks man
Hello everyone. Couple months back someone at work asked me if I could put android on the kindle fire hd 7. I dont recall which article I followed but do remember using fireflash to get twrp installed and got the device rooted. Originally I would try to flash a rom and it would hang at bootup with a google logo with gears. So being that this device is a bit more tricky then my original kindle fire to install roms on I had the person go out and purchase the fastboot cable. So here I am stuck at what to do next. I go thru the steps wipe cache etc. Install from zip and as soon as I do this failed pops up. Hoping someone can point me in the right direction as to why this is happening and what to do to resolve this and get jelly bean installed. I am attaching screenshots. If I can get this to work I need to do my parents kindle. Thanks in advance for any help.
Ok one. You got the wrong rom, two. you need kindle fire hd not kindle fire 2 if you can get it thru adb perfect if not return to stock and reflash. I'd personally use Kindle fire first Aide, seeing you got fastboot cable
Sent from my N861 using Tapatalk 4 Beta
south956 said:
Ok one. You got the wrong rom, two. you need kindle fire hd not kindle fire 2 if you can get it thru adb perfect if not return to stock and reflash. I'd personally use Kindle fire first Aide, seeing you got fastboot cable
Sent from my N861 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks..Im still new at this kindle fire hd. Can you link me to a rom for the kindle fire hd. I am unsure what you mean by getting it thru adb. Also how do I go back to stock, or use fire first aide. Sorry for the lack of knowledge any help is greatly appreciated.
Not that it matters that much but I thought I would mention that's not the newest version of twrp available for the kfhd, and the newest version only takes about 10 seconds to get into instead of a full minute.
Here's a link to cm 10.1 for kfhd7, http://forum.xda-developers.com/showthread.php?t=2245335
If you are interested in updating twrp, its really easy, u flash it like u would a ROM in twrp. Here's a link to hashcodes thread that tells about it: http://forum.xda-developers.com/showthread.php?t=2218796
Also thought I would ask to make sure, but since I saw the last photo I am assuming you can still boot into your stock amazon os? If you can that makes this a lot easier since you can either download the files from the kindles web browser or transfer them over to kindle from PC easily.
However, if you can't boot into stock os, u can use the adb sideload command to push the ROM onto the device, I think kffa may have something in it that does this for you, I haven't ever had to use it though so I am unsure. Hope this helps!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Not that it matters that much but I thought I would mention that's not the newest version of twrp available for the kfhd, and the newest version only takes about 10 seconds to get into instead of a full minute.
Here's a link to cm 10.1 for kfhd7, http://forum.xda-developers.com/showthread.php?t=2245335
If you are interested in updating twrp, its really easy, u flash it like u would a ROM in twrp. Here's a link to hashcodes thread that tells about it: http://forum.xda-developers.com/showthread.php?t=2218796
Also thought I would ask to make sure, but since I saw the last photo I am assuming you can still boot into your stock amazon os? If you can that makes this a lot easier since you can either download the files from the kindles web browser or transfer them over to kindle from PC easily.
However, if you can't boot into stock os, u can use the adb sideload command to push the ROM onto the device, I think kffa may have something in it that does this for you, I haven't ever had to use it though so I am unsure. Hope this helps!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Sorry for the questions but I downloaded the newer twrp and then followed the instructions below and soon as I swiped it to flash it just failed. Is there other way to update twrp? I figured that the easiest way was to follow the directions below.
INSTALL INSTRUCTIONS:
While the ORANGE logo is showing on the screen, press and hold the volume up button till the BLUE logo shows. (This is the button farther away from the power button)
Select "Install"
Navigate to where you placed the file on your device
Select the .zip filename
Swipe to confirm flash
Reboot
justblinded said:
Sorry for the questions but I downloaded the newer twrp and then followed the instructions below and soon as I swiped it to flash it just failed. Is there other way to update twrp? I figured that the easiest way was to follow the directions below.
INSTALL INSTRUCTIONS:
While the ORANGE logo is showing on the screen, press and hold the volume up button till the BLUE logo shows. (This is the button farther away from the power button)
Select "Install"
Navigate to where you placed the file on your device
Select the .zip filename
Swipe to confirm flash
Reboot
Click to expand...
Click to collapse
btw I get the same error message trying to flash verifying zip signature
verifying update package
e:signature verification failed
error flashing zip
justblinded said:
btw I get the same error message trying to flash verifying zip signature
verifying update package
e:signature verification failed
error flashing zip
Click to expand...
Click to collapse
Turn off signature verification :silly:
justblinded said:
btw I get the same error message trying to flash verifying zip signature
verifying update package
e:signature verification failed
error flashing zip
Click to expand...
Click to collapse
I was able to flash the twrp then install the rom. Thank you guys for your help you saved the day! Now I have to do it all over again on my mothers tablet wish me luck! lol
Hello guys.
I would like to ask you for help with my bricked Homecare. I apparently cocked up the flashing process and now I don't know, how to proceed.
What I did:
At first I used the Russian (translated) version of supertool designated for Homecare Note 7. But the process wasn't 100 % successful. The bootloader has been unlocked, CWM recovery has been flashed, ROM 4.3 has been flashed. The tablet was able to boot, but it always froze after a few minutes of operation. Most probably there was a wrong boot flashed. No idea.
So, I checked the forums and RootJnky's videos and decided to use CWM to flash a deodex 4.3 stock ROM.
Flash process was successful, but after restart the tablet remains in boot-loop.
Now, I was NEVER able to enter the Recovery or Bootloader using the button combination. Don't ask me why, but it wasn't possible. I could however access recovery or bootloader using ADB.
Right now the only status except a boot-loop is the APX mode. Is there still a chance how to unbrick the tablet???
Thanks for any advice.
Jaro
jardam.cz said:
Now, I was NEVER able to enter the Recovery or Bootloader using the button combination. Don't ask me why, but it wasn't possible. I could however access recovery or bootloader using ADB...Jaro
Click to expand...
Click to collapse
At worse case scenario you need to use APX mode to reflash. You can get the download references for the APX files, particularly the package from Advent UK. The package is setup for Windows but it's easy to use in Linux with their executables.
The APX mode does reflash your tablet in whole, but the end result may not be perfect, but should allow a stepping stone to fastboot mode.
If you can obtain 'fastboot' mode then your can reflash partitions. The 'adb' mode in recovery level or system level will allow for updates with 'sideload' command.
Hope that helps.
e8hffff said:
At worse case scenario you need to use APX mode to reflash. You can get the download references for the APX files, particularly the package from Advent UK. The package is setup for Windows but it's easy to use in Linux with their executables.
The APX mode does reflash your tablet in whole, but the end result may not be perfect, but should allow a stepping stone to fastboot mode.
If you can obtain 'fastboot' mode then your can reflash partitions. The 'adb' mode in recovery level or system level will allow for updates with 'sideload' command.
Hope that helps.
Click to expand...
Click to collapse
@e8hfff I managed to sort him out yesterday using the APX method the use has now got it working, with no issues at all (WiFi works as well).
The only thing different for him is that his Generic bootanimation which Xolo Tegra Note 7's have is now showing advent.
I will send you a PM in a bit out the bootanimation as i have a idea LOL.
hacktrix2006 said:
@e8hfff I managed to sort him out yesterday using the APX method the use has now got it working, with no issues at all (WiFi works as well).
The only thing different for him is that his Generic bootanimation which Xolo Tegra Note 7's have is now showing advent.
I will send you a PM in a bit out the bootanimation as i have a idea LOL.
Click to expand...
Click to collapse
Hi hacktrix2006.
Thanks for the help again. The tablet is working like dream. All my Chinese colleagues are staring at it. The poor guys know only the products of the fruit company (Apple).
I saw the boot animation is a set of pictures in the flash package from Advent. It is ZIPed.
Is there any way how to make and flash a boot animation without reflashing the whole thing? (I know the answer already, but I don't know how to do it DD)
jardam.cz said:
Hi hacktrix2006.
Thanks for the help again. The tablet is working like dream. All my Chinese colleagues are staring at it. The poor guys know only the products of the fruit company (Apple).
I saw the boot animation is a set of pictures in the flash package from Advent. It is ZIPed.
Is there any way how to make and flash a boot animation without reflashing the whole thing? (I know the answer already, but I don't know how to do it DD)
Click to expand...
Click to collapse
The bootanimation.zip is in /lbh partition under media. Should be a easy enough to copy and paste in if not then i will have a look for a way of doing it without flashing all of it again.
Docs on Homecare Fly One rom update
Hi jardam.cz AND hacktrix2006
I see you guys have a working method to update the Homecare Fly One - do you have any documentation on how to root and update the rom for this model? Jardam mentioned a Russian rom, but it caused problems. I really don't want to brick this, as I live and breathe with this tablet every day! But I can't stand the limitations of no root.
Almost all the YouTube videos show EVGA solutions, and lots of people have Homecare Fly One problems - what's the solution please?
They are all the same base nvidia model which is p1640 the lbh partition is wrote when flashing via apx mode which can be risky. However there is a twrp recovery for our device and a stock 4.4.2 image from tom you can use to flash a generic version if the os.
OK, just got the Fire today. The OS says 5.0.1 from Nov 17th, and says update is available, version 541112720. I block OTAVerifier only, thinking by blocking the verification I can intercept the update file in /cache. then I turn on airplane mode, play a bit and boot into TWRP via fastboot, install SuperSu. All is good.
Then I decide to see what the update is all about, and let it download. To my surprise, it starts installing. After the installation, I see FireOS 5.1.1 Now, I try to go into TWRP via fastboot, and it does not reboot and just hangs. A couple more tries - and still nothing.
I go back to stock recovery, and start sideloading update-kindle-37.5.2.2_user_522054520.bin . It sideloads OK, and upon reboot i get dark screen. Nothing works. This sounds very similar to the 4th gen issues where downgrades were bricking Fires :
http://forum.xda-developers.com/fire-hd/general/stop-upgrade-to-lollipop-via-twrp-t3216817
It'll be simple to install 5.1.1 via TWRP once the update file is captured, such that the older bootloaders can be kept.
But beware of the update - without TWRP there likely won't be root!
Dang, sucks about the brick! Hopefully getting TWRP to work again won't take a herculean effort. Right now I'm loving SlimLP but anyone getting one for xmas would likely get that Fire OS 5.1.1 pushed to them right away upon booting up and logging in and I would hate to see them stuck on that!
Damn!
What if an open wifi network is within range? Will the Fire OS ask before connecting?
My friend has a new fire in the box & has an open wifi network within range of their place.
The 5.1.1 update should find it's way to amazon's Software Updates page in time. It's not there yet. http://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
blueberry.sky said:
What if an open wifi network is within range? Will the Fire OS ask before connecting?
My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
afaik they don't ship with wifi on, and you have to agree to connect if wifi is detected.
Still, anyone who might want to root needs to keep wifi off until this is sorted--or until they're rooted and can rename DeviceSoftwareOTA.apk . And everyone on rooted stock should confirm /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk is renamed to .apkOFF (or whatever), which should prevent a download. Don't know how the roms handle OTA.
I do believe that you should have to agree to connect to wifi. But I'd like to be 100% sure. Don't want to take the slightest chance.
I would appreciate confirmation from anyone with a brand new Fire & an open wifi network within range, that it will not auto-connect.
bibikalka said:
It'll be simple to install 5.1.1 via TWRP once the update file is captured, such that the older bootloaders can be kept.
But beware of the update - without TWRP there likely won't be root!
Click to expand...
Click to collapse
So, 5.1.1 can't boot TWRP and downgrading produces bricks. Lovely!
Wonder if there's any chance the CM recovery will boot?
I assume some of the "old-timers" here will capture the update soon enough. If not, I'm glad to give it a go.
tried the downgrade as well, same result. I think the reason we can't get back into recovery\fastboot is because the device is just endlessly rebooting (you can see in device manager). it wont let you power it off to try the volume down+power combo and just holding them does nothing. im going to let mine die overnight hopefully and maybe getting the volume down+power from off will let us back into recovery?
---------- Post added at 01:14 AM ---------- Previous post was at 12:46 AM ----------
DoLooper said:
So, 5.1.1 can't boot TWRP and downgrading produces bricks. Lovely!
Wonder if there's any chance the CM recovery will boot?
I assume some of the "old-timers" here will capture the update soon enough. If not, I'm glad to give it a go.
Click to expand...
Click to collapse
Well 5.0.1 is available on the Amazon website here: https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180 so I contacted Amazon for the 5.1.1 file and this was what I got:
Jyothirmayi: In this case, I'll personally follow up your contact and email you the link for the update because we currently don't have the manual link for the update in our website.
I will post here if\when I hear back
dmesg on linux machine when plug usb, open mediatek preloader com port.
Have this on bricked fire ?
usb 1-2.4: Product: MT65xx Preloader
usb 1-2.4: Manufacturer: MediaTek
cdc_acm 1-2.4:1.1: ttyACM0: USB ACM device
adb
usb 1-2.4: New USB device found, idVendor=1949, idProduct=0222
usb 1-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 1-2.4: Product: Fire
usb 1-2.4: Manufacturer: Amazon
usb 1-2.4: SerialNumber: xxxxxxxxxxxxxxxxxxx
fastboot
usb 1-2.4: New USB device found, idVendor=0bb4, idProduct=0c01
usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2.4: Product: Android
usb 1-2.4: Manufacturer: MediaTek
usb 1-2.4: SerialNumber: xxxxxxxxxxxxxx
If you have TWRP, why didn't you just use the file manager to copy and paste the OTA from your /cache to your sd card? If you can boot to TWRP, see if it's still there.
You can also dump your cache via adb shell from within TWRP and get the OTA by extracting the cache.img that dumps. There are several ways, as long as TWRP and fastboot are still booting.
Also, you can use adb shell within twrp to dd a system.img dumped from another fire tab, and restore your device that way if all else fails.
hp420 said:
If you have TWRP, why didn't you just use the file manager to copy and paste the OTA from your /cache to your sd card? If you can boot to TWRP, see if it's still there.
You can also dump your cache via adb shell from within TWRP and get the OTA by extracting the cache.img that dumps. There are several ways, as long as TWRP and fastboot are still booting.
Also, you can use adb shell within twrp to dd a system.img dumped from another fire tab, and restore your device that way if all else fails.
Click to expand...
Click to collapse
I think in the OP, he mentioned that he is no longer able to get into TWRP after 5.1.1 update...
So I bricked my device last night trying to downgrade before anyone had posted about it. Oops.
I did some Googling and theoretically these tools here should help us unbrick, but I believe we don't have the Amazon firmware in the right format.
HOWEVER, this tool, if I understand it right, should be able to pull the firmware from a working device in the right format for us to try flashing to a bricked device. Anyone want to give it a shot?
87racer said:
Jyothirmayi: In this case, I'll personally follow up your contact and email you the link for the update because we currently don't have the manual link for the update in our website.
I will post here if/when I hear back
Click to expand...
Click to collapse
mmoogle said:
So I bricked my device last night trying to downgrade before anyone had posted about it. Oops.
I did some Googling and theoretically these tools here should help us unbrick, but I believe we don't have the Amazon firmware in the right format.
HOWEVER, this tool, if I understand it right, should be able to pull the firmware from a working device in the right format for us to try flashing to a bricked device. Anyone want to give it a shot?
Click to expand...
Click to collapse
When we get the official file from Amazon, we can format it to the way the MTK Droid Tool wants it, and then that would theoretically work.
mmoogle said:
So I bricked my device last night trying to downgrade before anyone had posted about it. Oops.
I did some Googling and theoretically these tools here should help us unbrick, but I believe we don't have the Amazon firmware in the right format.
HOWEVER, this tool, if I understand it right, should be able to pull the firmware from a working device in the right format for us to try flashing to a bricked device. Anyone want to give it a shot?
Click to expand...
Click to collapse
Vlasp said:
When we get the official file from Amazon, we can format it to the way the MTK Droid Tool wants it, and then that would theoretically work.
Click to expand...
Click to collapse
Well, I've been there before with the 4th gen Fire HD :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
In a nutshell, MTK Droid tools don't even talk to the working Fire properly, so it's unlikely they'd help with a bricked one ...
87racer said:
tried the downgrade as well, same result. I think the reason we can't get back into recovery\fastboot is because the device is just endlessly rebooting (you can see in device manager). it wont let you power it off to try the volume down+power combo and just holding them does nothing. im going to let mine die overnight hopefully and maybe getting the volume down+power from off will let us back into recovery?
Click to expand...
Click to collapse
Just pull your battery. The back cover is very easy to get off. Use a knife just to widen the seam so you can get your fingernail in at the corner. Keep one fingernail at the corner & side a 2nd nail down along the edge.
Then the battery connector lifts out upwards.
http://forum.xda-developers.com/ama...o-photo-amazon-fire-2015-motherboard-t3227808
bibikalka said:
Well, I've been there before with the 4th gen Fire HD :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
In a nutshell, MTK Droid tools don't even talk to the working Fire properly, so it's unlikely they'd help with a bricked one ...
Click to expand...
Click to collapse
We might be in luck. I happen to have 3 of them One bricked, one mostly untouched on 5.1.1 and another with OTA blocked on 5.0.1. I will fiddle with the tools you posted and see if I can come up with something.
blueberry.sky said:
Just pull your battery. The back cover is very easy to get off. Use a knife just to widen the seam so you can get your fingernail in at the corner. Keep one fingernail at the corner & side a 2nd nail down along the edge.
Then the battery connector lifts out upwards.
http://forum.xda-developers.com/ama...o-photo-amazon-fire-2015-motherboard-t3227808
Click to expand...
Click to collapse
Good to know, even over night, it still isn't dead so I might give this a shot.
So, if i previously installed the google framework and blocked ota like most people did, this won't block the ota really ?
87racer said:
We might be in luck. I happen to have 3 of them One bricked, one mostly untouched on 5.1.1 and another with OTA blocked on 5.0.1. I will fiddle with the tools you posted and see if I can come up with something.
Click to expand...
Click to collapse
The best deal is of course to capture the 5.1.1 update file. I am eager to try it, provided I get root with requires installing via TWRP.
bibikalka said:
Well, I've been there before with the 4th gen Fire HD :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
In a nutshell, MTK Droid tools don't even talk to the working Fire properly, so it's unlikely they'd help with a bricked one ...
Click to expand...
Click to collapse
So MTK tools does talk but from what I gather it is looking for /proc/dumchar_info which contains the partition structure. This is used to create the scatter file that would allow us to push the firmware back. This file is non-existent. I tried to find some alternate way to build a scatter file but am coming up short and without it we can't really do anything using SP Flash...
Also tried looking into /proc/mtd for info but that file is basically blank. Not sure if Amazon is storing the partition information somewhere else or maybe its hard coded into a chip?
If anybody has any ideas, I have the working devices and can try pulling stuff but I am stumped atm
---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ----------
bibikalka said:
The best deal is of course to capture the 5.1.1 update file. I am eager to try it, provided I get root with requires installing via TWRP.
Click to expand...
Click to collapse
We were replying at the same time. I don't think a 5.1.1 file is going to help us on the bricked devices. Once bricked, the preloader seems to just endlessly loop so we would have no way to get the firmware on the device without using something like SP Flash and a scatter file (which eludes me atm)
Theoretically if we have the scatter file I think we should be able to use our 5.0.1 file and restore, then upgrade to 5.1.1 (or stay for root and fastboot boot support)
nEUTRon666 said:
So, if i previously installed the google framework and blocked ota like most people did, this won't block the ota really ?
Click to expand...
Click to collapse
What makes you say that? No one who did that has reported it updating.
The opportunity to unlock the Fire HD 6/7 bootloader and unbrick all bricks is upon us ! Sadly, it's about ~4 years too late.
Nonetheless, if you are proficient with IDA Disassembler and Python, please follow these instructions to accomplish these 2 objectives.
1) Zero out rpmb partition ( mmcblk0rpmb ) - this will set all the bricks free and enable them to boot (this is how anti-rollback is wiped)
2) Enable permanent bootloader unlock (more advanced)
Here are the relevant posts on how to do this:
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256 (full instructions)
https://forum.xda-developers.com/amazon-fire/development/downgrade-fire-7-2015-softbrick-t3894671 (rpmb partition zeroing method for Fire 7 2015)
bibikalka said:
The opportunity to unlock the Fire HD 6/7 bootloader and unbrick all bricks is upon us ! Sadly, it's about ~4 years too late.
Nonetheless, if you are proficient with IDA Disassembler and Python, please follow these instructions to accomplish these 2 objectives.
1) Zero out rpmb partition ( mmcblk0rpmb ) - this will set all the bricks free and enable them to boot (this is how anti-rollback is wiped)
2) Enable permanent bootloader unlock (more advanced)
Click to expand...
Click to collapse
Yeah, I saw the Fire HD 8 thread and was wondering if it'd be possible for us. Unfortunately, I'm neither proficient with IDA Disassembler nor python. And currently my Fire is on the latest FireOS, unrooted, with the wrong recovery installed. So right now I can't get into recovery to downgrade and fix it, and the preloader method doesnt work because the read/write commands don't work on the newer FireOS. I am interested in if this is possible though!
Update: I attempted using the files from the Fire 7 thread and this is what I got:
Code:
[2019-01-29 17:33:56.846249] Waiting for bootrom
[2019-01-29 17:34:07.704879] Found port = /dev/ttyACM0
[2019-01-29 17:34:07.744128] Handshake
[2019-01-29 17:34:07.766738] Disable watchdog
b''
b'\x00\x01'
Traceback (most recent call last):
File "main.py", line 128, in <module>
main()
File "main.py", line 57, in main
handshake(dev)
File "/root/fire7-2015-downgrade-unbrick/fire7-2015-downgrade-unbrick/modules/handshake.py", line 11, in handshake
dev.write32(0x10007000, 0x22000000)
File "/root/fire7-2015-downgrade-unbrick/fire7-2015-downgrade-unbrick/modules/common.py", line 152, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/root/fire7-2015-downgrade-unbrick/fire7-2015-downgrade-unbrick/modules/common.py", line 89, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: Serial protocol mismatch
I was using the linux iso for unbricking, so I'm not sure if that had something to do with it. Also, I hand-typed that error message so if there are any inconsistencies that may be why (I didn't have an internet connection to post from the iso).
spenceboy98 said:
Yeah, I saw the Fire HD 8 thread and was wondering if it'd be possible for us. Unfortunately, I'm neither proficient with IDA Disassembler nor python. And currently my Fire is on the latest FireOS, unrooted, with the wrong recovery installed. So right now I can't get into recovery to downgrade and fix it, and the preloader method doesnt work because the read/write commands don't work on the newer FireOS. I am interested in if this is possible though!
Update: I attempted using the files from the Fire 7 thread and this is what I got:
Code:
...
RuntimeError: Serial protocol mismatch
I was using the linux iso for unbricking, so I'm not sure if that had something to do with it. Also, I hand-typed that error message so if there are any inconsistencies that may be why (I didn't have an internet connection to post from the iso).
Click to expand...
Click to collapse
See this post for the proper output:
https://forum.xda-developers.com/showpost.php?p=78792151&postcount=14
I think HD 2014 does not switch to the bootrom mode, and is in the pre-loader mode. That's why it says protocol mismatch. With Fire 7 I got the initial stages to work - so it did go into the right mode! But with HD 2014 I got the same messages as you, under Windows. So I think it's just not switching into the bootrom mode.
We need some old timers here if we are to get this done!!!
@powerpoint45
bibikalka said:
I think HD 2014 does not switch to the bootrom mode, and is in the pre-loader mode. That's why it says protocol mismatch. With Fire 7 I got the initial stages to work - so it did go into the right mode! But with HD 2014 I got the same messages as you, under Windows. So I think it's just not switching into the bootrom mode.
We need some old timers here if we are to get this done!!!
Click to expand...
Click to collapse
I'm willing to pop open the back of my Fire HD 6 to check some pins if necessary. Hopefully we're not the only ones wanting to see progress for this device.
spenceboy98 said:
I'm willing to pop open the back of my Fire HD 6 to check some pins if necessary. Hopefully we're not the only ones wanting to see progress for this device.
Click to expand...
Click to collapse
Oh, there are plenty of motherboard pictures floating around:
https://forum.xda-developers.com/showpost.php?p=78789821&postcount=90
Gotta find something like these pins : CMD, CLK, DAT0. I could not spot any labels on the motherboard pictures. If the pin is outside of a shield, it'd be trivial to pop the cover, and short the pin. Then one still has to get the right addresses for HD 2014 to make everything work
bibikalka said:
Oh, there are plenty of motherboard pictures floating around:
https://forum.xda-developers.com/showpost.php?p=78789821&postcount=90
Gotta find something like these pins : CMD, CLK, DAT0. I could not spot any labels on the motherboard pictures. If the pin is outside of a shield, it'd be trivial to pop the cover, and short the pin. Then one still has to get the right addresses for HD 2014 to make everything work
Click to expand...
Click to collapse
I didn't see any labels on the board, so I tried a few pins (the ones that xyz` suggested) and I didn't seem to have any luck there. It's possible that I wasn't holding the wire I was using firm enough against the pins, but I don't know. I'm not sure what test points on this motherboard look like and if you have any suggestions or ideas, I'm willing to give it a go.
Also, on a new installation of Ubuntu 18.10, it's not even detecting the preloader. It just boots normally. And when I try in Windows 10, the device shows up as MT65xx Preloader and won't show up as a COM device even after installing the correct drivers.
spenceboy98 said:
I didn't see any labels on the board, so I tried a few pins (the ones that xyz` suggested) and I didn't seem to have any luck there. It's possible that I wasn't holding the wire I was using firm enough against the pins, but I don't know. I'm not sure what test points on this motherboard look like and if you have any suggestions or ideas, I'm willing to give it a go.
Also, on a new installation of Ubuntu 18.10, it's not even detecting the preloader. It just boots normally. And when I try in Windows 10, the device shows up as MT65xx Preloader and won't show up as a COM device even after installing the correct drivers.
Click to expand...
Click to collapse
Yep - it's a tough cookie. No labels on the board, and button pushes don't work either to get the device into the BootRom mode. I could only get the pre-loader mode as well.
We will have to wait for somebody to figure out the electrical connections here. Unfortunately, I don't have time to dig around like that.
(HD7, 7th Gen)
Just chiming in, I tried a few pads on the board (on both sides), and was unable to kick it into bootrom mode. It also looks like our shielding is soldered on. :/
May try some other methods later, but likely not going to have the easiest of times messing with this thing.
r3pwn said:
(HD7, 7th Gen)
Just chiming in, I tried a few pads on the board (on both sides), and was unable to kick it into bootrom mode. It also looks like our shielding is soldered on. :/
May try some other methods later, but likely not going to have the easiest of times messing with this thing.
Click to expand...
Click to collapse
7th Gen, or 4th Gen? Sorry for nitpicking, but it is huge for context!
spenceboy98 said:
Yeah, I saw the Fire HD 8 thread and was wondering if it'd be possible for us. Unfortunately, I'm neither proficient with IDA Disassembler nor python. And currently my Fire is on the latest FireOS, unrooted, with the wrong recovery installed. So right now I can't get into recovery to downgrade and fix it, and the preloader method doesnt work because the read/write commands don't work on the newer FireOS. I am interested in if this is possible though!
...
Click to expand...
Click to collapse
Btw, you can always sideload FireOS 4, and get root that way. Then re-load your current latest fireos via TWRP, and install SuperSu.
bibikalka said:
Btw, you can always sideload FireOS 4, and get root that way. Then re-load your current latest fireos via TWRP, and install SuperSu.
Click to expand...
Click to collapse
I can't because I have FireOS 5 with the twrp img installed (I didn't realize that the latest update.bin didn't include a stock recovery image). And I can't use the unbricking iso because it doesnt work with the latest FireOS. So this method is my best bet for getting back to stock with a stock recovery.
Btw, I'm not sure what exactly happened, but I'm pretty sure that my playing with the pins messed with something. All I get now is the grey Amazon logo and it doesn't boot into the OS. :|
spenceboy98 said:
I can't because I have FireOS 5 with the twrp img installed (I didn't realize that the latest update.bin didn't include a stock recovery image). And I can't use the unbricking iso because it doesnt work with the latest FireOS. So this method is my best bet for getting back to stock with a stock recovery.
Btw, I'm not sure what exactly happened, but I'm pretty sure that my playing with the pins messed with something. All I get now is the grey Amazon logo and it doesn't boot into the OS. :|
Click to expand...
Click to collapse
I see. Usually, recovery is verified each time you boot, and the OS will overwrite it if the checksum does not match. But, in your case, TWRP disabled that feature, so you are out in the cold.
I have 2 tablets that are looping on the white Amazon logo. I tried to restore them via aftv2-tools, but nothing worked. It's interesting you got the same glitch.
Look at the bright side - keep poking around now on your motherboard, you have nothing to lose!
I attempted to overwrite the beginning of EMMC - and got an absolutely dead tablet, see here:
https://forum.xda-developers.com/showpost.php?p=78871662&postcount=784
No bootrom mode as far as I can see ... One of these days I'll open the case, and try to disconnect the battery.
bibikalka said:
7th Gen, or 4th Gen? Sorry for nitpicking, but it is huge for context!
Click to expand...
Click to collapse
2017 Fire HD7, so 7th gen, aka austin
r3pwn said:
2017 Fire HD7, so 7th gen, aka austin
Click to expand...
Click to collapse
You are in the wrong forum.
The 2017 Fire 7 AKA austin doesn't use the suffix HD. It's just Fire or Fire 7.
This is what you are looking for: https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
spenceboy98 said:
I can't because I have FireOS 5 with the twrp img installed (I didn't realize that the latest update.bin didn't include a stock recovery image). And I can't use the unbricking iso because it doesnt work with the latest FireOS. So this method is my best bet for getting back to stock with a stock recovery.
Btw, I'm not sure what exactly happened, but I'm pretty sure that my playing with the pins messed with something. All I get now is the grey Amazon logo and it doesn't boot into the OS. :|
Click to expand...
Click to collapse
Did put any more time into this? Was it some damaged contact?
bibikalka said:
Did put any more time into this? Was it some damaged contact?
Click to expand...
Click to collapse
No I haven't. Not sure what the issue is. As far as I know it's still not booting up to anything. I just started school recently and I left my Fire HD6 at home, so I haven't had the chance to mess around with it more.
Just for test. Is there any possiblility that pressing the power button with any volume button makes the tablet enter in BootROM. My Fire and my BQ enter in BootROM when I press volume -. Just try all the bootloaders for see if one support it like 5.0.1.
Regards!
bibikalka said:
The opportunity to unlock the Fire HD 6/7 bootloader and unbrick all bricks is upon us ! Sadly, it's about ~4 years too late.
Nonetheless, if you are proficient with IDA Disassembler and Python, please follow these instructions to accomplish these 2 objectives.
1) Zero out rpmb partition ( mmcblk0rpmb ) - this will set all the bricks free and enable them to boot (this is how anti-rollback is wiped)
2) Enable permanent bootloader unlock (more advanced)
Here are the relevant posts on how to do this:
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256 (full instructions)
https://forum.xda-developers.com/amazon-fire/development/downgrade-fire-7-2015-softbrick-t3894671 (rpmb partition zeroing method for Fire 7 2015)
Click to expand...
Click to collapse
I would love to get my HD 6 working again.
I recently ran the amonet script on my HD 10 and in a few minutes had an unlocked bootloader and TWRP. I read the HD 8 thread where the author posted his exploit and it really is an epic achievement. I'm also hoping the bootloader unlock comes to the 4K firestick as well. It's a lot of work from I read, but the firestick is popular enough to warrant that kind of attention. I have a Fire HD 6 which only boots to a recovery that allows me to reset or reboot but has no option to apply update from adb, so I've been stuck on stock Fire OS. It would be nice to finally get TWRP after so long on the HD 6.
***