Develop Bugs

[GUIDE]Karbonn A5,A7,Walton Primo IMEI writting & No Sim Problem Fixing

All right everyone here I will give u the method of writing IMEI & No Sim Detection problem of Karbonn A5/W619/Walton Primo & Karbonn A7/S01..
Many of the User of A5 are having problem with the IMEI & Mobile network lost and no sim is detecting while upgrading or downgrading Baseband.
As I have been searching for solution about a month and there is no specific solution regarding this problem..Through some ideas from different sites & developer and experimenting with my own device I have managed to write back both IMEI & enabled mobile network.
Note: For A7 user Please download AP of your device not this one.
Software & Other Requirement:
1.Stock AP of Karbonn A5/W619/Walton Primo (Original Stock GB Rom).
Link : http://jabadbd24.blogspot.com/2013/03/walton-primo-karbon-a5-downgrade-to-gb.html
2.Baseband- V3025 & V3070 both.
3.Fastboot 1.0.2.4 (for downloading AP+BP to device).
4.Drivers.
5.QPST Modem Tool V1.1 (for writing IMEI).
Link : http://www.mediafire.com/download/c9nv2zc1a233s13/Qualcomm_Modem_Tools%20V1.1.rar
6.QPST 2.7 (for restoring network).
Link : http://www.mediafire.com/download/kna2s9x3z06gcuu/QPST_2.7_378.zip
*********************************** FB ID= facebook.com/dj.rifat*****************************************************
Procedure:
A. (BP+AP) Download:
1.If u have upgraded your device to ICS then u have to Downgrade to GingerBread. First goto recovery mode(CWM/TWRP).Goto mount and select all and wipe data,system,boot,cache,android secure,SD-ext.Then Power off the device.
2.Then Update BP.First with V3025 (591347_8376_WCDMA_V3025) & then with V3070 (591347_8376_WCDMA_V3070).
[note: before updating V3070 baseband,Copy and replace 'appsboot.mbn' & 'appsboothd.mbn' this two files from the AP folder to V3070 folder in ur PC.]
{
"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"
}
3.Then update Gingerbread AP in Fastboot mode (green screen on device).
4.Turn on mobile while it is connected with the PC.PC will detect new hardware.One from them u installed before while BP Download..
5.Goto Device Manager of PC.U will find three new hardware.Install driver for them.As Shown below:
B. Write IMEI
1)Unzip “Qualcomm_Modem_Tools_V1.1.rar”, open Qualcomm_Modem_Tools.exe, (Turn on ADB Debugging from Application>Development>ADB Debugging from ur mobile)
interface as blew:
(2) Select port. Port should be same as modem port.
(3) Write IMEI. Input new IMEI, click “write”.
(4) Complete writing IMEI.
(5) Then click read, confirm the new IMEI is successful written
C.Fixing NO sim problem and Network.
Now Install ''QPST 2.7.398.exe'' on PC.
(1) Open “QPST Software Download”(Start>Programs>QPST Software Download) and click Restore, interface as below:
(2) Power on handset, connect usb cable and select port by pressing browse as shown below.
(3) Now press the 2nd browse button and navigate to the folder of V3070 Baseband folder ( '591347_8376_WCDMA_V3070' this folder) and select ''591347_8376_WCDMA_V3070.qcn'' file. Now press START ,if you have done everything correctly it will go good.
(4)Restart your mobile.Now goto to Backup Tab and type a name in QCN file column according to ur choice for better understanding which qcn file is the working backup and select location where you wanna save it and press start.This qcn file is important because if u lost ur IMEI sometimes during upgrade or downgrade restoring this file will
recover ur IMEI & network.
This way I have solved my problem.I apologize As I am not a expert in this field if any mistake done by me.
If you don't understand any steps or having problem please let me know will try my best to help you.
You can also find me in facebook/dj.rifat if need help.
Thanks.
Hit like If I have helped you.

Gr8 work bro.. i appritiate your work..!

Rifat.ahmed08 said:
All right everyone here I will give u the method of writing IMEI & No Sim Detection problem of Karbonn A5/W619/Walton Primo & Karbonn A7/S01..
Many of the User of A5 are having problem with the IMEI & Mobile network lost and no sim is detecting while upgrading or downgrading Baseband.
As I have been searching for solution about a month and there is no specific solution regarding this problem..Through some ideas from different sites & developer and experimenting with my own device I have managed to write back both IMEI & enabled mobile network.
Note: For A7 user Please download AP of your device not this one.
Software & Other Requirement:
1.Stock AP of Karbonn A5/W619/Walton Primo (Original Stock GB Rom).
Link : http://jabadbd24.blogspot.com/2013/03/walton-primo-karbon-a5-downgrade-to-gb.html
2.Baseband- V3025 & V3070 both.
3.Fastboot 1.0.2.4 (for downloading AP+BP to device).
4.Drivers.
5.QPST Modem Tool V1.1 (for writing IMEI).
Link : http://www.mediafire.com/download/c9nv2zc1a233s13/Qualcomm_Modem_Tools%20V1.1.rar
6.QPST 2.7 (for restoring network).
Link : http://www.mediafire.com/download/kna2s9x3z06gcuu/QPST_2.7_378.zip
*********************************** FB ID= facebook.com/dj.rifat*****************************************************
Procedure:
A. (BP+AP) Download:
1.If u have upgraded your device to ICS then u have to Downgrade to GingerBread. First goto recovery mode(CWM/TWRP).Goto mount and select all and wipe data,system,boot,cache,android secure,SD-ext.Then Power off the device.
2.Then Update BP.First with V3025 (591347_8376_WCDMA_V3025) & then with V3070 (591347_8376_WCDMA_V3070).
[note: before updating V3070 baseband,Copy and replace 'appsboot.mbn' & 'appsboothd.mbn' this two files from the AP folder to V3070 folder in ur PC.]
3.Then update Gingerbread AP in Fastboot mode (green screen on device).
4.Turn on mobile while it is connected with the PC.PC will detect new hardware.One from them u installed before while BP Download..
5.Goto Device Manager of PC.U will find three new hardware.Install driver for them.As Shown below:
B. Write IMEI
1)Unzip “Qualcomm_Modem_Tools_V1.1.rar”, open Qualcomm_Modem_Tools.exe, (Turn on ADB Debugging from Application>Development>ADB Debugging from ur mobile)
interface as blew:
(2) Select port. Port should be same as modem port.
(3) Write IMEI. Input new IMEI, click “write”.
(4) Complete writing IMEI.
(5) Then click read, confirm the new IMEI is successful written
C.Fixing NO sim problem and Network.
Now Install ''QPST 2.7.398.exe'' on PC.
(1) Open “QPST Software Download”(Start>Programs>QPST Software Download) and click Restore, interface as below:
(2) Power on handset, connect usb cable and select port by pressing browse as shown below.
(3) Now press the 2nd browse button and navigate to the folder of V3070 Baseband folder ( '591347_8376_WCDMA_V3070' this folder) and select ''591347_8376_WCDMA_V3070.qcn'' file. Now press START ,if you have done everything correctly it will go good.
(4)Restart your mobile.Now goto to Backup Tab and type a name in QCN file column according to ur choice for better understanding which qcn file is the working backup and select location where you wanna save it and press start.This qcn file is important because if u lost ur IMEI sometimes during upgrade or downgrade restoring this file will
recover ur IMEI & network.
This way I have solved my problem.I apologize As I am not a expert in this field if any mistake done by me.
If you don't understand any steps or having problem please let me know will try my best to help you.
You can also find me in facebook/dj.rifat if need help.
Thanks.
Hit like If I have helped you.
Click to expand...
Click to collapse
Thank you very much. can u please tell about karbonn a7 plus stock AP where to find. i m having this mobile and facing the same problem.

Thank you so much!!!
I made an account just to say thank for this GUIDE. I was looking and waiting for a year for this GUIDE. THANK YOU SO MUCH!!!:good:

#Respect
Just register an account to post reply. Great work bro, help me pick my phone up from hell :laugh::good::good::good:

vktisnow said:
Thank you very much. can u please tell about karbonn a7 plus stock AP where to find. i m having this mobile and facing the same problem.
Click to expand...
Click to collapse
got my problem solved. thanks a lot for this awesome guide

Anybody can give proper link for the Files.. Most of them are DEAD !!!

i found Port number (COM6).. after this i am unable to write IMEI number(getting error Write IMEI fail). i have entered my old imei number.
when i dial *#06# in my mobile displaying as below:
IMEI1:
IMEI2:
both blanks...(So i entered old IMEI numbers).
And from where can i get new IMEI numbers?
can you please help me on this.

Does this work for SM-A520FDS?

Windows 10 mobile for Lumia 630?

Hello,
i know that Redstone won´t work on that device, but i have been told that some previouse versions of Windows 10 mobile worked on it. Can you please give me some advice on how i can get a compatible version ?
Windows Insider App is already installed and i joined the fast ring. However, no updates are shown if i try to update in settings.....
Please help!
Regards,
impact 79

impact79 said:
Hello,
i know that Redstone won´t work on that device, but i have been told that some previouse versions of Windows 10 mobile worked on it. Can you please give me some advice on how i can get a compatible version ?
Windows Insider App is already installed and i joined the fast ring. However, no updates are shown if i try to update in settings.....
Please help!
Regards,
impact 79
Click to expand...
Click to collapse
At this time there's no way longer presents for your phone .
you have to wait for Boot Loader unlock . by the latest news you should heard about it (Microsoft accidently published their secure boot golden key) it must no longer takes to the hack release then you can use upgrade advisor and registry hack to upgrade to TH2 (10586 build of windows 10)

The link contains cabs download link for updating from latest wp8.1 to windows 10 mobile 10586.107. For Lumia 630 (RM-978) .
Using iutool to push cab files to the phone .Then check update for 10586 in settings.
Waitting for RS on L630 too...

fishersfish said:
The link contains cabs download link for updating from latest wp8.1 to windows 10 mobile 10586.107. For Lumia 630 (RM-978) .
Using iutool to push cab files to the phone .Then check update for 10586 in settings.
Waitting for RS on L630 too...
Click to expand...
Click to collapse
Is there a link for .cab files of RM-976?

BlueTR said:
Is there a link for .cab files of RM-976?
Click to expand...
Click to collapse
Sorry, I don't have one. I only captured the update links for myself before.

fishersfish said:
Sorry, I don't have one. I only captured the update links for myself before.
Click to expand...
Click to collapse
Will it brick my device if i try the RM-978 files on my RM-976 ?

impact79 said:
Will it brick my device if i try the RM-978 files on my RM-976 ?
Click to expand...
Click to collapse
I am just a guy who like flashing roms. I am not sure, it may not. ( Mine is a Dual-SIM module ,yours is of single SIM )

Just tried to flash those files on my RM-976. Unfortunately the update stops with ERROR 0x800b0100.
Seems that the windows security .dll files are not properly registered.

Do i have to unlock the phone or something else before trying to flash ?

impact79 said:
Just tried to flash those files on my RM-976. Unfortunately the update stops with ERROR 0x800b0100.
Seems that the windows security .dll files are not properly registered.
Click to expand...
Click to collapse
iutool doesn't need anything else to be done before pulling update files to the phone
Iutool Error Codes
https://msdn.microsoft.com/en-us/library/windows/hardware/mt131833(v=vs.85).aspx
"TRUST_E_NOSIGNATURE" means what? Maybe someone knows it.

I am getting 0x801882c1 error code while installing updates any idea about this? Error code specifies 0x801882C1 E_CABAPI_NOT_CABINET BTS_E_PER_APP_REQUEST_LIMIT_REACHED not really sure what that means. Downloaded all files twice and tried.
---------- Post added at 09:25 PM ---------- Previous post was at 09:04 PM ----------
KillerTheLord said:
I am getting 0x801882c1 error code while installing updates any idea about this? Error code specifies 0x801882C1 E_CABAPI_NOT_CABINET BTS_E_PER_APP_REQUEST_LIMIT_REACHED not really sure what that means. Downloaded all files twice and tried.
Click to expand...
Click to collapse
Solved this by deleting extra Desktop.ini file. How getting same error as above 0x800b0100.

Readstone can be run on Lumia 630 (512MB RAM) ! The update packages( cab files) can be downloaded from catalog.update.microsoft.com ( search your phone carrier name, like mine: 000-HK ), queue by time ,add 14343 to bucket and download .( other items for 10586 and erlier version; there SHOULD HAVE the links for upgrading from wp8.1 to 10586.107 ). If you can not click to download , view the poped-up webpage's source then copy and sort the download links by yourself.
You only need to download the files similar to the files you grabbed when updating 10586.107 to 10586.545. OR similar to the files in my attachment. It seems that difference to OS language packages can be ignored.
*.cbs_*.cab files are for FULL update, maybe they can be used on 10586.545 ; *.cbsu_*.cab files must can be used on 10586.545. They CANNOT be used at the same time, I update failed once due to this.
Replace IME and Speech data packages with yours.
Use iutool.exe to push cab files to your phone as usual.
If you update failed and your downloaded files are not broken, try to replace thoes files which their name start with or like:
microsoft.devicelayout_qc8x26_16k.mainos.cbs_
microsoft.soc_qc8x26_16k.mainos.cbs_
for other defination, replace this file: microsoft.prerelease_protected.mainos_res_480x800.cbs_*.cab .I am not sure if it can be used on Lumia 630.
Here is my screenshot: SO.....SO exciting!!!
{
"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"
}

@fishersfish:
sounds great, thanks for sharing!
However, i don´t understand completely yet. I have Win Phone 8.1 Update (8.10.14234.375) on my Lumia 630 (Carrier 000-DE).
Which files do i have to download ?
fishersfish said:
Readstone can be run on Lumia 630 (512MB RAM) ! The update packages( cab files) can be downloaded from catalog.update.microsoft.com ( search your phone carrier name, like mine: 000-HK ), queue by time ,add 14343 to bucket and download .( other items for 10586 and erlier version; there SHOULD HAVE the links for upgrading from wp8.1 to 10586.107 ). If you can not click to download , view the poped-up webpage's source then copy and sort the download links by yourself.
You only need to download the files similar to the files you grabbed when updating 10586.107 to 10586.545. OR similar to the files in my attachment. It seems that difference to OS language packages can be ignored.
*.cbs_*.cab files are for FULL update, maybe they can be used on 10586.545 ; *.cbsu_*.cab files must can be used on 10586.545. They CANNOT be used at the same time, I update failed once due to this.
Replace IME and Speech data packages with yours.
Use iutool.exe to push cab files to your phone as usual.
If you update failed and your downloaded files are not broken, try to replace thoes files which their name start with or like:
microsoft.devicelayout_qc8x26_16k.mainos.cbs_
microsoft.soc_qc8x26_16k.mainos.cbs_
for other defination, replace this file: microsoft.prerelease_protected.mainos_res_480x800.cbs_*.cab .I am not sure if it can be used on Lumia 630.
Here is my screenshot: SO.....SO exciting!!!
View attachment 3844880
Click to expand...
Click to collapse

impact79 said:
@fishersfish:
sounds great, thanks for sharing!
However, i don´t understand completely yet. I have Win Phone 8.1 Update (8.10.14234.375) on my Lumia 630 (Carrier 000-DE).
Which files do i have to download ?
Click to expand...
Click to collapse
Sorry, I didn't find either(Maybe I am just too excited ). But there must be a way! A guy from my country ( China ) just capture a lot of update cabs ( from wp8.1 to w10m ) this month. But not include your phone. He must used an other way.
Here is the guy:
http://bbs.wfun.com/home.php?mod=space&uid=1183465
http://weibo.com/u/1144511064

fishersfish said:
Sorry, I didn't find either(Maybe I am just too excited ). But there must be a way! A guy from my country ( China ) just capture a lot of update cabs ( from wp8.1 to w10m ) this month. But not include your phone. He must used an other way.
Here is the guy:
http://bbs.wfun.com/home.php?mod=space&uid=1183465
http://weibo.com/u/1144511064
Click to expand...
Click to collapse
Hi. Do you still have the Build 10586 for Lumia 630 dual sim 512 ram ?please upload this for me so I can flash it on my phone using WP Internal.please I really need it.

ngame said:
At this time there's no way longer presents for your phone .
you have to wait for Boot Loader unlock . by the latest news you should heard about it (Microsoft accidently published their secure boot golden key) it must no longer takes to the hack release then you can use upgrade advisor and registry hack to upgrade to TH2 (10586 build of windows 10)
Click to expand...
Click to collapse
I have downloaded the cab files and but iutool give me error no update files found

mirasal2 said:
I have downloaded the cab files and but iutool give me error no update files found
Click to expand...
Click to collapse
Seems it's command issue .
iutool -v -p C:\Update\*
this is the exact command for when you put update files in c:\Update folder , Do not forget \* it means install anything presents in this path .

ngame said:
Seems it's command issue .
iutool -v -p C:\Update\*
this is the exact command for when you put update files in c:\Update folder , Do not forget \* it means install anything presents in this path .
Click to expand...
Click to collapse
I'm sorry to tell you it didn't work.
Do I have to extract cab files?
Which version from iutool should use,mine is seems like 2014 version

mirasal2 said:
I'm sorry to tell you it didn't work.
Do I have to extract cab files?
Which version from iutool should use,mine is seems like 2014 version
Click to expand...
Click to collapse
No difference witch version are you using .
and surely you don't have to extract cabs . It the thing that will phone do on prepairing for installation

ngame said:
No difference witch version are you using .
and surely you don't have to extract cabs . It the thing that will phone do on prepairing for installation
Click to expand...
Click to collapse
Could you tell me the steps clearly,please?

[ROM][STOCK][Android 6.0][M2-802L] B207 - Android 6.0 Marshmallow with EMUI 4.0

EDIT: For further updates and newer versions, please see my consolidated M2 8.0 Marshmallow ROM thread.
Here is the Huawei Official update ROM for the M2-802L, with Android 6.0 Marshmallow with EMUI 4.0. The download link points to the official Huawei server at hicloud.com.
Version: M2-802LC229B207CUSTC229D006
Download link: http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v67917/f1/full/update.zip
Download link text:
Code:
http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v67917/f1/full/update.zip
I installed this ROM over my old B005 ROM (Android 5.1.1 Lollipop + EMUI 3.1) and it installed fine, rebooted, created a new Dalvik cache and then updated the Google framework. Calls (I'm on AT&T in USA) and texts seem to work fine after the update. All my apps (and most of my settings) were preserved after the update. My AT&T MMS APN was erased, but I have another post on XDA for that. Wifi works too, it connects (as you can see in the screenshot) to the Wifi access points to which I had authenticated on my old ROM, before the update.
I have attached a screenshot of the ROM on my phone.
{
"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"
}
Installation Instructions:
If you are currently rooted and/or have a custom recovery installed, you will need to go back to the Huawei official recovery to install this update. You can do this by following the instructions in my previous post here.
Download the ROM update zip from the above link. Extract the contents of the zip file in the link after it has finished downloading. The contents are as follows:
Code:
update.zip contains
├── META-INF
│** ├── blacklist.conf
│** ├── CERT.RSA
│** ├── CERT.SF
│** ├── com
│** │** ├── android
│** │** │** └── otacert
│** │** └── google
│** │** └── android
│** │** ├── update-binary
│** │** └── updater-script
│** └── MANIFEST.MF
└── UPDATE.APP
5 directories, 8 files
Create a folder called dload on your SD Card. You can create it on either the internal or the external SD, it doesn't matter.
Copy the entire contents (the full META-INF directory as well as UPDATE.APP) of the unzipped download package into the dload folder on your SD Card, which you created above.
Go to your phone's "Settings". There, navigate to "Updater"->"Menu"->"Local Update", select the displayed option, and allow it to install. Your phone will boot into the original OEM recovery and install the ROM, after which it should (hopefully) boot into the new ROM.
It should then connect to the Google Play Store and update the Google framework. All your settings, apps etc should still be preserved - mine were.
Rooting instructions using phhusson's Superuser:
First install TWRP as your recovery. If in doubt, use the excellent Huawei Mediapad M2 rooting guide found on these forums. Note that if following this guide, you may want to make sure that your ROM is Android 5.1.1 (Lollipop), because Android 6.0 (Marshmallow) does not have the Unlock OEM selection in developer option (thanks for the tip, @Dvalin21).
Then grab the latest superuser.zip (from phhusson's Superuser project which is an actively-maintained fork of Koush's open-source Superuser project), and install it via the TWRP recovery.
Finally, get the "phh superuser" app from the Google Play store.
At this point, when I typed "su" in my terminal app, I got the usual permission dialog, and upon granting permissions, I was dropped into a root shell:
Have fun!
I found this ROM after seeing some posts on Russian forums - Google translate was my friend :silly:

Fantastic! I'll give this a go tonight.

PHH Superuser works to root the ROM
wmoore said:
Fantastic! I'll give this a go tonight.
Click to expand...
Click to collapse
Good luck!
Note: For some reason, running the latest stable SuperSU (SuperSU-v2.79-201612051815.zip from the main SuperSU thread) to root this ROM failed and the phone went into a bootloop. Since I had reflashed TWRP back on this ROM, I was able to get back into the bootloader (fastboot), reflash the stock recovery from B207 (which I had been wise enough to extract from the UPDATE.APP), and reflash the ROM again (kept my apps and settings). Trying to install SuperSU again now...
EDIT: There definitely seems to be a problem with SuperSU 2.79 as well as the updated beta 2.79-SR2. I've reported it on the SuperSU forums. Going to try rooting this ROM with an older version of SuperSU - I have 2.78 from when I rooted the older ROM (Android 5.1.1 Lollipop). Eyes, fingers and other crossable body parts crossed
EDIT 2: No joy on SuperSU 2.78 either. Given that Chainfire has relinquished control of SuperSU to some other entities, maybe this is not a bad thing. I am now trying phhusson's fork of Koush's open-source superuser.
EDIT 3: phhusson's Superuser worked!! To install it,
First install TWRP as your recovery,
Then grab and install the latest superuser.zip via the TWRP recovery.
Finally, get the "phh superuser" app from the Google Play store.
At this point, when I typed "su" in my terminal app, I got the usual permission dialog, and upon granting permissions, I was dropped into a root shell:

It worked! I'm finally on Marshmallow on my M2!! I haven't seen anything weird happening yet but I'll keep you posted.

Worked for me too!!! Thanks!

wmoore said:
It worked! I'm finally on Marshmallow on my M2!! I haven't seen anything weird happening yet but I'll keep you posted.
Click to expand...
Click to collapse
murphinator said:
Worked for me too!!! Thanks!
Click to expand...
Click to collapse
You're most welcome, you guys. Happy it worked for you :good: It's too bad that Huawei hasn't officially released Marshmallow to us, forcing us to take matters into our own hands...
When I get a little bit of free time here and there, I'll see if I can work on kanging this ROM - no promises though, since first I have a lot to learn :silly:

Can I use other country's firmware. But same model? (801L)

Caelestiel said:
Can I use other country's firmware. But same model? (801L)
Click to expand...
Click to collapse
Yes, it shouldn't be a problem. I was running the B005 build from China in USA. I had also installed the SYSTEM.img from the German ROM for a different model - the 801L - on my 802-L, and it worked.

One more thing, Can I use TWRP System and Data backup from B007 if I'm using Marshmallow?

Caelestiel said:
One more thing, Can I use TWRP System and Data backup from B007 if I'm using Marshmallow?
Click to expand...
Click to collapse
No, I don't think this will be possible.
The system image is actually the main ROM image/partition. If you overwrite system with your TWRP backup, you will actually be back in your old Lollipop B007 image.
The old data partition may or may not work, but I wouldn't take a chance - most cases of ROM misbehavior in custom ROMs are caused by people not properly clearing their data partition; the same principle may apply here.
If you asked this question because you want to keep all your existing apps and data, they should (most of them) survive the upgrade process, but make sure that you do not manually format/clear/factory-erase your main partitions in TWRP before you upgrade.

I am in Finland and myself have M2-801L. Does this update also in it.

Issue Resolved. idk how to delete comment :v

Eagle-no1 said:
I am in Finland and myself have M2-801L. Does this update also in it.
Click to expand...
Click to collapse
This ROM is specifically for the 802L. It may work on your 801L (as I mentioned in one of my other posts I have successfully flashed and used the 801L System image on my 802L), but be aware that since the two models support different cell frequencies, the radio image in this ROM may not work for you.
Later today, after I get back home, I will see if I can find a Marshmallow stock ROM for the 801L

Caelestiel said:
Issue Resolved. idk how to delete comment :v
Click to expand...
Click to collapse
No problem, don't worry about the comment. I missed seeing the original comment where you mentioned an issue, so just out of curiosity may I know what the issue was?

beast.in.black said:
This ROM is specifically for the 802L. It may work on your 801L (as I mentioned in one of my other posts I have successfully flashed and used the 801L System image on my 802L), but be aware that since the two models support different cell frequencies, the radio image in this ROM may not work for you.
Later today, after I get back home, I will see if I can find a Marshmallow stock ROM for the 801L
Click to expand...
Click to collapse
Alright. Great, I can not find this version of the OEM unlock possibility at all.
https://forum.xda-developers.com/showpost.php?p=70375484&postcount=39

beast.in.black said:
No problem, don't worry about the comment. I missed seeing the original comment where you mentioned an issue, so just out of curiosity may I know what the issue was?
Click to expand...
Click to collapse
I can't flash TWRP because of fastboot error and can't root because I have no recovery.
My bootloader was unlocked before using free and weird software, (nothing that has been said here so I can't remember how did I unlocked it) My warranty ended last Oct. 2016 so I decided to get unlock code from huawei. And reunlocked using that code.
The error was gone and I was able to flash recovery
---------- Post added at 12:53 PM ---------- Previous post was at 12:43 PM ----------
https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
I installed this to my 801L.
But in the settings, it became 803L...

Caelestiel said:
I can't flash TWRP because of fastboot error and can't root because I have no recovery.
My bootloader was unlocked before using free and weird software, (nothing that has been said here so I can't remember how did I unlocked it) My warranty ended last Oct. 2016 so I decided to get unlock code from huawei. And reunlocked using that code.
The error was gone and I was able to flash recovery
Click to expand...
Click to collapse
Oh, great to hear that you were able to get past the error!
Caelestiel said:
---------- Post added at 12:53 PM ---------- Previous post was at 12:43 PM ----------https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
I installed this to my 801L.
But in the settings, it became 803L...
Click to expand...
Click to collapse
Yes, the build.prop in that ROM seems to be the 803L build.prop. However, that ROM doesn't seem to overwrite the radio partition, so it should still be OK. When I had flashed the 801L system image on my 802L, my phone model showed "801L" in settings but I was still able to use all phone functions of the 802L frequencies (AT&T US data, MMS, calls).

beast.in.black said:
Oh, great to hear that you were able to get past the error!
Yes, the build.prop in that ROM seems to be the 803L build.prop. However, that ROM doesn't seem to overwrite the radio partition, so it should still be OK. When I had flashed the 801L system image on my 802L, my phone model showed "801L" in settings but I was still able to use all phone functions of the 802L frequencies (AT&T US data, MMS, calls).
Click to expand...
Click to collapse
But there's something bothering me, something suddenly pops up like "Unfortunately blahblah.apk has stopped" or something like that. I flashed it properly tho. Waiting for the creator's response.

Caelestiel said:
But there's something bothering me, something suddenly pops up like "Unfortunately blahblah.apk has stopped" or something like that. I flashed it properly tho. Waiting for the creator's response.
Click to expand...
Click to collapse
Hmmm...the way I see it, there are two separate and orthogonal variables at play here, any one of which might be responsible for the issue:
The ROM is a customized ROM.
It is originally for a mediapad model (803L) which is different from yours (801L).
Anyway, I have posted a thread with all the latest stock Marshmallow ROMs I was able to find for the different Mediapad M2 8.0 models - maybe the 801L ROM mentioned there can be your rescue ROM when you have a SHTF situation :fingers-crossed:

when coming android 6 for 801LV100R001c199b005 (middle easte) ?
when coming android 6 for 801LV100R001c199b005 (middle easte) ?

[GUIDE] Flashing a different customization on the XQ-AT51 with FlashTool

You can find out your current customization by dialling *#*#SERVICE#*#* -> Service info -> Software Info -> Customization Version. This guide explains how to flash another official Sony firmware of different customization onto your Xperia 1 II XQ-AT51. You do NOT need to unlock your bootloader to do this.
Download and install FlashTool from http://www.flashtool.net
On Windows you will then need to install the Flashmode and Fastboot drivers.
On Linux you do not need to install drivers, but you do need to set some udev rules.
On Windows you will first need to reboot Windows with driver signature enforcement disabled to do this. Then install the Flashmode and Fastboot drivers from the installed C:\FlashTool\drivers\Flashtool-drivers.exe:
{
"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"
}
Open Flashtool and let the device database sync
This may fail on Windows if you have Windows Defender Antivirus Real-time protection running -- disable Windows Defender Antivirus Real-time protection in Windows settings:
Click on the XperiFirm icon to get a list of official Sony firmwares:
Select the XQ-AT51 on the left, and the select the particular Customization you would like. Then click on the box below "Available Firmware" to start downloading:
Once the Firmware has downloaded, close XperiFirm and then let FlashTool do some processing on the downloaded firmware to create a .ftf file of the firmware in your C:\Users\<username>\.flashTool\firmwares folder.
This step is no longer needed as the FlashTool database has now been updated. This step is temporary and will not be required once the FlashTool devices database has been updated for the XQ-AT51.
Download the .fsc file and .properties file and unzip them into a new folder in C:\Users\<username>\.flashTool\mydevices\XQ_AT51 . Rename the .fsc file to "58.0.fsc" to use it with more firmware versions. Then in FlashTool's menu choose Devices->Manage->Import -- this will give an error, but ignore.
Now click on the Flash button and choose Flashmode.
Set up the Firmware Selector window as follows - this setup will erase all data on your phone. Then click Flash:
When prompted, power off your phone and then hold down the volume down key on your phone and connect a USB cable from the phone to your computer (do NOT use the UCB24 USB C - USB C cable that comes with the phone -- the UCB24 is for charging only and does not work -- you need to use a quality USB C - USB A cable or try the UCB32 instead). Keep the volume down key held until the notification light turns green. The flashing process will now be prepared.
When you get a prompt saying "A FSC script is found. Do you want to use it?" choose yes. An error of "those data are not in the fsc script: persist, reset-non-secure-adb" is entirely normal, so choose Yes, and let the flashing commence. If you get a prompt asking you to select a partition, select the top option for 128GB storage and the bottom for 256GB storage -- if unsure click cancel. If you get "ERROR:null" then repair your phone with Xperia Companion first.
Flashing will be complete when you see "Sync status : OKAY".
If you are worried as to whether the flashing worked or not, you can always then do a software repair using the Xperia Companion software. Please check your storage after flashing - some users are reporting that they only are seeing 128 GB of storage instead of 256 GB - please repair with Xperia Companion if you see this and report in the comments below.

I bought the phone from O2UK with the O2 firmware and managed to successfully flash it to the 1321-7192 Customized UK firmware with FlashTool. I now have VoLTE and WiFi-Calling on Vodafone UK .
FlashTool settings:
Here is the before and after Software Info in the *#*#SERVICE#*#* menu:
Here is the before and after in the *#*#4636#*#* Phone Information menu:
EDIT: I turned off and on again the WiFi Calling setting in My Vodafone and now Wi-Fi calling is also provisioned!:
UPDATE: After the 58.0.A.3.88 update on Vodafone with Customized UK, I no longer see Wi-Fi calling as being provisioned, nor do I get the Wi-Fi Calling menu option in network settings. However, Wi-Fi calling is actually still working and still turns on automatically when I get low cellular network strength.

brocnical said:
FlashTool settings:
Here is the before and after Software Info in the *#*#SERVICE#*#* menu:
Here is the before and after in the *#*#4636#*#* Phone Information menu:
Click to expand...
Click to collapse
Does this unlock the ability to have dual sim? I know you would still need a different sim tray. but if the phone will support dual sim after flashing that would make a huge difference for me.

Fatmonk8 said:
Does this unlock the ability to have dual sim? I know you would still need a different sim tray. but if the phone will support dual sim after flashing that would make a huge difference for me.
Click to expand...
Click to collapse
No idea. Are there not more hardware differences than just the SIM tray?

brocnical said:
No idea. Are there not more hardware differences than just the SIM tray?
Click to expand...
Click to collapse
I have no idea, On my OnePlus 7 Pro the only difference was the software and the sim tray, converted it to in global software and replaced the sim tray and dual sim worked.
Hoping its the same for this phone too.

I've managed to do this, but seems like I am only seeing 128GB of storage now? Is that normal, I didn't check before.

kasiopc said:
I've managed to do this, but seems like I am only seeing 128GB of storage now? Is that normal, I didn't check before.
Click to expand...
Click to collapse
No, that is not normal:
You should only have 128GB on the Japanese models. Did you flash a Japanese firmware?

brocnical said:
No, that is not normal:
You should only have 128GB on the Japanese models. Did you flash a Japanese firmware?
Click to expand...
Click to collapse
Customized UK 58.0.A.3.31, and used your files provided above.
---------- Post added at 07:46 PM ---------- Previous post was at 07:21 PM ----------
Works fine now after running Software repair on Xperia Companion. Stayed on the generic firmware as well.

I've gone to try this and Flashtool can't see any downloaded firmwares. In your screenshot the left panel has the model tree, mine is blank. The location is correct as I can see the files there in Explorer. Same both my computer's. Odd.

sidneylopsides said:
I've gone to try this and Flashtool can't see any downloaded firmwares. In your screenshot the left panel has the model tree, mine is blank. The location is correct as I can see the files there in Explorer. Same both my computer's. Odd.
Click to expand...
Click to collapse
Did you download the .properties file to the exact folder specifed and did you do a Devices->Manage->Import?

Got it, I missed the bit about renaming the FSC to 58.
Don't remember having to do this when I used to use this!

brocnical said:
Did you download the .properties file to the exact folder specifed and did you do a Devices->Manage->Import?
Click to expand...
Click to collapse
Hey,
I saw your post here: https://forum.xda-developers.com/showthread.php?p=82876277#post82876277
here: https://forum.xda-developers.com/showpost.php?p=82876571&postcount=2
and here: https://forum.xda-developers.com/showpost.php?p=82896159&postcount=2
where each post refers the other in 3 different threads.
Considering that you have already put the effort to write these, would you mind to aggregate this information in a single post, possibly the first post of this thread and rename it to a guide?

stsdema28 said:
Hey,
I saw your post here: https://forum.xda-developers.com/showthread.php?p=82876277#post82876277
here: https://forum.xda-developers.com/showpost.php?p=82876571&postcount=2
and here: https://forum.xda-developers.com/showpost.php?p=82896159&postcount=2
where each post refers the other in 3 different threads.
Considering that you have already put the effort to write these, would you mind to aggregate this information in a single post, possibly the first post of this thread and rename it to a guide?
Click to expand...
Click to collapse
Done.
I have also made a pull request in the FlashTool devices db so that we won't have to do the .fsc and .properties bit in the future.

I have two quick (hopefully related) questions.
1. Has anyone tried to flash XQ-AT51 firmware on XQ-AT52? Obviously, I know Dual SIM may be impacted, but does it work? Any other issues?
2. Is there a CSC version of XQ-AT51 software for USA yet? I couldn't find it on XperiFirm.
Thank you so much!

KlausWillSeeYouNow said:
1. Has anyone tried to flash XQ-AT51 firmware on XQ-AT52? Obviously, I know Dual SIM may be impacted, but does it work? Any other issues?
Thank you so much!
Click to expand...
Click to collapse
I would like to know this too, we might have an answer soon enough since it looks like some people have ordered the 1 ii from wandamobile which basically ships the HK dual sim version.

I'm getting an issue when I'm flashing either the Customized UK rom or the O2 one where it gets stuck installing dsp.000, have you seen this before?
If I exclude dsp.sin from the flash it completes fine but the screen resolution is really basic so I'm assuming its the display drivers. Running a repair from the Sony Companion after the flash fails.
Stuck! Can anyone help? TIA
Code:
26/037/2020 07:37:06 - INFO - (CommandFlasher.java:719) - signature status : OKAY
26/037/2020 07:37:06 - INFO - (CommandFlasher.java:722) - erase:dsp_a
26/037/2020 07:37:06 - DEBUG - (USBFlash.java:85) - Reading packet from phone
26/037/2020 07:37:06 - DEBUG - (USBFlash.java:93) - IN : [email protected]
26/037/2020 07:37:06 - INFO - (CommandFlasher.java:726) - erase status : OKAY
26/037/2020 07:37:06 - INFO - (CommandFlasher.java:732) - sending dsp.000
26/037/2020 07:37:06 - INFO - (CommandFlasher.java:735) - download:04000000
26/037/2020 07:37:06 - DEBUG - (USBFlash.java:85) - Reading packet from phone
26/037/2020 07:37:06 - DEBUG - (USBFlash.java:93) - IN : [email protected]

electric0ant said:
I would like to know this too, we might have an answer soon enough since it looks like some people have ordered the 1 ii from wandamobile which basically ships the HK dual sim version.
Click to expand...
Click to collapse
Agreed 100%. I would like to flash the USA firmware from the XQ-AT51 on my XQ-AT52, but (a) I don't know if it's advisable to do that, and would like to hear from someone who has; and (b) it doesn't appear that there is USA firmware yet for the XQ-AT51!
Hope we get our answer soon.

Apologies if its a noob question but if I flash different region software, will I loose DRM keys?

No

Ok managed to fix my issue, In the end I swapped the cable I was using which didn't occur to me as parts of the flash worked so assumed connectivity was ok.
I originally used the USB C - USB C cable that came with the phone. Swapped that to a USB C - USB A cable and the flash completed successfully!
Massive sense of relief after many hours of messing around with it! Hopefully this might help someone in the future

Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial

In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset.
from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool.
with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa).
MTK-bypass credits to @k4y0z
, @chaosmaster and @xyzz on github.
REQUIREMENTS:
• Python
Download Python
The official home of the Python Programming Language
www.python.org
• libusb-win32
https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
• Sp Flashtool
SP Flash Tool Download All versions for MediaTek Devices
SP Flash tool download is the best application to flash Stock firmware, Custom recovery and fix some extreme issues on MediaTek Android smartphones. Download SP Flash tool all versions from our official download page.
spflashtool.com
• Bypass Utility Compiled
18.9 KB file on MEGA
mega.nz
---------------------------------------------------------------
• Bypass Utility Latest Releases
Release 1.4.1 · MTK-bypass/bypass_utility
Improve handshake reliability
github.com
• Exploits Latest Releases
Release 1.5 · MTK-bypass/exploits_collection
mt6261 mt6572 mt6580 mt6582 mt6735 mt6737 mt6739 mt6755 mt6757 mt6761 mt6763 mt6765 mt6768 mt6771 mt6785 mt6799 mt6873 mt8127 mt8163 mt8173 mt8695
github.com
• Realme 3 (rmx1821) Flashtool Firmware link soon
> I will upload the realme 3 firmware with Scatter File and Auth File for Third Party Flashtool like SP Flashtool soon, but if you have an official firmware of realme 3 with Scatter and Auth File you can use it no matter what version it is.
> If you know how to extract an OFP file, you can download this realme 3|3i firmware and extract the OFP file.
https://fileload.coloros.com/30842RMX1821EX_11_C.17_201117_cb5665f2.zip
> Video Tutorial on how to Extract OPPO | REALME firmware (OFP file)
VIDEO TUTORIAL
TEXT TUTORIAL
INSTALLATION:
• Install Python (tick checkbox "Add Python X.X to PATH") and proceed.
( if you are using windows 10, Download and Install Python 3.9 through Microsoft Store )
• Install lib-usb_win32
{
"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"
}
Click Next>Next> until you see the next image
Click Finish and Launch Lunch Filter Wizard
Choose the "Install a device filter" and click next
You will see this device selection.
Now you will need to connect you phone with power off to computer.
> Hold all the buttons and connect to the computer (wait until you see Mediatek USB Port in libusb Device selection and Install)
(note: you have to select and install it very quick, because the phone disconnect in just a few seconds)
> Wait until it shows this (Click OK and close libusb and Disconnect your phone)
INITIALIZATION:
• Extract Bypass Utility, and go to extracted folder
> type "cmd" in the address bar and hit enter
> in cmd console install (Install pyusb, pyserial, json5)
by typing: pip install pyusb pyserial json5
> after that bypass mtk
by typing: python main.py
> when you see "Waiting for bootrom" , you need to connect your phone again (Holding all button and plug it into your computer and wait until it recognized.)
you should have this following output. do not close this window and remember the Found port of you phone
as you can see my port is = COM7
DO NOT DISCONNECT YOUR PHONE FROM COMPUTER THIS TIME
FLASHING FIRMWARE:
• Extract SP Flashtool and Realme 3 Firmware
• Open flashtool.exe and click Options>Connection
and tick AURT instead of USB.
Select the COM port of the phone which is COM7 in my case
then close Option Window
• Now In Flashtool choose Scatter-File from the Extracted Firmware of Realme 3
(wait until it finished the Processing)
• After that choose Authentication File
• After loading Scatter and Auth File Click Download
It should start downloading the firmware to you phone now without any error.
(wait until it finished the download.)
When finished downloading you get a check windows indicating that the flash was successful!
Thats it Congratulations! You may now disconnect your phone from your computer and POWER ON.
your DEAD [HardBricked] Realme 3 is now Alive!
(Note: This method is applicable to any MTK devices with SoC mt6735, mt6750, mt6765, mt6771, mt6785, mt8127, mt8163, mt8173, mt8695)
For more updates about MTK-Bypass visit the official github page @
MTK-bypass
MTK-bypass has 8 repositories available. Follow their code on GitHub.
github.com
all the tools and utility is not mine. credits to the developer.
Original Bypass Tool xdaThread
[MOD][DEV] MediaTek / MTK - Auth Bypass (SLA/DAA) - Utility
As some of you have already noticed, a couple of weeks ago @Dinolek and I published a utility, that allows bypassing authentication on MTK devices. The tool is based on an exploit dubbed kamakiri, which was originally found by @xyz` and released...
forum.xda-developers.com
special thanks to @popoff-r for mentioning about a thread of repairing MTK devices.

Thanks

fawazahmed0 said:
Thanks
Click to expand...
Click to collapse
so its you , i thought the two in the credits in your github bypass_utility is one who develop it. im sorry sir. im not really familliar where to see the owner of the work it github. im really sorry for not mentioning your name in this. gotta edit now. You are Great sir!

ATDteam said:
so its you , i thought the two in the credits in your github bypass_utility is one who develop it. im sorry sir. im not really familliar where to see the owner of the work it github. im really sorry for not mentioning your name in this. gotta edit now. You are Great sir!
Click to expand...
Click to collapse
Thank you for putting this altogether, this should speed up the development work for this phone(kernel etc), as people don't have to go to service center for hard brick.
Also I want to tell you, I shouldn't get the credits for bypass_utility, the two people you mentioned should be getting the credits, I just forked(copy/cloned) the repository.
I assume you are new to github, anyone can fork(copy/clone) a repository by clicking on fork button
You can differentiate whether a repository is forked(copied) or original by seeing on the top left side.
Thanks

fawazahmed0 said:
Thank you for putting this altogether, this should speed up the development work for this phone(kernel etc), as people don't have to go to service center for hard brick.
Also I want to tell you, I shouldn't get the credits for bypass_utility, the two people you mentioned should be getting the credits, I just forked(copy/cloned) the repository.
I assume you are new to github, anyone can fork(copy/clone) a repository by clicking on fork button
View attachment 5205247
You can differentiate whether a repository is forked(copied) or original by seeing on the top left side.
View attachment 5205251
Thanks
Click to expand...
Click to collapse
Thank you so much that was a very helpful information.

How to fix this error sir..

What Error?, please provide screenshot of the error, if you can't explain it.

ATDteam said:
What Error?, please provide screenshot of the error, if you can't explain it.
Click to expand...
Click to collapse
Tihis sir

What Error?, please provide screenshot of the error, if you can't explain it.
Al Djufri said:
Tihis sir
View attachment 5207505
Click to expand...
Click to collapse
try to uninstall python and reinstall again, also download the bypass_utility, the one that i attached in this thread.
and try again. make sure your usb cable is working properly, it seems that your device does not read properly by the utility. change your cable if posible. Download python 3.9, if still doest work. try using windows 10 OS.
18.9 KB file on MEGA
mega.nz

ATDteam said:
What Error?, please provide screenshot of the error, if you can't explain it.
try to uninstall python and reinstall again, also download the bypass_utility, the one that i attached in this thread.
and try again. make sure your usb cable is working properly, it seems that your device does not read properly by the utility. change your cable if posible. Download python 3.9, if still doest work. try using windows 10 OS.
18.9 KB file on MEGA
mega.nz
Click to expand...
Click to collapse
Reinstalling python
Reinstalling lib libusb
Changing usb cable
Changing port usb
Change pc, i mean borrow a pc from my friend
Changing spflashtool, same problem sir?
Do you have telegram account

thanks it works thanks for saving my phone

Its not the same in your first screenshot you reach "Disabling protection" but in the 2nd one only the utility found your phone..., did you release all the buttons emmidiately after your computer detects your phone phone? It is important that you release emmidiately. Did you try to use windows 10.? Sorry I dont have telegram.
Al Djufri said:
Reinstalling python
Reinstalling lib libusb
Changing usb cable
Changing port usb
Change pc, i mean borrow a pc from my friend
Changing spflashtool, same problem sir?
Do you have telegram accountView attachment 5208303
Click to expand...
Click to collapse

XxRRSxX said:
thanks it works thanks for saving my phone
Click to expand...
Click to collapse
Thanks for using this thread as your guide, but credits is to the developers of the Utility.

ATDteam said:
Its not the same in your first screenshot you reach "Disabling protection" but in the 2nd one only the utility found your phone..., did you release all the buttons emmidiately after your computer detects your phone phone? It is important that you release emmidiately. Did you try to use windows 10.? Sorry I dont have telegram.
Click to expand...
Click to collapse
I'm trying to with my friend pc(windows 10) using latest python and same error sir..
Always Immediately release my button when pc detection my device.. but same error

( SOLVED )
you must be use windows 10
Use latest python version
Use latest SpFlash tool version
And don't forget to chek libusb instalation
Check via cmd "pip install libusb" and "pip install libusb1"
And try to use command "python main.py"
Sorry for my English..
Thanks sir..

Al Djufri said:
( SOLVED )
you must be use windows 10
Use latest python version
Use latest SpFlash tool version
And don't forget to chek libusb instalation
Check via cmd "pip install libusb" and "pip install libusb1"
And try to use command "python main.py"
Sorry for my English..
Thanks sir..
View attachment 5208681
Click to expand...
Click to collapse
Nice thats great! sometimes you really need to be on Trial and Error before you achieve what you want. happy for you. Thank you for using my thread as guide, Credits to the developers of the utility. and you have a good english. mine is bad. :-D

Anyone who facing problem when bootrom check, you have to flash first time or it will show error. Otherwise you have to uninstall and reinstall libusb.exe and others.

Ok, thanks to ATDTEAM, very much, I bricked by patching boot image with magisk and flashing it, successfully flashed stock rom .ofp with SP Flash tool, not only this , I itentionally flashed another version , and it worked to, thnx to the bypass utility, it generates questions, the realme provides ozip files, so where are .ofp files coming from, or where we can get it, and... Fawazahmed0 , I am unable to flash twrp, I tried everything I could, I am on updated Android 10 c.19 now, so I can't flash custom recovery or root it... I can't even rollback bcoz I unable to find the older version ofp files, the ozip files just don't install, so please help for rooting Android 10, You have solved a major hurdle by introducing the method of bypass sp tool flashing but, the next step of flashing custom recovery and then rooting awaits... Pls help/ guide, Thnx...

Thanks brother, I've recently unbricked my device