Related
I have the phone in Bootloader mode (holding down power and volume down keys). I have all the required software installed. I use the command prompt to get my token and copy the info into the requisite slot in the HTC website window and when I hit the continue button I get an error message "Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work"
I have tried multiple times on two different computers. Always the same error. It is 7:30 pm EDT. I need help cuz I may be running out of time.
DiggerG said:
I have the phone in Bootloader mode (holding down power and volume down keys). I have all the required software installed. I use the command prompt to get my token and copy the info into the requisite slot in the HTC website window and when I hit the continue button I get an error message "Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work"
I have tried multiple times on two different computers. Always the same error. It is 7:30 pm EDT. I need help cuz I may be running out of time.
Click to expand...
Click to collapse
You aren't copying it right. Read the instructions and ensure you are only copying the information it wants
Sent from my HTC One using xda premium
Finally got it to work, but I'm not sure what I did differently. Put Command prompt window next to website window and that did it, but don't know why. Anyhow I have my email.
And I'm unlocked!!!
mine is stuck at waiting for device after i put in the command. Is there anyway anyone can send me the fastboot, adb, and adbwinapi.dll they used? I'm wondering if mine just isn't the right one but they should be. also i have the phone hooked up first and then go into fastboot and it says fastboot usb before i type in the command
thanks for any help
What do you mean "Stuck waiting for device after I put in the command"? If you pm me an email address, I can send the files tonight when I return from work.
DiggerG said:
What do you mean "Stuck waiting for device after I put in the command"? If you pm me an email address, I can send the files tonight when I return from work.
Click to expand...
Click to collapse
I type in "fastboot oem get_identifier_token" and then it displays waiting for device but doesn't do anything after that I waited for 30 minutes the first time and it stayed saying that. Ok I'll PM it now thank you
brom66an6 said:
I type in "fastboot oem get_identifier_token" and then it displays waiting for device but doesn't do anything after that I waited for 30 minutes the first time and it stayed saying that. Ok I'll PM it now thank you
Click to expand...
Click to collapse
The device isnt connected properly to the computer. Make sure you open your command prompt in the android folder and have the files within the same folder (i did this on OS X)
And then check to make sure you the computer recognizes the phone with
fastboot devices
You should see your device listed if it is connected properly.
brom66an6 said:
I type in "fastboot oem get_identifier_token" and then it displays waiting for device but doesn't do anything after that I waited for 30 minutes the first time and it stayed saying that. Ok I'll PM it now thank you
Click to expand...
Click to collapse
Did you install the HTC Sync Manager or install the HTC USB drivers from another source? Your phone won't be detected until you have the drivers installed. (I'm assuming you're using a Windows computer)
brom66an6 said:
mine is stuck at waiting for device after i put in the command. Is there anyway anyone can send me the fastboot, adb, and adbwinapi.dll they used? I'm wondering if mine just isn't the right one but they should be. also i have the phone hooked up first and then go into fastboot and it says fastboot usb before i type in the command
Either need htc drivers or your not in fastboot usb/bootloader
thanks for any help
Click to expand...
Click to collapse
If your getting that error, you have fastboot and adb but you haven't installed htc drivers yet.
If you don't have fastboot/adb files you will get a unknow command error.
Sent from my SPH-L710 using Tapatalk 2
*edit - I got it taken care of now i uninstalled and reinstalled the drivers and it worked this time. Thank you everyone for the help.
has anyone received the "Error Code (10) A request for the USB descriptor failed" error message? i can't get my laptop to seen my device in fastboot mode. i've installed/uninstalled the HTC drivers but no change. weird part is that i can communicate with my device via ADB when booted normally. any suggestions would be appreciated.
Waiting (and waiting) for device
18th.abn said:
If your getting that error, you have fastboot and adb but you haven't installed htc drivers yet.
If you don't have fastboot/adb files you will get a unknow command error.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I'm having exactly the same issue as brom66an6. fastboot starts, but never proceeds from "waiting for the device". If this is a driver problem, what drivers need to be installed on the phone?
what next??? I have the identifier token..
DiggerG said:
And I'm unlocked!!!
Click to expand...
Click to collapse
Great for you, I can't wait to get there myself.
It was late last night and I was one click away, but wan't sure how long until the next break stop would be, so I went to bed.
Now, I cannot recall what I was supposed to do. Can anyone please shed some light on the next instructions, I can no longer access these as I believe it was shown when you click to continue??
I have all the files/drivers and token placed in the same location on my drive and as a guess I've also copied the token .zip file to the SDcard on my HTC One X (vodafone stamped
I really wished they have a removable battery and media card support!! I have just purchased a new battery from eBay that proclaims a new chip on it that prevents overcharging. So that should be interesting, since the HTC charger is not a switching charger like my BlackBerry ones were.
What I want:
ROOT
a new clean/fast/efficient ROM, was thinking clockworkmod.
Since I have zero experience and limited time to troll through forums these days, I am really finding it hard to find a REALLY simple step by step guide to perform this. I know, it's not a simple proccess, I know, but perhaps just the steps in a efficient, simple list, overlooking stuff like backups etc, but perhaps a TIP to mention it would be a good idea as the next step will wipe everything etc
Thanks if you're still reading and perhaps WERE at my stage once before.
I'm sure custom ROMs are a personal preference, but any bad points about ROMs would probably be better than selling the good points.
CWM should be fine for my first attempt???
MANY thanks in advance for your time.
Steve.
[EDIT]
I'm now unlocked!!!!
I found the website that I was following, it is fantastic and just the right amount of simple for me.
Check it out...
www*droid-now*com/2013/08/htc-one-unlocking-bootloader-installing-custom-recovery-and-root/
Amazing Thanks..
DiggerG said:
Finally got it to work, but I'm not sure what I did differently. Put Command prompt window next to website window and that did it, but don't know why. Anyhow I have my email.
Click to expand...
Click to collapse
That sounds stupid... but it works, worked for me...
hi
i am trying to unlock the bootlaoder for my new htc m9
after i got the unloch_code, i receive this msg in cmd
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.038s
please help
what is missing ?
Can someone answer this
My htc one x9 gets recognized by my laptop everything works well
Lequired software is installed properly
And i try to type in fastboot devices and my phone appears to be in fastboot
But when i type fastboot oem get_identifier_token it says FAILED(remote:unknown command)
Finished.time:0.005
Plz im begging for help
Mine struck after the entry of code fastboot OEM get_identifier_token and my device is already detected and it's showing three dots "..." And that's it
Hey everyone,
So I've been having a problem with my Z Ultra that I haven't been able to solve for a number of weeks now.
The service menu on my C6833 specifically says that the bootloader is unlockable, as shown here:
(imgur) com/OO9549 (sorry, XDA won't let me post links yet. ><)
However, when I try unlocking using Sony's official instructions (and using FlashTool) - I get the following:
fastboot -i 0x0ffce oem unlock 0x(my key here)
...
FAILED (remote: Command did not succeed)
finished. total time: 0.027s
I've copied/pasted the key, I've typed it out manually, they all get me the same error. I'm running Windows 8.1 (finally managed to get the drivers installed), yet this also happened on a Windows 7 machine. I've been racking my brain, but I can't find ANYTHING that'll help. The last time I tried, I gave up trying to unlock the bootloader and installed the DualRecovery for locked bootloaders, which ended up bricking my phone and I had to flash back to stock.
Help! I just want to be able to install custom roms again! D:
Hmm, that's strange. I've googled a bit and you're not the first xperia owner with this issue. Some say that updating or re-flashing the ROM will fix it. Which version are you running?
LordManhattan said:
Hmm, that's strange. I've googled a bit and you're not the first xperia owner with this issue. Some say that updating or re-flashing the ROM will fix it. Which version are you running?
Click to expand...
Click to collapse
I've re-flashed the ROM a few times on different versions. I'm currently on 4.2.2 - 14.1.B.2.257.
Mandersoon said:
Hey everyone,
So I've been having a problem with my Z Ultra that I haven't been able to solve for a number of weeks now.
The service menu on my C6833 specifically says that the bootloader is unlockable, as shown here:
(imgur) com/OO9549 (sorry, XDA won't let me post links yet. ><)
However, when I try unlocking using Sony's official instructions (and using FlashTool) - I get the following:
fastboot -i 0x0ffce oem unlock 0x(my key here)
...
FAILED (remote: Command did not succeed)
finished. total time: 0.027s
I've copied/pasted the key, I've typed it out manually, they all get me the same error. I'm running Windows 8.1 (finally managed to get the drivers installed), yet this also happened on a Windows 7 machine. I've been racking my brain, but I can't find ANYTHING that'll help. The last time I tried, I gave up trying to unlock the bootloader and installed the DualRecovery for locked bootloaders, which ended up bricking my phone and I had to flash back to stock.
Help! I just want to be able to install custom roms again! D:
Click to expand...
Click to collapse
I had the same problem when I tried to unlock.
Tried 5 times and then was finally successful. Ensure that you have typed out the commands correctly. Don't copy and paste as that wont work.
Are you getting the same error in Flashtool?
Sent from my C6833 using Tapatalk
LordManhattan said:
Are you getting the same error in Flashtool?
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
I can't be sure as it was 3/4 months ago. Kept having issues, and I gave up. Then came back and after many attempts it worked. It was incorrect commands i was typing. 0 or O may have been the problem, or no space where they should be one.
If it says command failed then it sounds like you have the command correct, but the key is incorrect or the format of your input after the command is incorrect.
Also... are you rooted? Root first then try agian
hamdogg said:
I can't be sure as it was 3/4 months ago. Kept having issues, and I gave up. Then came back and after many attempts it worked. It was incorrect commands i was typing. 0 or O may have been the problem, or no space where they should be one.
If it says command failed then it sounds like you have the command correct, but the key is incorrect or the format of your input after the command is incorrect.
Also... are you rooted? Root first then try agian
Click to expand...
Click to collapse
I have copied/pasted, as well as typing out the commands. This has happened with Flashtool as well as in the command prompt.
And the phone is rooted.
EDIT:
I figured out the problem. I ended up using flashtool for the whole process. Windows 8.1's Driver Signature Verification NEEDS to be turned off. I ended up getting a new unlock code from Sony and that worked.
Mandersoon said:
I have copied/pasted, as well as typing out the commands. This has happened with Flashtool as well as in the command prompt.
And the phone is rooted.
EDIT:
I figured out the problem. I ended up using flashtool for the whole process. Windows 8.1's Driver Signature Verification NEEDS to be turned off. I ended up getting a new unlock code from Sony and that worked.
Click to expand...
Click to collapse
Hi Mandersoon,
I am in same problem and do you have any link or email to get new Unlock code from sony?
Thanks.
Encountered this on my first try. Then on the second attempt, it went through.
i had the same problem, it said "FAILED (remote: Incorrect format for unlock data. Should be on the form "0x)" so I did exactly as it said - added "0x" before my code and it worked!
I just removed "0x" from the unlock code given by sony, it worked like a charm. :good:
I dont know why.
BlackCatAlex said:
i had the same problem, it said "FAILED (remote: Incorrect format for unlock data. Should be on the form "0x)" so I did exactly as it said - added "0x" before my code and it worked!
Click to expand...
Click to collapse
can you please share the code i cant understand where to add 0x. i am facing the same issue. reply ASAP
Do not share the code/key. That's your unique key.
@psylbaba: it says "added "0x" before my code", so I assume he means 0x in front of the key when you're unlocking in Flashtool.
I just.....removed 0x and the <> in my code and it worked like a charm. Curious. (XZ1 user here)
Hi, found this thread when I was trying to unlock a Xperia z2, for me worked removing only the <> like this: fastboot oem unlock 0x"CODE"
Right click, administrator mode
Hi all i coming nere because i ve bought a huawei y330 and simply rooted (not alla permission canto install xposed) are there cwm and custom ROM for this device ?
huawei y330
help experts we need a custom rom for huawei y330 u11
lo siento pero por el momento no hay cwm
fijate que e tratado de ponerle el cwm pero nada no pude pero en mi logica talves sera que funciona el mismo cwm del y320 en el y300: Confundido:
BlackDemon503 said:
fijate que e tratado de ponerle el cwm pero nada no pude pero en mi logica talves sera que funciona el mismo cwm del y320 en el y300: Confundido:
Click to expand...
Click to collapse
plz translate in english
xXoglocXx said:
Hi all i coming nere because i ve bought a huawei y330 and simply rooted (not alla permission canto install xposed) are there cwm and custom ROM for this device ?
Click to expand...
Click to collapse
You can try mtk tools to make cwm recovery for your device
Sent from my x604 using Tapatalk
The-Immortal said:
You can try mtk tools to make cwm recovery for your device
Sent from my x604 using Tapatalk
Click to expand...
Click to collapse
wan't work, bricked phone with mtk tools
but thx anyway
any other method for flushing a custom recovery on this phone
Huawei Y330
bidarius said:
wan't work, bricked phone with mtk tools
but thx anyway
any other method for flushing a custom recovery on this phone
Huawei Y330
Click to expand...
Click to collapse
Do you know how to unbrick it?
i followed this thred worked for me, only spanish firmware sorry
movilesdualsim.com/tema/huawei-y330-u01-descarga-y-tutorial-instalacion.79190
Any movement on this? anyone find a working custom rom for this p.o.s.
Found working ROMs for this phone (Y330-U01 model). Some of the pages are in italian, but I managed to follow it with Google Translate. The italian forum requires registration. Rom itself has many languages presumably all that are in stock, English included.
Do any of this on your own responsibility, if something goes wrong it's not my fault. It worked for me on UK bought Y330-U01.
You might want to make copy of stock HwSettings.apk and HwSettings.odex - I needed to replace those for the 2nd rom as the included one was crashing now and then. Your mileage might vary.
Since it's my 1st post I can't post links, the links to tutorials and roms are at:
pastebin <dot> com <slash> Z8faVVe8
Notes from my experiences with installation:
for material themed rom: I had to replace HwSettings.apk and HwSettings.odex with ones from stock rom as the included crashed every now and then.
Xposed installation:
The material themed one includes Xposed by default (the theming is done via MonsterUI module) but it's old version so you might want to upgrade. If you just install newest Xposed (I use 2.7 experimental1) the theming will not work due to some bs around stock theme engine or whatnot. To make it work edit the phone's build.prop and set ro.config.hwtheme to 0, reboot phone.
Enjoy.
C.G.B. Spender said:
Found working ROMs for this phone (Y330-U01 model). Some of the pages are in italian, but I managed to follow it with Google Translate. The italian forum requires registration. Rom itself has many languages presumably all that are in stock, English included.
Click to expand...
Click to collapse
Thx man, I am checking your instructions right now, here the pastebin link since you can't post links. Btw the forum (phonenandroid) you mentioned is in French (not Italian). I'm posting for convenience the links you shared on pastebin:
stock UK rom (takes forever to download, but handy if you brick the phone)
http://consumer.huawei.com/uk/suppo...ex.htm?id=23023&pname=Y330-U01&pcode=Y330-U01
to unlock bootloader:
http://www.modaco.com/topic/362821-...ith-definitions-relock-guide-included/page-17
to install CWM recovery: (it can't mount external SD because it looks for it in wrong place, but flashing etc works):
http://www.phonandroid.com/forum/y330-custom-recovery-installation-t114528.html
rooted stock rom:
http://www.phonandroid.com/forum/rom-huawei-y330-u01-root-t117554.html
rooted stock material themed: (read note below)
http://www.phonandroid.com/forum/huawei-y330-material-by-speedo-t120876.html
Feel free to share more info about your experience. There is actually almost no custom rom for the Huawei Ascend Y330 so it's really important to share as much as you can. Thanks again & cheers.
I'm following the tutorial: https://www.dc-unlocker.com/free-huawei-bootloader-unlock-tutorial
I'm blocked here:
Turn off phone. Press "Volume down", "Volume up" and "Power" buttons. Hold them pressed for 5 seconds. Phone screen should become purple/pink. Connect phone to computer using USB cable
Click to expand...
Click to collapse
If I press voume down + voume up + power, my phone goes in recovery mode. It doesn't turn pink. If I press just volume down + power it goes into fastboot.
How the heck do I turn it pink as in the tutorial?
Or maybe if I see a recovery screen, it means my bootloader is already unlocked?
Hi,
thanks for linkifying my post. You're right it's in french not italian - pardon my ignorance. As for the step with the pink screen I didn't have pink screen either I think the point of the step is to get the phone to the unbooted state but accessible by adb so fastboot should do fine (I'm no expert though - I did many trial and errors on the steps due to the fact it was google translated, iirc vol up+power = recovery, vol down+power = fastboot - try both and whichever leads to successful next step was it (i think it's fastboot since the adb shell uses fastboot command to do stuff with bootloader in the guide)).
To check whether your bootloader is already unlocked do "fastboot oem get-bootinfo" (look at very last step from the dc-unlocker guide)
Sorry for not being any more helpful and good luck!
C.G.B. Spender said:
Hi,
thanks for linkifying my post. You're right it's in french not italian - pardon my ignorance. As for the step with the pink screen I didn't have pink screen either I think the point of the step is to get the phone to the unbooted state but accessible by adb so fastboot should do fine (I'm no expert though - I did many trial and errors on the steps due to the fact it was google translated, iirc vol up+power = recovery, vol down+power = fastboot - try both and whichever leads to successful next step was it (i think it's fastboot since the adb shell uses fastboot command to do stuff with bootloader in the guide)).
Click to expand...
Click to collapse
That French guy, Speedo4android is really damn cool! I'll thank him personally in French for this! And no sorry, I was just a bit puzzled looking around for Italian text and realized after a bit that maybe you just confused it with French, no big deal
vol down + power (fastboot) was the correct one.
C.G.B. Spender said:
To check whether your bootloader is already unlocked do "fastboot oem get-bootinfo" (look at very last step from the dc-unlocker guide)
Click to expand...
Click to collapse
Thanks very much for this command. I didn't know it! In my case it seems the adb/phone drivers were already installed as well as the adb tools. So I could issue (reposting for new users reading this) these commands:
Code:
fastboot devices
fastboot oem get-bootinfo
fastboot devices is the same as "adb devices". Just it lists devices (if connected) in fastboot mode. I could see my device. Issuing the second command showed me that the bootloader was already unlocked, so indeed no need to see the pink screen.
That said I proceeded to the tutorial to install the CWM recovery. It was a bit tricky to install the proper drivers. If somebody has problems with this, the answer is a google search to "adb drivers windows 8.1" (assuming one is using Windows 8.1, but I guess so) and find this: Fastboot Drivers Windows 8.1 [FIX] x64. To sum up, you have to allow Windows 8.1 to install unsigned drivers, like this:
DiogoCMartins said:
Press Windows Key + R (or go to Run)
Type “shutdown.exe /r /o /f /t 00″
Go to Troubleshoot –> Advanced options –> Start Up Settings –> Restart
After a computer soft reboot, hit Option 7 (Disable driver signature enforcement)
Restart your PC
Click to expand...
Click to collapse
That helped me a lot (other tutorials suggest point and click, I prefer one command via shutdown (with options)... as quoted above.
Tricky thing number 2 was to install the MTK Preloader Mediatek drivers for the device in fastboot mode. Check this out: HOW TO INSTALL MTK65XX PRELOADER USB VCOM DRIVERS IN WINDOWS
C.G.B. Spender said:
Sorry for not being any more helpful and good luck!
Click to expand...
Click to collapse
On the contrary, without your post I would have never be able to own this device, I almost lost hope when I read that no DEV is interested to create custom roms for this device... I was thinking it would be a pain to install CWM and in fact it was, but finally I got it! Maybe some DEVs will be interested to create more roms for this device... let's see. Thank you!
And thanks to Speedo4android for the hard work!
Speedo see you
firepol said:
That French guy, Speedo4android is really damn cool! I'll thank him personally in French for this! And no sorry, I was just a bit puzzled looking around for Italian text and realized after a bit that maybe you just confused it with French, no big deal ... And thanks to Speedo4android for the hard work!
Click to expand...
Click to collapse
Hello , i come here to tell you that a new version is allready on line , with the original fonts and a new théme , it's little diferent than the beta theme and fonts i send you last month.
now i'am sure it will work 100% stock fonts and can be change with theming engine.
More Screenshots here :http://www.phonandroid.com/forum/huawei-y330-material-by-speedo-t120876-40.html
direct link: https://drive.google.com/file/d/0B3kJoB8n78hZaTM1LU83TlRhcDA/view?usp=sharing
Just do a wipe cache and dalvik before install if comming from Material V2.0
flash Gapps again coz i delete it to clean system !! https://drive.google.com/file/d/0B3kJoB8n78hZRkJxVXBVc2hqMUE/view?usp=sharing
Thx for this post and feedback
Cordialement
Speedo.
Speedo.thc said:
Hello , i come here to tell you that a new version is allready on line , with the original fonts and a new théme , it's little diferent than the beta theme and fonts i send you last month.
now i'am sure it will work 100% stock fonts and can be change with theming engine.
More Screenshots here :http://www.phonandroid.com/forum/huawei-y330-material-by-speedo-t120876-40.html
direct link: https://drive.google.com/file/d/0B3kJoB8n78hZaTM1LU83TlRhcDA/view?usp=sharing
Just do a wipe cache and dalvik before install if comming from Material V2.0
flash Gapps again coz i delete it to clean system !! https://drive.google.com/file/d/0B3kJoB8n78hZRkJxVXBVc2hqMUE/view?usp=sharing
Thx for this post and feedback
Cordialement
Speedo.
Click to expand...
Click to collapse
Thank you Speedo, I wiped cache/dalvik cache, flashed Y330_Material_3Csign.zip, then flashed GappsV20sign.zip and it looks nice!
No succes
I've tried to unlock the bootloader with the fastboot oem unlock UUUUUUUUUUUUUUUU command, but this didn't worked. dc-unlocker didn't found the phone in fastboot mode. Does anyone have an idea. I tried to install the Windows 8 fix but when it was installed the Universal Bus Driver didn't worked after the installation. Am I fully screwed?
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.004s
C:\Windows\system32>fastboot oem unlock UUUUUUUUUUUUUUUU
...
FAILED (status read failed (Too many links))
finished. total time: 6772.110s
C:\Windows\system32>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Windows\system32>fastboot oem unlock UUUUUUUUUUUUUUUU
...
FAILED (status read failed (Too many links))
finished. total time: 17268.257s
Code:
C:\Windows\system32>fastboot oem unlock UUUUUUUUUUUUUUUU
< waiting for device >
...
FAILED (status read failed (Too many links))
finished. total time: 1172.944s
UPDATE:
The too many links error appears when the phone is disconnected while the process is running. Seems like there is nothing happening until the battery dies.
Bruno-der-Sumo said:
I've tried to unlock the bootloader with the fastboot oem unlock UUUUUUUUUUUUUUUU command, but this didn't worked. dc-unlocker didn't found the phone in fastboot mode. Does anyone have an idea. I tried to install the Windows 8 fix but when it was installed the Universal Bus Driver didn't worked after the installation. Am I fully screwed?
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.004s
C:\Windows\system32>fastboot oem unlock UUUUUUUUUUUUUUUU
...
FAILED (status read failed (Too many links))
finished. total time: 6772.110s
C:\Windows\system32>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Windows\system32>fastboot oem unlock UUUUUUUUUUUUUUUU
...
FAILED (status read failed (Too many links))
finished. total time: 17268.257s
Code:
C:\Windows\system32>fastboot oem unlock UUUUUUUUUUUUUUUU
< waiting for device >
...
FAILED (status read failed (Too many links))
finished. total time: 1172.944s
UPDATE:
The too many links error appears when the phone is disconnected while the process is running. Seems like there is nothing happening until the battery dies.
Click to expand...
Click to collapse
try adb oem unlock UUUUUUUUUUUUUUUU . it worked to me. i had the same problem like you.
After a day of messing around I got it to work.
I can't update the Xposed framework, says there's another app with the same name and same credentials or something.
Also: greenify keeps complaining that the auto-hibernation is not working, but I didn't inhibit it anywhere. Ideas?
The phone feels slightly hotter than before, but it's also very warm here anyway.
Thanks for all the tips and of course to Speedo
this allowed me to install and use Xposed 2.6..1:
Code:
With a proper build.prop editor:
Find this line: ro.config.hwtheme=1 (or 2, it depends on your device)
Change to: ro.config.hwtheme=0
a
Has anyone deleted the "Phone Manager" app? it wakes the cpu a ridiculous amount of times...
I just bought a Redmi 3S and I am not fond of the software. So I want to root it and put CM on it.
So I am trying to do like this guy: http://forum.xda-developers.com/showpost.php?p=66990194&postcount=36
but I cannot get the USB / adb to work. When I connect it to my computer a folder called "RedmI 3S" pops up but I cannot copy any files to it and I cannot see the device from adb. I tried to install the Mi PC suite but it says to update my device before connecting (which seems to be a bug in the suite: http://en.miui.com/forum.php?mod=viewthread&tid=96111&highlight=update+your+device+before+connecting)
I tried to click settings->about phone->build no 7 times but cannot get it into developer mode
So, can anyone please give me a step by step guide on how to root my Redmi 3S?
...and just after posting I found a tutorial on youtube
But now I am stuck on flashing twrp. It says:
fastboot.exe flash recovery twrp-3.0.2-0-ido.img
target reported max download size of 536870912 bytes
sending 'recovery' (13934 KB)...
OKAY [ 0.440s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.447s
So now my question is: how do I allow flashing?
I guess I need to unlock the device. Have created a MUI account and logged in to:
http://en.miui.com/unlock/
but everything is in chinese... Any suggestions?
Found an english page and logged in. Went back to the unlock page and requested permission to unlock my phone. Now I have to wait for 10 days for them to reply...
Others who wants to root their Redmi 3 may want to look at these videos to unlock and root:
https://www.youtube.com/watch?v=OFCig10fW9E&feature=youtu.be
https://www.youtube.com/watch?v=4Rv67v55h2w
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
marceloariel said:
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
Click to expand...
Click to collapse
Thanks for the reply. I actually tried this as well but it did not work. MiFlash just appears to be running the flash_all_lock.bat script on Windows and it failed because the bootloader was not already unlocked according to its debug logs when I ran it. I should have mentioned that above.
Not sure if it will help but did you try a factory reset?
Press and hold the Power+Volume Down buttons untill you see the android with the no command. Press and hold the Power button. Press and release the Volume Up button once then release the Power button. Then you should see some recovery options.
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
sensig said:
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
Click to expand...
Click to collapse
The issue is caused by fastboot rom containing dummy system_b image and flashing script "forgetting" to force partition A as active. If a phone has B as an active partition and someone uses flash_all_lock.bat script, the phone's screwed. No idea what brought Xiaomi to this "brilliant" idea, not only there is a higher chance to brick the phone, but the zip file is also unnecessarily larger.
With locked bootloader it isn't possible to switch active partition anymore, so the phone is a (semi)brick. EDL mode is usually used to reflash locked bootloaders.
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
There are two commands for setting active partition, depending on the fastboot version. It's either old
fastboot set_active a
or newer
fastboot --set-active=a
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
if you open flashing script file (.bat or .sh) in a text editor, you will see that fastboot is flashing system.img to system_a partition and system_other.img to system_b partition. That system_other.img is a dummy image and is not bootable. You either:
Option 1: Set active partition to A before running any stock flashing script.
Option 2: Replace system_other.img to system.img in the script.
Option 3: Force partition A after flashing userdata.img and before any lock or reboot command.
dephekt said:
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
Click to expand...
Click to collapse
I am in the same exact position with my Mi A3... did you ever resolve this and if so how?
mewcatchew said:
I am in the same exact position with my Mi A3...
Click to expand...
Click to collapse
What causes led to this behavior ?
htn711 said:
What causes led to this behavior ?
Click to expand...
Click to collapse
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
Click to expand...
Click to collapse
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting).
Click to expand...
Click to collapse
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
garylawwd said:
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
Click to expand...
Click to collapse
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
---------- Post added at 02:40 PM ---------- Previous post was at 02:30 PM ----------
htn711 said:
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
Click to expand...
Click to collapse
Did you read my posts? I get "locked state error" with fastboot commands. I can reboot bootlader in fastboot, and it tjust reboots into fastboot - thats just about all i can do. It wont let me change anything, can only get info and reboot...
mewcatchew said:
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
Click to expand...
Click to collapse
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
garylawwd said:
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
Click to expand...
Click to collapse
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
Ya I wouldn't go trusting some random Russian site either. I don't think there is anything you can do without either
A) going into edl and using a verified mi account
B) bringing it to a service centre (which nobody wants to do)
In fastboot you can't get any commands to work now right? Your device is fully locked again?
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
That Russian site is run by the XDA guy from what I understood. There are other paid services which have Xiaomi service accounts, I only pointed you to the cheapest "verified" eshop. Just Google another one if you don't trust Russians. All of them will need to connect to your PC over Teamviewer and do the flashing, you will just follow the instructions (connect the phone, reboot it etc.).