Hi,
I made a different thread to find a solution about this error I got when I try to flash the Androkernel boot.im and TWRP recovery on my UNLOCKED BOOTLOADER Z4 712 wifi european tablet.
I updated with the Sony PC Companion tool, I DID NOT turn ofn the MySony Security (that was THE problem that caused this error last time), and bootloader is still unlocked (checked with Sony Mobile Flasher).
The service mode say "root:unknow", in previous tablets/room it should say "bootloader locked or unlocked", but I'm not sure.
That's what I got when I tri to flash boot.img:
C:\>fastboot flash boot boot.img
sending 'boot' (32584 KB)...
OKAY [ 1.633s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 2.150s
Click to expand...
Click to collapse
Thank you for the help
Diomorgan said:
Hi,
I made a different thread to find a solution about this error I got when I try to flash the Androkernel boot.im and TWRP recovery on my UNLOCKED BOOTLOADER Z4 712 wifi european tablet.
I updated with the Sony PC Companion tool, I DID NOT turn ofn the MySony Security (that was THE problem that caused this error last time), and bootloader is still unlocked (checked with Sony Mobile Flasher).
The service mode say "root:unknow", in previous tablets/room it should say "bootloader locked or unlocked", but I'm not sure.
That's what I got when I tri to flash boot.img:
Thank you for the help
Click to expand...
Click to collapse
First of all it's not polite to create new thread in android development part. Here should be only roms, fixes, patches recoveries. Not q&a threads.
As to your problem, are you sure that you've unlocked bootloader? In service menu you should see
"Rooting status:
Boot loader unlocked: Yes"
if you doesn't see it, it means you haven't unlocked it or unlocking is not allowed on your device.
Diomorgan said:
Hi,
I made a different thread to find a solution about this error I got when I try to flash the Androkernel boot.im and TWRP recovery on my UNLOCKED BOOTLOADER Z4 712 wifi european tablet.
I updated with the Sony PC Companion tool, I DID NOT turn ofn the MySony Security (that was THE problem that caused this error last time), and bootloader is still unlocked (checked with Sony Mobile Flasher).
The service mode say "root:unknow", in previous tablets/room it should say "bootloader locked or unlocked", but I'm not sure.
That's what I got when I tri to flash boot.img:
Thank you for the help
Click to expand...
Click to collapse
Hi,
I think the problem is here if you enable myXperia before or after unlocking the bootloader ( can be @AndroPlus can explain better the problem ?)
Verify that your USB drivers for fastboot and adb are correcctly installed (install the USB drivers provided with Flashtool)
I hope you can root your tablet again :good:
I'm very sorry if I opened the thread here, feel free to close or move it, but I found it related the modding and , actually, in installing the androplus kernel.
As I said I did not turn on the sony security nor befor nor after, root status is "unknown", Flas Tool say is't unlocked, I already flashed the androkernel before and the problem was the MySony security, but now I know I don't have to turn it on.
Drivers are Ok, I flashed the new rom with Flash tool and then with Sony Companion.
Anyhow, if I'm bothering with this thread pleas close it, al try again and again
I think it's okey moderators will move the thread over.
Did you unlock your tablet by flashtool or follow official Sony instructions?
Do you have myxperia app installed?
Have you got factory reset after unlocking?
killdozer56 said:
Hi,
I think the problem is here if you enable myXperia before or after unlocking the bootloader ( can be @AndroPlus can explain better the problem ?)
Verify that your USB drivers for fastboot and adb are correcctly installed (install the USB drivers provided with Flashtool)
I hope you can root your tablet again :good:
Click to expand...
Click to collapse
alex009988 said:
I think it's okey moderators will move the thread over.
Did you unlock your tablet by flashtool or follow official Sony instructions? Official sony on previous firmware and flashtool say i'ts unloked
Do you have myxperia app installed? yes, but it's not enabled! Actually it's not an app, but an option in "security" menu.
Have you got factory reset after unlocking?
Click to expand...
Click to collapse
yes, I reinstalled the new rom with flashtool then with Sony Companion and root status is "unknown".I can try reflashing it tomorrow.maybe someway I got stuck in a unknow situation between locked and unlocked X-(
farfetch has beaten the same topic here to death.
same style:
many threads (unrelated to his topic)
look it up - it is not easy because of this
you will not like what you read:
you have bricked your tablet with enabling myXperia after unlocking the BL
DHGE said:
farfetch has beaten the same topic here to death.
same style:
many threads (unrelated to his topic)
look it up - it is not easy because of this
you will not like what you read:
you have bricked your tablet with enabling myXperia after unlocking the BL
Click to expand...
Click to collapse
First of all, I don't really understand how he was able to update something via pc companion with unlocked bootloader?
No ota update, nor update via pc companion is available after unlocking.
DHGE will we have the same? I mean when android MM will be released, we flash it and will it be with myxperia? And if we launch it by accident we break our tablet, right? In this case, how to remove it, factory reset?
alex009988 said:
First of all, I don't really understand how he was able to update something via pc companion with unlocked bootloader?
No ota update, nor update via pc companion is available after unlocking.
DHGE will we have the same? I mean when android MM will be released, we flash it and will it be with myxperia? And if we launch it by accident we break our tablet, right? In this case, how to remove it, factory reset?
Click to expand...
Click to collapse
I read about a guy thoblem because after updating with Companion bootloader was relocked, he unlocked again and so.
Anyhow,I just NOT UPDATED, but RESTORE/REFRESH the firmware flashed with Flashbout a bad flash with Flashtool. Immediately after the flash with compsnion,even without turning on the phone, I try and I got the same FAILED (remote: Command not allowed)
:crying:
I even relocked and reunlocked bootloader with Flashtool (didn't even know it's possible to relocked...).Thi lost :-/
UPDATE: I found that myxperia was administrator even if I didn't turn it on, so I remove from administrators, but....same problem
Maybe it's better to try to unlock bootloader again following official Sony instructions, not flashtool? WITH flashtool unlocking, you haven't got a factory reset, that's the reason of all your problems IMHO.
After unlocking my xperia must disappear.
alex009988 said:
I mean when android MM will be released, we flash it and will it be with myxperia?
And if we launch it by accident we break our tablet, right?
In this case, how to remove it, factory reset?
Click to expand...
Click to collapse
SONY thinks MyXperia is a useful feature security wise and I agree. It is just not for me since it prevents my tampering with the device.
I am sure it will be in MM.
You have to launch it explicitly on setup! SONY warns in the bootloader instructions to activate it after unlocking.
Once activated after unlocking the tablet is bricked. End of discussion, beaten to death in the xperia fora....
If a factory reset could revive the devices this would be no security feature but rather an annoyance for thieves.
DHGE said:
SONY thinks MyXperia is a useful feature security wise and I agree. It is just not for me since it prevents my tampering with the device.
I am sure it will be in MM.
You have to launch it explicitly on setup! SONY warns in the bootloader instructions to activate it after unlocking.
Once activated after unlocking the tablet is bricked. End of discussion, beaten to death in the xperia fora....
If a factory reset could revive the devices this would be no security feature but rather an annoyance for thieves.
Click to expand...
Click to collapse
I completely agree with what @DHGE said this is a no sense if a thief can reset the tablet with a factory reset once MyXperia has been activated. MyXepria operates at a low level, also be able to deactivate it easily is not possible.
:crying:
Oh my God.I haven't known it. http://fxpblog.co/2015/07/03/dont-destroy-your-unlocked-device.html poor people. Indeed, with unlocked bootloader and enabled myxperia, people get tea-tray instead of working device. And it's unrecoverable.
If nevertheless icon of my xperia will appear in a menu of new MM. Can I delete it with some kind of system-app-uninstaller ?
Edit 1. This damned app was in my system, so I used "Uninstall" app and remove my xperia, wiped dalvik and cash.
I strongly recommend it everybody to keep your device safe and don't worry incidental pressing.Better delete it!!!
I activated myxperia with unlockebootloader and I have no problem, can't be able to unactivate it, when I reflash the ro if activate it or not and I can remove administrator priviledge in security section.
If I clickif I want to turn it on and sony says that "if turned on"repair the firmware but will be "unusable" till you imput your google account saved for the my'm UNLOCKED I try turning on myxperia a few days ago to an disable it later (no ways, my xperia has only a blank page without settings), then I reflashed 2 times and both time it asked me if I to turn on the myxperia.I even try with flashtools to chek the bootloader, relock and reunlock and everything wly problem is flashing things via fastboot!
Related
few questions about using the unlocker, whilst using the qsd8250 _semc and qsd8250_setool2,
does the phone have to be in flash mode or just connected to pc via usb with usb debugging enabled??
also im gettin adb server is out of date killing...
*daemon started successfully*
getting that every second line or so, is that normal, also it completes the process up until the part where it reboots the phone, then on the pc it saying getting root rights and nothing happens from there???
any help greatly appreciated
follow the unlock instructions fully, if it worked you should lose the "sony" test that happens just after you power on. If not, look for the BL tool in dev section, this will make life easier.
And close flashtool when you do.
[email protected] said:
follow the unlock instructions fully, if it worked you should lose the "sony" test that happens just after you power on. If not, look for the BL tool in dev section, this will make life easier.
Click to expand...
Click to collapse
i was told the sony ericsson logo would only dissappear if i flashed a new ernel, so i did, now i have no signal, and ive tried to reset through seus done everything i can think of
[email protected] said:
i was told the sony ericsson logo would only dissappear if i flashed a new ernel, so i did, now i have no signal, and ive tried to reset through seus done everything i can think of
Click to expand...
Click to collapse
Did you unlock your phone by chance? A in sim unlock to use it on another network? If you did, then you will lose radio signal if it wasn't done with SETOOL.
Dark Nightmare said:
Did you unlock your phone by chance? A in sim unlock to use it on another network? If you did, then you will lose radio signal if it wasn't done with SETOOL.
Click to expand...
Click to collapse
i ran the test to mae sure i had semc certificate, which i did, so i proceeded with unlock
[email protected] said:
i ran the test to mae sure i had semc certificate, which i did, so i proceeded with unlock
Click to expand...
Click to collapse
After unlocking, you need to flash DoomLord's special custom kernel or sony's very own via flashtool. Could be that or simply flash backs stock and retry unlocking. Possibly failed.
well ive managed to get radio working again, had to go bac to 2.1, then a custom 2.2 rom so i could crash system server, then unlock bootloader again, so all is working now, but now i cant root for some reason
mods please close this thread now problem is solved
i was trying to follow this thread (http://forum.xda-developers.com/showthread.php?t=1285285) to unlock my sk17i. i'm pretty sure i did the right thing at first, but during "PROCESSING … REMOVE TESTPOINT NOW, THEN PRESS "READY"" part, i removed the USB instead of just the test point.
now the problem is nothing happens anymore after i click Ready (after connecting the test point) when i try to Patch SECMBoot.
i tried the RESTORE but it said 'nothing to restore'
is there any way to solve this? or maybe reset the process i abandoned before?
Well,does your phone still can be turn on?If no,use wotanserver,and try to unlock it again...
yes it can still be turn on. everything is still normal.
i have looked through wotanserver before posting this, but hesitated to use it. can i just unlock my phone using it and without installing their firmwares?
and it said
Beside unlocking removes Invalid SIM Card or SIM network unlock PIN screens and allows you to use your phone with different network SIM card – unlocking is NOT supported by WotanClient software!
Click to expand...
Click to collapse
done it.
instead of connecting testpoint to USB (which i did before), i connected test point to ground-negative connector of the battery.
now i have unlocked the device.
but sadly i used wotanserver and my phone is back to stock -_-"
thanks.
@hizperion
just a question sir, why are you trying to unlock bootloader?
if you have done it already thru test point that should be it.
this would allow you to use fastboot on your phone to install custom kernel.
flashing thru wotan would definitely lead to stock since that is what it does...
melander said:
@hizperion
just a question sir, why are you trying to unlock bootloader?
if you have done it already thru test point that should be it.
this would allow you to use fastboot on your phone to install custom kernel.
flashing thru wotan would definitely lead to stock since that is what it does...
Click to expand...
Click to collapse
the unlocking thru test point at the first time didn't work, because i plugged the USB out during the process. so it kinda stuck at some point (it seems like its already unlocked, but actually not yet). i tried to flash using fastboot but nothing happened too.
just check service menu.
if it states "bootloader unlocked : yes" then it is already unlocked.
if it states "bootloader unlock allowed :yes" then it is still locked.
melander said:
just check service menu.
if it states "bootloader unlocked : yes" then it is already unlocked.
if it states "bootloader unlock allowed :yes" then it is still locked.
Click to expand...
Click to collapse
well in that case, it was still locked
but i couldn't unlocked it anymore by connecting the testpoint to USB
connecting the testpoint to ground of the battery solved it, as mentioned above
Hi everybody! I'm new at this forum, i come from xperia x8 forum, and I have problems with custom kernels. I have a xperia Neo V, and I just cant connect the phone in fastboot mode. I'm not sure if it is properly bootloader-unlocked, as in the oficial sony's webpage it said that cdma devices cannot be unlocked (check http://unlockbootloader.sonymobile.com/), and I think that is the standard in Europe isn't it? (I'm from spain). Also, I checked the service menu and it also indicates that the bootloader cannot be unlocked.
Anyway i tried through the testpin-s1 tool method and everything seemed to work fine, i got the output with the two lowercase "r", but not the messages showing the model, software version, custom version, filesystem version and serial number, as said in vimjam's guide (check the post regarding unlock BL here: http://forum.xda-developers.com/showthread.php?t=1409269).
When I try to connect it in fastboot mode it just shows the sony ericsson logo and starts to charge, not showing any blue led. I know that this happens in locked devices, but the two lowecase "r" in s1 tool indicate that it is unlocked, so i dont understand... Can someone tell me if my phone is properly unlocked, or if custom kernels can be flashed connecting the device in flash mode (as it does work for me)? Thanks in advance
Eventhough your bootloader is now unlocked, your fastboot is still locked, you have sim-locked phone and you need to pay to unlock it.
ok, so you mean I have to sim-unlock my phone in adition to bl-unlock to connect it in fastboot mode? can this be done in wotanserver or i have to take it to some tech service?
danygarss said:
ok, so you mean I have to sim-unlock my phone in adition to bl-unlock to connect it in fastboot mode? can this be done in wotanserver or i have to take it to some tech service?
Click to expand...
Click to collapse
Yes, you can use wotanserver.
Madfysh said:
Yes, you can use wotanserver.
Click to expand...
Click to collapse
Hi,I managed to unlock my bootloader using msm7227_semc.cmd method.However when I tried to enter fastboot I couldnt
as my sim was locked.I paid for unlock via S1 tool and now have an unloked phone.However when I identify the phone to check
the status of the bootloader I only get one r "Look For Line RUNNING S1_EROM VER "r8A029" but the loader version has a
R .Is my bootloader still unlocked? I have tried getting into fastboot mode but nothing seems to happen.Can you please guide me?
Thanks for reading .Your reply is much appreciated.
Hello XDA Community
I have had my Sony Xperia Z ultra Since last year and i've never been able to Unlock the Bootloader...whenever i've tried it just doesn't work almost makes me not want the device as i cant stand the stock Sony Xperia UI.
First off the normal method ive tried just never works
UNLOCKING THE BOOTLOADER:
This may wipe your phone, so backup your stuff
• Go to Sony's dev site
• Request the unlock key and check your mail straight away. Email is quick these days.
• Open Flashtool on your computer (yes, the one you installed earlier)
• Click the "BLU" icon
• Follow the steps and enter your unlock key
Quick note...If i type *#*#7378423#*#* into the keypad and continue the steps i get to the Service info > Configuration > Rooting Status. If Bootloader unlock allowed and its always said Bootloader not allowed...now i don't know if that means anything or with a bit of hope ill still be able to Unlock my Phone...
My phone is a contract phone with o2 here in the uk and even trying to return the phone is impossible as they tell me all the time are you asking to unlock the device for use with a different network
I've done my best to explain to them no its the bootloader and they tell me i shouldn't be messing with the device etc etc etc etc.....
anyways theres no way of convincing them and am stuck with this exact phone...i dunno what else to do if even trying to unlock bootloader will ever work for me
" If Bootloader unlock allowed and its always said Bootloader not allowed."
Thats the problem.
You could look at installing a theme or maybe monx's ROM
blueether said:
" If Bootloader unlock allowed and its always said Bootloader not allowed."
Thats the problem.
You could look at installing a theme or maybe monx's ROM
Click to expand...
Click to collapse
This means that your bootloader is unlockable from the factory. There's no work around for this.
Sent from my C6833 using XDA Premium 4 mobile app
Hi guys, so I seem to have scewed up my phone quite badly. I tried to deodex running the new nougat firmware (with drm-fix and ric-off) by flashing a zip in the nougat firmware thread. Somehow I ended up with not being able to fastboot anymore.
I found out that my bootloader seems to be locked again. Thus I am not able to approach the fastboot mode, but failed to do any flash, as it says [FAILED (remote: not allowed)].
I checked the service menu and found the [Bootloader unlock allowed:no] and [Remote Lock State: Locked] after reflashing the nougat firmware.
So I wanted to unlock the device, how ever I ended up with flashing back to Lollipop and the device boots and then power off after a few seconds of use.
Could this due to "remote lock state: not allowed"?
Try relocking via flashtool?
So. Tried to lock and relock via flashtool. Checked drivers which are working fine.
I was trying to relock and then unlock again using flashtool after updating to .305 Marshmallow firmware . However this does nothing to the bootloader states. The weird thing is that there are no errors showing up in flashtool when unlocking/relocking. I can't even unlock via OEM because when I tick OEM unlock in the developer options this doesn't do any change (Rooting status: Bootloader unlock allowed : No, Remote Lock State: Locked). My DRM keys are gone as well. However I do have a TA Backup but can't restore because after downgrading to lollipop the device shuts down after 30 seconds.
I'm really annoyed because I bought the device with an locked bootloader (without carrier costumizations) and unlocked it via OEM unlock then updated to . Is there any chance to unlock the device again? Restore TA? Any recommendations what I could have done wrong would be helpful.
iArvee said:
Try relocking via flashtool?
Click to expand...
Click to collapse
[solved ] Bootloader is now sucessfully relocked andBootloader states are back to [Bootloader unlock allowed: Yes] and [Remote Lock State: UnLocked].
I need to mention that I bought a phone without carrier lock with [Bootloader unlock allowed: Yes].
So, for anyone who is interested or might face the issue in the future, here's what I did.
You will need your backed up TA-Partition-Image to restore via iovyroot:
1. Downgrade to Lollipop (32.0.A.6.200 / R2B (STOREFRONT GENERIC)) using Flashtool .
->Therfore select/tick everything in the wipe section when selecting the Lollipop-tft
2. Unmount your SIM, reboot the device
3. Skip everything on the welcome/configuration screen as fast as you can to get beyond the Android configuration screen
(skip wif config, Google-Account setup, untick myXperia services! etc.)
The phone might power off only after a few seconds because of the downgrade. So be fast!!!
4. Once you end up on the home screen, unlock developer options, and activate ADB debugging, grant ADB access (check via cmd: fastboot devices)
again: be fast! --> Don't worry if the phone shuts down again. Just reboot if you were not fast enough.
5. Download iovy.root ( iovy.root. Place TA-backup.img in the iovyroot-folder.
Then I modified "tarestore. bat" to save some time regarding the shutdowns. I used notepad++:
...
set response=
set /p response=Type "y" if you want to restore this file:
if "%response%" == "y" (
echo Starting restore
echo.
adb push "root/iovyroot" "/data/local/tmp/iovyroot" > NUL 2> NUL
adb push "root/restore.sh" "/data/local/tmp/restore.sh" > NUL 2> NUL
...
5. Run CMD as admin. CD to Iovyroot folder.
Restore using tarestore.bat (tarestore.bat TA-2016-xxx.img) as soon as your device boots up to home screen and seems to be connected as ADB device.
( I checked this by running the windows device manager simultaniously)
Wait to end the process.
-->When the restore was sucessfull, the device shouldn't shutdown again.
6. Reboot. Your bootloader is now locked again (but able to unlock via OEM unlock). DRM keys/functionality is restored.
I have the same problem (after i had nougat working incl drm fix and root, also the deodex, tried flashing lower ftf files too when i got this problem, noticed the rebooting, which it does not do at 305 kernel or higher..
I would have hope in your solution, if I could find my ta backups (i have from some other phones, this one, may have been on a crashed laptop, already searched through old hdds)
Could this be because of fastboot flash recovery twrp.img (cause that is something i never done before on the z5c.)
If anyone has a solution other than restoring the ta partition, i would like to know. Because i am very uncertain that i can find those files again...
Same case here z5c unlocked since +/- 1 year and I don't have any TAbackup too
I will try to downgrade to .200 But with bootloader unlock allowed : no ... I don't have much hope
edit : no chance, I tried .200 but without tabackup, I can't do nothing
When I faced this problem I noticed it happened because I wiped TA options with Flashtool. Never do that if you don't want to lose TA partition and all other things connected to it. I could fix it only by flashing TA backup even though I hadn't the timing issue zegovernator had for flashing back TA.
I actually wonder why Flashtool allows to wipe these critical partitions/options
ric69 said:
Same case here z5c unlocked since +/- 1 year and I don't have any TAbackup too
I will try to downgrade to .200 But with bootloader unlock allowed : no ... I don't have much hope
edit : no chance, I tried .200 but without tabackup, I can't do nothing
Click to expand...
Click to collapse
I'm sorry for you. I would recommend updating back to MM since LP gives you immediate shut downs when recognising that your TA is lost/wiped. It's sometime a pain in the ass that stuff gets posted before testing. Nonetheless, you could still try to send in your device back to Sony Costumer Service if you are under warranty (after flashing .200, say that it is "broken" and keeps crashing). However, I would not trust on them sending you a new device.
jutphaas said:
I have the same problem (after i had nougat working incl drm fix and root, also the deodex, tried flashing lower ftf files too when i got this problem, noticed the rebooting, which it does not do at 305 kernel or higher..
I would have hope in your solution, if I could find my ta backups (i have from some other phones, this one, may have been on a crashed laptop, already searched through old hdds)
Could this be because of fastboot flash recovery twrp.img (cause that is something i never done before on the z5c.)
If anyone has a solution other than restoring the ta partition, i would like to know. Because i am very uncertain that i can find those files again...
Click to expand...
Click to collapse
I sorry to say that, but if you lost your TA-backup or didn't even back it up before unlocking the bootloader there is no hope at the moment. You simply can't fastboot because of the Remote State: Locked. It keeps you from accessing the bootloader.
I found my iovyroot TA-backup.img file, I did have a .200 storefront ftf and tried it on that one, which was very anoying as it wants to start a demo , i found an other .200 ftf online which I tried, and the iovyroot seems to work, at that time no reboot, in service menu, the drm keys now seem fine there, Bootloader unlock allowed : No, Remote Lock State: unLocked , fastboot boot or oem unlock still seemed not working well i think that is what it said, (flashtool unlock always seems to, i did try) now i flash a new ftf and try my luck there with the unlock status.
flashing ftf 5.11 flashtool says
03/005/2017 05:05:49 - INFO - Loader : S1_Root_f936 - Version : MSM8994_50 / Boot version : S1_Boot_MSM8994_LA1.2_119 / Bootloader status : ROOTED
And now in 5.11 it also says bootloader unlocked : Yes Lost my drm again
So I am back in flashing and rooting (with drmfix etc) Android 7 again Thanks for sharing this solution!!
So you confirm that TA backup is the only solution to solve the "unlock allowed" bad state, don't you?
This is good for other people because when I faced the problem I was really scared to have messed up my phone!!!
i want to confirm the solution here
i had the same problem and the only way back of it was to downgrade to Lollipop and restore the TA-Partition
i dont think there is a solution if you did not backup your TA and have an image of it.
Yes, the TA restore is the only known solution, and I am glad Zegovernator shared his solution here