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
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.......
I've bricked radio/modem in my ZUK Z2 pro by hidden settings and „Set GSM/UMTS band” to USA band (only choice)
I live in Europe. I am a quite advanced user, I always root every phone.
Android Google play offered me to install an app „hidden settings”. I did.
There was a select radio band option. I clicked it just to check. In old MTK phones in engineering mode there were a list, like this http://www.cellphonemic.com/image/cache/data/B9500-band-500x500.jpg
But in new ZUK Z2 pro with android 6 there was a choice of USA band (only choice).
Something like this
http://attach.en.miui.com/forum/201608/23/031335orzj1vxxar1vymvm.png.thumb.jpg
It affected only the first SIM slot. Now my first SIM cannot connect - cannot send/receive calls and cannot send SMS. Changing to 3G and 2G gives me a no service. Changing to 4G gives me connection but only data works, cannot call, cannot send a SMS.
Many people have this problem after „Set GSM/UMTS band” to USA band (only choice). This is not a ZUK Z2 problem but Android settings problem.
IT'S STUPID that it could be undone. In OLD android there were a list:
"Automatic", "EURO Band", "USA Band", "JAPAN Band", "AUS Band", "AUS2 Band"
Method:
start an adb shell
type:
am start -n com.android.settings/.BandMode
works.
In new android there is only one entry "USA band".
I know people tried many things.
“Factory reset but that didn't help.”
“I did factory reset and nothing, I installed the factory image and either. “
I did for instance:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
Restart. No result.
It's very frustrating that the software will not allow me to reverse what he did.
Problem probably is here:
https://android.googlesource.com/pl....0_r26/src/com/android/settings/BandMode.java
Many people on many forums described this on many different phones and there is no solution.
One guy mentioned:
“Switch the phone to FLIGHT/AIRPLANE MODE (I did this by dragging down the top menu bar on my phone which is running a custom rom)
Press the menu key and SELECT RADIO BAND - you'll see the complete list of country bands - do NOT select a band yet....”
but it does NOT work for zuk z2 pro.
Zuk Z2 pro is no alone. One said: “Tks 4 ur guide !” but another “I try your trick,but not work in my device.”
One guy (Bitdomo's) made a custom rom for “nexus 5x” - instead of querying the baseband for available band modes just displays all six band modes. People were happy. “I flashed your ROM and then Phone Information had Auto in select band using which I switched back to GSM.”
https://img.xda-cdn.com/Lpw6Ao9fHG6...es.hu/151126/ffsafas_www.kepfeltoltes.hu_.png
or “ I resolved the problem by flashing Bidomo's ROM”.
But I don't have Nexus 5, I have Zuk Z2 pro.
So the only solution to change baseband is changing the source code of BandMode.java, compile and flash my own rom in the Zuk Z2 pro ?
Not cool Google.
There is probably also a second option:
“Well guys, if anyone else is having this problem now, there is an easier method. You can just restore your efs backup. Yes it's for root users only, but if you have it, it's as easy as rebooting to twrp and restoring efs then reboot without wiping anything.
Btw I have really no idea why google didn't implement an auto band option...”
But I don't have EFS backup...
some said:
“i just flash radio .img solved.”
I don't have radio.img for Zuk Z2 pro
Probably this setting has changed just a byte in a configuration. Does anybody have any idea where could it be ? Or any idea how to fix this baseband ?
Please help.
PS Fortunately second SIM card in my Zuk Z2 pro works. Strange, heh?
Problem SOLVED, but crazy.
As I mentioned I ****ed up my sim1 network when I clicked hidden settings (also can be reach by *#*#4636#*#*) and „Set GSM/UMTS band” to USA band (only choice in ZUK Z2 pro). Then my first sim1 could not call/send sms. Sim2 worked ok.
Even
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
and restart had had no result.
My baseband was:
#> getprop | grep -i baseba
[gsm.version.baseband]: [.2.0.c1.9-00026-M8996FAAAANAZM-1]
[gsm.version.baseband1]: [.2.0.c1.9-00026-M8996FAAAANAZM-1
I downloaded
https://drive.google.com/drive/folders/0B_e7IyAKmSLcTE0wdXcxdDhFb2c?usp=sharing
the same
filename: zuk_z2_baseband_2.0.079.zip
Baseband version: .2.0.c1.9-00026-M8996FAAAANAZM-1
supported Android version: 6.x/7.x
mentioned here https://zukfans.eu/community/threads/zuk-z2-baseband-collection-versions.4565/
There was a file
bytes 81568256 name NON-HLOS.bin
This is for ZUK z2, I have "zuk z2 pro" version but someone says it is the same.
The version match I hope.
But before I flashed it I made a backup of my modem by
# ls -l /dev/block/bootdevice/by-name/ | grep modem
lrwxrwxrwx 1 root root 16 Sep 28 1970 modem -> /dev/block/sde11
lrwxrwxrwx 1 root root 15 Sep 28 1970 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 Sep 28 1970 modemst2 -> /dev/block/sdf2
# dd if=/dev/block/sde11 of=/storage/emulated/0/DCIM/Camera/NON-HLOS-my.bin
194560+0 records in
194560+0 records out
99614720 bytes (95.0MB) copied, 1.575881 seconds, 60.3MB/s
and then I copied NON-HLOS-my.bin by android ftp server to my local computer disk. It was REALLY IMPORTANT !
I flashed
adb reboot bootloader
fastboot -i 0x2b4c flash modem non-hlos.bin
fastboot -i 0x2b4c erase modemst1
fastboot -i 0x2b4c erase modemst2
fastboot -i 0x2b4c reboot
(*) non-hlos was from
zuk_z2_baseband_2.0.079.zip
Baseband version: .2.0.c1.9-00026-M8996FAAAANAZM-1
After reboot I had neither cell network or wifi network !!!
Again erasing:
adb reboot bootloader
fastboot -i 0x2b4c erase modemst1
fastboot -i 0x2b4c erase modemst2
fastboot -i 0x2b4c reboot
The same
No wifi ! no sim 1, no sim2 !!!
**** I said.
So fortunately I had a backup.
So
adb reboot bootloader
fastboot -i 0x2b4c flash modem NON-HLOS-my.bin
fastboot -i 0x2b4c erase modemst1
fastboot -i 0x2b4c erase modemst2
fastboot -i 0x2b4c reboot
My wifi network and sim2 network were back, but not only ! Crazy thing, but my sim1 started working again !
Crazy heh ?
Probably this new NON-HLOS.bin which didn't work wrote something in the configuration and after re-flashed NON-HLOS-my.bin again it was able to went away from this stupid USA band and refreshed.
After this: sim1 and sim2 work again. Both can see GSM/3G, I can call/send sms by both.
SOLVED !
I have same problem with my new Lenovo legion pro 2 phone what steps would I have to change
Does anyone knows how to root lava x81?
I searched google bout it didn't help?
Phone Specs:
Mediatek MT6735
OS: Star OS based on Android 6
Kernel:3.18.19
[HELP] Please anyone help to build/port TWRP for Lava X81 MT6735 Marshmallow Arm64
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Any body please help us. Lava X81 16GB 3GB MT6735 SoC is a June 2016 Model. Today is 27 May 2019. Till now we don't find any custom recovery for Lava X81.
Device Vendor : Lava
Model/Version : X81
SoC Vendor : MediaTek
Soc CPU : MT6735 1.30 Ghz
CPU Cores : Quad-Core (4)
CPU Architecture : 4x ARM Cortex-a53 @ 1.30 GHz
CPU Family: Cortex-A53
CPU Clock Speed : 299 MHz - 1300 MHz (i.e., 1.3 GHz)
Machine : aarch64
ABI : arm64-v8a
Bit Version : 64-bit (Arm)
GPU Vendor : ARM
GPU Renderer : Mali-T720
GPU Clock Speed : 279 MHz - 448 MHz
RAM : 3 GB (2934 MB) LPDDR3_16GB
ROM : 16 GB
Screen Density : 320 DPI (xhdpi)
Resolution : 1280x720
Kernal Version : Linux 3.18.19 (1470576607)
Kernal Architecture : armv8l
[HELP] to build/port [TWRP] [RECOVERY] for Lava X81 MT6735 Marshmallow Arm64 ?
Android Version : 6.0
Android Version Codename : Marshmallow
Please anyone built/port TWRP for us (We are around lacks of users would got benifitted).
:good::good::good::good::good::good::good::good::good::good::good:
You don't need TWRP for rooting. Install MediaTek MT65xx USB VCOM Preloader USB Drivers. Install SP Flash Tool. Find a scatter file for your device. If you can not find it, you can create it. Load the scatter file. Read back boot.img from phone. Install the Magisk Manager app. Patch the boot.img from Magisk. On the Download Tab, flash the patched_boot.img from SP Flash Tool (IMPORTANT: uncheck all checkboxes except BOOT) You are rooted as soon as you boot from this patched_boot.img and can check it from Magisk Manager app
aIecxs said:
You don't need TWRP for rooting. Install MediaTek MT65xx USB VCOM Preloader USB Drivers. Install SP Flash Tool. Find a scatter file for your device. If you can not find it, you can create it. Load the scatter file. Read back boot.img from phone. Install the Magisk Manager app. Patch the boot.img from Magisk. On the Download Tab, flash the patched_boot.img from SP Flash Tool (IMPORTANT: uncheck all checkboxes except BOOT) You are rooted as soon as you boot from this patched_boot.img and can check it from Magisk Manager app
Click to expand...
Click to collapse
How to patch boot image with Magisk ? Anyone know
https: // www. t h e c u s t o m d r o i d .com/install-magisk-root-android-devices
aIecxs said:
https: // www. t h e c u s t o m d r o i d .com/install-magisk-root-android-devices
Click to expand...
Click to collapse
We are discussing here to root lava x81.
WIthout rooting, how to install Magisk & then how to patch boot.
Currently it is impossible without introducing A CUSTOM TWRP RECOVERY for LAVA X81
please READ my first post! then LOOK at the screen shot (second post)
https: // www. t h e c u s t o m d r o i d .com/install-magisk-root-android-devices/#Method-2-Patch-Stock-Boot-Image
aIecxs said:
https: // www. t h e c u s t o m d r o i d .com/install-magisk-root-android-devices
Click to expand...
Click to collapse
Thanks it works!
[ROOTED] Lava X81 using Magisk Manager by patching stock boot image (No TWRP)
---------------------------------------------------------
Who said this method to us ?
aIecxs, XDA Senior Member from Germany
https://forum.xda-developers.com/member.php?u=7285913
Thread Link :
https://forum.xda-developers.com/android/help/helproot-lava-x81-t3620166
Thanks alecks!!!!
------------------------------------------------------------
Youtube Video Assistance:
Video Name: How to root Android using Magisk Manager & stock boot.img
Channel : Hovatek
------------------------------------------------------------
REQUIREMENTS :
(0) Unlocked Bootloader
To unlock bootloader in Lava X81 by Fastboot mode use the command
fastboot oem unlock #unlock bootloader via fastboot mode
{{{{{ NOTE: Unlocking bootloader in Lava X81 will erase all the user data. So please take a backup before unlocking bootloader. }}}}}
(1) Stock boot.img for your phone model (its best its for your Build Number / Variant ) . You can extract from the stock rom / firmware of your device (you may check our collection at https://forum.hovatek.com/forum-89.html ) OR backup from your device using a hardware box e.g Miracle Box, CM2, Nck Box Pro etc
(2) Download Latest Magisk Manager {Currently 7.3.0 (220)}
(3) Active internet connection on your Android device
(4) A windows 10 Laptop
---------------------------------------------------------
INSTRUCTIONS :
Step 1: Patching the stock boot.img
1. Install Magisk Manager 7.3.0 (220) APK on your android device.
2. Copy the stock boot.img of Lava X81 to your phone's internal storage or SD card whereever you want (Internal Storege\Dowloads is the better option)
3. Launch Magisk Manager app and check for latest updates. After the updates you will see that Magisk Manager is up to date.
4. Then, Select (Magisk is not installed. Latest 19.3 (19300)) Install > (Install Magisk) Install > Select and Patch a File >
5. Navigate to the location of the stock boot.img you copied earlier on (select Dowloads option or in my case, I used ES File Explorer File Manager), then Select it
6. Magisk Manager should begin downloading the magisk zip file for our arm64-v8a Device platform.
7. Once download is complete, MagiskManager will automatically patch the boot file and store it under
/storage/emulated/0/Download/magisk_patched.img
(Then I renamed it as "patched_boot.img" for our convenience)
Step 2: Flashing the patched boot.img
Among a variety of options to flash, I preferred Fastboot method
(0) Connect your Lava X81 one or two times to the PC (for preinstalling drivers)
(1) Boot your Lava X81 into fastboot mode.
(2) Open platform-tools_r28.0.1-windows.zip file
(3) Simultaneously press Keyboard's Shift key and Right click on the mouse, to open PowerShell window
(4) On the PowerShell use the following codes to flash:
Starting from phone's normal usb debugging mode,
adb devices #Ensures your phone connectivity in ADB (Android Debug Interface) mode via USB Debugging
adb reboot-bootloader #Reboot your phone to Fastboot Mode from ADB
fastboot devices #Ensures your phone connectivity in Fastboot mode
fastboot getvar unlocked #To check whether the bootloader is unlocked or not. It should be unlocked to proceed further
fastboot flash boot patched_boot.img #Flash the Magisk Patched Boot image file in Fastboot Mode
fastboot reboot #Reboot to the system from exiting Fastboot Mode
(5) Congrats and check with a Root checker app for root status. While checking for root status itself pop out for root permission.
--------------------------------------------------------
Proofs and All the necessary files as a zip file - MediaFire Link
Root Lava X81 using Magisk Manager by patching stock boot image (No TWRP)
http://www.mediafire.com/file/zjb78878i52865c/Root_Lava_X81_using_Magisk_Manager_by_patching_stock_boot_image_%2528No_TWRP%2529.zip/file
---------- Post added at 05:23 PM ---------- Previous post was at 05:19 PM ----------
aIecxs said:
please READ my first post! then LOOK at the screen shot (second post)
https: // www. t h e c u s t o m d r o i d .com/install-magisk-root-android-devices/#Method-2-Patch-Stock-Boot-Image
Click to expand...
Click to collapse
[ROOTED] Lava X81 using Magisk Manager by patching stock boot image (No TWRP)
---------------------------------------------------------
Who said this method to us ?
aIecxs, XDA Senior Member from Germany
https://forum.xda-developers.com/member.php?u=7285913
Thread Link :
https://forum.xda-developers.com/android/help/helproot-lava-x81-t3620166
Thanks alecks!!!!
------------------------------------------------------------
Youtube Video Assistance:
Video Name: How to root Android using Magisk Manager & stock boot.img
Channel : Hovatek
------------------------------------------------------------
REQUIREMENTS :
(0) Unlocked Bootloader
To unlock bootloader in Lava X81 by Fastboot mode use the command
fastboot oem unlock #unlock bootloader via fastboot mode
{{{{{ NOTE: Unlocking bootloader in Lava X81 will erase all the user data. So please take a backup before unlocking bootloader. }}}}}
(1) Stock boot.img for your phone model (its best its for your Build Number / Variant ) . You can extract from the stock rom / firmware of your device (you may check our collection at https://forum.hovatek.com/forum-89.html ) OR backup from your device using a hardware box e.g Miracle Box, CM2, Nck Box Pro etc
(2) Download Latest Magisk Manager {Currently 7.3.0 (220)}
(3) Active internet connection on your Android device
(4) A windows 10 Laptop
---------------------------------------------------------
INSTRUCTIONS :
Step 1: Patching the stock boot.img
1. Install Magisk Manager 7.3.0 (220) APK on your android device.
2. Copy the stock boot.img of Lava X81 to your phone's internal storage or SD card whereever you want (Internal Storege\Dowloads is the better option)
3. Launch Magisk Manager app and check for latest updates. After the updates you will see that Magisk Manager is up to date.
4. Then, Select (Magisk is not installed. Latest 19.3 (19300)) Install > (Install Magisk) Install > Select and Patch a File >
5. Navigate to the location of the stock boot.img you copied earlier on (select Dowloads option or in my case, I used ES File Explorer File Manager), then Select it
6. Magisk Manager should begin downloading the magisk zip file for our arm64-v8a Device platform.
7. Once download is complete, MagiskManager will automatically patch the boot file and store it under
/storage/emulated/0/Download/magisk_patched.img
(Then I renamed it as "patched_boot.img" for our convenience)
Step 2: Flashing the patched boot.img
Among a variety of options to flash, I preferred Fastboot method
(0) Connect your Lava X81 one or two times to the PC (for preinstalling drivers)
(1) Boot your Lava X81 into fastboot mode.
(2) Open platform-tools_r28.0.1-windows.zip file
(3) Simultaneously press Keyboard's Shift key and Right click on the mouse, to open PowerShell window
(4) On the PowerShell use the following codes to flash:
Starting from phone's normal usb debugging mode,
adb devices #Ensures your phone connectivity in ADB (Android Debug Interface) mode via USB Debugging
adb reboot-bootloader #Reboot your phone to Fastboot Mode from ADB
fastboot devices #Ensures your phone connectivity in Fastboot mode
fastboot getvar unlocked #To check whether the bootloader is unlocked or not. It should be unlocked to proceed further
fastboot flash boot patched_boot.img #Flash the Magisk Patched Boot image file in Fastboot Mode
fastboot reboot #Reboot to the system from exiting Fastboot Mode
(5) Congrats and check with a Root checker app for root status. While checking for root status itself pop out for root permission.
--------------------------------------------------------
Proofs and All the necessary files as a zip file - MediaFire Link
Root Lava X81 using Magisk Manager by patching stock boot image (No TWRP)
http://www.mediafire.com/file/zjb78878i52865c/Root_Lava_X81_using_Magisk_Manager_by_patching_stock_boot_image_%2528No_TWRP%2529.zip/file
i have nothing todo with Magisk - all credits go to the author @topjohnwu
(and you don't need to unlock bootloader, just flash with SP Flash Tool)
These partitions are important when you'll have to restore the phone back to normal from worst case.
Code:
elableinfo (/dev/block/sda4) - This partition contains Certification Image, may not important.
imeilock (/dev/block/sdg1) - This partition contains your device IMEI.
persist (/dev/block/sda8) - This partition contains your device PSN, MAC, Bluetooth.
oemowninfo (/dev/block/sda2) - This partition contains SKUID, exclusive info, etc.
simlock (/dev/block/sde63) - Carrier locked TA-1251 only. Mandatory to allow your phone boot if your phone isn't carrier locked.
Other Snapdragon 765G based Android phones can also refer this, although we can't guarantee it will 100% apply on your phone. DO NOT FOLLOW THIS GUIDE IF YOU ARE USING TA-1257 (NOKIA 8 V 5G UW from Verizon Wireless).
WARNING:
1. DO NOT SHARE YOUR CRITICAL PARTITION BACKUP IMAGES TO ANYONE ELSE TO PREVENT ABUSE, PLUS, SHARING THIS VIOLATES THE RULE OF XDA.
2. CRITICAL PARTITION BACKUP IMAGES FOR BOTH TA-1243 AND TA-1251 AREN'T INTERCHANGEDABLE.
Click to expand...
Click to collapse
To backup these partitions:
1. Unlock the bootloader and root your phone with Magisk.
2. Execute these commands:
Code:
adb shell mkdir /storage/emulated/0/bgt-critical/
adb shell su
(Confirm root permission on your phone - if you missed that or didn't confirm it, open Magisk app and grant it manually)
adb shell su -c dd if=/dev/block/bootdevice/by-name/imeilock of=/storage/emulated/0/bgt-critical/imeilock.img
adb shell su -c dd if=/dev/block/bootdevice/by-name/persist of=/storage/emulated/0/bgt-critical/persist.img
adb shell su -c dd if=/dev/block/bootdevice/by-name/oemowninfo of=/storage/emulated/0/bgt-critical/oemowninfo.img
adb shell su -c dd if=/dev/block/bootdevice/by-name/simlock of=/storage/emulated/0/bgt-critical/simlock.img
adb pull /storage/emulated/0/bgt-critical/
3. Save entire bgt-critical directory at safe place.
Additionally, you must do QCN backup in case you erased NVRAM at worst case.
To do that:
1. Root your phone with Magisk.
2. Execute this command on your PC with ADB shell for enabling Qualcomm Diag Port:
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,adb
3. Install QPST 2.7.496 and use QPST Software Download to backup both XQCN and QCN images, and save both of them at bgt-critical partition you have saved.
Here's how to reinstall stock firmware, in case you bricked the phone at worst situation.
Please disable automatic translation on your web browser if you can't click "CLICK TO SHOW CONTENT" button.
Click to expand...
Click to collapse
Assuming you have UFS lun0-lun6 erased, or the phone is currently at Qualcomm 900E which are considered worst situation.
1. Download following firmware, and extract it 3 times - you'll get tons of files inside.
bgt-2210-0-00WW-B01.HMDSW.7z | by Hikari Calyx for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
2. Use text editor to open rawprogram0_sparse.xml and delete the string super.img inside to save time when doing part 1 flashing.
Use text editor to open rawprogram4.xml and replace the string abl.elf into BGT-abl.elf , then save it.
3. Copy prototype ABL into the firmware directory, and make sure the filename is BGT-abl.elf .
4A. (For Windows users)
Please install QPST 2.7.496 or newer and Qualcomm USB Driver before you proceed. You'd better to erase all other incompatible drivers to increase success rate.
Once installed, please copy QSaharaServer.exe and fh_loader.exe from QPST installation directory (C:\Program Files (x86)\Qualcomm\QPST\bin by default) to firmware directory.
4B. (For macOS / Linux users)
Please install Python EDL from following website:
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
5. If your phone is currently at 900E, you must disassemble the phone by opening the back cover and make sure the motherboard is exposed.
Disconnect the battery, use a pair of tweezers to short the test point, then connect your phone to PC. Using USB 2.0 port is strongly recommended for best stability.
{
"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"
}
If you're using PC that only has USB 3.1 port you may like encounter USB port throttling issue. In this case you must buy an USB hub as workaround.
To check if your phone is properly connected:
(For Windows users)
Please open Device Manager and check if your phone is listed as Qualcomm HS-USB QDLoader 9008 / Qualcomm HS-USB Diagnostics 9008. If not you need to disconnect the phone, short the test point and connect the phone to PC again. Once it's listed you can remove the tweezer.
(For macOS / Linux users)
Please execute this command:
Code:
lsusb
and see if a device started from 05C6:9008 is listed. If yes, you can remove the tweezer and proceed to next step.
6A. (For Windows users)
Please check the COM port in Device Manager, assuming the COM port number is 8.
Open a Command Prompt or PowerShell window at directory where you have tons of firmware files extracted.
Execute this command (replace the COM port number to actual COM port number you see in Device Manager)
Code:
.\QSaharaServer -p \\.\COM8 -s 13:prog_firehose_ddr.elf
If you see a message says image uploaded successfully, you can proceed to next step.
Execute this command to upload rawprogram XML configuration:
Code:
.\fh_loader --port=\\.\COM8 --search_path=. --sendxml=rawprogram0_sparse.xml,rawprogram1.xml,rawprogram2.xml,rawprogram3.xml,rawprogram4.xml,rawprogram5.xml,rawprogram6.xml --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=UFS
Wait for image files being uploaded, now write patch XML configuration:
Code:
.\fh_loader.exe --port=\\.\COM8 --search_path=. --sendxml=patch0.xml,patch1.xml,patch2.xml,patch3.xml,patch4.xml,patch5.xml,patch6.xml --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=UFS
Once these commands are executed successfully, you can disconnect the phone, reconnect the battery and power it on.
Your phone should boot straight into Fastboot mode. If it doesn't boot the battery might be drained, recharge it a little bit before you proceed.
6B. (For macOS / Linux users)
Assuming you have Python EDL installed properly.
Open a terminal under the directory where you have firmware extracted, and execute this command:
Code:
edl qfil rawprogram0_sparse.xml,rawprogram1.xml,rawprogram2.xml,rawprogram3.xml,rawprogram4.xml,rawprogram5.xml,rawprogram6.xml patch0.xml,patch1.xml,patch2.xml,patch3.xml,patch4.xml,patch5.xml,patch6.xml /path/to/where/firmware/images/arelocated/ --memory=ufs --loader=prog_firehose_ddr.elf
Wait for image files being uploaded. If the flashing procedure is throttling, you may want to execute this command before connecting phone with test point shorted.
Once this command is executed successfully, you can disconnect the phone, reconnect the battery and power it on.
Your phone should boot straight into Fastboot mode. If it doesn't boot the battery might be drained, recharge it a little bit before you proceed.
7. Reinstall all other partitions with Fastboot command.
If you're Windows user, please DO NOT USE Minimal ADB and Fastboot, but use this instead: https://developer.android.com/studio/releases/platform-tools
Code:
fastboot flash partition:0 gpt_both0.bin
fastboot --set-active=a reboot-bootloader
fastboot flash xbl xbl.elf
fastboot flash xbl_config xbl_config.elf
fastboot flash abl abl.elf
fastboot flash tz tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash storsec storsec.mbn
fastboot flash pwinfo pwinfo.img
fastboot flash bluetooth BTFM.bin
fastboot flash modem NON-HLOS.bin
fastboot flash core_nhlos Core_NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash logfs logfs_ufs_8mb.bin
fastboot flash keymaster km4.mbn
fastboot flash featenabler featenabler.mbn
fastboot flash toolsfv tools.fv
fastboot flash metadata metadata.img
fastboot flash aop aop.mbn
fastboot flash qupfw qupv3fw.elf
fastboot flash imagefv imagefv.elf
fastboot flash uefisecapp uefi_sec.mbn
fastboot flash multiimgoem multi_image.mbn
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
By doing this will allow your phone boot as the bare minimal situation, but not ideally functional.
Next you must restore critical partitions you have backed up before.
Code:
fastboot erase fsc
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fs_image.img
fastboot flash elableinfo /path/to/bgt-critical/elableinfo.img
fastboot flash imeilock /path/to/bgt-critical/imeilock.img
fastboot flash persist /path/to/bgt-critical/persist.img
fastboot flash oemowninfo /path/to/bgt-critical/oemowninfo.img
fastboot reboot
8. Once your phone boots into normal OS, use Magisk to root your phone, and execute this command to enable Qualcomm Diag Port:
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,adb
9. (For Windows users) Use QPST Software Download to restore the QCN/XQCN image you backed up before. Eject SIM before you doing so to prevent issues.
10. (Skip if you're not using Carrier locked TA-1251) Reboot the phone into Fastboot mode and flash simlock partition:
Code:
adb reboot bootloader
fastboot flash simlock /path/to/bgt-critical/simlock.img
fastboot reboot
11. Enjoy your fully revived Nokia 8.3.
Reserved #3
This step by step tutorial is all about
☆☆☆ FastbootD video tutorial : https://m.youtube.com/playlist?list=PLvggR4skCxYzhB3SXxpSx4LvRzGwx9k45Full round-trip of "GSIs flashing process".
Step to install Stock ROM with Fastboot ability.(need 3in1.tar)
Step to flash GSI on top of Stock ROM.
get rid of SU.which came with "bvS" or "bgS" Variant.(option if you want Magisk)
Step to update GSI without lost your data include magisk.
Step to Recovery back to the First Boot with Magisk (hidden).
<<Additional for PHH AOSP>>
Add Adaptive Auto-brightness for T225 (magisk module) here
Add Face Unlock. here
<< Additional for Stock SAM A13 based>>
Add Restore Samsung Knox features.(had lost from unlocked and root)
Add Advanced Setup New LeOS
ADD DUAL BOOT WITH Vega Bobo DSU Sideloader. (SAM Stock A13 Base) Example here:
**FastbootD Help.
fastboot commands
fastboot commands. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
--info--
Sam did not provided " fastboot mode" for all devices. only "Odin flashing tool".
What is the FasdtbootD?
What is FastbootD? How to Boot to FastbootD Mode
In this tutorial, we will explain you what is FastbootD Mode in Android, how to boot to FastbootD Mode and how to exit this mode.
www.droidwin.com
*Limitation of FastbootD
FastbootD not the same as regular "fastboot", impossible to use fastbootd without " Dynamic partition. etc., dynamic partitions are automatically created, resized, or deleted as needed.
*FastbootD has access in logical partition like Super Partition.
( have odm +product+vendor+system partition inside) , Because dynamic partitions are implemented in userspace, partitions needed by the bootloader can't be made dynamic. For example, boot, dtbo, and vbmeta are read by the bootloader, and so must remain as physical partitions.
then
You can't uses by fastbootD performed
Code:
fastboot --disable-verity flash vbmata vbmeta.img
✓ Not enough space to resize partition solution
Solution:
Removing stock system_ext and/or product from fastbootd is enough, like so:
***Don't uses this command
"fastboot delete-logical-partition product"
why ?
the product partition, with around 1.3GB in size isn’t even required by the GSIs.
then you can delete data on product partition.
*(Didn't delete product partition itself but deletes only data inside this partition , then android will auto-resize product'spartition.)
Do this.
Code:
adb reboot fastboot
Code:
fastboot erase product
set the size of the product partition to 0
Code:
fastboot resize-logical-partition product 0x0
To verify if the partition size has become 0.
Code:
fastboot getvar all
If one of the lines shows the below code, then the process is a success.
Code:
(bootloader) partition-size:product:0x0
{
"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"
}
or
>fastboot erase system_ext
>fastboot resize-logical-partition system_ext 0x0
---End Info--
Resource:
Basic knownledge.
my customAP tutorial.
** When using FastbootD you should knows
Set of fastbootd command.
-content-
Flashing Any GSIsUsing Fastboot without CustomAP 》Save your time.Example_use AOSP A13 from phhusson TrebleDroid GSI.
Complete Cycle From Fastboot Flashing >>>ROOT (Magisk,SU)>>Customized UI >>Update without Lost Data and Magisk.Requirement:
-Unlocked BootLoader
-(Recommend) Stock Firmware Update to A13 such as
"SM-T225XXU1CWA2" etc.,
Why? Used Android 13 GSIs.
1. MTP works
2. Offline Charging works
3. Google Assistant can call for you. (Ok Google call xxx) Stock A13 didn't do it.
etc.,
>Step to install Stock ROM together with Fastboot ability at the same time.
(clean install with stock firmware)
Extract AP Framework File for "recovery.img.lz4" and patch to add FastbootD ability. [ Download Attach file ] or patch by yourself here https://github.com/Johx22/Patch-Recovery.
Flash Stock Framework File with odin. (AP , BL, CP, CSC_not_home) + Magisk patch-boot & vbmeta & patch-recovery at (USERDATA Slot) ( include 3 patch-files to one tar file) [ Download Attach file ] -After reboot must connects internet and set "Developer options = enable OEM unlocking + USB debugging"
(Computer) Download and extract Platform tools to C:\ https://developer.android.com/studio/releases/platform-tools.
(Computer) Download and install Fastboot interface Driver. https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/
Note:
1.you can dirty flash patched fastbootD-recovery at AP slot. When you had any firmware or gsi installed.
2.Howto magisk-patch (boot.img.lz4 + vbmeta.img.lz4). in General Section.
>Step to flash GSI on top of Stock ROM
Set of Command to install GSIs on top of Stock Firmware.
-Connect device with USB cable to Computer.
-Download your GSIs.
-Extract "GSI.img file into platform tools directory.
-open CMD inside the platform-tools folder and then type in the below command
** Check device was already connected with computer.
*** Check bootloader version (patched) is the same as your device's firmware.
0.
Code:
adb devices
1.
Code:
adb reboot fastboot
-Device will turn display into FastbootD mode
2.
Code:
fastboot erase system
option: if you founded ‘Not enough space to resize partition’) error.
Code:
fastboot delete-logical-partition product
3.
Code:
fastboot flash system gsi-filename.img
4. FastootD (pic below)Select "Enter recovery menu"
5.Recovery (pic below)
Select "wipe data/factory reset" menu
6. Recovery (pic above)
Select "reboot system now" menu
>>Finished " Flashing with FastbootD"<<
After installation.
- This variant was included with " PHH-SU".
>Step get rid of SU.(option if you want Magisk) (bvS or bgS variant)
adb shell Enter
su Enter
chmod +x /system/bin/phh-securize.sh Enter
/system/bin/phh-securize.sh Enter
* Device will auto reboot.
After this Magisk icon will show up.
Click Magisk icon to continue setup additional files and reboot.
-----------------------------------------------------------------
*Step to update GSI without lost your data include magisk.
*** (Recommended: use Magisk-Gapps, if you don't want to re-process install gapps again.)
Disable all magisk modules. (if you used another Launcher or Port it from another GSI , pleases uninstall it first.)
Flash New-Update-GSI with FastbootD
Code:
fastboot flash system new-gsi.IMG
then REBOOT System (No factory reset or wipe data)
Code:
fastboot reboot
After get rid of SU , magisk will show up.
get rid of SU
Code:
adb shell
Code:
su
Code:
chmod +x /system/bin/phh-securize.sh
Code:
/system/bin/phh-securize.sh
Note: After this magisk will works again. (with all modules you had installed .)
===End of Update Version info===
Scripts by phhusson to automatically build/CI/Release TrebleDroid GSI
more than 2 times per month
Then I write this easy additional way to update without lost your data..
>Step to Recovery back toThe First Boot with Magisk (hidden installed).
1.Run Factory Reset From Recovery by press and hold (Power+ Vol down)
2. Connect internet and enable Developer options.
3. Enable OEM unlocking & USB debugging.
4. Reboot after that Magisk setting icon will show up again.
--End update--
Happy Chinese New Year!General Section
** Compared 2 projects
** Restore Samsung Knox features.
✓ How to create Magisk patch for boot.img + vbmeta.img
extract (vbmeta.img.lz4 + boot.img.lz4) from your AP Stock
create compress one file xxx .tar with 7zip
move (vbmeta.img.lz4 + boot.img.lz4).tar (xxx.tar) to tab a7 lite
install magisk.apk on you tab a7 lite
patch the tar file. (with magisk manager)
result magisk-patch file at Tab a7 :-Download folder.
✓ Howto install fastboot driver.
How to Install Fastboot Drivers in Windows 11
In this comprehensive tutorial, we will show you the detailed steps to install the Fastboot Drivers onto your Windows 11 PC
www.droidwin.com
✓ [Add pre-patch-recovery-FastbootD]
*** S2 = can't downgrade (Android version) even firmware version.
SM-T220 A13SM-T225 A13SM-T 227U A13SM-T 225N A13T220XXS2CWA7T225XXS2CWA8T227UVLU3CVLAT225NKOU1CWA3T220XXU1CWA2T225XXS2CWA6T220XXU1CWA1T225XXU1CWA2T220XXU1CVL7T225XXU1CVL6T220XXU1CVL5T225XXU1CVL5T220XXS2CWA8T225XXU2CWB3
✓ Howto install "adb &fastboot" on PC
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
You should also replace your adb with the latest binaries by Google.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download the platform tools for windows zip file. Find out where your current adb.exe file is located. Extract the zip into that location, overwrite the old file(s).
Note: Don't delete any files from platform-tools
>>>>>>>>>>>>>>
√ Download:
Where are New AOSP A13 official?
Releases · TrebleDroid/treble_experimentations
Scripts to automatically build/CI/Release TrebleDroid GSI - TrebleDroid/treble_experimentations
github.com
Note: (Read/Write System should uses variant "vndklite".)
✓Changes PHH-SU to Magisk.
- Connect device with your computer. run below command.
Code:
adb shell Enter
su Enter
chmod +x /system/bin/phh-securize.sh Enter
/system/bin/phh-securize.sh Enter
May be didn't found phh-securize.sh only uses root file manager deleted "/system/xbin/su"
√ You can install "GAPPS" by adb shell or by Magisk-Gapps module.
(Cause we didn't have TWRP, but don't worry about TWRP.)
*install Bromite Systemwebview
*Vega Bobo DSU Sideloader (Root mode with magisk)
*this firmware can't downgrade.**S2**T225XXS2CWA6 , it will no longer be possible to roll back even to the previous firmware .
( A13"SM-T225XXU1CWA2)
* Add some T220 FastbootD -Recovery-patch
Reserved:
Option tools for customize your AOSP GSI.
Install Gapps modules with Magisk. ( For Android 13)DOWNLOAD: https://litegapps.site/index.html
CLICK NAME FOR DOWNLOAD
1. [MAGISK]LiteGapps_Nano_arm64_13.0_v2.8_official.zip (Base)
2. GoogleSearch_LiteGapps_Addon_arm64_13.0.zip. (add-on)
3. GoogleAssistant_LiteGapps_Addon_arm64_13.0.zip. (add-on)
Note: you can add add-on mod from here.
STEP. ( with magisk manager )
Flash 1 and Reboot
Flash 2 and Reboot
Flash 3 and Reboot
How to configure Google Assistant . ( For make a call )
-Set Default Digital Assistant.
Open Setting and Search with keyword " digital assistant or assistant"
-Configure OK Google.
Open Setting 》Google 》Setting for Google apps 》Search Assistant & Voice 》 Google Assistant 》Hey Google & Voice match
ENABLE Hey Google.
tom.android said:
You can install "GAPPS" by adb shell .
Click to expand...
Click to collapse
Where can I download a compatible package and what command besides adb shell do I have to run in order to install?
nirogu325 said:
Where can I download a compatible package and what command besides adb shell do I have to run in order to install?
Click to expand...
Click to collapse
readme inside archrive.
tom.android said:
readme inside archrive.
Click to expand...
Click to collapse
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
nirogu325 said:
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
Click to expand...
Click to collapse
nirogu325 said:
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
Click to expand...
Click to collapse
1. install root explorer app. (such as Mixplorer)
2. create directory "gapps" or anyname at /data
such as /data/gapps
3. extract archrive " TitaTheGapps.zip" to dir from 2
4. open terminal adb shell ----then su then
cd /data/gapps/tita
chmod +x ./installer.sh
5. add more space for new gapps by delete some unuseful from "/system/system_ext/apex"
Del "android.vndk.v.28,29,30,32 keep only v31
6. run script---> sh ./installer.sh
note you can use command "mount -o rw,remount /system" or used root explorer do it. (changes RO to RW) before mod system.
nirogu325 said:
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
Click to expand...
Click to collapse
Here is what I did to install GApps on AOSP A13:
Get TheGappsInstaller-Tita archive here: https://github.com/ChonDoit/TheGappsInstaller/releases/tag/Tita (specifically: TitaTheGapps_Terminal_20221225.tar.xz)
Extract the tar archive from the tar.xz file
Follow instructions below (credits: ozmage)
adb push TitaTheGapps_Terminal_20221225.tar /sdcard/Download
adb root
adb shell
cd /data
mkdir GAPPS
mv /sdcard/Download/TitaTheGapps_Terminal_20221225.tar GAPPS
cd GAPPS
tar xvpf TitaTheGapps_Terminal_20221225.tar
cd TitaTheGapps_Terminal_20221225
chmod a+x ./installer.sh
sh ./installer.sh
tom.android said:
1. install root explorer app. (such as Mixplorer)
2. create directory "gapps" or anyname at /data
such as /data/gapps
3. extract archrive " TitaTheGapps.zip" to dir from 2
Click to expand...
Click to collapse
dapr0b said:
Here is what I did to install GApps on AOSP A13:
Get TheGappsInstaller-Tita archive here: https://github.com/ChonDoit/TheGappsInstaller/releases/tag/Tita (specifically: TitaTheGapps_Terminal_20221225.tar.xz)
*instructions*
Click to expand...
Click to collapse
Thank you both, THAT is real support.
Update: Howto update GSI without lost your data.
Update.
Flashing Any GSIsUsing Fastboot without CustomAP any longer.
tom.android said:
Update.Flashing Any GSIsUsing Fastboot without CustomAP any longer.
Click to expand...
Click to collapse
Thank you.
I have one question though.
My tab is already updated to SM-T225XXU1CWA2. In the firs step, can I just simply flash with ODIN your attached fastbootd-recovery.tar in AP slot and the 3-in-1.tar in USERDATA slot without including the stock framework file (AP, BL, CP, CSC)?
jtrakx said:
Thank you.
I have one question though.
My tab is already updated to SM-T225XXU1CWA2. In the firs step, can I just simply flash with ODIN your attached fastbootd-recovery.tar in AP slot and the 3-in-1.tar in USERDATA slot without including the stock framework file (AP, BL, CP, CSC)?
Click to expand...
Click to collapse
1. flash only 3in1.tar at AP slot. (magisk 25.2 + vbmeta + recovery-patch)
-install gsi
2. remove SU by
adb shell Enter
su Enter
bra bra bra
look at my tutorial
tom.android said:
1. flash only 3in1.tar at AP slot. (magisk 25.2 + vbmeta + recovery-patch)
2. remove SU by
adb shell Enter
su Enter
bra bra bra
look at my tutorial
Click to expand...
Click to collapse
Thank you. That's a big help.
update iconify v6.0 (extract zip file run iconify.apk ) or update from app.
Iconify • Customize Boring Android UI
Updated to v6.0.0
What's new?
• Custom battery color
• Semi Transparent Brightness bar style
• Semi Transparent QS tile style
• Semi Transparent Notification style
• 5 styles of volume panel
• Improved UI roundness
XPosed Menu: (LSPosed recommended)
• Transparent Qs Panel (Supports more rom)
• Window Level Blur and Force blur enabler for unsupported ROMs
• Vertical QS tiles
• Custom header image (GIF supported)
• Custom header clocks
• Custom lockscreen clocks (custom font supported)
• Clock and status icons background chip
Full Changelog: Click Here
Teamfly Launcher (Didn't test)
TeamFiles Launcher
A launcher which aims to provide stability, speed & customizationMore info at github.com/TeamFiles/TeamFiles-LauncherJoin t.me/loopprojects to get more updates!
store.kde.org
May be compatible with quick switch of OneUI 5.
I also have a question, is this only for SM-T225XXU1CWA2 only ? or T220 can do this too . I have T220 XAR us version android 13 gsi pixel Experience plus with magisk. I want to install fastbootD and install gsi without custom AP.. do I use this guide?
abc1054 said:
I also have a question, is this only for SM-T225XXU1CWA2 only ? or T220 can do this too . I have T220 XAR us version android 13 gsi pixel Experience plus with magisk. I want to install fastbootD and install gsi without custom AP.. do I use this guide?
Click to expand...
Click to collapse
yes u can , extract AP file>>recovery.img.lz4. boot.img.lz4. vbmeta.img.lz4. upload here if you can't patch.
Can you explain how to patch it. Thanks
abc1054 said:
Can you explain how to patch it. Thanks
Click to expand...
Click to collapse
1.boot.IMG.lz4. 2. vbmeta.IMG.lz4. patch with magisk
2.recovery.IMG.lz4. patch follow with https://github.com/Johx22/Patch-Recovery
tom.android said:
yes u can , extract AP file>>recovery.img.lz4. boot.img.lz4. vbmeta.img.lz4. upload here if you can't patch.
Click to expand...
Click to collapse
Here is my files