i recently got a dell streak 5. the device was used by the army but i want to restore it so i can use it for personal use.i woke up this morning and the dell streak turned on and was stuck on the dell logo boot screen. never left there. it has continued to do its boot loop. i tried to flash a new android 2.2 os; didnt work. tried to flash a new rom: didnt work. i also tried to root it using superoneclick, also didnt work. im out of ideas for doing a recovery for the device. i kinda figured the root process would fail due to the fact that superoneclick needs the phone to be on and open to work and authorize but i gave it a go. any more ideas would be appreciated. thanks in advance.
You're able to get into recovery, so the device isn't bricked. You should be able to install a stock recovery using fastboot or (better) Multiflasher. From there you should be able to install a stock ROM. After that, root but do not use SuperOneClick to do so. One click root tools can do more harm than good, so use the recommended methods in the XDA wiki.
Related
Galaxy S Vibrant had it rooted with 2.1 but now that i have updated to 2.2 wont work. Tried uninstalling Z4mod(RyanZa) installed Astro and reinstalled z4mod (had to use astro to install non store app) Z4mod installed and will open but it gets stuck each time i try to run the perm root. I'm a total noob only rooted originally with the help of my little brother. Problem is the phone is sooooo slow now i can hardly stand it. It needs to be faster liked it better before.
If there is no fix for this how to I go back to the 2.1 so i can re root.
Debugger is checked
error message i get says
"the appllication z4root ( process com.z4mod.z4root) has stopped unexpectedly"
Plug in your USB cable . If you read the debug option it says "Debug mode when USB is connected" . So plug in the USB then run z4root .
If you get stuck, Odin back to stock, then root> then flash any rom you want. In the future use Superoneclick to root, it has less problems.
oka1 said:
If you get stuck, Odin back to stock, then root> then flash any rom you want. In the future use Superoneclick to root, it has less problems.
Click to expand...
Click to collapse
Previously rooted with out using a computer, was hopping that I could do it the same way.
I have never used odin and i have never flashed my rom....just a noob with a phone that used to be faster...
Please elaborate on flashing a rom i want to learn more i have seen some stuff but really am just a bit scared to try it myself
should i uninstall z4root and try superoneclick instead... as of now phone is just stock with z4root installed but not working.
Try superoneclick
Sent from my SAMSUNG-SGH-I897 using XDA App
I used to have root on my optimus v. When I purchased my nexus s I decided to unroot it and try and sell it. I had a few problems unrooting due to superoneclick freezing but when I tried to get root permission in the terminal I was denied, so I figured I was unrooted. However I recently went to factory reset the phone, so it would be back to it's original state, to sell it. Well, now my phone doesn't load anything but the RA recovery I had installed when I rooted. So I tried to install the stock recovery and rom again, but it keeps giving me verification and script errors. I can't get to USB debugging mode to root it again, so I'm kind of stuck in a loop. Anyone have any advice? Very frustrating since I'm rely on this phone until my nexus s get's activated.
Well, after hours upon hours I finally got adb and fixed it. Now I'm off trying to figure out how to stop this from happening again.
Next time try disabling signature and script verification.
Sent from my LG-P509 (Optimus T) with Void Gear using XDA App
Ok here is my situation:
I was running Gingerblur 3.5, and decided I wanted to go to AlienROM. I unlocked the phone successfully using RSDLite and fastboot. I was still able to boot the phone after this process.
I attempted flashing Alien using the older CWM that wasn't designed for unlocked phones (didn't realize that there were different versions at the time) and the phone wouldn't boot. After research, I found that there was indeed a newer version of CWM that was necessary for flashing unlocked phones. I attempted flashing this using moto-fastboot, but got a stormgr partition: SOS error when trying to do so. After more research, I believe this is because I didn't delete the recovery_install.sh file before attempting to flash the new CWM. I attempted to go back to Gingerblur so I could remove the recovery_install.sh file using root explorer, but now Gingerblur won't boot either.
I sense that if I can get rid of the recovery_install.sh file somehow, I will be able to flash the newer CWM, and then be able to successfully install Alien.
My question is, how would I go about deleting this file if the phone won't boot? Is it possible to do this via the CLI on my computer? I don't have my *nix netbook with me at the moment, so I'm stuck using tools that are available only on Windows (I mean I could throw up a VM, but I'd rather not if I can avoid it).
Any help would be greatly appreciated.
Thanks!
So u can't get into fastboot or get it to give you the RSDLite prompt when u turn the phone on? Because if so, I know how I personally would fix it. I would use RSDLite to flash a stock version of gingerbread, then delete the file needed to install the new CWM.
Sent from my MB860 using XDA Premium App
Hey guys. been following xda since HTC eris. i moved a little to quickly this time and now im stuck...
i will start from the beginning.
I purchased my phone not too long ago (last week) and immediately looked up the gingerbreak. went through the motions and seemed to acquire root (superuser.apk). i then tried using titanium backup. "no root privileges). not thinking, i received a ota notification. i then did it.
in result, i lost root (if i even had it), I've tried slow88lx from rootzwiki rooting program for 2.3.3, and RSD gives me a failure result "failed flashing process. failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected" so i could sbf back to 2.2.2.
tried threads:[Q] Rooting Question, [Q] Dx2 Cant Root <similar problem, [SBF] Gingerbread SBF for MB870 Verizon Droid X2 [SBF], SBF TUTORIAL (Collection of instructions from various threads), Droid X2 OTA Gingerbread Root Guide <both one click and adb, UPDATED - [HOW-TO] SBF back to stock Froyo, Update to P3Droids Pre-Rooted GB Update, etc....
I am lost in limbo. phone works with all of its stock flaws. plz help.
Try redownloading all the files needed here again. Install and reboot both the phone and ur pc. If on Vista or Win7 right click RSD Lite and select "run as administrator" from the properties menu. If that still doesnt work report back with ur results please.
make sure you are using rsd 5.3. after you reinstall everything on your comp, connect the phone to a different usb port (sometimes that helps). make sure you put the phone in rsd mode. i would use the gingerbread sbf and the new one click root as well if i were you. and make sure you do a factory reset after you sbf.
Thx guys. RSD 5+ did the trick. Flashed to 2.3.3 and ota rooted.
Really appreciate the suggestions.
Sent from rooted X2 ^_^
Thanks for letting us know you got it working!
The one click that droid-life posted for motorola devices worked without a hitch. I tried gingerbreak and had no luck either.
x2 was running stock 2.3, now running eclipse. liking it.
Hopefully someone can help me. So I rooted my device using the Casual method. Tried many times. It still errored out but when I looked on my phone SU was installed. The root worked but when I tried to go into recovery, it took me to Android recovery not TWRP. So being ignorant, I decided to install TWRP through the Goo Manager and when I tried to go into recovery, I got the "system software not authorized by vzw" error. Could only get into download mode. Decided to flash back to stock using Odin. Process went fine but it basically put my phone back to where it was without root (same apps, settings, etc.). I guess it didn't do a complete flash? So I decided to run casual again to re root/unlock bootloader. Tried it multiple times on win7 64bit computer. Even tried it on a 32bit VM. Came up with this error. Someone please help!