Related
i guess im going to call verizon with a bs reason i need a new phone. I have tried to update off nan from when i first rooted downloads but wont install dont understand sbfing and zip files wont load need serious help
What exactly is your phone doing right now? Is it stuck on the boot logo or what?
Its operational, I just flashed back to first nan and reloaded fission cause nothing I did the 928 back to stock ect worked, even tried updating without signing into google, unrooted and all that just frustrated it won't work
Sent from my DROIDX using XDA App
Ok, so you are up and running then. The only thing i was going to suggest is flashing SBF to get you back to Stock Android 2.2 and starting the process over again. I had a similar problem and wiped everything clean IOT get what i wanted. SBF'ing is simpler then you think, all you need is 2 files (rsdlite_4.8 and VRZ MB810_2.3.15 sbf). There's lots of articles here on it and I used them when I thought I bricked my phone. I started all over and was able to receive my 2.2.1 update.....finally!!
have you done the ota update? if so use 2.3.32.sbf you can get it by google and search droid x 2.3.32 sbf and its the first result. and dl rdlite 4.8. very easy to flash. several guides on here as stated.
I got it my drivers are up to date but won't find my phone.. And I'm leary all I got to do is that file and update?
Sent from my DROIDX using XDA App
Try running rsdlite as the administrator. (Right click rsdlite)
Now won't find it and I got a toshiba, only a little bit over a year old
Sent from my DROIDX using XDA App
EDIT - finally got rsd lite to recognize but first attempt failed trying again... pray
EDIT #2 - YEs, rebooted with 2.3.320 now to find 2.3.340 n flash it
hello all
sorry if this is in the wrong section.
today i decided i didnt like my old rom and tried to install fission using the fission rom manager. in the install screen, i forgot to check the wipe box by mistake.
now my phone WILL NOT go any farther than the white moto logo at the very beginning of the boot animation. Is there anyway I can fix this? i am not that experienced at this stuff, so a good explanation is needed. please help!
i just figured out how to get to (stock) recovery from boot, but even after wiping and retryin a few times, it still wont work....
i have also not upgraded or updated really anything since i got my phone months ago, except root, and deodex, and flyx rom
-matt
You won't lose root, and when you sign back into google all your apps will come back. Did you make a recent backup? If so you can use it from recovery
Sent from my DROIDX using XDA App
You can even wipe and reinstall if you still wanna try fission since you're in recovery.
Sent from my DROIDX using Tapatalk
google has all of my tons of apps? sik. but from recovery there is no option to restore/backup nandroid, like bootstrap
the options are reboot, apply sdcard update.zip, wipe data/factory reset, wipe cache partition
Oh you're in stock recovery... Just wipe and reboot.
Sent from my DROIDX using Tapatalk
well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that
Try pulling the battery, should reboot to clockwork recovery when you put battery back in, then you can restore a backup or flash a rom from sd card.
Sent from my DROIDX using XDA App
mattmartin77 said:
well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that
Click to expand...
Click to collapse
Most roms require .320/.340. You definitely wanna upgrade if you plan on flashing in the future.
Sent from my DROIDX using Tapatalk
well neither of those solve my problem, i am debating on whether on not to take it to verizon, but idk if they will even help me.
if you can get to clockwork recovery you can download a rom by computer and transfer to your sd card, or put your card in another phone to download it. Then flash that rom. Be sure to mount the system before flashing
Sent from my DROIDX using XDA App
Hi matt.. soon after getting my X, I got stuck in your situation while flashing a rom. I took it to verizon and after trying to troubleshoot it for a few minutes, they decided to just overnight me another one. I told them that I woke up and the phone was stuck at the M. I didn't mention anything about being rooted or trying to flash a rom.
The phone was also within the one year warranty though. You might want to try this route if all else fails.
Good luck!!
Sent from my DROIDX using XDA App
If everything else fails you can sbf. I'll pm you a link for the 2.2315 full sbf, just download rsd lite 4.8 and google how to do a sbf if your not familiar. Then you can do the official ota and be up to date
Sent from my DROIDX using XDA App
thnx everyone. ive never sbf'ed before, but ill give it a shot. i wish i could get to clockwork, it would make everything so much easier.
i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.
mattmartin77 said:
i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.
Click to expand...
Click to collapse
What version of rsd are you using? you can just sbf .320 full then .340 system only and it will be updated no need to sbf an old file.
i am using the newest rsd i could find. 4.9 right? and it seems as if i need pst_flash.ini according to the sbf installation instructions i found here
edit: hey thnx everyone for the help. i took it to verizon and the techs said it was a "complete software crash". yay i bricked my phone:/... the good news is that verizon is overnighting me a new one.
when i get it i am going to root it. i also want it to be the latest sbf or whatever its called so i can get either fission or gummyjar on there. now i need 2 more questions answered.
1. which option in about is the one that tells me what sbf im on?
2. i kinda need a really good tut on how to flash a new sbf and get it to .340 because i clearly failed miserably at it last time, so anyone have a link or willing to write it up?
It should have.340 on it or be ready to update. You can check by going to settings, about phone, build number. It should say 2.2.340
Sent from my DROIDX using XDA App
oh build number. thnx bro, so many confusing numbers, why cant there just be simple names? lol
Full SBF isn't out yet for 2.3.340 you will need the SBF for 2.3.320 and then the patches to get to 2.3.340. Keep it handy just in case!
yah i have the .15 sbf right now for safe keeping but i cant find the .32 or the .34 patch, but it isnt urgent since i heard that the new phone that is coming will be preloaded with the newest everything.
can i just use z4root to root my new phone? or do i have to do the doroot thing in adb like i originally did on my first dx?
I also wanted to know if i could use one of the kernels i saw in the fission rom manager with a rom other than fission, such as gummyjar.
I tried to flash Fizzion rom and then all it would do is get stuck at the M. . Then i couldn't get clockwork recovery to come up.. I tried to sbf and it keeps failing at the very end of a long ass process.. I used sbf on this phone once before and had no problems.. Now it doesn't do anything but go to the bootloader. .It's a friends phone so im kinda freaking out..
What version were you on and what sbf versiln did you try to flash?
Sent from my DROIDX using XDA App
2.3.15 trying to use 2.3.15 sbf
Can you boot into stock recovery? (Home and power, at triangle push search button once)
If you can, try to wipe data and cache.
Sent from my DROIDX using XDA App
I wish i could boot into stock recovery.. doesn't do anything but go to the bootloader.
boredmug said:
I tried to flash Fizzion rom and then all it would do is get stuck at the M. . Then i couldn't get clockwork recovery to come up.. I tried to sbf and it keeps failing at the very end of a long ass process.. I used sbf on this phone once before and had no problems.. Now it doesn't do anything but go to the bootloader. .It's a friends phone so im kinda freaking out..
Click to expand...
Click to collapse
Some friend you are.... Lol.
Sent from my DROIDX using XDA App
lol.. well now it boots up.. I said it failed the sbf flash but it booted into stock 2.2. . wtf?
boredmug said:
I tried to flash Fizzion rom and then all it would do is get stuck at the M. . Then i couldn't get clockwork recovery to come up.. I tried to sbf and it keeps failing at the very end of a long ass process.. I used sbf on this phone once before and had no problems.. Now it doesn't do anything but go to the bootloader. .It's a friends phone so im kinda freaking out..
Click to expand...
Click to collapse
Sometimes it will say it failed at the end, but it just isn't overwriting bp-passthroug. This isnt an essential file if you are already on the same version as the sbf you are using. These are radio files I believe... So if this part fails...oh well. As long as it is writing the system files, that is what you should be concerned about for the most part.
Please help...very similar situation I am in as was boredmug. I Flashed the Fission Rom...then it got stuck on the "M" boot animation...I did some research and used RSD Lite 4.8 to flash 2.3.15 sbf from bootloader... It started working fine and then right at the end of the process my bootloader said "Battery low...Unable to program". I know my battery was fully charged..
Could I just need a new battery maybe?? hopefully???
jeraspie28 said:
Please help...very similar situation I am in as was boredmug. I Flashed the Fission Rom...then it got stuck on the "M" boot animation...I did some research and used RSD Lite 4.8 to flash 2.3.15 sbf from bootloader... It started working fine and then right at the end of the process my bootloader said "Battery low...Unable to program". I know my battery was fully charged..
Could I just need a new battery maybe?? hopefully???
Click to expand...
Click to collapse
I had this happen to me before. You will need to charge your battery before you continue. I hope you did not fry out your battery as this has also happened to me. Give it a full charge as well.
There is a full 340 SBF that you can use with RSD Lite as well as a zip, maderstcok for 340. With the maderstcok update ( which works just as well as flashing with RSD Lite ) it doesn't matter which bootloader you have as long as you are on 2.3.15. It will update all files so you are on the latest version of Android.
Make sure you guys are wiping data/cache as well before SBF or installing new ROMS.
When I plug the phone into USB port and the led is green and the bootloader still says "Battery low, Cannot program." Would it help to get another battery?
It also says "NEW_MAP Blank" above the battery low message. Does that have something to do with it?
Sent from my Ginger Tazz using XDA App
jeraspie28 said:
When I plug the phone into USB port and the led is green and the bootloader still says "Battery low, Cannot program." Would it help to get another battery?
It also says "NEW_MAP Blank" above the battery low message. Does that have something to do with it?
Sent from my Ginger Tazz using XDA App
Click to expand...
Click to collapse
USB port charging is not enough to charge the phone properly. You will need to charge the phone with the wall charger while the phone is off or take it to a Verizon store so they can charge it for you. Usually the batteries from VZW come with less then half a charge. They can also test your battery to make sure it's still good.
I finally solved the problem by "rigging" up the battery to another USB cable wires. Crazy, but it worked. I'm all good now.. Thanks.
http://www.droidforums.net/forum/te...ons/99781-droid-not-booting-odd-behavior.html
Jeremy
I had a new phone on 2.3.4. The first thing I tried to do was to unlock it by RSD flashing the unlock sbf from the main pudding thread (http://forum.xda-developers.com/showthread.php?t=1136261).
The initial process seemed to go okay, but I think when the phone was supposed to reboot, it ended up giving me a boot failure message (0x1000, if I remember correctly).
So, I tried the "fastboot oem unlock" command anyway, and it worked.
I tried to RSD flash the full 2.3.4 sbf from brandon15811's thread, but RSD gave an error, something about not being able to find the handle or something.
So, the next thing I did was to see if I could flash RomRacer's CWM via fastboot, and that seemed to work, too.
After that, if I tried to reboot, I would get the motorola startup screen and the word "unlocked", but it just seems to stay there.
I'm about to see if I can use the recovery to flash the full 2.3.4 sbf from here (http://forum.xda-developers.com/showthread.php?t=1138204).
Is that the right way to try to fix this, or is there something else I should try?
Haphim said:
I had a new phone on 2.3.4. The first thing I tried to do was to unlock it by RSD flashing the unlock sbf from the main pudding thread (http://forum.xda-developers.com/showthread.php?t=1136261).
The initial process seemed to go okay, but I think when the phone was supposed to reboot, it ended up giving me a boot failure message (0x1000, if I remember correctly).
So, I tried the "fastboot oem unlock" command anyway, and it worked.
I tried to RSD flash the full 2.3.4 sbf from brandon15811's thread, but RSD gave an error, something about not being able to find the handle or something.
So, the next thing I did was to see if I could flash RomRacer's CWM via fastboot, and that seemed to work, too.
After that, if I tried to reboot, I would get the motorola startup screen and the word "unlocked", but it just seems to stay there.
I'm about to see if I can use the recovery to flash the full 2.3.4 sbf from here (http://forum.xda-developers.com/showthread.php?t=1138204).
Is that the right way to try to fix this, or is there something else I should try?
Click to expand...
Click to collapse
If you have cwm just use samcripp's fruitcakes and see if that works.
Sent from my MB860 using XDA Premium App
msd24200 said:
If you have cwm just use samcripp's fruitcakes and see if that works.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I haven't confirmed it works yet, but if it does, why those builds instead of brandon15811's?
Haphim said:
I haven't confirmed it works yet, but if it does, why those builds instead of brandon15811's?
Click to expand...
Click to collapse
Sbf flashing is dangerous and not recommended
Sent from my MB860 using XDA Premium App
Unlocking an atrix already on 2.3.4 will give you a soft brick, its been confirmed many times. No way around it. Find the fruit cakes thread as msd24200 stated. Any recovery will work. If you do the full 2.3.4 sbf you can't rds back to an older build our even if you try the 2.3.4, that would give you a hard brick. If your unlocked just go for one of the great roms available.
Sent from my MB860 using XDA App
Dirtburgler said:
Unlocking an atrix already on 2.3.4 will give you a soft brick, its been confirmed many times. No way around it. Find the fruit cakes thread as msd24200 stated. Any recovery will work. If you do the full 2.3.4 sbf you can't rds back to an older build our even if you try the 2.3.4, that would give you a hard brick. If your unlocked just go for one of the great roms available.
Click to expand...
Click to collapse
I did a lot of reading before doing this, and somehow, I never came across that particular fact. Ai! Well, thank you for pointing that out!
So, here's a question then... I have another phone that has 1.83 on it. What's the best way to upgrade that to 2.3.4, unlocked and rooted? Should I follow the same path I did here, do the OTA update, unlock and brick via the unlock sbf, flash a recovery, then apply a fruitcake?
Or is there a better way? I've heard that the 2.3.4 update resizes the partitions, and that seems like a good thing, so I'm not sure I want a path that avoids that.
What do you think?
Haphim said:
I did a lot of reading before doing this, and somehow, I never came across that particular fact. Ai! Well, thank you for pointing that out!
So, here's a question then... I have another phone that has 1.83 on it. What's the best way to upgrade that to 2.3.4, unlocked and rooted? Should I follow the same path I did here, do the OTA update, unlock and brick via the unlock sbf, flash a recovery, then apply a fruitcake?
Or is there a better way? I've heard that the 2.3.4 update resizes the partitions, and that seems like a good thing, so I'm not sure I want a path that avoids that.
What do you think?
Click to expand...
Click to collapse
why bother to update if you're going to downgrade it again?
the unlocker SBF if 1.8.3, and the phone is on 1.8.3, so flash that. then install 2.3.4 via CWM with a fruitcake. done.
dLo GSR said:
why bother to update if you're going to downgrade it again?
the unlocker SBF if 1.8.3, and the phone is on 1.8.3, so flash that. then install 2.3.4 via CWM with a fruitcake. done.
Click to expand...
Click to collapse
Unce I've unlocked the phone on 1.8.3, would it be better to do the OTA update for 2.3.4, and then root? Is this even possible?
One important question, if I apply the CWM fruitcake over 1.83. will it resize the partitions the way the OTA update would?
Haphim said:
Unce I've unlocked the phone on 1.8.3, would it be better to do the OTA update for 2.3.4, and then root? Is this even possible?
One important question, if I apply the CWM fruitcake over 1.83. will it resize the partitions the way the OTA update would?
Click to expand...
Click to collapse
I don't believe so, someone correct me if I'm wrong, but in all honesty there is no reason to use fruitcakes if you don't plan on going back to an older build. Even if you mess something up flashing roms you can go into recovery and restore a backup and your good to go. The only way I've seen a hardbrick is from going back with rsd.
I would unlock then ota to 2.3.4 then install romracers cwm and then your free to flash pre rooted stock roms or cherry (3.14) or alien rom.
Sent from my MB860 using XDA App
Nevermind 10char
I could see flashing back to an older build beneficial to a developer but not your everyday user and rom flasher. Both methods will get you to the same place, fruitcake or ota. I know there are benefita doing the ota like partition size and some other tweaks but I'm not 100% what those benefits are.
I jumped in early and got the leaked ota before we knew of the hard brick issue and like I said I'm still rocking the same atrix I bought back in march.
Sent from my MB860 using XDA App
Dirtburgler said:
I don't believe so, someone correct me if I'm wrong, but in all honesty there is no reason to use fruitcakes if you don't plan on going back to an older build. Even if you mess something up flashing roms you can go into recovery and restore a backup and your good to go. The only way I've seen a hardbrick is from going back with rsd.
I would unlock then ota to 2.3.4 then install romracers cwm and then your free to flash pre rooted stock roms or cherry (3.14) or alien rom.
Click to expand...
Click to collapse
Thanks! If that's an okay route to take, then that's what I'll do.
Hey guys so i mistakenly updated to 2.3.3 the other day and really didn't like it so I rooted my phone, and was about to flash Miui when I changed my mind and tried to Deodex my phone, because i had already rooted the phone I tried to do the manual deodex shown in the "noobs guide post" i did everything according the the instructions but it didn't work. So I grabbed the SHADO_X6_2.3.34_SYSTEM-ONLY.SBF file and loaded it in RSD lite to flash back and un-root my phone.. well half way into the process the phone rebooted to the Red M logo.. and everything I've done since has been to no avail.. i tried to download other SBF files that were supposed to be the "full" sbf but for some reason RSD lite wont even let me flash them... If i boot holdig the menu button the phone will bring up the recovery menu and from there i can still select the 4 different options but even after doing the factory data reset and formatting the catch nothing seems to change.. I have been looking for several hours now to get this working and I'm getting really frustrated. So i just want to apologist if this situation has already been dealt with but if you guys could help me out to get my phone working again i would be incredibly great full.
Look into the full sbf using the linux iso 1kds did, wish I would post links
Sent from my DROIDX using XDA App
STAYFROSTY777 said:
Look into the full sbf using the linux iso 1kds did, wish I would post links
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I think I read something about the but havn't been able to find where to get the linux iso, am i correct in saying you can temporarily boot linux from the disk to do this? BTW Thank for the sugestion, my wife was about to make me sleep in the dog house for messing my phone up lol so when i get off work i'll try to find the Linux iso, maybe i can even find a thred that has a walk through to fix it.
In the event that I do get everything working again, is it easier to flash roms from gingerbread or from Froyo? or if you want a gingerbread rom i'm assuming you have to flash it from gingerbread correct?
Yes your correct about the roms from my understanding, and haha I know the feeling, yeah just burn the iso onto a disc (its not very big) on boot from disc on your computer, follow the instructions, and it will sbf you to froyo, probably be doing this for me tomorrow since in have some problems with tethering, good luck man, let me know how it goes
Sent from my DROIDX using XDA App
sweet I'll be happy to have my phone back.. lol i miss it, i feel lost without it to be honest. I never knew how attachedi was to my phone. but anyway I'll forsure let you know how it goes i'm praying that this will fix my phone, I have never really come accross a true definition of how to tell if your phone is "bricked" or not. it seems like everyone says their phone is bricked just because they cant get it to boot up but i always thought that the term "bricked" refered to the phone being so screwed up that you can no longer fix or salvage it.. does anyone know the actual definition?
I was recomended to look at this web page it was incredabley helpfull!! i'm running throught the process right now so i'll report my results when done but i'm pretty optimistic about this.
http://www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html
Awesome man, i used that method, might be doing again after work today to change roms
Sent from my DROIDX using XDA App
yeah i was so happy that it worked although i was still worried at first because the phone still boots to the Red M logo but after a sec it goes the the droid eye and then load GB anyway now i just need to really understand how to deodex and flash a rom right way, but at least now i know how to fix the phone if i screw something up. One more question, would you guys say that my phone was considered bricked? if so than is it safe to say that there is nothing you can do to it that you can't fix using the Linux boot SBF method?
btw the actual page i used with all the downloads of Linux is right here in case anyone else needs it.
http://www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html
It doesn't sound like it was bricked, and so for I haven't seen anything to bad where you can just use the Linux way, unless you mess up the hardware lol
well thats somewhat good to know lol thanks for all the advice
Anytime buddy, always glad to help
Sent from my DROIDX using XDA App
The reason why the first sbf didn't work is because you used a SYSTEM only Sbf and it was for froyo 2.3.340 instead of the FULL sbf which reverts everything back to froyo instead of just the system.
Sent from my DROIDX using XDA App
hmm so how is the system only sbf any different than doing a factory reset while running 2.3.340? i mean does doing the system only sbf undo rooting your phone?