Related
I may have to return my ATRIX due to Let'sTalk horrible customer service, but I was wondering if there is anyway to re-lock the Bootloader, or to hide the fact that it says, Unlocked. Thank you in advanced
Also, I'm sorry if this is in the wrong section, as this is urgent to me and I have yet to see any otherpost relating this topic.
There is another topic like this.
No you can't re-lock and no you can't "hide" the unlock wording. Sorry.
Sent from my AWESOME Atrix
Assume you installed 2.3 using CWM, if that is the case, you can flash the stock 1.8.3. Because the bootloader is not compatible with the unlocked phones, it won't show the "unlocked" text when you turn on the phone. I have tried it when I was trying to get rid if the unlocked text.
The down side is, you won't be able to flash custom ROM until you flash a compatible bootloader.
Sent from my Motorola Atrix 4G MB860 using XDA App
But downgrading will hard brick the phone.be very very carefully.
Reflash To Stock
Unfortunately, there is no way to relock a bootloader. Hence all of the warnings when you committed
but, if you use 4.5.91 the software at the address below should reinstall the newest stock software...
direct.motorola.com/hellomoto/motosupport/source/SoftwareUpdateSelect.asp?country=USA&language=ENS
be careful because Im not sure how motorola update will react to an unlocked bootloader. Ask around...do so at your own risk.
If you want to try a harder, albeit, safer method, and you are sure that you do not have a phone running 4.1.5.91, you can restore your phone to a factory SBF with this process:
briefmobile.com/motorola-atrix-4g-system-boot-file-sbf-leaked
DO NOT UNDER ANY CIRCUMSTANCES TRY TO RESTORE A 4.5.91 system to stock with RSD LITE.
To go to any of the blue webaddresses above, copy-paste them into your browser. Sorry, but I am not allowed to post links yet.
I wonder why nobody has created a CWM downgrade for US Atrixes. NFHimself made one for Bell or international users to go to 2.2.2 Bell and it works really well. Pretty much every partition is replaced. Great for masking that your boot loader is unlocked. Someone should probably do that for ATT to make downgrading less risky than flashing an sbf again...
drpratik said:
But downgrading will hard brick the phone.be very very carefully.
Click to expand...
Click to collapse
The downgrading and hard brick problem stems from using the OTA update, so you won't hard brick if for example you upgraded with KP's 4.5.91.
You also should be able to flash the 4.5.91 SBF. You just can't downgrade. There are other threads about this.
Sent from my Alienated Atrix
maledyris said:
I wonder why nobody has created a CWM downgrade for US Atrixes. NFHimself made one for Bell or international users to go to 2.2.2 Bell and it works really well. Pretty much every partition is replaced. Great for masking that your boot loader is unlocked. Someone should probably do that for ATT to make downgrading less risky than flashing an sbf again...
Click to expand...
Click to collapse
The reason the fruitcakes were created and deemed safe by the devs were because it didn't touch the BL, which people believe to be the culprit behind the hard bricks. NFhimself was brave enough to testing flashing the BL via cwm in his gobstopper on international phones, but I don't think any other devs are willing to risk hard bricking their phones by testing that theory on US phones.
There also isn't enough "reward" for doing so because if people want to downgrade they can use a fruitcake. The only gain is to get rid of the "unlock" text. But if you were really that concerned about it despite reading all the warnings of this will void you warranty, you shouldn't have unlocked in the first place.
maledyris said:
I wonder why nobody has created a CWM downgrade for US Atrixes. NFHimself made one for Bell or international users to go to 2.2.2 Bell and it works really well. Pretty much every partition is replaced. Great for masking that your boot loader is unlocked. Someone should probably do that for ATT to make downgrading less risky than flashing an sbf again...
Click to expand...
Click to collapse
Hi,
One of the reasons I did up a default CWM of 2.2.2 is to have a means of doing a reset after trying all ATT/ORANGE/TELSTRA/MOVIESTAR/etc firmwares out there which may have side effects or accumulated side effects. Hence the inclusion of the stock bootloader and radio and a write of the extra partitions to clean up whatever mix and match leftovers are in there from the various carriers. The other big one is just to be able to get a Bell OTA applied when it comes out, it will probably be similar to the leak, but best to be safe.
This is more of a Bell/Intl issue as ATT folks tend to run just ATT firmware or flash just boot and system via CWM/fastboot and don't have the same issues as flashing a sbf file.
Both the stock 2.2.2 and leaked ap20 OTA bootloaders from Bell are safe to flash after IHOP, this is not the case with ATT bootloaders and may be the case for any included in a sbf file. Finding out the hard way is not an option.
Cheers!
ken218 said:
Assume you installed 2.3 using CWM, if that is the case, you can flash the stock 1.8.3. Because the bootloader is not compatible with the unlocked phones, it won't show the "unlocked" text when you turn on the phone. I have tried it when I was trying to get rid if the unlocked text.
The down side is, you won't be able to flash custom ROM until you flash a compatible bootloader.
Sent from my Motorola Atrix 4G MB860 using XDA App
Click to expand...
Click to collapse
Say I unlocked it at 1.8.3 should I go down to 1.5.7? Is that safe?
moto helper update relocked mine flashed it to 4.5.91 and i had to reunlock and root agin i thought i was getting a driver update not ota.I was on rom homebase + extras but my win 7 64 bit wasent seeing my phone so i reinstalled drivers and updated drivers and updated moto helper and in the process flashed my phone to stock that pissed me off had to start over..I rebooted the phone several times and never seen unlocked on boot tried to fastboot into android recovery and got the triangle im all good now back on homebase ext4 just thought id share that you realy can relock at least it dont say unlocked i beleve its locked
defnow said:
and no you can't "hide" the unlock wording. Sorry.
Click to expand...
Click to collapse
Err...............yes you can!
care to share how?
Scolis said:
care to share how?
Click to expand...
Click to collapse
Read the thread from the start. It's already been said!
CaelanT said:
Read the thread from the start. It's already been said!
Click to expand...
Click to collapse
Trying this today. Seems like my vibrator motor quit working. Phone is 6 months old I should be under the year warranty or so right?
leperkuan said:
Trying this today. Seems like my vibrator motor quit working. Phone is 6 months old I should be under the year warranty or so right?
Click to expand...
Click to collapse
When I was at school 6 months < 1 year so yes!
This is where you need to look:
http://forum.xda-developers.com/showthread.php?t=1163009
CaelanT said:
When I was at school 6 months < 1 year so yes!
This is where you need to look:
http://forum.xda-developers.com/showthread.php?t=1163009
Click to expand...
Click to collapse
Lol well I wasn't sure it had a one year warranty. Found out my vibrator does work. Just sometimes doesn't on cm7. Weird. Well I may try this anyways. Tired of custom Roms.
Sent from my MB860 using Tapatalk
leperkuan said:
Found out my vibrator does work.
Click to expand...
Click to collapse
Think you should go to another site other than XDA with this. Something in the XXX domain should work for you. Too much information for me! LOL................
assuming it is still in warranty
hard brick the phone and return it
just tell them you was doing a software update and your kid unplugged the phone while doing so
Hi, I had a question regarding what I've been seeing in the forum. A lot of you mention you go into Sprint and get a replacement EVO--does this work only if you pay that monthly insurance rate? I once went in with a LG Marquee that had issues and they didn't replace it for me (they said it had water damage even though this was a very new phone and I know for certain it did not). Did I just have a bad experience or will Sprint actually replace the phone if there are significant issues? Also, would they replace it if its rooted or has a unlocked bootloader?
Thanks.
I didn't want to make a new thread for this question:
If I do the OTA update to Jelly Bean, will I still be able to unlock bootloader, install TWRP and root? I don't mind being S-On--I just want to be able to run a rom like MeanBean.
007math said:
I didn't want to make a new thread for this question:
If I do the OTA update to Jelly Bean, will I still be able to unlock bootloader, install TWRP and root? I don't mind being S-On--I just want to be able to run a rom like MeanBean.
Click to expand...
Click to collapse
yes u can still unlock the bootloader and root.. u just wont be able to get s-off at the moment..
I have a gs4 with an unlocked bootloader (MDK baseband). The data port on mine went south, so I'm looking for another one on swappa. I found one but the baseband does not have mdk in it. It's rooted with 4.4.4, so I know it has an unlocked bootloader. The phone I have now has the mdk in the baseband. My question is how can this be? I know it's been updated, but I didn't think you could update it without loosing the unlocked bootloader. Thanks
http://forum.xda-developers.com/showthread.php?t=2817708
wily5150 said:
I have a gs4 with an unlocked bootloader (MDK baseband). The data port on mine went south, so I'm looking for another one on swappa. I found one but the baseband does not have mdk in it. It's rooted with 4.4.4, so I know it has an unlocked bootloader. The phone I have now has the mdk in the baseband. My question is how can this be? I know it's been updated, but I didn't think you could update it without loosing the unlocked bootloader. Thanks
Click to expand...
Click to collapse
You could try to fix it yourself, or buy a replacement port and find a small electronics repair shop to do it for you...
https://www.ifixit.com/Guide/Samsung+Galaxy+S4+USB+Board+Replacement/16542
http://www.amazon.com/ePartSolution...sim_cps_1?ie=UTF8&refRID=1NMWVPP4H227S5XYBGJ0
wily5150 said:
I have a gs4 with an unlocked bootloader (MDK baseband). The data port on mine went south, so I'm looking for another one on swappa. I found one but the baseband does not have mdk in it. It's rooted with 4.4.4, so I know it has an unlocked bootloader. The phone I have now has the mdk in the baseband. My question is how can this be? I know it's been updated, but I didn't think you could update it without loosing the unlocked bootloader. Thanks
Click to expand...
Click to collapse
Being rooted doesn't mean you have an unlocked bootloader. They are two completely different things. That being said, you should try everything you can to hold on to your MDK phone. They are like gold around here now.
Sent from my NCC-1701 using Tapatalk.
I've rooted a mek device using towelroot. and it didnt have a unlocked bootloader.So like the above poster said, just cause its rooted doesn't mean its MDK
Also, keep in mind that you can't always go by what the build number in About Phone says...cuz even though I have MDK firmware, my build number in the ROM I'm running says that my build number is NE5.
A great tool for determining the ACTUAL firmware/build number is Samsung Phone Info from the Play Store
Keep it kid!
Thanks for your input. I will buy the charge port from the link you provided. I never even thought about fixing it myself. Good job. Thanks again
Will unlocked version of sprint get an OTA
aukhan said:
Will unlocked version of sprint get an OTA
Click to expand...
Click to collapse
Do you mean "bumped," with TWRP recovery?
If so, you'll still get notified about the OTA. The OTA should fail to run, but on my last device some people had the KitKat update run even though they had a custom recovery, and it screwed up all sorts of things. So don't accept the OTA if you get it.
To make sure you don't get the OTA, see this thread: http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
If by "unlocked" you mean something else, please explain.
As long as the phones system is totally original with no mods or deleted files you should get ota...depends on how it was unlocked.
Sent from rotary technology Phone
meyerweb said:
Do you mean "bumped," with TWRP recovery?
If so, you'll still get notified about the OTA. The OTA should fail to run, but on my last device some people had the KitKat update run even though they had a custom recovery, and it screwed up all sorts of things. So don't accept the OTA if you get it.
To make sure you don't get the OTA, see this thread: http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
If by "unlocked" you mean something else, please explain.
Click to expand...
Click to collapse
Droid2drummer said:
As long as the phones system is totally original with no mods or deleted files you should get ota...depends on how it was unlocked.
Sent from rotary technology Phone
Click to expand...
Click to collapse
I am basically getting a used device from a Friend of mine who got it from US and now in India its a Sprint variant and he is currently using it here, Where as he is not in to Rooting and Customizing, Where as I am so Ill be getting the device today evening, I need to know if its unlocked CAN it be locked again by Sprint (Not sure how it was unlocked) if its locked again can i use Bump and Unlock.
aukhan said:
I am basically getting a used device from a Friend of mine who got it from US and now in India its a Sprint variant and he is currently using it here, Where as he is not in to Rooting and Customizing, Where as I am so Ill be getting the device today evening, I need to know if its unlocked CAN it be locked again by Sprint (Not sure how it was unlocked) if its locked again can i use Bump and Unlock.
Click to expand...
Click to collapse
Im sure if its unlocked it can still get ota by flashtool. If system is changed. But as far as root or bump. Certainly can. It can be bumped stumped etc. And flashtool back for ota. Depending how it was unlocked. Meaning if it was rooted to unlock then will have to flashtool back im almost sure. Again if your wanting to make sure it stays unlocked usually once unlocked it will stay. I guess it will depend how. And if oem unlocked then im sure re locking is not much of an option. However you should be fine from many of these worries. Hope not to confuse you. Im very tired. Lol. Trying to cover all bases. There are many ways to unlock many devices on many carriers so its really hard to say. But there are mostly generalized options one would believe.
Sent from rotary technology Phone
Droid2drummer said:
Im sure if its unlocked it can still get ota by flashtool. If system is changed. But as far as root or bump. Certainly can. It can be bumped stumped etc. And flashtool back for ota. Depending how it was unlocked. Meaning if it was rooted to unlock then will have to flashtool back im almost sure. Again if your wanting to make sure it stays unlocked usually once unlocked it will stay. I guess it will depend how. And if oem unlocked then im sure re locking is not much of an option. However you should be fine from many of these worries. Hope not to confuse you. Im very tired. Lol. Trying to cover all bases. There are many ways to unlock many devices on many carriers so its really hard to say. But there are mostly generalized options one would believe.
Sent from rotary technology Phone
Click to expand...
Click to collapse
Thanks for such a detailed answer,
Now when I get the bhone should i be unlocking Bootloader ?
Please suggest me an easy way to ROOT this device?
Which is the most customizied Rom available on this Sprint Thread, I am sure I should not be flashing any other Carrier Roms or International Version of ROM which may Brick the device.
My Friend is claiming that is factory unlocked,Is there a way to find if device is Factory unlocked ??
Hi,I want to install custom rom. (like most people) but, With htc one m7 I used the warranty, so, I want to be able to use it with the M8. My question is. to return full stock, its need s off right? Right now I cant afford 25 for the soff (in my country, outside of USA is a little more difficult because the conversion). So, if I use the dev unlock bootloader, Can I install custom any rom ( i ask because I dont know where I saw custom rom requiring S-OFF) and then do the s off after a while (maybe 2 o 3 months). If I use dev unlock from htc, they will be able to track that I install custom roms? And how about bricks, wich side is safest (only unlock bootloader or Soff) and wich side is more easy to recover?.
Thanks in advance
lorddavid said:
Hi,I want to install custom rom. (like most people) but, With htc one m7 I used the warranty, so, I want to be able to use it with the M8. My question is. to return full stock, its need s off right? Right now I cant afford 25 for the soff (in my country, outside of USA is a little more difficult because the conversion). So, if I use the dev unlock bootloader, Can I install custom any rom ( i ask because I dont know where I saw custom rom requiring S-OFF) and then do the s off after a while (maybe 2 o 3 months). If I use dev unlock from htc, they will be able to track that I install custom roms?
Click to expand...
Click to collapse
HTC will typically not honor a warranty for a device purchased from and intended for another country. However, how HTC handles warranty seems to vary from one location to another. Did you buy the M7 from the US?
Along those lines, how HTC handles bootloader unlocks via HTCDev.com also seems to vary from one country to another. Yes, they can and will track the phones IMEI by HTCDev.com, and know you requested a bootloader unlock code. Some folks have had their warranty claims denied that way. But others are successful returning the phone to bootloader LOCKED (not RELOCKED, s-off required to make it LOCKED after unlocking it), stock software, possibly s-on.
You don't need s-off to flash ROM. But you will want to make sure your firmware is up to date. If the phone is on stock Lollipop, the firmware is probably up to date (especially if the phone was purchased new, not used). Otherwise, s-off makes it a bit easier to update firmware, but its also possible with s-on.
lorddavid said:
And how about bricks, wich side is safest (only unlock bootloader or Soff) and wich side is more easy to recover?.
Click to expand...
Click to collapse
Are you talking about recovering from no-boot conditions? s-off always gives more options. But most cases of no boot are solved by flashing custom recovery again, flashing a ROM, or other functions possible with s-on.
Yes, with M7 I bought it from ATT, and they honor the warranty, but IN USA. I was there in vacation and send it. I'm in kitkat, I didnt update with RUU because dont know if sunshine works on latest firmware. So, even if I unlock with dev unlock. And after that I use S-OFF to make it Locked, they still can track it? In theory is better to go with S-OFF directly?
lorddavid said:
Yes, with M7 I bought it from ATT, and they honor the warranty, but IN USA. I was there in vacation and send it.
Click to expand...
Click to collapse
Based on reports I've seen on XDA, your warranty won't be honored since you are not located in the US. Of course, if you travel back to the US, or send it to a US friend to send in for warranty, that might work.
lorddavid said:
I'm in kitkat, I didnt update with RUU because dont know if sunshine works on latest firmware. So, even if I unlock with dev unlock. And after that I use S-OFF to make it Locked, they still can track it? In theory is better to go with S-OFF directly?
Click to expand...
Click to collapse
Sunshine s-off function still works on Lollipop. However, the root function does not (and root is needed to s-off). Some folks have temp rooted, and able to get s-off to work (then bootloader unlock).
But I would recommend using sunshine to root, s-off then bootloader unlock (bypassing HTCDev.com) all those things with sunshine; while still on KitKat (before RUU to Lollipop), if you are worried about warranty.
lorddavid said:
So, even if I unlock with dev unlock. And after that I use S-OFF to make it Locked, they still can track it?
Click to expand...
Click to collapse
Yes, they can still track it. The bootloader unlock code is based on your IMEI, and they are probably tracking/recording the IMEI numbers that go through HTCDev.com.
I think some folks have been successful making the phone back to LOCKED (and even s-off) and of course also stock software, and getting the warranty honored. But I'd say its no guarantee. Some folks will also say they can't "legally" void your warranty for requesting an unlock bin code (as long as you return to "full" stock) as they can only prove you requested a code, not that you actually used it.
But at that point, its your word against there's. HTC holds the cards here. You can try to fight it, but in the meantime you still don't have a working phone.
To some degree, when we all mod our phones, we have to assume that there is some risk that warranty will be void.
Ok, so I think that I will save mone for S-OFF, better play safe. Just a question, to update firmware I need to RUU? (After S-Off of course) Or can you point me to a guide to flash latest sense and lollipop rom? (I know how to flash recovery, s off, etc. but not sure about the match of firmware or what firmware/radio to use). THanks
lorddavid said:
Ok, so I think that I will save mone for S-OFF, better play safe. Just a question, to update firmware I need to RUU? (After S-Off of course) Or can you point me to a guide to flash latest sense and lollipop rom? (I know how to flash recovery, s off, etc. but not sure about the match of firmware or what firmware/radio to use).
Click to expand...
Click to collapse
You can update firmware (after s-off) with AT&T Lollipop RUU, or by flashing a firmware.zip in fastboot.
Flashing AT&T firmware will keep the same band support. If you want to change the band support, you can flash another version's firmware. But it depends on what bands your carrier uses for 3G and 4G (LTE).
redpoint73 said:
You can update firmware (after s-off) with AT&T Lollipop RUU, or by flashing a firmware.zip in fastboot.
Flashing AT&T firmware will keep the same band support. If you want to change the band support, you can flash another version's firmware. But it depends on what bands your carrier uses for 3G and 4G (LTE).
Click to expand...
Click to collapse
Its more fast to just flash the firmware i think, because I dont need to download all the RUU.
And with the HTC really can change the band support? I think that is something of hardware. But if that can be done I want to try it.
I will search for the Firmware for flash. If I have problems I will ask. Thanks again
EDIT: I'm preparing , found some firmware but cant see from wich carrier are. Are those https://www.androidfilehost.com/?w=files&flid=32780
EDIT 2: I found that the numbers means the region. So, whats the latest firmware? Can I flash it even if my phone is ATT? Because I saw Just 1 for ATT
lorddavid said:
And with the HTC really can change the band support? I think that is something of hardware. But if that can be done I want to try it.
Click to expand...
Click to collapse
You are somewhat correct, in that before the M8, band support was set in hardware on most (or all?) phones.
But a new feature of the Snapdragon 801 chipset, is that band support is set in software. Flashing another CID's firmware will change the band support (may need to change CID and MID, and s-off required to change CID/MID).
lorddavid said:
EDIT: I'm preparing , found some firmware but cant see from wich carrier are. Are those https://www.androidfilehost.com/?w=files&flid=32780
Click to expand...
Click to collapse
AT&T is 502. But that thread only has 1.54.502 (which is same or probably even older than current firmware), and what you want (latest) is 4.28.502.
You can get the 4.28.502 firmware on the following thread, but you have to download the ROM with it (all packed in the same zip):
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Not sure if 4.28.502 firmware is posted by itself anywhere else (I haven't seen so).
redpoint73 said:
You are somewhat correct, in that before the M8, band support was set in hardware on most (or all?) phones.
But a new feature of the Snapdragon 801 chipset, is that band support is set in software. Flashing another CID's firmware will change the band support (may need to change CID and MID, and s-off required to change CID/MID).
AT&T is 502. But that thread only has 1.54.502 (which is same or probably even older than current firmware), and what you want (latest) is 4.28.502.
You can get the 4.28.502 firmware on the following thread, but you have to download the ROM with it (all packed in the same zip):
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Not sure if 4.28.502 firmware is posted by itself anywhere else (I haven't seen so).
Click to expand...
Click to collapse
Thanks, thats new to me. And yes I found under 1540 a more recent firmware. So there is 0 risk of brick flashing other firmware right? I need SuperCID? Or is the same with ATT? (I'm curious for trying because with my phone my 3G speed is capped to 1mb dont know why, and other friends, same plan, other phone, have more speed)
lorddavid said:
Thanks, thats new to me. And yes I found under 1540 a more recent firmware. I need SuperCID? Or is the same with ATT?
Click to expand...
Click to collapse
Pretty sure you need to change your CID either to Dev Edition CID or SuperCID.
lorddavid said:
So there is 0 risk of brick flashing other firmware right?
Click to expand...
Click to collapse
There is never zero brick risk. Your phone can brick just sitting there, doing nothing (very unlikely, but its possible). In particular, flashing hboot (which firmware does) if anything goes wrong (for instance, don't disconnect the phone while its flashing!) while writing hboot, it will brick.
But flashing another CID's firmware is low risk. Probably no more risk than flashing the proper CID firmware, or doing an official RUU or OTA.