Database Users

The unbrick image for HDX 7"

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

Anyway to downgrade from 7.4.8

Today I just scored a Kindle Fire HD 1st Gen (at least I think so). The back say Model Number X43Z60.
I have been studying this thread http;//wwwforum.xda-developers.com/showthread.php?t=2271909&nocache=1
+Note: As of Amazon OS update 7.3.x+, there has been a lot of issues with rooting and flashing the 2nd-bootloader. Many users reported bootloops during the completion of the guide. Those with tablets running 7.3.0 or higher, please proceed with caution, and make sure you have a factory cable on hand if you wish to advance. I strongly recommend you make backups in Step 2. If you want guaranteed success, use this tool to revert back to 7.2.3 before using the guide. You will need to flash a brand-new 7.2.3 on top to revert, so you will lose everything if you don't backup your files first.
Click to expand...
Click to collapse
Will the tool in the section above allow me to downgrade from 7.4.8?
Also are there any guides floating around on how to make a fast boot cable?
I have a cord factory cord that I had made for my Motorola would that work?
*********************************************************************************************
I feel like a complet idiot for even posting that, after a bit of research I found this method (check it out) which a few people had confirmed that it work on the newest Kindle OS which shortly after I posted my Kindle updated to (7.4.9).
A lot of clicking later and my fire is running CM flawlessly!

mikecella said:
Today I just scored a Kindle Fire HD 1st Gen (at least I think so). The back say Model Number X43Z60.
I have been studying this thread http;//wwwforum.xda-developers.com/showthread.php?t=2271909&nocache=1
Will the tool in the section above allow me to downgrade from 7.4.8?
Also are there any guides floating around on how to make a fast boot cable?
I have a cord factory cord that I had made for my Motorola would that work?
*********************************************************************************************
I feel like a complet idiot for even posting that, after a bit of research I found this method (check it out) which a few people had confirmed that it work on the newest Kindle OS which shortly after I posted my Kindle updated to (7.4.9).
A lot of clicking later and my fire is running CM flawlessly!
Click to expand...
Click to collapse
I had the same one and just followed the tut to backup, then install bootloader and then flashed rom. Didn't downgrade and it all went fine.

[STOP] FireOS 5.1.1 & attempted downgrade - the fastest Fire brick!

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.

Kindle fire hd 8 hard brick, I think that's it.

Hi,
I used adb sideload to upgrade my firmware so I could root my Kindle fire HD 8 and stuff, but since I didn't know which version I was on to begin with, I guess I flashed the wrong version. Stayed dead after pressing reboot in recovery. Well, that was stupid, but I never had a brick this bad on any of my numerous android phones.
So, to summarize:
Doesn't turn on.
No lights or anything when charging (Does it even have a notification light?)
Doesn't get recognised on 3 different pcs, not by device manager on windows or dmesg on linux.
Not only doesn't get recognised, but just nothing in device manager or anywhere, absolutely nothing.
Can't get into recovery.
Got a fastboot cable, connected it, no reaction what so ever.
So all in all, that's it isn't it? I destroyed it by installing the wrong firmware? I have done that many times on different phones but was always able to get into recovery or fastboot.
If you guys have any Ideas, I appreciate it.
Thanks in advance, Fritz

derfritz said:
Hi,
I used adb sideload to upgrade my firmware so I could root my Kindle fire HD 8 and stuff, but since I didn't know which version I was on to begin with, I guess I flashed the wrong version. Stayed dead after pressing reboot in recovery. Well, that was stupid, but I never had a brick this bad on any of my numerous android phones.
So, to summarize:
Doesn't turn on.
No lights or anything when charging (Does it even have a notification light?)
Doesn't get recognised on 3 different pcs, not by device manager on windows or dmesg on linux.
Not only doesn't get recognised, but just nothing in device manager or anywhere, absolutely nothing.
Can't get into recovery.
Got a fastboot cable, connected it, no reaction what so ever.
So all in all, that's it isn't it? I destroyed it by installing the wrong firmware? I have done that many times on different phones but was always able to get into recovery or fastboot.
If you guys have any Ideas, I appreciate it.
Thanks in advance, Fritz
Click to expand...
Click to collapse
I'm very sorry for you. But, I'll have to say, that's it.
Amazon has a very strange way of preventing downgrade, they have an exclusive process looking for a version mismatch, and when it detects a version mismatch, it terminates the installation in a special ... way. Effectively bricking the device by failing the signatures and files of every partition, purposefully. I confirmed this myself by looking at the abandoned logs a Fire device produced before it shutted down forever.
If that's the 7th Gen model, please contact an Amazon representative. They should offer you a replacement for your device, but your data is gone.
Good luck!

Supersonic27543 said:
I'm very sorry for you. But, I'll have to say, that's it.
Amazon has a very strange way of preventing downgrade, they have an exclusive process looking for a version mismatch, and when it detects a version mismatch, it terminates the installation in a special ... way. Effectively bricking the device by failing the signatures and files of every partition, purposefully. I confirmed this myself by looking at the abandoned logs a Fire device produced before it shutted down forever.
If that's the 7th Gen model, please contact an Amazon representative. They should offer you a replacement for your device, but your data is gone.
Good luck!
Click to expand...
Click to collapse
Thankfully I had no important data on it. I had a 6th gen so that's no option either. Well, thank you for your help, I think I'll stay away from amazon devices for a while...

Walmart ONN 100003652 10.1 inch and gen 2 100015685 series root and CFW / Linux OS!

I know I’m a newb here but I wanted to make a thread dedicated to theses devices in which I I have detailed instructions for rooting as well as CFW’s and unbricking!
I appreciate any donations sent via PayPal email for PayPal is on my profile.

Onn 100003562 Root instructions:
****UPDATE*****
With the newly uploaded rom all you have to do is download use sp flash to install .
May still have to run " fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img " command in fastboot mode.
Step 1: Downloads
Download Magisk manager and update.
Download ADB & FASTBOOT.
Below I'll have a link for windows. for linux run command "sudo apt install adb".
Dwnload boot.img and vbmeta.img.
Download SP Flash Tools and wwrMTK <---Will make this much faster XD.
I have all of these available
here--> https://drive.google.com/drive/folders/1lREGI_nd7kghuR6vCDjhiOZvbWrpJfBo?usp=sharing <--here.
Step 2:
Install magisk manager and update.
You can either download on the tablet or sideload with adb.
For sideload in windows shift + right click in the platform tools directory and click open power shell here.
Make sure you have MagiskManager-v8.0.0[1].apk saved within this directory.
Then run command "adb install MagiskManager-v8.0.0[1].apk"
For linux Right click the directory in which you have MagiskManager-v8.0.0[1].apk stored and click open terminal here.
Then run command "adb install MagiskManager-v8.0.0[1].apk"
Step 3:
Either make a backup with SP Flash tools or use the boot.img i have provided and copy it to your tablet.
Open magisk on the tablet and click the install then click select image to patch. Locate the boot.img and select it by clicking on it. Watch it finish make sure it fully completes the patch and creates the magisk-patched.img file. Also it may or may not be necessary to patch the recovery.img depending on your system. most likely not.
Step 4:
Flashing the .img files.
Now that you have adb and the images necessary to flash your device power it down and back up holding the volume up key. Once It boots it should load into the bootloader screen click the up key until you have fastboot selected and then click the down key.
Now that you are in fast boot mode you are going to navigate to adb fastboot directory and right click and select open powershell here. again make sure you have all necessary .img files stored in the adb fastboot directory. you should have the patched .img and the vbmeta.img stored in the directory for windows.
Run these commands:
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
Wait for it to reboot and then you will be rooted with magisk. enjoy.
I'm always grateful for donations paypal email for donations is on my profile.

Thanks for everyone's work for these tablets. I have both the new 7" and 10.1". Does anyone know how to edit the lk.bin file to remove that ugly Orange State warning after unlocking the bootloader?
This is a post that works great for the 7".
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
I just want to see if the same thing can be done with the 10.1"? If the files are identical great, but I don't want to risk needing to restore my tablet by just trying it blind. Not yet anyway.

PleaseBeNicetoMe said:
Thanks for everyone's work for these tablets. I have both the new 7" and 10.1". Does anyone know how to edit the lk.bin file to remove that ugly Orange State warning after unlocking the bootloader?
This is a post that works great for the 7".
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
I just want to see if the same thing can be done with the 10.1"? If the files are identical great, but I don't want to risk needing to restore my tablet by just trying it blind. Not yet anyway.
Click to expand...
Click to collapse
That thread has a modified lk.bin file to remove the orange state warning. It has worked great on both of my Gen 2 7 inch tablets

Okiera29 said:
That thread has a modified lk.bin file to remove the orange state warning. It has worked great on both of my Gen 2 7 inch tablets
Click to expand...
Click to collapse
I'm looking to do the same on my 10", do you think they're interchangeable?

Yes onm

Abelbody said:
Yes onm
Click to expand...
Click to collapse
Something must be lost in translation. I'm looking for a patched lk.bin for the 10.1", not the 7".
If anyone is interested, the 7" version is not compatible with the 10.1" version. Luckily SP Flash restored it.

PleaseBeNicetoMe said:
Something must be lost in translation. I'm looking for a patched lk.bin for the 10.1", not the 7".
If anyone is interested, the 7" version is not compatible with the 10.1" version. Luckily SP Flash restored it.
Click to expand...
Click to collapse
Sorry about that. It appears that Fred patched your lk.bin file for you on the other thread today

Okiera29 said:
Sorry about that. It appears that Fred patched your lk.bin file for you on the other thread today
Click to expand...
Click to collapse
Yes it worked too if anyone has the same question

Help! I followed the instructions in the OP, and everything worked fine. I then used ADB to uninstall some of the preinstalled apps, but I think I uninstalled something I shouldn't have. i'm getting crashes from mutltiple apps (Bluetooth, Contacts, etc).
I've downloaded the stock firmware/full in the linked GDrive share; how can I restore back to this stock firmware? I'm pretty new/noob with this, but I am familiar with Linux commands. (familiar enough to be dangerous...)

hightowerc said:
I've downloaded the stock firmware/full in the linked GDrive share; how can I restore back to this stock firmware? I'm pretty new/noob with this, but I am familiar with Linux commands. (familiar enough to be dangerous...)
Click to expand...
Click to collapse
I believe that you need to download SP Flash tools if you haven't already. You can then, using the provided scatter file and the downloaded firmware, just reflash the stock firmware to the tablet. You will of course, have to re-root the tablet after it finishes

PleaseBeNicetoMe said:
Thanks for everyone's work for these tablets. I have both the new 7" and 10.1". Does anyone know how to edit the lk.bin file to remove that ugly Orange State warning after unlocking the bootloader?
This is a post that works great for the 7".
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
I just want to see if the same thing can be done with the 10.1"? If the files are identical great, but I don't want to risk needing to restore my tablet by just trying it blind. Not yet anyway.
Click to expand...
Click to collapse
I’ll look into it sorry I’ve been having some issues lately and haven’t gotten much done on this thread. I was hoping to make an all in one spot for the newer android 10 models. I’ll get the 7 model info and stocks here soon. Is there already a working orange state mod already? If so can you link it and I’ll get into messing with it.
also these Mtk devicesseem to be difficult to get the source for. I’ve contacted mtk multiple times now and still have not gotten a response. I have however been digging through the hidden settings of thesedevices and it seems if they were to release their source they and Walmart may get into a huge amount of trouble as well as lawsuits filed against them. I’m finding these tablets have a sim installed somewhere and are uploading and downloading data via hidden software I’ve disabled the Verizon network locks and the data services in my device I just haven’t been able to really get into it to see what data is being transfer but I have also found some kinda remote camera and sound recorder software also hidden on the device.

KaosKreationz said:
I’ll look into it sorry I’ve been having some issues lately and haven’t gotten much done on this thread. I was hoping to make an all in one spot for the newer android 10 models. I’ll get the 7 model info and stocks here soon. Is there already a working orange state mod already? If so can you link it and I’ll get into messing with it.
also these Mtk devicesseem to be difficult to get the source for. I’ve contacted mtk multiple times now and still have not gotten a response. I have however been digging through the hidden settings of thesedevices and it seems if they were to release their source they and Walmart may get into a huge amount of trouble as well as lawsuits filed against them. I’m finding these tablets have a sim installed somewhere and are uploading and downloading data via hidden software I’ve disabled the Verizon network locks and the data services in my device I just haven’t been able to really get into it to see what data is being transfer but I have also found some kinda remote camera and sound recorder software also hidden on the device.
Click to expand...
Click to collapse
Don't know about your data transfer theory but there's the post with the 10.1" Pro lk.img edit to remove the Orange State warning.
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com

PleaseBeNicetoMe said:
Don't know about your data transfer theory but there's the post with the 10.1" Pro lk.img edit to remove the Orange State warning.
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
Click to expand...
Click to collapse
thnx ill check this out very soon. im working on a Wiko Ride rn. frp bypass was a total pain took 2 days of trial and error but i was able to bypass.XD

hightowerc said:
Help! I followed the instructions in the OP, and everything worked fine. I then used ADB to uninstall some of the preinstalled apps, but I think I uninstalled something I shouldn't have. i'm getting crashes from mutltiple apps (Bluetooth, Contacts, etc).
I've downloaded the stock firmware/full in the linked GDrive share; how can I restore back to this stock firmware? I'm pretty new/noob with this, but I am familiar with Linux commands. (familiar enough to be dangerous...)
Click to expand...
Click to collapse
What’s your system? Did you get it fixed? I know I screwed up my first go round with the 10.1 Bluetooth and such kept crashing after I removed one of the un used features well supposed to be unused. It was the telephony and the contacts and autodialer that caused my issues. But like I stated before there seems to be some kind of wireless data traffic that’s not supposed to be there hidden software wise and it seems to utilize the cellphone apps that are supposed to be unused. Like the original bloatware remover from one of these threads on the original android 9 versions cannot be used bc there is something utilizing the cellphone data apps.
Anyway if there is anything you need firmware wise let me know I’ll upload whatever I have available.

This is just BS. I agree about the hidden sim. I went through the different log files. This entire system is corrupt. My Google play store was installed by.... You guessed it Google Play. Click on it and I get a retry
My new Samsung phone is also screwed up and the 102.00 for Norton VPN and security was shredded in seconds.
There is NO original boot, no original system. What an I supposed to do? This is the 2nd one. Can't hard reset damn phone, Cricket because I've lost so many. I was able to hard set the Samsung without the SIM card, and it was perfect. Put the SIM card in, and all that freaking bloat comes in.
So I'm no IT person, with compromised systems that's supposed to download ANYTHING and just hope I'm not redirected?? I'm just so suck and Tues off this. I just need to search, make phone calls. I don't even do any social media any longer! Please, tell me what I can trust anymore??? And I'm just out another round it up to 500.00 and I'm in disability. I'm so disheartened and hopeless

I used this method to root the new tablet I just picked up, and now whenever I launch any app it freezes my tablet and forces a fast reboot of the tablet, I believe I am on android 10, but I can't confirm as I can't even open settings

okay, so I tried to completely flash the stock images you provided in the other thread, got everything working again, without root, then flashed the patched images you had and got stuck in a screen that just said onn with nothing else happening
edit: I have adb access to the device when it's plugged in so I'm not sure what is happening

Alright, I found out my issue, I was flashing the wrong patched boot img on an older firmware instead of updating to latest, I have gotten a working magisk root on the 10.1 tablet.

So as promised I have attached the lk.bin with the no orange state modification it does still seem to hang for 5 seconds but the ugly message is no longer visible.
this is for the 100003562 10.1 inch model but should work with the newer 10.1 inch models with the MT8768WA chipset that come with android 10.
Installation Instructions:
1. Download lknoorange.bin attached to post.
2. Open either powershell (Windows) or Terminal (linux) where you have the file saved.
3. Put device in fastboot mode by powering on and holding the volume up button and selecting fastboot with volume down button.
4. Use command:
"fastboot flash lk lknoorange.bin"
5. Use command:
"fastboot reboot"
Now you should no longer see the ugly message on boot.
Always love getting donations thanks again all and I wish you the happiest of holidays.

Trixi Needs a Rabbit said:
This is just BS. I agree about the hidden sim. I went through the different log files. This entire system is corrupt. My Google play store was installed by.... You guessed it Google Play. Click on it and I get a retry
My new Samsung phone is also screwed up and the 102.00 for Norton VPN and security was shredded in seconds.
There is NO original boot, no original system. What an I supposed to do? This is the 2nd one. Can't hard reset damn phone, Cricket because I've lost so many. I was able to hard set the Samsung without the SIM card, and it was perfect. Put the SIM card in, and all that freaking bloat comes in.
So I'm no IT person, with compromised systems that's supposed to download ANYTHING and just hope I'm not redirected?? I'm just so suck and Tues off this. I just need to search, make phone calls. I don't even do any social media any longer! Please, tell me what I can trust anymore??? And I'm just out another round it up to 500.00 and I'm in disability. I'm so disheartened and hopeless
Click to expand...
Click to collapse
I guess i'm kinda lost here at what you may be stating and or asking? what device are you needing help with? I do not have a samsung so i honestly can not be of much help other then to point you in the right direction.
If you need help with a stock image for the 100003562 i have one here.