Medion X5004 Root - Android Q&A, Help & Troubleshooting

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?

Related

[Q] Can't get identifier token

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

[Q] Cwm and custom rom huawei y330

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...

[Help] ARM Trusted Firmware bricked my unlocked honor 4x!

Dear Esteemed XDA members,
I have spent literally days of testing and researching to try and unbrick my phone. Friends and family have seen my obsession with trying to fix this, some even offering to buy me a new phone!!!! But this ain't about money - this is about having control of my damn device!!! I'm usually pretty good with trying to solve this kind of stuff, but this time I'm truly stumped (and desperate, and obsessed!). I have come to the conclusion that it's directly related to ARM Trusted Firmware. Here are the details of my "journey" to date... please read it, and if you know how to fix it, please share!!! then I can get my life back!!!! Before I go any further, I am certain that my problem was initially triggered by doing an official update on a rooted phone. So to avoid experiencing the same problem I'm about to describe, it's best to unroot and relock your device before loading new official firmware.
I have a Huawei Honor 4x (Che2-UL00, with Kirin 620 chipset) with an unlocked bootloader. Recently, I tried to manually upgrade from Kitkat (emui3.0) to Lollipop (emui3.1), using the official update.app from huawei's website (image was good - I checked the hash). To load the update.app, I used the official huawei recovery. The progress bar went to roughly 90% and then hung. Upon restarting my phone, it went into rescue mode with the following error: Func NO : 15 (bl31 image) Error NO : 1 (security verify failed).
Interestingly, I looked closely at the fastboot.img files for kitkat Vs lollipop (I got the image files by using HuaweiUpdateExtractor). I noticed that only the lollipop fastboot image contains this error message text. Also, bl31 is related to ARM trusted firmware, for more info search for BL31 (Secure Monitor) on google, or see bl31_main.c in the Trusted Firmware source code. So it seems that the lollipop image is using the full ARM trusted firmware, an extra layer of security which is preventing the (unlocked) bootloader from allowing me to load into recovery. I think this is the core problem, and I think there is a way to solve it but I just don't have a deep enough understanding to get there. Below I'll explain each step I went though and provide some additional diagnostic info:
1. First step was to access recovery mode (Vol UP + power). This failed and resulted in same bl31 error message.
2. Second step was to try and update again using the three-button force update (Vol Up + Vol Down + Power). It vibrates once after a few seconds, and freezes with the logo screen with the red light flashing. As an experiment, I tried this without the SDCARD and noticed it vibrated almost instantly, which suggests that it does try to load something from the SDCARD when inserted. I didn't get any further in this mode.
3. Final step I tried was to load into fastboot (Vol Down + Power). This worked and I got into a special "Rescue&Fastboot" mode. First thing I tried was to manually downgrade to kitkat by flashing the kitkat images using the fastboot flash command. The images boot.img, system.img, recovery.img flashed successfully. cust.img simply failed. I desperately wanted to flash the kitkat fastboot.img which doesn't contain the trusted firmware bl31 image stuff, but fastboot replied: FAILED (remote: Command not allowed). In fact, many of the fastboot commands fail with this same error message, even though there is the "PHONE unlocked" writing in red on my phone screen. With the limited command set available (even fastboot oem device-info is not allowed!), here is the diagnostic info I was able to get:
a) fastboot oem check-rootinfo
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1452356543
I think this change from RISK to SAFE is the core of my problem. the change_time is from several days ago when I attempted to update. I think it reflects the trusted firmware state (I'm guessing here, as I can't find documentation for these commands).
b) fastboot oem backdoor info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
I think that FB LockState: LOCKED means that fastboot is locked (guessing again, can't find documentation!), which explains why many of the commands fail.
c) fastboot oem check-image
(bootloader) secure image verify successfully
I think this checks the recovery image, because when I flash a different recovery, this signature check fails
d) fastboot getvar rescue_phoneinfo
rescue_phoneinfo: Che2-UL00 V100R001CHNC00B365
This appears to be the ROM version at the time of purchase.
e) fastboot oem get-build-number
(bootloader): Che2-UL00 V100R001CHNC00B384
This actually corresponds to the build number of kitkat I was using just before the failed upgrade to lollipop.
f) fastboot oem relock mycode
FAILED (remote: root type not allowed).
I tried this just to see if it wold relock. I'm not sure what the error means, but I do not that this command failed with signature verify fail if i change the recovery image.
Here are the questions I want to ask:
1. Can I force the device to flash a new image? I can't get into recovery or have full access to fastboot commands due to the trusted firmware stuff. And as I mentioned earlier the three button trick fails with a freeze at the logo screen. It appears that I need to do this using a means other than fastboot. The only interface I have is Android Sooner ADB Interface. adb devices renders nothing. Only fastboot finds a device.
2. Can I somehow make the "security verify check" pass so that I don't get that bl31 error? I'm not sure exactly which images this bl31 thing is trying to verify! Perhaps some combination of images from the new lollipop stuff I tried to flash and the kitkat build I had running previously?
3. Can somehow disable all this Trusted Firmware stuff??
4. Any other suggestions???
This is driving me to the brink on insanity!!! Gotta figure it out!! Thanks for reading and trying to help!
Hi,
Did anyone solve this problem?
I'm facing the exact same situation.
Che2-UL00 too.
Thanks in advance!
prezident36 said:
Hi,
Did anyone solve this problem?
I'm facing the exact same situation.
Che2-UL00 too.
Thanks in advance!
Click to expand...
Click to collapse
I still find it hard to believe this problem absolutely cannot be solved. However, I took it to a Huawei service center and they weren't able to unbrick it either. They had to replace the mainboard, which seems like a complete waste. Cost around $50, so not the end of the world but still annoying.
Anyway, screw this whole "trusted firmware" rubbish. I'm the owner of the device, yet I'm not "trusted".
hello, i have exactly the same problem!
---------- Post added at 10:58 PM ---------- Previous post was at 10:41 PM ----------
Where do i get the replacement mainboard from?
Me too, upgrading kitkat to lollipop. Now facing that rescue error.
My Honor 4X is unlock bootloader and root before upgrading lollipop,

Huawuei Y6 II l_21 hard to root like the hell

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.

V600TM Root/Unlocking Issues

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

Categories

Resources