im trying to search but cant find anything... i rooted my Dinc, clockwork installs fine...then i flashed Sky Raider 2.5.2 and its installed and working fine... i can install and use apps that require root, but if i boot into recovery, it goes back to the stock one, not clockwork.
why is it doing this?
anyone?
im following this guide EXACTLY.
http://forum.xda-developers.com/showthread.php?t=760306
nevermind, im stupid. disregaurd. lol
Related
First off, I am very familiar with Custom Roms and Never had this problem before.
I had to use the 2.3.13 SBF bc I was in a boot loop from a theme. I am rooted again using rageagainstthecage and can access the ClockworkMod recovery. I have tried multiple times to install 2.3.15 deodexed from the TBH app with no success. ClockworkMod says the install was successful but under system info it states it is 2.3.13. I know that it is 2.3.13 odexed bc Tranquility causes a boot loop. Backup and Restore work fine but not zip files. Does anyone know why it will not install?
I think I just experienced the same thing. Had to use the same sbf last night. This morning I tried to install zapx and seems like nothing happened and I was back at stock. Also I cant get back into clockwork recovery.
SysAdmNj said:
I think I just experienced the same thing. Had to use the same sbf last night. This morning I tried to install zapx and seems like nothing happened and I was back at stock. Also I cant get back into clockwork recovery.
Click to expand...
Click to collapse
You probably need to bootstrap the system again using the koush's app, to get back into recovery.
I installed ZapX but I had network issues with the market. So i reverted using a backup.
I was able to get clockwork back and install a different rom and the rom took this time. Rubix .5 to be exact.
good news- full 2.2 sbf is available now. there are links in x development.
thanks but i think they removed the thread ?
SysAdmNj said:
thanks but i think they removed the thread ?
Click to expand...
Click to collapse
Yeah- they did. there are other android forums with links still. Or search for...
VRZ_MB810_2.3.15_1FF_01.sbf
on megaupload or hot file or one of those sites.
I used ODIN to revert back to stock kernel, rooted my vibrant, then I installed rom manager from the market.
However, when I start rom manager and click "Flash ClockworkMod Recovery", nothing actually happens! I don't get prompted to select a phone model or anything. Upon rebooting into recovery, I don't even get to the clockwork mod recovery screen. What gives?
it's driving me nuts and i'm going to set dev's on fire, esp since i just downloaded nero. samsung doesn't seem to be supported with the new update as of the last 24 hours and now i need a new method for getting into clockwork without using terminal or adb of any of that stuff. im not a total noob, but trying to work with that is like trying to read spanish. no comprehendo'
the weird thing is that I was able to use rom manager in the past to go from samsung's stock firmware to Onyx, and again when I went to Nero Beta. I don't understand why it would stop working now.
http://forum.xda-developers.com/showthread.php?p=9869448#post9869448
BAM!!!!! clockwork backdoor confirmed.
installing nero as i type.
^ thanks for sharing the fix. Fyi though, koush has fixed the server issue. All is well.
I had the Liberty 1.5 ROM on my Droid Rooted with Rom Manager Clock Work recovery and everything was fine until..
I found a file on the web called Monster_D2_2.3.2_4.5.153 I used Clock Work recovery and installed it.
Now my phone says I have Android Version 2.3.3 Build Number STAB
Kernal Version: 2.6.32.9-gd72dc5da20523
It's running fine but I have lost ClockWork Recovery. I can not root the phone after trying several different methods. I can not install anything on it with its stock recovery without getting a signiture failure in the stock recovery and worst of all I can not uninstall it or overwrite it with anything I have loaded on the SD card.
I would be happy to remove this build and re-install Liberty.
I would be even more happy If I could just get this rooted and have my clockwork recovery back.
can anyone help me by pointing me to a thread or link that can help?
Thanks SO much
Gingerbread Dead :0
The problem is that there isn't a known process for rooting Gingerbread (except for installing a pre-rooted ROM)
SBF back to stock, and then you should be able to root, install clockworkmod, and then reinstall Liberty.
pcwebiz said:
I had the Liberty 1.5 ROM on my Droid Rooted with Rom Manager Clock Work recovery and everything was fine until..
I found a file on the web called Monster_D2_2.3.2_4.5.153 I used Clock Work recovery and installed it.
Now my phone says I have Android Version 2.3.3 Build Number STAB
Kernal Version: 2.6.32.9-gd72dc5da20523
It's running fine but I have lost ClockWork Recovery. I can not root the phone after trying several different methods. I can not install anything on it with its stock recovery without getting a signiture failure in the stock recovery and worst of all I can not uninstall it or overwrite it with anything I have loaded on the SD card.
I would be happy to remove this build and re-install Liberty.
I would be even more happy If I could just get this rooted and have my clockwork recovery back.
can anyone help me by pointing me to a thread or link that can help?
Thanks SO much
Gingerbread Dead :0
Click to expand...
Click to collapse
Yup, SBF is the way to go.
SBF Guide:
http://forum.xda-developers.com/showthread.php?t=770224 (be sure to use RSDlite 4.9)
SBF Download:
h t t p://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html
If you made a backup of liberty before you installed 2.3.3, after you root and put clockwork on, you should be able to just restore it.
It's always good to do as much research as you can before trying anything like that.
I installed VRZ_A955_2.3.20_1FF_01.sbf
Then I was able to root the phone and use my root applications. The device is very slow and too sketchy to complete anyone task so it was a failure.
Now with your advice I should get back on the right track. Thank You very much for the response. I thought for a moment I might have to drop my phone on the pavement and go to phoneclaim dot com. But you cant learn anything taking the easy way out. lol I'll post the outcome.
pcwebiz said:
I installed VRZ_A955_2.3.20_1FF_01.sbf
Then I was able to root the phone and use my root applications. The device is very slow and too sketchy to complete anyone task so it was a failure.
Now with your advice I should get back on the right track. Thank You very much for the response. I thought for a moment I might have to drop my phone on the pavement and go to phoneclaim dot com. But you cant learn anything taking the easy way out. lol I'll post the outcome.
Click to expand...
Click to collapse
Yup, as long as you can get the phone into bootloader mode, the phone isn't bricked.
Hope everything works out!
Sent from my Liberated DROID 2
I've had that performance problem after SBF'ing as well. I think I cleared data and rebooted a couple times to address the issue...
Complete Recovery!
Thank You SO much!
I began having a black screen.after a few weeks on gingerbread so I decided to sbf back to froyo but it failed now my phone gives the MOTO logo and goes directly to a black screen. I can't get it into flash mode even with holding the arrow up key. I'm out of ideas here so I'm really hoping to find a way to get this working again without being worried that its truly bricked. Any help would be greatly appreciative.
Have you been able to boot into anything else, such as the stock recovery?
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
I would recommend reading the Droid X wiki at the Cyanogenmod website. I had some of the same issues until I followed the downgrade + root method and then installed ROM Manager and CM7 manually through recovery. Good luck!
Sent from my DROIDX using XDA App
Schwazilla said:
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
Click to expand...
Click to collapse
Don't use ROM manager and don't use dxbootstrap (unless you have usb debugging unchecked). I use d2 bootstrap always. And you will have the occasion of it going in to cwm when you boot phone back up. I dealt with it for while. And cwm should be 2502 or something like that when you're just rooted 605. Did you make a nandroid of your rooted 605 before you tried to flash liberty
? Hopefully you did. Go back to that. Then use d2 bootstrap to get in to recovery, wipe data, cache and dalvik, then select install ip from sd card, then choose zip, then scroll via volume down to the liberty file, select that and flash.
I used directions posted over at Androidforums.com under the All Things Root forum for the Dx. I had a couple of hiccups, but it was user error. I now have Liberty 3 running smoothly on my Dx. Check it out, including the guide and ROM lists.
HTH
chaz_
Schwazilla said:
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
Click to expand...
Click to collapse
Just re-flash ur phone dude. do you know how to do that? It's a pain in the butt. but it is always failsafe.
hey all, I could use a little help on my phone. I tried to root it and I am stuck I have been using my old evo3d since it came out, and just picked up an HTC 10, so I am rusty on rooting and other things.
Anyway, I unlocked the bootloader on the HTC10 via htcdev,
installed twrp
flashed supersu (this where where the issue started)
so basically I thought I was rooted, did a root checker app and it said I wasn't.
I went to reflash supersu.zip and wiped everything again, but actually wiped EVERYTHING, no OS on my phone now.
Anyway, I am now asking for help. I am S-on right now, can get in to recovery, but just don't want to screw it up more. So could use a few tips. I am thinking about flashing the bad boy rom, but am wondering if I need to be s-off or anything like that? or can I just put the zip on my sd card and flash?
Thanks,
did you flash the modified su
https://tapatalk.com/shareLink?url=...perSU 2.74-2 With ForceEncrypt Set to Default
Sent from my 2PS64 using XDA-Developers mobile app
I did use that one when I did it. It didn't seem to work, (a couple apps said that there wasn't root) so in the process of trying again, I am pretty sure I wiped EVERYTHING on the phone. Literally no android on it at all I think. I can get in to htc download and in to twrp recovery, but nothing else. So at this point, I need to figure out how to flash either a custom rom, or a stock, or what ever just to get my phone back. Thanks for any help
I do know that it does require you to format data because of encryption.
Sent from my 2PS64 using XDA-Developers mobile app
tsbrewers said:
hey all, I could use a little help on my phone. I tried to root it and I am stuck I have been using my old evo3d since it came out, and just picked up an HTC 10, so I am rusty on rooting and other things.
Anyway, I unlocked the bootloader on the HTC10 via htcdev,
installed twrp
flashed supersu (this where where the issue started)
so basically I thought I was rooted, did a root checker app and it said I wasn't.
I went to reflash supersu.zip and wiped everything again, but actually wiped EVERYTHING, no OS on my phone now.
Anyway, I am now asking for help. I am S-on right now, can get in to recovery, but just don't want to screw it up more. So could use a few tips. I am thinking about flashing the bad boy rom, but am wondering if I need to be s-off or anything like that? or can I just put the zip on my sd card and flash?
Thanks,
Click to expand...
Click to collapse
Just put the ROM.zip on the sdcard and flash, ROM is already rooted, no S-off required
Thanks for the help, I think I got it figured out. Reinstalled supersu and then flashed the badboyz rom, seems to be working as we speak, so hopefully got it all worked out.
tsbrewers said:
Thanks for the help, I think I got it figured out. Reinstalled supersu and then flashed the badboyz rom, seems to be working as we speak, so hopefully got it all worked out.
Click to expand...
Click to collapse
Remember that pretty much all your custom ROMs come rooted. No need to root the stock ROM unless you plan to stay stock.
Way too many times I see people having trouble or run into problems trying to root, when all they want to do is install a custom ROM.