Database Develop

[How To] Downgrade 2.2 To 2.1

Not sure if this has already been posted somewhere, but after my experience I figured it might be useful to someone. If it's been posted already ignore this and move on with your day/night
1. flash sbf
2. phone will go in the boot loop of death, thats fine lol.. when rsdlite says 100 percent pull the battery
3. put the battery back in, hold down the home button plus the power button till you see the moto logo followed by the triangle
4. hit search button, your now in recovery
5. do a factory restore
6. once complete reboot phone
7. thank god and swear you wont flash your phone ever again (ofcourse only to do it in a day or so after you have calmed down)
rsdlite and sbf can be found in this thread CLICK

If you made a nandroid backup of 2.1 couldn't you just restore that? I'm pretty sure you can. I remember doing it with the Moto Droid.

taypotts said:
If you made a nandroid backup of 2.1 couldn't you just restore that? I'm pretty sure you can. I remember doing it with the Moto Droid.
Click to expand...
Click to collapse
not sure if you can use bootstrap in froyo, and besides if you ever need to go back to a unrooted state this is the way to go :: cough warranty ::

taypotts said:
If you made a nandroid backup of 2.1 couldn't you just restore that? I'm pretty sure you can. I remember doing it with the Moto Droid.
Click to expand...
Click to collapse
Do not restore a 2. 1 nandroid in 2. 2. The update changes the bootloader and recovery versions which aren't part of the backup. The phone will just hang at the MOTO logo. I learned this the hard way. You have to use the sbf. You can then apply your nandroid to get everything back.
Sent from my DROIDX using XDA App

iB4STiD said:
Not sure if this has already been posted somewhere, but after my experience I figured it might be useful to someone.
Click to expand...
Click to collapse
Could you explain?
I am holding off on switching to 2.2, always do to let everyone else find the bugs.
What was your experience?

bad4u6669 said:
Could you explain?
I am holding off on switching to 2.2, always do to let everyone else find the bugs.
What was your experience?
Click to expand...
Click to collapse
what i meant by my experience was downgrading 2.2 to 2.1, My g/f has the droid x, and i am the one to root or mod her phone for her. She wanted to try out froyo and liked the rom alot. there are little bugs i noticed
1. odd little animation hiccup when scrolling home screens
2. lag in gallery
3. what seemed like market delay (but the market has been slow lately, same thing on my vibrant and g1)
but this is a test build not a "final rom"
Like i said downgrading the phone is a little different than other android phones Ive used and i thought this post may help someone out. Im the type of person who wont mod something unless i know i can get back to where i started and with this sbf and "how to" you wont have to worry about that.

pjsockett said:
Do not restore a 2. 1 nandroid in 2. 2. The update changes the bootloader and recovery versions which aren't part of the backup. The phone will just hang at the MOTO logo. I learned this the hard way. You have to use the sbf. You can then apply your nandroid to get everything back.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
also i believe it updates the radio and kernel.. thanks pj for explaining that

If I wanted to go to 2.1 ,don't see why...at the moment.
Before I do a SBF would it be ok to to do a data wipe and a partition wipe in recovery mode then do the SBF bootrecovery deal???
Thank You

after you upgrade to 2.2 koush has a new DroidXBootstrap.apk out
go back to his website and DL it and reinstall then rerun bootstrap.
after that rom manager can do backups or recoveries.
sucks you all get bootloop with sbf, ive done it twice now and has worked fine
keeps all my apps and stuff
goodluck

pjsockett said:
Do not restore a 2. 1 nandroid in 2. 2. The update changes the bootloader and recovery versions which aren't part of the backup. The phone will just hang at the MOTO logo. I learned this the hard way. You have to use the sbf. You can then apply your nandroid to get everything back.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I'm kinda confused what you mean? I did a nandroid backup of 2.1 with the latest bootstrap and clockworld.
I just remember using a nandroid on my girl's moto droid and I went from 2.2 all the way back to 2.0.1.

when trying to sbf on my Mac I get this -bash: ./sbf_flash: Permission denied? Any suggestions I have been asking for 2 days now hopefully someone can help. Thanks

taypotts said:
I'm kinda confused what you mean? I did a nandroid backup of 2.1 with the latest bootstrap and clockworld.
I just remember using a nandroid on my girl's moto droid and I went from 2.2 all the way back to 2.0.1.
Click to expand...
Click to collapse
I also did the same from my Eris. The major difference is that the recovery on those devices were completely replaced not just patched. When you restore a 2.1 nandroid from a 2.2 droid x the android 3e recovery is not replaced. When the system tries to boot it sees that as an invalid recovery image and won't boot, it just hangs at the moto logo forever. When you upgarde to 2.2 on a Droid or an Eris your still using clockwork recovery or amon ra's recovery and not upgrading to the android 3e system recovery. Maybe it was just a fluke that it didn't work for me but it makes sense as to why it would fail, otherwise we would be able to have a full custom recovery.

dscottjr81 said:
when trying to sbf on my Mac I get this -bash: ./sbf_flash: Permission denied? Any suggestions I have been asking for 2 days now hopefully someone can help. Thanks
Click to expand...
Click to collapse
From my understanding sbf_flash is for linux only. To flash on mac you need to use rsd lite with a virtual windows os.
http://www.droidforums.net/forum/droid-hacks/38671-flashing-sbf-mac.html

i cant get my phone to flash. i have done this 2 before with my droid x on 2.1 but now that i am on 2.2 every time i try to use RSDlite, i connect my phone and select my SBF but the START button will not light up so i cannot proceed. any thoughts.. im running windows 7 64 and i have all the drivers working for my phone.

failed sbf flash
Hey guys, i got an error in RSD that says "Failed flashing process. Failed flashing process. Phone[0000]: Phone is not compatible with muli-interface super-file. (0x703B); phone connected
Any ideas, i'm really new to android stuff, been using WM forever.
Thanks for the help

please ignore me as I can't read apparently
if anyone else sees this remeber to copy the pst_flash file to the Program Files/Motorola/RSDLite directory

tacticalmedicokc said:
please ignore me as I can't read apparently
if anyone else sees this remeber to copy the pst_flash file to the Program Files/Motorola/RSDLite directory
Click to expand...
Click to collapse
thanks. i had the same problem.

[Q] JPC Bootloader Problem?

Samfirmware tweet 3hr ago that the new Froyo JPC firmware have some bootloader problem.
Any clue about this? Does it will permanently damage your phone?
I'm considering Flash this via ODIN or the HK one.

Yeah a lot of people are flashing it because it WILL permanently damage your phone.... just think about it for a sec.

MomijiTMO said:
Yeah a lot of people are flashing it because it WILL permanently damage your phone.... just think about it for a sec.
Click to expand...
Click to collapse
Simple english please.
I don't think anyone more should flash this fw.
It's buggy and crazy.
Also your nv-data.bin is modified.
I don't want my warranty to be un-voidable(by flashing original firmware).

I flashed through KIES and I believe this doesn't damage your phone. It's only thorugh Odin??

No, Kies modifies your /efs data as well. Flashing this firmware in any way shape or form will more or less permanently alter your phone

Zilch25 said:
No, Kies modifies your /efs data as well. Flashing this firmware in any way shape or form will more or less permanently alter your phone
Click to expand...
Click to collapse
Implying restoring a backup of the /efs folder after flashing back an original firmware will not undo any changes made by JPC.

I've restored the stuff in /efs to get my phone back to working order- I still have goofed up build numbers and things like that. It's unfair to imply that this is totally safe for anyone to do, especially those that aren't super comfortable screwing around with protected areas on their phones. It's doubly unfair for people to have the impression that odin is the only unsafe way to install it =P

dutchcow said:
Implying restoring a backup of the /efs folder after flashing back an original firmware will not undo any changes made by JPC.
Click to expand...
Click to collapse
So essentially I'm f*cked then.

Thread Astaire said:
So essentially I'm f*cked then.
Click to expand...
Click to collapse
Not necessarily, it's too soon to tell if it will effect anything... take comfort in the fact that 85% of the SGS XDA community flashed this. Even if there IS an issue people will find ways around it =P

So what exactly is stored in the /efs folder and why is it such a bad thing that JPC has modified it? I've flashed this firmware. Does this mean I can't go back to an older firmware now?

I'm not sure of everything contained in the efs folder, but it contains your nv_data.bin files which contain all the unlock codes and such, so at least for people who have carrier locked phones it causes a mandatory network unlock request. You can get around that by restoring the backup files that the firmware conveniently makes.
Those are really the only show-stopping bugs, the rest of them are a bit more subtle, such as marking your phone as being a korean variant =P Though this problem apparently hasn't cropped up for everyone.

ed10000 said:
So what exactly is stored in the /efs folder and why is it such a bad thing that JPC has modified it? I've flashed this firmware. Does this mean I can't go back to an older firmware now?
Click to expand...
Click to collapse
You can, I flashed back JP3 after having a lot of errors with JPC

Zilch25 said:
I'm not sure of everything contained in the efs folder, but it contains your nv_data.bin files which contain all the unlock codes and such, so at least for people who have carrier locked phones it causes a mandatory network unlock request. You can get around that by restoring the backup files that the firmware conveniently makes.
Those are really the only show-stopping bugs, the rest of them are a bit more subtle, such as marking your phone as being a korean variant =P Though this problem apparently hasn't cropped up for everyone.
Click to expand...
Click to collapse
Ah that's good to hear. Mine is the international version, so it should be fine. I thought the new recovery mode and stuff had problems or something.
EDIT:
iuzar said:
You can, I flashed back JP3 after having a lot of errors with JPC
Click to expand...
Click to collapse
After flashing back to JP3, do you still have the new recovery mode or back to the old one? Can you use Clockwork Recovery now?

ed10000 said:
Ah that's good to hear. Mine is the international version, so it should be fine. I thought the new recovery mode and stuff had problems or something.
Click to expand...
Click to collapse
It does, you've got to flash your stock I9000 kernel before trying to apply update.zip files- since your power button wont work as the selector haha So far that's the only issue I know of with it though
Edit: Make sure you flash back to the JPC kernel before you try to actually boot

Zilch25 said:
It does, you've got to flash your stock I9000 kernel before trying to apply update.zip files- since your power button wont work as the selector haha So far that's the only issue I know of with it though
Click to expand...
Click to collapse
Are you sure? Because right after flashing JPC, I went into recovery mode and did a Factory Reset. The volume up/down buttons worked fine for navigating through the menu and the Home button worked fine for clicking a menu item.

ed10000 said:
Are you sure? Because right after flashing JPC, I went into recovery mode and did a Factory Reset. The volume up/down buttons worked fine for navigating through the menu and the Home button worked fine for clicking a menu item.
Click to expand...
Click to collapse
That might be an issue for me because I'm on a captivate No physical home for me haha. I know for I9000 people rooting though they had to flash the original kernel to get it to work (Stole their trick but substituted the I897 kernel to get it to work for me), but I'm not sure why that is

Samsung have disabled the test keys in all firmwares after JP2. We don't have a real key yet, so gotta flash back to JP2 or before in order to apply an update.zip
Hopefully someone will find a new root-workaround soon.

windy31 said:
Samfirmware tweet 3hr ago that the new Froyo JPC firmware have some bootloader problem.
Any clue about this? Does it will permanently damage your phone?
I'm considering Flash this via ODIN or the HK one.
Click to expand...
Click to collapse
Perhaps SamFirmware had his SGS brick when he try to flash it with odin3.
Sent from my GT-I9000 using XDA App

Thanks for the clarification Ryan
As for samsung firmwares it seems he's just erring on the side of caution, he's got a post in Dutch up there that seems to roughly translate into him trying to avoid throwing up a suspicious firmware (the EFS changes etc) and potentially screwing tons of people, gotta respect that

Yes, especially since Samsung put this firmware up as a "beta" in kies withouth worrying about screwing people...

RAZR recovery on Droid 4?

Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283

jgardner said:
Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
Click to expand...
Click to collapse
Why not do the nandroid with safestrap?

I didn't think safestrap was working with the D4?

jgardner said:
I didn't think safestrap was working with the D4?
Click to expand...
Click to collapse
I dont know whats going on lol.....everyone is coming with all these different stories. I used the root exploit that was out and used the safestrap for recovery. I dont think I did anything different than anyone else. And then i took a chance flashing a Razr rom

Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk

jgardner said:
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I took it out until Hashcode brings it out for Droid 4. I've been corresponding with him and if the maker of Safestrap tells you it isn't safe to use on Droid 4 yet then you usually should listen.
All up to your risk though.

I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?

Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.

mattlgroff said:
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
Click to expand...
Click to collapse
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
As far as the warnings i didnt see the warning to not use safestrap till i got on here and it was to late. I figured since i was able to boot into recovery and make a backup i would be ok

Briteyez83 said:
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
Click to expand...
Click to collapse
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.

Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Which FASTBOOT error are you seeing? It should be referencing one of the partitions.
Sent from my DROID4 using XDA App

greekchampion04 said:
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Click to expand...
Click to collapse
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.

Briteyez83 said:
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Click to expand...
Click to collapse
I cant help unless I know what your error message says when you turn on the phone. :/
Sent from my DROID4 using XDA App

Send me your email addy in a message and ill send you a pic of it

Briteyez83 said:
Send me your email addy in a message and ill send you a pic of it
Click to expand...
Click to collapse
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?

Hashcode said:
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Click to expand...
Click to collapse
No, i dont. Im new to root, just rooted in nov. If you give me something thst would fix it that would be awesome.

Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.

Hashcode said:
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Click to expand...
Click to collapse
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.

Briteyez83 said:
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Click to expand...
Click to collapse
If it works, I'll create a new thread with the instructions as I believe there are a few in your situation.

Yes there is quite a few. Ill let you know as soon as i can

[Q] Bell XT860 stock recovery

I would have posted this question in response to these instructions, however I'm still a noob on these forums, and haven't met my 10 post quota yet.
http://forum.xda-developers.com/showthread.php?t=1255198
My question is will this recovery method work for Bell Canada users, or will it only function for Verizon users?
I've installed AOKP a few months back, and while I enjoy it, I've lost support for some key features; namely HDMI, which is disappointing. When I tried recovering to the stock rom to hold me over until some new features and revisions show up on the mod scene, I found out my system backup was corrupt.
I have found a few downloads to system images, however every one I have found link to files that are now taken down. Can someone upload a current system dump?

I can set you up when I get home later
Sent from my XT860 using xda premium

try here http://sbf.droid-developers.org/umts_solana/list.php

What would happen if I flashed the Bell firmware to a Verizon Droid3?
Will it change the radio.img
Will I have to unlock it again?
Will everything still work?
I am using 5.7.906.xt852

jazz53 said:
What would happen if I flashed the Bell firmware to a Verizon Droid3?
Will it change the radio.img
Will I have to unlock it again?
Will everything still work?
I am using 5.7.906.xt852
Click to expand...
Click to collapse
Quite honestly no one knows. Wanna be the first?
Sent from my XT860 using xda premium

I'm really eager to find out. Worst case, you could always just flash the bell XT860 radio afterwards and see what happens!

I am way too new at this to try experimenting with untried solutions
I just barely figured out how to root my ph. Still working on how to flash.
Is it the same as installing a ROM?

jazz53 said:
I am way too new at this to try experimenting with untried solutions
I just barely figured out how to root my ph. Still working on how to flash.
Is it the same as installing a ROM?
Click to expand...
Click to collapse
No, you have to completely reflash your device and will have to re-root it. I think you should give it a go though
You'll need to download RSD Lite and download the XT860 Bell SBF files (they are about 500mb to download). Also make sure you FULLY CHARGE your phone, just in case you run into any issues. I think you can find an SBF how-to doc in the development forums. Please keep us posted.
Are you on Verizon? Because if you and this works, you probably won't be able to use it with them anymore.

Nope, I am on PCMobile without a data plan, use wifi.
I think maybe I'll try a Rom first.

Bricked

Can't get into recovery or anything can someone help or point me into the right place to fix this just need to get the phone up and running the rest i can do root ect,,,,,

mobgod said:
Can't get into recovery or anything can someone help or point me into the right place to fix this just need to get the phone up and running the rest i can do root ect,,,,,
Click to expand...
Click to collapse
Does your phone turn on at all?

i can get into fastboot but thats about it

mobgod said:
i can get into fastboot but thats about it
Click to expand...
Click to collapse
maybe the correct files to flash or what i can do to just get the phone back to stock

mobgod said:
i can get into fastboot but thats about it
Click to expand...
Click to collapse
You will have to use RSD and fxz you phone back to stock. I was in you situation once tried using the bootstrap built for the razor. As long as you can access fast boot mode your alright. Here's the link where you can find the file you need. http://forum.xda-developers.com/showthread.php?t=132810
Get the. 902 fastboot file.

nobe1976 said:
You will have to use RSD and fxz you phone back to stock. I was in you situation once tried using the bootstrap built for the razor. As long as you can access fast boot mode your alright. Here's the link where you can find the file you need. http://forum.xda-developers.com/showthread.php?t=132810
Get the. 902 fastboot file.
Click to expand...
Click to collapse
I've tried that keeps failing with rsd step 6 I believe the first time I got to step 20 than all hell broke lose I believe it was something about web top. Should I just try 902 again is what your telling me ? Also big question is how can I charge the battery I'm getting low battery in fastboot ??
Sent From My Rooted 3D

mobgod said:
I've tried that keeps failing with rsd step 6 I believe the first time I got to step 20 than all hell broke lose I believe it was something about web top. Should I just try 902 again is what your telling me ? Also big question is how can I charge the battery I'm getting low battery in fastboot ??
Sent From My Rooted 3D
Click to expand...
Click to collapse
You might have bad partitions. That might be pretty hard to fix with only rsd light you might have to make your own fxz flashable zip to repartition your phone. That would take some good coding skills.

androidifyme said:
You might have bad partitions. That might be pretty hard to fix with only rsd light you might have to make your own fxz flashable zip to repartition your phone. That would take some good coding skills.
Click to expand...
Click to collapse
you RSDd over safestrap didnt you..

nitephlight said:
you RSDd over safestrap didnt you..
Click to expand...
Click to collapse
Not sure trying to fix my buddy's phone but I think the battery is to dead now how can I charge it ??
Sent From My Rooted 3D

mobgod said:
Not sure trying to fix my buddy's phone but I think the battery is to dead now how can I charge it ??
Sent From My Rooted 3D
Click to expand...
Click to collapse
goto radio shack and buy one of those chargers that works for most batteries like phones and cameras or you can try the usb cable hack.
once charged you will need to FXZ through RSDLite.
RSDLite 5.7
http://d-h.st/Wja
FXZ 905 - Please read the README.txt for more info
http://d-h.st/W6A
Motorola Device Manager (up-to-date USB drivers for Windows)
http://www.adrive.com/public/ABQ6M2/MotorolaDeviceManager_2.2.26.exe

mobgod said:
Can't get into recovery or anything can someone help or point me into the right place to fix this just need to get the phone up and running the rest i can do root ect,,,,,
Click to expand...
Click to collapse
mobgod said:
i can get into fastboot but thats about it
Click to expand...
Click to collapse
mobgod said:
I've tried that keeps failing with rsd step 6 I believe the first time I got to step 20 than all hell broke lose I believe it was something about web top. Should I just try 902 again is what your telling me ? Also big question is how can I charge the battery I'm getting low battery in fastboot ??
Sent From My Rooted 3D
Click to expand...
Click to collapse
twinkyz1979 said:
goto radio shack and buy one of those chargers that works for most batteries like phones and cameras or you can try the usb cable hack.
once charged you will need to FXZ through RSDLite.
There is a program that SamuraiHL has posted called House of Bionic. It's on the droidforums web site and you should be able to search for it there. Either that or google House of Bionic. It should bring up the thread where you can download this program. It's definitely a lifesaver. I would post the link myself but I haven't posted here enough yet to do that.
Hope this helps you out!
Cindy
Click to expand...
Click to collapse

cindylike24 said:
twinkyz1979 said:
goto radio shack and buy one of those chargers that works for most batteries like phones and cameras or you can try the usb cable hack.
once charged you will need to FXZ through RSDLite.
There is a program that SamuraiHL has posted called House of Bionic. It's on the droidforums web site and you should be able to search for it there. Either that or google House of Bionic. It should bring up the thread where you can download this program. It's definitely a lifesaver. I would post the link myself but I haven't posted here enough yet to do that.
Hope this helps you out!
Cindy
Click to expand...
Click to collapse
Link to usb hack http://www.droidforums.net/forum/dr...-code-corrupt-battery-low-cannot-program.html
Link to House of Bionic. http://www.droidforums.net/forum/mo...wngrade-902-no-app-data-loss.html#post2173723
Make sure you download the latest drivers and the right rsd to be used. Link to find both http://www.droidhive.com/forums/ind...nks-in-op-updated-dailyformerly-whats-in-dev/
The reason for it error in out is because the phone doesn't have enough juice to do the fxz process. Make sure that battery has over 50% charge before attempting or do the usb hack with a cord that you will no longer be using.
Click to expand...
Click to collapse

I had this same problem. I used my warranty and got a new bionic. I blame Verizon and Motorola for not giving us what we want with an unlocked bootloader. Personally, I feel they should support the rooting community and be able to reinstall the operating system when we mess up, similar to how we can reinstall windows on a computer. They can even charge $50 for the service and be able to do it in-store from a computer. Not only could they make more money, they wouldn't have to replace as many devices.
Sent from my DROID BIONIC using Tapatalk 2

smokedkill said:
I had this same problem. I used my warranty and got a new bionic. I blame Verizon and Motorola for not giving us what we want with an unlocked bootloader. Personally, I feel they should support the rooting community and be able to reinstall the operating system when we mess up, similar to how we can reinstall windows on a computer. They can even charge $50 for the service and be able to do it in-store from a computer. Not only could they make more money, they wouldn't have to replace as many devices.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
You blame Verizon because you voided the warranty and ****ed up your own phone? Blame yourself for buying a phone that was known to have a locked bootloader to begin with.

smokedkill said:
I had this same problem. I used my warranty and got a new bionic. I blame Verizon and Motorola for not giving us what we want with an unlocked bootloader. Personally, I feel they should support the rooting community and be able to reinstall the operating system when we mess up, similar to how we can reinstall windows on a computer. They can even charge $50 for the service and be able to do it in-store from a computer. Not only could they make more money, they wouldn't have to replace as many devices.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
I would have to say that this is the reason there will most likely never be an unlocked phone sold again for VZW. By doing this you are making everyone look bad! You break, void warranty, then you should have to buy another one. If you don't like my statement don't try something you apparently have no knowledge to do.

Relax guys don't jack the thread for people that need the info
Sent From My Rooted 3D

i hada bricked phone i installed ics 235 and tryed to reflash it after data failed from safestrap . first i used a script it failed bad to reflash stuck in fastflash. so i found house of bionic(hob) of course cell battery was dead before i found it. crap i found online u can stick usb cable after cuttinfg it open and use red(pos)+ n black(neg)- wires to battery sandwhich it in phone . and it work 15min later battery ok used hob to reflash 235 used update 235 on sd card bang its alive.
....this order is my back aka new rsd flash ....no worryes