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

[Q] where to get signed images?

Hi,
As I believe I need to reflash my chromecast using the original firmware, does anyone know where I can get it from?
(If your interested in why, please see below.)
I seem to have a bricked Chromecast that I'm trying to revive (black screen after the booting chrome logo),
I have soldered in the serial port and it seems to boot the normal image ok (see bottom for dump), I have tried both the normal and the recovery image, it performs the recovery okay, however the normal boot after recovery yields the same results.
Therefore I would consider the next step to reflash it, however it refuses to flash using the GTV released firmware, because the existing firmware is to new to allow for the exploit, I therefore believe that i need a current firmware which is signed by google to attempt recovery of the chromecast, I spoke to google about it and I was welcome to sent it back and get a replacement, however as I'm in Europe, it would be cheaper to just buy a new one, than to pay the postage.
P.S. I posted this in a non-QA forum, under the assumption that links would be of general interest to chromecast developer community, and therefore would be easier to find here, if moderators disagree, I apologize for the inconvenience of moving this post.
Normal boot:
s_init start. boot_strap=0x00000080 (source=NAND), boot_state=0x0
PG868: leakage=192 vcore=11 sysctl=59
Customer key found, loading customer key...
Loading Secure Customer Key Store is finished
Loading Secure Customer Key Store is finished
Finish loading Customer Key store
bootloader image verified, start...
eureka-b3 BG2CD [Aug 5 2013 10:54:27] ver:f07e92b-dirty
OTP s0x000000FF lkg curr=192 mAnd_randomizer_init_by_flash_type(chip_id = 0x2C48044AA500): !!! RANDOMIZED !!!
[FASTLOGO] init.
[FASTLOGO] Set CPCB1 output reso 8.[SHOWLOGO] start
showlogo_init_irq, Enable IRQ_dHubIntrAvio0(0x20) for cpu 0
[FASTLOGO] done.
fts: v94 loaded from 0x00174000
[SHOWLOGO] stopped
Boot normal GTV image
fts: record v95 commited @ 0x00178000
Uncompressing Linux... done, booting the kernel.
Click to expand...
Click to collapse

bse10093 said:
Hi,
As I believe I need to reflash my chromecast using the original firmware, does anyone know where I can get it from?
(If your interested in why, please see below.)
I seem to have a bricked Chromecast that I'm trying to revive (black screen after the booting chrome logo),
I have soldered in the serial port and it seems to boot the normal image ok (see bottom for dump), I have tried both the normal and the recovery image, it performs the recovery okay, however the normal boot after recovery yields the same results.
Therefore I would consider the next step to reflash it, however it refuses to flash using the GTV released firmware, because the existing firmware is to new to allow for the exploit, I therefore believe that i need a current firmware which is signed by google to attempt recovery of the chromecast, I spoke to google about it and I was welcome to sent it back and get a replacement, however as I'm in Europe, it would be cheaper to just buy a new one, than to pay the postage.
P.S. I posted this in a non-QA forum, under the assumption that links would be of general interest to chromecast developer community, and therefore would be easier to find here, if moderators disagree, I apologize for the inconvenience of moving this post.
Normal boot:
Click to expand...
Click to collapse
If you had the exploitable bootloader, I would refer you to my thread I made awhile back about debricking, but if yours is updated, I think all you can really do is send it back to google, or buy a new one. To my knowledge, there has been no leak of an official signed USB image.
What you can try though is booting the chromecast into recovery (no idea how you can do that if its "bricked"), and have a jump drive with one of the official OTA Zips on it, named ota.zip. The chromecast recovery, if unable to find a update at /data/, will check an external jump drive.
Here is the link for the Official 13300 update. http://dl.google.com/googletv-eurek....1f63ef63d1f43c6222116806e5bea38a47e9f124.zip

tried recovery, but no luck
Thanks for your suggestions, I've tried to see if I can get it to load the software either by corrupting the boot (touching the memmory without the shield after a few tries seems to be enought to cause corruption and thereby make it try to boot from usb, however seems to fail locating the image it may however just be a matter of me having to put it in there in a certain way.
The device seems to have bricked in a weird way, that is the recovery process seems to run without error and so does the normal boot process until the very end when it is supposed to switch from the spinning chrome logo into the chromecast desktop, it just switches to the black screen.
I was able to start the recovery, but I assume that it must have an existing ota.zip in /data/, as it doesn't seem to check the jump drive.
ddggttff3 said:
If you had the exploitable bootloader, I would refer you to my thread I made awhile back about debricking, but if yours is updated, I think all you can really do is send it back to google, or buy a new one. To my knowledge, there has been no leak of an official update.
What you can try though is booting the chromecast into recovery (no idea how you can do that if its "bricked"), and have a jump drive with one of the official OTA Zips on it, named ota.zip. The chromecast recovery, if unable to find a update at /data/, will check an external jump drive.
Click to expand...
Click to collapse

Have you tried doing a factory reset on the chromecast? by button, or the setup application?

bse10093 said:
Thanks for your suggestions, I've tried to see if I can get it to load the software either by corrupting the boot (touching the memmory without the shield after a few tries seems to be enought to cause corruption and thereby make it try to boot from usb, however seems to fail locating the image it may however just be a matter of me having to put it in there in a certain way.
The device seems to have bricked in a weird way, that is the recovery process seems to run without error and so does the normal boot process until the very end when it is supposed to switch from the spinning chrome logo into the chromecast desktop, it just switches to the black screen.
I was able to start the recovery, but I assume that it must have an existing ota.zip in /data/, as it doesn't seem to check the jump drive.
Click to expand...
Click to collapse
I believe it will try to install a file named ota.zip on the root of a flash drive if it doesnt find an ota on internal storage.
{
"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"
}

factory default
ddggttff3 said:
Have you tried doing a factory reset on the chromecast? by button, or the setup application?
Click to expand...
Click to collapse
Yes I've tried it and it runs without errors, reboots however when back in normal boot mode it still shows the black screen instead of chromecast desktop.
P.S. maybe I should mention that the chromecast ad-hoc network also comes up, unfortunately though that doesn't seem to help.

doesn't seem to activate usb key
tvall said:
I believe it will try to install a file named ota.zip on the root of a flash drive if it doesnt find an ota on internal storage.
Click to expand...
Click to collapse
I tried renaming, however when starting recovery with the usb key containing the official 13300 renamed as ota.zip, it never has any disk activity on the usb key, however I can verify that it can read the key from the bootloader as it detect the key, but fails the signing step

[TUTORIAL] How to downgrade to KitKat permanent (NO root!)

I thought I should share my findings regarding the downgrade process.
It's a long tutorial, but I listed every step for newbies too.
Biggest issue I had with it - is that the phone constantly downloaded the LL update, no matter what. So here is the solution:
I have used my phone with this setup for the past few days, and it did not download the LL update.
Now I can use my phone on trip, during work, and only lose a few %. Back with LL I lost all my battery even with a few hours of use.
The battery life is pure GODLY now.
Downgrading does NOT trip Knox!
Preparation...
- Download ODIN 3.09 and the latest KitKat firmware for your variant from Sammobile.com.
- Uncompress the firmware file.
- Do a full backup of your phone and your SD card files by copying over everything to your PC and by using Super Backup app. No promo, I just used this one and it works wonderful. (For Contacts, SMS, etc.)
Install phase ONE...
- Power off your phone.
- Enter Recovery Menu, by holding VOLUME_UP + HOME + POWER.
Once you see the Samsung logo, release Power, keep holding the other two.
An Android mascot will pop up.
- Navigate with volume keys, and power. (power is "ok", volumes are up and down.)
- Go into "Wipe Data", wipe.
- Press reboot, then turn off your device once it boots.
Install phase TWO...
- Remove your back cover, remove SD card (just in case), remove SIM card.
- Keep battery, of course (lol).
- Boot phone in DOWNLOAD mode by holding VOLUME_DOWN + HOME + POWER.
- Connect your phone to PC, launch ODIN, load the unpacked firmware with the "AP" button.
Do not touch other buttons and switches.
- Press "Start", wait until your phone reboots.
Install phase THREE...
- After your phone booted, DO NOT CONNECT TO WIFI or INSTALL YOUR SIM CARD.
- Turn off wifi, make sure it DOES NOT CONNECT and DID NOT CONNECT TO ANY WIFI NETWORK!!!
- Go into Settings -> About Phone -> Software Updates. Untick "check for updates".
- Turn off your phone.
- Add a DATA SIM CARD. That can connect to mobile networks.
- Boot phone.
- Once it is booted, you will see that the phone will check for updates.. (yeah, to hell with our settings)*
- Open the notification, and you can find an option "NEVER REMIND ME".
* If it does not check, you can do it manually BUT ONLY IF YOU HAVE A DATA SIM CARD INSTALLED!
Then you can see what update you have, and whether you want to download it. Some people reported there are patches for KitKat on some regions.
DONE. You just outsmarted the evil Samsung. Good job.
- If you have your sd card installed, everything in place, you can now connect to wifi.
- Install/recover stuff, set up things, etc. You are good to go.
Ps.: If you are a Samsung employee, please, don't screw us over by force shipping some sneaky OTA to our devices. We do like to have choice what / which version we run, etc. Forcing crap down our throats is not really a nice way to treat customers.

... Reserved ...

h8Aramex said:
I thought I should share my findings regarding the downgrade process.
It's a long tutorial, but I listed every step for newbies too.
Biggest issue I had with it - is that the phone constantly downloaded the LL update, no matter what. So here is the solution:
I have used my phone with this setup for the past few days, and it did not download the LL update.
Now I can use my phone on trip, during work, and only lose a few %. Back with LL I lost all my battery even with a few hours of use.
The battery life is pure GODLY now.
Downgrading does NOT trip Knox!
Preparation...
- Download ODIN 3.09 and the latest KitKat firmware for your variant from Sammobile.com.
- Uncompress the firmware file.
- Do a full backup of your phone and your SD card files by copying over everything to your PC and by using Super Backup app. No promo, I just used this one and it works wonderful. (For Contacts, SMS, etc.)
Install phase ONE...
- Power off your phone.
- Enter Recovery Menu, by holding VOLUME_UP + HOME + POWER.
Once you see the Samsung logo, release Power, keep holding the other two.
An Android mascot will pop up.
- Navigate with volume keys, and power. (power is "ok", volumes are up and down.)
- Go into "Wipe Data", wipe.
- Press reboot, then turn off your device once it boots.
Install phase TWO...
- Remove your back cover, remove SD card (just in case), remove SIM card.
- Keep battery, of course (lol).
- Boot phone in DOWNLOAD mode by holding VOLUME_DOWN + HOME + POWER.
- Connect your phone to PC, launch ODIN, load the unpacked firmware with the "AP" button.
Do not touch other buttons and switches.
- Press "Start", wait until your phone reboots.
Install phase THREE...
- After your phone booted, DO NOT CONNECT TO WIFI or INSTALL YOUR SIM CARD.
- Turn off wifi, make sure it DOES NOT CONNECT and DID NOT CONNECT TO ANY WIFI NETWORK!!!
- Go into Settings -> About Phone -> Software Updates. Untick "check for updates".
- Turn off your phone.
- Add a DATA SIM CARD. That can connect to mobile networks.
- Boot phone.
- Once it is booted, you will see that the phone will check for updates.. (yeah, to hell with our settings)
- Open the notification, and you can find an option "NEVER REMIND ME".
DONE. You just outsmarted the evil Samsung. Good job.
- If you have your sd card installed, everything in place, you can now connect to wifi.
- Install/recover stuff, set up things, etc. You are good to go.
Ps.: If you are a Samsung employee, please, don't screw us over by force shipping some sneaky OTA to our devices. We do like to have choice what / which version we run, etc. Forcing crap down our throats is not really a nice way to treat customers.
Click to expand...
Click to collapse
Very well explained. I will keep this in mind if Lollipop doesn't start to get any better in the next update... ARG SAMMY WHY DID YOU DO THIS!

good write up. In addition, in your "Install phase THREE..." go to settings>applications manager> disable the "software update". - the one with green icon... this will stop the phone from upgrading to LP.. and you can skip the last part of your tutorial.....
{
"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"
}

xdm9mm said:
good write up....
Click to expand...
Click to collapse
I tried this one, but the update still showed up.
The only way was for me, is to tap on that "never remind me again" thing.
Oh well, if you had luck this way, that's fine too (at least we have a workaround handy if the original tutorial does not work for someone.)
Ps.: I hope the 5.1. update will fix all the issues (especially battery wise).
Though... the S6 5.1 update was a let down.

Perfect tutorial man for those beginners. But I thought you might want to add in one thing. When you originally flash KK there will be a small 100+MB update that needs to be done. As it was said in the XDA TV video its for a battery issue. Once that downloads and reboots to install, go right back into the Settings->About Phone->Software updates and uncheck auto updates.

Well. I was really tired when I read your reply and I could not remember if I ever updated adter the flash. Turns out I did, and now I have L coming down once again. Oh my.
Did a Nova backup, Super Backup, and I will reflash on the weekend. And now I will have to charge my power bank, and prepare a mobile charging cable too. Oh good times...

h8Aramex said:
Well. I was really tired when I read your reply and I could not remember if I ever updated adter the flash. Turns out I did, and now I have L coming down once again. Oh my.
Did a Nova backup, Super Backup, and I will reflash on the weekend. And now I will have to charge my power bank, and prepare a mobile charging cable too. Oh good times...
Click to expand...
Click to collapse
Sorry about that, I know the feeling, I did that a few weeks ago myself. Hoping there was a 5.1.1 update, But turns out I couldn't dismiss the update once it checked.

Guys 'coming stupid question'
If I want to downgrade ti kk do I nedd zo check or unchek re-partition? And what about Bootloader?
Thanks..My lolipop have too much lags and battery drop too fast...

Jovan1997 said:
Guys 'coming stupid question'
If I want to downgrade ti kk do I nedd zo check or unchek re-partition? And what about Bootloader?
Thanks..My lolipop have too much lags and battery drop too fast...
Click to expand...
Click to collapse
I just do a factory reset in L, then keep the stock options on ODIN. That worked for me.

cash2387 said:
Perfect tutorial man for those beginners. But I thought you might want to add in one thing. When you originally flash KK there will be a small 100+MB update that needs to be done. As it was said in the XDA TV video its for a battery issue. Once that downloads and reboots to install, go right back into the Settings->About Phone->Software updates and uncheck auto updates.
Click to expand...
Click to collapse
Ok, so since I had to reinstall the phone, I tried what you said.
Well, I only get the L update, after it checks for updates... No small update or anything.
I used this firmware: http://www.sammobile.com/firmwares/download/44754/N910CXXU1BOC3_N910COXX1BOC1_XEH/
N910CXXU1ANK5_N910COXX1ANK2_N910CXXU1ANK5_HOME.tar.md5
Maybe some regions do have small patches for battery issues (even on Kitkat)... or some regions don't have this "latest KK" as md5 file.

Could be the difference in versions your right.I used this one to go back to 4.4.4. It's the AOA1 build for my carrier
http://www.sammobile.com/firmwares/download/42501/N910W8VLU1AOA1_N910W8OYA1AOA1_ESK/

I saw someone else post on another thread that you can't downgrade from BOF5.
This is on Sprint.
Is that true?

ucallmebobby said:
I saw someone else post on another thread that you can't downgrade from BOF5.
This is on Sprint.
Is that true?
Click to expand...
Click to collapse
Yes, I have read the Sprint forum (I was searching for something else on Google), and some people did complain about that.
It's the bootloader or something.
Well, I am pretty sure it's possible to downgrade... somehow.
(The S4 Mini got the same problem. Once you are on 4.4, you cannot downgrade, it will just fail at the end of the process.
For God knows what reason.)
Uhm... make a thread in the Sprint forum, and if someone got his Knox tripped, he can try the reformat and other options to flash the KitKat rom back. (Well, even if he succeeds, we won't know whether those checkboxes will trip knox or not. There is just no way to tell. Knox should _not_ be tripped when flashing official firmwares.)

ucallmebobby said:
I saw someone else post on another thread that you can't downgrade from BOF5.
This is on Sprint.
Is that true?
Click to expand...
Click to collapse
Please dont make another thread in the Sprint forum pertaining to downgrading to KK after being on OE1 bootloader and up.
Theres too many already and its been answered numerous times when OE1 first came out. I replied to your Question in the other thread about going to KK from LP and with you being on OF5, as of right now, its not possible and Odin will prevent you from bricking your phone, giving you an auth error.

hi my friend, i am in 5.0.1 lollipop with DBT Firmware CSC N910FXXU1BOC3. It is save to downgrade without trip Knox counter? Can you tell me the kitkat version who download?

I did this to my Note Edge too....LP is garbage and people praise it? I guess newer is not better...great tutorial though. Its people like you that take the time and do things like this that makes the world a little better place.

I'm only getting a NAND write start /fail error message. My phone has been doing some goofy stuff lately. Screen locks up (blank) and nothing responds. I get the menu lights for a sec and then they are gone. Plug the phone into the pc leave it for a few minutes and everything comes back. Dunno if that is a software or hardware issue.

Hi again,
it's impossible to downgrade to 4.4.4 from 5.1.1 AFAIK (in N910C)
thanks sammy for your locked bootloaders...

amd-dude said:
I'm only getting a NAND write start /fail error message. My phone has been doing some goofy stuff lately. Screen locks up (blank) and nothing responds. I get the menu lights for a sec and then they are gone. Plug the phone into the pc leave it for a few minutes and everything comes back. Dunno if that is a software or hardware issue.
Click to expand...
Click to collapse
so, it is success to flashing the 4.4?
could you please advise about it?
thanks

[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

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