Hi guys,
Need some help with unlocking bootloader.
Anyway, after unlocking bootlader sucessfully and restarting, tablet doesn't load, it gets stuck after Sony and Xperia logo and keeps restarting over and over again, also after this I tried to flash boot.img of different firmwares, it doesnt boot up and doesn't go to recovery mode either.
What could be the problem?
P.S. though after this, tried to flash stock ROM with flashtool in flash mode, tablet loaded up and started working, but of course, if I try to flash any boot.img, it won't load up again...
Try looking for is it unlockable
Good day, can you try the following to check whether your tablet is unlockable?
You flash the stock firmware back,
then enter the service code in your tablet.
Then check whether it is unlockable.
The way to enter the service code is:
1) Open the Contact App,
2) Go to setting,
3) Long press the bottom area of the tablet, for maybe 10 sec?
4) After you release your finger, a dialer will come out.
5) Enter: without the quote "*#*#7378423#*#*"
6) I get this from Sony website:
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
Guide: How to enter Service Menu by XperiaBlog
If it show Yes, means that we need to find out other solution.
If No, then your tablet is not unlockable.
I'm Malaysian, I don't know what kind of Tablet cannot be unlocked in other region.
Trevor Chuah said:
Good day, can you try the following to check whether your tablet is unlockable?
You flash the stock firmware back,
then enter the service code in your tablet.
Then check whether it is unlockable.
The way to enter the service code is:
1) Open the Contact App,
2) Go to setting,
3) Long press the bottom area of the tablet, for maybe 10 sec?
4) After you release your finger, a dialer will come out.
5) Enter: without the quote "*#*#7378423#*#*"
6) I get this from Sony website:
Guide: How to enter Service Menu by XperiaBlog
If it show Yes, means that we need to find out other solution.
If No, then your tablet is not unlockable.
I'm Malaysian, I don't know what kind of Tablet cannot be unlocked in other region.
Click to expand...
Click to collapse
Hi,
Thanks for quick response. Yes bootloader is unlockable. Just to be more precise, it's SGP321
giosal said:
Hi,
Thanks for quick response. Yes bootloader is unlockable. Just to be more precise, it's SGP321
Click to expand...
Click to collapse
Okay. Now when you boot into fastboot mode,
you enter the command: fastboot devices
what does it come out?
Trevor Chuah said:
Okay. Now when you boot into fastboot mode,
you enter the command: fastboot devices
what does it come out?
Click to expand...
Click to collapse
This comes out:
Code:
C:\***>fastboot devices
CB5A1UV0GY fastboot
C:\***>
So, obviously, it sees it, right?
giosal said:
This comes out:
Code:
C:\***>fastboot devices
CB5A1UV0GY fastboot
C:\***>
So, obviously, it sees it, right?
Click to expand...
Click to collapse
Yes, it sees it.
Okay, the unlock key is expired once used.
I think maybe you can retrieve the key again from Sony website?
Sony Unlock
The following is a note in my own guide for unlocking
Maybe you try the getvar version before unlock.
In the cmd windows type in fastboot.exe -i 0x0fce getvar version
If a value is returned (it will return 0.5), it means the phone is correctly connected
Click to expand...
Click to collapse
---------- Post added at 10:33 PM ---------- Previous post was at 10:32 PM ----------
After unlock, try reboot it directly with
"fastboot reboot"
Trevor Chuah said:
Yes, it sees it.
Okay, the unlock key is expired once used.
I think maybe you can retrieve the key again from Sony website?
Sony Unlock
The following is a note in my own guide for unlocking
Maybe you try the getvar version before unlock.
---------- Post added at 10:33 PM ---------- Previous post was at 10:32 PM ----------
After unlock, try reboot it directly with
"fastboot reboot"
Click to expand...
Click to collapse
Got the unlock key from Sony website, checked var version, unlocked bootloader. This is the output:
Code:
C:\*>fastboot -i 0x0fce getvar version
version: 0.5
finished. total time: 0.002s
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
FAILED (remote: Command did not succeed)
finished. total time: 0.037s
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
OKAY [ 3.681s]
finished. total time: 3.681s
C:\*>
Which is pretty strange, why doesn;t it succeed from first try?
After reboot it's the same: keeps restarting over and over again...
giosal said:
Got the unlock key from Sony website, checked var version, unlocked bootloader. This is the output:
Code:
C:\*>fastboot -i 0x0fce getvar version
version: 0.5
finished. total time: 0.002s
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
FAILED (remote: Command did not succeed)
finished. total time: 0.037s
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
OKAY [ 3.681s]
finished. total time: 3.681s
C:\*>
Which is pretty strange, why doesn;t it succeed from first try?
After reboot it's the same: keeps restarting over and over again...
Click to expand...
Click to collapse
Yup, it is weird, why not succeed for the first time.
Now is it rebooted?
Trevor Chuah said:
Yup, it is weird, why not succeed for the first time.
Now is it rebooted?
Click to expand...
Click to collapse
No, it just keeps restarting over and over... Although if I connect in fastboot mode and after connect to charger, it displays the charging progress.
giosal said:
No, it just keeps restarting over and over... Although if I connect in fastboot mode and after connect to charger, it displays the charging progress.
Click to expand...
Click to collapse
Have you try to let it restart and restart?
Maybe eventually it will successfully rebooted?
Trevor Chuah said:
Have you try to let it restart and restart?
Maybe eventually it will successfully rebooted?
Click to expand...
Click to collapse
I left it to restart over and over, it restarted already more than 10 times, still restarting...
giosal said:
I left it to restart over and over, it restarted already more than 10 times, still restarting...
Click to expand...
Click to collapse
I never have this problem.
Have you try fastboot other ROM's boot.img?
Not only boot.img with recovery, but real CustomROM.
Maybe you can try CyanogenMod or OmniROM.
Download it and extract it's boot.img.
Then try fastboot flash it and see.
I'm using OmniROM.
Sent from my SGP311 using XDA Free mobile app
Trevor Chuah said:
I never have this problem.
Have you try fastboot other ROM's boot.img?
Not only boot.img with recovery, but real CustomROM.
Maybe you can try CyanogenMod or OmniROM.
Download it and extract it's boot.img.
Then try fastboot flash it and see.
I'm using OmniROM.
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
gonna try it now. is recovery included in OmniROM?
giosal said:
gonna try it now. is recovery included in OmniROM?
Click to expand...
Click to collapse
Yes. It include TWRP.
Sent from my SGP311 using XDA Free mobile app
Trevor Chuah said:
Yes. It include TWRP.
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
OK, cool, actually gonna try CM11 for now, it downloaded much faster
this is what I get:
Code:
C:\*>fastboot flash boot boot_CM.img
sending 'boot' (10664 KB)...
OKAY [ 0.345s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.345s
C:\*>
If I unlock bootloader again, it will write it....
Unlocked again, this is output:
Code:
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
FAILED (remote: Command did not succeed)
finished. total time: 0.047s
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
OKAY [ 0.391s]
finished. total time: 0.391s
C:\*>fastboot flash boot boot_CM.img
sending 'boot' (10664 KB)...
OKAY [ 0.344s]
writing 'boot'...
OKAY [ 0.516s]
finished. total time: 0.875s
C:\*>fastboot reboot
rebooting...
finished. total time: 0.000s
C:\*>
Obviously, it doesn't boot now at all...
giosal said:
this is what I get:
Code:
C:\*>fastboot flash boot boot_CM.img
sending 'boot' (10664 KB)...
OKAY [ 0.345s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.345s
C:\*>
If I unlock bootloader again, it will write it....
Unlocked again, this is output:
Code:
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
FAILED (remote: Command did not succeed)
finished. total time: 0.047s
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
OKAY [ 0.391s]
finished. total time: 0.391s
C:\*>fastboot flash boot boot_CM.img
sending 'boot' (10664 KB)...
OKAY [ 0.344s]
writing 'boot'...
OKAY [ 0.516s]
finished. total time: 0.875s
C:\*>fastboot reboot
rebooting...
finished. total time: 0.000s
C:\*>
Obviously, it doesn't boot now at all...
Click to expand...
Click to collapse
Hmm.....
After flash the cm boot.img, reboot, have you see Sony logo with purple led light on? No led light at all?
Maybe after boot up, you keep pressing volume up, until it enter recovery.
Btw, it is not necessary to enter fastboot unlock command each time. Just assume it has been unlocked.
Sent from my SGP311 using XDA Free mobile app
Trevor Chuah said:
Hmm.....
After flash the cm boot.img, reboot, have you see Sony logo with purple led light on? No led light at all?
Maybe after boot up, you keep pressing volume up, until it enter recovery.
Btw, it is not necessary to enter fastboot unlock command each time. Just assume it has been unlocked.
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
That's the thing, I guess it doesn't unlock... Because unless I do it everytime before flashing, it fails the flashing as you can see in the output.
When I try to turn on tablet after flashing there is nothing at all, LED blinks once white and that's it. If I keep power button pressed, it keeps blinking. And it doesn't go into recovery, even though I keep pressing volume up button
giosal said:
That's the thing, I guess it doesn't unlock... Because unless I do it everytime before flashing, it fails the flashing as you can see in the output.
When I try to turn on tablet after flashing there is nothing at all, LED blinks once white and that's it. If I keep power button pressed, it keeps blinking. And it doesn't go into recovery, even though I keep pressing volume up button
Click to expand...
Click to collapse
I have no idea now...
Have you try install any recovery when you were at stock ROM?
And, you use flashtool to flash back the stock ftf file?
Did you untick all the ta files?
Sent from my SGP311 using XDA Free mobile app
Trevor Chuah said:
I have no idea now...
Have you try install any recovery when you were at stock ROM?
And, you use flashtool to flash back the stock ftf file?
Did you untick all the ta files?
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I did try, but it didn't work either... Could you give me a link to the recovery?
Yes, I use flashtool to flash back the stock ftf, but I never unchecked the ta files. What do they do? Let me try it now. Which files should I exclude and how exactly?
Related
This phone has never been even mentioned on xda so there is nothing to search for.
Anyways i have gone thru some threads of similar phones and tried some one click root methods. They didnt work.
So i thought i should unlock the bootloader.
Just for the sake of it i tried to boot into recovery and was successful.
Then i started following those htcdev.com instruction which required me to go into the bootloader mode.
But whenever i try doing that it either:
-Remains stuck at htc logo screen (the 1st one and not the bootanimation)
-Boots normally
then i saw that i had to press this button release this after so many seconds and......
so just to be sure that im not making those silly mistakes i tried to go into bootloader thru adb which always remains stuck at the htc splash screen (htc - powered by android).
then i tried to go to recovery but now even that isnt possible.
so in short: i cant get into the bootloader so i cant unlock or root. I cant get into the recovery either. The phone otherwise is working pretty normal. But on trying to get into any modes i remain stuck at the 1st htc screen (and not the bootanimation) and then i have to remove the battery to get it booting normally.
It is HTC Desire 516 Dual sim and is on JB 4.3 (if u needed this)
and finally i got this log from a unlock tool if it makes it easier for you
adb: reboot-bootloader
adb out:
Reboot success!
fastboot: devices
fastboot out: 0123456789ABCDEF fastboot
fastboot: oem lock
fastboot timeout
lock_failed
adb: reboot-bootloader
adb out:
Reboot success!
fastboot: devices
fastboot out: 0123456789ABCDEF fastboot
fastboot: getvar version
fastboot out: version: 0.5
finished. total time: 0.003s
fastboot: getvar version-bootloader
fastboot out: version-bootloader:
finished. total time: 0.003s
fastboot: getvar version-main
fastboot out: version-main:
finished. total time: 0.003s
fastboot: getvar serialno
fastboot out: serialno: 0123456789ABCDEF
finished. total time: 0.003s
fastboot: getvar product
fastboot out: product: MSM8610
finished. total time: 0.003s
fastboot: getvar modelid
fastboot out: modelid:
finished. total time: 0.003s
fastboot: getvar cidnum
fastboot out: cidnum:
finished. total time: 0.003s
fastboot: getvar build-mode
fastboot out: build-mode:
finished. total time: 0.003s
fastboot: getvar boot-mode
fastboot out: boot-mode:
finished. total time: 0.003s
fastboot: getvar security
fastboot out: security:
finished. total time: 0.003s
fastboot: getvar imei
fastboot out: imei:
finished. total time: 0.003s
fastboot: oem get_identifier_token
fastboot timeout
get_device_info_failed
Click to expand...
Click to collapse
pls do help if u can :highfive: :fingers-crossed:
noone? @psych.half suggest anything?
T3snake said:
noone? @psych.half suggest anything?
Click to expand...
Click to collapse
Remove your battery before trying to boot into fastboot.
If you can't remove your battery, go to Settings->Power options And disable fast boot
dummie999 said:
Remove your battery before trying to boot into fastboot.
If you can't remove your battery, go to Settings->Power options And disable fast boot
Click to expand...
Click to collapse
yea tried that..
same result
btw volume up brings up recovery and down brings bootloaderr
is fastboot a different mode or u call bootloader mode and fastboot the same..?
T3snake said:
yea tried that..
same result
btw volume up brings up recovery and down brings bootloaderr
is fastboot a different mode or u call bootloader mode and fastboot the same..?
Click to expand...
Click to collapse
Yes fastboot and bootloader are the same
Have you tried booting into bootloader with "adb reboot bootloader"
Info
You are not alone !
Now can have all the stock files here .
dummie999 said:
Yes fastboot and bootloader are the same
Have you tried booting into bootloader with "adb reboot bootloader"
Click to expand...
Click to collapse
yea both recovery and bootloader isnt accessible by adb
joldisadrian said:
You are not alone !
Now can have all the stock files here .
Click to expand...
Click to collapse
but there are only kernel sources
T3snake said:
yea both recovery and bootloader isnt accessible by adb
Click to expand...
Click to collapse
How do you mean isn't accesible? What do you see when you type those commands? What is the output?
I have this device, and i booted it in fastboot mode successfully. Open ADB and type "adb reboot-bootloader", the phone will reboot and remain stuck in the boot logo (the first). Now open fastboot and type "fastboot devices" and it will be recognized. I can't unlock bootloader, because when i type "fastboot oem get_identifier_token" it remains stuck, and it's so annoying because i want to root this device, can you help me? :crying:
I'm having the same problem. The bootloader is not accessible. I tried all possible root methods but none work. Kinda regretting now buying this phone
dummie999 said:
How do you mean isn't accesible? What do you see when you type those commands? What is the output?
Click to expand...
Click to collapse
As I said it reboots but remains stuck at HTC logo until removal of battery
Sent from my SM-T211 using Tapatalk
AceXer said:
I have this device, and i booted it in fastboot mode successfully. Open ADB and type "adb reboot-bootloader", the phone will reboot and remain stuck in the boot logo (the first). Now open fastboot and type "fastboot devices" and it will be recognized. I can't unlock bootloader, because when i type "fastboot oem get_identifier_token" it remains stuck, and it's so annoying because i want to root this device, can you help me? :crying:
Click to expand...
Click to collapse
So since its stuck and we can't do anything
BTW we had an 110 mb update just a few days ago but since my phone can't get into recovery the final steps don't take place where it goes to recovery and finishes up(in my case it remains stuck at HTC logo so device remains as it was when I boot it normally)
Sent from my SM-T211 using Tapatalk
rakeshz said:
I'm having the same problem. The bootloader is not accessible. I tried all possible root methods but none work. Kinda regretting now buying this phone
Click to expand...
Click to collapse
Well if they gave us an app2sd feature I ccud forgive em a bit.
I contacted the customer service and when I mentioned a stuck up screen they immediately asked if I WS rooting. So maybe htc did it intentionally or maybe some1 fishy intervened or something
Sent from my SM-T211 using Tapatalk
T3snake said:
Well if they gave us an app2sd feature I ccud forgive em a bit.
I contacted the customer service and when I mentioned a stuck up screen they immediately asked if I WS rooting. So maybe htc did it intentionally or maybe some1 fishy intervened or something
Sent from my SM-T211 using Tapatalk
Click to expand...
Click to collapse
Yes, seriously we need the move to sd card feature. The whole reason of having a feature phone without being able to install any apps or big games sucks
rakeshz said:
Yes, seriously we need the move to sd card feature. The whole reason of having a feature phone without being able to install any apps or big games sucks
Click to expand...
Click to collapse
I calculated and found that u can get Max 1.7 GB free (as indicated by the mobile) but if u use mtp or reach 1.5 GB u will not be able to put anything more since there shud always be 200mb free
So we get only 1.5 GB after disabling all the preinstalled apps
Sent from my SM-T211 using Tapatalk
So I'm able to boot into fastboot mode, I'm able to boot into recovery mode. But how can we unlock the bootloader?
AceXer said:
So I'm able to boot into fastboot mode, I'm able to boot into recovery mode. But how can we unlock the bootloader?
Click to expand...
Click to collapse
Go to htcdev.com
If u can get into fastboot mode u can run some commands to get a token paste the token at the place indicated and follow the steps
Sent from my GT-S5282 using Tapatalk
T3snake said:
Go to htcdev.com
If u can get into fastboot mode u can run some commands to get a token paste the token at the place indicated and follow the steps
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
Yes, but this device isn't in the list, and when I type (in fastboot mode) "fastboot oem get_identifier_token" it stuck and three dots appear.
All command work, but if i type "oem" after "fastboot" (ex. "fastboot oem command list) it stuck with three dots. Help meeeee pleease!
AceXer said:
Yes, but this device isn't in the list, and when I type (in fastboot mode) "fastboot oem get_identifier_token" it stuck and three dots appear.
All command work, but if i type "oem" after "fastboot" (ex. "fastboot oem command list) it stuck with three dots. Help meeeee pleease!
Click to expand...
Click to collapse
Hi,
I have same device and same problems. I think I tried all solutions I've seen so far. I had HTC wildfire, Motorola XT530, Huawei Ascend G300, HTC Desire X, and I have some expirience rooting, but this phone makes me sick. Just sent an rage mail to HTC, saying that they made great little piece of hardware with software making it almost unusable. So far I tried SuperOneClick, RootGenius and adb root, but nothing works.
I updated to Project Spectrum 1.1 then tried to flash SuperSU from the stock recovery. No idea why I thought this was a good idea.
Now the phone gets stuck on the "Oppo - powered by android screen" and the recovery gets stuck on the charging screen, but indicates that it is not charging even when it is.
I can get it into fastboot, but can't actually do much with it...
# fastboot devices
2a108da fastboot
# fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (10860 KB)...
OKAY [ 0.342s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.343s
# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.342s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.343s
I have tried fastboot from both Gentoo Linux (android-tools 5.1.1_p13) and Windows 10, using the ADB and Fastboot installer v1.4.3
It seems that phone is bricked.
I had the same situation with my R5 and the only way to get in life again is to use an unbrick tool provided by oppoforums .
You can ask Ricky at oppoforums.
Ricky is not replying after six days. Do you still have the tool?
Lum_UK said:
Ricky is not replying after six days. Do you still have the tool?
Click to expand...
Click to collapse
You have PM
mermigas said:
You have PM
Click to expand...
Click to collapse
may you can upload this tool here`? i need it too
Problem
Hello. I have the same problem and Ricky doesn't reply. Can i have this tool for unbrick my phone?
I want to install twrp recovery in mobile me, I have to do all the tutorial that is in Google and YouTube, I am very difficult time at the CMD, from the early look good, I enter format fastboot flash recovery twrp.img, but in fact, there are writing failed (remote: partition flashing is not allowed), how do I fix this, I haven't unlock bootloader, in the setting My mobile, I have activated OEM unlock the developer option, My Mobile : xiaomi redmi note 3 pro (Kenzo)
You have to unlock bootloader first if you want to install twrp
I have a Le(Letv) LeEco 2 smartphone.
The bootloader is selected unlocked,as is usb debugging selected.
But I fail to install the TWRP recovery rom.
The excerpt after running in ADB is shown below :--->
E:\ADB+Recovery>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
E:\ADB+Recovery>fastboot flash recovery twrp-3.0.2-0-s2.img
target reported max download size of 536870912 bytes
sending 'recovery' (17234 KB)...
OKAY [ 0.563s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.584s
E:\ADB+Recovery>fastboot reboot
rebooting...
finished. total time: 0.000s
E:\ADB+Recovery>
Click to expand...
Click to collapse
How do I install TWRP successfully.
mar.ur said:
You have to unlock bootloader first if you want to install twrp
Click to expand...
Click to collapse
Does this error occur ONLY when the bootloader is locked ??? In other words, does this error mean the bootloader is locked?
SameerSohrab said:
Does this error occur ONLY when the bootloader is locked ??? In other words, does this error mean the bootloader is locked?
Click to expand...
Click to collapse
Yep your bootloader Is locked
Use command "fastboot oem unlock" or "fastboot oem unlock-go" to unlock bootloader.
After that "fastboot flash recovery ~/recovery.img"
Fastboot error unlocking
sebastian1978 said:
Use command "fastboot oem unlock" or "fastboot oem unlock-go" to unlock bootloader.
After that "fastboot flash recovery ~/recovery.img"
Click to expand...
Click to collapse
I used commands "fastboot oem unlock" or "fastboot oem unlock-go". but i still get
errors:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.046s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock-go
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.040s
Hi, How I use this comand? On cm prompt?
Thank you
Same Problem
thierryrojas said:
Hi, How I use this comand? On cm prompt?
Thank you
Click to expand...
Click to collapse
did you solve the problem, I have the same issue with my phone?
@The_Joker after fastboot oem unlock i get: FAILED (remote: Token verification failed, reboot the device)
Same problem
the same worry. my redmi 4 does not even turn on. I think that I have deleted the system bad luck. he does not want to turn on and the booloader stays locked on miUnlock and per cmd.
what can i do?
Chiko Tridipa said:
I want to install twrp recovery in mobile me, I have to do all the tutorial that is in Google and YouTube, I am very difficult time at the CMD, from the early look good, I enter format fastboot flash recovery twrp.img, but in fact, there are writing failed (remote: partition flashing is not allowed), how do I fix this, I haven't unlock bootloader, in the setting My mobile, I have activated OEM unlock the developer option, My Mobile : xiaomi redmi note 3 pro (Kenzo)
Click to expand...
Click to collapse
partition flashing is not allowed if the bootloader is locked. U have to unlock ur bootloader in order to modify anything.
---------- Post added at 01:51 PM ---------- Previous post was at 01:50 PM ----------
Server16 said:
the same worry. my redmi 4 does not even turn on. I think that I have deleted the system bad luck. he does not want to turn on and the booloader stays locked on miUnlock and per cmd.
what can i do?
Click to expand...
Click to collapse
unlock bootloader officially.
---------- Post added at 01:53 PM ---------- Previous post was at 01:51 PM ----------
catalinrcd said:
@The_Joker after fastboot oem unlock i get: FAILED (remote: Token verification failed, reboot the device)
Click to expand...
Click to collapse
u cannot unlock bootloader by normal cmd command line. U have to use the official MI unlock for unlocking the redmi note 3.
pritamdutt said:
partition flashing is not allowed if the bootloader is locked. U have to unlock ur bootloader in order to modify anything.
---------- Post added at 01:51 PM ---------- Previous post was at 01:50 PM ----------
unlock bootloader officially.
---------- Post added at 01:53 PM ---------- Previous post was at 01:51 PM ----------
u cannot unlock bootloader by normal cmd command line. U have to use the official MI unlock for unlocking the redmi note 3.
Click to expand...
Click to collapse
The phone does not turn on. and I have already received the SMS from the unlocking MI before,
but my concern is that the phone will not turn on anymore. barely the MI logo appears and goes off
NB: I have already tried the flash cable qualcomm but still nothing
It's here : http://en.miui.com/unlock/
Hi! Where I should write these cmds? Answer pls
Server16 said:
The phone does not turn on. and I have already received the SMS from the unlocking MI before,
but my concern is that the phone will not turn on anymore. barely the MI logo appears and goes off
NB: I have already tried the flash cable qualcomm but still nothing
Click to expand...
Click to collapse
If it is blinking red probably you can flash through EDL mode.
you guys know there's an unofficial method to unlock bootloader right? the thread is currently hot:
https://forum.xda-developers.com/redmi-note-3/how-to/guide-rn3-pro-se-t3565172
Oem unlocking
FAILED (remote: oem authentication failed,please get right authentication f)
finished. total time: 0.003s
I have this error message please help me
Hi the correct command on a A2 Lite is:
fastboot flash boot twrp.img
as in ... recovery is now "boot"
Hey guys,
I have an European LG G5 H850 with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP once, but I didn't want to install it, but instead keep the stock recovery untouched. So I booted into the bootloader, entered "fastboot boot twrp.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.462s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.482s
I have absolutely no idea what I'm doing wrong. I made sure twrp.img is referring to the correct file, and I tried both the Android SDK platform tools and the 15 seconds ADB installer, but none of them worked. When I try flashing the recovery with "fastboot flash recovery twrp.img", it seems to work because this appears:
target reported max download size of 536870912 bytes
sending 'recovery' (20900 KB)...
OKAY [ 0.471s]
writing 'recovery'...
OKAY [ 0.198s]
finished. total time: 0.670s
But when I try to boot into the bootloader again, it just gives me the option to do a factory reset, nothing else. So I assume that something went wrong. I have absolutely no idea what it could be, so please help me. I also asked on reddit, but didn't get any answers so far. Any help would be greatly appreciated!
Thanks in advance!
JonSchnee777 said:
Hey guys,
I have an European LG G5 H850 with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP once, but I didn't want to install it, but instead keep the stock recovery untouched. So I booted into the bootloader, entered "fastboot boot twrp.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.462s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.482s
I have absolutely no idea what I'm doing wrong. I made sure twrp.img is referring to the correct file, and I tried both the Android SDK platform tools and the 15 seconds ADB installer, but none of them worked. When I try flashing the recovery with "fastboot flash recovery twrp.img", it seems to work because this appears:
target reported max download size of 536870912 bytes
sending 'recovery' (20900 KB)...
OKAY [ 0.471s]
writing 'recovery'...
OKAY [ 0.198s]
finished. total time: 0.670s
But when I try to boot into the bootloader again, it just gives me the option to do a factory reset, nothing else. So I assume that something went wrong. I have absolutely no idea what it could be, so please help me. I also asked on reddit, but didn't get any answers so far. Any help would be greatly appreciated!
Thanks in advance!
Click to expand...
Click to collapse
The "fastboot boot twrp.img" command didn't work for me either, but the keystroke to do a "factory reset" -- which is really a keystroke to enter recovery -- did work. Specifically, I
powered down the LG G5 completely (nothing attached to the USB-C port, or battery pull)
with the power off (preferably via battery pulled), held down the Volume Down and Power/Fingerprint buttons
As soon as the LG logo appeared, released and re-pressed the Power/Fingerprint button, all the while continuing to hold down Volume Down
Held down both while the LG logo showed, releasing them after the white screen appeared asking whether you want to do a full erase. Answer yes (Press and release Volume Down until the Yes is grey, then press Power/Fingerprint button)
It prompts you once again. Answer yes again the same way.
At this point after a few seconds, TWRP starts. It hasn't actually done an erase.
This is important: after fastboot flash recovery twrp.img, you need to pull the battery to power down, and then follow the instructions above to enter TWRP. Do not boot into system with the stock ROM after fastboot. It will replace TWRP with the stock recovery at boot time, and in that scenario, the full erase mentioned above actually does erase data and internal storage.
TWRP will on first start change the system image (once you "allow modification") so that the stock ROM stops replacing it at boot time.
If you did boot up the stock ROM after fastboot, you will need to re-enter fastboot and flash TWRP again (power down with USB-C port clear, hold down Volume Up, insert USB-C cable, fastboot flash recovery twrp.img). Then pull the battery with fastboot still running, then boot into TWRP as above.
Unfortunately most writeups aren't crystal clear about the correct sequence of steps. Most cover some steps and gloss over others.
You aren't doing anything wrong.
LG did not put the typical Fastboot commands into the bootloader.
Fastboot flash does not work either.
You need to follow the other methods available on xda to get TWRP on your device.
Edit: woops. That's only with H830. Follow the instructions in the H850 TWRP thread.
Sent from my LG-H830 using Tapatalk
Tried to ulock with ASUS app v8: "unknon error, probably a network issue, wait and retry" returned
Tried fastboot oem unlock:
OKAY [ 0.019s]
Finished. Total time: 0.020s
Any suggestioin?
I guess I posted the wrong place ... but I don't know where and how to move it ...