A) TOUCH SCREEN: I have 2 phones Moto G Power 2020 XT2041-4 Code name: SOFIA Firmware: QPMS30.80-109-5 and after installing TWRP I found that touch screen on one of the phones doesn't work. I started looking for the differences in these phones and I discovered that screen vendors of the phones are different and correspondingly they used different drivers, so with available unofficial TWRP 3.5.0-10 touch screen worked only for one phone. I had to provide drivers and references to these drivers in TWRP in order other phone's touch screen worked in TWRP. How I resoled the problem (step by step):
1) find out what screen vendor you have in your phone | install on your phone apk "Devices Info HW+" start it up and in "General" look for "LCM" records | I have in both my phones different vendors: "dsi_ft8756_tm_vid_display" & "dsi_ft8756_auo_vid_display" | One phone Moto G Power with "dsi_ft8756_tm_vid_display" vendor had no problems with touch screen and other Moto G Power has no touch screen with "dsi_ft8756_auo_vid_display" screen vendor.2) unpack TWRP with AIK (android-image-kitchen) | open file \ramdisk\sbin\load_ts_firmware.sh in notepad for editing and find this record:sofia)insmod $module_path/aw8695.kofirmware_file="focaltech-tianma-ft8756-0b-01-sofia.bin"then edit last line and exchange name of the firmware file so it would look like:sofia)insmod $module_path/aw8695.kofirmware_file="focaltech-auo-ft8756-0b-01-sofiap.bin"save the file and repack TWRP in AIK | test your phone booting to a new repacked TWRP file | Touch screen must work nowB) OTG: I noticed that in both of my Moto G Power I could not mount USB-OTG in TWRP. | I unpacked the TWRP with AIK and edited \ramdisk\etc\twrp.fstab file so last two lines should look like this:
/external_sd vfat /dev/block/mmcblk1p1 flags=removable;storage;display="external_sd"/usb-otg auto /dev/block/sda1 flags=fsflags=utf8;display="usb-otg";storage;wipeingui;removable
save the file and repack TWRP in AIK | test your phone booting to a new repacked TWRP file | USB-OTG must work now
That's all folks. Enjoy!
PS: Two attached files edited TWRP files based on unofficial TWRP 3.5.0-10 | "twrp-3.5.0-10_tm.img" for Moto G Power 2020 with "dsi_ft8756_tm_vid_display" touch screen vendor and "twrp-3.5.0-10_auo.img" for Moto G Power 2020 with "dsi_ft8756_auo_vid_display" touch screen vendor. USB-OTG & touch screen are fixed.
I look forward to trying this out! I think several of us have wondered why our touchscreens were screwy while others claimed they had no issues.
Bravo sir!!
Wow...sounds like fun....and I'm gonna try on sofiap metropcs...had same issue
I took yours TWRP 3.5.2-10 and edited files same way as I wrote above: 1) "\ramdisk\system\etc\twrp.flags" to fix USB-OTG and 2) "\ramdisk\system\bin\load_modules.sh" to fix touch screen for the Sofia XT2041-4 with "dsi_ft8756_auo_vid_display" vendor's display
Now both of my Moto G Power has updated TWRP and working touch screen and USB-OTG. Thank you for the TWRP 3.5.2-10
PS: yes "dsi_ft8756_auo_vid_display" is used for Moto G Stylus XT2043 (Code name: SOFIAP) but in my second Moto G Power XT2041-4 screen like in Moto G Stylus XT2043
Finally got around to trying this out. I can confirm that the 'auo' versions work with proper touchscreen operation! I tried out the 3.5.2-10_auo file, and although I didnt test it extensively, it looks to finally be the working TWRP many of us have been hoping for.
Good work guys, and thank you.
(BTW: anyone else who uses this from fastboot/command line note the 3.5.2 file uses a "_" after TWRP, rather than a "-" like the typical img files. My inattention to that detail had me scratching my head for a few minutes )
Is there any other way to find which screen you have? I tried the free version of the app you mentioned. It didn't have an LCM record. So I paid "plus" version of the app, and it doesn't show an LCM record either - maybe because I'm not rooted. I don't know. (I have an XT2041-4)
Tom2112 said:
Is there any other way to find which screen you have? I tried the free version of the app you mentioned. It didn't have an LCM record. So I paid "plus" version of the app, and it doesn't show an LCM record either - maybe because I'm not rooted. I don't know. (I have an XT2041-4)
Click to expand...
Click to collapse
the app you need is called Device Info HW, and the info is listed under touchscreen in the first tab buddy
Yeah, not so much. Like I said, I downloaded the app, it didn't show the info mentioned above. So I tried the paid "plus" version of the app. It showed the exact same info, but not the info mentioned above.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tom2112 said:
Yeah, not so much. Like I said, I downloaded the app, it didn't show the info mentioned above. So I tried the paid "plus" version of the app. It showed the exact same info, but not the info mentioned above.View attachment 5473507
Click to expand...
Click to collapse
Something similar happened while trying to determine the type of display on my device as well, same model number as yours. The suggested information was not available in the app.
Tom2112 said:
Yeah, not so much. Like I said, I downloaded the app, it didn't show the info mentioned above. So I tried the paid "plus" version of the app. It showed the exact same info, but not the info mentioned above.View attachment 5473507
Click to expand...
Click to collapse
out of curiosity, did you try either of the two attached twrp images?
Had the same issue, no mention of LCM record between Kernel and Touchscreen sections under General tab.
Only after enabling Use Root (for getting complete information) in Settings did the LCM record appear.
Beetle84 said:
out of curiosity, did you try either of the two attached twrp images?
Click to expand...
Click to collapse
No, I was trying to figure out which one was the right one for my phone.
Tom2112 said:
Yeah, not so much. Like I said, I downloaded the app, it didn't show the info mentioned above. So I tried the paid "plus" version of the app. It showed the exact same info, but not the info mentioned above.View attachment 5473507
Click to expand...
Click to collapse
Try booting into fastboot. On my g power it shows the display model at the bottom of the screen.
Tom2112 said:
No, I was trying to figure out which one was the right one for my phone.
Click to expand...
Click to collapse
You should simply flash them, saves all the trouble. If it works, yay if not, reflash stock recovery and you are no worse off.
I can confirm that on my XT2041-4, booting into fastboot shows the display model at the bottom of the screen. On mine, it shows...
Panel: 0x91560201 tm_ft8756_fhd_vid
Hey guys, I tried this for my sofia XT2041-4 with auo touchscreen version and it works fine except for flashing roms and other zips. Every time I try to flash something, I get an error message. Does flashing work for everyone else? Thanks.
Aceofzeroz said:
Hey guys, I tried this for my sofia XT2041-4 with auo touchscreen version and it works fine except for flashing roms and other zips. Every time I try to flash something, I get an error message. Does flashing work for everyone else? Thanks.
Click to expand...
Click to collapse
Boot into twrp and go into the mount tab. By default twrp only seems to mount data, so mount the other partitions on your phone. If that was the issue then it should work now.
DAV1326 said:
Boot into twrp and go into the mount tab. By default twrp only seems to mount data, so mount the other partitions on your phone. If that was the issue then it should work now.
Click to expand...
Click to collapse
I see, that makes sense. I'm going to try it and see if it works and report back if it does or doesn't. Thanks again for your quick response!
Edit: I tried once again by mounting the other partitions but I still get the same error only when I flash rom zips. Howeer when I tried the twrp-3.5.0-10_auo (I was using the twrp-3.5.2-10) it works with that one. Thanks again for your help!
Aceofzeroz said:
I see, that makes sense. I'm going to try it and see if it works and report back if it does or doesn't. Thanks again for your quick response!
Edit: I tried once again by mounting the other partitions but I still get the same error only when I flash rom zips. Howeer when I tried the twrp-3.5.0-10_auo (I was using the twrp-3.5.2-10) it works with that one. Thanks again for your help!
Click to expand...
Click to collapse
Thanks. I also ran into issues with the twrp-3.5.2-10 version when trying to flash zips. Because my phone had other issues I wasn't sure why. I recently found that the twrp-3.5.0-10 (auo version) worked.
I noticed that the original & and auo 3.5.0 versions are similar in size but the 3.5.2 ones are considerably smaller than 3.5.0.
Leroy_Sparks said:
Thanks. I also ran into issues with the twrp-3.5.2-10 version when trying to flash zips. Because my phone had other issues I wasn't sure why. I recently found that the twrp-3.5.0-10 (auo version) worked.
I noticed that the original & and auo 3.5.0 versions are similar in size but the 3.5.2 ones are considerably smaller than 3.5.0.
Click to expand...
Click to collapse
Oh awesome, you're welcome! Yeah, you're right about that size difference and I noticed it as well, but thought that it'd still work regardless. Glad we both got this sorted out in time before giving up on this wonderful fix.
Related
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
BLU R1 HD
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters@bullet25
@triggerlord
@jasonmerc
@ColtonDRG
...To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for BLU R1 HD
[Index] BLU R1 HD - Amazon and OEM Variants
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]BLU R1 HD[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. [/SIZE]
[SIZE=+1]Q1: Can I root the BLU R1 HD?[/SIZE]Yes. for the Amazon Variant please see these posts:
Original Root Post Here (Includes TWRP)
Or Step-by-Step Root Here (Includes TWRP)
For the OEM Variant please see this post:
Step-by-Step Root (Includes TWRP)[SIZE=+1]Q2: Can I unlock the bootloader?[/SIZE]Yes for the Amazon Variant please see this post:
Bootloader Unlock
For the OEM Variant please see this post:
Step-by-Step Root (Includes TWRP)*Forum Rules | New Users Guide | XDA Tour | Report PostsA special thanks to everyone who contributed to the production of this FAQ
revered #2
Yo, I'll help. I'm stalking these forums 24/7 anyway.
Manual Camera Compatibility
Does it fully support the Camera2 API for use with manual camera apps?
TorrentialTech said:
Does it fully support the Camera2 API for use with manual camera apps?
Click to expand...
Click to collapse
Give me an app that uses Camera2 API and I'll test it and let you know.
Also @bullet25 I can never sleep anyway so add me to this glorious list, if you'd be so kind
jasonmerc said:
Give me an app that uses Camera2 API and I'll test it and let you know.
Also @bullet25 I can never sleep anyway so add me to this glorious list, if you'd be so kind
Click to expand...
Click to collapse
play.google.com/store/apps/details?id=pl.vipek.camera2_compatibility_test&hl=en This should do it
TorrentialTech said:
play.google.com/store/apps/details?id=pl.vipek.camera2_compatibility_test&hl=en This should do it
Click to expand...
Click to collapse
Doesn't look too pleasing.
jasonmerc said:
Doesn't look too pleasing.
Click to expand...
Click to collapse
Oh, that's a shame. I was hoping it would support Camera2 being such a recently launched phone. Hopefully it would work with a simple build.prop edit like the Redmi Note 3 or the Moto X Style.
TorrentialTech said:
Oh, that's a shame. I was hoping it would support Camera2 being such a recently launched phone.
Click to expand...
Click to collapse
There's always other alternatives that use their own camera drivers rather than manufacturer-bundled ones. Open Camera for one is a very good app that does not depend on device bundled camera drivers. It is very feature-rich and can be a powerful camera app if used in the right hands. Open Camera might be able to do what you're looking to do:
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera
Thought I would ask this in the right thread.
My Amazon subsidized R1 HD is rooted with systemless Xposed installed. I did take the OTA update last week. It had been working fine for two days. I powered the phone off and placed on the charger, at which point it keeps continuously attempting to boot, just flashing the White Blu screen every 4-5 seconds. No combination of button presses, or holding of power seems to be able to stop it, so can't power the phone down, or get into TWRP. Ideas? It does not have a SIM in it at the moment, or when this occurred if that might matter.
While I have rebooted the phone many times since rooting, this may have been the first time that I have completely powered it down since rooting and installing TWRP this weekend. I had not made any changes to anything for a day or so, and it had survived many reboots. The only thing I can think of is that I did freeze the Amazon Offers App in TiBu to see what would happen, however, not sure that is in anyway related since it is not even getting to a point in the startup where it would check.
Is there some kind of boot verification Power Up, that does not occur on reset, where the modified Boot image of SuperSU would be the issue?
The only response I can get from the phone is that if I hold Volume+ and Pwr, the phone takes a few more seconds between reboots.....
ariesgodofwar said:
Thought I would ask this in the right thread.
My Amazon subsidized R1 HD is rooted with systemless Xposed installed. I did take the OTA update last week. It had been working fine for two days. I powered the phone off and placed on the charger, at which point it keeps continuously attempting to boot, just flashing the White Blu screen every 4-5 seconds. No combination of button presses, or holding of power seems to be able to stop it, so can't power the phone down, or get into TWRP. Ideas? It does not have a SIM in it at the moment, or when this occurred if that might matter.
While I have rebooted the phone many times since rooting, this may have been the first time that I have completely powered it down since rooting and installing TWRP this weekend. I had not made any changes to anything for a day or so, and it had survived many reboots. The only thing I can think of is that I did freeze the Amazon Offers App in TiBu to see what would happen, however, not sure that is in anyway related since it is not even getting to a point in the startup where it would check.
Is there some kind of boot verification Power Up, that does not occur on reset, where the modified Boot image of SuperSU would be the issue?
The only response I can get from the phone is that if I hold Volume+ and Pwr, the phone takes a few more seconds between reboots.....
Click to expand...
Click to collapse
Is it booting into android at least? If it is you can try:
Code:
adb reboot recovery
then in twrp do a default wipe (data, cache, dalvik) then see if everything is fine afterwards.
If not, try just letting it do its thing until it dies then see if it acts normal.
Otherwise its probably a hardware issue and needs to be replaced.
I've shutdown and booted mine several times with the TWRP and Root installed so I don't think its that.
bullet25 said:
Is it booting into android at least? If it is you can try:
Code:
adb reboot recovery
then in twrp do a default wipe (data, cache, dalvik) then see if everything is fine afterwards.
If not, try just letting it do its thing until it dies then see if it acts normal.
Otherwise its probably a hardware issue and needs to be replaced.
I've shutdown and booted mine several times with the TWRP and Root installed so I don't think its that.
Click to expand...
Click to collapse
Thanks! Yeah, it is not booting anywhere other than the White Screen that say BLU, so I can't even get to adb or TWRP (If I could I could fix it). Letting it die is my only other thought....... I was using a Nexus charge block, and a 3rd party cable which has been sketchy in the past, so maybe related to that.
But as you say, it may be hardware related, as it does not even seem to be going far enough in boot process to load Fastboot, let alone OS.
I raised a replacement request with Amazon just in case.....
Question on Encryption.
I have root and TWRP working correctly. My work Outlook profile requires (and I want) device encryption. I select the option to encrypt, enter my pin, get the Android guy gear cut in half thing icon for about 30 seconds then just a black screen. I let it sit like this for over an hour and nothing changed, so I rebooted. Phone isn't encrypted. Tried it again and got the same result. Am I missing something obvious here? Can you not encrypt if you have unlocked or something? Thanks!
brockwitting said:
Question on Encryption.
I have root and TWRP working correctly. My work Outlook profile requires (and I want) device encryption. I select the option to encrypt, enter my pin, get the Android guy gear cut in half thing icon for about 30 seconds then just a black screen. I let it sit like this for over an hour and nothing changed, so I rebooted. Phone isn't encrypted. Tried it again and got the same result. Am I missing something obvious here? Can you not encrypt if you have unlocked or something? Thanks!
Click to expand...
Click to collapse
I know with other phones you can do encryption with an unlocked bootloader, I don't know about this one. Either something is wrong with the phone's encryption or I honestly don't know. I'll try encrypting mine when I get a chance.
@brockwitting Encryption seems to be working. You have to unroot first and have a pin/patteren/or password to unlock the device. After that go through the encrypt steps. My phone shows the Android cut in half logo for about 10 second then a black screen for about another 30. It then rebooted and was at just the wallpaper. I hard shutdown by holding the power button then rebooted again. After I got a pin unlock screen after inputting the pin I had to press the power button, this might be normal I've never actually used android encryption before, and the phone was working fine since.
Screenshot
You can reboot into recovery afterwards and reroot.
bullet25 said:
@brockwitting Encryption seems to be working. You have to unroot first and have a pin/patteren/or password to unlock the device. After that go through the encrypt steps. My phone shows the Android cut in half logo for about 10 second then a black screen for about another 30. It then rebooted and was at just the wallpaper. I hard shutdown by holding the power button then rebooted again. After I got a pin unlock screen after inputting the pin I had to press the power button, this might be normal I've never actually used android encryption before, and the phone was working fine since.
Screenshot
You can reboot into recovery afterwards and reroot.
Click to expand...
Click to collapse
Sorry for the noobishness here, is there an easy way to temporarly Unroot without doing a full device restore to my pre-root state?
brockwitting said:
Sorry for the noobishness here, is there an easy way to temporarly Unroot without doing a full device restore to my pre-root state?
Click to expand...
Click to collapse
Open the SuperSU app, go to settings and there's an option for Full Unroot. Select that, reboot, then do the device encryption. After you verify its working okay reboot back into recovery and flash SuperSU again. TWRP will ask for your password, just enter your password/pin when it does.
bullet25 said:
Is it booting into android at least? If it is you can try:
Code:
adb reboot recovery
then in twrp do a default wipe (data, cache, dalvik) then see if everything is fine afterwards.
If not, try just letting it do its thing until it dies then see if it acts normal.
Otherwise its probably a hardware issue and needs to be replaced.
I've shutdown and booted mine several times with the TWRP and Root installed so I don't think its that.
Click to expand...
Click to collapse
So, just wanted to close the loop in the event anyone else runs into this. After 7 hours of rebooting every 3 seconds, the battery ran out. The phone then turned on just fine when I attempted to restart it.......... very odd, but all seems well.
ariesgodofwar said:
Thanks! Yeah, it is not booting anywhere other than the White Screen that say BLU, so I can't even get to adb or TWRP (If I could I could fix it). Letting it die is my only other thought....... I was using a Nexus charge block, and a 3rd party cable which has been sketchy in the past, so maybe related to that.
But as you say, it may be hardware related, as it does not even seem to be going far enough in boot process to load Fastboot, let alone OS.
I raised a replacement request with Amazon just in case.....
Click to expand...
Click to collapse
Well spft is still an option. At the point of power off to power on there is a pause on Android that spft uses to inject a DA program of sorts (download assistant). So try to do a readback of the first like 5mb. The read back information dosent matter itbis the DA injection your looking for. If it works the on off cycle should stop. Then unplug and phone should be off
Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.
Shinnazuka0411 said:
Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.
Click to expand...
Click to collapse
For a device that was format all. Will need more partitions than are in that package you tried. Also I have tried to work with someone else who had the 8gb size device, we could not get past that error.
I do recall that the last last person got a new board for his phone and pulled the images from it to share. There is a link in the main thread somewhere. But , well even when he tried to restore his own backup from good device to the one with do error, it did not work.
NVM
I remembered it wrong. He tried to pull it, but could not do it.
Look through this thread. Maybe you can try to follow the advice I gave him, and it may work for you.
https://forum.xda-developers.com/r1...-blu-r1-hd-t3440261/post76482224#post76482224
Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV
Shinnazuka0411 said:
Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV
Click to expand...
Click to collapse
There is now a "repair rom" listed in an mtk support group I try to follow. I have not checked it out yet, but maybe it will help. Let me open this on PC to search for the link
this one was labled v6.4 firmware http://www.mediafire.com/file/6kys9896445l5sm/SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip/file
this is labled as a repair firmware http://www.mediafire.com/file/il54pxuvpkargtr/BLU_R1_HD_R0030UU_REPAIR_MT6735.rar/file
I would have you look at those , first i suppose.
if it does not work I do have backups made from miricle-box, but they are not uploaded anywhere right now.
Real appreciated, will keep you updated, if anything works ill post it here.
Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL
Shinnazuka0411 said:
Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL
Click to expand...
Click to collapse
all I can do is share the backup from miricle-box that I have.
https://www.androidfilehost.com/?fid=5862345805528042536
Just trying to catch up, so bricked phone that wont format correct? Do you have twrp on it?
mrmazak said:
all I can do is share the backup from miricle-box that I have.
androidfilehost/?fid=5862345805528042536
Click to expand...
Click to collapse
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??
TavoStyle said:
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??
Click to expand...
Click to collapse
This is from 16gb so the R0030uu
mrmazak said:
This is from 16gb so the R0030uu
Click to expand...
Click to collapse
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TavoStyle said:
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
Click to expand...
Click to collapse
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\
mrmazak said:
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\
Click to expand...
Click to collapse
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)
TavoStyle said:
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)
Click to expand...
Click to collapse
Most important part (custom build number) is missing from screen shot.
mrmazak said:
Most important part (custom build number) is missing from screen shot.
Click to expand...
Click to collapse
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig
TavoStyle said:
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig
Click to expand...
Click to collapse
so your build number is 6.6
you may be able to unlock.
But is phone still alive?
mrmazak said:
so your build number is 6.6
you may be able to unlock.
But is phone still alive?
Click to expand...
Click to collapse
My phone is stuck in the BLU logo
TavoStyle said:
My phone is stuck in the BLU logo
Click to expand...
Click to collapse
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\
Bricked BLU R1 HD
mrmazak said:
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\
Click to expand...
Click to collapse
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA. I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone. I am trying to install twrp but when I power on my device it is stuck on the boot loading screen. I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Tried using adb commands but when I connect to the phone and run adb commands it says no authorisation.
If I can install twrp on the device then I will be able to install the rom from rootjunky, not sure if you require more info.
Awaiting your ananlys
Kind Regards
ismailf007 said:
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA.
Click to expand...
Click to collapse
The latest ota blocks the use of sp flash tool. And the kernel exploit used previouls. But now there is new exploit. But you cannot boot so that is mutt point now
ismailf007 said:
I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone.
Click to expand...
Click to collapse
Did you only format the data partition or whole device.?
ismailf007 said:
I am trying to install twrp but when I power on my device it is stuck on the boot loading screen.
Click to expand...
Click to collapse
This confuses me. You just said you had twrp already. Now you have trouble to I stall it.
ismailf007 said:
I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
Click to expand...
Click to collapse
Did you use / try volume up?
ismailf007 said:
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Click to expand...
Click to collapse
From what you say.
1. You had working phone with SU root.
2. You have twrp installed
3. You wiped / formated with twrp
4. You now only boot to a logo screen. No recovery, or bootloader?
WARNING: DO THIS AT YOUR OWN RISK !!!!
I AM NOT RESPONSIBLE IF YOU START CRYING INTO YOUR BRICKED TABLET
This guide is only for devices with "OEM Unlocking" option greyed out !!!
Others can follow the simpler procedure mentioned in the TWRP thread...
Prerequisites:
QDLoader_HS_USB_Driver (Google it and find)
Hex Editor (eg. HxD)
PC and some brain to understand....
Procedure:
Install the drivers and hex editor.
Clone this repo to PC - https://github.com/Naveen3Singh/BLUnlocker (Thanks to the dev )
Extract the firehose file from stock rom. (eg. "prog_emmc_firehose_8917_ddr.mbn" for TB-X304)
Boot into edl mode using key combo
or using adb
Code:
adb reboot edl
Check the port number in device manager and run " dump_devinfo.bat ".
Mention port number and full path to "*.mbn" file (eg. D:\where\every\it\is\prog_emmc_firehose_8917_ddr.mbn)
A file named " devinfo.img " will be dumped to the working dir. Edit it using an HEX editor as shown below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Save the devinfo.img after editing and run " unlock.bat "
Reboot after success message.
Voila !! You have Successful unlocked the bootloader. Reboot to system by holding the power button.
EDIT (13/01/2020): After unlocking bootloader and restarting, if it asks for password, Reboot to recovery and format data...
Flash TWRP and Enjoy rooting...
PS: The same procedure can be done using QFIL tools (QPST)
Attached:
Firehose file of TB-X304F and TB-X304L (DONT USE ON OTHER DEVICES!!!)
Credits:
Thanks to the dev who wrote the code ( https://github.com/Naveen3Singh )
@hk96 (Myself)
Hit thanks if this helped....
Reserved !!!
Thank you very much! It worked perfectly!
Firehose file for X304L if anyone needs it
Hb20032003 said:
Thank you very much! It worked perfectly!
Click to expand...
Click to collapse
Great! I also have this problem...
Does unlocking in this way factory resets the tablet?
Is the "firehose" file version sensitive (i.e., if I use the S001016 file in a S001014 TB-X304F will I have any kind of trouble?)
Thanks!
njascgil said:
Great! I also have this problem...
Does unlocking in this way factory resets the tablet?
Is the "firehose" file version sensitive (i.e., if I use the S001016 file in a S001014 TB-X304F will I have any kind of trouble?)
Thanks!
Click to expand...
Click to collapse
After unlocking, when u Boot into system it asks for a password, even if u didn't set one to start with (atleast in my case).
So you need Boot into recovery and wipe data.
Short answer: yes, factory reset is necessary.
Regarding file version, I hav no idea... May be u can give it a try...
Hb20032003 said:
Firehose file for X304L if anyone needs it
Click to expand...
Click to collapse
Thanks...
Let me add this to OP, so that it is easier for others.
Can you please make a video tutorial? i am new to rooting and am unable to understand the instructions properly.
Chhayank_Sharma said:
Can you please make a video tutorial? i am new to rooting and am unable to understand the instructions properly.
Click to expand...
Click to collapse
May do it when i find time....
But there are many videos on the same procedure for other Qcom phones, you can get some hint from that.
If you are very new to this, i suggest you not to do, unless your are confident.
hk96 said:
May do it when i find time....
But there are many videos on the same procedure for other Qcom phones, you can get some hint from that.
If you are very new to this, i suggest you not to do, unless your are confident.
Click to expand...
Click to collapse
ok thanks.
hk96 said:
Regarding file version, I hav no idea... May be u can give it a try...
Click to expand...
Click to collapse
I was going to try it, but it's my daughter's tablet and she didn't let me do it... She is afraid of loosing some games' progress...
Nothing work for me
Eagle-no1 said:
Nothing work for me
Click to expand...
Click to collapse
May be you would have missed something....
This seems to work for most people.
hk96 said:
May be you would have missed something....
This seems to work for most people.
Click to expand...
Click to collapse
I got to work now, I had an old bad cable in use. Thank you.
hk96 said:
PS: The same procedure can be done using QFIL tools (QPST)
Click to expand...
Click to collapse
How? I watched a video and I can load the mbn but I don't know what to put in the xml thing box. I tried doing the method steps but it says Failed to write hello response back to device Did not receive Sahara hello packet from device
Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.
Jakeup96 said:
Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.
Click to expand...
Click to collapse
could you explain how you did it pleasssee
Jakeup96 said:
Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.
Click to expand...
Click to collapse
Haha... Everything happens gradually...
rustyrust said:
could you explain how you did it pleasssee
Click to expand...
Click to collapse
I think, the instructions are crisp and clear as possible...
Can u tell where u got stuck ??
Work! You're GENIUS
hello,
I already root some device but here I'm stuck because I don't find the port number in device manager :-( drivers installed and "lenovo tab4 10" displayed in device manager. in properties I have : port_#0002.hub_#0005
I tried use 0002 or 0005 as port number but the .bat script failed each time. do I have correct port number ?
[EDIT] I have "failed to write hello response back to device" message and my tablet is in FFBM Mode.
[EDIT] in FFBM mode, my device is recognized in device manager (but i'm not sure to find the correct port and the script don't work) and in FastBoot Mode (first menu), my device seems to be not recognized in device manager. I guess that the script must be launched in this mode but I miss a driver. I install "adb drivers" + QDLoader-HS-USB_Driver_64bit_Setup drivers. What do I miss ?
To start this journal I will begin by stating, I am not actually sure if it will be possible to finish this journal; from what I have read there can be quite a number of obstacles with international versions of the OPPO, some of which can be quite troublesome, but I thought it would be an interesting and hopefully helpful (for my self and anyone else wanting to do the same) way of going through the process with such a modern device.
The device arrives tomorrow, I wanted to get the initial post in without knowing precise details about the device.
I will update this primary post with the journal entries and post into the main thread when I update it going forwards
-- Entry 1 29/01/2022 00:21 (Dellivery today at some point!)
So far I have found out that cpw means car phone warehouse, which used(still is?) a store in the uk, 'EE' a network provider in the UK releases of the Oppo x3 find pro are apparently identical to releases from this store.
I have asked the user who informed me of this if they could possible put any information they are aware of within this thread.
Also, I will be doing the unboxing and initial looking at what it is via youtube I hope this is ok? I could not see a way to embed video onto this platform!
-- Entry 2 29/01/2022 10:53 (Delivery)
This is just a few images of the arrived device, simply unboxed and put on charge nothing has been set on the device what so ever.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also note that this image showing the build number is by @alvydas it is not from my device yet! just some more information to add to the journal, this is believed to be the same as mine should show later on when I decide to video/start the phone up
Also for note the CPH (Possible related to CarPhoneWarehouse) prefix in the build number)
-- Entry 3 29/01/2022 13:11 (Turning on, Bootloader unlock, USB Debugging enabled)
Youtube video:
- May still be processing the HD version in google HQ!
-- Entry 4 30/01/2022 10:53 (Getting sorted)
Ok so we can't root it and we can't change the boot laoder .... however we can get novo launcher to start by default! The pro version at least!
Not exactly an amazing feat but hey its progress, I also removed the gmail mail application as I preffer outlook (mainly because I have 3 email accounts):
And boy .... you can really remove everything including:
130|OP4F57L1:/ $ pm uninstall --user 0 com.oppo.launcher
The coloros launcher its self X_X, so it seems you cannot get root, but there is no protected package, you can remove ANYTHING.
so this bodes the question .... other than wanting lineage OS of course, how thin can we get it ....
-- Entry 3 10/02/2022 10:53 (Hackery and cleaning)
.... So there is no fastboot on the international model, it is simply not there I even got EE them self to confirm this.
However, I have made some progress in discovering a way to get to the qualcomm flashable download mode, that is it will show up as a:
One of those (if you have the Qualcomm drivers installed), some information I put in the forum about this mode was this:
1) Turn the phone off (shutdown)
2) Hold the power button and the Vol up/down (I Forget which) down all the way through the phone starting, you will feel a little Bzzzzz
3) you will be presented with a menu probably in chinese, this is because you held down the power button and it auto selected the first language (its not a biggie), just press the back touch screen button in the top left <--
4) Select english (or chinese if you preffer!)
5) you will be presented with a menu that has 3 options, Format, Reboot, .... something else ...
6) Select none of the options! look to the bottom of the screen you will see a version mine was v12 o3 v1.2 - double tap this
7) you will get a warning you are entering 'customer service mode', and wallah .... you will get the device show up in device manager.
I was going to shoot a video of this, I still might! but its rather redundant at this point as I am now at a brick wall, I need to figure out how to deal with this mode, can I flash something to it .... how?
I am scrubbing the phone of all the bloatware I can and to be honest I have it pretty damn clean .... but still the fastmode is elusive and what else could be loaded onto this lovely phone.
Entry 1 added - nothing really important
Entry 2 added, initial unboxing simply for charging, video to come soon: looking for details!
The CPW in the build number is more of a guess than anything else we all could be wrong
alvydasd2 said:
The CPW in the build number is more of a guess than anything else we all could be wrong
Click to expand...
Click to collapse
@alvydasd2 Soon see! I hope you do not mind but I included your image in the journal at the top.
PaulGWebster said:
@alvydasd2 Soon see! I hope you do not mind but I included your image in the journal at the top.
Click to expand...
Click to collapse
Yh that's fine
Entry 3 uploaded, many thanks @alvydasd2 We do have slightly different builds it seems!
So now next up I believe its rooting the phone should be fun, also I beleive there is a way to root a phone but hide it from applications like paypal ... would love to find more out on this
Also have to figure out if all the fancy camera things will work with a custom rom, such as the microscope mode and all the advanced functionalities
Maybe the best initial tangent is to simply root the phone and remove any bloatware as well as installing novolauncher, followed by re-rooting it
That way I will not lose the ability to use the special camera functions and in turn still receive updates, I believe I can actually freeze certain packages too so they are effectively immutable, so they show up but can never run or be changed ... hmmm
PaulGWebster said:
So now next up I believe its rooting the phone should be fun, also I beleive there is a way to root a phone but hide it from applications like paypal ... would love to find more out on this
Click to expand...
Click to collapse
Rooting ain't gonna be easy on this phone that's if you can unlock the bootloader which is pretty much impossible unless you have a Chinese variant of the phone or somehow figure out a way to root it without unlocking the bootloader would be a miracle
alvydasd2 said:
Rooting ain't gonna be easy on this phone that's if you can unlock the bootloader which is pretty much impossible unless you have a Chinese variant of the phone or somehow figure out a way to root it without unlocking the bootloader would be a miracle
Click to expand...
Click to collapse
Check the youtube video, I appear to have lol ... though I did notice that going into the recovery menu is all in chinese ... so I assume its the chinese version:
The only problem being ... I have no idea idea what this menu says -_-
I guess that is tomorrows episode though, connecting it via ADB+TWRP
Usually first thing when you open recovery is choosing a language idk why English wasn't there and btw the difference between the builds is you're running lower firmware so if you try to update it you should get the same build number as me and if u had the Chinese version your model would have been PEEM00 or something like that
alvydasd2 said:
Usually first thing when you open recovery is choosing a language idk why English wasn't there and btw the difference between the builds is you're running lower firmware so if you try to update it you should get the same build number as me and if u had the Chinese version your model would have been PEEM00 or something like that
Click to expand...
Click to collapse
ah ha I held the button down to long it auto selected chinese somehow I pressed back and got the recovery options ... not seeing TWRP though ... and when I do a TWP fastboot it does not boot into the bootloader...
The OEM Bootloader though is saying its unlocked in dev options
PaulGWebster said:
ah ha I held the button down to long it auto selected chinese somehow I pressed back and got the recovery options ... not seeing TWRP though ... and when I do a TWP fastboot it does not boot into the bootloader...
The OEM Bootloader though is saying its unlocked in dev options
Click to expand...
Click to collapse
Oppo has a weird bootloader cuz it can only be unlocked with an app that only works on Chinese version and to access fastboot u need a unlocked bootloader
just read this .... so there is no way to even fastboot the device https://forum.xda-developers.com/t/...access-for-oppo-phones-starting-2016.3348114/
I wonder if you could flash on the chinese version of the firmware
it seems that the device is really a 'realme gt 5g' .... trying to verify this
PaulGWebster said:
it seems that the device is really a 'realme gt 5g' .... trying to verify this
Click to expand...
Click to collapse
It's not -_-
Hi
I bought a new OnePlus 10 PRO from Aliexpress. Its a CH version that the seller installed on it a global rom.
In the first setup of the phone, When I get to setting the fingerprint, I am unable to set it. I get the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried updating the phone, I tried factory reset... its always the same.
Any idea?
Thanks !
Are you sure that he installed the global rom? With model is yours NE2213 ? I bought from them also but I don't have this issue.
Anyway, you can try to use Oxygen Updater, to check if there is an update for your device or since your device is reseted, you can install ColorOS back
Hi,
I am on NE2215. Using Oxygen Updater I see that I have the most up to date version.
Not sure exactly how to install ColorOS.. I do want to have the regular OS that I would have as if I bought the global version (which i guess this is what the global rom mean..)
Right, I agree with you. I recommended to install the coloros just to check if it's a compability issue.
You can try to reinstall you version and see what happens, just download it and flash it again.
ok, and now for someone that have no idea how to do it?
If yours is NE2215 A13 you can download the ota file from this link: https://android.googleapis.com/packages/ota-api/package/7548d30abac02bde85a403bcc3a218df868e1910.zip
Then put it in your phone root and from your device Settings -> About the device -> Click on the option to check for the update -> 3 dots menu -> local installation and chose this package. It will start the installation.
Thank you for your help !
Downloaded and copied into my device files.
However - When I go to "About device" and click on the "up to date" button to search for updates, it just tells me I have no updates and i see no 3 dots to go for local installation:
What am I missing?
I think it's obvious that something went wrong during the region change, this issue was prevalent on the 8 pro and was extremely difficult to fix.
Check out the 8 pro threads you'll be sure to see it. It's a partition iirc and if it's borked then it simply will not work..
I can't remember the name of it off hand but have a look and I'm sure you can get an idea of what may be wrong, specifically that partition.
Overall it's difficult to say as you've got a region changed phone, have you asked the seller what they did? If it is indeed as difficult as it was on the 8 pro to fix and seeing as you may be the only person experiencing this (far as I know) then I'd consider returning it.
You could re-flash the entire OS via fastboot enhance but that would also bring with it inherent problem's, if it's new then I guess the question you need to ask yourself is it worth it?
Did you save much money getting that converted variant?
dkaro said:
Thank you for your help !
Downloaded and copied into my device files.
However - When I go to "About device" and click on the "up to date" button to search for updates, it just tells me I have no updates and i see no 3 dots to go for local installation:
View attachment 5624305
What am I missing?
Click to expand...
Click to collapse
This page is from android play services. You need to click on the first banner
@dladz TBH I bought it for around 70% of the price I would pay locally.. So yea, it was much cheaper. I also had before OP9 global rom and had no issues with it.
Maybe indeed as last step its worth trying to reinstall everything again.. I'm just not sure how to do it. I cannot find the local upgrade option as advised above, and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
@zopostyle I did click on that banner you're showing and I got to the page I showed you before..
I'm clueless
If that is the page showing I'm assuming you're on a gsi ROM and not oxygen os.
Now it's better to reinstall OxygenOS completely because it doesn't seem to be the ROM you're running.
Search here on xda to unlock your bootloader and then you need to find the zip with the full ROM for you device and install it from fastboot as mentioned.
OK, i'm trying to unlock my bootloader but as I mentioned:
dkaro said:
and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
Click to expand...
Click to collapse
Any idea what am I doing wrong?
I tried several tutorials online and so far I found no tutorial that will actually give me step by step that each step is actually working..
Maybe it's missing the drivers. Try this https://gsmusbdriver.com/oneplus-10-pro
dkaro said:
@dladz TBH I bought it for around 70% of the price I would pay locally.. So yea, it was much cheaper. I also had before OP9 global rom and had no issues with it.
Maybe indeed as last step its worth trying to reinstall everything again.. I'm just not sure how to do it. I cannot find the local upgrade option as advised above, and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
@zopostyle I did click on that banner you're showing and I got to the page I showed you before..
I'm clueless
Click to expand...
Click to collapse
I feel you buddy.
You can use the app in my Magisk guide to do local installs.
Unlocking the bootloader you need to type fastboot flashing unlock
I haven't had to change region myself, but I did make a thread for someone else where the process was listed, think I called it changing Chinese firmware iirc.
If it's just a case of a re-flash of the firmware you're on, it's not that difficult.
Just use oxygen updater and grab the full firmware then do the local update using the app I mentioned above (listed in my Magisk/root guide)
I've never done this when not having the bootloader unlocked personally, but you can unlock and that'll wipe your phone with the recovery already on your device.
Only issue I have going down these routes is what else is missing? Do any of these processes stand up if we can't rely on the integrity of the OS that someone has put on and made a balls of it?
Sorry I know you may not agree but 30% is a small price to pay to avoid a brick and bring stability..
But that's me
zopostyle said:
Right, I agree with you. I recommended to install the coloros just to check if it's a compability issue.
You can try to reinstall you version and see what happens, just download it and flash it again.
Click to expand...
Click to collapse
That is a seriously good shout and would explain the fingerprint.
Hi guys, thank you again for helping me.
I tried installing again the uSB drivers, and ran again "fastboot flashing unlock" - it still telling me:
As far as I understand I have to unlock it for next step, right? (either for resetting back to colorOS or reinstalling oxygen)
I will try later tonight the other method (this magisk thing) - is this the link you're talking about?
Can you please also give me a link to download the full most up to date global Oxygen version and the CH Color one? i'll try both
Thanks !
For OxygenOS there is no A13 full yet...so you have to download A12 from this link: https://gauss-componentotacostmanua...22/03/24/a9f9e7ec682744c2ba606a366df587ac.zip
Source: https://www.xda-developers.com/oneplus-oxygenos-12-android-12-update-tracker/#oneplus10pro
The chinese one is hard to find, if I find it I post the link here...
Also this thread might help you: https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585
zopostyle said:
For OxygenOS there is no A13 full yet...so you have to download A12 from this link: https://gauss-componentotacostmanua...22/03/24/a9f9e7ec682744c2ba606a366df587ac.zip
Source: https://www.xda-developers.com/oneplus-oxygenos-12-android-12-update-tracker/#oneplus10pro
The chinese one is hard to find, if I find it I post the link here...
Also this thread might help you: https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585
Click to expand...
Click to collapse
Really is odd about them not being full... They're massive compared to conventional incremental updates. 4.05GB that's a hell of an incremental.
Haven't had to do it myself and it's sightly off topic but is the full version you'd use to recover a phone albeit without a functional MSM?
So fastboot flashing?
Cheers
Hi again,
So, i'm trying to follow the tutorial here. I got stuck already in the first step - I cannot extract the boot file using Fastboot Enhance:
This is although in this link I have downloaded a full version (EU version (NE2213_11.A.13)).
What should I do next please?
dkaro said:
Hi again,
So, i'm trying to follow the tutorial here. I got stuck already in the first step - I cannot extract the boot file using Fastboot Enhance:
View attachment 5624521
This is although in this link I have downloaded a full version (EU version (NE2213_11.A.13)).
What should I do next please?
Click to expand...
Click to collapse
As @zopostyle said earlier.. you'd need to use 12 mate. As that's the only full version available...13 won't cut it...you can extract the images using the button that says allow incremental, that's useful for extracting boot images for rooting.
But there's a reason why that's there, it's so you don't go ahead and flash it.... According to @zopostyle 12 is the only full version so that's what you would need.
Again I've not done this myself so perhaps wait for someone else to chime in what to do next.