Related
I stupidly wrote down the wrong sim unlock code given to me by ATT on my phone and I guess I entered the wrong code too many times. I called ATT tech support and they said that my phone is locked permanently ATT now.
Is there a fix around this or am I screwed?
Thx
he.spinal said:
I stupidly wrote down the wrong sim unlock code given to me by ATT on my phone and I guess I entered the wrong code too many times. I called ATT tech support and they said that my phone is locked permanently ATT now.
Is there a fix around this or am I screwed?
Thx
Click to expand...
Click to collapse
As far as I know, you are SOL and is locked permanently to ATT, unless theres a way to unlock it via the service menu after a code has been inputted wrong.
Go to Cellunlocker.net and talk to someone in support about getting a code that unlocks your sim-locked status. It's not the code to unlock your phone, it's the code that resets the perma-lock state of the phone.
I guess i am SOL i called cell unlocker and they said they dint have the software to do it
Did you try the method listed for unlocking your phone from the service menus - without an unlock code?
I have not seen it explained, but it appears to me that by disabling the SHA256 network lock, you are basically getting rid of the requirement for the unlock code that is cryptographically dependent on the IMEI.
I did it on my AT&T phone and plopped in a T-mo sim and it worked fine:
http://forum.xda-developers.com/showthread.php?t=2285431
I am not responsible for anything you may mess up though.
he.spinal said:
I guess i am SOL i called cell unlocker and they said they dint have the software to do it
Click to expand...
Click to collapse
You might have one other option that I know of that might work, might not work, or might make things worse. It is the "Free unlock" menu method in the general section. I am assuming you haven't tried it already. Normally I tell people to stay clear of it because of the slim chance it could screw your phone up, but in your case, I'd say it's already screwed up.
Follow the directions and see if restoring your "Golden backup" (NV restore) resets the cell locks on your phone. You can also try thing like turning SHA256 "On", or "Off" and see if it makes a difference. The reason the free unlock method works for some and not others all depends on what info resides in your phones NV backup. For some, it restores full phone functionality without network locks (sim unlocked), for others, it restores exactly what is already on the phone's NV memory (still network locked), and for others, it restores a backup that screws the phone up. There is a slim possibility that if you restore the NV data via the hidden menu, you might restore your phones original sim locked state and then be able to use the code with SHA256ON or maybe Off.
The risk you take if you try it is completely yours.
It might help, it might not help, or it could make it worse. Good luck.
Would flashing back to stock rom work? I am still fairly new with android devices coming from iphones so i dont want to mess with it if it has absolutely no chance of working. The phone is still working fine just can't unlock it.
Thx for the suggestions tho
he.spinal said:
Would flashing back to stock rom work? I am still fairly new with android devices coming from iphones so i dont want to mess with it if it has absolutely no chance of working. The phone is still working fine just can't unlock it.
Thx for the suggestions tho
Click to expand...
Click to collapse
Flashing back to stock is not going to cure your problem. You're kind of hosed at this point. Scott's suggestion is probably your best bet, BUT you could end up with no phone working at all. If you can still get phone service I'd leave it as is and give up ever unlocking.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
---------- Post added at 07:19 PM ---------- Previous post was at 07:01 PM ----------
TO ANYONE WHO IS FOLLOWING THIS THREAD, PLEASE DON'T DO ANY THING TO YOUR PHONE BECAUSE YOU THINK IT MAY BE COOL. Really know what your doing and why before you do try it. You can really mess up your phone. There a lot of good info in this forum, use it. And take your time, read, study, and read some more.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
about permanent unlock!!
hello buddy , did you found any solution for the permanently lock to att? im having the same problem! thanks
he.spinal said:
Would flashing back to stock rom work? I am still fairly new with android devices coming from iphones so i dont want to mess with it if it has absolutely no chance of working. The phone is still working fine just can't unlock it.
Thx for the suggestions tho
Click to expand...
Click to collapse
I wasn't able to unlock my AT&T GS4 via the service menu methods, nor with an unlock code I bought online. I was finally able to unlock it via the USB program at FastGSM. It seemed kind of shady but it worked for me...
Zoide_ said:
I wasn't able to unlock my AT&T GS4 via the service menu methods, nor with an unlock code I bought online. I was finally able to unlock it via the USB program at FastGSM. It seemed kind of shady but it worked for me...
Click to expand...
Click to collapse
Which Version worked for you? Their download page has several but none of them say Fire Phone.
I bought this phone for my mom and sent her the unlock code... but she missed it 5 times.. LOL now it is permanently locked to At&t
ZeroHart said:
Which Version worked for you? Their download page has several but none of them say Fire Phone.
I bought this phone for my mom and sent her the unlock code... but she missed it 5 times.. LOL now it is permanently locked to At&t
Click to expand...
Click to collapse
Sorry, it was so long ago I don't know. The Paypal receipt says "Samsung i337 Unlocking Software", if that helps.
Zoide_ said:
I wasn't able to unlock my AT&T GS4 via the service menu methods, nor with an unlock code I bought online. I was finally able to unlock it via the USB program at FastGSM. It seemed kind of shady but it worked for me...
Click to expand...
Click to collapse
Zoide_ said:
Sorry, it was so long ago I don't know. The Paypal receipt says "Samsung i337 Unlocking Software", if that helps.
Click to expand...
Click to collapse
No Problem, Thanks
The Free Google Drive space promotion was recently increased from 65GB to 100GB. So, there is more reason than ever to get this great offer.
If however, like me, you rooted your phone and found out you couldn't redeem it... and also read some people claiming that HTC wouldn't provide a code to redeem the offer because you had unlocked the bootloader... Follow the steps below to get this offer without dealing at all with HTC.
There are two primary obstacles to redeeming this offer. Since you rooted your phone, you have unlocked the bootloader. Even if you have relocked it using fastboot oem lock, this will still prevent the Drive App from displaying the offer screeen. The problem is that when you use fastboot oem lock, you are changing the status of the bootloader to ***RELOCKED*** . What you need is a factory default bootloader lock, which displays as ***LOCKED*** on the hBoot screen.
Plus, if you attain S-Off after unlocking your bootloader following HTCDev, it is very possible you will have a
*** TAMPERED ***
banner on your hboot screen. This must be removed as well.
HUGE thanks to Scotty1223 who first shared the methods for removing the TAMPERED banner and locking the bootloader to factory default several months ago. I am just consolidating those steps plus some other minor info into a sequential series of steps in one place for convenience.
These steps presume you have ADB installed, and have not changed your CID.
STEPS to GET TO STOCK FOR PURPOSES OF THE GOOGLE DRIVE PROMO.
1. Make a Nandroid backup using TWRP or CWM.
2. Get S-Off.
Use Sunshine or some other method to get S-Off. Link to Sunshine S-Off apk
3. Remove ***TAMPERED*** Banner.
If you have a ***TAMPERED*** banner on your hboot screen, follow the steps below (thanks to Scotty1223 for sharing this method). ADB must be installed!!! You can go to the first step of this thread to install a compact version
Connect your phone to your PC. Open up a terminal (as administrator in Windows...or as root in Linux) and cd to the adb directory (which contains fastboot, etc.).
Enter the following:
adb devices
You should see your device's serial number appear on the screen... If so, you are all good. If not, please check your ADB install..... there are many many guides to getting this set up.
Now we are going into the ADB Shell, which is like a terminal emulator from the OS on your phone. Enter the following:
adb shell
to enter the shell. You will be presented with a prompt... most likely it will be
[email protected]_m8: / $
Enter the following command to get root in ADB
su
[Very important note: You need this for superuser privileges on your phone... Make sure to wait for a prompt that looks like the following:
[email protected]_m8:/ #.
(if you are getting something different, don't worry... Just make sure there is a '#' at the end of the prompt)
If it hangs and only shows the first prompt like this:
[email protected]_m8: / $ <== note the '$' at the end
Then hit return in your terminal window on your PC (whether in windows or linux). It may exit automatically from the shell.
If this happens, it is because you have not used adb shell yet and have SuperSU (or Superuser) on default settings, which is to prompt the first time an app asks for root privileges. You should see a toast/dialog box on your phone that requests superuser permissions for "ADB Shell". Grant them, and then enter adb shell again from the terminal window on your PC. Now the root prompt (in red above) should show up in the terminal window.]
Now copy the line below and paste it into the terminal window on your PC at the root prompt:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
You should get something like this in response:
ock/mmcblk0p6 bs=1 seek=5314564 <
1+0 records in
1+0 records out
1 bytes transferred in 0.007 secs (142 bytes/sec)
If not, double check that you copied the above line correctly, that there are no spaces before the 'echo', and enter it again.
Then enter:
adb reboot bootloader
This will boot into hboot. Confirm that the ***TAMPERED*** is in fact not showing on the hboot screen.
Back in your terminal on your PC, enter:
fastboot reboot
to reboot the phone.
4. Lock the bootloader.
To lock the bootloader the correct way, you must follow the steps below. As far as I have determined, it is the same for all carriers of the HTC One M8. Again, a big thanks to Scotty1223 for this very cool route to locking the bootloader.
Like step 3, above, we are going into the ADB Shell, which is like a terminal emulator from the OS on your phone. If you do not have ADB installed on your PC, there are ample resources all over the internet for getting this installed...
Enter the following:
adb shell
to enter the shell. You will be presented with a prompt... most likely it will be
[email protected]_m8: / $
Enter the following command to get root in ADB
su
[IMPORTANT NOTE: See warning under Step 3 about getting a root prompt]
Then copy and paste this into your terminal on your PC:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
And lastly:
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Confirm that your bootloader shows a ***LOCKED*** banner (and not ***RELOCKED***).
Back in your terminal on your PC, enter:
fastboot reboot
to reboot the phone
5. Getting to Stock.
****If you have NOT touched the stock Rom at all, nor deleted any system apps (essentially you have merely rooted and flashed a stock recovery) you can skip this step (no need to perform either step 5a or 5b). Just Reboot and finish with step 7.
To get the Google Drive storage you need to be running near to stock.. This means you need the stock firmware, and the stock Sense Rom (including all system applications). Many people will not have to worry about firmware or system applications. However, if you switched to an AOSP/AOKP Rom or a different kernel, then you do. Depending on your situation, follow step 5a OR step 5b.
5a. If you have switched to an AOSP/AOKP Rom, and are unsure about your firmware being correct and/or stock, an easy way to get all of the components which make up full stock (stock rom, stock firmware, stock hboot) is to flash an RUU from your carrier (see M8 forum for your carrier...there should be a roll-up thread with links and instructions to flash an RUU. NOTE: For anyone reading this thread that somehow managed to lock the bootloader without S-off, It is highly recommended NOT TO FLASH AN RUU WITH BOOTLOADER LOCKED AND S-ON. You must have S-OFF to flash an RUU with a locked bootloader).
5b. If you don't have to worry about firmware, but have deleted several system apps or otherwise altered the stock Rom, then you should restore a stock nandroid or find and flash a stock Rom. You should again go to the HTC One M8 forum for your carrier to get these items. If restoring a stock nandroid backup, make sure you have made a backup (as instructed in Step 1) so you have the right folder structure (whether you are using TWRP stock nandroid or a CWM stock nandroid) on the SD in which to place the stock nandroid.
6. Reboot.
7. REDEEM OFFER!
Go to the Play Store and uninstall any and all Google Drive updates (I did not have any, but in some cases Drive may have updated while you were rooted). After uninstalling any Drive updates, you should be able to go into the Drive app, and see the promo screen immediately and redeem the promo. If you do not see any screen with the offer, select "Product Tour" from the dropdown menu and go through the various "tour" screens. At the end it will show you the offer—it will probably be for 65GB. After you accept the offer however, it will say "an extra 50GB has been added to your Google Drive storage (so 65GB + 50GB = 115GB)
Again a big thank you to Scott1223 for the methods which allow us to go back and get this offer!!!
....and also thank you to jshamlet, kabuts, rcharliesam, phil.culler for helping me in some other threads!!!!
And exocetdj for his awesome help!!!!!!!
Please comment!
extremely well put out guide mate :good:
Maybe worth merging this with other thread so people have it all in one place?
One post for original method and then the next for this one? both brilliantly relevant
exocetdj said:
extremely well put out guide mate :good:
Maybe worth merging this with other thread so people have it all in one place?
One post for original method and then the next for this one? both brilliantly relevant
Click to expand...
Click to collapse
Is there a guide to get the Google Drive offer? I only saw various threads discussing it and threads explaining how to get back to stock...or Scotty1223's method to lock the bootloader.
I wouldn't have compiled a complete guide if there was one already. I hope I didn't miss it.
I started one in the other thread...but it was just a post in the third page of a thread discussing the Drive offer and discussing ways to get it (like contacting HTC, etc. (But thank you for reminding me-- I really should link that post to this thread since the guide in that post is old).
Let me know where the other guide is and I will try to get them merged or linked or something.
syntropic said:
Is there a guide to get the Google Drive offer? I only saw various threads discussing it and threads explaining how to get back to stock...or Scotty1223's method to lock the bootloader.
I wouldn't have compiled a complete guide if there was one already. I hope I didn't miss it.
I started one in the other thread...but it was just a post in the third page of a thread discussing the Drive offer and discussing ways to get it (like contacting HTC, etc. (But thank you for reminding me-- I really should link that post to this thread since the guide in that post is old).
Let me know where the other guide is and I will try to get them merged or linked or something.
Click to expand...
Click to collapse
HERE is is
They are about the same thing, may be better if everything is in the same place. have a word with the OP and see what he thinks then ask a mod, they should be able to help out
I got the 'not applicable due to tampering' error, but not going to bother with the hassle of relocking the bootloader. I probably would be interested in this offer if my BT Broadband wasn't so utterly dreadful that uploading anything takes a lifetime.
The offer's two years would be up by the time I'd finished uploading this year's holiday snaps
exocetdj said:
HERE is is
They are about the same thing, may be better if everything is in the same place. have a word with the OP and see what he thinks then ask a mod, they should be able to help out
Click to expand...
Click to collapse
That's just a thread debating ways some people were able to get it... Posts point to threads to lock the bootloader, and other posts state the tampered banner needs to be removed but no links.... It's a mess for anyone that doesn't understand what all needs to be done, nor how to do it.
That's why I compiled the thread here...it takes all the endless discussions, and just condenses it into a straightforward sequence of steps to get it.
syntropic said:
That's just a thread debating ways some people were able to get it... Posts point to threads to lock the bootloader, and other posts state the tampered banner needs to be removed but no links.... It's a mess for anyone that doesn't understand what all needs to be done, nor how to do it.
That's why I compiled the thread here...it takes all the endless discussions, and just condenses it into a straightforward sequence of steps to get it.
Click to expand...
Click to collapse
Fair point, as u were soldier!!!! :good:
Save yourself all this time/effort. Just chat with HTC support on their website. Takes less than 5 minutes and they email you a link to activate the extra space. I did this for both my phone and my wife's phone, when they had been unlocked for months already.
I was able to redeem the offer rather quickly, followed your directions, installed a stock rom, redeemed the promotion and nandroid back to Venom within 30 minutes. Mostly because I was reading like an idiot (totally exhausted from work.)
Thanks.
nomisunrider said:
Save yourself all this time/effort. Just chat with HTC support on their website. Takes less than 5 minutes and they email you a link to activate the extra space. I did this for both my phone and my wife's phone, when they had been unlocked for months already.
Click to expand...
Click to collapse
I think its luck of the draw... when this happened to me... I read everywhere, and out of everyone I spoke to who had to go to HTC because they couldn't redeem it through the Drive app, about 15% of them chatted with an HTC rep who either: (a) never asked them a single question and just sent them an email with a promo code link; (b) asked them to confirm that the caller "has not unlocked the bootloader or rooted their phone" (in which case the caller would need to lie and say "no sir! I would never do something foolish like that" and then get the email with the promo code), or (c) the rep asked them their IMEI, then said in a wry voice "I see you requested a bootloader unlock token...." (almost as if the rep was leading the caller to admit he unlocked the bootloader—and if he did...no promo).
The other 85% (who for the most part unlocked their bootloader using HTCDev) could not get the Drive deal because HTC had it on file they requested an unlock token... and in most of these cases, HTC was resolute on the offer being ineligible for those who unlocked their BL.
Given those odds—and the fear of choking if I called/chatted with HTC and had to lie—I opted to take the above steps and create a guide for anyone who needed it. Trust me... I would not have bothered to make it if it sounded like it was simple matter of contacting HTC.
I was debating going through all of this to get the offer since I'm cheap and don't want to pay for dropbox right now.
I did the online chat, and they didn't ask me any questions. I just said I tried to do it over crappy wifi connection early and it failed and now it won't redeem.
I have a Verizon edition however, so I can't unlock with HTC dev which is likely why I didn't get asked questions. My backup was to say something stupid like "unlock....? Like with my SIM code? Or the lockscreen code? Yea, I did that."
Fortunately they didn't ask and were really nice. But thanks for this guide; i was about to switch ROMs so I had just made a nandroid and was about to try and get it to redeem the hard way.
If you have Verizon or used Sunshine (or similar) I would try their support first.
Thanks very much for taking the time to write this guide.
In my case I was also just able to get in touch with HTC via chat and give them my IMEI, no need to relock, revert to stock etc.
I lost my 65gb free storage. Is there anyway to recover it?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
syntropic said:
I think its luck of the draw... when this happened to me... I read everywhere, and out of everyone I spoke to who had to go to HTC because they couldn't redeem it through the Drive app, about 15% of them chatted with an HTC rep who either: (a) never asked them a single question and just sent them an email with a promo code link; (b) asked them to confirm that the caller "has not unlocked the bootloader or rooted their phone" (in which case the caller would need to lie and say "no sir! I would never do something foolish like that" and then get the email with the promo code), or (c) the rep asked them their IMEI, then said in a wry voice "I see you requested a bootloader unlock token...." (almost as if the rep was leading the caller to admit he unlocked the bootloader—and if he did...no promo).
The other 85% (who for the most part unlocked their bootloader using HTCDev) could not get the Drive deal because HTC had it on file they requested an unlock token... and in most of these cases, HTC was resolute on the offer being ineligible for those who unlocked their BL.
Given those odds—and the fear of choking if I called/chatted with HTC and had to lie—I opted to take the above steps and create a guide for anyone who needed it. Trust me... I would not have bothered to make it if it sounded like it was simple matter of contacting HTC.
Click to expand...
Click to collapse
Interesting. I was one of those who unlocked the bootloader through HTCDev. I called HTC, the rep asked for my IMEI number, and I got the activation email within 5 minutes. No mention of unlocked bootloaders. I guess it really depends on how laid back the rep is.
adotkdotjh said:
Interesting. I was one of those who unlocked the bootloader through HTCDev. I called HTC, the rep asked for my IMEI number, and I got the activation email within 5 minutes. No mention of unlocked bootloaders. I guess it really depends on how laid back the rep is.
Click to expand...
Click to collapse
Who knows too if there has been an internal policy change? HTC's website (I can't remember where) states that you are not eligible for the storage if you unlocked your bootloader. About a month ago, the threads I saw on this topic were more of a warning to get it first and then root or else you can't get it.
But since this phone has been out for 6 months and a lot of upfront costs are reduced (for me, I paid $0 to get it under TMO), a lot more people are getting this phone.
Plus Google changed the promo from 65GB to 100GB about a month ago...so it's possible that HTC has encountered higher-than-expected number of purchasers who unlocked the bootloader and also want the Google Drive storage. And maybe recently they have decided relax their restrictions... I am sure that those who were told no were angry. I know that had I ended up calling/chatting with HTC and they said "sorry, you unlocked your bootloader", I would have been very upset.
syntropic said:
Who knows too if there has been an internal policy change? HTC's website (I can't remember where) states that you are not eligible for the storage if you unlocked your bootloader. About a month ago, the threads I saw on this topic were more of a warning to get it first and then root or else you can't get it.
But since this phone has been out for 6 months and a lot of upfront costs are reduced (for me, I paid $0 to get it under TMO), a lot more people are getting this phone.
Plus Google changed the promo from 65GB to 100GB about a month ago...so it's possible that HTC has encountered higher-than-expected number of purchasers who unlocked the bootloader and also want the Google Drive storage. And maybe recently they have decided relax their restrictions... I am sure that those who were told no were angry. I know that had I ended up calling/chatting with HTC and they said "sorry, you unlocked your bootloader", I would have been very upset.
Click to expand...
Click to collapse
Yeah policy change could definitely happened. Then again, I was dealing with HTC Canada, so that may have been the difference. I didn't even know the offer was changed to 100GB. Htc advantage website still said 65gb when I called htc to redeem the offer several weeks ago, and when I saw they gave me 100gb, I thought the extra space was their way of saying "sorry for trouble".
Just got my 100gb free through HTC chat. Very easy just needed my name phone number and email address :good:
Congratulations!
+100GB
added for 2 years
Go to Google Drive
But this guide is very much appreciated i was just hoping I wouldn't have to go this route. Thank you very much for taking the time to share
Less work necessary for me
i followed your great guide to redeem the Drive's extra space successfully however i only had to do the:
TEMPERED OUT Removed
UNLOCKED BOOTLOADER Removed
Running Viper without many stock apps
So i avoided all the returning to stock rom and nandroid backup.
Thanks again man
Hello,
thanks for this write-up! All you need to do is remove TAMPERED flag and LOCK bootloader. There is no need to go back to stock
Thanks one more time!
I was also able to get the offer after contacting the htc support via the live chat.
I didn't bothered with getting back to stock or anything - I just pinged them, was asked for my serial etc. and got an offer email with my 100GB.
No word about the htc dev token I have requested etc. - after about 3 minutes I received email stating that:
Based on your ticket ##TicketNumber## we have increased the storage space for your Google Drive account. In order to access the additional space, please visit the website via the link listed below.
and with the activation link...
---------- Post added at 09:21 PM ---------- Previous post was at 09:21 PM ----------
pastynko said:
Hello,
thanks for this write-up! All you need to do is remove TAMPERED flag and LOCK bootloader. There is no need to go back to stock
Thanks one more time!
Click to expand...
Click to collapse
True - on my M7, it was all about the locked bootloader....
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
.G33K said:
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
Click to expand...
Click to collapse
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Heisenberg said:
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Click to expand...
Click to collapse
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
.G33K said:
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
Click to expand...
Click to collapse
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Heisenberg said:
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Click to expand...
Click to collapse
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
.G33K said:
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
Click to expand...
Click to collapse
Did you format userdata? It's worth a try.
Heisenberg said:
Did you format userdata? It's worth a try.
Click to expand...
Click to collapse
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
.G33K said:
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
Click to expand...
Click to collapse
It probably won't work, any build should work, but it's worth a try. If that fails I can only suggest flashing TWRP recovery and trying to flash a custom ROM to see if that works.
So long as you have the bootloader.img and radio.img files, you can try to format boot as well, however Heisenberg may yell at me for even typing that
I had a similar issue - bootloop, but it was getting to the boot animation for about 3 seconds, then rebooting. When I formatted all the areas before flashing them from the stock image, it allowed me to boot up as normal. Stable ever since.
Hi There,
Coming back to the issue, I have just downloaded the build that was suggested by "Heisenberg" and tried it. It was still the same, as in the Google logo keep on flashing but the android bot just appeared once with the logo. But still there not luck as the device stays with Google logo but does nothing.
However, I'm able to see the device on fastboot. Nevertheless, I cannot seem to use adb command.. it doesn't even list on devices. Does that mean the adb isn't working?
Meanwhile, all my fastboot commands are working with no issues at all.
EDIT: When I tried the TWRP recovery, I can flash the recover, but I can seem to go to the recovery window at all as the device keep on showing "The device software can't be checked for corruption". When I pass that also the same boot loop.
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
Unfortunately yes. Unless you enabled OEM Unlocking in the developers menu before your phone went sideways you probably have a hard bricked phone. Is it under warranty?
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
TemplesOfSyrinx said:
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
Click to expand...
Click to collapse
Bootloop issues are common on the 6P even with custom ROMs--it just happens to be much more likely you can recover with the custom ROMs installed since the bootloader is unlocked. I think it's a hardware issue with the 6P rather than an OTA issue. It's probably not an accident that Huawei didn't make the Pixels.
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
This happened to my wife's phone, sent back to Bell. Will see what happens.
TemplesOfSyrinx said:
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty on the Nexus 6P. If you are under warranty then just RMA the phone if an OTA bootloops your phone. It's your choice whether to keep the bootloader locked or not but if you keep the bootloader locked it's probably impossible to recover from a bootloop. Google keeps factory images for Nexus and Pixel phones on its website but you can't flash those images with a locked bootloader. Why would they provide the images if using them voided your warranty?
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
What Android version you had on your phone? What's your emmc name and ram name in bootloader? What's the manufacturing date in bootloader?
TemplesOfSyrinx said:
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
Click to expand...
Click to collapse
I think you bought the wrong phone. Nexus devices were never available commercially through carriers and were made for developers and people who like to flash things with their phones. There are ways to use Android Pay with an unlocked bootloader if you are so inclined. You are right that an unlocked bootloader is considered less secure but if you only install apps from Google Play or another trusted source you shouldn't have problems. You can also simply enable allow Oem Unlock in the developer menu. This doesn't actually unlock your bootloader but makes it possible for you to unlock it via fastboot if you get bootlooped and need to flash a factory image to restore. This way you can unlock the bootloader in an emergency but your phone is still secure. I think this should be enabled by default when the phones are shipped. Too many people with locked bootloaders end up with hard bricked phones where the Nexus 6P is concerned. Honestly, you would probably be better off selling your Nexus and getting something else that's more stable and made for people who have no Interest in flashing anything.
Hey guys.
I've managed to find a couple of videos and tutorials on rooting the A1000 (99% of them using KingRoot), but there's absolutely no info on the A1000m. While it's basically the same phone with a bit less memory, it won't root. I've tried pretty much everything I found on the web with no success. And quite frankly I'm scared to keep going, because I can't find the firmware and if I brick this stupid phone I'll probably have to pay for it, because it's not mine. Not a big deal, it's one of the cheapest devices available in my country, but I'd rather find a way to root it or at least keep it in working condition before returning it to it's owner.
Any help on the matter will be greatly appreciated. Even if all you can do is tell me that it's impossible to root. I just need to be sure, before I return it.
topdawg89 said:
Hey guys.
I've managed to find a couple of videos and tutorials on rooting the A1000 (99% of them using KingRoot), but there's absolutely no info on the A1000m. While it's basically the same phone with a bit less memory, it won't root. I've tried pretty much everything I found on the web with no success. And quite frankly I'm scared to keep going, because I can't find the firmware and if I brick this stupid phone I'll probably have to pay for it, because it's not mine. Not a big deal, it's one of the cheapest devices available in my country, but I'd rather find a way to root it or at least keep it in working condition before returning it to it's owner.
Any help on the matter will be greatly appreciated. Even if all you can do is tell me that it's impossible to root. I just need to be sure, before I return it.
Click to expand...
Click to collapse
Just needed to know:
Do you tried KingRoot or skipped it because you were scared?
Tried it. And that's the one that scared me. At first it wouldn't work. Someone told me to give it another try and it said the phone was rooted. But it wasn't. All it did was break the playstore and it wouldn't let me download anything. The phone froze and restarted a couple of times... It was a pain in the ass. And the other app that came with it, King User - it wouldn't go away even after a hard reset. I had to install KingRoot again, try rooting it a couple of times until it said it was successful and then do the unroot procedure in King User to get rid of the app.
In my opinion, KingRoot is a total waste of time. Never used it before, don't plan on doing it in the future.
topdawg89 said:
Tried it. And that's the one that scared me. At first it wouldn't work. Someone told me to give it another try and it said the phone was rooted. But it wasn't. All it did was break the playstore and it wouldn't let me download anything. The phone froze and restarted a couple of times... It was a pain in the ass. And the other app that came with it, King User - it wouldn't go away even after a hard reset. I had to install KingRoot again, try rooting it a couple of times until it said it was successful and then do the unroot procedure in King User to get rid of the app.
In my opinion, KingRoot is a total waste of time. Never used it before, don't plan on doing it in the future.
Click to expand...
Click to collapse
A1000 has older chipset Spreadtrum SC7731 without G mark on the end. your vibe A has half memory and smaler kapacity of battery bad plastiks and dimensions look same on www gsmarena com
ps: kingo root for windows with debuging activate in phone working with A1000 on second try (and another few phones year before), and cpu-z (cpuid) confirm it is root acess
hey, I ve got Lenovo A1000m too but I ve tried many softwares and tutorials but noone goes...Can anyone help me?
A1000m unlock bootloader?
Hey guys
Has anybody managed to unlock the bootloader?the method with Fastboot oem unlock doesn’t work.
Any help?
Thanks
Quick and simple bc after sifting through this website I accidently figured it out. First use the script from this post - https://forum.xda-developers.com/t/oneplus-pure-debloat.4157691/ then check dev options and OEM unlocking should be ungreyed out. Grab your oneplus unlock by running this command - "fastboot oem get_unlock_code" Then go to - https://www.oneplus.com/unlock_token submit your token and serial number and wait exactly one week to the day. Download this tool https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ and you can unlock the bootload with your unlock.bin file. After that whats next is up too you!
I don't know about SIM unlocking, however I did figure out which package specifically enables the toggle for OEM unlocking in the Developer Options.
So I took a look at the debloat thread linked above and I went through the list of packages and I was uninstalling them on my phone one by one until I found the one that enabled the toggle for OEM unlocking in the Developer Options.
When I uninstalled the package com.qualcomm.qti.uim, the toggle for OEM unlocking was no longer greyed out.
That's a great find. Is it enough to simply force-stop the package or does it need to be disabled/uninstalled?
Might try this on the OP9 or OP10 if I get one.
LLStarks said:
That's a great find. Is it enough to simply force-stop the package or does it need to be disabled/uninstalled?
Might try this on the OP9 or OP10 if I get one.
Click to expand...
Click to collapse
I didn't see if force stopping it worked or not so I wouldn't be able to answer that. I just uninstalled it with adb.
Title of tread said sim-unlocking, after reading through, it only mentions bootloader unlocking via the OnePlus website and all in one flashing tool. Yes it may bypassed the carrier restriction for bootloader unlocking, but is the phone actually sim unlocked? As you can use it with another carrier?
But I agree, finding out com.qualcomm.qti.uim being the toggle for bootloader unlock is great find.
I disabled com.qualcomm.qti.uim via ADB myself and while 'OEM Unlocking" is no longer grey and you can enable the option the bootloader for me is still locked. My OnePlus 8T model is through T-Mobile
kevinco1 said:
I disabled com.qualcomm.qti.uim via ADB myself and while 'OEM Unlocking" is no longer grey and you can enable the option the bootloader for me is still locked. My OnePlus 8T model is through T-Mobile
Click to expand...
Click to collapse
gotta complete the whole process homie.. AFTER doing the uninstall or disable of com.qualcomm.qti.uim, then you gotta flip the toggle and then reboot to bootloader. after that you need to run the fastboot command, "fastboot oem get_unlock_code"... copy that code to your clipboard, then go to the Oneplus website, fill out the form and paste that code in the proper field.
After that it does take exactly one week... (to the minute) and you will need to go back to this site and you will see it change to download. Download that file and flash it via fastboot, then confirm you want to unlock and its done!
Now after that you have to remember to NEVER flash a stock firmware via fastboot again, otherwise you will re-lock your bootloader. I cannot confirm whether or not you will be able to, or even need to flash the unlock token again, but in the case of Samsung phones, when you flash the bootloader unlock token, you DO NOT get a second chance. If you unlock it once, and then accidently re-lock via flashing stock, you will be stuck with a locked bl. (EDIT: you CAN flash stock with samsung, as long as the bootloader version isnt changed. If you upgrade the BL then you are stuck!)
(Now theres a simpler way around all this but you must do your research, and look into converting your TMO-US fw to TMO-EU ... this can be done without unlocking the bootloader. And after the conversion, if you disable the OP mentioned file, you can simply toggle, and run the "fastboot oem unlock" command and thats it... no token file needed! And i am in Texas, so i can confirm 100% that ALL of the bands are active and available, and i get 5g with absolutely no problem... In fact my phone runs quicker and gets better battery life on the EU fw. )
Then when your phone is fully paid off, simply flash back to the US fw and you can have them Sim unlock you and you can either go thru the normal unlocking process, or you can go back to the EU... but either way no foul, no harm!
So to get T-Mobile to do it on their end do this.
Go on their site and facebook, keep telling them this. "I'm a developer who can't develop app's on my device, can you please allow my phone to be unlocked." Most will tell you it needs to be paid off, but you quite possibly will get that disgruntled worker or guy who just doesn't care. Took me 5 tries, then the guy I got was like, "okay I'll do it for you!" #boomdone
Social engineering at its finest.
kyanox said:
So to get T-Mobile to do it on their end do this.
Go on their site and facebook, keep telling them this. "I'm a developer who can't develop app's on my device, can you please allow my phone to be unlocked." Most will tell you it needs to be paid off, but you quite possibly will get that disgruntled worker or guy who just doesn't care. Took me 5 tries, then the guy I got was like, "okay I'll do it for you!" #boomdone
Social engineering at its finest.
Click to expand...
Click to collapse
I have had this same issue. I bought the 8T+5G from OnePlus online store TMobile version (because the unlocked versions were sold out). Been back and forth betwee TMobile and OnePlus for 4 days, and OnePlus finally says they nor Tmobile can unlock the device until it has been used on Tmobile's service for 45 days (part of the unlock policy). I knew this, but thought surely someone can help me. OnePlus assured me that the IMEI number does not enter into the system as an unlockable phone until after the 45 days, and that NOBODY can unlock the phone until then... Am I screwed for 40 more days???? This in my opinion is a scam to force people to use a service they may not want.
i am shop in istanbul come to me oneplus 8t 5g t-mobile i ask whole world for simlock no one can and one of customer tell me i can unlock he take device for 3 hour he come back and device unlocked and he tell me i can do anything in oneplus phones i got crazy how he did this ? anyone know how ?
jabe78 said:
I have had this same issue. I bought the 8T+5G from OnePlus online store TMobile version (because the unlocked versions were sold out). Been back and forth betwee TMobile and OnePlus for 4 days, and OnePlus finally says they nor Tmobile can unlock the device until it has been used on Tmobile's service for 45 days (part of the unlock policy). I knew this, but thought surely someone can help me. OnePlus assured me that the IMEI number does not enter into the system as an unlockable phone until after the 45 days, and that NOBODY can unlock the phone until then... Am I screwed for 40 more days???? This in my opinion is a scam to force people to use a service they may not want.
Click to expand...
Click to collapse
Does this still work on the recent 8T phones? Please do keep us updated on your situation. I'm thinking about buying this phone unlock the boot-loader, Sim unlock and get Lineage on it. I don't mind 45 days if they actually unlock it
TommyQuid said:
Does this still work on the recent 8T phones? Please do keep us updated on your situation. I'm thinking about buying this phone unlock the boot-loader, Sim unlock and get Lineage on it. I don't mind 45 days if they actually unlock it
Click to expand...
Click to collapse
Yeah. I'm going to wait it out. Counting down the days I'm chained to T-Mobile (38 left). I actually wanted their service so it isn't an inconvenience, but I hate being forced to do anything, much less wait to do what I wanted to do from day one, which is Flash Roms. I'm looking at Lineage too. So I will update this post once I get to that point. Here's hoping they keep their word, because my 15 day return policy on the phone runs out in two days.
Alright folks I've been with Samsung over a decade and just got my first Oneplus (8T+5G KB2007) so don't start yelling at me just yet. Got this thing on Amazon and appears to be new. I'm sim/network unlocked through TMO. My OEM Unlock was never greyed out. I can toggle no problem. However, I went through the debloat described above because of the following problem: Sticks on "waiting for any device" after running "fastboot oem get_unlock_code" Please tell me this is an easy fix. I already reinstalled the google driver through SDK Manager bla bla bla.... Am I missing something simple? Any help would be appreciated. THX
jabe78 said:
Yeah. I'm going to wait it out. Counting down the days I'm chained to T-Mobile (38 left). I actually wanted their service so it isn't an inconvenience, but I hate being forced to do anything, much less wait to do what I wanted to do from day one, which is Flash Roms. I'm looking at Lineage too. So I will update this post once I get to that point. Here's hoping they keep their word, because my 15 day return policy on the phone runs out in two days.
Click to expand...
Click to collapse
I should've done more research myself. Galaxy was about to quit on me so I grabbed this one specifically because it was rated as one of the very top phones for development. If it wasn't such a rush I would've spent more time.
jtford said:
Alright folks I've been with Samsung over a decade and just got my first Oneplus (8T+5G KB2007) so don't start yelling at me just yet. Got this thing on Amazon and appears to be new. I'm sim/network unlocked through TMO. My OEM Unlock was never greyed out. I can toggle no problem. However, I went through the debloat described above because of the following problem: Sticks on "waiting for any device" after running "fastboot oem get_unlock_code" Please tell me this is an easy fix. I already reinstalled the google driver through SDK Manager bla bla bla.... Am I missing something simple? Any help would be appreciated. THX
Click to expand...
Click to collapse
Have you checked if your phone is properly connected to your computer? Check using "fastboot devices" to see if your device is detected, and if it is not, then go within the Windows Device Manager and install the appropriate driver from Google, which can be found by searching "Google Fastboot Driver".
Xryphon said:
Have you checked if your phone is properly connected to your computer? Check using "fastboot devices" to see if your device is detected, and if it is not, then go within the Windows Device Manager and install the appropriate driver from Google, which can be found by searching "Google Fastboot Driver".
Click to expand...
Click to collapse
It doesn't show it shows under adb devices but not fastboot devices. Let me find the fastboot driver real quick and try. Thanks
jtford said:
It doesn't show it shows under adb devices but not fastboot devices. Let me find the fastboot driver real quick and try. Thanks
Click to expand...
Click to collapse
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Rootk1t said:
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Click to expand...
Click to collapse
Holy ****.... finally! I just needed the OnePlus_usb_driver_setup.exe in order to install the right driver from said directory. Big thanks man. Really!
TommyQuid said:
Does this still work on the recent 8T phones? Please do keep us updated on your situation. I'm thinking about buying this phone unlock the boot-loader, Sim unlock and get Lineage on it. I don't mind 45 days if they actually unlock it
Click to expand...
Click to collapse
So it was actually 40 days, I don't know why I said 45. Anyway, even after (48 days), it took me calling TMOBILE and having someone talk to their (OEM team) and start a conversation with them. 3 days later I was able to SIM unlock the phone. I was able to toggle OEM unlocking. Did the Fastboot command to get the Unlock Code, and sent it to OnePlus for "7 days". What the crap is all of this hassle? I left Android and went to Apple for 7 years. When I left, you could unlock a bootloader in minutes. For being so keen on allowing us to unlock our phones, it seems they give you a Circus of Hoops to jump thru "on Their timeline". Anyway, I actually think I may have screwed up the code because it was displayed on two lines from Fastboot. I sent it as one line. Hoping they sort it out and I don't have to reapply and wait another 7 days. What a mess!
jabe78 said:
So it was actually 40 days, I don't know why I said 45...
Click to expand...
Click to collapse
Thanks for the update