I KNEED AN ANSWER TO THIS SUBJECT.
I have read some of the posts about the new EVO 4G update, and some of the people have complained about the new update has a locked bootloader.
I need to know is it really locked?
I downloaded a Android 2.3.3 update a couple of months ago, and it came with the new fastboot option enabled by default. With fastboot enabled, the phone boots much faster, but you would be locked out of the bootloader. That was only until you disabled it. Then it was business as usual getting into the bootloader (volume down + power button).
Now I hear that some of the people who have downloaded the latest (unrooted) EVO update have their bootloaders locked, while others were able to do a nandroid recovery to restore their phones after updating because the phone was still S-OFF. That would mean that the bootloader is still unlocked. How can a bootloader be both locked and unlocked.
Is the bootloader really locked by the update, or is it just temporarily locked because these people did not turn off the fastboot option in the settings, which does bypass the bootloader. Does anyone know, or how many people know the answer to this?
It's locked and not encrypted is what I believe.
Sent from my PC36100 using Tapatalk
novanosis85 said:
It's locked and not encrypted is what I believe.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Any sources for this information, or did I overlook a post?
how to access recovery after 2.3.3 update
1.Turn phone off. 2. Remove battery from phone. 3.Hold Volume button down and power button at same time for like 7 seconds. 4. That's it.
If you get a new EVO 4g with 2.3.3 yes it will be locked. HTC said all future devices will be unlocked that is why the EVO 4g is still locked.
The EVO 4g OTA and 2.3.3 out of the box is not encrypted just locked.
Source: me doing a lot of reading today.
Locked. Not encrypted.
I have a hunch that HTC meant to say that their bootloaders would no longer be encrypted rather than locked.
pharmteckCA said:
1.Turn phone off. 2. Remove battery from phone. 3.Hold Volume button down and power button at same time for like 7 seconds. 4. That's it.
Click to expand...
Click to collapse
When are you supposed to put the battery back in??? I'm confused
soxfan81 said:
When are you supposed to put the battery back in??? I'm confused
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"
}
Sent from my PC36100 using Tapatalk
If you were s off when updating, you will still be able to flash recoveries and roms etc. If you were s on and updated, your SOL for now.
exSD said:
Locked. Not encrypted.
I have a hunch that HTC meant to say that their bootloaders would no longer be encrypted rather than locked.
Click to expand...
Click to collapse
First of all, there isn't a phone out there with an encrypted bootloader. There are however cryptographically signed bootloaders. Huge difference.
Second, they did in fact say the bootloaders will no longer be locked.
Rakeesh_j said:
cryptographically
Click to expand...
Click to collapse
That's a crazy serious word right there.
mattykinsx said:
That's a crazy serious word right there.
Click to expand...
Click to collapse
+1 it makes me feel retarded.
HTC EVO = my best friend
I wonder if we can just OEM unlock it in fastboot?
RileyGrant said:
If you were s off when updating, you will still be able to flash recoveries and roms etc. If you were s on and updated, your SOL for now.
Click to expand...
Click to collapse
So, if someone's phone is still S-OFF after updating, and they could just flash another recovery, and then a ROM or backup, then how is the bootloader locked?
shortydoggg said:
So, if someone's phone is still S-OFF after updating, and they could just flash another recovery, and then a ROM or backup, then how is the bootloader locked?
Click to expand...
Click to collapse
Good question
Sent from my PC36100 using XDA App
shortydoggg said:
So, if someone's phone is still S-OFF after updating, and they could just flash another recovery, and then a ROM or backup, then how is the bootloader locked?
Click to expand...
Click to collapse
if your not S-OFF you can't.
asked and answered.
Alanmw86 said:
if your not S-OFF you can't.
asked and answered.
Click to expand...
Click to collapse
That did not answer the question.
The question was if your phone is S-OFF, then how is the bootloader locked, NOT WHAT YOU CANNOT DO IF YOUR PHONE IS NOT S-OFF. We already know that.
The reason I asked this question, is because some people have installed the latest update and rerooted their phones because the phones were still S-OFF. This would seem to suggest that the bootloaders are not locked.
If you do not turn off the fastboot option in the settings, or reset the battery, the bootloader will be bypassed, making it appear that the bootloader is locked when it may not be. I would like to know if anyone installed the latest (unrooted) update, and disabled the fastboot or reset the battery, and found that the bootloader is in fact locked.
My guess is that the update doesn't check your security bit, however it still prevents custom firmware from being loaded in that there isn't any mechanism available to load any custom firmware.
In other words, if your security bit is off already, and you update, you can still place a pc3600.img on your sdcard and have it flash that without it performing a signature check first.
However if your security bit is on at the time of applying the update, then you're a bit SOL, because prior to flashing the new image, it will perform a signature check.
Again, that is just my guess (haven't looked at the update as I've been using AOSP for a long time now.)
shortydoggg said:
That did not answer the question.
The question was if your phone is S-OFF, then how is the bootloader locked, NOT WHAT YOU CANNOT DO IF YOUR PHONE IS NOT S-OFF. We already know that.
The reason I asked this question, is because some people have installed the latest update and rerooted their phones because the phones were still S-OFF. This would seem to suggest that the bootloaders are not locked.
If you do not turn off the fastboot option in the settings, or reset the battery, the bootloader will be bypassed, making it appear that the bootloader is locked when it may not be. I would like to know if anyone installed the latest (unrooted) update, and disabled the fastboot or reset the battery, and found that the bootloader is in fact locked.
Click to expand...
Click to collapse
I had S-off and ran the OTA, no problem turning off the fast boot option and flashing either Clockworkmod or AmonRa. But I did have to switch to AmonRa in order to run the update, it wouldn't install with CWM.
tempe38 said:
I had S-off and ran the OTA, no problem turning off the fast boot option and flashing either Clockworkmod or AmonRa. But I did have to switch to AmonRa in order to run the update, it wouldn't install with CWM.
Click to expand...
Click to collapse
Does anyone who still has S-OFF and installed the new OTA have the new hboot version 2.16?
Related
Yesterday, it randomly started force closing all apps repeatedly (force close loop) and often freezing until the battery was pulled. It would work fine after powering on for 30-60 minutes at a time but then start messing up again. Sometimes it messed up right away though.
Today I made a nandroid backup and then tried wiping data/factory reset and wiping cache. I get this:
{
"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"
}
I know that is not good. But what does it mean??
---
Anyway, now no matter what ROM I flash (CM7.0.0, or an old nightly 37, 41, etc), I click "Reboot system now" and the screen just goes to black forever. I have to pull the battery again.
But then it freezes at the MyTouch 4G screen (left it for 10+ minutes). It never gets past that.
Yes, I even did a nandroid backup before wiping. But even restoring that does the same thing: it restores, I click reboot, and it goes to a black screen.
But no matter what, after a battery pull, it just freezes at the MyTouch 4G screen forever.
I *can* get into the white hboot/fastboot screen via Power + Volume Down and then get into CWM Recovery from there.
It just can't *boot* into any Android rom.
Am I bricked?? Is there a way to fix this??
Please help!
Everyone that i am aware of that has encounter this has not been able to recover from it.
It looks like it might be truly bricked.
Do u have the good emmc chip or bad? Theres plenty of threads regardin that issue...
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.4
Yup it looks like your eMMC chip went bad. I have a phone here that is doing the same exact thing. I have tried everything from fastbooting a new bootloader to the PD15 whatever its called full restore image. Nothing is working at all. I fear you have a truly bricked phone.
Ah [email protected]#!#[email protected]#[email protected]#$!$ !!!!!
A) What could have caused this?? From my viewpoint, of course it seems totally random but from reading other people's cases, have you guys seen any common link or can think of something that could have caused this?
[Edit] And B) Also, do you think T-Mobile would warranty replace it even though it is rooted with CyanogenMod 7 (even though it cannot be seen)? It was purchased Oct 2010, and I do have insurance on it.
Paul22000 said:
Ah [email protected]#!#[email protected]#[email protected]#$!$ !!!!!
A) What could have caused this?? From my viewpoint, of course it seems totally random but from reading other people's cases, have you guys seen any common link or can think of something that could have caused this?
[Edit] And B) Also, do you think T-Mobile would warranty replace it even though it is rooted with CyanogenMod 7 (even though it cannot be seen)? It was purchased Oct 2010, and I do have insurance on it.
Click to expand...
Click to collapse
once they see Clockwork ROM manager they'll know it was rooted.
cmdmilitia13 said:
Do u have the good emmc chip or bad? Theres plenty of threads regardin that issue...
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.4
Click to expand...
Click to collapse
How do I check?
neidlinger said:
once they see Clockwork ROM manager they'll know it was rooted.
Click to expand...
Click to collapse
Well, A) that's only if they press Volume Down + Power button. Do they normally know how to do that?
Also, B) is there a way to remove CWM?
Paul22000 said:
How do I check?
Click to expand...
Click to collapse
you have to be able to get into recovery.
http://forum.xda-developers.com/showpost.php?p=13834944&postcount=1
neidlinger said:
once they see Clockwork ROM manager they'll know it was rooted.
Click to expand...
Click to collapse
I have heard of people frying their motherboards by over volting the charging port so they no longer turn on before sending it in for a warranty return. I cant comment on this but if I can get mine warrantied that way I will do it. Not like the motherboard is any good now so might as well try. However! I do not suggest doing this.
Paul22000 said:
Well, A) that's only if they press Volume Down + Power button. Do they normally know how to do that?
Also, B) is there a way to remove CWM?
Click to expand...
Click to collapse
I'm sure they check first thing.
technically you could if you have the .85 hBoot.
But if you have the .85 hBoot they'll know the phone was tampered with since the engineering screen is different
neidlinger said:
you have to be able to get into recovery.
http://forum.xda-developers.com/showpost.php?p=13834944&postcount=1
Click to expand...
Click to collapse
Unfortunately, I'm not able to use adb even though I have it installed:
What am I missing here to get adb working?
In case I can't get that working, do any of these help to see if my emmc is bad?
Paul22000 said:
Unfortunately, I'm not able to use adb even though I have it installed:
What am I missing here to get adb working?
In case I can't get that working, do any of these help to see if my emmc is bad?
Click to expand...
Click to collapse
to get the phone working again? nope. To get it to an honest warrant-able state yes.
I was able to check the eMMC chip version on my bricked phone so you should be able to also. You need to be in clockwork recovery to do it.
neidlinger said:
to get the phone working again? nope. To get it to an honest warrant-able state yes.
Click to expand...
Click to collapse
Yes, at this point I don't care about getting this phone working. I have been paying for insurance every month since October, so getting it replaced is fine by me.
I just want to know how to get the phone in a state so that T-Mobile doesn't deny my warranty because I put CyanogenMod on it.
How do I get to back to a warrant-able state? That would be AMAZING. Any would would be MUCH appreciated!
Paul22000 said:
Yes, at this point I don't care about getting this phone working. I have been paying for insurance every month since October, so getting it replaced is fine by me.
I just want to know how to get the phone in a state so that T-Mobile doesn't deny my warranty because I put CyanogenMod on it.
How do I get to back to a warrant-able state? That would be AMAZING. Any would would be MUCH appreciated!
Click to expand...
Click to collapse
it's pretty much impossible at this state. If you have the .85 hBoot you could flash the stock image. but you need a working rom to flash back to .86 hBoot. When you do not have.
neidlinger said:
it's pretty much impossible at this state. If you have the .85 hBoot you could flash the stock image. but you need a working rom to flash back to .86 hBoot. When you do not have.
Click to expand...
Click to collapse
Wait? I thought you said I could get it back to warrant-able state in your last post? Did I misunderstand what you said?
Either way, is there a way to just get rid of CWM?
If I can do that, then the *ONLY* way for them to tell I did anything would be the hboot version at the top, correct?
I would be willing to try going to multiple T-Mobile stores and hoping to find someone that didn't know about hboot versions.
So as long as I can get rid of CWM, I will be confident enough to go to multiple T-Mobile stores in order to TRY to get a replacement.
Is there a way to get rid of CWM on a bricked phone?
Paul22000 said:
Wait? I thought you said I could get it back to warrant-able state in your last post? Did I misunderstand what you said?
Either way, is there a way to just get rid of CWM?
If I can do that, then the *ONLY* way for them to tell I did anything would be the hboot version at the top, correct?
I would be willing to try going to multiple T-Mobile stores and hoping to find someone that didn't know about hboot versions.
So as long as I can get rid of CWM, I will be confident enough to go to multiple T-Mobile stores in order to TRY to get a replacement.
Is there a way to get rid of CWM on a bricked phone?
Click to expand...
Click to collapse
i did say to get it to a warrant-able state you need ADB up and running. But there lies a problem when, and i mentioned, it will not get the phone working again.
you need two things 1) a stock recovery image 2) to flash the stock .86 hBoot.
If you have the engineering hBoot, .85 you can flash the stock recovery image. Just has you would flash clockwork via hBoot. but to get back to the stock .86 hBoot you need to have the phone up and running. Which you cannot do at this point. You are correct the only way they would tell if it's been tampered with is the .85.xxxxx hBoot version at the top of the screen.
If you have the .85 hBoot you could try flashing the stock recovery image to the phone and see if that will overwrite CWM.
neidlinger said:
i did say to get it to a warrant-able state you need ADB up and running. But there lies a problem when, and i mentioned, it will not get the phone working again.
you need two things 1) a stock recovery image 2) to flash the stock .86 hBoot.
If you have the engineering hBoot, .85 you can flash the stock recovery image. Just has you would flash clockwork via hBoot. but to get back to the stock .86 hBoot you need to have the phone up and running. Which you cannot do at this point. You are correct the only way they would tell if it's been tampered with is the .85.xxxxx hBoot version at the top of the screen.
If you have the .85 hBoot you could try flashing the stock recovery image to the phone and see if that will overwrite CWM.
Click to expand...
Click to collapse
A) So just to make absolutely sure. Even with ADB, there's 0% chance of ever getting this phone booting into Android again, correct?
B) If so, well replacement is the only opton. So from the pictures above in post #12, I have 0.85, yes?
C) So I just need to flash the stock recovery image from CWM to overwrite CWM?
D) If all three are correct, then which file do I need to flash? Is is one of the two files listed here? http://forum.xda-developers.com/showthread.php?t=843289
Paul22000 said:
A) So just to make absolutely sure. Even with ADB, there's 0% chance of ever getting this phone booting into Android again, correct?
B) If so, well replacement is the only opton. So from the pictures above in post #12, I have 0.85, yes?
C) So I just need to flash the stock recovery image from CWM to overwrite CWM?
D) If all three are correct, then which file do I need to flash? Is is one of the two files listed here? http://forum.xda-developers.com/showthread.php?t=843289
Click to expand...
Click to collapse
a) with adb up and running you can flash the stock recovery image, but not the old school hBoot
b) i am at work and WebSense blocks alot of images.
c) yes
d) depends on if you had the pre or post OTA recovery image.
im actually trying to unroot my phone. i rooted it using unrevoked and was wondering where i can find a manual on how to unroot. thanks
Though I have seen no manuals, there are plenty of tutorials, walk-throughs, wiki's, etc... Just a search box away.
*hint check the stickies as well
just did this the other day.
Am still new xda user so i cant post the links, but the general steps are to get the 'unrevoked s-on' tool from the unrevoked site & follow their steps to reflash to S=ON.
After your phone is s-on download htcsync from the HTC site and install that (for latest usb drivers). If need be uninstall old versions first.
after htc sync is installed grab the RRU version you want to flash back to and double click the exe. From there its idiot proof, click 'next' to continue.
I used RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe (md5: 26dcb19a186128e46f6d52a29cccd7cc) from the shipped-roms site
needless to say, once you unroot dont get the OTAs from sprint, youll get hosed trying to root again until 2.3.3 (hboot 2.16) method is released.
Flash this in your custom recovery. S-on.zip
Download this and rename it to PC36IMG.zip and then put it on the root of your SDCARD, boot into your bootloader and select yes to the update.
Didn't mean to interrupt anyone's helping but it's easier with links.
mattykinsx said:
Flash this in your custom recovery. S-on.zip
Download this and rename it to PC36IMG.zip and then put it on the root of your SDCARD, boot into your bootloader and select yes to the update.
Didn't mean to interrupt anyone's helping but it's easier with links.
Click to expand...
Click to collapse
you don't happen to have the newest RUU?
evolishesh said:
you don't happen to have the newest RUU?
Click to expand...
Click to collapse
Not released yet.
Easiest way is to run that RUU and update OTA.
Warning if you do update to 2.3.3, root has NOT been achieved so you'll be stuck there.
mattykinsx said:
Didn't mean to interrupt anyone's helping but it's easier with links.
Click to expand...
Click to collapse
No sweat. You linked him to exactly what he needs. Good man!
Worked great! Thanks guys!!
Sent from my PG86100 using XDA Premium App
Thanks matty
sling said:
Thanks matty
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"
}
My power button is busted and need to take it to Sprint for repair. I used unrevoked to root and went into bootloader and see i have s-off, hboot 0.97 and radio 2.15.00.04.08. How am I able to get s-on if i cant flash the s-on tool due to my power button? Help is much needed, thanks.
Deadbolt said:
My power button is busted and need to take it to Sprint for repair. I used unrevoked to root and went into bootloader and see i have s-off, hboot 0.97 and radio 2.15.00.04.08. How am I able to get s-on if i cant flash the s-on tool due to my power button? Help is much needed, thanks.
Click to expand...
Click to collapse
Honestly, if you just run a RUU so that it looks stock they're not gonna notice.
mattykinsx said:
Honestly, if you just run a RUU so that it looks stock they're not gonna notice.
Click to expand...
Click to collapse
Which RUU do I run? And then how do I root it back when the power button is fixed?
Deadbolt said:
Which RUU do I run? And then how do I root it back when the power button is fixed?
Click to expand...
Click to collapse
Read the first post, part that's bolded for your s-on/power button issue:
http://forum.xda-developers.com/showthread.php?t=998372
Which RUU...well you can run the latest since you're returning it...
http://www.mediafire.com/file/bjxvu....651.1-4.24.651.1_release2dk2r14ngv5s3bvl.zip
Rename it PC36IMG.zip
When you get a replacement it will likely have 2.3.3 installed so you have to use the revolutionary way.
http://forum.xda-developers.com/showthread.php?t=1228566
mattykinsx said:
Read the first post, part that's bolded for your s-on/power button issue:
http://forum.xda-developers.com/showthread.php?t=998372
Click to expand...
Click to collapse
I looked at that thread but ROM manager won't work from what I gathered when i ran the app. I don't have clockworkmod recovery installed to flash it through ROM manager. I currently have Amon RA recovery.
mattykinsx said:
Which RUU...well you can run the latest since you're returning it...
http://www.mediafire.com/file/bjxvu....651.1-4.24.651.1_release2dk2r14ngv5s3bvl.zip
Rename it PC36IMG.zip
Click to expand...
Click to collapse
Most likely I won't be getting a replacement because the problem is repairable. I'd like an RUU that I can easily root after they repair the phone.
Deadbolt said:
I looked at that thread but ROM manager won't work from what I gathered when i ran the app. I don't have clockworkmod recovery installed to flash it through ROM manager. I currently have Amon RA recovery.
Click to expand...
Click to collapse
You can just change your recovery to clockworkmod via ROM Manager...
Deadbolt said:
Most likely I won't be getting a replacement because the problem is repairable. I'd like an RUU that I can easily root after they repair the phone.
Click to expand...
Click to collapse
No reason that you can't easily root the newest RUU.
Also, I had this same issue and they couldn't repair it. Had to replace the Evo.
mattykinsx said:
You can just change your recovery to clockworkmod via ROM Manager...
Most likely I won't be getting a replacement because the problem is repairable. I'd like an RUU that I can easily root after they repair the phone.
Click to expand...
Click to collapse
No reason that you can't easily root the newest RUU.
Also, I had this same issue and they couldn't repair it. Had to replace the Evo.[/QUOTE]
Lemme see if I can get ROM manager to flash the s-on tool...
I called the sprint repair store and they told me it was repairable and I wouldn't need a replacement but who knows if they were blowing smoke up my ass. I really don't want to pay a deductible...
Deadbolt said:
Lemme see if I can get ROM manager to flash the s-on tool...
I called the sprint repair store and they told me it was repairable and I wouldn't need a replacement but who knows if they were blowing smoke up my ass. I really don't want to pay a deductible...
Click to expand...
Click to collapse
It can be repairable.
It just depends on if it's the button itself or the board.
In my case it was the board and therefore was a defect.
As long as it's not due to physical/water damage they will replace it [if necessary] without a deductible.
mattykinsx said:
No reason that you can't easily root the newest RUU.
Also, I had this same issue and they couldn't repair it. Had to replace the Evo.
Click to expand...
Click to collapse
Currently trying to get ROM manager to flash the clockworkmod recovery...is there an RUU still available that allows me to flash to root with the capability of unrooting after I re-root my phone if needed? I've read revolutionary, you can't unroot.
Deadbolt said:
Currently trying to get ROM manager to flash the clockworkmod recovery...is there an RUU still available that allows me to flash to root with the capability of unrooting after I re-root my phone if needed? I've read revolutionary, you can't unroot.
Click to expand...
Click to collapse
I've read you can't get s-on but I saw a post in the thread in Q&A (asking how) with a response that might tell you how.
I'd give you the link but I'm in bed now.
I believe its still I page one on that sub.forum
So, I don't mean to start a panic for the remaining Atrix faithful here, but it seems like Motorola has started to block the ability to flash SBF's, including the pudding/IHOP files, on New and replacement Atrix phones. I've been in discussions with at least three recipients of replacement devices over the last three days that all have the same issue.
Anytime any SBF file is flashed to the device it fails with the error SFV:106:1:2 Unable to reenumerate device (or something similar). It does not put you into fastboot or give you the options it used to, you simply have to battery pull and the phone boots normally as if nothing ever happened. Even the current version SBF for AT&T (4.5.141) will not flash to the phone; it ends in the same error.
Without being able to flash ANY SBFs, that means the bootloader on these new phones remains locked down for the moment. I know we have lost many of our original developers that worked to try to unlock the bootloader the first time, but I also know we have many talented devs currently with us.
Is there anyone able to provide insight as to what might have been changed by Motorola and how we might be able to overcome it?
Here are links to my discussions with them, as well as another post I just found that is similar from a Bell user:
http://www.atrixforums.com/forum/showthread.php?p=107507
http://forum.xda-developers.com/showthread.php?p=25167191 (not sure if same situation, sounds possibly similar)
Sent from my MB860 using Tapatalk 2
Can anyone confirm this has happened to them? Motorola will lose alot of loyal customers, myself included, if they pull this bull.
yes it is true. i got my atrix today, i sent it in and i tried to unlock it right away but that proved to be impossible. if you follow those links, i have the exact same symptoms.
If anyone who is experiencing this can run some tests for samcripp, it looks like he's willing to help where he can. See this post here: http://www.atrixforums.com/forum/motorola-atrix-hacks/3331-tut-unlocking-bootloader-installing-custom-roms-63.html#post108017
Thanks!
That is so lame! This was my first Motorola smartphone and I have a feeling it will be my last.
Sent from my MB860 using xda premium
Just use the automated boot loader unlock it worked for my friend
Sent from my MB860 using XDA
kufusoto said:
Just use the automated boot loader unlock it worked for my friend
Sent from my MB860 using XDA
Click to expand...
Click to collapse
So far, that has failed with the same result for the two users that have tried it under these conditions.
i replied on the other forum
kufusoto said:
Just use the automated boot loader unlock it worked for my friend
Sent from my MB860 using XDA
Click to expand...
Click to collapse
did he ever send it into moto for any repairs?
Unable to unlock BL
I have had my Atrix 4G for almost 1 year. It was purchased as a refurb directly from AT&T. It came with Froyo on it & I patiently waited for and applied the OTA to 2.3.4 and 2.3.6. I was able to successfully root it but it will not give me the Unique ID when I run "fastboot oem unlock". It says:
C:\fastboot>fastboot oem unlock
...
(bootloader) OEM unlock is not implemented
OKAY [ 0.001s]
finished. total time: 0.001s
I will get the FUSE and edit this post.
ReservedOdm: 10000000000030001000300000000
BKrenning said:
I have had my Atrix 4G for almost 1 year. It was purchased as a refurb directly from AT&T. It came with Froyo on it & I patiently waited for and applied the OTA to 2.3.4 and 2.3.6. I was able to successfully root it but it will not give me the Unique ID when I run "fastboot oem unlock". It says:
C:\fastboot>fastboot oem unlock
...
(bootloader) OEM unlock is not implemented
OKAY [ 0.001s]
finished. total time: 0.001s
I will get the FUSE and edit this post.
Click to expand...
Click to collapse
You need to flash the "pudding" SBF unlocker file before using the fastboot commands. See the Unlock/IHOP sticky post at the top of the Development section.
Sent from my MB860 using Tapatalk 2
{
"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"
}
this is what i get after trying the automatic unlock tool.
it says unlocked but its not. its not rooted either. what did you use to root? like ^^^ it never showed my unique ID and just hung there.
thegogetter- said:
this is what i get after trying the automatic unlock tool.
it says unlocked but its not. its not rooted either. what did you use to root? like ^^^ it never showed my unique ID and just hung there.
Click to expand...
Click to collapse
how is it not unlocked, if it says unlocked and starts fastboot? just fastboot flash romracers recovery onto it and thats it, than you can flash custom roms.
das8nt said:
So, I don't mean to start a panic for the remaining Atrix faithful here, but it seems like Motorola has started to block the ability to flash SBF's, including the pudding/IHOP files, on New and replacement Atrix phones. I've been in discussions with at least three recipients of replacement devices over the last three days that all have the same issue.
Anytime any SBF file is flashed to the device it fails with the error SFV:106:1:2 Unable to reenumerate device (or something similar). It does not put you into fastboot or give you the options it used to, you simply have to battery pull and the phone boots normally as if nothing ever happened. Even the current version SBF for AT&T (4.5.141) will not flash to the phone; it ends in the same error.
Without being able to flash ANY SBFs, that means the bootloader on these new phones remains locked down for the moment. I know we have lost many of our original developers that worked to try to unlock the bootloader the first time, but I also know we have many talented devs currently with us.
Is there anyone able to provide insight as to what might have been changed by Motorola and how we might be able to overcome it?
Here are links to my discussions with them, as well as another post I just found that is similar from a Bell user:
http://www.atrixforums.com/forum/showthread.php?p=107507
http://forum.xda-developers.com/showthread.php?p=25167191 (not sure if same situation, sounds possibly similar)
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
I get that error when
1. I try to flash a SBF file not meant for my phone. (Yeah... Stupid move)
2. There is a hardware problem with my phone.
---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------
thegogetter- said:
this is what i get after trying the automatic unlock tool.
it says unlocked but its not. its not rooted either. what did you use to root? like ^^^ it never showed my unique ID and just hung there.
Click to expand...
Click to collapse
If it never showed your unique ID, your phone has been unlocked before.
crnkoj said:
how is it not unlocked, if it says unlocked and starts fastboot? just fastboot flash romracers recovery onto it and thats it, than you can flash custom roms.
Click to expand...
Click to collapse
It did not start at fastboot automatically, he made it start at fastboot. =D Funny what some people do...
When I try to flash a recovery it hangs on waiting on device and doesn't do anything. I tried that already. I don't have root either
das8nt said:
You need to flash the "pudding" SBF unlocker file before using the fastboot commands. See the Unlock/IHOP sticky post at the top of the Development section.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
That's what I figured. I was hoping someone had come up with an easier route by now or at least figured out what was in the OTA that is blocking the phone from giving out it's unique id.
There is a Samsung Note on CL calling my name. Maybe I'll answer it--LOL.
Thank you for your help!
thegogetter- said:
When I try to flash a recovery it hangs on waiting on device and doesn't do anything. I tried that already. I don't have root either
Click to expand...
Click to collapse
Have you installed the drivers for your phone? If you're trying to flash a recovery, you should be unlocked and to unlock your phone, you would need the drivers.
Off the top of my head, the error from rsd seems like one you get when you try to use a ramloader from ATT with a Bell phone. That is why there were radio sbfs for Bell and for ATT separately.
You have to realise that the sbf files with the unlockable bootloaders are mods of existing sbf files and may simply be out of date with regard to the new phones. You would need a new sbf file to hack in the replacement bootloader. So what you are really looking for is another unlockable bootloader in the wild as part of a sbf that can be stripped down to just the bootloader part.
Or Motorola could just take it's **** out of it's ***.
Cheers!
i sent my atrix to get fixed in the last 3 weeks and i got it back, the bootloader was still unlocked but it needed to be "reminded" of it if you will. it had stock 4.5.151 on it and when it booted up there was no "unlocked" text and i couldn't flash a recovery, so i all i had to do was SBF to 2.3.4 and flash the trololol.sbf and it "reminded" my phone that it was unlocked. during the flashing process it rebooted and showed up as "unlocked" in the corner without having to re "fastboot oem unlock" it and i could flash a recover from there. using the latest RSDLite and Windows XP via Bootcamp with an AT&T Atrix and all AT&T files.
i got it to work after using a different computer and loading fresh drivers. thanks guys.
my new S7 Edge (No Brand Europe) it show me OEM UNLOCK line under Developer Options Tab
I have turned on button and restarted device.
So, Can this device be Bootloader unlockable ?
{
"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"
}
wolfgart said:
my new S7 Edge (No Brand Europe) it show me OEM UNLOCK line under Developer Options Tab
I have turned on button and restarted device.
So, Can this device be Bootloader unlockable ?
Click to expand...
Click to collapse
Yes.
Oh, and thanks for making me excited before I read you weren't referring to a Vodafone branded model.
Beefheart said:
Yes.
Oh, and thanks for making me excited before I read you weren't referring to a Vodafone branded model.
Click to expand...
Click to collapse
YES? Sure ?
So, How to boot device in Fastboot mode to unlock bootloader ?
wolfgart said:
YES? Sure ?
So, How to boot device in Fastboot mode to unlock bootloader ?
Click to expand...
Click to collapse
You don't need to unlock it, that toggle being there means the bootloader isn't locked in the first place. Just untoggle it and you're good to go. Besides, I knew for a fact before I created this thread that the non-branded international model didn't have a locked bootloader. Samsung do not lock bootloaders, certain carriers when they order their phones ask Samsung to lock the bootloader for them before then applying bloat and carrier features. I'm just hoping at this point that Vodafone UK isn't one of them.
Beefheart said:
You don't need to unlock it, that toggle being there means the bootloader isn't locked in the first place. Just untoggle it and you're good to go. Besides, I knew for a fact before I created this thread that the non-branded international model didn't have a locked bootloader. Samsung do not lock bootloaders, certain carriers when they order their phones ask Samsung to lock the bootloader for them before then applying bloat and carrier features. I'm just hoping at this point that Vodafone UK isn't one of them.
Click to expand...
Click to collapse
Wrong, that toggle is not bootloader unlock, nor is it an indication you can unlock your bootloader. It simply is a setting within android OS to allow you to use selinux permissive kernels. Even the AT&T S6 had it, and their bootloader is locked down tighter then a submarine.
Sent from my SM-T710 using Tapatalk
EDIT...............
Beefheart said:
Great. Not what I read. How do you find out the bootloader is unlocked then?
Click to expand...
Click to collapse
You try to flash a custom kernel using ODIN, if it boots, it's unlocked.
I would assume there is an indication of whether your device is locked or not in the rom download screen as well.
Beware that flashing a custom kernel on the device will trip the knox counter to 0x1, which on Snapdragon SOC is irreversible (a fuse is blown), it can be undone on the Exynos version (as the flag is stored in eMMC) if the Engineering/JIG firmware ever leaks (this happened a while back on the Note 3)
mathieulh said:
You try to flash a custom kernel using ODIN, if it boots, it's unlocked.
I would assume there is an indication of whether your device is locked or not in the rom download screen as well.
Beware that flashing a custom kernel on the device will trip the knox counter to 0x1, which on Snapdragon SOC is irreversible (a fuse is blown), it can be undone on the Exynos version (as the flag is stored in eMMC) if the Engineering/JIG firmware ever leaks (this happened a while back on the Note 3)
Click to expand...
Click to collapse
Here my screen on Download Mode :
Fap Lock is OFF
wolfgart said:
Here my screen on Download Mode :
Fap Lock is OFF
Click to expand...
Click to collapse
That's FRP, which stands for Factory Reset Protection. This relates to the OEM Toggle option I talked about earlier in the thread. I was under the impression that, in order for that to be off when you get the phone, the bootloader is unlocked. But according to _Dennis_ that isn't the case.
I would really like an easy way of finding out if Vodafone have locked this bootloader without flashing a custom kernel, of which there are none at the moment anyway. If this thing is locked, I'm returning it so only have a small window to do so.
Been searching everywhere, but it seems the only way to tell this for sure is to flash a custom ROM\Root the phone and see if it works.
Going by past experience with Vodafone since the original S phone, it hasn't been locked, so it would be a shame if they have decided to start doing this!
---------- Post added at 11:04 AM ---------- Previous post was at 11:00 AM ----------
http://forum.vodafone.co.uk/t5/Samsung-Galaxy-S7-Edge/S7-Edge-Bootloader-Unlocked/m-p/2475021
Most latest posts on that thread indicate its unlikely to be locked, but we still need to wait and see.
We may even have to wait for root to become available before we can find out!
EDIT..............................
if its an international non carrier, sim free and purchased outright from samsung or anywhere else; then the boot-loader is unlocked or at the very least easily unlockable
_Dennis_ said:
Wrong, that toggle is not bootloader unlock, nor is it an indication you can unlock your bootloader. It simply is a setting within android OS to allow you to use selinux permissive kernels. Even the AT&T S6 had it, and their bootloader is locked down tighter then a submarine.
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
I've since discovered your claim is completely wrong, it has nothing to do with selinux state, and it is related to the bootloader as I indicated. Read the following:-
http://android.wonderhowto.com/insp...ndroid-even-if-you-dont-plan-rooting-0167840/
Also, look at the description under the toggle.
However, I'm unsure if it does indicate the bootloader is unlocked at this time.
Beefheart said:
I've since discovered your claim is completely wrong, it has nothing to do with selinux state, and it is related to the bootloader as I indicated. Read the following:-
http://android.wonderhowto.com/insp...ndroid-even-if-you-dont-plan-rooting-0167840/
Also, look at the description under the toggle.
However, I'm unsure if it does indicate the bootloader is unlocked at this time.
Click to expand...
Click to collapse
Interesting. Ill see what mine says when I get home. Its strange I never had this on my other Samsung S devices, so it must be new.
My Verizon S7 Edge also has this toggle. I don't know if it actually unlocks the bootloader though.
Blart said:
My Verizon S7 Edge also has this toggle. I don't know if it actually unlocks the bootloader though.
Click to expand...
Click to collapse
Could you boot into your download mode and post a photo of the screen? I'd like to compare it to mine.
Beefheart said:
There is a way. Go into download mode, connect to PC and you can check via the fastboot command in a command prompt.
> fastboot devices (to check if the device is seen)
> fastboot oem device-info
Look for:-
Bootloader unlock allowed - Yes >> This means that your Bootloader is Locked
Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
Click to expand...
Click to collapse
strange, i don't have fastboot commands works on Download mode.
I always use them with my LG G4
it seems fastboot commands are not allowed ...
My wife said the same when I run through the instructions at home over the phone, I thought it was simply my laptop and a driver error. But perhaps there is an issue with the fastboot command with the S7's bootloader.
I need to find out today if this thing is bootloader unlocked, so I can return it fast if it isn't.
wolfgart said:
Here my screen on Download Mode :
Fap Lock is OFF
Click to expand...
Click to collapse
This download screen is identical to mine.
_Dennis_ said:
Wrong, that toggle is not bootloader unlock, nor is it an indication you can unlock your bootloader. It simply is a setting within android OS to allow you to use selinux permissive kernels. Even the AT&T S6 had it, and their bootloader is locked down tighter then a submarine.
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
The dumb thing about this is if you can't boot the phone you cant toggle that option, you can't unlock the bootloader to flash a stock rom.
wolfgart said:
Here my screen on Download Mode :
Fap Lock is OFF
Click to expand...
Click to collapse
Heh fap lock
{
"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"
}
Hi. i was curious about the DSU loader so i installed it and rebooted. But it started bootlooping then showed the "system is corrupt" message. After that it rebooted and only went into fastboot after that, Im a bit panicked since the phone is only a couple hours old and I forgot to unlock the bootloader. if anyone knows how to fix this itd be appreciated.
I did quite a lot of flashing and rooting and as far as I know, there should be an option withing fastboot to reboot to bootloader. But I am not aware of the Nothing recovery image.
When in bootloader, you can then unlock the device with fastboot commands via command line.
Have you tried any of that?
miris83 said:
I did quite a lot of flashing and rooting and as far as I know, there should be an option withing fastboot to reboot to bootloader. But I am not aware of the Nothing recovery image.
When in bootloader, you can then unlock the device with fastboot commands via command line.
Have you tried any of that?
Click to expand...
Click to collapse
sadly doesnt work since oem unlocking is off, and i cant access the os. it seems its in slot b right now, but i cant switch slots due to a locked bootloader.
any ideas would help
why use DSU?if you are stupid in this matter? say goodbye to the phone
Curiosity got the best of me. I used DSU cause I thought I would be able to keep it locked
Seaman228 said:
why use DSU?if you are stupid in this matter? say goodbye to the phone
Click to expand...
Click to collapse
Why do you trash the topic with anything but any attempt for help? Drop the keyboard and take a walk.
Someone had to say it
miris83 said:
Why do you trash the topic with anything but any attempt for help? Drop the keyboard and take a walk.
Click to expand...
Click to collapse
Trash? I told the truth, if you're crying I'm sorry
You really forgot rule 1 in android modding.
Unlock.
The.
****ing Bootloader.
Seaman228 said:
Trash? I told the truth, if you're crying I'm sorry
Click to expand...
Click to collapse
And even more trash ... You are a waste of time, man.
gordonsosig said:
View attachment 5711879Hi. i was curious about the DSU loader so i installed it and rebooted. But it started bootlooping then showed the "system is corrupt" message. After that it rebooted and only went into fastboot after that, Im a bit panicked since the phone is only a couple hours old and I forgot to unlock the bootloader. if anyone knows how to fix this itd be appreciated.
Click to expand...
Click to collapse
As I see it now, this might be your best bet at this point: https://forum.xda-developers.com/t/...t-centre-and-staff-14-september-2022.4492645/
The staff is pretty friendly. I already reported some bugs and it was just fine.
Use "fastboot getvar current-slot" to get your current slot then switch to the other slot with "fastboot --set-active=a" or "fastboot --set-active=b" I believe those commands work even with a locked bootloader.
Seaman228 said:
why use DSU?if you are stupid in this matter? say goodbye to the phone
Click to expand...
Click to collapse
it's Nothing's fault for screwing up their DSU implementation. On a locked bootloader it should either boot the DSU image (like Pixel), or reject it and boot back to normal system. In NO CIRCUMSTANCES it should BRICK the device like this
Google didn't mention the best way to install the Android 12 Beta on Pixel phones
DSU is the best way to install the Android 12 Beta release on Pixel phones, but Google totally neglected to mention it.
www.xda-developers.com
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
nguyenlucky said:
it's Nothing's fault for screwing up their DSU implementation. On a locked bootloader it should either boot the DSU image (like Pixel), or reject it and boot back to normal system. In NO CIRCUMSTANCES it should BRICK the device like this
Google didn't mention the best way to install the Android 12 Beta on Pixel phones
DSU is the best way to install the Android 12 Beta release on Pixel phones, but Google totally neglected to mention it.
www.xda-developers.com
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
Click to expand...
Click to collapse
sadly i live in switzerland so there isnt any service center i can get to. so either we find a solution or the phone collects dust on my shelf
nguyenlucky said:
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
Click to expand...
Click to collapse
On the other hand the MSM tool may exist only as an internal tool which they might provide on request in such situations. As you pointed out in the article, they messed up the implementation. To be honest, I wonder how this may have happened in the first place - to boot into mode which should not be available with the booloader unlocked. And given the company has a past link with OnePlus and OnePlus does have an MSM tool ...
Unless @gordonsosig asks the support, he will not know.
Have a look here : https://forum.xda-developers.com/t/nothing-phone-1-flashing-utilities.4478457/
And there : https://forum.xda-developers.com/t/help-to-developers.4484061/
I also went into this issue with disabled OEM Unlock. My phone was repaired for free in the customer care because I had an warranty. I wrote an email about this issue to the producer because I think it should not be possible to hard brick the phone by playing with developer options. I hope they will fix it.
And I think moderator should pin this thread to be always on top, because people should see the varning, this can save users from bricking their phones.
kuba3351 said:
I also went into this issue with disabled OEM Unlock. My phone was repaired for free in the customer care because I had an warranty. I wrote an email about this issue to the producer because I think it should not be possible to hard brick the phone by playing with developer options. I hope they will fix it.
Click to expand...
Click to collapse
where do i send it? is it in person or mail in? any help is appreciated
I returned my phone into the place where I buy it, and they sent it to the customer care. There is an official website: https://pl.nothing.tech/ so I think you can find an information about how to send your phone or use an Contact us link and I think they will help you.
kuba3351 said:
I returned my phone into the place where I buy it, and they sent it to the customer care. There is an official website: https://pl.nothing.tech/ so I think you can find an information about how to send your phone or use an Contact us link and I think they will help you.
Click to expand...
Click to collapse
guess im ****ed. already contacted them but i bought the phone from ebay so they said just contact ebay