Hi guys, I want to know what happens to my Droid Incredible, and I installed the drivers, (HTC Driver 4.0.1.002), connect the PC to ADB, and works perfectly, but the reboot into bootloader / fastboot, just do not take, and last but not least, the PC does not recognize the USB. Why does this happen? I received it yesterday, so I have not done much.
Importantly, I have installed Windows 8 Pro on my PC, is it that the drivers are not working properly?
CheerS!
neotenshi said:
Hi guys, I want to know what happens to my Droid Incredible, and I installed the drivers, (HTC Driver 4.0.1.002), connect the PC to ADB, and works perfectly, but the reboot into bootloader / fastboot, just do not take, and last but not least, the PC does not recognize the USB. Why does this happen? I received it yesterday, so I have not done much.
Importantly, I have installed Windows 8 Pro on my PC, is it that the drivers are not working properly?
CheerS!
Click to expand...
Click to collapse
check your usb port is not 3.0-- you should use a 2.0 port, look inside the port. if it's blue it's 3.0, black is 2.0. 3.0 doesn't work well with adb.not saying this is your problem, but it could be.
Aldo101t said:
check your usb port is not 3.0-- you should use a 2.0 port, look inside the port. if it's blue it's 3.0, black is 2.0. 3.0 doesn't work well with adb.not saying this is your problem, but it could be.
Click to expand...
Click to collapse
Really? I had no idea. I prove this, was connecting with 3.0
Cheers!
Another problem, now, entering the token to HTCDev, recognizes the error 160:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 160.
Error Reason: MID Not Allowed.
Why? -_-
neotenshi said:
Another problem, now, entering the token to HTCDev, recognizes the error 160:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 160.
Error Reason: MID Not Allowed.
Why? -_-
Click to expand...
Click to collapse
you recieved a token via e-mail?? if so, it should work.
or are you trying to get the unlock token, make sure you copy and paste it in correctly, also did you supercid (11111111)to get a token
Aldo101t said:
you recieved a token via e-mail?? if so, it should work.
or are you trying to get the unlock token, make sure you copy and paste it in correctly, also did you supercid (11111111)to get a token
Click to expand...
Click to collapse
I put the unlock code that gives me the file, and I get that: (
neotenshi said:
I put the unlock code that gives me the file, and I get that: (
Click to expand...
Click to collapse
did you run the automated script to give you fakecid, it's all here in this forum. check it out. then you go to htcdev and get your unlock code.look under development section.
automated script for fake cid-unlock bootloader, etc
neotenshi said:
I put the unlock code that gives me the file, and I get that: (
Click to expand...
Click to collapse
Means you didn't supercid correctly, run script again
Sent from my ADR6410LVW using xda app-developers app
Again the script? Or something is failing?
= Step 2: SuperCID =
========================
Your phone's CID is being modified to SuperCID. Once complete, your
phone will reboot to the bootloader.
/dev/block/mmcblk0p4: cannot open for read: Permission denied
remote object '/sdcard/mmcblk0p4' does not exist
El sistema no puede encontrar el archivo especificado.
cannot stat 'mmcblk0p4': No such file or directory
/sdcard/mmcblk0p4MOD: cannot open for read: No such file or directory
rm failed for /data/local.prop, No such file or directory
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.011s]
finished. total time: 0.012s
neotenshi said:
Again the script? Or something is failing?
= Step 2: SuperCID =
========================
Your phone's CID is being modified to SuperCID. Once complete, your
phone will reboot to the bootloader.
/dev/block/mmcblk0p4: cannot open for read: Permission denied
remote object '/sdcard/mmcblk0p4' does not exist
El sistema no puede encontrar el archivo especificado.
cannot stat 'mmcblk0p4': No such file or directory
/sdcard/mmcblk0p4MOD: cannot open for read: No such file or directory
rm failed for /data/local.prop, No such file or directory
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.011s]
finished. total time: 0.012s
Click to expand...
Click to collapse
The only way you can use the SuperCid option in the script is if you already have root (does it not say this right next to the task???). Follow the instructions here under "Usage - typical procedures" completely.
mdmower said:
The only way you can use the SuperCid option in the script is if you already have root (does it not say this right next to the task???). Follow the instructions here under "Usage - typical procedures" completely.
Click to expand...
Click to collapse
I run the script again, and it worked. Now I'm flashing a ROM to test equipment: P Thanks
Related
i did exactly every steps that show. but how come when i submit.
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 140.
Error Reason: Token Decryption Fail.
Help!!!!!!!!!!!!!!!!
try going thru the whole process again, gettin the token and make sure u copy the "<<<<<<<<" too
Make sure you copy your token identifier in a notepad and delete "info" on the left side.
This should be posted in Q&A section.
<<<< Identifier Token Start >>>>
82520115AFCD5337DCDC6485A6D7D4B8
376D2DF9939BF47E6378597AFD70F7DF
451558E2810941B9D81C93F5DDC9EF95
3479EA6AD52893243D92159DB9CE811B
04C0CDF6110E7A639ABA2594AF8B554C
2EA1C220CBF75B9920AB072A839819C7
1F439E0D2A48068759FD2F2FB378C758
758CBE0CAE55F316C6BE8B0084209B5B
54C150522AD3F3265C053B6911BA6F14
23C2B5B88BC74AB3792A0704B6563F11
62D6B0BACB741AE287F9FDAD7C022CF5
B691FAEB0C4C2E79B82012695A1B5298
C29F5B396397047A77007643C9ADE588
61F90A391B7AC0945E264CA500C978AB
F03F42FE9A3E7584508FEA909CD2D82F
135C461490BE1978ED2A8DD814C37535
<<<<< Identifier Token End >>>>>
this how i copy.
dt53444 said:
<<<< Identifier Token Start >>>>
82520115AFCD5337DCDC6485A6D7D4B8
376D2DF9939BF47E6378597AFD70F7DF
451558E2810941B9D81C93F5DDC9EF95
3479EA6AD52893243D92159DB9CE811B
04C0CDF6110E7A639ABA2594AF8B554C
2EA1C220CBF75B9920AB072A839819C7
1F439E0D2A48068759FD2F2FB378C758
758CBE0CAE55F316C6BE8B0084209B5B
54C150522AD3F3265C053B6911BA6F14
23C2B5B88BC74AB3792A0704B6563F11
62D6B0BACB741AE287F9FDAD7C022CF5
B691FAEB0C4C2E79B82012695A1B5298
C29F5B396397047A77007643C9ADE588
61F90A391B7AC0945E264CA500C978AB
F03F42FE9A3E7584508FEA909CD2D82F
135C461490BE1978ED2A8DD814C37535
<<<<< Identifier Token End >>>>>
this how i copy.
Click to expand...
Click to collapse
That looks correct. So you already got your Unlock_code.bin?
<<<< Identifier Token Start >>>>
82520115AFCD5337DCDC6485A6D7D4B8
376D2DF9939BF47E6378597AFD70F7DF
451558E2810941B9D81C93F5DDC9EF95
3479EA6AD52893243D92159DB9CE811B
04C0CDF6110E7A639ABA2594AF8B554C
2EA1C220CBF75B9920AB072A839819C7
1F439E0D2A48068759FD2F2FB378C758
758CBE0CAE55F316C6BE8B0084209B5B
54C150522AD3F3265C053B6911BA6F14
23C2B5B88BC74AB3792A0704B6563F11
62D6B0BACB741AE287F9FDAD7C022CF5
B691FAEB0C4C2E79B82012695A1B5298
C29F5B396397047A77007643C9ADE588
61F90A391B7AC0945E264CA500C978AB
F03F42FE9A3E7584508FEA909CD2D82F
135C461490BE1978ED2A8DD814C37535
<<<<< Identifier Token End >>>>>
this is how i copy
still got same error!!!
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
i got it people. Thank you
What was the problem?
I'm facing the same issue
Make sure you aren't selecting the empty column just to the left of the token identifier. There is a single vertical line to the left that sometimes gets selected if your not carefull. I am willing to bet that this is your problem.
Mine is getting to this point:
c:\Android>fastboot oem get_identifier_token
< waiting for device >
and then just sits there. Is this because I rooted before doing HTCDev?
Will
shellguy said:
Mine is getting to this point:
c:\Android>fastboot oem get_identifier_token
< waiting for device >
and then just sits there. Is this because I rooted before doing HTCDev?
Will
Click to expand...
Click to collapse
i rooted before htc dev so that shouldn't b your problem also read this thread cause alot of ppl are having a difficult time selecting the token
I get
C:\Users\mark\Downloads\android-sdk_r12-windows\android-sdk-windows\platform-too
ls>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
and it just sits there. Only way to end it is to unplug phone. RUU'ed and updated htc sync then went through the whole process again and still nothing.
ummm am i an idiot..but i dont see the evo 4g lte listed on htcdev...which one are ya'll selecting
dahray02 said:
ummm am i an idiot..but i dont see the evo 4g lte listed on htcdev...which one are ya'll selecting
Click to expand...
Click to collapse
At the bottom "All Other Supported Models"
shellguy said:
Mine is getting to this point:
c:\Android>fastboot oem get_identifier_token
< waiting for device >
and then just sits there. Is this because I rooted before doing HTCDev?
Will
Click to expand...
Click to collapse
Make sure you have the proper drivers installed if not adb wont communicate with the phone.
Sent from my EVO using xda premium
durandetto said:
Make sure you have the proper drivers installed if not adb wont communicate with the phone.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I used the same PC to root the device too, but that was done via script.
Will
I'm having a problem as well. I got my Unlock code email. I downloaded it and put it in the Android file I created. Highlighted folder, shift+right click, got my cmd prompt, copied and pasted the fastboot flash unlock token...... and got this:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
error: cannot load 'Unlock_code.bin'
C:\Android>
I don't remember having any issues when I did my Evo3d????????
FIXED: Had to actually type command. DO NOT copy and paste
shellguy said:
I used the same PC to root the device too, but that was done via script.
Will
Click to expand...
Click to collapse
Do you have adb installed?
Did you put in the path in your environment variables?
Do you have have HTC sync or disk drive disabled?
Is USB debugging on?
Lastly, computer OS? sometimes its just easier to use xp than w7.
If the answer to the first 4 questions were all yes, it should work...
What? XP is kicking my a$$! When I'm on a friends win7 PC, it finds drivers right away. Hell, I still can't even get XP to recognize my device storage to put my music on my phone (adb sees my device just fine and fastboot commands dont work either). Driving me nuts.
sent from my Evo LTE, usually.
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
I succeeded in doing the following:
1) downgrade my tablet to a rootable fw version
2) rooted with doomlord tool
Now I need to unlock my bootloader: I had requested the key a while ago, but never got around to using it.
I followed all the instructions and succeeded in connecting the tablet in fastboot mode to my pc (drivers installed fine and I receive a reply when issuing the trial command getvar version, meaning, I presume that the device is connected and able to receive commands and reply to them).
However when I issue the command in the instructions on http://unlockbootloader.sonymobile.com/instructions and replace the final "KEY" with the key provided by Sony via email I receive a reply "FAILED (remote: Command did not succeed)": what could I be doing wrong? I also copied and pasted the command in order to make sure that the syntax was correct and checked the code I input many times to make sure I did not miss or messed up something, but it all seems OK. I issued the command from within the same directory where the getvar command was issued, i.e. within Android SDk/Tools folder (the procedure on the website doesn't suggest to change folder, so I didn't!) , but no success at all!
Can anyone suggest some way out?
Thanks
Luca
astrovale said:
I succeeded in doing the following:
1) downgrade my tablet to a rootable fw version
2) rooted with doomlord tool
Now I need to unlock my bootloader: I had requested the key a while ago, but never got around to using it.
I followed all the instructions and succeeded in connecting the tablet in fastboot mode to my pc (drivers installed fine and I receive a reply when issuing the trial command getvar version, meaning, I presume that the device is connected and able to receive commands and reply to them).
However when I issue the command in the instructions on http://unlockbootloader.sonymobile.com/instructions and replace the final "KEY" with the key provided by Sony via email I receive a reply "FAILED (remote: Command did not succeed)": what could I be doing wrong? I also copied and pasted the command in order to make sure that the syntax was correct and checked the code I input many times to make sure I did not miss or messed up something, but it all seems OK. I issued the command from within the same directory where the getvar command was issued, i.e. within Android SDk/Tools folder (the procedure on the website doesn't suggest to change folder, so I didn't!) , but no success at all!
Can anyone suggest some way out?
Thanks
Luca
Click to expand...
Click to collapse
Sorry if this is a dumb question, but is bootloader unlocking allowed on your tablet ?
Some service providers have blocked bootloader unlocking.
GretaLewd said:
Sorry if this is a dumb question, but is bootloader unlocking allowed on your tablet ?
Some service providers have blocked bootloader unlocking.
Click to expand...
Click to collapse
I followed the procedure on the Sony website to check that and the answer is yes, it can be unlocked.
I tried some other tutorials and no results. It seems that it might be connected to the doomlord exploit (which I used to gain root access), but all the instructions on how to get around that have failed to allow me the unlocking!!!!
astrovale said:
I followed the procedure on the Sony website to check that and the answer is yes, it can be unlocked.
I tried some other tutorials and no results. It seems that it might be connected to the doomlord exploit (which I used to gain root access), but all the instructions on how to get around that have failed to allow me the unlocking!!!![/QUOTE
SOLVED
Click to expand...
Click to collapse
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...
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11. Many guides online seem to gloss over needing the bootloader unlocked before root. TMALSS; I'm not sure if the non-international version can be bootloader unlocked and/or if I can root without needing this. Long version of what I've tried is below:
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Thus to unlock the bootloader, I am following a guide from TWRPupdate:
It says to perform 'adb reboot bootloader' and then 'fastboot oem device-id':
Code:
C:\adb-platform-tools>fastboot device-id
fastboot: usage: unknown command device-id
My phone only reboots into normal mode whenever running reboot bootloader command within ADB.
I can run fastboot commands when I run 'adb reboot fastmode' but I don't believe this is true fastmode. As I have tried everything mentioned here, such as cables or different computers. Essentially most fastboot commands I've tried do not work except for showing my device as listed / connected.
I have also tried the drivers from LG / Google / ADB separately. And on 2 computers.
Is it possible that I don't have rescue mode or a bootloader still? As I get a black screen when entering recovery mode (but my computer recognizes A device), but adb nor fastboot does. I used to see the recovery screen logo, but I stopped seeing this screen either after updating to Android V11 or reading/backing-up the partitions in QFIL.
In last resort, I have tried rooting via patching the boot image using Magisk v23. I downloaded the firmware for my carrier, converted the KDZ to DZ via Python, and extracted the boot.img_117638 file. Given the file is 0 bytes with nothing in text edit, I still converted it to an img file. But in the kdztools android app, when I select this image file and run, I get:
Code:
!Invalid input file
!Installation failed
I'm guessing the boot.img file should have some data in it. But I'm not sure this method would even work due to the fastboot issues, especially with 'download to device' errors.
-------
I'm just at a standstill on what to even try next. I don't see many people having this much trouble unlocking/rooting their v60. Did the OTA Android v.11 break the root-ability?!
PS: Debugging and OEM unlock are both set in developer options. I can also list drivers used if need.
Thanks for the help in advance!
While digging I also found a post by alexenferman whom managed to use QFIL to root many older ZTE smartphones. They state it may but likely won't work on newer flagship phones. It's a great tutorial I'll have to try soon, but is there a reason it likely won't work here?
kyij said:
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11.
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
NGOwner said:
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
Click to expand...
Click to collapse
Haha, I remember reading that and still continued
I am on Verizon myself using this TM model. I know the phone was unlocked to the point where I could use it with Verizon. I even got 5g using my old 4g sim card.
Anyhow.. I have tried using that command already, and get the same 'command not supported issue'.
Code:
C:\adb-platform-tools>fastboot devices
LMV600TMc40cxxxx fastboot
C:\adb-platform-tools>fastboot oem unlock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Again have tried different computers and cables as I've read fastboot can be pretty picky too.
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
NGOwner said:
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
Click to expand...
Click to collapse
Yes I do, I have turned it off and back on as well.
Well then at this point, I'm tapped out. Smarter folks than me will need to step in and take up the mantle.
[NG]Owner
I ended up posting a form to reddit where about 10 people insisted I did something wrong, and with little surprise -- I did.
I did not flash the engineering bootloader after saving a copy.
Makes a lot more sense since it seemed like a lot of steps to backup without actually doing anything
Thanks NG for the help too!
are you success to unlock bootloader yet. if no i will show you
adb reboot fastboot> select reboot bootloader on your phone> fastboot oem unlock