Hey guys, sorry for my bad english.
Guys, could someone help me? I was following the procedures to install a custom ROM, and when I use to unlock the bootloader Freegee gave a message: "sorry your version is not currently supported software." Asked for upload the boot image and when did the problem persists. If there is someone with the same problem, please help me.
Remembering that not bricked my cell, not only completed the bootloader, which is essential for using the custom rom.
-
# edit
Now the problem is another. When I tried to install the bootloader as I said above, I went with. Apk I saw a tutorial that passed me. It did not work as reported. Now tried with the PlayStore, busybox installed and executed normally. However, when I went to "unlock" there was no such option. Instead this was "re-lock", as if the bootloader was already unlocked, just not realized any unlock procedure. Could anyone help me with this problem? Appreciate.
Related
Hi all,
I've got the Sony Xperia S and unlocked the bootloader and rooted it once and flashed it with the AOKP, but that didn't work, so I tried the Cyanogenmod 10.0 (Jelly Bean). In summary I think it was the wrong Combination of kernel and custom rom, because it didnt boot anymore and got stuck at the logo.
So I closed the bootloader again and installed the official stock rom from Sony, and all got fine, luckily.
With some more reading into right forums and better knowledge I got the right custom rom and kernel and tried to unlock the bootloader again, but suddenly it didnt work.
Message: Failed (remote: oem unlock 0xF (und noch mehr F) )
I did all with fastboot and the right adb drivers, the phone is installed correctly.
Yesterday I asked for my problem in a shop and the guy said, that the bootloader of any Sony device would close completely, if the (right or wrong) unlock code is used for too many times (like the limit of 10 times).
If he's right, I've got a big problem. But can't I open it with an alternatvie method? Or is there just any mistake?
Thanks for any answer
Chriszo
i dont know, but ive already relocked and unlocked many times without error ,
try to do it again and be sure to input the correct 0xKEY
CM10 contains it's own kernel so could never be a wrong combination of rom and kernel. Did you actually unlock the bootloader or just root the phone? Sounds like your bootloader was locked and you were trying to flash still
Sent from my 4.2.2 Xperia S via Tapatalk
Thanks for the answers.
I don't still know what constellation I really tried to instal the kernel and firmware, but I think it was an advanced stock kernel and then the firmware of the aokp. After that I tried the Cyanogenmod, but the device just didnt boot, there was only the logo.
I remember to have taken the kernel named ics17.elf and the advanced stock kernel with the official 4.0.55 build number.
The the device was rooted and the "sd card" was not wiped, but the data of the apps were deleted.
So the bootloader was open because the kernel can't be flashed with a locked bootloader.
After that I flashed the aokp and then the cyanogen mod.
Because of no booting I relocked the bootloader and installed the official firmware from sony.
Since then I try to unlock the bootloader with this damn error
I try to unlock with another computer. Maybe it work and its a simple solution. To unlock my bootloader i need to use my wife´s laptop.... i try in my compputer many times, install drivers, uninstall, and a lot of tricks but fastboot give me "error" all the times... lol
I just chatted and called with the Sony support (nice to hear great english at the phone ) and again got to hear, that they aren't able or allowed to give any information about the bootloader because of the possibility to loose the warranty of the phone.
I dont know really where my problem is but I think the code is not working any more, although I cant imagine of that
Is there any other way to do that? Or do I just do a stupid mistake ???
Thanks
Chris
Chriszo said:
I just chatted and called with the Sony support (nice to hear great english at the phone ) and again got to hear, that they aren't able or allowed to give any information about the bootloader because of the possibility to loose the warranty of the phone.
I dont know really where my problem is but I think the code is not working any more, although I cant imagine of that
Is there any other way to do that? Or do I just do a stupid mistake ???
Thanks
Chris
Click to expand...
Click to collapse
No no no!
Another guy on xda did it with FlashTool on locked bootloader. I was able to do it until the logo...
Apparently you only can flash roms I think, not?
Anyway Sony supports Open Developer Community as well, they give you info about bootloader here:
unlockbootloader.sonymobile[dot]com
No, I cant flash any rom, therefore I need an unlocked bl. And the stock rom from sony isnt available in the internet, just with the Sony-mobile-update-service.
Well, of course I tried the way Sony dicribes on this webside, as explained below -.-
Got the solution ??
Hey I have the same exact problem and i did the same things as you did ... did get a solution?? please inform me if you did.....
Hello all
I recently unlocked my phone and installed the viper ROM using twrp. It worked successfully. I then re-locked it to get the fingerprint scanner functionality back. After that I tried to unlock it again to add some of the audio mods. At this point my phone would not boot all the way. I was stuck between the bootloader and download mode after running the unlock command. This after only having the phone 5 days..lol. I managed to get the stock ruu from the htc site and reflashed it back to stock. It now works except I cant unlock it again. I am getting the 35 RU_PARTITION_NOT_SUPPORT unlocker error message after uploading the Unlock_code.bin. Has anyone seen this and/or figured it out? My apologies if this is the wrong area to post this. I am new here. Thanks for the help!
Edit:
Tried multiple unlock keys from HTC
Tried factory reset
Booting into recovery phone image comes up with red warning icon in it and nothing happens. Need to power down and restart. Seems the recovery partition is possibly hosed.
Dissectional said:
Hello all
I recently unlocked my phone and installed the viper ROM using twrp. It worked successfully. I then re-locked it to get the fingerprint scanner functionality back. After that I tried to unlock it again to add some of the audio mods. At this point my phone would not boot all the way. I was stuck between the bootloader and download mode after running the unlock command. This after only having the phone 5 days..lol. I managed to get the stock ruu from the htc site and reflashed it back to stock. It now works except I cant unlock it again. I am getting the 35 RU_PARTITION_NOT_SUPPORT unlocker error message after uploading the Unlock_code.bin. Has anyone seen this and/or figured it out? My apologies if this is the wrong area to post this. I am new here. Thanks for the help!
Click to expand...
Click to collapse
tried requesting for new unlock key from htc dev?
also you don't need to relock for enabling fingerprint scanner...
SacredDeviL666 said:
tried requesting for new unlock key from htc dev?
also you don't need to relock for enabling fingerprint scanner...
Click to expand...
Click to collapse
Yes. I tried a new unlock key. I even contacted htc support but they didnt want to help seeing as how my phone now works. As for the fingerprint scanner. I saw no options for it in viper and from what I searched a few sites said the fingerprint scanner was disabled in unlocked mode. But I will keep that in mind if I ever get past this. I should add also..my phone doesnt say LOCKED or UNLOCKED either. It says RELOCKED on top. Never saw that before either.
Thanks for the reply!
Dissectional said:
Yes. I tried a new unlock key. I even contacted htc support but they didnt want to help seeing as how my phone now works. As for the fingerprint scanner. I saw no options for it in viper and from what I searched a few sites said the fingerprint scanner was disabled in unlocked mode. But I will keep that in mind if I ever get past this. I should add also..my phone doesnt say LOCKED or UNLOCKED either. It says RELOCKED on top. Never saw that before either.
Thanks for the reply!
Click to expand...
Click to collapse
I haven't heard of the fingerprint scanner not working after the HTC One Max disabled it with a unlocked bootloader.
The fingerprint scanner on the 10 will work just fine with a unlocked bootloader, you should beable to unlock again to get rid of the relock if you want too
afuller42 said:
I haven't heard of the fingerprint scanner not working after the HTC One Max disabled it with a unlocked bootloader.
The fingerprint scanner on the 10 will work just fine with a unlocked bootloader, you should beable to unlock again to get rid of the relock if you want too
Click to expand...
Click to collapse
You may be right about the fingerprint scanner. I will look into that when I get it unlocked. That is the main goal right now.
If you are s-OFF the phone will show as "s-off, locked" but still, in fact, be unlocked.
the command to lock and unlock will not work.
I was confused to but when i checked the s-off thread i saw that it will ask if it should be "s-off unlocked or "s-off locked" and recomended Locked, but had no difference other then visual.
---------- Post added at 08:31 AM ---------- Previous post was at 08:30 AM ----------
And btw, lock status should not affect the fingerprint scanner.
Confirmed it doesn't I am s-0ff and unlocked, twrp and custom rom. Fingerprint working 100%
the exclamation on booting to recovery just indicates that you are on stock recovery...
try the steps here for recovery flashing... and unlocking again... if it might help... http://forum.xda-developers.com/showpost.php?p=66713447&postcount=1
You could try contacting Scotty, might have a way like on previous devices to lock/unlock your bootloader without htcdev.com once S-OFF (DO NOT use the codes for M7 M8 or M9)
http://forum.xda-developers.com/showthread.php?t=2470340
Shouldn't this work?
fastboot oem unlock
Are your developer options enabled right now. And did you check the box to allow bootloader unlock again?
Sent from my HTC 10 using XDA Labs
Some luck
Well.. First off I must say thanks for the reply's so far. Secondly I must apollogize... I have things working (unlocked, rooted and runing viper one) but my solution was a rather odd one.
After trying a few things suggested I went back and just tried reflashing the Unlock.bin. For whatever reason it worked this time after numerous fails mostly involving the dreaded error message found in the title of the post. I then tried to flash twrp but all attempts yielded the error: FAILED (remote: cannot flash this partition in s-on state. Which sucks because I cant get S-off without being root that I am aware of. For whatever reason I set up the tools (fastboot and adb) in another folder and voila! it worked! I am assuming this was also the issue with the Unlock.bin as well as I had switched to another folder at that time as well. Any ideas why that is? Just curious.
Well I am off to enjoy my tweaking (my phone that is)
Happy modding! And thanks for the help!
Dissectional said:
Well.. First off I must say thanks for the reply's so far. Secondly I must apollogize... I have things working (unlocked, rooted and runing viper one) but my solution was a rather odd one.
After trying a few things suggested I went back and just tried reflashing the Unlock.bin. For whatever reason it worked this time after numerous fails mostly involving the dreaded error message found in the title of the post. I then tried to flash twrp but all attempts yielded the error: FAILED (remote: cannot flash this partition in s-on state. Which sucks because I cant get S-off without being root that I am aware of. For whatever reason I set up the tools (fastboot and adb) in another folder and voila! it worked! I am assuming this was also the issue with the Unlock.bin as well as I had switched to another folder at that time as well. Any ideas why that is? Just curious.
Well I am off to enjoy my tweaking (my phone that is)
Happy modding! And thanks for the help!
Click to expand...
Click to collapse
glad its sorted for you and back to flashaholic mode
Dissectional said:
Well.. First off I must say thanks for the reply's so far. Secondly I must apollogize... I have things working (unlocked, rooted and runing viper one) but my solution was a rather odd one.
After trying a few things suggested I went back and just tried reflashing the Unlock.bin. For whatever reason it worked this time after numerous fails mostly involving the dreaded error message found in the title of the post. I then tried to flash twrp but all attempts yielded the error: FAILED (remote: cannot flash this partition in s-on state. Which sucks because I cant get S-off without being root that I am aware of. For whatever reason I set up the tools (fastboot and adb) in another folder and voila! it worked! I am assuming this was also the issue with the Unlock.bin as well as I had switched to another folder at that time as well. Any ideas why that is? Just curious.
Well I am off to enjoy my tweaking (my phone that is)
Happy modding! And thanks for the help!
Click to expand...
Click to collapse
Sounds like your Environmental PATH is set to just that one folder.
Windows?
There's some good threads here on XDA,
http://forum.xda-developers.com/showthread.php?t=1161776
Glad you got it working though!
hey guys, i need a little help here, i am trying to downgrade my firmware to .200 but my z5p keeps getting stuck in a boot loop and i have no idea how to proceed. I saw another thread with another user having similar issue but the solution offered didnt work for me, any help is appreciated. scratch that something worked...
now im getting "command not allowed" when i try to unlock bootloader, any help is appreciated
scratch that too, i did nto turn on oem unlock
Hi, my carrier purchased 'Lisa' came with its ROM showing as version RKOEUBY.
My carrier isn't keeping up with updates so was wondering if I can just flash the ROM RKOEUXM without unlocking the bootloader?
I have my banking apps etc on this phone so am reluctant to unlock the bootloader unless absolutely necessary.
If anyone else has found an easy way to solve this would be grateful for your feedback.
Many thanks
rockyrobin said:
Hi, my carrier purchased 'Lisa' came with its ROM showing as version RKOEUBY.
My carrier isn't keeping up with updates so was wondering if I can just flash the ROM RKOEUXM without unlocking the bootloader?
I have my banking apps etc on this phone so am reluctant to unlock the bootloader unless absolutely necessary.
If anyone else has found an easy way to solve this would be grateful for your feedback.
Many thanks
Click to expand...
Click to collapse
Hi !
The best way is to download the zip of your European ROM from the Xiaomi site and try to install it from the update utility in your phone's settings. If that doesn't work, you'll have to unlock your bootloader, install the ROM you want with the flash utility, and choose the relock option before the install starts. Then you will be on an official Xiaomi ROM, with your bootloader locked and you will have updates from Xiaomi and no longer from your operator.
Bill
Hi,
I confirm that manually flashing the European ROM does not work (in my case at least), so I am stuck on MIUI 12.5.6 with RKOEUSF ROM.
If anyone finds a way to upgrade to the official version without unlocking the bootloader, and therefore not breaking the warranty, I would be grateful if you could share it.
Thanks
Hi !
From the moment you want to install a new ROM, you have no choice but to unlock your bootloader. You can then reblock it. Afterwards, I don't know if the warranty is impacted because you go through the official unlocking from Xiaomi.
Bill
Thanks Bill,
I've just tried flashing the zip of my ROM and the phone just quits the update after a long pause, saying that it cannot verify update.
Guess I'll have to unlock the bootloader. There's plenty of info about how to do this, but I've noticed a number of people complaining about the flash process.
When they apply the update, at the end they get an error message. The only way they get round this is with an edit of the settings of miflash.
Is this something I need to worry about?
Just been reading about these errors and it appears that they are caused by the path to the ROM file having too many characters.
Placing the ROM file in your C: folder solves this.
Howdy, Y'all! I have a buddy who has a Q7+ that bricked its self during an update. Powering up, the phone goes into fastboot mode. I have tried searching for the stock ROM for it, but all the download links I have found seem to be either expired or no longer working. This Q7+ is from Metro (by T-Mobile). We tried to unlock the boot loader to install a custom ROM but since LG no longer has their dev portal working, this was futile. We also tried with this reversed engineered MTK Tool but that also did not work as it did not pick up the phone. If someone could either help us to unlock the boot loader and get TWRP installed or get us the stock ROM, we would greatly appreciate the assistance. Thank you all so much!