Can I flash the original stock recovery and KEEP all of my already flashed roms? Isnt ClockWork just used to flash new roms? I don't necessarily still need it do I?
I'm not sure it will affect but you also have to consider that you won't be able to update your rom
Also....why would you want to do that?
Consider using the new cwm3 available from the ROM Manager app in the market. It's the newest and is an official release. Works flawlessly.
Did it! Everything works, yay.
Wanted to because I like turning my phone off when I hit the sack in order to charge it. However Clockwork turns on when charging and the phone is off. I know I could just charge it and leave it on, but not my style.
Also I can always put Clockwork back on now that I know I can take it off.
Related
I have flashed the new CyanogenMod and the Cyanogen Recovery 1.4 and when I wipe everything and flash, it'll load up and I can use the phone 100% perfectly, but once I reboot my phone, or turn it off and on, it never goes past the green boot screen. Anyone have any solutions/reasons why it does that? It's with every single Cyanogen mod too, i've tried several of them.
Probably because you have a lot of apps?
If not, reflash it.
tmc_adio07 said:
I have flashed the new CyanogenMod and the Cyanogen Recovery 1.4 and when I wipe everything and flash, it'll load up and I can use the phone 100% perfectly, but once I reboot my phone, or turn it off and on, it never goes past the green boot screen. Anyone have any solutions/reasons why it does that? It's with every single Cyanogen mod too, i've tried several of them.
Click to expand...
Click to collapse
what do you actually flash and what is the actual process, you shouldnt have any issues after it boots up the first time, wipe everything and make an exterior partition meaning get rid of your cyanogen recovery 1.4 and get amon ra's latest... look in the dev section and read up on cyan's page on how to flash the rom
mt3g said:
what do you actually flash and what is the actual process, you shouldnt have any issues after it boots up the first time, wipe everything and make an exterior partition meaning get rid of your cyanogen recovery 1.4 and get amon ra's latest... look in the dev section and read up on cyan's page on how to flash the rom
Click to expand...
Click to collapse
Thanks for help man, right now I'm running dwang's rom 100% perfect w/ no issues at all. it can reboot and everything just fine. I'm just a little worried on going back and trying to flash cyanogens.
When I installed it, I first did the root process, downloading the .apk file and going through all that part smooth, then I downloaded and flashed the Cyanogen Recovery 1.4, and from there I downloaded the two files (DRC83_base and the latest cyan's rom, i forgot the version #) and applied update from SD, first doing DRC83 and right after doing the rom itself, without rebooting the phone. It loads up A-OK and I can installl the apps and go about my business, but once I need to restart my phone, it just never turns back on. I'm puzzled completely...I even did the whole unroot and reroot thing and STILL i'm not having any luck.
K I got confused in there some where did you flash a cyan rom at all in there I read that you flashed the drc83 zip file but sounds like you just flashed that and booted the phone lol... never tried that but.... any way it seems like you are doing everything correct onlything I could suggest is make sure you have the correct htc base image, and make sure you wipe and repair everything!!!!! and also try a differant download of cyanogen as you might have gotten a bad one or something I have never had any issues with a cyanogen rom except maybe a FC back on 4.0xx or something
兄弟，估计你刷成砖了。同情ing。。
Everytime i tell it too boot into recovery it just shows the little android guy with a triangle and exclamation and then reboots. I've installed bootstrap and run clockwork recovery. What am i doing wrong? last time i did this and was able to manually go into recovery but when i flashed a rom i just got stuck at motorola bootscreen and had to use sbf. Please enlighten me someone.
Ok.. i tried skipping clockwork and just booted into recovery through bootstrap.. Works. I try and flash a rom and the orange bar comes up and says it's installing. The bar never fully goes across but it says the installation is complete. When i try and reboot to try the rom i get stuck at the boot screen. Any ideas what is going on?
boredmug said:
Ok.. i tried skipping clockwork and just booted into recovery through bootstrap.. Works. I try and flash a rom and the orange bar comes up and says it's installing. The bar never fully goes across but it says the installation is complete. When i try and reboot to try the rom i get stuck at the boot screen. Any ideas what is going on?
Click to expand...
Click to collapse
are you using 2.2? what ROM? you need to run the bootstrap once for it to work, and it will say clockworkmod installed is version 2.5.0.7 in ROMManager thats the bootstrapped version of clockwork mod.
then download the ROM, and don't touch anything after you hit the ok button on the screen that asks to backup current ROM and wipe user data. just let it work.
The system info says 2.1update1. I did as you described. I just used bootstrap to boot to recovery and tried flashing a rom and it does the same thing. Just sits at the motorola bootscreen. I'm gunna try my nandroid recovery to go back to the rooted stock rom.. I really don't know what to do from here though because neither way is working for me.
Also, my clockworkMod Recovery is v2.5.0.6 not .7. Maybe this is the issue? when i used rom recovery it said i had the most recent version. I'm Nandroiding right now which seems to be working.
boredmug said:
The system info says 2.1update1. I did as you described. I just used bootstrap to boot to recovery and tried flashing a rom and it does the same thing. Just sits at the motorola bootscreen. I'm gunna try my nandroid recovery to go back to the rooted stock rom.. I really don't know what to do from here though because neither way is working for me.
Also, my clockworkMod Recovery is v2.5.0.6 not .7. Maybe this is the issue? when i used rom recovery it said i had the most recent version. I'm Nandroiding right now which seems to be working.
Click to expand...
Click to collapse
you should update to version 2.2
check http://rootzwiki.com/ it has the files you'll need
ok. Thanks. Maybe this is the problem? I'm trying to flash a 2.2 rom and currently have 2.1 on my phone? So i've already done sbf back to 2.1 once last night. I'm assuming this procedure is pretty much the same. I'm guessing i will have to reroot my phone. Can i use the same method as 2.1 or is there another method for the droid x with 2.2? Thanks for the help!
boredmug said:
ok. Thanks. Maybe this is the problem? I'm trying to flash a 2.2 rom and currently have 2.1 on my phone? So i've already done sbf back to 2.1 once last night. I'm assuming this procedure is pretty much the same. I'm guessing i will have to reroot my phone. Can i use the same method as 2.1 or is there another method for the droid x with 2.2? Thanks for the help!
Click to expand...
Click to collapse
just check the website i posted, it has guides for everything you need
well.. Now i have 2.2 on my phone but no root. adb can't find my phone.. WTF
Thanks for pointing me in the right direction. Was finally able to get it all working. Now I have a working 2.2 custom Rom and can proceed with flashing this thing to cricket. Kinda sucks because I'm doing all this for a friend and using this phone I've kinda come to the conclusion that its a better made phone than my evo. Colors look better on the lcd, camera takes better pictures and the aluminum case is certainly nice too. Only drawback I see is the dev. Much more development for the evo, but then again it is an older phone.
boredmug said:
Thanks for pointing me in the right direction. Was finally able to get it all working. Now I have a working 2.2 custom Rom and can proceed with flashing this thing to cricket. Kinda sucks because I'm doing all this for a friend and using this phone I've kinda come to the conclusion that its a better made phone than my evo. Colors look better on the lcd, camera takes better pictures and the aluminum case is certainly nice too. Only drawback I see is the dev. Much more development for the evo, but then again it is an older phone.
Click to expand...
Click to collapse
I like my DX and it does have a few advantages over the EVO (e.g. battery life and build quality). However, I would gladly trade it for an EVO, since that device has 4G access, a front camera, cyanogenmod support, more accessible bootloader, etc.
I just had my phone rooted on tuesday by a friend. It started turning itself off for the first few hours and went back to normal for a day. Last night it started turning itself on and off every minute. I know nothing about phones, can anyone help me?
How did your friend root?
Did they delete system apps?
Did they apply lag fixes?
Perhaps just flash a custom rom. Their better than stock and should fix your issue. I hope they didn't do a lag fix. Disable it if they did.
He did something like holding the power button/volume up/down to get into download mode? That's all i know. He said he didn't remove any of the system apps, or change anything. He added a wifi-tethering for me, that's why he rooted it. I know nothing about phones and computers. I'm out of town for another week so i can't have him fix it, but i need to do something so i can use my phone. Any suggestions?
oh ya, he used ODIN if i remember right
I don't know why he would be using Odin if all he was doing was rooting the phone. Can you get to the web to DL anything? I would try flashing something with clockwork till you can re-flash to stock with Odin. You need to find out what exactly your friend did when he worked on your phone.
Can you adb? I would like to see the log.
Sent from my Bionixed SGH-T959 using XDA App
my phone wont stay on long enough to do anything. When i push the power/up/down buttons at the same time i get a picture of a droid and it says power reset or unknown upload mode
whats adb? I'm a preschooler when it comes to anything computer/phone related
I was getting panic mode/upload when I was messing with eugenes kernals.
intruda119 said:
I was getting panic mode/upload when I was messing with eugenes kernals.
Click to expand...
Click to collapse
As was I, and that's the only time I've seen that screen.
OP, you're friend definitely did more than simply root your phone. Especially if you say he used Odin? There's no reason to use Odin to gain root.
I would recommend you Odin back to stock and start fresh.
is there any way i can do it without Odin? I'm out of town for a week and need my phone
Rom manager / clockworkmod. Just go to the app store (it's free) and download it. Flash the recovery and flash back to stock 2.1 eclair. It should fix it then when you get home just use the one click root method to root your phone. Check the vibrant bible in android dev. to do it, it's really easy to do yourself since it is literally, one click ^_^ Also for the rom of 2.1 I also recommend going to the vibrant bible for that as well. All you have to do is dl rom manager, put the 2.1 rom on the root of your sd (not external sd) then go into rom manager and install custom rom (pick the stock 2.1). It will wipe your data but your phone should be fixed and you can always dl back your apps and import contacts through your gmail account. Hope this helps.
http://forum.xda-developers.com/showthread.php?t=740077
that's eugene's stock 2.1 for vibrant flashable through clockworkmod ^_^
Just tried to flash a rom and the phone rebooted and when it came back I have no market at all. I press on the market icon and I get a note saying to send a message and report it. I am freaking out.
Vinny
Did you flash a gapps (Google apps) package?
Sent from my Nexus One using XDA App
Yeah, you need to flash a Google Apps zip. Roms don't come with them, or well, some do, but technically that isn't legal and Google doesn't like it.
did you do a nandroid?
And here, not sure how these work on a non cm7 rom, but you can give it a go.
http://goo-inside.me/google-apps/
The universal dpi for cm7 might work. You would probably need to wipe your phone
cm6 hdpi might be your best bet
I did a back up and my rom never flashed due to the new recovery I used on rom manager. My original rom (stock with root obviously) came back with al my google apps but the market. I DL the market thru my browser but my phone will not allow the download. Tried going into recovery but the new recovery I dl thru rom manager will not allow me to use my back up or the other roms I have on my sd card. When I go into recovery I get the triangle and the little guy, I hit the power button and volume up and go into this weird looking recovery that doesn't allow what I need.
Help me I'm screwed I think. I think the new recovery I dl screwed me all up.
Vinny
Put the old recovery on it then, and restore your nandroid.
If you ended up with stock, you may have lost your root. So root again and install the recovery that you made the nandroid with.
vinnyjr said:
I did a back up and my rom never flashed due to the new recovery I used on rom manager. My original rom (stock with root obviously) came back with al my google apps but the market. I DL the market thru my browser but my phone will not allow the download. Tried going into recovery but the new recovery I dl thru rom manager will not allow me to use my back up or the other roms I have on my sd card. When I go into recovery I get the triangle and the little guy, I hit the power button and volume up and go into this weird looking recovery that doesn't allow what I need.
Help me I'm screwed I think. I think the new recovery I dl screwed me all up.
Vinny
Click to expand...
Click to collapse
I'm a bit confused.
It looks like you're using the stock recovery. Somehow you corrupted flashing a recovery.
You're far from screwed. If you can flash clockwork 3.0 from ROM manager. If that doesn't work, try this.
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I would advise using clockwork, as it has tight integration with ROM manager. Here's the download for that.
http://mirror1.kanged.net/recoveries/recovery-clockwork-2.5.1.4-passion.img
IF you lost root, you're going to have to go through a lengthy process. Let me know if you need help.
running stock rom on stock rom slot everything works fine, when i install a custom rom to rom slot 1 and boot to custom rom the rom works and does everything it should but i am not able to reboot or power off my phone. it does this if i am on custom rom or stock rom. when rebooting or powering off it gets stuck right after logo of rom goes away and stays there with led light, back arrow and open apps keys lit up. i have to remove battery and boot that way. after i wipe/ delete custom rom from rom slot 1 and everything works fine ??????
Dpike698 said:
running stock rom on stock rom slot everything works fine, when i install a custom rom to rom slot 1 and boot to custom rom the rom works and does everything it should but i am not able to reboot or power off my phone. it does this if i am on custom rom or stock rom. when rebooting or powering off it gets stuck right after logo of rom goes away and stays there with led light, back arrow and open apps keys lit up. i have to remove battery and boot that way. after i wipe/ delete custom rom from rom slot 1 and everything works fine ??????
Click to expand...
Click to collapse
If you would have read numerous threads on the issue you would have known. Instead you found out the same way I did some weeks ago!! There are known bug issues with Safestrap that cause the problems you are experiencing when using a rom slot. Use the stock slot only and all will work well. Yes, this means you have to wipe out your stock S5 system, but you can always odin back to stock.
Chopstix9 said:
If you would have read numerous threads on the issue you would have known. Instead you found out the same way I did some weeks ago!! There are known bug issues with Safestrap that cause the problems you are experiencing when using a rom slot. Use the stock slot only and all will work well. Yes, this means you have to wipe out your stock S5 system, but you can always odin back to stock.
Click to expand...
Click to collapse
With our build you pretty much have to treat safestrap like any other custom recovery. Most other recoveries that I'm aware of don't have various slots for you to dual boot stock and custom roms. Making a backup within safestrap is definitely recommended before you wipe the stock rom slot that way if you want to go back, you won't need to recover with odin. Not saying that's a bad way to go, just a little inconvenient.
Sad to say the developer of our recovery if off doing other things. I don't know if this rom slot one issue is something that can be patched within the recovery, or it's it's more of a ROM developer kind of thing, but I don't see that getting fixed any time soon.
DJNads said:
With our build you pretty much have to treat safestrap like any other custom recovery. Most other recoveries that I'm aware of don't have various slots for you to dual boot stock and custom roms. Making a backup within safestrap is definitely recommended before you wipe the stock rom slot that way if you want to go back, you won't need to recover with odin. Not saying that's a bad way to go, just a little inconvenient.
Sad to say the developer of our recovery if off doing other things. I don't know if this rom slot one issue is something that can be patched within the recovery, or it's it's more of a ROM developer kind of thing, but I don't see that getting fixed any time soon.
Click to expand...
Click to collapse
No it won't... Hash said in the safestrap thread that he was shutting down deveopment work on it... the only hope would be that another dev dives in to it.
Chopstix9 said:
No it won't... Hash said in the safestrap thread that he was shutting down deveopment work on it... the only hope would be that another dev dives in to it.
Click to expand...
Click to collapse
Considering it's open source, I'm hoping it won't be too long before another developer picks it up. (PlayfulGod maybe? )