Related
hi all.
like so many others, Xiaomi forced update 6.1.14 on to my phone which locked the bootloader. i even thought i had stopped the phone from auto updating, but it seems i was wrong. since then, i have been put on to the latest 2 updates. i want to get off of the rom i am on but cant do anything now with the phone in the installing rom dept because regardless of whether i try to use the 'Updater' to put a Chinese dev rom on the phone or any other rom, or if i rename a rom and put it on the root of the phone, i cannot update. i always get a message saying Unable to verify rom and the phone simply stops. when trying to go into recovery mode, as i am unable to get to TWRP, i have even been locked out of that. i applied for an unlock code, but haven't received anything and with Chinese New Year fast approaching, bringing a holiday, i can see Xiaomu ignoring those who asked for a code even longer than they have. i haven't read of a single person being sent the code at all, which is very bad on Xiaomi's part.
i was really pleased with this phone. it worked well for me and did all i wanted but now i have a door stop, to all intents and purpose. such a shame as the way things have gone, i wont be buying from them again.
does anyone have any solution to this problem?
many TIA,
Prettygrim
Download stable ROM - http://bigota.d.miui.com/V7.0.16.0.LXKCNCI/miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
Update your phone to that ROM
You will lost all data and setting (/sdcard is safe)
Bootloader unlocked
Flash CM13
cowithgun said:
Download stable ROM - http://bigota.d.miui.com/V7.0.16.0.LXKCNCI/miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
Update your phone to that ROM
You will lost all data and setting (/sdcard is safe)
Bootloader unlocked
Flash CM13
Click to expand...
Click to collapse
And stay away from dev ROMs unless you have an unlock code.
hi and tnx for the replies.
to cowithgun:
unfortunately, i cannot update to that or any other rom, as i stated above. trying to do so via the 'Updater' and all i get is 'Unable to verify rom', that is after being told i must connect to the WLAN. the speed of that is almost non-existent.
if i try to do so by putting the rom in the root of the drive, renaming it 'update.zip' i again get told 'unable to verify rom'. because of the failure to be able to do anything 'conventional' was the reason i asked for help. i have even tried Kingroot and Kingoroot but both have failed.
to qtotter:
one of the methods i was asked to try was to try to use a Chinese dev rom, but i cant even get one of those on the phone (my wife is Chinese, so no language issues).
with the upcoming Chinese New Year, i can see Xiaomi using that as an excuse to delay giving out unlock codes, if it intends doing so at all. i am extremely p****d off at what they have done and in my case, they have turned a phone that i really liked into half a phone. such i stupid stunt to pull when the 'unlocked' was a feature used to actually make the phone a more attractive sale. really disappointed
should have asked guys, what method would you suggest i try to get this rom, (if the blasted phone doesn't give me the same message as before about cant verify it) installed on the phone? bear in mind i have no official recovery and obviously no TWRP.
TIA
Prettygrim said:
hi and tnx for the replies.
to cowithgun:
unfortunately, i cannot update to that or any other rom, as i stated above. trying to do so via the 'Updater' and all i get is 'Unable to verify rom', that is after being told i must connect to the WLAN. the speed of that is almost non-existent.
if i try to do so by putting the rom in the root of the drive, renaming it 'update.zip' i again get told 'unable to verify rom'. because of the failure to be able to do anything 'conventional' was the reason i asked for help. i have even tried Kingroot and Kingoroot but both have failed.
to qtotter:
one of the methods i was asked to try was to try to use a Chinese dev rom, but i cant even get one of those on the phone (my wife is Chinese, so no language issues).
with the upcoming Chinese New Year, i can see Xiaomi using that as an excuse to delay giving out unlock codes, if it intends doing so at all. i am extremely p****d off at what they have done and in my case, they have turned a phone that i really liked into half a phone. such i stupid stunt to pull when the 'unlocked' was a feature used to actually make the phone a more attractive sale. really disappointed
should have asked guys, what method would you suggest i try to get this rom, (if the blasted phone doesn't give me the same message as before about cant verify it) installed on the phone? bear in mind i have no official recovery and obviously no TWRP.
TIA
Click to expand...
Click to collapse
I tested it myself, it should work. More precisely, I did this:
1. Download this into your computer: http://bigota.d.miui.com/V7.0.16.0.LXKCNCI/miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
2. Connect phone to computer via USB, copy the zip into your phone, say /sdcard/downloaded_rom/miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
3. Start Updater, press the "..." on upper right and select "Choose update package", select the ROM.
4. Installing older developer ROM will causes the error you mentioned, but if you have 6.1.14, installing stable 7.0.16 is OK and tested working. Not sure what is changed but if it still wont work, try the latest 7.1.6 stable instead.
5. It will warn you of losing setting. Please YES.
6. When it's done, you will have a MIUI ROM but bootloader no longer lock.
7. Install CM13 as soon as you can!
Sounds like the problem is your recovery. You said you have no official recovery.
Sent from my Mi-4c using Tapatalk
just tried it and no luck, i'm afraid. still getting the message 'Cant verify update'. also tried moving the file to root of phone, renaming it to 'update.zip' and still no luck, still getting the same message. it seems that the phone is well and truly locked down so it wont even take one of Xiaomi's own official updates, unless it is a progression from the present rom. that in my view is well over the top!!
tnx for trying and if you or anyone has another idea, please let me know. it appears that the thing to turn off is the verification of the rom. is that possible, and if so, how?
one thing i have noticed in the settings -->developer options is 'verify apps over USB. could this be anything to do with the rom verification failure? the txt for that is greyed out with the button on (redish) but i cant see how to change the setting. worth a try maybe? anyone know how to change it?
Ulver said:
Sounds like the problem is your recovery. You said you have no official recovery.
Sent from my Mi-4c using Tapatalk
Click to expand...
Click to collapse
you may well be right, but if that's the case, it was done by Xiaomi. is there a way of getting it to work? how do i actually check it isn't working? as stated before, when 'booting into recovery', i get an image of the phone on screen with the USB cable either connected or disconnected, depending on the actual state and nothing else happens. i have to do a reboot holding the start button to achieve this
Prettygrim said:
bear in mind i have no official recovery and obviously no TWRP.
Click to expand...
Click to collapse
I'm still waiting for my mi4c to come from China, and this is the reason why I'm gonna flash the latest (unlocked) official "stable" ROM first only to update the recovery and radio partitions right after I receive the phone. Resellers in China sometimes put their custom ROMs, recovery images or malware in the phones.
I don't think I'd flash twrp right away. I'd install cm12.1 or cm13 by "fastboot boot recovery.img" leaving the official recovery left in the phone so that I could go back to the official ROMs in the official way, and confirm if everything works as expected before flashing twrp.
What I don't understand is why people flash the dev (locked) ROMs as they are downloaded. What they need is just boot.img and /system, isn't it?? I'd replace "firmware-update" folder, where bootloader, radio and recovery images are located, in the dev ROM with the one from the stable ROM if I wanna try dev ROMs. Or I'd replace boot.img and system.* in the stable ROM with the ones in the dev ROM. Those modded ROMs should be able to be flashed with twrp...
the main reason for using the Chinese dev roms is because they are supposed to bee already rooted. once any of these roms is on the phone, according to what else i read, any rom going over the top would keep root. personally, i didn't find any rom that had root already and had to root my phone, following instructions i found on the MIUI and other sites. the built in recovery on my phone does nothing.
i had issues with TWRP when first using it, but put that down to being a novice. i found the files needed and the procedure to get out of the constant TWRP loop, which meant the phone was basically soft bricked and all was good. however, even that method fails now with the message something like 'phone is locked, cannot continue.
i have put an official complaint into Xiaomi about the bootloader locking and also about the time being taken to issue unlock codes, which is much longer than 3-21 days in some cases.
if i get anywhere, i'll post what i'm told
Since the latest miui ROMs are all based on Android 5.1.1, it's really easy to root mi4c yourself even on official standard ROMs. You don't have to flash dev ROMs or flash custom recovery like twrp. You can just run twrp on the fly like "fastboot boot twrp.img" to flash SuperSU.zip as long as bootloader is unlocked.
I'd say it's more dangerous to flash dev ROMs only for rooting especially if it's for your wife, not for yourself... Dev ROMs are for people who want to try new functions and designs still under development.
Anyway, I hope you will get an unlock SMS from xiaomi soon!
Had same Problem
search for miui_MI4c_V7.1.6.0.LXKCNCK_1debc127a9_5.1.zip
Hope it helps
So if the bootloader is locked, you can unlock it by flashing an older dev rom?
ermacwins said:
So if the bootloader is locked, you can unlock it by flashing an older dev rom?
Click to expand...
Click to collapse
No. Older Developer ROM will not work. Updater will refuse to update it. I tested a few of them back then, only by flashing the latest stable ROM back then (7.0.16) work.
cowithgun said:
No. Older Developer ROM will not work. Updater will refuse to update it. I tested a few of them back then, only by flashing the latest stable ROM back then (7.0.16) work.
Click to expand...
Click to collapse
And now flash the lastest developer and try roll back one o two a time (this work for my with the original recovery) and later use one rom from xiaomi.eu that one has not locked bootloader .
Sorry for my bad english.
i'm probably being real thick here guys. please bear with me. i am, as i said before, new to all this stuff with phones.
remember too that i have an unlocked bootloader now, courtesy of Xiaomi.
so, just to be clear, i am using miui_MI4c_5.12.31_5d6537a0b8_5.1.zip. to remove the possibility of Xiaomi doing something else to the phone that i dont want, i would like to get on to the xiaomi.eu_multi_libra roms. how do i go about doing this in idiot-proof steps, please? also, if i manage to achieve what i want, how do i stop the phone taking official updates? there must be a setting in the phone somewhere that can be disabled and prevent it updating to what i dont want. i found the one in the 'updater settings' but am of the opinion there is another somewhere that i cant find.
hope someone will be gentle with me
TIA
If you're already on Xiaomi.EU ROMs, you won't get OTA updates directly from Xiaomi that will lock your bootloader.
Sent from my Mi-4c using Tapatalk
i am on
miui_MI4c_5.12.31_5d6537a0b8_5.1.zip
which is an official rom, i believe. hence the questions in my former posts. i want to get on to the libre eu roms but am unsure how to go about it. i have read about using various roms first but i believe doing so is under certain circumstances, ie, bootloader locked, phone not rooted. my phone has the bootloader unlocked now by Xiaomi and i have rooted the phone. this is where my confusion comes in that i was hoping someone could clarify
You have unlock permission from xiaomi now, which means you don't need to worry about updates. You can unlock your phone again anytime you want. It's not one time only thing.
well that's a relief! tnx, qtotter! i didn't want to have to go through all this again, just because the maker decided i hadn't actually bought the phone, i had just bought permission to use it, as long as it was how he wanted me to use it!
bloody USA judge who decided that must have been paid a small fortune to rule in favour of this! just what the entertainment industries and others wanted!! didn't care what the implications were or ow the industries would take the p**s out of customers!!
I'm new to the XDA Forums and even forums in general so if I speak out of place or anything like that I apologize ahead of time. So anyway, where do I start? I'll try to give you the short version. So I bought an LG Stylo 2(model: LG K540) through Cricket the day they came out. It was $170 phone. On the second day of using my new phone I got the bright idea that I'd try and root it BY MYSELF. I knew better but for some reason I had this false burst of confidence & thought I had everything under control. Well, thanks to Kingroot that burst of confidence didn't last long and there I was with a 2 day old phone BRICKED. Reason I never posted on the forums is because I've got a buddy who , in my eyes, knows everything there is to know about Android and thats who I'd normally go to when I wanted to root a phone so he's who I immediately turned to but even he couldn't figure it out. He couldn't help me unless we had the stock firmware or someone with the exact same phone and according to him we could some how use a backup of that phone to fix mine. Cricket just wanted to sell me another phone even though I was standing there with a 2 day old phone and LG just wants me to send the phone in to them, which I have no desire to do. I've searched all over the internet trying to locate the firmware because even I can fix the phone if I had that but nothing. Had hoped by now LG would have released the firmware but at this point who knows when that'll happen. I'd even pay for it at this point. Anyway, just thought I'd give the forum a shot on the off chance someone might be able to help me or point me in the right direction. Oh and if you were wondering what the phone does now, when I turn it on the LG logo appears like it should but then right as it appears you see a message in red lettering that says: BOOT VERIFICATION FAIL!!- CAUSE: MISMATCH_SIG_LEN And it just loops this over & over until you pull the battery out. Please someone help me!
send to lg said stop working no luck with tihs hard brick
Source code to rom¿?
I ran into basically the same situation as you. I'm currently downloading Android open source project on to a fresh install Ubuntu 16.04. I am currently in the middle of running sync.
I'm curious if there is anybody out there who would be willing to give a few pointers, on compiling the ROM from LG open source code. They told me I had to use it in the readme.txt.
Im a noob with fair knowledge of modding and stylo not stylo 2. There's no way to say for sure if this will work but on lg mm on h631 u need to unlock dev option in settings 1st. Make sure to check off oem unlock and usb debugging. Connect to pc and you will get a popup or 2, one will ask to allow pc to connect to phone, the second is to allow usb debugging. After you allow both, open cmd in your adb fastboot folder. Type " adb reboot bootloader." should reboot the phone to bootloader/fastboot mode. Then you type " fastboot oem unlock." you will see sending.. Once sending is done type " fastboot reboot." when the phone restart you should see bootloader unlocked on splash screen. Then i rooted with kingroot. Then use rashr to flash twrp. Then used twrp to flash supersu to get rid of kingroot.. My h631 now in business and i just started working on a port for lg ux 5.0. This is the guild i use for a better idea http://forum.xda-developers.com/lg-g-stylo/how-to/guide-lg-g-stylo-how-to-root-t-mobile-6-t3333916. You might need lgflashtool and kdz to unbrick..
NO NEED to beg.
I don't know very much but I know $$$ talks and since no one save the few who suggested contacting lg wants to help, Ill try. At the moment I am efforting a solution via the Chinese. I expect to have a working copy in the next 48hrs. when I do, we can arrange for you to get access to the mega.nz cloud and get urs.
say a prayer......
Francis
Hello Sir, I ran into same problem trying to root. If you can, can you please send me a link so that i can use my phone again. Thank You it will be greatly appreciated
can some one help me. i cannot use adb to unbrick
Please send me the link
facorbin said:
I don't know very much but I know $$$ talks and since no one save the few who suggested contacting lg wants to help, Ill try. At the moment I am efforting a solution via the Chinese. I expect to have a working copy in the next 48hrs. when I do, we can arrange for you to get access to the mega.nz cloud and get urs.
say a prayer......
Francis
Click to expand...
Click to collapse
Hi, can you please send me the link? I need it bad thx
if you cant boot into dlmode then your hard bricked, so find a way to get back to dl mode/recovery
BIN File
Hello, I have a Stylo 2 K540 from cricket, it is having issues with the Wi-Fi, it will not connect to either Wi-Fi or bluetooth, MAC address was set at 02:00:00:00:00 or something like that, I opened the phone and it has humidity sensor active, cleaned the affected area but it seems like it was useless, eventhough I was pretty sure that was not the main problem. I looked for some troubleshooting options and found non of use, firmware is sold for $30 online so it is not an option since I am not certain loading firmware will be of any help. I tried repairing MAC address via Octoplus using other addresses but was useless as well.
I have little to no experience with software on phones, but I like to read and learn. I decided to connect the phone to the computer and "Read full flash" on Octopus, I have created the Bin file, I have a perfectly working phone as well, I was wondering if there is any way to get the KDZ file from the Bin file doing some sort of conversion, or if I could do some sort of fix or workaround with this bin file, I can share it if anybody needs it or if it can be of any use to get the firmware
estebangtz said:
Hello, I have a Stylo 2 K540 from cricket, it is having issues with the Wi-Fi, it will not connect to either Wi-Fi or bluetooth, MAC address was set at 02:00:00:00:00 or something like that, I opened the phone and it has humidity sensor active, cleaned the affected area but it seems like it was useless, eventhough I was pretty sure that was not the main problem. I looked for some troubleshooting options and found non of use, firmware is sold for $30 online so it is not an option since I am not certain loading firmware will be of any help. I tried repairing MAC address via Octoplus using other addresses but was useless as well.
I have little to no experience with software on phones, but I like to read and learn. I decided to connect the phone to the computer and "Read full flash" on Octopus, I have created the Bin file, I have a perfectly working phone as well, I was wondering if there is any way to get the KDZ file from the Bin file doing some sort of conversion, or if I could do some sort of fix or workaround with this bin file, I can share it if anybody needs it or if it can be of any use to get the firmware
Click to expand...
Click to collapse
cna you possible sned me it I might be able too
no longer have the bin file
HERPDERP202 said:
cna you possible sned me it I might be able too
Click to expand...
Click to collapse
I am sad to say my computer stopped working and just got it back today, all my information was lost so I no longer have the bin file
bsimpson1858 said:
I'm new to the XDA Forums and even forums in general so if I speak out of place or anything like that I apologize ahead of time. So anyway, where do I start? I'll try to give you the short version. So I bought an LG Stylo 2(model: LG K540) through Cricket the day they came out. It was $170 phone. On the second day of using my new phone I got the bright idea that I'd try and root it BY MYSELF. I knew better but for some reason I had this false burst of confidence & thought I had everything under control. Well, thanks to Kingroot that burst of confidence didn't last long and there I was with a 2 day old phone BRICKED. Reason I never posted on the forums is because I've got a buddy who , in my eyes, knows everything there is to know about Android and thats who I'd normally go to when I wanted to root a phone so he's who I immediately turned to but even he couldn't figure it out. He couldn't help me unless we had the stock firmware or someone with the exact same phone and according to him we could some how use a backup of that phone to fix mine. Cricket just wanted to sell me another phone even though I was standing there with a 2 day old phone and LG just wants me to send the phone in to them, which I have no desire to do. I've searched all over the internet trying to locate the firmware because even I can fix the phone if I had that but nothing. Had hoped by now LG would have released the firmware but at this point who knows when that'll happen. I'd even pay for it at this point. Anyway, just thought I'd give the forum a shot on the off chance someone might be able to help me or point me in the right direction. Oh and if you were wondering what the phone does now, when I turn it on the LG logo appears like it should but then right as it appears you see a message in red lettering that says: BOOT VERIFICATION FAIL!!- CAUSE: MISMATCH_SIG_LEN And it just loops this over & over until you pull the battery out. Please someone help me!
Click to expand...
Click to collapse
you can go into download mode by pressing volume up key and inserting usb cable .press the volume up until you see download mode a firmware readed by z3x box is available on clamgsm forum you can flash it with z3x box crack .
Hello Guys,
i had bought an Huawei P20 about an year ago. Now you know with all of this "USA-Huawei" Trouble going on, the thought came to my mind that i better start unlocking bootloader and be prepared to flash custom rom if worst come to worst. so far, so good.
now i started looking around if there is an easy method of getting the bootloader unlocked. but oh my, the huawei company is very friendly to us users and say "no, you wont get any unlock code from us anymore". so screw that.
now i want to try some experimental stuff. it looks like this:
my Smartphone has currently the version EML-L29 8.1.0.168(C432). I bought some Credits (i think it is that thing for $4) from DC-Unlocker. Yeah yeah i know, there they say "no support for Huawei P20!!!". But i still want to try. Well i tried, but it doesnt work - what you should expect.
now i read from some other website that there is another way of unlocking it. i only read it diagonal but the one thing i read was the information "unlocking bootloader is only possible till firmware version june 2018". so i jumped to an maaybe interesting conclusion about unlocking the phone with DC-Unlocker or HCU (whatever, i guess maybe both use the same method anyway).
if i do an rollback to the old firmware version *before* June 2018 on the device, wouldnt it be possible to do the unlock? Because the security patches that preventing it unlocked arent on the device then.
So what i have done so far is loading the old firmware version 8.1.0.128(C432). But the source is saying that it is coming from "Asia" but in the next line it reads "Asia, Europe" etc. - do they mean that this version is universal or do i run in trouble if i install one that is having the wrong area?
the next thing that kinda baffles me... all guides are sayin "copy the extracted dload folder to your sd-card". even the p20 guides do that. but.. well you know, the p20 device doesnt even have sd-card support. so how are you intended to use it then? i wonder about that a bit.
i dont think that without unlocked bootloader, flashing an original OTA full update would be impossible. but im not really sure how. there is this shady menu you can reach if you call this strange numbercode. but im very unsure if that will really work out. the phone (it is still a phone without SD-Card-Support) even has the option "apply update from sd-card". so im wondering how this feature they implemented in the original software is intended to use at all. maybe i should push the dload folder on the internal storage? i dunno.
i read about another possibilty of flashing stock roms. they say you can do it per adb command. so no problems would be here, i have adb and the hisuite and all already set. but i have absolutely no idea if that is possible without unlocked bootloader. so the questions arose from my mind are those:
- does an stock rom image from possibly/maybe asia would do any harm to my device like it is getting unbootable or anything like that?
- is it possible to flash an image older android stock rom with methods like this special menu on the device or the adb load?
- do you all think that my plan of downgrading the phone in order to get the bootloader code would work?
i'm looking very forward to your answers )
no_monday said:
Bootloader Unlocking through Downgrade possible?
Click to expand...
Click to collapse
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.
Jan Philipp said:
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.
Click to expand...
Click to collapse
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.
no_monday said:
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.
Click to expand...
Click to collapse
It seems you have a couple of questions, pal, I answered to the first one (Bootloader Unlocking through Downgrade possible?). All I said is that it's impossible to unlock the bootloader through a downgrade. If you read all the how-to's you should have noticed that FirmwareFinder doesn'st work anymore since EMUI 9.0. This Information simply means Huawei doesn't allow us to flash updates on our own anymore like we did before. For sure there are some guides how to rollback to Android 8 but even this changes nothing to the bootloader.
Sadly I have no answer to the other questions about the strange behavior, it sounds pretty odd. Never heared something like this. But good luck fixing your phone anyway.
well i found out a couple of things now.
first thing: you know the service menu when you try to apply a zip archive from sd card? well you wont be able to use it UNTIL you use an usb-otg cable and an exFat formatted USB-Stick. Next thing to know is, you have to use the right images. there seem to be an kind of rule how this images are supposed to be and the image i found was from an russian firmware download site it was linked here in the forum in a thread. so i did choose "apply zip from sdcard" and .. IT DOES! the device rebooted, the stick flashed and the flashing process occured! and guys, im back to Version EML-L29 8.1.0.128(C432)! it is clearly stated in the build version view in settings. so.. i guess you *can* roll back even without firmware updater.
so far so good. but lets get back to the problem with the Bootloader. sadly Jan Philipp was totally right.. the bootloader cant be unlocked even in this version with the security patch of 5. may 2018. that is kinda sad. even kingoroot is still no different from before. i guess i have to search now for an way to get the system rooted. however, it must be easier on an earlier security update stage like now instead of the future versions of emui 8.1.
edit: another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).
"unlocking bootloader with exploit is only possible till firmware version june/july 2018" does not apply to 2018's devices with kirin970, kirin980 & kirin710.
You are with kirin970.
So to unlock your kirin970, the only way for now is to wait for 3rd party seller to hypotheticaly start back their dervice:
- In the last 6 months there was only 2 'windows' which lasted 3 or 4 days where you could order your bootloader's unlock code by imei (from 5 to 124 us$).
GuestD0711 said:
another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).
Click to expand...
Click to collapse
Google Play services require all permissions, otherwise won't work.
I also been searching on how to unlock the bootloader and found no solution or hope. I guess we are stuck with EMUI forever.
Reply from Huawei:
You can roll back to earlier versions of EMUI software, but you have to roll back one version at a time. However, our earlier phones operate exclusively on Google Mobile Services so removing it would limit the functionality extremely, however, we do have a range of new devices that no longer rely on Google Mobile Services and use Huawei Mobile Services instead - such as our P40 series.
Here are the instructions for rolling back software:
[Rollback Guideline] EMUI 9.1 (Android 9) Rollback to EMUI 9.0 (Android 9) Operation Instruction
EMUI 9.1 (Android 9) can now be rolled back to the official version of EMUI 9.0 (Android 9) using HiSuite, without downloading any intermediate packages. To ensure that the rollback succeeds, read the instructions carefully and perform the steps as instructed.
1. The following are precautions for roll-back.
a. Rolling back to an earlier version will erase all data on your device. Use an SD card, computer, or Cloud storage to back up all important data before rolling back your phone, and make sure all backed up content is complete and effective.
b. Use a computer running a Windows operating system to visit http://consumer.huawei.com/minisite/HiSuite_en/index.html and download the latest version of HiSuite. If HiSuite is installed on your computer, click the version number in the lower left corner of the page to check if it is the latest version. Make sure HiSuite version is 9.1.0.303 _OVE or above.
c. Before rolling back the phone, make sure your phone has not been upgraded using non-official updates. Otherwise, the roll-back may fail and unknown issues may be introduced. If you have used non-official packages to upgrade your phone, it is recommended that you go to an after-sales service center to roll back your phone.
d. Before rolling back your phone, make sure that your phone system has not been unlocked or rooted. If the system has been unlocked or rooted, it is recommended that you go to an after-sales service center to roll back your phone.
e. Before the roll-back, restore the phone to factory settings to make sure there is enough storage space.
f. Make sure the battery level is more than 50%.
Hi All,
I need assistance to update my EML L29 Huawei P20 phone.
The phone is Locked and FRP Lock
Issue the phone is always booting into recovery mode and not into the main screen.
I tired flashing via CMD using twrp.img file but its not writing.
Need help
Hi Everyone,
Living in Japan, we have no official channel to purchase a OnePlus handset here.
Really wanted to get a OnePlus 7 Pro as I felt it is the best model on the market as of today.
Knowing that, I got mine on Amazon Japan from a HK online shop which had very good reputation.
Now, the problem is these phones always come already opened as they say they need to confirm operation before sending it.
I have been reading news and article about this where we see more third party companies flash their roms with malware/ransomeware already built in...
In these situation, the best way to clean the phone is to do a full re-install of the OS.
I did review a bunch of article on XDA and it seems that now, due to the A/B partition setup, we can't just use official OnePlus image to load from the fastboot easily.
We have to rely on community provided too and stock rom to be able to do so....
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Sorry if I sound paranoid. Ideally, I understand the best thing to do was to buy directly from Oneplus and work a way to have it shipped to Japan but thought it would be interesting for me to learn more about android.
With previous Oneplus, it was easier as they were provided this type of official file for recovery but they stopped...
Thank you again for your time and hopping to learn more about how new android setup works.
Is the bootloader locked? Is Widevine (Netflix HD) certification still there? You can check these things to see if the phone has been tampered with.
brissoukun said:
Hi Everyone,
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Thank you again for your time and hopping to learn more about how new android setup works.
Click to expand...
Click to collapse
Good questions. Before you start, check the model number of your device through Settings > About. I'm assuming it's the international/global/unlocked version (GM1917).
With regard to question 1, a full build downloaded from the link you provided should contain every part of the OS, and flashing it through local update should overwrite anything that was there before. Before flashing, I would perform a full data wipe through recovery like you mentioned.
Q2: There is an MSM tool that will completely flash a system image for the OP7 Pro. I don't think they're generally intended for public use but they always get leaked anyways. They write an image (in the case of OnePlus, a .ops file) to the phone using a PC and USB connection. Here is a link to a thread which contains the MSM tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Download the tool for the model of your phone (probably the international, firmware GM21AA), and extract its contents into a directory. In order for the tool to work, you need the OnePlus USB drivers installed on your PC. Plug the phone into your PC with it on, and enable USB file transfer. Open File Explorer and you should see a drive labeled "OnePlus drivers" or similar. Open it and run the driver setup executable file. You'll also need ADB to make your phone reboot into a mode that will allow the tool to perform its tasks. Here is a guide to installing ADB:
https://www.xda-developers.com/what-is-adb/
Once you've set that up, make sure the phone is plugged into the PC and the MSM tool is open. Make the phone boot into edl mode by typing
Code:
adb reboot edl
and once it says Connected next to a COM port in the tool, press start. Don't interrupt the process until it completes the download and the status message turns green. The phone should automatically reboot. This method is arguably more risky than using the local upgrade option, so do it at your own risk.
Q3: Make sure that OEM unlocking is turned off in developer settings and that the bootloader is locked (if the bootloader is unlocked, you'll see a yellow warning message after you power on the device from a power off state). Without an unlocked bootloader it would be pretty difficult to make any deep modifications to the device.
Hi @Zocker1304 and @TManchu,
Please let me thank you very much first for your kind and detailed reply, this is really welcome.
@Zocker1304:
I checked using the ADB/Fastboot connection that indeed, the Bootloader is locked so, that looks good.
Also installed (using a separate Google account) DRM Info app to confirm that the Widevine is properly installed and at L1 level which indeed again, looks good.
@TManchu
Thank you again for your very detailed reply! This was exactly what I needed as information.
I did already exactly as mentioned for the #1 so, it looks I should be good now with a proper rom from OnePlus (and did a full wipe in the Recovery boot mode)
For #2, I think I will skip that since as you rightly said, with #1, it should be fine so, prefer to keep with the recommended step.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
brissoukun said:
.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
Click to expand...
Click to collapse
No problem! I’ve just done some reading and from what I understand, re-locking the bootloader on anything other than a completely stock ROM will result in a bricked phone. I believe this is due to the way Android handles data encryption. If what you’ve heard is true, being able to lock your bootloader on a custom ROM would be great for device security. However, should something go wrong with the ROM having a locked bootloader might make it more difficult to fix.
I know that there are ways to sign system and boot images so that you can lock the bootloader with them installed, but I think that would still show a warning though I'm not sure.
Anyways, if all the build dates and numbers in the system info are correct, the firmware should be stock and as long as the bootloader is locked too, I don't believe you can tamper with that.
Hi Gents,
Thank you very much for the answer to the thread and much appreciated.
Apologies for not getting back to you all earlier as yesterday was family day...haha!
Well, since things looked good on the OS and the build, I went ahead and started to use the phone properly setting up my accounts. It did give me some incentive to get all my sensitive accounts setup with 2FA so that in case I get hacked with my passwords in the future...they would still need the 2fa (using Google Authenticator).
I did check also all system apps/running process and didn't see anything shady.
Just for reference, here were the type of articles I was refering too for the OS being plagued with malware even out of the box:
Page_theverge.com/2019/6/6/18655755/google-android-malware-triada-ota-rom-ads-spam-oem (sorry gents, new account, cannot put links yet)
However here, it seems it is due to lax review from the maker to third party tools which were including malware...
To have the same level on the oneplus I bought from the HK shop, they would have needed access to OnePlus Dev team to inject the malware in official image (knowing anyway I have re-installed a new image from the local update).
Otherwise, I was reading on the web about the fact to relock the bootloader with a custom roam and there seems to have a lot of messages but not concrete steps. It seems it depends a lot on phone model and brand.
When you are checking
Page_gizmochina.com/2019/06/10/relock-bootloader-oneplus-7-pro/
This is where you can read at the end:
"The above method only works if OnePlus 7 Pro is running on stock recovery and stock firmware. The ability to relock devices running custom recovery is expected in the next few weeks. "
That was published last month so, not sure if they got this to work on the OnePlus 7 pro yet.
So that's it, I am now using my new device which looks to work great and hopefully, won't get any bugs down the road.
I appreciate you taking the time to get back to me and will continue to learn about android.:good:
Hey there! I'm new around here and I'm not sure if this has been asked before... I found this thread but there are a couple differences between our cases and none of the solutions given in the comments seem to work:
"The system has been destroyed" Poco X3 NFC
So here's the thing -- I've been using this phone for a few months as a replacement for an iPhone. I used to be in the custom ROM scene back in 2015-2016 with an old Huawei I had, so I more or less know how all of this works. Since MIUI is visually horrible (in my opinion) I decided to try my luck at installing PixelExperience (great ROM, btw!). Since I've recovered my previous phone, this one has been sitting in a drawer for a couple months already, so I wanted to restore it to factory settings and sell it.
Aaaaand this is where **** happened. I had this weird intrusive thought of using "fastboot oem lock" before doing anything else just to see what would happen. The result? The phone is now bricked. I can access fastbook but that's about it, trying to boot into the system or recovery just gives me a "The system had been destroyed - Press power button to shutdown".
I know you can fix this by unlocking it again, but every tool I find online is meant for Windows and there are barely any solutions for macOS. I have found two of them: XiaoMiTool V2 (but needs adb to be enabled) and XiaomiADBFastbootTools, which seems to kind of work.
It detects the device when put in fastboot mode, but when clicking on "OEM Unlock" it just says "Token Verify Failed, reboot the device" (screenshot attached).
Trying to unlock it from the Terminal does pretty much the same thing (obviously).
Before you ask - Yes, I have all the required drivers installed as this is the exact same computer that I used to unlock the bootloader and flash OFRP. Everything works normally, it's just that I don't have access to the OEM unlock tokens to do it directly from the Terminal the same way I used to do it with previous phones.
So uhh... What can I do? Is it going to stay this way forever? Are there any solutions for macOS users that don't require having to use BootCamp or VM? I don't mind doing it but I'd rather have it as the very last resort, since it's too much of a hassle to do it. I have Xubuntu installed on my secondary drive, so if there is anything that could work on Linux, I'll take it too.
Thank you all for your help!
Edit 1: By the way! If this gets solved, could anyone be kind enough to guide me through the steps on how to mark it as [SOLVED] and close the thread? I'm really really bad at forums.
To the best of my knowledge, MIUI tools check online if the device is currently associated with a MI account -- and in case it isn't, nothing else goes...
My guess would be to try to run MiFlash with its last fastboot stock ROM in a Windows VM.
In case that doesn't work, taking it to Xiaomi tech support would be the best bet...
pnin said:
To the best of my knowledge, MIUI tools check online if the device is currently associated with a MI account -- and in case it isn't, nothing else goes...
My guess would be to try to run MiFlash with its last fastboot stock ROM in a Windows VM.
In case that doesn't work, taking it to Xiaomi tech support would be the best bet...
Click to expand...
Click to collapse
Thanks for taking your time to answer! I'll just have to install Windows in an external disk and see how it goes
I'm guessing MiFlash works offline, without checking anything about the phone on their servers, right?
kakuluva said:
I'm guessing MiFlash works offline, without checking anything about the phone on their servers, right?
Click to expand...
Click to collapse
I'm not really sure about that (haven't done it myself), but it has been the general recommendation here when faced with serious trouble so I would expect so. YMMV, though.