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.
Related
I'm trying to de-softbrick an Evo3D for an aquaintance, and I've run out of ideas, so any help this forum is willing to offer is muy apreciada.
Info about phone:
UNLOCKED
HBOOT 1.5
S-ON
Phone will not boot to OS. Phone will boot into hboot. Recovery menu does not function, it shows the fastboot menu instead. Selecting Fastboot takes you to the Fastboot menu, which seems to work fine. Factory Reset option takes you to Fastboot menu.
Initially phone seems to load PG86IMG.zip for flashing, but when the blue loading meter fills up, it says "parsing PG86IMG.zip" for a second and then boots me back to the hboot menu, without asking me to install the file. I've tried both the stock rooted and unrooted zips.
Tried plugging the phone into my computer and running the RUU exe. It will not detect the phone, which I'm guessing is because the phone won't boot into the OS. Also, phone does not appear to respond to any adb or fastboot commands (tried doing adb pull and fastboot reboot, neither worked).
EDIT: Now the phone is detected by the RUU, but I get a 155 error code, and the phone says "Security fail!" and "Update fail!"
Again, any help is appreciated.
What happens when you try to run any fastboot command?
xxjrkkrjxx said:
What happens when you try to run any fastboot command?
Click to expand...
Click to collapse
I get < waiting for device > and it just sits there forever.
try this
Enter FASTBOOT
Open command prompt in your computer
Relock your device by typing "fastboot oem lock" , device will reboot.
Enter FASTBOOT again (you will see *** RELOCKED ***)
Apply the RUU.
RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10. 0808_NV_SPCS_1.31_003_release_219445_signed
http://www.filefactory.com/file/cfd5...445_signed.exe
Your device will be back to stock rom unrooted
Mr.Esp said:
try this
Enter FASTBOOT
Open command prompt in your computer
Relock your device by typing "fastboot oem lock" , device will reboot.
Enter FASTBOOT again (you will see *** RELOCKED ***)
Apply the RUU.
RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10. 0808_NV_SPCS_1.31_003_release_219445_signed
http://www.filefactory.com/file/cfd5...445_signed.exe
Your device will be back to stock rom unrooted
Click to expand...
Click to collapse
Here's the output of the fastboot oem lock (it's responding to fastboot commands now YAY!):
Code:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 66977136 (0x3FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
It does show the phone as relocked now, but right below the pink "***RELOCKED*** I also have ***SECURITY WARNING***. The security warning part seems to go away if I boot into hboot with the sd card removed.
EDIT: RUU worked on the second try after this. Thanks a ton!
I'm having the same issue but the link to the RUU does not work anymore, can anyone repost?
martymania85 said:
I'm having the same issue but the link to the RUU does not work anymore, can anyone repost?
Click to expand...
Click to collapse
http://tinyurl.com/6tauv3b
billdozer357 said:
Here's the output of the fastboot oem lock (it's responding to fastboot commands now YAY!):
Code:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 66977136 (0x3FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
It does show the phone as relocked now, but right below the pink "***RELOCKED*** I also have ***SECURITY WARNING***. The security warning part seems to go away if I boot into hboot with the sd card removed.
EDIT: RUU worked on the second try after this. Thanks a ton!
Click to expand...
Click to collapse
Does USB come up next to Fastboot? If so can you reflash CWM?
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?
a bit similer with this case
my friend bought it 20 days ago and he unlock it
but he cant flash twrp as like guides
he had no expirience before this
so i get tablet and tried to solve the problem but
fastboot doesnt work properly
fastboot devices/reboot/device-info works
but
fastboot flash recovery twrp.img/ flash boot boot.img(guide on carbon rom)/boot twrp.img/and etc that for flashing or change any system
does not work
massage like failed(long link/bigger than max allowed)
changing everytime i try
i though there might some issues when my friend unlock the bootloader
so i 'fastboot oem lock' and try to unlock again
but from then fastboot not work properly
can be boot or 'adb reboot fastboot' to fastboot
but it become unknown device on windows device manager
fastboot command not work
when mi flash try to detect device, fastboot mode end and 'press any key to power off' screen came out
some times it working for few seconds so i try unlock with official xiaomi tool but tool said 'already unlocked'
right after i locked bootloader i used 'fastboot oem device-info' and checked bootloader is locked
i can switch oem unlock on/off in developer option but it doesnt change anything
i searched as i can and edl mode looks last
but few things to consider
1. its official chinese rom and working now
2. i dont know broken fastboot can be restored with flashing rom with edl (i flash rom with update app in settings but not solved)
3. adb reboot edl doesnt work it just rebooted(should teardown it but i dont know what pin to short)
the reason why i trying to install custom rom(or eu rom) is my friend and i not live in native english country
hope i get some help
thx
Ryzen CPU?
thE_29 said:
Ryzen CPU?
Click to expand...
Click to collapse
ryzen 1, 2, intel sandy etc
tried all i got
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
KrakmanCz said:
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
Click to expand...
Click to collapse
nope
cant go into edl mode until i teardown it
miflash 2018 doesnt connect with pad on fastboot mode
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
chocodesk said:
ryzen 1, 2, intel sandy etc
tried all i got
Click to expand...
Click to collapse
Ok, when you also tried Intel.. But Ryzen CPUs have major problems with the flash tool and the tablet. Would not do anything on Ryzen PCs.
KrakmanCz said:
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
Click to expand...
Click to collapse
on basic
with was detected as fastboot before
but know its unknown on device manager
update driver doesnt work
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Dannyboy3210 said:
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Click to expand...
Click to collapse
i tried 2.0 and 3.0
not work
tablet owner decide to use it on stock chinese rom
not in my hand now
$ adb reboot bootloader
List devices on fastboot :
$ fastboot devices
XXXXXX fastboot
Check if bootloader is unlocked :
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.003s
Flash TWRP recovery :
$ fastboot flash recovery recovery.img
Sending 'recovery' (54400 KB) OKAY [ 1.540s]
Writing 'recovery' OKAY [ 0.410s]
Finished. Total time: 1.952s
Reboot your device
$ fastboot reboot
Rebooting
Finished. Total time: 0.000s
I installed TWRP on MIUI 10 using this description. On the end , after TWRP installed - I rebooted again to TWRP and installed stock rom at once . I not tested , but theory says , MIUI will reflash recovery if it will be booted in this situation .
Sorry to piggy-back off this post, but I'm having a similar issue with my Mi Pad I just received:
I can boot it into Fastboot mode no problem, even see it listed when I use the "Fastboot devices" command. When I run the OEM info everything comes back true for unlocked.
However, when I try to flash anything I get the max size error or just a "FAILED" and it kicks the Mi Pad to a black screen with the white text "Press any key to shut down".
Any ideas?
*edit*
I've continued testing, and I'm really at a loss here. See the response I'm getting using fastboot:
\minimal_adb_fastboot_1.4.3_portable>fastboot flash boot kernel.img
target didn't report max-download-size
sending 'boot' (15060 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I can transfer files in windows no problem... I can use adb commands no problem... fastboot just doesnt seem to work.
I figured out my issue. You cannot use USB 3 ports to connect and run fastboot commands. I bought a cheap USB 2 hub, ran the cable from that and had no problems at all.
Getting super frustrated!
Using ADB Debuging. Here are my steps.
1. adb devices
2. adb reboot bootloader
3.fastboot devices.
4. fastboot oem unlock
Then I get this...
FAILED (remote: unknown command)
finished. total time: 0.005s
after so many attempts I finally check adb devices and nothing shows up! It's like it automatically disconnects with adb debugging but it does not. Because I am able to to put fastboot reboot.
Can someone please help me with this! Thank you!
Use the fast boot command
Fastboot flashing unlock
Only this works on A12 devices
fastboot flashing unlock
oem unlock has been deprecated for awhile, manufacturers were just slow to implement changes.
I'm currently trying to unlock the bootloader on my Tecno Spark 8C, model KG5K. A fairly new phone brand, so documents regarding this is really shallow.
So I opted for ways that are supported on a variety of Android phones instead. I've used every way possible that I can find. ADB, Magisk, TWRP,... but none has worked, because of one sole reason: the Fastboot. So, essentially what is happening to the Fastboot is that it's seems to be missing a LOT of typical features in a Fastboot, like flashing unlock and OEM unlock.
I tried turning on OEM unlock in settings and made sure USB debugging is enabled, disabled all of the security features and even checked if my phone is ALWAYS transferring files to my laptop, but nothing is phasing the Fastboot unknown command and unlock bootloader failed error messages.
The only imaginative option that I can think of now, is whether if I can update/replace the original Fastboot that came with my phone, but I can't explain it in technical terms, or even know if such a method existed.
I would appreciate all the help I can, thanks to all of you in advance.
mayberandomparable said:
I'm currently trying to unlock the bootloader on my Tecno Spark 8C, model KG5K. A fairly new phone brand, so documents regarding this is really shallow.
So I opted for ways that are supported on a variety of Android phones instead. I've used every way possible that I can find. ADB, Magisk, TWRP,... but none has worked, because of one sole reason: the Fastboot. So, essentially what is happening to the Fastboot is that it's seems to be missing a LOT of typical features in a Fastboot, like flashing unlock and OEM unlock.
I tried turning on OEM unlock in settings and made sure USB debugging is enabled, disabled all of the security features and even checked if my phone is ALWAYS transferring files to my laptop, but nothing is phasing the Fastboot unknown command and unlock bootloader failed error messages.
The only imaginative option that I can think of now, is whether if I can update/replace the original Fastboot that came with my phone, but I can't explain it in technical terms, or even know if such a method existed.
I would appreciate all the help I can, thanks to all of you in advance.
Click to expand...
Click to collapse
In fastboot mode, is your phone recognised with a random string of numbers or alpha-numeric characters? If not, you may lack the fastboot drivers which are distinct from adb drivers. Please install the Platform Tools from this link and try.
TNSMANI said:
In fastboot mode, is your phone recognised with a random string of numbers or alpha-numeric characters? If not, you may lack the fastboot drivers which are distinct from adb drivers. Please install the Platform Tools from this link and try.
Click to expand...
Click to collapse
080293723C004560
Does this qualifies as having distinct drivers? I'm not too sure.
mayberandomparable said:
080293723C004560
Click to expand...
Click to collapse
If that is the response to the 'Fastboot devices' command and the same is shown when you issue the 'adb devices' command (while in adb mode) then you have no driver issue. What about the Platform Tools that you use (you said that several commands were missing), did you try the one I linked?
Further, the bootloader unlock command varies between devices and what works for one model may not work for another. You have to search for the proper command for your device.
Code:
C:\>fastboot devices
C:\>fastboot getvar version
C:\>fastboot getvar all
TNSMANI said:
If that is the response to the 'Fastboot devices' command and the same is shown when you issue the 'adb devices' command (while in adb mode) then you have no driver issue. What about the Platform Tools that you use (you said that several commands were missing), did you try the one I linked?
Further, the bootloader unlock command varies between devices and what works for one model may not work for another. You have to search for the proper command for your device.
Click to expand...
Click to collapse
I tried the commands, but one stood out because of the output it given. Fastboot getvar all returned nothing for all. And I did try the official Android platform-tools, but it's still the same results, I'm afraid.
Beside that, getvar version given a 1.0 version. Checked the device ID on both modes, they're the same.
Also, I did extensively search for any sliver of documentation on the fastboot of this device, but I basically got nothing, since this device is still fairly new.
Fastboot is a bit of a weird animal.
The desktop executable knows valid commands and will not even attempt something that it doesn't know.
Code:
C:\>fastboot fishheads
fastboot: usage: unknown command fishheads
C:\>fastboot oem fishheads
FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\>fastboot erase fishheads
Erasing 'fishheads' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
The first error is local, the second one is remote because the desktop knows "oem" is good and doesn't care after that.
The third fails on no partition called "fishheads", but it tried. Try that and these:
Code:
C:\>fastboot getvar product
C:\>fastboot getvar serial
C:\>fastboot getvar unlocked
C:\>fastboot getvar variant
C:\>fastboot getvar partition-size:boot
C:\>fastboot getvar partition-size:boot_a
C:\>fastboot getvar partition-size:boot_b
Renate said:
Fastboot is a bit of a weird animal.
The desktop executable knows valid commands and will not even attempt something that it doesn't know.
Code:
C:\>fastboot fishheads
fastboot: usage: unknown command fishheads
C:\>fastboot oem fishheads
FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\>fastboot erase fishheads
Erasing 'fishheads' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
The first error is local, the second one is remote because the desktop knows "oem" is good and doesn't care after that.
The third fails on no partition called "fishheads", but it tried. Try that and these:
Code:
C:\>fastboot getvar product
C:\>fastboot getvar serial
C:\>fastboot getvar unlocked
C:\>fastboot getvar variant
C:\>fastboot getvar partition-size:boot
C:\>fastboot getvar partition-size:boot_a
C:\>fastboot getvar partition-size:boot_b
Click to expand...
Click to collapse
I might picking up what you're putting down here.
The first 3 getvar(s) returned empty, partition-size:boot returned a failure, but boot_a and boot_b returned the same 0x4000000
@mayberandomparable
Did you try 'fastboot flashing unlock' command or 'fastboot oem unlock' command? If all such commands fail, you may need a special unlock zip file which seems to be available for the 8 Pro model but not for yours (https://forum.xda-developers.com/t/twrp-for-tecno-spark-8-pro-kg8-root-other-guide.4477425/).
Did you try fastboot erase fishheads
It could tell you that your device is locked.
Renate said:
Did you try fastboot erase fishheads
It could tell you that your device is locked.
Click to expand...
Click to collapse
Got the "Flashing Lock Flag is locked. Please unlock it first!", chief.
TNSMANI said:
@mayberandomparable
Did you try 'fastboot flashing unlock' command or 'fastboot oem unlock' command? If all such commands fail, you may need a special unlock zip file which seems to be available for the 8 Pro model but not for yours (https://forum.xda-developers.com/t/twrp-for-tecno-spark-8-pro-kg8-root-other-guide.4477425/).
Click to expand...
Click to collapse
Got stuck.
(ignore me listening to PATD, forgot for a moment)
The "special unlock zip file" is just a script that requires that fastboot flashing unlock works.
You made me watch that video of PATD. It's kind of violent, eh?
Renate said:
The "special unlock zip file" is just a script that requires that fastboot flashing unlock works.
Click to expand...
Click to collapse
Oh shoot, yeah it is.
Well, we're going in circles now.
mayberandomparable said:
Got the "Flashing Lock Flag is locked. Please unlock it first!", chief.
Click to expand...
Click to collapse
So, is this operation possible?
It could be that the OEM unlocking in Android Settings is broken/ineffective.
It could be that the fastboot needs some oem command.
Like (hypothetically) fastboot oem secret-unlocking-command pwd12345
Now, if you had a copy of abl we could reverse engineer it.
Have you tried to see if you can reach fastbootd? That's the user space fastboot that's in some Android.
Check if there is a difference between adb reboot bootloader and adb reboot fastboot
Is this a Qualcomm thing? Have you tried EDL? adb reboot edl
Renate said:
It could be that the OEM unlocking in Android Settings is broken/ineffective.
It could be that the fastboot needs some oem command.
Like (hypothetically) fastboot oem secret-unlocking-command pwd12345
Now, if you had a copy of abl we could reverse engineer it.
Have you tried to see if you can reach fastbootd? That's the user space fastboot that's in some Android.
Check if there is a difference between adb reboot bootloader and adb reboot fastboot
Is this a Qualcomm thing? Have you tried EDL? adb reboot edl
Click to expand...
Click to collapse
Hardly a Qualcomm thing, since this is using UNISOC.
Also, yes, it does have a fastbootd mode. Found on a whim!
Edit: Just tried EDL, sent straight back to the regular reboot command.
So... Does this other fastboot react at all differently?
Renate said:
So... Does this other fastboot react at all differently?
Click to expand...
Click to collapse
Oh I got something! The flashing unlock didn't work, guessing the manufacturer changed it. But OEM works flawlessly!
The last time I tried to do anything on fastbootd, platform-tools didn't even recognized the device, but now it works!
mayberandomparable said:
... but now it works!
Click to expand...
Click to collapse
So, can you fastboot erase fishheads
Renate said:
So, can you fastboot erase fishheads
Click to expand...
Click to collapse
Oop- still got a locked error, unfortunately.