Droid X Provlems...? - Droid X General

Well this evening I got fed up with the stock ROM and decided since I am close to my upgrade date I'd take a swing at installing Cyanogen 7 for Droid X. I first made a backup of my original system and then installed CM7. The install went fine and the phone booted into CM7 for me. It was suggested that with Clockwork I could do an advanced restore and restore all the apps and settings that I had on my phone previously so at this point I decided to do that...and this is also where things went a little side ways.
I just selected data only restore but now when I attempt to boot up the phone starts to load CM7, but reboots after a few seconds of loading. I have booted into the Motorola recovery manager and attempted to apply the update.zip (CM7 install file) on my SDCARD using this method, but it fails due to a signature error. At this point I am not sure what else I can do to get this problem worked. Any suggestions are welcome.
Thanks,
whit3fir3
---------- Post added at 01:30 AM ---------- Previous post was at 01:14 AM ----------
Well a little more effort and about 6 beers later I got the problem worked out...
Thanks,
whit3fir3

You should not restore data on cm7. You need to get into recovery and wipe data.

Related

Unable to Boot into recovery.

Rooted the Vrz Gtab using Z4root. installs a few aps, added Rom Manager.
Wanted to create a backup boot into recovery and bout 20% stops and reboots.
what ever I do from this point it not save and when I reboot it bring me back to the previous point. I customized the tab everything is working fine, but if Power off it goes back to the previous point.
the right thing to do it to flash back to back?
Any Ideas?
thanks
68 views and not replies..
Anybody?

[Q] [+Problem] Can't boot into CWM Recovery

Hi,
I really love my Nook Color (firmware 1.2/blue dot on package) which I picked up two days ago. I Installed CM7 on the microSD card right away and it's running fine overall. -- However, I cannot boot into recovery. - DANG!!!#[email protected]#
I have looked allover this forum and beyond, but none of the other threads deal with my NC's CWM problem - or offer a working solution I could understand/use...
The ingredients I took to cook up my CM7 install:
1.) "generic-sdcard-v1.3.img" ('extracted' to SD using Win32DiskMgr)
2.) "update-cm-7.0.3-encore-signed"
3.) "gapps-gb-20110613-signed"
Everything installed OK, including CWM 3.0.2.8., which is showing as app.
BUT... no matter how [often] I try to boot into CWM Recovery, it always boots straight into CM7.
(And, yes... I've tried all the "N" + "Power" button press combinations, I think... but none of them worked).
MY QUESTIONS:
- Any idea what I did wrong? Why can't I boot into recovery?
- How can I fix this without having to use ADB? (Note: Yes, I am willing to learn, but command-line programming is not exactly my idea of fun). I was hoping there actually is a simple fix to this problem... something like "place this [...] on your SD card and boot", or so???
...Thanks for your help & suggestions.
Have you tried holding down the power from cm7 and selecting reboot into recovery?
Sent from my LG Optimus V using Tapatalk
I think i know your problem. The 1.3 installer image is not fully compatible with CM7.0.3. You might be able to update to the RC or a nightly and get it to work. Otherwise you are going to have to remake the SD card.
Sent from my LG Optimus V using Tapatalk
koopakid08 said:
I think i know your problem. The 1.3 installer image is not fully compatible with CM7.0.3. You might be able to update to the RC or a nightly and get it to work. Otherwise you are going to have to remake the SD card.
Click to expand...
Click to collapse
Thanks for your help, koopakid08! After flashing CM7 three more times in the meantime, I had that hunch, too...
Can you tell me what to use if one of my "components" is no good(?)??
I want to run CM7 off my microSD (not the eMMS install). -- So.. what do you recommend me to do, as I'm afraid I don't quite understand what you mean with "update to RC or nightly"...
Is my issue related to the CM7 version, or is it the "generic-sdcard-v1.3" image?? If it's the CM build (7.0.3), there is no RC available for the "encore" yet; just a nightly (#177) dated 8/31/2011.
If the problem is the sdcard 1.3 image, what else is there I can use to run CM7 off my microSD?
-- Thanks!
---------- Post added at 11:48 PM ---------- Previous post was at 11:34 PM ----------
Interesting... just found another guide on the web. Didn't see that all weekend .. :-(
http://androidforums.com/nookcolor-all-things-root/352736-how-install-cm7-your-nook-color.html
I'll try this one, hope it's finally working also for me...
---------- Post added 19th September 2011 at 12:31 AM ---------- Previous post was 18th September 2011 at 11:48 PM ----------
I can't believe it was THAT easy... [email protected]@##%$&$%@%*(!%%^& !!!!!!
It was indeed either the sdcard image, or CM7.0.3. Which one, I really don't care anymore, as I just flashed the latest CM nightly (#177) ... and CWM Recovery ...WORKS [:gasp:] !!!
It's a bit late now here in Chicagoland, so I better hit the pillow (it's a school night ..ha ha... tomorrow].
I will post instructions later; just in case someone else runs into the same issue.
Thanks, again, koopakid08, for getting me on the right track.
Good Night!!
Just in case you want to know what the problem was. It was the CM version you were using. The 1.3 image only works with cm7.1 versions. Glad you got it figured out.
Sent from my NookColor using Tapatalk
Just an additional observation... You are using an old version of CWR. The newest is 3.2.0.1.
I don't know if you got everything sort out but, bear in mind: booting off uSD has NOTHING to do with CwM R., whatever version.
Moreover, you boot into "recovery", not boot into "clockworkmod recovery"
If you intend to run off uSD, you can completely ignore anything about ROM Manager or CwM Recovery since those are not go together and it causes more headache than help.

Lost Boot/Recovery Img

Strange happenings going on with my Nexus S.
It has been rooted for a while and have been running Genexus S 2.0 ROM which was fine to start with but I have recently been getting lag issues with the screen, issues with character selection on the keyboard etc.
However, I have had a few crashes when the phone has been charging and the phone is being not just hot, I'm talking boiling to the touch!
I have rebooted into recovery but....recovery img and boot img have disappeared. They have been present in recent weeks but for some reason they have disappeared.
I have reinstalled clockworkrecovery via ROM Manager a couple of times but there is still no change. TBH I'm sick of the issues I've had with the phone since rooted and it's not for me so plan on going back to stock whenever I can, however, I need recovery!
Can anyone point me in the right direction to sort this out and if possible not by plugging my phone into a PC. I am away with work and don't have my own computer for a while.
Thanks
you can always flash the boot recovery back into the phone, just follow any of the how to root guides
meso100 said:
Strange happenings going on with my Nexus S.
It has been rooted for a while and have been running Genexus S 2.0 ROM which was fine to start with but I have recently been getting lag issues with the screen, issues with character selection on the keyboard etc.
However, I have had a few crashes when the phone has been charging and the phone is being not just hot, I'm talking boiling to the touch!
I have rebooted into recovery but....recovery img and boot img have disappeared. They have been present in recent weeks but for some reason they have disappeared.
I have reinstalled clockworkrecovery via ROM Manager a couple of times but there is still no change. TBH I'm sick of the issues I've had with the phone since rooted and it's not for me so plan on going back to stock whenever I can, however, I need recovery!
Can anyone point me in the right direction to sort this out and if possible not by plugging my phone into a PC. I am away with work and don't have my own computer for a while.
Thanks
Click to expand...
Click to collapse
its because you installed your recovery via rom manager. you want to reflash your clockwork recovery through fastboot so that it will stay permanently. look in the development section for instructions.
---------- Post added at 05:30 PM ---------- Previous post was at 05:29 PM ----------
AllGamer said:
you can always flash the boot recovery back into the phone, just follow any of the how to root guides
Click to expand...
Click to collapse
i got to say that youre the only xda mod, that i know of, that also helps out people with issues and not just xda/site stuff. thank you!
Thanks for your help guys.
I flashed the cwm recovery via fastboot and loaded up cm7 but each new ROM I used (that had been there previously) didn't boot into a fresh version, it had elements of the previous versions I had run such as MIUI (the clock), the Genexus S 2.0 drag and drop lock and wallpaper and some elements from The Infinity ROM. Very strange.
Prior to the latest mix up the phone had become very unstable, especially the touch screen and I am not exaggerating when I say the phone just wasn't usable. I even considered getting a BlackBerry Torch 9810!!! I mean wtf?!
Anyway, I have reflashed a stock nandroid backup via CMW and relocked the bootloader. I had a few permission errors but when I rebooted that seemed to go away. I'm now quite happy I'm back to standard because of the reliability issues I experienced.
When I reboot to recovery it comes up with a White box with an arrow coming out with the android at the side of it. Is this normal or should there be a standard recovery img? However, I have noticed if I press the volume up and power again it goes to a purple recovery screen with wipe cache partition, factory reset etc.
Also, all my ROMS and Titanium Backup files are still viewable from recovery, is that usual? Would I be ok to mount as USB and delete those individual files?
Thanks
When you switch roms you MUST wipe data factory reset, wipe cache, wipe dalvic cache. Then flash the new rom.
Sent from my Nexus S 4G using xda premium

[Q] Samsung Galaxy Spica stuck in bootscreen after update

Hello everyone,
Today I bought an used Samsung Galaxy Spica from a friend as a backup phone for my HTC One X. It had Android 1.5 installed so i tried to update it to Android 2.1. I tried to update it with KIES or PC Studio, but it both failed. I still dont know why.
So I searched on the web and found out that you could update it with ODIN.
So I used this tutorial with the included files. http://www.greaky.com/2010/02/samsu...02/samsung-i5700-galaxy-spica-android-21.html
But when it reboots I get a image of a phone with a exclamation. I also tried the Flash 1, Flash 2 and Flash 3 method, but in the end when it reboots it gets stuck at the samsung screen with a filled bar.
What am I doing wrong guys?
Suckup SpiceGenMod RC1
Have you been here yet?
Search on google for suckup.de and samdroid and you'll get there.
Tends to be the most stable ROM and also the best guide on how to get a good stock version in plus then root and install the ROM itself.
Otherwise the forum for Spica is over at samdroid.net
---------- Post added at 05:09 PM ---------- Previous post was at 04:53 PM ----------
btw, if you still get stuck at the bar after resetting then let me know.
It could be extra kernel files or similar causing the boot problem or any manner of things but if you can get to recovery then try doing a wipe of everything from the main menu plus the advanced menu... Otherwise reset back to stock via Odin, but make sure you use the right one for your region, then root, then install a ROM.
And don't forget to sipe caches and dalvik AFTER installing the ROM!
Iniesta89 said:
But when it reboots I get a image of a phone with a exclamation. I also tried the Flash 1, Flash 2 and Flash 3 method, but in the end when it reboots it gets stuck at the samsung screen with a filled bar.
Click to expand...
Click to collapse
we got the same problem....
can anyone help us?
That normally means the kernel can't boot the OS.
I normally go into recovery, advanced then wipe dalvik-cache and battery stats then back to main menu and wipe cache then reboot again.
---------- Post added at 11:57 AM ---------- Previous post was at 11:48 AM ----------
Or, phone with exclamation is normally download mode. Have you tried using Odin with the spica settings file to re-flash a stock firmware to reset? Then root it agian and ROM it after that? ie start from scratch with 2.1/2.2 and ditch 1.5 all together?

[Solved] Used flashify to restore stock kernel, phone won't boot can't access DL-Mode

Hi,
I had Stock LG G2 Firmware, installed root, twrp and used the phone for months.
A few days ago I installed a custom kernel, and I used Flashify to flash the new kernel, and saw Flashify has an option to backup the current Kernel.
I used it, and indeed today I decided to go back to the stock kernel because the new kernel was not charging properly. (Slow)
Now, After flashing the stock kernel with Flashify, the phone won't boot, won't go into download mode, won't go into recovery (TWRP)
And I get an error message :
Secure boot error / Boot certification verify
Now, when I connect the phone via usb to my windows 7, it doesn't recognize it even though I have the drivers.
Instead I get lots of small mass storage drives which windows wants to format (no thanks)
And in ubuntu I get lots of popups for unmountable partitions. Dbus-daemon and compiz go crazy at 50% cpu each and I can't do anything because the computer locks up from heat and resource exhustion.
HELP please.
I'm fine with bash and linux, but I need someone to help me get a bit further from this point.
Cheers,
Eitam.
What is your model number
Sent from my LG-VS980 using Tapatalk
D802 from Taiwan, sorry for not specifying this earlier.
So, I kept at it, apparently i'm an idiot.
Instead of using dconf-editor to disable automount, I tried using gconf-editor (Doh!!!!!)
Eventually was able to use Ubuntu LiveCD to flash according to this thread :
http://forum.xda-developers.com/showthread.php?t=2582142
Even after flashing, same problem with secure boot error etc.
I then tried to factory reset, and got TWRP!
I have a TWRP backup from a few days ago. Restoring now.
Damn it takes lots of time.
Everything is back and working.
---------- Post added at 11:25 PM ---------- Previous post was at 10:26 PM ----------
[/COLOR]
eitama said:
Everything is back and working.
Click to expand...
Click to collapse
i have the same think. i dont have unlimited internet connection right now. so i cant repair my phone. can i ask you one question. if i have a backup of the stock rom can ı restore it after ı get in twrp. and did you use the exect same method? or did you send different files to the phone? thnask a lot.
ps: i had cm11-m8 isntalled.
I used that method, and I was on stock and restored stock.
I think I used the files in the thread, but It was a long time ago so I don't remember.
Sorry for you that you have to deal with this - but atleast you know you can get out of it! Also, once you have twrp running, I think you can use some method to flash stock rom even without the backup.

Categories

Resources