From xBIGREDDx
• Lollipop 5.1.0
• Enhanced access via Quick settings for Wifi and Bluetooth.
• UI enhancements - Volume slider.
• New animations on the Clock app.
• Improved SD Card support (Fixed bug that prevented some apps from being moved to SD Card)
• Updated localization, Four additional languages added - Danish (Denmark), Finnish (Finland/Sweden), Norwegian, Swedish (Finland & Sweden).
• Depth processing improvements for Dell Gallery
• Added two new Dell Live wallpapers
• Miscellaneous bug fixes
MAKE SURE TO HAVE ENOUGH FREE SPACE or update fails.
OTA process failed, I think I also had an out of space issue?
Code:
I/SystemUpdateOTA(16111): Copy file from /storage/emulated/0/update.zip to /data/data/com.dell.systemupdateota/update.zip
I/SystemUpdateOTA(16111): Fail to copy package to /data/data/com.dell.systemupdateota/update.zip
EDIT: OTA is 1GB and I only had 750MB free. Trying again.
EDIT2: Update successful on tablet that was rooted. Lost root though. First boot took maybe 10 minutes sitting at the "intel inside" screen.
Also, Developer Options now has an "OEM unlocking" option, but 'fastboot oem unlock' doesn't seem to work. Not sure if this is normal or a side-effect of having been rooted and/or having the developer firmware previously installed. I won't have much time today to mess with it but I can maybe upload the update.zip in a few hours.
It looks like it's the 5.1 update.
I noticed as well. It failed on my rooted system.
I'll grab the OTA zip tomorrow after work and upload it, unless anyone else does it before
Do they fix gyro speed or anything?
Update failed for me. Not enough space.
Got the release notes from logcat:
• Lollipop 5.1.0
• Enhanced access via Quick settings for Wifi and Bluetooth.
• UI enhancements - Volume slider.
• New animations on the Clock app.
• Improved SD Card support (Fixed bug that prevented some apps from being moved to SD Card)
• Updated localization, Four additional languages added - Danish (Denmark), Finnish (Finland/Sweden), Norwegian, Swedish (Finland & Sweden).
• Depth processing improvements for Dell Gallery
• Added two new Dell Live wallpapers
• Miscellaneous bug fixes
Click to expand...
Click to collapse
OTA process failed, I think I also had an out of space issue?
Code:
I/SystemUpdateOTA(16111): Copy file from /storage/emulated/0/update.zip to /data/data/com.dell.systemupdateota/update.zip
I/SystemUpdateOTA(16111): Fail to copy package to /data/data/com.dell.systemupdateota/update.zip
EDIT: OTA is 1GB and I only had 750MB free. Trying again.
EDIT2: Update successful on tablet that was rooted. Lost root though. First boot took maybe 10 minutes sitting at the "intel inside" screen.
Also, Developer Options now has an "OEM unlocking" option, but 'fastboot oem unlock' doesn't seem to work. Not sure if this is normal or a side-effect of having been rooted and/or having the developer firmware previously installed. I won't have much time today to mess with it but I can maybe upload the update.zip in a few hours.
Misc Fixes... include lower touch and audio latency! Great for music creation apps!
I think the gyro seems somewhat better. Screen rotates faster than before and consistently. Still could be improved though. I hope the swipe down menu glitch is fixed as well. It would vanish for me sometimes.
OVERALL a great update and I hope to see more support in the future. Good work dell!!!!
I can update with root?
Update working for me with root without problem. But root is gone
Leader2light said:
From xBIGREDDx
• Lollipop 5.1.0
• Enhanced access via Quick settings for Wifi and Bluetooth.
• UI enhancements - Volume slider.
• New animations on the Clock app.
• Improved SD Card support (Fixed bug that prevented some apps from being moved to SD Card)
• Updated localization, Four additional languages added - Danish (Denmark), Finnish (Finland/Sweden), Norwegian, Swedish (Finland & Sweden).
• Depth processing improvements for Dell Gallery
• Added two new Dell Live wallpapers
• Miscellaneous bug fixes
MAKE SURE TO HAVE ENOUGH FREE SPACE or update fails.
OTA process failed, I think I also had an out of space issue?
Code:
I/SystemUpdateOTA(16111): Copy file from /storage/emulated/0/update.zip to /data/data/com.dell.systemupdateota/update.zip
I/SystemUpdateOTA(16111): Fail to copy package to /data/data/com.dell.systemupdateota/update.zip
EDIT: OTA is 1GB and I only had 750MB free. Trying again.
EDIT2: Update successful on tablet that was rooted. Lost root though. First boot took maybe 10 minutes sitting at the "intel inside" screen.
Also, Developer Options now has an "OEM unlocking" option, but 'fastboot oem unlock' doesn't seem to work. Not sure if this is normal or a side-effect of having been rooted and/or having the developer firmware previously installed. I won't have much time today to mess with it but I can maybe upload the update.zip in a few hours.
Click to expand...
Click to collapse
Does enabling the OEM unlocking change the device state from locked to unlocked in droidboot?
Has the update been captured and uploaded some where?
I'm thinking that both the 7840 and 7040 will have to use the bootloader unlock and a built recovery.
Just like the 3830 they should only need the unlocked firmware files the rest of the dev rom wouldn't be needed. Someone would just need to be brave and test and modify the instructions to only cover the bootloader unlock.
OTA zip:
https://mega.nz/#!1tRR0CZL!HYwoF6eiLQudUBaWw5Rhwjj6Vjy4ZdQbGIq1xrNQEOo
MD5: c2f7c2ba635480bdb937a438439f3677
social-design-concepts said:
I'm thinking that both the 7840 and 7040 will have to use the bootloader unlock and a built recovery.
Just like the 3830 they should only need the unlocked firmware files the rest of the dev rom wouldn't be needed. Someone would just need to be brave and test and modify the instructions to only cover the bootloader unlock.
Click to expand...
Click to collapse
I am curios to see if the droidboot itself is locked several droidboots, I have tried are locked, eg they can't flash anything.
@xBIGREDDx has uploaded the update.
Yep their droidboot is locked.
Code:
[email protected]:~/Desktop/untitled2$ '/home/vampirefo/Desktop/untitled2/trigger' 4
Using Trigger 4
target reported max download size of 536870912 bytes
sending '/tmp/recovery.zip' (7154 KB)...
OKAY [ 0.284s]
writing '/tmp/recovery.zip'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.318s
target reported max download size of 536870912 bytes
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.061s]
writing '/tmp/recovery.launcher'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.095s
...
FAILED (remote: command not allowed in this device state)
finished. total time: 0.035s
target reported max download size of 536870912 bytes
sending '/system/bin/logcat' (349 KB)...
OKAY [ 0.055s]
writing '/system/bin/logcat'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.096s
...
FAILED (remote: command not allowed in this device state)
finished. total time: 0.035s
[email protected]:~/Desktop/untitled2$
Look at this users output :
http://forum.xda-developers.com/showthread.php?p=61983870
I read it wrong man i really need to get glasses
Did the ota include any full kernel images that could be repacked for custom recovery?
Could anyone see if after updating to the 5.1 image, if there is a '/vendor/lib64' folder on the device?
Thank god I disabled the system update app. Otherwise, I had been forced to update 5.1.0 and lost root.
It seems rooting the latest 5.1.0 is a little tricky? or using oem unlock in developer menu will work with previous method?
social-design-concepts said:
Look at this users output :
http://forum.xda-developers.com/showthread.php?p=61983870
I read it wrong man i really need to get glasses
Did the ota include any full kernel images that could be repacked for custom recovery?
Click to expand...
Click to collapse
Thanks, based on those shots I apparently had a messed up droidboot. I reflashed it using the dev tools, now I have "Device State - locked" and if I run 'fastboot oem unlock' it asks me if I want to unlock, but it's Google/Nexus style so I will have to data wipe before it lets me unlock. Looks like we won't have to wait for unlocked "developer" firmware anymore. Once I back up some stuff I'll run the unlock and then try the tethered recovery. I think at this point if we could get a flashable recovery that would work fine too.
The OTA includes a full boot.img, if that's what you're asking.
Related
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...
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,
I'm getting an error when trying to unlock my phone's bootloader :
FAILED remote: Command not allowed.
I am copy/pasting "fastboot -i 0x0fce oem unlock 0xBEA3575C8951F712"
When I type "fastboot devices" it recognizes my device, and I installed all the drives from flashtool so I don't think its a driver issue.
I've tried using flashtool, the sdk, and minimal adb and falshboot. For flashtool I've tried adding the ulcode.txt to registerd devices folder.
I've tried different PC's and different cables. I've also tried it on androids 5, 6, 7, all of which I've flashed from the flashtool download tool (Custom UK versions).
I have USB Debuggin on, OEM unlock on, and Unkonwn Sources on. When I type *#*#7378423*#*# the phone says "Bootloader unlock allowed : yes".
A final thing to note is when I flashed android 7 the OEM unlock butto was grayed out - "Bootloader already unlocked", even though the *#*#.... code still said "Bootloader unlock allowed : yes".
I've searched all the forums and none of the fixes seem to work. Any help would be greatly appreciated - thanks!
Edit : I tried this on my old z1 compact and it worked, so its nothing wrong with my computer. I guess my z5 is just broken.
Nope, I am having the exact same issue you are. I have model E5823.
Got the unlock code off sony.
Trying everthing I can.. Can't get past that damn FAILED (remote: Command not allowed). error.
Installed 5 different fastboot/adb programs, sony drivers are latest. fastboot and adb do work, they see the device OK, it just won't accept any unlocking.
Unlockable is yes, in service settings view.
I am currently in the middle of trying to get the sony emma flashtool program to actually access my phone - it just gives me a "phone is locked" message..
going to try flashing a stock ROM with flashtool next.. but you're not giving me hope.
It is possible, because sony itself says it is, and there are other people out there who have done it. There must be a way.
Hey guys,
same here.
After fastboot fails to unlock the bootloader with
fastboot -i 0x0fce oem unlock 0xKEY
Click to expand...
Click to collapse
I tried it with flashtool and this post https://forum.xda-developers.com/showpost.php?p=58070067&postcount=34 and it worked!
But now I want to flash the modified kernel with TWRP and SuperSU with
fastboot flash boot kernel.img
Click to expand...
Click to collapse
but without success
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Same in Flashtool using option >>>>lightning icon"/Fastboot mode/Select kernel to Flash/path to boot.img.
Now bootloader is unlocked but DRM Keys still activ - if i can trust the system information.
Backup the TA-Partition was successful with iovyroot.
Whats wrong with this piece of plastic? I'm rooted all my Galaxy's before, but without any problems - this Z5c is annoying. And only because I want to change my MAC address, because my wife has same phone and same MAC Both in the same network isn't good.
Anybody who can help?
Thanks!
lfjriazr6kp6w95 said:
Hey guys,
same here.
After fastboot fails to unlock the bootloader with
I tried it with flashtool and this post https://forum.xda-developers.com/showpost.php?p=58070067&postcount=34 and it worked!
But now I want to flash the modified kernel with TWRP and SuperSU with
but without success
Same in Flashtool using option >>>>lightning icon"/Fastboot mode/Select kernel to Flash/path to boot.img.
Now bootloader is unlocked but DRM Keys still activ - if i can trust the system information.
Backup the TA-Partition was successful with iovyroot.
Whats wrong with this piece of plastic? I'm rooted all my Galaxy's before, but without any problems - this Z5c is annoying. And only because I want to change my MAC address, because my wife has same phone and same MAC Both in the same network isn't good.
Anybody who can help?
Thanks!
Click to expand...
Click to collapse
You helped me fix it! Turns out I had named my ulcode file ulcode.txt so it was actually ulcode.txt.txt
I still don't get why adb didn't work but flashtool does, though.
For your other point, I used this guide to flash a kernel.sin:
https://twigstechtips.blogspot.ca/2016/04/sony-z5-compact-root-without-losing-ta.html
Hope it helps, and thanks again!!!!!
lfjriazr6kp6w95 said:
>> I tried it with flashtool and this post ***pasted*** and it worked!
1.: Go to the folder where Flashtool was installed
2.: Open the folder named "custom"
3.: Open the folder named "mydevices" (if it exists, in my case Flashtool version 0.9.18.4)
4.: Right button, New, Folder. Name the folder with your device code.
5.: Open the folder created previously
6.: Right button, New, Text Document. Name the text document as ulcode
7.: Open the text document created previously
8.: Paste your unlock code and save
9.: Open Flashtools and try the BLU option again.
obs 1: the step #3 I think it depends on your Flashtool version, because it wasn't mentioned at the solution
obs 2: at the step #4 is mentioned your device code. your device code is showed in the log when you click the button BLU, at the "Current device", after your device model.
Search a line like:
09/045/2015 23:45:08 - INFO - Current device : C2104 - AB100C2DE3 - 1272-4136_R5B - 1269-5420_15.3.A.1.17 - WORLD-a_15.3.A.1.17
in this case, the device code is AB100C2DE3 and this should be the new folder name (step 4)
Click to expand...
Click to collapse
I tried that method, it does not work. It SEEMS to work from face value, yes, but it is faulty I think.
Also, the location of the folder is wrong - it should go in /users/USERNAME/.flashtool/registeredDevices/
It 'unlocks' it during the flash stage of BLU in flashtool, yes, but it's supposed to do it in the fastboot stage according to other instructions I've read! It also freezes up and does not complete the operation unless I 'cancel' it - but it's supposed to go through a wipe process. It never does.
The system info has no status on whether or not it's unlocked or unlockable after flashtool 'unlocks' it using that method. Also, no other flashing can be done, because it returns the same Command not allowed error every time.
I believe fastboot is set up correctly as it returns getversion 0.5 and the device shows up in fastboot devices. I checked the IMEI was a correct one by going to imei.info. Don't know what else to do.
Why the heck are our devices refusing to unlock when others are doing it fine, and it's claiming to be unlockable?!?
I returned my Z5C and got a new one from the manufacturer and it's again refusing to unlock.
Hi,
I am late on this thread, but just buy a Z5C and face exactly that situation : no way to unlock the device ! Using flashtool and BLU results as a Rooting Status unknown, so I have to unlock the device using flashtool again...
The only thing I succeed is to flash the latest firmware with the help of XperiFirm. Still have "Bootloader unlock allowed : yes" but impossible to unlock it.
Has anyone found a solution for that problem ? Could it be related to a specific firmware to install ?
I am totally lost after two days of reading and unsuccessful attempts ; I would really like to install LineageOS on my new Z5C.
Any help would be greatly appreciated. Thanks.
Hi,
After some hours fighting with windows, drivers, signature (all in a VM), I switched back to Linux/Ubuntu. At least flashtool seems to work better (out of the box), and it asks me to reconnect the device in fastboot mode... But still the same error at the end. It adds "Maybe the OEM is not enabled", but it is of course (double checked).
But what means "Bootloader status : ROOTABLE" ? Did I miss something ?
Can somebody help please ? I contacted Sony support, but they don't support such operation...
Here is the log from flashtool :
====================
05/032/2018 17:32:18 - INFO - Please connect your device into flashmode.
05/032/2018 17:32:35 - INFO - Opening device for R/W
05/032/2018 17:32:35 - INFO - Device ready for R/W.
05/032/2018 17:32:35 - INFO - Reading device information
05/032/2018 17:32:36 - INFO - Phone ready for flashmode operations.
05/032/2018 17:32:36 - INFO - Opening TA partition 2
05/032/2018 17:32:37 - INFO - Current device : E5823 - CB5A274154 - 1299-1743_R12C - 1295-6639_32.2.A.5.11 - GENERIC_32.2.A.5.11
05/032/2018 17:32:37 - INFO - Closing TA partition
05/032/2018 17:32:37 - INFO - No loader in the bundle. Searching for one
05/032/2018 17:32:37 - INFO - Processing loader.sin
05/032/2018 17:32:37 - INFO - Checking header
05/032/2018 17:32:37 - INFO - Flashing data
05/032/2018 17:32:37 - INFO - Loader : S1_Root_f936 - Version : MSM8994_41 / Boot version : S1_Boot_MSM8994_LA1.2.2_42B / Bootloader status : ROOTABLE
05/032/2018 17:32:37 - INFO - Max packet size set to 4M
05/032/2018 17:32:37 - INFO - Opening TA partition 2
05/032/2018 17:32:37 - INFO - Start Reading unit 00 00 08 B2
05/032/2018 17:32:37 - WARN - ERR_SEVERITY="MINOR";ERR_CODE="0025";ERR_DYNAMIC="00000000";
05/032/2018 17:32:37 - INFO - Closing TA partition
05/032/2018 17:32:37 - INFO - Ending flash session
05/032/2018 17:32:37 - INFO - Now unplug your device and restart it into fastbootmode
05/033/2018 17:33:51 - INFO - Unlocking phone using key AF668B4FXXXXXXXX
05/033/2018 17:33:51 - INFO - ...
05/033/2018 17:33:51 - INFO - FAILED (remote: Command did not succeed)
05/033/2018 17:33:51 - INFO - finished. total time: 0.032s
05/033/2018 17:33:51 - WARN - Maybe the OEM is not enabled
05/033/2018 17:33:58 - INFO - Device disconnected
05/033/2018 17:33:58 - INFO - Device connected in fastboot mode
05/034/2018 17:34:07 - INFO - Device disconnected
I give up ! Tried almost everything (Win7x32, Win8.1x64, Flashtool v0.9.25 & 0.9.23 with ulcode.txt file created in user profile, Ubuntu, adb/fastboot command, from simple package, or Android studio), without any success. Some feedback though about Flashtool :
> Much easier to use the Linux version. On Ubuntu 18.10, it just works out of the box. I can easily flash the latest firmware ("Customized FR" in my case) though I downloaded it with Xperifirm on windows, as I did want to install mono on my Ubuntu desktop. At least I am now running Android 6.0.1.
> With version 0.9.25, I can use UBL button, Flashtool asks first for connect device in Flashboot mode (green light), then asks to disconnect and reconnect in Fastboot mode (blue But same error at the end : FAILED (remote: Command did not succeed). After a reboot, I can see "Rooting status : Unknown" in the service page.
> If I reflash, unknown rooting status is still there. I have to use Flashtool 0.9.23.2 (found link on another xda thread, only for windows) to "relock" the device and get back the "Bootloader unlock allowed : yes".
I don't understand what happens, what is the reason for that... Total mystery to me. There are so many posts about this issue, no one gives a real solution, Sony support does not care.
I am sad to be unable to install LineageOS on my device... Now will look how to "clean" Xperia Android as much as possible. Don't know if this is even possible. Don't know if I can root my phone, etc...
Last, why did I buy a Sony Z5C ? was looking for small (4.6") & afordable phone with good camera... Never thought I would be unable to install LineageOS.
That does sound frustrating. Have you checked the settings in the developer options? There's one there about "allow oem unlocking". If it's not set, you can't do it from fastboot, so maybe that's your problem? It's worth a try, at the very least.
tonsofquestions said:
That does sound frustrating. Have you checked the settings in the developer options? There's one there about "allow oem unlocking". If it's not set, you can't do it from fastboot, so maybe that's your problem? It's worth a try, at the very least.
Click to expand...
Click to collapse
Yes, I checked that for sure... Same for "Enable USB debug" and "Allow Unknown sources" in Security options.
Yesterday, as a last try, I follow that thread : I flashed old Lollipop firmware (E5823_32.0.A.6.200), backup TA partition, and tried unlock booloader again : same error FAILED (remote: Command did not succeed).
Probably something changed on Sony side that makes unlocking bootloader impossible ? That's what I think now.
Hmm, and in the service menu it says bootloader locking is allowed?
I'd be very surprised if Sony changed anything recently (if they even could, on a released phone), and I was able to do it successfully a few weeks back.
What's the error if you use an invalid unlock key? Maybe there's a typo (or request it from Sony again)? I know I'm grasping at straws, but I'm otherwise not sure. I had no difficulties at all...
tonsofquestions said:
Hmm, and in the service menu it says bootloader locking is allowed?
I'd be very surprised if Sony changed anything recently (if they even could, on a released phone), and I was able to do it successfully a few weeks back.
What's the error if you use an invalid unlock key? Maybe there's a typo (or request it from Sony again)? I know I'm grasping at straws, but I'm otherwise not sure. I had no difficulties at all...
Click to expand...
Click to collapse
Yes, Bootloader is OK, and providing a invalid unlock results in the same error : FAILED (remote: Command did not succeed).
From Sony website, you always get the same number when providing your EMEI.
Note there tones of threads about this issue, and really no clear solution, at least none from what I tried...
hi man!. Have you figure out how to unlock the bootloader? Same situation over here. This is my 3th xperia but first time facing this issue. Tomorrow I will install win 7 and will see if works
minos_cr said:
hi man!. Have you figure out how to unlock the bootloader? Same situation over here. This is my 3th xperia but first time facing this issue. Tomorrow I will install win 7 and will see if works
Click to expand...
Click to collapse
Unfortunately no. It is still the same, and I gave up for now, as I tried everything I could.
But I have a last plan : my Z5C is now running Android 6.0.1, which I installed myself using Flashtool & Xperifirm. Actually I got that phone with Android 5.1.1, and no upgrade was available when looking at system parameters, or even the Sony website). So I did it myself, using last package for French in Xperifirm.
And now, when looking at http://www.sonymobile.com/update, providing my EMIE code, it says my phone is up to date and running Android 7.1, which is wrong.
So I contacted Sony support for that, and they asked me to run a System -> Factory settings -> ReInit -> Clear everything. (or something simmilar).
I did not do it, because I am pretty sure this will not work, and I will probably go back to Android 5.1.1.
But I may contact the repair service (http://support.sonymobile.com/fr/repair/) and send my phone back to them asking for Android 7.1. I can complain for that, because my warranty is still valid !
My last hope is that when I will get back the phone from them, totally reinitialized, unlocking may work !!
I cannot do it for now, because I am going to move the next 2 months, but will try this when I am back. As I said, this is my last hope, unless someone find a solution to that problem.
Good luck to you, and keep us informed... By the way, which Android version are you running, and what says the Sony update site ?
man, yesterday I was frustrated too. Today, I installed windows 7 (it was a pain in the a**) and flashtool did the job like a champ.
pled said:
Unfortunately no. It is still the same, and I gave up for now, as I tried everything I could.
But I have a last plan : my Z5C is now running Android 6.0.1, which I installed myself using Flashtool & Xperifirm. Actually I got that phone with Android 5.1.1, and no upgrade was available when looking at system parameters, or even the Sony website). So I did it myself, using last package for French in Xperifirm.
And now, when looking at http://www.sonymobile.com/update, providing my EMIE code, it says my phone is up to date and running Android 7.1, which is wrong.
So I contacted Sony support for that, and they asked me to run a System -> Factory settings -> ReInit -> Clear everything. (or something simmilar).
I did not do it, because I am pretty sure this will not work, and I will probably go back to Android 5.1.1.
But I may contact the repair service (http://support.sonymobile.com/fr/repair/) and send my phone back to them asking for Android 7.1. I can complain for that, because my warranty is still valid !
My last hope is that when I will get back the phone from them, totally reinitialized, unlocking may work !!
I cannot do it for now, because I am going to move the next 2 months, but will try this when I am back. As I said, this is my last hope, unless someone find a solution to that problem.
Good luck to you, and keep us informed... By the way, which Android version are you running, and what says the Sony update site ?
Click to expand...
Click to collapse
I imagine (but can't say for certain) that whatever check Sony is using to display that info is either the last version that "called home" (maybe it needs the Xperia Companion software?), or the latest version that the phone was ever updated to. If you flash an old one with Flashtool (or worse: never connect to the internet with it), how on earth would you expect them to know the right version? Why would it even matter? The OS version is (largely) unrelated to the fastboot version, and shouldn't affect unlocking, other than the "allow oem unlocking" option in the developer settings.
I agree that the factory reset will leave it on the same OS; there's no reason it would upgrade.. I'm not sure why the OS wouldn't show updates available, maybe that customization version never had more releases. But is there any reason not to just download it and flash with Flashtool?
I couldn't find any other threads with people reporting problems - the majority of reports I saw were of successes. Not that I don't believe what you're seeing, mind you, just that I know there have been a lot of people getting things to work without a lot of issues.
minos_cr said:
man, yesterday I was frustrated too. Today, I installed windows 7 (it was a pain in the a**) and flashtool did the job like a champ.
Click to expand...
Click to collapse
Would be happy to know which Win7 (x32 or x64) and which flashtool version you used. Also if you setup the ulcode.txt file ?
---------- Post added at 09:59 AM ---------- Previous post was at 09:40 AM ----------
tonsofquestions said:
I imagine (but can't say for certain) that whatever check Sony is using to display that info is either the last version that "called home" (maybe it needs the Xperia Companion software?), or the latest version that the phone was ever updated to. If you flash an old one with Flashtool (or worse: never connect to the internet with it), how on earth would you expect them to know the right version? Why would it even matter? The OS version is (largely) unrelated to the fastboot version, and shouldn't affect unlocking, other than the "allow oem unlocking" option in the developer settings.
I agree that the factory reset will leave it on the same OS; there's no reason it would upgrade.. I'm not sure why the OS wouldn't show updates available, maybe that customization version never had more releases. But is there any reason not to just download it and flash with Flashtool?
I couldn't find any other threads with people reporting problems - the majority of reports I saw were of successes. Not that I don't believe what you're seeing, mind you, just that I know there have been a lot of people getting things to work without a lot of issues.
Click to expand...
Click to collapse
Well, this is a mystery to me. What I can say is that Sony website displays now :
Votre Xperia Z5 Compact est à jour !
Sortie : 32.2.A.5.11
Informations sur mon Android™
Android™ 7.1 Nougat est publié pour Xperia Z5 Compact.
Initially, I got the phone with Version 32.0.A.6.200. So they know somewhere I did an upgrade.
I would be happy to download the 7.1 version, but using Xperifirm, the only one I can find for the French country is the one I got, resulting in Android 6.0.1.
And because I have no knowledge at all on Sony specific things, I did try another firmware : I don't want to brick my phone.
Honestly, I have tried everything I could (Linux, Win, adb, flshtool, x32, x64, ulcode.txt, etc...) will always the same error, despite I agree most of people appears to success at one time. But most of the time without any clear explanation of what happen ! (except ulcode file story).
I read somewhere my problem could be related to the "Customization Version" (1299-1743_R12C in my case). Don't even understand what it could be related to, and how to change it.
What I expect is that Sony repair service will wipe everything on my phone, so that I could unlock it after it that.
Would be happy to know which Win7 (x32 or x64) and which flashtool version you used. Also if you setup the ulcode.txt file ?
Click to expand...
Click to collapse
I've personally used both Windows 10 (x64) and Linux. I used the latest version of Flashtool (0.9.25.0) and 0.9.24.4, though I couldn't tell you which combination I used on which OS.
[OS woes]
Let's start from the beginning. What OS are you trying to get to. Why?
Also note that there are multiple download versions in XperiFirm for your 1299-1743, make sure you're taking the right one.
I see 32.2.A.5.11, which it looks like you have (according to the earlier screenshot), which should be Marshmallow.
I also see 32.4.A.1.54, which should be Nougat.
Either should be straightforward to install with FlashTool (it sounds like you installed 5.11 with it?).
In the end, the customization option is mostly some regional differences - language, built-in apps, some VoLTE/fingerprint options for some regions, etc. Nothing significant ... or important if all you want to do is unlock it. That should be completely independent of the OS version.
Downgraing your OS and unlocking the bootloader should both end up resetting your phone/wipe the data.
So you should back up anything you want, and then mess around from there. I also fear the Sony Repair will wipe data, but it s also called "repair" so maybe it will backup/restore some of it. I'm not sure.
It's also possible that something is wonky with the OEM unlock setting, so wiping data will kick it back into working. It can't hurt to try, and is certainly easier than sending in a phone...
tonsofquestions said:
So you should back up anything you want, and then mess around from there. I also fear the Sony Repair will wipe data, but it s also called "repair" so maybe it will backup/restore some of it. I'm not sure.
It's also possible that something is wonky with the OEM unlock setting, so wiping data will kick it back into working. It can't hurt to try, and is certainly easier than sending in a phone...
Click to expand...
Click to collapse
Thank you for your advice. Will try again from scratch when I am back from travelling : 2 months in Asia ! At least, I will benefit of the "panorama" feature from the Sony camera that I may lose with LineageOS !
Official Global JoyUI 11 (Android 10) - SKYW2004221OS00MQ0 Factory OTA & Boot Image
Finally, Android 10, JoyUI11 is released officially yesterday. Thanks so much again to @ripiad, he shared me the big new version and I uploaded those(full update & boot image) at here.
If anyone receives the global EEA android 10 and shares it to me, I will upload that too.
Enjoy your BS.
wga0 said:
Finally, Android 10, JoyUI11 is released officially yesterday. Thanks so much again to @ripiad, he shared me the big new version and I uploaded those(full update & boot image) at here.
If anyone receives the global EEA android 10 and shares it to me, I will upload that too.
Enjoy your BS.
Click to expand...
Click to collapse
Can i update on locked bootloader and how? Sorry for asking dumb question
kumar abhishek said:
Can i update on locked bootloader and how? Sorry for asking dumb question
Click to expand...
Click to collapse
Put the update.zip file into /sdcard/ota/ directory, then dial *#*#1027#*#*. You don't need to unlock the bootloader only for that. You can find details from other thread.
Yep found it in another thread and updated sucessfully. Many thanks
Help joyui11
help I updated to joyui 11 with local update procedure but the lock does not work does not save the password even fingerprints. I'm without shermo locks you can help me thanks
babboooo said:
help I updated to joyui 11 with local update procedure but the lock does not work does not save the password even fingerprints. I'm without shermo locks you can help me thanks
Click to expand...
Click to collapse
It says it's compatible to android 9, reset is not required, but it's big upgrade. Plz backup and disable all locks before upgrade.
kumar abhishek said:
Can i update on locked bootloader and how? Sorry for asking dumb question
Click to expand...
Click to collapse
Hi bro i updated but thats not joy ui11
Can u share with me that threads..
.
hello, how long does the update in OTA take, because I am stuck on the start screen "black shark born to complete" need help please
cjscratch said:
hello, how long does the update in OTA take, because I am stuck on the start screen "black shark born to complete" need help please
Click to expand...
Click to collapse
Try hold volume down+power button wait until device restart
It will back to your previous version
cjscratch said:
hello, how long does the update in OTA take, because I am stuck on the start screen "black shark born to complete" need help please
Click to expand...
Click to collapse
If something goes wrong, and your phone doesn't booted, just try to reboot several times. It will change the slot automatically after several boot failure, and will be back to before the update. Or boot into the bootloader and change the slot manually, 'set active_slot x'. x is a or b. use a slot marked as successful.
Official Global JoyUI 11 (Android 10) - SKYW2004221OS00MQ0
hi friends I have tried several times to start joyui11 the problem in the start screen flashes several times and asks you to reset joyui 11 when I managed to start it anyway I noticed many bugs and system settings problems such as (lock screen) etc. that in my opinion I am not from the same region at the end I went back with my region with automatic update 01mp3-01mp4-01mp5 besides it does not update anymore I am with bootloader unlocked with joyui11 it blocks you bootloader if you see developer settings it is blocked maybe because new android 10? it's very nice however the new interface changes little from miui. I hope it arrives for my region of Italy thanks for the support #vga0
Invalid MMI code
wga0 said:
Put the update.zip file into /sdcard/ota/ directory, then dial *#*#1027#*#*. You don't need to unlock the bootloader only for that. You can find details from other thread.
Click to expand...
Click to collapse
Hey, several of my blackshark2 friends are not able to dial *#*#1027#*#*. It will prompt Connecton problem or invalid MMI code.
Fyi, I did successfully updated to Joy Ui 11 without issues, but not my friends.
Do you have solutions for that?
The upgrade worked flawlessly aand I am in awe in how much better it is now compared to the Android 9 one! One thing tough is not working; All the options for the light settings are grayed out. I was hoping that the side lights would finally work properly as a notification LED. Anyone else having this issue?
hello there,
do we still get stockish experience on the new joyui 11 update?
Attention skyw2004221os00mq0 ota
after various tests and various reboots joyui11 works only with blocked bootloader I discovered this I did not understand why the new update did not work it crashed and the system did not work well then I tried to block bootloader so starting from 1mp5 to 0mq0 to run no startup problem and now fingerprints also work.attention to update with unlocked bootloader
So joyui11 shifts from stock to miui as base. Would there be a stock variant of joyui11?
babboooo said:
after various tests and various reboots joyui11 works only with blocked bootloader I discovered this I did not understand why the new update did not work it crashed and the system did not work well then I tried to block bootloader so starting from 1mp5 to 0mq0 to run no startup problem and now fingerprints also work.attention to update with unlocked bootloader
Click to expand...
Click to collapse
Bro how do you lock the bootloader again? In any firmware (Mp3, mp4, etc) my bootloader stills unlocked. Only in the first time that I try JUI11 goes blocked
#Diex_7
it is better to start factory reset from settings
1 go back to mp3 depends on your region (global or EEA) so (0mp3 or 1mp3)
2 have the system perform automatic updates to the last
3 use pc adb and fastboot
4 enable usb debug developer settings
5 use pc command (adb reboot bootloader) and confirm usb debug notification
6 use pc adb command (fastboot flashing lock) gives you okay
7 press power button the phone asks you to reset foul otherwise you can't go on
8 once the system has started, activate developer settings and deactivate unlock oem
9 download joyui11 * # * # 1027 # * # * install and you're done only with locked bootloader does android 10 joyui11 work
babboooo said:
#Diex_7
it is better to start factory reset from settings
1 go back to mp3 depends on your region (global or EEA) so (0mp3 or 1mp3)
2 have the system perform automatic updates to the last
3 use pc adb and fastboot
4 enable usb debug developer settings
5 use pc command (adb reboot bootloader) and confirm usb debug notification
6 use pc adb command (fastboot flashing lock) gives you okay
7 press power button the phone asks you to reset foul otherwise you can't go on
8 once the system has started, activate developer settings and deactivate unlock oem
9 download joyui11 * # * # 1027 # * # * install and you're done only with locked bootloader does android 10 joyui11 work
Click to expand...
Click to collapse
Sorry for late answer and thank you for commenting. JoyUI11 changes its base and has lots of incompatible settings. Reset before/after, restore/disable all customs,locks are recommended strongly, and OEM unlock is also seemed as bug because MIUI and stockUI has completely different unlock management
Skyw2004221os00mq0 ota
it's true however there are some bugs that can be fixed in the updates.
the battery consumes more on 0mq0 games sometimes like COD skip screen and you have to re-enter the side led strips are off the s sign on developer settings some functions do not go the brightness when you unlock becomes strong however a great job is a real adapted miui stockui was boring now you can also install apk miui
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