Related
lg g2 d802 İMEİ NULL REPAİR
We will repair phone with only 2 programs. You needn't QPST, qcn, etc.
I already haven't qcn backup, so i failed to back up and change it.
İf you did number 4 before, just do number 2, reset phone. Your imei will come back.
Necessary programs: I used theese, you can use newer versions.
Minimal ADB Fastboot v1.1.3
EFS Professional 2.1.80 beta
1-)Connect the phone "Lg Software", you will see in device manager (com&lpt) port.
Driver I used: LGUnited MobileDriver_S51MAN313AP22_ML_WHQL_Ver_3.13.2
Device manager -> androidnet usb modem #2 -> modem -> The fastest connection=115200.
LG G2 D802, MSM7945, SNAPDROGAN 800, ANDROİD 4,4,2, V20c, Made in Taiwan.
2-)Phone should be root.
İf your phone doesn't seem with root in ADB FAST BOOT: uninstall supersu, install again form google play.
I uninstalled supersu, installed superuser# from google play.
3-)We will just here enter 7 commands.
Install ADB FASTBOOT and open, enter commands one by one.
........Enter “adb shell”. You will see *Daemon not running, starting it now on port 5037 *Daemon started
succsfully* [email protected]:/$ .
........Enter “su”. İf you see 'not found', your phone is not root.
........Enter “setprop sys.usb.config diag,adb”. Port will opened.
........Enter "ls -al /dev/block/platform/msm_sdcc.1/by-name".
After this command, you will look for: modemst1, modemst2, fsg
lrvrwxrwx root root 1970-01-03 03:31 modemst1 -> /dev/block/mmcblk0p10
cblk0p10
lrvrwxrwx root root 1970-01-03 03:31 modemst2 -> /dev/block/mmcblk0p11
cblk0p11
lrvrwxrwx root root 1970-01-03 03:31 fsg -> /dev/block/mmcblk0p16
p16
İmportant is last numbers here, mine is 10,11,16. You just change theese numbers with yours.
Enter 3 commands below one by one, by changing only with your last numbers.
......dd if=/dev/zero of=/dev/block/mmcblk0p10
......dd if=/dev/zero of=/dev/block/mmcblk0p11
......dd if=/dev/zero of=/dev/block/mmcblk0p16
If you didn't do these commands, qv nv items fails.
4-)Go into Qualcom Nv tools in EFS PROFESSİONAL.
You will see LG Andoidnet Usb serial port (comx) on top and connect.
If it is not connected, go to phone: Settings->general->pc connection->tethering and connect.
If it still fails, get empty "send pc" box in qualcom nv tools program and connect.
İf you connected, read phone info and go into secure ops. tab.
You will see 3 boxes under MEİD/ESN/İMEİ REPAİR in secure ops tab.
We will just fill them and write phone.
First we should learn Meid hex, esn hex, imei dec numbers from meidconverter.com
Meid hex is the first 14 digits of our 15-digits IMEI number.
Write your meid and convert in site. You will see screen below.
Format Value
Hex ESN
Decimal ESN
Hex MEID 3xxxxxxxxxx8
Dec MEID 08xxxx7845xxx3448
Pseudo Hex ESN 80DBxxx7
Pseudo Dec ESN 12xxxxxx207
IMEI
MetroPCS SPC 7xxxx0
We just need here: Pseudo Hex ESN. Because it gives us our 'esn hex' value, 8 digits mixed with letters.
'Meid hex' is the first 14 digits of our 15-digits IMEI number.
'İmei dec' is our 15 digit imei numbers we knew.
Write these in Nv TOOLS, tick the boxes and write the phone.
Finished.... When you reset the phone, your imei will come back.
If your phone keeps restarting, first press power button 30 seconds. You sure phone turned off exactly.
Press and hold volume+, plug suitable usb cable until download mode.
While you are connected pc in download mode, use B2CAppSetup program.
my lg g2 d802 imei turned null after ungrading from kitkat to lollipop
whn i enter the command
"lrvrwxrwx root root 1970-01-03 03:31 modemst1 -> /dev/block/mmcblk0p10
cblk0p10"
i get an error
"tmp-mksh: lrvrwxrwx: not found"
please help
everything is ok but when i was click on read phone info one error is showing phone lost please help.......
Hi All,
"fastboot erase all" command has erased the following partitions which are related to IMEI information :crying:
hob, dhob, fsc.
In 4.4.4 Kitkat kernel the above partitions were reflected at locations :
hob -- dev/block/platform/msm_sdcc.1/by-name/hob
dhob -- dev/block/platform/msm_sdcc.1/by-name/dhob
fsc -- dev/block/platform/msm_sdcc.1/by-name/fsc
In AOSP 5.1 Lollipop, i have found the below location where my motorola getvar variables reside .
imei -- proc/config/imei ----------------> which contains 3 files each of 0.0kb
If we found a way to change kernel to read "fastboot getvar imei" and write into path "/proc/config/imei" in 5.1 lollipop or "dev/block/platform/msm_sdcc.1/by-name/hob" in 4.4.4 Kitkat,
Our biggest problem will be solved ..
After comparing folder structure of another working MOTO E
srikanth979 said:
Hi All,
"fastboot erase all" command has erased the following partitions which are related to IMEI information :crying:
hob, dhob, fsc.
In 4.4.4 Kitkat kernel the above partitions were reflected at locations :
hob -- dev/block/platform/msm_sdcc.1/by-name/hob
dhob -- dev/block/platform/msm_sdcc.1/by-name/dhob
fsc -- dev/block/platform/msm_sdcc.1/by-name/fsc
In AOSP 5.1 Lollipop, i have found the below location where my motorola getvar variables reside .
imei -- proc/config/imei ----------------> which contains 3 files each of 0.0kb
If we found a way to change kernel to read "fastboot getvar imei" and write into path "/proc/config/imei" in 5.1 lollipop or "dev/block/platform/msm_sdcc.1/by-name/hob" in 4.4.4 Kitkat,
Our biggest problem will be solved ..
Click to expand...
Click to collapse
The below mentioned paths:
dev/block/platform/msm_sdcc.1/by-name/hob --- which will be unavailable from lollipop has nothing to do with IMEI as they have same files when we flash stock 4.4.4 firmware
proc/config/imei -- contains 3 files (ascii, *** , raw) each with 0.0 kb ---- which is of no use for us
proc/config/ -- have all the folders and files identical to unbricked and bricked phone --- again no use for us
I have found some files related to radio missing in "fastboot erase all" mobiles
{not sure whether these below files are missing after flashing Stock firmware but doesn't exist in PA custom rom}
init.mmi.rc
init.mmi.radio.sh
/pds
Required :
- Driver Qualcomm for Windows
- QPST_2.7.422.zip
- Driver ADB Installer
- Modem Lenovo A6000/A6000+ include ADB fastboot
- Extrac Modem in drive C:\adb and open the folder
** Edit file qcn use HxD change IMEI and Convert IMEI
SIM 1
Sector 343 Offset 0002AE50 point 00-08
Change 08 8A 76 21 04 22 57 85 45 adjust to you IMEI-1
SIM 2
Sector 188 Offset 000178E0 point 00-08
Change 08 8A 76 21 04 22 57 85 26 adjust to you IMEI-2
** Step change IMEI :
1. Open Convert IMEI
2. Write you IMEI-1 and klik Convert
3. Open HxD
4. Press Ctrl + F write/copas 08 8A 76 21 04 22 57 85 45 Datatype Hex-values Direction All - Ok
5. Replace it with IMEI-1 numbers convert results
6. Write you IMEI-2 and klik Convert
7. Open HxD
8. Press Ctrl + F write/copas 08 8A 76 21 04 22 57 85 26 Datatype Hex-values Direction All - Ok
9. Replace it with IMEI-2 numbers convert results
10. Close HxD and save file qcn
{
"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"
}
** For those who use stock rom not need root can be directly executed steps :
1. Install driver qualcomm, qpst, adb installer
2. Open the folder C:\adb
3. Press and hold down the Shift + Right Click - Open command windows here
4. Sign in fastboot mode button (vol- & power) and type :
fastboot erase modem (enter)
fastboot erase modemst1 (enter)
fastboot erase modemst2 (enter)
fastboot flash modem NON-HLOS.bin (enter)
fastboot flash modem modemst1.bin (enter)
fastboot flash modem modemst2.bin (enter)
5. Turn off the phone remove the battery
6. Sign test mode button (vol+ & Power)
7. Open QPST software download
8. Tab Restore
9. Browse PORT Qualcomm Diag
10. If you already connect, browse file QCN
11. Select the edited file QCN use hex editor
12. Tick Allow phone/file ESN mismatch
13. Start (wait for the process)
14. Reboot phone
15. Check the IMEI
16. Check signal SIM-1 the WCDMA/LTE only
17. Finished :laugh:
** For those who use custom rom / are not able to enter the test mode must root stock rom steps:
1. Root
2. Open SuperSU settings default access to Grant
3. Turn off the phone
4. Proceed to step 1 to 5
5. Turn on the phone
6. Install Terminalemulator.apk
7. Open terminalemulator type su (enter)
8. Type setprop sys.usb.config diag, adb (enter)
9. Continue to restore files qcn step 7 to finish
Special thanks :
- Allah SWT.
- Carlos Spitzer
- fawazahmed0
- Robby Primarizal
- Hanif Nurul Huda
- Amri Gadroen
- All member (OFFICIAL INDONESIA) LENOVO A6000 INA
@zround - Just in case, you are feeling low due to no response from anyone. Brother, what you did was a much much needed thing, as many of the A6000 users are having IMEI problems on flashing custom ROMs. This thread is definitely a life saver for the guy having IMEI issue.
Sometimes, you don't get much appreciation from others in the beginning (has happened with me), but that doesn't mean you stop doing so.
So, all I wanna say is "thanks" and I really appreciate what you did.
:silly:
sasukay said:
@zround - Just in case, you are feeling low due to no response from anyone. Brother, what you did was a much much needed thing, as many of the A6000 users are having IMEI problems on flashing custom ROMs. This thread is definitely a life saver for the guy having IMEI issue.
Sometimes, you don't get much appreciation from others in the beginning (has happened with me), but that doesn't mean you stop doing so.
So, all I wanna say is "thanks" and I really appreciate what you did.
:silly:
Click to expand...
Click to collapse
@sasukay if there is no response means i think they managed to restore IMEI Lenovo A6000/+ in my way, :angel: i'm not proud of the appreciation and responses but can share and help others who seemed to me it was really fun.
let's drink a cup of coffee so as not to panic
zround said:
@sasukay if there is no response means i think they managed to restore IMEI Lenovo A6000/+ in my way, :angel: i'm not proud of the appreciation and responses but can share and help others who seemed to me it was really fun.
let's drink a cup of coffee so as not to panic
Click to expand...
Click to collapse
Hehhehhe.....I was just being dramatic... :silly:
hi sir,
i have lenovo a 6000.problem both imei null .when i try to write the qcn from ur guide.but in ur 9th step when i select the diag phone it shows no phone connected in qpst window.any solution please.
rajendrakumar said:
hi sir,
i have lenovo a 6000.problem both imei null .when i try to write the qcn from ur guide.but in ur 9th step when i select the diag phone it shows no phone connected in qpst window.any solution please.
Click to expand...
Click to collapse
if you use a stock rom then how to enable diag port android to turn off the device to unplug the battery and then press and hold the button (vol + & power) until the entrance test mode and plug the USB cable
or
by turning on the device (root) pairs terminalemulator.apk open to write:
su
setprop sys.usb.config diag, adb
restore qcn :good:
This saved my life thank you so much. Love from philippines bro
Unable to mount /modem
Bro.. ini udah ikutin sampe step 5, lalu pas gua nyalain malah stuck di logo booting. Coba clear cache via TWRP ada tulisan "Unable to mount /modem". Kira2 itu knp ya ? hehehe masih noob
waw steady
LYudhistira said:
Bro.. ini udah ikutin sampe step 5, lalu pas gua nyalain malah stuck di logo booting. Coba clear cache via TWRP ada tulisan "Unable to mount /modem". Kira2 itu knp ya ? hehehe masih noob
Click to expand...
Click to collapse
Step :
Masuk fastboot dan erase semua partisi, (boot, userdata, cache, system, modem, modemst1, modemst2)
Flash stock rom Lollipop via qfil qpst atau qualcomm downloader
Root
Masuk fastboot dan eksekusi
fastboot erase modem
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash modem modemst1.bin
fastboot flash modem modemst2.bin
Restore qcn
Hello, my imei's are good but error in network (cannot connect to selected network ) after writing qcn (without editing ) only SIM 1 worked with network but sim 2 not working > but after editing with my imei's no network .. any suggestions i need booth sims to work!?
Sobaro said:
Hello, my imei's are good but error in network (cannot connect to selected network ) after writing qcn (without editing ) only SIM 1 worked with network but sim 2 not working > but after editing with my imei's no network .. any suggestions i need booth sims to work!?
Click to expand...
Click to collapse
- That's because the modem partition problem,
- try
fastboot erase modem
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash modem modemst1.bin
fastboot flash modem modemst2.bin
- after that restore qcn already in the edit imei previous,
if still not successful,
then delete all partitions (boot, splash, userdata, cache, system) via fastboot, and then flash a stock rom via qfil or qualcomm downloader continued upgrading to latest stock rom, then restore qcn.
thanx that worked for me , now i get the two sims to work like a charm but still second imei is showing null !! i have no problem as long as sims are working but it is good if some one give a reason! thanx in advance
wrongly restored efs,modem... partitions from a lenovo a6000+ to another a6000
wrongly restored efs,modem... partitions (using TWRP) from a lenovo a6000+ to another a6000
i have no backups of the corresponding partitions of this phone
now phone showing imei null and sim detection errors also ui getting unstable and services are unstable in stock rom (most times) when flashed using qualcomm downloader & bootloops in other some custom roms.
fastboot,recovery etc of the phone is perfectly working.
when i did writing the altered qcn (with corresponding imei) via qpst i got just errors.
can anyone help me troubleshoot this ??
https://drive.google.com/file/d/0BwFcGoIexiPed210VXdnY2xUYU0/view?usp=sharing
zround said:
Required :
- Driver Qualcomm for Windows
- QPST_2.7.422.zip
- Driver ADB Installer
- Modem Lenovo A6000/A6000+ include ADB fastboot
- Extrac Modem in drive C:\adb and open the folder
** Edit file qcn use HxD change IMEI and Convert IMEI
SIM 1
Sector 343 Offset 0002AE50 point 00-08
Change 08 8A 76 21 04 22 57 85 45 adjust to you IMEI-1
SIM 2
Sector 188 Offset 000178E0 point 00-08
Change 08 8A 76 21 04 22 57 85 26 adjust to you IMEI-2
** Step change IMEI :
1. Open Convert IMEI
2. Write you IMEI-1 and klik Convert
3. Open HxD
4. Press Ctrl + F write/copas 08 8A 76 21 04 22 57 85 45 Datatype Hex-values Direction All - Ok
5. Replace it with IMEI-1 numbers convert results
6. Write you IMEI-2 and klik Convert
7. Open HxD
8. Press Ctrl + F write/copas 08 8A 76 21 04 22 57 85 26 Datatype Hex-values Direction All - Ok
9. Replace it with IMEI-2 numbers convert results
10. Close HxD and save file qcn
** For those who use stock rom not need root can be directly executed steps :
1. Install driver qualcomm, qpst, adb installer
2. Open the folder C:\adb
3. Press and hold down the Shift + Right Click - Open command windows here
4. Sign in fastboot mode button (vol- & power) and type :
fastboot erase modem (enter)
fastboot erase modemst1 (enter)
fastboot erase modemst2 (enter)
fastboot flash modem NON-HLOS.bin (enter)
fastboot flash modem modemst1.bin (enter)
fastboot flash modem modemst2.bin (enter)
5. Turn off the phone remove the battery
6. Sign test mode button (vol+ & Power)
7. Open QPST software download
8. Tab Restore
9. Browse PORT Qualcomm Diag
10. If you already connect, browse file QCN
11. Select the edited file QCN use hex editor
12. Tick Allow phone/file ESN mismatch
13. Start (wait for the process)
14. Reboot phone
15. Check the IMEI
16. Check signal SIM-1 the WCDMA/LTE only
17. Finished :laugh:
** For those who use custom rom / are not able to enter the test mode must root stock rom steps:
1. Root
2. Open SuperSU settings default access to Grant
3. Turn off the phone
4. Proceed to step 1 to 5
5. Turn on the phone
6. Install Terminalemulator.apk
7. Open terminalemulator type su (enter)
8. Type setprop sys.usb.config diag, adb (enter)
9. Continue to restore files qcn step 7 to finish
Special thanks :
- Allah SWT.
- Carlos Spitzer
- fawazahmed0
- Robby Primarizal
- Hanif Nurul Huda
- Amri Gadroen
- All member (OFFICIAL INDONESIA) LENOVO A6000 INA
Click to expand...
Click to collapse
Using Window 10, I'm not able to perform 1s step) Shift + click anywhere in folder, I think driver is not supported
2) not able to install terminal emulator bcz unknown source blocked and not working .
I edited the QCN file but unable to move forward from first step,
What should I do,
No communiction device , no imei, no bluetootgh, no wifi.
Should I use windows 7? Also how to install terminal apk if unknown source is not getting enabled for security purpose? Can I perform these steps on MM custom roms?
zround said:
Step :
Masuk fastboot dan erase semua partisi, (boot, userdata, cache, system, modem, modemst1, modemst2)
Flash stock rom Lollipop via qfil qpst atau qualcomm downloader
Root
Masuk fastboot dan eksekusi
fastboot erase modem
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash modem modemst1.bin
fastboot flash modem modemst2.bin
Restore qcn
Click to expand...
Click to collapse
Bro ganteng...
Abis ngikutin langkah tersebut di atas
Ane malah got Baseband: Unknown
Panik...
Trust flash page Downloaded yg Ada do ....kitkat_ROW.zip
baseband balik...
Imei Null
Trus Masukin imei pake program imei writter
Jadi
Normal
Tapi "tetep no service"
What's should I do ya Gan?
Any other method Kali Gan...
BTW... Makasih banyak udah menginspirasi
rifky said:
Bro ganteng...
Abis ngikutin langkah tersebut di atas
Ane malah got Baseband: Unknown
Panik...
Trust flash page Downloaded yg Ada do ....kitkat_ROW.zip
baseband balik...
Imei Null
Trus Masukin imei pake program imei writter
Jadi
Normal
Tapi "tetep no service"
What's should I do ya Gan?
Any other method Kali Gan...
BTW... Makasih banyak udah menginspirasi
Click to expand...
Click to collapse
Lollipop only om bosku, :laugh:
pankajy said:
Using Window 10, I'm not able to perform 1s step) Shift + click anywhere in folder, I think driver is not supported
2) not able to install terminal emulator bcz unknown source blocked and not working .
I edited the QCN file but unable to move forward from first step,
What should I do,
No communiction device , no imei, no bluetootgh, no wifi.
Should I use windows 7? Also how to install terminal apk if unknown source is not getting enabled for security purpose? Can I perform these steps on MM custom roms?
Click to expand...
Click to collapse
Try opening of adb cmd wear this in windows 10
- Flash stock rom lollipop
- Then follow these instructions
If you still can not, then tried to use windows 7 because I put windows 7 when executed
zround said:
Lollipop only om bosku, :laugh:
Click to expand...
Click to collapse
thanks...
AWALE PANCEN LOLLIPOP Gan
it is lollipop lho...
i decide to flash KITKAT because, the BaseBand Unknown show up after trying flash it back with lollipop Bro...
ngono lho
but finally it is back to lollipop again now, of course with All time "No Service" message
yesterday... i try to do all those wonderfull steps of yours again...
but alhamdulillaah... i have no luck... yet
actually... what is the lolllipop version of the phone should be to do those step you wrote
because i did it with my A6000 using the latest lollipop 5.0.2 / Kraft-A6000_S061_100727, is it matter? (singing Nothing Else Matters)
and would you please checkput my attachment please, did you see anything wrong there?
btw, where did you get those modem, modemst1, modemst2 & non-hlos bin files from? would you mind share it with us
always thanks in advanced
Sobaro said:
thanx that worked for me , now i get the two sims to work like a charm but still second imei is showing null !! i have no problem as long as sims are working but it is good if some one give a reason! thanx in advance
Click to expand...
Click to collapse
really? you did it?
so glad to know that :good:
congrat man
would you please tell me what version of firmware do you have?
mine is like in the attachment
Thanks in advance
This page is trying to find out which partition is for what ?
Code:
Model: MMC P1J95K (sd/mmc)
Disk /dev/block/mmcblk0: 15302656s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131072s 262143s 131072s fat16 modem
2 262144s 265215s 3072s tunning
3 265216s 267263s 2048s traceability
4 267264s 267265s 2s fsc
5 267266s 267281s 16s ssd
6 267282s 268305s 1024s sbl1
7 268306s 269329s 1024s sbl1bak
8 269330s 270353s 1024s rpm
9 270354s 271377s 1024s rpmbak
10 271378s 272401s 1024s tz
11 272402s 273425s 1024s tzbak
12 273426s 275473s 2048s pad
13 275474s 276497s 1024s hyp
14 276498s 277521s 1024s hypbak
15 277522s 280593s 3072s modemst1
16 280594s 283665s 3072s modemst2
17 283666s 285713s 2048s simlock
18 285714s 288785s 3072s efsdata
19 393216s 393279s 64s DDR
20 393280s 396351s 3072s fsg
21 396352s 396383s 32s sec
22 396384s 398431s 2048s aboot
23 398432s 400479s 2048s abootbak
24 400480s 466015s 65536s boot
25 466016s 531551s 65536s recovery
26 531552s 5898239s 5366688s ext2 system
27 5898240s 5963775s 65536s ext4 persist
28 5963776s 6004735s 40960s reserved
29 6004736s 6021119s 16384s splash
30 6021120s 6062079s 40960s ext4 tctpersist
31 6062080s 6082559s 20480s ext4 hdcp
32 6082560s 6082575s 16s fota
33 6082576s 6606863s 524288s ext4 cache
34 6606864s 6608911s 2048s misc
35 6608912s 6613007s 4096s persistent
36 6684672s 6686719s 2048s devinfo
37 6815744s 6816767s 1024s keystore
38 6816768s 6816831s 64s config
39 6816832s 6816959s 128s oem
40 6816960s 6823151s 6192s redbend
41 6823152s 6825199s 2048s ciqbp
42 6825200s 6827247s 2048s ciqap
43 6827248s 15302622s 8475375s ext4 userdata
25. recovery - partition to be used for recovery boots this is allinone image to let you boot when all door closed.
26. system - this is android which is booted once linux bootup and mounted at /system
33. cache - for temporary work usually lost after reboot but not always
43. userdata - this partition hold userdata, internal sd (/storage/sdcard0 or /sdcard), internal app installed mainly mounted at /data
10. tz
11. tzbak - Trusted Zone and back up are trusted zone providers to android
5. ssd - secure software download; "Secure Software Download" is a memory based file system (RAMFS) for secure storage, used to download and store "who knows what" on the eMMC. It is a referenced part in the Remote Storage RPC Client of the MSM kernel.
6. sbl1 - secondary bootloader
7. sbl1bak - secondary bootloader backup
8. rpm - resource and power manager @MotoJunkie01 /rpm is also known as primary bootloader, and flashing this partition should always be avoided if at all possible. /rpm, /sbl1, /tz, and /aboot are all considered bootloaders.
9. rpmbak - resource and power manager backup
24. boot - this partition holds kernel and initrd.gz
15. modemst1 - Modem1 (NV data)
16. modemst2 - Modem2 (NV data)
22. aboot - AP Bootloader {AP has some thing to do with APN configuration}
23. abootbak - AP Bootloader backup
20. fsg - Probably stands for File System (FS) "Golden". According to Samsung documentation, this partition is a "Golden Copy". This is partially confirmed by RE of the PARAM partition, which indicate that this partition should contain a copy of MODEMST1. As such it is a backup of the current EFS2 filesystem. The creation of a FSG is not supported on flash devices and the internal (QMI) DIAG request "EFS2_DIAG_MAKE_GOLDEN_COPY", can only be used to create a backup one time over the life of the device. [80-V1294-11] ref
rest of the partition you write
Good research. /rpm is also known as primary bootloader, and flashing this partition should always be avoided if at all possible. /rpm, /sbl1, /tz, and /aboot are all considered bootloaders (and/or bootloader dependent partitions). Tampering with any of these is the quickest way to hard brick a device beyond repairability. /fsg, in Motorola devices anyway, is considered a radio firmware partition and contains the fsg-id configuration for carrier dependent parameters. I included /fsg in my modem thread (my baseband installer flashes /modem, /fsg, and formats modemst1 & modemst2). The /simlock partition does exactly what it implies. When a network unlock code is entered into the device, the requisite changes are applied to /simlock in order to enable GSM network unlocking. In theory, if an unlocked device's /simlock partition is flashed to a locked device, the locked device also becomes network unlocked. This works on most brands which use a similar partition index for network locking/unlocking. I'll research the partitions you didn't reference and add some additional info.
The /splash partition is the boot logo.
The /splash partition is the boot logo.
If you remove or tamper it you will get beautiful tux icon
Recovery and boot are actually in the same format -- an "ANDROID!" archive containing a kernel, an initrd, and a kernel command line. The recovery is just another kernel and an initrd containing all the files you see in your recovery.
Cache is used for the system communicating with the recovery. The system places a command in a file there telling the recovery to perform a function like factory reset or apply a FOTA. The recovery reads that, does the command, and writes its state and logs back to cache. I don't know what else cache is used for, but FOTA temp files certainly don't download there (they're in /data/data/com.tcl.dmclient/files/last_dlpkgfile on this phone), and the Play Store doesn't download stuff to there when installing apps.
tz/tzbak are something for the ARM Trust Zone, which is a bit like TPM on PCs. It's a function built into the processor that can be used to store keys securely. These partitions contain an ELF file, so I suspect this is a binary that interfaces with or runs inside the Trust Zone, and not the data store for it.
I haven't seen any real info about ssd, but given "Secure Software Download" and that it's only 8 KB, I'm guessing it's used by the baseband for things like updates and SIM apps pushed through the cell network.
The boot sequence as I understand it is rpm -> sbl1 -> aboot -> boot (Linux kernel).
Rpm, sbl1 and tz are updated with each firmware update for this device that I've seen. It looks like the updater changes rpm, sbl1 and tz; and then rpmbak, sbl1bak and tzbak are updated after a successful boot. The updater seems to update both aboot and abootbak though. I determined this by looking at a backup taken after an update and reboot, and one taken after an update and no reboot.
Do you have a link where I can read more about fsg, modemst1/2, EFS2 and EFS2_DIAG_MAKE_GOLDEN_COPY?
Chupi383 said:
Recovery and boot are actually in the same format -- an "ANDROID!" archive containing a kernel, an initrd, and a kernel command line. The recovery is just another kernel and an initrd containing all the files you see in your recovery.
Cache is used for the system communicating with the recovery. The system places a command in a file there telling the recovery to perform a function like factory reset or apply a FOTA. The recovery reads that, does the command, and writes its state and logs back to cache. I don't know what else cache is used for, but FOTA temp files certainly don't download there (they're in /data/data/com.tcl.dmclient/files/last_dlpkgfile on this phone), and the Play Store doesn't download stuff to there when installing apps.
tz/tzbak are something for the ARM Trust Zone, which is a bit like TPM on PCs. It's a function built into the processor that can be used to store keys securely. These partitions contain an ELF file, so I suspect this is a binary that interfaces with or runs inside the Trust Zone, and not the data store for it.
I haven't seen any real info about ssd, but given "Secure Software Download" and that it's only 8 KB, I'm guessing it's used by the baseband for things like updates and SIM apps pushed through the cell network.
The boot sequence as I understand it is rpm -> sbl1 -> aboot -> boot (Linux kernel).
Rpm, sbl1 and tz are updated with each firmware update for this device that I've seen. It looks like the updater changes rpm, sbl1 and tz; and then rpmbak, sbl1bak and tzbak are updated after a successful boot. The updater seems to update both aboot and abootbak though. I determined this by looking at a backup taken after an update and reboot, and one taken after an update and no reboot.
Do you have a link where I can read more about fsg, modemst1/2, EFS2 and EFS2_DIAG_MAKE_GOLDEN_COPY?
Click to expand...
Click to collapse
I can confirm that modemst1 and modemst2 are nv data partitions. The /fsg partition (a configuration which has been used by Samsung and Motorola for many years) is a baseband firmware partition that contains carrier ID and carrier regional information.
---------- Post added at 03:35 AM ---------- Previous post was at 03:33 AM ----------
MotoJunkie01 said:
I can confirm that modemst1 and modemst2 are nv data partitions. The /fsg partition (a configuration which has been used by Samsung and Motorola for many years) is a baseband firmware partition that contains carrier ID and carrier regional information.
Click to expand...
Click to collapse
@Chupi383, Question: have you been able to successfully capture an OTA for this device? If so, where is the OTA stored once downloaded? Thanks for your help on this.
@MotoJunkie01 The downloaded OTA is stored as /data/data/com.tcl.dmclient/files/last_dlpkgfile.
You can also get the download URL for an XML file named "desc" from logcat. You can download desc by using a user agent string spoofer with the user agent "Red Bend Software vDirect Mobile(TM) RedBend-vdm-5.6.0.65". Then that will contain the download URL for the zip itself, which you can download with the same user agent. The fun thing about these zips is once you have the URL for one, you can guess the URLs for other to/from firmware version pairs.
{
"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"
}
Orangefox-DualBoot-Guac-Unified - Android 10/11 version
THANKS TO:
- Zackptg5 - The father of this mod
- DrakePL (Orangefox Recovery)
- Ae3NerdGod, Neel P, Whismasterflo
- Muphetz, Varun Soma, Pranav - for testing
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Click to expand...
Click to collapse
Modified recovery and installer script for all OP7/Pro/5G variants that re-purposes userdata for true dual booting. You can still use this as a regular stock twrp zip - one stop shop for magisk, verity, and/or forced encryption modifications
Disclaimer
I am not responsible for anything bad that happens to your device. Only experienced users should be using this mod
This is no walk in the park mod. Although I have extensively tested it, there is always the possibility of a brick with anything that involves repartitioning. Make sure you have a backup and know how to reparititon your phone back to stock (there's a guide at the end of this readme with the basics)
YOU'VE BEEN WARNED - Use at your own risk
Click to expand...
Click to collapse
Limitations
If you set a password, regardless of encryption status, it'll corrupt the other slot if it's also password protected.
Note that some roms set one automatically Either don't use a password on one slot, or leave one slot (I'll use 'a' in this example) unencrypted and:
Setup rom, password, and everything on slot a
Boot back into twrp, choose common data as storage, and backup userdata (if not using a/b/c layout, backup TWRP folder to your computer)
Setup rom, password, and everything on the other slot (b)
Boot back into twrp, switch back to slot a (reboot back into twrp), and restore the twrp backup
If you messed this up and are unencrypted - delete these files in /data/system if present: locksettings.db gatekeeper.password.key password.key gatekeeper.pattern.key pattern.key gatekeeper.gesture.key gesture.key
If you messed this up and are encrypted - you lost the data on that slot:
Unmount metadata in twrp gui
Format metadata with this command:
Code:
mke2fs -t ext4 -b 4096 /dev/block/sda$metadata_partnum
where metadata_partnum is the partition number of the current metadata partition (you can find this with sgdisk /dev/block/sda --print). DO NOT FORGET THE PARTITION NUMBER. If you do, you'll format all of sda which results in a brick
Reboot into twrp and format data in gui
Storage settings only supports 128 and 256gb userdata partitions
Just a cosmetic issue as it'll say that system is taking up the difference
Some other features/notes
Can choose between stock layout, a/b userdata, or a/b/c userdata where 'c' is a common data partition that'll show up in both roms - it's quite handy
Option to choose between ext4 and f2fs
Disables verity - fstabs are modified for dual boot and so this is a must unless you choose stock layout in which case it's optional
Option to disable forced encryption
Option to install magisk
Quickmode for faster rom testing
Failsafe to keep from changing slots automatically when used in conjunction with rom install
Common Data
If you choose a/b/c layout - you'll have a/b userdata, but you'll also get a 3rd userdata partition I call 'Common Data'
The name 'Common Data' gives away its purpose - to store files that you'll access on both slots/roms. So stuff like zips, pictures, music, TWRP backups, etc.
In TWRP, this shows up as another storage option for backup/restore and on your pc as well - your phone will have 'Common Storage' and 'Internal Storage'
In order to be accessible when booted, some parts of the system are modified so that the it'll be accessible WITHOUT root by the following mechanisms:
The common data partition is mounted to /sdcard/CommonData
.nomedia file is placed in CommonData so files in it won't be picked up twice if you decide to mount over internal storage as outlined below
Furthermore, if your use case is like mine where my music files are in common data, you can make 'mounts.txt' file in /datacommon containing a list of every FOLDER to mount directly over top of sdcard. So for example:
/datacommon/Music -> /sdcard/Music
This of course mounts over anything there (overwrites it for as long as it's mounted) so make sure that you don't have the same folder in both datacommon and regular data
Note that there are 3 exceptions to this folder mounting rule:
All - if this is the FIRST line, ALL folders in datacommon will be mounted
Android
lost+found
The reasoning should be obvious - lost+found isn't something you should need to mess with and Android is for regular data partition only - that's OS specific and should be on separate slots
Note that you should have 1 folder listed on every line, for example:
PHP:
Music
Pictures
ViPER4AndroidFX
Flashing Instructions (if Android 11, see second post)
You MUST be booted into TWRP already when flashing this zip (you can grab a bootable twrp image from here)
Since this modifies data - the zip CANNOT be on sdcard or data at all UNLESS you do not want to repartition/format
If you flash from data, the zip will copy itself to /tmp and instruct you to flash it from there OR you can just install twrp/magisk/disver-fec
You could do the above or copy it to a place like /dev or /tmp and flash it from there
Alternatively, you can adb sideload it
Read through ALL the prompts - there's lots of options
How to Flash Roms
Nothing changes here except ONLY FLASH IN TWRP
Roms always flash to the opposite slot. Keep that in mind and you'll be fine
So don't take an OTA while booted - boot into twrp, switch slots, reboot into twrp, flash rom
Normal flash procedure:
Boot into twrp
reboot into twrp selecting slot you do NOT want rom installed to
Flash rom
Flash this zip
Reboot into twrp
When using failsafe mode,
TWRP will boot into the slot you were in BEFORE you flashed the rom.
TWRP will almost certainly show the incorrect "current slot" at the reboot menu.
The slot selection buttons still work. If youve kept track in youre head, and the zip didnt fail; pick the correct slot now
or reboot to recovery, then switch into the slot which contains the new rom youve just installed
Flash everything else
Quickmode usage NOT RESPONSIBLE FOR BUGS, BRICKS OR MISTAKES! USE AT OWN RISK!
Change the zip name to enable quickmode options (Case Sensitive!)
keeps current layout
add the words fast or quick in the zip file to enable quickmode with the following default options:
ForceEncryption disabled for both slot
s
Magisk installed to both slots
add any of the following options to the name of the zipfile to custimize quickmode to your liking, capitilizing the letter of the slot youd like to enable that option for:
fec.ab will ENABLE force encrytion for the capitalized slot letter
su.ab or magisk.ab will ENABLE the installation of magisk for the capitalized slot letter
Example: if the file is named Orangefox-DualBoot-fast-fec.AB-su.aB.zip then:
ForceEncryption will be ENABLED on both slot _a and slot _b
Magisk will be installed on slot _b, but NOT installed on slot _a
ADVANCED USERS ONLY NOT RESPONSIBLE FOR BUGS, BRICKS OR MISTAKES! USE AT OWN RISK!
confirm.y will skip the final confirmation before any work is done, and run the options chosen or defaults if none specified
the word warp this can be used instead of fast or quick and confirm.y if you'd also like to use quickmode without confirmation
Failsafe usage / explaination
I've had a few instances where a rom doesnt agree with whats going on, and the dualboot zip gets stuck on a slot and never finishes. This results in forcing the phone off, and leaves the phone in a non bootable state, with an unprepared slot. Not to mention a stock, or worse, no recovery at all. Bootloop city.
Enter the failsafe option: just add ` nofail ` or ` failsafe ` (case sensitive) to the zip name like above, and the zip will revert the slot change caused by the rom install and keep you able to boot back into the current slot's TWRP so you can sort out the slot youre working on. Pair this with a usb drive or commondata, and youre (relatively) safe to flash on the go, or from your bed with the computer off.
Notes
After applying the failsafe, the reboot screen in TWRP will ALMOST CERTANLY show the incorrect slot until you either manually select a slot or reboot recovery.
This adds a step or two to the flashing process, make sure you've read that.
[/QUOTE]
Help! I Can't Boot!
Usually this is because you switched roms without formatting data first. This should be flashing 101 but we all forget sometimes. Plus this slot stuff can get confusing
If it only happens with a/b/c and not any other layout, there's a good chance it's selinux related. Try setting selinux to permissive at kernel level with this mod (source here).
Click to expand...
Click to collapse
How to Manually Repartition Back to Stock
In the event any step in the repartioning fails, the entire installer aborts. The good news is that this prevents a potential brick. The bad is that you need to manually revert back
Boot into twrp. If sgdisk is not present in sbin, grab it from this zip (in tools) and adb push it to /sbin and chmod +x it
sgdisk /dev/block/sda --print Note that /dev/block/sda is the block that userdata and metadata are stored on - no other block is touched by this mod. This will show up the current partition scheme. Stock looks something like this (on OP7 Pro):
PHP:
Number Start (sector) End (sector) Size Code Name
1 6 7 8.0 KiB FFFF ssd
2 8 8199 32.0 MiB FFFF persist
3 8200 8455 1024.0 KiB FFFF misc
4 8456 8711 1024.0 KiB FFFF param
5 8712 8839 512.0 KiB FFFF keystore
6 8840 8967 512.0 KiB FFFF frp
7 8968 74503 256.0 MiB FFFF op2
8 74504 77063 10.0 MiB FFFF oem_dycnvbk
9 77064 79623 10.0 MiB FFFF oem_stanvbk
10 79624 79879 1024.0 KiB FFFF mdm_oem_dycnvbk
11 79880 80135 1024.0 KiB FFFF mdm_oem_stanvbk
12 80136 80263 512.0 KiB FFFF config
13 80264 969095 3.4 GiB FFFF system_a
14 969096 1857927 3.4 GiB FFFF system_b
15 1857928 1883527 100.0 MiB FFFF odm_a
16 1883528 1909127 100.0 MiB FFFF odm_b
17 1909128 1913223 16.0 MiB FFFF metadata
18 1913224 1945991 128.0 MiB FFFF rawdump
19 1945992 61409274 226.8 GiB FFFF userdata
You may have different size userdata - mine is 256gb - depending on your device but that doesn't matter. You just need to see where they're located
Take note of the number (I'll call userdata_num for the sake of this tutorial) and start sector (userdata_start) for the first partition AFTER rawdump, and the end sector (userdata_end) of the last parititon on sda
sgdisk /dev/block/sda --change-name=17:metadata - renames metadata partition back to non-ab stock
sgdisk /dev/block/sda --delete=19 - this deletes the entire partition - use this command for each user/metadata partition after rawdump (ones generated by this zip)
sgdisk /dev/block/sda --new=$userdata_num:$userdata_start:$userdata_end --change-name=$userdata_num:userdata - this creates the new userdata partition
Final step is to format the new userdata partition: mke2fs -t ext4 -b 4096 /dev/block/sda$userdata_num $userdata_size - where userdata_size can be calculated with this shell command: sgdisk /dev/block/sda --print | grep "^ *$userdata_num" | awk '{print $3-$2+1}'
MAKE SURE YOU VERIFY ALL VARIABLES HERE ARE SET PROPERLY - if you mess this up, you could format all of sda resulting in a brick
Run sgdisk /dev/block/sda --print again to make sure everything is correct and then reboot back into twrp
Changelog
Click to expand...
Click to collapse
21/03/2021 - V1.8
Updated companion app to 2.8.7
05/03/2021 - V1.6
Updated init.mount_datacommon.sh to support the application sharing
Updated the dual boot companion app V2.6 BETA
Added mounting inactive system to sdcard/DualBoot/
Added mounting inactive SDcard to sdcard/DualBoot/
EXPERIMENTAL - Added application sharing between ROMs (Only A/B/C Layout)
Localizations update
Minor bugfix here and there.
13/02/2021- V1.5
Updated the dual boot companion app V1.7.2
Updated Orangefox recovery to latest git
06/02/2021- V1.3
Updated the dual boot companion app
Fixed the Orangefox full screen bug on OP7 pro
05/02/2021- V1.1
Added the dual boot companion app
Fixed the OOS11 flashing bug
20/01/2021- V1.0
It works with OxygenOS 11 ( WARNING: --- Stay unencrypted! --)
Magisk 21.4 updated
New version of Orangefox recovery (R11) - 20-01-2021 update
Know bug: Flashing from OOS11 slot can overwrite the same slot.
19/11/2020 - A11-0.4
Fixed root install for Android 11
Minor improvement
21/10/2020 - A11-0.4
Root not installed if Android 11 - Please do it manually.
CommonData mount fix in Android 11
Minor improvement
Android 11: please install Magisk 20422 and MagiskManager 297
16/10/2020 - A11-0.2
Changed to OrangeFox Recovery
Added check to get the right initrc (Android 11 compliant)
16/10/2020 - A11-0.1
Initial release
Click to expand...
Click to collapse
Download
Orangefox-DualBoot-Guac-Unified-A11-V1.8
GitHub
https://github.com/Invernomut0/OrangeFox-DualBoot-Guac-Unified
Telegram support chat: https://t.me/OrangeFoxDualBootRebornOnePlus7
XDA:DevDB Information
Orangefox-DualBoot-Unified, Tool/Utility for the OnePlus 7
Contributors
invernomut0
if you like my work, send me a beer
Click to expand...
Click to collapse
DUALBOOT COMPANION APP
FLASH PROCEDURE - Android 11
Related to Orangefox-DualBoot-Guac-Unified-A11.zip
WARNING: OOS11 --- Stay unencrypted! ---
Example (starting point)
Slot A A10 Rom
Slot B A10 Rom
1 - Flash from slot A A11/OOS11 rom
2 - Flash Orangefox-DualBoot-Guac-Unified-A11.zip
3 - Reboot to recovery (Now you are in slot B automatically)
4 - Format data
5 - Flash Orangefox-DualBoot-Guac-Unified-A11.zip
7 - Reboot to system
Install magisk manager attached
Ending point
Slot A A10 rom
Slot B A11/OOS11 rom
Now you should have a working A10 rom on slot A and a working A11/OOS11 rom on slot B.
Please report any problems.
Reserved
I am on oos a10, rooted, twrp and encrypted... Can i use this for dual boot oos a10 with some custom a11 without having to decrypt/data loss???
kpmohamedhussain said:
I am on oos a10, rooted, twrp and encrypted... Can i use this for dual boot oos a10 with some custom a11 without having to decrypt/data loss???
Click to expand...
Click to collapse
Hi. All your data will be wiped and you have to reinstall both slots OS since this is repartitioning your userdata into A and B so do a Backup of all your data before.
It works great with A10 and A11. I had a little issue because I had A10 on A and B slot and when flashed this, then A11 ROM, rebooted to other slot flashed this again A11 was working great, but when tried to switch back to the slot with A10, after boot my pin wouldn't work anymore, so needed to delete locksettings.* an *.key files from /data/system.
Thanks for the great job!
vladvlad12 said:
It works great with A10 and A11. I had a little issue because I had A10 on A and B slot and when flashed this, then A11 ROM, rebooted to other slot flashed this again A11 was working great, but when tried to switch back to the slot with A10, after boot my pin wouldn't work anymore, so needed to delete locksettings.* an *.key files from /data/system.
Thanks for the great job!
Click to expand...
Click to collapse
Only set a PIN on one of the slots. Otherwise you will have that issue that your PIN does not work anymore on the other slot if you set it on both!!
Does anyone have OOS Open Beta 17 or 18 working with this recovery?
ImamBukhari said:
Does anyone have OOS Open Beta 17 or 18 working with this recovery?
Click to expand...
Click to collapse
I will try it for you, be back in like 10 minutes with edit.
Back, is not working. It stuck at patching fstabs.
vladvlad12 said:
I will try it for you, be back in like 10 minutes with edit.
Back, is not working. It stuck at patching fstabs.
Click to expand...
Click to collapse
Take a look at the recovery.log in /tmp then to check while it is getting stuck.
Wishmasterflo said:
Take a look at the recovery.log in /tmp then to check while it is getting stuck.
Click to expand...
Click to collapse
Ok, just give me a minute, already installed another ROM, will try to give info u asked in a few minutes. Someone told me when i tried to do same with twrp dual boot that twrp can't yet decrypt OOS Beta 17 and 18
IDK what happened but now my touchscrren is not working...
After stuck at patching I rebooted into fastboot changed active slot to other slot, rebooted into recovery, it enter in OrangeFox Recovery but no touch...
Got a bit scared there... Rebooted to system then back to recovery and touch is working now...
But there is no /tmp folder...
vladvlad12 said:
I will try it for you, be back in like 10 minutes with edit.
Back, is not working. It stuck at patching fstabs.
Click to expand...
Click to collapse
Could you please also provide the postition of init.rc. look at /init.rc and check if the file exists.
invernomut0 said:
Could you please also provide the postition of init.rc. look at /init.rc and check if the file exists.
Click to expand...
Click to collapse
Dualboot still no work with oos beta 17 and 18,,its always stuck when patching fstab ( decrypt).
There's init process called High Assurance Boot (HAB) that verify your system's integrity. Check the script "/vendor/etc/init/hw/init.mmi.hab.rc".
This command show many values, which one to pick.
gdisk /dev/block/sda --print | grep "^ *$userdata_num" | awk '{print $3-$2+1}'
edit: typo, worked fine now...
Tried it with Beta 19 and doesn't work with that either
Download link not working - Magisk 20422 and MagiskManager 297
ImamBukhari said:
Tried it with Beta 19 and doesn't work with that either
Click to expand...
Click to collapse
Do you have OP7 or OP7 pro/T?
invernomut0 said:
Do you have OP7 or OP7 pro/T?
Click to expand...
Click to collapse
I'm using a 7 Pro
kpmohamedhussain said:
Download link not working - Magisk 20422 and MagiskManager 297
Click to expand...
Click to collapse
Files restored
Works great, tested with multiple ROMs...
Having below issues
1. Even if pin not setup in secondary ROM, need to delete files otherwise pin in primary is not accepted
2. After every flash of this recovery, all my magisk settings, modules are all lost
3. Images and videos in common data not visible in gallery