All Thanks to @Derjan23
I used Code from his post here
thanks to @OopsWare for his analysis of this code here
Disclaimer:
I am not responsible for any damage at your device!
You're running this programm on your own risk!
Here's unlock Program it does the following
1-try to read odm_reserved
2-check if your bootloader unlocked or locked
3-calculate the most effective string that you have to echo to reverse bootloader state(it will relock if your Bootloader is unlocked - unlock if your Bootloader is locked
4-you can copy echo command and use it after su root in terminal
DONT BLOWN ALL FUSES WITH echo /data/local/tmp/odm_reserved >/sys/firmware/fuse/odm_reserved
The unlock check use 8 bytes of fuses which are Stored at sys/firmware/fuse/odm_reserved in the 1st 16 hexadecimal digits
I will use the value most unlocked devices have to explain 00000040 000000c0
those 8 bytes divided into 2 groups:
1- red group is unlockable or no unlockable
2- blue group for locked unlocked
each hexadecimal digit represented in 4bits the unlock check needed only 2bits from each group - 1st check iteration is made on digit 4 and digit c
4 = 0100 binary
c=1100 binary
1st group: unlockable is 01 non-unlockable is 10 - 00 stops checking - 11 check next 2 bits
2nd group: unlocked is 11 any other value is locked
here is the order it iterates through those bytes
00000040 000000c0
1-40 c0
2-00 00
3-00 00
4-00 00
the order inside each byte
40 = 01000000
c0 = 11000000
1-01 11
2-00 00
3-00 00
4-00 00
Conclusion : you have 16 chance to unlock relock the method used is unlocking (thanks to d in odm word) but blows all your chances
to unlock you need 01 in 1st group 11 in 2nd group
if 1st group is 10 like in 80 10000000 your only choice to unlock is to flash these fuses and use next ones so you should make them 11010000 which equal d0 and you need 11 in corresponding bits in 2nd group
00110000 30
so in your rooted JB device use Terminal app
1- su
2- echo 40000000c0 >/sys/firmware/fuse/odm_reserved
here's the 4 chances in 1st byte in order
1- unlock 40000000c0 relock c000000000
2- unlock d000000030 relock f000000000
3- unlock f40000000c relock fc00000000
4- unlock fd00000003 relock ff00000000
thats in 1st byte of our 4 bytes 2nd will be unlock 40ff0000c000 relock c0ff00000000
1st byte in 1st group will be ff and 1st byte in 2nd group it doesn't matter so i used 00 and it'll continues like this
be aware that any binary 1s in odm reserved can't be 0 again so the result of echo command = digits you send logical OR digits in the file
why would anyone want to relock the bootloader?
Also does this mean that users who did echo /data/local/tmp/odm_reserved have a permanently unlocked bootloader? that ant be relocked?
DavidXanatos said:
why would anyone want to relock the bootloader?
Also does this mean that users who did echo /data/local/tmp/odm_reserved have a permanently unlocked bootloader? that ant be relocked?
Click to expand...
Click to collapse
they have a chance to relock without unlocking again @exFAT did it - if bootloader itself check this fuse then unlock methods(adb and fastboot) only sets this flag so bootloader allow any boot images (unlocked) or specific ones (locked)and this flag is dangerous because when it becomes all ones (16 f) you will stayed with locked device forever
if unlocking methods change bootloader itself then unlock through hack only shouldn't be enough and unlock methods should be used - and in that case relock should have no effect only its shown like this in hidden menu
hmm...
here: http://forum.xda-developers.com/showpost.php?p=40635481&postcount=8
he wrote that despite of having blown all fuses he can still but CWM and a custom ROM.
Just a question...?
After reading this i've just been thinking...
Would flashing the firmware through LG Flash Tool affect the Bootloader lock state?
Has anyone followed the ODM Reserved Mod and re-flashed an LG Firmware?
If so does the Bootloader Unlock remain? Is it permanent? :good:
i used the ODM hack and flashed back to LG jelly bean with LG Mobile Flash Tool. Bootloader is still unlocked Flashed CWM & CM.10.1 over my 232.10 Hutchison branding! Now my baseband Version is from my Provider instead of the EUR one.
sorry about my english ^^
i think that using LG Flash Tool to rollback to ICS will affect that.
reas0n said:
i think that using LG Flash Tool to rollback to ICS will affect that.
Click to expand...
Click to collapse
I don't think soo... when you go back to JB, bootloader still unlocked.
RuedasLocas said:
I don't think soo... when you go back to JB, bootloader still unlocked.
Click to expand...
Click to collapse
I have tried it my self using the very first thread about unlocking the bootloader with writing fuse in temp folder. Went back to ICS with LG Flash Tool and afterthat I updated to stock jelly bean and rooted it is still unlocked. But I really don't know if it was locked in ICS? any ways I on CM10.1 and its TOP.
I also think it's like @RuedasLocas wrote.
GizModio said:
After reading this i've just been thinking...
Would flashing the firmware through LG Flash Tool affect the Bootloader lock state?
Has anyone followed the ODM Reserved Mod and re-flashed an LG Firmware?
If so does the Bootloader Unlock remain? Is it permanent? :good:
Click to expand...
Click to collapse
Erazor84 said:
i used the ODM hack and flashed back to LG jelly bean with LG Mobile Flash Tool. Bootloader is still unlocked Flashed CWM & CM.10.1 over my 232.10 Hutchison branding! Now my baseband Version is from my Provider instead of the EUR one.
sorry about my english ^^
Click to expand...
Click to collapse
lock state is put in fuses being read in odm_reserved file - Jellybean Rom allowed write them - I tried same hack on rooted ICS and it was not working
bootloader official unlock procedure does change odm_reserved from 4000000000 to 40000000c0
they needed to drop some of their security to allow us to write these fuses through adb to unlock our bootloader
so any flashing doesn't affect it but hack method will do
future81 said:
lock state is put in fuses being read in odm_reserved file - Jellybean Rom allowed write them - I tried same hack on rooted ICS and it was not working
bootloader official unlock procedure does change odm_reserved from 4000000000 to 40000000c0
they needed to drop some of their security to allow us to write these fuses through adb to unlock our bootloader
so any flashing doesn't affect it but hack method will do
Click to expand...
Click to collapse
So both the "ODM_Reserved Mod" and the official Boot-loader unlock do exactly the same?
They both change the code?
GizModio said:
So both the "ODM_Reserved Mod" and the official Boot-loader unlock do exactly the same?
They both change the code?
Click to expand...
Click to collapse
I think so maybe official bootloader unlock do other things additional to that but i'm convinced the bootloader itself kept unchanged it's only was checking these fuses even on ICS - that can be proved if someone with unlocked bootloader flashed ICS and tried flashing cwm recovery after rooting it and rebooted into it without security errors
I've made small program to unlock relock
OP updated
Hmm...
Sent from my LG-P880 using Tapatalk 2
exFAT said:
Hmm...
Sent from my LG-P880 using Tapatalk 2
Click to expand...
Click to collapse
so did you flash stock Rom with lg methods and then laufersteppenwolf kernel?
if you didn't use lg flash tools you shouldn't risk try it
here is unlocking process log
D/UnlockService( 625): sim state:0 mcc:4095 mnc:255
D/UnlockService( 625): readSysfs_string() : 0x000000000000000000000000000000000000000000000000 00000040000000c0
D/UnlockService( 625): setUnlockAvailBit strRead : 00000000000000000000000000000000000000000000000000 000040000000c0
D/UnlockService( 625): setUnlockAvailBit reversed : 40000000
D/UnlockService( 625): setUnlockAvailBit nProcessingNumber : 40000000
D/UnlockService( 625): setUnlockAvailBit nResetMaskingBits : c0000000
D/UnlockService( 625): setUnlockAvailBit nNotAvailMaskingBits : 80000000
D/UnlockService( 625): setUnlockAvailBit nAvailMaskingBits : 40000000
Click to expand...
Click to collapse
and this is hidden menu unlock check log
BootloaderUnlock_Test( 2641): readSysfs_string() : 0x000000000000000000000000000000000000000000000000 0000004000000000
BootloaderUnlock_Test( 2641): bootloader_unlock_flag_read strRead : 00000000000000000000000000000000000000000000000000 00004000000000
BootloaderUnlock_Test( 2641): bootloader_unlock_flag_read reversed : 40000000
BootloaderUnlock_Test( 2641): bootloader_unlock_flag_read reversed : 00000000
BootloaderUnlock_Test( 2641): nProcessingNumber_Avail : 40000000
BootloaderUnlock_Test( 2641): nProcessingNumber_Unlock : 0
BootloaderUnlock_Test( 2641): bootloader_unlock_flag_read nResetMaskingBits : c0000000
BootloaderUnlock_Test( 2641): bootloader_unlock_flag_read nNotAvailMaskingBits : 80000000
BootloaderUnlock_Test( 2641): bootloader_unlock_flag_read nAvailMaskingBits : 40000000
Click to expand...
Click to collapse
so unlock bootloader typically reverse hidden menu check - it requires avail masking bits (first 4 or d not 8 or e) and set corresponding bits to 11 (c or f)
even the rest of the log before the odm reversed part (readsysfs) looks like a checking with operator if it allows bootloader unlocking or not then the unlocking itself is made by this flag
and i'm not sure whats the difference between really locked (4 with non 11 in corresponding bits or 8) and between that all f situation - it's stopped because it checked all fuses and didn't find required 4 and didn't stopped with 8
future81 said:
so did you flash stock Rom with lg methods and then laufersteppenwolf kernel?
if you didn't use lg flash tools you shouldn't risk try it
here is unlocking process log
and this is hidden menu unlock check log
so unlock bootloader typically reverse hidden menu check - it requires avail masking bits (first 4 or d not 8 or e) and set corresponding bits to 11 (c or f)
even the rest of the log before the odm reversed part (readsysfs) looks like a checking with operator if it allows bootloader unlocking or not then the unlocking itself is made by this flag
and i'm not sure whats the difference between really locked (4 with non 11 in corresponding bits or 8) and between that all f situation - it's stopped because it checked all fuses and didn't find required 4 and didn't stopped with 8
Click to expand...
Click to collapse
I was on Kholk's kernel and stock v20b HKG when I relocked (apparently). I flashed Werewolf kernel manually via terminal emulator, rebooted fine.
Sent from my LG-P880 using Tapatalk 2
does the fuse remain even when you move away from STOCK ROM?
jonnya70 said:
does the fuse remain even when you move away from STOCK ROM?
Click to expand...
Click to collapse
yes its hardware bit designed to be written once
I just tried your App and it Worked very Good.
The Hidden Menu Shows Unlocked in my Phone and I even not Restart the Phone.
Now I just have to get CWM to confim everything it's ok but I'm sure it will work.
Related
Hi
today i sim-unlocked my Xperia X8 using Omnius, but now i want to unlock the bootloader to install a different kernel from the stock kernel.
Following the instructions below http://forum.xda-developers.com/showthread.php?t=1254225, when i start the file msm7227_omniusSL.cmd i get this:
------
Requires Android firmware 2.x standard process.
Press any key to continue. . .
Getting ROOT rights.
* Daemon not running. starting it now *
* Daemon started successfully *
1368 KB / s (585731 bytes in 0.418s)
property service neutered.
adbd killing. (Should restart in a second or two)
Waiting ...
Removing restrictions on NAND MPU SEMC backdoors. Permanent. Require ROOT rights.
376 KB / s (3087 bytes in 0.008s)
Success
Waiting ...
Getting ROOT rights.
error: protocol fault (no status)
Waiting ...
Writing semcboot patched. Two step process
First, we need to get access semcboot area
656 KB / s (8064 bytes in 0.012s)
Second, we need to write semcboot
3100 KB / s (596916 bytes in 0.188s)
successfully wrote 0003ff00
Press any key to continue. . .
------
but than if i verify with s1tool, i get the message (RUNNING S1_EROM VER" R8A029 ") and so bootloader has not been unlocked.
Does anyone know a solution?
I used Omnius for SE v0.27
Thanks a lot
I have the same problem ...
me too...any news?
Same for me!
Any of you with original 2.1??? Maybe it only works on original 2.1, I remember that I had to change from rom to original 2.1 so I could unlock with Omnius.
n4s said:
Same for me!
Any of you with original 2.1??? Maybe it only works on original 2.1, I remember that I had to change from rom to original 2.1 so I could unlock with Omnius.
Click to expand...
Click to collapse
I tried with the original 2.1 and with other 2.2/2.3 but it's the same
Hi,
I have been making some experiences and I think that all of us want to unlock boot loader to be able to change kernel.
So it's true that using the omnius method it doesn't work but if we use semc method it works, but we loose radio.
So my idea was:
1- Unlock with SEMC method
2- Apply custom kernel
3- Unlock with Omnius method (this will relock bootloader but recover radio)
I have tried 1 and 3 and worked, I'm just affraid that also doing nº2 might bring some problems, what's your opinion?
Found my answer!-""If you relock your bootloader while using a custom kernel your phone will be bricked!""
Somebody already unlocked bootloader anyone of you?
I have searched I never found anyone that sim-unlocked with omnius and then unlocked bootloader
n4s said:
I have searched I never found anyone that sim-unlocked with omnius and then unlocked bootloader
Click to expand...
Click to collapse
I just found out this myself. After wasting $100 (Sale Price) for the omnius unlocker. They never stated anywhere that it would relock bootloader, nor did they mention it could be unlocked. After an inquiry, I was told that msm7227_OmniusSL.cmd should help me...? So I am off on another research adventure. Not to mention I cannot even get my phone to "register on the network". Anyone want a Omnius License with 11months and 2weeks with 4 x10 unlock credits? I take paypal! I just knew I should have ordered the sekey and waited a month for it to arrive from hong kong. I truly feel like I got the "Royal Shaft!".
Can anyone help?
@unimatrix725 if you made a backup of your TA, then you could restore your TA as it was before you unlocked with omnius, so you can unlock your bootloader, the only downside is that your phone will be sim-locked once again, oh and watch out, because you can only restore TA with an active omnius account, i.e. have a 1 day/month/year account, so if you want to restore your TA you should do it before selling your credits
i hate that the only safe way to have both bootloader and sim unlocked is with setools, because the credits i dont mind, but the activation fee is too much price for unlocking one phone
well,for our x8 device,we can actually unlock bootloader using flashtool(latest one)
here a complete tutorial with picture that i manage to safe as pdf file(for my future use) and i think it might help,but it actually from x10 forum,however i already test it myself,and work it for our x8,to unlock the bootloader,follow this step carefully
press thanks if i help
he he he, sorry i think i misspoke that, what i meant was have unlocked sim with setools and unlock bootloader with any other method, not necessary both with setools , if someone could fix the my7227bootwrite_omniusSL so everyone that unlocked their sim with omnius could unlock the bootloader would be great, but i haven't seen any dev interested in helping us ...
unimatrix725 said:
I just found out this myself. After wasting $100 (Sale Price) for the omnius unlocker. They never stated anywhere that it would relock bootloader, nor did they mention it could be unlocked. After an inquiry, I was told that msm7227_OmniusSL.cmd should help me...? So I am off on another research adventure. Not to mention I cannot even get my phone to "register on the network". Anyone want a Omnius License with 11months and 2weeks with 4 x10 unlock credits? I take paypal! I just knew I should have ordered the sekey and waited a month for it to arrive from hong kong. I truly feel like I got the "Royal Shaft!".
Can anyone help?
Click to expand...
Click to collapse
OK EVERYONE HAVING THE SAME PROBLEM HERE IS HOW TO FIX IT!! After network unlocking your phone with Omnius and you then want to unlock the bootloader follow this tutorial: http://forum.xda-developers.com/showthread.php?t=1254225. You will be using tool msm7227_setool2.cmd to unlock your bootloader. When you have unlock the bootloader install a custom kernel then install your custom rom I suggest GingerDx. (I am not going to get into how to flash a custom kernel or roms there is loads of threads to help you with that). You will notice the network does not work (no coverage). Download the stock kernel from the link above. Flash the stock kernel then use msm7227_OmniusSL.cmd to lock your bootloader. This may take a few times and a bit of patience before the bootloader locks. Now you will have coverage and be able to use any sim card in your phone. Custom kernels dont work after using omnius network unlock tool. It always ends up with no coverage. So just stay on stock kernel. If you need to update your rom you will have to go through the whole method again. I have attached the bootloader unlocking/relocking tools below
I HOPE THIS HELPED EVERYONE WHO IS HAVING THIS PROBLEM IF YOU NEED ANY HELP PM AND I WILL HELP THE BEST I CAN
HIT THE THANKS BUTTON!!!!!
bahmonkeys said:
OK EVERYONE HAVING THE SAME PROBLEM HERE IS HOW TO FIX IT!! After network unlocking your phone with Omnius and you then want to unlock the bootloader follow this tutorial: http://forum.xda-developers.com/showthread.php?t=1254225. You will be using tool msm7227_setool2.cmd to unlock your bootloader. When you have unlock the bootloader install a custom kernel then install your custom rom I suggest GingerDx. (I am not going to get into how to flash a custom kernel or roms there is loads of threads to help you with that). You will notice the network does not work (no coverage). Download the stock kernel from the link above. Flash the stock kernel then use msm7227_OmniusSL.cmd to lock your bootloader. This may take a few times and a bit of patience before the bootloader locks. Now you will have coverage and be able to use any sim card in your phone. Custom kernels dont work after using omnius network unlock tool. It always ends up with no coverage. So just stay on stock kernel. If you need to update your rom you will have to go through the whole method again. I have attached the bootloader unlocking/relocking tools below
I HOPE THIS HELPED EVERYONE WHO IS HAVING THIS PROBLEM IF YOU NEED ANY HELP PM AND I WILL HELP THE BEST I CAN
HIT THE THANKS BUTTON!!!!!
Click to expand...
Click to collapse
I want to try this, but I've a dumb question... why do I need to install the custom kernel and then the stock one? .... why not just flash the rom alone?
bahmonkeys said:
OK EVERYONE HAVING THE SAME PROBLEM HERE IS HOW TO FIX IT!! After network unlocking your phone with Omnius and you then want to unlock the bootloader follow this tutorial: http://forum.xda-developers.com/showthread.php?t=1254225. You will be using tool msm7227_setool2.cmd to unlock your bootloader. When you have unlock the bootloader install a custom kernel then install your custom rom I suggest GingerDx. (I am not going to get into how to flash a custom kernel or roms there is loads of threads to help you with that). You will notice the network does not work (no coverage). Download the stock kernel from the link above. Flash the stock kernel then use msm7227_OmniusSL.cmd to lock your bootloader. This may take a few times and a bit of patience before the bootloader locks. Now you will have coverage and be able to use any sim card in your phone. Custom kernels dont work after using omnius network unlock tool. It always ends up with no coverage. So just stay on stock kernel. If you need to update your rom you will have to go through the whole method again. I have attached the bootloader unlocking/relocking tools below
I HOPE THIS HELPED EVERYONE WHO IS HAVING THIS PROBLEM IF YOU NEED ANY HELP PM AND I WILL HELP THE BEST I CAN
HIT THE THANKS BUTTON!!!!!
Click to expand...
Click to collapse
thank you, my u20i finally has signal
I also have Unlocked with Omnius and for now, i always Flash Kernel's with Omnius self.
- Choose your Device
- Click Flash
- in "Customization File" looking for your .ftf file
- Enable unsigned Flashing
And lets start...
First time posting a thread.
So I have my HTC One here, rooted, bootloader unlocked, installed Cyanogenmod 11, but it is SIMLOCKED.
I tried T-mobile support, and out of three times that I requested the unlock code from them they only sent me the unlock code once AND IT FAILED
I tried the Ultimate Simlock Code Generator 2.1 and it just didn't respond after I complete the survey before it is supposed to give me the download link.
I tried to find the UN_lock_code with this method from another thread:
To find your SIM UNLOCK CODE you need:
1) Root
2) Android Terminal Emulator (free from the market)
3) Your IMEI number (dial *#06# on your dialler)
There are 4 steps to the process:
1) Obtain your UN_lock_code from your phone
2) Calculate the key from your IMEI number
3) Subtract (2) from (1)
4) Unlock your phone
Step 1
Obtain your UN_lock_code from your phone as follows:
Open the Terminal Emulator app and type:
su [enter]
strings -n 8 /dev/block/mmcblk0p6 [enter]
It will output several lines of data (including your IMEI number)
One of the lines will be [eg] UN_Lock_code=063312345
Make a note of this number (This is NOT your SIM unlock code)!
Step 2
Make a key from your IMEI number:
a) Write down the last 7 digits of your IMEI number in this format: 1234 567
b) Reverse the 2 blocks: 567 1234
c) Add a 4th digit X: 567 X 1234 where:
X = the sum of the first 3 digits (If the sum is 2 digits, write only the 2nd digit)
[5 + 6 + 7 = 18 in the example above so X = 8]
[if the sum is 3, X = 3]
[if the sum is 17, X = 7]
[if the sum is 25, X = 5] etc.
Using the above IMEI number we get:
567 8 1234 (= the key)
Step 3
Perform a simple sum.
UN_Lock_code [step 1] – key [step 2] = SIM UNLOCK CODE
e.g. 063312345 - 56781234 = 6 531 111
This needs to be an 8-digit number, so add a zero at the beginning if necessary
YOUR SIM UNLOCK CODE IS: 0653 1111
Click to expand...
Click to collapse
But I got stuck on the first step already because I couldn't even find where the UN_lock_code in the lines of data.
I looked up everywhere else and the rest of the internet just told me to pay to unlock from some random apps on Google Play Store.
I am in Taiwan now so some of the T-Mobile support pages aren't even reachable (error 500), not to mention going to a T-Mobile store.
So what is my best bet now? Is it because I have Cyanogenmod 11? Are there any other ways to unlock the simlock? Or should I just pay for it and get over with this quickly?
Thank you in advance!!
alex93310 said:
First time posting a thread.
So I have my HTC One here, rooted, bootloader unlocked, installed Cyanogenmod 11, but it is SIMLOCKED.
I tried T-mobile support, and out of three times that I requested the unlock code from them they only sent me the unlock code once AND IT FAILED
I tried the Ultimate Simlock Code Generator 2.1 and it just didn't respond after I complete the survey before it is supposed to give me the download link.
I tried to find the UN_lock_code with this method from another thread:
But I got stuck on the first step already because I couldn't even find where the UN_lock_code in the lines of data.
I looked up everywhere else and the rest of the internet just told me to pay to unlock from some random apps on Google Play Store.
I am in Taiwan now so some of the T-Mobile support pages aren't even reachable (error 500), not to mention going to a T-Mobile store.
So what is my best bet now? Is it because I have Cyanogenmod 11? Are there any other ways to unlock the simlock? Or should I just pay for it and get over with this quickly?
Thank you in advance!!
Click to expand...
Click to collapse
Sim unlock code only works with a stock rom. Install the stock rom and try again
bored_stupid said:
Sim unlock code only works with a stock rom. Install the stock rom and try again
Click to expand...
Click to collapse
Are you sure? Most other sources say that ROM doesn't matter. I will try it though.
alex93310 said:
Are you sure? Most other sources say that ROM doesn't matter. I will try it though.
Click to expand...
Click to collapse
Yes you need to be on stock rom. There is many threads here about this.
Sent from my HTC One using XDA Free mobile app
alray said:
Yes you need to be on stock rom. There is many threads here about this.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Do you mean any rom with sense 5.0 and Android 4.2?
I'm not sure how many times I've already tried and failed to enter the correct unlock code, so I have few chances of error.
I just flashed the android revolution stock odex. Will this work?
alex93310 said:
Do you mean any rom with sense 5.0 and Android 4.2?
I'm not sure how many times I've already tried and failed to enter the correct unlock code, so I have few chances of error.
I just flashed the android revolution stock odex. Will this work?
Click to expand...
Click to collapse
well if i was you, id install the T-Mobile stock since its them you got the sim unlock code from,
Problem Solved!
Thank you all for the advice! I flashed the original T-Mobile ROM found here: http://forum.xda-developers.com/showthread.php?t=2353812
and entered the unlocking code T-Mobile gave me the first time and it worked! I don't have to carry around 2 phones anymore! :laugh:
alex93310 said:
Thank you all for the advice! I flashed the original T-Mobile ROM found here: http://forum.xda-developers.com/showthread.php?t=2353812
and entered the unlocking code T-Mobile gave me the first time and it worked! I don't have to carry around 2 phones anymore! :laugh:
Click to expand...
Click to collapse
Pleased youve got it to work now. Can you add solved to your post title please. Edit-Advanced.
I just received my XP and to start off with I want to root.
All root methods I've found, need to unlock the bootloader before rooting.
I'm looking for methods to unlock the phone without unlocking the bootloader.
deboopi2 said:
I just received my XP and to start off with I want to root.
All root methods I've found, need to unlock the bootloader before rooting.
I'm looking for methods to unlock the phone without unlocking the bootloader.
Click to expand...
Click to collapse
it would already help to have a temporary root to be able to save the TA partition. With a TA backup you could unlock the bootloader, install the AndoPlusKernel build and flash a prerooted image and look (restore TA) the bootloader again
Waiting for an exploit...
DiLeon said:
it would already help to have a temporary root to be able to save the TA partition. With a TA backup you could unlock the bootloader, install the AndoPlusKernel build and flash a prerooted image and look (restore TA) the bootloader again
Waiting for an exploit...
Click to expand...
Click to collapse
For my know, there have no method to temporary root for xp now. Have you got any idea?:fingers-crossed:
bkk99213 said:
For my know, there have no method to temporary root for xp now. Have you got any idea?:fingers-crossed:
Click to expand...
Click to collapse
Unfortunately not
I found this link to towelroot. I do not know if it works (haven't tried it yet), but this might be a solution.
If it works one should be able to backup the TA partition with TA-Backup if this still works for recent devices.
deboopi2 said:
I found this link to towelroot. I do not know if it works (haven't tried it yet), but this might be a solution.
If it works one should be able to backup the TA partition with TA-Backup if this still works for recent devices.
Click to expand...
Click to collapse
It won't work as Sony already patched it.
Does anybody knows any of the methods mentioned in the following link, do they work without unlocking because unlocking is not mentioned.
http://androidrootmania.net/how-to-root-sony-xperia-x-performance-dual/
deboopi2 said:
Does anybody knows any of the methods mentioned in the following link, do they work without unlocking because unlocking is not mentioned.
http://*******.net/how-to-root-sony-xperia-x-performance-dual/
Click to expand...
Click to collapse
It's scam website (copy and paste...).
All rootkit released before now won't work.
is the lack of root an issue from Sony or Android? I thought Sony was pretty welcoming to the Dev community and even allowed unlocking the bootloader
acme64 said:
is the lack of root an issue from Sony or Android? I thought Sony was pretty welcoming to the Dev community and even allowed unlocking the bootloader
Click to expand...
Click to collapse
People in this thread wants root with locked bootloader.
Unlocking and rooting is pretty easy.
AndroPlus said:
People in this thread wants root with locked bootloader.
Unlocking and rooting is pretty easy.
Click to expand...
Click to collapse
ooh i see, for things like backing up the drm keys i assume. thanks for clarifying.
unlocking and rooting loses the ability to miracast though
Anybody know if any progress has been made for root in lb?
Sent from my F8131 using Tapatalk
As i know , there`s no progress for LB.
hm...WTF?
I have LB, stock firmware. After flashing device I had that:
14/058/2016 18:58:27 - INFO - Writing TA unit 00002725. Value : 32 30 31 36 2D 30 39 2D 31 34 20 31 38 3A 35 38 3A 32 37 00
14/058/2016 18:58:27 - INFO - Writing TA unit 00002774. Value : 00
14/058/2016 18:58:27 - INFO - Closing TA partition
14/058/2016 18:58:30 - INFO - Ending flash session
14/058/2016 18:58:30 - INFO - Flashing finished.
14/058/2016 18:58:30 - INFO - Please unplug and start your phone
14/058/2016 18:58:30 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
14/000/2016 19:00:26 - INFO - Device connected with USB debugging on
14/000/2016 19:00:26 - INFO - Connected device : Sony Xperia X Performance
14/000/2016 19:00:26 - INFO - Installed version of busybox : N/A
14/000/2016 19:00:26 - INFO - Android version : 6.0.1 / kernel version : / Build number : 35.0.A.1.275
14/000/2016 19:00:26 - INFO - Phone in recovery mode
14/000/2016 19:00:26 - INFO - Root Access Allowed
Click to expand...
Click to collapse
maybe we can use it?
Desperanto86 said:
hm...WTF?
I have LB, stock firmware. After flashing device I had that:
maybe we can use it?
Click to expand...
Click to collapse
weird, when you reconnect does it still show up as root acces allowed? If so you could try to push SuperSU to phone with flashtool
Desperanto86 said:
hm...WTF?
I have LB, stock firmware. After flashing device I had that:
maybe we can use it?
Click to expand...
Click to collapse
Which firmware?
Sent from my F8131 using Tapatalk
I guess until Nougat is released there will be no news. Maybe then there is some sort of exploit.
Gesendet von meinem D5803 mit Tapatalk
As far as I know - if the device is unlocked you can't use OTA updates?
How do you upgrade your android version if there are no custom roms then? (like when nougat finally comes out for the f8131)
With Flashtool and / or Sony Companion it shouldn't be a problem.
Gesendet von meinem F8131 mit Tapatalk
UPDATED:
Issue has been solved
( i buy 4 credits from dc unlocker and use HCU to read my boot loader code )
yes i know this is all from dc unlockcer yes they , unbrick my P9 but they also
changed the boot code when you flashed the rom via DC phoenix
im suspecting it that way .
Hello guys. Debranded P9 here
Nougat C432B386 Eva-L09
hw eu :country vendor
Bootloader unlocked and FRP lock
my device gets suffer from a hard brick
and recovered by DC Phoenix. In order to
have a Stable Nougat Firmware i decide to
debrand my phone ......
1st attempt : flashing the (.dgkmts AL10 chinese rom)
after flashing the chinese Al10 firmware
from DCUnlocker (.dgkmts) the device boot and
can be flashed into original stock rom
but the first attempt fails because my
vendor comes from a different build
2nd attempt: flashing the (.dgkmts AL10 chinese rom)
but this time, i decide to wipe NVME and OEM
after booting into system and checking my device
details my IMEI stays the same but Serial No is missing
so i had to use HCU to write my IMEI and Serial No.
and obtain a new vendor from hw eu
after booting system, I start to forced update the
EVA-L09C432B136
then i unlocked my bootloader at this stage
using the same bootloader code from Huawei
FIRMWARE:EVA-L09 C432B136
( please focus on this, i already unlocked the bootloader
here , and allow the oem to unlock )
status : bootloader unlock
frp unlock
the process is successfully done and after that
i check my device details and perfectly debrand
my P9, after a minute it received an OTA update
from Huawei System Updater ( C432B186 )
I update into it and reboot and received another update
again C432B322 ( Nougat-beta version) and then
received the Final Build C432B386
SUMMARY STAGES:
bricked and wiped oem info / SN rewrite using HCU
1. AL10 Chinese rom >
2. C432B136 ( stock firmware)
( do unlocked bootloader )
3. OTA C432B186
4. OTA C432B322 ( Nougat beta )
5. OTA C432B386 ( Nougat Stable)
status : bootloader unlock
frp lock
I'm into that version C432B386
and now im having a trouble here
flashing the original bootloader code
command : fastboot oem unlock xxx-xxxx-xxx
it says : wrong password
failed to write the command
" is it possible to obtain a new bootloader code ?"
i don't know why the boot code changed even though
i use it in unlocking my Bootloader and it succeed
2nd scenario:
when i try to go to developer options and
go to Allow oem unlock
so that i can be able to obtain FRP unlock
but it is greyed out.
" i've read that if you're on Nougat and you are already
in unlocked bootlader, you will have this issue "
the possible way of unlocking FRP is relocked the
bootloader first and the OEM UNLOCK option will
come out.
i guess the solution is finding a new Bootloader code
but "how?" does anyone knows this?
3rd scenario: flashing new recovery
( expecting to have administrative rights )
i try to flash also the twrp nougat version
but it says verification error
command : fastboot flash recovery twrp3.1.0-3-eva.img
failed
i don't want to end up bricking my device again
I'm having a hard time to resurrect this and I don't
want to happen it again, I'm busy with my work so
i have to asked you guys, finding a best way how
to fixed this..
if someone is having a same situation like me
please participate on the thread and or someone who
already fixed this kind of issue please give us information . thank you !
oem info / SN rewrite using HCU
You rewrited the serial number? Yeah I don't know how to help you there...
benjamen50 said:
oem info / SN rewrite using HCU
You rewrited the serial number? Yeah I don't know how to help you there...
Click to expand...
Click to collapse
yes sir , there is HCU Client tool that can re-write Serial Number/IMEI / read bootcode
i use it and replaced the missing Serial Number of my device
vinfrix said:
yes sir , there is HCU Client tool that can re-write Serial Number/IMEI / read bootcode
i use it and replaced the missing Serial Number of my device
Click to expand...
Click to collapse
Imo, If you change serial.no then your unlock code would be different
Try relocking and again unlocking the bootloader.
_Frostplexx_ said:
Try relocking and again unlocking the bootloader.
Click to expand...
Click to collapse
i tried to but the code seems already changed.
FiKsTyLeR said:
Imo, If you change serial.no then your unlock code would be different
Click to expand...
Click to collapse
even if i write the same serial code ?
vinfrix said:
i tried to but the code seems already changed.
Click to expand...
Click to collapse
Dude i am in a similar situation.
I have the bootloader unlocked but frp is locked.
When you relocked and unlocked was the OEM unlock option changeable (not grayed out, no FRP LOCK) again?
revery0 said:
Dude i am in a similar situation.
I have the bootloader unlocked but frp is locked.
When you relocked and unlocked was the OEM unlock option changeable (not grayed out, no FRP LOCK) again?
Click to expand...
Click to collapse
yes if you unlock again it will come out
vinfrix said:
yes if you unlock again it will come out
Click to expand...
Click to collapse
As it turns out, you need to rollback to b182 and then upgrade to N through OTA.
dload b300
dload b182
OTA b386
OEM Unlock, ADB Debugging, USB Debugging
Unlock bootloader
twrp
revery0 said:
As it turns out, you need to rollback to b182 and then upgrade to N through OTA.
dload b300
dload b182
OTA b386
OEM Unlock, ADB Debugging, USB Debugging
Unlock bootloader
twrp
Click to expand...
Click to collapse
why should i rollback ?
Subj.
Yes. We can do OEM Unlock - that is nice ...
but are that is possible to make reset to initial state ?
OEM-Locked ... with original firmware with slider in Locked position
or that Unlock act similar as Samsung-Knox? - one time fuse, and that can be treaten as warranty-void related ...
i'm on Current version A.22 @RMX3085
DaLiV said:
Subj.
Yes. We can do OEM Unlock - that is nice ...
but are that is possible to make reset to initial state ?
OEM-Locked ... with original firmware with slider in Locked position
or that Unlock act similar as Samsung-Knox? - one time fuse, and that can be treaten as warranty-void related ...
i'm on Current version A.22 @RMX3085
Click to expand...
Click to collapse
You can lock bootloader if you unlocked it. But if you root your phone and do modifications you have to flash the whole firmware with sp flash tool.