Hello guys;
I bought just three days ago a new zuk Z1, it doesn't seem to have probblem and then I would start to mod it (root, custom rom ecc.).
but this will void the warranty.
there is a way to restore warranty for the zuk z1? (es. lock the bootloader, reset the flash counter, stock system and recovery ), if in the future the phone might have problems.
thank you
I just want to know if it is possible to restore warranty or is lost forever?
anyone?
use this link to get the official stock cyanogen flashable zip : http://builds.cyngn.com/factory/ham/cm-12.1-YOG4PAS3OH-ham-signed.zip
or this one to be used with fastboot: http://builds.cyngn.com/factory/ham/cm-12.1-YOG4PAS3OH-ham-signed-fastboot.zip
and ensure that developer mode is enabled : "go to settings >about click 5 times on the build number till it says you are no a developer" go to developer mode and ensure "Update Cyanogen" recovery is ticked.
tara you are back on fully stock like brand new out of the box
yacbos said:
use this link to get the official stock cyanogen flashable zip : http://builds.cyngn.com/factory/ham/cm-12.1-YOG4PAS3OH-ham-signed.zip
or this one to be used with fastboot: http://builds.cyngn.com/factory/ham/cm-12.1-YOG4PAS3OH-ham-signed-fastboot.zip
and ensure that developer mode is enabled : "go to settings >about click 5 times on the build number till it says you are no a developer" go to developer mode and ensure "Update Cyanogen" recovery is ticked.
tara you are back on fully stock like brand new out of the box
Click to expand...
Click to collapse
But your bootloader will be unlocked still I guess.
Planet X said:
But your bootloader will be unlocked still I guess.
Click to expand...
Click to collapse
Code:
fastboot -i 0x2b4c oem lock-go
If i'm not wrong this is the method to lock it back
But you can't restore DRM Keys ....
olefou-zuk said:
But you can't restore DRM Keys ....
Click to expand...
Click to collapse
Is not a Sony Z device .
@tomdan95 warranty is not an issue, since there's none for this device : You won't be able to contact ZUK's after sale support whatsoever because it doesn't exist
So I advise you not to **** your device up like I did x')
I-Immortal said:
@tomdan95 warranty is not an issue, since there's none for this device : You won't be able to contact ZUK's after sale support whatsoever because it doesn't exist
So I advise you not to **** your device up like I did x')
Click to expand...
Click to collapse
no warranty? in europe you have it 2 years.
http://www.zuk-store.com/en/content/6-our-strengths
I-Immortal said:
@tomdan95 warranty is not an issue, since there's none for this device : You won't be able to contact ZUK's after sale support whatsoever because it doesn't exist
So I advise you not to **** your device up like I did x')
Click to expand...
Click to collapse
I have bought it from amazon so According to the laws in Europe i can send it to Them for the warranty
I-Immortal said:
@tomdan95 warranty is not an issue, since there's none for this device : You won't be able to contact ZUK's after sale support whatsoever because it doesn't exist
So I advise you not to **** your device up like I did x')
Click to expand...
Click to collapse
I know you're very annoyed because of what happened to your device but since you bought your ZUK from eBay..well..It's Amazon or an authorized reseller.
I live in Egypt and I bought mine from UniGroup which is an authorized reseller for ZUK. I have a one year warranty.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zuk offcial reseller of italy
anyway thanks for all the answers
so ultimately , it is possibile to restore warranty, after unlock bootloader and root?
Guys, I live in Europe (France) and I bought it on eBay to TomTop which is an official and authorized seller (see on zuk.hk/onlineshop ) there was a 2 years warranty mentioned, but since ZUK has no after sale support, there's nothing they can do to repair the device so you'll have to hope the seller is kind enough to refund/exchange it (which was not the case with TomTop) or hope that you've bought it with PayPal :3
And @tomdan95 , it should be restored once you've unrooted and relocked the bootloader of the device
Planet X said:
But your bootloader will be unlocked still I guess.
Click to expand...
Click to collapse
i trust the only way to lock/unlock boot loader is via fast boot it cant be done via flashing or restoring.
yacbos said:
i trust the only way to lock/unlock boot loader is via fast boot it cant be done via flashing or restoring.
Click to expand...
Click to collapse
The easiest way is to use the toolkit of @mauronofrio http://forum.xda-developers.com/zuk-z1/orig-development/tool-toolzukz1eng0-0-3-mauronofrio-t3332563. This tool does eveything for you.
It is possible to clear flags and restore warranty state
Flags are stored in:
/dev/block/bootdevice/by-name/aboot
Unlock Bit Position - 0x001FFE10 Hex
Tamper Bit Position - 0x001FFE14 Hex
Link: http://forum.xda-developers.com/zuk-z1/help/guide-unlock-bootloader-zuk-z1-wiping-t3251801
as far as I remember, I had to flash twrp 3 and it allowed me to change aboot.img and clear all flags
Wasnt easy but it is doable
Chiminig in with some personal experience, I actually was able to get my ZUK Z1 fixed by warranty after unlocking then re-locking the bootloader.
So I bought my ZUK from a local reseller with 1 year warranty, unfortunately it seems I got a faulty unit since I had major battery problems - including the phone randomly turning off at times and often displaying wildly inaccurate battery percentages. I tried fixing the issue myself, and thinking it might be a software issue I factory-reset the phone... then later I also decided to try and see if CyanogenMod 13 fixes the issue (which was less smart, given the potential to screw up the warranty). Finally when none of it worked, I decided to take it back to the store for warranty service - so before that, I flashed back the stock Cyanogen OS factory image (links here then relocked the bootloader thru fastboot using the command "fastboot -i 0x2b4c oem lock-go". With the info command ("fastboot -i 0x2b4c oem device-info") it then shows:
Code:
(bootloader) Device tampered: [B]false[/B]
(bootloader) Device unlocked: [B]false[/B]
(Note that even when the bootloader was unlocked, it still said "Device tampered: false", but true on the latter).
Now I'm not sure if there are any other flags that could indicate I was messing with the device's software (which could have been a convenient thing for them to blame me for the battery troubles), I don't think there are but even if there were my warranty fixers did not notice them. I later got the device back with a new battery.
Tuberomix said:
Chiminig in with some personal experience, I actually was able to get my ZUK Z1 fixed by warranty after unlocking then re-locking the bootloader.
So I bought my ZUK from a local reseller with 1 year warranty, unfortunately it seems I got a faulty unit since I had major battery problems - including the phone randomly turning off at times and often displaying wildly inaccurate battery percentages. I tried fixing the issue myself, and thinking it might be a software issue I factory-reset the phone... then later I also decided to try and see if CyanogenMod 13 fixes the issue (which was less smart, given the potential to screw up the warranty). Finally when none of it worked, I decided to take it back to the store for warranty service - so before that, I flashed back the stock Cyanogen OS factory image (links here then relocked the bootloader thru fastboot using the command "fastboot -i 0x2b4c oem lock-go". With the info command ("fastboot -i 0x2b4c oem device-info") it then shows:
Code:
(bootloader) Device tampered: [B]false[/B]
(bootloader) Device unlocked: [B]false[/B]
(Note that even when the bootloader was unlocked, it still said "Device tampered: false", but true on the latter).
Now I'm not sure if there are any other flags that could indicate I was messing with the device's software (which could have been a convenient thing for them to blame me for the battery troubles), I don't think there are but even if there were my warranty fixers did not notice them. I later got the device back with a new battery.
Click to expand...
Click to collapse
Can u tell me how u flashed those images??
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey guys i updated my device to JB V20a but i cannot unlock bootloader.I'm not getting any error but when I run the command "adb reboot oem-unlock"y.phone reboots and asks me if i want to unlock bootloader.I choose yes and then it says "Download mode" with red colour letters.Then nothing.When I disconnect from cable the phone says factory reset............Please wait!
Its unlockable?Or i am doing something wrong?
If it's unlockable can I flash a .kdz rom from other country and achieve to unlock it?
Sent from my LG-P880 using xda app-developers app
GRG13 said:
Hey guys i updated my device to JB V20a but i cannot unlock bootloader.I'm not getting any error but when I run the command "adb reboot oem-unlock"y.phone reboots and asks me if i want to unlock bootloader.I choose yes and then it says "Download mode" with red colour letters.Then nothing.When I disconnect from cable the phone says factory reset............Please wait!
Its unlockable?Or i am doing something wrong?
If it's unlockable can I flash a .kdz rom from other country and achieve to unlock it?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
Make sure you have fastboot drivers installed, it was my problem. It will work when it goes from download mode to factory reset WITHOUT taking the cable out, try the unlock tool it has drivers packaged with it i believe
Otherwise?It means that its unlockable
Στάλθηκε από το LG-P880 μου χρησιμοποιώντας Tapatalk 2
GRG13 said:
Otherwise?It means that its unlockable
Στάλθηκε από το LG-P880 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Eur 4.1 firmware is unlockable, if it isnt i dont think reboot-oem-unlock would work
nevermind
About unlocking the bootloader
Quick question guys, I had a Atrix 4G. When I unlocked the bootloader at the boot logon it shown the message "unlocked'.
When I unlock the bootloader for my "still to come" (shipped) O4X it will display any message of unlocked bootloader?
Sorry for my bad english
Erus Tyrannus said:
Quick question guys, I had a Atrix 4G. When I unlocked the bootloader at the boot logon it shown the message "unlocked'.
When I unlock the bootloader for my "still to come" (shipped) O4X it will display any message of unlocked bootloader?
Sorry for my bad english
Click to expand...
Click to collapse
it will on S/W upgrade screen, not on boot logon afaik
JoinTheRealms said:
Make sure you have fastboot drivers installed, it was my problem. It will work when it goes from download mode to factory reset WITHOUT taking the cable out, try the unlock tool it has drivers packaged with it i believe
Click to expand...
Click to collapse
I have the packet from 17 post, now, i click at install and nothing happens, could you tell me how proceeds ??
Im allways getting the message above:
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 169.836s
Installed the Euro-XXX and in About Phone read:
P88020A-724-06
Any rom installed returns this code 724-06, till the 20B, i got this code.
Any help ??
I have some stupid Questions
1. Is it possible to Lock the Bootloader again if you get it unlocked by any means?
2. How does this effect yoour warranty on the phone?
3. Do you lose your warranty?
sPEADy said:
I have some stupid Questions
1. Is it possible to Lock the Bootloader again if you get it unlocked by any means?
2. How does this effect yoour warranty on the phone?
3. Do you lose your warranty?
Click to expand...
Click to collapse
1. No. It may or may not show as locked if you get back to ICS, but if you then go back to JB it shows as unlocked again.
2 and 3. Depends if you bought the phone in Europe or elsewhere.
For Europe, you might lose the warranty regarding software-related issues. Hardware-related issues should still be covered (due to a EU directive, read more about it here), although you might find resistance from some LG Support centers. If you do, just state it's your right as granted by Directive 1999/44/CE. If they still don't grant you, I believe there are legal ways you must follow.
If you bought it outside of Europe, it would depend on the legislation of your Country.
Also, a quick reminder that there's still only Nightlies on the CM 10 ROM, and no other Custom ROMs to speak of. So my general advice would be to read on about the way to unlock your phone, but only do it if you actually want to install a Custom ROM right away (which also implies you're ready to the possible buggy-ness of the available ROMs).
skryptus said:
1. No. It may or may not show as locked if you get back to ICS, but if you then go back to JB it shows as unlocked again.
2 and 3. Depends if you bought the phone in Europe or elsewhere.
For Europe, you might lose the warranty regarding software-related issues. Hardware-related issues should still be covered (due to a EU directive, read more about it here), although you might find resistance from some LG Support centers. If you do, just state it's your right as granted by Directive 1999/44/CE. If they still don't grant you, I believe there are legal ways you must follow.
If you bought it outside of Europe, it would depend on the legislation of your Country.
Also, a quick reminder that there's still only Nightlies on the CM 10 ROM, and no other Custom ROMs to speak of. So my general advice would be to read on about the way to unlock your phone, but only do it if you actually want to install a Custom ROM right away (which also implies you're ready to the possible buggy-ness of the available ROMs).
Click to expand...
Click to collapse
My phone is just 3 months old I am not going to do this any way I am very happy with the Stock Rom I will give it a try when I am over the Warranty Period. Thank you for your reply.
Have a nice Day/Eve.
Hello everyone.
i been trying to unlock the boot loader on my Sony Z1 mobile phone.. i went into the 02 store today (UK) and asked the GURU and he said the phone would of come locked boot loader but by going to the Sony website you can request the unlock code... easy said then done right?
i am on a custom ROM with stock kernel because of the Locked-[BL] 4.4.4 kitkat with recovery.. i installed this..
http://forum.xda-developers.com/xperia-z1/development/ub-trinity-vengeance-raptorx-v1-0-t2838835
anyway i go to the Sony site and follow the walk-though... i get to stage 3 out of 4 and i get this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i pretty sure all the drivers for fast-boot mode are installed correctly and i don't understand the error code: remote: command not allowed)
after trying and spending a few hours on the forum i found no answer.. or reason behind it..
so i tried another approach using a boot-loader unlocker by kingo.. and this is the result..
Same Issue
I ran into this exact same issue on a Xperia Z Ultra. It seems that this is caused by the permissions being changed to" Read Only" on a specific partition of the bootloader/ low level flash memory. It seems to be caused by buggy versions of flash tool and or corrupted drivers. I did not find an answer to this unfortunately, but maybe this will help lead you in the right direction. If you can still return it, I would and play dumb. I am guessing it needs to be reflashed at the factory via the internal IO/JTAG headers. Hope this helps a bit. Please let me know if you find an answer.
Hello,
You must execute the Terminal on Windows as Admin. After that you have write permission.
-Happy Feet- said:
Hello,
You must execute the Terminal on Windows as Admin. After that you have write permission.
Click to expand...
Click to collapse
you mean open CMD prompt using admin then root to platform-tools?
Regards
Paul
Yes
-Happy Feet- said:
Yes
Click to expand...
Click to collapse
i tried this... did nothing still same error..
i contacted sony starting heres the chat log...
Please wait while we find an agent to assist you...
You are currently in position number 1 in the queue.
You have now been connected to an agent.
Kayleigh: Hi Paul, thank you for contacting Sony Xperia UK Chat Support. My name is Kayleigh, please could I take your full name and email address?
Paul Sharman: ***********
Paul Sharman: i need to talk with a phone tech, as my questions are very specific
Kayleigh: Thank you for providing me with this information, Please could you confirm which model of phone you have and which network it is on?
Paul Sharman: Sony Z1, on 02
Paul Sharman: c6903
Paul Sharman: ?
Paul Sharman: ??
Kayleigh: Thank you, how can I help you today?
Paul Sharman: i need to talk with a phone tech, as my questions are very specific
Kayleigh: Thank you, how can I help you today?
Paul Sharman: i am trying to unlock my phone bootloader... via your website.. http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Paul Sharman: as i get to the last step of your walkthough i get error saying: FAILED (remote: command not allowed)
Paul Sharman: http://s29.postimg.org/y79l26e2f/failed_step_2.jpg
Kayleigh: Unfortunately we are unable to provide full support with regards to unlocking the boot loader on your handset due to the fact that this process will void the warranty on your handset.
Paul Sharman: i been to see the GURU at 02 and he said i should contact sony directly.. because acording to 02 the phone should be able to unlock the bootloader... i have everything correctly setup. such as drivers.
Kayleigh: I'd recommend visiting the following link which should provide you with info on how to unlock the bootloader - http://unlockbootloader.sonymobile.com/
Kayleigh: If you are unsure how to unlock the boot loader on your handset, please be aware that if this process is carried out incorrectly you might damage the performance or function of your handset
Kayleigh: As this process voids warranty, we would be unable to help directly with any problems which may occur due to the boot loader being altered.
Paul Sharman: stop copying me messages from a transcript...
Paul Sharman: i understandly fully how to go though the process..
Paul Sharman: i need to talk with a tech from sony..
Paul Sharman: i am very aware of how to go though this process, i done it on 3 mobiles from 2008 to current year.. but the Z1 isnt working.. because i think there is a permissions issue
Kayleigh: This is not something anyone from this support team can help you with, we do apologise.
Paul Sharman: so wait?
Paul Sharman: if your website isnt allowing me to do this process it means my handset is faulty and has been for a while... way before i purchased the device from the phone shop.
Paul Sharman: so it means you have to replace it because your website states how to complete this process.. and since my phone isnt responding to the commands your website states..
Paul Sharman: i have full proof and evidence to support my claim.. i have asked in 3 different places (internet XDA forums, Phones shops and 02 Directly)
Kayleigh: This is up to the customer, we can not provide information of how to do this over the chat, you may void your warranty if you carry this out and that is the reason I can not support you further. You can always send the handset in for repair you do have a 24 month warranty with Sony Xperia for any manufacturing faults however if the bootloader has been locked the warranty may already be void.
Paul Sharman: yes but the bootloader isnt unlocked...
Paul Sharman: so i still have warranty...
Kayleigh: Therefore you can still send the handset in for repair if there is a fault.
Paul Sharman: when i send the phone back what are you going to do with it? you will check to see if the device is unlocked which it isnt..
Paul Sharman: and then find no other issues..
Paul Sharman: but the issue is your website isnt allowing me to unlock the bootloader...
Kayleigh: Therefore we can not help you further with your query. We do apologise.
Paul Sharman: yes you can...
Paul Sharman: at the end of the day my device is defected...
Paul Sharman: you can replace the hole handset or give me an upgrade
Paul Sharman: BOOTLOADER UNLOCKED ="NO" meaning my device covered by your warrently..
Kayleigh: In what way is this handset defected? You did suggest there was no issues to find.
Paul Sharman: to unlock the boatloader i get errors which no one can give me any support on.. even though you offer this service though your website you cant give me any direction.. your just telling me if it doesnt work there is nothing we can do... this is hopeless... its your brand your phone software...
Paul Sharman: Kernel isnt been setup of there has been a defect from the first time i powered on the device?
Paul Sharman: the stock kernel should allow the unlock bootloader with no errors according to your website?
Kayleigh: If there is an error unlocking the bootloader this is still something we can not help you with, as if the phone becomes faulty after unlocking this voids warranty, I can not provide you with further support on this.
Paul Sharman: this doesnt make any sense..
Paul Sharman: the PHONE should allow me to unlock the bootloader... your WEBSITE tells me how to do it..
Paul Sharman: not being successful means there is a problem with the handset..
Kayleigh: The link to unlock the bootloader is on our developers website, you do this at your own risk we can not provide further support.
Paul Sharman: the handset states the bootloader is locked so basicly its still under warrently?
Paul Sharman: your not listening to me are you?? i told you my phone is still bootloader unlocked = NO
Kayleigh: we would be unable to confirm that the handset is covered until the handset has been examined by our engineers therefore I can not answer that question I do apologise.
Paul Sharman: well i am telling you your engineers will find no evidence and i will send it back happyfully for them to do all testing they like..
Paul Sharman: so taking that on board what are you advising i do?
Paul Sharman: i want to send back the device for a full reset and rebuild software/hardware.
Paul Sharman: it would be easier just to send me a new device to be honest.
Paul Sharman: my SONY Z1 is defected..
Kayleigh: Our engineers can not unlock the bootloader therefore we would advise if you have no other fault on the handset the phone will be sent back to you unrepaired.
Paul Sharman: the device is still defected.
Kayleigh: Okay sorry to hear that in what way Paul?
Paul Sharman: the phone gives off random vibrations after activating a button.
Paul Sharman: the phone soft vibrate for a few mins until i shake it.
Paul Sharman: even when the device is off it continues to vibrate.
Paul Sharman: which is another defect..
Kayleigh: I'm sorry to hear that. I'd recommend that you try repairing the software on your handset to see if this helps. Do you have PC Companion installed on your PC?
Paul Sharman: yes i done this..
Paul Sharman: console.writeline;(DEFECTED PHONE) do i have to explain any more?
Kayleigh: Okay it sounds like your handset may need to be sent for repair. Which country was your handset purchased in?
Paul Sharman: UK
Paul Sharman: England
Kayleigh: Okay, would you like me to provide you with details on how to send your phone for repair?
Paul Sharman: you can arrange for someone to collect the device..
Kayleigh: We will not be able to do that, the address is freepost however.
Kayleigh: The average turnaround time for the repair is 5-7 working days from the day the handset is received at the repair centre.
Paul Sharman: ok
Kayleigh: Please could I take the IMEI number of your handset?
Paul Sharman: sure
Paul Sharman: how do i provide you this?
Kayleigh: the IMEI is found on the box starts with 35 or where the SIM card slot is, there is a small tag which pulls out and it is also on there.
Kayleigh: It can also be found by dialling *#06# on your handset.
Paul Sharman: **************
Kayleigh: Thank you. I’d recommend you keep a copy of this IMEI number for your own reference.
Kayleigh: To book your handset in for repair please visit the following link:
Kayleigh: http://mysupport.sonymobile.com/global-en/#/support
Kayleigh: You will then be asked to either login with or create a Sony Mobile account. If you do not already have an account you can create one alternatively you can sign in via Facebook or using Google+.
Kayleigh: Once your account has been created select Repair your device and you will be guided through the repair process.
Kayleigh: Please ensure you read through all of the information which is provided as you go through this online.
Kayleigh: I hope this information has been helpful to you. Is there anything else I can help you with in the mean time?
Paul Sharman: no thank you kayleigh.. thanks for your help
http://forum.xda-developers.com/xpe...bootloader-t2153261/post38878089#post38878089 I had to do something like this with the drivers to get them working.
Post 138.
Lord Takyon said:
http://forum.xda-developers.com/xpe...bootloader-t2153261/post38878089#post38878089 I had to do something like this with the drivers to get them working.
Post 138.
Click to expand...
Click to collapse
have just tried on windows 7.. still same problem... maybe my phone can never be unlocked for some reason.. its pretty dam shame..
I just downloaded the MINIMAL ADB and FASTBOOT program (search the forums for it)
ALSO
Download Flashtool, install it, and before opening up the program, go to your C drive, there should be a folder FLASHTOOL, open the folder, there should be another folder called drivers, install ALL the drivers
With the MINIMAL ADB and FASTBOOT program, choose the program to put icon on desktop, it will put a icon on your desktop, when you want to use it right click, and use as administrator.
It has all the files you need, the folder is stored in the C drive under program files (x86) and minimal adb and fastboot folder (you can also put your recovery img and boot img files to this folder)
when the program opens all you got to do is follow the bootloader unlock program, it should work perfectly now.
This still works if you have the android SDK stuff installed or not, I have used this program on virtually all my android phones, and flashed kernals etc perfectly, also unlocked bootloaders on all my sony phones
any problems, PM me
Well you said boot loader unlock no so you can't unlock your bootloader. Any phone brought from carrier is LB forever. No whats or buts
Are you sure you correctly checked if your bootloader is unlockable?
Type *#*#7378423#*#* at dialer, and go to 'SERVICE INFO > CONFIGURATION' and if 'Bootloader unlock allowed' is set to 'yes'.
If 'yes' you are OK. You can then just use Flashtool by Bin4ry and Androxyde to unlock the bootloader, using the code from SONY.
If 'no', I would suggest to FIRST make a backup, and after that flash another unbranded FTF, using FlashTool again. But beware, because you may get hardbricked!
try another usb cable
I get the same error using kingo's ... I have a carrier free phone bought from the sony store, Xperia Z1 and yes it said it was unlockable and I'm using widows 7 , Any help?
I have the same issue asked around but no solution yes
Did you got unlock bootloader or sim card on C6903 or have knowledge on how to do?
---------- Post added at 07:01 PM ---------- Previous post was at 06:11 PM ----------
NFS_FM said:
Are you sure you correctly checked if your bootloader is unlockable?
Type *#*#7378423#*#* at dialer, and go to 'SERVICE INFO > CONFIGURATION' and if 'Bootloader unlock allowed' is set to 'yes'.
If 'yes' you are OK. You can then just use Flashtool by Bin4ry and Androxyde to unlock the bootloader, using the code from SONY.
If 'no', I would suggest to FIRST make a backup, and after that flash another unbranded FTF, using FlashTool again. But beware, because you may get hardbricked!
Click to expand...
Click to collapse
If I flash another unbranded FTF using flashtool what's the possibility to get hardbrick?
I have a galaxy S2 branded on Orange and I haven't problem with root, unlock bootloader and SIM that I unlock by simply using a .apk , What's the difficult on Xperia Z1 (C6903) and why nobody find out the solution?
willflux said:
If I flash another unbranded FTF using flashtool what's the possibility to get hardbrick?
I have a galaxy S2 branded on Orange and I haven't problem with root, unlock bootloader and SIM that I unlock by simply using a .apk , What's the difficult on Xperia Z1 (C6903) and why nobody find out the solution?
Click to expand...
Click to collapse
Getting hard-bricked is only possible by flashing an inappropriate kernel, which may happen by installing a ROM not intended for the device, which means a Z2 or Z3 ROM. You can try any C6903 ROM variant without problems, if you are careful enough. After the flashing try again the procedure, via FlashTool this time.
Unfortunately or not, Samsung is Samsung, and Sony is Sony. Sony is much more "developper-friendly", but it doesn't leave XPERIA insecured, when Samsung uses TouchWiz, replacing as much "stock Android" as possible, creating new problems (e.g. Xposed for Lollipop).
NFS_FM said:
Getting hard-bricked is only possible by flashing an inappropriate kernel, which may happen by installing a ROM not intended for the device, which means a Z2 or Z3 ROM. You can try any C6903 ROM variant without problems, if you are careful enough. After the flashing try again the procedure, via FlashTool this time.
Unfortunately or not, Samsung is Samsung, and Sony is Sony. Sony is much more "developper-friendly", but it doesn't leave XPERIA insecured, when Samsung uses TouchWiz, replacing as much "stock Android" as possible, creating new problems (e.g. Xposed for Lollipop).
Click to expand...
Click to collapse
Hummm understood, I'll find the unbranded FTF to flash and them unlock the bootloader. I hope after unlock bootloader i can find a way to unlock the SIM witout paying for code
willflux said:
Hummm understood, I'll find the unbranded FTF to flash and them unlock the bootloader. I hope after unlock bootloader i can find a way to unlock the SIM witout paying for code
Click to expand...
Click to collapse
What code? There is nothing you have to pay for! The code is provided by Sony itself for free, from this site: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Excuse me if I misunderstood you.
I meant to unlock the SIM card, the only way I found to unlock until now is getting a code by paying a tax, even the .apk for android has this thing, I didn't know that unlock sim in android phone could be so worthwhile (I don't think that's worthwhile at all)
Hello guys!
So..today i tried to unlock my G6 Plus' bootloader and ended up doing so but i got an error when booting the phone with the following "Device has loaded a different operating system" and then i tried to flash the Stock Firmware and succeded in doing so, but the error was still there.
After this i locked the bootloader again but still the error is there and In the End i tried to flash the Stock Firmware again but the bootloader was locked and i ended up bricking the phone.
Now i tried everything the whole day to make it work again but no success at all.
PS: OEM Unlock is unticked so i cant unlock the bootloader...basically i cant flash anything on my G6 Plus.
Can you please help me guys in getting my phone working again? I tried like everyting but with OEM Unlock unticked and Bootloader Locked i can't really get it working.
Thank you in advance!
Dan.
Thank you in advance guys! Hope you can help me!
Can you still boot in the bootloader?
Thomas Hunter said:
Can you still boot in the bootloader?
Click to expand...
Click to collapse
Yes, bootloader is working fine.
Just Recovery isnt working, it goes in but wont load menu.
You're not hard bricked if bootloader works. Unlock bootloader and try flashing stock firmware again. I've run in to this issue a few times. Nothing to worry about in the end.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
You're not hard bricked if bootloader works. Unlock bootloader and try flashing stock firmware again. I've run in to this issue a few times. Nothing to worry about in the end.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
OEM unlock is unticked so... I cant really unlock the bootloader..
The switch itself does nothing. Unlock the bootloader and flash stock. When it is locked you are unable to modify system partition.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
The switch itself does nothing. Unlock the bootloader and flash stock. When it is locked you are unable to modify system partition.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
I tried to unlock it but i always got an error, something like "go to Settings and activate OEM Unlock" or something like this..
Could you provide a image
Thomas Hunter said:
Could you provide a image
Click to expand...
Click to collapse
Sure!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TrueGodFlow said:
Hello guys!
So..today i tried to unlock my G6 Plus' bootloader and ended up doing so but i got an error when booting the phone with the following "Device has loaded a different operating system" and then i tried to flash the Stock Firmware and succeded in doing so, but the error was still there.
After this i locked the bootloader again but still the error is there and In the End i tried to flash the Stock Firmware again but the bootloader was locked and i ended up bricking the phone.
Now i tried everything the whole day to make it work again but no success at all.
PS: OEM Unlock is unticked so i cant unlock the bootloader...basically i cant flash anything on my G6 Plus.
Can you please help me guys in getting my phone working again? I tried like everyting but with OEM Unlock unticked and Bootloader Locked i can't really get it working.
Thank you in advance!
Dan.
Thank you in advance guys! Hope you can help me!
Click to expand...
Click to collapse
Hi, Dan...
I really do wish I had some good news to impart, but sadly I suspect your Moto G6 Plus is probably not recoverable.
The OEM Unlocking setting in Developer Options is part of Googles Factory Reset Protection scheme. Ostensibly, it's designed to prevent lost or stolen devices from being reflashed back to stock and dishonest individuals then claiming the device as their own.
I ran afoul of this myself, four years ago, with my (then) new Nexus 9 tablet which originally shipped with Android 5, Lollipop and it was the first device I'd owned that required OEM Unlocking to be enabled in Developer Options before the bootloader could be unlocked.
I won't bore you with the details here, but if you have a mind to, you can read about my thwarted endeavours to resurrect my Nexus 9 here...
https://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312
Fortunately, my Nexus 9 was still new, and I had a no-quibble warranty that I'd paid extra for, so I was able to get it replaced at the store from which I'd bought it.
-----------------------------------------
Around 2015 a solution (of sorts) was eventually found for this problem, for both the Nexus 6 phone and the Nexus 9 tablet, however it required a very specific set of criteria for it to work.
The OEM Unlocking setting in Developer Options flips a binary state flag, from either ON (Enabled) or OFF (Disabled) and it's stored in a special Persistent (PST) partition, which doesn't get touched when factory resetting the device, when receiving OTA updates or when reflashing it. As the name suggests, it 'persists'.
So it required somebody to create a dump image file of the PST partition with the OEM Unlocking flag already set to ENABLED on their device. This dump image file would be created by using a <dd, if, of> command in a terminal shell.
The person whose device was semi-bricked, would download this dump image file of the PST partition, and flash it to their device using a similar <dd, if, of> shell command, via ADB in TWRP Custom Recovery. This would overwrite their PST partition, where the OEM Unlocking flag is NOT enabled...
...with a version where it IS enabled, and consequently fastboot flash commands would then work.
*****
It required root on both devices, and TWRP custom recovery to be already flashed on the semi-bricked device, since ADB shell commands can not be run in the normal stock recovery.
You can read about the technical details here...
https://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
-----------------------------------------
Theoretically, the method detailed above could perhaps be adapted for the Moto G6 Plus ~ you'd just need to find somebody with an already rooted Moto G6 Plus prepared to create a dump image file of their PST partition, with the OEM Unlocking setting enabled, and your G6 Plus would also need to be able to boot into TWRP to run the necessary ADB shell command to flash it.
And which is impossible, since (due to your locked bootloader) you can't either remotely boot TWRP from a laptop using fastboot boot twrp.img or flash it directly using fastboot flash recovery twrp.img
As I say, I wish I had better news for you.
-----------------------------------------
I hope all of the above makes sense; it is a little technical.
If I have any ideas that may be helpful, I'll post them here. But as it stands right now, and knowing what I know about this topic, I'm not optimistic there is a solution to your problem.
Ged.
The only other thing I can think of that may or may not work is a blankflash. Search the forums for it.
Sent from my moto g(6) plus using Tapatalk
You don't need to unlock oem as I got the same problem a year ago with my moto g5 plus so basically what I did was keep trying to flash a different fimware and eventually it worked with installed a firmware with oem locked.
Update:
____________________________
FINALLY SUCCESS!
Downgrading my ROG Phone 3 to android 10 and using the unlock too (NOT OBIWAN) and finally success! For other peoples reference, the Firmware version I used was:UL-ASUS_I003_1-ASUS-18.0823.2104.147-1.1.95-user.zip, and the unlock tool I used was AsusUnlock_1.0.0.7_210127_fulldpi(1).Zip.
Many thanks for all the assistance and suggestions!! If this thread needs to be marked in someway to show the issue was fixed, please let me know, I'm still a little new here. Thanks!
I do have one final question ( for now)
If I upgrade to android 12 via dropping the file and running the upgrade through the phone like normal, the boot loader should STAY unlocked, correct?
Original Post:
_____________________________
Alrighty! I'm average linux user with a ROG Phone 3, I'm not completely sure as to whether it's the strix edition or not - at first I didn't think so but I got the model "ASUS_I003DD" so? Not really sure what to make of it. I'm not a pro with adb but any advice and pointers that can be offered I'd really appreciate - end goal is to root the phone but I feel confident I can figure that out if I can get the bootloader unlocked... which all traditional and googled answers seem to not work.
I've tried unlocking the bootloader with both Strix and normal Asus bootloader unlock apps(links at the botttom). I even downgraded to Android 11 because I noticed that Asus had a separate tool specific for android 11 but to no avail, I run
(bashshell)~$ adb reboot-bootloader
(bashshell)~$ fastboot oem device-info
and every time it has returned:
(bashshell-output):
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Device Authorized: false
I am not sure what steps to take next. Suggestions? Advice from someone who has unlocked the rog3 before??
Strix firmware/support and app
ROG Phone 3 Strix Edition | ROG Phone 3 Strix Edition | Gaming Phones｜ROG - Republic of Gamers｜ROG Global
ROG Phone 3 Strix Edition is everything you’ve always wanted for mobile gaming! Play Cooler. Play Faster. Absolute Control.
rog.asus.com
Normal Rog3 firmware/support and app
ROG Phone 3
ROG Phone 3 sets the new standard for mobile gaming! Absolute Power. Absolute Visuals. Absolute Control.
rog.asus.com
Is the device original Global version or converted from a Chinese version that has been unlocked and then re-locked before you bought it? That may be the explanation. My guess is your device id is not being validated by the ASUS server when using the unlock tool. These devices cannot be unlocked through the conventional OEM unlock methods (unfortunately) because ASUS have removed that as an option.
I think this is not a problem since my rog and the Chinese version that was converted I used, I used Asus' own app to unlock it, I rooted everything perfect
hermam said:
I think this is not a problem since my rog and the Chinese version that was converted I used, I used Asus' own app to unlock it, I rooted everything perfect
Click to expand...
Click to collapse
What steps did you take? What firmware did you use? I’ve used both versions of android (11 & 12) and both unlock apps (for 11 and for 12) and the boot-loader remains locked. What steps did you take? What information can I relay to you to help? The most that ever happens, is unless there’s a “network error” for the app, it will reboot the phone, not reset and not unlock the phone.
Andrologic said:
Is the device original Global version or converted from a Chinese version that has been unlocked and then re-locked before you bought it? That may be the explanation. My guess is your device id is not being validated by the ASUS server when using the unlock tool. These devices cannot be unlocked through the conventional OEM unlock methods (unfortunately) because ASUS have removed that as an option.
Click to expand...
Click to collapse
What would you recommend to test if that is the situation or not? If it is, do we know how to unlock it “unconventionally”?
meisnerwest said:
What would you recommend to test if that is the situation or not? If it is, do we know how to unlock it “unconventionally”?
Click to expand...
Click to collapse
Does the ASUS unlock tool complete successfully followed by a reboot? If not that's a very good indication.
In that case, I believe a solution that I belive has worked for some folks has been to change the device fingerprint to it's original in order to pass the ASUS unlock server, then root the device and change it back to Global.
I haven't done it myself, i strictly only buy original Global version of ROG phones only for exactly reasons like this, but I believe there are posts to be found here that explains out what you need to change.
I don't know any other 'unconventional' ways of unlocking this device unfortunately.
Andrologic said:
Does the ASUS unlock tool complete successfully followed by a reboot? If not that's a very good indication.
In that case, I believe a solution that I belive has worked for some folks has been to change the device fingerprint to it's original in order to pass the ASUS unlock server, then root the device and change it back to Global.
I haven't done it myself, i strictly only buy original Global version of ROG phones only for exactly reasons like this, but I believe there are posts to be found here that explains out what you need to change.
I don't know any other 'unconventional' ways of unlocking this device unfortunately.
Click to expand...
Click to collapse
The Asus unlock tool will either (A) reboot the phone, but change nothing (nothing is reset, bootloader still locked) or (B) run a error that it complains could be a network error.
When you say "change the device fingerprint" do you mean the firmware? so if it is a China model or UK model for instance, flashing it back to that models firmware, running the unlock, and then flashing it the user's preference?
If so-> Do we have a way to tell what the appropriate firmware for the devices should be?( UK,CN, etc)
If someone does have "unconventional" methods I have LG phone I'd love to unlock at some point smh. One phone at a time! I'll troll the forums some more.
Andrologic said:
Does the ASUS unlock tool complete successfully followed by a reboot? If not that's a very good indication.
In that case, I believe a solution that I belive has worked for some folks has been to change the device fingerprint to it's original in order to pass the ASUS unlock server, then root the device and change it back to Global.
I haven't done it myself, i strictly only buy original Global version of ROG phones only for exactly reasons like this, but I believe there are posts to be found here that explains out what you need to change.
I don't know any other 'unconventional' ways of unlocking this device unfortunately.
Click to expand...
Click to collapse
By the way! I did some looking and the strix and normal edition appear to have writing on the back of the phone on the sim tray side - "strix edition" and "areodynamic '???'tek" - which my phone apears to have neither?? I have attached the photo i took as well as the photos I'm referencing. Could I get some thoughst on this? Does this help knowing where this phone came from? (CN WW TW etc)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
QUICK UPDATE: I did a little digging on this page:https://forum.xda-developers.com/t/...-ww-with-final-android-9-1910-64-raw.4002279/
and attached a screenshot of my device hardware info. From that am I to believe that the phone already has the global fingerpint and global firmware?
@meisnerwest
my phone is from tencent CN version Rog3 and it is irrelevant even if it's strix or whatever. if nothing is working for you try to downgrade to A10 , that's the firmware i had when i unlocked my bootloader using the applicatiom from their website.
if it just reboot and nothing happen try the older version of the application.
meisnerwest said:
By the way! I did some looking and the strix and normal edition appear to have writing on the back of the phone on the sim tray side - "strix edition" and "areodynamic '???'tek" - which my phone apears to have neither?? I have attached the photo i took as well as the photos I'm referencing. Could I get some thoughst on this? Does this help knowing where this phone came from? (CN WW TW etc)View attachment 5796715View attachment 5796717View attachment 5796721
View attachment 5796717
QUICK UPDATE: I did a little digging on this page:https://forum.xda-developers.com/t/...-ww-with-final-android-9-1910-64-raw.4002279/
and attached a screenshot of my device hardware info. From that am I to believe that the phone already has the global fingerpint and global firmware?
Click to expand...
Click to collapse
this is strix edition. did you manage to root your phone?
osomakohj said:
this is strix edition. did you manage to root your phone?
Click to expand...
Click to collapse
I have gotten the boot loader unlocked but I have not rooted it yet. If you have advice I'm all ears!
meisnerwest said:
I have gotten the boot loader unlocked but I have not rooted it yet. If you have advice I'm all ears!
Click to expand...
Click to collapse
we're on same boat. I've used the app you mentioned and unlock my a12 rog3. Just confuse about rooting. Does rooting active slot enough? Or should I root both slot? Because I am afraid about flashing TWRP. The root method I like to do is to patch the booting ang flash via fastboot
osomakohj said:
we're on same boat. I've used the app you mentioned and unlock my a12 rog3. Just confuse about rooting. Does rooting active slot enough? Or should I root both slot? Because I am afraid about flashing TWRP. The root method I like to do is to patch the booting ang flash via fastboot
Click to expand...
Click to collapse
Gotcha, I’ll let y’all know if I come across anything good then I’ll let y’all know what happens.
meisnerwest said:
Update:
____________________________
FINALLY SUCCESS!
Downgrading my ROG Phone 3 to android 10 and using the unlock too (NOT OBIWAN) and finally success! For other peoples reference, the Firmware version I used was:UL-ASUS_I003_1-ASUS-18.0823.2104.147-1.1.95-user.zip, and the unlock tool I used was AsusUnlock_1.0.0.7_210127_fulldpi(1).Zip.
Click to expand...
Click to collapse
Hi, this method works for me, April 10 2023
Thank you very much
Faye Reagan said:
Hi, this method works for me, April 10 2023
Thank you very much
Click to expand...
Click to collapse
Not working for me, on the same firmware and using the latest unlock tool.
Hi!
As you may know Honor is pretty restricted in modding.
I AM NOT RESPONSIBLE FOR ERRORS/BRICKED DEVICES'
THIS JUST GIVES AN IDEA ON WHAT TO DO AND IF YOU SHOULD BUY( I don't recommend for modding)
EDIT: IT SEEMS LIKE WE CANT UNLOCK THE BL
There are no recoveries yet
So we need boot.img to root with magisk
But Honor/Other websites does not provide firmware
So we need to dump firmware(which I have not done yet) to get boot.img using mtk client or unlocktool (idk if unlocktool is legit)
Then patch boot.img and flash
#YetAnotherPerson said:
Hi!
As you may know Honor is pretty restricted in modding.
I AM NOT RESPONSIBLE FOR ERRORS/BRICKED DEVICES'
THIS JUST GIVES AN IDEA ON WHAT TO DO AND IF YOU SHOULD BUY( I don't recommend for modding)
There are no recoveries yet
So we need boot.img to root with magisk
But Honor/Other websites does not provide firmware
So we need to dump firmware(which I have not done yet) to get boot.img using mtk client or unlocktool (idk if unlocktool is legit)
Then patch boot.img and flash
Click to expand...
Click to collapse
Hi! Thanks for requesting this page!
For anyone considering buying this phone, just like OP said, DON'T buy if you want to MOD it in any way!
Also, if anyone has any information on this phone, like the firmware, exploits, etc. PLEASE share it since this device is not even that known in XDA.
Sad update, I backed up my Linux computer to install windows and use many apps to retrieve stock firmware for rooting and when device gets bricked, but no success, and I installed Linux again. I did not dual boot because of storage issues
Our hope is not fully lost.
We could flash a rooted GSI.
But I just don't want to risk it as there is no way to return back to the stock firmware if something goes wrong or some features don't work(that's sometimes how GSI's are
#YetAnotherPerson said:
Our hope is not fully lost.
We could flash a rooted GSI.
But I just don't want to risk it as there is no way to return back to the stock firmware if something goes wrong or some features don't work(that's sometimes how GSI's are
Click to expand...
Click to collapse
But wouldn't we need to at least unlock the bootloader to flash anything?
JoeBro19 said:
But wouldn't we need to at least unlock the bootloader to flash anything
Click to expand...
Click to collapse
There is a bootloader unlock option in settings, developer options
#YetAnotherPerson said:
There is a bootloader unlock option in settings, developer options
Click to expand...
Click to collapse
That's only an option to allow the device to be unlocked, but it doesn't unlock it per se. That's done in fastboot mode or similar where you enter a code to unlock it, but Huawei/Honor stopped giving those codes years ago, that's why it's so difficult to do anything to these phones...
JoeBro19 said:
That's only an option to allow the device to be unlocked, but it doesn't unlock it per se. That's done in fastboot mode or similar where you enter a code to unlock it, but Huawei/Honor stopped giving those codes years ago, that's why it's so difficult to do anything to these phones...
Click to expand...
Click to collapse
Hi!
Do you know any way to check if the bootloader is unlocked other than the phone and fastboot method(those don't work for me). I think I did unlock the bootloader, here is what I did:
1. I typed "fastboot flashing unlock"
2. THAT BRICKED MY PHONE
3. I booted into recovery and did a factory reset
4. Did my usual setup again
5. I just went into settings(developer options) and the OEM unlock toggle was enabled without me touching it!
#YetAnotherPerson said:
Hi!
Do you know any way to check if the bootloader is unlocked other than the phone and fastboot method(those don't work for me). I think I did unlock the bootloader, here is what I did:
1. I typed "fastboot flashing unlock"
2. THAT BRICKED MY PHONE
3. I booted into recovery and did a factory reset
4. Did my usual setup again
5. I just went into settings(developer options) and the OEM unlock toggle was enabled without me touching it!
Click to expand...
Click to collapse
You can check by entering fastboot/bootloader mode and it'll say if the phone (bootloader) is locked or unlocked.
You can enter the bootloader by using adb and entering "adb reboot bootloader" and after you get restarted into the bootloader it'll tell you the status on the bottom of the screen.
I have that OEM unlock toggled on and as it still says "Phone Locked" in the bootloader, just as I said that toggling that option doesn't actually unlock it.
JoeBro19 said:
You can check by entering fastboot/bootloader mode and it'll say if the phone (bootloader) is locked or unlocked.
You can enter the bootloader by using adb and entering "adb reboot bootloader" and after you get restarted into the bootloader it'll tell you the status on the bottom of the screen.
I have that OEM unlock toggled on and as it still says "Phone Locked" in the bootloader, just as I said that toggling that option doesn't actually unlock it.
Click to expand...
Click to collapse
Thanks!
While I did not make any progress, atleast I found out I wasted my time "unlocking" the BL and still nothing happened. Just to confirm that the phone locked thing does change when BL in unlocked, I checked a yt video on someone flashing a GSI on an older honor device and it does say "phone unlocked" for them.
Let me explain a bit more on what happened on the BL unlock attempt:
1.I did fastboot flashing unlock in adb which should unlock the BL
2.It put me in a menu which had an option to unlock the bootloader and it did say it will void warranty
3. Then it said it was a sucess and then went into another menu asking what to do next (fastboot mode,reboot,and something else) but it glitched and clicking hw buttons did nothing so I rebooted and the device was in a bootloop so I had to reset the device using the recovery
4. In fastboot mode, it still says phone locked
In short: There is a bug preventing BL unlock. I am not sure if Honor devices still need a code to unlock the BL since you said they stopped providing them
#YetAnotherPerson said:
Thanks!
While I did not make any progress, atleast I found out I wasted my time "unlocking" the BL and still nothing happened. Just to confirm that the phone locked thing does change when BL in unlocked, I checked a yt video on someone flashing a GSI on an older honor device and it does say "phone unlocked" for them.
Let me explain a bit more on what happened on the BL unlock attempt:
1.I did fastboot flashing unlock in adb which should unlock the BL
2.It put me in a menu which had an option to unlock the bootloader and it did say it will void warranty
3. Then it said it was a sucess and then went into another menu asking what to do next (fastboot mode,reboot,and something else) but it glitched and clicking hw buttons did nothing so I rebooted and the device was in a bootloop so I had to reset the device using the recovery
4. In fastboot mode, it still says phone locked
In short: There is a bug preventing BL unlock. I am not sure if Honor devices still need a code to unlock the BL since you said they stopped providing them
Click to expand...
Click to collapse
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
JoeBro19 said:
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
Click to expand...
Click to collapse
Ok, but
JoeBro19 said:
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
Click to expand...
Click to collapse
Ok, but I'll give another warning: It's risky and may brick your device like mine and a factory reset from the recovery may be required. I am not respondible if something happens.
I did contact honor customer support but no reply yet
#YetAnotherPerson said:
Ok, but
Ok, but I'll give another warning: It's risky and may brick your device like mine and a factory reset from the recovery may be required. I am not respondible if something happens.
I did contact honor customer support but no reply yet
Click to expand...
Click to collapse
I doubt they'll anything other than "we don't provide those codes anymore"
And yeah I decided to try it anyway and it happened exactly the same as your case. I had to factory reset it to exit the boot loop. Fortunately, I did a backup just before trying it so I was able to restore it and not lose anything; but yeah, things seem to have come to a standstill.
JoeBro19 said:
I doubt they'll anything other than "we don't provide those codes anymore"
And yeah I decided to try it anyway and it happened exactly the same as your case. I had to factory reset it to exit the boot loop. Fortunately, I did a backup just before trying it so I was able to restore it and not lose anything; but yeah, things seem to have come to a standstill.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#YetAnotherPerson said:
View attachment 5902653
Click to expand...
Click to collapse
Just as I thought.... damn this companies...
So, unless some miracle happens and someone discovers an exploit on the processor or something that allows us to decipher the unlock code, there is absolutely nothing than we can do...
You can only unlock the bootloader on the new Honor at the Honor office. But this is only possible if the Honor employee is your friend.
volkodav1975 said:
You can only unlock the bootloader on the new Honor at the Honor office. The workers there have such smartphones, I have a friend among such workers and he made a request for me in a friendly way. I think that you will not see such a photo anywhere else. Alas, as long as it's useless, I need a custom one Recovery, But I don't know where to get it.
Click to expand...
Click to collapse
Well that's... disappointing... can't believe we have to even consider that. In my case, we don't have those centers, so I'm definitely screwed... good job Honor...