I seem to be having issues installing any of the available custom ROMS for my mopho.
I also had issues installing the latest 198_7 sbf. It wouldn't install OTA.
Coincidence? I think not.
I followed QBKing77's instructions to the letter for the magnifier ROM , and still ended up with a brick!
I purchased my phone late October.
Any ideas?
I've rooted, installed superuser, rom manager/premium, placed the ROM on both of the cards. Nothing works!
Luckily, Android installs and boots far faster than crackberry!
Is your bootloader unlocked?
Sent from my MB855 using xda premium
I get a big, fat old FAIL.
I've tried to derp it through rsdlite, and it fails.
If its pudding turn off the photon and it should say unlock at top left after than install cwm
Sent from my MB855 using xda premium
medic233 said:
I get a big, fat old FAIL.
I've tried to derp it through rsdlite, and it fails.
Click to expand...
Click to collapse
It always fails. Just go ahead and do the moto-fastboot commands and you will be unlocked.
Grrrrr.
Thank you all for being patient.
Sporting ACS Magnifier.
SCHWEET!
Related
Hi guys;
I want to update my Atrix, but I don't know what path to take?
a) Through the OTA 4.5.91...
b) Unlocking the bootloader, and then upgrading to GingerBread via Custom Roms...
I really need your help, because I am a newby in this whole area...
Right now I am runnig:
4.1.57 ATT
Android Version: 2.2.1
Build Number: GingerBlur 2.5
Your still on 57?
Sent from my MB860 using XDA App
yeah I am on 4.1.57
Why don't you at least update to 1.83. We've ben on .83 for months now.
Sent from my MB860 using XDA App
And what then?
artemalek said:
And what then?
Click to expand...
Click to collapse
Depends what you want to do with your phone. If you like testing out custom roms and stuff then go the way of unlocking the bootloader and flashing one of the custom GB roms. If you want a stock phone with some minor root modifications then flash ota and root. Just beaware if you do the ota build you cannot flash back to froyo (not sure why anyone would but just to warn you)
Sent from my MB860
can you refeer me to the posts where I can unlock the BL and then install a custom Rom
Yeah I am on 4.1.83 and Android 2.2.2.
I want to upgrade as well. Everything is stock currently.
I want to be able to do Cynogen later so I think I need to unlock and flash a custom rom.
So I am like the op and need to know where to go. There is so much argument and misinformation on this forum my head hurts. Just read for an hour and am more confused.
All I know is i dont want to do the OTA update lol!
HOwever I downloaded it already and my phone keeps asking me to install it...
DOes anyone know how to remove that?
Well, first, I suggest you do NOT flash the OTA update.
I recommend that you use the Pudding file in the Development sub-forum to unlock your device. There are video and text guides floating around how to unlock.
If you're not wanting to try out any ROMs yet, I suggest Kenneth's ROM. It's the OTA update, except without the risk of hard bricking if you ever need to flash down.
If you are all feeling adventurous, you could flash an Overclock kernel (I recommend Faux's 1.1GHz OC). You can also flash Ninja ROM v0.4.5. It's super fast.
@mercilus if you freeze the FOTA app in Titanium Backup, I think that stops it.
Here's the guide: http://forum.xda-developers.com/show....php?t=1167373
@artemalek I see that you're on 1.5.7, that means you have an AT&T branded device. You'll need to flash the AT&T version of Pudding for your unlock.
Sinful Animosity said:
Well, first, I suggest you do NOT flash the OTA update.
I recommend that you use the Pudding file in the Development sub-forum to unlock your device. There are video and text guides floating around how to unlock.
If you're not wanting to try out any ROMs yet, I suggest Kenneth's ROM. It's the OTA update, except without the risk of hard bricking if you ever need to flash down.
If you are all feeling adventurous, you could flash an Overclock kernel (I recommend Faux's 1.1GHz OC). You can also flash Ninja ROM v0.4.5. It's super fast.
@mercilus if you freeze the FOTA app in Titanium Backup, I think that stops it.
Here's the guide: http://forum.xda-developers.com/show....php?t=1167373
@artemalek I see that you're on 1.5.7, that means you have an AT&T branded device. You'll need to flash the AT&T version of Pudding for your unlock.
Click to expand...
Click to collapse
Your link seems to be broken. Thanks for the recommendations on roms!
@Sinful
I have it rooted... Can you give me step by step guide! Do I need first to upgrade to 4.1.83 or I can do it from 4.1.57???
mercilus said:
Your link seems to be broken. Thanks for the recommendations on roms!
Click to expand...
Click to collapse
D'oh! Will fix that immediately! Thanks for that!
artemalek said:
@Sinful
I have it rooted... Can you give me step by step guide! Do I need first to upgrade to 4.1.83 or I can do it from 4.1.57???
Click to expand...
Click to collapse
Here's a video: http://www.youtube.com/watch?v=H02N4p9vEg0
Here's a text guide: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
It doesn't matter about the Firmware version. The guy in the video is on 1.5.7 and unlocks it.
Sinful Animosity said:
Here's a video: http://www.youtube.com/watch?v=H02N4p9vEg0
Here's a text guide: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
It doesn't matter about the Firmware version. The guy in the video is on 1.5.7 and unlocks it.
Click to expand...
Click to collapse
On the text version, the directions say "RSD Lite 5.3.1 or sbf_flash [Download if Atrix is Froyo]"
Im on 2.2.2 so that means I should use sbf flash instead of rsd?
mercilus said:
On the text version, the directions say "RSD Lite 5.3.1 or sbf_flash [Download if Atrix is Froyo]"
Im on 2.2.2 so that means I should use sbf flash instead of rsd?
Click to expand...
Click to collapse
RSD is fine. I think sbf flash is for Linux.
Sent from my MB860 using XDA Premium App
Sinful Animosity said:
RSD is fine. I think sbf flash is for Linux.
Click to expand...
Click to collapse
I just followed the directions and RSD said it failed and gave me an error. I accidently hit show phone and it erased the error message but it was something about error at restarting.
Now my phone wont turn on? When I hit the power button/hold it all I get is blank screen.
It doesnt try to turn on or anything?
Did i mess up the phone permanently? crap... just what i was trying to avoid..
any advice?
How full was your battery? And if your phone was hard bricked, you'd be seeing an error.
Sent from my MB860 using XDA Premium App
Sinful Animosity said:
How full was your battery? And if your phone was hard bricked, you'd be seeing an error.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Battery was at like 80% when I last looked. So it was more when I started, and I did not leave the phone watched the whole process up til the point where it wont turn on anymore. So I doubt it lost all that battery in that brief 5 minute time.
Its been plugged in since still and no response from power button.
Everything was completely stock when I started.
Update: I just noticed when I take out my battery and plug in the charger I do get a green light as long as battery is out. When I put it in and plug in I get no lights. Not sure if thats helpful or means anything... (Just noticed its only with the USB charger I get the green light and not AC charger. The battery must be out)
Well i am not rooted at the moment cause i flashed a zip that took root off and still have a custom kernal going with unlocked bootloader is that even supposed to be possible?
Sent from my MB855 using xda premium
Thats impossible. As soon as you flashed that "zip" it over writes everything. You need to be unlock to have a custom kernel
Sent from my MB855 using xda premium
well thats what i thought but i couldent use root explorer or any root access apps but when i turn off the phone it still says unlock
curly9 said:
well thats what i thought but i couldent use root explorer or any root access apps but when i turn off the phone it still says unlock
Click to expand...
Click to collapse
Interesting. Interesting indeed. Is there anyway you could upload a vid of this?
i wouldent suggest it seeing now after it turned off it wouldent do the sbf files to fix. idk if it was dealing with that cause the sbf always finishes but ends up in a boot loop which as of right now im trying to fix it. but if it happens again ill c what i can do to show you. cause i always thought you had to be rooted to have an unlocked but idk if it was just a one time thing
Is the super user app installed?
Sent from my MB855 using xda premium
Yes it was
Sent from my MB855 using xda premium
I have this same issue right now how it happened for me is that I orginally used the one click root method I found here. Later down the road I noticed that a stable build of cm7 had come out so I decided to try it out. I flashed pudding and it worked just fine and unlocked the device when I went to go get clockwork on the device however, I noticed the my root was no longer working reading in the comments section I saw that the one click root method was not compatible with the unlocked bootloader. I tried to root the phone with the system.img file that it mentioned using in the guide it worked at least as far as pushing it to the device but still no root. I then tried to flash the device back to stock I used the sbf file provided and it did wipe the phone but I still have the unlock icon when I boot the phone and can no longer root it no matter what method I try. If anyone can help me with re locking my device, I would greatly appreciate it.
Have you tryed the depudding. Go into the pudding unlock section theres one that relocks it just like how u unlocked it
Sent from my MB855 using xda premium
As far as I'm aware, being unlocked and being rooted are two separate processes on this phone. You don't have to have one to have the other. I've been rooted and locked, rooted and unlocked, and unlocked with no root. Hope that helps.
And I haven't had any problems with the one-click root and unlocking or sbf-ing back to stock.
Sent from my MB855 using XDA App
Thanks for the help guys I got it to work now had to do a factory reset and then flash the sbf file and the seemed to unroot the device it still didn't unlock it however I think if I used the depudding method curly mentioned it would work.
photon
I am currently running an "unlocked bootloader" on a non- rooted system on my photon 4g. I was rooted and then unrooted because I couldn't flash cwm for some reason....I am really really looking to installing miui with the ultimate iphone theme. I love how poloshed and clean it looks!
Hi,
Could someone please help me? I'm trying to get back to full stock (well as close to it as possible) to either eliminate my problem or send back under warranty...my problem is detailed in this thread here: http://forum.xda-developers.com/showthread.php?t=1500220&page=3# ...basically my Atrix just will mot stop randomly rebooting/locking up with the screen off (needing a batter pull).
I have tried running RSDLite 5.6 in exactly the same way I unlocked the bootloader but nothing seemed to happen...RSDLite went all the way to 100% but all my phone did was reboot normally. Weird thing was, I didn't get a reboot for nearly 24 hours....and then they started again, quite regularly. Did I do something wrong? I though that SBFing it through RSD would just reflash completely back to stock.
Also, in case I cannot get rid of this REALLY annoying problem, I want to hide the 'unlocked' text at boot ...how would I go about doing that?
Thanks,
Mark
Anyone?
Sent from my MB860 using XDA App
Are you using the correct SBF file?
markdjj said:
Anyone?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
How could I tell? I have the IHOP _Bell file and the SBF file is just titled SBF_Flash
It worked a couple of months ago when I unlocked the bootloader
If you're trying to go back to stock then you have to find the official SBF. It sounds like you're using the same files that you used to unlock it in the first place.
markdjj said:
How could I tell? I have the IHOP _Bell file and the SBF file is just titled SBF_Flash
It worked a couple of months ago when I unlocked the bootloader
Click to expand...
Click to collapse
Use a Fruitcake or you will brick
Sent from my MB860 using xda premium
Please don't spread misinformation. Using RSD does not automatically result in a brick. I have used it numerous times flashing Official (AT&T) SBF builds and I am still using the same phone.
With that said, it is not recommended to use RSD (which I agree) but it can be used with caution and some knowledge/research in tow.
One precaution, do not flash previous builds (SBF).
dragoncius said:
Use a Fruitcake or you will brick
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Ok, thanks for the info, just come back to this after being away...I have done a bit of research on fruitcake but I haven't been able to find too much...where can I find the latest?
I got my boot loader unlocked successfully following the step by step instructions. I successfully installed twrp. I tried flashing the superSU file using twrp I downloaded from here but every time I try it fails. I've flashed the boot.IMG I got from here and still can't flash the supersu files and cant flash pre rooted roms to get successfully rooted. I even tried rebooting into recovery to flash again but no success no matter how many times I try. I used every tool that is released here and nothing works. Does anybody know why and am I the only person? I have the us version of the Droid DNA from Verizon. I just upgraded to it on 1/13/2013 and its 100% new & not refurbished.
I did a Google search and I read a little about s-on and s-off . If my Droid DNA is s-on how do I convert it to s-off. I don't know for sure but that maybe why trying to get my phone rooted is failing for me. Is that what my problem is?
AndroidSmitty said:
I did a Google search and I read a little about s-on and s-off . If my Droid DNA is s-on how do I convert it to s-off. I don't know for sure but that maybe why trying to get my phone rooted is failing for me. Is that what my problem is?
Click to expand...
Click to collapse
You can't. Everyone has s on.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
You can't. Everyone has s on.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Thanks But what do you mean i can't convert to s-off or i can't get this rooted? I never had this problem before. This is my first HTC I came from Motorola I was using Motorola from my first phone droid up to the razr. I love this HTC droid DNA.
If there's an error message, post it for more help possibly.
I've also heard some have had issues with TWRP recently.
-Sent from Marino's Galaxy Nexus-
I Am Marino said:
If there's an error message, post it for more help possibly.
I've also heard some have had issues with TWRP recently.
-Sent from Marino's Galaxy Nexus-
Click to expand...
Click to collapse
Yes when I flash the supersu files it said failed md 5 not found or something like that and when I tried to install a prerooted ROM it was over 800mb in size and it was taking more than 15 to install so I stop it. I tried another ROM and it started to install for about a second and it just stopped and rebooted my phone.
I don't know how to use the cwrm because it will not install anything from the internal memory so I can select the supersu files or ROM. I dont know anything about side loading but I tried somebody's tool I got from here to side load a ROM but it would not work for me.
Did you watch video on YouTube. That helped me a lot.
droid DNA
You can always just flash a stock rooted Rom if you can't gain root.
Sent from my HTC6435LVW using xda premium
AndroidSmitty said:
Thanks But what do you mean i can't convert to s-off or i can't get this rooted? I never had this problem before. This is my first HTC I came from Motorola I was using Motorola from my first phone droid up to the razr. I love this HTC droid DNA.
Click to expand...
Click to collapse
You can't get s off. But you can have root access.
What happens when you say flashing the file fails?
Sent from my HTC6435LVW using xda app-developers app
Thanks I'm fine now. I got rooted and got the pre rooted stock installed. I don't know why I was having all that problems rooting. I keep getting the message failed every time I tried flashing using the twrp but last night I successfully got root after flashing using twrp. I thought I was dreaming and almost fell over when I finally got rooted. Also the superSU dont update the su. I launched the SuperSU and it said to update the su file but when I did it also failed. The superuser is working better than SuperSU so far. Thanks y'all.
The message I was getting was just failed. The text on the twrp is so small its to hard to read.
AndroidSmitty said:
I got my boot loader unlocked successfully following the step by step instructions. I successfully installed twrp. I tried flashing the superSU file using twrp I downloaded from here but every time I try it fails. I've flashed the boot.IMG I got from here and still can't flash the supersu files and cant flash pre rooted roms to get successfully rooted. I even tried rebooting into recovery to flash again but no success no matter how many times I try. I used every tool that is released here and nothing works. Does anybody know why and am I the only person? I have the us version of the Droid DNA from Verizon. I just upgraded to it on 1/13/2013 and its 100% new & not refurbished.
Click to expand...
Click to collapse
I had the same issue, my phone would constantly freeze when trying to flash a new rom, or if it went through i would get an infinite boot loop. i dont know what i did to fix it, re-stocked my phone with the RUU, and flashed the battery plus rom, it went through and has worked beautifully since. so maybe try that rom and see if it works for you like it did with me, i tried HATKA and CODIS with no luck
Hello,
I have been researching this for a few days and am not having much luck. My mopho has been unlocked for several month and I have been trying various custom roms without issue (from Th3Bill: CM10, CM10.1, Paranoid, etc...). I am trying to restore the phone to stock so that I can activate it on a different phone line within my Sprint account. When I try and flash 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf via RSD Lite I get an error after it finishes creating the image and tries to reboot the phone.
The phone shows the following:
SVF:116:1:2
Failed to boot x2004
I have installed the stock recovery and done a complete wipe via that recovery. I have tried using RSD Lite 5.3, 5.5, and 5.7, and also tried doing it on a different PC. Again, all I am after is to get the phone activated on a different phone number with Sprint. Any ideas would be greatly appreciated!
Thanks in advance!
Try one of these and get back to me
https://sites.google.com/site/motosbf/photon-sbf-files
Sent from my MB855 using xda app-developers app
no luck
Thanks for the reply. I tried all of 3 of the sbf files and am still getting the same error as before. Please let me know if you have any other ideas.
Thanks in advance!
Did it come with 2.3.4 or 2.3.5?
Sent from my MB855 using xda app-developers app
MarcquisDale said:
Did it come with 2.3.4 or 2.3.5?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
The phone had 2.3.4 on it before I unlocked it and started installing the custom ROMs. The strange thing is that it is still unlocked and I can flash custom ROMs without issue.
Thanks again for the help!
Sorry i couldn't help much
Sent from my MB855 using xda app-developers app
Thanks MarcquisDale for the help
Just wanted to update and say I was able to solve my issue. I found a backup that I had made back when I was on the stock 2.3.4, which I did not realize I had. Restoring that backup got me back to 2.3.4 stock so that I could active, while keeping my bootloader unlocked. That allowed me to active the device and then install a CM10 based ROM again. Not sure if this is something that will actually help someone else but figured I would post the update just in case.
Thanks again