Credit to @user_ScoTTT
1. First of all, you need to sign up and login on the official website of Oppo in China. (Use Google Translate if you need to)
https://bbs.coloros.net/graphic?id=1498611
2. Follow the links and download the unlock program of Oppo Find x2 /x2 pro
3. Install the apk on your phone
4. Ensure your device has the latest version of your ROM installed.
5. Click "Start Applying" on the Unlock App. You will need to wait about a month. After a month, open the application, and if "Approved" is displayed, please go to the next step.
If not, Force Close the Application several times over and over, and maybe it will display "Approved".（Some Chinese citizens reported a similar situation.）If you still can't, please contact oppo online customer service, they can solve this problem for you.
6. Next, please back up your data.
7. After receiving the 'Approval' in the app.
Go to Settings - about mobile phone - version information - version number Click here five times.
Go to settings - other settings - Developer options then Check OEM unlock.
8. Once again, open the Deep Test application and click "Start the Depth Test". The phone will automatically restart and enter Bootloader mode.
9. Connect your phone to the computer.
10. Open the command prompt browse to your adb/fastboot location and enter
"fastboot flashing unlock"
then confirm. At this time, the mobile phone will give some warning information. Please read it carefully before making a decision.
If you decide, choose "unlock the bootloader" and press the power key to restart. It is worth noting that the phone will be formatted here. If you have opened "find my phone" before, you need to enter your oppo account password to start your phone.
11. You now setup your phone as normal though with an unlocked bootloader.
12. If you wish to Root then please see this guide: https://forum.xda-developers.com/find-x2-pro/how-to/magisk-root-install-unlocked-bootloader-t4157327
can i flash global rom after unlocked bootloader ?
i was wondering the same thing. i dont see why not. give it a shot and let us know. you have nothing to lose it will simply not let you flash if it doesnt work and your existing ROM/Phone will be unaffected.
Ok, so I've unlocked my Chinese Find X2 Pro using the official method, which is by using the depth testing app and waiting for approval, then unlocking via Fastboot.
But I still can't flash the global ROM using the stock ColorOS recovery. I've tried various versions, just either get the 'Installation failed' or 'The installed version is lower than current' error.
Do I need to wait until TWRP is available for the X2 Pro or is there another way? I don't want to root, just install the stock ROM from another region. Will Magisk allow me to do this?
Was really hoping unlocking the bootloader would do it, guess it's a good start
bugger.. it would appear that the ColorOS Recovery is preventing the install. So yes you would need TWRP or someone to hack the ColorOS recovery to flash without the check.
though with an unlocked bootloader you can flash TWRP as soon as it's been developed by someone.. or risk flashing a twrp from a similiar phone?
Bugger indeed, I've bricked it! Tried various ways to do it as really need to get rid of this Chinese ROM. I flashed a Boot image from a global version, didn't work. Then flashed the Chinese version back.
So then in a bold (stupid) move I tried to flash other images from the global ROM - now won't load into recovery at all. With nothing to lose I tried loading TWRP recovery from one of the latest Realme phones this morning, didn't fix it.
What is weird is in Oppo / Realme ROMs there is no recovery image - not sure if it's part of the boot image?
Does anyone know how to obtain a recovery image? I think this is what I'm missing. Thinking maybe it's not part of the ROM on these devices.
---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------
And FYI, I've been using a python tool to decrypt the ozip files. Have looked in multiple ROMs, beta and standard, Chinese and global and even a few Realme ROMs.
I'm starting to hate Oppo, it's even more of a pain in the ass than Samsung! :silly:
I bought a Xiaomi Mi Mix 3 5G yesterday off eBay just to get me by for the time being, it was a carrier version and I managed to get the stock global ROM with MI12 on it in 30 minutes using fastboot and flashing all the images. Refreshingly easy
klanbo78 said:
Bugger indeed, I've bricked it! Tried various ways to do it as really need to get rid of this Chinese ROM. I flashed a Boot image from a global version, didn't work. Then flashed the Chinese version back.
So then in a bold (stupid) move I tried to flash other images from the global ROM - now won't load into recovery at all. With nothing to lose I tried loading TWRP recovery from one of the latest Realme phones this morning, didn't fix it.
What is weird is in Oppo / Realme ROMs there is no recovery image - not sure if it's part of the boot image?
Does anyone know how to obtain a recovery image? I think this is what I'm missing. Thinking maybe it's not part of the ROM on these devices.
---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------
What method were you using to flash mate?
I had a look at the extract of the Global ROM and can see a heap of img files.. though your right there is no obvious Recovery image file.
That is strange. As the device has a Recovery mode. It would be very strange to make it part of the Boot Image. Surely Oppo has a recover tool that just puts everything back to default?
Click to expand...
Click to collapse
Sage said:
What method were you using to flash mate?
Click to expand...
Click to collapse
Just using the adb toools via command prompt on my PC and phone on fastboot mode.
I.e. fastboot flash boot boot.img
There's no system image either, only vbmeta_system.img which I don't think it's the same thing. Watching YouTube videos and searching the internet now to try and figure out
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
klanbo78 said:
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
Click to expand...
Click to collapse
Impressive mate well done! And thanks for posting the solution! With a recovery.img file you are now free to experiment! I hope you get the Global Working! Please keep us up to date!
Can you upload the recovery.img to help the community?
Sage said:
Impressive mate well done! And thanks for posting the solution! With a recovery.img file you are now free to experiment! I hope you get the Global Working! Please keep us up to date!
Can you upload the recovery.img to help the community?
Click to expand...
Click to collapse
You will be the first person in the world to have an unlocked bootloader on the Global ROM!
surely with some combination of Global and Chinese it will work!
Chinese Recovery -> Global Boot -> Global ROM -> Chinese Vendor
Global Recovery -> Global Boot -> Global System -> Chinese Vendor
Chinese Recovery -> Chinese Boot -> Global System -> Global Vendor
etc
etc
Sage said:
You will be the first person in the world to have an unlocked bootloader on the Global ROM!
surely with some combination of Global and Chinese it will work!
Chinese Recovery -> Global Boot -> Global ROM -> Chinese Vendor
Global Recovery -> Global Boot -> Global System -> Chinese Vendor
Chinese Recovery -> Chinese Boot -> Global System -> Global Vendor
etc
etc
Click to expand...
Click to collapse
Thanks for your support
I'll upload the recovery images for the global and Chinese variants once I'm back on my desktop later.
So the issue I'm facing now is it this phone doesn't have a system, vendor or product partition. My assumption is that I need to flash the global system image, as that's the one that basically contains the OS.
I think that these images are contained within the "super" partition which appears to be a dynamically resizable partition. I have no idea how to flash to these!
I'm trying to make sense of it all but fastbootd has come up a few times, which apparently is needed to flash to userspace which is where this super partition resides.
I can see in the ROM there is an updater script file that refers to these images, create groups in the super partition and resizes them as necessary. It seems to use the vb_meta_system image in some way. I have no idea how to replicate this script in fastboot though or if it's even possible?
Can anyone help?
---------- Post added at 08:59 AM ---------- Previous post was at 08:46 AM ----------
A bit of info on dynamic partitions...
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
vbmeta.img removes the boot verification so you definitely want to use that. see this thread for its use.
https://forum.xda-developers.com/find-x2-pro/how-to/magisk-root-install-unlocked-bootloader-t4157327
I downloaded the depth testing app but the submit application is greyed out. Any tips on what to do?
golemagg said:
I downloaded the depth testing app but the submit application is greyed out. Any tips on what to do?
Click to expand...
Click to collapse
I know they have a monthly quota, perhaps it's been reached this month.
Or maybe the servers are down? there were a few days during my application that I couldn't check the status, just assumed the server was offline - perhaps it's something like that.
Maybe just wait a few days and see.
Where is you download the app from? And do you have the Chinese variant?
klanbo78 said:
I know they have a monthly quota, perhaps it's been reached this month.
Or maybe the servers are down? there were a few days during my application that I couldn't check the status, just assumed the server was offline or something like that - perhaps it's something like that.
Maybe just wait a few days and see.
Where is you download the app from? And do you have the Chinese variant?
Click to expand...
Click to collapse
Understood. I'll keep monitoring it. Thanks a lot for the information.
klanbo78 said:
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
Click to expand...
Click to collapse
Can you please upload the recovery.img for people to use?
any other progress to report?
Sage said:
Can you please upload the recovery.img for people to use?
any other progress to report?
Click to expand...
Click to collapse
Yeah, that would be really nice. I couldn't boot also in recovery after android 11 beta:silly:
Sage said:
Can you please upload the recovery.img for people to use?
any other progress to report?
Click to expand...
Click to collapse
Here's the link to the recovery (and boot) images, have zipped them as they're quite large. I've included both variants (so PDEM30 and CPH2025).
https://drive.google.com/drive/folders/1HkNeQSuzsPDdue4KqRbDWLah0YH-CSwb?usp=sharing
In terms of progress, there is none. I got a bit adventurous and decided to flash all of the partitons on my PDEM30 with the images from the CPH2025 (manaully as there is no "flash-all.bat" file in the OTA ROM). I think it would have worked as it has for phones I've flashed this way in the past, but as I now know phones that launced with Android 10 are quite different due to having a dynamic "super" partition. This super partition contains the system, product, vendor image, etc. It should not (can't be) be flashed from fastboot as it's held in the "user space" of the phone and fastboot doesn't know how to deal with these partition types.
Pixel devices have a program called fastbootd which I think can be used for this, but Oppo doesn't appear to have that mode. Basically the phone now won't boot to recovery at all, I can only get into fastboot mode.
Not even worth holding out for TWRP as as of right now, TWRP doesn't support these dynamic partions (so any phone launced with Android 10). I contacted Oppo UK support and they said I could send in for repair, but then got told by the company who would be doing the repair (SBE UK) that they only support UK and EU devices. So looks like it might be going back to China for a repair (just need to find a freind who speaks Chinese )
Before that though I'm going to see if I can edit the recovery.img in Android Kitchen, to see if I can find the bit that's responsible for it not booting into recovery mode. I think at this point I have nothing to lose!!
I can't download unlock program of Oppo Find x2 / x2 pro, can you help me download it, thanks
Related
Consider one day you upset the devil and your phone is bricked by him, lets try to revive the phone from hell (at your own risk) :
Link to the OTA firmware's :
Click here for the links page
Important tools links:
[TOOL] Huawei Multi-Tool v8 by Team MT by inside!out
TWRP Honor 7X img
Stage 1
Download from here everything you need for the procedure - Download Folder Link
I am testing it on my BND-L21 firmware from BND-AL10
Downloading firmware (from topic). Full firmware must be more than 1.5Gb, all smaller is just
OTA Updates to the system.
After that we must download Huawei-MultiTool (future MT) version 8.x.x (link topic)
and downloading custom recovery. We will use TWRP for Honor7x (link topic)
Last we must prepare OTG Cable, SD Card more than 4Gb. On first stage that's all.
Stage 2
Go to MT and reboot phone to Fastboot mode (while phone off, hold "Volume -" and power)
If you did all correctly, you will see in the down right side your number and "Fastboot".
Now go in MT to the Bootloader and check the status. If you have already unlocked, skip this.
If you have locked phone, you must have IMEI and Huawei account. (if not please unlock your bootloader via the Huawei site)
After that, go to Recovery menu and choose our TWRP image in "Custom recovery" section and
type "Recovery". IMPORTANT!!! DON'T FLASH ERECOVERY, I DON'T HAVE THIS IMAGE!!!
After flashing recovery, we must turn off our phone.
Now we must to prepare base system image. In archive we have UPDATE.ZIP file. extract this
file to custom folder and open "Unbrick" in MT and choose "extractor". Open our file in extractor
and click right mouse key on empty space, choose extract all... and choose custom folder to
extracting.
Go to the folder and copy file VENDOR.IMG to the SD-Card (or USB with OTG). Turn on your
device in Recovery mode (Volume + and power), choose Wipe and Wipe ALL partitions! After
doing this, go to Install and choose "Install img", go to the SD-Card, and install VENDOR.img to
VENDOR folder (Important!)
After installing reboot phone again to Fastboot mode and connect to PC.
Now we must download .zip update to your region. We need this for using LTE (4G) in your country + Localization.
After downloading open .zip archive with our CUST file. archive must be called update_BND-
YOUR-NUMBER_hw_YOUR- COUNTRY.zip
From this archive we must extract .img file from root folder. It can be called cust.img CUST.img
version.img etc.
if name different from CUST.img rename it and put to the extracted UPDATE.app folder.
Last Stage 3
In MT go to Unbrick, choose our unpacked system with our CUST file and we must have at least
4/5 checkbox. And just type "UNBRICK" and wait. NOTICE: at moment of extracting system.img
it will be about 10-15 minutes. It's not a freezing of PC)
After good installing in log you will see like "All ok" Just reboot phone and you will see low level
factory reset, or something else like formatting. After formatting phone will reboot to the system.
That's all
Flashing Gapps method coming soon...
Password - 4pda for the update_full_bnd-AL10... Zip
Special Thanks to Kallibr44 my friend who helped me decipher everything. :highfive:
HIT THANKS IF I HELPED YOU IT MAKES ME HAPPY
We need a Full Firmware Package for L21,this is only Ota Updates.
letschky said:
We need a Full Firmware Package for L21,this is only Ota Updates.
Click to expand...
Click to collapse
there is a procedure used by EU users to completely revive the phone using the OTA but the procedure is too long which i haven't tried yet and is completely for users who have dead phones for now and yes obviously there is no official firmware available for Honor 7x but the user from an EU forum revived his phone so it is possible from the images.
though i made this thread for users who want to update their firmwares and not the procedure to flash a stock firmware since there is not one available yet but i can point to the thread where this user posted the procedure if someone wants to try. PM me
sid21 said:
i can point to the thread where this user posted the procedure if someone wants to try. PM me
Click to expand...
Click to collapse
Yes please....
fmotta said:
Yes please....
Click to expand...
Click to collapse
Sent reply.
There are teams who have unlocked a lot of stuff like flashing international FW,
flashing gapps on chinese fw, Automatic Call Recording, restoring the phone.
so i am in contact with them to make our phone better. lets keep our fingers crossed. :fingers-crossed:
i am waiting for firmware flashing to get it translated from one of the users.
This is the full recovery package right? Atleast for the Indian version?
TheDj408 said:
This is the full recovery package right? Atleast for the Indian version?
Click to expand...
Click to collapse
They arent recovery packages. they are full OTA which can be flashed for updating.
but there is a process to compile them into making them stock firmware packages but due to the long procedure i didnt post it here. rather wait for official stock firmware package.
sid21 said:
Hello Honor 7X Users, turns out there is firmware available for flashing for the AL10 and L21 variants
but i haven't tried them out and can post the procedure if someone needs it but all credit goes to PRO-TEAMMT for releasing them for us so now if we mess up we got official firmware's latest available to go back to.
I personally haven't tested any but i soon will.
Link to the firmware's :
Click here for the links page
Important tools :
[TOOL] Huawei Multi-Tool v8 by Team MT by inside!out
TWRP Honor 7X img
Steps : (Considering you have unlocked bootloader and flashed twrp)
1. Download the appropriate firmware as per your model (Link to the website given)
2. Clear Cache
3. Flash the firmware file
(Wait for the complete process to flash a firmware from scratch so that i can do it and confirm myself but if anybody tests before me let me know)
Refer to the thread by inside!out for any help till them if you want to try out
Click to expand...
Click to collapse
Hi
I am a New in Android world
I have honor 7x BND L21c185b101
And i rooted
Know exactly do this?
Step 3 how?
And the multi tool For what?
sid21 said:
there is a procedure used by EU users to completely revive the phone using the OTA but the procedure is too long which i haven't tried yet and is completely for users who have dead phones for now and yes obviously there is no official firmware available for Honor 7x but the user from an EU forum revived his phone so it is possible from the images.
though i made this thread for users who want to update their firmwares and not the procedure to flash a stock firmware since there is not one available yet but i can point to the thread where this user posted the procedure if someone wants to try. PM me
Click to expand...
Click to collapse
Can I have the procedure link?
I ordered a 7X from AliExpress.
I also own an Honor 5X & errrmmmm.. I'm not a developer rather still a learning buildbot ? still I want to take part in bringing up LOS or AOSP for Honor 7X. So we can work on it together if you want. ?
Cheers!
P.S. Belated Merry Christmas.
tootysa said:
Hi
I am a New in Android world
I have honor 7x BND L21c185b101
And i rooted
Know exactly do this?
Step 3 how?
And the multi tool For what?
Click to expand...
Click to collapse
exactly what you want to do?
this is to update to the latest firmware. if you have the latest firmware you dont need it.
the multi tool is used to flash stock with a procedure which is only needed to return to stock or else theres no need for it for the most part..
mumith3 said:
Can I have the procedure link?
I ordered a 7X from AliExpress.
I also own an Honor 5X & errrmmmm.. I'm not a developer rather still a learning buildbot ? still I want to take part in bringing up LOS or AOSP for Honor 7X. So we can work on it together if you want.
Cheers!
P.S. Belated Merry Christmas.
Click to expand...
Click to collapse
PM Sent kindly check.
sid21 said:
Hello Honor 7X Users, turns out there is firmware available for flashing for the AL10 and L21 variants
but i haven't tried them out and can post the procedure if someone needs it but all credit goes to PRO-TEAMMT for releasing them for us so now if we mess up we got official firmware's latest available to go back to.
I personally haven't tested any but i soon will.
Link to the firmware's :
Click here for the links page
Important tools :
[TOOL] Huawei Multi-Tool v8 by Team MT by inside!out
TWRP Honor 7X img
Steps : (Considering you have unlocked bootloader and flashed twrp)
1. Download the appropriate firmware as per your model (Link to the website given)
2. Clear Cache
3. Flash the firmware file
(Wait for the complete process to flash a firmware from scratch so that i can do it and confirm myself but if anybody tests before me let me know)
Refer to the thread by inside!out for any help till them if you want to try out
Click to expand...
Click to collapse
HI I wanna know many things:
1-if I can constantly update the 7x with the application (or the software on PC, is the same) "Firmware Finder" even if I don't recive the official OTAs (because I want to root my device)
2-if its possible upgrade the system via OTA (or Firmware finder etc...) when the device is rooted
3-is dangerous root the Honor 7x?
4-if I can upgrade the system when the device Is rooted via the software HiSuite
5- how/where can I do/find and restore a Nandroid Backup for my phone
6-where I can find a local/manual update (UPDATE. APP) for the 7x (in case a brick the phone)
7-how can i UNBRICK my phone I case of brick
(sorry for my bad english?)
PLEASE HELP ME??
Thanks
Lambo™ said:
HI I wanna know many things:
1-if I can constantly update the 7x with the application (or the software on PC, is the same) "Firmware Finder" even if I don't recive the official OTAs (because I want to root my device)
2-if its possible upgrade the system via OTA (or Firmware finder etc...) when the device is rooted
3-is dangerous root the Honor 7x?
4-if I can upgrade the system when the device Is rooted via the software HiSuite
5- how/where can I do/find and restore a Nandroid Backup for my phone
6-where I can find a local/manual update (UPDATE. APP) for the 7x (in case a brick the phone)
7-how can i UNBRICK my phone I case of brick
(sorry for my bad english?)
PLEASE HELP ME??
Thanks
Click to expand...
Click to collapse
1) ???
2) Not sure there is always a chance of bricking
3) Yes, if you don't know what you're doing. No if you're not going to be flashing anything.
4) You should be able to and also refer to #1.
5) None available
6) None available
7) You can't, no stock image released = no procedures to unbrick
Soapy! said:
1) ???
2) Not sure there is always a chance of bricking
3) Yes, if you don't know what you're doing. No if you're not going to be flashing anything.
4) You should be able to.
5) None available
6) None available
7) You can't, no stock image released = no procedures to unrbcik
Click to expand...
Click to collapse
1- can i upgrade the system at every update (when the device is rooted) with Firmware finder many times even if I don't recive the notification on the phone of the update (or if the device updater cannot find it)?
2-ok but if do all right steps you cannot brick the phone, no?
3-ok i only wanna unlock bootloader, flash twrp and root the phone. If I do all right steps there are no risks, no?
4-i don't understand it (in hisuite there s the option that says "Update device". With the device rooted can I update the phone with this software?)
5-ok but can I do one with a custom recovery, no?
6-ok so we just have to wait, no?
7-ok. Same thing of the - 6 (we have to wait for the UPDATE.APP for the 7x to be able to UNBRICK the phone in case it could happen, no?)
Sorry for my bad English and thanks for the answers?
Lambo™ said:
HI I wanna know many things:
1-if I can constantly update the 7x with the application (or the software on PC, is the same) "Firmware Finder" even if I don't recive the official OTAs (because I want to root my device)
2-if its possible upgrade the system via OTA (or Firmware finder etc...) when the device is rooted
3-is dangerous root the Honor 7x?
4-if I can upgrade the system when the device Is rooted via the software HiSuite
5- how/where can I do/find and restore a Nandroid Backup for my phone
6-where I can find a local/manual update (UPDATE. APP) for the 7x (in case a brick the phone)
7-how can i UNBRICK my phone I case of brick
(sorry for my bad english)
PLEASE HELP ME
Thanks
Click to expand...
Click to collapse
1. yes you can if the app supported honor 7x with their firmware but it doesn't yet, use twrp
2. yes you can upgrade via flashing it in twrp
3. unlocking bootloader itself is dangerous let alone rooting since your waranty is gone since there is still no sign of official stock firmware
4. same as no. 1 ans
5. if u flashed twrp you can do your nandroid backup which can be later restored anytime so it will be obv on the phone at that time
6. manual or local update? in the op main post i guess? by opening the link?
7. Still no official firmware and the procedure i am aware of consists of turning the official chinese firmware into normal by changing settings and stuff which is a long procedure so probably if u brick, u r stuck until honor decides to release stock firmware
by the looks i guess you have no clue about phone flashing, its better you dont try anything until there are guides properly made for newbies. :silly:
sid21 said:
1. yes you can if the app supported honor 7x with their firmware but it doesn't yet, use twrp
2. yes you can upgrade via flashing it in twrp
3. unlocking bootloader itself is dangerous let alone rooting since your waranty is gone [emoji14] since there is still no sign of official stock firmware
4. same as no. 1 ans
5. if u flashed twrp you can do your nandroid backup which can be later restored anytime so it will be obv on the phone at that time
6. manual or local update? in the op main post i guess? by opening the link?
7. Still no official firmware and the procedure i am aware of consists of turning the official chinese firmware into normal by changing settings and stuff which is a long procedure so probably if u brick, u r stuck until honor decides to release stock firmware
by the looks i guess you have no clue about phone flashing, its better you dont try anything until there are guides properly made for newbies. :silly:
Click to expand...
Click to collapse
Thanks lol [emoji23]
Sent from my BND-L24 using Tapatalk
I rooted my 7X(Al10) version successfully but while performing the reset, deleted the system file also by mistake. There is no TWRP backup. Is there any way to get the stock OS files again to flash in TWRP ? Or does anyone have a backup file they made that they can share? I tried Huawei e-recovery too, but that gets stuck at 'unable to get package info'. The people at the service centre can't think of any other method to restore the phone, except changing the motherboard. When is the official stock file expected to be available?
GC95 said:
I rooted my 7X(Al10) version successfully but while performing the reset, deleted the system file also by mistake. There is no TWRP backup. Is there any way to get the stock OS files again to flash in TWRP ? Or does anyone have a backup file they made that they can share? I tried Huawei e-recovery too, but that gets stuck at 'unable to get package info'. The people at the service centre can't think of any other method to restore the phone, except changing the motherboard. When is the official stock file expected to be available?
Click to expand...
Click to collapse
I have a TWRP backup not sure if it'll work, https://drive.google.com/file/d/1EntdgNwcJSOTZizqt_W-yWfkd3-YVmCm/view?usp=drivesdk
It's a zip file with 2 backup folder, one with boot and system and one with vendor
Edit: pls thank if it worked, so I have an indicator of the effectiveness
GC95 said:
I rooted my 7X(Al10) version successfully but while performing the reset, deleted the system file also by mistake. There is no TWRP backup. Is there any way to get the stock OS files again to flash in TWRP ? Or does anyone have a backup file they made that they can share? I tried Huawei e-recovery too, but that gets stuck at 'unable to get package info'. The people at the service centre can't think of any other method to restore the phone, except changing the motherboard. When is the official stock file expected to be available?
Click to expand...
Click to collapse
I am waitinig for the official stock file since two weeks now, because I deleted accidently the OS from my phone -_-
I think we can wait several weeks again...
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
Jan.Pul said:
I have a TWRP backup not sure if it'll work, https://drive.google.com/file/d/1EntdgNwcJSOTZizqt_W-yWfkd3-YVmCm/view?usp=drivesdk
It's a zip file with 2 backup folder, one with boot and system and one with vendor
Click to expand...
Click to collapse
Thanks! I will try on my bricked phone
sid21 said:
1. yes you can if the app supported honor 7x with their firmware but it doesn't yet, use twrp
2. yes you can upgrade via flashing it in twrp
3. unlocking bootloader itself is dangerous let alone rooting since your waranty is gone since there is still no sign of official stock firmware
4. same as no. 1 ans
5. if u flashed twrp you can do your nandroid backup which can be later restored anytime so it will be obv on the phone at that time
6. manual or local update? in the op main post i guess? by opening the link?
7. Still no official firmware and the procedure i am aware of consists of turning the official chinese firmware into normal by changing settings and stuff which is a long procedure so probably if u brick, u r stuck until honor decides to release stock firmware
by the looks i guess you have no clue about phone flashing, its better you dont try anything until there are guides properly made for newbies. :silly:
Click to expand...
Click to collapse
1. In the app firmware finder there are firmwares for the phone but how can I flash a official firmware (OTA I mean) if there are no one (or how can I flash a firmware finder Update)?
2. Same thing in -1 (I mean)
3. Ok. Now we have to wait the official stock firmware, no? (i don't understand this answer, please write it in another way)
4. I don't understand it
5. Okok (obv? Sorry I'm Italian hahaha)
6. It's not the same thing local or manual? Write it in another way please hahaha google translate doesnt help me?
7. Okok, So if I don't use your method I only have to wait that honor release the official stock firmware (UPDATE. APP). And for greater security it's better wait it before to root and unlock bootloader etc, no?
Anyway, I have an idea of what flashing is, in fact every device I have (they are all Samsung, so that's why I'm disoriented) is completely modified. The fact is that I dont have much experience (I'm 14 years old) with non-Samsung devices, in fact my honor 7x I received for Christmas and for the hurry and the want to modify it, I would like to know all these things.
Thank you
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
k0pernicus said:
I am waitinig for the official stock file since two weeks now, because I deleted accidently the OS from my phone -_-
I think we can wait several weeks again...
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
Thanks! I will try on my bricked phone
Click to expand...
Click to collapse
OK thanks I'll keep it aside in case of brick
I would recommend everyone to not do experiments over your phone to try and root and flash random stuff..
they only have official chinese firmware for flashing so its better to wait for the official firmware for non chinese version.
the method which i know of to flash on the phone is for people with flashing knowledge cz the procedure is not simple and secondly even i have been flashing my phone for many years on various devices yet i havent got the guts to root this first honor device cz their partitions are different and somewhat secured so dont play with it.
wait for the official firmware for your respective devices. maybe they will straightaway launch the oreo firmware.
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse
After many searches for the best help on my new Asus ZenFone V V520KL, I have no way to unlock the bootloader. Asus doesn't provide any support for this 2017 model, nor does Verizon, the company the phone was made for.
It comes stock with Nougat 7.0 OS, 32 GB ROM & 4 GB RAM. It's got a decent size screen and runs not too too bad.
I'm wondering if one of the tech people here would be so kind as to help me with not only unlocking the bootloader so I can then install a custom recovery image, preferrably TWRP, since I have used this type of program before on my other ZenFone 3 Zoom.
I already have ADB tools on my Windows 7 notebook (32-bit). I used it to install the last root on my other aforementioned phone so it will work.
What I'm wondering about is the bootloader unlock tool, custom recovery image (TWRP), and a way to root the bastard. Hopefully we can relock the bootloader after the job's done because it's annoying on my other phone to always have to bypass the "Can't check for corruption." screen before the phone actually boots. Again this is for the Asus ZenFone V V520KL model. There is really no information anywhere right now I know of that gets this job done.
Having a custom Pie 9.0 ROM upgrade would be the best if possible once we root the device.
My name is Andrew, S.D. from Canada.
Thanks and blessings.
Root
Did you find a way to root it?
No, I still need help with the original post. I can root the ZenFone 3 Zoom ZE553KL but they already tell us how to do that in another forum.
the Bootloader for v520kl is already unlock by ENG Firmware
Just serch it in forums
You're talking to a noob. Give me the location of ENG firmware.
Hi friend, in the other post de link for downloading de ENG Firmware is broken
[email protected] said:
Hi friend, in the other post de link for downloading de ENG Firmware is broken
Click to expand...
Click to collapse
This is the link
http://www.mediafire.com/file/lc17b75qbvy018z/Asus_Zenfone_V_V520KL_All_WW_ENG_T3.3.15.zip
I tried to flash it did not work for me..
---------- Post added at 10:55 PM ---------- Previous post was at 10:43 PM ----------
Doctor Andrew said:
You're talking to a noob. Give me the location of ENG firmware.
Click to expand...
Click to collapse
Here is the link:
https://forum.xda-developers.com/showpost.php?p=78833735&postcount=52
Hi friend,
It's de the same rom for this page
https:
www
hardreset.info/devices/asus/asus-v520kl/faq/firmware/ because, the size of this rom is 813MB
and the size of the rom of the link that you provide is 775.53 MB and the files is the same name.
or this rom has been updated.
someone know what version of android have this rom
Okay so we now have a link to just the ROM it looks like. Do we have a way to unlock the bootloader yet and install TWRP first? What about the TWRP image file, do we have one of those as well?
Doctor Andrew said:
Okay so we now have a link to just the ROM it looks like. Do we have a way to unlock the bootloader yet and install TWRP first? What about the TWRP image file, do we have one of those as well?
Click to expand...
Click to collapse
To flash the ENG rom, you do not need to unlock the bootloader. Just the Asus flash tool.
Once you flash it, you can reboot to fastboot mode(adb reboot bootloader) and use fastboot oem unlock to unlock bootloader. Be warned though the ENG firmware is very basic. No web browser, no google play, you can't pull down the notification bar etc. (Great battery life though with about 7-10 days since I am not using it at all).
As of right now, there is no TWRP for it that i know of. In fact, I can't even boot into recovery atm. I also am unable to get boot.img file form the .raw file so the various methods to root it seem to be out of reach for the moment.
I've absolutely no interest in the ENG firmware. Still looking for a solution to the original post that people can understand and use easily.
Doctor Andrew said:
I've absolutely no interest in the ENG firmware. Still looking for a solution to the original post that people can understand and use easily.
Click to expand...
Click to collapse
Well, ENG is the only way i could figure it out but I finally manged to get root on the phone with magisk. Still have some work to do to get play store and everything else running properly, but for now, hardest part is done.
oh my god - rooooot
faericia said:
Well, ENG is the only way i could figure it out but I finally manged to get root on the phone with magisk. Still have some work to do to get play store and everything else running properly, but for now, hardest part is done.
Click to expand...
Click to collapse
Good time of day, Faericia, this is just great news. You can share the experience of getting root with magisk?
Regarding Google Play and all that, where you need Google, using a bunch of microG and Aurora store.
MicroG is the core of Google services, which allows you to pass authorization through Google, synchronize and do it all without any garbage code, according to my observations, the expense is not much spent.
Aurora shop, as an analogue of Google Play, the application, the ability to save apk.
Due to the lack of binding to your Google account.
I think this connection may be relevant and rooted.
The initial partition should appear as root, it intends to resolve all the problems that I have in my phone. for asus applications, after I have done my best, several attempts have already been made.
It was possible to look in read mode using root explorer.
Perhaps you can somehow remove the protection of verizon on the bootloader.
PS the most hardcore variation of raw firmware, a hex editor, search in that between code, boot, recovery, system, etc. Very large empty spaces. previously there were 100 miles earlier.
I think this is part of verizon jokes.
This article should be cut and placed in img.
Thanks so much in advance.
hello when you finish you could share through a tutorial what you did I have my asus v with verizon rom and only data but if I can make it functional with the rom eng then better
Okay, Here are the steps. Before anything else though, I should warn you that I have not been able to get safetynet to pass. So if you have apps that require safetynet to pass, this may not be the way to go.
First you will need the ENG firmware:
https://mega.nz/#!l7wBlQ4B!uB63yH5Rir24GaSfDMWKowqdz-N_sc6SJ-q1WuuGiqM/
Also Asus Flash tools v 1.0.0.72:
https://drive.google.com/file/d/11rcjOgdpJhpK97GzbhYK6cYEIWOtzKE9/view
I am assuming you know adb and such. If not, search the forums and get the adb tools.
Using adb, Reboot to bootloader. ( adb reboot bootloader )
Load the .raw file in the asus flash tool, select v520KL and flash.
Once flash is done, unlock bootloader by going into bootloader (adb reboot bootloader) then type (fastboot oem unlock.)
Here is the patched_boot.img I used if you want to just try to flash that and see if it will work. This is for the eng firmware.
https://drive.google.com/file/d/1fUxGc27lrodR3ro9MIspde73G8Xg9VlW/view?usp=sharing
Go into bootloader and flash. (fastboot flash boot patched_boot.img)
Install magisk manager and test it out.
If you wish to patch the img yourself, the steps are below (still working on it):
So now we have the phone unlocked, and the software is very basic. We also need the boot.img file to patch since we do not have TWRP. Since I couldn't get it from the raw file (the extracted file is invalid with a size of 0 bytes) I decided to extract it from the phone. But to extract from the phone we need root. So for this next step, temporary root will have to do.
You can get temp root by using KingoRoot. Use the PC version and you will get root. This is just so we can extract the files from the phone itself.
I need to find the steps for the next steps again, but the basics is, extract boot.img from the phone. Patch it using magisk manager and then flash the patched_boot.img in bootloader mode. I had google play working(chinese version) but once i removed kingoroot it kept crashing. I currently have magisk and it gives me the root permissions but safetynet fails. I will retry this tomorrow and see if I can fix the safetynet issue and update this post with the steps.
Also I seem to have borken recovery mode on my phone. That may be because I tried flashing bunch of other stuff before I managed to root it so I do not know if it will be the same situation to you or not. I believe after I flashed ENG firmware, i had access to recovery mode at one point, but I may have just messed it up. Either way, Expect updates in the near future.
asus recovery
A huge over many thanks.
I also tried to get a temporary root, via the kingoroot pc version, it did not work, I suspect it because I installed eng, but did not oem unloock, when I did unlock, I somehow managed to get the boot out of the firmware, the user from 4pda was patched, but said that this boot is from 8 android, I thought that I had schizophrenia because later on trying to get boot I also got 0mb, this was due to the unexpected end of the archive.
In general, by flashing this boot, I also found a recovery mode and even a recovery mode, but going into recovery a message from Verizon was displayed, standard, when you roll the eng firmware for 5 seconds, hold something, etc. Well, you understand. And the whole laugh is that it was in a circle.
I suspect that asus had any plans for this device or for this amount of components. In other words, it was some kind of blank that was abandoned, maybe asus thought that this exclusive for verizon will make a trap, and then they say on the basis of v520kl we will make a non-exclusive open device, but alas, a huge member between two rolls.
Therefore, fortunately or unfortunately, recovery was not broken by you, most likely it was not working initially, but this is only a guess.
Daniel.Sim said:
A huge over many thanks.
I also tried to get a temporary root, via the kingoroot pc version, it did not work, I suspect it because I installed eng, but did not oem unloock, when I did unlock, I somehow managed to get the boot out of the firmware, the user from 4pda was patched, but said that this boot is from 8 android, I thought that I had schizophrenia because later on trying to get boot I also got 0mb, this was due to the unexpected end of the archive.
In general, by flashing this boot, I also found a recovery mode and even a recovery mode, but going into recovery a message from Verizon was displayed, standard, when you roll the eng firmware for 5 seconds, hold something, etc. Well, you understand. And the whole laugh is that it was in a circle.
I suspect that asus had any plans for this device or for this amount of components. In other words, it was some kind of blank that was abandoned, maybe asus thought that this exclusive for verizon will make a trap, and then they say on the basis of v520kl we will make a non-exclusive open device, but alas, a huge member between two rolls.
Therefore, fortunately or unfortunately, recovery was not broken by you, most likely it was not working initially, but this is only a guess.
Click to expand...
Click to collapse
I know recovery mode was working with VZW firmware. I know this because I tried installing using adb sideload several times. I might be mistaken on getting there once i flashed eng firmware but again, it has been a month or two since I tried it and all I know is, it won't go into the recovery screen now. Oh well, not my main phone so irrelevant.
I have installed patched boot img with fastboot. Now have root. But there a lot of apps not working. No Google apps at all. And no way to install them.
---------- Post added at 06:23 PM ---------- Previous post was at 06:15 PM ----------
Have installed patched boot img by faericia. Now I got root. But eng version doesn't have Google apps, so no play store, no Google pay, no accounts, no Gmail. And I don't know how to install it.
game #1 said:
I have installed patched boot img with fastboot. Now have root. But there a lot of apps not working. No Google apps at all. And no way to install them.
---------- Post added at 06:23 PM ---------- Previous post was at 06:15 PM ----------
Have installed patched boot img by faericia. Now I got root. But eng version doesn't have Google apps, so no play store, no Google pay, no accounts, no Gmail. And I don't know how to install it.
Click to expand...
Click to collapse
The only time I had Google apps was when I had kingoroot root still int he system. I then downloaded the Chinese google apps installer and used that to get it. Once i removed kingoroot google framwork kept crashing making it unusable.. If you don't need to pass safetynet, that might be the way. Othewise, I am still trying to work on it.
faericia said:
The only time I had Google apps was when I had kingoroot root still int he system. I then downloaded the Chinese google apps installer and used that to get it. Once i removed kingoroot google framwork kept crashing making it unusable.. If you don't need to pass safetynet, that might be the way. Othewise, I am still trying to work on it.
Click to expand...
Click to collapse
I found out how to stop frameworks from crashing. Just make it a system app. I use link2sd for this.
Now all gapps work nice.
As far as I know the bootloader for this phone is unlockable, but I've successfully rooted the L38041. I'll include the steps below. Please note, I'm only relating how I did this. There are probably more efficient methods, but, for me, this worked. I'm not responsible if you hardbrick your device.
Requirements:
a. Latest QPST from qpstflash (sorry, can't post links yet. Just google it).
b. Magisk Manager
c. Stock L38041 rom. I used the global version from FirmwareX.
d. ADB and Fastboot tools.
This method uses Qualcomm flashing, so if you've never heard of that, read as much as you can before you try this.
Steps
1. Download and extract the ROM to your PC.
2. Attach your adb enabled device via usb and copy the boot.img file from the extracted folder to your device storage.
3. Install and open magisk manager on your device, then install magisk via 'patch stock boot image'. Navigate to where you put the stock boot.img and select it.
4. Once completed, take the patched_boot.img, rename it back to boot.img, and put it back in the extracted ROM folder on your PC. Make sure you've backed up your stock boot. because you'll be replacing it with the patched.
5. Install the QPST package on your PC and run QFIL. Select Flat build, then navigate the programmer path to your ROM folder. Select the prog_emmc_ufs_firehose_Sdm660_ddr.elf as your programmer path. Next, load XMLs RawProgram0.xml and patch0.xml.
6. At this point, run the adb command "adb reboot edl." This will put your device into emergency download mode, in which you will be able to use QFIL . QFIL should go from 'No Port' to 'Qualcomm HS-USB QDLoader 9008'. Immediately after you see this pop up, select 'Download'. This will completely reset your device.
7. If flashing was successful, wait a bit then boot your device. You should see a little warning complaining that the software has been altered. Wait a little bit more. You can install magisk manager at this point if it didn't show up after the flash. Reboot the device again.
8. Et voila, you should have a rooted device now. Due to the locked bootloader, you still can't (or at least I couldn't) use a custom recovery, were there even one available.
Note: if you get a sahara error in the flashing process, it's probably because you waited too long to hit download.
Hope this helps for those of you with rooting your K5 Pro
edit: There is a way to unlock the bootloader! User KiiKeEp has posted a guide on the method, which also contains a usable TWRP for the global rom. Here's a more streamlined version adapted from his tutorial. Make sure you have oem unlocking enabled in developer options.
1. Go to "zui.com/iunlock" and fill in the boxes.
a. First input your IMEI1 which can be found by dialing *#06# or going to the "about phone" section in the settings.
b. Second, input your phone's serial number. You can find this by enabling debugging in your developer options menu, then using the adb command "adb reboot bootloader"
c. Input your email into the third box.
d. Type the displayed 4 digit number into the 4th box and then submit.
2. You'll receive an email containing a download link for an unlock .img called "sn.img". Download it.
3. Flash the unlock image in fastboot. Use the command "fastboot flash unlock", drag and drop the sn.img into the command window, hit enter, then follow the onscreen command.
4. If this is done correctly, you can flash the twrp.img that KiiKeEp included in his post. "fastboot flash recovery twrp.img"
Hello, Thanks for the information. I have bought this phone in November last year, and i like it. I bought it from Sunsky, i have the global version zui 5.0.066 st. Could you post or send me a video in how to do this please. I'm new in flashing phones. I only have flashes a Lenovo K5 note in the past (the 2016) version, it was easy because lenovo post the firmware and the instructions, i did it to upgrade the phone from Lollipop to Marshmallow. But i didn't root it. The K5 note is my father's phone.
I see how the Chinnese firmware looks, could i install the chinese firmware to my phone without any compatibility issues?, also i saw that the chinnese firmware has been updated to zui 5.0.163 st, with improvements and sound stability. And in the Lenovo Chinnese official club also there is a similar steps for rooting the device. Could you help me please to confirm these, and teach me how to do it, please?
Also, i have both firmwares, the CN lastest version; i downloaded it from the lenovo's chinnese official club (zui 5.0.163 st). And I also have the ROW version i don't remember where i downloaded it but this is the name of the file: L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225.rar
I have downloaded the QPFIL tool and lenovo drivers too. So i'm ready to learn. It would be great if you can make a video, please if you could. I only have install global versions, in the K5 note i install the global version. I could install the CN version in my K5 Pro without any issues? Thanks in advanced.
Julio2019 said:
Hello, Thanks for the information. I have bought this phone in November last year, and i like it. I bought it from Sunsky, i have the global version zui 5.0.066 st. Could you post or send me a video in how to do this please. I'm new in flashing phones. I only have flashes a Lenovo K5 note in the past (the 2016) version, it was easy because lenovo post the firmware and the instructions, i did it to upgrade the phone from Lollipop to Marshmallow. But i didn't root it. The K5 note is my father's phone.
I see how the Chinnese firmware looks, could i install the chinese firmware to my phone without any compatibility issues?, also i saw that the chinnese firmware has been updated to zui 5.0.163 st, with improvements and sound stability. And in the Lenovo Chinnese official club also there is a similar steps for rooting the device. Could you help me please to confirm these, and teach me how to do it, please?
Also, i have both firmwares, the CN lastest version; i downloaded it from the lenovo's chinnese official club (zui 5.0.163 st). And I also have the ROW version i don't remember where i downloaded it but this is the name of the file: L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225.rar
I have downloaded the QPFIL tool and lenovo drivers too. So i'm ready to learn. It would be great if you can make a video, please if you could. I only have install global versions, in the K5 note i install the global version. I could install the CN version in my K5 Pro without any issues? Thanks in advanced.
Click to expand...
Click to collapse
Sorry, I don't really have the time or the facilities to make a tutorial video, but the Chinese instructions follow the same process, only breaking up the process into a few more steps. Both achieve the same result. My thinking is that you might be able to install the Chinese firmware, but some forum discussions suggest that you will have some modem and IMEI issues if you do. There are ways to back these up using QPSTs software download application. My guess is that it'll probably work, but that it won't work flawlessly. Let me know how it turns out if you try it.
If you want to update your software without rooting, simply follow the process from step 5, using the new L38041_ROW ROM without swapping the boot.img. The link below shows the flashing process pretty well, but you'll need the later versions of QPST since you'll be using .elf programming paths and not .mbn. Once again, that will wipe your phone entirely.
"https://www.youtube.com/watch?v=W9Cz4LwAzLg"
Hello! Don't worry i'm going to follow your steps. By the way, about the CN firmware, would there be a way to back up my rom, my actual ROM with the modem and imei configuration? Is to prevent in bric the phone. I have read the warnings about the issues you talked about, and apparently these setteings are store in the nvram. There is a way to do a recovery image or ROM of my current firmware?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
And what version is your ZUI now? When i bought the phone, i tried to convince the provider to not install the custom global firmware, but he told me that lenovo technician said that they have to intall that global firmware. So, i accepted to buy the phone with the global version. I was trying to avoid all the gapps that the majority of phones have.
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
Could you tell me how to uninstall the gapps, please?. I only want to have running the only and minimal google processes. And the other reason is because i like the clock widget with weather that the CN version have. There are other things that the CN have that the global version doesn't have.
---------- Post added at 04:21 PM ---------- Previous post was at 04:20 PM ----------
Another question, do you know what enshrine is? Is in the wallpaper submenu but it doesn't do anything in my case. And theres a folder with images that i think are the wallpapers of the CN firmware. Thanks in advance
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
If I flash i need to install gapps or the gapps installs themeselve?
Julio2019 said:
Hello! Don't worry i'm going to follow your steps. By the way, about the CN firmware, would there be a way to back up my rom, my actual ROM with the modem and imei configuration? Is to prevent in bric the phone. I have read the warnings about the issues you talked about, and apparently these setteings are store in the nvram. There is a way to do a recovery image or ROM of my current firmware?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
And what version is your ZUI now? When i bought the phone, i tried to convince the provider to not install the custom global firmware, but he told me that lenovo technician said that they have to intall that global firmware. So, i accepted to buy the phone with the global version. I was trying to avoid all the gapps that the majority of phones have.
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
Could you tell me how to uninstall the gapps, please?. I only want to have running the only and minimal google processes. And the other reason is because i like the clock widget with weather that the CN version have. There are other things that the CN have that the global version doesn't have.
---------- Post added at 04:21 PM ---------- Previous post was at 04:20 PM ----------
Another question, do you know what enshrine is? Is in the wallpaper submenu but it doesn't do anything in my case. And theres a folder with images that i think are the wallpapers of the CN firmware. Thanks in advance
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
If I flash i need to install gapps or the gapps installs themeselve?
Click to expand...
Click to collapse
There probably is a way of completely backing up your current stock ROM, and I see tutorials on here about how to do it, but I couldn't figure out how to backup mine. I already had both Chinese and ROW roms, so I wasn't too worried. You CAN use QFIL to backup your IMEI, Modem, etc, however. It's in the tools drawer as "QCN backup restore"
I'm using 5.0.117 from FirmwareX ("https://firmwarex.net/lenovo-k5-pro-l38041-android-8-1-official-firmware/"). Honestly I'm unsure what release I was using before the flash. The new ROW rom will have a full google suite, but once you obtain root you can remove whichever apps you don't like. There's a whole host of information on xda and other forums about removing system apps on a rooted phone. Hell, there are even apps that do it for you. Magisk has a module as well which uses terminal commands. A quick and dirty method is to use a root explorer like Mixplorer and delete the /system/app/xxxx folder that you don't want.
I have no idea what enshrine is. My wallpaper menu just has static, dynamic, and album selections, with an option for HD desktop.
My thinking is that the Chinese version won't have gapps, in which you could potentially flash open gapps using an app like flashify. I'm not sure, as I've only used the ROW 5.0.117. Remember that this device as yet has no TWRP and prevents boot of an unauthorized recovery, so any sort of flashing has to be done via qualcomm flashing, or in system after gaining root access.
rlb596 said:
There probably is a way of completely backing up your current stock ROM, and I see tutorials on here about how to do it, but I couldn't figure out how to backup mine. I already had both Chinese and ROW roms, so I wasn't too worried. You CAN use QFIL to backup your IMEI, Modem, etc, however. It's in the tools drawer as "QCN backup restore"
I'm using 5.0.117 from FirmwareX ("https://firmwarex.net/lenovo-k5-pro-l38041-android-8-1-official-firmware/"). Honestly I'm unsure what release I was using before the flash. The new ROW rom will have a full google suite, but once you obtain root you can remove whichever apps you don't like. There's a whole host of information on xda and other forums about removing system apps on a rooted phone. Hell, there are even apps that do it for you. Magisk has a module as well which uses terminal commands. A quick and dirty method is to use a root explorer like Mixplorer and delete the /system/app/xxxx folder that you don't want.
I have no idea what enshrine is. My wallpaper menu just has static, dynamic, and album selections, with an option for HD desktop.
My thinking is that the Chinese version won't have gapps, in which you could potentially flash open gapps using an app like flashify. I'm not sure, as I've only used the ROW 5.0.117. Remember that this device as yet has no TWRP and prevents boot of an unauthorized recovery, so any sort of flashing has to be done via qualcomm flashing, or in system after gaining root access.
Click to expand...
Click to collapse
Hello, thank for your patience and teachings. Here are the image of the Enshrine Menu i talked about:
("https://drive.google.com/open?id=1FFgx5pmM6mIQUhrOLN2cjgyfOvFTV83s")
and here is when i select this option:
("https://drive.google.com/open?id=1L34tjYpiPmjAU443sjHCcM8TM8JyOY-o")
Oh, and also i want to ask you what does this application call AppDaily from Lenovo, i don't understand how to use it, here the image:
("https://drive.google.com/open?id=1z6swpSxTPw4JeodwZ-OvkKUav9FWEOsZ")
Hearing all you teach me, then i think it would be safe for the moment to only upgrade my system with the zui 5.0.117. It would be safe to make this upgrade. Do you recommend me to root after the upgrade?. Or wait more time for other solution. I think that first it would be better to upgrade with the ROW firmware. How do you feel the last ROW update. Although is strange because i have only see zui 5.0.066 and zui 5.0.088 global versions. Maybe only few phones receive the update. What do you think about?, What do you recommend? If only i upgrade the phone with the ROW there wouldn't be any modem and imei issues? Thanks in advance.
Julio2019 said:
Hello, thank for your patience and teachings. Here are the image of the Enshrine Menu i talked about:
("https://drive.google.com/open?id=1FFgx5pmM6mIQUhrOLN2cjgyfOvFTV83s")
and here is when i select this option:
("https://drive.google.com/open?id=1L34tjYpiPmjAU443sjHCcM8TM8JyOY-o")
Oh, and also i want to ask you what does this application call AppDaily from Lenovo, i don't understand how to use it, here the image:
("https://drive.google.com/open?id=1z6swpSxTPw4JeodwZ-OvkKUav9FWEOsZ")
Hearing all you teach me, then i think it would be safe for the moment to only upgrade my system with the zui 5.0.117. It would be safe to make this upgrade. Do you recommend me to root after the upgrade?. Or wait more time for other solution. I think that first it would be better to upgrade with the ROW firmware. How do you feel the last ROW update. Although is strange because i have only see zui 5.0.066 and zui 5.0.088 global versions. Maybe only few phones receive the update. What do you think about?, What do you recommend? If only i upgrade the phone with the ROW there wouldn't be any modem and imei issues? Thanks in advance.
Click to expand...
Click to collapse
Remember, I'm just telling you how I did it. Your experiences might vary, but I've had no problems with this latest ROW in any aspect. It runs well, is pretty intuitive, and I notice very little change from the previous stock rom. If you want to try out either ROM before rooting, I'd suggest that you not customize your phone very much, or have any personal files on the built in storage, as these will be lost will each qualcomm flash. I'd recommend that if you're going to update, you might as well try rooting now to save yourself those issues. If you're uneasy about rooting and aren't having any issues with your current ROM, I'd suggest you wait until you have some pressing issue, as many of the included apps on this phone can be disabled or uninstalled. My purpose for rooting was that I became used to root-requiring apps like AdAway and some magisk extensions. The apps you're talking about are included with this system as well, but I never used them. Before the root, I disabled them. After the root, I deleted them.
This is a very new phone, so I wouldn't be surprised if there's more development 6 months in the future. Keep an eye on 4pda and club.lenovo's discussion forum for this device, as I anticipate their being the forerunners.
rlb596 said:
Remember, I'm just telling you how I did it. Your experiences might vary, but I've had no problems with this latest ROW in any aspect. It runs well, is pretty intuitive, and I notice very little change from the previous stock rom. If you want to try out either ROM before rooting, I'd suggest that you not customize your phone very much, or have any personal files on the built in storage, as these will be lost will each qualcomm flash. I'd recommend that if you're going to update, you might as well try rooting now to save yourself those issues. If you're uneasy about rooting and aren't having any issues with your current ROM, I'd suggest you wait until you have some pressing issue, as many of the included apps on this phone can be disabled or uninstalled. My purpose for rooting was that I became used to root-requiring apps like AdAway and some magisk extensions. The apps you're talking about are included with this system as well, but I never used them. Before the root, I disabled them. After the root, I deleted them.
This is a very new phone, so I wouldn't be surprised if there's more development 6 months in the future. Keep an eye on 4pda and club.lenovo's discussion forum for this device, as I anticipate their being the forerunners.
Click to expand...
Click to collapse
Agree. Hope they focus more in the subject we are talking. By the way, i have checked the club.lenovo's, and they got another new update with more improvements and a fix for their wechat app. , Now they are on zui 5.0.188 st. Could you show me images of the zui 5.0.117 interface, if you could. If not, don't worry i'm going to google it. But leaving this aside, i'm satisfy with the phone, in my opinion, is a great phone!, I like it, has excellent performance, a cool design, is slim, have a nice display, and good cameras. Have a nice day, hope we could talk again soon. If i get any more news, be sure i'm going to share it. Here in xda, i think we are the only ones who are talking about this phone. Hope more people and xda developers join us. Thanks. God blessed you.
Latest .188 st ZUI's interface changes a lot, but is the chinesse variant of the ROM, it comes with chinesse apps and only english and chinesse languages installed. Deleting the chinesse bloatware is easy, there is a folder named "preloaded" or preinstalled (something like that) in /system/ get root rights and delete the entire directory.
please create forum
rlb596 said:
As far as I know the bootloader for this phone is unlockable, but I've successfully rooted the L38041. I'll include the steps below. Please note, I'm only relating how I did this. There are probably more efficient methods, but, for me, this worked. I'm not responsible if you hardbrick your device.
Requirements:
a. Latest QPST from qpstflash (sorry, can't post links yet. Just google it).
b. Magisk Manager
c. Stock L38041 rom. I used the global version from FirmwareX.
d. ADB and Fastboot tools.
This method uses Qualcomm flashing, so if you've never heard of that, read as much as you can before you try this.
Steps
1. Download and extract the ROM to your PC.
2. Attach your adb enabled device via usb and copy the boot.img file from the extracted folder to your device storage.
3. Install and open magisk manager on your device, then install magisk via 'patch stock boot image'. Navigate to where you put the stock boot.img and select it.
4. Once completed, take the patched_boot.img, rename it back to boot.img, and put it back in the extracted ROM folder on your PC. Make sure you've backed up your stock boot. because you'll be replacing it with the patched.
5. Install the QPST package on your PC and run QFIL. Select Flat build, then navigate the programmer path to your ROM folder. Select the prog_emmc_ufs_firehose_Sdm660_ddr.elf as your programmer path. Next, load XMLs RawProgram0.xml and patch0.xml.
6. At this point, run the adb command "adb reboot edl." This will put your device into emergency download mode, in which you will be able to use QFIL . QFIL should go from 'No Port' to 'Qualcomm HS-USB QDLoader 9008'. Immediately after you see this pop up, select 'Download'. This will completely reset your device.
7. If flashing was successful, wait a bit then boot your device. You should see a little warning complaining that the software has been altered. Wait a little bit more. You can install magisk manager at this point if it didn't show up after the flash. Reboot the device again.
8. Et voila, you should have a rooted device now. Due to the locked bootloader, you still can't (or at least I couldn't) use a custom recovery, were there even one available.
Note: if you get a sahara error in the flashing process, it's probably because you waited too long to hit download.
Hope this helps for those of you with rooting your K5 Pro
edit: There is a way to unlock the bootloader! User KiiKeEp has posted a guide on the method, which also contains a usable TWRP for the global rom. Here's a more streamlined version adapted from his tutorial. Make sure you have oem unlocking enabled in developer options.
1. Go to "zui.com/iunlock" and fill in the boxes.
a. First input your IMEI1 which can be found by dialing *#06# or going to the "about phone" section in the settings.
b. Second, input your phone's serial number. You can find this by enabling debugging in your developer options menu, then using the adb command "adb reboot bootloader"
c. Input your email into the third box.
d. Type the displayed 4 digit number into the 4th box and then submit.
2. You'll receive an email containing a download link for an unlock .img called "sn.img". Download it.
3. Flash the unlock image in fastboot. Use the command "fastboot flash unlock", drag and drop the sn.img into the command window, hit enter, then follow the onscreen command.
4. If this is done correctly, you can flash the twrp.img that KiiKeEp included in his post. "fastboot flash recovery twrp.img"
Click to expand...
Click to collapse
Greetings Mr rl596!
So, what order do you recommend, i have downloaded KiiKeEp files, and successfully have receive my unlock image from lenovo, but in with order do i need do thinks. Is the following order correct?
1.- unlock bootloader
2.- Install zui 5.0.117 st ROM
3.- Install TWRP image
4.- Root device
Is this order correct?, I have the CN ROM in hand too, tha latest one is .188 st. But i need to make an EFS backup with the QPST tool, just in case. I have ask KiiKeEp, i'm waiting for his answer too. I want to make a video tutorial, so more K5 pro users could get benefit of this, and use all the potential this phone has. But what benefits does a unlock bootloader have?, Oh, and I almost forgot, for the QPST tool, do i have to install the driver that shows in the Device Manager as L38041 or the one that shows as QUALCOMM?
. Thanks in advanced.
Hi.
Thank you very much for the instruction - I successfully got root on my phone.
The only difference is I didn't use ADB, I just entered Download mode via the buttons: hold the volume + and - and power down until the logo flash.
:good:
Hi guys,
I tried but i have an error "Download Fail:FireHose Fail:FHLoader Fail:Le fichier spécifié est introuvable"
log :
13: E:\Téléchargements\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\prog_emmc_ufs_firehose_Sdm660_ddr.elf
00:25:31: Requested ID 13, file: "E:\Téléchargements\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\prog_emmc_ufs_firehose_Sdm660_ddr.elf"
00:25:32: 622900 bytes transferred in 0.203000 seconds (2.9263MBps)
00:25:32: File transferred successfully
00:25:32: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\denis\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Download Fail:FireHose Fail:FHLoader Fail:Le fichier spécifié est introuvable (The specified file is not found)
Finish Download
do you have any idea ?
thx in advance
I was wondering if there is a difference between CN version and global version regarding future update which device should i get for better support or root
Hi, I have unlokced the bootloader and install magisk via twrp. Is there custom roms for this phone
O meu lenovo apresentar "Qualcum crushdump mode" alguém com isso?
---------- Post added at 05:04 AM ---------- Previous post was at 04:54 AM ----------
O meu lenovo fica no final do processo com "Qualcum crushdump mode" alguém conseguiu resolver isso?
Help! I do the first process but now i can´t enter phone because tell from password on encryption screen.
EDIT: I enter to EDL mode (Press Vol- and Vol+ at the same time and conect to the usb) and flash with QFIL with the original boot.img and the phone turn on normally.
Lenovo K5 Pro ROM
Hi.
Are you have good working ROM for Lenovo K5 Pro?
This is an awesome, awesome phone. I rooted it with Magisk boot image patching on PC, without TWRP and even installed GCam on it to improve the camera massively - can now take photos with Night Sight. The specs of this phone are AMAZING for its price. And the best part is it is without any notches, holes, pop-up cameras and retains the traditional clean design.
I tried the unlock bootloader (official) way to root the device but got stuck here:
Code:
C:\minimal_adb_fastboot_v1.4.3>fastboot flash unlock sn.img
target didn't report max-download-size
sending 'unlock' (5 KB)...
then nothing happens (waited for like 10 minutes).
Tried to install QPST 2.7 (3 different versions, same error) but setup gives me the following message:
Code:
the installer was interrupted before QPST 2.7 could be installed
SOLUTION: Download QPST Portable
---------- Post added at 08:25 ---------- Previous post was at 07:57 ----------
Getting Sahara error but not because I've waited too long! Any solutions? Getting desperate now.
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
RngrYogi said:
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
Click to expand...
Click to collapse
Also using your method would it require a user data wipe?
RngrYogi said:
Also using your method would it require a user data wipe?
Click to expand...
Click to collapse
yes, of course. it's like any standard boot loader unlocked. Which is why you do it first thing when you get the device.
Edit: I didn't see the question how to apply it -
just OEM unlock the device, and then
adb reboot bootloader
(wait for it too boot to boot loader)
fastboot flashing unlock
(accept unlocking voiding warranty, etc by pressing volume down and power)
fastboot flash boot <the boot.img>
Note that they don't recognize "fastboot boot" , which is my favorite way of rooting since it leaves the original image intact - and thus flashing is irreversible unless you get the stock OTA at a later time and flash it over. But this will not bring back the warranty and warnings.
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
greetings bro thanks for sharing the vbmeta.img file? didn't you use it?
few questions:
1. were did you find the stock firmware to pull the clean boot.img? Can you link it, I would like to have a backup if anything goes wrong
2. Is the patched boot.img for the North American Version?
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
morpheus______ said:
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
Click to expand...
Click to collapse
nice, thanks for the quick reply
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
On which rom you use it? Aparently its taken out from a Ianuary rom, latest being v2.32 afaik
Just whichever random firmware image I found. But you're overlooking one major thing which is - the kernel barely, if at all, changes between firmware versions . You can use this book image with any other firmware image of any date, earlier or later, and there's no reason why it wouldn't work. The Android OTA images are user mode, this is just the kernel + Ramdisk - and so are largely independent of each other. Only exception would be if there's some kernel vulnerability in that particular version of the kernel, which as far as we know now - there isn't.
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
LeonFresh said:
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
Click to expand...
Click to collapse
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Hi I just joined the TG but got banned any chance of unbanning me?
User is Indiana_Gems on TG I'm looking to change my RM7 CN to global
morpheus______ said:
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
Click to expand...
Click to collapse
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
LeonFresh said:
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
Click to expand...
Click to collapse
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
LeonFresh said:
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
Click to expand...
Click to collapse
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Morrovoker said:
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Click to expand...
Click to collapse
Not yet, I guess we just have to wait
LeonFresh said:
Not yet, I guess we just have to wait
Click to expand...
Click to collapse
any news yet i wanna switch from global to cn lol