I need root my xoom. What tutorial is corret? My model is MZ 605. A need help please...
Tks
rickjardim said:
I need root my xoom. What tutorial is corret? My model is MZ 605. A need help please...
Tks
Click to expand...
Click to collapse
Are you experienced with adb?
If so, use any tutorial on android development, you can try this: http://forum.xda-developers.com/showthread.php?t=979760
If you want something even easier you must try this: http://forum.xda-developers.com/showthread.php?t=1011196
Good luck on rooting process.
Dont forget to be sure of your model and the tutorial you are following...
Not root .. xoom brick. I need other boot.img. for mz 605. The xoom is gsm e wifi in brazil. Tks
Woot glad to see someone developing root for the 3g brazil xoom. I don't think anyone has taking on this project yet. Be sure to keep us updated. I am sure a lot of people are going to be waiting on your finished product.
Argh god dammit
I wish some people that have these new devices would come see us first before htey go overwriting their stock images and leaving them selves up **** creek without a paddle.
Dear colleagues in the Forum. I'm trying every way to access root in my xoom. I can not in any way. All information sought on forums did not work. If anyone can help me find a solution to this problem will be grateful and granting bonuses in cash (paypal). MZ 605 model is new and unique in the world to have wifi and 3g gsm. All methods of root in the forum are used to model MZ 600 or 604. This is the problem. thank you for your help.
rickjardim,
Try this one:
1. Install ClockworkMod Recovery v3.0.2.5 as described here: http://forum.xda-developers.com/showthread.php?t=1038870
This actualy means that you need to unclock bootloader and flash ClockworkMod Recovery. In this case you will loose your stock recovery
2. Download attached Root_Xoom.zip file and put it on SD card
3. Insert SD card into Xoom
4. Boot Xoom in the recovery mode
5. In ClockworkMod Recovery menu choose "install zip from sdcard" and "choose zip from sdcard" and install Root_Xoom.zip
6. Reboot Xoom
Hope you will have Root after that.
Adb, Fastboot and flash recovery ok! But the bootloader recovery mode is brick.
What does it means "recovery mode is brick" ? Could you please explain in more details
Recovery brick
The recovery mode brick on dysplay. the comand no funcion.
Motorola XOOM WiFi UMTS MZ605 Root!!!!
Motorola XOOM WiFi UMTS MZ605 Root!!!!
Based Xoom WiFi (MZ604) Root!! on http://forum.xda-developers.com/showthread.php?t=1010568
Prepare:
1) Download the Motorola WiFi Xoom Root Zip file and unzip it.
2) Replace the rootboot.img with the attached file boot-new.img in this post
3) You need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
4) You'll need fastboot - get it here http://developer.htc.com/adp.html
5) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools - http://developer.android.com/sdk/index.html
6) Place the files in the SDK Tools folder.
Ready:
1)Open cmd in the SDK Tools folder.
2)adb reboot bootloader
3) fastboot oem unlock
4) adb reboot bootloader
If stuck at "Dual Core Technology"
Hold VolUp and power to restart Xoom
Hold VolDown will booting unit for fastboot mode
5) fastboot flash boot boot-new.img
6) fastboot reboot
7) adb remount
8) DO NOT install these, as one of them will cause the WiFi fail (not sure which one):
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
9) adb push su /system/bin
10)adb shell ln -s /system/bin/su /system/xbin/su
11) adb shell chmod 4755 /system/bin/su
12) adb push Superuser.apk /system/app
13) adb reboot
WE HAZ ROOT!!
Hi,
mike00000
I do not understand step 8. Just jump from step 7 to 9?
rickjardim
I'm also in Brazil and have this model too, Any news? or
[ ] ´s
New image to XOOM MZ605. Please!!
Today I received my XOOM and lost it at the same time.
I tried to Root it and I couldn´t. I think there is no way to root for model MZ605. Now I need urgently a new image for it.
I've tried the recovery but did not work.
Please could someone help me?
Here is the new stock rom to MZ605 (3G and WIFI) from Brazil.
w*w*w.me*gauploa*d.co*m/?d=1O19E31S
About 125.27Mb
Just remove *.
Hi there,
The method of rooting for the European xoom works fine for the mz605. I've done it and upgraded to 3.1 and it works great.
The guides I used are in my signature, if you needhelp in portuguese or have any doubts please PM me.
Boa sorte! E cuidado.
sandro.bertini,
How do you get root?
The UK model is quadriband? I think not, but the Brazilian model is.
Como você conseguiu fazer root?
O modelo UK é quadriband? Eu acho que não, mas o modelo brasileiro é.
jrego,
I got root by following the instructions in the guide which is linked in my signature, just click the word “rooted ”.
The european model is quadbend for gsm and triband for wcdma (3g). The brazilian model is quadband for both, bjt the guides work great anyway.
PM me if you need help in portuguese.
Good luck.
Folks,
I´m trying to figure out how to update my stock brazil MZ605 to 3.1 with root (preferably).
No news about an OTA update (so far haven´t heard of any1 that managed to get it around here). Otoh, I can see that ppl from Brazil already managed to update and root it.
So far, I think that I´ll need to:
root 3.01;
update it with code from US version;
update / patch it with some of the european version;
root it;
Any1 working on a specific guide ? I can´t wait to use 3.1!
StealthNet,
I have mine working great in 3.1, as I state some 2 or 3 posts before yours.
Just follow the links in my signature:
1) Root using the link in the "ROOTED" word;
2) Install CWM Recovery using the instrucions in the CWM thread, does not matter the Xoom version;
3) Update to 3.1 using the Euro method (the link is in my signature in the "HC 3.1" phrase). I pulled the files using ADB instead of doing a full backup and wrote my own build.prop. Read the guide and you will understand what I mean.
4) If you want, flash the last Tiamat Kernel (you need to flash the 3G boot image that BRD says its for Verizon but don't worry, it doesn't break your 3G). The link is in the "Tiamat 1.4.4 Full Throttle @1.6GHz" phrase in my sig.
Good luck. If you need help in Portuguese PM me.
Last night I was trying to root this tablet.. Everything was going fine until I got stuck...
During the process it asks to do system restore.. I click yes but then after a few seconds it says restoration ended...
And it returns to home.... Also when it ask to do full restore there are fields where it asks for a password... I never enterd any pw at first boot...
So now I'm stuck... It doesn't ask for a pw when i agree to do a system restore..
À bit of info on the tablet.
Android version: 4.0.4
Baseband version: 1.4rc3
Kernel version: 3.0.8 [email protected] #95
Build number: DGM_PAD_T909_UK_G_V1_20121002 (lot no: 1210002)
Who can help me ?
Ok I just tried again... I gad to hit the restore button twice... But still no joy...
After reboot and the unlock screen it just goes straight to the homepage, it doesn't give me the terminal.. Here is what I get...
And now I'm stuck there...... I made a video on youtube...quality ain't that great..
youtu.be/ssiD_TfdUoQ
Please look at your device and click "Restore my data"
Achieved! hit ENTER to continue.
Druk op een toets om door te gaan. . .
failed on '/data/system' - Directory not empty
failed on '/data/app' - Directory not empty
mkdir failed for /data/app, File exists
Need to reboot now!
Waiting for device to come up again....
Unlock your device, a Terminal will show now, type this 2 lines, after each line
press ENTER
/data/local/tmp/onload.sh
/data/local/tmp/onload2.sh
after this is done press a key here in this shell to continue!
If the shell on your device does not show please re-start the process!
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
at com.android.commands.am.Am.run(Am.java:99)
at com.android.commands.am.Am.main(Am.java:80)
at com.android.internal.os.RuntimeInit.finishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:238)
at dalvik.system.NativeStart.main(Native Method)
Druk op een toets om door te gaan. . .
All solved now, finally got root access on the DGM-T909 tablet.
The principle is the same as the other methode I tried...
You must have the tablet installed in windows with the drivers
then go to this website : bdfabricio.blogspot.com.br/2012/08/root-android-40-novo-metodo.html
Download the app : Download (Versão 0.1 BETA)
Run it as admin or it will fail to install
After you run it check if your device is found under 'List of devices attached'
Then type s and press enter
Your device will restart and you now have root access.
Check it with 'Root Checker' app wich is found in google play
That's it....
Hope I helped someone out....
driver
hi how did u get the drivers for the dgm t-909 mine wont install on my windows 8
I have never rooted a device. before....Never Ever...... I am looking for help for an "ULTRA NOOB" guide on how to root my Le Max2 . My main and only goal for now is to get my device to an dark theme. Black background with white font. Any help out there? Oh yeah, and please let me reiterate how much of a beginner I am with all of this.
I don't really completely understand TWRP, or fastboot etc. Complete noob.
vanevs22 said:
I have never rooted a device. before....Never Ever...... I am looking for help for an "ULTRA NOOB" guide on how to root my Le Max2 . My main and only goal for now is to get my device to an dark theme. Black background with white font. Any help out there? Oh yeah, and please let me reiterate how much of a beginner I am with all of this.
I don't really completely understand TWRP, or fastboot etc. Complete noob.
Click to expand...
Click to collapse
Hello you need,
1) TWRP Recovery drive.google.com/file/d/0B8UizUpBrF1YeFZhckhqUlhsdzA (for Le Max 2 ONLY, search google for other phones.)
2) Root.zip drive.google.com/file/d/0B8UizUpBrF1YWmU0SU82clhUb0k (PUT THIS IN PHONE FOLDER) (DON'T UNZIP!!!)
3) An existing ADB and FASTBOOT. This comes with the Android SDK from Google. Google this if you don't have this one. or you can use Minimal ADB and Fastboot.
Steps -
1) Place the root.zip in the base folder of storage in phone.
2) Place the twrp.img in the same folder as ADB and FASTBOOT.
3) Check if phone is detected with this command, if it does not show any devices, add Drivers and/or change ADB and FASTBOOT versions.
Code:
adb devices
4) If it detects, run the following commands -
Code:
adb reboot bootloader
{[WAIT FOR DEVICE TO GO TO BOOTLOADER MODE]}
fastboot boot twrp.img
{[WAIT FOR RECOVERY TO OPEN]
5) Now flash supersu zip and reboot.
Regards
Vatsal,
Forum Moderator.
This TWRP is for NAVON Raptor 3G
It isn't compatible with NAVON Raptor 7, and never will!
Requirements:
Code:
[COLOR="Red"][B]-Unlocked bootloader[/B][/COLOR]
-ADB files
-Mediatek drivers (ADB driver, VCOM driver, etc..)
You can also try to flash this recovery with Flashify + root but it's not tested!
The following only applies to locked tablets:
To unlock bootloader go to Settings>About tablet and tap the Build number 3 times
Go to Developer settings, and tap on OEM unlocking
In CMD type adb reboot bootloader, this will reboot the tablet into fastboot mode
Place the recovery.img into the root folder of adb (i.e.: C:\adb\recovery.img)
Then type the following and enter per line:
Code:
[I][B]cd c:\adb[/B][/I]
[I][B]fastboot flash recovery recovery.img[/B][/I]
If you get a permission not allowed, your tablet isn't unlocked, you need to unlock it.
Warning: Unlocking bootloader will wipe your data!
Type: fastboot oem unlock
Then press Volume Up, it should say success. If it's not, repeat the oem unlock steps and try again.
Reset the tablet, then power up the Tablet by pressing Power + Volume up, then select Recovery
Enjoy the recovery!
What's not working:
Code:
-Mount USB storage
-MTP
-You tell me
Download link: https://drive.google.com/open?id=0B9kEI7tbfDrbU1NiVENCcFF6VGM
For Hungarians:
Ha bootloopol a tablet, nézd meg hogy unlockolva van-e az OEM unlock
a Build-ra koppintva 3x behozza a fejlesztői beállításokat, majd az OEM Unlock-ra kell menni
A tablet már nincs meg nekem, így nem tudok segíteni
Hi all,
It's been a long time since I released my root guide for Xperia XA and I'm back for the same reasons: I didn't find a way to root my new Smart TV so I worked hard to find the way and now I want to share the answer with you.
## Background
I bough a cheap Smart TV as a replacement of my 15 years old LG TV used as a monitor for my PC.
It's a 32" TV, manufactured by STRONG, model is SRT 32HC4432, Soc is MSD6683 and codename is "komagome"
The TV have Android TV 9 with only 1GB RAM so it's slooooow and the sound is awfull, I thinked "OK let's root it and tweak it a little". After a long search I found nothing easy and usable for my TV: No "one click" root solution, no factory firmware to extract boot.img and patch it, no TWRP and all guides are outdated for my TV. So I started from scratch (or near).
This guide should works for a lot of TV with MSTAR Soc and Android TV 9.
## Rooting MSTAR TV on Android TV 9 (PIE)
Before proceeding a word of caution (or why you wouldn't like to root your TV):
1. Unlocking your BootLoader will void your warranty.
2. Unlocking your bootloader will wipe the device (factory reset) so make a backup !
3. Disabling dm-verity is a security flaw
3. If you have confidential files in your TV don't unlock your bootloader, as long as your TV is locked your data are officially secured.
4. Opening your TV will void your warranty too.
5. If you brick your TV and you don't have a factory firmware you will no be able to recover it.
6. This guide is not for noob and I will not answer questions like: How to enable ADB? What is UART? How to connect with Putty?
Edit: rooting will break videos on YouTube, Netflix,... Thanks to @dante_ov for the feedback, I will try to find why and fix the problem.
## Requirement
- Adb and Fastboot drivers on your PC
- An USB to serial adapter
- Some solder skills if you are not lucky like me
- Putty software or equivalent
- A USB key (or two)
- Magisk Manager apk
- A file manager app to install apk
- A brain (recommanded)
## Method
1) Unplug the power cord of the TV and remove the back cover of the TV.
2) Connect RX, TX and GND of your adapter on the UART port of the motherboard, DO NOT CONNECT VCC ! On my motherboard it's at the bottom near RCA connectors and I have to solder wires because there is no socket
3) Connect Putty with speed set to 115200
4) Plug the power cord and right after keep pressing Enter on your PC until you see the prompt in the terminal session. For me the prompt is <<M5621>>#
6) We need the partitions info, the command ismmc part
copy/paste the result in a text file on your PC and save it, now we can make a backup of all partitions.
7) Format your USB key in FAT32 and plug it on the USB port on the right of the TV, it will be USB 0, if you connect on the bottom USB port it will be USB 2 or 3. Given commands will be for USB 0.
8) Enter command usb reset 0 to initialize the key
9) For root we only need the recovery partition but to be safe make a backup of all partitions. Be carefull with userdata partition because of FAT32 limitations, size limit is 4GB. You can skip it if you don't care about your user data.
You have to backup partitions one by one because the commands with emmcbin without comments and mmc dd mmc2usb to make a full backup corrupt the dump or the USB key
The command looks like:
emmcbin [usbportnum] [pad] [binname] [offset/partitionname] [dumpsize]
For [offset/partitionname] we use the name of the partition and for [dumpsize] we use length, both values obtained at step 6. [binname] is the name of the created file on the USB key.
For sample:
emmcbin 0 0 recovery.bin recovery 65536
after the dump, if like me you have an error
** Bad Signature on 0:37: expected 0x5840, got 0x0000
[do_emmc_mkbin]: check bininfo of part 37 failed ignore it
10) Now that you have all partitions enter usb stop
Unplug the key and copy the content in a safe place
11) We have to unlock the bootloader by entering
avbab set_device_state 0
setenv devicestate unlock
saveenv
12) We have to disable dm-verity to avoid bootloop, command is
avbab disable-verity
13) Unplug/replug the tv and boot normally, you should see the annoying message " /!\ Your bootloader is unlocked ... " and the wipe data processing screen right after. Wait and follow the setup wizard, enable ABD on the TV then install Magisk Manager app.
13) Rename recovery.bin to recovery.img, copy it on the USB key and plug it on the bottom port of the TV.
14) Open Magisk Manager and patch recovery.img, don't uncheck recovery setting box.
15) On your computer, pull the patched recovery with ADB, it should be in /storage/emulated/0/Download/Magisk_patched_XXX.img
Then copy it on the USB key from the PC and rename it recovery2.bin
I have to do like this because I can't simply copy/paste from internal storage to USB (permission denied)
16) Plug the key on the right side of the tv and do step 4 again
17) We will flash the patched recovery on the recovery partition and on boot too !
(I will explain why later)
Commands are:
usb reset 0
usb_partial_upgrade_to_emmc recovery2.bin recovery
usb_partial_upgrade_to_emmc recovery2.bin boot
18) unplug/plug the power cord and boot normally
19) YOU ARE ROOTED !
20) Hit the thank button on this post
## Unroot
You can unroot the device by flashing the stock boot and recovery with commands from step 17.
You can enable dm-verity again with avbab enable-verity command
You can relock the bootloader with avbab set_device_state 1 command
## Conclusions and comments
If you are familiar with MSTAR devices you noticed that I didn't used special tools and keys, all ways used before are not working anymore, upgrade packages are differents too. Now they are in pkg format so it's not possible to extract boot, recovery, system, ... like before (or I missed the way)
I found a factory firmware for the KIVI 32f710kw who is the copy of my TV but I wasn't able to unpack it.
SPI and TFTP ways are not possible on my TV (as I tried).
An other big change is that the TV uses "system as root" to work so the ramdisk is in system partition and not in the boot that's why I flashed the patched recovery on boot too on step 17.
You can flash only on recovery partition but each time you shutdown (not standby) the TV you will have to reboot to recovery to trigger the root as explained in Magisk documentation.
I don't know if UART through HDMI is working on power on to do the same without opening the TV, I can enable it in the factory menu within Android but I don't have the adapter to try.
## What next ?
Now that I have root and disabled dm-verity I'm free to edit factory configs to enable some features, add the missing HDCP2 key and tweak the firmware.
An other good thing will be to try firmwares from differents TV and GSI Roms
because YES my TV is "Treble enabled"
Have a nice day and good luck !
Thanks for sharing
rrvuhpg said:
We have to unlock the bootloader by entering
avbab set_device_state 0
Click to expand...
Click to collapse
avbab seems not exist on my MSD338 based TV. Upon entering the commands in the console (<< MStar >>#), it returns an error saying Unknown command 'avbab' - try 'help'. The command also doesn't appear in help
The other commands do work though
Do commands differ between devices? Is there any alternative command I can use on my TV, that also unlocks the bootloader? Is there some proper documentation for these commands, since the descriptions in help are really vague
sagnikpal2004 said:
avbab seems not exist on my MSD338 based TV. Upon entering the commands in the console (<< MStar >>#), it returns an error saying Unknown command 'avbab' - try 'help'. The command also doesn't appear in help
The other commands do work though
Do commands differ between devices? Is there any alternative command I can use on my TV, that also unlocks the bootloader? Is there some proper documentation for these commands, since the descriptions in help are really vague
Click to expand...
Click to collapse
Hi,
After a quick search it looks like MSD338 is an "old" Soc so all previous commands and tools should works. You will probably have better answers for MSD338 here: https://forum.xda-developers.com/t/tools-mstar-android-tv-firmware-tools.3559227/
rrvuhpg said:
Hi all,
It's been a long time since I released my root guide for Xperia XA and I'm back for the same reasons: I didn't find a way to root my new Smart TV so I worked hard to find the way and now I want to share the answer with you.
## Background
I bough a cheap Smart TV as a replacement of my 15 years old LG TV used as a monitor for my PC.
It's a 32" TV, manufactured by STRONG, model is SRT 32HC4432, Soc is MSD6683 and codename is "komagome"
The TV have Android TV 9 with only 1GB RAM so it's slooooow and the sound is awfull, I thinked "OK let's root it and tweak it a little". After a long search I found nothing easy and usable for my TV: No "one click" root solution, no factory firmware to extract boot.img and patch it, no TWRP and all guides are outdated for my TV. So I started from scratch (or near).
This guide should works for a lot of TV with MSTAR Soc and Android TV 9.
## Rooting MSTAR TV on Android TV 9 (PIE)
Before proceeding a word of caution (or why you wouldn't like to root your TV):
1. Unlocking your BootLoader will void your warranty.
2. Unlocking your bootloader will wipe the device (factory reset) so make a backup !
3. Disabling dm-verity is a security flaw
3. If you have confidential files in your TV don't unlock your bootloader, as long as your TV is locked your data are officially secured.
4. Opening your TV will void your warranty too.
5. If you brick your TV and you don't have a factory firmware you will no be able to recover it.
6. This guide is not for noob and I will not answer questions like: How to enable ADB? What is UART? How to connect with Putty?
Edit: rooting will break videos on YouTube, Netflix,... Thanks to @dante_ov for the feedback, I will try to find why and fix the problem.
## Requirement
- Adb and Fastboot drivers on your PC
- An USB to serial adapter
- Some solder skills if you are not lucky like me
- Putty software or equivalent
- A USB key (or two)
- Magisk Manager apk
- A file manager app to install apk
- A brain (recommanded)
## Method
1) Unplug the power cord of the TV and remove the back cover of the TV.
2) Connect RX, TX and GND of your adapter on the UART port of the motherboard, DO NOT CONNECT VCC ! On my motherboard it's at the bottom near RCA connectors and I have to solder wires because there is no socket
3) Connect Putty with speed set to 115200
4) Plug the power cord and right after keep pressing Enter on your PC until you see the prompt in the terminal session. For me the prompt is <<M5621>>#
6) We need the partitions info, the command ismmc part
copy/paste the result in a text file on your PC and save it, now we can make a backup of all partitions.
7) Format your USB key in FAT32 and plug it on the USB port on the right of the TV, it will be USB 0, if you connect on the bottom USB port it will be USB 2 or 3. Given commands will be for USB 0.
8) Enter command usb reset 0 to initialize the key
9) For root we only need the recovery partition but to be safe make a backup of all partitions. Be carefull with userdata partition because of FAT32 limitations, size limit is 4GB. You can skip it if you don't care about your user data.
You have to backup partitions one by one because the commands with emmcbin without comments and mmc dd mmc2usb to make a full backup corrupt the dump or the USB key
The command looks like:
emmcbin [usbportnum] [pad] [binname] [offset/partitionname] [dumpsize]
For [offset/partitionname] we use the name of the partition and for [dumpsize] we use length, both values obtained at step 6. [binname] is the name of the created file on the USB key.
For sample:
emmcbin 0 0 recovery.bin recovery 65536
after the dump, if like me you have an error
** Bad Signature on 0:37: expected 0x5840, got 0x0000
[do_emmc_mkbin]: check bininfo of part 37 failed ignore it
10) Now that you have all partitions enter usb stop
Unplug the key and copy the content in a safe place
11) We have to unlock the bootloader by entering
avbab set_device_state 0
setenv devicestate unlock
saveenv
12) We have to disable dm-verity to avoid bootloop, command is
avbab disable-verity
13) Unplug/replug the tv and boot normally, you should see the annoying message " /!\ Your bootloader is unlocked ... " and the wipe data processing screen right after. Wait and follow the setup wizard, enable ABD on the TV then install Magisk Manager app.
13) Rename recovery.bin to recovery.img, copy it on the USB key and plug it on the bottom port of the TV.
14) Open Magisk Manager and patch recovery.img, don't uncheck recovery setting box.
15) On your computer, pull the patched recovery with ADB, it should be in /storage/emulated/0/Download/Magisk_patched_XXX.img
Then copy it on the USB key from the PC and rename it recovery2.bin
I have to do like this because I can't simply copy/paste from internal storage to USB (permission denied)
16) Plug the key on the right side of the tv and do step 4 again
17) We will flash the patched recovery on the recovery partition and on boot too !
(I will explain why later)
Commands are:
usb reset 0
usb_partial_upgrade_to_emmc recovery2.bin recovery
usb_partial_upgrade_to_emmc recovery2.bin boot
18) unplug/plug the power cord and boot normally
19) YOU ARE ROOTED !
20) Hit the thank button on this post
## Unroot
You can unroot the device by flashing the stock boot and recovery with commands from step 17.
You can enable dm-verity again with avbab enable-verity command
You can relock the bootloader with avbab set_device_state 1 command
## Conclusions and comments
If you are familiar with MSTAR devices you noticed that I didn't used special tools and keys, all ways used before are not working anymore, upgrade packages are differents too. Now they are in pkg format so it's not possible to extract boot, recovery, system, ... like before (or I missed the way)
I found a factory firmware for the KIVI 32f710kw who is the copy of my TV but I wasn't able to unpack it.
SPI and TFTP ways are not possible on my TV (as I tried).
An other big change is that the TV uses "system as root" to work so the ramdisk is in system partition and not in the boot that's why I flashed the patched recovery on boot too on step 17.
You can flash only on recovery partition but each time you shutdown (not standby) the TV you will have to reboot to recovery to trigger the root as explained in Magisk documentation.
I don't know if UART through HDMI is working on power on to do the same without opening the TV, I can enable it in the factory menu within Android but I don't have the adapter to try.
## What next ?
Now that I have root and disabled dm-verity I'm free to edit factory configs to enable some features, add the missing HDCP2 key and tweak the firmware.
An other good thing will be to try firmwares from differents TV and GSI Roms
because YES my TV is "Treble enabled"
Have a nice day and good luck !
Click to expand...
Click to collapse
Hello,
Thanks you very much! Very useful guide, I was able to root my TV following the instructions, I have a JVC with mainboard 17MB170 (Produced by VESTEL). UART is over VGA, I connected through a RaspberryPi 3 B+ UART pins with PuTTY because I didn't have any USB to UART interface.
My questions is:
Is there any solution for the process not breaking YouTube and Netflix, I installed SafetyNet module and it showing to be compliant but still YouTube is not working. (Application opens up but throws an error when you try to play any video)
Best regards!
ScorpionXII said:
Hello,
Thanks you very much! Very useful guide, I was able to root my TV following the instructions, I have a JVC with mainboard 17MB170 (Produced by VESTEL). UART is over VGA, I connected through a RaspberryPi 3 B+ UART pins with PuTTY because I didn't have any USB to UART interface.
My questions is:
Is there any solution for the process not breaking YouTube and Netflix, I installed SafetyNet module and it showing to be compliant but still YouTube is not working. (Application opens up but throws an error when you try to play any video)
Best regards!
Click to expand...
Click to collapse
Hi,
I'm happy to see that my guide worked for you
I never found how to fix the issue with YouTube and Netflix, sorry for that.
If you find the fix you can share it here
Very nice tutorial!
I managed to root my NOBLEX DM32X7000 TV (also MSD6683-based) thanks to your method and it works fine except for one huge issue...
While you all mention that YouTube and Netflix breaks for you, I didn't have that problem at all. Instead, my Live TV app breaks and it gets stuck on "Retrieving data..." for all inputs when the boot image is patched with Magisk.
Would you mind sharing your LiveTV and MtkTvInput apps so I can try mix and matching them?
Finding other firmwares for this SoC is quite difficult, I haven't been able to find one so far.
Seem hardcode for me
rrvuhpg said:
Hi all,
It's been a long time since I released my root guide for Xperia XA and I'm back for the same reasons: I didn't find a way to root my new Smart TV so I worked hard to find the way and now I want to share the answer with you.
## Background
I bough a cheap Smart TV as a replacement of my 15 years old LG TV used as a monitor for my PC.
It's a 32" TV, manufactured by STRONG, model is SRT 32HC4432, Soc is MSD6683 and codename is "komagome"
The TV have Android TV 9 with only 1GB RAM so it's slooooow and the sound is awfull, I thinked "OK let's root it and tweak it a little". After a long search I found nothing easy and usable for my TV: No "one click" root solution, no factory firmware to extract boot.img and patch it, no TWRP and all guides are outdated for my TV. So I started from scratch (or near).
This guide should works for a lot of TV with MSTAR Soc and Android TV 9.
## Rooting MSTAR TV on Android TV 9 (PIE)
Before proceeding a word of caution (or why you wouldn't like to root your TV):
1. Unlocking your BootLoader will void your warranty.
2. Unlocking your bootloader will wipe the device (factory reset) so make a backup !
3. Disabling dm-verity is a security flaw
3. If you have confidential files in your TV don't unlock your bootloader, as long as your TV is locked your data are officially secured.
4. Opening your TV will void your warranty too.
5. If you brick your TV and you don't have a factory firmware you will no be able to recover it.
6. This guide is not for noob and I will not answer questions like: How to enable ADB? What is UART? How to connect with Putty?
Edit: rooting will break videos on YouTube, Netflix,... Thanks to @dante_ov for the feedback, I will try to find why and fix the problem.
## Requirement
- Adb and Fastboot drivers on your PC
- An USB to serial adapter
- Some solder skills if you are not lucky like me
- Putty software or equivalent
- A USB key (or two)
- Magisk Manager apk
- A file manager app to install apk
- A brain (recommanded)
## Method
1) Unplug the power cord of the TV and remove the back cover of the TV.
2) Connect RX, TX and GND of your adapter on the UART port of the motherboard, DO NOT CONNECT VCC ! On my motherboard it's at the bottom near RCA connectors and I have to solder wires because there is no socket
3) Connect Putty with speed set to 115200
4) Plug the power cord and right after keep pressing Enter on your PC until you see the prompt in the terminal session. For me the prompt is <<M5621>>#
6) We need the partitions info, the command ismmc part
copy/paste the result in a text file on your PC and save it, now we can make a backup of all partitions.
7) Format your USB key in FAT32 and plug it on the USB port on the right of the TV, it will be USB 0, if you connect on the bottom USB port it will be USB 2 or 3. Given commands will be for USB 0.
8) Enter command usb reset 0 to initialize the key
9) For root we only need the recovery partition but to be safe make a backup of all partitions. Be carefull with userdata partition because of FAT32 limitations, size limit is 4GB. You can skip it if you don't care about your user data.
You have to backup partitions one by one because the commands with emmcbin without comments and mmc dd mmc2usb to make a full backup corrupt the dump or the USB key
The command looks like:
emmcbin [usbportnum] [pad] [binname] [offset/partitionname] [dumpsize]
For [offset/partitionname] we use the name of the partition and for [dumpsize] we use length, both values obtained at step 6. [binname] is the name of the created file on the USB key.
For sample:
emmcbin 0 0 recovery.bin recovery 65536
after the dump, if like me you have an error
** Bad Signature on 0:37: expected 0x5840, got 0x0000
[do_emmc_mkbin]: check bininfo of part 37 failed ignore it
10) Now that you have all partitions enter usb stop
Unplug the key and copy the content in a safe place
11) We have to unlock the bootloader by entering
avbab set_device_state 0
setenv devicestate unlock
saveenv
12) We have to disable dm-verity to avoid bootloop, command is
avbab disable-verity
13) Unplug/replug the tv and boot normally, you should see the annoying message " /!\ Your bootloader is unlocked ... " and the wipe data processing screen right after. Wait and follow the setup wizard, enable ABD on the TV then install Magisk Manager app.
13) Rename recovery.bin to recovery.img, copy it on the USB key and plug it on the bottom port of the TV.
14) Open Magisk Manager and patch recovery.img, don't uncheck recovery setting box.
15) On your computer, pull the patched recovery with ADB, it should be in /storage/emulated/0/Download/Magisk_patched_XXX.img
Then copy it on the USB key from the PC and rename it recovery2.bin
I have to do like this because I can't simply copy/paste from internal storage to USB (permission denied)
16) Plug the key on the right side of the tv and do step 4 again
17) We will flash the patched recovery on the recovery partition and on boot too !
(I will explain why later)
Commands are:
usb reset 0
usb_partial_upgrade_to_emmc recovery2.bin recovery
usb_partial_upgrade_to_emmc recovery2.bin boot
18) unplug/plug the power cord and boot normally
19) YOU ARE ROOTED !
20) Hit the thank button on this post
## Unroot
You can unroot the device by flashing the stock boot and recovery with commands from step 17.
You can enable dm-verity again with avbab enable-verity command
You can relock the bootloader with avbab set_device_state 1 command
## Conclusions and comments
If you are familiar with MSTAR devices you noticed that I didn't used special tools and keys, all ways used before are not working anymore, upgrade packages are differents too. Now they are in pkg format so it's not possible to extract boot, recovery, system, ... like before (or I missed the way)
I found a factory firmware for the KIVI 32f710kw who is the copy of my TV but I wasn't able to unpack it.
SPI and TFTP ways are not possible on my TV (as I tried).
An other big change is that the TV uses "system as root" to work so the ramdisk is in system partition and not in the boot that's why I flashed the patched recovery on boot too on step 17.
You can flash only on recovery partition but each time you shutdown (not standby) the TV you will have to reboot to recovery to trigger the root as explained in Magisk documentation.
I don't know if UART through HDMI is working on power on to do the same without opening the TV, I can enable it in the factory menu within Android but I don't have the adapter to try.
## What next ?
Now that I have root and disabled dm-verity I'm free to edit factory configs to enable some features, add the missing HDCP2 key and tweak the firmware.
An other good thing will be to try firmwares from differents TV and GSI Roms
because YES my TV is "Treble enabled"
Have a nice day and good luck !
Click to expand...
Click to collapse
Will this method work on my Hisense 50A71F, based on Board : MSD6886, platform M7322?
rrvuhpg said:
4) Enchufe el cable de alimentación y luego siga presionando Enter en su PC hasta que vea el mensaje en la sesión de terminal. Para mí, el aviso es <<M5621>>#
Click to expand...
Click to collapse
Hola . Tengo en mi taller un tv con micro MSD6683BQHT... Obtengo el log en consola sin problemas pero no puedo entrar a modo super usuario de ninguna manera como demás tv . He usado enter, esc hasta botón de power presionado etc etc . Alguien me ayuda ?
Thank you, I have successfully rooted my device following the tutorial.