Hello everyone
I unlocked my Atrix (MB860, NORDICS RETAIL) some months ago and then I installed NottachTrix1.3.1 Rom. The day after the new Rom installation I experienced a lot of stability issues so I flashed the stock SBF file to bring the phone into its original state.
But since that time my phone is working worse than before: it gets very hot sometime and the battery drains much faster, if before with an intense use it worked for more than a 24 hours now with a moderate use if doesn't reach night sometime. This happens even if I flash the SBF file and then I leave all only the original applications of the phone without a restore of the backed-up ones.
I've been reading many articles about Atrix problems till now, but there are so many that it's probably impossible to not get confused, and I haven't been able to find something that helps me to solve mine yet.
Now I have some doubts I would like to ask you:
1- Did I pick up the right sbf file for my phone (the package says MB860, NORDICS RETAIL my sbf file is 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.1-release-keys-signed-NonEFIGSRetail-EU.sbf)?
2- There can be some components installed by custom rom that may still be working in the device(kernel,filesystem,radio or whatever) also after the sbf file flash and causing the problems I'm experiencing?
Thank you
Bye
Big-Bob said:
Hello everyone
I unlocked my Atrix (MB860, NORDICS RETAIL) some months ago and then I installed NottachTrix1.3.1 Rom. The day after the new Rom installation I experienced a lot of stability issues so I flashed the stock SBF file to bring the phone into its original state.
But since that time my phone is working worse than before: it gets very hot sometime and the battery drains much faster, if before with an intense use it worked for more than a 24 hours now with a moderate use if doesn't reach night sometime. This happens even if I flash the SBF file and then I leave all only the original applications of the phone without a restore of the backed-up ones.
I've been reading many articles about Atrix problems till now, but there are so many that it's probably impossible to not get confused, and I haven't been able to find something that helps me to solve mine yet.
Now I have some doubts I would like to ask you:
1- Did I pick up the right sbf file for my phone (the package says MB860, NORDICS RETAIL my sbf file is 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.1-release-keys-signed-NonEFIGSRetail-EU.sbf)?
2- There can be some components installed by custom rom that may still be working in the device(kernel,filesystem,radio or whatever) also after the sbf file flash and causing the problems I'm experiencing?
Thank you
Bye
Click to expand...
Click to collapse
i donr know the anwser of the first question.
second no when you flash a sbf you erase everything on the phone so it looks like when you buy it even lock the bootloader again.
maybe one app runing in background or mobile data.
send it to technical support if youre in warranty.
cheers
Thank you lucamibel
lucamibel said:
second no when you flash a sbf you erase everything on the phone so it looks like when you buy it even lock the bootloader again.
Click to expand...
Click to collapse
Oh well it's not really like you said, for example the bootloader unlocking process is not reversible through the sbf file flash, because after it, the "Unlocked" text on the top-left corner is just hidden but if you try to re-take the unlocking procedure when you execute the unlocking command it will say that the device is already unlocked while when you execute it at the first time it unlocks the phone , so there is something that the sbf file flash procedure doesn't recover. I haven't tried to install the rom recovery tool without unlocking the phone yet, I'm try to avoid other dangerous actions on it now.
lucamibel said:
maybe one app runing in background or mobile data.
Click to expand...
Click to collapse
These issues will happen even if I leave the phone with the configuration in the SBF file image, so I would exclude that reason.
lucamibel said:
send it to technical support if youre in warranty.
Click to expand...
Click to collapse
I'm still in warranty, but the phone is unlocked
Bye
Big-Bob said:
Thank you lucamibel
Oh well it's not really like you said, for example the bootloader unlocking process is not reversible through the sbf file flash, because after it, the "Unlocked" text on the top-left corner is just hidden but if you try to re-take the unlocking procedure when you execute the unlocking command it will say that the device is already unlocked while when you execute it at the first time it unlocks the phone , so there is something that the sbf file flash procedure doesn't recover. I haven't tried to install the rom recovery tool without unlocking the phone yet, I'm try to avoid other dangerous actions on it now.
These issues will happen even if I leave the phone with the configuration in the SBF file image, so I would exclude that reason.
I'm still in warranty, but the phone is unlocked
Bye
Click to expand...
Click to collapse
You are correct in saying that the bootloader remains unlocked. Also, if you search the forums I think you will have a very hard time finding anyone who has had a warranty return rejected for an unlocked bootloader. I would get rid of the "unlocked" text and send it in for repair if you need to.
Thanks CaelanT
I think that would probably be the best thing to do. It's being too hard to find a solution by myself.
I've just bring the phone back at its factory status and as soon as it'll restart with the issues I'll send it to the assistance, if they won't matter about the unlocked status it would be only better.
Big-Bob said:
Thanks CaelanT
I think that would probably be the best thing to do. It's being too hard to find a solution by myself.
I've just bring the phone back at its factory status and as soon as it'll restart with the issues I'll send it to the assistance, if they won't matter about the unlocked status it would be only better.
Click to expand...
Click to collapse
sorry i think i dont express well when i said that, i mean it that the "unlocked" cartel hide and you can send it to technical support
cheers
Related
So I've had my Atrix for a few months now, and it's mostly awesome. I'm coming from having owned an iPhone before, and it's just fantastic. I've stayed away from modding it too much however, since I knew the bootloader was locked and not a lot could really be done. But, according to several posts I see here, the bootloader seems to have been unlocked recently. Yay?
So, I ask that you forgive my ignorance. What does this mean? Does a given ROM need to be modified to work with every model of phone? If so, which ones presently work with the Atrix? Any? (It looks like the unlock was found very recently.) How does that process work exactly? Is there any way to ensure a recovery path if something were to go wrong, so that I don't brick my phone?
I'm just curious here. Presently, my phone is on the stock firmware without any upgrades at all, and I've simply rooted it and installed the webtop mod so I could play games on my TV. Other than that, it's been lots of Android Market for me. I'd like to branch out, and I don't even know where to begin.
There aren't any custom rom's for this yet, there's work being done, so it's just a matter of time. However, there is a developer build from Asia that can be flashed. There are a few issues with it, so if you are averse to troubleshooting or dealing with issues then just wait a few days.
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Can I flash the UK Firmware on a unlocked ATT Atrix now?
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
schlupp88 said:
Can I flash the UK Firmware on a unlocked ATT Atrix now?
Click to expand...
Click to collapse
_Dennis_ said:
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
Click to expand...
Click to collapse
_Dennis_ is right. You should sbf_flash -x to extract the UK firmware and use fastboot to flash just boot.img (CG56 in Froyo) and system.img (CG57 in Froyo). If you want to flash the radio, use a custom .sbf (for AT&T) with only the radio. We don't yet know whether you can replace your bootloader with a UK bootloader. We still flashed a signed bootloader to our phone. In the worst case, if you flash a UK signed bootloader and your boot ROM is looking to find an AT&T signature in your bootloader: BAD! It is fairly unclear that the unlock ALSO tells boot ROM not to care about signatures, it may very well still care. And the order of RSD: erase,write,verify is a little dangerous...
I as well, don't know much about this... but as far as I know, this will mean that developers will be able to create real operating systems for the phone and not have to wait for att/moto to do that...
in the past it was an OS from att/moto, and all the "roms" in xda were actually the same OS but with some skins and mods added to them...
Yes, if you look at the development forums for just about any other android phone, you will see full customized ROMs that can be installed. That's where we are headed.
_Dennis_ said:
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
Click to expand...
Click to collapse
I did a test with this.
I flashed 1.8.3 SBF over my unlocked bootloader to see if I could use moto-fastboot to flash over a 'stock' bootloader. It works to flash system (since it is still technically unlocked) but fails to flash boot.
So DO NOT TRY TO SBF FLASH A INTERNATIONAL VERSION unless you want to be stuck on the version with no way to get your phone back off.
I also would not flash the boot.img of a international version for the same reason.
beatphreek said:
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Click to expand...
Click to collapse
I just finished unlocking and installed the new CWM recovery, just waiting for some roms! About the full system backup with CWM, does is deposit a folder to the SD card I can remove for safe keeping like TIBu? I never used CWM to backup or restore.
climo said:
I just finished unlocking and installed the new CWM recovery, just waiting for some roms! About the full system backup with CWM, does is deposit a folder to the SD card I can remove for safe keeping like TIBu? I never used CWM to backup or restore.
Click to expand...
Click to collapse
I think that the backup will be found in a Clockwork folder on your sd card. I also think that when you do the backup you will get to choose the destination. Either sd or external sd.
I haven't used the bl unlock or the new ClockworkMod (Just waiting on a nice rom). But that is how it went for me on the previous CWM that didn't require the unlocked bootloader.
Maybe someone who has this newer stuff can shed a little more light on it.
beatphreek said:
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Click to expand...
Click to collapse
Does this essentially create an image of your device? Or does it just back up the firmware?
When CWM backs up ur files it creates a image file of
Boot.img
Cache.img
Data.img
recovery.img
system.img
so yes it does use a image.
Y'all talking about custom ROM's and such, no one seems to care about overcloking.. no one seems to realize what a beast a 1.4ghz Atrix would be.
Viamonte said:
Y'all talking about custom ROM's and such, no one seems to care about overcloking.. no one seems to realize what a beast a 1.4ghz Atrix would be.
Click to expand...
Click to collapse
+1.
ROMs will sometimes require you to have the custom kernel associated with them. CM7 for the Captivate comes to mind. With custom kernels, the Captivate was a beast. We had the VooDoo lagfix, which actually made the device usable on bootup. We were able to convert all partitions to ext4, and kind-of make the GPS work.
Overclocking is a possibility too. There's so much that is able to be done. It's a bit difficult coming from an iPhone where customization was limited, even with jailbreaking. But you'll soon get the hang of it.
GPS. Nice point too, but Moto itself promisses improvements on the 2.3.4 OTA. This is the most sorely needed fix for me, since my gps SUCKS. It can take anywhere up to 30 minutos to find my locations. Yes, you read that right.
Viamonte said:
GPS. Nice point too, but Moto itself promisses improvements on the 2.3.4 OTA. This is the most sorely needed fix for me, since my gps SUCKS. It can take anywhere up to 30 minutos to find my locations. Yes, you read that right.
Click to expand...
Click to collapse
Mine works great. You may have a hardware issue?
Sent from my MB860 using XDA App
JayRolla said:
Mine works great. You may have a hardware issue?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
+2
It shouldn't take that long to lock on. Mine locks on instantly.
Hi there,
I'll try to make this brief. My touch screen has a 1/2" slice that is unresponsive (middle of the default google bar and down) and I am under warranty so I figured hey, let's call and get the phone warrantied.
Motorola is sending me a new phone when should be at my apartment when I arrive back from my travels.
My bootloader is unlocked. I understand there is no physical or theoretical way to relock thee bootloader; I get that. I am on 4.5.91. I never did the OTA updates; every update or ROM or anything since 1.26 has been from here. I've read a LOT in the last 24 hours.. and I'm concerned that trying to SBF anything over 4.5.91 will end up bricking the phone that I'm slated to return for a faulty screen. So, I was then thinking about moto-fastboot. That works for system and boot, but not bootloader, right?
My main concern is this: I don't want them to turn my phone on and see "UNLOCKED" in the top left and immediately charge me $499 for voiding the warranty. I DO understand this is a risk I took, and I am willing to eat the charge should it happen; but that withstanding my screen is legitimately borked. I'd be willing to try something to overwrite this bootloader if there were a tangible means to do it without like >80% chance of bricking it. Every SBF I've flashed on here has been pudding.
Is there anything that can be done to get rid of "UNLOCKED" up there? I know it won't relock the bootloader; but I want the techs to see that the screen is broke before they start snooping through system settings. I may get lucky, I don't know.
Also, anyone with experience warrantying a phone with an unlocked bootloader? How did it work out for you?
As it stands now I'm downloading the stock 1.8.3 system and boot images. But they won't overwrite the bootloader. I have about 4 days to figure this out before I fly home.
Thoughts?
I'm pretty sure you're stuck man.
Sent from my MB860 using Tapatalk
Hey I would play it safe and just buy another ATRIX off craigslist. I picked up an ATRIX in my area for 200 that is in mint condition. That sure beats the 499 they are going to charge you when they power on the device to check for user related problems before they slap a new screen on it and put it their refurbish phones inventory.
Sent from my MB860 using XDA App
I'd need somebody else to confirm this:
I thought that when you installed 4.5.91 through the safe .zip files, you were able to flash back to a previous SBF safely. I remember people in the IRC doing just that, and reporting that once they had done so, the "UNLOCKED" message on startup disappeared until they reflashed pudding. I'm pretty sure that it didn't actually relock the bootloader, just somehow get rid of the "UNLOCKED", but again I'm not entirely sure.
tl;dr I think you are safe to flash an SBF if you got GB from a .zip and that way you won't show "UNLOCKED".
I thought about that but I'd rather just get one from them if I'll be spending any money period.
I read a few posts that stated that there was a way to remove the "UNLOCKED" on the bootloader by flashing stock SBF's but I'm not sure if that would result in a brick at this point.. which is why I haven't tried it.
Either way.. I was also thinking: when they were troubleshooting me on the phone, they had me do a factory reset. This was yesterday. So, if it does brick I may have a "I did a system update and something went wrong" way out.
Would love to hear from someone who has experience with warranty services.
Thanks to both of you for your replies. I am also slightly inclined to believe I am boned. :[
KF as soon as someone verifies that I'll be happy to. I still have the 1.2.6 and 1.5.7 stock SBF's. To the best of my knowledge, I never let the OTA update happen. On my XOOM yes but not on the Atrix. Just unlocked, flashed what ever rom/zip I wanted, and went to town. Sucks that my screen blew I just had it where I wanted it with 2.3.4 :[
There's an 4.5.91 SBF. It should be safe to flash per eval-'s post. This should get rid of your "unlocked" without the danger of attempting to flash an earlier version.
lauterm said:
There's an 4.5.91 SBF. It should be safe to flash per eval-'s post. This should get rid of your "unlocked" without the danger of attempting to flash an earlier version.
Click to expand...
Click to collapse
I agree...by flashing a rom via RSD should get rid of "UNLOCK" text..
here is another link...http://forum.xda-developers.com/showthread.php?t=1125944
deziguy420 said:
I agree...by flashing a rom via RSD should get rid of "UNLOCK" text..
here is another link...http://forum.xda-developers.com/showthread.php?t=1125944
Click to expand...
Click to collapse
I love you both. It worked and I'm on the stock stuff now.
Everything else is up to the fate of the universe. At least they'll see that my screen is messed up before they start prodding around.
What happened?
Can you let us know if this was successful? I'd really like to do the same thing if it was...
I'm very familiar with Samsung and Odin, but Motorola stuff its confusing as hell. I've got a Photon now (and my ET4G). I've been reading through the stickies and the general / Q&A section and can't seen to find a definitive answer to a few questions...
1. I am 2.3.4 running 4.5.1A-1_SUN-198_6. What is the latest root method?
2. Do I need an unlocked bootloader to flash roms and kernels?
3. Any fix for the random "sleep of death" without updating to 2.3.5?
Thanks in advance for any help you all can give!
- Z
zzelinka said:
I'm very familiar with Samsung and Odin, but Motorola stuff its confusing as hell. I've got a Photon now (and my ET4G). I've been reading through the stickies and the general / Q&A section and can't seen to find a definitive answer to a few questions...
1. I am 2.3.4 running 4.5.1A-1_SUN-198_6. What is the latest root method?
2. Do I need an unlocked bootloader to flash roms and kernels?
3. Any fix for the random "sleep of death" without updating to 2.3.5?
Thanks in advance for any help you all can give!
- Z
Click to expand...
Click to collapse
Funny because Samsung's are the complicated ones. All rooting info is listed in development section. One click root should work.
And yes you must of course unlock the bootloader to do any of that.
Sleep of death? Heard of it from like two random people. Never had it happen.
Sent from my SGH-I777 using XDA
zzelinka said:
I'm very familiar with Samsung and Odin, but Motorola stuff its confusing as hell. I've got a Photon now (and my ET4G). I've been reading through the stickies and the general / Q&A section and can't seen to find a definitive answer to a few questions...
1. I am 2.3.4 running 4.5.1A-1_SUN-198_6. What is the latest root method?
2. Do I need an unlocked bootloader to flash roms and kernels?
3. Any fix for the random "sleep of death" without updating to 2.3.5?
Thanks in advance for any help you all can give!
- Z
Click to expand...
Click to collapse
if you are familiar with odin then its gunna be a breeze, tars = sbf's, and odin = rsd lite. if you bork something youve gutta get into the proper mode (download mode = rsd mode) load up rsdlite and add the sbf in and click start.
shabbypenguin said:
if you are familiar with odin then its gunna be a breeze, tars = sbf's, and odin = rsd lite. if you bork something youve gutta get into the proper mode (download mode = rsd mode) load up rsdlite and add the sbf in and click start.
Click to expand...
Click to collapse
Cool. I am contemplating just updating to the newest update and not needing with anything for now. I pretty much bought it to use for my $59.99 lapdock. I actually bought two off Craigslist for $230. They are both pretty much brand new and came with original boxes, etc.
I'm still on the fence. It randomly shuts off and won't turn back on without a battery pull. Its frustrating as hell. Its done it probably 5-10 times tonight alone, and tonights the first night I've had it! I've read that updating to the newest system update takes care of the problem.
- Z
na7q said:
Funny because Samsung's are the complicated ones. All rooting info is listed in development section. One click root should work.
And yes you must of course unlock the bootloader to do any of that.
Sleep of death? Heard of it from like two random people. Never had it happen.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
It just seems like its so much more complicated. Seems like I can brick my phone more easily with all this Moto software.
- Z
zzelinka said:
It just seems like its so much more complicated. Seems like I can brick my phone more easily with all this Moto software.
- Z
Click to expand...
Click to collapse
I urge you not to take the 2.3.5 as if it doesn't fix your sleep of death, there is literally no way to get it off your phone. Our stuff only seems a bit confusing because there is an extra step in there (unlocking) that you people don't have to contend with. Also, we lack a definitive AIO that does everything within one program. It takes a bit of getting used to but as shabby said, the concept is generally the same and there are simple guides for each step.
-Root using torpedo method (aio will probably work but torpedo never fails)
-unlock bootloader
-install a recovery (twrp is fine but you're probably used to cwm)
-flash yo sheet
Acvice said:
I urge you not to take the 2.3.5 as if it doesn't fix your sleep of death, there is literally no way to get it off your phone. Our stuff only seems a bit confusing because there is an extra step in there (unlocking) that you people don't have to contend with. Also, we lack a definitive AIO that does everything within one program. It takes a bit of getting used to but as shabby said, the concept is generally the same and there are simple guides for each step.
-Root using torpedo method (aio will probably work but torpedo never fails)
-unlock bootloader
-install a recovery (twrp is fine but you're probably used to cwm)
-flash yo sheet
Click to expand...
Click to collapse
Werd. Was there ever a fix for sleep of death?
Do not update it with ota.
Flash 198_7 sbf and then flash only locked bootloader from 2.3.4 sv1 custom sbf thread.
It should solve the problem.
peetr_ said:
Do not update it with ota.
Flash 198_7 sbf and then flash only locked bootloader from 2.3.4 sv1 custom sbf thread.
It should solve the problem.
Click to expand...
Click to collapse
I'll check it out. Thanks for the info!
- Z
peetr_ said:
Do not update it with ota.
Flash 198_7 sbf and then flash only locked bootloader from 2.3.4 sv1 custom sbf thread.
It should solve the problem.
Click to expand...
Click to collapse
I saw the SV1 Locked Bootloader.sbf.zip but no 198_7 file. Am I missing something obvious. I probably am
EDITED: I'm a moron. Found it on Loikifish's site...
One more question, your phone is unlocked or locked, when the sleep of death problem occurs?
peetr_ said:
One more question, your phone is unlocked or locked, when the sleep of death problem occurs?
Click to expand...
Click to collapse
It's unlocked. Totally stock, nothing on it. No apps, nada. Just takes a nap on me and never wakes up... I switched back to my ET4G for now. At least until I can get the sleep of death figured out. Any help would be greatly appreciated. Gonna sell one of my MoPho's and maybe the second one w/ my lapdock if I figure out what to do about it. I don't want to pay to get a replacement either....
- Z
Ok so do what I wrote before, that should solve the problem an you will stay unlocked.
Actually you can try, that just flashing 198_7 sbf and not unlocking, will solve the problem.
I mistyped. It's LOCKED. Should I still just flash the 198 and the locked only?
EDIT: Shabby's AIO worked and I'm thinking about unlocking the bootloader. I can't remember if I saw somewhere where I can retain 4G with unlocking the BL. I can't seem to find it now...
Yes, if it's 198_6 now, you can flash 198_7 sbf, so that 2.3.5 update won't bother you and unlock only with bootloader, not derpunlock.sbf.
Tell me, if that helped with those deaths.
So I did an expirement to test a theory... I activated my Photon on my line the day before yesterday. I had a sleep of death if I let the phone sit too long (maybe 20-30 minutes). I was in good radio areas. I took the Photon off my line and let it sit to see if it would go to sleep and not wake up.
Guess what? I left it on for 12+ hours unattended and when I went to turn it on... No sleep of death! I'm going to put it back on my line and see if it sleeps hard again. I think we can then say the problem is most likely some sort of radio related. Am I correct?
- Z
It is possible. You could try to find out where is the problem on yours.
I only know, that one man had this problem everytime he tried to unlock his phone with derpunlock.sbf. When he flashed full 198_7 sbf, everything was fine. Once he tried to unlock different way, that sleep of death was gone.
But this looks like the cause of your problem could be somewhere else.
peetr_ said:
It is possible. You could try to find out where is the problem on yours.
I only know, that one man had this problem everytime he tried to unlock his phone with derpunlock.sbf. When he flashed full 198_7 sbf, everything was fine. Once he tried to unlock different way, that sleep of death was gone.
But this looks like the cause of your problem could be somewhere else.
Click to expand...
Click to collapse
I unlocked using the derpunlock and fastboot method for CWM. It went off without a hitch. Switched back to the Photon to see if the SOD's still occur. I'll keep this thread updating to see if the problem gets resolved. Thanks for the help!
Many helpful people here .
Thanks to all, I might get a photon soon
Buttery Smooth THS15 Deviled
lord dredd said:
Many helpful people here .
Thanks to all, I might get a photon soon
Buttery Smooth THS15 Deviled
Click to expand...
Click to collapse
We try
Hey,
I was on CM7, then I flashed Stock Gingerbread using CWM (Fruitcake, I think), I want to remove root and the "unlocked" sign when booting. I was searching this forum (and the rest of the internet ) for a couple of days and didn't find a solution. Either the links are dead or there is a person threating with hard brick. Does anyone know how to do this safely and has necessary files, please? Thank you in advance.
Wait, what exactly do you want to do?
If you want to just remove the text while the BL and everything else remains unlocked... That is impossible, you cannot do that.
If you want to re-lock your BL... well, that would probably be the only time (apart from when unlocking the BL) when you should reach for a SBF. There is no other known way to re-lock the BL.
Yep, I need to re-lock the BL, to get the phone to factory state (I know it won't actually re-lock the BL, just the sign will disappear). But I didn't find any usable SBF's, everybody is writing about hardbrick or the links are down. I found a couple of US ATT SBF's , but really don't know which one to use, I really don't want to brick my phone
Okay, I found this site with SBF's:
http://www.filefactory.com/f/89f588286a560e39/
I guess this one SHOULD put my phone back to factory state without root access and unlocked sign. Does anyone know, if it's safe? And if it's the only file I need to flash. Thanks
All the SBFs were removed here because they are too dangerous. For that same reason, you won't find many people here who will be willing to help you with them, not even say "yes, this one is good" or "no, don't use this one". It's just too dangerous and nobody wants to take responsibility for other people's phones like that. Not to mention, you failed to give any relevant information on your phone, so even if someone wanted to help, they can't.
What information do you have on mind?
Currently I'm running rooted unlocked stock gingerbread 2.3.4 (System version: 45.31.20.MB860.NonEFIGSRetail.en.EU, Build number: 4.5.2A-74_OLE-31.20).
If flashing SBF is dangerous, is there any method to get back to factory state?
Yes, that would be the information needed.
Flashing a SBF is the only known way to remove the "Unlocked" text while booting; however you will still find very little support here for doing that - like I said, it is too dangerous, things can go wrong too easily.
You can flash a fruitcake to return the system to stock, but the "Unlocked" text will remain.
That's what I was afraid of So no one will tell me: "Yes, with your configuration you can flash this and you'll be fine."
Nevermind, I will send for repair like this (problem with touchscreen - fantom touches, quite common hardware problem on atrixes) and in the worst case I´ll just pay for the repair.
Anyways, thank you for help, I really appreciate it! :good:
People have been known to just flash over the stock firmware and send it in and be fine. A lot of service centers don't really care about the unlocked BL or even a custom recovery.
i think he can remove unlocked sign with flashing motorola logo. if i remember corectly
Sent from my MB860 using xda app-developers app
Nope.
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
ibma said:
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
They pulled the AT&T update. Soooo....just gotta wait.....
ibma said:
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
I'm just guessing this is a case of autocorrect, and you mean "custom ROM" and not "art room"?
How did the custom ROM get on your phone, did you buy it that way or did someone do it for you?
The update won't install with a custom ROM, its true (at least if any system files have been altered, which is usually the case). Also, it won't install with a custom recovery. Might even send you into a bootloop and render the phone unusable.
If you want to return to a stock condition and get the update, you can either read up and learn, or run the RUU to return to stock (bootloader must be locked or you need S-off). In either case, we can help you, but need specifics on how you want to approach it.
redpoint73 said:
I'm just guessing this is a case of autocorrect, and you mean "custom ROM" and not "art room"?
How did the custom ROM get on your phone, did you buy it that way or did someone do it for you?
The update won't install with a custom ROM, its true (at least if any system files have been altered, which is usually the case). Also, it won't install with a custom recovery. Might even send you into a bootloop and render the phone unusable.
If you want to return to a stock condition and get the update, you can either read up and learn, or run the RUU to return to stock (bootloader must be locked or you need S-off). In either case, we can help you, but need specifics on how you want to approach it.
Click to expand...
Click to collapse
oh the lousy autocorrect got me.
I have no idea what im doing lol, im following a tut to install revolution hd rom and so far everything is working perfect lets see what happens after system reboot.
Can I unroot and relock bootloader after custom rom install done ?
Update: restoring old content phone seems faster with better signal, but before custom rom it had 4g signal now seems only 3g
Now that sucks boomsound enable/disbale in settings is gone!
So is extreme power saving gone from status bar
also 4g signal
Signal will not show 4g or 4glte like AT&T [email protected] [email protected]
You could relock and unroot,but then no reason to flash a custom rom.
Those two settings are in settings. And on the m8 443 euro builds some are reporting lesser [email protected]
There are AT&T ROM's available that are tailored to us AT&T/GSM networks
ibma said:
oh the lousy autocorrect got me.
I have no idea what im doing lol, im following a tut to install revolution hd rom and so far everything is working perfect lets see what happens after system reboot.
Can I unroot and relock bootloader after custom rom install done ?
Update: restoring old content phone seems faster with better signal, but before custom rom it had 4g signal now seems only 3g
Click to expand...
Click to collapse
ibma said:
Now that sucks boomsound enable/disbale in settings is gone!
So is extreme power saving gone from status bar
also 4g signal
Click to expand...
Click to collapse
ibma said:
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
Just use this guide to flash the ruu for 4.4.3. It only works on att m8. MAKE SURE YOU READ THE DIRECTIONS! You just need to relock your boot loader if you are not s-off
http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
ibma said:
I have no idea what im doing lol, im following a tut to install revolution hd rom
Click to expand...
Click to collapse
This is the exact reason I highly discourage following step-by-step tutorials; and/or using toolkits. You are modding the phone with apparently very little understanding of what you are actually doing. Not only is this very risky, as it might result in damage to you phone. But it also leaves you completely unequipped to handle any problems.
My suggestion is to spend a few hours reading the basic information that the folks here have taken the time to compile. This isn't "techie" stuff, this is the basic information and concepts that should be understood before doing any modding of the phone. Quite simply IMO if you don't understand the basics, you have no business rooting/modding the phone.
exad's excellent guide: http://forum.xda-developers.com/showthread.php?p=52484527
FAQs: http://forum.xda-developers.com/showthread.php?t=2711073
Index of AT&T M8 resources: http://forum.xda-developers.com/showthread.php?t=2751432
Index of "international" M8 resources (most apply to AT&T version): http://forum.xda-developers.com/showthread.php?t=2694600
redpoint73 said:
This is the exact reason I highly discourage following step-by-step tutorials; and/or using toolkits. You are modding the phone with apparently very little understanding of what you are actually doing. Not only is this very risky, as it might result in damage to you phone. But it also leaves you completely unequipped to handle any problems.
My suggestion is to spend a few hours reading the basic information that the folks here have taken the time to compile. This isn't "techie" stuff, this is the basic information and concepts that should be understood before doing any modding of the phone. Quite simply IMO if you don't understand the basics, you have no business rooting/modding the phone.
exad's excellent guide: http://forum.xda-developers.com/showthread.php?p=52484527
FAQs: http://forum.xda-developers.com/showthread.php?t=2711073
Index of AT&T M8 resources: http://forum.xda-developers.com/showthread.php?t=2751432
Index of "international" M8 resources (most apply to AT&T version): http://forum.xda-developers.com/showthread.php?t=2694600
Click to expand...
Click to collapse
What i did is i unocked, rooted, then installed twrp, took nanodroid backup and installed custom rom, would it cause any issues if i factory reset the phone ?(will it reset to at&t room that came with the device)
ibma said:
What i did is i unocked, rooted, then installed twrp, took nanodroid backup and installed custom rom, would it cause any issues if i factory reset the phone ?(will it reset to at&t room that came with the device)
Click to expand...
Click to collapse
Again, you need to learn and research more before doing anything. This is another perfect example. Factory reset doesn't do anything to the ROM. All it does is wipe the user data partition, and isn't going to help your case in any way. And trying to make up your own solutions is not a good idea (but at least you thought to ask before trying it).
If the intent is to simply be on the latest 2.23 stock software, just run the RUU. You will need to relock the bootloader before RUU if you are s-on. Also, back up any personal data, as user data will be wiped by RUU.
redpoint73 said:
Again, you need to learn and research more before doing anything. This is another perfect example. Factory reset doesn't do anything to the ROM. All it does is wipe the user data partition, and isn't going to help your case in any way. And trying to make up your own solutions is not a good idea (but at least you thought to ask before trying it).
If the intent is to simply be on the latest 2.23 stock software, just run the RUU. You will need to relock the bootloader before RUU if you are s-on. Also, back up any personal data, as user data will be wiped by RUU.
Click to expand...
Click to collapse
I restored stock recovery and got bavk to att rom RUU is giving me usb error dunno why.
ibma said:
I restored stock recovery and got bavk to att rom RUU is giving me usb error dunno why.
Click to expand...
Click to collapse
Not enough info. What exactly does the error say?
S-on or S-off. Did you relock the bootloader?
Any response if you type (using adb):
adb devices
Improper HTC/ADB drivers or using Microsoft USB 3.0 drivers on USB 3 port on Windows 8.x instead of Intel USB drivers would be my first two guess. The ladder of the two issues would be most likely scenario if RUU communicates with device while booted into Android OS but fails to connect when the device is in fastboot/boot loader mode.
-Sent from a payphone...