Related
I installed an Eonon GA5153F the other day and I can't seem to figure out what MCU it is compatible with. From Eonon it comes with MCU: MTCB-ZD v2.68. I know the GA5153 is compatible with KLD but this one has that F at the end of the model number. Can I just install a pre rooted rom without messing with the MCU (flash only the rom and not the MCU)? I really want to install Malaysk's rom and have all that rooted goodness.
has anyone successfully installed Malaysk's rom on the GA5153F yet?
Hi I have a eonon I used this thread and its all ok its running KitKat 4.4.4
http://forum.xda-developers.com/showthread.php?t=2660662
Sent from my GT-P5210 using XDA Free mobile app
pcmender2005 said:
Hi I have a eonon I used this thread and its all ok its running KitKat 4.4.4
http://forum.xda-developers.com/showthread.php?t=2660662
Sent from my GT-P5210 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the reply. Is your a GA5153F? Im starting to think it is a JY unit now because it has the JY apps installed.
hippie131 said:
Thanks for the reply. Is your a GA5153F? Im starting to think it is a JY unit now because it has the JY apps installed.
Click to expand...
Click to collapse
No mine is a eonon GA5162 no trouble rooting it and updating it mate
Try this mate its jy rom
http://huifei.fs-fileserver.de/content/firmware/KK 4.4.4 Dualcore (Factory & DSA Rooted)/JY 4.4.4/
Sent from my GT-P5210 using XDA Free mobile app
Any update on this?
Have the same HU (Eonon GA5153F) and want to install a custom ROM and TWRP recovery, but can't find anything relevant to 'ZD' MCU.
I too have just installed the GA5153F in my car and while it's a good unit, I'd love root to be able to do a little more with it. Like yours, mine says ZD 2.68 and having only had it installed for a few hours, I'm nervous about flashing something that could brick it immediately!
Looking forward to hopefully getting some more information on this one soon
Just found the thread that tells you the access code you use in Factory Settings that gives you root - *#hct#root#
Think I'm gonna start there and see how it progresses..
You get root with that code, then you can install SuperSU from Play store and update su binaries (before restarting). Then you have fulltime root (tested).
Waiting for TWRP to do a nandroid backup before messing more with the system...
hi there, did you flashed any rom yet? i would love to have 2gb space for app...Malaysk's (mmm )i do have the same unit, ive rooted, installed xposed and a few modules, everything is ok till now!...
Upd - i did flashed Malaysk's ROM And all went fine much much better now!
You flashed the ROM from here http://huifei.fs-fileserver.de/cont...k/Malaysk Quadcore RK3188/800x480/09.09.2015/ without messing with MCU?
Did you change CAN-BUS settings or did they work out of the box (the default is VW simple if I remember correctly)?
no, was update_4_4_4_800X480_8_RK3188_MAL_19_10_2015 found here
http://forum.xda-developers.com/showthread.php?t=3246370
go down and you will found it!
maybe you have to change the bt(bluethooth), from 6 to 5 on factory settings
well i can tell you it worth flash this rom.....from 10 to 100% better
pedromaiaz said:
no, was update_4_4_4_800X480_8_RK3188_MAL_19_10_2015 found here
http://forum.xda-developers.com/showthread.php?t=3246370
go down and you will found it!
maybe you have to change the bt(bluethooth), from 6 to 5 on factory settings
well i can tell you it worth flash this rom.....from 10 to 100% better
Click to expand...
Click to collapse
Yeah, eventually I found the thread after some digging, and found there is this updated ROM version which is not on the server.
Now I have to find the time to try it
i have a MTCB-ZD-V2.81 what could it be? is a Eonon GA5163F
Maybe...its for mazda?....same specs i think!
yeah mines for mazda
I've got a GA5163F (for Mazda) as well and I have the MTCB-ZD-V2.81 MCU. How did you guys go about flashing Malaysk's ROM? I'm trying to follow the thread but I'm a little confused.
mokflurry said:
I've got a GA5163F (for Mazda) as well and I have the MTCB-ZD-V2.81 MCU. How did you guys go about flashing Malaysk's ROM? I'm trying to follow the thread but I'm a little confused.
Click to expand...
Click to collapse
i got it to install on mine. you can go to http://forum.xda-developers.com/showthread.php?t=3246370 for the latest firmware.
then RK3188 800x480
download the latest and extract it. from there it should have instructions on what to do.
if not put the "update.img" on the root of sd or usb (fat32), plug it in and enter recovery,
-To get into the Recovery Menu:
-Use a paper-clip and press and hold the RES button by the eject button for 3 seconds.
-Keep the RES button pressed and hold the power button for 3 seconds.
-Release the RES button, keep power button pressed
-Release the power button once the lights turn on.
Flashing the rom:
Malaysk Rom Only:
1. Wipe all the data/factory and cache reset.
Note: This will erase the flash memory and give 2 gb of instead of the 1 gb of factory application installation memory using the Malaysk Rom.
It will also delete the factory rom. No going back.
2. Update system/mcu image from usb.
Credit to this thread for instrutions:
http://forum.xda-developers.com/and...non-ga5151f-mazda-3-android-headunit-t3240475
kuraijay said:
i got it to install on mine. you can go to http://forum.xda-developers.com/showthread.php?t=3246370 for the latest firmware.
then RK3188 800x480
download the latest and extract it. from there it should have instructions on what to do.
if not put the "update.img" on the root of sd or usb (fat32), plug it in and enter recovery,
-To get into the Recovery Menu:
-Use a paper-clip and press and hold the RES button by the eject button for 3 seconds.
-Keep the RES button pressed and hold the power button for 3 seconds.
-Release the RES button, keep power button pressed
-Release the power button once the lights turn on.
Flashing the rom:
Malaysk Rom Only:
1. Wipe all the data/factory and cache reset.
Note: This will erase the flash memory and give 2 gb of instead of the 1 gb of factory application installation memory using the Malaysk Rom.
It will also delete the factory rom. No going back.
2. Update system/mcu image from usb.
Credit to this thread for instrutions:
http://forum.xda-developers.com/and...non-ga5151f-mazda-3-android-headunit-t3240475
Click to expand...
Click to collapse
Thank you so much! That's quite extensive and helpful. So I'm downloading (update_4_4_4_800X480_RK3188_10_MAL_11_12_2015.rar) and I see there's a READ ME.doc and update.img in it. I'm assuming the read me will have the instructions and the update.img is essentially the ROM? I'm familiar with flashing roms on my phones but I'm used to seeing ROMs in .ZIP formats.
Did you do a back up of any sort? Just want to make sure I'm not missing anything.. thanks!
I just wanted to help shed some light regarding issues rolling back from Android N back to M with the Nexus 6p. Prior to having this device I used to own a Huawei Ascend Mate 7. Back in the day when the Mate 7 had Lollipop, we also used to have "previews" of MM. Given the differences in regional models one had to flash firmware from certain regions just to get the Upgrade file to MM.
That said while upgrading to MM for the Mate 7 was a mostly straightforward affair, climbing back down the ladder was a different story. The way I remembered it if we wished to go back to Lollipop the following had to be done:
1.) Download a "Roll-back" file to be flashed via stock recovery. Now after flashing back this file, the OS is still technically "MM" but is now compatible for downgrading.
2.) Then one had to download the ff. next:
-The full firmware you are transitioning back to (Lollipop or Kitkat)
-The latest stock recovery compatible with the version you are downgrading to
3.) Then lastly flash back the recovery file via fast boot then after a reboot flash back the firmware via stock recovery. Afterwards you are back to your previous Android version.
If one bypasses the steps mentioned and flashes the previous firmware right away the same boot loops occur. Like with the 6p, flashing the OTA/upgrade files change not only the related images, but also the way the phone is partitioned. This is why I think a "Roll back" file is necessary-it restores the partitioning and under the hood stuff to make the phone compatible again with the previous android version.
Now we have to find out where we could find such file. For those who were on the previous Dev previews (Np5 downwards) who downgraded back to MM, How did you guys go about the process? I think the process with downgrading from Preview to MM should also hold the key to resolving the boot loop when downgrading from the official version. What do you guys think?
blitzkriegger said:
I just wanted to help shed some light regarding issues rolling back from Android N back to M with the Nexus 6p. Prior to having this device I used to own a Huawei Ascend Mate 7. Back in the day when the Mate 7 had Lollipop, we also used to have "previews" of MM. Given the differences in regional models one had to flash firmware from certain regions just to get the Upgrade file to MM.
That said while upgrading to MM for the Mate 7 was a mostly straightforward affair, climbing back down the ladder was a different story. The way I remembered it if we wished to go back to Lollipop the following had to be done:
1.) Download a "Roll-back" file to be flashed via stock recovery. Now after flashing back this file, the OS is still technically "MM" but is now compatible for downgrading.
2.) Then one had to download the ff. next:
-The full firmware you are transitioning back to (Lollipop or Kitkat)
-The latest stock recovery compatible with the version you are downgrading to
3.) Then lastly flash back the recovery file via fast boot then after a reboot flash back the firmware via stock recovery. Afterwards you are back to your previous Android version.
If one bypasses the steps mentioned and flashes the previous firmware right away the same boot loops occur. Like with the 6p, flashing the OTA/upgrade files change not only the related images, but also the way the phone is partitioned. This is why I think a "Roll back" file is necessary-it restores the partitioning and under the hood stuff to make the phone compatible again with the previous android version.
Now we have to find out where we could find such file. For those who were on the previous Dev previews (Np5 downwards) who downgraded back to MM, How did you guys go about the process? I think the process with downgrading from Preview to MM should also hold the key to resolving the boot loop when downgrading from the official version. What do you guys think?
Click to expand...
Click to collapse
That isn't how it works on a Nexus, no such thing as a roll-back. It's a phone manufactured by Huawei, but it doesn't operate in the same way.
Heisenberg said:
That isn't how it works on a Nexus, no such thing as a roll-back. It's a phone manufactured by Huawei, but it doesn't operate in the same way.
Click to expand...
Click to collapse
Yes of course I'm well aware of that. I can't imagine going back to the mate 7 and the horrors of its upgrade process. I guess what I'm getting at is that there is an in-between thingy majingy yet to be dully understood with regards to rolling back, as some of the people having issues even after doing a direct fastboot flash of stock MM images coming from Nougat. Anyways just throwing out some ideas.
I'm trying to root the brand new model with MediaTek processor (Z300M) but nothing has worked so far. Any suggestions?
I'm surprised there is no root for this ?? I'd love to get rid of all the ASUS bloatware??
any luck?
for any mt8163 devices anywhere?
Damn, hoped by now there would be something... oh well... back to the cave.
Asus ZenPad 10 Z300M (P00C) Android 6.0
Has Anyone had any luck finding a way to unlock the bootloader on a Z300M (P00C) (marshmallow 6.0, Android security patch level 1 December 2016)
I'm trying to root it so I can change the ROM on it to the new Android 7.1 . I've been reading all the post in hear about it, Tried all the intel stuff (no joy) KingRoot doesn't work, Won't pay OneClick.. Came across some dodgy webpage with a program called Autoroot tools V3.0 Which wants you to install some software first before it lets you download the program....... very suspect.. so no. Back to square one No Unlocked Bootloader, no root....... can anyone help ?
You may find this useful ..
https://forum.xda-developers.com/an...d-10-z300c-t3214802/post65188654#post65188654
Asus have released their bootloader unlock tool, it may be somewhere to start. I'd suggest you check the support section of the asus website for the Z300M. I've downloaded, installed and tried to run however it failed. I've updated the tablet to android 7.0 and made no other modifications, tried on the home WiFi and hotspot through my phone. Failing them two I attempted to reflash 7.0 in the hopes that would help... The tablet doesn't pick up the files. Possibly because it isn't so much an update?
Either way I've become stuck on this whole situation too. It's quite a pain and I don't have the knowledge to start from scratch, I'm not even sure where to start.
Guys, I'm pretty sure you don't need to unlock the bootloader to flash anything to that tablet. The Z300M and the Z380M are basically the same tablet, just with a different screen size. I've had a fully working TWRP custom recovery posted for the Z380M since April. There's also a version of Mediatek Smartphone Flash Tool that lets you flash it without any bootloader unlock. So here's what you need to do, in a nutshell, to build and flash a custom recovery for the Z300M:
Make a scatter file for this device. The partition layout may be the same as the Z380M, in which case you can just use mine (just change the project name). If not, you can build one from the GPT by reading off the first 4 or 5 sectors from the flash ROM with Flash Tool's readback function and converting the LBA addresses to byte addresses.
Take my recovery source code and import the compiled kernel from the Z300M.
Change TWRP's theme layout (e.g. to landscape mode).
Change the model/device names to ones corresponding to the stock names.
Compile and flash it with SP Flash Tool
I'll be glad to help build the scatter file, etc. Just PM me the GPT.
Removed all information due to the wrong process being used.
Im attempting to get info or at least start a thread on the possibility of ROOTING the (Walmart) ONN Surf 100005208 10.1"
It's a rebranding of the ONA19TB003. Same hardware, new name.
jordianz said:
Im attempting to get info or at least start a thread on the possibility of ROOTING the (Walmart) ONN Surf 100005208 10.1"
Click to expand...
Click to collapse
As @razredge stated, the Onn Surf 10.1 is merely a rebranding of its predecessor tablet. The Surf 10.1 can be rooted with or without TWRP. Follow the guides on rooting the previous Onn 10.1. Everything works exactly the same. TWRP is fully compatible as well.
can you share your stock firmware with me
no
the thing was a brick when i attempted the mod its a MT8768WA chipset not MT8163
Viva La Android said:
As @razredge stated, the Onn Surf 10.1 is merely a rebranding of its predecessor tablet. The Surf 10.1 can be rooted with or without TWRP. Follow the guides on rooting the previous Onn 10.1. Everything works exactly the same. TWRP is fully compatible as well.
Click to expand...
Click to collapse
KaosKreationz said:
the thing was a brick when i attempted the mod its a MT8768WA chipset not MT8163
Click to expand...
Click to collapse
Regardless of chipset platforms, both Onn 10.1" tablet variants can be rooted using the same TWRP and the same root method, and without TWRP by fastboot flashing a Magisk patched boot image.
Viva La Android said:
Regardless of chipset platforms, both Onn 10.1" tablet variants can be rooted using the same TWRP and the same root method, and without TWRP by fastboot flashing a Magisk patched boot image.
Click to expand...
Click to collapse
I keep reading it can’t and I do not want to brick this tablet so tell me exactly how to root it it’s the android 10 preloaded version.
---------- Post added at 08:37 PM ---------- Previous post was at 08:34 PM ----------
KaosKreationz said:
I keep reading it can’t and I do not want to brick this tablet so tell me exactly how to root it it’s the android 10 preloaded version.
Click to expand...
Click to collapse
Also how does one patch the image with magisk if the magisk software does not work on said tablet?
As well as how does one dump the images when so flash nor mt software doesn’t recognize the image.
KaosKreationz said:
I keep reading it can’t and I do not want to brick this tablet so tell me exactly how to root it it’s the android 10 preloaded version.
---------- Post added at 08:37 PM ---------- Previous post was at 08:34 PM ----------
Also how does one patch the image with magisk if the magisk software does not work on said tablet?
As well as how does one dump the images when so flash nor mt software doesn’t recognize the image.
Click to expand...
Click to collapse
Well, you just taught me something I wasn't aware of. I have not yet seen the Onn 10.1" variant with preloaded Android 10. My variant (Onn Surf 10.1, Model No. 100005208) came with Android 9 Pie. And I was able to root it using the TWRP build from my tablet's predecessor, which had the same chipset and also rah on Android 9 Pie. You seem to be referring to an entirely new variant that ships with Android 10. What is your exact model number and your current firmware build number? I'll see what I can find out.
Viva La Android said:
Well, you just taught me something I wasn't aware of. I have not yet seen the Onn 10.1" variant with preloaded Android 10. My variant (Onn Surf 10.1, Model No. 100005208) came with Android 9 Pie. And I was able to root it using the TWRP build from my tablet's predecessor, which had the same chipset and also rah on Android 9 Pie. You seem to be referring to an entirely new variant that ships with Android 10. What is your exact model number and your current firmware build number? I'll see what I can find out.
Click to expand...
Click to collapse
It just got a silent OTA update which I was trying to find in the saved directory but it went right to it and installed before i had a chance to pull it. ****ing thing has been a pain since i got it. trying to root and remove bloat bc its a decent setup and could run pretty fast if it were a clean android OS.
To answer your question it is the ONN 10003562 with MT8768WA Chipset ill update with the firmware one i fix the damn thing it bricked on me again while removing bloatware. this thing has some kinda tamper check or something. i get it starting to run really nice without root and then on reboot its a brick.
KaosKreationz said:
It just got a silent OTA update which I was trying to find in the saved directory but it went right to it and installed before i had a chance to pull it. ****ing thing has been a pain since i got it. trying to root and remove bloat bc its a decent setup and could run pretty fast if it were a clean android OS.
To answer your question it is the ONN 10003562 with MT8768WA Chipset ill update with the firmware one i fix the damn thing it bricked on me again while removing bloatware. this thing has some kinda tamper check or something. i get it starting to run really nice without root and then on reboot its a brick.
Click to expand...
Click to collapse
So you have yet another variant of the Onn 10.1" tablet. That's good to know. My 100005208 was merely a rebranding of its predecessor but it appears now that Onn has released yet another variant. Yeah, hold off on trying to root right now. Anything released with Android 10 out of the box uses the system-as-root (SAR) implementation. While Magisk does support SAR, the rooting process has changed up some. I'll see what I can dig up for you.
Viva La Android said:
So you have yet another variant of the Onn 10.1" tablet. That's good to know. My 100005208 was merely a rebranding of its predecessor but it appears now that Onn has released yet another variant. Yeah, hold off on trying to root right now. Anything released with Android 10 out of the box uses the system-as-root (SAR) implementation. While Magisk does support SAR, the rooting process has changed up some. I'll see what I can dig up for you.
Click to expand...
Click to collapse
ok thanks. the only thing I am able to really do is remove some bloatware. but even then it still runs like ****. I found some OTA's in one of the threads here and also its supposedly a stock from the box backup but the scatter doesnt match the chipset. I was hoping someone could inform me if there is a way to get an android ten backup of the older device and swap out keys or whatever the thing is checking for when it boots and flash it.
very limited with no real su so stuff wont work right when I delete certain bloatware. Also if anyone can inform as to how I can even pull my firmware and recover.img and boot.img etc. I have tried MTK device or whatever that software is as well as sp flashtool and nothing seems to read the device rom. can see the device but cant pull. its been so long since ive used or attempted to root an android device im out of practice.
KaosKreationz said:
ok thanks. the only thing I am able to really do is remove some bloatware. but even then it still runs like ****. I found some OTA's in one of the threads here and also its supposedly a stock from the box backup but the scatter doesnt match the chipset. I was hoping someone could inform me if there is a way to get an android ten backup of the older device and swap out keys or whatever the thing is checking for when it boots and flash it.
very limited with no real su so stuff wont work right when I delete certain bloatware. Also if anyone can inform as to how I can even pull my firmware and recover.img and boot.img etc. I have tried MTK device or whatever that software is as well as sp flashtool and nothing seems to read the device rom. can see the device but cant pull. its been so long since ive used or attempted to root an android device im out of practice.
Click to expand...
Click to collapse
Earlier, you mentioned a "silent OTA." Could you elaborate on that? Did the OTA install seamlessly, without rebooting to recovery? I'm wondering if your variant has A/B partitions.
Viva La Android said:
Earlier, you mentioned a "silent OTA." Could you elaborate on that? Did the OTA install seamlessly, without rebooting to recovery? I'm wondering if your variant has A/B partitions.
Click to expand...
Click to collapse
When I said silently I meant I was sitting at the computer with the tablet hooked up in adb mode and i walked away for maybe 3 minutes to relieve myself and upon returning the tablet was rebooting and installing an update. I swear I had the automatic updates in dev mode turned to off.
Here is what I gather from the device.
KaosKreationz said:
When I said silently I meant I was sitting at the computer with the tablet hooked up in adb mode and i walked away for maybe 3 minutes to relieve myself and upon returning the tablet was rebooting and installing an update. I swear I had the automatic updates in dev mode turned to off.
Here is what I gather from the device.
Click to expand...
Click to collapse
Thanks for the stats. Yeah it looks like you're fully Treble supported but non-A/B. Ok just to make sure I'm not missing something, sort of give me a simple outline on everything you've done from start until now. Did you mention your device was a brick when you got it, or did you brick it initially attempting to root? How did you recover from the brick? I'm assuming SP Flash Tool and I recall you mentioned something about a mismatched scatter file. I believe I have a root solution for you but I want to make sure I have my info correct. Thanks for helping me to help you. You seem to know your Android well.
It was a soft brick via adb removal of bloat ware it was able to be restored from factory settings..
I think I may almost have it but i'm to afraid of flashing the boot.img bc I did brick the first one I had via sp flash. The firmware someone added in this thread a bit back says 100003562 but the chipset is MT6765 not the MT8768WA. I was able to mod that boot.img with magisk but as I stated I'm to afraid to flash it I tried the fastboot boot magiskpatched.img command it seemed to read with no errors but it shutdown and then rebooted. soo im afraid it may cause a loop. Im trying now to figure out a way to remove the dm verity check but have had no success as of yet. if i could just pull my own roms Im sure I could get this to root with magisk maybe.
link to larger files https://drive.google.com/drive/folders/1-j0wj9d0FuLxvHdvW8CjYICp3-xV00cs?usp=sharing
I cant seem to get SP Flash to read the device scatter properly Im unable to pull roms with readback I think i have to set it up manually?
I have attached the screenshots, rom, magisk image created as well as the bug report from soft brick.
It would Be soo much easier if i could get the DM verity off and or pull my roms.
KaosKreationz said:
It would Be soo much easier if i could get the DM verity off and or pull my roms.
Click to expand...
Click to collapse
Ok as you probably know, your device has SAR (system-as-root) implementation, because it shipped with Android 10. It appears that you will need to install Magisk to recovery ramdisk, because your boot image contains no ramdisk. Magisk does support this, as you probably know. Go to this link and look under the heading "Magisk in Recovery"
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
My Moto G7 Play is SAR as well, and has no boot image ramdisk, so I have it rooted with Magisk installed to recovery. It's different indeed, but as of now, it's the only root solution for SAR devices with recovery ramdisk implementations like yours and mine. Magisk will actually "live" within the recovery partition and actually becomes hijacked by Magisk. As you will read in the link I sent, it is still possible to use recovery mode. You will need to get a stock recovery image from somebody with your variant who has pulled the image, or from a stock firmware package. In sum, you will be patching your recovery image, not your boot image. Accordingly, you will be flashing your /recovery partition to achieve root, not your /boot partition. As you know, as long as you are bootloader unlocked, you can flash the patched recovery image using fastboot. You will not need a TWRP for root. In the link I sent, also look for the previous heading "Patching Images." To test and make sure I'm 100% right on this, install the latest Magisk Manager app on your device and open the app. Look in the "Ramdisk" section. If it says NO, then I'm right and you must install Magisk to recovery as I've stated. If it says YES I'm wrong and you need to disregard this entire post.
But please let me know the status on things, and if you manage to get Magisk systemless root installed properly.
Anyone have a 100003562 boot.img or recovery.img for the MT8678WA
---------- Post added at 06:52 PM ---------- Previous post was at 06:45 PM ----------
I tried the recommended and it bricked I'm only able to use and now when the device boots it hangs at the logo screen or does anyone know Walmarts update software command.
Hey guys,
I was using TWRP + Lineage 15.1 ROM on my Fire HD 8 (2018 - 8th Gen) but decided to return to stock ROM and get rid of it.
As I didn't find any guidance anywhere I've tried to sideload the original stock ROM through TWRP even I didn't really think that was a good idea. I upladed the file (update-kindle-Fire_HD8_8th_Gen-PS7315_user_1958_0018354775684.bin - perhaps not the correct file anyway ) which resulted in boot loop. I now cannot access TWRP. Does anyone please have a link with instructions how to unbrick my device or even better with instructions to directly flash the stock ROM for 8th Gen please? I only keep finding links for older devices.
Many thanks guys.
ertech said:
Hey guys,
I was using TWRP + Lineage 15.1 ROM on my Fire HD 8 (2018 - 8th Gen) but decided to return to stock ROM and get rid of it.
As I didn't find any guidance anywhere I've tried to sideload the original stock ROM through TWRP even I didn't really think that was a good idea. I upladed the file (update-kindle-Fire_HD8_8th_Gen-PS7315_user_1958_0018354775684.bin - perhaps not the correct file anyway ) which resulted in boot loop. I now cannot access TWRP. Does anyone please have a link with instructions how to unbrick my device or even better with instructions to directly flash the stock ROM for 8th Gen please? I only keep finding links for older devices.
Many thanks guys.
Click to expand...
Click to collapse
It seems that the bootloader files for OS 6 (TZ and LK) are incompatible with OS 7.3.1.5. I found that you could not even shut down the tablet when it was bootlooping: holding the power button down for >30 seconds did nothing. To stop it you need to open the tablet and disconnect the battery.
You will need to copy a version of OS 6 onto a micro SD card (change the file extension from '.bin' to '.zip'). Insert the micro SD, after reconnecting the battery and putting the rear shell back on. You should be able to boot into recovery (TWRP) with the left volume button/ power button. Wipe system and data then flash the OS 6 zip.
Locate the newer thread for unlocking the HD 8/ 8th gen. tablet (amonet-3) and download the latest amonet version (currently 3.0.1) and the 'return to stock' zip, then follow the instructions in that thread to return to stock. Essentially you unzip the two downloads, merge, and run the return to stock script. From TWRP you boot the tablet into hacked fastboot mode and the script will restore stock boot and recovery images (unpatched). After a reboot you should be able to enter standard Amazon recovery mode. If you then ADB sideload the OS 7.3.1.5 software you will eventually boot into OS 7 (Pie).
Link to 'amonet-3' thread: https://forum.xda-developers.com/showpost.php?p=80166353&postcount=1
@MontysEvilTwin I haven't updated mine to 7.x release but wanted to see if you have been able to successfully unlock and root on newer firmware?
I'm guessing as you said bootloader files for OS 6 (TZ and LK) are incompatible, its not going to work?
madman said:
@MontysEvilTwin I haven't updated mine to 7.x release but wanted to see if you have been able to successfully unlock and root on newer firmware?
I'm guessing as you said bootloader files for OS 6 (TZ and LK) are incompatible, its not going to work?
Click to expand...
Click to collapse
I've had no luck unlocking the Karnak (or Mustang). I think there a couple of issues. The unlock doesn't work with the OS 7.3.1.5 bootloaders, you get a bootloop. I expected this as it is only the very first version of the Karnak LK file (OS 6.3.0.0) that has the necessary vulnerability for a full unlock. However if you use a modified version of Amonet to flash the OS 7.3.1.5 PL and TZ plus the OS 6.3.0.0 LK you get a bootloop, even without unlocking and unpatched stock boot and recovery images. It may not be impossible, I am hoping that the unlock authors (@xyz` and @k4y0z) will take a look at some point.
Thank you very much @MontysEvilTwin for your response and great explanation. Opening the device, disconnecting the battery and taking all these steps just to flash the stock ROM and selling it for a few pounds is probably way more effort than what it's worth. I'll probably just sell the case and hand the device for a safe disposal. It might be perhaps worth it to create a separate topic with a step by step walkthrough to safely revert a rooted device with TWRP & custom ROM back to Stock ROM for less advanced users like me? (I appreciate what I attempted to do was a bit stupid, just saying it would be useful having this explained somewhere...)
As I'm not going to use "Karnak" any more I'd like to thank everyone here for all their contributions as you made my experience with my device significantly better and also to thank everyone who found time to answer my questions. I just wanted to say that you're doing an amazing thing and making people like me happy. :good:
ertech said:
Thank you very much @MontysEvilTwin for your response and great explanation. Opening the device, disconnecting the battery and taking all these steps just to flash the stock ROM and selling it for a few pounds is probably way more effort than what it's worth. I'll probably just sell the case and hand the device for a safe disposal. It might be perhaps worth it to create a separate topic with a step by step walkthrough to safely revert a rooted device with TWRP & custom ROM back to Stock ROM for less advanced users like me? (I appreciate what I attempted to do was a bit stupid, just saying it would be useful having this explained somewhere...)
As I'm not going to use "Karnak" any more I'd like to thank everyone here for all their contributions as you made my experience with my device significantly better and also to thank everyone who found time to answer my questions. I just wanted to say that you're doing an amazing thing and making people like me happy. :good:
Click to expand...
Click to collapse
OK, if you just want to unbrick it is quite easy. If you have the latest TWRP (you will have if you unlocked with amonet version-3 for thIs tablet) it is likely that your bootloaders are unchanged. To get out of the bootloop you can either disconnect the battery or let it run down. Then you should be able to boot into recovery. From there you can flash a backup of your previous OS, or wipe system and data and reflash a stock OS 6 update.