Database Develop

Fixing Data > WiFi transition and other radio problems

All credits of this solution go to user dcseek who brought us the solution for this incredible annoying bug on our phones. It's not a bug actually. I think we should blame ourselfs, because it went all wrong when flashing a baseband. Personally I think it goes wrong when flashing a baseband fails and you have to try it again (yup, smartflash) or when flashing a korean baseband.
I decided to make a thread in the Q&A section, BUT BE CAREFUL!!! this is serious business, but concerning how many noobs are facing this bug (like me), it's worth to fix it.
Before you continue, all data will be wiped! Make sure to backup anything you need!!! Including Internal SD!!!
I am NOT responsible for any damage you possible create. I don't think you can brick your phone because our phone seems to be unbrickable, but I do not want to be blamed for any damage. I just made a guide on which I spent some of my free time to make it easier. I saw a lot of questions regarding hyperterminal. All I can say is: it's quiet easy!
Q: What's the problem?
A: Data connection won't be established after let's say beïng 20 minutes or more on wifi. Airplane on/off or rebooting is the only way to fix... There are also other problems related tot this fix. No guarantee, but connection losses etc. can be fixed with this!
Q: What causes this problem?
Two possible reasons, both are beïng fixed with this procedure:
A1) imei is totally lost or reset to something like 356200000000000 Check your imei by calling *#06#
A2) Some old calibration data in the radio will cause an unknown network state, which is actually edge (the fastest GSM connection). Old radio calibration data needs to be cleared.
Q: Are there other concequences?
A1: Yes, edge won't work, so everytime edge is requested, you will get a signal drop. I'm not sure but it seems like signal loss is caused by this
A2: 3g battery drain! Radio is sending a lot of data to the provider, I logged it and I saw many old useless data passing.
How do you do it?
First you will need a stock based rom. I recommend Stefan's unbrick rom, because you can flash it over every setup. You don't have to think about what you have right now, wether you've ICS, GB, CM, Stock, it doesn't matter. It's also a very easy one-click installation.
Download here It's a customized stock rom with a lot of nice upgrades and features, but the most important thing for this tutorial is to have a rom which everyone can flash with a few clicks and also contains the hidden menu from LG.
How to install?
Unpack rom
- Unpack Stefan's 7z file with 7zip or your favourite unzipper.
- 7zip is free, click
Prepare Phone
-Power down phone
-Remove battery
-Hold VOL_DWN+VOL_UP & plug in USB connection from computer (note, your phone will not visibly respond but it will boot to APX mode quickly)
-Open Device Manager in Windows and you should see "APX Device" listed with an error, or not if you have used NVFlash before
-Right click on the APX device
-Select 'Update driver software'
-Select 'Browse my computer...'
-Select 'Let me pick...'
-Select 'Have disk'
-Browse to directory you extracted the *driver* software to above (It's included in Stefan's zip)
-Select 'NVIDIA USB Boot-recovery driver for mobile devices'
-Accept any warnings, including the big red alert (you may need to disable UAC)
-Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'
If not, uninstall the driver, reboot, rinse and repeat
Install the rom:
- Go to the folder where you unpacked Stefans rom
- Run Windows installer and follow instructions on screen, should be peace of cake for everyone!
- DONE
Now you've got a stock rom, it's time to flash your favorite baseband. Thanks to TonyP, there is a special topic about basebands. Please do not discuss here which one to choose.
TonyP's baseband tread
Flash it like normal, except for checking Erase CAL data. This time you have to enable the checkbox:
{
"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"
}
If you get an error near the end, please see TonyP's topic how to solve! Or try 10 times like me, then it works too.
Congratulations! If your imei wasn't lost yet, it is now Now we have to restore it.
Step one - download Hyperterminal:
Download free trial, works perfectly on win7 x64 and more: click
Step two - connect phone in the right way
Boot the stock rom, you can cancel setup wizzards if you want. It's not important. Go to phone and call 1809#*990# when you have an old stock rom and call 3845#*990# when you have an ICS stock rom. Thats the hidden menu. Go to port settings and select CP USB (which is Com Port USB). Just click OK without clicking the checkbox to set it on boot. Connect USB cable and wait for your PC to install the drivers.
If all goes well, go to device manager (right click computer > properties > device manager somewere over there)
Note that in my case, it's com6. In your case it could be different. Write down which com port says LGE mobile USB serial port.
Step three - configure the program:
It's easy. Start as admin. Just cancel all the phone and location setup's until you get a blank terminal screen.
Click cancel in this window:
Then click yes to continue cancelling in the popup. Then the following window will appear. Click cancel too:
Now you should see a blank window. Click in it somewhere. A new window appears where you can choose the right com port. Choose the right one, which we got from the previous step. Note that it's probably just 'com x' and NOT LGE xxx xxx (that one sounds more logic but that's another port).
Click properties and select the right options like these:
Click ok twice and you if you did it right, you see this window with the state 'connected' in the lower left corner:
Type 'AT' (without the quotes) and hit enter. Wait for response. If response is 'OK' then you did a good job! Continue to the next step. If you don't see OK try another com port until you see OK.
Now I don't have any screenshots left. But now it's peace of cake.
Type: at%imei [hit enter]
Result is your current imei. You can check it.
Now, you have to write your own imei back with the following command (imei is on a sticker under the battery):
Originally Posted by Raum1807
You should add that the IMEI number must be entered without dashes. It seems to be a common mistake.
For example if your IMEI on the sticker is 123456-78-901234-5 then the command must be at%imei=123456789012345
Just type that, like 'at%imei=123456789012345' (without quotes) and hit enter. You should get a message that your imei is written with succes. Close hyperterminal and reboot your phone.
Check your imei by calling *#06#
It should be the whole number without stripes and dashes.
After this procedure, just flash your own favourite rom back. You can do this as many times as you want. Don't be affraid to damage anything, allthough this procedure is at your own risk.

Gd job x_justin mate it will definitely benefit lots of ppl. Awesome!!:thumbup:

Tnx mate! If there are any things unclear, just tell me.

well done

thanks this seems to have done the trick, I thought it was an ics/jb on p990 problem

Aaaaaaand your thread has been added to my Baseband thread. :good:
I'm sure this will help some people to follow the procedure.
I'd love to see a couple logcat lines added which are typical for this problem.

tonyp said:
Aaaaaaand your thread has been added to my Baseband thread. :good:
I'm sure this will help some people to follow the procedure.
I'd love to see a couple logcat lines added which are typical for this problem.
Click to expand...
Click to collapse
Thanks, I updated the installation progress. Now Stefan's unbrick rom is recommended and installation instructions are included.
If someone plans to run this tutorial, please tell me if something is wrong with one of the steps.

Double post, never mind

ive often wondered about this you mentioned.
i have it go 3g for a split second then revert to H all the time. sometimes just unlocking my fone and watching it do it 3-4 times. with nothing active.. =/
hope this fix's my terrible battery life and radio drain.
thanks for your hard work.

I did this and it didn't work for my phone...
Every time it looses 3g it doesn't switch to edge, and if I ask it to go to edge it doesn't finds it. ..
I must reset my phone to get edge connection which I rarely lose...
Will my problem be related to something else?
I do have a p990 but done in Korea sold in Europe
Sent from my LG-P990 using xda app-developers app

emilic said:
I did this and it didn't work for my phone...
Every time it looses 3g it doesn't switch to edge, and if I ask it to go to edge it doesn't finds it. ..
I must reset my phone to get edge connection which I rarely lose...
Will my problem be related to something else?
I do have a p990 but done in Korea sold in Europe
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
it does say in the instructions you won't be able to get an edge connection after the fix. As the signal around here is always 3g or hspa it worked like a treat.

Re: Fixing Data > WiFi transition and other radio problems
Ok it is working now!!!!
I almost never loose signal and can paas from 3g to edge!!!
Basically I inactivated the 3g for 1 day and le my phone run on edge... then I turned on the 3g And magic!!!
Now my phone changes to edge automatically when I am in the metro, etc.
Mwahhahaha by the way I am on v30b for baseband and original Rom.
I also love my battery life
Sent from my LG-P990 using xda app-developers app

if i flash stefans rom
does that mean i'm on the new bootloader then?
and if so, how can i convert back to the old and cm10.1

i now encountered a problem during the process
i'm in hyperterminal
connected with correct settings
but i can't type anything
update:
really checked 15 times and the port was com6, then suddenly it changed to com4 and everything worked.

solved
thank you for the tutorial

Solved

Re: Fixing Data > WiFi transition and other radio problems
My Problem was not fixed by this.
When i set airplanemode and back i get no gsm connection until i restart my phone
Sent from my Nexus 7 using Tapatalk HD

Thank you, this is a very useful guide !

derEremit said:
if i flash stefans rom
does that mean i'm on the new bootloader then?
and if so, how can i convert back to the old and cm10.1
Click to expand...
Click to collapse
yes if u flash the "ICS" Stefan's ROM then you have now the NewBL "ICS Bootloader"
if you want to return to the old "GB BL"
Use this.
http://forum.xda-developers.com/showthread.php?t=2020737

i cant write AT into hyperterminal - so i dont know what to do - i did every step carefully and everything worked fine until now... pls HELP

Return MJ5 to Stock after Kingo Root

I had a heck of a dilemma this past week.
I have the N900A that I rooted using Kingo Root. No safestrap or new roms, just rooted. I obviously had the 'Custom' icon.
At day 20, my phone wouldn't charge any more or be recognized by USB. I tried everything. Factory reset, cleaned the port, cleaned the cables, new cables. Nothing helped. And it would have to be warranty exchanged through AT&T, but the warranty was voided because of root. I couldn't use Kingo to unroot, because the PC wouldn't recognize it.
I was able to find a workaround, using this:
http://forum.xda-developers.com/showthread.php?t=2559715
In fact, I really only used the third step. I didn't download or flash the rom. By some miracle, the PC would connect to the phone when it was in download mode. I used Odin to flash those four files, rebooted, and the custom icon was gone.
I'm hoping that this has removed all trace of root from the phone. The knox counter is still at zero.
I thought I would post this in case anyone else had a similar problem.

its on here too
http://forum.xda-developers.com/showthread.php?t=2559715

Return to stock
steveh_131 said:
I had a heck of a dilemma this past week.
I have the N900A that I rooted using Kingo Root. No safestrap or new roms, just rooted. I obviously had the 'Custom' icon.
At day 20, my phone wouldn't charge any more or be recognized by USB. I tried everything. Factory reset, cleaned the port, cleaned the cables, new cables. Nothing helped. And it would have to be warranty exchanged through AT&T, but the warranty was voided because of root. I couldn't use Kingo to unroot, because the PC wouldn't recognize it.
I was able to find a workaround, using this:
http://rootzwiki.com/topic/110386-return-to-stock-mj5-works/
In fact, I really only used the third step. I didn't download or flash the rom. By some miracle, the PC would connect to the phone when it was in download mode. I used Odin to flash those four files, rebooted, and the custom icon was gone.
I'm hoping that this has removed all trace of root from the phone. The knox counter is still at zero.
I thought I would post this in case anyone else had a similar problem.
Click to expand...
Click to collapse
Ok so, only doing step 3 returns the device to complete stock? I would do all the steps, but I don't really understand all of them.

asilva54 said:
its on here too
http://forum.xda-developers.com/showthread.php?t=2559715
Click to expand...
Click to collapse
Thank you, didn't see that when I searched last time.
ZOMBIExM4STER said:
Ok so, only doing step 3 returns the device to complete stock? I would do all the steps, but I don't really understand all of them.
Click to expand...
Click to collapse
I believe the rest of the steps serve to load the MJ5 version ROM onto the device (in case you've installed a newer one or something). Since I already had the stock ROM, they proved unnecessary for me. I just used Odin to flash those 4 files and since the icon disappeared, I stopped there.

steveh_131 said:
Thank you, didn't see that when I searched last time.
I believe the rest of the steps serve to load the MJ5 version ROM onto the device (in case you've installed a newer one or something). Since I already had the stock ROM, they proved unnecessary for me. I just used Odin to flash those 4 files and since the icon disappeared, I stopped there.
Click to expand...
Click to collapse
I'm on stock too, I want to do this because I'm having problems with the keyboard. The whole process is really confusing to me, do you think you can help me out?

ZOMBIExM4STER said:
I'm on stock too, I want to do this because I'm having problems with the keyboard. The whole process is really confusing to me, do you think you can help me out?
Click to expand...
Click to collapse
I will try, but I am not an expert by any means. I tinker, but hopefully these other more experienced guys will chime in if I say something incorrect.
1. Download odin from here: http://www.firmware-files.com/download.php?id=1&token=QDXtLX5r3hLhxpTt604CYR6zP9twKSmr
2. Extract odin to a folder on your computer
3. Download these four files:
http://www.firmware-files.com/download.php?id=8&token=1QMc777QYjZgceInVMKs1HlcxAWv2wrU
http://www.firmware-files.com/download.php?id=7&token=6AfQkrv4S1mjr2oClQdwHp62lZpT8BK5
http://www.firmware-files.com/download.php?id=6&token=rXopUUlOTAGrBAQfksBLl1lKu52xIjl0
http://www.firmware-files.com/download.php?id=15&token=5CYaBqGOCoJSQMM6K7WECGlLDK4NYWTT
4. These four files will be zipped. You need to extract the zip files somewhere onto your computer. Each file should have a .tar.md5 extension once you extract them.
5. Power off your phone. Put it into download mode. To do this:
Power off your phone completely'
Hold down the home button, volume down button and power button all at the same time
When the screen comes on, let go of the buttons
It will give you a warning. Press the volume up button to proceed to download (odin) mode.
6. Run the Odin3 v3.09.exe application (that you extracted in step 2)
7. Now that odin is running and hopefully connected, you need to specify the four files that you extracted to be downloaded. You should end up with a screen that looks like this:
{
"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"
}
8. Click start and let it run until it is finished. Once it is finished, hold down the power button to power off your phone then do the same to turn it back on. The custom icon should be gone.

First thing I do after rooting is Wanam and turn off the Custom - just in case something like this happens. If the phone later blows up, factory reset if possible and walk it in for an exchange. Then if, when it blows up, even Odin can't see it, there's still no lock on the screen.

Rukbat said:
First thing I do after rooting is Wanam and turn off the Custom - just in case something like this happens. If the phone later blows up, factory reset if possible and walk it in for an exchange. Then if, when it blows up, even Odin can't see it, there's still no lock on the screen.
Click to expand...
Click to collapse
Doesn't factory reset delete the Xposed framework?
With AT&T you can't do a walk-in exchange after 14 days - pretty scary to mail it in for exchange and risk a $650 charge when they discover you rooted it.
I had the icon turned off with Wanam, but it came back.

steveh_131 said:
Doesn't factory reset delete the Xposed framework?
Click to expand...
Click to collapse
I could probably write an accounting program for an agency as large as the US government (or have fixed the health insurance site - doing something for half a century does pound some knowledge into even rock hard heads like mine), but when it comes to Android, I'm one of the learners, not one of the teachers. You know the answer to this question better than I do. I'd assume it does. I've made a lot of stupid assertions over the years, so ...
I downloaded a course that I may start reading one of these days, so I might yet learn enough to write a "Hello, World" app for Android. (Programmers know what I'm talking about - the difference between being able to develop a program and being able to code something to run in a particular environment - and the only internal environment I know in Android is where the battery and cards go.)
With AT&T you can't do a walk-in exchange after 14 days
Click to expand...
Click to collapse
SSSSSSHHHHHHHH!!!!!!! You weren't supposed to tell them that. I hope they didn't read this thread, and I hope the very nice lady who gave me the phone I'm using now doesn't get into trouble. (I'm not talking about walking in and saying "I don't like this phone, may I have a different one, please?" I'm talking about walking in during the warranty period and saying "could you please make my phone work?" and being told that they'll have to give you another phone. The only thing I'd trade my N3s for is N3s with unlocked bootloaders. I just want to see something other than comets revolving around Samsung's name.)
I had the icon turned off with Wanam, but it came back.
Click to expand...
Click to collapse
Mine stayed off - for the 3 or 4 days that the hardware didn't die on me. Then ... well, maybe Samsung has a way to read melted silicon, or whatever it did to make itself electrically invisible, but I'm not going to worry about it.

Wanam will keep the icon hidden but once you factory reset the phone I believe it deletes the xposed framework and the icon comes back.
I could be wrong about that, but that is my understanding.
I don't think you'd ever fool the warranty department that way, unfortunately, which is why I used this method.
Sent from my SAMSUNG-SM-N900A using Tapatalk 2

after doing just step 3 did you run a root check to see if that was gone? also what was the state of your phone after only doing step 3....meaning custom on dl mode and lock on boot screen....just wondering cause the files are so small to think that it would completely return to stock (like day 1)

ryant100 said:
after doing just step 3 did you run a root check to see if that was gone? also what was the state of your phone after only doing step 3....meaning custom on dl mode and lock on boot screen....just wondering cause the files are so small to think that it would completely return to stock (like day 1)
Click to expand...
Click to collapse
No custom and no lock. I didn't run a root check, not even sure how.
The files are small because you're not flashing an entire ROM. My ROM was still stock.

[Help Thread] BLU R1 HD - Ask Any Question, Noob Friendly

[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 Posts​A 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

G900A Galaxy S5 Android 6.0 Odin Update Files - Without Wiping!

Using Odin files to update a Samsung AT&T model will almost always result in a factory reset being performed, and I've also seen the same thing happen when trying to update via OTA zip in Recovery. I'm providing this package for anyone still using the S5, to be able to update software without needing to do a factory reset. I have personally verified that these files will perform the update without wiping any data. These files will update you to the Build/Baseband ending in QD1, Android 6.0.
My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc.
Happy flashing!
https://www.androidfilehost.com/?fid=1899786940962576350

Worked great..Thanks! But....
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again

3rdRockfromSun said:
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again
Click to expand...
Click to collapse
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again

iBowToAndroid said:
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again
Click to expand...
Click to collapse
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?

3rdRockfromSun said:
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?
Click to expand...
Click to collapse
https://www.att.com/deviceunlock/

Thanks in advance for any help, short version at top, details below.
-- Short version:
Please help me recover my data, and phone if possible.
I need the data, esp texts and notes, for both personal (some family members have passed on) and business.
I have a new Galaxy S21 and / or PC Smart Switch ready to receive data backup if we can evacuate it from the S5.
ODIN flash seems to pass but has 'Resizing Data' fail, and phone still won't boot past AT&T logo screen.
All web searches seem to say Factory Reset is my last option, but I don't want to lose the data.
Please share ANY advice on how I can recover the data.
-- More details:
Phone = SM-G900A Samsung Galaxy S5 AT&T
Use = pristine, never rooted, modded, or unfortunately backed up
Status = will not boot, passes screen 1 'Galaxy S5', screen 2 'Samsung script', then stops on screen 3 'AT&T globe logo'
More details = Used clean for ~7 years, then on day x, saw phone automatically complete a system update (green screen, sprockets, "your phone is updating"), which was surprising as it's years after it is no longer supported by AT&T. After that update, I continued to use the phone that day, but it then rebooted automatically and stuck on the AT&T globe logo.
Attempts to fix = soft reset, battery pull, can't get into SAFE MODE, can get into and out of recovery mode, found this firmware (THANKS @iBowToAndroid), used multiple ODIN (Odin3 v3.13.3_3B_PatcheD, Odin3 v3.14.1_3B_PatcheD) to flash it (my first Android flashing experience). On flashing process, ODIN on PC shows 'PASS' and log shows "<OSM> All threads completed. (succeed 1 / failed 0)", but phone shows 'Resizing Data' failed:
"
Supported API: 3
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
-- Resizing Data...
Can't open dir '/data/user/0/com.sec.knox.bluetooth' (Permission denied)
E:failed the resizing-data
"
PFA screen shots

Martin2019 said:
Thanks in advance for any help, short version at top, details below.
Click to expand...
Click to collapse
Trying the "wipe cache partition" is the only thing I can think of

iBowToAndroid said:
Trying the "wipe cache partition" is the only thing I can think of
Click to expand...
Click to collapse
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
The string seems to indicate a 'user data' permission error?
Is there any way to debug the logic of the firmware or slog through the 'Recovery Logs' to determine and resolve the cause of the permission error?
When the problem began, I had an SD card and SIM card loaded.
I've since removed both in trying to address this, also per 'web advice'.
Any chance putting them back in helps somehow?
Any other options available via apply update from SD card or ADB?
Any way to setup the Android OS as a secondary drive to another machine to pull data out that way?
I've done similar things with Windows OS in PC environment, but I'm not seeing anyone trying that with Android.
If I am really stuck with factory reset, are there any data recovery programs I could try afterward that work with the G900A?
So far I've looked at Dr Fone, Tenorshare, EaseUS, FonePaw, and D-Back, and none seem to work with the AT&T model variant.
Maybe that's just because they don't have access to AT&T firmware available to install, but if I clear the stuck boot via FR, they then might be able to get some of my data back via drive scan - whatever data is not truly overwritten by the FR?

Martin2019 said:
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
Click to expand...
Click to collapse
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset

iBowToAndroid said:
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset
Click to expand...
Click to collapse
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.

Martin2019 said:
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.
Click to expand...
Click to collapse
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times

iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Totally agree, and totally on me for not having a backup.
I was just foolish enough to not know yet how easy it is to back up.
Give me 10 minutes of life again now in this phone, I use Smart Switch to backup, and I'm off to a new phone, or even FR on this one and reload.
Now where did I put my Delorean...

iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Have you ever tried a 'combination key' approach to get data access?
As in...
Smart Switch on PC won't connect, but ODIN does show 'Added'.
I don't understand the granular details, but hoping you might...
Could we use both Smart Switch and ODIN in some combination sequence that would allow Smart Switch to pull the data off to a Smart Switch PC backup that I could then throw onto a new phone?

When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?

iBowToAndroid said:
When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?
Click to expand...
Click to collapse
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?

Martin2019 said:
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?
Click to expand...
Click to collapse

Any 3rd party software will require ADB to be enabled. Smart Switch is the only one that *might* work just over MTP, but I'm pretty sure MTP doesn't fully load until the device is booted. Even if it did, you would likely need to allow on the popup message. Does the phone show up as a device/drive when it's plugged in while sitting on the AT&T logo?

I think you're asking "does the phone show up as a device/drive" in something like a windows file explorer, and the answer is unfortunately no, or at least not that I've found yet - I've tried several times now, and I'm still trying any combinations I can.
For now...
I can get EaseUS to show 'MTP USB device' per the pic attached in my last, but can't really get it to connect past that point, as it asks for USB Debugging, which it appears I can't do due to stuck in boot loop.
Smart Switch seems to try to connect for awhile, then says it failed to connect, so I think I'm then left with 'Samsung Smart Switch Emergency Software Recovery' (PFA).
Do you have experience using it?
Do you know if it could work to reload the firmware / OS without wiping the data?
AT&T Advanced Technical Support guy says it gives you an option to choose whether or not using it resets the phone (wipes your data), so he thinks (hopes) that would work, but he didn't sound certain at all.
I understand your point on the pop up message user prompt for File Transfer Mode. I used that mode many times in the past, so I'm hoping it might default on the phone so we wouldn't need to answer the pop up prompt to reach that status , but I'm obv not sure about that.
Per the speculation in my last, do you know of any combination approach we might use to get the desired result, like maybe... use ADB somehow to change 1 parm value to reach MTP mode, then use that progress step to enable Smart Switch to connect so we could offload the data?
Thanks again for your help

1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
2. But if the phone never shows up as a device/drive (would show up under "Portable Devices" in Windows Dev Man), then it's not loading fully - and it normally doesn't do that until it boots past the carrier splash screen.
3. Even if it did boot fully and showed up as a device/drive, the MTP pop-up prompt shows up every single time you connect the device. There's no way around that. So the device would show as empty, with no files or folders, until you tapped "Allow" on the popup.
4. No, there's nothing else you can do to turn on any other connection modes

iBowToAndroid said:
1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
Click to expand...
Click to collapse
Device Manager does show an entry for the phone connected via USB cable:
Under 'Disk Drives' as
SAMSUNG MZMTE256HMHP-000MV
Under 'Universal Serial Bus Controllers' as
SAMSUNG Mobile USB Composite Device
Please tell me that helps us somehow?

General Journal: A brand new OPPO Find X3 Pro (UK/EE) - From new to clean de-bloated android (hopefully)

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 -_-