Related
OK so I was using the RSD 4.7 w/patch. I was trying again since it failed last time. I knocked the usb cable out now. It reads "code corrupt" I am trying one last time to see if the sbf file goes through. Anyone get any ideas?
slseale said:
OK so I was using the RSD 4.7 w/patch. I was trying again since it failed last time. I knocked the usb cable out now. It reads "code corrupt" I am trying one last time to see if the sbf file goes through. Anyone get any ideas?
Click to expand...
Click to collapse
Doesn't sound good. If the sbf procedure is interrupted before it finishes then only the manufacturer can fix it.
ok i had the same situation but i unbricked my phone.
initially i borked my services.jar file and got endless bootloop.
so i then attempt the sbf on win7 64bit.
1st attempt says it fails on the uploading RAM to bootloader.
phone reboots but is still in bootloop.
2nd attempt says failed at same part so i unplug the phone and im stuck with
code corrupt. At this point pressing power makes the phone go straight to the bootloader with code corrupt message.
Ok so i call verizon and ask if they got any Droid x in stock lol. They of course tell me nope so i try again but this time i switch to a different computer using
Win XP 32bit. i download rsdlite with patch , drivers and of course the sbf file.
3rd attempt i get through phone is back to working order, and the /data partition is untouched so all my apps are still intact.
just had to re-root the phone.
close call i must say but at least i know it does work now. Think its the 64 bit OS
that messed it up.
the only other thing i noticed is that when i installed rsdlite on winxp and started it up my firewall asked for permission to unblock rsd from the net.
when i installed on my win7 64 bit the firewall nvr asked for this permission so im guessing the program contacts outside sources for something?
only thing i can think of for the intial failure 64bit or firewall.
hope this helps anyone else having problems
slseale said:
OK so I was using the RSD 4.7 w/patch. I was trying again since it failed last time. I knocked the usb cable out now. It reads "code corrupt" I am trying one last time to see if the sbf file goes through. Anyone get any ideas?
Click to expand...
Click to collapse
who can help me ,waiting .................
liliu said:
who can help me ,waiting .................
Click to expand...
Click to collapse
Try downloading a later version of RSD Lite, such as 4.8. Or even better, use Linux.
But the 'code corrupt' issue is common and you need only SBF to fix it.
Sent from my DROIDX using XDA App
dont worry about it. Ive had this show up on my bootloader plenty of times.
What u wanna do is .sbf back to a working copy of .340 (VRZ_MB810_2.3.34_1FF_01.sbf) and start over again
There is also a bootable linux iso image available for download. Fully automated and totally painless way to SBF back to Froyo 2.3.340.
My DroidX Thrives on the DarkSlide!!
liliu said:
who can help me ,waiting .................
Click to expand...
Click to collapse
use the linux sbf solution.
after a failed windows flash for any reason i resort to linux. but thats just me and i have never had a bad flash using linux....ever. i have brought many dead devices back to life
read and re-read the instructions. then proceed at you own risk.
Droid X SBF with Linux
+1 on linux.
It takes way more time to get RSD working on Win7 than when I use XP. For some reason the drivers just don't seem as robust.
http://www.multiupload.com/ZUK28IEYAU
download this linux based disc image.... burn the iso with a program such as nero or even the windows image burning software
boot from cd.... all you need to do is start your phone up in bootloader already hooked up to your computer and run this disk
Just wanted to +1 the Linux boot disc suggestions. When you get the CODE CORRUPT error message it means the SBF flash failed in some way. The linux method should get you up and running again. It's never failed for me.
SaurusX said:
Just wanted to +1 the Linux boot disc suggestions. When you get the CODE CORRUPT error message it means the SBF flash failed in some way. The linux method should get you up and running again. It's never failed for me.
Click to expand...
Click to collapse
+1 for any Linux sbf method, works ten times better than using RSD Lite.
Sent from my DROIDX using XDA App
I also will +1 the Linux method to sbf, has worked flawlessly for me, never longer that 15 from insertation of CD into comp. It's great.
Enjoy. Terry
Sent from my DROIDX using XDA App
No Megaupload
I am looking for solutions to sbf'ing my phone and I keep running into links to download from megaupload...wait...I think it just worked. I updated to the most recent rsd lite and it worked while I was writing this. I was going to try the method above, which has a link to megaupload, but I guess I don't need to.
I did find the sbf files here: It won't let me post a sites.google.com/site/motosbf/
I had to do a lot of digging to find that. Is there somewhere else that people are putting files like these and files like the Linux one mentioned above?
weekscorp said:
I am looking for solutions to sbf'ing my phone and I keep running into links to download from megaupload...wait...I think it just worked. I updated to the most recent rsd lite and it worked while I was writing this. I was going to try the method above, which has a link to megaupload, but I guess I don't need to.
I did find the sbf files here: It won't let me post a sites.google.com/site/motosbf/
I had to do a lot of digging to find that. Is there somewhere else that people are putting files like these and files like the Linux one mentioned above?
Click to expand...
Click to collapse
Google "1kds Droid x" it should turn up everything you need.
Sent from my Transformer TF101 using Tapatalk
I posted a step by step method with links (including .621 sbf) here
obviously, you don't want to sbf to .621 unless you already took the OTA....
Anyone around that used this thread?
My screen says 'service required, code corrupt'. RSD does not show the phone, it may not be able to get into fastboot. I am using Win 7 64 bit and I see some people say they had trouble with that? Should I try on a fresh win 7 32 bit?
Thanks
There is no fastboot. Just bootloader.
sd_shadow posted an in depth on how to sbf your phone and gain root. Go read it. Download the files. Make a boot disc/usb. And do it.
There is no reason to use RSD with the ezsbf method. You can do whatever you want. But the ezsbf/root method is the easiest even if it looks difficult.
RSD Lite on Windows 7 64 bit
SharpnShiny said:
Anyone around that used this thread?
My screen says 'service required, code corrupt'. RSD does not show the phone, it may not be able to get into fastboot. I am using Win 7 64 bit and I see some people say they had trouble with that? Should I try on a fresh win 7 32 bit?
Thanks
Click to expand...
Click to collapse
I have also had trouble with Windows 7 64 bit. It was much easier when I went back to my old XP machine. It also works really well on Linux, I didn't even have to worry about drivers.
I can't use any more thanks today (reached the limit) but thanks!
I'm going to put 32 bit windows on a spare partition just to be sure.
Does anyone have an sbf for the R2D2 Edition? I got a little too tweaky.
Thanks!
Lol.. not yet.. next time boostrap and make a back up
See if you can recover with the r2d2 rom from mydroidworld
http://www.4shared.com/file/rePStgcF/VZW_24_Full_ROM.html
I've got a nandroid backup on my SD card I jsut can't seem to get back to the bootstrapper.
Try booting up and then pull your battery and then try booting up again. See if that puts you into bootstrap.
Sent from my R2-D2 using XDA App
Thanks for the advice, I've been yanking the batt, pressing volume buttons and everything the only thing I can get to is the stock reset screen (android with !) and the boot loader. At this point I've probably done more harm than good resetting memory and clearing cache and stuff.
Oh, in case anyone wondered, the sbf fro the regular Droid 2 does not work on this bad boy. That'll teach me to mess wiht things I don;t know about. Looks like what I have is Bootloader and a copy of my backup from clockworkmod.... is there a way to build an sbf from your .img files?
Try powering down the phone then plugging it in and boot it up. That often loads clockwork revovery on mine.
Try going back into bootstrap recovery and pushing the bootstrap recovery button again. Then the reboot recovery button. That should work. I had the same thing happen to me and that worked.
Sent from my DROID2 using Tapatalk
hyatari said:
Try powering down the phone then plugging it in and boot it up. That often loads clockwork revovery on mine.
Click to expand...
Click to collapse
Yeah, for whatever reason that often does cause my d2 to boot into cwm.. I think it replaces that weird battery startup thing, did anyone else get that when they first used their d2?
Sent from my DROID2 using XDA App
rexit1982 said:
Thanks for the advice, I've been yanking the batt, pressing volume buttons and everything the only thing I can get to is the stock reset screen (android with !) and the boot loader. At this point I've probably done more harm than good resetting memory and clearing cache and stuff.
Click to expand...
Click to collapse
If your D2 won't boot all the way up (which is what it sounds like), you may be able to get into CW Recovery by one of the methods below:
1. This is the most reliable way I've found: Boot up and pull battery when the boot animation starts (after the M logo disappears). Then reinsert battery and start up...should go to CW Recovery then. Thought I spell it out just in case you hadn't tried it that way specifically.
2. Make sure there is no 'update.zip' file in the root of your SD card - again make sure NO 'update.zip' file. Then boot into stock recovery, choose the apply update.zip option, and after it aborts, pull the battery and boot up again.
3. Another set of steps that might work:
-Boot into stock recovery by holding X while powering up
-Hit the magnifying glass on the keyboard to open recovery menu
-Highlight reboot and hit "ok" on the keyboard
-When you get the "M" screen pull the battery
-Power back up and it will go to Clockwork recovery
Good luck on that....
rexit1982 said:
Oh, in case anyone wondered, the sbf fro the regular Droid 2 does not work on this bad boy. That'll teach me to mess wiht things I don;t know about. Looks like what I have is Bootloader and a copy of my backup from clockworkmod.... is there a way to build an sbf from your .img files?
Click to expand...
Click to collapse
What makes you say that...what did you try and what happened? What version of RSD Lite did you use, and what was the failure/results, etc. This is a pretty surprising thing to hear.
R2D2 and D2 are the same HW as far as anyone has seen from specs, etc., the 2.2.20 SBF not working seems odd.
Thanks.
I used RSDlite 4.7. the flash get tot he reboot point and then a bootloader error thaT said "bootloader err:A5,70,70,00,1f".
rexit1982 said:
I used RSDlite 4.7. the flash get tot he reboot point and then a bootloader error thaT said "bootloader err:A5,70,70,00,1f".
Click to expand...
Click to collapse
You're two versions behind...RSD Lite 4.8 and 4.9 are out. I'd suggest you get at least 4.8 and try again. I don't have the links, but should be google-able.
When you used 4.7 you added the RSD patch on top of RSD 4.7 after you installed it, right?
What does the phone do now when you boot it up? Just sit on M logo, get to boot animation, or ?
Redflea said:
You're two versions behind...RSD Lite 4.8 and 4.9 are out. I'd suggest you get at least 4.8 and try again. I don't have the links, but should be google-able.
When you used 4.7 you added the RSD patch on top of RSD 4.7 after you installed it, right?
What does the phone do now when you boot it up? Just sit on M logo, get to boot animation, or ?
Click to expand...
Click to collapse
Yes I did drop the patch on. The phone goes straight to a black screen with white writing that says
Bootloader
D2.35##
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
##Updated code
I googled the error, I found this was the same error that DroidX users who OTA'd to their 2.2 update and then tried to SBF back to 2.1.
I have a new device now but I am keeping hold of the old one for the next couple days to try anything anyone ahs any ideas on. When I get to my other phoe I'll try a new rdslite.
If you don't have a linux computer I'm working on a livecd with adb and the sbf_flash script so that anybody with a computer can flash there phone in linux. I have one version so far but I'm trying to cut down the size because it's too big for a CD.
newk8600 said:
If you don't have a linux computer I'm working on a livecd with adb and the sbf_flash script so that anybody with a computer can flash there phone in linux. I have one version so far but I'm trying to cut down the size because it's too big for a CD.
Click to expand...
Click to collapse
Sounds like a good project...
rexit1982 said:
Yes I did drop the patch on. The phone goes straight to a black screen with white writing that says
Bootloader
30.03**********
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
***I am not sure if these were the same numbers but the rest of the message is exact match
I googled the error, I found this was the same error that DroidX users who OTA'd to their 2.2 update and then tried to SBF back to 2.1.
I have a new device now but I am keeping hold of the old one for the next couple days to try anything anyone ahs any ideas on. When I get to my other phoe I'll try a new rdslite.
Click to expand...
Click to collapse
You mean you're going to try the newer RSD Lite on the new phone or the old phone?
Interesting that it's the same error the Droid X users were getting...that does change the game a little, doesn't it. Thanks for the additional information - a relevant "news" post is here:
http://www.mydroidworld.com/forums/...-1-any-reason-after-official-upgrade-2-2.html
So it seems like VZW may have made the same change to the bootloader w/2.4.x on the D2 that they made w/2.2 on the DX.
Redflea said:
You mean you're going to try the newer RSD Lite on the new phone or the old phone?
Interesting that it's the same error the Droid X users were getting...that does change the game a little, doesn't it. Thanks for the additional information - a relevant "news" post is here:
http://www.mydroidworld.com/forums/...-1-any-reason-after-official-upgrade-2-2.html
So it seems like VZW may have made the same change to the bootloader w/2.4.x on the D2 that they made w/2.2 on the DX.
Click to expand...
Click to collapse
I am running RDS lite 4.9 against my "old" device right now. I'll let you know how it works out. What is the current official SW version on the D2?
The VERY first time I tried this I did get a success message when it was done
I get an error now, Error sending RAM download to bootloader ... I am trying to attach pictures of the full message.
Actually, the mem_map blank and the bootloader messages are pretty common across all motorola phones, I've seen similar error messages on the older p2k (v300, razr, etc) type phones when you have a flash fail out at certain points. It's generally recoverable (in most cases, anyway) as long as you have a full flash (.sbf or .shx)
rexit1982 said:
I am running RDS lite 4.9 against my "old" device right now. I'll let you know how it works out. What is the current official SW version on the D2?
The VERY first time I tried this I did get a success message when it was done
I get an error now, Error sending RAM download to bootloader ... I am trying to attach pictures of the full message.
Click to expand...
Click to collapse
For the D2 (non-R2D2) it's 2.2.20, which is what the avaialable D2 SBF is...
bladearronwey said:
Actually, the mem_map blank and the bootloader messages are pretty common across all motorola phones, I've seen similar error messages on the older p2k (v300, razr, etc) type phones when you have a flash fail out at certain points. It's generally recoverable (in most cases, anyway) as long as you have a full flash (.sbf or .shx)
Click to expand...
Click to collapse
Thanks...
I believe I've also seen some comments that when flashing via a Windows box fails, that trying from a Linux setup can be more likely to be successful, but don't remember the details, so I may be garbling that info...
newk8600 said:
If you don't have a linux computer I'm working on a livecd with adb and the sbf_flash script so that anybody with a computer can flash there phone in linux. I have one version so far but I'm trying to cut down the size because it's too big for a CD.
Click to expand...
Click to collapse
Please let me know when you have this livecd available. I too had the same response on my Droid 2. I wound up having to buy a new D2, but I'm still holding onto my old one...hoping one day I might be able to revive ut. LOL
Sent from my DROID2 using XDA App
Hey guys, I have done a ton of reading and researching about modding android phones since recently migrating from iPhones. I got a Droid1 and did some basic root/rom/overclock etc.
I just got a DX a few days ago and right away decided to start with the modding. Anyways, In a nutshell I attempted to go about the ROMing process in a similar manner to my Droid1 and ended up going to the Rubix1.6 ROM without ever backing up my stock OS.
I wanted to be able to jump back and forth to a blurless/blurred ROM to get a good feel for what I want outta it but am not sure how I should go about getting the stock OS stuff back on. I've read up about the SBF, but is that the only way to go?
Thanx for any help guys, greatly appreciated.
Sam G
Sadly, yes. Since you didn't back up before you started you will have to SBF to get a stock ROM. Be sure to make a nandroid of your modded ROM, SBF, root, backup, then flash back and forth.
Now as far as a Nandroid backup you mean just a backup through clockwork recovery correct?
CBX133 said:
Now as far as a Nandroid backup you mean just a backup through clockwork recovery correct?
Click to expand...
Click to collapse
yea. a nandroid backup is the backup you create in cw recovery
Ok So I did it and restored nicely after doing a wipe after.. Now I can't ACTIVATE my phone. Any ideas why it would mess with the activation. When I hit activate and then 1 it just says to enter the number.. SHIIT
CBX133 said:
Ok So I did it and restored nicely after doing a wipe after.. Now I can't ACTIVATE my phone. Any ideas why it would mess with the activation. When I hit activate and then 1 it just says to enter the number.. SHIIT
Click to expand...
Click to collapse
the activation system has been down for a few hours now. You can try *22899. Or do it online here http://www.verizonwireless.com/b2c/activate. Or just call the 1800 number and do it with a csr.
Ok, I'm hoping it is just a bad coincidence that the activation server is down. I'll pack it up and try again in the morning. If that's what it is then I am all set otherwise. Thanx!
CBX133 said:
Ok, I'm hoping it is just a bad coincidence that the activation server is down. I'll pack it up and try again in the morning. If that's what it is then I am all set otherwise. Thanx!
Click to expand...
Click to collapse
of course it's just a coincidence. flashing a rom or doing an sbf to your phone does not cause the verizon activation system to crash. lol. whenever you sbf your phone or do a factory reset, you have to do the *228 to reactivate. thats normal.
Just some info... when I wipe out my phone and boot it up (skipping) activation it works already. Found this out by wiping my phone, booting it up, and I got a text message immediately. Lol.
CBX133 said:
Hey guys, I have done a ton of reading and researching about modding android phones since recently migrating from iPhones. I got a Droid1 and did some basic root/rom/overclock etc.
I just got a DX a few days ago and right away decided to start with the modding. Anyways, In a nutshell I attempted to go about the ROMing process in a similar manner to my Droid1 and ended up going to the Rubix1.6 ROM without ever backing up my stock OS.
I wanted to be able to jump back and forth to a blurless/blurred ROM to get a good feel for what I want outta it but am not sure how I should go about getting the stock OS stuff back on. I've read up about the SBF, but is that the only way to go?
Thanx for any help guys, greatly appreciated.
Sam G
Click to expand...
Click to collapse
'
Just consider your SBF your 2.3.15 backup copy. It's not a pain. It's easy and it should be a tool in every modder's arsenal. IMO, people who don't know how to sbf, are destined to have to anyway, eventually, if they mod enough. The only thing is that when they have to, they won't know how and will kinda panic. I say be ready to sbf before you root, so you're ready when trouble comes.
Me? I love modifications and will sometimes go too far or make a mistake at 2 am, when I really should be sleeping instead and I wind up bricked. No problem. Just SBF and I'm on my way. If you need further info or how to's feel free to ask.
Steven
Steven58 said:
'
Just consider your SBF your 2.3.15 backup copy. It's not a pain. It's easy and it should be a tool in every modder's arsenal. IMO, people who don't know how to sbf, are destined to have to anyway, eventually, if they mod enough. The only thing is that when they have to, they won't know how and will kinda panic. I say be ready to sbf before you root, so you're ready when trouble comes.
Me? I love modifications and will sometimes go too far or make a mistake at 2 am, when I really should be sleeping instead and I wind up bricked. No problem. Just SBF and I'm on my way. If you need further info or how to's feel free to ask.
Steven
Click to expand...
Click to collapse
Hey just got my replacement x today already rooted and have fly x on it. The sbf back up category is my only weakness. When my phone goes belly up im kinda lost. Do you have or know of any threads walktbroughs on bow to.bring a bricked phone back to life. Im putts replacements for this year through asurion and will have to do this if im bricked again. I was stuck on the tranquility logo couldn't get out. Thanx.
Sent from my DROIDX using Tapatalk
illcat2000 said:
Hey just got my replacement x today already rooted and have fly x on it. The sbf back up category is my only weakness. When my phone goes belly up im kinda lost. Do you have or know of any threads walktbroughs on bow to.bring a bricked phone back to life. Im putts replacements for this year through asurion and will have to do this if im bricked again. I was stuck on the tranquility logo couldn't get out. Thanx.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Here's what I used to guide me through the sbf...
Here is a link to the guide I used. It is for the 2.1 SBF though.
http://www.intomobile.com/2010/09/21/droid-x-stock-android/
Here are the instructions with my modifications for 2.2...
IMPORTANT!!! - the directions are for restoring 2.1 so you do not do some of the steps! They were the best I could find. I followed them except for things that did not apply.
instructions:
1. First off, choose the right version of Motorola USB drivers for your computer and install them (32bit) (64bit)
2. Download & install RSD Lite 4.7 (download)
I did not use 4.7 as it is not current. I used 4.9
You will need to patch this after installing. There is an .ini file included in the folder that needs to be placed in your install directory. /Program Files/Motorola/RSD Lite
I used 4.9 and did not have to patch any files- the above step was unnecessary.
3. Download the Droid X Android 2.1 SBF file, which you can find here
of course I used the 2.2 SBF file here...
http://rootzwiki.com/
4. Unzip the SBF file to your desktop
i did not unzip mine to the desktop- i put it where i stash my android files- it made no difference.
5. Run RSD Lite, and click the “…” button, then find the SBF file that you just unzipped to your desktop and select it.
Starting here i followed the directions to the "t". Went through all the steps. !!!!!MAKE SURE YOU START WITH 100% BATTERY!!!!!! It takes a long time and if your phone dies during the process it is a nightmare.
6. Plug your Droid X into your computer and power it down
Go into the Bootloader (with phone off, hold the CAMERA button and VOLUME DOWN, then hit the POWER button)
After holding for 2-3 seconds, release the buttons and RSD Lite should recognize your Droid X
7. Click the start button to flash Android 2.1 to your phone.
of course we are flashing 2.2
8. When the flashing is complete, unplug your phone
The Droid X will likely not boot up all the way, so pull the battery out
Put the battery back into the phone and reboot into Recovery mode ( Hold the HOME button and press POWER until you get an exclamation mark. Release the HOME button and press the SEARCH button)
Using the VOLUME UP/DOWN buttons, navigate to “wipe data/ factory reset” option on the screen, and press the CAMERA button halfway down to execute.
When complete, choose to reboot your phone
9. It takes a while. Hope this helps. And I hope it goes smoothly. It was nerve racking for me. After you have finished the process you will not be rooted. Use the market app "Z4root" or which ever method you prefer.
good luck.
Click to expand...
Click to collapse
thepolishguy said:
Here's what I used to guide me through the sbf...
Click to expand...
Click to collapse
i really appreaciate the guide and quick response im going to try to save these for future refrence.
just tried this method for the experience on the droid i bricked. worked like a charm was a bit easier too. phone rebooted on its own. i wiped just to make sure since i need to send it back to vz i already got my replacement. but this definetly gives me a little more confidence knowing i can bring it back from the dead if i have to. thanks again.
detailed sbf restoration instructions
illcat2000 said:
Hey just got my replacement x today already rooted and have fly x on it. The sbf back up category is my only weakness. When my phone goes belly up im kinda lost. Do you have or know of any threads walktbroughs on bow to.bring a bricked phone back to life. Im putts replacements for this year through asurion and will have to do this if im bricked again. I was stuck on the tranquility logo couldn't get out. Thanx.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
sure! from http://androidforums.com/droid-x-al...ing-custom-rom-theme-how-unbrick-droid-x.html
*my note: make sure you install moto dx drivers on your PC: http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
C. UnBRICKING INSTRUCTIONS:
HELP ME. Ima noob! I BRICKED MY PHONE!
1. go to Home and DL the leaked full OTA FROYO 2.2 .SBF file.
2. Download and install RSDLite v4.8 (it should be on Home if not, go Google it.)
3. If your phone is stuck on the load screen, pull the battery, wait a minute, push the battery back in and restart with the phone’s Boot Loader Mode (do this by pressing the red camera button + volume down + power button hold all of them in the order that I stated until your phone flashes briefly). Your phone should flash white and a Boot Loader menu will come up. Make sure there is at least 20 to 25 percent battery life remaining in order for the reformat of you phone to complete. If your phone dies in the middle of this process GOD HELP YOU.
4. Run the RSDLite File and connect your Droid X to your computer via USB.
5. Browse for the .SBF file you downloaded in step 1 and click “Start”, at which point the program should run and your phone will proceed to unbrick
6. EASY RIGHT?
7. Once unbricking you will have to go through reactivation of your phone. This is normal so just go through the steps you did when you first started.
8. GUESS WHAT? You made a backup of your previous customizations REMEMBER? If you don’t want to deal with the hassle of re-downloading your entire life onto your phone again follow the “ROOTING” instructions in Part A and redownload Bootstrap and reboot into recovery mode to RESTORE the backup you made by following steps 2-11 in Part B….except you won’t be going to “install from sdcard” you will going to “Backup and Restore” and “Restore from sdcard”.
HELP Please - Error running SBF in RSD Lite
First off, I'm a newbie, so please go easy on me if these are dumb questions. I get the following error while trying to run "VRZ_MB810_2.3.15_1FF_01.sbf" in RSD Lite 4.7 while in boot mode. I don't know what else to do. My phone won't work. Thank you for any advice you can give.
Failed flashing process. [Phone 0000]: Phone is not compatabile with multi-interlace interface super-file. (0x703B): Phone connected.
rossi28usa said:
First off, I'm a newbie, so please go easy on me if these are dumb questions. I get the following error while trying to run "VRZ_MB810_2.3.15_1FF_01.sbf" in RSD Lite 4.7 while in boot mode. I don't know what else to do. My phone won't work. Thank you for any advice you can give.
Failed flashing process. [Phone 0000]: Phone is not compatabile with multi-interlace interface super-file. (0x703B): Phone connected.
Click to expand...
Click to collapse
did you put the patched pst_flash.ini file in the rsdlite install directory?
I put that file in program files>motorola>rsd lite. I did it after installing the program if that matters. The zip file folder name was RSD Lite 4.7+Patch. Also, in RSD Lite in order for the program to recognize my droid x i had to select the "first come first serve device id mode" under the device id options in the config menu. Don't know if this matters, just trying to give as much info as possible. Thanks.
rossi28usa said:
I put that file in program files>motorola>rsd lite. I did it after installing the program if that matters. The zip file folder name was RSD Lite 4.7+Patch. Also, in RSD Lite in order for the program to recognize my droid x i had to select the "first come first serve device id mode" under the device id options in the config menu. Don't know if this matters, just trying to give as much info as possible. Thanks.
Click to expand...
Click to collapse
yea, you can only do it after installing the program. it has to be closed though when you do it and you have to overwrite existing file. if you did all that properly, then it may be a corrupted sbf. I would just install rsdlite 4.8 or 4.9 and retry. those dont require a patch.. if no workie, then redownload sbf.
rsd lite 4.8 is here http://www.multiupload.com/HL0ZAL9GK8
I can't remember the order I did it in so I'll re-install with the instructions you gave. Thank you! I'll report back.
Since Josuearisty has tested my sbf on his phone, it makes me think the method only works on the phone it was created on. Its actually really simple and easy to do, and I can give instructions for both Linux and Windows on how to make it. I posted instructions a few posts down, but they're vague cause I don't like typing a lot of text on my phone. Who does?
***Your always in the danger zone when messing with SBF files, I've done this method multiple times and it worked. If you follow the instructions word for word, you should be safe. Since I got this working for my phone, I thought everyone would like to know how I did it to make their own Custom SBF for when that bad time comes.***
Things Required
RSDLite or sbf_flash
stock sbf
adb setup and working
MotoAndroidDepacker
Thread With RSDLIte, SBF, and most everything needed..
Page with MotoAndroidDepacker and other helpful tools.
Step 1
Flash your phone with the Stock sbf from The thread also contains RSDLite, SuperOneClick, and MotoDrivers if you need them.
Step 2
Use the eeblueoffee trick to bypass blur setup.
Step 3
Enable Debugging at Settings/Applications/Development/Android Debugging
***Enable Screen Always on--its directly below Android Debugging. This is very important, the phone likes to freeze while doing dd commands and the screen shuts off midway.***
Step 4
Root Phone With SuperOneClick and Enable Non-Market Apps. Then Reboot Phone.
Step 5
Open A Terminal Or Command Prompt When Phone Boots Up
5a. adb shell
5b. su
5c. dd if=/dev/block/system of=/sdcard/CG39.smg then exit adb
5d. adb pull /sdcard/ E:\ (or whereever on your system you want it, E: is my ntfs shared partition)
Step 6
Open MotoAndroidDepacker
6a. Open Sbf and unpack it
Step 7
Replace unpacked CG39.smg with the dd CG39.smg from phone
Step 8
Open MotoAndoridDepacker
8a. Open folder with all the smg's
8b. Compile Sbf
Step 9
Your done, flash the phone with the newly created sbf.
***Its a good idea to wipe data\factory reset in between stock and custom sbf flashes. SBF Flashing doesn't wipe the \data\ directory and latent crap from the previous flash can be left behind. That's why you have to wipe data\factory reset after SBFing from a custom rom, if you're curious***
Step 4.5 (Advanced and Experemental)
You can add in any extras you want between steps 4 and 5. And they have to be added to the SYSTEM PARTITION ONLY. I've only added in 2nd-init Defy, and while it got the bootmenu DIRECTLY after an sbf flash, the only links that worked were Reboot and Shutdown. I'll look for a fix when I feel up to hours of sbf flashing again. You could try to either install Titanium Backup Pro and move apps like Bravo Sideload Enabler to the system partition, or use adb to install as a system app. To be safe, I'd do as little as possible, in as few of steps as possible, for example, I only touched my phone to enter eebluroffee and to enable debugging, that's all. Then uninstall TB Pro, and continue on to Step 5. Sorry for the Wall of Text, but all this is important.
HOW THIS WORKS
After the phone is flashed with the sbf, the system partition is signed DURING the first boot. By doing a diskdump, you're able to get the CG39.smg plus the key it gets on first boot, and since the signature is already there on your custom CG39.smg from the dd, it doen't get recreated when flashing your custom sbf and booting up. I was hoping the one I made was universal, but it doesn't seem to be. I'll try to make one for us (a universal preroot) if its even possible.
***Original Post*****
Like the title says, a prerooted sbf. I've tested this three times, with a stock sbf and full data\fatcory reset in between each flash. Only tested on Linux with sbf_flash. No RSDLite on Windows since I don't have it installed to test with.
You still have to use Bravo Sideload Enabler from market for non market apps. I plan to change that. I'm halfway there already, I know which xml to edit to enable non market apps, but am unsure of the syntax used in AndroidManifest.xml to edit it before compiling the apk. Another idea is to make Bravo Sideload Enabler a system app and part of the sbf, but I didn't think of it until just now, literally, right now.
With this sbf, to flash CM7 or any custom rom, the steps are simply Flash sbf, Bravo Sideload Enabler, Defy 2nd-init, flash rom.....that's it.
Also, to get around the blur setup, type eebluroffee on the soft-keyboard on the very first screen you get to, just press the menu "button" for a second or so. Sometimes it takes a few times to work.....but eventually it does.
Link to sbf: http://www.mediafire.com/?tx1sdgftp9ng5b6
Thank Josuearisty for giving me the idea, and Epsylon3 for his informative post with all the information I needed to make this.
I also tried adding in Defy 2nd-init. After flashing, it would go to the custom bootmenu, but nothing worked.
skeevy420 said:
Like the title says, a prerooted sbf. I've tested this three times, with a stock sbf and full data\fatcory reset in between each flash. Only tested on Linux with sbf_flash. No RSDLite on Windows since I don't have it installed to test with.
You still have to use Bravo Sideload Enabler from market for non market apps. I plan to change that. I'm halfway there already, I know which xml to edit to enable non market apps, but am unsure of the syntax used in AndroidManifest.xml to edit it before compiling the apk. Another idea is to make Bravo Sideload Enabler a system app and part of the sbf, but I didn't think of it until just now, literally, right now.
With this sbf, to flash CM7 or any custom rom, the steps are simply Flash sbf, Bravo Sideload Enabler, Defy 2nd-init, flash rom.....that's it.
Also, to get around the blur setup, type eebluroffee on the soft-keyboard on the very first screen you get to, just press the menu "button" for a second or so. Sometimes it takes a few times to work.....but eventually it does.
Link to sbf: http://www.mediafire.com/?tx1sdgftp9ng5b6
Thank Josuearisty for giving me the idea, and Epsylon3 for his informative post with all the information I needed to make this.
I also tried adding in Defy 2nd-init. After flashing, it would go to the custom bootmenu, but nothing worked.
Click to expand...
Click to collapse
Great, I always thought about it, its a good thing for us.
I'd like to try on Windows and RSD Lite but I'm afraid of damaging my phone.
It shouldn't hurt. Like I said, I've already flashed it 3 times. Or 7 sbf flashes in the past few hours, including stock flashes. I'd appreciate an RDS Test. I don't really want to flash the sbf again....I restored my WR1.4 nandroid only 45 mins ago after about 6 hours of testing this. I'll be back on in the morning, it's 1am here and I'm getting tired.
skeevy420 said:
It shouldn't hurt. Like I said, I've already flashed it 3 times. Or 7 sbf flashes in the past few hours, including stock flashes. I'd appreciate an RDS Test. I don't really want to flash the sbf again....I restored my WR1.4 nandroid only 45 mins ago after about 6 hours of testing this.
Click to expand...
Click to collapse
at least if we are rooted, we can download terminal emulator from play store and install bravo sideloader enabler from sd card.
I cant download sideloader from market cause I dont live in US, at least is a great advantage for us!
I could make sideload enabler a system app installed by default. Give me a day or two for that.
Error on Windows with Rsd Lite, just showed me the logo and then back to bootloader.
Thanks God I was able to flash the original sbf file again.
Damn. Maybe the method I used only works on my phone. It's easy to do.
After stock sbf flash, do the eebluroffee trick.
Root with SuperOneClick
Adb shell
su
dd if=/dev/block/system of=/sdcard/CG39.smg
adb pull /sdcard/CG39.smg E:\
Decompile stock sbf with MotoAndroidDepacker
Replace stock CG39.smg with created one
Repack sbf with Depacker
Flash
See, its not that hard. That's all I did and it worked perfectly for me.
It's possible it only works on the phone that makes it. And you HAVE to edit the system dump. If you edit stock sbf's CG39.smg, it gives bootloader error. With this method, you could technically make a CM7 sbf.
Anybody with linux try my sbf with sbf_flash?
skeevy420 said:
Damn. Maybe the method I used only works on my phone. It's easy to do.
After stock sbf flash, do the eebluroffee trick.
Root with SuperOneClick
Adb shell
su
dd if=/dev/block/system of=/sdcard/CG39.smg
adb pull /sdcard/CG39.smg E:\
Decompile stock sbf with MotoAndroidDepacker
Replace stock CG39.smg with created one
Repack sbf with Depacker
Flash
See, its not that hard. That's all I did and it worked perfectly for me.
It's possible it only works on the phone that makes it. And you HAVE to edit the system dump. If you edit stock sbf's CG39.smg, it gives bootloader error. With this method, you could technically make a CM7 sbf.
Anybody with linux try my sbf with sbf_flash?
Click to expand...
Click to collapse
I have done that before, not decompile sbf with motoandroiddepacker, I made a backup of system using those commands.
I think that SBF will not work with any other phone, but at least is a big advance.
If everybody can do it, they will be able to flash their custom SBF alredy rooted and maybe with any other apps.
---------------------------------------------------------
The thread you posted with rsd lite and sbf file is dead, links are not working, use this post in the same thread:
http://forum.xda-developers.com/showpost.php?p=22706722&postcount=66
I uploaded the files again, I'll create a post with these files.
That thread worked 4 months ago dammit.
I hope it does lead to better things, but its worth the 10 minutes of effort to make you own personal preroot sbf, and easy to do in my opinion.
Also sort of related, I think we have version 3 bootloader. That explains why if you flash a Defy sbf, you can't go back. It changes efuse level and you can't change efuse down, only up.....its what screws Defy users who go sbf crazy and flash the first thing they see. We don't have that problem cause we only have the one sbf..... Damn you Motorola.
skeevy420 said:
That thread worked 4 months ago dammit.
I hope it does lead to better things, but its worth the 10 minutes of effort to make you own personal preroot sbf, and easy to do in my opinion.
Also sort of related, I think we have version 3 bootloader. That explains why if you flash a Defy sbf, you can't go back. It changes efuse level and you can't change efuse down, only up.....its what screws Defy users who go sbf crazy and flash the first thing they see. We don't have that problem cause we only have the one sbf..... Damn you Motorola.
Click to expand...
Click to collapse
I made a custom SBF now and it didnt work, what version of motodepacker did you use?
Is there anything else to do?
What about sbf calc, I think it is to determinate if sbf is good or not, I dont know.
Version 1.3, not the mono one. I didn't use sbf-recalc, only used it once ever 8 hours ago actually. Do you have access to Linux and have a blank cd handy? Try flashing with sbf_flash since its what I used. I'll try with RSDLite tomorrow night, about 20 hours from now. I just installed White Rabbit Test2 and I'd like to run it for a day to see how it performs and it likes my tweaked smartass.
The instructions I posted were the ones I used, on both Windows and Linux, and worked twice. The first time I tried, all I did was edit it with " mount ./cg39.smg ./cg39 -o loop" and that didn't work. The only thin you could do different is to replace dd if=/dev/block/system with dd if=/dev/block/mmcblk1p25 the of= part stays the same.
Another possible problem is your memory card became full during the dump. It will just quit without error. You should have at least 400mb free to be safe, 330mb BARE minimum and probably not very safe. With only adding root\superuser, the created sbf should only be 378,546,533 Bytes & 378,546,533 Bytes. Those are the exact filesizes of the first two sbf's I made. Yes, they're the same size. The md5 is different.
92cb645d5a04d1221f81ee566072149f ./firmware.sbf (1)
fc4e49adf931377c8ccbd3943b3664ba ./custom.sbf (2)
I used the second one I made two more times before I posted to make sure it did work, and once earlier this evening when I flashed the wrong defy zip.
I first came across this method on a post from Epsylon3 at Defy dev on a post about BL7 sbf's not being able to root. I came across it a second time somewhere here on xda and it explained it with a bit more detail, but I had already made my second sbf by then and it worked....and I was ecstatic.
skeevy420 said:
Version 1.3, not the mono one. I didn't use sbf-recalc, only used it once ever 8 hours ago actually. Do you have access to Linux and have a blank cd handy? Try flashing with sbf_flash since its what I used. I'll try with RSDLite tomorrow night, about 20 hours from now. I just installed White Rabbit Test2 and I'd like to run it for a day to see how it performs and it likes my tweaked smartass.
The instructions I posted were the ones I used, on both Windows and Linux, and worked twice. The first time I tried, all I did was edit it with " mount ./cg39.smg ./cg39 -o loop" and that didn't work. The only thin you could do different is to replace dd if=/dev/block/system with dd if=/dev/block/mmcblk1p25 the of= part stays the same.
Another possible problem is your memory card became full during the dump. It will just quit without error. You should have at least 400mb free to be safe, 330mb BARE minimum and probably not very safe. With only adding root\superuser, the created sbf should only be 378,546,533 Bytes & 378,546,533 Bytes. Those are the exact filesizes of the first two sbf's I made. Yes, they're the same size. The md5 is different.
92cb645d5a04d1221f81ee566072149f ./firmware.sbf (1)
fc4e49adf931377c8ccbd3943b3664ba ./custom.sbf (2)
I used the second one I made two more times before I posted to make sure it did work, and once earlier this evening when I flashed the wrong defy zip.
I first came across this method on a post from Epsylon3 at Defy dev on a post about BL7 sbf's not being able to root. I came across it a second time somewhere here on xda and it explained it with a bit more detail, but I had already made my second sbf by then and it worked....and I was ecstatic.
Click to expand...
Click to collapse
Im a little bit afraid of breaking my phone, just thinking about a hardbrick make not to follow with this now.
Well I used the mono one, I was not out of memory 16gb with only 2 in use.
I think the backup was fine, maybe it was something with motodepacker.
I'll try later, I think I'll try with a cliq xt I have, which has some problems, that way if something is wrong, I wont be losing a big thing!
I understand that hardbrick fear. This is my only phone. My backup (oldscool razr) crapped out a while back, so I sat there looking at that terminal with the first sbf for 5 mins before the first flash, then when it didn't boot, I was like oh f&^k. Flashed stock, made the 2nd, and it worked. Made a third and it's my new sbf.
skeevy420 said:
I understand that hardbrick fear. This is my only phone. My backup (oldscool razr) crapped out a while back, so I sat there looking at that terminal with the first sbf for 5 mins before the first flash, then when it didn't boot, I was like oh f&^k. Flashed stock, made the 2nd, and it worked. Made a third and it's my new sbf.
Click to expand...
Click to collapse
Well, I do it easy.
After flashing is completed:
I write eebluroff in the motoblur screen.
Enable debugger in applications.
Install sideloader enabler apk with adb
Install gingerbreak to root and 2nd init to install custom recovery from SD Card and restore my backup.
That's all I do when I flash with RSD Lite, I wish at least that the SBF file would come with sideload enabler pre-installed or the ability to install from sdcard!
I noticed quite a few market enabling apps yesterday. Couldn't test cause I'm on wr1.4.
Never used gingerbreak.
2nd-init didn't function properly after sbf flash. Only access to bootmenu, shutdown and restart.
Try SuperOneClick 1.9.5. Its version I used.
Also, enable screen always on. Stock became iffy during adb when screen went off.
skeevy420 said:
I noticed quite a few market enabling apps yesterday. Couldn't test cause I'm on wr1.4.
Never used gingerbreak.
2nd-init didn't function properly after sbf flash. Only access to bootmenu, shutdown and restart.
Try SuperOneClick 1.9.5. Its version I used.
Also, enable screen always on. Stock became iffy during adb when screen went off.
Click to expand...
Click to collapse
2nd init copies some files to a folder that maybe is in another code group.
At least with sideload enabler for bravo, it would be great.
We just have to install gingerbreak from sdcard to root and 2nd init defy.
Hey guys, let me just preface this by saying that this was my first time trying to root, and that I am still very unfamiliar with many of the things involved in rooting. That said, here is my problem and almost exactly what I did to get there.
Alright, so I chose last night to be the night when I finally rooted my Droid 2. I had android 2.3.4 gingerbread .621 version when I started. I ran through the easy windows install instructions first on this page: well, since I can't post links, the page is http: //rootzwiki . com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/ (just remove the spaces in the web address). This didn't work because being the noob that I am, I didn't realize how to flash the .sbf file using rsd lite (now I know how to do that I guess, just a little too late).
So I said screw that, I will just run the cd. I downloaded the .iso, burned it to cd, booted to cd, and ran the program. The first time, I tried using the "Root Only" option. This ran, but didn't seem to work. So once that didn't work, I ran the first option that let you have the option to root (I have forgotten the exact wording). This worked and I got to the screen where I had to factory reset the phone. However, instead of being able to do this, I was stuck in bootloader with the error message "Err: A5,70,70,00,1F." So at this point I kind of realized that I was screwed so I tried to flash stock android 2.3.4 back to my phone using RSD Lite. I did this, and ended up changing the error message from the previously mentioned one to "Err:A5,70,70,00,00." So at this point I figured that I had a bad .sbf file and downloaded a new one and used RSD Lite to flash it. After I did this and it failed, I now am stuck in bootloader with a "Code Corrupt" message.
So basically, rooted or not, I would like to be able to use my phone again. I have seen in a couple places that the problem could be due to low battery, but I have switched to a fully charged one with no luck still.
This was my first attempt at rooting, and I am fully hating my first experience, but I'm already this far so I am willing to do the work to learn and get my phone back. If anyone can provide me with some pretty detailed instructions (remember, I'm a total noob and bricked my phone on something everyone else seems to have had no trouble with), that would be incredible.
Thank you in advance!
Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http://droid.koumakan.jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?
bhigham said:
Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http ://droid. koumakan.jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?
Click to expand...
Click to collapse
Yes, it is the droid 2.
bhigham said:
Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http ://droid.koumakan. jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?
Click to expand...
Click to collapse
Quick question though, when I am looking for an SBF to flash, do I want to flash on 2.3.4 like I had on, or a previous version, or does it matter?
xwsxlogan said:
Quick question though, when I am looking for an SBF to flash, do I want to flash on 2.3.4 like I had on, or a previous version, or does it matter?
Click to expand...
Click to collapse
Problem with Droid 2 on 2.3.4, is that once on that version, you can never go back to an earlier one.
That error message you mentioned first, sounds like the error message you get when trying to flash an older SBF.
Incidentally, where did you download the CD that you tried to flash from? Was it the one linked in the first post of the thread?
bhigham said:
Problem with Droid 2 on 2.3.4, is that once on that version, you can never go back to an earlier one.
That error message you mentioned first, sounds like the error message you get when trying to flash an older SBF.
Incidentally, where did you download the CD that you tried to flash from? Was it the one linked in the first post of the thread?
Click to expand...
Click to collapse
Yes, it was in the link listed before. The method had been cross posted on this site and on their site.
Ok, above the err message, what does the top line say?
bhigham said:
Ok, above the err message, what does the top line say?
Click to expand...
Click to collapse
The only screen that I can get reads as follows:
Bootloader
D2.37
Code Corrupt
Battery OK
OK to Program
Connect USB
Data Cable
Someone suggested that by holding up and power would bypass the "code corrupt" message, but that does not work. Also, the X+Power to try and wipe the phone clean doesn't work either.
When you flash stock 2.3.4 with rsdlite, does rsdlite give you any error messages?
One of the most common errors with rsdlite is when it has the drivers for the regular bootloader mode, but not the drivers for the radio flash mode.
If this happens, you will get that code corrupt error message.
Also, what OS are you using? XP, Vista, 7, 64bit,
bhigham said:
When you flash stock 2.3.4 with rsdlite, does rsdlite give you any error messages?
One of the most common errors with rsdlite is when it has the drivers for the regular bootloader mode, but not the drivers for the radio flash mode.
If this happens, you will get that code corrupt error message.
Also, what OS are you using? XP, Vista, 7, 64bit,
Click to expand...
Click to collapse
I did get an error message when trying to flash the stock 2.3.4 and it was something to do with RAM, but unfortunately this was 5AM this morning and I was beyond exhausted so I don't remember exactly.
I am using Windows 8 x64, but have access to XP, Vista, 7, and server if I need to.
I would definitely try XP if I were you, and if you have access to another USB cable, I would try that.
To use XP, install the motorola drivers first, then use rsdlite.
I have used RSDlite 5.6 and 5.7 on my D2G, and both have worked fine with XP
bhigham said:
I would definitely try XP if I were you, and if you have access to another USB cable, I would try that.
To use XP, install the motorola drivers first, then use rsdlite.
I have used RSDlite 5.6 and 5.7 on my D2G, and both have worked fine with XP
Click to expand...
Click to collapse
Alright, I will go ahead and get XP installed along with the drivers. Do you think that I should use a version previous to 2.3.4 then so that I have a better chance to root?
I am charging up my battery now using another phone, so I will start on it in a bit. Thank you again for answering all of my stupid questions and helping me out, I really appreciate you taking the time to do it.
It would be nice if you were able to go back to an earlier version, but that isn't an option. Once on 2.3.4, no going back.
bhigham said:
It would be nice if you were able to go back to an earlier version, but that isn't an option. Once on 2.3.4, no going back.
Click to expand...
Click to collapse
So you're saying that the only thing I will be able to flash is the 2.3.4?
xwsxlogan said:
So you're saying that the only thing I will be able to flash is the 2.3.4?
Click to expand...
Click to collapse
exactly
bhigham said:
exactly
Click to expand...
Click to collapse
Alright, I will try again tonight with a charged battery and XP and let you know how it goes.
This link here http://www.google.com/url?sa=t&sour...rICoBg&usg=AFQjCNHht4SU69VoDkBnMBCA_0uf9WYpyw. Will take you to the download for the correct sbf.
Correct sbf should read: 1ff-p2a_droid2_cdma_droid2-user-2.3.4-4.5.1_57_dr4-51-120117-release-keys-signed-Verizon-US.sbf.gz
Sent from my DROID2 using Tapatalk 2
Alright Update after flashing the .sbf file that was given in the previous post.
I used XP, running RSD Lite 5.6, with Motorola drivers installed. I charged a second battery up to around 70% or so to use during the process. I also changed USB cords from the previous one that I was using. I loaded the .sbf into RSD Lite, started it, and it ran flawlessly, skipping right over the RAM step in which it failed last night. Had to remove the battery and reinstall to do the manual reboot, and all of my phone settings were exactly as I had left them when I started. I had to dial *228 +1 to get the phone back on the network, but that was no problem.
So after all of this, I'm back to where I started last night haha. Special thanks to bhigham for all of the support and walking me through this today and also slogar25 for confirming that I had downloaded the right .sbf file.
So I guess my problem is solved...until I try and root it again!
glad your phone is working again.
If you want to try to root again, you might have better luck with a freshly wiped phone, but if you prefer not to risk it, I don't blame you.
It is possible a cord issue, but just guessing here.
bhigham said:
glad your phone is working again.
If you want to try to root again, you might have better luck with a freshly wiped phone, but if you prefer not to risk it, I don't blame you.
It is possible a cord issue, but just guessing here.
Click to expand...
Click to collapse
Yep, I've noticed you have been following the cross post on this site for the methods that I tried last night when I really didn't have a clue what I was doing. Do you think that I should just try the CD method again? I mean worst case I would do the same thing I did last night, but now I know how to flash it back to the stock 2.3.4. I don't mind wiping my phone, but after it survived everything I did last night, I feel more attached to my data haha.
Also, how do I mark this post as solved?