Related
1st way :
Pulled full OTA file for Lenovo Vibe Shot - z90a40 ROW
Installation Procedures for the official rekaveri following:
Clean, not rutirovannaya and the changed S240-th firmware.
Be sure to set the region code. After the update, you do not change ...
Download the file update.zip and throw your phone. I checked on the external memory card.
Reboot in rekaveri. Select English and tychem to Install update.zip
What follows is some question about the installation. Select YES
The installation process is 100% dlitelnyy.Posle installation still some time to think. Do not panic.
After installation is complete, select the restart system . The first start will be long enough.
I recommend to do a factory reset. In order to avoid possible problems during the transition from one to another OS
2nd way :
How to install TWRP rekaveri for the following:
Installed S240-th firmware.
Be sure to set the region code. After the update, you do not change ...
Download the archive TWRP_lenovoota.zip and throw your phone. I checked on the external memory card.
Reboot in rekaveri. Select Install and update the file with.
Make wipes are cache, dalvik-cache, data and phone.
After installation is complete, reboot the system. The first start will be long enough.
I recommend to do a factory reset. In order to avoid possible problems during the transition from one to another OS
down load files : https://cloud.mail.ru/public/36qb/qhqsDGNVr
3rd: for who have problem with 1st & 2nd
1- download thise file :http://lenovo-forums.ru/topic/19311...363_160625_row/?do=findComment&comment=497835
2- Installing the firmware using QFIL on the Lenovo device based on Qualcomm chips:
(A)
We set vcredist_x86.exe , which go in the complete set with "proshivalschikom" itself;
set himself "flasher" - QPST.2.7.422.msi ;
install drivers for the Qualcomm chips - they are in the archive Qualcomm_USB_Drivers.7z
(B)
Completely turn off your device , and then we press the volume up key (Volume Up), and holding it connect the USB-cable which is already connected to the USB 2.0 port of your PC - in the Device Manager, you should see the device Qualcomm Lenovo HS-USB QDLoader 9008
3-Just install the firmware: -
(A)
Run the program QFIL
In the Programmer patch specify the path to the file prog_emmc_firehose_89XX.mbn (in my case prog_emmc_firehose_8916.mbn)
, for this click on Knop «the Browse» , in the window that opens, specify the path to the folder with the firmware (in my case ROW_S121), then choose prog_emmc_firehose_89XX.mbn file and click "Open" . then click on digging "the Load the XML ..." , alternately choose in the window that opens - first rawprogram0.xml and click "Open", and then patch0.xml and also click "Open".
http://lenovo-forums.ru/uploads/monthly_12_2014/post-53625-0-76252800-1419253051.png
(B)
Open the Device Manager on your PC, then turn off the device (smartphone or tablet) and take out the USB-cable from the device (if it was connected).
The device should restart at the successful process of filling the firmware and boot into Android OS.
http://lenovo-forums.ru/uploads/monthly_12_2014/post-53625-0-39327800-1419253052.png
for root :::::::::
1ST : Unlock BootLoader
1. Install the software package QPST and drivers LenovoUsbDriver , QualcommUSBDrivers on your computer ( drivers are archived Service QPST programs )
2. Unpack the archive Z90a40_Android-L_unlock_7M.7z to the root of any drive.
3. Connect the device ( Z90a40 ) to a PC via USB-cable.
4. On your device, turn on debugging by the ADB .
5. Run the utility QFIL :
- in the line Select Build Type , select the Flat the Build
- in line Select Programmer press the button Browse and specify the path to the unzipped files \ Z90a40_unlock_7M \ the img \ prog_emmc_firehose_8936.mbn
- click on the button Load XML and select the first rawprogram0.xml and then patch0.xml
http://lenovo-forums.ru/uploads/monthly_2016_04/sshot-1.png.661990ee862f9d3e35653a046c561c4a.png
6. Run Reboot_QDLoader.bat::
http://lenovo-forums.ru/uploads/mon...7M_3.png.3018b3c020fc59cdab5e8b73461cc42e.png
7. In the main program window to see that the device is switched to the mode Qualcomm HS-USB QDLoader 9008 .
http://lenovo-forums.ru/uploads/monthly_2016_04/sshot-2.png.a73fc14b40f138b5a2fa71480a6df072.png
8.Start the process of firmware bootloader unlocked by pressing the button Download .
(If you have not defined QFIL utility device Qualcomm HS-USB QDLoader 9008 mode, then you should check through the Device Manager on your PC - there are no problems with Qualcomm driver)
9. At the end of the process unlocked bootloader firmware to the device you will see a sign in the window Status QFIL program the following lines:
Download Succeed
the Finish Download
http://lenovo-forums.ru/uploads/monthly_2016_04/sshot-3.png.3a5566b24283b342edc285b724004305.png
10.Turning off the device from the USB-cable and clamp button Power to turn on the device (sometimes takes up to 10-20 seconds).
11. Open the main settings menu, the device and go to the " About phone -> Device Information " and press 7 times to select " Build number " until the display shows that you have become a developer.
12. Go back to the device's main Settings menu and go to the " For Developers " in " Factory Unlock " switch the toggle switch in the ON state .
13.Turn off the device (Z90a40), we press both volume buttons and connects to a PC via a USB-cable (the device enters the mode fastboot ), then run Unlock_Bootloader.bat
You should see the value of true if the secondary Bootloader check the status in the string the Device unlocked :
(Bootloader) Device tampered: false
(Bootloader) Device unlocked: true
(Bootloader) Charger screen enabled: false
(Bootloader) Display panel: A
OKAY [0.046s]
finished. total time: 0.046s
http://lenovo-forums.ru/uploads/monthly_2016_04/sshot-4.png.49581f68c35fd8e8922eaef936037988.png
14.So all of this unlocking process is completed successfully .
files need links :
http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=56368
2nd: to do ( install TWRP 3.0.2.0 for Lenovo Vibe Shot )
Extract the folder TWRP archive TWRP-3.0.2.0_Z90a40_by_SevenMaxs.7z to the root of any drive
Turn off the device ( Z90a40 ), we press both volume buttons and connects to a PC via a USB-cable; the device will go into fastboot mode (on the PC must be set for the driver ADB).
Connect your phone to a PC via usb-cable, and run the Flash-TWRP.bat ( the Run-TWRP.bat for a single run TWRP.)
We are waiting for the phone to boot into TWRP
You can now disconnect the usb-cord
Installation is finished!
links : http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=56391
Login or TWRP:
On the device is turned off hold down both volume buttons and the inclusion of produce, release the power button immediately once the device is turned on and the volume buttons once away; boot logo TWRP.
3rd : install su from twrp
su.zip link : https://drive.google.com/file/d/0BxQ_dY80FUzYUXN6QThDd3pSWWc/view?usp=sharing
4th: install xposed.zip ( the erorrs have been solved)
link :
soooooooooooooooooooooon
soz for error happen before
updated 23/8/2016
that's all
Everything is fine, but TWRP in Russian how to change it to English?
xposed mode is not installing
in TWRP its said that I/O error on system folder.
MOD EDIT: Please don't quote the OP
In Chinese MM which used the same TWRP i guess
I played with buttons it is one of the bottom buttons
It will give you a blue screen with tabs
One of them has the earth planet icon
It contain languages you will find english within them
Please confirm that rooting was successful on official S363 MM or not
Sent from my Lenovo VIBEShot
shouk_1987 said:
In Chinese MM which used the same TWRP i guess
I played with buttons it is one of the bottom buttons
It will give you a blue screen with tabs
One of them has the earth planet icon
It contain languages you will find english within them
Please confirm that rooting was successful on official S363 MM or not
Sent from my Lenovo VIBEShot
Click to expand...
Click to collapse
Root successful :good:
but I cant able to xposed framework
because in TWRP its says "cp: can't stat "/system" I/O error"
---------- Post added at 03:49 AM ---------- Previous post was at 02:51 AM ----------
cant able to install xposed framework tried everything
Sent from my Lenovo Z90a40 using XDA Premium 4 mobile app
xposed worked with me and now erorr
sorry for that but it solved try agine
since root of the rom I tried about hundred times but still xposed framework not installed ?
Sent from my Lenovo Z90a40 using XDA Premium 4 mobile app
yasirriaz1977 said:
since root of the rom I tried about hundred times but still xposed framework not installed ?
Click to expand...
Click to collapse
Try new zip
shouk_1987 said:
In Chinese MM which used the same TWRP i guess
I played with buttons it is one of the bottom buttons
It will give you a blue screen with tabs
One of them has the earth planet icon
It contain languages you will find english within them
Please confirm that rooting was successful on official S363 MM or not
Click to expand...
Click to collapse
All work now
elbhrawy said:
Try new zip
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?act=attach&id=7533763&dlsess=8f37b888e4eb17f073e312a5fa82e658 new link give me error like this
Sent from my Lenovo Z90a40 using XDA Premium 4 mobile app
yasirriaz1977 said:
http://4pda.ru/forum/index.php?act=attach&id=7533763&dlsess=8f37b888e4eb17f073e312a5fa82e658 new link give me error like this
Click to expand...
Click to collapse
I will upload now
elbhrawy said:
I will upload now
Click to expand...
Click to collapse
eagerly waiting for xpposed to work on my charmed device
yasirriaz1977 said:
eagerly waiting for xpposed to work on my charmed device
Click to expand...
Click to collapse
Updated
elbhrawy said:
Updated
Click to expand...
Click to collapse
Downloading ..........................................
when installed will update here soon.....:good:
update.........
same error
cp:can't stat '/system/xposed.prop': I/O error
updater process ended with ERROR: 1
Error installing zip file '/sdcard/Z90a40 restoration/xposed-v80-sdk23-arm64-by-romracer-20160202.zip'
update .........
after aforementioned error my device also unroot
now I am going to root it again
yasirriaz1977 said:
Downloading ..........................................
when installed will update here soon.....:good:
update.........
same error
cp:can't stat '/system/xposed.prop': I/O error
updater process ended with ERROR: 1
Error installing zip file '/sdcard/Z90a40 restoration/xposed-v80-sdk23-arm64-by-romracer-20160202.zip'
update .........
after aforementioned error my device also unroot
now I am going to root it again
Click to expand...
Click to collapse
its worked with me
elbhrawy said:
its worked with me
Click to expand...
Click to collapse
but its not worked for me, please do something
Sent from my Lenovo Z90a40 using XDA Premium 4 mobile app
i have problem with update
the update.zip block at 45% update
i'll try with file TWRP_lenovoota.zip...where i'll put the file?
on sd card ...but i put it in specific folder? rename the file?
tnx in advance
il_milanese said:
the update.zip block at 45% update
i'll try with file TWRP_lenovoota.zip...where i'll put the file?
on sd card ...but i put it in specific folder? rename the file?
tnx in advance
Click to expand...
Click to collapse
use qfil better
I have the bootloader unlock and TWRP installed,
the TWRP recovery let me know that i have no SO installed.
how can I install/flash a rom without brick the phone with this recovery installed?
Things to mustnt do with TWRP installed?
i've been 2 days without phone(bricked). I need help
Thank you
a bit confussing cause the english not too good, look like translated from other language.
can somebody fix it?
so can i have root with marsmallow?
Thank U.
OTA update v363 Ok. Thank U.
Hello everyone ,
This is my firt's tutorial !
Today i'm going to teach you how to root your phone ( in my case it's a Ulefone Germini Pro ) and restore IMEI's.
/!\ATTENTION/!\ i don't take any responsability for anything that happen to your phone ! So do it at you own risk ! /!\
Before starting , my phone as a MTK chipset , so i don't advise you to try this if your chipset isn't a MTK ! And you need a OTG cable with a mouse !
Lets go :
TO ROOT [WORKS FOR ULEFONE GERMINI PRO] :
Important be sure to download PDANET it will solve alot of problems with the drivers !!
0-Enable USB DEBUGGING
1- Download the stock rom of your phone and check if is the same version as your phone ! ( exemple : my phone is an android 7.1.1 so i need to download the stock room version 7.1.1)
2- Download the drivers : http://www.devfiles.co/download/0InO9P5m/MT65xx_USB_VCOM_DRIVERS.zip and install them !
3-Download twrp (recovery.img) : https://mega.nz/#!8f43VYLa!o-elPp74o35tm3AdtcW1wVbFnBHIGi_dUP7skWWGmOM
4-Download Modified Boot (boot.img) : https://mega.nz/#!sHQxySJL!MRqtD6-VoZMLyEpr-ym7LlktiMR0GXYKUuLZlpbxhE0
5-Download latest version of SPFlash Tool : http://spflashtools.com/category/windows
6-Now you need to download SuperSu , but this one as to be downloaded with your phone directly on you need to put it on a sdcard , as you want !
here's the link : https://download.chainfire.eu/supersu-stable
7- Run Flashtool.exe
8- Choose scatter file ( it's on your downloaded Stock Rom )
9- Untick everything
10- Tick recovery
11 - Click on location to choose the custom recevery.img ( you downloaded before )
12 - double check only recovery is tick
13- Turn off you phone and plug it one time and check if the pc detect's it
14 - Unplug it
15 - So now the phone stills off , on sp flash tool click download
16- Plug your phone and wait few seconds
17 - the flashing should start
18 - if all go well you could see a green arrow on the program
19 - now untick recovery
20 - tick boot
21- click on location and find your custom boot.img
22 - and flash it the same way as recovery.img
23 - Now as a said before if you have downloaded SuperSu direclty in your phone , just turn it on by pressing power + volume UP
24 - You should see a little menu , use volume up to choose recovery and volume down to confirm it
25-TWRP should appear
26 - Put the otg cable on your phone and plug a mouse on it
27 - you should get a message asking to modify system , with the mouse slide to authorize
28 - after that click on install
29 - choose the superSU.zip where you download it
30 - slide to flash it
31 - Reboot and you should get rooted
32 - Enjoy
TO RESTORE YOUR IMEI'S :
You need :
-PC
-The Program
-The Stock room you downloaded before
- The drivers
- The box of your imei's
Let's go :
0- Download the program
http://www12.zippyshare.com/v/UafLqKD2/file.html
Important be sure to download PDANET it will solve alot of problems with the drivers !!
1- Start the program
2- Go to help about sn and check that you have a new version mine is : 1.1604.00
3- Comport : select USB VCOM
4- Target Type : Select SmartPhone
5- click on system config
6- tick imei and dual imei ( if you have 2 imei's else tick only imei )
7- click on MD1_DB and choose a file in your stock rom that the name start like this :
MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V62_4_P3_1_ulwctg_n.EDB
Be sure to check that and the end of the file is a .EDB
8- click on AP_DB and choose a file in you stock room that the name is start like this :
APDB_MT6797_S01_alps-mp-n1.mp9_W17.18
Be careful you stock room can contain to files choose the one that end with a number and not with a ENUM
9 - click on save
10 - power off you phone and disconnect it from the pc
11- press start
12 - put you imei's
13 - press ok
14 - connect your phone
15- if it's all okay you should see a message with passed on it ! IF it fails try again one time because my firts time failed too
16 - After getting the message passed , disconnect your phone and turn it on !
17 - You should get your imei's back !
18 - ENJOY !!
Credits :
Annubiis : For helping with my phone.
RAMANDEEP SINGH from androidweblog.
dodos from bbs.elephone .
If it helped you click on say thank's and if you need help comment this post !
Thanks alot bro it worked for my lenovo k8 plus dual sim phone...... and also PdaNet is must i understood.....
Redmi note 7 pro working ?
Mine is Samsung m10s, exynos, latest version Android 11. Do u think it will woerk on my phone, actually my phone says imei NG status and I'm unable to make calls, mobile data or sms. Please help me
Hello everyone ,
so , I've been this and here is what i did to get back to normal :
1- download MiFlash and the oreo 8.1 (V9.6.8.0.ODHMIFE) fastboot image from here
2- download *adb* file that i upload , and extract the files
3- download this file ,and extract the files , you will find *TWRP* folder
4- copy or move *adb* folder to the C:\
5- use Miflash to flash the fastboot image
6- when your phone start bootlooping go to the fastboot in the phone
7 - open the *adb* folder and run *Command Prompt* , write *fastboot boot recovery.img*
8- when the TWRP start go to pc and copy *TWRP* folder and place it in the main internal
9-go to restore in TWRP and chose the backup folder , restore *Boot* and *EFS* and swipe (if it doesn't show anything to restore go to TWRP>backup and copy *2018-12-06--15-41-27_PQ1A181205006* folder into *TWRP* folder "not to backup folder")
10- now in TWRP go to reboot and click bootloader
11- you will go to fastboot , flash oreo 8.1 (V9.6.8.0.ODHMIFE) by MIflash
12- everything will get back to normal !! :highfive:
update (3-10-2019) :
i recommend to flash latest official mi a1 rom maybe well fix it (using fastboot) ,
any way here is new link for TWRP file http://www.mediafire.com/file/j6682qbs7qa5sg5/TWRP.7z/file
thanks to :
@joeyhuab for the advice
@berlin51 for the link
@abhishek987 for the recovery image file
So this will not mess up any IMEIs or anything? Is this a universal solution for everyone who messed up?\
EDIT: Nevermind, used the guide, works fine. Thanks for that!
It's working. Thank you!
Just need to copy "2018-12-06--15-41-27_PQ1A181205006" to TWRP folder.
following the tutorial, but my sim card didnt work, any solution?
adnbwta said:
following the tutorial, but my sim card didnt work, any solution?
Click to expand...
Click to collapse
IMEI must've got corrupted
Dail *#06# and check if it is showing phone's IMEI numbers n not zeroes
UCFour said:
IMEI must've got corrupted
Dail *#06# and check if it is showing phone's IMEI numbers n not zeroes
Click to expand...
Click to collapse
imei still there, both sim, but in settings-imei SV both are 00, anyway to fix it?
adnbwta said:
imei still there, both sim, but in settings-imei SV both are 00, anyway to fix it?
Click to expand...
Click to collapse
SV values are zeroes by default
Try to flash the same fastboot rom again but this time via EDL mode [ fastboot oem edl] using miflash
UCFour said:
SV values are zeroes by default
Try to flash the same fastboot rom again but this time via EDL mode [ fastboot oem edl] using miflash
Click to expand...
Click to collapse
Can you explain a bit
Sent from my OnePlus5T using XDA Labs
If anyone is planning to flash Pie stable/beta
1. First take a backup of EFS from TWRP and Low level backup of all partitions ( system n data not needed ) with low level backup tool via EDL
2. In order to get Pie booted, you just need "System.img" extracted from the OTA ( use payload dumper) or just take the system.img file floating around here
3. Transfer System.img to adb folder >> Boot to fastboot and flash the system.img only
fastboot flash system_a system.img
fastboot flash system_b system.img
Everything works except dual 4G/VoLTE
Downgrade will also won't have any issues
> For Dual 4G/VoLTE, you also need to flash modem and rpm
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img [ Optional]
But now if you try to downgrade , you might end up with bootloop
>> To Fix bootloop, boot to EDL
Flash the fastboot rom you were running before when you took back of partitions
Then Use lowlevel backup tool to restore all the partitions and reboot
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
Amanpreetsingh said:
Can you explain a bit
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
Procedure is same as flashing fastboot rom via EDL mode with MiFlash but instead of flashing it from fastboot try it from EDL mode
Use this command within fastboot mode to get to EDL
fastboot oem edl
Total process will take 10+ minutes, once the flashing status changes to "Success", hold the power button for around 10 seconds to reboot
UCFour said:
SV values are zeroes by default
Try to flash the same fastboot rom again but this time via EDL mode [ fastboot oem edl] using miflash
Click to expand...
Click to collapse
done that, but the sim still not showing, tried to swipe sim to slot 2 but no change, really confused right now
adnbwta said:
done that, but the sim still not showing, tried to swipe sim to slot 2 but no change, really confused right now
Click to expand...
Click to collapse
Check if those IMEI numbers are your phone ones only? AFAIK EFS is device specific which contains information like IMEI, MAC Address..
UCFour said:
Check if those IMEI numbers are your phone ones only? AFAIK EFS is device specific which contains information like IMEI, MAC Address..
Click to expand...
Click to collapse
both IMEI in the settings and in the box are the same, but now after flash image from EDL both IMEI become 0 and unknown, any solution?
adnbwta said:
both IMEI in the settings and in the box are the same, but now after flash image from EDL both IMEI become 0 and unknown, any solution?
Click to expand...
Click to collapse
Use this guide
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
1. Download 7.8.23 Nougat Fastboot rom, flash it via EDL
2. If the phone boots fine to OS, Great! [ IMEI fix only possible with Nougat ] else restore the EFS again via TWRP [ Don't restore anything else modem/boot] to get the rom booted
3. Download Qualcomm dailog driver, IMEI to Hex converter, HEX Editor and QPST tool [ Latest ]
4. Open IMEI to HEX Converter, inpur your IMEIs and save the hex numbers somewhere else
5. Now download the QCN file linked in this post, open the QCN with hex editor and navigate to the address locations 0x17C50 & 0x02530 and replace the hex values "08 8A 16 11 11 11 11 11 11" and "08 8A 26 22 22 22 22 22 22" with the ones you saved before and save the QCN file [ You can can .qcn extension if this file doesn't work in the final step ]
https://forum.xda-developers.com/showpost.php?p=76496159&postcount=23
5. Now type *#*#717717#*#* , you will see dialog port enable status
6. Connect phone to PC, enable Dev options and USB Debugging
7. Open QPST [ Software Download ], Restore Tab see if the port is showing. If it isn't update the driver within device manager
If the port isn't showing even after driver update, detach the phone USB and re-connect phone
8. with the Com port displayed, select browse under xQCN file tab and the select the QCN file u modified with your IMEI numbers
9. Select "Allow ESN Mismatch" and hit start >> wait until status changed to memory process done successfully (something similar)
10. Reboot phone and everything will be fine
After everything is done, first its better to update to Oreo via OTA first [ Two 1GB Updates ] and then flash oreo fastboot rom
UCFour said:
If anyone is planning to flash Pie stable/beta
Click to expand...
Click to collapse
Is that for people who flash it through fastboot or is this required if we update to the stable through OTA as well?
michkost858 said:
Is that for people who flash it through fastboot or is this required if we update to the stable through OTA as well?
Click to expand...
Click to collapse
There is no official fastboot rom yet, the one available has the contents of extracted payload.bin from the OTA
Even if you update your phone via official stable OTA, you will be facing same downgrade issues
Yeah i meant it for those who are planning to flash via fastboot as most OTA users with locked bootloader wouldn't bother to downgrade
Please help me I did the steps and manages to restore the stock rom, but I get a message saying "phone not allowed" And when I want to make a call tells me "mobile network not available "
UCFour said:
Use this guide
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
1. Download 7.8.23 Nougat Fastboot rom, flash it via EDL
2. If the phone boots fine to OS, Great! [ IMEI fix only possible with Nougat ] else restore the EFS again via TWRP [ Don't restore anything else modem/boot] to get the rom booted
3. Download Qualcomm dailog driver, IMEI to Hex converter, HEX Editor and QPST tool [ Latest ]
4. Open IMEI to HEX Converter, inpur your IMEIs and save the hex numbers somewhere else
5. Now download the QCN file linked in this post, open the QCN with hex editor and navigate to the address locations 0x17C50 & 0x02530 and replace the hex values "08 8A 16 11 11 11 11 11 11" and "08 8A 26 22 22 22 22 22 22" with the ones you saved before and save the QCN file [ You can can .qcn extension if this file doesn't work in the final step ]
https://forum.xda-developers.com/showpost.php?p=76496159&postcount=23
5. Now type *#*#717717#*#* , you will see dialog port enable status
6. Connect phone to PC, enable Dev options and USB Debugging
7. Open QPST [ Software Download ], Restore Tab see if the port is showing. If it isn't update the driver within device manager
If the port isn't showing even after driver update, detach the phone USB and re-connect phone
8. with the Com port displayed, select browse under xQCN file tab and the select the QCN file u modified with your IMEI numbers
9. Select "Allow ESN Mismatch" and hit start >> wait until status changed to memory process done successfully (something similar)
10. Reboot phone and everything will be fine
After everything is done, first its better to update to Oreo via OTA first [ Two 1GB Updates ] and then flash oreo fastboot rom
Click to expand...
Click to collapse
i follow the tutorial, but the imei in phone is different with the one in the box, maybe I did something wrong in step 5, can u tell me how to change or remove imei?
adnbwta said:
i follow the tutorial, but the imei in phone is different with the one in the box, maybe I did something wrong in step 5, can u tell me how to change or remove imei?
Click to expand...
Click to collapse
If the IMEI is different then u haven't edited the QCN correctly
Flash Nougat firmware again via EDL
and this time edit the IMEI hex values correctly in the qcn file via hex editor
Also make sure u have converted your IMEI to hex values
for me nothing is showing in twrp folder in restore
pls help
i folled the steps in op properly
---------- Post added at 06:24 AM ---------- Previous post was at 06:01 AM ----------
jai krishna said:
for me nothing is showing in twrp folder in restore
pls help
i folled the steps in op properly
Click to expand...
Click to collapse
I took my own backup of boot and efs.so one folder created in twrp folder.
i replaced my files with the downloaded files given in op
thanks a lot.love u all
I have a question, I am on Android P official BETA flashed with TWRP. I have backed up my previous P PE ROM with Boot, EFS, Persist, Modem full Nandroid Backup. Can I flash official P STABLE (Fastboot ROM) with MiFlash Tool when its available?? Without bricking my device??
The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.
placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed
After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.
Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now
Thread was opened.
mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot
Would this work on Blu Vivo XI since same chipset?
sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer
Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof
mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!
Code:
[B]DISCLAIMER[/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
**All credits for this guide go to Denver Alfito Anggada and Realme 3 pro Indonesia Group. I am just sharing it here for the benefit of those people who are not on Telegram**
UNLOCK BOOTLOADER
1.Download the In depth test APK (see attachment)
2.Open the In Depth Test application
APK then tap In Query Application Status
Request Submission then
wait about 5 minutes
4. Tap the back button in the left corner
top then reopen
In Query Application status
5. When "Review Sucessful " appeared, tap
start in depth test.
6. The device will then
enter fastboot, then plug the
device to PC. Download and install
fastboot (https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/)
then move the folder named
"platform-tools" to the desktop
(recommended).
7. Open the platform-tools folder
then right-click +shift, then select
open command window here (Win
7) or Open Windows
Powershell (Windows 10)
8.a. For Windows 7, you must have
installed NET Framework
4.5. Type "fastboot flashing unlock "
b. For Windows 10, type
"./fastboot flashing unlock "
9. Then, press the volume button
to UNLOCK BOOTLOADER
10. CONGRATULATIONS! YOU HAVE
SUCCESSFULLY UNLOCKED YOUR
BOOTLOADER
HTML:
<iframe width="560" height="315" src="https://www.youtube.com/embed/mZMVohIuOYU" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
TWRP
**INTERNAL MEMORY WILL BE WIPED! BACKUP BEFORE PROCEEDING**
11. Turn off your device
12. Hold the volume key
-down + power to device
-go to fastboot
13. Plug the device into a PC / Laptop
14. Download recovery.img (https://drive.google.com/file/d/1z8Mv2IBstJchXlbsHpL-Xxup2Xr_O7gR/view)
Move the recovery file that you have downloaded into the folder platform-tools
15. Inside the folder, Shift + Right-click then select open command window here (Windows 7) or open Windows Powershell (10)
16.
a. type fastboot flash recovery.img (Windows 7)
b.
type ./fastboot flash recovery.img (Windows 10)
17. After getting OKAY written, Continue to install VBMETA (see attachment)
18. Move the vbmeta.img file into the platform-tools folder
19. Return to Windows Powershell /Command prompt then type fastboot - disabled-verity - vbmeta flash-verification-enabled vbmeta.img (Windows 7)
./fastboot - disabled-verity - vbmeta flash-verification-enabled vbmeta.img (Windows 10)
20. Press the volume button to Recovery then press power to confirm
21. After entering Recovery, make sure the device is still plugged in,the select wipe then FORMAT DATA, type yes, then tap back and reboot to recovery.
22. After returning to recovery, copy Charlie Decryption by Nitish (see attachment) to your device through computer
23. Flash fix and VOILA! you successfully installed TWRP on your device
INSTALL GSI
**ONLY FLASH A/B GSI**
24. To flash GSI, enter the GSI file on your device (make sure already in the img format, if not yet, try extracting first.
25. Then, in TWRP, press install, then open the file location you, if it doesn't appear, press install the image below right,then tap the file
26. Tap System Image and slide to flash
27. VOILA YOU HAVE SUCCESSFULLY FLASHED GSI ON YOUR DEVICE
Some GSI's you can try:
AOSIP: https://sourceforge.net/projects/il.../AOSiP-9.0-GSI-arm64_ab-20190604.img/download (or whichever is latest)
Bootleggers:https://androidfilehost.com/?fid=1395089523397961183 (or whichever is latest)
Havoc OS:https://androidfilehost.com/?fid=6006931924117888100
MAGISK
Download and extract patched image.tar (https://drive.google.com/file/d/1W1DYJJH6g7AgtT3SCCDdtag1u_F9TMX-/view?usp=drive_open)
Unlock bootloader (if you haven't)
Place all extracted images in ADB tool’s folder.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
If your device asks for permission to “Allow USB debugging”, tap OK.
Once your device boots into bootloader mode, type these into the command line.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Reboot device into system
Done
if you boot on gsi you will get full mode magisk (able to use module )
if you boot on colorOS you will get core mode magisk (not able to use module )
if you boot GSI with magisk , install magisk module named SafetyPatch , this will give you safety net passed
*THE END*
Wow. Thanks a lot bro. Anyway have you tried the gsi rom? What knid ofbugs on realme 3 pro? Some says fingerprint not work, etc.
matrix0807 said:
Wow. Thanks a lot bro. Anyway have you tried the gsi rom? What knid ofbugs on realme 3 pro? Some says fingerprint not work, etc.
Click to expand...
Click to collapse
Fingerprint/pin/pattern not working
Problems with making calls (you can make call but cannot end it) I think it is related to VoLTE
Bluetooth music (Potential fix: Go to Vendor/Overlay/BluetoothResCommon.apk delete this apk, then reboot...BT music works...) need confirmation
Bluetooth incall audio
Confirmation
Is this process working successfully?
Yes many people have followed this method
Hb20032003 said:
Fingerprint/pin/pattern not working
Problems with making calls (you can make call but cannot end it) I think it is related to VoLTE
Bluetooth music (Potential fix: Go to Vendor/Overlay/BluetoothResCommon.apk delete this apk, then reboot...BT music works...) need confirmation
Bluetooth incall audio
Click to expand...
Click to collapse
I hope I can add busybox or Xposed modules without bricking/bootlooping my phone ?
Failed fastboot commamd
I am getting failed (write to device failed (too many links)) when using fastboot command please help
How to relock bootloader
TWRP corrupted my device when I flashed now don't wanna take more risks. How to relock the bootloader please
failed (write to device failed (too many links))
Muktesharyan said:
I am getting failed (write to device failed (too many links)) when using fastboot command please help
Click to expand...
Click to collapse
I was facing the same issue on my Windows 10. To solve the issue run the same command in a windows 7 PC. It worked for me 100%. i wasted the entire day searching for the solution. but switching to good'ol windows 7 pc fixed it.
Can someone help me..I'm stuck after the following command..
./fastboot - disabled-verity - vbmeta flash-verification-enabled vbmeta.img
Command prompt says unknown command -
PS: I modified like this.. ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img everything went smooth, but rootchecker says no root access. What might be the problem?
PS: I run magisk app, now it's been rooted.
Edit: Magisk installation is lost after sometime. No root access anymore. Guide need update. Had to follow other method. Thanks to @4j17h for helping me.
Is it possibleto unlock the bootloader without the depth test apk part?
Okay I can enter TWRP after following the first part of the guide....
until I followed the Magisk guide, then I cant enter TWRP anymore...
Also, does anyone knows how to remove that irritating red flashing saying that you rooted your device?
Hb20032003 said:
Fingerprint/pin/pattern not working
Problems with making calls (you can make call but cannot end it) I think it is related to VoLTE
Bluetooth music (Potential fix: Go to Vendor/Overlay/BluetoothResCommon.apk delete this apk, then reboot...BT music works...) need confirmation
Bluetooth incall audio
Click to expand...
Click to collapse
Hi,
I am trying to delete BluetoothResCommon.apk , but it says file system is read only , Can someone help me out here.
Regards
Need help
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
do you have tutorial to remove bloatware/pre-installed in RM 3 Pro ?
No bootloader
Hi, I tried to unlock the bootloader of my Realme 3 Pro on latest version A15, but something went wrong after the Depth Test app.
When I try to boot the bootloader, it only shows me a monkey icon, with letters in chinese (I guess), with something like 6 10 written, then it reboot.
Tried to install stock A14, but nothing changed.
Would be glad if someone know a solution.
jayroulm953 said:
do you have tutorial to remove bloatware/pre-installed in RM 3 Pro ?
Click to expand...
Click to collapse
If you're rooted then no worries, just use TiBu to uninstall all those bloatwares.
Samdroid18 said:
If you're rooted then no worries, just use TiBu to uninstall all those bloatwares.
Click to expand...
Click to collapse
without root ? no chance ?
Hello...!!!! Do you know why the phone does not go into fastboot mode when you start the depth test? It restarts in system mode. Thank you.
Pasku21 said:
Hello...!!!! Do you know why the phone does not go into fastboot mode when you start the depth test? It restarts in system mode. Thank you.
Click to expand...
Click to collapse
I have exactly the same problem, I don't know what to do...