Develop Bugs

A Few Questions Regarding Bootloader and Rooting

Hey XDA people
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I recently bought a Sony Ericsson Xperia Play R800i, running android 2.3.4 and the latest Sony apps and stuff I also know that is unlocked to any carrier. I had read some things about locked bootloaders on this phone and was interested in rooting.
Question
1. What is a locked bootloader and what does it do? Can I unlock and relock it?
2. What's the easiest way to backup everything, except games on my phone?
3. If I root will I still be able to upgrade to ICS when the time comes? If so what's the easiest method to root?
4. If I install the ICS beta, can I return to stock GB?
5. What are some benefits of rooting this phone, I know about Custom Roms and such, is there anything else?
6. Can you dual boot between to different versions of android on the phone?
I think thats it, I'm used to my cheap Huawei U8180 that I could do anything too, I just don't wanna **** something up on this one.
Thanks
Sent from my Xperia Play R800i using Tapatalk Android

1. A locked bootloader, means that you cannot flash roms using flashtool or flash kernels. You can unlock it and I think there is away to relock it. However, unlocking it voids the warranty.
2. The easiest way to backup everything is to run a NANDROID backup from recovery.
3. If you root, you will still be able to upgrade. The easiest method varies, but if you dont want to unlock your bootroader look up ZergRush.
4. If you install the ICS beta yes you can return to stock GB.
5. Rooting the phone allows you to use themes, install clockwork mod recovery, install apps to sd card and various other things.
6. You can dual boot in a sense but it is still being worked on.

XperiaPlayer said:
1. A locked bootloader, means that you cannot flash roms using flashtool or flash kernels. You can unlock it and I think there is away to relock it. However, unlocking it voids the warranty.
2. The easiest way to backup everything is to run a NANDROID backup from recovery.
3. If you root, you will still be able to upgrade. The easiest method varies, but if you dont want to unlock your bootroader look up ZergRush.
4. If you install the ICS beta yes you can return to stock GB.
5. Rooting the phone allows you to use themes, install clockwork mod recovery, install apps to sd card and various other things.
6. You can dual boot in a sense but it is still being worked on.
Click to expand...
Click to collapse
If my bootloader is locked can I install your ICX Rom via ClockworkMod recovery?
Sent from my Xperia Play R800i using Tapatalk Android

Zerosuit Connor said:
If my bootloader is locked can I install your ICX Rom via ClockworkMod recovery?
Sent from my Xperia Play R800i using Tapatalk Android
Click to expand...
Click to collapse
You can't install the ICX kernel without unlocking the bootloader, so no.
Locked cwm only works with certain stock-based roms, like T.E.A.M. or Darkforest.
To install anything else you need a cwm kernel that has been flashed with fastboot. The type you install with an app after obtaining root cannot change kernels, only the system partition.
Basically, one runs from kernel, the other runs from system.
Custom kernels can only be flashed with fastboot.
Stock kernels can be flashed with fastboot or flash mode.
You only have usable fastboot with an unlocked phone.
If you try flashing something like cyanogen with the locked recovery you'll get a boot loop.
Sent from a Galaxy far, far away

captain67 said:
You can't install the ICX kernel without unlocking the bootloader, so no.
Locked cwm only works with certain stock-based roms, like T.E.A.M. or Darkforest.
To install anything else you need a cwm kernel that has been flashed with fastboot. The type you install with an app after obtaining root cannot change kernels, only the system partition.
Basically, one runs from kernel, the other runs from system.
Custom kernels can only be flashed with fastboot.
Stock kernels can be flashed with fastboot or flash mode.
You only have usable fastboot with an unlocked phone.
If you try flashing something like cyanogen with the locked recovery you'll get a boot loop.
Sent from a Galaxy far, far away
Click to expand...
Click to collapse
What's the easiest way to unlock my bootloader? I would like it to be one of the reversible methods so if I **** it up, I can claim warranty.
Sent from my Xperia Play R800i using Tapatalk Android

Zerosuit Connor said:
What's the easiest way to unlock my bootloader? I would like it to be one of the reversible methods so if I **** it up, I can claim warranty.
Sent from my Xperia Play R800i using Tapatalk Android
Click to expand...
Click to collapse
Personally I like to use Omnius, but it can't be re-locked per se. http://forum.xda-developers.com/showthread.php?t=1134334 as you can see in that thread, it's patched to seem locked but if they try loading an unsigned image it'll still work so they would find out.
I think re-locking only truly works for the official method, which if you're carrier locked isn't possible.
Also if you use Omnius, be very careful about leaving the sticker covering the test point intact or the warranty is void.
Sent from a Galaxy far, far away

Is there anything purely software? Can the one that sony ericsson posted for their handsets be relocked?
I have no experience with testpoints and it all seems way to much of a pain in the ass.

Zerosuit Connor said:
Is there anything purely software? Can the one that sony ericsson posted for their handsets be relocked?
I have no experience with testpoints and it all seems way to much of a pain in the ass.
Click to expand...
Click to collapse
u can follow this tutorial.. working with all xperia 2011 phone
http://forum.xda-developers.com/showthread.php?t=1034087

ezadsyafiq99 said:
u can follow this tutorial.. working with all xperia 2011 phone
http://forum.xda-developers.com/showthread.php?t=1034087
Click to expand...
Click to collapse
Can I relock If i use that method?

The carrier locked plays can be done ONLY with the test point. That's it, no exceptions.
If you bought the phone full price and not carrier locked, you can use the official Sony method, which is reversible.
Unlocking your sim does not enable fastboot to use the official method so don't bother asking.
When the phone is off, hold the search button and plug it into USB. If the notification light is blue and the screen stays black, you have fastboot and can use the official method.
Sent from a Galaxy far, far away

Worked brilliantly and I am so impressed, thankyou to eeveryone. What's the best kernel for the xperia play? I have the doom kernel atm
Sent from my R800i using Tapatalk

I've been trying to unlock the bootloader on my R800i using the instructions on the sony unlockbootloader site. My phone isn't locked to any carrier, it says the bootloader is unlockable, and when I put it into fastboot mode with the search key while plugging in I get the blue light and I get a device that shows up under device manager as S1Boot Fastboot. I've installed the android sdk along with google usb driver 4.0 and the android_winusb.inf file from the site. It keeps telling me that no drivers were found when i manually try to install the driver though, also tried downloading fastboot usb drivers from a few other places (also to no avail). Keep getting the waiting for devices message without this driver being installed.
Anyone have any ideas why this driver won't install for me?
Running Windows Vista SP2 and using my SE Xperia Play R800i.
Appreciate any help.

Gjusmc said:
I've been trying to unlock the bootloader on my R800i using the instructions on the sony unlockbootloader site. My phone isn't locked to any carrier, it says the bootloader is unlockable, and when I put it into fastboot mode with the search key while plugging in I get the blue light and I get a device that shows up under device manager as S1Boot Fastboot. I've installed the android sdk along with google usb driver 4.0 and the android_winusb.inf file from the site. It keeps telling me that no drivers were found when i manually try to install the driver though, also tried downloading fastboot usb drivers from a few other places (also to no avail). Keep getting the waiting for devices message without this driver being installed.
Anyone have any ideas why this driver won't install for me?
Running Windows Vista SP2 and using my SE Xperia Play R800i.
Appreciate any help.
Click to expand...
Click to collapse
Have you installed the android dev tool, forget what it's called
Sent from my Xperia Play using Tapatalk

[Q] N7100 Emergency Calls Only

Okay my phone has been working fine till now.
My IMEI is intact still displays *#06# the correct no. It has been unlocked. I have rooted installed a custom ROM all was working okay till yesterday. When I turn the phone on emergency calls only is displayed. When I try to make a call it pops up with not registered on network. My data works okay though so I know am not blacklisted. Has anybody got a fix. Been searching but can seem to find a solution. Please help.

you have a backup of your efs folder?

Try a data clear.
Make sure you already have a backup of efs.
Sent from my GT-N7100 using xda premium

UtkarshGupta said:
Try a data clear.
Make sure you already have a backup of efs.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I have tried it already. It's seems like my phine has locked itself in emergency mode and doesnt want to come out of it
Sent from my GT-I9305 using xda app-developers app

MrCeez said:
I have tried it already. It's seems like my phine has locked itself in emergency mode and doesnt want to come out of it
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Gonna have to bump this, since I have the same issue.
Phone was working fine until I tried this rom. Now every rom I try, including flashing stock using odin, leaves the phone as "emergency calls only". I've tried different modems etc, nothing.
Current baseband N71000NEDLK1.
Even flashing the proper UK 3 network stock rom, nothing.

Have you tried with another sim card? Maybe you have a damage sim.

zabumba said:
Have you tried with another sim card? Maybe you have a damage sim.
Click to expand...
Click to collapse
Ive tried my mrs' o2 card, same issue there.
It feels like a rom has changed everything, my modem even. I've tried to flash one recommended for Three UK, but it didn't seem to stick in recovery.

X82X said:
Ive tried my mrs' o2 card, same issue there.
It feels like a rom has changed everything, my modem even. I've tried to flash one recommended for Three UK, but it didn't seem to stick in recovery.
Click to expand...
Click to collapse
Try to restore the stock Firmware or a different custom rom

aukhan said:
Try to restore the stock Firmware or a different custom rom
Click to expand...
Click to collapse
I fear for the worst. I've read a few entries from people saying when this happened to them (some never rooted or on any custom rom) they had a paperweight.
I've tried about 6 different stock roms, many custom. Many modems. Nothing will get it working.
The phone has full signal, can scan for networks, but will not allow calls or connect to data.
I've tried the sim elsewhere and it's fine.
Since this is my only means of communication, I'm extra worried.
Any help on this matter, is greatly appreciated!

X82X said:
I fear for the worst. I've read a few entries from people saying when this happened to them (some never rooted or on any custom rom) they had a paperweight.
I've tried about 6 different stock roms, many custom. Many modems. Nothing will get it working.
The phone has full signal, can scan for networks, but will not allow calls or connect to data.
I've tried the sim elsewhere and it's fine.
Since this is my only means of communication, I'm extra worried.
Any help on this matter, is greatly appreciated!
Click to expand...
Click to collapse
Is your IMEI number intact as shown on the box ?
Which device is this i mean model ?
N7100 or N7105 or some other is this a Carrier specific device ?.

aukhan said:
Is your IMEI number intact as shown on the box ?
Which device is this i mean model ?
N7100 or N7105 or some other is this a Carrier specific device ?.
Click to expand...
Click to collapse
The IMEI is 004XXX010640000 / 01
Model N7100.
{
"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"
}

X82X said:
The IMEI is 004XXX010640000 / 01
Model N7100.
Click to expand...
Click to collapse
Is IMEI matching on the box ?

aukhan said:
Is IMEI matching on the box ?
Click to expand...
Click to collapse
Sorry, I never had a box. My dad has been using it great for 6 months, I have it a day, stick a rom on it and boom. But I'm smelling something with the kernel. I changed the kernel and now there is no signal at all. I need to find the right one for this UK model.

I've got the same exact problem as well, my N7100 bought it from china ( not copy) and after install Hong Kong version of stock rom via Odin,I have the same exact problem.
1. I can search for all the available network.
2. Under settings-about-status, it shows my phone number, my carrier, HSDPA mode...all looks normal except "emergency call"
3. I tried calling the sim that was in the N7100 and text message, the line works,text message shows as delivered, but nothing turns up on the N7100.
I've tried custom,stock,per-rooted from many versions of the world but the problem is still there.

X82X said:
Sorry, I never had a box. My dad has been using it great for 6 months, I have it a day, stick a rom on it and boom. But I'm smelling something with the kernel. I changed the kernel and now there is no signal at all. I need to find the right one for this UK model.
Click to expand...
Click to collapse
i think your the victim of IMEI corrupt or EFS Folder corrupted
as the IMEI 004XXX010640000 / 01 this is what you posted it looks suspcious to me
pull the battery there is sticker match the IMEI showing on the sticker and from phone see it they matches if they dont they your in deep trouble where you may have to get it serviced
---------- Post added at 02:37 PM ---------- Previous post was at 02:36 PM ----------
pixellized said:
I've got the same exact problem as well, my N7100 bought it from china ( not copy) and after install Hong Kong version of stock rom via Odin,I have the same exact problem.
1. I can search for all the available network.
2. Under settings-about-status, it shows my phone number, my carrier, HSDPA mode...all looks normal except "emergency call"
3. I tried calling the sim that was in the N7100 and text message, the line works,text message shows as delivered, but nothing turns up on the N7100.
I've tried custom,stock,per-rooted from many versions of the world but the problem is still there.
Click to expand...
Click to collapse
suggest you to try this and check #15

aukhan said:
i think your the victim of IMEI corrupt or EFS Folder corrupted
as the IMEI 004XXX010640000 / 01 this is what you posted it looks suspcious to me
pull the battery there is sticker match the IMEI showing on the sticker and from phone see it they matches if they dont they your in deep trouble where you may have to get it serviced
Click to expand...
Click to collapse
Correct. The IMEI is totally different. But as I said, I am not going to fix it. I'll just sell it on cheap for someone else to. It's a shame and annoying that something like this can go wrong and potentially brick a phone. I know theres risks to all rooting/custom roms, which I accept, but it still doesn't stop it stinging when it does go wrong, which to my knowledge, wasn't my fault.

X82X said:
Correct. The IMEI is totally different. But as I said, I am not going to fix it. I'll just sell it on cheap for someone else to. It's a shame and annoying that something like this can go wrong and potentially brick a phone. I know theres risks to all rooting/custom roms, which I accept, but it still doesn't stop it stinging when it does go wrong, which to my knowledge, wasn't my fault.
Click to expand...
Click to collapse
always remember option number when rooting device always make a backup of Efs folder or backup you rom

aukhan said:
always remember option number when rooting device always make a backup of Efs folder or backup you rom
Click to expand...
Click to collapse
But, for me, the IMEI number is still the same as my original number,from the back of the phone sticker & also the box, could my phone's problem be any different?

pixellized said:
But, for me, the IMEI number is still the same as my original number,from the back of the phone sticker & also the box, could my phone's problem be any different?
Click to expand...
Click to collapse
First thing before you try anything else make a backup of EFS folder search for the thread you will find specific to Note 2.
then try to make a ROM backup
then Flash the stock Firmware see if this works.

X82X said:
Correct. The IMEI is totally different. But as I said, I am not going to fix it. I'll just sell it on cheap for someone else to. It's a shame and annoying that something like this can go wrong and potentially brick a phone. I know theres risks to all rooting/custom roms, which I accept, but it still doesn't stop it stinging when it does go wrong, which to my knowledge, wasn't my fault.
Click to expand...
Click to collapse
Don't be paniced mate. The problem is easy to solve. With a root explorer find the folder efs_Backup, location of the folder varies from rom to rom. If you are in a custom stock rom, you'll find it under sd card. It also may locate on root/media. Every time you flash a new rom the efs backed up automatically in zip. After finding the folder, open it, you'll find many zip files mentioned dates. Extract the one you remember when your phone was fine. Then copy the whole content of the extracted folder and paste to the root/efs.
Before pasting, erase the existing contents of the efs folder.
DONE!
Sent from my GT-N7100 using xda premium

Should we wait to see if it is rooted ?

I have in the past setup my new devices, spent hours then somebody finally roots the device.
This usually means wiping the device, unlocking the bootloader, rooting and reinstalling everything again.
It is much easier if the first thing I do is unlock the bootloader and then root.
I then set up my device, and back up everything using Titanium Backup.
What do you do keep using the old device for a few weeks and wait for news and a procedure to unlock the bootloader and root ?

AstroDigital said:
I have in the past setup my new devices, spent hours then somebody finally roots the device.
This usually means wiping the device, unlocking the bootloader, rooting and reinstalling everything again.
It is much easier if the first thing I do is unlock the bootloader and then root.
I then set up my device, and back up everything using Titanium Backup.
What do you do keep using the old device for a few weeks and wait for news and a procedure to unlock the bootloader and root ?
Click to expand...
Click to collapse
Not even ordering until I am sure that is all in place.

Can anyone buy the pixel for me and send it to me in Zimbabwe, I cannot order it for now.

I'm waiting for a method of gaining root access to be achieved before placing my order. The phone I have now (Nexus 6) still works fine so I'm in no rush. Also, I am kind of interested in seeing what kind of reviews the XL gets anyways. Mainly regarding the volume of the speaker.

cmzizi said:
Can anyone buy the pixel for me and send it to me in Zimbabwe, I cannot order it for now.
Click to expand...
Click to collapse
How do you plan on paying for it? I can bring it with me on my trip to Zimbabwe 10/17/16.

I can do payment via PayPal.
Sent from my SM-N930F using Tapatalk

You will almost certainly have root access on this device. The bootloader looks to be unlockable unless you get the Verizon branded version.
Remember, root doesn't mean supersu, or even the su binary. Root means the ability to run commands in the superuser context. You will have that at the very least. From there a new solution to give root access to normal android applications may need to be developed, but that is only a matter of time. As long as your bootloader is unlockable, you can build whatever you need into the kernel as a module, or run a service from init (like daemonsu).

grneyez said:
How do you plan on paying for it? I can bring it with me on my trip to Zimbabwe 10/17/16.
Click to expand...
Click to collapse
The phone doesnt come out until after this date. This is impossible

cmzizi said:
Can anyone buy the pixel for me and send it to me in Zimbabwe, I cannot order it for now.
Click to expand...
Click to collapse
cmzizi said:
I can do payment via PayPal.
Sent from my SM-N930F using Tapatalk
Click to expand...
Click to collapse
I'll PM you.
---------- Post added at 03:54 PM ---------- Previous post was at 03:49 PM ----------
KnownDominance said:
The phone doesnt come out until after this date. This is impossible
Click to expand...
Click to collapse
For you yes that is correct, for me I get it sooner. Thanks

tigercranestyle said:
in the past only unlocking the bootloader erased data... not the actual rooting. why not just unlock the bootloader before setting it up, continue to use the device as you please, and then just wait until a root method is released?
Click to expand...
Click to collapse
That is what I normally do...... unlock the bootloader right out of the box (it wipes the phone then before you set it up) then you have the option to root later on if you like.

ill keep my s7. the phone looks smooth And fluid but i hate the design. its also way overpriced.

How could you wait? Buy it. If for some wild reason we couldn't get root. I'm sure it would still be returnable. If you wait, the phone will already have root and a custom ROM before one ever shows up on your doorstep.lol
Sent from my Nexus 6P using XDA-Developers mobile app

{
"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"
}

charlieb620 said:
Click to expand...
Click to collapse
I don't do that.... I usually buy Verizon and purposely get at least 3 phones and return them as defective when I dont have root to my own device. Just as a little F-U to them. Then I finally hack my own phone and go with it. But I'll return as many as I can as defective first until they wise up and stop sending them to me.
You simply should not have to pay extra when hardware and software shouldn't be tied together in the first place. Why would I pay extra for an unlocked device that is exactly the same hardware as the locked one.

That is definitely the most immature thing I've heard all week.
You don't like their policies so you are 'showing them'? Give me a break. My 11 year old grew out of that behavior 5 years ago...
Sent from my Nexus 6P using Tapatalk

AstroDigital said:
I have in the past setup my new devices, spent hours then somebody finally roots the device.
This usually means wiping the device, unlocking the bootloader, rooting and reinstalling everything again.
It is much easier if the first thing I do is unlock the bootloader and then root.
I then set up my device, and back up everything using Titanium Backup.
What do you do keep using the old device for a few weeks and wait for news and a procedure to unlock the bootloader and root ?
Click to expand...
Click to collapse
Dude its not hard to completely re set your phone quit being lazy I do it like 30 + times in 2 months, and install many themes apps widgets and configurations. I also use Nova launcher back up where you just have to install widget apps etc. But re setting a phone is nothing and do not expect root on this phone. Just google search root pixel phones. Many sources say its going to be impossible. Hope you didnt get it for root purposes. lol

AstroDigital said:
I have in the past setup my new devices, spent hours then somebody finally roots the device.
This usually means wiping the device, unlocking the bootloader, rooting and reinstalling everything again.
It is much easier if the first thing I do is unlock the bootloader and then root.
I then set up my device, and back up everything using Titanium Backup.
What do you do keep using the old device for a few weeks and wait for news and a procedure to unlock the bootloader and root ?
Click to expand...
Click to collapse
I even already wait 3rd year cause I skip ugliest nexus 6p and now pixel xl which has no unlocked bootloader and no root, and on top of that it has NOT wireless charging AGAIN !!!
I'm incredibly disappointed because Pixel XL seems good even it has HUGE, gigantic bezels on top and bottom.
For now Nexus 6 is the best and hope not the last google phone.

BaconSeeds said:
Dude its not hard to completely re set your phone quit being lazy I do it like 30 + times in 2 months, and install many themes apps widgets and configurations. I also use Nova launcher back up where you just have to install widget apps etc. But re setting a phone is nothing and do not expect root on this phone. Just google search root pixel phones. Many sources say its going to be impossible. Hope you didnt get it for root purposes. lol
Click to expand...
Click to collapse
Not one source says impossible...stop spreading false propaganda, phones will be rooted within days

I can assure you this thing will be rooted, I will see to it myself

DespairFactor said:
I can assure you this thing will be rooted, I will see to it myself
Click to expand...
Click to collapse
I hope so I want it to be rooted just the articles I've read made it seem doubtful. Especially b/c I pre ordered one.

SM-G960FD Flash Stock Firmware gets stuck on recovery.img

Hello all, So I have been flashing for years but I am a complete nOOb. Ive just spent 4 hours looking around the internet and XDA for a solution to this issue... Any thoughts or help would be greatly appreciate it!
First off when I received this phone I waited the 7 days for Samsung's new security feature (I came from a S5 so this was a shock). Flashed TWRP with no issues. Proceeded over a few weeks to flash Lineage, Resurrection remix, and then tried to flash Light ROM for the s9. Had some issues with that so I flashed back to Stock Firmware no issue and have been using the past month. Now that I am not busy again I wanted to get twrp back on my phone but OEM unlock was not available. Thought that was weird seeing as the up time was well over the 168 hour marker so I decided to factory reset just to see if that would reset it. I waited the 7 days again and still wasnt there. So I wanted to Flash Stock rom again but now whenever I do it this pops up on the download screen:
sw rev. check fail (bootloader) device 2, binary 1
and Odin is stuck on the recovery.img protion.
Please let me know if you an help or if more info is needed!

Check you're not trying to downgrade the bootloader as shown here
G960FXXU2BRGA << Version 2
Check which version it says in Download mode (B:1 or B:2)
Either match it or flash a higher version

*Detection* said:
Check you're not trying to downgrade the bootloader as shown here
G960FXXU2BRGA << Version 2
Check which version it says in Download mode (B:1 or B:2)
Either match it or flash a higher version
Click to expand...
Click to collapse
{
"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"
}
Picture is of my download screen and ,
Great call! Just dug into it some more and thats the issue. Since the PAK CSC isnt on U2 yet im going to flash one from another country. I know you can but ive never heard of the downsides of flashing another countries firmware... is there one? Also have you heard of the issue with the oem unlock not appearing after 7 days?
Edit: Also what is the proper way to give you credit for answering the question as well as pointing out a good answer for people in the future who are confused? Just the thanks button?
Update: I tried again with a swiss one with Version 2 but it still failed. Ill download a few and try them as well just to be sure.

drowsy_fish said:
Picture is of my download screen and ,
Great call! Just dug into it some more and thats the issue. Since the PAK CSC isnt on U2 yet im going to flash one from another country. I know you can but ive never heard of the downsides of flashing another countries firmware... is there one? Also have you heard of the issue with the oem unlock not appearing after 7 days?
Edit: Also what is the proper way to give you credit for answering the question as well as pointing out a good answer for people in the future who are confused? Just the thanks button?
Update: I tried again with a swiss one with Version 2 but it still failed. Ill download a few and try them as well just to be sure.
Click to expand...
Click to collapse
Yea just hit the thanks button if someone helped (I don't see your image)
Only real downsides I've heard of are things like VoLTE and WiFi calling not being active on certain CSCs
Check the "Repartition" option in ODIN 3.13.1 settings too, possible the custom ROM messed them up
OEM unlock does seem to be hit and miss for some people, some get it immediately (I did), some wait 7 days, others wait 7 days and nothing, not seen a solution other than just keep waiting yet

*Detection* said:
Yea just hit the thanks button if someone helped (I don't see your image)
Only real downsides I've heard of are things like VoLTE and WiFi calling not being active on certain CSCs
Check the "Repartition" option in ODIN 3.13.1 settings too, possible the custom ROM messed them up
OEM unlock does seem to be hit and miss for some people, some get it immediately (I did), some wait 7 days, others wait 7 days and nothing, not seen a solution other than just keep waiting yet
Click to expand...
Click to collapse
Eh im not to worried about VoLTE or WifiCalling so thats good but I was under the impression you needed a PIT file to re-partition your phone without bricking it? (No clue whata PIT file is , just remember reading that about 5 years ago)
Hmm thats annoying.... the idea for this security is nice but it is sure a hassle for people who want custom binaries.

drowsy_fish said:
Eh im not to worried about VoLTE or WifiCalling so thats good but I was under the impression you needed a PIT file to re-partition your phone without bricking it? (No clue whata PIT file is , just remember reading that about 5 years ago)
Hmm thats annoying.... the idea for this security is nice but it is sure a hassle for people who want custom binaries.
Click to expand...
Click to collapse
PIT file is now included in the CSC part of the firmware (Partition Information Table)
Yea Samsung have really gone to town on locking down devices lately, I haven't even bothered rooting a phone since my S5, had an S7 and now S9 since then, just left them stock

*Detection* said:
PIT file is now included in the CSC part of the firmware (Partition Information Table)
Yea Samsung have really gone to town on locking down devices lately, I haven't even bothered rooting a phone since my S5, had an S7 and now S9 since then, just left them stock
Click to expand...
Click to collapse
God, I loved the S5... solid phone. Had it up to just 3 months ago when I got the s9.
I had just tried to flash the firmware I just used and failed with. But I clicked to fast and forgot to check the box for it to re-partition with. Weirdly enough it flashed with no issue... I have no clue what happened but it must have just been those 1s and 0s being finicky. Thanks for the info about the bootloader ect though.... you have been a huge help brother

drowsy_fish said:
God, I loved the S5... solid phone. Had it up to just 3 months ago when I got the s9.
I had just tried to flash the firmware I just used and failed with. But I clicked to fast and forgot to check the box for it to re-partition with. Weirdly enough it flashed with no issue... I have no clue what happened but it must have just been those 1s and 0s being finicky. Thanks for the info about the bootloader ect though.... you have been a huge help brother
Click to expand...
Click to collapse
Nice one, just a glitch in the matrix no probs :good:

*Detection* said:
Check you're not trying to downgrade the bootloader as shown here
G960FXXU2BRGA << Version 2
Click to expand...
Click to collapse
I am also stuck at recovery.img in Odin, while downgrading to a 6 months older stock firmware. The long story short - I want the older firmware because I have a TWRP backup done while this older stock rom was installed on my phone. When upgraded to the new stock firmware, I lost root and restored the TWRP backup (incl. boot) but in the end it the phone doesn't start up. So I want to install the older stock rom in order to be able to restore the TWRP backup. Any ideas how to do that? My only wish is to have a phone that boots and to which I can restore the TWRP backup (where all my apps and settings are).
Update: managed to flash the new firmare, I obviously cannot flash the older firmware because of the older bootloader. So, any ideas how to restore the TWRP backup (made when the old firmware was installed) while the new firmware is currently installed?

Question Can't register fingerprints

After updating the requisite firmware, I performed a clean flash of the latest CRDroid build (previously I was using the March 28) build. During the initial setup, as well as after through the regular settings page, I was unable to register any of my fingerprints to the biometric unlock. In the setup screen, the UDFPS lights up when pressed (see screenshot), but no matter how long I keep my finger pressed on it the print will not register. I have rebooted, clean flashed, and dirty flashed the ROM, and the problem appears every time. I have tried installing both with and without GApps. I even tried flashing LineageOS instead of CRDroid, and I had the same issue. What steps should I be taking to troubleshoot 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"
}

Do you have the backup of persist partion?

PattasuBalu said:
Do you have the backup of persist partion?
Click to expand...
Click to collapse
No, the only backup I have of my previous install is the Swift Backup of apps and settings.

Try going to stock and check if the fingerprint is working. If its working then it may be a bug. If not then I think you have over written the persist partition.

PattasuBalu said:
Try going to stock and check if the fingerprint is working. If its working then it may be a bug. If not then I think you have over written the persist partition.
Click to expand...
Click to collapse
What's the easiest way to revert to Stock? Should I just download one of the packages in the pinned post on this forum and sideload?
And if my persist partition is corrupted, what recourse do I have?

Try MSM tool. Probably one or both slots are derped. Also maybe you use wrong base firmware for these roms

sumfahg said:
What's the easiest way to revert to Stock? Should I just download one of the packages in the pinned post on this forum and sideload?
And if my persist partition is corrupted, what recourse do I have?
Click to expand...
Click to collapse
If persist partition is corrupted you have no other choice except to give your phone to OnePlus service center as this is unique for every phone.

EugenStanis said:
Try MSM tool. Probably one or both slots are derped. Also maybe you use wrong base firmware for these roms
Click to expand...
Click to collapse
MSM Tool worked fine, but I was also unable to enroll there. Seems my only choice is to find a OP service center and get the phone sent out.

sumfahg said:
MSM Tool worked fine, but I was also unable to enroll there. Seems my only choice is to find a OP service center and get the phone sent out.
Click to expand...
Click to collapse
Just dont forget to lock your bootloader and say that the new update broke your phone. BTW dont forget to take a backup of persist.img when you flash a new rom.

Yeah I have one stored in the cloud before I ever even unlocked bl. Can't just use any model persist partition..it's particular to each device. Sending in is only option or don't use fp option.

PattasuBalu said:
If persist partition is corrupted you have no other choice except to give your phone to OnePlus service center as this is unique for every phone.
Click to expand...
Click to collapse
There's also a way to re-register it. Had this happen on my 8. Just didn't work the same since.

mattie_49 said:
Yeah I have one stored in the cloud before I ever even unlocked bl. Can't just use any model persist partition..it's particular to each device. Sending in is only option or don't use fp option.
Click to expand...
Click to collapse
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?

sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
Click to expand...
Click to collapse
I think he took the backup via Partitions Backupper app which was the same app I used take a backup of my persist.img. But the app requires super user access to take backup.

TheKnux said:
There's also a way to re-register it. Had this happen on my 8. Just didn't work the same since.
Click to expand...
Click to collapse
Can you please mention the steps and what are the backsides of doing this?

sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
Click to expand...
Click to collapse
Many ways to accomplish without root. And you back up the persist partition. Not root directory. Msm Read back with F8. Then find persist and send it to the root directory of C drive with Read back feature. . Password oneplus

sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist
sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You can backup persist and co with msm tool (read back modus)

PattasuBalu said:
Can you please mention the steps and what are the backsides of doing this?
Click to expand...
Click to collapse
Just search xda. Pretty sure it's on the OnePlus 8 or 8T forums.