Related
So gentleman its about time i asked for help. I am not a dev but very android savvy, have rooted, recovered, de-bricked 100+ devices and only two hard bricks so far.
So here goes. i got a m8 hk edition brand new, proceeded with custom recovery, unlocked boot-loader, firewater s-off blah blah and next i try to sim unlock. while in programming screen i looked away and my baby boy hit a the screen and chose an unknown option, my phone rebooted, upon boot I was greeted by a phone lock screen please enter password. I never set one. I cannot call but only 911 sometimes can *2 but only for a second. cannot reset after 10 attempts, lock is persistent after flash of new rom and now i really messed up s back on and relocked bootloader. i can unlock bootloader again but since flashed new rom and reset device adb isnt on. have tried everything google got and searched for almost a year to no avail for a solution. PLEASE HELP. I AM NO NOOB. also have tryed the encryption bug fix too and nothing.....REWARD......
Have you tried a RUU? Hit the second link in my sig and read the RUU section. Then go to the thread in the link below and grab the RUU for software version 3.31.654.2 and run it from your computer.
http://forum.xda-developers.com/showthread.php?t=2729173
ruu
I have tried several ruus not sure of versions with fail if i remember right error was something about security or permissions.. also cid was changed at some point, havent worked on phone in a month downloading your link now. I appreciate any and all input on this and would like to hear of any others with this problem. as soon as i get device booted with recovery i will post more information about device specs
jamesdeanwest said:
I have tried several ruus not sure of versions with fail if i remember right error was something about security or permissions.. also cid was changed at some point, havent worked on phone in a month downloading your link now. I appreciate any and all input on this and would like to hear of any others with this problem. as soon as i get device booted with recovery i will post more information about device specs
Click to expand...
Click to collapse
If you changed your CID then you're S-off and there is no need to relock your bootloader. You may need to change your CID back to stock (SPCS_004 in your case) if you continue to get errors while trying to run the RUU, however, I don't believe that will be necessary.
If you're wanting to go back totally stock & S-on, locked bootloader and all, check out the guide in the link below.
http://forum.xda-developers.com/showthread.php?t=2826343
Ruu's flash successfully but device still boots locked. I was s off but returned device back to s on at some point. I can still re-lock and unlock bootloader, but i cannot return to s off because the Device has yet to enable ADB . Since every flash clears all settings after boot the developer settings are not even enabled because im locked out at first boot EVERY time I factory reset or flash a new Rom or ruu.
Please tell me something I havent tried yet. Something im missing? Im thinking about offering a reward to anyone who can help me solve this problem.
In the picture is something I haven't been able to find on than any other Harman Kardon m8. What password? Could it have possibly been a password set with my root anti-theft app AVAST?
If you select emergency call from the screen in the picture, does it bring up the dialer or just call 911?
If the dialer comes up, can you enter any ## or *# whatever type commands? Maybe reset it from there. ##72786# or ##786#
fgr said:
If you select emergency call fe, does it bring up the dialer or just call 911?
If the dialer comes up, can you enter any ## or *# whatever type commands? Maybe reset it from there. ##72786# or ##786#[/QUO
Dialer comes up but the only code it will take is *2
activation menu but only for a second. 25 $ bounty on this issue if anyone has some insight on how to resolve this issue. ANYONE HAVE A JTAG? ILL SEND.MY DEVIVE TO U AND.PAY YOUR FEE?
Click to expand...
Click to collapse
no dialer codes
fgr said:
If you select emergency call fe, does it bring up the dialer or just call 911?
If the dialer comes up, can you enter any ## or *# whatever type commands? Maybe reset it from there. ##72786# or ##786#[/QUO
Dialer comes up but the only code it will take is *2
activation menu but only for a second. 25 $ bounty on this issue if anyone has some insight on how to resolve this issue. ANYONE HAVE A JTAG? ILL SEND my device
TO U AND.PAY YOUR FEE?
Click to expand...
Click to collapse
Have you contacted Sprint?
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
BlackStorm94 said:
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
Click to expand...
Click to collapse
Same thing happened to me after I unbricked my device using the exact same tutorial. However, even with IMEI 0 I can still make and receive calls and text messages. But I'm not sure if I should leave my device like this. If someone has any solution to provide I would be very grateful! I hope it doesn't involve flashing any ROM again cause I'm really afraid that I may brick my phone again ...
Hey guys, I had exactly the same problem. I tried different things including flashing various Roms and Bootstack, but nothing seemed to work. Since I’ve been searching for a solution quite a while, I now have the honor to help you out and everyone with an L90, who stumbles upon the same issue.
First of all, I made a backup of my EFS, so that I could restore the state my phone was in (IMEI=0, but working baseband). You can do that easily with TWRP (thx to shoxxy . By the way, this is something which we all should have done beforehand. It would have been much easier to restore our IMEIs.
But don’t worry, if you follow the instructions in this video (https://www.youtube.com/watch?v=nwzgs1Cmr9k) you should be able to get your IMEI working again. For those, who feel more comfortable following written instructions I copied the following procedure using this thread (http://forum.xda-developers.com/showthread.php?t=1960918) as a model and edited them a little to the way it just worked for me.
Do this on your own responsibility! And better double-check with the video our other threads.
Before you start:
Download this package (http://www.mediafire.com/download/figdbxb75j5kyry/package.rar), it belongs to the user who made the video on youtube (PremiumRepair).
Make sure your phone is rooted and USB-Debugging is enabled (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Procedure :
Install Drivers. Either you use LG Support Tool or download them directly. For me the LGUnitedMobileDriver+3.14.1_ML_WHQL.exe worked just fine. Don’t forget to uninstall old drivers or you could run into problems.
Install QPST v2.7.378. Microsoft Visual C++ 2005 Redistributable is a prerequisite, just confirm it.
Plug your device into your PC (USB port)
Run QPST Configuration from your Windows Start menu. Switch to the second tab ("Ports") and choose "Add new port" (bottom left button). You should see a COM port associated with "USB/QD Diagnostic". Select it, then press Ok. You can close the QPST Configuration window now.
Open Windows Explorer and browse to "C:\Program Files\Qualcomm\QPST\bin" (or wherever you installed QPST) and launch RF_NV_Manager.exe. In RF NV Manager, Go to "Settings / Comport". You should see your COM port in the dropdown box. Select it, then press OK.
Go to "File" and choose "Read from phone". RF NV Manager will read all NV items from the phone. Now if you see item #550, you will be able to alter it (see below). If you can’t find it, go to “File” and choose “Read supported RF NV Items”. If you still can't find it, there is a way to create it. Take a look at the thread I linked to.
Now comes the critical step of altering the IMEI. Select item #550 and you'll see 9 boxes on the right, a "Write NV" button and an "Hex" checkbox. Check the "Hex" checkbox.
Now, you'll have to enter the IMEI in the 9 boxes in a very specific way. The easiest way is to use the IMEI converter (for other method see linked thread). Put your IMEI in, convert it and put the digits in the boxes (two number per box).
Now you can then press "Write NV" to write the IMEI value to your phone.
Once done, unplug the device, and reboot it. Now you IMEI should be changed. If it’s not your number, take a look at the step seven again and check the video.
Please give a feedback, if it worked for you (incl. Details about your device, ROM, etc.) so that other users can profit from it. Thanks
Edit: @ BlackStorm94 - Don't worry about the warning. It will vanish if you install a different ROM.
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Lazgeor said:
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Click to expand...
Click to collapse
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
mhikel said:
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Click to expand...
Click to collapse
So, I rooted the phone successfully, but the phone is still not recognized by QPST Configuration or RF NV Manager. My pc recognizes the phone and I can do everything properly, but these programs say that there is No Phone ... I don't know what to do ...
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
mhikel said:
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
Click to expand...
Click to collapse
I'm going to try on a new computer tomorrow afternoon and I'll let you know how it went. I uninstalled all drivers associated with my phone on my computer and after reinstalling them I still got no results. I guess I may have confused it So that's why I'll try on a new one. Thanks for your help
Hello, sorry for the late reply. I just wanted you to know that even though I tried with another computer, my phone was still not recognizable. It doesn't really matter tho, cause even with the IMEI 0 I still have service and it works normaly for about a month now. If you have any solution then I would like to try it, but if not then it's okay. Thanks for your time
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
[/COLOR]
mhikel said:
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Click to expand...
Click to collapse
Yeah yeah, I had USB Debugging enabled every time I plugged my phone into both of my PCs. But I don't think that's the reason this tutorial isn't working on my phone. When I unbricked the device, I had to use the L90 D405 loader.img in order to reflash the bootloader and recovery. But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n. I hope you understood this cause I know it's a bit weird I see options to activate NFC but I never use it so I can't tell you if it works. However I can activate it properly. Anyway, about the IMEI, as I told you, it basically works without problems even with 0 because I think that my service provider doesn't block anybody except someone reports the device as stolen. If you have any further solutions then let me know but if not the don't worry, I'm okay!
Lazgeor said:
But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n.
Click to expand...
Click to collapse
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
mhikel said:
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
Click to expand...
Click to collapse
It's okay I don't want to bother you any further. I'll buy a new phone soon anyways and since I'll give this one to my small brother, I don't think he'll really worry if his IMEI is 0 If at some point this device gets blocked by a service provider then I'll start searching for ways to fix it again. That bootstack page you mentioned seems useful. I'll try that if I do have any problems. Thank you very much for your help
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
mhikel said:
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
Click to expand...
Click to collapse
Update: I actually fixed it I know I told you that I would leave it as it is for now, but today I had nothing to do, so I decided to try my best and fix it. What I did was, as the post you told me said, I had to install the Kit Kat bootstack and the easiest way to do that is by flashing the Kit Kat rom. So I downgraded to android 4.4.2 using the stock rom I found on another post, and then I used your tutorial on the Kit Kat version. This time I was able to pass step 6 because my phone was getting recognized properly. I also didn't needed root access after all, since the new rom was just installed and it worked. After finishing the tutorial and restarting the phone, my IMEI was back! Then I upgrated my phone to the lollipop version, and when the upgrade finished, my IMEI was still there. So now I'm in lollipop with a working IMEI. I'm so thankful to you now, thank you very much for helping me and providing me these useful tutorials. I really appreciate it
Wow, that's just great!=) congratulations, you can be proud! Happy for you, that was quite an issue. You are welcome=) Well, someone from this forum helped me out, when I seeked for help and I am happy to give something back. Thank you for sharing your solution! That should be helpful for the next one stumbling over this problem. Enjoy your completely restored phone!=)
My p10 was just got back from warranty claim for broken screen. When i turn it on, there was this menu asking to recalibrate fingerprint sensor because the sensor was just replaced (not inputting new fingerprint). It was unclear how i should do it at first, however after few attempts it was supposedly asking me to rotate the phone while the finger resting on top of the sensor.
Too bad, i think my first few failed attempts may have miscalibrated the whole sensor.
Anyone knows how to get back into that menu?
Allesa said:
My p10 was just got back from warranty claim for broken screen. When i turn it on, there was this menu asking to recalibrate fingerprint sensor because the sensor was just replaced (not inputting new fingerprint). It was unclear how i should do it at first, however after few attempts it was supposedly asking me to rotate the phone while the finger resting on top of the sensor.
Too bad, i think my first few failed attempts may have miscalibrated the whole sensor.
Anyone knows how to get back into that menu?
Click to expand...
Click to collapse
Remove the fingerprint in Settings and add a new one.
Sent from my LON-L29 using XDA Labs
Mostar088 said:
Remove the fingerprint in Settings and add a new one.
Sent from my LON-L29 using XDA Labs
Click to expand...
Click to collapse
that was the first thing i did.
well it is solved now. Solution is to re-flash full firmware. Factory reset wont do.
how did u reflashed it .. bcz I tried volume down+up+lock method but always it fails to updata
Allesa said:
that was the first thing i did.
well it is solved now. Solution is to re-flash full firmware. Factory reset wont do.
Click to expand...
Click to collapse
can u plz tell me how u reflashed it... bcz I have the same problem but my firmware always fails installing at 5%
kanishka1234 said:
can u plz tell me how u reflashed it... bcz I have the same problem but my firmware always fails installing at 5%
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page58
I replaced a broken display on a P10 VTR-L29 and the fingerprint button is not working, everything else is. At first I though the display is faulty, but now I have doubts since the fingerprint option on the menu is just not there. I re-flashed the same version of the firmware (B369) via TWRP and the problem persists. I may have to try a factory reset.
sky|ined said:
I replaced a broken display on a P10 VTR-L29 and the fingerprint button is not working, everything else is. At first I though the display is faulty, but now I have doubts since the fingerprint option on the menu is just not there. I re-flashed the same version of the firmware (B369) via TWRP and the problem persists. I may have to try a factory reset.
Click to expand...
Click to collapse
Fingerprint is not accidentally paired with PCB like in iPhone?
is there any solution for now? cause i cant unlock the bootloader any more
StarSix01 said:
is there any solution for now? cause i cant unlock the bootloader any more
Click to expand...
Click to collapse
So this is how it ends when noobs messing with phones they don´t understand.
-You can unlock bootloader by paying some bucks to DC phoenix.
When you have no fgingerprint sensor options enabled it points that:
- the fingerprint sensor is broken
- the fingerprint sensor is not conected right
Hi alll
I had the same problem after replacing my screen.
I used Quick tuneup, and since the fingerprint sensor work correctly.
DallasCZ said:
So this is how it ends when noobs messing with phones they don´t understand.
-You can unlock bootloader by paying some bucks to DC phoenix.
When you have no fgingerprint sensor options enabled it points that:
- the fingerprint sensor is broken
- the fingerprint sensor is not conected right
Click to expand...
Click to collapse
Who are You to call me a noob??
Ive got the phone from a friend and just asked for help.
Did i say, that there is no Option for fingerprint? NO there is one
StarSix01 said:
Who are You to call me a noob?
Ive got the phone from a friend and just asked for help.
Did i say, that there is no Option for fingerprint? NO there is one
Click to expand...
Click to collapse
Sorry bro, my fault, i thought you are the one who asked before you.
You didnt say anything about your problem just asked if there is a solution and that you cannot unlock bootloader. With this info no one is able to help you. But anyway:
1. method:
-Remove existing fingerprints
-do a factory reset
-add a new fingerprint (when finger not scaned properly try to push a little bit harder on the sensor and rotate the finger)
-After the new fingeprint is scaned it should work well
2. method:
-after you recieve OTA notification (every month) go to settings/system updates/ there are three dots in upper right corner and select "get the whole latest package". This will download the whole firmware and perform a factory reset low level and this should work (if simple factry reset didnt work for you).
if this methods don´t work i will suggest you to go to phone service.
DallasCZ said:
Sorry bro, my fault, i thought you are the one who asked before you.
You didnt say anything about your problem just asked if there is a solution and that you cannot unlock bootloader. With this info no one is able to help you. But anyway:
1. method:
-Remove existing fingerprints
-do a factory reset
-add a new fingerprint (when finger not scaned properly try to push a little bit harder on the sensor and rotate the finger)
-After the new fingeprint is scaned it should work well
2. method:
-after you recieve OTA notification (every month) go to settings/system updates/ there are three dots in upper right corner and select "get the whole latest package". This will download the whole firmware and perform a factory reset low level and this should work (if simple factry reset didnt work for you).
if this methods don´t work i will suggest you to go to phone service.
Click to expand...
Click to collapse
No problem Bro
I managed to download a filmware package with the filmware Finder (somehow it worked) do i have to use the dload method now?
spoolerbloque said:
Hi alll
I had the same problem after replacing my screen.
I used Quick tuneup, and since the fingerprint sensor work correctly.
Click to expand...
Click to collapse
thank you very very much its work for me
Hey,
I purchased a Samsung Note 8 (SM-N950F) a couple of years from Amazon.de. The phone was unlocked, since then new OS releases were really slow so I decided to download the Pie update from Sammobile and updated my phone via Odin. The phone is using official firmware and has never been rooted yet when I try to activate Google Pay I receive the following error; "Couldn't finish setup to pay in shop. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I spoke to Samsung and told me to check a few things and they confirmed the phone is not rooted, I spoke to Google and they told me I should ask Samsung how to unlock the bootloader but Samsung said doing this would void my warranty. I'm a bit confused as to what to do, is there a stock pie rom I can use without voiding my warranty?
Thanks a lot, appreciate any help
Regards
p4rma
The only thig i can think of is that, the phone you've got has a CSC code of a region where Google Pay is not supported, or maybe you are living in a country that do not support Google Pay.
If you think I'm wrong, flash stock pie firmware.
Flashing stock offiicial binaries doesn't need your bootloader to be unlocked.
Thanks for the quick reply I will try this. Would Samsung have their own stock pie rom? Kinda wish I just waited for the pie update rather than flashing. Its annoying I can't use Netflix either as it says my device is not compatible.
I just checked and my bootloader is N950FXXU7DSJ1
Hey there,
I also faced the same issue when using GPay. I recommend trying these steps, might workout for you (it did for me):
Before doing this I recommend Backing your phone up, sometimes phone might erase user data but I didn't lose data.
1. Goto Settings > About Phone > Software Information > Build Number (Tap this thing 7 times). It should display a toast saying Developer options has been enabled.
2. Go back to Settings > Developer Options.
3. Turn on USB Debugging first, just in case.
4. See if OEM Unlock is turn on, if it is then turn it off.
5. Try turning it back on if it is turned off, you phone will reboot if you do so. Once rebooted, go back and turn it back off.
You shall be able to use Google Pay.
Note: These are the exact same steps that I did and it started to work for me.
As for changing CSC its a little complicated (by rooting its way easier but then you will lose Samsung Pay & some other Knox features). You will need to do a couple of steps and it also leads to erasing of user data.
If you don't wanna risk anything, why not try SPay. It might be supported in your country.
Unix_Dominator said:
Hey there,
I also faced the same issue when using GPay. I recommend trying these steps, might workout for you (it did for me):
Before doing this I recommend Backing your phone up, sometimes phone might erase user data but I didn't lose data.
1. Goto Settings > About Phone > Software Information > Build Number (Tap this thing 7 times). It should display a toast saying Developer options has been enabled.
2. Go back to Settings > Developer Options.
3. Turn on USB Debugging first, just in case.
4. See if OEM Unlock is turn on, if it is then turn it off.
5. Try turning it back on if it is turned off, you phone will reboot if you do so. Once rebooted, go back and turn it back off.
You shall be able to use Google Pay.
Note: These are the exact same steps that I did and it started to work for me.
As for changing CSC its a little complicated (by rooting its way easier but then you will lose Samsung Pay & some other Knox features). You will need to do a couple of steps and it also leads to erasing of user data.
If you don't wanna risk anything, why not try SPay. It might be supported in your country.
Click to expand...
Click to collapse
Thank you Unix_Dominator!!!!!!!!! This worked, I can now use Google Pay & Netflix
p4rma said:
Thank you Unix_Dominator!!!!!!!!! This worked, I can now use Google Pay & Netflix
Click to expand...
Click to collapse
I'm glad it worked out for you too!!!
Unix_Dominator said:
I'm glad it worked out for you too!!!
Click to expand...
Click to collapse
I noticed it has stopped working again but I'll try your method again. Did you have the issue or is yours pemanently fixed?
Thanks
p4rma said:
I noticed it has stopped working again but I'll try your method again. Did you have the issue or is yours pemanently fixed?
Thanks
Click to expand...
Click to collapse
It has been permanently fixed for me, I never faced any issue with GPay after that method (I don't use Netflix though). Could you also see if you phone is updated to the latest version, if so also check if your phone has a fix for Stagefright.
To check if you are vulnerable to that exploit download this app it will tell you Click Here . If it fails, try OEM unlock as off and see, might fix it.
I really hope this issue doesn't come back for you.
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.