Hi there. Longtime XDAer (back to the OG Moto Droid) but new account. I am a OnePlus devotee that has converted to Pixel 6. I have used Qualcomm's EDL mode with the MsmDownloadTool in the past, is there an equivalent for the Tensor chip? I have no current need for it, but I like to have the appropriate tools ready for future issues, especially in light of the dumb Android 13 bootloader rollback issue some people seem to have.
FWIW, before posting I searched for EDL but that did not return anything. And the PixelFlasher appears to just be a adb/fastboot GUI, is that correct?
There's none afaik, and yes, PixelFlasher is just an GUI for easier operation
Can someone please tell me what EDL is
taanh1412 said:
There's none afaik, and yes, PixelFlasher is just an GUI for easier operation
Click to expand...
Click to collapse
Thank you for your reply! Bummer, I hope someone updates the forum if/when it gets released. As of right now, there'd be no way to fix a real brick if we don't have a EDL type of mode other than sending back to Google. Maybe one of their engineers could leak a version of it someday
bush911 said:
Can someone please tell me what EDL is
Click to expand...
Click to collapse
A very small embedded OS on Qualcomm chips, think of it kind of like a motherboard controller. Very handy when you have completely FUBAR'd the storage OS or bootloader, essentially bricking the device. EDL allows you to gain very low level SoC access to reflash stock images, thus unbricking. It has no printed screen, it just stays black. You have to use a PC tool to flash
centifanto said:
A very small embedded OS on Qualcomm chips, think of it kind of like a motherboard controller. Very handy when you have completely FUBAR'd the storage OS or bootloader, essentially bricking the device. EDL allows you to gain very low level SoC access to reflash stock images, thus unbricking. It has no printed screen, it just stays black. You have to use a PC tool to flash
Click to expand...
Click to collapse
And since Tensor is a modified Exynos (Samsung) processor there almost certainly is no EDL mode. How Google restores bricked units is anyone's guess, but Samsung does have a dedicated download mode that, combined with Odin / Heimdall on a PC / Mac, allows for flashing of stock images.
EDL is Emergency DownLoad mode on Qualcomm processors.
There's a ROM in Qualcomm processors that is always present and is the first step to booting.
In normal operation it will load the SBL/XBL (secondary bootloader) which will load the aboot (Android application bootloader).
If something goes wrong in booting (or if you configure it by test points or boot config) it can load a diagnostic program which is basically a replacement for the SBL/XBL.
That program (which in Qualcomm parlance is called a "loader") allows you to read/write partitions and even memory.
The difficulty comes that a lot of this is securely signed so there can be problems finding a loader that works.
Other brands have ROMs built in which do the same thing but are all incompatible with each other.
MediaTek has MTK mode, Allwinner has FEL mode...
Note: By "ROM" I mean truly read-only memory built into the processor chip itself.
(I think the casual usage of "ROM" to mean an OS loaded onto R/W flash is misleading.)
Strephon Alkhalikoi said:
And since Tensor is a modified Exynos (Samsung) processor there almost certainly is no EDL mode. How Google restores bricked units is anyone's guess, but Samsung does have a dedicated download mode that, combined with Odin / Heimdall on a PC / Mac, allows for flashing of stock images.
Click to expand...
Click to collapse
Interesting. The only Samsung I have messed with was the old Galaxy S5 that luckily had a bootloader exploit. Was a PIA to root though and after that I swore I'd never buy their junk. Nowadays they are impossible unlock and modify, as Exynos versions don't fully work in the US so you have to buy their Snapdragon variants which are locked down like crazy.
Maybe Google will release the download mode procedures and tooling
Renate said:
EDL is Emergency DownLoad mode on Qualcomm processors.
There's a ROM in Qualcomm processors that is always present and is the first step to booting.
In normal operation it will load the SBL/XBL (secondary bootloader) which will load the aboot (Android application bootloader).
If something goes wrong in booting (or if you configure it by test points or boot config) it can load a diagnostic program which is basically a replacement for the SBL/XBL.
That program (which in Qualcomm parlance is called a "loader") allows you to read/write partitions and even memory.
The difficulty comes that a lot of this is securely signed so there can be problems finding a loader that works.
Other brands have ROMs built in which do the same thing but are all incompatible with each other.
MediaTek has MTK mode, Allwinner has FEL mode...
Note: By "ROM" I mean truly read-only memory built into the processor chip itself.
(I think the casual usage of "ROM" to mean an OS loaded onto R/W flash is misleading.)
Click to expand...
Click to collapse
Wow, this is an amazing reply! Thank you! So much detailed and insightful information I didn't know. This is what makes the XDA forums amazing.
And yes, I have always been confused why the word ROM become the standard for the OS installed on Android phones, precisely for the reason you pointed out. Android ROMs are anything but read only
centifanto said:
Interesting. The only Samsung I have messed with was the old Galaxy S5 that luckily had a bootloader exploit. Was a PIA to root though and after that I swore I'd never buy their junk. Nowadays they are impossible unlock and modify, as Exynos versions don't fully work in the US so you have to buy their Snapdragon variants which are locked down like crazy.
Maybe Google will release the download mode procedures and tooling
Click to expand...
Click to collapse
Yeah, Google won't do that. As for Samsung, the Galaxy S4 I own did have a locked bootloader until I used Chainfire's RegionLock Away to permanently unlock the bootloader. The root process for that device was relatively painless, requiring Odin and - at the time - a specialized recovery payload that would root the device as there was no TWRP.
Well for one y'all are missing the fact that since the chip has an exposed serial unit, we can do some reverse engineering on the bootrom and find jump points to certain addresses in memory. Such as the recovery mode. Google host the gs101 and oriel kernel repositories in its open source git repositories. I've found a tone of useful information in there. Ghirda is a good program for reverse engineering.
EDL for Exynos uses Exynos Dead Boot Mode. After changing the USB mode and using dwusb3 drivers we should have enough range to write/send bytes to chipset
NonStickAtom785 said:
Well for one y'all are missing the fact that since the chip has an exposed serial unit, we can do some reverse engineering on the bootrom and find jump points to certain addresses in memory. Such as the recovery mode. Google host the gs101 and oriel kernel repositories in its open source git repositories. I've found a tone of useful information in there. Ghirda is a good program for reverse engineering.
EDL for Exynos uses Exynos Dead Boot Mode. After changing the USB mode and using dwusb3 drivers we should have enough range to write/send bytes to chipset
Click to expand...
Click to collapse
Wow, this is amazing info! Thanks for sharing, I had no idea about this boot mode. I found these comments in this link:
USB download mode is only accessible if first boot method has failed...Once the first boot method fails, USB download mode can be accessed by pressing and holding power button.
This link also looks interesting.
All of this sounds like only someone with advanced knowledge would be able to figure it out, and with the high risk of truly bricking their device.
Related
Hello,
A friend of friend of mine unlocked bootloader on his G5, then some magical stuff probably happened, because secure boot got stuck on boot verification failrue with probably most common issue, signature length mismatch. We're trying to get it to work now, but we can't seem to find a solution to it. Fastboot doesn't work, because secure boot gets tripped in every bootmode. Does anybody have an idea which pins to short out on motherboard for boarddiag operation or something? I'd really appreciate that.
Download Mode should still work.. even with the secure boot tripped msg.. as long as they didn't mess with the download mode partition on purpose before this all happened.
The unique programmers required for the G5 for BoardDiag to work are not public so forcing your way into 9008 won't get you anywhere.
He isn't able to fire up download mode either. He says that it prints different_hash error there. I'd probably have to take another one of the same model(H850, I believe) and mirror kernel and bootloader from it, but I don't have eMMC programmer, nor physical access to that phone.
[/COLOR]
autoprime said:
Download Mode should still work.. even with the secure boot tripped msg.. as long as they didn't mess with the download mode partition on purpose before this all happened.
The unique programmers required for the G5 for BoardDiag to work are not public so forcing your way into 9008 won't get you anywhere.
Click to expand...
Click to collapse
Keij0 said:
He isn't able to fire up download mode either. He says that it prints different_hash error there. I'd probably have to take another one of the same model(H850, I believe) and mirror kernel and bootloader from it, but I don't have eMMC programmer, nor physical access to that phone.
Click to expand...
Click to collapse
Keij0 said:
He isn't able to fire up download mode either. He says that it prints different_hash error there. I'd probably have to take another one of the same model(H850, I believe) and mirror kernel and bootloader from it, but I don't have eMMC programmer, nor physical access to that phone.
Click to expand...
Click to collapse
bumping old thread, i know. Did we ever establish either board diag files for g5 or any solution to No download mode issue with it reporting Different Hash when attempting to enter it? My phone boots fine but no DL mode......backstory: I have a RS988 that i attempted to repair for a friend after they locked it with frp, i removed the frp, via creating a apparently incorrectly modified firmware via my z3x's firmware maker feature(it copies the partitions available on the device into a new firmware file). it doesn't have rs988 listed as a model available to edit so(like normally works with devices, i used vs986(or whatever verizon's variation was, i know rookie mistake) but I believe i have screwed up because since writing the modified firmware i can get into the OS fine but can not enter DL mode again without the "Different Hash" issue. I believe shortwire plus board diag fix could be resolution but could use some feed back . @autoprime Anything i can do to rewrite those partitions manually with the RS988 variant's original kdz and any type of serial connection/jtag/virtual com ports/tty/AT+/linux computer, lol anything? I'm pretty much equipped for anything except jtag but even that can be arranged lol
I have a chinese TVpad2 mini-pc running on custom linux (factory OS) with busybox.
I want to install Android or anything other than the factory OS but there's a lot of problems with this device:
-Filesystem is CRAMFS
-Can only access as root through telnet
-Can't access bootloader or put into FWDN (no info how this is done for this device)
What I have:
-Firmware update that contains the kernel
-Telnet root access
-Physical access to device (USB flashdrive only)
There is a forum dedicated to TVpad but they are also having trouble installing an OS on tvpad2...
What do I need to know that will help me accomplish this?
thanks
TVpad3
Hi,
I actually have TVpad3 which is very similar to your TVpad2, and Im very keen on having Android developed for these TVpads.
Theres probably thousands of these wasted devices around the world after the TVpad pirate network got shutdown.
Ive searched high and low, and so far have Not found any trace of any custom Android development anywhere.
So hopefully we can kick start something here !
This is what I know so far ....
Since the devices run on highly stripped-down Android OS, we know these devices can run android and should be a potential for custom Android development.
Unfortunately theres little hardware or development info out there for these devices.
But as far as I know, the hardware platform for these models are all based on Telechip TCC89xx chips.
https://www.telechips.com/eng/Product/consumer_pro13.asp
I have a TVpad3 personally, which I believe is based on a Telechips TCC8925.
Ive found that there are a few similar devices out there based on this platform, including the Pandawill CX-01 TV sticks which have very similar specs to TVpad3 (512mb RAM, 4gb Flash).
So we definitely know that the TVpad's hardware is capable of running full blown Android !
http://www.cnx-software.com/2012/06...v-box-powered-by-telechips-tcc8923-cortex-a5/
http://www.slatedroid.com/topic/36988-cx-01-cortex-a5/
Telechips has released platform sources here, with the latest being Android KitKat... its a bit old but could have potential for a starting point...
https://www.telechips.com/technical_support/kor/opensource/opensource_list.asp
I havent found anything about booting these devices into Recovery or ADB.
But there seems to be some mention of a "FWDN" mode here:
http://freaktab.com/forum/tv-player-support/other-tv-players/4695-cx-01-information-by-tatubias
http://tvpadtalk.ca/discussion/506/how-to-unbrick-your-tvpad1
http://androtab.info/arm/telechips/how-to-update/
http://auswitch.xyz/2012/08/16/how-to-upgrade-firmware-for-cx-01-mini-pc/
From what I can gather, FWDN works in conjunction with a Windows-based utility used to flash firmware over a USB cable.
And this poses the biggest problem for TVpads, they DONT have any peripheral USB port !
I've pulled my TVpad3 apart, and found what appears to be provision for a USB header, but im not sure if these are functional even if a USB socket was soldered in ?
If we can get a functional USB peripheral port working, then that would lead us to the Second problem, that is, HOW to activate FWDN mode on the TVpad ?
From what I can gather, different Telechip TCC89xx based devices seem to have different ways to enter FWDN mode.
Some devices require a certain key combo to be pressed during power up, while others need a hidden button pressed or certain pins on the circuit board to be shorted.
So before we can even think about developing Android, we need to figure out those two issues...
1 - USB connectivity, so that we can flash it with FWDN tool.
2 - How to enter FWDN mode, so that the FWDN tool can talk to the TVpad.
If we can overcome these two issues, then we can start building sources.
Or even flash ROMs from similar Telechip TCC89xx based devices.
Anyway, I hope this helps anyone out there.
And I hope we can really make some progress here
.
Unfortunately I've hard-bricked my TVpad2 playing around with fdisk command in telnet. I found out that if you repartition and then copied all the data back, changes will be persistent so you can store whatever onto the NAND flash. Just don't delete the partition containing linux which I idiotically did... oh well.
Anyway there's a command utility "tccbox" with various tools one of them having the ability to update firmware. Hopefully TVpad3 has it as well?
Sorry to hear you bricked your TVpad !
I guess your only way back is to FWDN flash it.
I wasnt even aware the TVpads had telnet enabled.
But that "tccbox" utility sounds very interesting.
I wonder if we can use it to flash firmwares from other TeleChips based devices ???
.... such as the Pandawill CX-01 TV sticks.
wildchill said:
Sorry to hear you bricked your TVpad !
I guess your only way back is to FWDN flash it.
I wasnt even aware the TVpads had telnet enabled.
But that "tccbox" utility sounds very interesting.
I wonder if we can use it to flash firmwares from other TeleChips based devices ???
.... such as the Pandawill CX-01 TV sticks.
Click to expand...
Click to collapse
Hi i have found my old TVpad3 but no working now, i want flash it for use to android device, you have any tutorial for this PLS
TY
These tablets were sold with certain Vizio TVs in mid-2016 into 2017, primarily used for Smartcast to the TV.
They are now obsolete since Vizio released firmware for their TVs turning them into normal Smart TVs, requiring the owners of these TVs to get new remotes and the tablets stopped being useful for this function.
Here in 2019, one can buy these tablets, at the low price end, in working condition, for $25 (for the M series) to $40 (for the P series) shipped.
The specs are as follows:
XR6M10:
Snapdragon 410 1.2GHz quadcore APQ8016
2GB RAM
8GB Storage
1280x720 IPS display
802.11n, Bluetooth 4.0
2740mAh battery
MicroUSB for charging, Qi Charging built-in for bundled charge pad or any compatible charging solution
XR6P10:
Snapdragon 615 1.45GHz octocore APQ8039
2GB RAM
16GB Storage
1920x1080 IPS display
802.11n, Bluetooth 4.0
2740mAh battery
MicroUSB for charging, Qi Charging built-in for bundled charge pad or any compatible charging solution
Both tablets feature side-firing stereo speakers, a headphone jack, and NO cameras. The size of the tablet is comparable to the size of a Galaxy Note 9, give or take.
Both tablets came with Android 5.1.1, and OTA updates upgraded them to 6.0.1. There are ZERO available stock ROM files available for the tablets. I've tried sniffing the updater and they seem to go to a dead website.
The stock ROM is fairly clean, and only has the Vizio Smartcast app which needs disabling upon setting up. Aside from this, there is no other bloatware on the tablet to speak of after running a fine-tooth comb through the system apps. You get a clean and snappy tablet.
The problem:
There's no stock ROM file available, neither for Android 5.1.1 or for 6.0.1. Vizio does not have any sort of download for either on their site, nor did in the past. The updater checked a third-party website affiliated with Vizio to manage the tablet's updates, as it does with their TVs. Since the website is inert, it can be safely said that Vizio is no longer interested in their existence at all, especially since the warranty on every single one of these tablets is now up.
The tablet seems it can have the bootloader unlocked, the developer options has the toggle for that, but there's no way to get into fastboot. Holding VOL UP+DOWN+POWER at boot or sending the "adb reboot bootloader" command sends it into a "Qualcomm HS-USB QDLoader 9008" mode under USB. This, from what I understand, is behavior persistent with the locked bootloader, but I have no idea of how to get it out of this and just into fastboot. Stock recovery does not have a fastboot option either.
The desires list:
Have someone that knows the intricacies of the MSM8916 platform and the APQ8016/APQ8039 get their hands on these tablets
Get a ROM dump of both tablets in stock form so people with bricked tablets can flash them with it
Get Root (Patch level on the 6.0.1 stock ROM is from October 2016, shouldn't be hard)
Get the bootloader unlocked, somehow, and if not, figure a way to get something like Safestrap running on it if the out-of-the-box kernel allows for it
Custom ROMs? LineageOS would be sweet, especially with some of the tablet-specific fixes that have dropped in the past couple months overall.
so I ask: is there any interest in the freeing of these super cheap tablets? The price to spec ratio is not bad (once again, I got my 6M10 for $25 shipped, and the seller has like 7 more as of the time of this writing), and it doesn't seem like it would be all too hard to unlock the bootloader and get it rooted (at least, from my perspective, that of a novice in this specific hardware field). There are plenty of these in the wild in the hands of people that bought the TVs and plenty in the hands that bought them from ebay when the tablets became obsolete.
This link contains screenshots of CPU-Z and the About Tablet settings section from the tablet, uploaded to imgur. If anyone needs more information on this tablet that needs an app or adb command, I can make this happen.
Board Pic of the XR6M10, XR6P10 should be the same inside:
(click for larger image)
Update: I have temp root.
I have temp root!-the latest kingroot (NOT Kingoroot) APK seemed to have done the trick. I was able to fire up adaway and get the hosts file set up with adblocks to keep the thing safer.
The root is still temporary so it goes away after a reboot. The rooting process involves it doing the root process once, then rebooting, then failing, then you reboot once more, and then retry rooting from the app. From here, 80% of the time, it works and you're able to get temporary root for that boot session.
Once you're done with anything you need root for, you should reboot and then uninstall Kingroot, which you then need to deactivate the device administrator priveleges for, before it will allow you to cleanly uninstall it.
I also made a huge discovery that may turn out better for anyone that can help getting this thing properly rooted and the bootloader unlocked... it seems the file manager included in the stock ROM is v3.0.0 from Cyanogenmod 12.1.
This makes me think that the ROM creator either used that since it was opensource and readily available than come up with their own solution, or that this ROM has some cyanogenmod roots.
I also found this post from another Q&A thread in this section:
TheDrive said:
This device have made by Chinese/Indian company Borqs. The code name Bennu-M. Platform is Qualcomm APQ8016 (MSM8916 w/o modem). There should work standard method to bring EDL mode. Hold Vol+ and Vol- at power on (press power). Then connect to the PC. Thus device will stay look dead, however should be detected as Qualcomm QDLoader 9008 on the PC side. This is the factory described method.
You can flash factory firmware from this mode using external bootloader (programmer) for MSM8916 firehose protocol. This procedure is described in the thousands of manuals around the net. Qualcomm tools like QPST or QFIL can be used as good as many 3rd party utils to flash and manage any another available way. Many professional 'box' tools should support this device too but only as 'generic' msm8916 (if applicable).
However I can't find the firmware package for this device anywhere. You should ask and require the manufacturer/distributor to publish firmware, the source code and all the corresponding matherials to be able to flash and rebuild firmware from sources in any manner you want without any limitations as required by GNU/GPL free open source software licenses this firmware is obligated to.
Everyone who have the device working or software dead, can try to dump the current firmware and data, stored on the internal eMMC memory module in part(s) or in whole image using free QTools project utilities and suitable external bootloader with ability to dump eMMC, not only to flash as many factory supplied programmers do. There are programmer(s) for MSM8916 available in the project repo. Read and understand manuals carefully before trying anything!
There is definitely another ways to root, dump, flash, manage the device in any manner YOU WANT, not only the way you are "allowed" to use your own device by manufacturer/distributor. FTA!
You can root the device then dump all the multiple partition images manually (dd if=/dev/block/mmbblk0...... of=/sdcard/......) or using built custom recovery like CWM/TWRP for your device. Please note, kernel sources are important but not mandatory to build e.g. CWM. You can build one using CWM image from the similar device and the kernel (boot/recovery) image binaries from your device. There are good manuals and image repacking utils available around like e.g. AndImgTool.
There are the way to produce factory image from the eMMC/partitions dump(s). Use utils like R-Studio to dump particular partition images from the eMMC dump (it's like whole HDD or UFD image with all the sectors raw, one by one, w/o any modifications/compression/etc) Manuals / utils are avavailable to make e.g. sparse and xml scripts set which is flashable by the programmer in the EDL mode (i.e. from any damaged state, because EDL is built in to the PBL and masked to the internal CPU ROM, thus can not be damaged in any manner, except firing the CPU up).
You can also flash partition images from the more common Fastboot mode, unless eMMC GPT and bootloaders (SBL/RPM/TZ/ABoot) stay intact (logo showed). You can't dump from fastboot, which is common due to the (foolish) 'safety' requirements. It's security by obscurity and is definitely not for your favor, but for the corps control over you and force to send valuable private data to foreign clouds.
Please share eMMC full and/or partitions dumps using reliable 'neverending' file cloud/hosting since there is no factory firmware available yet (ever). I do not own this device and never seen being overseas, so I can't share.
Click to expand...
Click to collapse
This gives a little bit more information but seems to be more waffle than helpful. Still need someone, or some individuals, that can get one of these devices into their hands and work on a way to get the bootloader unlocked, the eMMC dumped, and ROMs going.
Update file?
I THINK I have the update file for 6.0.1. I did a packet sniff on a 5.1.1 tablet using a mitm packet sniffer and I ran the system updater, and was able to get this URL:
http://updatev.vo.llnwd.net/v1/idownload/64821.bin
The filesize is 570MB or so, and it looks like it might be the real deal. since it's a .bin file and 7zip can't read it, I won't be able to see what it really is without going over to the box that has a copy of universal extractor installed.
I'll be doing this momentarily and editing this post once I figure out what the contents are or if it's even readable to that extent. Knowing vizio, it could very well be encrypted and need decrypting by the updater application.
Update: it seems to be encrypted. oh joy.
Update 2: I got together with a friend on discord and we successfully decompiled the updater app to a point.
This MEGA link contains all the files thus far and a copy of the tablet's /system/framework folder for decompiling purposes.
However, it doesn't seem we're getting anywhere. the file is still encrypted and I still can't figure out what's needed to decrypt it. Hopefully someone with more knowledge on this can lend a hand.
Sudosftw said:
I THINK I have the update file for 6.0.1. I did a packet sniff on a 5.1.1 tablet using a mitm packet sniffer and I ran the system updater, and was able to get this URL:
http://updatev.vo.llnwd.net/v1/idownload/64821.bin
The filesize is 570MB or so, and it looks like it might be the real deal. since it's a .bin file and 7zip can't read it, I won't be able to see what it really is without going over to the box that has a copy of universal extractor installed.
I'll be doing this momentarily and editing this post once I figure out what the contents are or if it's even readable to that extent. Knowing vizio, it could very well be encrypted and need decrypting by the updater application.
Update: it seems to be encrypted. oh joy.
Update 2: I got together with a friend on discord and we successfully decompiled the updater app to a point.
This MEGA link contains all the files thus far and a copy of the tablet's /system/framework folder for decompiling purposes.
However, it doesn't seem we're getting anywhere. the file is still encrypted and I still can't figure out what's needed to decrypt it. Hopefully someone with more knowledge on this can lend a hand.
Click to expand...
Click to collapse
Just out of curiosity, with the temp root, have you tried using dd to get the recovery image off? If we can do that, we might be able to work on getting a custom recovery built.
Qiangong2 said:
Just out of curiosity, with the temp root, have you tried using dd to get the recovery image off? If we can do that, we might be able to work on getting a custom recovery built.
Click to expand...
Click to collapse
It's not possible to get a proper recovery image from within the system files so far as I know, but my take so far has been that there is no proper way to get that at this time without decrypting that file grabbed from the update server. I'd do it on a 5.x ROM since that will get me permaroot, but the issue is getting and keeping root on a 6.x ROM.
Although encrypted (so far as I can tell) the image linked above is the real deal, and I've given all I can to get it decrypted. A proper exploit to take care of this tablet's vulnerabilities and get temp root (on 6.x) that isn't kingo is what is really needed at this point so to not hinder going around the system with crudware and shady background apps, shouldn't be hard since the security patch level for the 6.x ROM is 2016-10-01.
Even if the ROM is extracted or a recovery image found, custom recovery won't be possible until the bootloader is unlocked, and this isn't doable until someone figures out how the qualcomm qdloader9008 stuff works with this specific tablet. Fastboot is unreachable and I'm almost sure I'm doing something wrong.
I'll get temp root and see about dd'ing stuff later on. What exactly would be needed for me to dd off? Whole disk and then go through it elsewhere? I could definitely see if rsync exists and dd over rsync to another box.
Sudosftw said:
It's not possible to get a proper recovery image from within the system files so far as I know, but my take so far has been that there is no proper way to get that at this time without decrypting that file grabbed from the update server. I'd do it on a 5.x ROM since that will get me permaroot, but the issue is getting and keeping root on a 6.x ROM.
Although encrypted (so far as I can tell) the image linked above is the real deal, and I've given all I can to get it decrypted. A proper exploit to take care of this tablet's vulnerabilities and get temp root (on 6.x) that isn't kingo is what is really needed at this point so to not hinder going around the system with crudware and shady background apps, shouldn't be hard since the security patch level for the 6.x ROM is 2016-10-01.
Even if the ROM is extracted or a recovery image found, custom recovery won't be possible until the bootloader is unlocked, and this isn't doable until someone figures out how the qualcomm qdloader9008 stuff works with this specific tablet. Fastboot is unreachable and I'm almost sure I'm doing something wrong.
I'll get temp root and see about dd'ing stuff later on. What exactly would be needed for me to dd off? Whole disk and then go through it elsewhere? I could definitely see if rsync exists and dd over rsync to another box.
Click to expand...
Click to collapse
I found this today: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
The miflash tool seems promising (it works with nearly any device)
For the dd stuff, you can usually figure out the partitions easily with the fstab file in /. However, getting a raw dump is always useful.
Really, the big 3 would be the recovery.img, the boot.img, and the system.img. We can work from there
Qiangong2 said:
I found this today: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
The miflash tool seems promising (it works with nearly any device)
For the dd stuff, you can usually figure out the partitions easily with the fstab file in /. However, getting a raw dump is always useful.
Really, the big 3 would be the recovery.img, the boot.img, and the system.img. We can work from there
Click to expand...
Click to collapse
I've had that installed whilst trying to figure the image out and the qdloader stuff, it doesn't do anything for this tablet sadly :/
Sudosftw said:
I've had that installed whilst trying to figure the image out and the qdloader stuff, it doesn't do anything for this tablet sadly :/
Click to expand...
Click to collapse
Hmmm. Which tablet do you have? The M or the P?
Qiangong2 said:
Hmmm. Which tablet do you have? The M or the P?
Click to expand...
Click to collapse
this is the M. the P was out of my price range ($40 shipped over $25 shipped) when I was looking at them, but now the Ms are going for around 25 bucks but 15 shipping from another seller, bringing the price up to 40 bucks where the P was. ended up buying the other Ms from the one seller and gave them out to family members because I was so impressed... but I really should have set some money aside for one of the Ps as well and didn't.
Sudosftw said:
this is the M. the P was out of my price range ($40 shipped over $25 shipped) when I was looking at them, but now the Ms are going for around 25 bucks but 15 shipping from another seller, bringing the price up to 40 bucks where the P was. ended up buying the other Ms from the one seller and gave them out to family members because I was so impressed... but I really should have set some money aside for one of the Ps as well and didn't.
Click to expand...
Click to collapse
Okay. You said miflash doesn't do anything, does the device show up in the application and not function? Or does it not show up at all?
Qiangong2 said:
Okay. You said miflash doesn't do anything, does the device show up in the application and not function? Or does it not show up at all?
Click to expand...
Click to collapse
just doesn't show up at all. and yet installing the qualcomm qdloader drivers says it's connected in device manager, so something's up. tried on two different boxes, different cables, no dice.
Sudosftw said:
just doesn't show up at all. and yet installing the qualcomm qdloader drivers says it's connected in device manager, so something's up. tried on two different boxes, different cables, no dice.
Click to expand...
Click to collapse
Hmmm. That's unusual. Are you running it in win 7 compatibility mode?
It would be nice to see community roms for these devices. I have the XR6P. If you need any info from this device, just tell me what to do.
I'm very interested in this as I have one of these tablets that I would like to use in my vehicle as a display for my piggyback ECU tuner. It doesn't currently support USB OTG, but I read that if I can gain root access I can add the file to give it USB Host functionality. Can anyone confirm this? I have tried several apps to get it rooted including Kingroot as you were able to get a temp root with that. Unfortunately Kingroot, as all the others I have tried, won't even install on the tablet. Again, I'm only looking to get this thing to be OTG capable. If anyone here has any suggestions, I would be very grateful! Thanks all!
I just bought an M remote to replace my broken P remote. My P remote had Android 6. My M remote has Android 5, and the OTA updater says there's no update. Any way to get Android 6 on this?
I have factory firmware for Bennu P and Bennu M , but take some time to upload the file.
ALANCHONG said:
I have factory firmware for Bennu P and Bennu M , but take some time to upload the file.
Click to expand...
Click to collapse
Hey. You can lay out the firmware for XR6M10
XR6M10 and XR6P10 firmware
konog said:
Hey. You can lay out the firmware for XR6M10
Click to expand...
Click to collapse
Mega Link: mega.nz/#F!n65kVYIT!PKH8A1WoD_Nc4DU_-9dbiQ
ALANCHONG said:
Mega Link: mega.nz/#F!n65kVYIT!PKH8A1WoD_Nc4DU_-9dbiQ
Click to expand...
Click to collapse
All the time, an error pops up at 12 seconds
Flash fail (-4002)
Log:
21:59:03.576 Arrival: \\?\USB#VID_05C6&PID_9008#5&13a74b18&0&11#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
21:59:03.591 Thread '_PortDownloadThread' started
21:59:04.610 Get Port ...
21:59:04.610 _GetDevicePortName (0): COM5
21:59:04.630 _ComPort: COM5
21:59:04.640 Get Port (0)
21:59:04.650 Flash ...
21:59:09.668 _Connect (0)
21:59:09.668 Downloading flash programmer: C:\_qcMUP\v8016-SIGNED-VIZIO-user-IMAGES\v8016-SIGNED-VIZIO-user-IMAGES\prog_emmc_firehose_8916.mbn
21:59:14.669 Failed to read the command from the opened port
21:59:14.669 _FlashProgrammer (-4002)
21:59:15.700 Flash (-4002)
21:59:15.700 Flash fail (-4002)
21:59:15.731 Download ended: -4002
21:59:15.763 Thread '_PortDownloadThread' ended
konog said:
All the time, an error pops up at 12 seconds
Flash fail (-4002)
Log:
21:59:03.576 Arrival: \\?\USB#VID_05C6&PID_9008#5&13a74b18&0&11#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
21:59:03.591 Thread '_PortDownloadThread' started
21:59:04.610 Get Port ...
21:59:04.610 _GetDevicePortName (0): COM5
21:59:04.630 _ComPort: COM5
21:59:04.640 Get Port (0)
21:59:04.650 Flash ...
21:59:09.668 _Connect (0)
21:59:09.668 Downloading flash programmer: C:\_qcMUP\v8016-SIGNED-VIZIO-user-IMAGES\v8016-SIGNED-VIZIO-user-IMAGES\prog_emmc_firehose_8916.mbn
21:59:14.669 Failed to read the command from the opened port
21:59:14.669 _FlashProgrammer (-4002)
21:59:15.700 Flash (-4002)
21:59:15.700 Flash fail (-4002)
21:59:15.731 Download ended: -4002
21:59:15.763 Thread '_PortDownloadThread' ended
Click to expand...
Click to collapse
Please check if the driver is installed
Hi
I just got a third LMX210 today to add to my collection. Lol really im just trying to solve a problem. I bought a ulma to replace cm and i came across a ulm model and decided to just replace my cm today. The problem is that all three of these phone which normally have easily unlockable bootloaders will not boot into fastboot. The fortune 2 will not even boot into recovery. They all will boot into a blank screen with the android robot and will boot into download mode.
The natural solution would be to install an older or even plain stock firmware. But say you dont have a windows 10 or Mac computer. I havent found a way to flash lg firmware using a linux distribution yet.
On the other phones i tried removing the laff partition to force the phone into fastboot by plugging into pc while holding the volume up button. This did nothing but repeat the logo until the button released.
Yes usb debugging was enabled and adb was used to try these procedures. The drones at lg know nothing and ask to send the phones in for repair.
Short of re-installing the stock firmware there has to be way to get past this. And to tell you the truth i dont have a way to flash the stock firmware so i dont even know if that will work.
Ok guys got any ideas?
Update.
Ok spent 4 hours on a windows pc today trying to flash firmware and install qcom drivers thinking the download errors were due to the drivers. Then at the last moments went to Tecknights page and downloaded and installed the lgup dual mode program.
So the bastitches of higher android office decided to screw everyone out of bootloader unlocking. The ARB numbers have recently (like in the past 3 months) been changed to 003. Meaning you cannot flash firmware with an ARB number lower than 003.
But that doesnt stop us completely. Two ideas initially popped into my head. Hex edit the .kdz so that the ARB number matches the phone. Or lol split the .kdz into its seperate partition images then wipe the partitions and use qdl or lgup to repair the now bricked phone. No device data no ARB no problem.
Im hoping the former works over the latter but ill keep you informed.
But really guys thats extreme and i cant see too many folks going through the wipe process to enable fastboot. So we have to find an easier way.
Is there any way to know what partition the ARB protection resides in? If those parts could be wiped im thinking it might fool the flashtool into thinking that there isnt any protection.
one of your devices is MTK isn't it? can't you use SP Flash Tool like for other Mediatek devices? you should be able to flash images to emmc_user with locked bootloader, for example boot, recovery, system, ... all you need is a correct scatter file (which you could create with WwR MTK)
So your saying finish porting my recovery and use sp flash tools to install it. See i have been curious about that procedure and how not having an unlocked bootloader would effect flAshing from recovery. I was thinking brick. But its worth a try if it wont brick and i get full Root with magisk. Ty
Btw when i was porting my recovery i ran into a rather large well too large problem. When i went repack using abdroid image studio which i have used in the past with out problem, it would not shrink the image back down even though i was only trading a few files. How do i fix that
start with readback boot / recovery. then try to unpack, so you will know the scatter is right (at least, for this partitions) or compare files with your already existing backup files
no problems here with unpacking/ repacking with AIK
IDEA:::: ok so for the Qcom boards i have a solution possibly. I know that the older software versions have working fastboot and recovery going and can be boot loader unlocked. That tells me that a fota uodate is screwing things up.
PROBLEM:::: ARB my fortune 2 will not let me install at all anything before ARB3.
ARB_location:::: bootloader
Solution:::: download and extract the stock .kdz for device with working features. Wipe parts bootloader and laf using qpst and reinstall. Solves two problems in one go. Allows fastboot and and bootloader unlock and future re-install of stock firmware
may work but remember your bootloader is locked and you need to by-pass this via testpoint (or at least previously enabled oem unlocking and don't lost these setting) otherwise sahara will fail
well it was an idea. I just did some fact checking and also looked at the files dumped from the .dz dump of the fortune 2 stock rom. PBL or primary bootloader cannot be removed or flashed according to a thread it is a pernanent installation.
But upon more reading i can flash my recovery and boot.img using qfil in qpst along witn every thing else. But i need to know wether qfil reads ARB info and if so where i can find it in the firmware so i dont flash that img but instead pull it from phone as is.
i would really like to know what the twitterpating deal is with these LMX210 phones. ok when i firsr got my fortune 2 i bought it for two reasons the rootability of the device and the fact that tje msm8937 board came pre-installed with otg software by default which in my eyes meant no more freaking computer to use adb.
Well it is all there the drivers the software. but guess what. it doesnt work. i have no idea whats stopping it all from working but even lsusb doesnt bring a twitch or hint of reading any thing over the usb.
does any one know how to fix this
Yo. There is definitely ways to flash on linux using virtual machines, wine etc to run windows apps but you got ahold of a windows box to use. IF it is in EDL mode (Qualcomm mode with a driver saying 9008 in it..) then there is still faith you can revive it. You will need the firmware dumped from someone then youll need to run a program creating XML files for the phones firmware parition files. Youll next need a firehose which is what they call the programmers for EDL that send through the commands and firmware in a low low level that these programs like LGUP just do not do yet (don't know why..... Im waiting for someone to program the LGUP dev version with an EDL mode using emmcdl along with a way to create XML files too. Who knows maybe it will happen if we bring it up enough. The hardest problem youll have is getting a proper emmc programmer for the phone. I can source a lot so if teknight doesnt have something to help with EDL just get ahold of me and ill see what I have and send you some stuff.
Man i have been trying to unbrick the LMX-210 CV1 devices since last year. Tek has nothing but supports the work in hope of finding a solution. I have a ton of fire hoses and saharas all of which have cost me nothing but frustration. I have almost every qpst made and have tried them all with my firehose and saharas. Thr only thing i havent done is pull the mbns off my phones and try them. Trust me system dumps are crap.
The only sign of life i came by was flashing an sd card with the gpt and then flashing each partition manually using ubuntu. In return i got the battery logo but thats it.
Would love to figure it out though
By the way I have been compiling kernels. I call it the jokerfish kernel. Its packed full of drivers and debugging features plus gpu idlers boosters and all those crazy fishy thIngs. Its got governors and wire guard. Otg support. Io schedulars and overclocks. Cpu hotplugging and fast charge.
Now i cant figure out how to get fast charge to work but its set up for msm-otg phy-msm-otg qpnp-smbcharger and smb135x.
All that and not a single panic to reboot in over a week and 1/2 which is how long its been compiled. I used tweaks from the dragonheart kernel source and ported them over and did a lil c++ magic.
It has kcal too but n0 app supports it. All kinds of media and sound codecs as well. You think it would be slow but my compiling and coding skills are as mad as me. Hahahaha.'
But dont Take my word for as the gentle over there on your couch. See that smile? Hes as happy as fish in a pond.
Just remember Duhjoker is in no way responsible for bricked devices so try it at the risk to yourself.
This particular fishy thingy works for msm8917 cv1 devices like aristo 2 and k8+ which have been tested by the madman himself.
If you like you could thank me but the permanent smiles on your faces will be just as loved.
lol so fast_charge is working on the kernel but you have to add a custom tunable to a kernel app to get it going. Just add the path
/sys/class/power_supply/usb/uevent
Then you will get a choice of values to manipulate
Mecool KM2 - Root
Hi
Is there any change for TWRP or ROOT method for this Widevine certified Mecool device? Any TWRP,ROOT and MagiskHide are possible?
Looking for someone who help me root this device.
Code:
CPU: Amlogic S905X2 Quad Core ARM Cortex A53
GPU: ARM Mail-G31 MP2
OS: Android 10.0 ATV
Memory: DDR4 2GB, eMMC 8GB
Review: https://www.wirelesshack.org/review-mecool-km2-android-10-tv-box-2gb-ram-s905x2-cpu.html
reserved for future updates
LifelessLife said:
Mecool KM2 - Root
Hi
Is there any change for TWRP or ROOT method for this Widevine certified Mecool device? Any TWRP,ROOT and MagiskHide are possible?
Click to expand...
Click to collapse
I don't think this will happen. This box is certified by Netflix.
Once you can root it, Mecool will lose the Netflix certification and most probably Mecool won't get certification in the future.
Noter2017 said:
Once you can root it, Mecool will lose the Netflix certification and most probably Mecool won't get certification in the future.
Click to expand...
Click to collapse
That's not true. Nvidia Shield is rooted, doesn't mean they cannot get future certifications.
rajricardo said:
That's not true. Nvidia Shield is rooted, doesn't mean they cannot get future certifications.
Click to expand...
Click to collapse
Can you name another box?
The Shield is a complete exception. Not even the certificated Xiaomi boxes can be rooted, even though they have a huge community.
Mecool also has to be super careful. Not that long ago they have been selling boxes with fake/illegal certificates that could play Netflix in HD. Netflix blocked all of these boxes at some point.
Hi All,
I'm fairly new to this android tv scene, but have been following these discussions for a couple months now... I'm a hardware guy, so I picked up a couple of these units, and dissected one, ie took off the CPU and emmc.
I'm still not quite understanding of what exactly is happening with 'unlocking' bootloaders, and how this AMLogic 'tee' environment fully works, maybe you all can try to help me out a bit..
but I did want to share that I see we can still USB boot this thing, and use the AMLogic burning tool to at least re-write an image to the flash... the 'boot_5' pin I've shown in the attached pics..
you can catch it from that via (or trace) in the pic, and just touch it to gnd while powering on the unit, and it goes into USB boot via the amlogic rom... world cup device comes up and you can indeed use the burning tool..
I also dumped the emmc flash if anyone wants it? I'm not sure if that helps for being able to root it though, that's where I need some help understanding... I realize there are BL1, BL2, and BL3 boot stages, BL2 & BL3 I believe are the 'boot.img' and 'bootloader.img' that are present in the flash? that right?
I can put the emmc dump up on a mega.nz link if anyone wants it, but wasn't sure if it matters...
Principal-McVicker said:
but I did want to share that I see we can still USB boot this thing,
Click to expand...
Click to collapse
By, "USB boot" do you mean actually boot operating system files from USB, or do you mean just the ability to obtain a burn mode (worldcup) connection over USB?
Principal-McVicker said:
I'm still not quite understanding of what exactly is happening with 'unlocking' bootloaders,
Click to expand...
Click to collapse
Skyworth has modified u-boot (bl33) for this device such that u-boot won't recognize an unlocked status for the bootloader.
Principal-McVicker said:
use the AMLogic burning tool to at least re-write an image to the flash...
Click to expand...
Click to collapse
For the above reason (no recognition of an unlocked status), flashing images that are not unmodified stock will fail verification and not boot.
Principal-McVicker said:
I also dumped the emmc flash if anyone wants it?
Click to expand...
Click to collapse
What version does it contain?
Hi,
So hopefully this will clarify a bit... the AmLogic S905X2/X3 uses the 'boot4/boot5/boot6' pins for the power-on boot order (power-on config) pins... these are shared pins, that are also DAT4,DAT5,DA6 (data bits 4,5,6) for the emmc interface.
So internally the amlogic has boot4/5/6 pull up, ie '111' for the boot order. When you pull boot5 low, it goes 101, ie USB first.... this is essentially what this is doing, so the amlogic bootRom is now in USB boot first, versus emmc.
(I'm assuming you can prob. also do this by just shorting any of the emmc data bits to gnd (versus just bit 5), cause corruption, and it should also fail over to usb..
I haven't tried to actually flash any image yet, but at least I see the worldcup device, and connect with the burning tool...
so I'll attach the bootup log, as well as the 'build.prop' from the /vendor folder in the image... I think this should tell you what version it's running...
*** BTW: forgot to mention, most of these devices that have a 'recovery' button or hidden switch, seem to be using 'GPIOA0_3' pin, a GPIO pin... and it's coded into the AmLogic u-boot code is 'AMLOGIC_KEY' or something like that... so when you hold it... u-boot eventually see's it and halts, and starts up the usb device ***
This is much later then when doing the above, putting the CPU into usb-boot.. just FYI....
Another thing I wanted to mention, regarding the BL33 (which I now understand is u-boot), in the image dump, it starts at offset 0x200, and appears to probably be AES encrypted, there's not even a header on it?
I also took apart an X96 Max+ for comparison, since that box is pretty much open, and the flash image has u-boot unencrypted at the same location, and it starts with the @aml header...
I've been going through the AMLogic tools trying to understand where/how the encryption is done, but I don't understand yet how this BL33 is encrypted, and how BL32 knows what the keys are? and what's the difference from the X96 having u-boot unencrypted..
and in this one, the BL33 is encrypted? How did 'Skyworth' decrypt the bootloader to patch it?
(I'll follow-up with a mega.nz link with the mecool image once it finishes uploading)
Here's the full emmc dump:
734.74 MB file on MEGA
mega.nz
LifelessLife said:
Mecool KM2 - Root
Hi
Is there any change for TWRP or ROOT method for this Widevine certified Mecool device? Any TWRP,ROOT and MagiskHide are possible?
Looking for someone who help me root this device.
Code:
CPU: Amlogic S905X2 Quad Core ARM Cortex A53
GPU: ARM Mail-G31 MP2
OS: Android 10.0 ATV
Memory: DDR4 2GB, eMMC 8GB
Review: https://www.wirelesshack.org/review-mecool-km2-android-10-tv-box-2gb-ram-s905x2-cpu.html
Click to expand...
Click to collapse
Principal-McVicker said:
but at least I see the worldcup device, and connect with the burning tool...
Click to expand...
Click to collapse
Note that there are two types of worldcup connections. One is invoked entirely from bootrom, it is sometimes called usb download mode. It is sort of a DFU mode that has limited functionality.
In the uart console, a connection to this type of worldcup connection will look something like this;
Code:
G12A:BL:0253b8:61aa2d;FEAT:F2F939B2:32060;POC:F;RCY:0;EMMC:800;NAND:81;SD?:20000;USB:8
Note that nothing can be done using the burning tool, or the command-line update tool, with the above type of worldcup connection on the km2, due to download mode access being password protected on this device. Notwithstanding the fact that the usb burning tool will report the connection.
The second type of worldcup connection is invoked from an application in u-boot named "update". This type of worldcup connection can work with the usb burning tool or the command-line update tool. There is no password protection. In the uart console, a connection to this type of worldcup connection will look something like this;
Code:
InUsbBurn
wait for phy ready count is 0
[MSG]sof
Set Addr 1
Get DT cfg
Get DT cfg
Get DT cfg
set CFG
Get DT cfg
Get DT cfg
Principal-McVicker said:
I've been going through the AMLogic tools trying to understand where/how the encryption is done, but I don't understand yet how this BL33 is encrypted, and how BL32 knows what the keys are? and what's the difference from the X96 having u-boot unencrypted..
Click to expand...
Click to collapse
Read all of the stuff at the following link, starting from oldest to newest;
Code:
https://fredericb.info/tag/amlogic.html
Principal-McVicker said:
How did 'Skyworth' decrypt the bootloader to patch it?
Click to expand...
Click to collapse
Maybe it is not most correct to call it a "patch" I use that terminology because that is what skyworth uses. You'll see something like this in the uart console;
Code:
[sk_patch,24]amlogic's uboot for Android10().date:Apr 8 2021
Starting the controller
USB XHCI 1.10
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
[sk_usb_cfg_init,422]load file "/skyworth/factory_mode/uboot/check_udisk.cfg" from u disk failed!
[sk_boot,182]general boot.
Whatever skyworth does to u-boot, it is done at the source level before the bootloader is compiled.
Principal-McVicker said:
most of these devices that have a 'recovery' button or hidden switch, seem to be using 'GPIOA0_3' pin, a GPIO pin... and it's coded into the AmLogic u-boot code is 'AMLOGIC_KEY' or something like that... so when you hold it... u-boot eventually see's it and halts, and starts up the usb device ***
This is much later then when doing the above, putting the CPU into usb-boot.. just FYI....
Click to expand...
Click to collapse
You can define the upgrade_key to be any gpio pin you like that is not otherwise used.
You can use GPIOA0_3, but I think skyworth also uses that for some usb power mode. I think I used GPIOA0_5, which is one of the pins on the uninstalled infrared led near the micro sd slot.
The factory location for the reset button is a side mounted smd switch below the microsd slot (opposite side of the board). In the fcc photo's this switch is actually installed along with some smd resistors near it. I never figured out what gpio pin it uses. But it could never work without being defined in the environment, which it is not!
What's your end goal here? Modifying the bootloader will be rough unless you can get the bootrom keys. If you don't modify the bootloader so that an unlocked status is recognized, you can't flash non-stock partitions.
If you just want root, that can be done with a workaround. If you want to use the device to boot an alternate operating system, this probably can be done, with a workaround.
G12A:BL:0253b8:61aa2d;FEAT:F2F939B2:32060;POC:F;RCY:0;EMMC:800;NAND:81;SD?:20000;USB:8
Note that nothing can be done using the burning tool, or the command-line update tool, with the above type of worldcup connection. Notwithstanding the fact that the usb burning tool will report the connection.
Click to expand...
Click to collapse
Heya,
Just wanted to clarify on this... that is the USB connection right from bootROM that I get... and the burning tool would work if I had the bootrom pwd, as this unit reports PWD is needed...
I just did this last night on a 'banana pi M5', which does not have a pwd locked bootrom, and I did the usb burn from this boot method, as it did not have any code on it whatsoever prior to me loading it....
Thanks for all of the info BTW, I'll read over it all, what I really wanted to know about was how that BL33 was encrypted... I'll get back if I have more questions, but I really appreciate all the info
My end goal was really just to understand what all of you already knew, I just couldn't get my head around all of it... I wanted to either just load another OS on this entirely, or figure out a way to hack the bootloader....
Principal-McVicker said:
Just wanted to clarify on this... that is the USB connection right from bootROM that I get... and the burning tool would work if I had the bootrom pwd, as this unit reports PWD is needed...
Click to expand...
Click to collapse
Right, in order to use usb download mode, you need the password (if one is employed).
But this is the very odd case use of a worldcup connection. Unheard of for end-user use.
End users use the reset button, which runs the u-boot "update" application to establish a more robust worldcup connection that can flash and read, and even run u-boot shell commands, without any password.
yeah, so I've been looking at compiling source, as its all up there for the banana pi, so I can play with all the pieces..
Is this skyworth info up in another thread here on this site?
Also, how did he actually write this re-compiled BL33 to the device? he re-program the flash and re-mount it? or just tap the lines and program in place?
Or, I'm taking a guess he may have used the unsigned loader exploit? I'm guessing that may not be patched in current bootROMs? or at least not all of them?
Principal-McVicker said:
these devices that have a 'recovery' button or hidden switch, seem to be using 'GPIOA0_3' pin, a GPIO pin...
Click to expand...
Click to collapse
goapy said:
The factory location for the reset button is a side mounted smd switch below the microsd slot (opposite side of the board). In the fcc photo's this switch is actually installed along with some smd resistors near it. I never figured out what gpio pin it uses. But it could never work without being defined in the environment, which it is not!
Click to expand...
Click to collapse
Since you have an extra km2 with the x2 SoC removed, can you trace back the factory reset button traces to the gpio location on the SoC?
I tried finding it by shorting the traces, and using u-boot's gpio command to see which pins had a status change, but I still couldn't find which gpio pin is being used by the factory reset switch location.
Principal-McVicker said:
Here's the full emmc dump:
734.74 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
Thanks for this. This contains version;
MECOOL/HP4035-Mecool/LAS:10/QTT5.200819.003/C2.0.6_20210723:user/release-keys
Although over a year old, it is 4 months newer than what I had.
Since you have an extra km2 with the x2 SoC removed, can you trace back the factory reset button traces to the gpio location on the SoC?
I tried finding it by shorting the traces, and using u-boot's gpio command to see which pins had a status change, but I still couldn't find which gpio pin is being used by the factory reset switch location.
Click to expand...
Click to collapse
Sure thing... I'll do this tonight when I get back home from work, no problem at all...
I think the first step I'd like to try with this thing is just get root? if possible... or at least do something fun to it...
(best way to try and really get a better understanding of this arm tee is to work on a fully locked implementation like this one)
Principal-McVicker said:
I think the first step I'd like to try with this thing is just get root? if possible... or at least do something fun to it...
Click to expand...
Click to collapse
Since doing this is a rather technical process and requires verbose instructions, I'll send the details via direct message.
Principal-McVicker said:
(best way to try and really get a better understanding of this arm tee is to work on a fully locked implementation like this one)
Click to expand...
Click to collapse
It might help to turn on full log level console output for the stock build. Then at least you'll see all of the tee interactions during bootup.
goapy said:
Since doing this is a rather technical process and requires verbose instructions, I'll send the details via direct message.
It might help to turn on full log level console output for the stock build. Then at least you'll see all of the tee interactions during bootup.
Click to expand...
Click to collapse
Heya, Ok... that would be great if you could PM me whatever you can help with...
I double-checked myself, as I thought maybe I missed a u-boot console, but I don't see one on this thing, I don't see any way for it to break into u-boot or any stage while it's booting up? nothing I hammer on the keyboard stops the process from what I can tell?
So, I was trying to identify which pads you are saying are for the smd switch.. but I waasn't totally sure, figured it would be faster to just post the top/bottom pics from that side, and you just circle the spot you want me to trace out?
(FYI, I took down my mega.nz link for the dump, since it sounds like you pulled it down, I hate leaving that stuff up for long unless someone else needs it, they can always PM me)
See attached image. The purple arrow identifies the pad that I want to trace.
But I just remembered that it is difficult to trace because it goes to a via to the opposite side of the board underneath the card slot.
I don't want to make work for you, I was just curious.