Develop Bugs

Noob Dev trying to Find a Fix

Im not gonna beat around the bush im a New Dev trying to Make a ROM im not 100% knowledgable on this but learning.
Rom Base 4.1.1-STock- from upndwn4par
what i wants to do with this?
1st Make it a LITE rom<trying to cut on the stock Fatness
2nd Make Simple mods(hold back to kill, Center Clock, bootanimation,23 toggle mod etc You get my point)
so far ive trim Down to the nest knowledge of Debloating- ive been using THIS LIST from another forum(and comparing to other gs3 the bloat is thesame)
So far ive only cut down the rom in bloat not to heavy but fairly a decent amount by 100mbs EST.
Here so far i think what is preventing my flash from workin>Since im new i though i would start using android Kitchen what ive done with this is: boot animation,data/app enable,The rest was done by the rom provider root,busybox deodex.
Now i compile in android kitchen but when i flash i get this error
Installing '/external_sd/redone.zip'... Checking for MD5 file... I:Cannot find file /external_sd/redone.zip.md5 Skipping MD5 check: no MD5 file found. mount: failed to mount /dev/block/mmcblk0p17 at /cache: Device or resource busy mount: failed to mount /dev/block/mmcblk0p15 at /data: Device or resource busy script aborted: format() expects 4 args, got 3 format() expects 4 args, got 3 E:Error executing updater binary in zip '/external_sd/redone.zip' Error flashing zip '/external_sd/redone.zip' Updating partition details... Iata backup size is 0MB, size: 12335MB, used: 16MB, free: 12161MB, in data/media: 16MB. I:Unable to mount '/usb-otg' I:Actual block device: '', current file system: 'vfat' I:Set page: 'flash_done' I:Set page: 'clear_vars'
i just need someone more advanced in this than me to help me out when i did a search to try and fix it stated to replace the update-binary so i did with the orignal stock binary and no go
HERE IS EVERYTHING REMOVE FROM ROM AND ALSO THE BUILD
https://www.dropbox.com/sh/jm0btla9iaxkj6r/0Q_XOBbGn4?v=0mcns
Much thanks
DEV CAN WE MOVE THIS TO THIS THREAD http://forum.xda-developers.com/showthread.php?t=2182496

crashpsycho said:
Im not gonna beat around the bush im a New Dev trying to Make a ROM im not 100% knowledgable on this but learning.
Rom Base 4.1.1-STock- from upndwn4par
what i wants to do with this?
1st Make it a LITE romSince im new i though i would start using android Kitchen what ive done with this is: boot animation,data/app enable,The rest was done by the rom provider root,busybox deodex.
Now i compile in android kitchen but when i flash i get this error
Installing '/external_sd/redone.zip'... Checking for MD5 file... I:Cannot find file /external_sd/redone.zip.md5 Skipping MD5 check: no MD5 file found. mount: failed to mount /dev/block/mmcblk0p17 at /cache: Device or resource busy mount: failed to mount /dev/block/mmcblk0p15 at /data: Device or resource busy script aborted: format() expects 4 args, got 3 format() expects 4 args, got 3 E:Error executing updater binary in zip '/external_sd/redone.zip' Error flashing zip '/external_sd/redone.zip' Updating partition details... Iata backup size is 0MB, size: 12335MB, used: 16MB, free: 12161MB, in data/media: 16MB. I:Unable to mount '/usb-otg' I:Actual block device: '', current file system: 'vfat' I:Set page: 'flash_done' I:Set page: 'clear_vars'
i just need someone more advanced in this than me to help me out when i did a search to try and fix it stated to replace the update-binary so i did with the orignal stock binary and no go
HERE IS EVERYTHING REMOVE FROM ROM AND ALSO THE BUILD
https://www.dropbox.com/sh/jm0btla9iaxkj6r/0Q_XOBbGn4?v=0mcns
Much thanks
DEV CAN WE MOVE THIS TO THIS THREAD http://forum.xda-developers.com/showthread.php?t=2182496
Click to expand...
Click to collapse
If you want to make a base its actually a bit more frustrating than building the ROM as a cook. I wish you I could help you but I got the same error while using the kitchen. Ive been told that the kitchen can be a bit tricky for our devices so.... I suggest you get upndwn4par's stock base and build your ROM with that. Its already done and you can now tinker just like I did.
I would then hit up loserskaters how to thread and search out any ofher ones you like.
Do you know how to compile and decompile?
Also copy the text from this thread to. your new one and I can copy my response over there. Devs will read the other one more often and its less clutter.
Have any questions I can help however I can but I'm just a cook too
Sent from my SAMSUNG-SGH-I747 using xda premium

I have never tried the kitchen so I do not know there. But what I usually have done is get a ROM that you know can be flashed and works on your phone.
Then do whatever you are wanting to change from your base ROM your using (stock deodexed works best usually since it hasn't been modified at all yet). Make all your changes to the .apk's after decompiling them, then recompile all the .apk's
Next take all your NEWLY recompiled .apks and move them into the working ROM that is recovery flash able. Put them in all the same locations where you find them.
Make changes to the updater-script only where needed for things like your ROM name and etc. and save it.
So once your done you should have a working flashable in recovery zip that now has all your .apks inside of it. Make a nandroid and then flash your newly created ROM. Give Thanks to whichever ROM dev you used the flashable zip from for use of their scripting.
Again all the above is after you know how to decompile/recompile the .apks without any errors. I also test each .a pk by pushing it to the phone first, overwriting the original apps .a pk Reboot the phone to make sure the .apks work correctly and the mods you changed in the .apks works correctly. I am not a dev but did some cooking and changing things to add whatever functionality I wanted. Then I started just wanting to theme things and got away from making as many mods (since usually the ROM I am running at the time they have/had already implemented many of the things I liked). If I can be of any help shoot me a pm.
Also as stated above, Losersk8ter has made a few How To threads for the things your asking about that you want to change/add. Some of his mods have really gone over the top lately with some REALLY cool features all put together like I haven't seen in a TW based ROM. So I am sure once you hit the ground running a bit you can pm him for advice if needed.
Sent from My Spiderman Themed I747

Get personal data from i747 bricked phone

Hi all,
I need some help.
My wife have an Samsung i747 phone which she used to store there all the pictures of our boys from the past 2 years. She never backuped the pictures.
Starting two weeks ago the phone got stuck very often, and became very hot. Last week the phone didn't power on anymore.
I could enter to download mode, but didn't succeed to go Recovery mode except of few times (I know it sounds weird, but I try a lot.. most of the times the text "Recovery Booting" for one second, and than I got the "Samsung S III" logo and the device shut down..).
So if I understood right, the was soft brick.
The few times i succeeded enter recovery mode it always print errors of something like "e: mount /system | /data | /cache failed".
I saw this thread and decide to give it a chance.
I didn't know what is the version of the bootloader (or anything else... my wife neither) so I go on the 4.3 bootloader.
I flashed the twrp 2.6.3.0 recovery and I saw there in backup section that the data is about 12giga. I couldn't make any backup of anything. I tried to reset to factory settings (without wiping the user data) and it failed(I even tried to backup the recorvery and boot partition that weights 10 mb and it failed).
I tried to flash from my sd card the:
d2att_I747UCUEMJB_bootloader
d2att_I747UCUEMJB_modem
d2att_Kernel_Stock_init.d_4.3_MJB_v1.0
AT&T_I747UCUEMJB
and everything worked but the AT&T_I747UCUEMJB.zip .
I tried flash newer twrp version, at first 2.6.3.1 and lastly 2.8.7.0. In all the same result - I can't flash the AT&T_I747UCUEMJB.zip file. the error says something about the updater (I can't read the whole error, the screen cutting the line).
Still when I open the recovery it says it couldn't load /system /cache /data partitions. I tried to change the fs type, wiping the partition, formatting - but nothing worked.
Can any one help me get the pictures out? They mean a lot to us, except the pictures from the I747 we only have a few pictures from the last 2 years.
Thanks!
p.s
I thinks that this is the log from twrp when I tried to install the AT&T_ rom:
Code:
Installing '/external_sd/AT&T_I747UCUEMJB.zip'...
Checking for MD5 file...
I:Cannot find file /external_sd/AT&T_I747UCUEMJB.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
Creating filesystem with parameters:
Size: 1572864000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 6000
Label:
Blocks: 384000
Block groups: 12
Reserved block group size: 95
Created filesystem with 11/96000 inodes and 12609/384000 blocks
error: file_write: write: I/O error
E:Error executing updater binary in zip '/external_sd/AT&T_I747UCUEMJB.zip'
Error flashing zip '/external_sd/AT&T_I747UCUEMJB.zip'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p14
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
I:Set page: 'flash_done'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p14
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
I:Set page: 'action_complete'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p14
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
I:Set page: 'clear_vars'
I:Set page: 'flash_done'
I:Set page: 'rebootcheck'
I:Set page: 'confirm_action'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'wipe'
I:Set page: 'advancedwipe'
I:Set page: 'wipe'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'

Did you try mounting that data partition in TWRP? I assume you did and that didn't work for you.
You mentioned that you tried chnaging the fs, wiping, formatting. Which partitions are you referring to?

audit13 said:
Did you try mounting that data partition in TWRP? I assume you did and that didn't work for you.
You mentioned that you tried chnaging the fs, wiping, formatting. Which partitions are you referring to?
Click to expand...
Click to collapse
I tried to mount the partitions. It didn't work. In the Mount section of twrp when I clicking the system and cache partition nothing happens. And in the backup section it shows that the size of system and cache partitions is 0MB.
I tried to change the /system /cache partitions. I didn't try the /data partition because I'm afraid losing all my data.
I forgot to mention that right now, the only way I can boot to recovery and download mode is by the sd card with the debrick image.

Since you can boot with the debrick image, did you try reflashing a bootloader or modem to the phone?
Sounds like you have the same problem as this XDA member: http://forum.xda-developers.com/galaxy-s3-att/help/failed-to-mount-data-frozen-factory-t3181035

audit13 said:
Since you can boot with the debrick image, did you try reflashing a bootloader or modem to the phone?
Sounds like you have the same problem as this XDA member: http://forum.xda-developers.com/galaxy-s3-att/help/failed-to-mount-data-frozen-factory-t3181035
Click to expand...
Click to collapse
If I understand correctly, its not the same problem. He couldn't mount just the /data while I can't /data /system /system. Another differnce is that his problems occured after he flashed things, mine was with the original recovery, and I can't do a factory reset.
Please tell me if I'm wrong.

The other user could only boot his phone using a debrick image in the phone. Will your phone boot without the sdcard?
The other user had to flash a bootloader in order to boot without the sdcard in the phone.

audit13 said:
The other user could only boot his phone using a debrick image in the phone. Will your phone boot without the sdcard?
The other user had to flash a bootloader in order to boot without the sdcard in the phone.
Click to expand...
Click to collapse
I can't boot when the sdcard isn't there.
Should I try to flash another bootloader? If so, can you tell me what bootloader should I install.
The most important thing to me right now is to get my pictures back, so currently I don't care booting with the sd card. After I get my pictures I would like to make the phone work without the sd card.
Thanks!

Do you know which bootloader was on the phone before you started flashing bootloaders?
I am not sure if flashing a bootloader and recovery will get you access to the pictures. I have never experienced a bricked s3.

audit13 said:
Do you know which bootloader was on the phone before you started flashing bootloaders?
I am not sure if flashing a bootloader and recovery will get you access to the pictures. I have never experienced a bricked s3.
Click to expand...
Click to collapse
I don't know. But what I do know is that the first time I used the debrick sd card it shows in the download mode the "warranty bit: 0" that wasn't there before. The second time I powered on the device it shows that the warranty bit is 1.
If thats help somehow recognizing the bootloader version.
I flashed (via recovery) the bootloader maximum 2 time, and via Odin few times (every time I tried another version of the recovery..something like 5 times).

I've notice that if I trying to get into download mode and release the buttons fast, the next time the device booting its showing this screen:
And when I'm going into Recovery mode its showing this screen:
Before I did the debrick the screen I has is the first one.
I thinks the second one is the debrick, because it always shows the first image for 1-2 seconds and it is rebooting and shows the second picture.

The screen without twrp is the first screen. The second screen is how the phone would look with twrp.
The fact that the warranty bit exists in download mode means the phone has at least a 4.3 bootloader.
If the phone had a kit kat bootloader before you flashed anything, flashing the mjb bootloader is probably what bricked the phone.
Are you able to confirm which rom version was on the phone before you flashed anything? This will help determine which bootloader and modem should be flashed to the phone.

audit13 said:
The screen without twrp is the first screen. The second screen is how the phone would look with twrp.
The fact that the warranty bit exists in download mode means the phone has at least a 4.3 bootloader.
If the phone had a kit kat bootloader before you flashed anything, flashing the mjb bootloader is probably what bricked the phone.
Are you able to confirm which rom version was on the phone before you flashed anything? This will help determine which bootloader and modem should be flashed to the phone.
Click to expand...
Click to collapse
I didn't have the warranty bit in download mode before I used the debrick image, and I didn't flash anything before, the warranty bit appears only after I used the debrick image. So I guess I had the 4.1.2 bootloader (I remmeber that we were updating the phone once using Kies..about 2 years ago or something like that..).
I never flashed anything to this phone before the twrp last week after the brick happened. And My wife was using the Stock rom.
But 2 days ago when I tried following this thread I do flash (using twrp install section) a bootloader.(when the sd card inserted). I took the bootloader he recommended:
Use this bootloader for the AT&T i747 ONLY https://www.dropbox.com/s/vbyeorrxapwrots/d2att_I747UCUEMJB_bootloader.zip the one in the tread where I got mine hasn't been working so use this bootloader it is the same one just hosted by a different person.
Click to expand...
Click to collapse
Thanks for trying helping!

It's also possible that the internal memory in the phone is damaged. It does happen on occasion.
Sorry, but I am out of ideas at this point.

audit13 said:
It's also possible that the internal memory in the phone is damaged. It does happen on occasion.
Sorry, but I am out of ideas at this point.
Click to expand...
Click to collapse
I thought damaged memory is the case at first, but if so the twrp 2.6.X version wouldn't recognize that my data is about 12 giga.
How can I assure this is the case?

A couple of ideas that may be of some help.
If you can boot into TWRP again you can go to >> Advanced >> Terminal Command >> Select
and enter these commands to determine current installed bootloader and modem
Code:
getprop ro.bootloader
getprop | grep version.baseband
Also, IIRC, once you are booted into your recovery, TWRP, you should be able to remove the sdcard with the debrick image and replace it with a blank card. Then, from with the Advanced menu of TWRP can you use the File Manager to copy folders/directories.

dawgdoc said:
A couple of ideas that may be of some help.
If you can boot into TWRP again you can go to >> Advanced >> Terminal Command >> Select
and enter these commands to determine current installed bootloader and modem
Code:
getprop ro.bootloader
getprop | grep version.baseband
Also, IIRC, once you are booted into your recovery, TWRP, you should be able to remove the sdcard with the debrick image and replace it with a blank card. Then, from with the Advanced menu of TWRP can you use the File Manager to copy folders/directories.
Click to expand...
Click to collapse
getprop ro.bootloader returns I747UCUEMJB (I thinks this is because I flashed the bootloader in @theramsey3 thread when I tried to follow his instrucions.)
getprop | grep version.baseband returns nothing. I tried "getprop | grep baseband" and it returns 2 result :
[ro.baseband]: [msm]
[ro.boot.baseband]: [msm]
I already tried the File Manager option. There is nothing in /data and /sdcard directories.
Thanks!

Sorry I wasn't of more help.

i believe TWRP (at least in version 2.8.x.x and newer) it will connect to your pc as a media device, which (at least on my i747) includes both the internal sd card (including the part i imagine your worried about, pictures and videos) as well as the external storage
at which point you should be able to copy files from your phone to your pc

logoster said:
i believe TWRP (at least in version 2.8.x.x and newer) it will connect to your pc as a media device, which (at least on my i747) includes both the internal sd card (including the part i imagine your worried about, pictures and videos) as well as the external storage
at which point you should be able to copy files from your phone to your pc
Click to expand...
Click to collapse
I thinks it called MTP. I don't have the internal sd card. I have the external sd card only, so I can't copy my files.
Do you have any other idea?
Added the log of twrp if it will help somehow.

reading the log, it complains about not being able to mount the data, system, and cache partition
which to me reads as the phones internal storage is dead or almost dead, or heavily corrupted.
while i'm no expert, you may have to go to an actual expert to get the data recovered, because if recovery can't mount it then i don't really know how you could get any consumer hardware to do so

Vernee Apollo Discoveries

I wanted to create a thread so as to report any unique findings from the internet realm and my own discoveries surrounding the Vernee Apollo Phone. The aim is to bring resources together to encourage development and to release utilities and roms.
Please post your own discoveries and updates!!!
This is NOT a "Vernee Apollo Lite" nor a "Vernee Apollo X" thread even though some information maybe relevant.
Device Name and Specs
Vernee Apollo.
Device Model =K15TA_A
Official Product Website
Official Product Forum
http://www.devicespecifications.com/
Vernee Apollo - Antutu Benchmark v6.2.7.
Score 92,235.
3D: 19159
UX: 38097
CPU: 27535
RAM: 7444
Helio X25 MT6797 Family System on a Chip (SoC) Comparison
Vernee Apollo deploys a X25 MT6797T.
https://en.wikipedia.org/wiki/MediaTek#Octa-_and_deca-core
https://www.mediatek.com/products/smartphones/mt6797-helio-x20
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADB and FASTBOOT Modes
The Vernee Apollo's bootloader supports Fastboot. The Recovery mode supports the Android Debugging Bridge (ADB) . To access, perform the button sequence below. A menu will appear allowing you to cycle through option to either boot into the recovery partitio,n or to start the Fastboot service.
ADB service is also available also within the Android desktop if you enable USB Debugging in the revealed developers settings menu. You will most likely need to accept a signed key issued from the managing computer for the service to communicate!
Accessing Bootloader Menu
Buttons: [Top-Volume] + [Power-Button] for 8 Seconds.
When the phone is shutdown, hold both buttons at same time from for 8 seconds. The Bootloader menu will appear and then release buttons.
Using Bootloader Menu
Button: [Top-Volume] = Cycle selection.
Button: [Bottom-Volume] = Choose selected item.
With the high screen resolution it maybe hard to see the text-options. There should be three;
1. Recovery, (Boot into Recovery partition with ADB.)
2. Fastboot, (Start Fastboot server.)
3. Normal. (Proceed to boot normally.)
Using Recovery Mode and Menu
When you boot the Recovery partition you will be meet with a failed Android icon on the stock Vernee release rom. ADB will be accessible from here. Note: The Recover menu will cause the ADB server to fail. If you want to display the recovery menu options then perform the following during the failed Android icon screen.
Buttons: [Top-Volume] + [Power-Button] pulsing till the menu appears.
Fastboot
If you plan to develop on your Apollo or to install future community roms then it's advisable to unlock your storage partitions. Unlocking will allow you to change partitions but doing so will void software warranty clauses, and in the process scrub all your personal data from the phone so it's best to do it before installing personal content.
To unlock the phone issue the following command through Fastboot. You will be asked to confirm.
Code:
fastboot oem unlock
Engineering Mode
Enter the following phone number in Android desktop
Code:
Dial *#*#3646633#*#*
Phone Test Options
Alternatively there is a phone test mode available at low level with less options. Whilst the phone is shutdown, press the following.
Buttons: [Bottom-Volume] + [Power-Button] for 8 Seconds.
A test menu will appear and is in simplified Chinese.
SIMS
If your phone is not receiving data over 4G or 3G, Google on another computer "apn" "YOURMOBILEPHONEPROVIDER" "YOURNATION". Example;
Code:
"apn" "vodafone" "uk"
You should find links to technical settings for your data provider's access. Then enter them in by navigating to;
Settings>More>Mobile network settings>Access point names>CLICK-YOUR-LOCKED-ON-PROVIDER>THEN-CONFIRM-SETTINGS
USB
Device USB Coding
Code:
System Mode:
ID 0e8d:201d MediaTek Inc.
ADB Mode:
ID 0e8d:2008 MediaTek Inc.
Fastboot Mode
ID 0bb4:0c01 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo
Microsoft Windows VCOM Drivers
On Microsoft systems you will need to have drivers installed so as to communicate with the Mediatek phone.
MediaTek DA USB VCOM (Android) Driver 3.0.1504.0 for Windows 7/Windows 8.1
MediaTek DA USB VCOM (Android) Driver 3.0.1504.0 for Windows 10
UART Ability?
I haven't opened the phone yet but if anyone does please capture images of the circuit board. If there are UART pins on the board it may have a root shell piped to the interface. A UART (universal asynchronous receiver/transmitter) in this sense is a device that couples serial communications port to USB to run a terminal over.
Vernee Official Rom Images & "Over The Air" Updates
Official Product Downloads/Support
VerneeX25_Recovery_OriginalStock_v1p0 (Thx to Relief66)
Download (2016-12) ROM "full_k15ta_a-ota-1482441792.zip"
Download (2017-01) ROM "full_k15ta_a-ota-1484567521.zip" (Creating .img from .dat files works!)
Download (2017-07) ROM "full_k15ta_a-ota-1499861676.zip"
Download (2017-07) OTA Patch "20170712201130-OTA.rar"
Note: "20170712201130-OTA.rar" is only designed to update "full_k15ta_a-ota-1482441792.zip" image.
Flashing Partitions
There are three main ways to flash;
1. using "Smart Phone Flash Tool",
2. Fastboot flash command,
3. via internal software like a root bash shell or routine from recovery.
Partition Table
Code:
system logical drive = 2621.44MB [= 2684354560 bytes = 5242880 x 512blocks]
recovery logical drive = 16.384MB
Scatter file from OTA
----------------------------
preloader 0x0
pgpt 0x0
recovery 0x8000
para 0x1008000
custom 0x1088000
expdb 0x13c88000
frp 0x14688000
nvcfg 0x14788000
nvdata 0x14f88000
metadata 0x16f88000
protect1 0x18f88000
protect2 0x19788000
seccfg 0x1a000000
oemkeystore 0x1a800000
proinfo 0x1aa00000
md1img 0x1ad00000
md1dsp 0x1c500000
md1arm7 0x1c900000
md3img 0x1cc00000
scp1 0x1d100000
scp2 0x1d200000
nvram 0x1d300000
lk 0x1d800000
lk2 0x1d880000
boot 0x1d900000
logo 0x1e900000
tee1 0x1f100000
tee2 0x1f600000
keystore 0x1fb00000
system 0x20800000
cache 0xc0800000
userdata 0xdb000000
flashinfo 0xFFFF0080
sgpt 0xFFFF0000
recovery.fstab
------------------
# mount point fstype device [device2]
/boot emmc boot
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p5
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p3
live fstab via "cat /fstab.mt6797"
------------------------------------------
# 1 "vendor/mediatek/proprietary/hardware/fstab/mt6797/fstab.in"
# 1 "<built-in>"
# 1 "<命令行>"
# 1 "vendor/mediatek/proprietary/hardware/fstab/mt6797/fstab.in"
# 20 "vendor/mediatek/proprietary/hardware/fstab/mt6797/fstab.in"
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/metadata,
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata /nvdata ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,formattable
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvcfg /nvcfg ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/custom /custom ext4 ro wait
/devices/mtk-msdc.0/11230000.msdc0* auto vfat defaults voldmanaged=sdcard0:auto
/devices/mtk-msdc.0/11240000.msdc1* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata
/devices/soc/11270000.usb3_xhci* auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/frp /persistent emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvram /nvram emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/proinfo /proinfo emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk /bootloader emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk2 /bootloader2 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/para /misc emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot /boot emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo /logo emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/expdb /expdb emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/seccfg /seccfg emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee1 /tee1 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee2 /tee2 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/scp1 /scp1 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/scp2 /scp2 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md1img /md1img emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md1dsp /md1dsp emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md1arm7 /md1arm7 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md3img /md3img emmc defaults defaults
Raw block partition label and user/group
-----------------------------------------------------
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/proinfo u:object_r:nvram_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/nvram u:object_r:nvram_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/nvdata u:object_r:nvdata_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/frp u:object_r:frp_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/expdb u:object_r:expdb_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/misc2 u:object_r:misc2_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/logo u:object_r:logo_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/para u:object_r:para_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/tee1 u:object_r:tee_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/tee2 u:object_r:tee_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/seccfg u:object_r:seccfg_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/userdata u:object_r:userdata_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/cache u:object_r:cache_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/recovery u:object_r:recovery_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/protect1 u:object_r:protect1_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/protect2 u:object_r:protect2_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/keystore u:object_r:keystore_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/oemkeystore u:object_r:oemkeystore_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/boot u:object_r:boot_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/persist u:object_r:persist_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/system u:object_r:system_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/nvcfg u:object_r:nvcfg_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/md1img u:object_r:md_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/md1dsp u:object_r:dsp_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/md1arm7 u:object_r:md_block_device:s0
/dev/block/platform/mtk-msdc\.0/[0-9]+\.msdc0/by-name/md3img u:object_r:md_block_device:s0
On my rooted phone I can check the UUID of the partitions. (You may need BusyBox installed to use blkid command!).
Code:
adb shell
su
blkid
displays;
Code:
/dev/block/loop0: LABEL="iAmCdRom" TYPE="iso9660"
/dev/block/loop1: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/zram0: TYPE="swap"
/dev/block/mmcblk0p3: LABEL="custom" UUID="0f1095f4-0ece-e656-b6ac-e2ce104d5722" TYPE="ext4"
/dev/block/mmcblk0p6: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p7: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p9: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p28: LABEL="system" UUID="da594c53-9beb-f85c-85c5-cedf76546f7a" TYPE="ext4"
/dev/block/mmcblk0p29: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p30: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk1p1: UUID="0508-0E13" TYPE="vfat"
Modifying Partitions
Modify partitions often means Users hacking the commercial roms and that means extracting out the important files to work with. The most important blocks are the system-partition which holds the operating system, then the recovery-partition which pole vaults Users with low level tools and abilities, like startup phone root powers. Noting many modern phone root modes, deploy on the recovery-partition rather than modify the system-partition, so as to retain full compatibility and retention of abilities, when conducting "Over the Air" / OTA updates from the manufacturer.
There are two popular platforms to hack on. 1. on native Linux including the phone itself, and 2. on a Microsoft Windows platform with Linux style utilities.
To ready a partition, to then modify it, and to then save it for flashing has many steps. One should obtain the manufacturer's rom or OTA update, to seek out the latest images and files to utilise.
In this example of hacking an official rom, we will be using "full_k15ta_a-ota-1484567521.zip". Utility executables are readily available in repositories related to your Linux distribution, like AUR on Archlinux.
Linux - ACCESSING SYSTEM IMAGE TO MODIFY
1.) Extract the zip file to a new folder. The directory should be something like this structure.
Code:
.../tinysys-scp.bin
.../logo.bin
.../lk.bin
.../md1rom.img
.../system.patch.dat
.../type.txt
.../custom.new.dat
.../custom
.../custom/cip-build.prop
.../custom/app-res
.../custom/app-res/quicksearchbox-res
.../custom/app-res/quicksearchbox-res/quicksearchbox-res.apk
.../custom/app-res/android-res
.../custom/app-res/android-res/android-res.apk
.../custom/app-res/browser-res
.../custom/app-res/browser-res/browser-res.apk
.../custom/app-res/launcher3-res
.../custom/app-res/launcher3-res/launcher3-res.apk
.../custom/media
.../custom/media/audio
.../custom/media/audio/notifications
.../custom/media/audio/notifications/Leaf.ogg
.../custom/media/audio/notifications/Pure.ogg
.../custom/media/audio/notifications/Triumph.ogg
.../custom/media/audio/notifications/Vernee_n002.ogg
.../custom/media/audio/notifications/The_time_tunne.ogg
.../custom/media/audio/notifications/Jump.ogg
.../custom/media/audio/notifications/Whisper.ogg
.../custom/media/audio/notifications/Vernee_n001.ogg
.../custom/media/audio/notifications/Cuckoo.ogg
.../custom/media/audio/notifications/Cleverer.ogg
.../custom/media/audio/notifications/Meteor.ogg
.../custom/media/audio/notifications/Bongo.ogg
.../custom/media/audio/notifications/Ripples.ogg
.../custom/media/audio/notifications/Whistle.ogg
.../custom/media/audio/notifications/Gift.ogg
.../custom/media/audio/alarms
.../custom/media/audio/alarms/ClassicAlarm.ogg
.../custom/media/audio/alarms/Waltz.ogg
.../custom/media/audio/alarms/Vernee_a001.ogg
.../custom/media/audio/alarms/GoodLuck.ogg
.../custom/media/audio/alarms/Foredawn.ogg
.../custom/media/audio/alarms/Vernee_a002.ogg
.../custom/media/audio/alarms/MorningSunShine.ogg
.../custom/media/audio/alarms/Walking_in_the_rain.ogg
.../custom/media/audio/ringtones
.../custom/media/audio/ringtones/Call_of_love.ogg
.../custom/media/audio/ringtones/Spring.ogg
.../custom/media/audio/ringtones/New_life.ogg
.../custom/media/audio/ringtones/Menuet.ogg
.../custom/media/audio/ringtones/Vernee_r004.ogg
.../custom/media/audio/ringtones/Heartbeat.ogg
.../custom/media/audio/ringtones/Vernee_r005.ogg
.../custom/media/audio/ringtones/Technology.ogg
.../custom/media/audio/ringtones/Longing.ogg
.../custom/media/audio/ringtones/Vernee_r002.ogg
.../custom/media/audio/ringtones/Vernee_r003.ogg
.../custom/media/audio/ringtones/Westlake.ogg
.../custom/media/audio/ringtones/Vernee_r001.ogg
.../custom/media/audio/ringtones/Progress.ogg
.../custom/media/audio/ringtones/Journey.ogg
.../custom/media/audio/ringtones/GuitarPop.ogg
.../custom/media/audio/ringtones/Cloud.ogg
.../custom/media/audio/ringtones/Capriccioso.ogg
.../custom/media/audio/ringtones/IceWorldPiano.ogg
.../custom/plugin
.../custom/plugin/FwkPlugin
.../custom/plugin/FwkPlugin/FwkPlugin.mpinfo
.../custom/plugin/FwkPlugin/FwkPlugin.apk
.../custom/plugin/Signatures
.../custom/plugin/Signatures/mplugin_guard.xml
.../custom/etc
.../custom/etc/resources.xml
.../custom/bootani
.../custom/bootani/shutanimation.zip
.../custom/bootani/bootanimation.zip
.../custom/customprop
.../custom/customprop/custom.prop
.../system.new.dat
.../custom.patch.dat
.../md1arm7.img
.../md3rom.img
.../preloader_k15ta_a.bin
.../md1dsp.img
.../scatter.txt
.../custom.transfer.list
.../file_contexts
.../boot.img
.../META-INF
.../META-INF/CERT.SF
.../META-INF/MANIFEST.MF
.../META-INF/CERT.RSA
.../META-INF/com
.../META-INF/com/android
.../META-INF/com/android/metadata
.../META-INF/com/android/otacert
.../META-INF/com/google
.../META-INF/com/google/android
.../META-INF/com/google/android/update-binary
.../META-INF/com/google/android/updater-script
.../trustzone.bin
.../system.transfer.list
.../sdat2img.py
2.) the images we are looking for are either the system-partition or the recovery-partition to modify. In this case there is only the system and it's held in the file "system.new.dat", a 1.6 gigabyte file. We know from the partition tables above that the system-partition is 2.6GB wide, so this image is either compressed or short. Most partitions deployed on Android for updating are compressed in what's called a sparse format.
We need to uncompress any sparse file before we can work with it or mount it, but the issue in this case is the image is also in "dat" structure, which means we need to unsparse using structured data held in "system.transfer.list". Here we use "sdat2img" executable to create the file "system_fullsize.img";
Code:
sdat2img system.transfer.list system.new.dat system_fullsize.img
Alternatively if the file was not a dat format, we could simply unsparse using;
Code:
simg2img system.img system_fullsize.img
3.) Now that we have the full image we can mount it as a file-system to tinker with it. Example of making a mount point and mounting it;
Code:
sudo mkdir /system
sudo mount -t ext4 -o loop ./system_fullsize.img /system/
You can now modify the image simply by changing the files in the directory mounted on. After changes you can save out and attempting to flash it back to the phone for your custom system.
Linux - CAPTURING THE MOUNT BACK TO AN IMAGE FILE
1.) After we have modified the mounted system-partition we need to save it back out for flashing if you want to see your changes live on the phone.
Labelling (If desired). We can name the mount to enforce block-labels. In this case the loop device was "loop0" used to mount the image. (Check which loop-device was used when performing this. eg: lsblk) Here we are going to label it "system"..
Code:
e2label /dev/loop0 system
It maybe important to set the partition UUID the same as the manufacturer uses so the the mounting process finds the correct partition to mount at boot. We know the system partitions UUID from the above discovery details;
Code:
UUID="da594c53-9beb-f85c-85c5-cedf76546f7a"
We can set the mounted image's UUID to suit the original before creating a new;
Code:
sudo tune2fs /dev/loop0 -U da594c53-9beb-f85c-85c5-cedf76546f7a
Here we capture out the device to an "ext4" format file-system image. The length option, being 2684354560 bytes. Labelling option "-a" with name "system".
Code:
sudo make_ext4fs -s -l 2684354560 -a system system_modded.img /system/
2.) To flash your image, Android's recent "fastboot" utility will allow for unsparse and sparsed images to be flashed. I have broken down the fastboot process into each step.
CAUTION: fastboot writes over your phone's partition blocks. If you are not skilled in this area of computing them research "fastboot" before use.
Note: current I have not found out why this process is incompatible with Vernee Apollo. The images I write back are not operational even though they flash properly. My hunch is that I may need to enforce an ISO/image UUID the same as the manufacturers, but I haven't tested this yet.
Code:
fastboot -w
fastboot format system
fastboot flash system ./system_modded.img
If we want to sparse the file before flashing;
Code:
img2simg system_modded.img system_modded_sparse.img
If we want to create a sparse dat structured image;
Code:
img2sdat ./system_modded.img
Linux - ACCESSING RECOVER IMAGE TO MODIFY
An Android recovery image is really three items in one image. There is a compressed kernel (zImage) used to run a recovery system, a ramdisk (initrd.img), and configuration file. The ramdisk "initrd.img" holds the operating system files used by the recovery kernel. Note the bootimage partition/image is a similar structure to a recovery-image.
If you need a similar development community then the Xiaomi Redmi Pro is a similar phone due to its Mediatek Helio x25 but it uses a different cameras, screen and sensors. Modifying and tweaking settings in their recovery images can work on your Vernee Apollo X25.
To extract the sub held files (bootimg.cfg, zImage, initrd.img);
Code:
abootimg -x recovery.img
To unpack a ramdisk "initrd.img";
Code:
mkdir initrd
cd initrd
sudo zcat ../initrd.img | cpio -idmv
To pack files whilst in your ramdisk directory ''/initrd";
Code:
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
To pack back up components into a recovery rom;
Code:
abootimg --create recovery_new.img -f bootimg.cfg -k zImage -r initrd.img
Alternatively;
Code:
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel ./zImage --ramdisk ./newramdisk.cpio.gz -o recovery_new.img
Software
Chainfire SuperSU Release Announcement
F-Droid. Alternative App Store for public domain software.
.

Known Recovery Image Developers
Cleopatra Bianchi
https://forum.xda-developers.com/general/rooting-roms/vernee-apollo-helio-x25-twrp-root-t3554788
Known ROM Developers
Cleopatra Bianchi
https://forum.xda-developers.com/general/rooting-roms/vernee-apollo-helio-x25-roms-fix-t3561019
Vernee Apollo X25 General Resource Sites
http://www.needrom.com/ Vernee/ApolloX25
.

Hardware
Protective Covers
Silicone and more rigid covers are becoming available for the Vernee Apollo. Make sure you don't get a Lite version as it wont fit.
Those looking for more range and are willing to mod, the Lenovo K5 Note is very similar in dimensions to the Apollo X25, but the headphone jack, volume and power buttons are slightly off. Modding a K5 Note case will require cutting holes for the headphone jack, buttons, speaker holes, and possibly for the flash. Clear covers will allow the flash to work. Make sure the camera and finger scanner is a complete open section on any K5 cover!
https://www.aliexpress.com/item/Ver...-Shell-Back-Cover-For-Vernee/32799796884.html

TWRP Vernee Apollo Helio X25
Cleopatra Bianchi said:
Click to expand...
Click to collapse
http://bbs.vernee.cc/forum.php?mod=viewthread&tid=1721&extra=page%3D1

Cleopatra Bianchi said:
http://bbs.vernee.cc/forum.php?mod=viewthread&tid=1721&extra=page%3D1
Click to expand...
Click to collapse
I left it up to you to post. I hope people comment on what they think. I'm working on my own images so I can't install others at the moment to give an opinion. Readers please note I can't verify the security on this share. Do not take any compromising actions.
I'm super busy so not sure when I will have my own solutions.

How I wish I had more knowledge. This piece of Hw (Raw Hw?) has a lot of potential, but lacks interest of any developer adapt/adopt it....
The conditions are there (lets hope the owners free the code, as they have done with its small brother), and let's hope there are enough and good drivers for the chosen Hw.
Just to encourage your efforts.
Regards

I agree
lots of good hardware and poor software...I hope in this community

At the moment I found these "bad" things about this phone:
1) you can't choose to view the battery percentage in the upper bar
2) you have to set the APN manually or you can't use internet
3) you can't turn volume up or down if the screen is switched off

I've kind of hit a wall with modding the system image to root it. The system images I produce are just not compatible with flashing. They flash but no desktop runs on the phone. Tried both sparse and raws. and I've got the partition size correct. Mount point is set properly to "system" and they're ext4 images.
I'm building Chainfire's version of ext4_utils, specifically the make_ext4fs util. If that doesn't work then I'll build Google's version. Long process as you need SELinux headers which takes ages to install. There maybe a bug in older versions that's causing the trouble. Other thoughts, there maybe a different padding method or bit plane for storing file system nodes. I may need SELinux builds of executables just to get the job done as I did notice in a hex.diff that the original image has SELinux stamps in it. I need more investigation to know why that's so.
It would be nice if Cleopatra Bianchi chimed in if She knows the issue or has even been down this road before, so to speak.

Hi, E8
Do not know even if this could be valuable, but the sources of the lite version are there. I suppose they are taking the same engineering approaches with the big brother... or not...
but would check
Regards

jrotaetxe said:
Hi, E8
Do not know even if this could be valuable, but the sources of the lite version are there. I suppose they are taking the same engineering approaches with the big brother... or not...
but would check
Regards
Click to expand...
Click to collapse
I'll look into it as the scripts may indicate the process to image creation. Cheers.

TWRP and ROOT - successfully tested !
https://forum.xda-developers.com/general/rooting-roms/vernee-apollo-helio-x25-twrp-root-t3554788

Such a cool phone, but sending it back. Doesn't work with US carriers

Stock firmware in Flash Tool
Cleopatra Bianchi said:
TWRP and ROOT - successfully tested !
https://forum.xda-developers.com/general/rooting-roms/vernee-apollo-helio-x25-twrp-root-t3554788
Click to expand...
Click to collapse
I look forward to flash the stock firmware in Flash Tool. I foolishly made a phone of brick, all backups lost.

stock firmware
myextasy said:
I look forward to flash the stock firmware in Flash Tool. I foolishly made a phone of brick, all backups lost.
Click to expand...
Click to collapse
A working stock firmware will be here very soon.
Please be patient, I am working on that.

Cleopatra Bianchi said:
A working stock firmware will be here very soon.
Please be patient, I am working on that.
Click to expand...
Click to collapse
Anyway to unlock bands to get it working in US ???

myextasy said:
I look forward to flash the stock firmware in Flash Tool. I foolishly made a phone of brick, all backups lost.
Click to expand...
Click to collapse
You can easily restore the phone using the official zip rom. Place it on a micro sdcard and install via the Bootloader menu. Instructions are on the forst comment on how to get to the bootloader menu and then recovery. If you're destroyed your recovery partition but still have fastboot access then you can use the system image within the official rom to flash the system partition with a bit of modifications.
I've been super busy so I haven't had the time to work on my own version of the TWRP Recovery.

How can I find the drivers ? When I google search I only find the one for Apollo lite

Do not believe you can "unlock" US bands, as they differ from EU/ASIA system.
Anyway, trying is (almost) free. The worst thing can happen is a brick
Regards

OnePlus3 (A3003), problems with upgrading / installing Lineage 14.1 20170511

Phone: OnePlusThree (msm8996) / A3003
Bootloader: Unlocked
DM-Verity: "Fixed" (i.e. don't get any warnings anymore)
OS: Ubuntu 16.04 w. working adb/fastboot from Google's "platform-tools"
Lineage version: Lineage 14.1 20170511 Nightly
TWRP version: 3.1.0.0
Also tried with:
OnePlus recovery tool: recovery_op3.img
OxygenOS: OnePlus 3 OxygenOS Open Beta 15
Other packages:
Root: addonsu-arm64-signed.zip (170126)
OpenGAApps: Arm 64, 7.1, Pico (170514)
Hi!
Had a working installation of Lineage 14.1 with a build from late April and wanted to update to the latest version.
Made a nandroid backup via TWRP and backed up via Titanium Backup. However I have ran into massive problems trying to get Lineage to work again.
I won't take up a lot of space here (and I honestly dont remember all the steps) by going into detail what I have done but here is my current setup:
Flashed OnePlus recovery tool, made a complete wipe (apps and everything) and then used adb sideload to sideload the official latest Oxygen build (Open Beta 15).
It reports everything went OK and I reboot into system. I get to enter my PIN and the OnePlus setup starts, select a fresh install and it boots into the OS as normal.
Enable USB-debugging and then boot into flashboot to flash TWRP. The flash reports OK. I shut down the phone and then start it into recovery using "volume down + power".
TWRP boots successfully. I swipe to allow modifications to the "system"-partition and push Lineage, OpenGAApps and addonsu to /sdcard/.
Advanced wipe > System, data, cache. No errors.
Install > Queue the .zips after one another, first Lineage then OpenGAApps and then addonsu > swipe.
"Patching system image unconditionally" and then it stalls around 80% or so. I still see the "blue animation" so it seems to be working / processing but I've tried to leave it as it is for hours and nothing else happens. I remember when it used to work and then it never got stuck on any step but executed all the installations one after each other.
Have I missed anything or doing something wrong? Not an expert in flashing roms but its a really annoying issue, haven't been able (since I want to be able to use Lineage, stock Oxygen seems to work but need to be able to get root and restore my Titanium Backup) my phone for around a week.
Any help is appreciated, if you need any logs etc. then I'll be happy to upload them.
Best Regards - TheSwede86

TheSwede86 said:
Phone: OnePlusThree (msm8996) / A3003
Bootloader: Unlocked
DM-Verity: "Fixed" (i.e. don't get any warnings anymore)
OS: Ubuntu 16.04 w. working adb/fastboot from Google's "platform-tools"
Lineage version: Lineage 14.1 20170511 Nightly
TWRP version: 3.1.0.0
Also tried with:
OnePlus recovery tool: recovery_op3.img
OxygenOS: OnePlus 3 OxygenOS Open Beta 15
Other packages:
Root: addonsu-arm64-signed.zip (170126)
OpenGAApps: Arm 64, 7.1, Pico (170514)
Hi!
Had a working installation of Lineage 14.1 with a build from late April and wanted to update to the latest version.
Made a nandroid backup via TWRP and backed up via Titanium Backup. However I have ran into massive problems trying to get Lineage to work again.
I won't take up a lot of space here (and I honestly dont remember all the steps) by going into detail what I have done but here is my current setup:
Flashed OnePlus recovery tool, made a complete wipe (apps and everything) and then used adb sideload to sideload the official latest Oxygen build (Open Beta 15).
It reports everything went OK and I reboot into system. I get to enter my PIN and the OnePlus setup starts, select a fresh install and it boots into the OS as normal.
Enable USB-debugging and then boot into flashboot to flash TWRP. The flash reports OK. I shut down the phone and then start it into recovery using "volume down + power".
TWRP boots successfully. I swipe to allow modifications to the "system"-partition and push Lineage, OpenGAApps and addonsu to /sdcard/.
Advanced wipe > System, data, cache. No errors.
Install > Queue the .zips after one another, first Lineage then OpenGAApps and then addonsu > swipe.
"Patching system image unconditionally" and then it stalls around 80% or so. I still see the "blue animation" so it seems to be working / processing but I've tried to leave it as it is for hours and nothing else happens. I remember when it used to work and then it never got stuck on any step but executed all the installations one after each other.
Have I missed anything or doing something wrong? Not an expert in flashing roms but its a really annoying issue, haven't been able (since I want to be able to use Lineage, stock Oxygen seems to work but need to be able to get root and restore my Titanium Backup) my phone for around a week.
Any help is appreciated, if you need any logs etc. then I'll be happy to upload them.
Best Regards - TheSwede86
Click to expand...
Click to collapse
Someone had a similar problem where the flash stuck at about 50%, it turned out TWRP didn't have enough space to unpack the ROM but doesn't give any indication. How much space do you have available? Deleting some files to create more space fixed the issue.

IronRoo said:
Someone had a similar problem where the flash stuck at about 50%, it turned out TWRP didn't have enough space to unpack the ROM but doesn't give any indication. How much space do you have available? Deleting some files to create more space fixed the issue.
Click to expand...
Click to collapse
What I think is weird is that when I flashed the official OnePlus Recovery I did a complete wipe before sideloading their official rom and when booting into TWRP I did the usual "system+data+cache"-wipe.
So space shouldn't be an issue.
However when I rebooted into recovery I got "Failed to mount '/system' (Invalid argument)".
I copied the logs from TWRP and please see them attached here and as you say "/system" seems to be have no space whatsoever allocated?
Code:
/system | /dev/block/sde20 | [B]Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB[/B]
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/sde20
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
Edit:
Quite interesting, if I use OnePlus official recovery and sideload the latest official build and then flash TWRP I get this when extracting the logs:
Code:
/system | /dev/block/sde20 | [B]Size: 2868MB Used: 2507MB Free: 360MB Backup Size: 2507MB[/B]
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/sde20
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
Even if I go about doing Wipe > Advanced Wipe > System, Cache and Data and then dump the logs again I get the same results.
The same if I use "Use rm -rf instead of formatting". Now as a newbie in this I guess it does not successfully wipe my "/system" partition even though I don't get any errors and there are no error handling if there is insufficient space in TWRP so it just hangs indefinitely? How can I go about formatting "/system" so I can install Lineage and why come the stock Oxygen OS works (via adb sideload)?

[solved] Recovery: "Unable to mount storage"

I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.

Fabian R�ling said:
I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.
Click to expand...
Click to collapse
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.

SubwayChamp said:
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.
Click to expand...
Click to collapse
I have never heard of a "super partition". How do I do that?

Fabian R�ling said:
I have never heard of a "super partition". How do I do that?
Click to expand...
Click to collapse
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.

SubwayChamp said:
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.
Click to expand...
Click to collapse
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.

Fabian R�ling said:
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.
Click to expand...
Click to collapse
Super partition is where some logical partitions are grouped like system, vendor, odm, product, etc.; it depends on the device we're talking about.
As you got a used device, it seems that the last owner did some stuff with it, probably unlocked bootloader (then relocked it) and mess with some custom ROMs (maybe). You can totally fix it by flashing the stock ROM and starting from there, being sure first that you can log in without issues in Google Play (that your account is authorized).
To have this partition readable, you may read this https://forum.xda-developers.com/t/...-mount-system-rw-super-rw-read-write.4247311/ in case this doesn't solve flashing the super partition it is a part of the process to flash the stock ROM.

SubwayChamp said:
flashing the super partition it is a part of the process to flash the stock ROM
Click to expand...
Click to collapse
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.

Fabian R�ling said:
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.
Click to expand...
Click to collapse
You can update through the stock recovery in case your TWRP have actually some issues, flash the stock recovery through fastboot (get it from your stock ROM) and then do the sideload through stock recovery, it's probable that the stock recovery can mount super partition and made readable again the system files that´s within, or you can simply flash this or that partition using fastboot commands, for this you need an unlocked bootloader, nothing more.
BTW did you try formatting data?.
And this tool should work for you https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4217855/

That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.

Fabian R�ling said:
That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.
Click to expand...
Click to collapse
The ROM to be flashed through recovery contains a payload.bin file within others one, this file can be unpacked, not sure if it contains a recovery image though, but you should get it from the full ROM that in some variant comes in oplus format and can be decrypted too, this full ROM contains all the images, it's useful to unbrick a OP device.
Linux doesn't have a counterpart of the Windows applications for smartphones and vice versa in regard to Android development, this is one of the reasons why I have a dual boot machine.
As per the last part it could be an issue from your browser, I didn't have this kind of behaviors from the XDA site.

For "boot.img" and "recovery.img" in the "EU" and the "global" section I get "fastboot: error: boot partition is smaller than boot image". The Magisk version can be installed, but then I get a Qualcomm crash screen when I try to actually start it.

Apparently I have a "OnePlus 7 Pro", not a "OnePlus 7T Pro". I bought that accidentally, but the specs are fine. Actually following the instructions for the correct device worked, who would have thought…