Related
Hi guys... I recently flashed wrong boot.img to my phone and now it's dead... but not completely dead.
It at least open the recovey menu and if i plug the phone on usb with the exclamation symbol the RSD Lite detect the phone.
The big problem is that i can't find either update.zip or rom in sbf or shx format.
Someone here have that rom? i tried compiling update.zip with an backup of romdump... But without success.
www megaupload com/?d=DQDXDFFY
well I found this version but do not know if anger already running on your spice this is a Brazilian updating your possilvelmente mobilicity should be (if I mistake not)
mine too died a few days still do gain compensation, something with the signature updating the sdcard
writes as if by rsd lite my spice not recognized?
THanks! I will download this update and see if it restore my phone.
It's a update that only go to the card and flash in recovery menu or need to flash with rsd lite?
Sorry for double post.
I tried to flash but no success.
It fails to flash... I think that's because that i don't have the boot partition on my phone, but it boot fine in recovery menu and show the infos on RSD Lite
Here's the log:
Code:
16:04:47, April 30, 2011
Line: 533
ERROR: Unable to retrieve interface handle.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
No one can help me?
po voces sao do brasil ? agora que percibi na bandeira
Yes i'm
----
Sim eu sou
Hi All,
I am also in dire need of a stock ROM for my XT300 Spice. Can anyone point to a Canadian (Mobilicity) SBF file, or update.zip?
I have already flashed the Brazilian version but it cannot find the Mobilicity network, it's only finding Rogers, even though I have a Mobilicity SIM. Any ideas?
Many thanks!
After doing some more research today I figured I may not need another ROM. The Brazilian ROM seems just fine BUT it did change the baseband, that's why it's not finding the network anymore.
Still, I have no clue on how to restore or fix the baseband. Can anyone point to a "how-to" and a baseband (modem) image or dump file off a stock Mobilicity Motorola Spice?
Please help!
Dial *#*#4636#*#* on the phone
Diagnostic/testing screen pops up. Select Phone Information
Scroll down and choose WCDMA only
does that work? just a small tip
Exactly the same for me, Any solution?
Dataslycer said:
Dial *#*#4636#*#* on the phone
Diagnostic/testing screen pops up. Select Phone Information
Scroll down and choose WCDMA only
does that work? just a small tip
Click to expand...
Click to collapse
Setting from "phone information" does'nt work unless u dont have the right baseband software for desired country....
what are those baseband versions?
Would you folks mind just posting the various Baseband Versions you're referencing, and whether the particular XT300 is AWS Mobilicity or the rumored 850&1900 AT&T version? My Mobilicity is A309_U3_01.71.0. I am assuming Baseband is the place to look, since the Streak actually SAYS AWS in it, if you have one of those rare birds, but no one seems to know what the non-AWS will say on the Spice XT300.
Thank you.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
elf.elf.baby said:
Would you folks mind just posting the various Baseband Versions you're referencing, and whether the particular XT300 is AWS Mobilicity or the rumored 850&1900 AT&T version? My Mobilicity is A309_U3_01.71.0. I am assuming Baseband is the place to look, since the Streak actually SAYS AWS in it, if you have one of those rare birds, but no one seems to know what the non-AWS will say on the Spice XT300.
Thank you.
Click to expand...
Click to collapse
Hey,
Do you have an SBF file of your firmware or know how to extract it off the phone?
Thanks.
Hi:
Newbie here, so please bear with me. I am fairly techie, but never really worked on phones (I'm a Windows / Network engineer by trade).
I had an S6 Edge on the Vodafone network, and live in an area with poor cell coverage. So, I fully took advantage of wifi calling. I've upgraded to the S8 (gorgeous phone, BTW) so I gave the device to my missus, who made the mistake of buying an EE iPhone, and hates it.
We unlocked the phone to the EE network, but the wifi calling option has vanished, and I've been told that this is by design, as only phone purchased directly from EE have wifi calling enabled.
Been looking around, and have seen that if we root the phone and flash it with an EE image, then things should be hunky dory. However, having never undertaken a project like this on a phone, I'm seeking some guidance, as I don't want to completely brick the device.
Are there any idiot-proof step-by-step guides on here to do this?
Cheers in Advance
Steevi93 said:
Hi:
Newbie here, so please bear with me. I am fairly techie, but never really worked on phones (I'm a Windows / Network engineer by trade).
I had an S6 Edge on the Vodafone network, and live in an area with poor cell coverage. So, I fully took advantage of wifi calling. I've upgraded to the S8 (gorgeous phone, BTW) so I gave the device to my missus, who made the mistake of buying an EE iPhone, and hates it.
We unlocked the phone to the EE network, but the wifi calling option has vanished, and I've been told that this is by design, as only phone purchased directly from EE have wifi calling enabled.
Been looking around, and have seen that if we root the phone and flash it with an EE image, then things should be hunky dory. However, having never undertaken a project like this on a phone, I'm seeking some guidance, as I don't want to completely brick the device.
Are there any idiot-proof step-by-step guides on here to do this?
Cheers in Advance
Click to expand...
Click to collapse
It's actually a lot simpler than you think. No need to root all you have to do is flash the EE firmware through Odin (Samsung flashing tool) and voila, EE Wi-Fi calling will appear. Also volte will be available too.
If you need step by step I can help.
I need model number and android version and I can link you the firmware.
callumbr1 said:
It's actually a lot simpler than you think. No need to root all you have to do is flash the EE firmware through Odin (Samsung flashing tool) and voila, EE Wi-Fi calling will appear. Also volte will be available too.
If you need step by step I can help.
I need model number and android version and I can link you the firmware.
Click to expand...
Click to collapse
Hey dude.... after trolling through this forum some more, I was able to find what I needed to flash the firmware onto the device... However, Wi-Fi calling (as an option) does not seem to appear yet, but I wonder if that is due to the lack of SIM card (wife put it back in her iPhone, so I could sort this at work.
If I've downloaded the wrong stuff, then I'm happy to redo.
Model Number: SM-G925F
Android Version: 7.0
Baseband Version: G925FXXU5EQF1
Steevi93 said:
Hey dude.... after trolling through this forum some more, I was able to find what I needed to flash the firmware onto the device... However, Wi-Fi calling (as an option) does not seem to appear yet, but I wonder if that is due to the lack of SIM card (wife put it back in her iPhone, so I could sort this at work.
If I've downloaded the wrong stuff, then I'm happy to redo.
Model Number: SM-G925F
Android Version: 7.0
Baseband Version: G925FXXU5EQF1
Click to expand...
Click to collapse
When you downloaded the firmware was there 5 files in the zip? Or just the one AP file?
Did you look in phone app > settings then scroll to bottom for Wi-Fi calling option? If you flashed an EE firmware it should be there mate.
As well as the EE firmware you need to have the EE csc. You have this csc, EVR?
callumbr1 said:
When you downloaded the firmware was there 5 files in the zip? Or just the one AP file?
Did you look in phone app > settings then scroll to bottom for Wi-Fi calling option? If you flashed an EE firmware it should be there mate.
As well as the EE firmware you need to have the EE csc. You have this csc, EVR?
Click to expand...
Click to collapse
Hi... There was only the one file (the AP file, I believe)_ and no, when I checked the phone settings, wifi calling was not showing as an option. If you have a link to the correct firmware, I'm happy to reflash the phone, as I have everything here with me at work.
Steevi93 said:
Hi... There was only the one file (the AP file, I believe)_ and no, when I checked the phone settings, wifi calling was not showing as an option. If you have a link to the correct firmware, I'm happy to reflash the phone, as I have everything here with me at work.
Click to expand...
Click to collapse
Flash this version from here
http://updato.com/firmware-archive-select-model?record=75717719616711E7963AFA163EE8F90B
The version you flashed previous was PRT Poland version.
Flash the one I posted it is UK EVR and then you will have Wi-Fi calling.
callumbr1 said:
Flash this version from here
http://updato.com/firmware-archive-select-model?record=75717719616711E7963AFA163EE8F90B
The version you flashed previous was PRT Poland version.
Flash the one I posted it is UK EVR and then you will have Wi-Fi calling.
Click to expand...
Click to collapse
Thanks.... I will give that a go when I get home. Cheers.
Steevi93 said:
Thanks.... I will give that a go when I get home. Cheers.
Click to expand...
Click to collapse
No problem
Steevi93 said:
Thanks.... I will give that a go when I get home. Cheers.
Click to expand...
Click to collapse
If by chance you encounter hidden.img fail in Odin don't panic.
Just unpack the firmware and remove the hidden.img. repack and flash again.
callumbr1 said:
If by chance you encounter hidden.img fail in Odin don't panic.
Just unpack the firmware and remove the hidden.img. repack and flash again.
Click to expand...
Click to collapse
Heya.... no such "issues" so to speak. Just one where my baby kicked the USB cable, causing a brief disconnect during the flashing process. This, of course, sent me into a spiral of panic because the entire phone crashed, with errors, recovery messages invoking Smart Switch, and the like. However, restarting the phone and connecting it to Odin completely recovered the phone.
Initially, the flashing worked, but it didn't enabled Wi-Fi calling, so I reset the phone back to factory settings, flashed it again and voila!!!! Worked like a charm! Then restored the backup from Smart Switch that I made yesterday, and the missus now has a full functional EE phone with Wi-Fi calling.
Thanks very much for your help mate.... you're a legend.
I'm gonna keep Odin, as it seems like a great recovery tool as well. :good:
Steevi93 said:
Heya.... no such "issues" so to speak. Just one where my baby kicked the USB cable, causing a brief disconnect during the flashing process. This, of course, sent me into a spiral of panic because the entire phone crashed, with errors, recovery messages invoking Smart Switch, and the like. However, restarting the phone and connecting it to Odin completely recovered the phone.
Initially, the flashing worked, but it didn't enabled Wi-Fi calling, so I reset the phone back to factory settings, flashed it again and voila!!!! Worked like a charm! Then restored the backup from Smart Switch that I made yesterday, and the missus now has a full functional EE phone with Wi-Fi calling.
Thanks very much for your help mate.... you're a legend.
I'm gonna keep Odin, as it seems like a great recovery tool as well. :good:
Click to expand...
Click to collapse
Hey buddy,
Brilliant news mate enjoy. Glad I could help you.
Yeah keep Odin as it's always very useful in times of need. However you shouldn't have any issues from now :good:
Thanks the posts if you can mate :good:
Hi All,
I tried some custom ROM on my P20 lite and it got stuck in a boot loop. So I flashed the Stock ROM from this thread using HuRUpdater. I tried version 8.0.0.146 then realised my p20 lite is only single sim unlike my partner's one so flashed 8.0.0.143 to see if that works.
The phone boots with both but shows Build Number 8.0.0.046(0CXB) and I can't get it to update. My partner's P20 Lite shows Build Number 8.0.0.144(C432) so I assume mine should work with the 143 SS from the thread above. My partners phone is just left stock bootloader hasn't been touched.
Any ideas what I'm doing wrong? I've tried eRecovery and that just says can't get package info.
At a loss now.
MikeyAlder said:
Hi All,
I tried some custom ROM on my P20 lite and it got stuck in a boot loop. So I flashed the Stock ROM from this thread using HuRUpdater. I tried version 8.0.0.146 then realised my p20 lite is only single sim unlike my partner's one so flashed 8.0.0.143 to see if that works.
The phone boots with both but shows Build Number 8.0.0.046(0CXB) and I can't get it to update. My partner's P20 Lite shows Build Number 8.0.0.144(C432) so I assume mine should work with the 143 SS from the thread above. My partners phone is just left stock bootloader hasn't been touched.
Any ideas what I'm doing wrong? I've tried eRecovery and that just says can't get package info.
At a loss now.
Click to expand...
Click to collapse
Is your device an ANE-LX1C432 Single SIM ?
Do you have SIM locked or is free?
It's single SIM and as far as I know it's ane-lx1C432 bought in the UK. It's also sim unlocked
MikeyAlder said:
It's single SIM and as far as I know it's ane-lx1C432 bought in the UK. It's also sim unlocked
Click to expand...
Click to collapse
1- Install terminal emulator from google play
2- Run this command
Code:
getprop ro.hw.custPath
3- If the output is different from this => /cust/hw/eu => let us know
HWANE:/ $ getprop ro.hw.custPath
/cust/o2/uk
HWANE:/ $
you flashed wrong lx1 file, its same with me, i flashed for my dual sim what are ANE-LX1c432 (dual sim actualy are ANE-L21c432 but single sim are ANE-L01c432) so i flashed for my dual sim ANE-L01c432 and now in build number i have 8.0.0.046(09B8) you need to download right ANE-L01C432 and agine with hurupdate, and all be ok
oh, right, your cust info are different, my writed here are wrong (becasue for me cust are hw/eu)
MikeyAlder said:
HWANE:/ $ getprop ro.hw.custPath
/cust/o2/uk
HWANE:/ $
Click to expand...
Click to collapse
In your phone only ROM's from your provider (O2) will work without issues.
You should restore your backup from your original rom.
Thanks for the info. I seem to have deleted my backup so not sure where to get O2 ROMs from. Am I able to change it to accept the EU ROMs or is that not possible?
MikeyAlder said:
Thanks for the info. I seem to have deleted my backup so not sure where to get O2 ROMs from. Am I able to change it to accept the EU ROMs or is that not possible?
Click to expand...
Click to collapse
Yes it is, but void your warranty.
1. Backup your oeminfo partition, use TWRP.
2. Check the thread HwOTA8 for Huawei P20 Lite, in this tool you can learn how to change oeminfo to hw/eu
3. Then install full firmware B146, but the Dual SIM, because that oeminfo is for Dual. This installation can be done with HuRUpdater tool
4. It's done.
Other possible way to restore your device is use a TWRP backup from other device with O2 rom.
Do it at your own risk.
kilroystyx said:
Yes it is, but void your warranty.
1. Backup your oeminfo partition, use TWRP.
2. Check the thread HwOTA8 for Huawei P20 Lite, in this tool you can learn how to change oeminfo to hw/eu
3. Then install full firmware B146, but the Dual SIM, because that oeminfo is for Dual. This installation can be done with HuRUpdater tool
4. It's done.
Other possible way to restore your device is use a TWRP backup from other device with O2 rom.
Do it at your own risk.
Click to expand...
Click to collapse
Thanks for all your help. Just got round to do this tonight and all is working correctly now. ?
I am new to this and I am very confused, I have the bootloader blocked in my p20 lite, I have ANE-LX3 with bloatware operator, I just want to remove all the bloatware and leave my cell phone with stock version without bloatware operator .... as I could remove everything that and with what program do you start?
jorgerolonpy said:
I am new to this and I am very confused, I have the bootloader blocked in my p20 lite, I have ANE-LX3 with bloatware operator, I just want to remove all the bloatware and leave my cell phone with stock version without bloatware operator .... as I could remove everything that and with what program do you start?
Click to expand...
Click to collapse
read, try this
My Note 8 was purchased from ATT a couple of years ago. I received the Pie update. Then I decided to switch to T Mobile. As soon as I booted up with a T Mobile SIM, the firmware changed itself to T Mobile.
Now I want to gift this phone to someone who lives in China. I tried to flash the latest U1_XAA firmware to the phone, but so far, it has failed to flash. Is this even possible? Or is there something special I needed to do to flash it with Odin?
Thank you.
de2000 said:
My Note 8 was purchased from ATT a couple of years ago. I received the Pie update. Then I decided to switch to T Mobile. As soon as I booted up with a T Mobile SIM, the firmware changed itself to T Mobile.
Now I want to gift this phone to someone who lives in China. I tried to flash the latest U1_XAA firmware to the phone, but so far, it has failed to flash. Is this even possible? Or is there something special I needed to do to flash it with Odin?
Thank you.
Click to expand...
Click to collapse
Follow the instructions to switch from N950U to N950U1 and you'll be fine just don't try to flash anything with a lower boot loader version it'll always fail! If you're on boot loader version 5 then you HAVE TO flash either 5 or 6 no going backwards to 4 or lower! There's a page on the forums to switch from N950U to N950U1.. It's easy to do. This is the page! Make sure you read from page 1 to understand! https://forum.xda-developers.com/galaxy-note-8/how-to/guide-sm-n950u-u1-t3685884
MrMike2182 said:
Follow the instructions to switch from N950U to N950U1 and you'll be fine just don't try to flash anything with a lower boot loader version it'll always fail! If you're on boot loader version 5 then you HAVE TO flash either 5 or 6 no going backwards to 4 or lower! There's a page on the forums to switch from N950U to N950U1.. It's easy to do. This is the page! Make sure you read from page 1 to understand! https://forum.xda-developers.com/galaxy-note-8/how-to/guide-sm-n950u-u1-t3685884
Click to expand...
Click to collapse
Thank you!
I am a noob at this. I've downloaded the latest U1_XAA firmware from Sammobile. Since I don't know how to decipher the firmware file name to see what bootloader it is, I assumed that it is equal or higher than the Android Pie in my Note 8. I will try flashing again with the PrinceComsy Odin again later since my phone has carrier's Android Pie right now (ATT to T Mobile automatically).
Just checked. Phone has PDA N950USQS6DSG6 and CSC N950UOYN6DSG6. I downloaded PDA N950U1UES6DSH1 and CSC N950U1OYM6DSH1 from Sammobile. Looks like they both are booloader 6, no? Will try PrinceComsy to flash.
Tried flashing, it failed. Don't know what to do now...
de2000 said:
Tried flashing, it failed. Don't know what to do now...
Click to expand...
Click to collapse
You need to make sure you use the right Odin and if it doesn't work just reboot into recovery mode and factory reset the phone so you can at least use it where it was before.
I've tried Patched, Prince, and regular Odin. They all failed...
Just wondering if the automatic change of ATT to T Mobile firmware when I changed carrier has anything messing this up.
MrMike2182 said:
You need to make sure you use the right Odin and if it doesn't work just reboot into recovery mode and factory reset the phone so you can at least use it where it was before.
Click to expand...
Click to collapse
Anything else I could try?
Thank you.
de2000 said:
Anything else I could try?
Thank you.
Click to expand...
Click to collapse
Does it at least boot up? If it does you can just send it the way it is and let whoever you're giving it to see if their sim card will work. It appears as if it's on the latest firmware version already which is boot loader version 6 so you might not be able to switch to the U1 version because Samsung might have blocked it in the new version.
Yeah, it operates as normal when I leave the loading screen. The phone was already unlocked and was used in Asia and Asian SIM card as an ATT phone. If there is nothing else I could do, I'll just have to give it out like the way it is.
Thanks for your help.
MrMike2182 said:
Does it at least boot up? If it does you can just send it the way it is and let whoever you're giving it to see if their sim card will work. It appears as if it's on the latest firmware version already which is boot loader version 6 so you might not be able to switch to the U1 version because Samsung might have blocked it in the new version.
Click to expand...
Click to collapse
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