Related
I have an Xperia tablet Z, I've checked the service menu and confirmed that the bootloader unlock allowed value is "Yes".
I've requested and received the unlock key, and following the instructions on http://unlockbootloader.sonymobile.com/instructions.
I've prepared my computer for the process, and can confirm that the device connects to fastboot without issue.
Upon using the fastboot.exe -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXX, I receive the following error:
...
FAILED (remote: Command did not succeed)
finished. total time: 0.035s
What do?
Doc_rockulus said:
I have an Xperia tablet Z, I've checked the service menu and confirmed that the bootloader unlock allowed value is "Yes".
I've requested and received the unlock key, and following the instructions on http://unlockbootloader.sonymobile.com/instructions.
I've prepared my computer for the process, and can confirm that the device connects to fastboot without issue.
Upon using the fastboot.exe -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXX, I receive the following error:
...
FAILED (remote: Command did not succeed)
finished. total time: 0.035s
What do?
Click to expand...
Click to collapse
The unlock code is case sensitive - are you using the right case ?
GretaLewd said:
The unlock code is case sensitive - are you using the right case ?
Click to expand...
Click to collapse
I've copied and pasted it from sony's email, unless it was provided to me in the incorrect case, I doubt that's the issue.
I've worked a way around my task that did not require bootloader unlocking, but any additional assistance would be appreciated.
I've got the same problem with unlocking the bootloader from my Sony Xperia Tablet Z Wifi (SGP312,FW 10.3.1.C.0.136). In service menu there is written, that my device is unlockable, so i get unlock key from sony, but i can't unlock.
When i write in cmd
Code:
fastboot.exe -i 0x0fce getvar version
then i get as result
Code:
version: 0.5
finished. total time: -0.000s
. That's fine.
When i write in cmd
Code:
fastboot.exe -i 0x0fce oem unlock 0xMyKey
where MyKey is the key i received from sony email, then this error returns:
Code:
...
FAILED (remote: Command did not succeed)
finished. total time: 0.031s
I'd like to install Cyanogenmod-ROM and a recovery like clockworkmod. i'm familiar with rooting HTC- and Samsung-Devices, but i got no idea how to unlock this bootloader!
There's a program on this forum I used that unlocks it pretty much for you just gotta give code its called flashtool used it a couple days ago
Sent from my SGP311 using XDA Premium HD app
this is from Sony
http://unlockbootloader.sonymobile.com/
---------- Post added at 09:41 AM ---------- Previous post was at 09:41 AM ----------
this is from Sony
http://unlockbootloader.sonymobile.com/
@ Beastint: Doomlords flashtool doesn't work with FW 10.3.1.C.0.136.
@ MikeViller: yes, that's how i did it
i tried unlocking bootloader with upper and lower case letters in key, but still getting error message.
There is a tool called vroot to root the tablet, but i'd like to unlock the bootloader too, so that i can install CWM -> h t t p : //forum.xda-developers.com/showthread.php?t=2433466
What are the benefits of unlocking the Bootloader ? Sorry for the newbie question am kind of new to Sony
N1NJATH3ORY said:
What are the benefits of unlocking the Bootloader ? Sorry for the newbie question am kind of new to Sony
Click to expand...
Click to collapse
Allowing use of custom kernel needed to use non stock rom ( CM, omni, aosp based roms)
Sorry to jump in on this post but....
I have rooted my SGP321 (Tablet Z 16GB LTE) but I get when I check and enter the code to see if I can unlock my bootloader I get a NO returned
Does this mean there is no way around unlocking it?
Sorry for the questions. (I wish it was as easy as installing ROM's on my HTC One)
Finally bootloader is unlocked!
I sent another email with IDID to Sony instead of serialnumber and the key i received worked to unlock bootloader.
@N345H: i'not sure, but NO seems to be NO
so if we contact sony to get the bootloader unlocked. if anything went wrong after that, can we just relock, and restore the drm key and send it in for warranty? any has any experiences to share?
so if we contact sony to get the bootloader unlocked. if anything went wrong after that, can we just relock, and restore the drm key and send it in for warranty? any has any experiences to share?
I know HTC keeps track of unlocks not sure if Sony does if you were able to restore ta and.go.back to stock I would think it would be ok. Sony is pretty good. I had a xperia arc unlocked had some issues restored and sent it in and they still fixed it no charge
Sent from my C6506 using Tapatalk
xuanphucn said:
so if we contact sony to get the bootloader unlocked. if anything went wrong after that, can we just relock, and restore the drm key and send it in for warranty? any has any experiences to share?
Click to expand...
Click to collapse
I unlocked my drive and read the warnings, and Sony says it depends on your warranty. you should check your own if you have one. Mine is voided. They also mention additional cost for repair for an unlocked device.
Hi all,
As a result of some attempts to restore stock rom for KIWI-UL00. I ended up in a pretty bad state :
1. The phone reboots perpetually.
2. Putting a 64gb sd card with stock rom gets the recovery to 5% and then phone gets into the reboots cycle. I actually do not know if the dload/UPDATE.APP is being picked up or the wrong boot flashed in is kicking in.
3. The phone is unlocked, but as a result of the flashing I got FRP lock??? Here is what I see in fastboot mode on the phone screen:
PHONE is Unlocked
FRP Lock
4. Any attempt to flash in a new BOOT, SYSTEM or RECOVERY with fastboot ends up with error:
./fastboot flash recovery ~/Downloads/split_updata.pl/kiw_ul00_B239_Unicom/RECOVERY.img
target reported max download size of 266338304 bytes
sending 'recovery' (55968 KB)...
OKAY [ 1.768s]
writing 'recovery'...
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (Undefined error: 0))
finished. total time: 1.769s
My thinking is that FRP lock is causing denying fastboot, but have no idea how to remove it. Without being able to flash in the correct stock recovery, I don't think I will be able to install the stock rom ever.
There are a lot of stuff written about FRP lock out there, but they assume working phone. In my case, I only have access to fastboot, not even adb!
Any ideas appreciated,
Thanks.
But u still can get it into fastboot right? Isnt it possible to use adb then to root it and put twrp on it and after that put custom firmware on it to get it booted up properly again. And after that installing a stock image again?
Dafriss said:
But u still can get it into fastboot right? Isnt it possible to use adb then to root it and put twrp on it and after that put custom firmware on it to get it booted up properly again. And after that installing a stock image again?
Click to expand...
Click to collapse
fastboot has very limited capabilities (I guess because of the FRP lock?) Some commands work, like this:
./fastboot oem get-bootinfo
...
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) Root State: ROOT
(bootloader) Bootloader WidevineKey: WidevineKey_VALID
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.011s]
finished. total time: 0.011s
but other like erase or flash fail with the same error.
Do you know how to use ADB when the device is in fastboot mode? I currently get this:
./adb devices
List of devices attached
My thinking is that in order for DB to work the device need to be put in recovery mode, something I cannot achieve.
The only other mode i can put the phone in is by holding the UP and POWER it gets into something that has "eRecovery", but the rest is all in Chinese . There are 3 menus you can select with the volume and power (no screen touch). The first one leads to wifi discovery and but nothing after that. The other two top level menus lead to restart - again they are in Chinese, not sure what they do.
hrstoyanov said:
fastboot has very limited capabilities (I guess because of the FRP lock?) Some commands work, like this:
./fastboot oem get-bootinfo
...
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) Root State: ROOT
(bootloader) Bootloader WidevineKey: WidevineKey_VALID
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.011s]
finished. total time: 0.011s
but other like erase or flash fail with the same error.
Do you know how to use ADB when the device is in fastboot mode? I currently get this:
./adb devices
List of devices attached
My thinking is that in order for DB to work the device need to be put in recovery mode, something I cannot achieve.
The only other mode i can put the phone in is by holding the UP and POWER it gets into something that has "eRecovery", but the rest is all in Chinese . There are 3 menus you can select with the volume and power (no screen touch). The first one leads to wifi discovery and but nothing after that. The other two top level menus lead to restart - again they are in Chinese, not sure what they do.
Click to expand...
Click to collapse
Isnt eRcovery from EMUI itself to save bricked phones? Like booting in new software or something? Maybe there are some video's about it on youtube???
I had some sort of the same issue but never had problems with frp lock before, i actually used a video from xda to get my honor 5x working again. I'll look for the link so you can see if the same steps work for you!
---------- Post added at 01:01 AM ---------- Previous post was at 12:59 AM ----------
Maybe thid will work when you make a walk around the rebooting parts
Dafriss said:
Isnt eRcovery from EMUI itself to save bricked phones? Like booting in new software or something? Maybe there are some video's about it on youtube???
I had some sort of the same issue but never had problems with frp lock before, i actually used a video from xda to get my honor 5x working again. I'll look for the link so you can see if the same steps work for you!
---------- Post added at 01:01 AM ---------- Previous post was at 12:59 AM ----------
Maybe thid will work when you make a walk around the rebooting parts
Click to expand...
Click to collapse
I saw the video, thanks. However, as you noticed in the video, not only phones boot ok, but when in fastboot mode, his phone reads:
Phone Unlocked
FRP Unlocked
When FRP is unlocked you can do all sorts of things with fastboot. I am not that lucky :crying:
hrstoyanov said:
I saw the video, thanks. However, as you noticed in the video, not only phones boot ok, but when in fastboot mode, his phone reads:
Phone Unlocked
FRP Unlocked
When FRP is unlocked you can do all sorts of things with fastboot. I am not that lucky :crying:
Click to expand...
Click to collapse
relax buddy, try dload method with any other version of stock firmware,
and if it doesnt help,
first find a rollback update.app package for your particular variant, first flash it
then , go back to lollipop firmware with the same dload method,.
you should be booted to lollipop firmware,
than, go on to developer options and enable oem unlock option
start from there..
thilak devraj said:
relax buddy, try dload method with any other version of stock firmware,
and if it doesnt help,
first find a rollback update.app package for your particular variant, first flash it
then , go back to lollipop firmware with the same dload method,.
you should be booted to lollipop firmware,
than, go on to developer options and enable oem unlock option
start from there..
Click to expand...
Click to collapse
The problem is that the "dload/update.app on sdcard" method only works if the phone has stock recovery and I blew that one off.
In order to flash in the stock recovery, i need the FRP lock removed, otherwise fastboot gives me the above errors . See my problem?
the eRecovery seems more hopeful. But is all in Chinese. I got to the first step where it finds my wireless network. I put the password for the WIFI
and it starts doing omething, but fails with big red exclamation mark and tones of thing written in chinese...
hrstoyanov said:
The problem is that the "dload/update.app on sdcard" method only works if the phone has stock recovery and I blew that one off.
In order to flash in the stock recovery, i need the FRP lock removed, otherwise fastboot gives me the above errors . See my problem?
the eRecovery seems more hopeful. But is all in Chinese. I got to the first step where it finds my wireless network. I put the password for the WIFI
and it starts doing omething, but fails with big red exclamation mark and tones of thing written in chinese...
Click to expand...
Click to collapse
how could you actually blow up recovery dude??
thilak devraj said:
how could you actually blow up recovery dude??
Click to expand...
Click to collapse
I think I flashed in the wrong HUAWEI recovery image - I used the latest stock rom for KIWI-L24, but my phone is KIWI-UL00.
I would love to be able to put the right one in, but the FRP Lock issue is preventing me. I don't understand how can the phone be unlocked but have a FRP lock??? See the FASTBOOT commands I used in earlier in this thread.
hrstoyanov said:
I think I flashed in the wrong HUAWEI recovery image - I used the latest stock rom for KIWI-L24, but my phone is KIWI-UL00.
I would love to be able to put the right one in, but the FRP Lock issue is preventing me. I don't understand how can the phone be unlocked but have a FRP lock??? See the FASTBOOT commands I used in earlier in this thread.
Click to expand...
Click to collapse
I'm having the same problem since 4months ago. Fed up of trying myself anymore so I Brought it to many phone shops but no one can repair. Might want to consider replacing the Mother board. anyone with solution pls help! Stupid FRP locked
hrstoyanov said:
I think I flashed in the wrong HUAWEI recovery image - I used the latest stock rom for KIWI-L24, but my phone is KIWI-UL00.
I would love to be able to put the right one in, but the FRP Lock issue is preventing me. I don't understand how can the phone be unlocked but have a FRP lock??? See the FASTBOOT commands I used in earlier in this thread.
Click to expand...
Click to collapse
rexaze said:
I'm having the same problem since 4months ago. Fed up of trying myself anymore so I Brought it to many phone shops but no one can repair. Might want to consider replacing the Mother board. anyone with solution pls help! Stupid FRP locked
Click to expand...
Click to collapse
FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options
Have you tried booting up TWRP from download mode and see if that works?
Fastboot boot TWRP.img
Sent from my KIW-L24 using Tapatalk
From aboot.img
{
"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"
}
Code:
fastboot oem frp-unlock
or
fastboot oem frp-erase
try if it works
2. Putting a 64gb sd card with stock rom gets the recovery to 5% and then phone gets into the reboots cycle. I actually do not know if the dload/UPDATE.APP is being picked up or the wrong boot flashed in is kicking in.
.[/QUOTE]
This part of your post makes it sound like at least one part of recovery is still functioning. (I think there are 2 recoveries on the 5x, but I don't know the details).
I also had the "stuck at 5%" problem when trying to use the "dload" method. Here was my experience:
1) Using 64gb SD card (Class 10 or something fancy)
I was never able to do a stock recovery. Despite many tries after reformatting the card, recovery process always terminated at approximately 5% ending in a reboot without applying the update (which in your case would probably be a bootloop since the existing system is bad).
2) Using 8gb SD card (An old card, class 2)
This worked the first time. I was literally about ready to throw this phone away and send an angry message to Honor, and only tried this out of desperation. I've used it multiple times since, and dload recovery always works with this card.
My conclusion was that this phone cannot seem to read all SD cards properly. I'm not sure if the problem is capacity (over 32gb??), speed class, or brand. Try another card and it may save you. To be safe, it's probably best to be a smaller size, lower speed class card.
dpredster said:
Have you tried booting up TWRP from download mode and see if that works?
Fastboot boot TWRP.img
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
Thank you so much, this worked for me
lukedunk said:
2. Putting a 64gb sd card with stock rom gets the recovery to 5% and then phone gets into the reboots cycle. I actually do not know if the dload/UPDATE.APP is being picked up or the wrong boot flashed in is kicking in.
.
Click to expand...
Click to collapse
This part of your post makes it sound like at least one part of recovery is still functioning. (I think there are 2 recoveries on the 5x, but I don't know the details).
I also had the "stuck at 5%" problem when trying to use the "dload" method. Here was my experience:
1) Using 64gb SD card (Class 10 or something fancy)
I was never able to do a stock recovery. Despite many tries after reformatting the card, recovery process always terminated at approximately 5% ending in a reboot without applying the update (which in your case would probably be a bootloop since the existing system is bad).
2) Using 8gb SD card (An old card, class 2)
This worked the first time. I was literally about ready to throw this phone away and send an angry message to Honor, and only tried this out of desperation. I've used it multiple times since, and dload recovery always works with this card.
My conclusion was that this phone cannot seem to read all SD cards properly. I'm not sure if the problem is capacity (over 32gb??), speed class, or brand. Try another card and it may save you. To be safe, it's probably best to be a smaller size, lower speed class card.[/QUOTE]
this might be one of my chances.. i trieda 32gig card.. so ill try a 8gig.. if this works im gonna kiss all of you guys.. looking for a solution sincetwo days.. with a hour sleepbreak... thnks for the tip for themoment.
Sent from my HUAWEI HUAWEI GRA-L09 using XDA Labs
maxprzemo said:
From aboot.img
Code:
fastboot oem frp-unlock
or
fastboot oem frp-erase
try if it works
Click to expand...
Click to collapse
can u explain a bit more
---------- Post added at 03:37 PM ---------- Previous post was at 03:35 PM ----------
dpredster said:
Have you tried booting up TWRP from download mode and see if that works?
Fastboot boot TWRP.img
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
how ?
Hello!! sorry for the bump, but I have exactly the same problem. Bootloader unlock, but FRP LOCK
Phone is bricked.
Updateapp fails to install at 5%
Any solution? Totally stuck.
---------- Post added at 08:57 PM ---------- Previous post was at 08:55 PM ----------
maxprzemo said:
From aboot.img
Code:
fastboot oem frp-unlock
or
fastboot oem frp-erase
try if it works
Click to expand...
Click to collapse
what's this about? aboot?
maxprzemo said:
From aboot.img
Code:
fastboot oem frp-unlock
or
fastboot oem frp-erase
try if it works
Click to expand...
Click to collapse
I am having the same problem (boot = unlocked, frp = lock) and here's what I get from those commands:
-----------------------
D:\_TEMP\Portables\ADB Tools>fastboot oem frp-unlock
...
FAILED (remote: oem_frp_check_password failed! Error = -1)
finished. total time: 0.013s
-----------------------
Whatever the FRP-Check Password is, I don't have it. I tried the OEM unlocker Code as well as the (former) google password (ok, just a stupid try).
donschmidto said:
From aboot.img
I am having the same problem (boot = unlocked, frp = lock) and here's what I get from those commands:
-----------------------
D:\_TEMP\Portables\ADB Tools>fastboot oem frp-unlock
...
FAILED (remote: oem_frp_check_password failed! Error = -1)
finished. total time: 0.013s
-----------------------
Whatever the FRP-Check Password is, I don't have it. I tried the OEM unlocker Code as well as the (former) google password (ok, just a stupid try).
Click to expand...
Click to collapse
Relock bootloader and unlock again. This way u can unlock frp
Hello,
As the title says, I'm wanting to root my new CAT S61. Anyone managed to unlock the bootloader yet? I've played around with it but haven't had any luck so far.
+1, Me too. Just started debating them on facebook, to maybe have some pressure on to unlock the bootloader the nice way. Until that I am ready to donate. I really miss htc sense, coming from 10-year htc spree.
I have had a few email and chat exchanges with them but haven't made any progress in getting them to provide any help in unlocking the bootloader but I still have my fingers crossed. And yes, I miss htc sense also.......I didn't think I would. FYI, I downloaded Nova Launcher and I set to look much like sense.
I've also been on to their support team looking for assistance with this..... Massively unhelpful...
I asked them about possibilities of unlocking the bootloader (I usually void every warranty covering computer equipment I own within days of owning devices) and I was told along the lines of "No. This will void the warranty so we would not allow this on the device.".... Its MY device and MY warranty to void ffs!
Really gets on my tits the attitude they took.
Anyway, am thinking that unlocking the bootloader may end up like a long wait and a bit of a chore; however if anyone is able to get a dump of the stock image it would surely be possible to patch the image with Magisk then "fastboot flash" it back onto the Cat S61?
This should at least give SU access (for busybox and all that lovely stuff) as well as keeping all the FLIR/proprietary laser/VOC sensor stuff.
EDIT: I've got in touch with Bullitt Group directly instead of going through Cat, and am awaiting a reply from them regarding acquiring a factory image I can play around with... Hopefully they will be able to supply it to me!
Regarding unlocking the bootloader, I haven't tried myself yet (because I haven't got around to getting my laptop OS installed again... That's another story entirely involving bad decisions with Kali lol) but if you boot the phone into bootloader mode (power on the device by using either volume up or volume down and power button or the adb reboot bootloader command via USB). Then you may be able to use the fastboot flashing unlock command to unlock the bootloader...
I really miss the sense freestyle themes, where there is no grid and you pick a theme with background image(can be changed) and stickers (just some themed icons with different sizes). Then you place your stickers and assign apps to them. I myself used an archtecure theme, where there were stickers varying feom minimalistic monopoly houses up to vertically big skyscrapers and horizontally long trains. For my gf I made nature theme with nice summer bliss and clouds, deers, rabbits, butterflies and birds. Its just so customizable. I hate being restricted to grids or standard sizes icons or their 2x, 4x and so on.
k46tank said:
I have had a few email and chat exchanges with them but haven't made any progress in getting them to provide any help in unlocking the bootloader but I still have my fingers crossed. And yes, I miss htc sense also.......I didn't think I would. FYI, I downloaded Nova Launcher and I set to look much like sense.
Click to expand...
Click to collapse
---------- Post added at 06:29 PM ---------- Previous post was at 06:23 PM ----------
I just received a 130MB OTA, I hope it was not a security update, casting me out of the gang, when someone finds the cure for the older build. The build LTE_D0201121.0_S61_0.040.02 gave me Flir Youtube streaming option.
luc1fer said:
I've also been on to their support team looking for assistance with this..... Massively unhelpful...
I asked them about possibilities of unlocking the bootloader (I usually void every warranty covering computer equipment I own within days of owning devices) and I was told along the lines of "No. This will void the warranty so we would not allow this on the device.".... Its MY device and MY warranty to void ffs!
Really gets on my tits the attitude they took.
Anyway, am thinking that unlocking the bootloader may end up like a long wait and a bit of a chore; however if anyone is able to get a dump of the stock image it would surely be possible to patch the image with Magisk then "fastboot flash" it back onto the Cat S61?
This should at least give SU access (for busybox and all that lovely stuff) as well as keeping all the FLIR/proprietary laser/VOC sensor stuff.
EDIT: I've got in touch with Bullitt Group directly instead of going through Cat, and am awaiting a reply from them regarding acquiring a factory image I can play around with... Hopefully they will be able to supply it to me!
Regarding unlocking the bootloader, I haven't tried myself yet (because I haven't got around to getting my laptop OS installed again... That's another story entirely involving bad decisions with Kali lol) but if you boot the phone into bootloader mode (power on the device by using either volume up or volume down and power button or the adb reboot bootloader command via USB). Then you may be able to use the fastboot flashing unlock command to unlock the bootloader...
Click to expand...
Click to collapse
LTE_D0201121.0_S61_0.040.02 is the build I'm on as well, so don't worry too much... However I've been on this build since sometime in July, so don't know why you've only just got the OTA ?
Anyway, the other thought I have been having is trying to port across a custom recovery from the Motorola Moto X4. Same chipset, same RAM, same board and same screen resolution, so it just might work... Once I get hold of a flash dump and unlock the bootloader that is ? I'm getting a bit ahead of myself!
Just received another OTA, September 1st patch, LTE_D0201121.0_S61_0.046.02. Radio is LTE_D0201121.1_S61 after the update. This one was larger, but I forgot to screenshot the exact changes and size.
luc1fer said:
LTE_D0201121.0_S61_0.040.02 is the build I'm on as well, so don't worry too much... However I've been on this build since sometime in July, so don't know why you've only just got the OTA ?
Anyway, the other thought I have been having is trying to port across a custom recovery from the Motorola Moto X4. Same chipset, same RAM, same board and same screen resolution, so it just might work... Once I get hold of a flash dump and unlock the bootloader that is I'm getting a bit ahead of myself!
Click to expand...
Click to collapse
Is any progress?
I am not a programmer, and can not help anything. Looking forward good news!!
Hi there, also looking forward for root, will hopefully get the phone end of the year...
ogghi said:
Hi there, also looking forward for root, will hopefully get the phone end of the year...
Click to expand...
Click to collapse
I will not buy it until it is rootable.
Nope, no luck as of yet... Nothing I seem to try is giving me any options or progress.
Rather frustrated carrying round 2 devices lol one for root apps and the s61 for everything else!
Still impressed at the phone though, VERY utilitarian!
Hey there, I will get my S61 tomorrow.
Was hoping for any root idea, but will hopefully survive without until we have the privilege to get it
... and there is no option in the programmer options (unlock bootloader)?
Did not stumble upon such a function yet.
The most annoying thing without root is missing a good ad blocking. dns66 seems to work, but there are still plenty of ads in apps that get through...
Also having potentially all power unlocked would be great!
So no news here I guess?
To enter bootloader:
1.switch of your phone
2.press volume down
3.conect the power cable
Does anyone refer to this thread?
https://forum.xda-developers.com/apps/magisk/how-to-install-magisc-twrp-locked-t3599926/page2
I've been looking at this phone for some time. I was able to get a Moto Z2 Force from Verizon into EDL mode with simple commands, so I'm wondering if you can unlock this bootloader just by telling it to unlock.
You would put the device into fastboot mode (by going to the bootloader, instructions were posted above i think), and then try some commands like this
fastboot flashing unlock
or
fastboot oem unlock
also check if in developer settings there is a toggle for Allow bootloader unlock or OEM unlock or w/e they call it.
if this works I highly suggest figuring out a way to grab the entire system to make a backup before you do anything. there's no twrp yet but it can't be too difficult to compile, but i dont have this $1000 waste of money to do any of this. i hope this post helps someone
james35888 said:
Does anyone refer to this thread?
https://forum.xda-developers.com/apps/magisk/how-to-install-magisc-twrp-locked-t3599926/page2
Click to expand...
Click to collapse
This doesn’t work since the boot loader is locked (stock boot loader has not been released on the web to my knowledge)
---------- Post added at 01:55 AM ---------- Previous post was at 01:38 AM ----------
Knuxyl said:
I've been looking at this phone for some time. I was able to get a Moto Z2 Force from Verizon into EDL mode with simple commands, so I'm wondering if you can unlock this bootloader just by telling it to unlock.
You would put the device into fastboot mode (by going to the bootloader, instructions were posted above i think), and then try some commands like this
fastboot flashing unlock
or
fastboot oem unlock
also check if in developer settings there is a toggle for Allow bootloader unlock or OEM unlock or w/e they call it.
if this works I highly suggest figuring out a way to grab the entire system to make a backup before you do anything. there's no twrp yet but it can't be too difficult to compile, but i dont have this $1000 waste of money to do any of this. i hope this post helps someone
Click to expand...
Click to collapse
Are these commands on a computer through ADB?
The only options I had on the phone were:
-Start
-Recovery Mode
-Restart Bootloader
-Power Off
-Boot to QMMI
-Boot to FFBM
Hi,
I looked a bit into the process of rooting on this device. It would be cool to get it rooted. I guess this process is in theory simple. But we should focus on the first problem:
Why is the option "OEM unlock" hidden in the developer Menu? Are there ways to make that option usable? If anyone has an idea how to make this option usable, we could get to the next step. Thanks to anyone who has an contribution.
Edit: some additional info
C:\adb\platform-tools>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
Finished. Total time: 0.000s
CatS61:/ $ getprop | grep oem
[ro.oem_unlock_supported]: [true]
[sys.oem_unlock_allowed]: [0]
Dear all,
I bought Mi Pad 4 and it was running well, and I want to update the ROM. The device is comes with Locked bootloader.
I unlocked my Mi Pad 4 using MI Unlock. And when I try to relock it using "fastboot oem lock" command, it become suddenly comes with black screen with written: "The system has been destroyed. Press power button to shutdown".
So I entered the fastboot mode and try some command/solutions:
- My device status is locked:
E:\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
finished. total time: 0.006s
- I can't unlock it using Mi Unlock:
- Flashing using MiFlashalso not allowed since it is still locked:
- I tried to unlock using fastboot, also failed:
E:\adb>fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.003s
- The faastboot screen in my mi pad is only for around 10 Second. After that it goes to "The System has been Destroyed" stage...
Any help is appreciated, because I cant use it anymore...
Why did you even want to close the BL again?!? I dont understand anyone who does that.
And AFAIK you can flash an original Image from Xiaomi even with locked BL. But I have never done it and the guide shows a working phone..
http://en.miui.com/thread-835254-1-1.html
You need the Mi-Flash Tool. And these damn Indian people with their fake titles on youtube.. The title is english and the freaking video is hindi or whatever.. SO ANNOYING!!!
Hi, the tutorial you gave is for 'normal' xiaomi phone, where it boot normally (even its BL is locked).
In my case, I cant load the BL (It said: Destroyed). The only thing I can do is restart to fastboot state, and after 20 seconds it goes again to Destroyed state.
Ok, so I have read some other threads and what seems the "only" solution is to unlock the bootloader again.. But the other people had no problem running "oem unlock".. And you get an error, what is kinda strange.
What happens in MiUnlock? Error?
Hi, I think the main problem is current status is "The System has been Destroyed", therefore it cannot load the BL.
Meanwhile, the BL is in Locked status. So it need to be un-locked first, so I can load the new ROM.
MIUnlock is error, it said: "Current account is not bound to this device", which is strange, because previously I unlocked using it before.
I assume MIUnlock said this because the status of "System destroyed"...
Never lock if there is not 100% Xiaomi official rom inside, and better use MiFlash with "clean all and lock" option for locking.
Thanks for your suggestion. Will do that after I fix this problem..
I think you have a bricked device.. Some devices have this "test-pins", where you can enable some debug-bridge and there you could flash it (mi5 or redmi5 was that in that thread). I dont know if the Pad4 has such Pins and you would have to open the whole device.. (its not something you can access from the outside).
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Noted on that, but too risky for me to open the case..
Any other solution would be really appreciated.
thE_29 said:
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Click to expand...
Click to collapse
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
P.Kosunen said:
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
Click to expand...
Click to collapse
Yup, and I cant do that since cannot load the BL, because it's "Destroyed" right now..
Up.
Does anyone have the solution on this?
Thanks.
Seemed "bricked" to me, welcome to the bricked world dude, I have had 2 beautiful paper holder on my desk.
mac_erot said:
Up.
Does anyone have the solution on this?
Thanks.
Click to expand...
Click to collapse
The only solution was already posted several times -> open device, find test-pins, use them and flash ROM. And yet, you still ignore it everytime. THERE is no other solution for bricked devices.
And: NEVER close the bootloader again on NON official ROMs.
2 ways to try out...
1st run
"fastboot flashing unlock"
2nd
"fastboot oem reboot EDL"
Or this link if the command doesn't work
https://www.google.com/amp/s/forum....e-how-to-reboot-to-edl-fastboot-t3394292/amp/
go to service centre they will be able to restore the device using edl i hope
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Looks like it is straightforward to remove the back cover. Perhaps you can find the EDL test points on the motherboard?
https://www.youtube.com/watch?v=RZpj0k9HKTQ
Is there no possibility to enable USB Debugging without entering the miui surface?
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Edl with test points should work, try some different ones, maybe the ones you are trying are wrong
---------- Post added at 06:47 AM ---------- Previous post was at 06:47 AM ----------
Also, try to run fastboot erase vbmeta
Hi,
I am having a tenor G phone (10. or G) which is more popularised in India but still lacks in development.
I can't able to root the phone or can't able to unlock the bootloader though there is the option in developer mode to unlock OEM whenever I tried to put the command "Fastboot OEM unlock"I ended in this error! " [ERR] Unknown Command error !!! OKAY [ 0.007s] finished"
If you need the specifications of the phone I have attached the link here http://www.gsmarena.com.co/2017/10/10-or-g.html
Help me guys, please...Like me, many are struggling to root this device...
TWRP is not also available so,
HElp us
rhudsonsamuel said:
Hi,
I am having a tenor G phone (10. or G) which is more popularised in India but still lacks in development.
I can't able to root the phone or can't able to unlock the bootloader though there is the option in developer mode to unlock OEM whenever I tried to put the command "Fastboot OEM unlock"I ended in this error! " [ERR] Unknown Command error !!! OKAY [ 0.007s] finished"
If you need the specifications of the phone I have attached the link here http://www.gsmarena.com.co/2017/10/10-or-g.html
Help me guys, please...Like me, many are struggling to root this device...
TWRP is not also available so,
HElp us
Click to expand...
Click to collapse
Hi there,
well first you need to type in adb reboot fastboot
then fastboot oem get_unlock_data
after that the command will give you a string of numbers and then you have to copy and paste those numbers on to the mobile companys bootloader unlock service website.
However since it's an Indian smartphone I am sure that the company will not provide such services as they restricted this service to everyone.....
However you can try and use KINGO ROOT to root your smartphone.
I am not sure if it will work but you can try it
For that too
I am getting the same error
Kingo root can't able to root this phone..I tried several rooting apps but not working
KIBS2173 said:
Hi there,
well first you need to type in adb reboot fastboot
then fastboot oem get_unlock_data
after that the command will give you a string of numbers and then you have to copy and paste those numbers on to the mobile companys bootloader unlock service website.
However since it's an Indian smartphone I am sure that the company will not provide such services as they restricted this service to everyone.....
However you can try and use KINGO ROOT to root your smartphone.
I am not sure if it will work but you can try it
Click to expand...
Click to collapse
Kingo root,
King root
Srs root
Dr fone
Iroot
Nothing is working on 10.or G
rony929 said:
Kingo root,
King root
Srs root
Dr fone
Iroot
Nothing is working on 10.or G
Click to expand...
Click to collapse
If you have unlocked bootloader, then try Magisk to root your phone.
HIT THANKS IF FOUND USEFUL
Augustoandro said:
If you have unlocked bootloader, then try Magisk to root your phone.
HIT THANKS IF FOUND USEFUL
Click to expand...
Click to collapse
Unable to unlock bootloader
rony929 said:
Unable to unlock bootloader
Click to expand...
Click to collapse
Does the method on second post not work?
There is jo option to unlock bootloader however there is option in DEVELOPER OPTION of UNLOCK OEM but its of no use
---------- Post added at 12:50 PM ---------- Previous post was at 12:48 PM ----------
And which post
What method
---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------
KIBS2173 said:
Hi there,
well first you need to type in adb reboot fastboot
then fastboot oem get_unlock_data
after that the command will give you a string of numbers and then you have to copy and paste those numbers on to the mobile companys bootloader unlock service website.
However since it's an Indian smartphone I am sure that the company will not provide such services as they restricted this service to everyone.....
However you can try and use KINGO ROOT to root your smartphone.
I am not sure if it will work but you can try it
Click to expand...
Click to collapse
Can u pls provide link of adb?