Related
So, I have been using the P780 for some time now and, after I started having some problems with it and having to reboot too often, I decided to root it to uninstall the bloatware and give root access to some programs.
Well, I started looking into it and noticed a thread tutorial just for that. It just happened to be for KitKat and I was still running Jelly Bean.
I decided to first update to KitKat using the Official Lenovo software from their support site.
I know I should have taken a backup before, but I guess I foolishly thought nothing would go wrong with an official updater.
...Nothing did, BUT: It updated to the 4.4.2 based VibeUI2.0 and as it happens it doesn't have google services....
So I tried installing them. I tried seemingly everything, but I just couldn't get them to work.
Eventually I just started looking for another ROM.
I tried installing a couple different ones, but none of them worked.
(Including both of the current working links for the ROW ROMs in this thread: http://forum.xda-developers.com/lenovo-p780/general/stock-rom-lenovo-p780-official-stock-t2656441)
I tried multiple methods:
I used TWRP and tried to use the zip flash - no luck (One error I can't remember right now. error corrupted zip once. once there was no errors, but after booting it was just the same old VibeUI ROM so nothing had happened)
I tried using SP Flash Tool - It didn't find my phone (Yes, I did have my drivers installed)
I tried adb sideloading - didn't work (Can't remember the errors right now, but it did download the ROMs to the phone, they just didn't seem to install)
If anyone can offer any advice either on how to get the Google services working on the VibeUI ROM or how to install another ROM that has the google services, please do.
I might update this with the specific errors at some point, but I've been fighting with this damn phone for about 6 hours now and I'm about to collapse from stress, so I'll give up FOR NOW.
If u are rooted ,just find flashable Google apps(Gapps) for ur system type and flash through recoveries to make Google apps/services work.
Hi,
I have the same issue, actually gave up on the phone, but got play store working on the first Vibe UI, now with the update I am back to square one. Been reading forums for hours now without success. GMS Tool not working, says it won't install. Anyone with advice for a novice like me would help too.
planesavvy said:
Hi,
I have the same issue, actually gave up on the phone, but got play store working on the first Vibe UI, now with the update I am back to square one. Been reading forums for hours now without success. GMS Tool not working, says it won't install. Anyone with advice for a novice like me would help too.
Click to expand...
Click to collapse
anyone who need help with flashing a new rom pm me!
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
Here's the full description of my problem.
I wanted to install a custom ROM, so I applied for permission to unlock. I obtained the permission about a month ago, and then the problems began.
First off, I'm not able to bind my account to my device under developer options. It shows error 80612 and some Chinese characters. When I try to unlock, it stops at 99%and says the account is not bound to device. I tried all the solutions listed on mi forums, but to no avail. The only solution left was to install developer ROM and try from there
Here comes the second problem. When I try to install it from updater app, it says I'm only allowed to install stable versions. So I tried to install via recovery. When I boot into recovery, just shows an image of phone and asks me to connect to PC suite. No options are shown, no way to navigate. I can only reboot by pressing power button. So I tried installing PC suite and connecting my phone, but the software refuses to recognise my phone, either says to connect phone via USB(which I did) or tells me to update phone to use suite (phone is on latest stable version)
This is like a roadblock to me. These many problems should not be existing in a ROM, especially when they claim to be developer friendly. It's almost like Xiaomi doesn't want people to unlock their phones. Please someone help me with this. Pics will be provided as requested.
Edit: I tired installing older versions of developer and even tried downgrading the stable version via updater app, but failed, showing error that i can't install anything other than stable and that i can't install older versions respectively
Bro firstly you have to install the developer ROM and yeah it shows the error that you can only install stable ROM
Solution = just download the oldest available developer ROM and then download the newest developer ROM
Flash the oldest zip first with the updater app the developer ROM will get flashed, boot it up but don't set it up completely. After you're in the system again go to the updater app then flash the newest developer ROM
Once all this is done setup all the necessary info on the newest beta build
Go to the MIUI forums , fill up all your info, next go to the MIUI forums on your windows PC and check that if all the info as you filled up in your device is there or not, if it's there then you're on the right track
Next check is the MI cloud services are activated or not, if they are active then go to MI cloud on your PC and just click on find device, if it exactly locates your device then you're all done.
The MIUI forums play a major role in unlocking the bootloader so make sure all your info is there and you browse then for quite a while.
Then just try to unlock your bootloader it'll surely work. ?
Attempting right away
Still the same error
You did all of the things that I wrote right
Got stopped at flashing the oldest developer ROM. It still shows the error that I can't install anything other than stable versions
Blocked at first step itself. Can't flash the older ROM too via updater app. Still shows the error that i can't install anything other than newer stable versions
You tried the oldest available global developer ROM right ?
Yes. I even tried downgrading the stable version. Even that didn't work
Bro try this - Update to the latest global stable ROM then test flashing the oldest global developer ROM . I hope it works for ya
That's what I did in the first step. I'm on the latest global stable. After your suggestion, I tired installing the oldest global developer. Same error
Ok I'll see what I can do to help you now cause your problem is getting pretty strange. ?
Hi guys.
I got the MIUI 10.2.3. update and everything was fine, until I tried playing pubg mobile.
Experienced a heavy lag, extreme lag.
I play with low settings and have never ever experienced frame drops like this in my phone.
There was no pubg update also so I can definitively say it's an MIUI issue.
Whatever I do, the phone is not responding in a positive way (uninstalled and reinstalled the game, etc.)
Now the latest software does not allow me to revert back to the previous version (10.2.2.) also.
Please suggest a fix, I'm desperate.
If you can not revert back, try a custom rom.
I figured I'd do that, but the mi unlock tool is giving me a serious headache.
Tried different versions and each has one unique problem.
Basically the unlock tool is not detecting my phone, even in fastboot mode.
All the drivers are installed though
Edit: I was able to get into fastboot and the unlock tool detected it.
The trick is apparently to place the mi unlock tool folder in the C: drive.
Looking for a way out other than flashing a new rom right now.
That will be my last option in case nothing else works out / a new update doesn't come soon enough.
rahulv93 said:
I figured I'd do that, but the mi unlock tool is giving me a serious headache.
Tried different versions and each has one unique problem.
Basically the unlock tool is not detecting my phone, even in fastboot mode.
All the drivers are installed though
Click to expand...
Click to collapse
which version did you use ?
rahulv93 said:
I figured I'd do that, but the mi unlock tool is giving me a serious headache.
Tried different versions and each has one unique problem.
Basically the unlock tool is not detecting my phone, even in fastboot mode.
All the drivers are installed though
Click to expand...
Click to collapse
Are you on a Ryzen PC ? Xiaomi drivers are known to have problems on Ryzen builds.
I made it work, used mi unlock version 2.3.803.10 and placed the folder in the C drive.
Using a lenovo laptop with windows 10.
The drivers were already installed so no problems on that end. The phone was detected and the unlock option came up in a couple of minutes.
Although I am apprehensive now about flashing a new rom, considering I need to backup my files and reinstall my apps after I switch to a new rom (got no time for that lol).
So on another note, I came across this link in a forum (which I am not allowed to post here because I'm not 10 posts old yet). Basically that it takes time for your phone to adjust to the update and for the battery consumption to become normal etc. Probably I should wait a few days and use my phone like I normally do and then observe the heating/frame drops/battery consumption.
you can revert to 10.2.2, thank GOD i didnot updated yet... flash the fastboot rom, if it still failing it, remove restrictions from those scripts, thats just 1 line to remove though, and then flash full fastboot rom... flash 10.2.2 if its fastboot rom available, otherwise flash a previous one then install 10.2.2 zip...
HassanMirza01 said:
you can revert to 10.2.2, thank GOD i didnot updated yet... flash the fastboot rom, if it still failing it, remove restrictions from those scripts, thats just 1 line to remove though, and then flash full fastboot rom... flash 10.2.2 if its fastboot rom available, otherwise flash a previous one then install 10.2.2 zip...
Click to expand...
Click to collapse
How do I remove restrictions from scripts? Remember my phone's bootloader is still locked. I haven't unlocked it.
You can try to factory reset though. I have mine on 10.2.3 and got no issues at all. Works like a charm.
Bro.. root your phone. Then flash MALAKAS KERNEL or any other OC kernel. Then flash magisk modules included in MALAKAS KERNEL. Damn smooth.. yeah.
Install beta ROM it is working quite fine and back up all your app and data before doing so and copy the backup and obb folder to your pc so that you can restore all your apps with their data later on without any hassle
yash6# said:
Install beta ROM it is working quite fine and back up all your app and data before doing so and copy the backup and obb folder to your pc so that you can restore all your apps with their data later on without any hassle
Click to expand...
Click to collapse
Do I need to unlock bootloader? Or can I do it wihout unlocking thru the updater app?
rahulv93 said:
Do I need to unlock bootloader? Or can I do it wihout unlocking thru the updater app?
Click to expand...
Click to collapse
http://en.miui.com/getrom.php?m=yes&mobile=2 open the link and download the latest zip file for poco F1 and after downloading update it through the updater app no need to unlock the bootloader just make a backup and copy it to a pc
Solution For Poco F1 10.2.3.0 framedrop/lag issue
I have made a solution to this issue watch this video-https://youtu.be/ucwMahPzGi0
---------- Post added at 08:54 AM ---------- Previous post was at 08:32 AM ----------
Watch this-https://youtu.be/ucwMahPzGi0
Can you provide logs on your device? While playing pubg, log it. Please send it here
You can revert back to 10.2.2 without rooting your phone. Just download 10.2.2 software package zip file. Go to settings> about phone> software update> chose update package >select that zip file. Remember to format your phone. I had to do the same thing. Thats the only solution for pubg to work fine.
highly temp on your poco!.
You should be that phone was under 44° celcius. If your phone running in 44°, 45° or above, your phone will be droped FPS for playing PUBG mobile (extreem-smoot). Take that phone to fan or AC or something that reducing temp.( Running in MIUI 10.3 - Active save iphone XS max - customuser.ini iphone xs max)
I almost play in pubg mobile if my phone under 43° celcius only.
Sory, my english was bad.
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