Related
Ive had this problem for ages and tried everything i can think of. hopefully by now someone has experienced the same problem and solved it.
*My phone is stuck on honor boot logo
*i can access e-recovery
*i can access stock recovery
*i can access fastboot and device is recognised on my laptop
* i can wipe cache and factory reset successully and have done many times
*i can and have used the dload (3 button method) to flash stock rom successfully
Now the problem is that although i have flashed the earliest stock rom NEM-L51C432B102 it fails saying incorrect package!!!i think this is because my phone came with B103 or B104 and you can only flash from what your phone originally had and up.
I have flashed NEM-L51C432b120 and also NEM-L51C432b130 and although it says successful it reboots and remains stuck on honor boot logo!
I have entered fastboot and i can issue commands but they all fail saying REMOTE COMMAND NOT ALLOWED.
I can't use ADB because it doesn't recognise my device. Obviously ADB and FASTBOOT wont work because i can't access developper options and select enable USB debugging or OEM Unlock because the phone is stuck on honor boot logo.
Also my bootloader must be locked. I have the unlock code but i can't issue the command FASTBOOT OEM UNLOCK XXXXXXXXXXXXXXX because as mentioned before it says FAILED REMOTE COMMAND NOT ALLOWED.
I have even tried flashing rollback packages(there isnt one for NEM-L51)for other models, followed by flashing stock rom for my model device.
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
iantechie1979 said:
Ive had this problem for ages and tried everything i can think of. hopefully by now someone has experienced the same problem and solved it.
*My phone is stuck on honor boot logo
*i can access e-recovery
*i can access stock recovery
*i can access fastboot and device is recognised on my laptop
* i can wipe cache and factory reset successully and have done many times
*i can and have used the dload (3 button method) to flash stock rom successfully
Now the problem is that although i have flashed the earliest stock rom NEM-L51C432B102 it fails saying incorrect package!!!i think this is because my phone came with B103 or B104 and you can only flash from what your phone originally had and up.
I have flashed NEM-L51C432b120 and also NEM-L51C432b130 and although it says successful it reboots and remains stuck on honor boot logo!
I have entered fastboot and i can issue commands but they all fail saying REMOTE COMMAND NOT ALLOWED.
I can't use ADB because it doesn't recognise my device. Obviously ADB and FASTBOOT wont work because i can't access developper options and select enable USB debugging or OEM Unlock because the phone is stuck on honor boot logo.
Also my bootloader must be locked. I have the unlock code but i can't issue the command FASTBOOT OEM UNLOCK XXXXXXXXXXXXXXX because as mentioned before it says FAILED REMOTE COMMAND NOT ALLOWED.
I have even tried flashing rollback packages(there isnt one for NEM-L51)for other models, followed by flashing stock rom for my model device.
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
Click to expand...
Click to collapse
Oh well. Seriously this is the same issue my frn asked me to help. This is soo serious that we can only unbrick through update.app or else service center. Since u said dload method works but stucks device on bootlogo. U need to visit service center if under Warranty
iantechie1979 said:
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
Click to expand...
Click to collapse
Flash these files and it should, most probably, be fine.
use dload method as given here- https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240
as there are many different opinions on this method of using only update.app file but thats not true and it should be all the files.
Main file - http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1165/g104/v71812/f1/full/update.zip
Data file- http://update.hicloud.com:8180/TDS/...1812/f1/full/hw/eu/update_data_full_hw_eu.zip
Flash both the files in order. 1st file will restore your system but then you need to have 2nd file so that apps are installed and all working fine.
After 1st file, it may reboot on its own and stuck on honor logo, reboot to recovery and then do factory reset, it will be fine.
Then let it boot to set up. Dont set your phone. Shutdown and flash the 2nd file.
boot and set up.
Good luck. Please provide feedback once done. In case of further issue, let me know and will dig more into this.
Oh this is hard.
chrisleLP said:
Oh this is hard.
Click to expand...
Click to collapse
What is hard?
shashank1320 said:
What is hard?
Click to expand...
Click to collapse
This problem.
chrisleLP said:
This problem.
Click to expand...
Click to collapse
you cant follow simple instructions? you shouldnt be on this forum if youre not ready to lose data or brick your device.
Thanks for your input so far people. Much appreciated. @shashank1320 I am downloading the files you suggested and will flash them exactly according to your instructions. I will get back to you in a couple of days with the result. Fingers crossed.
gopinaidu77 said:
Oh well. Seriously this is the same issue my frn asked me to help. This is soo serious that we can only unbrick through update.app or else service center. Since u said dload method works but stucks device on bootlogo. U need to visit service center if under Warranty
Click to expand...
Click to collapse
Unfortunately my warranty has expired. The annoying thing is that if i had sent my device off six months ago when this first happened it would still be under warranty but in the UK there is only 1 service center, yes 1, and its hundreds of miles away! So i figured i could solve it myself. You live and learn.
Hey there everyone. I still havent managed to solve the issue with my device and its not through lack of trying. I have re downloaded all of the stock firmwares that you can possibly find on the internet. I also found one ive necer seen before. Its a full service repair b355. Fingers crossed, a miracle might happen and it will just boot up like when i first bought it. to begin with tho, i'm going to start with b102 and work through them b120, b130 ,b130rollback ,b350(beta), b350, b355 and then the b355 full service repair! I also got a couple of rollback packages(around 80mb) if all else fails.
I know, i'm nuts!! Finally before i admit defeat i'm going to part with £15 to buy credits for the dc-unlocker and dcPhoenx programs. From what ive read it has a good chance of solving it. I've taken soooo long before considering this option because i think its wrong that someone(s) is making loads of money from this. Why havent huawei/honor included a similar program in hi-suite. Anyway ive gone off on a tangent.
One last question though. Strangely enough i only just thought of it recently....
Is it a necessity to have your sim card in the tray as well as the sd-card????? All this time i havent had a sim in the phone as its in a crappy old one so i can still communicate with the world!!!!
Thank you to everyone for taking your time to read this. I hope a solution is possible.
iantechie1979 said:
Hey there everyone. I still havent managed to solve the issue with my device and its not through lack of trying. I have re downloaded all of the stock firmwares that you can possibly find on the internet. I also found one ive necer seen before. Its a full service repair b355. Fingers crossed, a miracle might happen and it will just boot up like when i first bought it. to begin with tho, i'm going to start with b102 and work through them b120, b130 ,b130rollback ,b350(beta), b350, b355 and then the b355 full service repair! I also got a couple of rollback packages(around 80mb) if all else fails.
I know, i'm nuts!! Finally before i admit defeat i'm going to part with £15 to buy credits for the dc-unlocker and dcPhoenx programs. From what ive read it has a good chance of solving it. I've taken soooo long before considering this option because i think its wrong that someone(s) is making loads of money from this. Why havent huawei/honor included a similar program in hi-suite. Anyway ive gone off on a tangent.
One last question though. Strangely enough i only just thought of it recently....
Is it a necessity to have your sim card in the tray as well as the sd-card????? All this time i havent had a sim in the phone as its in a crappy old one so i can still communicate with the world!!!!
Thank you to everyone for taking your time to read this. I hope a solution is possible.
Click to expand...
Click to collapse
No need of sim card in tray while using dload. Just sd card is fine. Let me go through it again and try to help before you go for 15 dollars for dc phoenix
shashank1320 said:
No need of sim card in tray while using dload. Just sd card is fine. Let me go through it again and try to help before you go for 15 dollars for dc phoenix
Click to expand...
Click to collapse
Yeah i didn't think it made any difference but its good to make sure.
i'll be waiting patiently for any golden nuggets of help you can give me.
thanks shashank1320,:fingers-crossed:
iantechie1979 said:
Yeah i didn't think it made any difference but its good to make sure.
i'll be waiting patiently for any golden nuggets of help you can give me.
thanks shashank1320,:fingers-crossed:
Click to expand...
Click to collapse
Did you flash those files i given? If not can try. Else i will have to look for other alternative
yeah i downloaded those files you had mentioned in your post and followed the instructions to the letter.
I've got a suggestion if you have tried all these above.
Can you try the following on ADB and then try to unlock OEM again.
fastboot oem relock YourUnlockCode
I've done the same and it helped, even when bootloader displayed UNLOCKED. Please try it. :good::good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@shashank1320 Hi, i have similar problem with my NEM-L21 device... I tried to flash the Elite ROM v5.1 but i didnt succeed so i decided to restore my old rom from backup with TWRP. When i restored it it just didnt load. It was stuck on honor logo for a long time. I tried the dload method many times but nothing worked so far. I even tried unbrick it with HUAWEI Multi-tool but it also didnt worked.
Now i cant acces anything, just fastboot. I cant even turn off the device. Please can you help me somehow?
NameNotFound74 said:
@shashank1320 Hi, i have similar problem with my NEM-L21 device... I tried to flash the Elite ROM v5.1 but i didnt succeed so i decided to restore my old rom from backup with TWRP. When i restored it it just didnt load. It was stuck on honor logo for a long time. I tried the dload method many times but nothing worked so far. I even tried unbrick it with HUAWEI Multi-tool but it also didnt worked.
Now i cant acces anything, just fastboot. I cant even turn off the device. Please can you help me somehow?
Click to expand...
Click to collapse
Try unlocking the bootloader again even if it is unlocked. It will factory reset the device and it should boot fine. Have stuck on this many a time and this was the method i followed.
Hello, I flashed my mi8 like I do every week.
This week I flashed the xiaomi.eu weekly rom, used it for 10hours, then my phone randomly restarted, and now it don't detect SIM cards and don't turn on WIFI, and the phone restart every X minutes.
I think the persist partition has gone. I can't find it on TWRP.
Any help?
Thank you
eRvY said:
Hello, I flashed my mi8 like I do every week.
This week I flashed the xiaomi.eu weekly rom, used it for 10hours, then my phone randomly restarted, and now it don't detect SIM cards and don't turn on WIFI, and the phone restart every X minutes.
I think the persist partition has gone. I can't find it on TWRP.
Any help?
Thank you
Click to expand...
Click to collapse
Which TWRP did you use?
alone_in_dark said:
Which TWRP did you use?
Click to expand...
Click to collapse
I used the same I ever used, but a very old one? Do you think it's related to twrp?
eRvY said:
I used the same I ever used, but a very old one? Do you think it's related to twrp?
Click to expand...
Click to collapse
Follow his posts:
https://forum.xda-developers.com/search.php?searchid=461808923
Hope it might help you.
eRvY said:
I used the same I ever used, but a very old one? Do you think it's related to twrp?
Click to expand...
Click to collapse
Have you solved your problem? Can you please tell which TWRP were you using specifically?
alone_in_dark said:
Follow his posts:
https://forum.xda-developers.com/search.php?searchid=461808923
Hope it might help you.
Click to expand...
Click to collapse
i cant find that post?
I have the same problem.
Have you tried installing all possible ROMs nothing resoved?
Does anyone have a solution?
Follow this thread:
https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551
Which TWRP were you using specifically?
alone_in_dark said:
Follow this thread:
https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551
Which TWRP were you using specifically?
Click to expand...
Click to collapse
I'm having the same issues, I'm running the latest official TWRP. The thread you linked won't open.
alone_in_dark said:
Follow this thread:
https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551
Which TWRP were you using specifically?
Click to expand...
Click to collapse
Not solved ..
Anyone with a solution ??
Are you guys having the same issues as I?
Phone boot, don't detect SIM or Wifi, and reboot after 3-5mins?
Anyone find the solution?
alone_in_dark said:
Follow this thread:
https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551
Which TWRP were you using specifically?
Click to expand...
Click to collapse
eRvY said:
Are you guys having the same issues as I?
Phone boot, don't detect SIM or Wifi, and reboot after 3-5mins?
Anyone find the solution?
Click to expand...
Click to collapse
not yet, and I think it will be difficult,
but so many people with the same problem xiaomi will have to solve ..
Everyone should ask xiaomi support I already made my request I'm waiting for response.
sk3lt said:
not yet, and I think it will be difficult,
but so many people with the same problem xiaomi will have to solve ..
Everyone should ask xiaomi support I already made my request I'm waiting for response.
Click to expand...
Click to collapse
I sent my phone to checked by a professional, because it fell from the couch in the afternoon, and everything is working, no shorts.
Now I was almost 100% that the 19/12/2019 update ****ed my phone.
I already bought a realme x2 , because this is my 2nd xiaomi that die out of nowhere, the last one was a Mi4, random shutted down, and never went back to life.
Is your Mi8 chinese or globa versionl?
Mine is chinese
Same problem (global version). Did you fix It?
Hey guys, im from brazil and have same problem, anybody have a help?
Im trying unlock my fastboot for downgrade rom.
I found a fix, remove SIM card, wait 10 seconds, power off phone, put SIM cards back inside and boot the phone
tmcsword said:
Hey guys, im from brazil and have same problem, anybody have a help?
Im trying unlock my fastboot for downgrade rom.
Click to expand...
Click to collapse
This issue has happened on many phones over the past 5 years, and it can definitely be resolved, it has nothing to do with unlocking anything, it's a encryption problem.
It is possible that when Mi-Cloud attempts to register your sim card, that some sort of security packet is downloaded to the phone for your protection. Ensure that you can sign into your mi_cloud account and locate your device, if using Miui. Also, be sure that you have international texts enabled, they text just once or twice so it doesn't cost more than a few cents.
With all of that being said a persist issue isn't the same thing as a sim card issue, and if you phone will not boot you are well past taking out your sim card. The easiest and fastest solution is to restore your persist partition from a TWRP backup, if you have one.
If that is not an option follow my instructions here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
tsongming said:
This issue has happened on many phones over the past 5 years, and it can definitely be resolved, it has nothing to do with unlocking anything, it's a encryption problem.
It is possible that when Mi-Cloud attempts to register your sim card, that some sort of security packet is downloaded to the phone for your protection. Ensure that you can sign into your mi_cloud account and locate your device, if using Miui. Also, be sure that you have international texts enabled, they text just once or twice so it doesn't cost more than a few cents.
With all of that being said a persist issue isn't the same thing as a sim card issue, and if you phone will not boot you are well past taking out your sim card. The easiest and fastest solution is to restore your persist partition from a TWRP backup, if you have one.
If that is not an option follow my instructions here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Click to expand...
Click to collapse
Dear look, my fastboot is locked, for install twrp ( do you have some instruction for instal TWRP ? ) I think the bootloader need be unlocked, sure?
Thanks for try help me.
tmcsword said:
Dear look, my fastboot is locked, for install twrp ( do you have some instruction for instal TWRP ? ) I think the bootloader need be unlocked, sure?
Thanks for try help me.
Click to expand...
Click to collapse
If you are meaning that your bootloader is locked then the only option ( if your phone is linked to your MiCloud account) Is to return to a stock rom using Miflash or by downloading a fast boot images rom and using the flash all.bat method. The link that I provided earlier has a fast boot images rom linked.
Clarify whether or not you can access fastboot. If you can in fact access fast boot, and you previously used custom ROMs the instructions for installing TWRP are on the official TWRP website. You simply use ADB to push it yo the recovery partition.
tsongming said:
This issue has happened on many phones over the past 5 years, and it can definitely be resolved, it has nothing to do with unlocking anything, it's a encryption problem.
It is possible that when Mi-Cloud attempts to register your sim card, that some sort of security packet is downloaded to the phone for your protection. Ensure that you can sign into your mi_cloud account and locate your device, if using Miui. Also, be sure that you have international texts enabled, they text just once or twice so it doesn't cost more than a few cents.
With all of that being said a persist issue isn't the same thing as a sim card issue, and if you phone will not boot you are well past taking out your sim card. The easiest and fastest solution is to restore your persist partition from a TWRP backup, if you have one.
If that is not an option follow my instructions here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Click to expand...
Click to collapse
hey whats up man,I hope u still answers questions I really hope you do because I'm in a dire situation where is my xiaomi mi8 cant connect to my sim card .It all started this year after a use of this phone since 2019 january.After my trip overseas , I got my own national sim card in again after that it occurs the problem at first was not that consistent,sometimes it detects, sometimes its good,after a while I thought that the sim card is loose so I wedged the simcard with a bit of paper,about sometime it works and then it starts to overheat when it doesn't detect the sim card inside and starts to reboot on its own, if I remove my simcard,its all good I can use wifi without overheating,how can I actually solve this problem? i quite believe that mi account /micloud that is causing all of this? whats your opinion on this? Im not an expert at all.Thanks for your time of reading this
Hey!
Ive been noticing an issue with my device, since I think the update to MIUI 11 (but not sure).
Description:
- The compass (and other apps using compass like Google maps) gives incorrect readings, when put horizontally. When put horizontally and kept still, the compass will spin regularly ca 2 degrees per second completely independent from the actual pointing direction. When the phone is kept vertically the compass works normally. I have made a video displaying the correct reading when vertically, and the spinning when kept horizontally: https://youtu.be/xgC4fHqH4Ys
- When checking the underlying gyroscope functionality with "Sensor Multitool", I have come across what I think is an erratic z axis reading. When I spin the phone randomly, the gyroscope in the x and y axis registers adequate readings, but the z axis stays completely flat. I have produced a video showing this behavior: https://youtu.be/1dY_xdF5Nz8
I have found this thread from Aliosa007 ( https://forum.xda-developers.com/showthread.php?t=3972249 ) that describes a very similar issue, but this user had recently flashed a new rom and the problem is attributed with the flashing. The users there assume the issue being a corrupt persist.img and most problem solving techniques involve flashing etc. But my phone is locked and not rooted. Could I also have received a corrupt persist.img during the normal update process recently to MIUI 11.
Currently trying to figure out, what the best way forward is. Wait and hope that this will be fixed with the next update or go the warranty route?
Thanks for helping me out with this one!
Hi.
I'm sorry I won't be very useful since I'm just having the exact same problem as you and don't know how to solve it... My phone isn't flashed either and my compass spins continuously.
I just wanted to know if you found a solution since your original post.
I also wanted to know if you tried factory resetting your phone ? I was thinking about trying that but if you already did and it didn't solve the issue, maybe I won't bother...
Thanks in advance.
Tistou52 said:
Hi.
I'm sorry I won't be very useful since I'm just having the exact same problem as you and don't know how to solve it... My phone isn't flashed either and my compass spins continuously.
I just wanted to know if you found a solution since your original post.
I also wanted to know if you tried factory resetting your phone ? I was thinking about trying that but if you already did and it didn't solve the issue, maybe I won't bother...
Thanks in advance.
Click to expand...
Click to collapse
Hey Tistou, thanks for your message. I haven't found a solution to the issue yet, unfortunately.
I tried factory resetting the phone but that didn't solve it. Did this problem just occur one day - or was it after you updated the phone? In my case Im not 100% sure it began after the updated and if it didn't, it could be an indication for a hardware issue.
I will keep this thread up to date in case I find a solution to the issue. But at the moment, I am out of ideas. I thought about flashing the phone with an alternative ROM and replace the persist.img. But currently the assumed risk/benefit keep me up from doing that. I'd assume sending Xiaomi feedback on that issue
Best,
schnodda
schnodda123 said:
Hey Tistou, thanks for your message. I haven't found a solution to the issue yet, unfortunately.
I tried factory resetting the phone but that didn't solve it. Did this problem just occur one day - or was it after you updated the phone? In my case Im not 100% sure it began after the updated and if it didn't, it could be an indication for a hardware issue.
I will keep this thread up to date in case I find a solution to the issue. But at the moment, I am out of ideas. I thought about flashing the phone with an alternative ROM and replace the persist.img. But currently the assumed risk/benefit keep me up from doing that. I'd assume sending Xiaomi feedback on that issue
Best,
schnodda
Click to expand...
Click to collapse
Hey,
well I couldn't really tell if it's related to an update : I got my mi 9T pro like two or three weeks ago and updated to 11.0.3 the day I got it...
The weird thing is that I noticed the problem one first time, and then two or three days later the issue solved itself without me doing anything particular and my compass started working normally again... And then two or three days ago it started spinning continuously again... I just hope it's software related and not an hardware issue...
I think I'm just going to wait for the next system update and if doesn't solve the problem I may send the phone back (but I don't wanna ... The phone otherwise is so great...).
I'll update the thread if I find something.
Good luck
Hi there, I had a similar problem a while ago when going from custom rom Android 10 back to miui 10 Android 9. Pop up camera and gyro sensors wouldn't work so no auto rotate either. Simple fix was to flash the persist img in custom recovery, then go into stock camera app and it'll ask to calibrate, after than everything worked fine. This should work for you and everyone else with this problem hopefully.
Flashing persist won't wipe any of your data so don't worries there. I'll see if I can find the file I have it somewhere and I'll send the link.
So really the only way to fix this is to have compatible custom recovery with persist partition, flash the persist.img, but since you have a locked bootloader and stock recovery I don't think you have any options to fix this unfortunately, maybe fastboot rom through miflash? That didn't work for me but it might work for you.
hoopsnake said:
Hi there, I had a similar problem a while ago when going from custom rom Android 10 back to miui 10 Android 9. Pop up camera and gyro sensors wouldn't work so no auto rotate either. Simple fix was to flash the persist img in custom recovery, then go into stock camera app and it'll ask to calibrate, after than everything worked fine. This should work for you and everyone else with this problem hopefully.
Flashing persist won't wipe any of your data so don't worries there. I'll see if I can find the file I have it somewhere and I'll send the link.
So really the only way to fix this is to have compatible custom recovery with persist partition, flash the persist.img, but since you have a locked bootloader and stock recovery I don't think you have any options to fix this unfortunately, maybe fastboot rom through miflash? That didn't work for me but it might work for you.
Click to expand...
Click to collapse
Thank you so much for your response! That keeps my hopes up that I get it solved eventually.
I am currently not planning to unlock my bootloader, I am currently exploring to go the warranty route because that's the easiest way forward. But in case that won't work, I will definitely try to flash the persist.img. I will have to try to get my hands on the persist.img file!
Thanks again!
schnodda123 said:
Thank you so much for your response! That keeps my hopes up that I get it solved eventually.
I am currently not planning to unlock my bootloader, I am currently exploring to go the warranty route because that's the easiest way forward. But in case that won't work, I will definitely try to flash the persist.img. I will have to try to get my hands on the persist.img file!
Thanks again!
Click to expand...
Click to collapse
persist.img is in the fastboot rom, so if you download that and extract you can get the img. You should be able to flash it thru fastboot using adb on PC with the command 'fastboot flash persist persist.img'. no need to unlock bootloader
I'm not gonna be near my PC for a while so won't be able to upload it for you
hoopsnake said:
persist.img is in the fastboot rom, so if you download that and extract you can get the img. You should be able to flash it thru fastboot using adb on PC with the command 'fastboot flash persist persist.img'. no need to unlock bootloader
I'm not gonna be near my PC for a while so won't be able to upload it for you
Click to expand...
Click to collapse
Sorry sir, but i think you cannot flash persist.img thru fastboot, because it read-only partition ,
I read several times that it must be flashed with twrp (dunno what that means)... But I also read that it makes you lose L1 widevine (dunno what that means either). Could someone enlighten me ?
And do you think the next MIUI update could fix that ?
Tistou52 said:
I read several times that it must be flashed with twrp (dunno what that means)... But I also read that it makes you lose L1 widevine (dunno what that means either). Could someone enlighten me ?
And do you think the next MIUI update could fix that ?
Click to expand...
Click to collapse
Not an expert on the matter. But a peripheral knowledge of the matter.
It appears to me that you are new to the matter. So I will use easy language.
TWRP is a so called "custom recovery" for Android that allows users to basically change the underlying firmware/system software (a process often referred to as "flashing") of the device. It is basically the entry point towards conveniently changing system files, that Android normally forbids you to change. To install a costum recovery, the bootloader of the phone has to be unlocked, so that the device can boot into the custom recovery instead of the OS directly. https://www.quora.com/What-is-TWRP-Why-is-it-used?share=1
Widevine L1 is a software part within Android that basically authenticates, that the device at hand is allowed to handle media files that are DRM protected (eg. within Netflix). When Android has been changed from the default configuration (by flashing a custom rom), the software part should revoke the authorization or restrict it. This behavior depends I think on the capability of the custom rom to trick widevine into believing that its genuine.(not so sure about that)
https://www.androidauthority.com/widevine-explained-821935/
Heres hoping that the next update will solve the issue! The issue isnt so dramatic to go the persist.img route. So I will patiently wait for the update. I will keep the thread updated.
schnodda123 said:
Not an expert on the matter. But a peripheral knowledge of the matter.
It appears to me that you are new to the matter. So I will use easy language.
TWRP is a so called "custom recovery" for Android that allows users to basically change the underlying firmware/system software (a process often referred to as "flashing") of the device. It is basically the entry point towards conveniently changing system files, that Android normally forbids you to change. To install a costum recovery, the bootloader of the phone has to be unlocked, so that the device can boot into the custom recovery instead of the OS directly. https://www.quora.com/What-is-TWRP-Why-is-it-used?share=1
Widevine L1 is a software part within Android that basically authenticates, that the device at hand is allowed to handle media files that are DRM protected (eg. within Netflix). When Android has been changed from the default configuration (by flashing a custom rom), the software part should revoke the authorization or restrict it. This behavior depends I think on the capability of the custom rom to trick widevine into believing that its genuine.(not so sure about that)
https://www.androidauthority.com/widevine-explained-821935/
Heres hoping that the next update will solve the issue! The issue isnt so dramatic to go the persist.img route. So I will patiently wait for the update. I will keep the thread updated.
Click to expand...
Click to collapse
Hola @schnodda123, ¿Logaste darle solución? No he podido arreglar mi eje z en mi caso en un Redmi Note 8, estoy algo incomodo, si bien el celular funciona bien el tener el sensor mal es fastidioso
Hi @ schnodda123, Did you manage to give it a solution? I have not been able to fix my z axis in my case on a Redmi Note 8, I am somewhat uncomfortable, although the cell phone works well, having the wrong sensor is annoying
UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.
Can we get a video of how to do this?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.
AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks
#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.
Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project
So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader
MOD EDIT:
This is the latest version
这是最新版本
#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
any luck with that? can I backup my firmware before doing it?
darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.
Foreword: My time with Vivo has come to an end. After flashing a wrong devicecfg and accidentally rebooting my device it is now in a hard bricked state.
Vivo has locked down EDL, there is absolutely no way to flash or backup anything in EDL mode without the official Tools (namely Vivo AFTool 5.9.80).
Vivo India refers me to Vivo Germany - Vivo Germany has outsourced its customer support to bulgaria.
The people on the other side of the line know absolutely nothing about the technical aspect and refuse to put me through to anyone with any kind of knowhow.
Due to their anti consumer and anti repair attitudes I will not buy another Vivo phone.
With this out of the way: You might end up like me with a hard brick. Or without signal.
Even if this will not save you from a hard brick I can not stress this enough: Make a BACKUP! And backup your data. This will wipe your phone.
This process is IRREVERSIBLE unless you have a split ROM of the chinese Firmware or your own Backup.
THIS or BL UNLOCK will break your portrait mode. No more bokeh, neither in Origin OS nor FunTouch.
Do NOT flash fsg, modemst1 and modemst2. They are commented out in the COMMANDS file.
You do this at your own risk. As said before this might brick your device.
Unlock your Bootloader
Backup your Partitions
Download my Flash Folder and Extract it: Android File Host
Open 01COMMANDS.txt and read the instructions
Open a command shell in the same folder that you can find 01COMMANDS.txt in
Run the given commands in blocks or one after the other
If you do not have signal after flashing you might have to erase modemst1 and modemst2 partitions, so that they get replaced by the backup in fsg.
A magisk flashed boot.img and adb-modded recovery is included so you can flash it after booting up FunTouch once and backup all your partitions again.
Thanks again to @Pervokur for helping me along the way. There is definitely an easier method that involves less risky flash operations.
My phone died on the cross while I was trying to figure it out, so maybe someone else will pick up the torch.
I will not be able to offer any kind of support.
RIP @Killuminati91's Vivo, who died for the cause.
Sorry to hear that, man, you were so close to what looked like an easy switch between ROMs.
I know you said you were no developer but you are still a leap ahead of most of us here. Long do we miss the good old days where ROMs, kernels and pure innovation shortly followed our much-wanted phone when flashing a few ROMs a week was normal.
Thanks for all your help, perhaps one day there will be a way to recover your phone.
Many thanks, may I relock the bootloader when i finished change to Global rom?
amos0609 said:
Many thanks, may I relock the bootloader when i finished change to Global rom?
Click to expand...
Click to collapse
Same question
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
how did you relock the bootloader, does the portrait mode work again?
does any one change the origin os /ocean into funtouch？
version？ how to relock after it can switch to funtouch？
by the way, I saw the post on the taiwan vivo phone of fb
the second hand goods, it wrote he change the origin os into funtouch
and he sell this service , it charge 2000 nt dollars in taiwan.
maybe someone can save your phone.
Killuminati91
I think the only problem that keeps the phone from being recognized as official FunTouch is dm-verity.
In theory both phone versions have the same exact hardware.
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
stevenkh168 said:
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
Click to expand...
Click to collapse
Message?
silence360 said:
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
Click to expand...
Click to collapse
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Killuminati91 said:
Message?
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Click to expand...
Click to collapse
did you try using the OriginOS's camera app on FuntouchOS ? I find it when u use the front facing camera, the portrait mode still work. In the other hand, the back camera is not working in portrait mode. I follow your guide and using the FuntouchOS about 2 days. Everything works fine, except the portrait mode and the AOD. Cant use it anymore.
Oh I see, now that is weird that the portrait mode is not working. So even if you switch not all functionality has returned. Thanks for the explanation. Hopefully someone can continue your work, and find a solution for a seamless transition.
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
hope to see some good news from you sir.
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
Update us...
have you been able to solve it?
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
NHQ Thang said:
how did you relock the bootloader, does the portrait mode work again?
Click to expand...
Click to collapse
same question
adkana4310 said:
Update us...
have you been able to solve it?
Click to expand...
Click to collapse
If u asking me so no im still on the same cant flash
redwatch99 said:
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Click to expand...
Click to collapse
Someone who can help me solve it ?