Database Users

Boot Screens

How to replace the ADVENT logo on the boot screen.
The screen resolution is 1024x600.
How to replace your Boot Screen:
Create and save your bootscreen as a PNG (if it is smaller than 1024x600, your bootscreen will be centered, transparency will result in the ANDROID boot glare effect).
1. Connect your Vega to your PC's usb.
2. Turn USB Debugging on in the Applications menu.
3. In command prompt / terminal, browse to the directory containing adb.exe, type:
Code:
adb-windows pull /system/framework/framework-res.apk /framework-res.apk
This will copy the framework-res.apk from your Vega and save it in the directory adb.exe is located.
4. Open framework-res.apk in WinZIP / WinRAR or similar and browse to /assets/images/
5. Replace android-logo-mask.png with your bootscreen and save the apk in the same format, overwriting the original.
6. In your already open command prompt / terminal window type:
Code:
adb-windows remount
adb-windows shell rm /system/framework/framework-res.apk
adb-windows push framework-res.apk /system/framework/
7. Reboot your Vega.
********* Reducing the file size *******************
If you want to reduce the file size of your new framework-res.apk file, you could delete the following files from /res/drawable/:
nvidia_wallpaper01.jpg
nvidia_wallpaper02.jpg
nvidia_wallpaper03.jpg
nvidia_wallpaper04.jpg
nvidia_wallpaper05.jpg
nvidia_wallpaper06.jpg
nvidia_wallpaper07.jpg
nvidia_wallpaper_dual01.jpg
nvidia_wallpaper_dual02.jpg
nvidia_wallpaper_dual03.jpg
nvidia_wallpaper_dual04.jpg
nvidia_wallpaper_dual05.jpg
nvidia_wallpaper_dual06.jpg
nvidia_wallpaper_dual07.jpg
Also you can remove all *.ogg from the following directory /system/media/ringtones
Boot Screens:
File name: Advent_Vega_Leather.jpg File size: 235.60 KB
File name: android3d.jpg File size: 366.66 KB
File name: Androidboot.jpg File size: 1.24 MB
File name: androidlogomask.png File size: 807.17 KB
File name: Androidwall.jpg File size: 136.15 KB
File name: Android_green.jpg File size: 123.04 KB
File name: Android_logo.jpg File size: 86.83 KB
File name: android_logo_mask.png File size: 18.18 KB
File name: android_logo_mask2.png File size: 40.21 KB
File name: boot.jpg File size: 1.25 MB
File name: Bootphotoshop.jpg File size: 337.77 KB
File name: Bootphotoshop2.jpg File size: 337.44 KB
File name: Bootphotoshop3.jpg File size: 354.39 KB
File name: Bootphotoshop4.jpg File size: 233.84 KB
File name: stealboot.jpg File size: 513.15 KB
File name: Vega_Black_Leather.jpg File size: 434.97 KB
File name: Vega_Glow.jpg File size: 321.36 KB
File name: wallpapergrey.jpg File size: 77.28 KB
******** Thanks to JordanT92 who provided the original information.
******** And boffboff, remlap, morchuboo, arad85, wobblydoggy, Higgsy, donalkeane from MoDaCo who provided the graphics.

@percy25 - are you just copy/pasting all this stuff from the modaco forums?
Everytime I come and refresh here, it seems there's another thread with the same info...
At least give some credit to the users from other places, who've done the work already?

monkeyboy451 said:
@percy25 - are you just copy/pasting all this stuff from the modaco forums?
Everytime I come and refresh here, it seems there's another thread with the same info...
At least give some credit to the users from other places, who've done the work already?
Click to expand...
Click to collapse
Good point Monkeybot451, Updated Post.
I have moved my Post "Advent Vega - ROMs / Software Updates / Guides / How Tos, Links to ROMs, Flash Updates, Guides, Misc apk's" from Modaco to here as from now will only be maintaining it here.

percy25 said:
Good point Monkeybot451, Updated Post.
I have moved my Post "Advent Vega - ROMs / Software Updates / Guides / How Tos, Links to ROMs, Flash Updates, Guides, Misc apk's" from Modaco to here as from now will only be maintaining it here.
Click to expand...
Click to collapse
Seriously that just sucks and I think unfair I honestly don't see this community growing the numbers MoDaCo has.
Good luck with it though but these kinds of attitudes make me dislike this forum. Seems like cutting and running for no reason to me.

remlap said:
Seriously that just sucks and I think unfair I honestly don't see this community growing the numbers MoDaCo has.
Good luck with it though but these kinds of attitudes make me dislike this forum. Seems like cutting and running for no reason to me.
Click to expand...
Click to collapse
I didnt mean to upset anyone!
I have just found the XDA Developers fourm more open to development as its free to all (Instead of the charging scheme modaco uses). I believe updates should be available to all for the community to benefit.
To keep everyone happy I will maintain both post to benefit all.

Hi Percy, yeah thats true, still you don't have to pay MoDaCo still use the forums I honestly like the idea of two separate forums doing different things that I can take the best from both and hopefully contribute where I can
Cheers mate

Please note that this is a very easy way to lock your device.
I tried to change my boot screen and got stock in booting due to "insufficient disk space" issue, and had to reflash the device.

Harplo said:
Please note that this is a very easy way to lock your device.
I tried to change my boot screen and got stock in booting due to "insufficient disk space" issue, and had to reflash the device.
Click to expand...
Click to collapse
True, I been in that situation many times. I sometimes find if you use a "adb shell rm" command to remove old framework.apk first, this can help.

percy25 said:
I have just found the XDA Developers fourm more open to development as its free to all (Instead of the charging scheme modaco uses). I believe updates should be available to all for the community to benefit.
Click to expand...
Click to collapse
Could not agree with your more. Welcome to xda dev, hope we can all do great things to are vegas.
You are keeping me happy with all of your useful info. Helped loads with the performance pack. Thanks

I have updated the attached framework-res.apk to include the following:
Android Boot Screen
Battery Colour changed to Blue (instead of Green by default)
Removed the Nvidia Wallpapers to keep file size down.
Link to File:
File name: framework-res.apk File size: 6.49 MB
See the first post for instructions on how to install.

[Q] Edit clockworkmod flash.cfg file?

Hello all, I'm totally newb to flashing ROM so please take it easy if the question is redundant. I have flashed and got this Gingerbread ROM from MDJ (http://forum.xda-developers.com/showthread.php?t=877777) running perfectly fine. In his instruction, he uses the 250MB partition. So after installation of a lot of apps, my system storage is listed as:
Total: 250MB, Free: 123MB. (I got these numbers from Quick System Info)
I guess the ROM only used 127MB? I'm thinking changing the flash.cfg file like this,
From "system ya 250M" to "system ya 130M" so that would give me a few more MB in the userdata partition.
Is that gonna break something I don't know about?

erythrophilia said:
Hello all, I'm totally newb to flashing ROM so please take it easy if the question is redundant. I have flashed and got this Gingerbread ROM from MDJ (http://forum.xda-developers.com/showthread.php?t=877777) running perfectly fine. In his instruction, he uses the 250MB partition. So after installation of a lot of apps, my system storage is listed as:
Total: 250MB, Free: 123MB. (I got these numbers from Quick System Info)
I guess the ROM only used 127MB? I'm thinking changing the flash.cfg file like this,
From "system ya 250M" to "system ya 130M" so that would give me a few more MB in the userdata partition.
Is that gonna break something I don't know about?
Click to expand...
Click to collapse
First of all that will wipe your existing installation / data clean. Hope you understand that. Secondly, it should work fine but doesn't leave you much space at all on your system partition. I would add a little more- maybe 135M or 140M.

I see. I already have a CWM backup so the data won't be a problem. So that means the size specified in flash.cfg isn't directly linked to other things? I mean like if I change it, and the ROM boots up, it looks for the right size, and then if the original size isn't there, it will refuse to boot.
But anyway, I'll experiment with it later today. Thanks.

erythrophilia said:
From "system ya 250M" to "system ya 130M" so that would give me a few more MB in the userdata partition.
Is that gonna break something I don't know about?
Click to expand...
Click to collapse
I have been flashing Nand roms but until now i dont understand how to edit flash cfg. there is no choice in the clockwork recovery that has such option. I know it may sound silly.Thank you

jad71 said:
I have been flashing Nand roms but until now i dont understand how to edit flash cfg. there is no choice in the clockwork recovery that has such option. I know it may sound silly.Thank you
Click to expand...
Click to collapse
You have to edit the flash.cfg in notepad before you flash it on your phone

Cant find flash.cfg
acho07 said:
You have to edit the flash.cfg in notepad before you flash it on your phone
Click to expand...
Click to collapse
i also face similar issues, can u explain where to find the flash.cfg file.

azi43far said:
i also face similar issues, can u explain where to find the flash.cfg file.
Click to expand...
Click to collapse
When you download clockwork recovery on your computer, in the extracted folder there should be a file "flash.cfg" open that in notepad and change the values to whatever you require then flash it using the daf.exe via usb flasher in magldr.

Just adding this information if someone stumbles onto this article again :
Description of flash.cfg format
===============================
1. each line define one partition
2. maximum number of partitions is 16
3. order of partitions are same like lines in the file
4. line format: <partition name> <flags/type> <size> <data filename>
partition name - up to 15 chars, shown in MTD later
size - can be related to filesize: "filesize", "filesize+10M", "filesize+10b",
or have fixed size: "10M", "100b"
[M - means Megabytes, b - menas blocks (each NAND block is 128kbytes)]
can be "allsize" for auto size partition.
flags/type - can be different values:
types:
"ya" - YAFFS2 partition. MAGLDR can show root directory context or read kernel/initrd from it
"raw" - RAW data.
flags:
"ro" - disable add extra 5% to partition size and count bad blocks into size
"boot" - this partition contains zImage and initrd.gz for NAND boot (it must have YAFFS2 type)
"asize" - auto size. this partition will use all available space after other partitions. only one partition can have this type.
"nospr" - binary data have not spare data. (2048+0 format), otherwise 2048+64 format used.
"nors" - use exactly specified size for partition. no resize is done.
"hr" - this partition must be erased if user select "AD HardReset" in MAGLDR menu.
different flags and types separated via "|" symbol, like "boot|ya|ro"

bamit99 said:
Just adding this information if someone stumbles onto this article again :
Description of flash.cfg format
===============================
1. each line define one partition
2. maximum number of partitions is 16
3. order of partitions are same like lines in the file
4. line format: <partition name> <flags/type> <size> <data filename>
partition name - up to 15 chars, shown in MTD later
size - can be related to filesize: "filesize", "filesize+10M", "filesize+10b",
or have fixed size: "10M", "100b"
[M - means Megabytes, b - menas blocks (each NAND block is 128kbytes)]
can be "allsize" for auto size partition.
flags/type - can be different values:
types:
"ya" - YAFFS2 partition. MAGLDR can show root directory context or read kernel/initrd from it
"raw" - RAW data.
flags:
"ro" - disable add extra 5% to partition size and count bad blocks into size
"boot" - this partition contains zImage and initrd.gz for NAND boot (it must have YAFFS2 type)
"asize" - auto size. this partition will use all available space after other partitions. only one partition can have this type.
"nospr" - binary data have not spare data. (2048+0 format), otherwise 2048+64 format used.
"nors" - use exactly specified size for partition. no resize is done.
"hr" - this partition must be erased if user select "AD HardReset" in MAGLDR menu.
different flags and types separated via "|" symbol, like "boot|ya|ro"
Click to expand...
Click to collapse
This is what i get when I open flash.cfg. Where do I insert the values!

[Q] Mounting ext4 as data before boot + PA 2.00

Hi everyone.
I'm trying to increase data partition storage by using ph03n!x walkthru on Paranoid Android 1.992 and 2.0. I'm stuck at extracting boot.img in Working folder. The rom.zip itself don't have boot.img or boot folder so after extracting PA rom in dsixda kitchen i copied boot.img from Nandroid backup on SD. But while im trying to extract that boot.img there's an error
Code:
Working folder found
Android 'magic' header not found at start of boot.img
Cheching if it exists elsewhere ...
Warning: Android header not found in boot.img (unsupported format)
Error: kernel offset (page size) is 0
Press Enter to continue
So i took recovery.img from nandroid backup, renamed it to boot.img and extracting went fine, but there was some problems: could not find init.htcleo.rc file and "on fs" lines in init.rc file
Any suggestions how to do it? I think that real init.rc is placet in boot.img (not recovery.img), but how to extract it?

Do you have a working folder setup? If you do, then forget about the boot.img, just place the 'boot' directory from the ROM's zip (under /kernel/). If you do not have a Working folder setup, then follow my instructions to create a temporary ROM zip with the required folders - meta-inf, system and boot.

ph03n!x said:
just place the 'boot' directory from the ROM's zip (under /kernel/)
Click to expand...
Click to collapse
Thanks a lot ph03n!x. It worked And also thanks for this great mod (Initrd.gz was great, now its time for this new method )

RSDxml-custom recovery/restore/keep data/root/remove warning logo-AIO-4.4.4

What IS this post about?
Firmware restore of 4.4.4 using RSD Lite, but for unlocked boots, the recovery flashed is custom & the logo used is the normal M-multi color rather than the warning version. Comes in Philz & Twrp flavors. Upon rebooting, Philz or TWRP will root for you.
User data is retained, not erased.
Note: After this restore you may notice problems because you kept data-just wipe data from recovery & reboot. Keeping data like this is non standard.
The logo used is from here.
First 2 attachments are about 10 MBs. There are 3 modded files to extract: MOD...xml (RSD instructions), recovery & logo to paste into your unzipped/extracted FXZ/XML folder. You may want to rename the stock recovery & logo so they will not be overwritten. Here is the usual fxz Source, which you may have already.
Do not paste the source xml folder contents into mine.
The 2 last attachments are modded full FXZs, 900 MB.
Choose the mod xml from RSD Lite 615. Moto drivers are here. There is no getvar or erase userdata as the X firmware has-which is strange for the stock XML. So use of the modded or source FXZ will leave user data alone.
Settings/Developer Options: Enable USB debugging to use RSD.
If you want a fresh restore just wipe data from stock or custom recovery before you use get into the bootloader/apfastboot screen
Note: step 2 is ap/fastboot (RSD mode) & step 6 (recovery) is where to wipe data.
Faster Mega server full versions can be downloaded for regular use on locked xt-1080s as each modded Full fxz can be easily put back to normal. Recovery.img.orig 10.5 MB & logo.bin.orig 2.6 MB just need renaming, as well as the modded ones renamed: recovery.img.mod Philz: 10.4 MB, TWRP: 8.6 MB & logo.bin.mod 2.6 MB. Then run the original xml (included)(not the one labeled MOD). Again there is no data wipe in this original firmware.
A better backup

Full 444 xml with Philz recovery is up.
It is easily converted back to the normal fxz for locked boot users.
But why? Mega is much faster than the sbf/xml storehouse site.

So if your un Rooted this is useful how?

PILLMUZIK3600 said:
So if your un Rooted this is useful how?
Click to expand...
Click to collapse
Just a faster download of the fxz, is all. Then you must convert the xml folder to normal.

Thanx
Big thanx for this solution. Now I have fully rooted and System RW on Verizon Moto Droid Ultra. I was on OTA updated to 4.4.4, and Root was broken. And now all - OK

dschewchenko said:
Big thanx for this solution. Now I have fully rooted and System RW on Verizon Moto Droid Ultra. I was on OTA updated to 4.4.4, and Root was broken. And now all - OK
Click to expand...
Click to collapse
How did this help keep WP off?

I have not unlocked the bootloader I already have stock android 4.4.4 on my droid maxx, I do not read English well, tell me know if I can flash this rom to get root without problems?

aviwdoowks said:
How did this help keep WP off?
Click to expand...
Click to collapse
I don't know. All apps have full access to system partition, but Safestrup cann't to be installed

luisdev said:
I have not unlocked the bootloader I already have stock android 4.4.4 on my droid maxx, I do not read English well, tell me know if I can flash this rom to get root without problems?
Click to expand...
Click to collapse
No way but a boot unlock. 444 has no exploit for rooting.
This helps unlocked phones only.

dschewchenko said:
I don't know. All apps have full access to system partition, but Safestrup cann't to be installed
Click to expand...
Click to collapse
Why don't you share all the details here.

Solution
aviwdoowks said:
Why don't you share all the details here.
Click to expand...
Click to collapse
Before this thread, I have 4.4.4 with broken root after OTA update (without system RW and SuperSU crash)
My way:
-Install RSD and drivers
- do solutions from head from head
- download file from 1 attach
- replace files
- flash it and see on phone error about size of recovery
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)

dschewchenko said:
Before this thread, I have 4.4.4 with broken root after OTA update (without system RW and SuperSU crash)
My way:
-Install RSD and drivers
- do solutions from head from head
- download file from 1 attach
- replace files
- flash it and see on phone error about size of recovery
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
Click to expand...
Click to collapse
Do you have a locked or unlocked bootloader?

aviwdoowks said:
Do you have a locked or unlocked bootloader?
Click to expand...
Click to collapse
I have locked verizon moto droid ultra

dschewchenko said:
I have locked verizon moto droid ultra
Click to expand...
Click to collapse
What build did it come with? Please post all info & steps!! Did you use any exploits?

aviwdoowks said:
What build did it come with? Please post all info & steps!! Did you use any exploits?
Click to expand...
Click to collapse
I have Verizon XT1080 with Locked BL, on 4.4.2 was root and WP off, after WiFi updating to 4.4.4 all was broken, and after that I wrote upper I'm now with root and system read/write permission, but safestrap see that WP ON and crashes after tapping somewhere. After updating SuperSU root will be lost.
For system R/W you may go to Terminal and run:
- su
- mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
and than with mount command check if /system have rw. After reboot you may to remount
P.S. Sorry for my english, I'm from Ukraine =)
Very bad that Moto with cutted language pack =(

dschewchenko said:
Before this thread, I have 4.4.4 with broken root after OTA update (without system RW and SuperSU crash)
My way:
Click to expand...
Click to collapse
-Install RSD and drivers
- do solutions from head from head
???
- download file from 1 attach
Was that the small?
- replace files
This must have been recovery, logo & the mod.XML.
- flash it and see on phone error about size of recovery
Details?
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
In app drawer?
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
I have no idea how you kept root if RSD succeeded properly.

aviwdoowks said:
-Install RSD and drivers
- do solutions from head
???
in head of this thread
Here is an alternate method to flash 444 "pre-recovery'ed" and thereby pre-rooted. Comes in Philz & Twrp flavors.
3 modded files: ...xml (RSD instructions), recovery & logo to paste into your unzipped FXZ/XML folder. Source.
Flash from RSD Lite 615. Moto drivers. There is no getvar or erase userdata as the X firmware has-which is strange for the stock XML. Added custom recovery & stock (boot) logo.
Settings/Developer Options: Enable USB debugging to use RSD.
If you want a fresh restore just wipe data from stock or custom recovery before you use get into the bootloader/apfastboot screen
Note: step 2 is ap/fastboot (RSD mode) & step 6 (recovery) is where to wipe data.
Paste the 3 files to your xml folder. You may want to rename the stock recovery & logo so they will not be overwritten.
Faster Mega server (but slow uploads, 1 a day. 2 Ultra & 2 X) full versions soon. 10 MB vs 900 MB.
Note for locked users: each modded Full fxz can be easily put back to normal. Recovery.img.orig & logo.bin.orig just need renaming. Then run the original xml (included). Again there is no data wipe in this original firmware.
A better backup
ATTACHED FILES
File Type: txt Philz_6.57.9_NO ERASE_user.data_stkBOOTlogo_1FF-obake_verizon-user-4.4.4-SU4.21-MEGA.xml.zip.txt - [Click for QR Code] (112 Bytes, 9 views)
File Type: txt Twrp-2.8.0.1_NO ERASE_user.data_stkBOOTlogo-1FF-obake_verizon-user-4.4.4-SU4.21-MEGA.xml.txt - [Click for QR Code] (111 Bytes, 13 views)
File Type: txt Full_Philz_6.57.9_NO ERASE_user.data_stkBOOTlogo1FF-obake_verizon-user-4.4.4-SU4.21.xml.zip.txt - [Click for QR Code] (110 Bytes, 3 views)
Click to expand...
Click to collapse
- download file from 1 attach
Was that the small?
this -> "Philz_6.57.9_NO ERASE_user.data_stkBOOTlogo_1FF-obake_verizon-user-4.4.4-SU4.21-MEGA.xml.zip.txt"
- replace files
This must have been recovery, logo & the mod.XML.
files from downloaded archive
- flash it and see on phone error about size of recovery
Details?
-standart flashing with RSD-Lite. When recovery uploading , on phone screen was error about incorrect size of recovery, and then I reboot phone to recovery(stock with VOL-DOWN and POWER), then I do full wipe, thenreboot to clean system, in menu I see SuperSU, then download and run Terminal, tap in Terminal "su", all OK, try to remount system to RW, all OK, then download Root Explorer, root permission applied and go to system for manipulate with files =)
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
In app drawer?
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
I have no idea how you kept root if RSD succeeded properly.
Click to expand...
Click to collapse
=)

dschewchenko said:
=)
Click to expand...
Click to collapse
So you flashed the mini version without system, motoboot, boot, gpt & etc.
It is still confusing so for everyone's benefit maybe, in time, your sweet time, you could be more clear about the exact steps.
Thank you.

aviwdoowks said:
So you flashed the mini version without system, motoboot, boot, gpt & etc.
It is still confusing so for everyone's benefit maybe, in time, your sweet time, you could be more clear about the exact steps.
Thank you.
Click to expand...
Click to collapse
I don't change xml, from downloaded archive I replace files with source Source (from head of thread) And in RSD check xml file that from archive Philz

dschewchenko said:
I don't change xml, from downloaded archive I replace files with source Source (from head of thread) And in RSD check xml file that from archive Philz
Click to expand...
Click to collapse
Just to be clear, I intended the attachments to overwrite the source. You overwrote the attachment with the source!! (If I read you right)
The Q is did you achieve something good by your mistake?

Anyone know how to Root ASUS Zenpad 10 (Z300cnl)?

Hello!
Does anyone know how to root the new ASUS Zenpad 10 Z300cnl (model p01t_1; adroid 6.0.1)?
I've tried many programs like KingRoot, Farmaroot, srsroot e.t.c, but they're not working!
Please, help with it!

I'm in the same situation kpyTb ...
SOS

Hello !
Need also root for the ASUS Zenpad 10 Z300cnl (model p01t_1; adroid 6. 0. 1) please help
Best thanks in advance
Sorry for my english

z300cnl
Same problem here, tried KingRoot (stuck at 1%), nothing found on the internet so far, checked all z300 related forums here.
Any help much appreciated

KpyTb said:
Hello!
Does anyone know how to root the new ASUS Zenpad 10 Z300cnl (model p01t_1; adroid 6.0.1)?
I've tried many programs like KingRoot, Farmaroot, srsroot e.t.c, but they're not working!
Please, help with it!
Click to expand...
Click to collapse
Use chainfire's systemless root method to root your device. Flash Beta SuperSU.zip in custom recovery. It will patch your boot.img and install SuperSU app to your android.

following discussion...do we have any chance?

asus zenpad 10 CNL root - please help me root this tablet, I'm totally desperate ... need accurate references that where I download and how to install them. too please, thanks a lot.
[email protected]

Z300cnl
Are there news for the ROOT of Z300CNL? I could not find anything on the web.
Best thanks in advance

Ashwinrg said:
Use chainfire's systemless root method to root your device. Flash Beta SuperSU.zip in custom recovery. It will patch your boot.img and install SuperSU app to your android.
Click to expand...
Click to collapse
great idea, yeah. but there's this list:
Code:
hammerhead-mra58k-boot-systemless.zip - [Click for QR Code] (7.82 MB, 33662 views)
File Type: zip angler-mdb08k-boot-systemless.zip - [Click for QR Code] (9.48 MB, 15646 views)
File Type: zip bullhead-mdb08i-boot-systemless.zip - [Click for QR Code] (9.98 MB, 7692 views)
File Type: zip fugu-mra58k-boot-systemless.zip - [Click for QR Code] (5.97 MB, 3336 views)
File Type: zip razor-mra58k-boot-systemless.zip - [Click for QR Code] (7.24 MB, 3696 views)
File Type: zip razorg-mra58k-boot-systemless.zip - [Click for QR Code] (7.24 MB, 2738 views)
File Type: zip razor-mra58u-boot-systemless.zip - [Click for QR Code] (7.24 MB, 3468 views)
File Type: zip shamu-mra58k-boot-systemless.zip - [Click for QR Code] (7.78 MB, 11488 views)
File Type: zip volantis-mra58k-boot-systemless.zip - [Click for QR Code] (7.70 MB, 3398 views)
File Type: zip volantisg-mra58k-boot-systemless.zip - [Click for QR Code] (7.70 MB, 3956 views)
soooo wich one we need for p01t_1? :X

there is no way to root this tablet ?
weird

yeah, that's one bad surprise :/

hello there is no way to root this tablet?