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.

[DUMP] ZTE Light Tab 2(V9+) a.k.a. Light Plus

http://www.4shared.com/file/dcITNyo7/original_rom_zte_light_plus.html
Inside the zip file:
boot.img
recovery.img
splash.img
system.img <--- successfully opened with ext2explore
recovery last_log <--- extra useful information
Original rom with gingerbread 2.3.4.
Please share / modified / duplicate / distribute
Edit: I also found rom dump of Megafon V9+ posted by azunai from 4pda forum (thanks man!) here. This is Russian version of ZTE Light Tab 2. Apparantly this rom is a newer version using gingerbread 2.3.5.
Edit2: 16/12/2011 Official firmware upgrade from Megaphone V9PLUSV1.0.0B03. I read that you loose root with this firmware upgrade and have trouble getting it back. So beware.

fathroen said:
http://www.4shared.com/file/dcITNyo7/original_rom_zte_light_plus.html
Inside the zip file:
boot.img
recovery.img
splash.img
system.img <--- successfully opened with ext2explore
recovery last_log <--- extra useful information
Original rom with gingerbread 2.3.4.
Please share / modified / duplicate / distribute
Edit: I also found rom dump of Megafon V9+ posted by azunai from 4pda forum (thanks man!) here. This is Russian version of ZTE Light Tab 2. Apparantly this rom is a newer version using gingerbread 2.3.5.
Edit2: 16/12/2011 Official firmware upgrade from Megaphone V9PLUSV1.0.0B03. I read that you loose root with this firmware upgrade and have trouble getting it back. So beware.
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
STOCK ROM:
Warning: To see more languages in settings just delete \system\etc\customize\default.xml with any root explorer and reboot
V9PLUSV1.0.0B15 (Download)
MD5: 68db20b10bc24eb0797d8d21cc9d5441
Code:
ro.build.version.release=2.3.5
ro.build.date=Fri Nov 18 15:43:27 CST 2011
ro.product.model=Light Tab 2
ro.product.locale.language=en
ro.product.locale.region=US
ro.build.software_version=V9PLUSV1.0.0B15
ro.build.sw_internal_version=V9PLUSV1.0.0B15
V9PLUSV1.0.0B03 (Download)
MD5: da870860911c038f9f3e9c136479e591
Code:
ro.build.version.release=2.3.5
ro.build.date=Mon Dec 12 07:22:32 CST 2011
ro.product.model=MegaFon V9+
ro.product.locale.language=ru
ro.product.locale.region=RU
ro.build.software_version=MEGAFON_V9PLUSV1.0.0B03
ro.build.sw_internal_version=MEGAFON_V9PLUSV1.0.0B03
------------------------------------------------------------------------------------------------------------------------------------------------
Driver for ZTE Light Tab 2 / ZTE V9 PLUS / ZTE V9+
ZTE Handset USB Driver 5.2066.1.11 (Download)
MD5: e7257bce4c2bbdc34eb09b8989d09594
------------------------------------------------------------------------------------------------------------------------------------------------
Root for ZTE Light Tab 2 / ZTE V9 PLUS / ZTE V9+
1) Unlock Root 2.2.1
MD5: c5cb298a434957179dab6891fa8cbfc1
1) Install ZTE Handset USB Driver 5.2066.1.11 and Android ADB Drivers
2) Settings - Applications - Design - "Debugging USB" tick
3) Connect the USB cable
4) Press click "Root"
5) Reload
2) Update.zip
MD5: a2844ac335a5c1cfdb9bea2fc041b415
1) Volume down + Power
( Run ClockWorkMOD 4.0.1.5) MD5: 068c0689c0dd8d36600bdc4ddf653076
2) install zip from sdcard - choose zip from sdcard - update.zip
3) Reboot
------------------------------------------------------------------------------------------------------------------------------------------------
ClockWorkMOD 4.0.1.5 for ZTE Light Tab 2 / ZTE V9 PLUS / ZTE V9+
ClockWorkMOD 4.0.1.5 (Beta 2) (Download)
MD5: 068c0689c0dd8d36600bdc4ddf653076
1) Power Off
2) Home + Volume DOWN + Power (Hold for 10 seconds)
3) Сonnect the usb cable
4) Run - INSTALL - ClockWorkMOD 4.0.1.5.bat
Else
1) Run CMD
Code:
adb reboot bootloader
cd C:\android-sdk-windows\tools
fastboot flash recovery b2_recovery-clockwork-4.0.1.5-v9plus.img

You can install this rom the newest model in a light or light V9 pro?, have different cpu, is the same thing?
thanks

fathroen said:
http://www.4shared.com/file/dcITNyo7/original_rom_zte_light_plus.html
Inside the zip file:
boot.img
recovery.img
splash.img
system.img <--- successfully opened with ext2explore
recovery last_log <--- extra useful information
Original rom with gingerbread 2.3.4.
....
Click to expand...
Click to collapse
Is there a chance that you can find any ZTE V11a/V71a aka Vodafone Smart Tab 10/7 stock rom, pls?

can someone share them file free? i can't download from vip-file..

is anyone having problems with wifi mac after update?

The ClockWorkMod file is no longer available. Does someone have another link or can you upload to a shared link? Thanks.

how do i flash the dump file to my tab?

Anybody have link for custom rom for this device?

[Q] How to get multi boot ?

I find some topic to make multi boot for X5 but I don't know exactly how do it !
http://forum.donanimhaber.com/m_59231411/tm.htm
And here:
-------------------------------------
Multi-boot
In fact, users in China use the U8800, multi-system has been used for a long time.
So, now I will use my broken English to tell you how to use multi-system
First, you need The extra two partitions in the 4G space. you could use twosys-partition.zip to get The extra two partitions 15&16
download partition package:http://forum.xda-developers.com/atta...1&d=1321675310
And
The second system-specific recovery system
http://forum.xda-developers.com/atta...1&d=1321675310
put the twosys-partition.zip and you like rom's zip into Sdcard
rename the recovery_4.0.1.5_en_sys2.img to recovery2.img , then place it to /cust
Boot into recovery,flash this package directly, same as flashing a ROM.
After flashing go to advanced options, choose to reboot to recovery.
Go into recovery again, flash this package again directly, same as flashing a ROM.now you will have The extra two partition 15 and 16
OK, let's flash two system into you phone
Go into recovery again, flash you like rom's zip
boot into first system, you could use RootExplorer access /cust, rename the recovery.img to recovery1.img, rename the boot.img to boot1.img,rename the recovery2.img to recovery.img.
reboot you system into recovery, now you recovery is second system recovery,you could flash the 100911-cm7,it will auto flash into second system.
reboot system, you will into second system (CM7)
if you want change you system to first, you could use RootExplorer access /sbin/gk, you will found some .sh files,Execution the 8-ChangeSys will auto rename all
img file then auto reboot to first system.
you could copy the 8-changesys.sh to any place let you change system easy.
restore offical partition ： download
Important：only the 100911-CM7 can flash into second system, other ROM only flash into first system
please backup your data, because you will lost all data in phone
Attached Thumbnails
Click image for larger version Name: IMG_20110507_215751.jpg Views: 12861 Size: 82.6 KB ID: 589834 Click image for larger version Name: CAP201106210959.jpg Views: 7380 Size: 23.3 KB ID: 631536 Click image for larger version Name: CAP2011062109581.jpg Views: 11102 Size: 29.6 KB ID: 631537
Attached Files
File Type: zip offical-partition-2sys.zip - [Click for QR Code] (1.29 MB, 1459 views)
File Type: zip twosys-partition.zip - [Click for QR Code] (1.19 MB, 525 views)
File Type: zip recovery5.0.2.7_en_sys1.zip - [Click for QR Code] (4.20 MB, 788 views)
File Type: zip recovery5.0.2.7_en_sys2.zip - [Click for QR Code] (4.20 MB, 633 views)
Click to expand...
Click to collapse
So any one who can held us to make multi boot for X5 Actual Fine ?

http://forum.donanimhaber.com/m_59231411/tm.htm is my guide and it's for 35 kernels
Multi-boot
In fact, users in China use the U8800, multi-system has been used for a long time.
So, now I will use my broken English to tell you how to use multi-system
First, you need The extra two partitions in the 4G space. you could use twosys-partition.zip to get The extra two partitions 15&16
download partition package:http://forum.xda-developers.com/atta...1&d=1321675310
And
The second system-specific recovery system
http://forum.xda-developers.com/atta...1&d=1321675310
put the twosys-partition.zip and you like rom's zip into Sdcard
rename the recovery_4.0.1.5_en_sys2.img to recovery2.img , then place it to /cust
Boot into recovery,flash this package directly, same as flashing a ROM.
After flashing go to advanced options, choose to reboot to recovery.
Go into recovery again, flash this package again directly, same as flashing a ROM.now you will have The extra two partition 15 and 16
OK, let's flash two system into you phone
Go into recovery again, flash you like rom's zip
boot into first system, you could use RootExplorer access /cust, rename the recovery.img to recovery1.img, rename the boot.img to boot1.img,rename the recovery2.img to recovery.img.
reboot you system into recovery, now you recovery is second system recovery,you could flash the 100911-cm7,it will auto flash into second system.
reboot system, you will into second system (CM7)
if you want change you system to first, you could use RootExplorer access /sbin/gk, you will found some .sh files,Execution the 8-ChangeSys will auto rename all
img file then auto reboot to first system.
you could copy the 8-changesys.sh to any place let you change system easy.
restore offical partition ： download
Important：only the 100911-CM7 can flash into second system, other ROM only flash into first system
please backup your data, because you will lost all data in phone
Attached Thumbnails
Click image for larger version Name: IMG_20110507_215751.jpg Views: 12861 Size: 82.6 KB ID: 589834 Click image for larger version Name: CAP201106210959.jpg Views: 7380 Size: 23.3 KB ID: 631536 Click image for larger version Name: CAP2011062109581.jpg Views: 11102 Size: 29.6 KB ID: 631537
Attached Files
File Type: zip offical-partition-2sys.zip - [Click for QR Code] (1.29 MB, 1459 views)
File Type: zip twosys-partition.zip - [Click for QR Code] (1.19 MB, 525 views)
File Type: zip recovery5.0.2.7_en_sys1.zip - [Click for QR Code] (4.20 MB, 788 views)
File Type: zip recovery5.0.2.7_en_sys2.zip - [Click for QR Code] (4.20 MB, 633 views)
Click to expand...
Click to collapse
this guide for 32 kernels.

forumber2 said:
http://forum.donanimhaber.com/m_59231411/tm.htm is my guide and it's for 35 kernels
Click to expand...
Click to collapse
Can you translate it?
Google translate is s**t
Sent from my U8800 using Tapatalk 2

Qqqxxxzzz said:
Can you translate it?
Google translate is s**t
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
i will try but i dont have enough time.

Please !
Could you transalate to English please ?

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?

How to patch extras+info app 2018-???? for Interop Unlocking WP 8.1/10

Hi there to those who are having trouble patching extras+info app for interop unlock. I have found a solution for it. However, in this method, not all Lumia devices are supported for this method.
List of Lumia devices that are supported with this method:
520
521
525
620
625
720
820
920
925
928
1020
1320
Method requirements:
WP Internals (any version) (the reason for device limitation)
A .FFU file of the device (get one from here: http://lumiafirmware.com/)
Its own lumia emergency loader (.vpl) (same from here: http://lumiafirmware.com/)
Engineering SBL3 files (dl link at below) (ps: its not mine)
vcreg xap for patching (dl link at below) (again, its not mine)
Method instructions:
Unlock the bootloader and gain root access to your phone.
Go to this directory:
Code:
[drive of mainos]\Data\PROGRAMS\{2377...}\Install
P.S.: Access denied error? visit here.
Delete the following files:
WMAppManifest.xml
AppManifest.xaml
OEMSharedFolderAccessLib.dll
OEMSharedFolderAccessLib.winmd
Right click the XAP file and open it with 7-zip. And extract all its contents to the previous directory where extras+info app was located.
Reboot phone to boot up normal mode.
After booting up, go to settings and select extras+info/Extras & info.
I hope this thread helped you all!

CRAZIELYme said:
Hi there to those who are having trouble patching extras+info app for interop unlock. I have found a solution for it. However, in this method, not all Lumia devices are supported for this method.
List of Lumia devices that are supported with this method:
520
521
525
620
625
720
820
920
925
928
1020
1320
Method requirements:
WP Internals (any version) (the reason for device limitation)
A .FFU file of the device (get one from here: http://lumiafirmware.com/)
Its own lumia emergency loader (.vpl) (same from here: http://lumiafirmware.com/)
Engineering SBL3 files (dl link at below) (ps: its not mine)
vcreg xap for patching (dl link at below) (again, its not mine)
Method instructions:
Unlock the bootloader and gain root access to your phone.
Go to this directory:
P.S.: Access denied error? visit here.
Delete the following files:
WMAppManifest.xml
AppManifest.xaml
OEMSharedFolderAccessLib.dll
OEMSharedFolderAccessLib.winmd
Right click the XAP file and open it with 7-zip. And extract all its contents to the previous directory where extras+info app was located.
Reboot phone to boot up normal mode.
After booting up, go to settings and select extras+info/Extras & info.
I hope this thread helped you all!
Click to expand...
Click to collapse
No need to patch extras+info , windows phone internals already gives root access (interop unlock) with unlimited xap install enabled

?
fadilfadz said:
No need to patch extras+info , windows phone internals already gives root access (interop unlock) with unlimited xap install enabled
Click to expand...
Click to collapse
Interop Unlocking requires altering the phone's registry. How would WP Internals do that??? They use an Engineering bootloader to do Root Access to the C: drive of the phone. Registry altering didn't occurred during the process...

CRAZIELYme said:
Interop Unlocking requires altering the phone's registry. How would WP Internals do that??? They use an Engineering bootloader to do Root Access to the C: drive of the phone. Registry altering didn't occurred during the process...
Click to expand...
Click to collapse
Ooh yeah, but after getting root access just simply install root tool and vcreg for interop unlock

WP internals 2.5 supports 95% of the phones... Gonna try your way on my 635. Will edit if it works.
Edit: Did it... Doesn't work on 635, when you open extras&info it instantly closes.

fadilfadz said:
Ooh yeah, but after getting root access just simply install root tool and vcreg for interop unlock
Click to expand...
Click to collapse
This is the correct answer, once you unlock the bootloader and enable root access, you can just simply sideload vcreg and use it.