did a lil research on google by what I was told........downloaded RSD Lite. When I went to look for phone info, noticed that there was NO IMEI info! No MIN, PRL Version, MEID,ICCID, IMEI, IMEI SV Unkown......No IP Address, No Wifi MAC Address or Bluetooth info...................there is a serial number tho. I can turn it on and play with it; it will go into bootloader or fastboot mode or what ever its called. From what ive read it came with kitkat version, it has lollipop installed. Is there anything I can do?
I'm thinking all that stuff should populate once you install a SIM card and put it on the network. If you really want a rooted phone, do it now with sunshine and unlock your bootloader. Otherwise, after you update to the latest marshmallow version, you will be forever hosed and not able to root at all. If the bootloader of states it is already unlocked, it's likely that sunshine has already been used.
A phone can't simply be unrooted to bet an update. The update will see the ROM is not pure stock, and fail. RSD can put a phone right, but can wipe the data. If rooted, why not put TWRP on, flash a stock rom in TWRP, saving data, reflash stock recovery in ADB, take update, TWRP back on, back up pure new-stock, mess with ROM. Little involved? Sure. More so than re-doing all your apps and settings? HELL NO!
Sent from my XT1254 using Tapatalk
cannon8694 said:
did a lil research on google by what I was told........downloaded RSD Lite. When I went to look for phone info, noticed that there was NO IMEI info! No MIN, PRL Version, MEID,ICCID, IMEI, IMEI SV Unkown......No IP Address, No Wifi MAC Address or Bluetooth info...................there is a serial number tho. I can turn it on and play with it; it will go into bootloader or fastboot mode or what ever its called. From what ive read it came with kitkat version, it has lollipop installed. Is there anything I can do?
Click to expand...
Click to collapse
Bootloader unlocked or nah? TWRP installed or nah?
cannon8694 said:
Was told the VerizonDroid Turbo was rooted and needed to be unrooted.........plz help
Click to expand...
Click to collapse
Who told you it was rooted?
Who told you it "needed" to be unrooted? Your post is very confusing.
I won't have a phone that is not rooted. All my phones WILL be rooted. Rooted means you are the "admin", you are the real owner.
In bootloader mode, what does the "status code" say? O, 3 ? What number do you see?
ChazzMatt said:
Who told you it was rooted?
Who told you it "needed" to be unrooted? Your post is very confusing.
I won't have a phone that is not rooted. All my phones WILL be rooted. Rooted means you are the "admin", you are the real owner.
In bootloader mode, what does the "status code" say? O, 3 ? What number do you see?
Click to expand...
Click to collapse
i just want the phone to work! would prefer it to be rooted, never had a rooted phone! status code = 0
TheSt33v said:
Bootloader unlocked or nah? TWRP installed or nah?
Click to expand...
Click to collapse
New to this........wtf is TWRP?
Okay, if status code is 0, that means your bootloader is locked. As long as you haven't taken all the over the air updates, you can still unlock it (and then root it). Follow this guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
cannon8694 said:
i just want the phone to work! would prefer it to be rooted, never had a rooted phone! status code = 0
Click to expand...
Click to collapse
TheSt33v said:
Okay, if status code is 0, that means your bootloader is locked. As long as you haven't taken all the over the air updates, you can still unlock it (and then root it). Follow this guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
Click to expand...
Click to collapse
If your bootloader is locked with status code of 0 (zero), your phone has NEVER been rooted and the bootloader has never been unlocked.
As @TheSt33v says, as long as you are not on the very latest firmware from March 2017, then you can unlock your bootloader and root your phone. Verizon released an update last month to block unlocking the bootloader on the Droid Turbo XT1254. Do NOT take any OTA updates!
TWRP is a "custom recovery" to replace stock recovery. It lets you make backups of your system (to restore your phone to earlier time in case of disaster) but also lets you "flash" zipped files like SuperSu to root.
If you are new to this, go read his guide in the link above, VERY CAREFULLY. All the information can be a little overwhelming. But do NOT take any OTA updates if you have not already. Because if you are on the very latest firmware, you are out of luck in unlocking the bootloader and rooting. Good luck.
when i type "fastboot flash recoveryTWRP.img"
ChazzMatt said:
If your bootloader is locked with status code of 0 (zero), your phone has NEVER been rooted and the bootloader has never been unlocked.
As @TheSt33v says, as long as you are not on the very latest firmware from March 2017, then you can unlock your bootloader and root your phone. Verizon released an update last month to block unlocking the bootloader on the Droid Turbo XT1254. Do NOT take any OTA updates!
TWRP is a "custom recovery" to replace stock recovery. It lets you make backups of your system (to restore your phone to earlier time in case of disaster) but also lets you "flash" zipped files like SuperSu to root.
If you are new to this, go read his guide in the link above, VERY CAREFULLY. All the information can be a little overwhelming. But do NOT take any OTA updates if you have not already. Because if you are on the very latest firmware, you are out of luck in unlocking the bootloader and rooting. Good luck.
Click to expand...
Click to collapse
when I type "fastboot flash recovery TWRP.img" into Minimal ADB and Fastboot it comes back "targer reported max download size of 536870912 bytes ; error: cannot load 'TWRP.img : No error"
did I possibly put the file in wrong place when it said to copy it to same directory as Minimal ADB and Fastboot?
cannon8694 said:
when I type "fastboot flash recovery TWRP.img" into Minimal ADB and Fastboot it comes back "targer reported max download size of 536870912 bytes ; error: cannot load 'TWRP.img : No error"
did I possibly put the file in wrong place when it said to copy it to same directory as Minimal ADB and Fastboot?
Click to expand...
Click to collapse
Reading the guide we told you about, have you unlocked your bootloader yet with Sunshine exploit? That's necessary prerequisite before trying to flash TWRP recovery.
If you haven't done that yet, which firmware version are you on? Settings/About Phone/Firmware -- or something close to that. Let's make sure you are eligible to unlock your bootloader before we get into detailed discussion. If you've already unlocked the bootloader, then ignore this question.
ChazzMatt said:
Reading the guide we told you about, have you unlocked your bootloader yet with Sunshine exploit? That's necessary prerequisite before trying to flash TWRP recovery.
If you haven't done that yet, which firmware version are you on? Settings/About Phone/Firmware -- or something close to that. Let's make sure you are eligible to unlock your bootloader before we get into detailed discussion. If you've already unlocked the bootloader, then ignore this question.
Click to expand...
Click to collapse
I downloaded the sunshine.apk. I moved it to the internal storage via usb cable, but cant seem to find it on phone to open it? if that's even how im suppose to do it? the droid razr m that im using now has a file manager app. thlis turbo doesn't seem to have on?
cannon8694 said:
I downloaded the sunshine.apk. I moved it to the internal storage via usb cable, but cant seem to find it on phone to open it? if that's even how im suppose to do it? the droid razr m that im using now has a file manager app. thlis turbo doesn't seem to have on?
Click to expand...
Click to collapse
You can install a file manager app from the play store. ES is probably the most popular free one but I prefer File Manager+.
Definitely do more research on unlocking the bootloader and flashing things, once you get root you can make mistakes which can brick your phone. But with that responsibility comes more freedom to do what you want to your device.
Sent from my XT1254 using Tapatalk
ChazzMatt said:
If you haven't done that yet, which firmware version are you on? Settings/About Phone/Firmware -- or something close to that. Let's make sure you are eligible to unlock your bootloader before we get into detailed discussion.
Click to expand...
Click to collapse
cannon8694 said:
I downloaded the sunshine.apk. I moved it to the internal storage via usb cable, but cant seem to find it on phone to open it? if that's even how im suppose to do it? the droid razr m that im using now has a file manager app. thlis turbo doesn't seem to have on?
Click to expand...
Click to collapse
Before we go any further, please go to Settings/About Phone, and look at your build number.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's some examples above. It will look something like this, on one of those screenshots. We need you to tell us EXACTLY what the "Build Number" says on your phone, please?
My WiFi is saying unavailable. Can't connect in order to get app store
cannon8694 said:
My WiFi is saying unavailable. Can't connect in order to get app store
Click to expand...
Click to collapse
Not asking about Wi-Fi or anything in the apps store.
Just tell us the build number in Settings/About Phone. Type in the exact numbers and letters, please.
Take a screenshot if you have to.
Capture a Screenshot - DROID TURBO by Motorola. To capture a screenshot, simultaneously press and hold the Power and Volume Down buttons. To view the screenshot you've taken, navigate: Apps > Photos from a Home screen.
Click to expand...
Click to collapse
But you can also just look at the screen and type.
SpyderPride said:
You can install a file manager app from the play store. ES is probably the most popular free one but I prefer File Manager+.
Definitely do more research on unlocking the bootloader and flashing things, once you get root you can make mistakes which can brick your phone. But with that responsibility comes more freedom to do what you want to your device.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
but how do I get it to install on my phone with no sim card, service or wifi
ChazzMatt said:
Not asking about Wi-Fi or anything in the apps store.
Just tell us the build number in Settings/About Phone. Type in the exact numbers and letters, please.
Take a screenshot if you have to.
But you can also just look at the screen and type.
Click to expand...
Click to collapse
SU4TL-49
cannon8694 said:
SU4TL-49
Click to expand...
Click to collapse
Fantastic. You're eligible for bootloader unlock. Just don't take any OTA updates from Verizon.
ChazzMatt said:
Fantastic. You're eligible for bootloader unlock. Just don't take any OTA updates from Verizon.
Click to expand...
Click to collapse
ok but im stuck on installing the sunshine.apk on the phone, and it said to copy the twrp.img to the same directory that minimal adb and fastboot? what that mean
cannon8694 said:
but how do I get it to install on my phone with no sim card, service or wifi
Click to expand...
Click to collapse
SIM cards are free, go pick one up or order one and activate the phone?
Sent from my XT1254 using Tapatalk
Related
So I just got the Google Play Edition and I can't seem to figure any tutorial thread out on how to unlock the bootloader then root my phone, then install a custom recovery, then install a rom :/ I need some help. So currently, I am at the htcdev part to unlock bootloader using this tutorial. When I get to step 11 it says to skip to step 8 which I can not do on the page (Guessing the guide is outdated?). So I go ahead and do step 5-7 and when I type "fastboot oem get_identifier_token" on step 5 it just stays stuck on "waiting for device" on the CMD prompt. What am I doing wrong?
PS. which I click fastboot as instructed on step 2 of htcdev it just send me back to the screen before.
EvoTheBoy said:
So I just got the Google Play Edition and I can't seem to figure any tutorial thread out on how to unlock the bootloader then root my phone, then install a custom recovery, then install a rom :/ I need some help. So currently, I am at the htcdev part to unlock bootloader using this tutorial. When I get to step 11 it says to skip to step 8 which I can not do on the page (Guessing the guide is outdated?). So I go ahead and do step 5-7 and when I type "fastboot oem get_identifier_token" on step 5 it just stays stuck on "waiting for device" on the CMD prompt. What am I doing wrong?
PS. which I click fastboot as instructed on step 2 of htcdev it just send me back to the screen before.
Click to expand...
Click to collapse
Stuck waiting for device mean your drivers are not installed preoperly, download HTC Sync manager install it and then remove HTC sync, you will see the driver package above it, leave that alone.
Also, your phone must be in the bootloader when trying to get ID token, not booted up. (just in case)
Instructions to unlock the bootloader are at HTCDev whilst your trying to actually unlock the bootloader, you will need to register: http://www.htcdev.com/bootloader unlocking is the easy part.
Seanie280672 said:
Stuck waiting for device mean your drivers are not installed preoperly, download HTC Sync manager install it and then remove HTC sync, you will see the driver package above it, leave that alone.
Also, your phone must be in the bootloader when trying to get ID token, not booted up. (just in case)
Instructions to unlock the bootloader are at HTCDev whilst your trying to actually unlock the bootloader, you will need to register: http://www.htcdev.com/bootloader unlocking is the easy part.
Click to expand...
Click to collapse
Thank you for the reply! I got as far as inputting "fastboot flash unlocktoken Unlock_code.bin" into the cmd prompt which says it was successful but doesn't show nor do anything on my phone like it says it should. Any ideas on how to fix that?
EvoTheBoy said:
Thank you for the reply! I got as far as inputting "fastboot flash unlocktoken Unlock_code.bin" into the cmd prompt which says it was successful but doesn't show nor do anything on my phone like it says it should. Any ideas on how to fix that?
Click to expand...
Click to collapse
Really sorry I didn't read your first post properly, you have a gpe device, different kettle of fish, the HTC dev way doesn't work for gpe, try this instead.
http://www.ibtimes.co.uk/htc-one-google-play-edition-how-unlock-bootloader-root-install-twrp-1429968
For the Google Play Edition just use fastbot oem unlock and you're done
However, bear in mind that you won't be able to use Sense-based ROMs as the partitions are different. You're limited to AOSP/CM-based ROMs (unless you can convert to a Sense M7, which I assume so as they're technically the same device)
Seanie280672 said:
Really sorry I didn't read your first post properly, you have a gpe device, different kettle of fish, the HTC dev way doesn't work for gpe, try this instead.
http://www.ibtimes.co.uk/htc-one-google-play-edition-how-unlock-bootloader-root-install-twrp-1429968
Click to expand...
Click to collapse
EddyOS said:
For the Google Play Edition just use fastbot oem unlock and you're done
However, bear in mind that you won't be able to use Sense-based ROMs as the partitions are different. You're limited to AOSP/CM-based ROMs (unless you can convert to a Sense M7, which I assume so as they're technically the same device)
Click to expand...
Click to collapse
I keep getting this error :/ Idk if this helps but it says s-on and hboot is 1.54 and my OS is 5.11.1700.3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
EddyOS said:
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
Click to expand...
Click to collapse
It is weird. I googled it and came about people saying to downgrade (Which I have 0 knowledge of when it comes to HTC devices.. coming from LG as my device with experience). Idk. Thanks for the help hopefully someone can help me out about this.
The whole point of the GPe phones is that they're easy to unlock, like a Nexus, so it should just unlock with that command. The only thing I can think of is you're using outdated fastboot files so perhaps looks into updating them but failing that I'm at a loss
EddyOS said:
The whole point of the GPe phones is that they're easy to unlock, like a Nexus, so it should just unlock with that command. The only thing I can think of is you're using outdated fastboot files so perhaps looks into updating them but failing that I'm at a loss
Click to expand...
Click to collapse
Guess that isn't the problem :/ I triple checked to make sure I had the right fastboot and I kept getting the same error.
EddyOS said:
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
Click to expand...
Click to collapse
I've never seen that.. It's very odd.
graffixnyc said:
I've never seen that.. It's very odd.
Click to expand...
Click to collapse
I read online about it and saw some say to call google and they could help fix the problem cause it is a problem within the actual device. I called them and they didn't help lol. Anyways, my device is still under warranty and has the purple camera tint problem so I will try to send it in and hopefully get a new model back.
OT: if anyone has had this error before please say how you fixed it thanks
UPDATE: After some googling I found out that after 4.4.2 fastboot oem unlock does not work anymore with this devices (I am on 5.0.1)
I did "oem unlock" on my new Nexus 6, because i wanted to upgrade directly to the newest image of Android 6.
However after that, i discovered, that i had to "Enable OEM unlock" in developer settings, to "oem lock" and "oem unlock" the device.
But I didn't had to do this the first time.
So is this feature not implemented in the first firmware version of the Nexus 6, or is my "new" device not realy new?
Looks like it was already unlocked when you got it. Usually you get a few messages about unlocking the phone to warn you and tell you the device will be wiped aka factory reset.
JulianPascal said:
I did "oem unlock" on my new Nexus 6, because i wanted to upgrade directly to the newest image of Android 6.
However after that, i discovered, that i had to "Enable OEM unlock" in developer settings, to "oem lock" and "oem unlock" the device.
But I didn't had to do this the first time.
So is this feature not implemented in the first firmware version of the Nexus 6, or is my "new" device not realy new?
Click to expand...
Click to collapse
are the dev options in settings witthout you unlocking them? if yes, then your new phone isnt new.
simms22 said:
are the dev options in settings witthout you unlocking them? if yes, then your new phone isnt new.
Click to expand...
Click to collapse
No, the developer options were not enabled. I got into fastboot mode, made sudo fastboot oem unlock, clicked yes and it was unlocked. I flashed the Android 6 image manually and after that i couldn't relock it. I had then to activate the developer options to relock the device.
gee2012 said:
Looks like it was already unlocked when you got it. Usually you get a few messages about unlocking the phone to warn you and tell you the device will be wiped aka factory reset.
Click to expand...
Click to collapse
I got this warning, but i didn't have to activate “Enable OEM Unlock” in the developer options to unlock the device.
JulianPascal said:
I got this warning, but i didn't have to activate “Enable OEM Unlock” in the developer options to unlock the device.
Click to expand...
Click to collapse
Hard to believe to be honest. But hey anything is possible, maybe some kind of magical glitch ?
gee2012 said:
Hard to believe to be honest. But hey anything is possible, maybe some kind of magical glitch ?
Click to expand...
Click to collapse
i think ive read about two more phones that had that "glitch", but its not common for sure.
simms22 said:
i think ive read about two more phones that had that "glitch", but its not common for sure.
Click to expand...
Click to collapse
I`am glad there is still some magic left in this world
gee2012 said:
Hard to believe to be honest. But hey anything is possible, maybe some kind of magical glitch
Click to expand...
Click to collapse
i've got only 1 Warning the first time: "Unlock bootloader? - yes(may void waranty / no)"
after the upgrade i get: the red "Waring" and then "Unlock bootloader?" - yes(may void waranty / no)
JulianPascal said:
i've got only 1 Warning the first time: "Unlock bootloader? - yes(may void waranty / no)"
after the upgrade i get: the red "Waring" and then "Unlock bootloader?" - yes(may void waranty / no)
Click to expand...
Click to collapse
Oke, you`re one of the happy few where this happens. Was the device wiped/factory reset during the process?
simms22 said:
i think ive read about two more phones that had that "glitch", but its not common for sure.
Click to expand...
Click to collapse
Maybe this only happens with a old bootloader version, which dosen't support this feature yet? Which would explain, why i couldn't relock it after upgrading. Do you have a link?
JulianPascal said:
Maybe this only happens with a old bootloader version, which dosen't support this feature yet? Which would explain, why i couldn't relock it after upgrading. Do you have a link?
Click to expand...
Click to collapse
Thats probably it, had that on a N4 too once when i used CF Auto-Root (not wiped)
JulianPascal said:
Maybe this only happens with a old bootloader version, which dosen't support this feature yet? Which would explain, why i couldn't relock it after upgrading. Do you have a link?
Click to expand...
Click to collapse
na. it was there on the very first version of pre 5.0 that the phone came with. so it was there on all bootloader versions.
gee2012 said:
Oke, you`re one of the happy few where this happens. Was the device wiped/factory reset during the process?
Click to expand...
Click to collapse
I did a full wipe before flashing, so I'm not shure if the upgrade process itself reseted the device.
gee2012 said:
Oke, you`re one of the happy few where this happens. Was the device wiped/factory reset during the process?
Click to expand...
Click to collapse
simms22 said:
na. it was there on the very first version of pre 5.0 that the phone came with. so it was there on all bootloader versions.
Click to expand...
Click to collapse
Motorola Support says, it's normal for older firmware versions, that they can be unlocked without activating this option.
JulianPascal said:
Motorola Support says, it's normal for older firmware versions, that they can be unlocked without activating this option.
Click to expand...
Click to collapse
i ran the very first version of software on my n6, back in november of last year, and it had to be unlocked with hitting the oem unlock option first. calling people at motorola is just going to get you talking to people that dont know whats going on.
simms22 said:
i ran the very first version of software on my n6, back in november of last year, and it had to be unlocked with hitting the oem unlock option first. calling people at motorola is just going to get you talking to people that dont know whats going on.
Click to expand...
Click to collapse
Ok, this is strange, the Device was new and the package sealed. I mean, could realy someone have somehow re-sealed it? Someone at Nexus Help Forum suggested, maybe someone at Motorola made a mistake in the final preparation process, so there are just some devices affected.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/nexus/ZoVKdHn-cM4/xwaB-b8MAQAJ
So, do you think the Device is safe to use(regarding the devices firmware (bootloader etc.) isn't altered/ some sort of maleware embedded)? Or should I return it, if I can?
JulianPascal said:
Ok, this is strange, the Device was new and the package sealed. I mean, could realy someone have somehow re-sealed it? Someone at Nexus Help Forum suggested, maybe someone at Motorola made a mistake in the final preparation process, so there are just some devices affected.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/nexus/ZoVKdHn-cM4/xwaB-b8MAQAJ
So, do you think the Device is safe to use(regarding the devices firmware (bootloader etc.) isn't altered/ some sort of maleware embedded)? Or should I return it, if I can?
Click to expand...
Click to collapse
mistakes do happen. ive seen people buy a n6 from tmobile but receive an att version, with all the att trimings. if you want to check if locking it is possible, you probably should. but, i think it probably is safe to use.
Theoretically someone could have bought it, opened it, unlocked it and did what ever with it, somehow reasealed it and returned it to the retailer(you have the right to return something you bought online in a 14 day period in germany).
I noticed something there are two numbers which are each 11 digits long, one on the the bottom and one on the side of the packaging.
(I covered them on the pictures, but marked where they are)
The two numbers differ at my packaging, Is this normal or should the two numbers be the same?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JulianPascal said:
Motorola Support says, it's normal for older firmware versions, that they can be unlocked without activating this option.
Click to expand...
Click to collapse
I have read this as well.
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.
Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk
SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.
TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.
Here's the tool. Freshly modded by yours truly.
https://mega.nz/#!uNwERIDK!1fbu5KGWH441r0EFwHb_rgEamjax068RAjT-Ze9ELVc
You know what to do - power down, hold volume up and volume down, connect USB, run it.
This will convert you to the T-Mobile firmware. T-Mobile users with the non-TMO phone who run this tool and convert will get better WiFI Calling support + T-Mobile bloat + possibly working RCS. You will lose dual SIM support.
If you wind up wanting to restore back to international firmware, grab the international (GM1917) MSM tool from the 'Guac For All' thread. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Enjoy!
how's RCS working for you? i have the international version too and thinking about switching to see if its better for my MMS and calling
This works great! Don't know if I will keep it TMobile or not, but working great so far.
Sent from my GM1917 using Tapatalk
RCS chat seams to be working. Although I don't know anyone else that has it to test it out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GM1917 using Tapatalk
I did notice that the fingerprint sensor is not nearly as good with the T-Mobile firmware. It worked almost every time when it was international, but with the T-Mobile firmware installed, it failed most times, so I disabled it.
Sent from my GM1917 using Tapatalk
DTop said:
T-Mobile users with the non-TMO phone who run this tool and convert will get better WiFI Calling support
Click to expand...
Click to collapse
On the stock T-Mobile ROM does it turn off the cellular radio and disconnect from the tower when wifi calling is connected?
I remember my old T-Mobile Samsung doing this and it would save a lot of battery life.
Doesnt that msm tool in slayers thread do the same thing or is this easier? Also quick question ...i have a tmobile op7pro unlocked bootloader , rooted and on intl fw 9.5.8 ....what i want to do is go back to tmobile 9.5.8 and root /twrp ..... not used to this whole A/B slot thing...so what are my options? Msm tool back to tmobile boot device, turn on dev options make sure usb debugging/ oem unlock is on etc at this point is this where i can just flash twrp in fastboot? Or does this not work on tmobile fw?....because if so thats cool..im sure once twrp is installed i can flash maqisk etc
sarni84 said:
Doesnt that msm tool in slayers thread do the same thing or is this easier? Also quick question ...i have a tmobile op7pro unlocked bootloader , rooted and on intl fw 9.5.8 ....what i want to do is go back to tmobile 9.5.8 and root /twrp ..... not used to this whole A/B slot thing...so what are my options? Msm tool back to tmobile boot device, turn on dev options make sure usb debugging/ oem unlock is on etc at this point is this where i can just flash twrp in fastboot? Or does this not work on tmobile fw?....because if so thats cool..im sure once twrp is installed i can flash maqisk etc
Click to expand...
Click to collapse
From I can see, yes this is the same thing as slayer's thread. This thread is directed at T-Mobile users with the international model who want the T-Mobile software. Whereas slayer's thread is directed at those with the T-Mobile model who need to get back to stock.
As far as I know they both are the same, its just two different threads for two different reasons.
So either will work the same. It shouldn't matter if they're both the same T-Mobile firmware.
EDIT: Model number shows different on this build. See OP response.
If you just want rooted stock with Magisk and TWRP, once you're back on T-Mobile stock you can use the all in one tool to flash TWRP and install Magisk.
You shouldn't need to oem unlock the bootloader again. Once you unlock it, it always stays unlocked unless you manually relock it yourself.
All in one tool here: https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3930862
Extract that download and open tool all in one.
It should show adb device Oneplus 7 Pro at the top. Check fastboot drivers and usb connection if it doesn't. Also make sure your screen is on with usb debugging allowed.
Then click Recovery Flasher and Device Rooter.
Select "TWRP OP7P" from the list where it shows "MANUAL" in all caps.
Then check the box to root after boot, select the latest Magisk version from the drop down menu.
Click the button to start the process. It may ask to reboot into fastboot/bootloader, choose yes. If it works as it should, it will automatically download TWRP and Magisk and load them onto your phone.
Thanks bro yeah I know I won't have problems with the bootloader I was just worried about the stock boot image.... I thought I saw somewhere that you needed a modified one
KemikalElite said:
From I can see, yes this is the same thing as slayer's thread. This thread is directed at T-Mobile users with the international model who want the T-Mobile software. Whereas slayer's thread is directed at those with the T-Mobile model who need to get back to stock.
Click to expand...
Click to collapse
It is not the same thing. The tool in Slayer's thread will only work for converting from T-Mobile (GM1915) to international (GM1917 software, but the phone still displays the GM1915 model number in settings). The tool in this thread will only work for converting from International (GM1917) to T-Mobile (GM1915 software, but the phone still displays the GM1917 model number in settings).
Feel free to give it a try, you'll see XD
sarni84 said:
Thanks bro yeah I know I won't have problems with the bootloader I was just worried about the stock boot image.... I thought I saw somewhere that you needed a modified one
Click to expand...
Click to collapse
The stock boot image is injected when Majisk is installed, making it modified. It should install fine with the stock boot image/kernel. :good:
KemikalElite said:
The stock boot image is injected when Majisk is installed, making it modified. It should install fine with the stock boot image/kernel. :good:
Click to expand...
Click to collapse
Cool. U the man thanks:good:
Is it possible this can be modded for T-Mobile devices converted to International to go back to T-Mobile firmware? I ask for troubleshooting the sleep-of-death issue some of us have been experiencing and also in case of needing to warranty the device.
Link to the Sleep-Of-Death thread added.
https://forum.xda-developers.com/oneplus-7-pro/how-to/poll-phone-randomly-powered-off-t3940427
Se7eN43 said:
Is it possible this can be modded for T-Mobile devices converted to International to go back to T-Mobile firmware? I ask for troubleshooting the sleep-of-death issue some of us have been experiencing and also in case of needing to warranty the device.
Link to the Sleep-Of-Death thread added.
https://forum.xda-developers.com/oneplus-7-pro/how-to/poll-phone-randomly-powered-off-t3940427
Click to expand...
Click to collapse
If you have the T-Mobile version you should use this download instead to return to stock:
https://forum.xda-developers.com/on...obile-one-plus-7-pro-msm-tool-revert-t3936528
------------------------------------------------------
I loaded this on my phone and for anyone who wants to know, Safetynet works and L1 widevine (HD Netflix) works. I'm not sure how this happened, but the bootloader relocked on its own. (maybe after a factory reset, maybe I clicked something by accident) Either way you can lock the bootloader running this if needed as long as you aren't rooted or don't have a custom recovery, and it will work okay.
Edit: Locked bootloader wants unlock token to unlock now. Do NOT lock bootloader.
RCS works as well but visual voicemail doesn't even work on the stock ROM. I know this isn't a fault of the ROM, its a Oneplus or T-Mobile issue, but if Android supports built-in visual voicemail without using the terrible T-Mobile VVM app, it should work as intended. I remember visual voicemail working fine on my Nexus 5.
T-Mobile please fix this.
KemikalElite said:
If you have the T-Mobile version you should use this download instead to return to stock:
https://forum.xda-developers.com/on...obile-one-plus-7-pro-msm-tool-revert-t3936528
------------------------------------------------------
I loaded this on my phone and for anyone who wants to know, Safetynet works and L1 widevine (HD Netflix) works. I'm not sure how this happened, but the bootloader relocked on its own. (maybe after a factory reset, maybe I clicked something by accident) Either way you can lock the bootloader running this if needed as long as you aren't rooted or don't have a custom recovery, and it will work okay.
RCS works as well but visual voicemail doesn't even work on the stock ROM. I know this isn't a fault of the ROM, its a Oneplus or T-Mobile issue, but if Android supports built-in visual voicemail without using the terrible T-Mobile VVM app, it should work as intended. I remember visual voicemail working fine on my Nexus 5.
T-Mobile please fix this.
Click to expand...
Click to collapse
Wow! I can't believe I missed this. Thank you for prompt reply.
KemikalElite said:
If you have the T-Mobile version you should use this download instead to return to stock:
https://forum.xda-developers.com/on...obile-one-plus-7-pro-msm-tool-revert-t3936528
------------------------------------------------------
I loaded this on my phone and for anyone who wants to know, Safetynet works and L1 widevine (HD Netflix) works. I'm not sure how this happened, but the bootloader relocked on its own. (maybe after a factory reset, maybe I clicked something by accident) Either way you can lock the bootloader running this if needed as long as you aren't rooted or don't have a custom recovery, and it will work okay.
Edit: Locked bootloader wants unlock token to unlock now. Do NOT lock bootloader.
RCS works as well but visual voicemail doesn't even work on the stock ROM. I know this isn't a fault of the ROM, its a Oneplus or T-Mobile issue, but if Android supports built-in visual voicemail without using the terrible T-Mobile VVM app, it should work as intended. I remember visual voicemail working fine on my Nexus 5.
T-Mobile please fix this.
Click to expand...
Click to collapse
Ok so basically u can flash back to tmobile but it locks the bootloader... .so now if u want to unlock and STAY on tmobile u have to get an unlock token from one plus.....or just flash international and unlock again with command easily.....thats what i was worried about happening. Crazy how the bootloader gets locked again
Quick question to any one on the TMO version. Do the TMO firmware have video calling like must of TMO phones.
mario1634 said:
Quick question to any one on the TMO version. Do the TMO firmware have video calling like must of TMO phones.
Click to expand...
Click to collapse
Yes. and yes it sucks like other TMO phones
sarni84 said:
Ok so basically u can flash back to tmobile but it locks the bootloader... .so now if u want to unlock and STAY on tmobile u have to get an unlock token from one plus.....or just flash international and unlock again with command easily.....thats what i was worried about happening. Crazy how the bootloader gets locked again
Click to expand...
Click to collapse
Has anyone had any luck getting an Unlock Token for a GM1917? I tried the unlock site and it says I need a valid IMEI, and when I called OnePlus, the support rep said they only have the tools for the 6t.
Might try calling again today in case the late night call center was just ill equipt
Tardeaux said:
Has anyone had any luck getting an Unlock Token for a GM1917? I tried the unlock site and it says I need a valid IMEI, and when I called OnePlus, the support rep said they only have the tools for the 6t.
Might try calling again today in case the late night call center was just ill equipt
Click to expand...
Click to collapse
Any luck ?
Hi!
As you may know Honor is pretty restricted in modding.
I AM NOT RESPONSIBLE FOR ERRORS/BRICKED DEVICES'
THIS JUST GIVES AN IDEA ON WHAT TO DO AND IF YOU SHOULD BUY( I don't recommend for modding)
EDIT: IT SEEMS LIKE WE CANT UNLOCK THE BL
There are no recoveries yet
So we need boot.img to root with magisk
But Honor/Other websites does not provide firmware
So we need to dump firmware(which I have not done yet) to get boot.img using mtk client or unlocktool (idk if unlocktool is legit)
Then patch boot.img and flash
#YetAnotherPerson said:
Hi!
As you may know Honor is pretty restricted in modding.
I AM NOT RESPONSIBLE FOR ERRORS/BRICKED DEVICES'
THIS JUST GIVES AN IDEA ON WHAT TO DO AND IF YOU SHOULD BUY( I don't recommend for modding)
There are no recoveries yet
So we need boot.img to root with magisk
But Honor/Other websites does not provide firmware
So we need to dump firmware(which I have not done yet) to get boot.img using mtk client or unlocktool (idk if unlocktool is legit)
Then patch boot.img and flash
Click to expand...
Click to collapse
Hi! Thanks for requesting this page!
For anyone considering buying this phone, just like OP said, DON'T buy if you want to MOD it in any way!
Also, if anyone has any information on this phone, like the firmware, exploits, etc. PLEASE share it since this device is not even that known in XDA.
Sad update, I backed up my Linux computer to install windows and use many apps to retrieve stock firmware for rooting and when device gets bricked, but no success, and I installed Linux again. I did not dual boot because of storage issues
Our hope is not fully lost.
We could flash a rooted GSI.
But I just don't want to risk it as there is no way to return back to the stock firmware if something goes wrong or some features don't work(that's sometimes how GSI's are
#YetAnotherPerson said:
Our hope is not fully lost.
We could flash a rooted GSI.
But I just don't want to risk it as there is no way to return back to the stock firmware if something goes wrong or some features don't work(that's sometimes how GSI's are
Click to expand...
Click to collapse
But wouldn't we need to at least unlock the bootloader to flash anything?
JoeBro19 said:
But wouldn't we need to at least unlock the bootloader to flash anything
Click to expand...
Click to collapse
There is a bootloader unlock option in settings, developer options
#YetAnotherPerson said:
There is a bootloader unlock option in settings, developer options
Click to expand...
Click to collapse
That's only an option to allow the device to be unlocked, but it doesn't unlock it per se. That's done in fastboot mode or similar where you enter a code to unlock it, but Huawei/Honor stopped giving those codes years ago, that's why it's so difficult to do anything to these phones...
JoeBro19 said:
That's only an option to allow the device to be unlocked, but it doesn't unlock it per se. That's done in fastboot mode or similar where you enter a code to unlock it, but Huawei/Honor stopped giving those codes years ago, that's why it's so difficult to do anything to these phones...
Click to expand...
Click to collapse
Hi!
Do you know any way to check if the bootloader is unlocked other than the phone and fastboot method(those don't work for me). I think I did unlock the bootloader, here is what I did:
1. I typed "fastboot flashing unlock"
2. THAT BRICKED MY PHONE
3. I booted into recovery and did a factory reset
4. Did my usual setup again
5. I just went into settings(developer options) and the OEM unlock toggle was enabled without me touching it!
#YetAnotherPerson said:
Hi!
Do you know any way to check if the bootloader is unlocked other than the phone and fastboot method(those don't work for me). I think I did unlock the bootloader, here is what I did:
1. I typed "fastboot flashing unlock"
2. THAT BRICKED MY PHONE
3. I booted into recovery and did a factory reset
4. Did my usual setup again
5. I just went into settings(developer options) and the OEM unlock toggle was enabled without me touching it!
Click to expand...
Click to collapse
You can check by entering fastboot/bootloader mode and it'll say if the phone (bootloader) is locked or unlocked.
You can enter the bootloader by using adb and entering "adb reboot bootloader" and after you get restarted into the bootloader it'll tell you the status on the bottom of the screen.
I have that OEM unlock toggled on and as it still says "Phone Locked" in the bootloader, just as I said that toggling that option doesn't actually unlock it.
JoeBro19 said:
You can check by entering fastboot/bootloader mode and it'll say if the phone (bootloader) is locked or unlocked.
You can enter the bootloader by using adb and entering "adb reboot bootloader" and after you get restarted into the bootloader it'll tell you the status on the bottom of the screen.
I have that OEM unlock toggled on and as it still says "Phone Locked" in the bootloader, just as I said that toggling that option doesn't actually unlock it.
Click to expand...
Click to collapse
Thanks!
While I did not make any progress, atleast I found out I wasted my time "unlocking" the BL and still nothing happened. Just to confirm that the phone locked thing does change when BL in unlocked, I checked a yt video on someone flashing a GSI on an older honor device and it does say "phone unlocked" for them.
Let me explain a bit more on what happened on the BL unlock attempt:
1.I did fastboot flashing unlock in adb which should unlock the BL
2.It put me in a menu which had an option to unlock the bootloader and it did say it will void warranty
3. Then it said it was a sucess and then went into another menu asking what to do next (fastboot mode,reboot,and something else) but it glitched and clicking hw buttons did nothing so I rebooted and the device was in a bootloop so I had to reset the device using the recovery
4. In fastboot mode, it still says phone locked
In short: There is a bug preventing BL unlock. I am not sure if Honor devices still need a code to unlock the BL since you said they stopped providing them
#YetAnotherPerson said:
Thanks!
While I did not make any progress, atleast I found out I wasted my time "unlocking" the BL and still nothing happened. Just to confirm that the phone locked thing does change when BL in unlocked, I checked a yt video on someone flashing a GSI on an older honor device and it does say "phone unlocked" for them.
Let me explain a bit more on what happened on the BL unlock attempt:
1.I did fastboot flashing unlock in adb which should unlock the BL
2.It put me in a menu which had an option to unlock the bootloader and it did say it will void warranty
3. Then it said it was a sucess and then went into another menu asking what to do next (fastboot mode,reboot,and something else) but it glitched and clicking hw buttons did nothing so I rebooted and the device was in a bootloop so I had to reset the device using the recovery
4. In fastboot mode, it still says phone locked
In short: There is a bug preventing BL unlock. I am not sure if Honor devices still need a code to unlock the BL since you said they stopped providing them
Click to expand...
Click to collapse
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
JoeBro19 said:
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
Click to expand...
Click to collapse
Ok, but
JoeBro19 said:
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
Click to expand...
Click to collapse
Ok, but I'll give another warning: It's risky and may brick your device like mine and a factory reset from the recovery may be required. I am not respondible if something happens.
I did contact honor customer support but no reply yet
#YetAnotherPerson said:
Ok, but
Ok, but I'll give another warning: It's risky and may brick your device like mine and a factory reset from the recovery may be required. I am not respondible if something happens.
I did contact honor customer support but no reply yet
Click to expand...
Click to collapse
I doubt they'll anything other than "we don't provide those codes anymore"
And yeah I decided to try it anyway and it happened exactly the same as your case. I had to factory reset it to exit the boot loop. Fortunately, I did a backup just before trying it so I was able to restore it and not lose anything; but yeah, things seem to have come to a standstill.
JoeBro19 said:
I doubt they'll anything other than "we don't provide those codes anymore"
And yeah I decided to try it anyway and it happened exactly the same as your case. I had to factory reset it to exit the boot loop. Fortunately, I did a backup just before trying it so I was able to restore it and not lose anything; but yeah, things seem to have come to a standstill.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#YetAnotherPerson said:
View attachment 5902653
Click to expand...
Click to collapse
Just as I thought.... damn this companies...
So, unless some miracle happens and someone discovers an exploit on the processor or something that allows us to decipher the unlock code, there is absolutely nothing than we can do...
You can only unlock the bootloader on the new Honor at the Honor office. But this is only possible if the Honor employee is your friend.
volkodav1975 said:
You can only unlock the bootloader on the new Honor at the Honor office. The workers there have such smartphones, I have a friend among such workers and he made a request for me in a friendly way. I think that you will not see such a photo anywhere else. Alas, as long as it's useless, I need a custom one Recovery, But I don't know where to get it.
Click to expand...
Click to collapse
Well that's... disappointing... can't believe we have to even consider that. In my case, we don't have those centers, so I'm definitely screwed... good job Honor...