Telnet and Terminal Emulator errors... I can not root. - G1 General

I am on 1.41, and using the war theme. I have not been able to telnet or use TE for a few days now, so I decided to post. I know if telnet does not connect, I can su, then telnet from the TE.... but not even that works.
Telnet tells me error ... connection refused, something something null.... so I went right over to TE and did a su, telnet ... error type 3, activity class (then something about superuser...) su permission denied.
Can anyone shine some light on this issue ...

It seems that you flashed the 1.31 version of the theme. go back to original JF 1.41 and try to dl the updated theme. I think we all had an issue with this until they updated the themes. Im using Vintage War and it works great. I have no problems with TE or su enter.

yep yep yep

So.. I have the same error, and this happened while in root (JFv1.41 RC30) as well as after I went back to official RC29 to get the RC33 update (of course, the next day JF already released his RC33..doh..) trying to get root back, and I get that same error, and I can't figure out whats going on, since I rooted just fine the first couple times I tried.. any ideas??
**yes, I have followed the instructions just as I did before when it worked. No idea whats preventing it.

did you type in telnetd from the main screen before you opened up terminal emulator

Yep. Followed instructions completely as they are set out:
http://forum.xda-developers.com/showthread.php?t=442480 from the sticky of it.

Related

Shell hangs while manually rooting

Hey guys,
I love everything people have done on here, and thought its about time for me to take the plunge and load a custom rom. I followed the instructions to manually root my hero, and everything "seemed" successful. I get to the Shell, get my #, enter the mount command in all of the walkthroughs, and.....nothing happens, it just hangs. I've let it sit there for half an hour and nothing happens. I then ctrl-c, re-opened the shell and enter basic commands (cd, pwd, ls) and nothing happens. Any ideas?? The sprint update seems like its never coming and I was so excited to play with a custom rom this weekend!

some rooting help

im following the walkthrough from stock 1.5 to 2.1 rooted and i just did step 1 where i load the PB00IMG.zip. when i turned my phone back on it asked me to login to gmail and all that stuff and now when i check the phone info it says i'm running 2.1 already even though i have not gone through the other steps? i assume i still need to? and am i supposed to be on 2.1 already after step 1? i was just under the impression that i would have 2.1 still the very end?
i also saw that there was a new thread that had a new eris official .zip should i use that one? or the one mentioned in the walthrough?
yes you should be on 2.1 after the first step but you do need to continue on with the other steps. you can use erisofficial.zip or the one in the post or any of the roms that have now been made for the rooted eris. there are quite a few choices in roms now so you can look through them and see which one appeals most to you....
Ok. I am having trouble with step 3... not sure how to get the common prompt to go to the sdk tools folder so I can start inputing the lines? I'm new so any help would be great. also... what is going to be the difference between the 2.1 I have running now and the one that would be flashed in the last step? I have a Droid and am doing this for my wife. is step 3 pretty much like making a nandroid backup?
Go to My Computer and ( C: ). Find your AndroidSDK folder and keep going until you are in your tools folder. Right click on any item and go to Properties. Under your Command Prompt type cd (followed by a space and type whatever it says next to Location in Properties). Hope this helps.
For me, in my cmd I type: cd C:\AndroidSDK\android-sdk-windows\tools
After you hit enter, it should have C:\AndroidSDK\android-sdk-windows\tools (or whatever your path is) followed by a cursor. Now you can type your commands.
Ok Ill try that when I get back home. just curious though... what would happen if I jusT stopped after step 1 with the 2.1 that's on the phone now?
I left it right there for about a week. I didn't have time to finish the rest. Nothing bad will happen, you just won't be able to flash custom ROMs or other root-related things. You still have 2.1 and you can download apps that you couldn't with 1.5. If you're content with that, you may be better off just doing the OTA leak instead.
The roms have fixed alot of the glitches in the original 2.1 root that you have on there now such as having to log in to gmail after each reboot.
i get to the last part of running the commands and the i get errors saying out of memory???
it ran through the errors a bunch and the very end it says error writing recovery: no space left on device...? after doing step 1 i used mybackup pro to re load all my wifes texts... all 8000 of them... could that be the reason?
ok i ran through the steps and didnt get an error this time... but how do i know if it worked?
yamaha83 said:
ok i ran through the steps and didnt get an error this time... but how do i know if it worked?
Click to expand...
Click to collapse
power down your device, then while pressing the end/power button and volume up at the same time and you should come into the recovery menu. From there you can flash updates, roms etc. you can back up your current config all sorts of things.
So I have not been able to check if I flashed the recovery correctly yet cuz my wife had to go out of town. but now she can't send pic messages. is this one of the fixes in some of the roms? Also now that I have root I should be able to back up all her data and apps to restore them onto a new Rom right? Just want to make sure its the same as my Droid...
I'm in the from stock 1.5 to rooted 2.1 thread and everytime I try the command:
adb shell flash_image recovery /sdcard/recovery.img
I get:
flash_image: permission denied
Any help is appreciated as I'm coming form the vogue android forum and this is getting a little foreign to me
EDIT: I'm assuming i'm retarded and forgot to run the command before it.. I just ran through it again with nothing denied
Up and running good!! Thanks for the help everyone!
Anyone have any suggestions on a good stable Rom??
I've been using Jamezelle's Sense-able 2.0. I've tried the others, this one is most stable in my opinion. I'm waiting for the EvilEris 1.2 to come out to try that.

[Q] Root stuck, Red triangle and exclamation mark

Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.
You need to do the root process to get to the care bear, then flash villainrom on the care bear, before rebooting.
That will get you sorted
Well I rooted using universal androot, then used the teminal to input the su (press enter)
flash_image recovery /sdcard/recovery.img (press enter) part of instructions but at no point do I see the care bear :S
I have the same problem as Ejen. The phone is root i have superuser permission i do titanium backup .I put RA-hero-v1.7.0.1 with Better Terminal Emulator. When I turn off phone and press Home&Power I get a picture phone with a triangle. Does anyone have an idea how to solve this?
Yes, this is because stock rom automatically reflashes recovery with the stock one each shutdown iirc.
You need to stop this happening, but I can't remember the command. When you have root using universal androot though, you can stop it happening.
Or maybe it's too early for me. Wait till I've had a coffee or two and I'll revisit this...
Perhaps you can edit /system/etc/install-recovery.sh. A quick look trough /system didn't find anything like a shutdown script so perhaps this file is run by the android environment.
I had this same issue the other night, been searching for a fix, hopefully one appears here soon, thanks Pulser_g2, i was hoping to install your 1.5 Rom
Bloke
Ah seems I'm not the only one well at least I wasn't just being silly then, well tried it multiple times but still seem to have no success even tried the unlockr websites method with no success either.
If anyone knows thanks
Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try http://forum.xda-developers.com/showthread.php?t=726118 and see if that works.
I'm trying to work out what's going on here...
P
I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help
Ejen said:
I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help
Click to expand...
Click to collapse
Ok,... So how far did you get on setting up adb http://www.villainrom.co.uk/forum/s...de-Setting-up-ADB-and-how-to-use-it.-(Windows) ?
I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know
Ejen said:
I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know
Click to expand...
Click to collapse
Type adb devices, and if you see your phone's serial number, then you don't need to worry about drivers. Remember to "cd" into the correct folder first.
I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back
Ejen said:
I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back
Click to expand...
Click to collapse
Where have you downloaded your Android SDK too?
for example > "cd c:\SDK\tools"
pulser_g2 said:
Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try VillainROM Roots 2.1 and see if that works.
I'm trying to work out what's going on here...
P
Click to expand...
Click to collapse
I guess that is already on the phone RA-hero-v1.7.0.1 as you said stock rom automatically reflashes recovery. I suppose that the method VillainROM Roots 2.1contains RA-hero-v1.6.2.img. What will then happen with recovery if i try to do again root with VillainROM Roots 2.1?
When you try that method, you get the phone booted into patched recovery, at which point you take a nandroid backup and flash a custom ROM.
this prevents the recovery being lost. Just try it
I'm not at home and can not install ADB and run runindos.bat. I have on SD card recovery and FroydVillain 1.5. That's why I tried this method.Next week I'll be home and if someone does not fix the problem i will try the method you suggested me.
Can I try to put again recovery with Better Terminal Emulator, maybe recovery was corrupted ....
i went through the same thing!!
Ejen said:
Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.
Click to expand...
Click to collapse
helloo!! i apologise if i am interupting or butting in whilst your in the middle of other solutions... i just saw the title and jump right in. i went through the exact same thing just 2 weeks ago!! unfortunately for me there was no successful forums or websites at the time... it sounded like a simple problem, with no simple solution.
this may not be what you where looking for, but its a very quick easy method that definately worth a try.
so... am i right in saying you have the official OTA HTC android 2.1 update?? and you now want to get this rooted?? and have you also tried rooting using the two common methods, the "one click root" and the "unrevoked" one? thats wat i did and i kept being stuck at the same red triangle and exclamation mark.
those methods (and countless others) will not work with the official htc hero android 2.1. (as far as i know) what you will need to do is downgrade the phones software. check htc's website and look for the older RUU and using the computer get your hero back to android 1.5. (under no circumstance should you upgrade your 1.5 android to the 2.1 android via HTC's OTA update... its only going the remove the root access!!!! - always reject it)
then continue to root as per the numerous rooting guides. done? now, obviously you will want to flash an android 2.1 rom. if you want to keep to htc's original 2.1, you can search for this in the forums under 'development'. or go ahead and flash the custom roms (villianrom).
thats exactly how i did it. im not entirely sure if this is the info you are after... but reply back and ill be happy to answer any query - big or small. (i should warn you, im no expert - but this forum is filled with the earths most powerful brains - u should have an answer in no time!!)
I have an HTC Hero. I ran the simple root method and got Carebare response.
I too have read numerous threads in the forum here and elsewhere but can't seem to get past the USB section.
adb says no device
I can use HTC Sync to sync data to the phone.
The SDK is installed and I have previously used it to capture screen shots of my device.
If I try to run one of the RUU executables, it fails with a [114: USB Error] (number may be wrong but the message is right.
I can mount the SD card and copy files to/from it.
I am running Windows 7 Home Premium 64bit on a Quad Core AMD CPU.
If I do the Home/Power thing, I get the same red triangle as described in the 1st message of this thread.
Fwiw, I have successfully and repeated loaded ROM's on my previous phone (HTC S621) so I am not a complete newb (but i am newb to Android).
What am I missing? This shouldn't be this hard (at least from what I've seen posted anyway)

Somebody, i need to unroot my phone using Mac , don't know how

im having problems , on how to unroot my phone , so i can install EB13 , i know that i have to open App Terminal , but don't know what to type next inside of it
and what does this mean's (chmod +x run.sh and run it)
somebody plz explain it to me like a little kid
just recently change from Windows to Apple and everything is different and frustrating ..thanks
Somebody!!!! plz help me
I'm having trouble understanding. Rephrase
Which eb13 did you download? I think z4root can root and unroot an epic. I just used it to perm root my gf's epic last night. She rolled back to di18.
It can be done on a Mac but I gave up and dual booted with XP and flash that way because it's easier.
Or something easier could be to dl a version of eb13 that you can flash with clockwork recovery. Flash it like a rom. Clear all the caches and do a full factory wipe in clockwork then flash the rom. After that root if possible with z4root app. Get eb13 that is a full install in recovery, not an update.
have you tried here? there are instructions for osx
http...forum.androidcentral.com/epic-4g-rooting-roms-hacks/60768-how-factory-restore-fix-bricked-phone.html
I talked my gf through flashing an update.zip that was a full di18 with clockworkmod mod that was already on the phone from when I had it. As long as you already have cwm recovery and there's a version of eb13 that is full and meant to be flashed in custom recovery, I don't see why it wouldn't work. You could do all this without a computer or at least I did when she went from eb13 full to di18 full.
If rom manager had an epic recovery on the server, I checked last night and it's gone, I think in theory it can be done. If you had a new phone, run z4root for permanent root. Then run rom manager for cwm recovery. Then download full eb13 that is set up to install like install.zip. Boot into cwm recovery and clear out all caches and do full factory reset then flash the new rom. Then boot into phone like normal and set it up. Install and run z4root again and hope it works with froyo. Then I think you're done and didn't use a computer. Someone will probably point out that there's some thing that needs a PC for.
Use wifi of course
This is actually quite easy thanks to the directions posted in this thread here:
http://forum.xda-developers.com/showthread.php?t=808103
If you rooted using the one click method, I believe this should work to undo root. Someone please correct me if I'm wrong as I'm still new-ish to this myself.
INTEL MAC & LINUX:
Note: Mac and Linux users may be prompted to enter administrative password, as adb server requires sudo permissions to start.
No drivers required.
Extract the zip file.
Open Terminal. Use the cd command to get to the directory. If you extracted inside the Downloads folder, it would be easy in Terminal as so:
Code:
cd ~/Downloads/epic.aio.v2.04
Now give permissions and run it:
Code:
chmod +x run.sh
./run.sh
Click to expand...
Click to collapse
sorry, let me b clear , i did a clockworkmod(2.5.1) a few month ago with my Mac , now i forgot how to uninstall it. Anyways i download a version of Eb13 to my sd card(on the phone) an when i try to install it on my phone it says that it install , but when i go to chk the version it still's showing 2.1 update 1
i did everything through the phone but it is NOT installing EB13
question, do i need to bring my phone completey to stock, that means removing the Clockworkmod(2.5.1) or can i install EB13 with the CWM already in my phone???
Where can i find a good version of EB13 that i can download straight from my phone, cuz using my Mac and trying to push the program through it is a little bit of confusing inputing all does codes , like , what the hell this means ( chmod +x run.sh)???
come on man, read a little bit. you can do it.
get access to a windows computer for a few hours and use ODIN to flash over EB13. read xda's samsung epic wiki page.
Art77 said:
sorry, let me b clear , i did a clockworkmod(2.5.1) a few month ago with my Mac , now i forgot how to uninstall it. Anyways i download a version of Eb13 to my sd card(on the phone) an when i try to install it on my phone it says that it install , but when i go to chk the version it still's showing 2.1 update 1
i did everything through the phone but it is NOT installing EB13
question, do i need to bring my phone completey to stock, that means removing the Clockworkmod(2.5.1) or can i install EB13 with the CWM already in my phone???
Where can i find a good version of EB13 that i can download straight from my phone, cuz using my Mac and trying to push the program through it is a little bit of confusing inputing all does codes , like , what the hell this means ( chmod +x run.sh)???
Click to expand...
Click to collapse
thats a command u put in terminal..u have to put something before that though.. go here and download the file....leave it in your downloads folder unzipped...go into terminal and paste the first code...then copy second code (chmod + run.sh
./run.sh) and your good it opens a script and im not sure which but one of the numbers does the uninstall....but yea u shouldnt have to uninstall....just find a pc get odin and odin the EXT4 version here and its ALOT easier..
is not working or im not doing it correctly...thanks anyway i give up

[Q] Cant get Droid 2 Gingerbread 4.5.601.A955 Update

Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.
This process should un root and put you back on stock Froyo. This is a complete factory wipe, so if you're wanting to back anything up, do it before any of these following steps. Once complete, go to Settings > About Phone > Check for Updates and report back.
WARNING: Only run the first set of instructions, do not flash the Gingerbread leak, you can get the official after running RSDlite.
To get back to stock: http://www.mydroidworld.com/forums/...id-2-gingerbread-2-3-3-release-prerooted.html
1. Grab the SBF File
You must start the process with your phone running the official 2.3.20. If you have already upgraded to gingerbread grab this 2.3.20 sbf file .... Download
2. Grab RSDlite
You must use RSDLite to use the sbf file from step 1 .... RSDLite
3. Grab the Drivers Drivers ....Download now
4. Run RSDLite and sbf your phone back to 2.3.20
Didn't work
I was unable to get the OTA to work. I was rooted using OneClickRoot and unable to update like everyone else (FAILED). I tried to sideload from a post on another page, but that didn't work either (not even sure that was the correct file). So I followed the direction as mentioned above, SBFing to a stock 2.3.20, but only after I did a complete wipe of the phone. Now that I have SBFed I don't have any phone signal and cant get it to work with anything I have tried. I don't want to go crazy trying stuff and brick my phone. So at this point, how do I get my phone working again. Screw GB for now, I just need my phone to work. HELP!
It's pretty hard to brick a D2 unless you happen to flush it down the toilet. SBF again to 2.2, do NOT root. Go to the about phone menu and run the OTA update to GB. After that run the one click root for Droid 3.
working
I don't know why, but after re-installing (SBF) 2.3.20 the phone decided to stop working. I thought it could have been a bad SBF file, and it could have been. The step that seemed to work was wiping the phone after the install. Once I did this step, of course you have to set the phon up again, but it prompted me to "Activate" the phone. So I hit activate and the phone called Verzon and run a programming function. Once that completed the phone worked fine. I am currently downloading the OTA, so here's hoping!
I did actually get the sideload (update.zip) file to work before going back to 2.3.20 as mentioned above, but I still didn't have phone. At this point I was going to do a wipe but could not get the phone to enter recovery, I'm thinking there must be some other method that's different to get it there. If anyone know, that would be good info to have.
Still downloading.....
I believe if you dial *228 it will activate for you.
I am also unable to get the OTA GB update to work. It gets all the way to re-boot and about 1/3 of progress bar after accepting to install the 4.5.601.A955. Just like mentioned in one of these other posts. I have tried everything - uninstalling and reinstalling z4 root, deleting SU, Bootstrap recovery, root explorer etc. All of which were not done properly or in the right order. I have been working on this the last 2 days. Yesterday, I even called tech support at Verizon, they helped me do a factory reset, and when it failed again, offered to send me a new D2 because my phone is still under warranty and won't accept the update, so I took their offer.
But then I got nervous because my clockwork mod was still showing up on power up, so I finally figured out how to remove that. I have SBF'd at least a couple of times since I got clockwork removed and update still fails.
My memory is not to good, but I think I first rooted in late Dec 2010. It seems like the 2.3.2 OTA update came out in Jan or Feb 2011. I don't believe I had to unroot to get that update. My current System Version is 2.3.20 A955 - Android version 2.2, and that is what it goes to after doing the factory reset on the phone. The Verizon tech didn't act like it should have gone back to an earlier version.
I have only one other issue - a week ago the phone took a bath when I fell in the water. Dried it off quickly and the only thing wrong other than barely-noticeble water damage to the display, is that the power button now requires exactly 3 pushes every time to boot the display to the unlock screen.
Sorry for the long post. Here are my questions: I no longer have clockwork at power up, it boots like a normal out of the box D2, am I missing something? Will Verizon be able to tell that I had rooted my phone? Could the water and resulting power button issue be the cause of it not accepting the update? TIA
Im having a similar problem. I can get the ota update just fine, but it will install aboutt 1/3 of it and just stop and reboot. All i did was root. I unrooted and same thing happpens. Downloaded this thing like 6 times already and same thing each time. Although a long time ago i did uninstall nfs, blockbuster, and i think kindle but i cant remember...
Are you doing a full factory wipe back to 2.3.2 when you do this or are you just "wipe data/factory reset" in recovery? Because if you only do that in recovery you're just wiping data. There's another thread here with a .zip you can run in stock recovery, not clockwork. Rename to update.zip, put it on the main directory of SD, boot holding X and power, then press the volume buttons. Hit install update.zip.
On the D2 - I am doing Settings<Privacy<Factory Data Reset<Reset Phone< Confirm.
How do you get into stock recovery? Do I need to be rooted again?
I would imagine but I don't know. Boot up holding the X key and power, should bring you to a droid guy with a !. Hit the volume buttons, if you get a blue and red recovery menu, you're in. It's not going to ask you for superuser so it's worth a shot at least.
Thanks for your help idefiler6. I got into stock recovery, but when I did the update it also failed - some logwrapper error. I am now having difficulty getting back in to stock recovery.
I had deleted system/bin/hijack and renamed system/bin/logwrapper.zip to system/bin/logwrapper to remove or stop the clockwork mod from booting up, which did make clockwork go away using Root Explorer. I found a post here to do this droidxforums.com/forum/droid-x-help/22080-im-begging-help-please-help-3.html
Anyway, my new phone is supposed to get here Wed. So I guess I'll just take my chances of whether Verizon cares or figures out I had rooted my phone. Regardless, the power button failing to work properly, should qualify for warranty coverage.
Crossing my fingers for you.
im getting mine replaced under warranty due to it cannot install the update no matter, how many times we have wiped it with tech support.
I also was very lucky since I got my 2nd warranty phone right before the one year mark so it extened the phone i have now another 90 days.
Problems all around
I too am having the OTA update problem. Downloads fine and gets about 1/3 of the way before rebooting and giving me an update failed message.
Current Device info:
D2G
System Version: 2.4.330.A956
Android Version: 2.2
Unrooted using Z4Root
Current logwrapper from November 12, 2010. No hijack or recovery .bin files in place.
I have tried RSDlite 4.8 and 4.9 using two separate downloads of the 2.3.20.A955 SBF from the link provided in this thread. Motorola Drivers are up to date and no errors are showing up in my Device Manager on my W7 PC.
The error I get when flashing in RSD is;
critical error febe 0047
Any thoughts? I'd like to try Gingerbread but haven't had any luck no matter what I try.
When in Doubt Go Linux!
Here's how I fixed the problem. I'm not a big Windows guy and the issues I was having were frustrating me because I had to update drivers, download new versions, blah, blah, blah.
I found a solution that allowed me to use my Fedora OS and it took me 10 minutes, no hassles, no errors. The incredible thing is, it kept ALL of my data, apps and settings on the phone! I had to upgrade from 2.29 (the flash from below) to 2.30 OTA and then to Gingerbread OTA Awesome stuff.
Here are the steps provided by hwertz from modmymobile.
"Download sbf_flash (just goggle it)
Download DROID2WE_X6_2.4.29_FULL.sbf.zip" (google this too)
(You would download these with firefox, make sure Firefox saves in the directory "Download".)
Open a terminal (Applications->Terminal)
Plug in your phone via USB, turn it off. Flip open the keyboard and turn it on WHILE holding down the up arrow. You'll see this screen with blocky white text, like right away -- it doesn't even get to the Motorola logo."
-----
OK, so in the terminal, you will
type "cd Download"
(If you saved somewhere else, cd to there. For instance if you saved to "Desktop" you would "cd Desktop" instead.)
Type "gunzip sbf_flash.gz"
If this gives an error, it's ok, it means you already had "sbf_flash" instead of "sbf_flash.gz"
type in "chmod +x sbf_flash"
Type in "unzip DROID2WE_X6_2.4.29_FULL.sbf.zip"
Then type in "sudo ./sbf_flash DROID2WE_X6_2.4.29_FULL.sbf"
If you are running a "real" copy of Ubuntu this'll ask for your password. The LiveCD has no password so it won't.
That's it! It'll appear to do nothing for a few seconds while it loads the flash, then it'll start flashing your phone which takes 5 or 10 minutes.
Good luck!
Thank you hwertz and thank you Linux!
cbotd said:
I too am having the OTA update problem. Downloads fine and gets about 1/3 of the way before rebooting and giving me an update failed message.
Current Device info:
D2G
System Version: 2.4.330.A956
Android Version: 2.2
Unrooted using Z4Root
Current logwrapper from November 12, 2010. No hijack or recovery .bin files in place.
I have tried RSDlite 4.8 and 4.9 using two separate downloads of the 2.3.20.A955 SBF from the link provided in this thread. Motorola Drivers are up to date and no errors are showing up in my Device Manager on my W7 PC.
The error I get when flashing in RSD is;
critical error febe 0047
Any thoughts? I'd like to try Gingerbread but haven't had any luck no matter what I try.
Click to expand...
Click to collapse
I don't particularly know how much of a difference this is, but the D2G and the D2 are two different phones, everything I have posted is for the OG D2. Might want to check the threads in the D2G forum because the files you need to SBF must differ in some way. I could be wrong...
that would explain it
idefiler6 said:
I don't particularly know how much of a difference this is, but the D2G and the D2 are two different phones, everything I have posted is for the OG D2. Might want to check the threads in the D2G forum because the files you need to SBF must differ in some way. I could be wrong...
Click to expand...
Click to collapse
That makes sense. Either way, I'm happy as can be and in love with my phone all over again. GB is fast and smooth on my D2G and after gaining root access again last night all my SU apps are back in working order.
Droid 2 updated
I had to revert back to stock 2.3.20 using the RSDLite flashing method, I let it do its thing, then performed a factory reset.
Powered the phone on, activated it, then just downloaded the OTA update over wi-fi to make it faster, installed like a charm, then ran the rooting utility.
Phone is rooted, deBloated, and rockin steady already.
Gotta say, I love my D2 again.
A955 & A957 Gingerbread sbf
On September 15th an official Gingerbread sbf was released from Motorola for the Droid 2 (not the Global). Here are the exact file names in case anyone has access:
A955:
1FF-p2a_droid2_r2d2_cdma_droid2_r2d2-user-2.3.3-4.5.1_57_DR2-32-110726-release-keyssigned-Verizon-US.sbf.gz
A957 (R2D2):
1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keyssigned-Verizon-US.sbf.gz

Categories

Resources