How to dump the full OS image from the new 2019 SHIELD TV Pro? - Nvidia Shield TV & Shield TV Pro (2019) Questions

As the title states, my friend who has the new 2019 SHIELD TV Pro at his home wants to dump the OS so that developers can take a peek and figure out how the new AI Upscaling works, and if it is portable to the older shields. Thanks for any help.

Developers are already trying to figure this out.

SkOrPn said:
As the title states, my friend who has the new 2019 SHIELD TV Pro at his home wants to dump the OS so that developers can take a peek and figure out how the new AI Upscaling works, and if it is portable to the older shields. Thanks for any help.
Click to expand...
Click to collapse
Hi, is he able to unlock bootloader with fastboot? There is a twrp he could use to dump it. Thanks for offering, will be useful.

EDIT: What exactly do you have? He is currently ready to try adb and fastboot commands, but he is currently in the middle of looking for a cable and to position a PC close enough to his shield, lol
No, he hasn't done anything like that yet. He has been waiting for me to get proper instructions on the entire process. I will walk him through the adb setup and see if he can get into the bootloader soon.
Thanks for the offer, I will let him know asap. He lives in the UK and I in the US so we're 7 hours apart. But at least it's a Saturday, lol.

SkOrPn said:
EDIT: What exactly do you have? He is currently ready to try adb and fastboot commands, but he is currently in the middle of looking for a cable and to position a PC close enough to his shield, lol
No, he hasn't done anything like that yet. He has been waiting for me to get proper instructions on the entire process. I will walk him through the adb setup and see if he can get into the bootloader soon.
Thanks for the offer, I will let him know asap. He lives in the UK and I in the US so we're 7 hours apart. But at least it's a Saturday, lol.
Click to expand...
Click to collapse
Enable adb in developer settings and run `adb reboot-bootloader`.
A fastboot menu should show, use the power button to navigate and select unlock bootloader.
The device will be wiped and the bl will be unlocked.
Then boot into fastboot again and run `fastboot boot <twrp img I pm you>`

OK, I forgot about the wiping part. Good chance he might bail now, but we''ll see. Lol
EDIT: OK, he has no plan to bail on this process, but he can't find his A to A cable. So he just ordered it from Amazon. Will come back when he receives it. He ordered the UGREEN USB 3.0 cable below, so I hope that will work.
https://www.amazon.co.uk/dp/B00P0E39CM

SkOrPn said:
OK, I forgot about the wiping part. Good chance he might bail now, but we''ll see. Lol
EDIT: OK, he has no plan to bail on this process, but he can't find his A to A cable. So he just ordered it from Amazon. Will come back when he receives it. He ordered the UGREEN USB 3.0 cable below, so I hope that will work.
https://www.amazon.co.uk/dp/B00P0E39CM
Click to expand...
Click to collapse
i dont see why it wouldnt work lol.. its a to a..

elliwigy said:
i dont see why it wouldnt work lol.. its a to a..
Click to expand...
Click to collapse
We were questioning if it being 3.0 was an issue or not. Most if not all people I know of used 2.0 cables for adb. But he wanted to buy the 3.0 version for several valid reasons.

Hope this goes well

bylaws said:
Enable adb in developer settings and run `adb reboot-bootloader`.
A fastboot menu should show, use the power button to navigate and select unlock bootloader.
The device will be wiped and the bl will be unlocked.
Then boot into fastboot again and run `fastboot boot <twrp img I pm you>`
Click to expand...
Click to collapse
I never received that special TWRP that you have. I have the official one and the one from the 2017/2015 models in the older shield forums. Are you speaking about one of those?
EDIT: Never mind, as soon as he unlocked it, it disabled Dolby Vision which is the reason he purchased it in the first place. As soon as he re-locked the bootloader Dolby Vision came back. VERY interesting find. This means that the Dolby Vision license that NVIDIA purchased had a stipulation that it could not be enabled on unlocked devices. Makes sense. He is doing a TWRP backup at the moment, but we still don't know how to dump the OS proper. He is trying my twrp image that I use for my 2015 shield TV.

https://forum.xda-developers.com/showpost.php?p=80769929&postcount=312
Is that the one that booted?
Worst case, should be able to dd the images from /dev/block/platform. But the twrp backup is just a tar file, so should be able to extract stuff from there too.
Fwiw, I'm going to continue doing twrp and such support for these newer device in the same thread as the older devices.

SkOrPn said:
I never received that special TWRP that you have. I have the official one and the one from the 2017/2015 models in the older shield forums. Are you speaking about one of those?
EDIT: Never mind, as soon as he unlocked it, it disabled Dolby Vision which is the reason he purchased it in the first place. As soon as he re-locked the bootloader Dolby Vision came back. VERY interesting find. This means that the Dolby Vision license that NVIDIA purchased had a stipulation that it could not be enabled on unlocked devices. Makes sense. He is doing a TWRP backup at the moment, but we still don't know how to dump the OS proper. He is trying my twrp image that I use for my 2015 shield TV.
Click to expand...
Click to collapse
Thx for that valuable information! ....This sucks big time...no unlocked bootloader means no magisk thus no root.
I had small hopes that dolby vision passtrough would be possible on my 2017 model by porting the new 2019 firmware to it (theoretically dolby vision is possible on 2017 model from a hardware perspective) but until now I thought I could sell my 2017 model, get a 2019 one, root it through magisk and have dolby vision.
No dolby vision on a magisk rooted 2019 model is an absolute dealbreaker for me
I'm not happy how nvidia handeled this....I'd even pay a small amount to enable/unlock dolby vision somehow on my 2017 model..
I mean there had to be a better way. Like, get the amount of wanted dolby vision licenses, order x dolby vision licenses and then sell them for x$ to 2017 and 2015 owners.

Yeah agreed. The 2019 now looks like the worst of all the shield TV models to me, except for Dolby Vision. Sheer unadulterated 100% pure money grab by Nvidia. I won't be downgrading my shield hardware just for Dolby vision. Instead I'm going to hold out hope that these 2019 features somehow makes their way to the earlier models.

SkOrPn said:
Yeah agreed. The 2019 now looks like the worst of all the shield TV models to me, except for Dolby Vision. Sheer unadulterated 100% pure money grab by Nvidia. I won't be downgrading my shield hardware just for Dolby vision. Instead I'm going to hold out hope that these 2019 features somehow makes their way to the earlier models.
Click to expand...
Click to collapse
It is potentially possible to restore Dolby vision as it seems to be done in software (as it comes back when bl relock). A dump would be really helpful (see what steel01 said above)

bylaws said:
It is potentially possible to restore Dolby vision as it seems to be done in software (as it comes back when bl relock). A dump would be really helpful (see what steel01 said above)
Click to expand...
Click to collapse
Would be really good to see a full dump of the 2019 non PRO model too, being that it's 32-bit
The Shield Tablet needs some love...

Stickman89 said:
Would be really good to see a full dump of the 2019 non PRO model too, being that it's 32-bit
The Shield Tablet needs some love...
Click to expand...
Click to collapse
we have managed that, steel01 is working on porting it with the new blobs
a 64 bit one would still be useful though

bylaws said:
we have managed that, steel01 is working on porting it with the new blobs
a 64 bit one would still be useful though
Click to expand...
Click to collapse
Yeah I knew he intended on working on it; I spoke with him 2 weeks back. Well that's great news, he's got the new 32-bit blobs! That wasn't a thing when we spoke, he was still looking to acquire them.
Looks like I have to play catch up, admittedly I've been busy. Thanks for the update.
Best Regards,

bylaws said:
we have managed that, steel01 is working on porting it with the new blobs
a 64 bit one would still be useful though
Click to expand...
Click to collapse
Assuming root was needed, how the hell do we flash firmware in fastboot now on SIF model!? I been going crazy all weekend lol

elliwigy said:
Assuming root was needed, how the hell do we flash firmware in fastboot now on SIF model!? I been going crazy all weekend lol
Click to expand...
Click to collapse
By soldering a usb port to the internal usb header, hopefully there will be an alternative in the future though

If still needed I have a dump(DD) of recovery, boot, system and vendor if someone needs it. I also have the OTA zip file from last hotfix 8.1.1 which was pushed a few days ago.
I'm still having trouble with rooting the shield 2019 pro I'm able to get twrp working with the twrp experimental version but ones started it can not find system. Since it's nod defined in /proc/mounts.
Tried pachting the boot.img from the Ota zip file but keeps hanging on the Nvidia logo.
Will upload a file to Google drive.

Related

[Guides] Nexus 9 - Root & Custom Recovery + Videos Running Different ROMs

Exactly like the thread i started for the Shield Tablet, ill be uploading a lot of videos in this thread explaining how to unlock the bootloader, Root the Device and Install Custom Recovery
I'll make sure to test all the ROMs released for the device and upload videos running them to this thread.
Guides / Tutorials (Step by Step)
How to Unlock the Bootloader
How to Root
How to install TWRP/Custom Recovery
Nexus 9 Overclocked results
-------------------------------------------------------------
Videos running different custom ROMs
Ill be testing video, sound, webbrowsing, maps, play store and custom setting(if the rom provides them)
AICP
Candy5
CyanogenMod 12
Dirty Unicorns
Flounder Pure AOSP
LiquidSmoot
Lollipopalooza
Paranoid Android
RASTAPOP
Resurrection Remix
SimpleAOSP
SlimLP
Temasek
--------------------------------------------------------------
You put shield tablet in the thread title....
Sent from my OtterX using Tapatalk
Great looking forward to seeing some videos.
Just got information that my pre-order is delayed to Nov 15 = (
I promise to upload the videos asap when i get my device
EverythingPortable said:
Just got information that my pre-order is delayed to Nov 15 = (
I promise to upload the videos asap when i get my device
Click to expand...
Click to collapse
from who?
USBhost said:
from who?
Click to expand...
Click to collapse
From a local store here in gothenburg. I should have ordered from google
EverythingPortable said:
From a local store here in gothenburg. I should have ordered from google
Click to expand...
Click to collapse
Cool Nexus 9 my next tablet
I just got my 9 today. fastboot oem unlock right out of the box. BRING ON THE REST!!! w00t!!!
I want to point out that in the developer settings there is a tic box for "Enable OEM Unlock" that needs to be checked before you can run the command.
benniebeeker said:
I just got my 9 today. fastboot oem unlock right out of the box. BRING ON THE REST!!! w00t!!!
I want to point out that in the developer settings there is a tic box for "Enable OEM Unlock" that needs to be checked before you can run the command.
Click to expand...
Click to collapse
Getting mine today as well. I've always OEM unlocked immediately and rooted used SuperSU on all my Nexus devices. However, on the latest L Preview for Nexus 5 and 7 Chainfire said you had to install a custom kernel to obtain root due to SELinux changes. Since I'm loathe to run a custom kernel on a new chipset I'm thinking of staying locked for the foreseeable future. Frankly ruins the Android "make it your own" ethos I've ALWAYS valued, but I just ain't gonna put up with tons of growing pains while all this is worked out.....
BillLee3 said:
Getting mine today as well. I've always OEM unlocked immediately and rooted used SuperSU on all my Nexus devices. However, on the latest L Preview for Nexus 5 and 7 Chainfire said you had to install a custom kernel to obtain root due to SELinux changes. Since I'm loathe to run a custom kernel on a new chipset I'm thinking of staying locked for the foreseeable future. Frankly ruins the Android "make it your own" ethos I've ALWAYS valued, but I just ain't gonna put up with tons of growing pains while all this is worked out.....
Click to expand...
Click to collapse
You should just unlock the bootloader out of the box anyway. Will save you much headache down the road when you decide to do it and already have a bunch of data on your device.
Brian706 said:
You should just unlock the bootloader out of the box anyway. Will save you much headache down the road when you decide to do it and already have a bunch of data on your device.
Click to expand...
Click to collapse
This. I always unlock first thing if I have any intentions on doing it at all. Simply because I don't want to lose my data later on. Unlocking is easy and took me 2 minutes on my nexus 9. No reason not to.
Sent from my G3
jreyno10 said:
Unlocking is easy and took me 2 minutes on my nexus 9. No reason not to.
Click to expand...
Click to collapse
"No reason not to" meaning Google doesn't invalidate warranty merely by unlocking, right ?
Nexus were made to be unlocked.
mikereidis said:
"No reason not to" meaning Google doesn't invalidate warranty merely by unlocking, right ?
Nexus were made to be unlocked.
Click to expand...
Click to collapse
+1 there
Oh, that's good to know! This is my first Nexus device.
So, unlocking does not void the warranty in any way?
Scotlac said:
Oh, that's good to know! This is my first Nexus device.
So, unlocking does not void the warranty in any way?
Click to expand...
Click to collapse
Discussing that here: http://forum.xda-developers.com/nexus-9/help/unlocking-bootloader-rooting-n9-void-t2931784
By from HTC and warranty may be affected.
By from Play, and I think warranty is OK.
I'm considering returning mine since I'm underwhelmed for $400, and I'll just relock it and return to stock first.
mikereidis said:
Discussing that here: http://forum.xda-developers.com/nexus-9/help/unlocking-bootloader-rooting-n9-void-t2931784
By from HTC and warranty may be affected.
By from Play, and I think warranty is OK.
I'm considering returning mine since I'm underwhelmed for $400, and I'll just relock it and return to stock first.
Click to expand...
Click to collapse
I think regarding HTC, it depends on what's affected. I don't think that they will deny you a hardware warranty just because you unlocked the bootloader and/or rooted. Unlocking the bootloader is a safe process sanctioned by HTC themselves. Well, on HTC devices anyway. Nexus won't require HTCdev unlock.
They really can't even tell that you rooted or what you've done if you return to stock. All they know is that you unlocked the bootloader at some point. If the phone legitimately malfunctions, they won't deny you a repair/replacement just because you unlocked.
The first videos are now uploaded, hope you enjoy them. Everytime a new cusom rom is released ill upload a videos running the rom. Ill be testing video, sound, webbrowsing, maps, play store and custom setting(if the rom provides them)
Where can I download the script in the videos please?
albsat said:
Where can I download the script in the videos please?
Click to expand...
Click to collapse
Not sure i understand, what script?
EverythingPortable said:
Not sure i understand, what script?
Click to expand...
Click to collapse
There is a bat script in the videos, for bootloader unlock and root install. Where can I download it?

Root method for xt1528 once we can recover from QDL mode

Hi,
If people would like to figure out how to get the xt1528 out from QDL mode then I will provide a method for PERM root and xposed as we did for the moto x here.
This is an article that talks about working with the new sahara protocol the Moto E uses. The qdloader used for the moto x is an older protocol.
Good luck!
jahrule said:
Hi,
If people would like to figure out how to get the xt1528 out from QDL mode then I will provide a method for PERM root and xposed as we did for the moto x here.
This is an article that talks about working with the new sahara protocol the Moto E uses. The qdloader used for the moto x is an older protocol.
Good luck!
Click to expand...
Click to collapse
This will be awesome.
Sent from my XT1528 using XDA Free mobile app
jahrule said:
Hi,
If people would like to figure out how to get the xt1528 out from QDL mode then I will provide a method for PERM root and xposed as we did for the moto x
Click to expand...
Click to collapse
How did you get it into the QDL mode?
fire3element said:
How did you get it into the QDL mode?
Click to expand...
Click to collapse
You get into it by soft bricking your phone. But you can't get out until someone can do the procedure above. I am sure it is trivial using qfil but I run Linux solely and am not in a rush just giving a helping hand to someone here if they want to put a little effort in.
jahrule said:
You get into it by soft bricking your phone. But you can't get out until someone can do the procedure above. I am sure it is trivial using qfil but I run Linux solely and am not in a rush just giving a helping hand to someone here if they want to put a little effort in.
Click to expand...
Click to collapse
I am ready to get the ball rolling on this. This phone needs root at the least, since the bootloader is locked (thanks to Verisucks). I will PM you.
fire3element said:
I am ready to get the ball rolling on this. This phone needs root at the least, since the bootloader is locked (thanks to Verisucks). I will PM you.
Click to expand...
Click to collapse
Pm responded
How's it going?
I can help with this as well. I have my XT1528 on standby. Don't have much dev experience with Android, but I can sure try.
Unless you are willing to stare endearingly at a shiny paperweight that once was your phone, I don't think anyone can do much to help.
To sum this up for new eyes wondering where this might be headed:
Motorola (along with many of the other major phone manufacturers) have removed the ability to load QDownload mode manually. Apparently, the XT1528 along with many newer devices, is now running a new protocol for the diagnostic port. (and there is more than one way the port can be present/active, to further complicate things)
Please do not ask me to explain. I am just barely beginning to understand this stuff myself.
As of right now, the only known method to get our Verizon 2nd gen Moto E into QDL is to actually BRICK the device. At which point the phone will resort to the next level down, since it can not boot properly.
So unless you are willing to intentionally brick your phone to advance this cause... I am afraid that you can not do much.
There is also the looming risk that the device can not be recovered if the new protocols are not figured out. I am treading in uncharted waters here.
Means you or I lost a phone and the $$$ spent on it. By another one and try again.
If you are adamant about wanting to help, click on the 2 links in the OP. @jahrule has posted information that tells us with direction to go.
And if you do not understand what is going on in either article........................................ maybe it is best left alone.
Not being harsh, just safer that way. I am having to figure this stuff out as I go too.
As for progress..? None. I am not intentionally bricking my phone until I gather enough info that will lead me to the conclusion that I can recover the device.
So goes without saying. BE NICE____DO NOT PESTER
@fire3element
I got mine brand new off of Amazon for $48.00, if someone wants to sacrifice the 48 bucks? My note 4 just came in, so I might be willing to brick mine for the cause. I will do some reading where you posted earlier and see what I can do
---------- Post added at 08:20 PM ---------- Previous post was at 08:15 PM ----------
neo4uo said:
@fire3element
I got mine brand new off of Amazon for $48.00, if someone wants to sacrifice the 48 bucks? My note 4 just came in, so I might be willing to brick mine for the cause. I will do some reading where you posted earlier and see what I can do
Click to expand...
Click to collapse
@jahrule
Are you proposing that we brick the phone and use an international boot loader with the Verizon modem to flash, since the boot loader would be corrupt it wouldn't be locked anymore?
jahrule said:
Are you proposing that we brick the phone and use an international boot loader with the Verizon modem to flash, since the boot loader would be corrupt it wouldn't be locked anymore?
Click to expand...
Click to collapse
No, we are not trying to mess with the bootloader. I do not think we even could. The ideal way to go about that would be to use the XT1526 Boost Mobile bootloader and modify it to fit the XT1528. Those 2 models are about the closest in hardware of all the variants. (and I have already tried working on this in the last few months with no progress)
I do not think that would work anyways.
What we are attempting to do here is inject root into the system partition after the kernel startup. After the OS is booted, and root is in place, it should become permanent from then on. At least until you delete, install over, or wipe the device.
The issue here is, there is no way to manually put the phone into QDL mode. (as I mentioned in my post above).
Once we are in QDL, there is no known way to get it out. If the flasher tool does not see/read the phone, there will be no way to recover since we can not flash files to fix what we had to break to get there in the first place.
See the paradox now? LoL
Personally, I can not afford to throw this phone to the gutter. Simply do not have that kind of money laying around. If you can stand to throw $50 into the wind, more power to you Bro
Give it a go, but don't be careless just for the sake of wanting to try something. (speaking from experience here)
UPDATE: I think I am going to hold off on this for now. Looks like the Stagefright vulnerability is going to lead to a new ROOT exploit.
This is bad news for android, but great news for those of us that have locked down devices. Please download the Zimperium StageFright Detector app from the play store to see if you device is vulnerable.
If it is, DO NOT TAKE ANY UPDATES till we get confirmation that a new exploit will benefit us or not.
My GoPhone moto e says it is vulnerable running 5.1 stock firmware
Sent from my MotoE2(4G-LTE) using XDA Free mobile app
fire3element said:
No, we are not trying to mess with the bootloader. I do not think we even could. The ideal way to go about that would be to use the XT1526 Boost Mobile bootloader and modify it to fit the XT1528. Those 2 models are about the closest in hardware of all the variants. (and I have already tried working on this in the last few months with no progress)
I do not think that would work anyways.
Click to expand...
Click to collapse
The bootloader is the same. This will help nothing.
fire3element said:
What we are attempting to do here is inject root into the system partition after the kernel startup. After the OS is booted, and root is in place, it should become permanent from then on. At least until you delete, install over, or wipe the device.
Click to expand...
Click to collapse
What we are trying to do is use qfil or blanflash qflash to recover from QDL mode and be able to write partitions from there.
fire3element said:
The issue here is, there is no way to manually put the phone into QDL mode. (as I mentioned in my post above).
Once we are in QDL, there is no known way to get it out. If the flasher tool does not see/read the phone, there will be no way to recover since we can not flash files to fix what we had to break to get there in the first place.
Click to expand...
Click to collapse
Issue is only recovering from QDL mode which is the goal see above. Getting the phone into QDL mode is very easy.
fire3element said:
See the paradox now? LoL
Personally, I can not afford to throw this phone to the gutter. Simply do not have that kind of money laying around. If you can stand to throw $50 into the wind, more power to you Bro
Give it a go, but don't be careless just for the sake of wanting to try something. (speaking from experience here)
UPDATE: I think I am going to hold off on this for now. Looks like the Stagefright vulnerability is going to lead to a new ROOT exploit.
This is bad news for android, but great news for those of us that have locked down devices. Please download the Zimperium StageFright Detector app from the play store to see if you device is vulnerable.
If it is, DO NOT TAKE ANY UPDATES till we get confirmation that a new exploit will benefit us or not.
Click to expand...
Click to collapse
Stagefright will get one system permissions not root permissions.
neo4uo said:
@fire3element
I got mine brand new off of Amazon for $48.00, if someone wants to sacrifice the 48 bucks? My note 4 just came in, so I might be willing to brick mine for the cause. I will do some reading where you posted earlier and see what I can do
---------- Post added at 08:20 PM ---------- Previous post was at 08:15 PM ----------
@jahrule
Are you proposing that we brick the phone and use an international boot loader with the Verizon modem to flash, since the boot loader would be corrupt it wouldn't be locked anymore?
Click to expand...
Click to collapse
I am proposing that you read the way CrashXXL achieved root on the moto x and we do the same
jahrule said:
Stagefright will get one system permissions not root permissions.
Click to expand...
Click to collapse
Surely I am not misinterpreting what I am seeing here.
https://www.youtube.com/watch?v=PxQc5gOHnKs
Looked for a video of Josh's DefCon presentation, but could not find one. So either he has not presented yet, or no one had uploaded the vid at this time.
Here is an excerpt from the Zimperium blog:
" 2. Zimperium Research Labs (zLABS) will release a video later this week with a Stagefright RCE demonstration. Several large carriers requested that we delay the release of our working exploit. We agreed, given the gravity of the situation. Unfortunately, because the patches are open-source [1, 2], many researchers are already working on creating an exploit. We are planning to release our exploit on August 24th, 2015. However, if an exploit is publicly released or attacks are detected in the wild before that date, we will release ours for testing purposes at that time. "
and
" 6. Josh will present the full details of his research at Black Hat on August 5th or DEFCON on August 7th. We invite you to join us! "
Hopefully this is the new exploit we have all been waiting for. I know that I need to move away from my current device because of hardware issues, however I can not do that until I root this device. More info is sure to come in the next few weeks
jahrule said:
The bootloader is the same. This will help nothing..
Click to expand...
Click to collapse
I should have clarified myself. My attempt was to replace the Verizon "locked" bootloader withe the Boost "un-locked" bootloader.
Again, I do not think it will work. However, if the flasher tool will actually work with this phone, then I suppose it would not hurt to try it. If it does not work, simply flash your backup of the original BL.
Is it possible to flash 5.0.1 back after you update? or remove any update..? Hahaha I updated mine for stagefright without thinking. Diddnt know untill i checked it & found it wasnt vunarable. I know it was before.. Ugh. Carelessness on me behalf.
Hey guys, I have this phone as well as the htc desire 526 pp and they are both just laying in a drawer. I bought them when I couldn't afford a real replacement for my broken nexus 6 and now that I don't need either I would be more then willing to sacrifice mine for the sake of helping out. Plus if it works then the phone is rooted, negative if I can't use it I can free up some drawer space. Not a big loss either way as the screen is too small for my liking. Very nice phone otherwise just not enough space or screen.
So just a quick little update on this.
I purposely bricked another Moto E and was able to get it to show up in the Device Manager as QCOM_BULK (not the exact wording, I forgot) . This required me to flash a bad Bootloader to get the device to fail to turn on, thus kicking it into the fall back mode. I tried flashing all other partitions to make the phone go into the BULK mode. None worked except for the bootloader.
Could not get anywhere with it. We need some specific files to flash in order to get the device rooted or bootloader unlocked. Its not just a few files either, and they have some weird extensions.
I ended up taking the device back and getting something else. Just don't have time to keep playing with it. Someone smarter than me could probably get it done with not a whole lot of effort.
Sorry guys. I tried with my limited knowledge and skills.
Since you have abandoned this project, do you think you could PM me any/all info you have? I would like to take a stab at this.
Steve_xposed said:
Since you have abandoned this project, do you think you could PM me any/all info you have? I would like to take a stab at this.
Click to expand...
Click to collapse
I too would like to see the process, in order to enter QDL mode, I LITERALLY have no use for this phone as it is damaged but still boots and can use screen

Change emmc Chip to achieve root?

If i were to change the emmc chip on my 7th gen 7" and 8" fire tablets for an emmc chip with vanilla Android am i likely to run into any issues?
J_IO_B said:
If i were to change the emmc chip on my 7th gen 7" and 8" fire tablets for an emmc chip with vanilla Android am i likely to run into any issues?
Click to expand...
Click to collapse
yes, you will run into many problems. 1st problem is desoldering it. 2nd problem if desoldering wasn't a dead end, finding a preprogrammed emmc chip that will work for it is pretty much impossible. but don't worry there is a new exploit for all MediaTek processors that will let you flash partitions in boot rom mode! it's only a matter of time for this device to get hacked.
ANDROID2468 said:
yes, you will run into many problems. 1st problem is desoldering it. 2nd problem if desoldering wasn't a dead end, finding a preprogrammed emmc chip that will work for it is pretty much impossible. but don't worry there is a new exploit for all MediaTek processors that will let you flash partitions in boot rom mode! it's only a matter of time for this device to get hacked.
Click to expand...
Click to collapse
Thanks for the reply if i did have the ability to desolder/resoldrer and program the emmc chip do you know what i should program it with? a compatible image? Or is it this that isn't available?
The exploit sounds even more promising do you know where i can find out more?
J_IO_B said:
Thanks for the reply if i did have the ability to desolder/resoldrer and program the emmc chip do you know what i should program it with? a compatible image? Or is it this that isn't available?
The exploit sounds even more promising do you know where i can find out more?
Click to expand...
Click to collapse
I pach a system.img with root now I'm just waiting for a script to flash it!( The scripts use python and I'm kinda new to programming python) I requested on a different thread for the script...
So I wouldn't go with the desolder the emmc route because then you have to warty about soldier balls, bridges, killing you emmc chip with heat, etc.
Sent from my VS986 using XDA Labs
ANDROID2468 said:
I pach a system.img with root now I'm just waiting for a script to flash it!( The scripts use python and I'm kinda new to programming python) I requested on a different thread for the script...
So I wouldn't go with the desolder the emmc route because then you have to warty about soldier balls, bridges, killing you emmc chip with heat, etc.
Sent from my VS986 using XDA Labs
Click to expand...
Click to collapse
How did you get on?
J_IO_B said:
How did you get on?
Click to expand...
Click to collapse
if you short one of the pads under the sheld to ground you will be able to boot to boot rom mode. that's when you will run the script to that will decrypt the keys so you can flash anything from there.
Bit late but its kinda impossible to change emmc chips.
If you get past soldering you could replace emmc chips with one from an old broken fire
and maybe it will work then
But who knows
we already have full root and bootloader unlock for most of the fire devices now
check the relevant sub for your model
LOS (soon)
ANDROID2468 said:
if you short one of the pads under the sheld to ground you will be able to boot to boot rom mode. that's when you will run the script to that will decrypt the keys so you can flash anything from there.
Click to expand...
Click to collapse
Sorry for the hijack here, but do this work on Fire HD 8 5th Gen model?
Thanks!
mugorj said:
Sorry for the hijack here, but do this work on Fire HD 8 5th Gen model?
Thanks!
Click to expand...
Click to collapse
Yes, technically it will but this method is harder to do.
here is a more in-depth guide on this. But I would not use this method, it's complex.
About the bootloader unlock:
The explicit to unlock the bootloader hasn't been ported to your device (if it has, I can't find it on XDA). It's because this model isn't that common. I will help Root you device using this method but I'm not skilled enough to Port the bootloader unlock.
ANDROID2468 said:
Yes, technically it will but this method is harder to do.
here is a more in-depth guide on this. But I would not use this method, it's complex.
About the bootloader unlock:
The explicit to unlock the bootloader hasn't been ported to your device (if it has, I can't find it on XDA). It's because this model isn't that common. I will help Root you device using this method but I'm not skilled enough to Port the bootloader unlock.
Click to expand...
Click to collapse
@ANDROID2468:
Thank you very much for your help!
If I can achieve root access, I believe I'll be 97% happy. I have just managed to have another launcher working on my device with Launcher Hijack (just discovered that Amazon implemented a childish blocking by the app name), and the thing is flying! I'm much happier! The device is perfectly usable now!
If I just can uninstall some Amazon crap and have my stuff going, I'll be happy, even if it's still running FireOS underneath.
I'll read the topic you mentioned carefully. If I still need help, I'll politelly ask you for guidance.
Thanks again!
mugorj said:
@ANDROID2468:
Thank you very much for your help!
If I can achieve root access, I believe I'll be 97% happy. I have just managed to have another launcher working on my device with Launcher Hijack (just discovered that Amazon implemented a childish blocking by the app name), and the thing is flying! I'm much happier! The device is perfectly usable now!
If I just can uninstall some Amazon crap and have my stuff going, I'll be happy, even if it's still running FireOS underneath.
I'll read the topic you mentioned carefully. If I still need help, I'll politelly ask you for guidance.
Thanks again!
Click to expand...
Click to collapse
ok, first I need to know what version of fire os you are running.
Then, I need a picture of your board. you need to open your tablet and you need to take off the shield. here is an example (you have the 5th gen so the shield should just pop off):
mugorj said:
@ANDROID2468:
Thank you very much for your help!
If I can achieve root access, I believe I'll be 97% happy. I have just managed to have another launcher working on my device with Launcher Hijack (just discovered that Amazon implemented a childish blocking by the app name), and the thing is flying! I'm much happier! The device is perfectly usable now!
If I just can uninstall some Amazon crap and have my stuff going, I'll be happy, even if it's still running FireOS underneath.
I'll read the topic you mentioned carefully. If I still need help, I'll politelly ask you for guidance.
Thanks again!
Click to expand...
Click to collapse
sorry, I didn't read your message carefully. the post that I posted previously was about porting a root method used by the fire 7 (7th gen) which was used before the bootloader unlock was released(well the 5th gen was released at the time but not 7th gen ). that method is a lot easier to do and less likely to kill your device.
Do you have a link for the root method please?
laharl_22 said:
Do you have a link for the root method please?
Click to expand...
Click to collapse
do you have a hd8 5th gen? or something else?

Root on 2019 devices

Has anyone got Root on the 2019 models yet?
Take a look at post 2 in the Developer image thread. There are instructions mentioning a beta TWRP and Magisk. Seems like a rooting solution to me. I've never tried this myself but that thread seems like it would be a good start for you.
Root pro 2019 - good.
Is root break dolby vision or other fonctionality or magisk is undetcted ?
I can't install Fastboot drivers on Windows 10. Please HELP
3DSammy said:
Take a look at post 2 in the Developer image thread. There are instructions mentioning a beta TWRP and Magisk. Seems like a rooting solution to me. I've never tried this myself but that thread seems like it would be a good start for you.
Click to expand...
Click to collapse
There saying not to root yet in that post unless you know exactly what your doing. I've never rooted before. Are there no other options?
pensburgh said:
There saying not to root yet in that post unless you know exactly what your doing. I've never rooted before. Are there no other options?
Click to expand...
Click to collapse
If you haven't rooted say Android phones before, I'd follow the advise of others. Especially when the root methods are beta in nature and not tried and tested by those with experience. Personally while curious, I'm already on the Nvidia hotfix images and the device works very well for me. I can't see the need as of yet. With that being said all my other Android devices are rooted and hacked to some degree or other.
It's recommended not rooting you lose AI Upscaling feature unless your not bothered about it also you lose it if bootloader is unlocked or tampered with
Sent from my GM1920 using Tapatalk
hi, I have successfully rooted the Shield Pro 2019.
Unfortunately big problems: both 8.0.1 and 8.1.1 aren't stable. To a degree where it's not usable.
All of a sudden I get black screens. Netflix videos won't start, even the YouTube app sometimes won't start up.
Are you guys actually able to use the Shield rooted, or what am I missing?
Daniel_Robson said:
It's recommended not rooting you lose AI Upscaling feature ...
Click to expand...
Click to collapse
I was just checking in and loosing that feature kills it for me. When I bought the device I assumed AI Upscaling was just marketing hype but used it the middle setting definitely adds a 4K likeness to a 1080p image on my 4K projector. I also like that the frame-rate restriction of [email protected] or lower is a non-issue as that is source specific. All streaming sources I play (Netflix, Prime, Disney+, Crave and YouTube) are [email protected] or lower so I'm always having AI Upscaling kick in. Originally I was using frame-rate matching as I thought that was the only way to meet the AI Upscaling criteria but I was mistaken.
Yeah I've done rooting in the past, so I'd be game to try it, but not if it's unstable.
Rey3000 said:
I can't install Fastboot drivers on Windows 10. Please HELP
Click to expand...
Click to collapse
Disable Driver Signature enforcement on Windows 10:
https://www.simple-shop.si/en/disable-enable-driver-signature-enforcement-on-windows-10
Does somebody have a dump of system partition of shield/pro 2019?

Onn 7" Gen 2 (100026191) dumping and development

I have recently rooted my Onn 7, and extracted the boot and recovery images.
(I accidentally deleted the boot image, but I still have one patched with Magisk, and the recovery image is still present.)
I want to get the entire system dumped, including the original system and boot partitions, which would require some help from other tablet owners (I'm broke right now).
I can walk you through the entire process of rooting the system, I just need willing participants.
(I could also use some help porting TWRP, since I have no idea how that works anymore.)
Hi, just got my hands on this device. I'd appreciate it if you can help me get my device rooted. I'm looking to remove some apps that came along with it. Thanks
strggdrive said:
Hi, just got my hands on this device. I'd appreciate it if you can help me get my device rooted. I'm looking to remove some apps that came along with it. Thanks
Click to expand...
Click to collapse
Do you want to do Magisk method or GSI method?
PseudoDistant said:
Do you want to do Magisk method or GSI method?
Click to expand...
Click to collapse
I'm not sure really, whichever is easier I think.
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
discord.gg
Actually just join here, I'll help you live.
strggdrive said:
I'm not sure really, whichever is easier I think.
Click to expand...
Click to collapse
Magisk, definitely.
PseudoDistant said:
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
discord.gg
Actually just join here, I'll help you live.
Click to expand...
Click to collapse
Hey I just got my hands on a 100026191 are you still looking for help? I have this 7in and an 8in 3rd gen that I'm working on currenty. Thanks!
dilo34 said:
Hey I just got my hands on a 100026191 are you still looking for help? I have this 7in and an 8in 3rd gen that I'm working on currenty. Thanks!
Click to expand...
Click to collapse
Yea, both are doable.
PseudoDistant said:
Yea, both are doable.
Click to expand...
Click to collapse
Can you give me information on how to root via the Magisk method please ?
LiftedByNature said:
Can you give me information on how to root via the Magisk method please ?
Click to expand...
Click to collapse
You need to dump your `boot.bin`, either from an OTA update, or from a temprooted system.
Hello, I have an Onn 7, Gen 3 that I just picked up. I found the files you posted in the other forum but am not sure how to build a TWRP based off of those. Help please
Im also looking for a root method for the Onn Surf 7 gen 2. I get that i need to use usb debugging to log the url for the ota update, however my unit came with android 11 go and says up to date when i check for updates after a factory reset. can you tell me what I've done wrong? also what program are you using to run adb logcat from PC?

Categories

Resources