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...
Related
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
Hello i am new to this forum so please dont be too harsh on me
I tried to root this phone and no software or anything worked so far.
I tried the following rooting solutions:
Framaroot APK
Kingo Root
Towelroot APK
vRoot (PC with USB)
The specs of the phone are:
Original FW Lolipop 5.0.2
Kernal Verison 3.10.49
CPU is an Qualcomm Technologiers MSM8939
I hope somebody here can help me to root this thing. :fingers-crossed:
I've the same phone and the same problem... :'(
Hi!
Sorry for the huge post
I've got the same phone (in Belgium btw) and until now still no root.
But I have faith and will continue to search. I will attain root even if I have to hack the whole damn device!
Thing I've tried :
- all the "one click" or simple methods I've encoutered on the Internet (not enough fingers to count them all ^^) .
- This guide, both methods, stuck when trying to write on /system partition ofc, or psneuter gives an error... http://forum.xda-developers.com/showthread.php?t=2684210 (probably outdated for Lollipop 5.0.2)
- ADB : tried to flash a .zip with just su and busybox binaries with stock <3e> recovery (via adb sideload), giving the "bad footer" and another (sry don't remember which) error , probably because of bad signature of the .zip. "adb devices" gives "0123456789ABCDEF device" as a result...
- Fastboot: unlocking bootloader with "fastboot oem unlock" ->> gives "... OK [0.005 sec]" result or something. but I can't verify if it's unlocked. The damn device won't show the fastboot mode correctly. Instead it gives a "Medion powered by android" splashscreen, can't see the normal fastboot screen. The "fastboot devices" command on my PC gives me the "serial no fastboot" result, but it seems really restricted in what I can do with it.... "fastboot getvar all" returns nothing (tried all var names I could find but just a few return something-> version: 0.5; serialno; product: MSM8916)
- even the *#*#7378423#*#* command seems to be blocked, and nothing seems to be able to give me the bootloader status (locked/unlocked) :crying:
I gues I need to go further and dig into making images of bootloader or system or recovery partitions and see what's in there and what I can do with that.
Preparing to become an android hacker here XD.
Will post here when I have something.
Radek.
Ps: if anyone with knowledge could point me to some starting point on what would be a correct approach, it'd be MUCH appreciated.
Hi there!
Just a little heads up to say that I contacted Medion support (Belgium) yesterday and I already got an answer...
I was asking if there are any ways to have some hint(or anything, maybe a code for bootloader unlocking) from them about rooting, unlocking or whatever. And if anything of the sort would void the warranty.
The answer I had is that Medion is not giving any support of the sort and yes, rooting would void the phone's warranty.
So we at least know what to expect from them... nothing! :silly:
Now back to hacking and digging for a root method
Cheers.
Dear Rodzzinn, you are my hero
I have a belgian x5004 too, like other users I experience constant freezes and reboots. Have tried everything, including sending it back tot Medion... It came back with just the same problem... Thanks for all the great work!
Hi guys,
i do have the same phone and i'm trying eagerly to root this phone but i do get the same hurdles. I'm from good ol' Germany and i tried to get more informations from the Medion support over here, too.
It's still pending. So if I know something I write down for us.
Best regards
Rodzzinn said:
Hi!
Sorry for the huge post
I've got the same phone (in Belgium btw) and until now still no root.
But I have faith and will continue to search. I will attain root even if I have to hack the whole damn device!
Thing I've tried :
- all the "one click" or simple methods I've encoutered on the Internet (not enough fingers to count them all ^^) .
- This guide, both methods, stuck when trying to write on /system partition ofc, or psneuter gives an error... http://forum.xda-developers.com/showthread.php?t=2684210 (probably outdated for Lollipop 5.0.2)
- ADB : tried to flash a .zip with just su and busybox binaries with stock <3e> recovery (via adb sideload), giving the "bad footer" and another (sry don't remember which) error , probably because of bad signature of the .zip. "adb devices" gives "0123456789ABCDEF device" as a result...
- Fastboot: unlocking bootloader with "fastboot oem unlock" ->> gives "... OK [0.005 sec]" result or something. but I can't verify if it's unlocked. The damn device won't show the fastboot mode correctly. Instead it gives a "Medion powered by android" splashscreen, can't see the normal fastboot screen. The "fastboot devices" command on my PC gives me the "serial no fastboot" result, but it seems really restricted in what I can do with it.... "fastboot getvar all" returns nothing (tried all var names I could find but just a few return something-> version: 0.5; serialno; product: MSM8916)
- even the *#*#7378423#*#* command seems to be blocked, and nothing seems to be able to give me the bootloader status (locked/unlocked) :crying:
I gues I need to go further and dig into making images of bootloader or system or recovery partitions and see what's in there and what I can do with that.
Preparing to become an android hacker here XD.
Will post here when I have something.
Radek.
Ps: if anyone with knowledge could point me to some starting point on what would be a correct approach, it'd be MUCH appreciated.
Click to expand...
Click to collapse
By the way, is "QuickBoot" in developer options the same as FastBoot ?
Hi guys,
did get mail from the Medion Support. Guess what, nothing achieved there. Can we achieve something if we get the recovery image?
Maybe something like cooking ur own system on the base of the original rom.
hey guys,
I just wondered, seeing the troubles around here if there would be a possible way to root this thin and throw a Windows mobile 10 ROM to it.
I know this is android forum... but I could not find direct results under x5004 on windows mobile so don't shoot!
thx!
cboy1980 said:
hey guys,
I just wondered, seeing the troubles around here if there would be a possible way to root this thin and throw a Windows mobile 10 ROM to it.
I know this is android forum... but I could not find direct results under x5004 on windows mobile so don't shoot!
thx!
Click to expand...
Click to collapse
Hi cboy1980
for the time being is one of the Xiaomi devices the only one able to flash windows phone on it. No luck so far with other android phones.
Hello everyone, i have too this smartphone and this one freeze and reboot sometime with no reason... also the phone communications quality are poor and sometime cut
I have already sent my phone to medion's service care, but they do nothing and my phone is always in the same state !
They suggest me to send this one again... yeah cool to buy a phone that is constently away and nothing is done for recover the problems !
I will keep you informed
Found solution!
I've found a solution to root the x5004 (md99238)!
You just have to install the Kingroot APK to your smartphone!
With the PC version it isn't possible but with apk it's workin'
kingroot.net
@SISN (DE)
Thanks for the note, it worked. For months, I was looking for a way to roton the phone.
Danke für den Hinweis, es hat geklappt. Seit Monaten suchte ich nach einer Möglichkeit das Handy zu rooten.
Gerne
icke68746 said:
@SISN (DE)
Thanks for the note, it worked. For months, I was looking for a way to roton the phone.
Danke für den Hinweis, es hat geklappt. Seit Monaten suchte ich nach einer Möglichkeit das Handy zu rooten.
Click to expand...
Click to collapse
Gerne
Is there anybody who know if there are some costom roms for this phone?
Awesome!!!
Thx for the heads up! Now we finally have a rooted device! Let's get this rolling! XD
I managed to switch from Kinroot to SuperSU:
Credit to Bakageta here: kingroot to supersu on android forums. (hope I can post the link)
Installed Flashify and seems that stock recovery and kernel backup went well.
Root seems stable.
I'll see how far I can get cooking some Android :highfive:
Good luck all.
Next step:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 0.006s]
finished. total time: 0.006s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.007s
Seems encouraging as it stays unlocked even after a reboot-bootloader ...what do you think?
Don't we have an unlocked rooted awesome device now?
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.).
Good morning,
I'm trying to root this Huawuei Y6 II 2017 l_21 factory resetted but it's becoming very very hard, cause i've try every single method and nothing work.
The device is debug USB and OEM unlocked, and even bootloader unlocked and FRP unlock.
I've installed USB drivers on my window 7 ( and some of them didn't install correctly ).
The device connected correctly to hi suite but it's full upgraded android 6 emui 4.1.x.x Kirin620
-I've tried kingoroot both pc and apk
-I've tried Manual rooting with mini adb and fastboot plus TWRP 3.0.2 of this guide ( https://forum.xda-developers.com/android/general/rooting-huawei-y6-ii-cam-l21-t3501162 ) and TWRP 3.1.1-0
but when i'm launching the command fastboot flash recovery TWRPxxx.img it gives me that:
target reported max download size of 471859200 bytes
sending 'recovery' (25152 KB)...
OKAY [ 0.736s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.743s
Actually i've asked for a new unlock bootloader code to huawuei, but i have even tried to get the code with dc-unlocker following this guide ( https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code ) and even in this case my PC didn't find the mobile phone.
So Actually i have 2 major issues:
1) Why i got the error in ADB ?
2) why my pc even with USb drivers didn't find correctly the device in order to let dc unlocker find the bootloader code?
My objective is to root the Phone and recover deleted data by factory reset, but i don't know what to do now.
help!
jackielong said:
Good morning,
I'm trying to root this Huawuei Y6 II 2017 l_21 factory resetted but it's becoming very very hard, cause i've try every single method and nothing work.
...
1) Why i got the error in ADB ?
2) why my pc even with USb drivers didn't find correctly the device in order to let dc unlocker find the bootloader code?
My objective is to root the Phone and recover deleted data by factory reset, but i don't know what to do now.
help!
Click to expand...
Click to collapse
This is weird to me, because the error message in fastboot it what you get when you've not unlocked the bootloader (allowed to read, not write).
And the fact that fastboot and ADB recognized your device means that on the USB drivers side, you've a correction set up...
So I'd say that the bootloader isn't unlock at first glance. And unfortunately I don't know any ways of unlocking Huawei phones now...
I didn't know DC unlocker and I can't certify if this software is legit or not, nor provide you help regarding the software.
So I don't think you'll be able to successfully root your device. But that's just what I think, maybe someone more experienced will find the solution.
Have a good day
Even if one finds a TWRP image that at 100% matches his/her device, it's not a good idea to flash it: instead boot into it
Code:
fastboot boot twrp.img
BTW: Doing so has the additional advantage that TWRP doesn't get detected.
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