Hello, firstable congratulations to everyone to made an awesome forum, page, etc...
Im from Mexico and I have a HTC one M8 Sprint and I use it on GSM band
a guy sold me with a program named teamwin this program appears when I try to install the new version
I already have the 4.4.3 android version, 6.0 sense and 2.16.651.4 sofware version
and my doubt is can I make any modd to my celphone? I guess that's sounds pretty obviously but I'm new on the topic
I remember I can modd a sony ericsson telephones (like w600) but now Im so noob on the celphone topics.
I like learn new things and I only asking for your help, maybe if you can help me I appreciate that
All the links you can give me will be readed 100% for sure.:good:
So greetings for everyone and again please help me to get this cellphone a new life :laugh:
Hold down power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons and only hold vol down. Don't let go, until you see a white screen with various info on it. This it the bootloader. If the phone simply reboots to OS or Safe Mode, you just had bad timing of the button combo. Repeat the process until you see the bootloader screen.
On the bootloader screen, does it say RELOCKED, UNLOCKED, or LOCKED near the top?
Does it say Software modified, or official?
Does it say s-off or s-on?
redpoint73 said:
Hold down power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons and only hold vol down. Don't let go, until you see a white screen with various info on it. This it the bootloader. If the phone simply reboots to OS or Safe Mode, you just had bad timing of the button combo. Repeat the process until you see the bootloader screen.
On the bootloader screen, does it say RELOCKED, UNLOCKED, or LOCKED near the top?
Does it say Software modified, or official?
Does it say s-off or s-on?
Click to expand...
Click to collapse
It says
Tampered
Unlocked
S-ON
About the OS I don't know, the phone already has SuperU app, also I don't know how it works
Erbat said:
It says
Tampered
Unlocked
S-ON
About the OS I don't know, the phone already has SuperU app, also I don't know how it works
Click to expand...
Click to collapse
You need to update the firmware, to do much of any mods (like current ROMs).
You can do so by either:
1) Finding the proper stock nandroid and stock recovery, then OTA update to latest version.
2) Relock the bootloader, and use latest Sprint RUU (will wipe the phone).
redpoint73 said:
You need to update the firmware, to do much of any mods (like current ROMs).
You can do so by either:
1) Finding the proper stock nandroid and stock recovery, then OTA update to latest version.
2) Relock the bootloader, and use latest Sprint RUU (will wipe the phone).
Click to expand...
Click to collapse
I'm a bit affraid because I don't know if after to do that my phone still works
It's sprint and I use it here in mexico with movistar so I need something else to do this proccedure? I also searching the topics you told me here in the forum
Erbat said:
I'm a bit affraid because I don't know if after to do that my phone still works
Click to expand...
Click to collapse
In your first post, you ask about doing mods. Now you are saying you are afraid to. So I have no idea what your comfort level, what you are willing to accomplish, etc.
As long as you are willing to learn, put in some time reading and understanding, and follow instructions carefully, there isn't much to be afraid of. Any mods to the phone involve some risk. But the risk of permanent damage (a true "brick") are minimal. The worst that is likely to happen, is the phone fails to boot, and you may need to troubleshoot for an hour to 2 to get it back running. But that happens to just about anyone that mods phones, at some time or other. Its just part of the game.
But in the phone's current condition, something needs to be done by you, in order to update the phone in any way; whether it be by official means (RUU or OTA) or custom ROM. Otherwise, it will be stuck on Android 4.4.3 as it is now.
Erbat said:
It's sprint and I use it here in mexico with movistar so I need something else to do this proccedure?
Click to expand...
Click to collapse
Not sure what you are asking, are you wondering if any additional hardware is needed? You will need a computer for either method I stated, plus the sync cable that came with the phone (or other charge/data cable). PC is required for Method #2.
Yes for sure Im reading the past days about the topic and the fears I guess its for my phone became to an expensive brick, but I want to do this, I sent you a PM and I read your answer sorry for do that.
And finally about the last quote, I mean the M8 its originally sprint (on the starts screen says) so I want to know if its possible make the unblock totally to use on any company of the world or the country (Mexico) above than GSM, maybe 3G or in the best way 4G
Erbat said:
And finally about the last quote, I mean the M8 its originally sprint (on the starts screen says) so I want to know if its possible make the unblock totally to use on any company of the world or the country (Mexico) above than GSM, maybe 3G or in the best way 4G
Click to expand...
Click to collapse
So it sounds like you already using the phone on Movistar, just not with 3G or 4G?
There is a mod to unlock bands, which seems to work on your Sprint CDMA version (from what I understand). But it requires s-off ($25 by sunshine app) and is a slightly more complicated mod: http://forum.xda-developers.com/htc-one-m8/general/unlock-bands-qualcomm-device-phone-t2880239
So if you are unsure about doing what I've previously described; the mod to unlock bands is definitely the next level beyond that. Mods done with s-off are more risky, and can actually brick the phone (render it permanently unusable).
Whatever you do, do NOT try to flash another carrier/region versions radio, firmware, RUU, etc. in an attempt to change the band support. You may see some recommendations to that effect. But this does NOT work on the Sprint version, and will probably BRICK your phone.
Sorry I think I don't give my idea correctly, my English is not good.
I wonder if you can make my htc have the most updated software and if it is possible to use other phone network than the GSM because since I buyed (used) has the same software, the same HTC Sense and I could only use the internet GSM mobile network
My phone is
m8_WHL PVT SHIP S-ON *Unlocked*
So I would like to write the correct idea because your help it's usefull for me
really I appreciate your help and therefore not want to lose by confusion or my bad english
then I hope this time to let me know if this is better for your
I'm trying to do my best
Erbat said:
Sorry I think I don't give my idea correctly, my English is not good.
I wonder if you can make my htc have the most updated software and if it is possible to use other phone network than the GSM because since I buyed (used) has the same software, the same HTC Sense and I could only use the internet GSM mobile network
Click to expand...
Click to collapse
Updating the software is a completely separate matter from the phone's band support (3G and LTE bands the phone is compatible with).
I already told you how to update the software, in Post #4 above.
To see if the phone will work with your carrier's 3G or LTE network, you first need to know what 3G and 4G band (or bands) they use for each. Can't really do anything without that basic info. Either research online, or call your carrier and ask them. This is something you should have done before buying the phone; as changing to the proper band support is not always possible.
redpoint73 said:
To see if the phone will work with your carrier's 3G or LTE network, you first need to know what 3G and 4G band (or bands) they use for each. Can't really do anything without that basic info. Either research online, or call your carrier and ask them. This is something you should have done before buying the phone; as changing to the proper band support is not always possible.
Click to expand...
Click to collapse
The band works on 850/1900, while 4G LTE conection use band 4 - LTE AWS frecuency of 1700 MHz and 2100 MHz.
I work today on the software ( the most important for me )
Erbat said:
The band works on 850/1900, while 4G LTE conection use band 4 - LTE AWS frecuency of 1700 MHz and 2100 MHz.
Click to expand...
Click to collapse
Sprint M8 supports 3G bands 850 and 1900.
Are you sure you entered your carrier's APN info correctly?
Did you try the SIM card in another phone, to make sure the SIM works for 3G?
redpoint73 said:
Sprint M8 supports 3G bands 850 and 1900.
Are you sure you entered your carrier's APN info correctly?
Did you try the SIM card in another phone, to make sure the SIM works for 3G?
Click to expand...
Click to collapse
yes I use the right APN settings but when I bought the guy who sold it to me also told me it was unblock for any company here in Mexico but the problem is that you could not upgrade because when the file is downloaded and is installed, the phone enters into recovery mode and can not be or I do not know if it's my mistake, you can not install at all
He say that if I upgrade or modify the phone I can lose part of the unblock of the phonel and it became unusable here in Mexico
I screwed a lot
I don't know what I did wrong on the process of re-stock the phone and now don't start.
only shows the white screen with HTC green logo.
I rememberd when I try to wipe I check all the options and "I swipe to wipe" later when the phone will be reboot
shows me a message about the superU and I install (because already has it)
I was scared and search about this and only found a way to enter on bootloader and says this
*Tampered*
*Relocked*
Well, 6 hours later I have this now:
*Tampered*
**Unlocked**
m8_WHL PVT SHIP S-ON
HBOOT-3.18.0.0000
OS-2.16.651.4
eMMC-boot 2048MB
but when I unlock the bootloader (here's the tutorial of bootloader http://www.htcdev.com/bootloader)
I see the recovery mode once but when I try to do the next step (http://forum.xda-developers.com/showthread.php?t=2755657)
I can not start the recovery mode and I don't do any of progression
Also I can see an message saying me the phone hasn't any OS file so I guess that's the reason I can make it start, only turn on and shows the same white screen with HTC logo, I can entered to Bootloader and FASTBOOT but when I select recovery the phone returns to HBOOT and when I turn off and later turn on happen the same (entered directly to HBOOT screen)
Im a bit concerned about that I hope you can teach me how
*Edited now I can enter to recovery I relocked and unlocked again and I can enter again to recovery and bootloader, please help me to put the files of OS
maybe with a SD card?
Return to stock
Hi Erbat,
first of all it would be nice to get an overview of your device and its versions, you can do this by doing the fastboot command "fastboot getvar all"
The most important version wich you already have is your OS 2.16.651.4, everything what you try to flash to your device if you want to return to stock should match this number or it will mostly fail.
So at this point forget about the Guide with official OTA updates and root access, because its for 4.16.401.10 and you should mainly focus on returning to stock without root to get new updates (easier)
I dont know how much knowledge you already have but just to mention:
Every OS with 2.16.651.4 is for your Sprint version, this means all of the files without 651 will lead in the wrong direction.
Later when you use a RUU ("official" files to return to stock firmware) or a nandroid backup (stock backup created by other users), the files and backups you will find have to match exactly to your OS Version 2.16.651.4 to work.
So at the moment you should focus on returning your device back to stock firmware and OS first, after that you can recieve official OTA updates from HTC :good:
The tutorials/threads you should focus on are mainly these two:
[GUIDE][S-ON] Restore your (European) HTC One M8 back to stock
[tutorial] How to get back on stock with TWRP Stock Nandroid Backups
Edit: You can't use your recovery, because if i understood this right you got TWRP (a custom recovery) before and might have corrupted/deleted it, simply flash the newest version of TWRP 2.8.7.0 with the fastboot command "fastboot flash recovery *NAME-OF_RECOVERY*.img"
TWRP: http://teamw.in/project/twrp2/225/
(If i got anything wrong pls correct me ^^)
KODEC.4 said:
Hi Erbat,
first of all it would be nice to get the an overview of your device and its versions, you can do this by doing the fastboot command "fastboot getvar all"
The most important version wich you already have is your OS 2.16.651.4, everything what you try to flash to your device if you want to return to stock should match this number or it will mostly fail.
So at this point forget about the Guide with official OTA updates and root access, because its for 4.16.401.10 and you should mainly focus on returning to stock without root to get new updates (easier)
I dont know how much knowledge you already have but just to mention:
Every OS with 2.16.651.4 is for your Sprint version, this means all of the files without 651 will lead in the wrong direction.
Later when you use a RUU ("official" files to return to stock firmware) or a nandroid backup (stock backup created by other users), the files and backups you will find have to match exactly to your OS Version 2.16.651.4 to work.
So at the moment you should focus on returning your device back to stock firmware and OS first, after that you can recieve official OTA updates from HTC :good:
The tutorials/threads you should focus on are mainly these two:
[GUIDE][S-ON] Restore your (European) HTC One M8 back to stock
[tutorial] How to get back on stock with TWRP Stock Nandroid Backups
Edit: You can't use your recovery, because if i understood this right you got TWRP (a custom recovery) before and might have corrupted/deleted it, simply flash the newest version of TWRP 2.8.7.0 with the fastboot command "fastboot flash recovery *NAME-OF_RECOVERY*.img"
TWRP: http://teamw.in/project/twrp2/225/
(If i got anything wrong pls correct me ^^)
Click to expand...
Click to collapse
OK I will try to do those things you've post here.
So tonight before I went to sleep the recovery says I don't have OS installed, that's so confusing because I don't know how install it again, I'm pretty noob so I (if you can do it) explain me a lot to do.
Yesterday already learn to use fastboot and the files and those things to do on the computer, I like to learn and more if is for recover my phone :laugh:
Erbat said:
OK I will try to do those things you've post here.
So tonight before I went to sleep the recovery says I don't have OS installed, that's so confusing because I don't know how install it again, I'm pretty noob so I (if you can do it) explain me a lot to do.
Yesterday already learn to use fastboot and the files and those things to do on the computer, I like to learn and more if is for recover my phone :laugh:
Click to expand...
Click to collapse
I know it looks pretty bad for a "noob" if he got no OS on his device and it won't boot anymore, but don't worry as long as you get your phone into fastboot mode you can fix everyting :fingers-crossed:
KODEC.4 said:
I know it looks pretty bad for a "noob" if he got no OS on his device and it won't boot anymore, but don't worry as long as you get your phone into fastboot mode you can fix everyting :fingers-crossed:
Click to expand...
Click to collapse
I can't do anything on cmd, my phone hasn't battery today and when I try to do fastboot getvar all say wating for your device and yesterday obviously don't say this
I need wait to 30%? I guess I have readed this before
Charge it up, restart everything (pc) and try again. You can use "fastboot devices" wich will list all devices connected in fastboot mode (ofc you must choose fastboot in bootloader menu first)
Next could be that you have HTC sync active witch might block something -> uninstall HTC sync
Otherwise you might have driver problems, if so, uninstall htc drivers and sync and reinstall HTC sync to get new drivers. -> uninstall sync only again (maybe reboot)
If all this does not work search for specific fastboot drivers for the M8 and try it with them
Erbat said:
I don't know what I did wrong on the process of re-stock the phone and now don't start.
only shows the white screen with HTC green logo.
I rememberd when I try to wipe I check all the options and "I swipe to wipe" later when the phone will be reboot
Click to expand...
Click to collapse
You should never wipe any of the partitions in the TWRP "Advanced" menu, unless you know exactly that they mean, and what the result will be (those options are called "Advanced" for good reason!). Even if the phone was properly working before, what you did was to wipe the OS (system partition) and make it stop working!
Further, you wiped any backup files and personal data that may have been on internal storage or the removable SD.
Simple rule when modding the phone: Do not experiment or make up your own solutions (will almost always fail and possibly make matter worse); and only do exactly what is directed to you from the proper guides, reputable "helpers", etc.
---------- Post added at 10:30 AM ---------- Previous post was at 10:27 AM ----------
Erbat said:
I screwed a lot
I don't know what I did wrong on the process of re-stock the phone and now don't start.
Click to expand...
Click to collapse
Can't help you, if you don't tell us exactly what you did: step by step, in specific detail, with links to the files you are trying to use, exact file names, etc.
If you don't tell us what you did, we can't see what you did wrong.
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
Erbat said:
I see the recovery mode once but when I try to do the next step (http://forum.xda-developers.com/showthread.php?t=2755657)
Click to expand...
Click to collapse
This guide has nothing to do with returning to stock, and is not for your version of the M8.
Nothing good can come of this; for what you are trying to do.
If you didn't know what you were doing, you should have stopped and asked. Learning and reading is good (and I applaud the effort), but don't do anything unless you are sure about it. In your case particular (due to your lack of knowledge/experience) I'd recommend not do anything unless we specifically direct you to. You seem to be going down the wrong roads, and just want to make sure we mitigate that now.
---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------
Erbat said:
I can't do anything on cmd, my phone hasn't battery today and when I try to do fastboot getvar all say wating for your device and yesterday obviously don't say this
I need wait to 30%? I guess I have readed this before
Click to expand...
Click to collapse
The phone needs to be powered on, and in bootloader-fastboot mode for any fastboot commands to work.
Charge the phone for a few hours, and try again.
We need to get fastboot working, to move forward at all.
Related
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
xxshererxx said:
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
Click to expand...
Click to collapse
what exactly is happening when you try and unlock the bootloader?
xxshererxx said:
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
Click to expand...
Click to collapse
Is urs the AT&T One? Then the bootloader unlock process is different. If urs is the standard international SIM unlocked, then ideally you should see a splash after you run the bootloader unlock command, which prompts you to unlock the bootloader. Please state what exactly ur issue is when u try to bootloader unlock
I'm with Verizon but it just gives me a 1 line error message doesn't run through anything else or load up anything. I type in "bootloader oem unlock" or whatever after clearly identifying my device is connected with "adb device" and nothing happens. It takes about 0.14 sec and says something along the lines of "[ERRORR] ......" after running again it takes 0.00 sec and says same thing, I can screenshot if you think it would be more helpful.
Please help, I appreciate both responses. Just really want this to work.
xxshererxx said:
I'm with Verizon but it just gives me a 1 line error message doesn't run through anything else or load up anything. I type in "bootloader oem unlock" or whatever after clearly identifying my device is connected with "adb device" and nothing happens. It takes about 0.14 sec and says something along the lines of "[ERRORR] ......" after running again it takes 0.00 sec and says same thing, I can screenshot if you think it would be more helpful.
Please help, I appreciate both responses. Just really want this to work.
Click to expand...
Click to collapse
Hahahaha Verizon is REALLY REALLY BAD when it comes to dev. support. Ideally, you shouldn't be posting this in this forum. Post it on the Verizon forum. But, I can help you.
http://rumrunner.us/downloads-2/
Download the package. Extract the zip and run the 'soju.exe' program. Please read ALL the pre-requisites mentioned in the instructions tab.
P.S. From next time if you're asking for help, please state that you're on Verizon
raghav kapur said:
Hahahaha Verizon is REALLY REALLY BAD when it comes to dev. support. Ideally, you shouldn't be posting this in this forum. Post it on the Verizon forum. But, I can help you.
Download the package. Extract the zip and run the 'soju.exe' program. Please read ALL the pre-requisites mentioned in the instructions tab.
P.S. From next time if you're asking for help, please state that you're on Verizon
Click to expand...
Click to collapse
Worked like a charm, but now I am having trouble with the recovery portion of all this.
I have downloaded and installed the TWRP Manager app and then went to install the recovery and it said my device is not supported, this same problem happened with CWMR.
xxshererxx said:
Worked like a charm, but now I am having trouble with the recovery portion of all this.
I have downloaded and installed the TWRP Manager app and then went to install the recovery and it said my device is not supported, this same problem happened with CWMR.
Click to expand...
Click to collapse
I think you'll find more help here: http://forum.xda-developers.com/verizon-htc-one
A friend recently gifted me a used One that he had previously unlocked and rooted, but returned to stock. I am attempting to unlock, root, and SIM unlock it. (It is sprint, I want to use it on att)
I do not know a lot about the One, I am not a huge fan of HTC in general as it seems that their phones were always overly complicated to work on.
I successfully unlocked the bootloader and threw clockworkmod recovery on, which is when the problems started. Since then, I was no longer able to boot the phone...
Then, as usual, the tampered message showed in my HBOOT menu.
I installed twrp recovery but that failed to work, so I then realized I had not downloaded the version for Sprint HTC Ones. After downloading the correct version, it does boot into recovery.
However, I cant seem to install any roms (this includes through ADB). It throws the error message "FAILED remote not allowed"
So Im sort of in a bind here, and I thought maybe someone with more knowledge about the One could help me out. Is the sprint version even capable of use on an ATT network, and if so, can someone please tell me how on earth I can fix this thing? I want to make a backup phone for use due to the fact that I'd like to sell my nexus 5 and buy a Oneplus One.
Thanks a ton!
Any help here? I still haven't been able to fix this. I've been trying several different recoverys, roms, etc. I also tried to reboot the phone to RUU but that was no help either. Remote errors..
EvanLovesToast said:
Any help here? I still haven't been able to fix this. I've been trying several different recoverys, roms, etc. I also tried to reboot the phone to RUU but that was no help either. Remote errors..
Click to expand...
Click to collapse
The Sprint HTC One is a CDMA phone and the AT&T is a GSM. They have different radios and partitions. Since it is a Sprint phone, you need to make sure you only put Sprint compatablile software on your phone, if you don't you will end up bricked. You might find more resources to help you at the Sprint HTC One forum. This forum is primarily for the GSM variants. I don't know which RUU you ran but you might want to find out what is really on your phone by running a fastboot getvar all on your phone. It will tell you what hboot, firmware, security, etc. Depending on your status, you can only flash certain RUU's.
Thank you very much for the info. Problem is, I was unable to even try using an RUU because it gives me the error that the phone is not even connected to the computer..
EvanLovesToast said:
Thank you very much for the info. Problem is, I was unable to even try using an RUU because it gives me the error that the phone is not even connected to the computer..
Click to expand...
Click to collapse
Check nkk71's post the first three or four questions may help you out. But like I said, you really need to go to the Sprint forum and post your questions there because what works for one variant may not work for the other variants.
I wrote a brief thread regarding my phone before...
I'll just give the details:
I'm the second owner, phone died while updating.
Phone was bootloader unlocked, and with TWRP recovery.
As such, baseband and IMEI info are missing, I have the original IMEI but, no efs backup or anything.
Any ideas? I've tried to re-install factory stock via both Skipsoft Toolkit and another Toolkit [Yes, I realize this is no help, now]
I've heard restoring another EFS from another phone may work...? I don't know though, I have two Nexus 5's and I can pull an EFS just to try to get back my original IMEI or I've read EFS Pro could help but, again I'm quite lost and just need a hand here.
Thanks.
Ive been an active user on this forum and the rules is that you cant discuss changing the imei here, because its illegal in many countries
Skickat från min Nexus 6 via Tapatalk
No changing!
I'm not discussing changing anything, I just want to repair my missing imei!
It was lost and I can't get a signal on any carrier without one.
I have my original IMEI and just want to restore it.
RedHazy said:
I'm not discussing changing anything, I just want to repair my missing imei!
It was lost and I can't get a signal on any carrier without one.
I have my original IMEI and just want to restore it.
Click to expand...
Click to collapse
here's a silly question.. how did you lose your imei? its not an issue on the n6 like earlier nexus phones, people just dont accidentally lose their imei, or their efs., unless they are restoring a nandroid from another phone, that has their efs backed up also..
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Sidenote: I did mess around with Titanium Backup but, I don't see that erasing my IMEI.
RedHazy said:
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Click to expand...
Click to collapse
If know the IEMI for your device there are threads on XDA that may restore it. If don't know the original IEMI you are dead in the water from the get go.
RedHazy said:
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Click to expand...
Click to collapse
i dont think that you are a criminal, seriously. i was just curious, as on the n5 and n4 that happens often. it really does happen very rarely on a n6. i think the phone dying while updating might of done it. if your bootloader is still unlocked, flashing the factory image might help you. but you will have to do it right, via fastboot while youre in the bootloader. dont use any toolkits, seriously!
I do appreciate the help, I'm going to try flashing the factory image right image see if that helps. Fingers crossed, I'll update with my results. prdog1, you wouldn't happen to know of those threads at all, in case of failure with my factory image.
Thanks, I do appreciate the suggestions. I want to fix this for me and whomever has any issues in the future.
RedHazy said:
I do appreciate the help, I'm going to try flashing the factory image right image see if that helps. Fingers crossed, I'll update with my results. prdog1, you wouldn't happen to know of those threads at all, in case of failure with my factory image.
Thanks, I do appreciate the suggestions. I want to fix this for me and whomever has any issues in the future.
Click to expand...
Click to collapse
heres some instructions, dont lock tbe bootloader after, just follow the flashing the factory image instruction. and if tou run into trouble, let us know, so we can help you http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Some VERY curious thoughts! I wasn't paying much attention until after losing my IMEI but, I've noticed a few things! For anyone that has lost an IMEI on your Nexus 6 in you scroll through your bootloader and go to "Barcodes" option, your IMEI is there! Anywho, back to my dilema.
I'm on 5.0.1 LRX22C
Now when re-flashing stock I noticed it would end up failed every time, with flash all or individually flashing items.
I noticed that my bootloader is 71.08 and 5.0.1 is 71.05 can anyone tell me which is 71.08 as there are three 5.1.0 stocks and I want to have the right one that corresponds to 71.08 bootloader.
For further help my full baseband on my phone is D4.0-9625-02.55.04 which incidentally belongs to 5.0.1, I'm thinking this mismatch may be one of my issues.
And thanks, simms22 for the guide, I'm downloading 5.1.0 right now. I'll keep consistent updates!
RedHazy said:
Some VERY curious thoughts! I wasn't paying much attention until after losing my IMEI but, I've noticed a few things! For anyone that has lost an IMEI on your Nexus 6 in you scroll through your bootloader and go to "Barcodes" option, your IMEI is there! Anywho, back to my dilema.
I'm on 5.0.1 LRX22C
Now when re-flashing stock I noticed it would end up failed every time, with flash all or individually flashing items.
I noticed that my bootloader is 71.08 and 5.0.1 is 71.05 can anyone tell me which is 71.08 as there are three 5.1.0 stocks and I want to have the right one that corresponds to 71.08 bootloader.
For further help my full baseband on my phone is D4.0-9625-02.55.04 which incidentally belongs to 5.0.1, I'm thinking this mismatch may be one of my issues.
And thanks, simms22 for the guide, I'm downloading 5.1.0 right now. I'll keep consistent updates!
Click to expand...
Click to collapse
flash 5.1.1, its the latest. and when you flash a factory image, itll replace the bootloader with whats included in the factory image. oh, btw, do not use flash-all, it wont work, its broken. flash the separate image files individually.
Fingers crossed!
simms22 said:
flash 5.1.1, its the latest. and when you flash a factory image, itll replace the bootloader with whats included in the factory image. oh, btw, do not use flash-all, it wont work, its broken. flash the separate image files individually.
Click to expand...
Click to collapse
Flashed 5.1.1, fingers crossed. It's been about 27-ish minutes and it's still loading the first boot!
UPDATE: I'm at an hour now, waiting for first boot. Doesn't seem to be a bootloop, any ideas
UPDATE: An hour and a half, still booting.... may need to try something else.
RedHazy said:
Flashed 5.1.1, fingers crossed. It's been about 27-ish minutes and it's still loading the first boot!
UPDATE: I'm at an hour now, waiting for first boot. Doesn't seem to be a bootloop, any ideas
UPDATE: An hour and a half, still booting.... may need to try something else.
Click to expand...
Click to collapse
wipe the phone, factory reset i mean
(sorry for getting back so late)
The same thing just happened to me, I had Cyanogenmod 12.1 on my phone, it was a nightly that I did on the 27th of last month. Like two days ago around noon, the phone was charging and it just lost all signal so I rebooted the phone and still the same thing, on the top it said that the phone had no sim card inserted. So I powered off the phone and removed the sim card and started the phone then I powered off and inserted the sim card and nothing, I updated to the newest nightly and nothing. Then I wiped the whole phone and flashed the newest nexus 6 factory image for t-mobile and still nothing. The thing that sucks is that I did backup my efs partition but I just updated the pc to windows 10 and I deleted the old.windows files so I am out of luck. I'm planning on taking it to T-Mobile and hopefully I can get a new one or get this one fixed. I hope you find a fix.
droid4lif3 said:
The same thing just happened to me, I had Cyanogenmod 12.1 on my phone, it was a nightly that I did on the 27th of last month. Like two days ago around noon, the phone was charging and it just lost all signal so I rebooted the phone and still the same thing, on the top it said that the phone had no sim card inserted. So I powered off the phone and removed the sim card and started the phone then I powered off and inserted the sim card and nothing, I updated to the newest nightly and nothing. Then I wiped the whole phone and flashed the newest nexus 6 factory image for t-mobile and still nothing. The thing that sucks is that I did backup my efs partition but I just updated the pc to windows 10 and I deleted the old.windows files so I am out of luck. I'm planning on taking it to T-Mobile and hopefully I can get a new one or get this one fixed. I hope you find a fix.
Click to expand...
Click to collapse
That doesn't mean your IMEI is broken or missing. You made no mention of checking it in the about phone section or in the dialer by input *#06#. It's likely that your SIM card is just broken. The IMEI doesn't just wipe itself out.
---------- Post added at 05:12 AM ---------- Previous post was at 05:07 AM ----------
The same goes for the OP. I see few people claiming that root, TWRP or failing an install of a ROM wiped out their IMEI. Yet none take into account that maybe their SIM is broken, or the phone may be flagged, etc. Especially when one is not the first owner of the device.
I'm telling you guys that literally none of those things mess with the IMEI and all things stated lead me to believe that it is not an issue.
graydiggy said:
That doesn't mean your IMEI is broken or missing. You made no mention of checking it in the about phone section or in the dialer by input *#06#. It's likely that your SIM card is just broken. The IMEI doesn't just wipe itself out.
---------- Post added at 05:12 AM ---------- Previous post was at 05:07 AM ----------
The same goes for the OP. I see few people claiming that root, TWRP or failing an install of a ROM wiped out their IMEI. Yet none take into account that maybe their SIM is broken, or the phone may be flagged, etc. Especially when one is not the first owner of the device.
I'm telling you guys that literally none of those things mess with the IMEI and all things stated lead me to believe that it is not an issue.
Click to expand...
Click to collapse
The IMEI is stored in the CID partition. The CID is a small datablock containing the processor UID, Channel ID (different CID), a bootloader unlock flag, and IMEI. The CID is unique to each device, and controls several aspects of the device. This datablock has a signature on it so that your device information cannot be modified. Should you corrupt this partition, you will lose your IMEI, and the ability to unlock your bootloader. This is the only likely scenario in which you lost your IMEI. If you boot into your bootloader, you may see an error similar to
Code:
CID Datablock Error! 0xDEAD
otherwise I'm going to assume that is still intact. The IMEI has not been stored in the EFS for many years now. Check your CID on the device and make sure it's not 0xDEAD.
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------
Hi how can I check if the CID has been corrupted? I recently locked my bootloader luckily I had a custom recovery and was able to flash a rom and get into the developer settings to enable oem unlock and I unlocked it again.
droid4lif3 said:
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
Click to expand...
Click to collapse
Did you seriously just ask an iPhone question? ???
Seriously though, bring it back to T-Mobile.
Lol, no, I knew I shouldn't of put that she had a iPhone 6S, now I will never be helped. I am just saying that I used a different sim card to make sure that it wasn't the sim card that was messed up.
droid4lif3 said:
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------
Hi how can I check if the CID has been corrupted? I recently locked my bootloader luckily I had a custom recovery and was able to flash a rom and get into the developer settings to enable oem unlock and I unlocked it again.
Click to expand...
Click to collapse
You can check by running the command
Code:
fastboot getvar all
in fastboot/bootloader mode.
You should see something like this:
Code:
(bootloader) cid: 0x00DE
(bootloader) channelid: 0x00
The CID should be 0x00DE if it is not corrupt.
Ok, Ladies and Gentleman I need some deep thought processing here for some help with a Motorola Nexus 6. In brief here is what the problem is, a while back when flashing Pure Nexus rom, I experienced a loss of my IMEI. I can restore my IMEI but if and when I do, I lose any 4g and LTE connectivity. The phone functions in 3g with data and phone etc... just slow as molasses but if I restore my IMEI to the one that doesn't show up my IMEI correctly I get back LTE/4g and all works fine also. I've tried going all the way back to the original firmware which was saved to computer and restoring it. Same thing, I have IMEI but no LTE/4g. restore bad efs and get LTE/4g back. I've tried going through all the factory firmware's and flashing by ADB and or TWRP and nothing firmware wise will allow me to restore the IMEI and have LTE/4g signal. If I restore the bad efs and get OOOOOOOO for IMEI when using the *#06# on any firmware version, I regain LTE/4g functioning! I am using Pure Nexus 7.1 now and can still see the 00000000 as a IMEI, if I restore my efs and get IMEI back showing correctly, no LTE/4g signal! My phone can only function as it should as long as the IMEI doesn't show correctly! I have tried just flashing base bands and other segments of any rom and still the problem persist! I have even tried restoring an EFS from another nexus 6 and still no help. It's not the sims because I've tried AT&T sims and Verizon sims from other phones and it does the same thing! I've tried flashing with a sims in the phone and without. Any ideas??? It's like somehow a correlating segment of a file is not being recognized when the correct IMEI is present, like some thing some where in the efs, IMEI, and radio are not taking to each other so to speak, unless it shows the zero's! Brain waves come on and help me out here!!
Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)
jbaumert said:
Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)
Click to expand...
Click to collapse
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!
TheWacoKid said:
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!
Click to expand...
Click to collapse
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.
jbaumert said:
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.
Click to expand...
Click to collapse
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!
Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.
Dixon Butz said:
Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.
Click to expand...
Click to collapse
Thanks! Ok, Itried that, restored my IMEI, "reset APN to default" Tried Carrier reset ##3282# and it says "NO Cellular Network" even though I am showing my network and 3G. So, I rebooted and same thing, went to PRL and tried to update and it says "update error" but it will refresh!
TheWacoKid said:
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!
Click to expand...
Click to collapse
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.
admiralspeedy said:
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.
Click to expand...
Click to collapse
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!
TheWacoKid said:
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!
Click to expand...
Click to collapse
You know some magic we don't? There is no way you've flashed a ROM with ADB...
@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.
dahawthorne said:
@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.
Click to expand...
Click to collapse
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.
admiralspeedy said:
You know some magic we don't? There is no way you've flashed a ROM with ADB...
Click to expand...
Click to collapse
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??
Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
TheWacoKid said:
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??
Click to expand...
Click to collapse
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.
admiralspeedy said:
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.
Click to expand...
Click to collapse
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup
rignfool said:
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup
Click to expand...
Click to collapse
No, you can use ADB sideload to flash a ROM which requires you to be in the recovery. Standard ADB cannot be used to flash a ROM.
admiralspeedy said:
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.
Click to expand...
Click to collapse
Amazing to any one with half a brain how you a Troll can think from typed response that someone is yelling, swinging, snarky and rude but your the one with an attitude that is all the above because like I said your a childish troll! I can't believe this site would even allow someone like you to be a member paid or otherwise! Your attitude is all your own and based on your own weak assumptions! Now go back to playing with your legos!
drmuruga said:
Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.
TheWacoKid said:
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.
Click to expand...
Click to collapse
So was there a solution? The thread just ended. I also have this problem but I'm no where as technical as thewacokid.
But I do know how to follow steps
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.