I got my Atrix a few weeks ago (used, it was unlocked already), and have been having Sleep Of Death issues since day one. I finally got fed up, and flashed the full 4.5.141 sbf via RSDLite. The SODs dissapeared completely. I rooted, still no problems. Then I unlocked the BL and SODs returned. I tried with the Automatic Unlocker, and manually with the original pudding method. Same thing.
When I do the unlocks it says I'm already unlocked, the only thing that changes is the "Unlocked" text comes back on the boot screen. But if I don't flash the pudding I still cant use fastboot to flash recovery etc.
Does anybody have an idea on what could be the problem? Maybe it's because the pudding is for 4.5.91 BL?
Thank you
EDIT:
I flashed 4.5.91 stock (almost bricked my phone), and unlocked with pudding. Still had SODs, so it's not because of 4.5.141. Any help would be really appreciated.
I also sometimes get a red text saying: Unrecoverable bootloader error 0x00000004. And have to do a battery pull to restart the device.
eNorby said:
I got my Atrix a few weeks ago (used, it was unlocked already), and have been having Sleep Of Death issues since day one. I finally got fed up, and flashed the full 4.5.141 sbf via RSDLite. The SODs dissapeared completely. I rooted, still no problems. Then I unlocked the BL and SODs returned. I tried with the Automatic Unlocker, and manually with the original pudding method. Same thing.
When I do the unlocks it says I'm already unlocked, the only thing that changes is the "Unlocked" text comes back on the boot screen. But if I don't flash the pudding I still cant use fastboot to flash recovery etc.
Does anybody have an idea on what could be the problem? Maybe it's because the pudding is for 4.5.91 BL?
Thank you
Click to expand...
Click to collapse
Once the bootloader is unlocked you can't lock it back... its actually a fuse in hardware.
Sent from my MB860 running Jokersax's CM9
giqbal said:
Once the bootloader is unlocked you can't lock it back... its actually a fuse in hardware.
Sent from my MB860 running Jokersax's CM9
Click to expand...
Click to collapse
Yes, I get that. But when I flash the stock 4.5.141 sbf, the unlocked text dissapears. I understand that the BL is still technically unlocked, but for some reason I can't fastboot flash recovery, and similar stuff. Only after I flash pudding. But then I get SODs.
Stupid sod
eNorby said:
Yes, I get that. But when I flash the stock 4.5.141 sbf, the unlocked text dissapears. I understand that the BL is still technically unlocked, but for some reason I can't fastboot flash recovery, and similar stuff. Only after I flash pudding. But then I get SODs.
Click to expand...
Click to collapse
I installed advanced wifi lock from the market and that's helped with my SOD issues.
I used a wakelock app. but it drained my battery fast. I want a real solution. Now that I know what causes the SODs, I'm determined to fix them. I'm on stock for now with no SODs what so ever.
Sent from my MB860 using XDA
flashed 4.5.91 and unlocked. still got SOD...
bump.
Someone have any ideas?
bump
bump. please?
Its not the pudding thats causing it - Otherwise everyone here with an unlocked bootloader would be *****ing about it.... Its an app or something else you've installed that doesn't agree with something else. You'll have to spend the time tracking them down one by one. Its a PITA, but your only real option. Best bet - completely wipe everything after a full backup, and then start from scratch.
G-Man. said:
Its not the pudding thats causing it - Otherwise everyone here with an unlocked bootloader would be *****ing about it.... Its an app or something else you've installed that doesn't agree with something else. You'll have to spend the time tracking them down one by one. Its a PITA, but your only real option. Best bet - completely wipe everything after a full backup, and then start from scratch.
Click to expand...
Click to collapse
I already tried that. Wiped at least a dozen times, tried all the ROMs available, all the kernels, all the radios. It's the unlocked BL that is causing it. And I'm not the only one with this problem, I read about others in another thread. I don't know why only a few of us are getting this. But I'm 100% sure it's because of pudding. Because flashing back the stock BL (via rsd lite) fixes it.
Stock MotoBlur, with the locked bootloader works fine. As soon as I flash pudding (and that is the only thing I change) the reboots and SODs return.
There has to be an issue with your device then, otherwise every single person would have the same issue. Its not the pudding... If it was, EVERYONE would have this issue. Its your device, or something else on it.
G-Man. said:
There has to be an issue with your device then, otherwise every single person would have the same issue. Its not the pudding... If it was, EVERYONE would have this issue. Its your device, or something else on it.
Click to expand...
Click to collapse
Yes, I get that. But what I want to know is what? What is the unlocked bootloader doing, that the locked one isn't?
Its more than likely a hardware issue... This was the case back when I had my Samsung Captivate.... Some builds had no issues, and others (newer builds) were plagued with random garbage that couldn't be resolved no matter what people tried to do... I've had my Atrix 4G since pre-release day, Feb 22nd of last year. Haven't had a single issue. Others who got theirs months later, or just recently, have had some issues that I dont know why they are having (Rescue Sqad Staff on a forum dedicated to the Atrix 4G and Atrix 2) Sometimes the only way to fix certain things are to replace the device.
G-Man. said:
Its more than likely a hardware issue... This was the case back when I had my Samsung Captivate.... Some builds had no issues, and others (newer builds) were plagued with random garbage that couldn't be resolved no matter what people tried to do... I've had my Atrix 4G since pre-release day, Feb 22nd of last year. Haven't had a single issue. Others who got theirs months later, or just recently, have had some issues that I dont know why they are having (Rescue Sqad Staff on a forum dedicated to the Atrix 4G and Atrix 2) Sometimes the only way to fix certain things are to replace the device.
Click to expand...
Click to collapse
Yeah that is what I'm probably going to do. But I still don't get why it works flawlessly with the stock BL...
Sent from my MB860 using XDA
same issue, everything like this.. i wonder when will we find a solution for this SOD problem?..
Im having the same issue with my atrix unlocked the BL / SOD, how can you return again to stock without hardbrick the phone? Thanks for the info in advance!
I'm having the same problem...
I'm wondering , maybe the ram fixes in the pudding topic could help solve this?
I have exactly the same issue. No SOD with stock rom 4.5.141 and face with SOD after unlocking bootloader. Anybody has any ideas?
Also getting SOD ...
I have exactly the same issue. No SOD with stock rom 4.5.141 and SOD after unlocking bootloader.
Related
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
its been said before that once you're unlocked, you're always unlocked. Flash a fruitcake for a stock setting.
RampageRR said:
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
Click to expand...
Click to collapse
If you haven't updated to OTA 2.3.4, you can SBF flash 2.2.2 and it will restore your phone to default.
Note: It will remain unlocked, but it won't show the "Unlocked" text during boot.
This way you might get lucky and they fix it without noticing that it's unlocked.
Good luck.
xploited said:
If you haven't updated to OTA 2.3.4, you can SBF flash 2.2.2 and it will restore your phone to default.
Note: It will remain unlocked, but it won't show the "Unlocked" text during boot.
This way you might get lucky and they fix it without noticing that it's unlocked.
Good luck.
Click to expand...
Click to collapse
the SBF file, is that the Pudding one? (sorry didnt mean to hijack just have the same problem)
Pizzaapu said:
the SBF file, is that the Pudding one? (sorry didnt mean to hijack just have the same problem)
Click to expand...
Click to collapse
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
xploited said:
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
Click to expand...
Click to collapse
guess that's a little moot in this case since he's sending it back to motorola anyways lol
The other suggestion is to sbf flash the 2.3.4 sbf, still may risk hard bricking since it's not really confirmed if it's safe since most of the hard bricks have from sbfing backwards.
xploited said:
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
Click to expand...
Click to collapse
Lol hes returning back to Moto anyways ha ha! I'll try it out, I fastbooted to Gingerbread (via Kenn) So I never did the OTA.... so I guess I am safe.
Per this post, you can tell if you've flashed OTA 2.3.4. If it has been flashed already, then DO NOT downgrade to a official 2.2.2 build.
mysticdrew said:
guess that's a little moot in this case since he's sending it back to motorola anyways lol
The other suggestion is to sbf flash the 2.3.4 sbf, still may risk hard bricking since it's not really confirmed if it's safe since most of the hard bricks have from sbfing backwards.
Click to expand...
Click to collapse
Its safe. I have done it. U can sbf the 2.3.4 (4.5.91) over 2.3.4 (4.5.91) even after ota. I used the pudding sbf and did not brick my phone. Even still, same rules apply, your risk.
My overclocked alien atrix
Sass86 said:
Its safe. I have done it. U can sbf the 2.3.4 (4.5.91) over 2.3.4 (4.5.91) even after ota. I used the pudding sbf and did not brick my phone. Even still, same rules apply, your risk.
My overclocked alien atrix
Click to expand...
Click to collapse
Yeah but doesn't using the pudding 2.3.4 (4.5.91) still makes you have the "Unlocked" thing on the boot setting? which is what the OP wants to avoid so if he takes it to like AT&T if they see it and see Unlocked they will void the warranty, I am pretty sure the retail story wont extract his phone to see if the fuse it sparked and unlocked.
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
I am not sure about the sbf, but I can tell you for sure fruitcake will not get rid of the unlock logo, flashing a fruitcake is only a stock ROM.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
No. Only if you haven't upgraded via ota update. If you did, then there is no way of removing "unlocked" yet.
My overclocked alien atrix
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
Just a thought... did you ever back up your PDS partition?
Touchscreen issues sometimes are due to pds issues. If you have made a backup, wouldn't be a bad idea to try restoring it to see if that fixes your issue.
If you didn't back it up, take a look at this thread with a pds file that helped others.
http://forum.xda-developers.com/showthread.php?t=1131649
RampageRR said:
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
Click to expand...
Click to collapse
Probably a long shot but, I used to have very similar issues with other phones in the past when I've had a screen protector on for awhile and it gets scratched up. Maybe try remove the screen protector if there is one and see what happens.
If it is going back for repair. why not intentionally hard brick it? The first thing they will do is the full blown factory flash, erasing all evidence.
If you do this, make certain you give them a story that somehow describes both the actual problem and the bricked condition (else they might think the un-bricking fixed it and not catch the other issue.
EDIT: Maybe not all evidence, the fuse that was blown when you unlocked a 2.3.4 might be a real hardware type fuse and never be cleared. Don't know.
My device is doing this exact same thing and I'm in the same position you are in. I never backed up the PDS partition, but a backup using the image in the linked thread did not solve the problem. Nor did flashing multiple new ROMs.
I'm not sure if this is a hardware or software problem. It problem seems to go away if you lock the screen a few times, but then later reapers.
Sorry to hijack this thread, but does anyone know if replacing the digitizer will fix this problem? Since I'm in New Zealand this would be an economic solution as shipping to and from the US is pricey.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
Ok, I have the same issue as you, I was able to fix the "unlocked" logo ( I havn't taken it back to AT&T yet for warranty, but I will update when I do). So this is what I did, when I upgraded to 4.5.91 I fastbooted it instead of OTA or flashing it, I also unlocked my bootloader by using pudding. Assuming if you did the same, then will be able to flash the official 4.5.91 via SBF ( I wasnt going to try 1.8.3 because I didn't want to risk the brick). I got the 4.5.91 sbf from this link: http://forum.xda-developers.com/showthread.php?t=1125944 ... My phone is still rooted, but the "unlocked" logo is now gone and I flashed fruitcakes so It looks completly stocked now! I hope this helps, I dont think you will fool motorola if you send it in for repairs, but I am pretty sure you can get by with that if you have to return it to the store for warranty reasons! Good luck : )
Pizzaapu said:
Ok, I have the same issue as you, I was able to fix the "unlocked" logo ( I havn't taken it back to AT&T yet for warranty, but I will update when I do). So this is what I did, when I upgraded to 4.5.91 I fastbooted it instead of OTA or flashing it, I also unlocked my bootloader by using pudding. Assuming if you did the same, then will be able to flash the official 4.5.91 via SBF ( I wasnt going to try 1.8.3 because I didn't want to risk the brick). I got the 4.5.91 sbf from this link: http://forum.xda-developers.com/showthread.php?t=1125944 ... My phone is still rooted, but the "unlocked" logo is now gone and I flashed fruitcakes so It looks completly stocked now! I hope this helps, I dont think you will fool motorola if you send it in for repairs, but I am pretty sure you can get by with that if you have to return it to the store for warranty reasons! Good luck : )
Click to expand...
Click to collapse
I just saw this. I ended up using the stock 2.3.4 sbf, and then doing a factory reset in the privacy menu. Now has all the stock info in the "about phone" section. I'll let you all know how it goes. Thanks for the suggestions.
Just got back from AT&T! they said it was a software issue! They gave me the warranty and gave me a refurbished Atrix with 1.8.3, stock froyo on it! I'll stay OTA until CM7 comes out of pre-beta then see how to root it after OTA : )
Any help/advice would be appreciated, thank-you!
Mine was purchased Mar/11, I had unlocked bootloader, and running Darkside ROM, all was good.
Then haptic feedback/vibration started cutting in/out.
Tried going back to CM7, Aura... no resolution. Read on xda re: some people having hardware issues with vibe mechanism, so loaded up NFHimself's Gobstopper (thanks!) to make phone appear as stock as possible, and took in to Bell for service. Came back from Motorola repair shop, vibes fixed, running GB 2.3.6. Battery life absolutely sucks, which is what started me down this whole road of custom ROMs in first place!! As I said, Darkside was awesome, almost double battery life for same usage.
So... I want to re-unlock and get going again, really unsure where to start. Some have said follow exact same steps and unlocking first time, others say no need to repeat fastboot oem unlock, and others say just jump in at flashing a custom (Romracers) recovery??
I am leery of using RSDlite and IHOP again, heard bad things about messing with .sbf files after phones software has been updated??
I read another thread on here about antifuses, and such, not sure if that's the case, but for sure the unlocked message no longer appears during boot.
The intro on NFHimslelf's Froyo Gobstopper thread alludes to the fact that you need to RE-unlock after flashing it, and now for sure after Motorola techs updated phone, so... kindly, where should I start &/or what steps should I skip to get back to where I was without bricking??
Thanks very much!
Just flash the IHOP unlock SBF. Even if it reports as failing the install just pull the battery then reboot. Should see unlocked on the boot screen. Then boot to fastboot, flash recovery, reboot to recovery and flash your ROM or backup.
Sent from my Xoom using xda premium
d3athsd00r
Thanks very much for your reply! I will try tonight after work and report back!
I'm back in business! Thanks again
I am merely rooted, so no other mods. I did my over the air update to 4.5.141 last week and have had nothing but problems: spontaneous reboots, weird A2DP stuff (launching both music and beyond pod simultaneously and locking the phone!), poor battery life.
I want to go back to what was stable and worked, 2.3.4 (4.5.91) and am confused as to how to safely do this. From what I read, I cannot use the old SBF because it will brick the phone. I have not found the SPF for 2.3.4, anyway, so that is probably not important. I do not really want to use CWM and a new rom, I just want to use the phone. I root for WifiTether and Ti backup reasons only and do not need to do anything else. I can wait for Q4 for ICS, but not if it has all these problems over the next 10 months!
How can I go safely back to a stock 2.3.4?
Keithspg
The only thing I can think of is to unlock the bootloader (if possible) and flashing a fruitcake. I haven't read of anyone successfully unlocking the bootloader after the OTA AND having never unlocked it before but that doesn't mean it's not possible.
keithspg said:
I am merely rooted, so no other mods. I did my over the air update to 4.5.141 last week and have had nothing but problems: spontaneous reboots, weird A2DP stuff (launching both music and beyond pod simultaneously and locking the phone!), poor battery life.
I want to go back to what was stable and worked, 2.3.4 (4.5.91) and am confused as to how to safely do this. From what I read, I cannot use the old SBF because it will brick the phone. I have not found the SPF for 2.3.4, anyway, so that is probably not important. I do not really want to use CWM and a new rom, I just want to use the phone. I root for WifiTether and Ti backup reasons only and do not need to do anything else. I can wait for Q4 for ICS, but not if it has all these problems over the next 10 months!
How can I go safely back to a stock 2.3.4?
Keithspg
Click to expand...
Click to collapse
I'm with you Keith
I am also rooted for TI backup. Since the update WiFi has been randomly dropping. My ABC news app keeps losing connection when going to video section. While on Android IRC WiFi drops out and I have to reconnect. Before update WiFi remained connected for days.
I have way too much work into the phone to reformat to anything. I am hoping ICS upgrade will fix the problem but who knows what they will bring.
Since we are rooted there is no way Motorola will support us. We need a dev here to figure out what went wrong. (
Just backed up, wiped the phone (from fastboot menu), re-rooted, restored. Not an hour later, spontaneous power off while in my pocket. This really sucks. I can un-root, if that will fix it, but do not see how root can be causing the problem. Still have not unlocked the boot loader and would use that only as a last resort.
Regardless, it is not clear to me that the 3.2.4 unlock instructions will work with 3.2.6.
I do not know what a pudding or a fruitcake is, really. I have been reading about CM7 and it does not not appear as 'released' for Atrix. Also it looks like a hassle to add everything Google after you install it *and* the fingerprint sensor does not yet work with the alpha builds which do exist for Atrix.
not happy at all.
keithspg said:
Just backed up, wiped the phone (from fastboot menu), re-rooted, restored. Not an hour later, spontaneous power off while in my pocket. This really sucks. I can un-root, if that will fix it, but do not see how root can be causing the problem. Still have not unlocked the boot loader and would use that only as a last resort.
Regardless, it is not clear to me that the 3.2.4 unlock instructions will work with 3.2.6.
I do not know what a pudding or a fruitcake is, really. I have been reading about CM7 and it does not not appear as 'released' for Atrix. Also it looks like a hassle to add everything Google after you install it *and* the fingerprint sensor does not yet work with the alpha builds which do exist for Atrix.
not happy at all.
Click to expand...
Click to collapse
Adding the Google "everything" is actually very easy. Flash the gapps after the rom, then first time you go to market after signing in, it prompts you to install whatever google apps you want. As for the fingerprint, I'm on cm7 weekly build Feb 20 and I only use fingerprint to unlock. So it works. And its been very stable for me so far. Hth
The unlocker that was posted by the htc dev, I heard some trouble with that. I want to get off this stock ROM or.at least get rid of that BLOATWARE Vzw puts in there. I seen some people have inactive or (bricked) phones after unlocking...or no service? Has the bugs been worked out of that unlock software? Last thing I need is a dead phone. :/
No.
When were there ever bugs? I've never heard of any of that. The worst that happens is it will wipe your internal storage... Can't remember about external, but backup everything you need and there won't be a problem
Sent from my ADR6425LVW using Tapatalk 2
Unless you go out if your way to do something ridiculous before researching xda, im pretty sure the only way you can mess up that bad is pulling the battery while flashing a kernel /radio/firmware
Sent from my ADR6425LVW using xda premium
With just htc dev unlock and no s-off you are pretty much safe from ... just about anything
I did about 38 firmware updates for other users before we had s off which involved relocking and then unlocking in a 2 week period. Prior to that I probably helped about 15 people by remoting in to their computer and unlocking their phone new out of the box then fastboot flashing recovery and then flashing a custom rooted rom and kernel.
So I would guess without counting the updates I did where people had their unlock codes from before, I did approximately 30 htcdev bootloader unlocks.
I've never seen a bricked device or loss of signal from an OEM unlock. Also, I've never seen a true bricked device besides hardware failure that wasn't related to unlocking, it was just a rare factory defect.
Now I have helped about a dozen people (estimating conservatively) that made threads saying their device was bricked. Each time, it was because they had a different boot.img than the one from their rom and attempted to boot, often because they just forgot to flash the kernel. This results in a harmless bootloop until the user flashes a boot image and can be easily resolved by restoring the nandroid or by flashing the new kernel their rom needs.
An example of this where it's seen often is a person installs a gingerbread rom and boot.img. A month later they flash an Ice Cream Sandwich rom, and forget there's a gingerbread kernel on it needs to be replaced with the ICS kernel (kernel is in form of boot.img) So they reboot, hang on the white HTC boot screen, and panic, thus creating the "Help I've bricked my phone" threads. Sadly, some people don't wait for assistance and return their phone to Verizon before realizing it wasn't bricked it was bootlooped.
Also, with s off, I've seen the same identical problem. Their computer screws up while running the windows script. The Juopunut bear s off program has replaced the boot.IMG on said phone with the one it installs temporarily to gain s off. They see the JP bear logo when they reboot and panic because they think it's bricked. In reality, they just need to flash one PH98IMG.zip they used to install the rom and they will be right back to normal.
Most of the threads and gtalk messages I get about signal loss is because people reboot with the battery cover off and don't realize that it's because they forgot to put the cover back on and the antennas are in the cover.
I'm not calling anyone liars, just stating that in all the cases I've helped out with, the bricks weren't bricks at all just a minor misunderstanding on part of the user. I always recommend when people get frustrated they put the phone down and cool off to prevent the panic and confusion as much as possible.
Sent from my ADR6425LVW using xda premium
No reason to unlock now that we have S-Off. You'll have complete access to everything and they don't have a record that you voided your warranty by unlocking. S-Off is pretty easy to achieve now that the software has a lot of the bugs worked out of it. Also it makes flashing roms and going back and forth between versions a lot easier!
brando56894 said:
No reason to unlock now that we have S-Off. You'll have complete access to everything and they don't have a record that you voided your warranty by unlocking. S-Off is pretty easy to achieve now that the software has a lot of the bugs worked out of it. Also it makes flashing roms and going back and forth between versions a lot easier!
Click to expand...
Click to collapse
Pretty much everything you said about not unlocking is wrong.
You cannot do the S-OFF procedure unless you are rooted, and you aren't rooted unless you are unlocked.
In the interest of full disclosure, I know of 2 Rezounds that have bricked, but from attempting things you will never do.
Hello guys, you'll have to excuse me for the wall of text, but it is necessary to fully describe my ordeal.
I bought an used atrix about 4 months ago from ebay (and i'm now deeply regretting it, too many issues). When I first received the phone I was unable to hear callers, even though they could hear me (badly, but could). I resolved that the easiest way possible: I bought a headset. Even with that issue and since it was impractical for me to return the phone because I'm in a different country (customs alone were over $100) I continued to use it. I flashed CM7 and ATT N_.37, flashed TWRP 2.1 and I enjoyed my phone for a couple months (even with the audio issue). Then one day, I went to bed with my phone on a full charge and in the morning I found it turned off. I tried to turn it back on and nothing happened. I thought maybe the battery had been drained by something, because I had left 3G data enabled. I tried to charge it and nothing happened, except the phone started to get really really hot in the lower part so I decided to disconnect it. I tried again a couple hours later and same thing happened. Next day I hit the power button and was able to enter android recovery. I wiped and factory reset, reinstalled cm7, gapps and radio and phone turned on and showed around 60% charge and it seemed fine and then all of a sudden the led started glowing light blue. Then the phone shut down and started to boot loop. I took off the battery, let it rest a while and then when I turned it back on everything worked fine (still, minus audio). That was two weeks ago. Today, it started to do the something similar but worse. Blue led flashing and boot loop are there but if I enter recovery I can't find anything in the sdcard, and if I place a microsd in the slot it isnt recognized. Also, led is flashing blue even while in recovery so I doubt it is a CM7 issue.
tl;dr My phone is dead. Can it be fixed or do I now own a $250 paperweight?
Try to flash your phone with your stock firmware using rsd lite
here a list of firmwares ... http://forum.xda-developers.com/showthread.php?t=1125944
WARNING! : flash it with YOUR stock sbf !!!
isn't that dangerous? from what i understand with this post it seems as if it isn't advisable to use an sbf on an unlocked bootloader.
not.a.troll said:
isn't that dangerous? from what i understand with this post it seems as if it isn't advisable to use an sbf on an unlocked bootloader.
Click to expand...
Click to collapse
Only if you're downgrading. It can work if you do it properly, but it's not recommended. Fruitcakes are the more foolproof way to go.
well i chickened out of the .sbf flash and just tried the moto-fastboot stock restore available elsewhere. while everything seemed to flash correctly i am still bootlooping/shut down. also, light blue led still there and sometimes i get stuck on bootscreen and can't even enter recovery. guess ill have to take it to a shop and see if something can be done. else S>atrix 4g for parts.
D:
hello to all
my atrix 4g originally was in firmware 4.5.141.MB860 ATT, i unlocked the bootloader succesfully and flash CM7... but for reasons of life (silly excuse jejeje) i want to take it back to the original fw... with this files: Blur_Version.4.5.141.MB860.ATT.en.US and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.gz can i go back to stock fw? with this stock files i lose the boot unlock? is this a safe method? and what is the safest?
thanks for your help and greetings from Colombia (and sorry for my bad english)
Flash the latest sbf for your phone. I've done several with no problems. Yes, you do lose the unlocked bootloader though.
This will return you to stock. I used the same files.
not.a.troll said:
well i chickened out of the .sbf flash and just tried the moto-fastboot stock restore available elsewhere. while everything seemed to flash correctly i am still bootlooping/shut down. also, light blue led still there and sometimes i get stuck on bootscreen and can't even enter recovery. guess ill have to take it to a shop and see if something can be done. else S>atrix 4g for parts.
D:
Click to expand...
Click to collapse
I also have been through several phones with this issue. Although you can flash the sbf with no troubles, that is really only good for sending it into warranty. From my experience, this is a hardware issue, and flashing the stock sbf doesn't solve the problem. If you do not have warranty, a repair shop is your best bet.
Good luck.
Repy
x-geo said:
hello to all
my atrix 4g originally was in firmware 4.5.141.MB860 ATT, i unlocked the bootloader succesfully and flash CM7... but for reasons of life (silly excuse jejeje) i want to take it back to the original fw... with this files: Blur_Version.4.5.141.MB860.ATT.en.US and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.gz can i go back to stock fw? with this stock files i lose the boot unlock? is this a safe method? and what is the safest?
thanks for your help and greetings from Colombia (and sorry for my bad english)
Click to expand...
Click to collapse
Hi,
Yes you can go back to your stock rom. Another yes, you will lose all your files and your bl unlock too. You have to start everithing from the begining. this is a safe method if you flash your own rom.