I am rooted & on latest radio(901). i installed safestap & loaded recovery from there. i booted into the recovery menu with the 'menu' button & went to 'safe mode' to allow installation of a rom .zip
anyway, it installed & i rebooted the phone, but now it's back to a stock rom(yet still rooted & still on 901).
what's going on here?
Maybe your install file was the .901 update??
Related
I can't seem to get a ROM to install on my motodroid - I have the latest ROM Manager and the ClockworkMod recovery app flashed but every time I try to install a ROM (either downloaded w/ ROM Manager or via a file saved to the SD vai the USB cable) I get the attached alert display. Alt+Ctrl+Del reboots me back to the starting point...
What's wrong?
Tom
Having the same problem!
Having the same problem and getting the same screen after reboot.
i dnt think rom manager works on milestone/droid .. AOR is recommended ..
rrohanjs said:
i dnt think rom manager works on milestone/droid .. AOR is recommended ..
Click to expand...
Click to collapse
ROM Manager works on Droid, but not on Milestone.
?
I have a Droid, i am still having the same problem with rom manager. I used superoneclick to root, I have the latest busybox update, and superuser.
ashersgate said:
I have a Droid, i am still having the same problem with rom manager. I used superoneclick to root, I have the latest busybox update, and superuser.
Click to expand...
Click to collapse
I don't know if this works like it does on Milestone, but have you tried holding the camera button+volume up?
Try 4.....
Tried holding those no good. would like to get gingerbread on it soon. thks for the help so far.
Think I did push those button soon enough. 5th try it is installing.
ashersgate said:
Think I did push those button soon enough. 5th try it is installing.
Click to expand...
Click to collapse
So that key combo worked?
well.......
It brick the phone but i was able to recover from it. How can I get the apps on my sd card back on my phone.
seems like holding 'x' work to get me back from brick
I was able too restore back to the rpm i was using before i started with a backup in rom manager......awsome so now i can play without worry,,,,,, thanks so much!!!!!!
More on the problem
So, I consistently get the screen in the original post if I try to select the option presented after the download is complete to automatically boot to recovery and install the ROM - but if I install from a .zip while already in ClockworkMod, I am successful in installing a ROM. The problem seems to come with doing an over-the-air download in ROM Manager then attempting to transition to ClockworkMod to do the install. Alt-Ctrl-Del while on the screen displayed in the original post reboots and gets me back to my existing ROM...
It seems like something is not working as it should be, but it seems I have a way to make things work...
Tom
"Reboot into Recovery" also fails
I just tried to "Reboot into Recovery" from ROM Manager and that also failed (gave me the dead screen shown on the original post)...
Booting while holding x gets me into ClockworkMod successfully. I currently have ClockworkMod version 3.1.0.2 installed (it has given me the most success so far).
Any suggestions?
Tom
It seems I was wrong - I'm not currently able to boot into recovery using the x button during boot...
Tom
Getting better
I flashed back to the "current" ClockworkMod - 2.5.0.1 - and now I can "Reboot into Recovery"...
Maybe not better...
Errr My device seems flaky - I tried to install a ROM and the transition to ClockworkMod did not work again... Isn't this supposed to "Just work"?
More success yesterday
Once I got Pete's Gingerbread ROM loaded/installed (via .zip file) my problems getting to ClockworkMod and trying new ROMs seem to have cleaned up.
After performing the "e-mail connect" (to do that I had to turn off Droidwall) I was successful in downloading directly to the phone and flashing a new ROM.
Good luck all...
Tom
Hi,
I'm having a major issue with not being able to flash roms using clockworkmod for some strange reason.
I decided to move from MIUI rom because every time I gave it a chance when new versions came out, it constantly let me down with countless bugs and such. So, I've decided to go back to modified stock ROMs as they seem more reliable.
When I attempted to flash using clockworkmod (that comes with MIUI) it failed to apply the new (non-MIUI) ROM and forced it to go into a bootloop which knackered up going into recovery, so my only other option was to go into download mode and flash a stock ROM (I chose the latest, I9000XXJW4), root it, flash cyanogenmod and try again.
But unfortunately this did not work and now I'm stuck on the stock ROM.
I've taken a video of the exact moment it all goes wrong. Also, below is each step taken of the process.
youtube.com/watch?v=EmZAZ3DeL2U
1) Download Samsung Value Pack (I9000XXJW4) and CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
2) Galaxy S rebooted to download mode
3) Used Odin3 1.85 to apply JW4_JW4_JW4.TAR file to the PDA section. Re-Partition is not checked.
4) Allowed the device to reboot to the home screen.
5) Powered off the device and booted back to download mode
6) Used Odin3 1.85 to apply CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.TAR to the PDA section. Re-Partition is not checked.
7) Allowed the device to reboot to the home screen (The video begins now).
8) Launched the CWM application (with root permissions) and rebooted to Recovery.
9) Wipe data/factory reset selected and confirmed
10) Wipe Dalvik Cache selected and confirmed
11) Format /system selected and confirmed
12) Install zip from SD Card, Choose Zip from sdcard and update-cm-7.1.0-GalaxyS-signed.zip selected and confirmed.
13) Here is an extract from the log that follows before rebooting:
- Finding update package...
- Opening update package...
- Installing update...
- Checking state of BML/MTD...
14) Self-Rebooted
15) Boot-loop
Any help is greatly appreciated!
Thanks,
Andy
when it bootloops it does it cause it just flashed the kernel and its trying to run the stock rom on the cynogen kernel. so pull the battery, put it back in. reboot into recovery and flash the rom again. it should work the second time cause its using the cynogen mods version of cwm recovery. let it boot it will take a while. but that should work.
dont forget to hit thanks!
taz0697 said:
when it bootloops it does it cause it just flashed the kernel and its trying to run the stock rom on the cynogen kernel. so pull the battery, put it back in. reboot into recovery and flash the rom again. it should work the second time cause its using the cynogen mods version of cwm recovery. let it boot it will take a while. but that should work.
dont forget to hit thanks!
Click to expand...
Click to collapse
Genius!
Thank You!
Cannot believe the solution was staring at me the entire time!!
Hi!! I'm new at the forum, I've looking for information and didn't find anything related. I hope this is the
apropiate section
I've a Galaxy Ace with Froyo, so I rooted it with SuperOneClick without any problems. Then I reeboted in stock
recovery and installed a .zip for ClockWorkMod recovery. Afterwards I couldn't boot into any recovery, but the
pone still worked. So I installed Titanium, made a backup, etcetera; everything worked perfectly. I've tried
to reboot into recovery with an app called CWM (same icon as ROM manager). Just opened it and press "Reboot into
recovery". Now the phone is not working. I can enter download mode (yellow letters saynd "Downloading...") but
Odin stucks in Setting Connection (same simpthoms of ROM manager). I hope you have a solution.
Thanks!!
I have a friend with a S5830 (not S5830i, not S5830g; plain S5830). She would like ICS/CM9 installed on it.
The phone does NOT have the latest official update. Its stock recovery doesn't have a "apply update from SDCARD" option; rather, it has "apply sdcard/update.zip", which means I have to rename files I want to flash as update.zip.
I rooted it following this procedure (renaming Root.zip to update.zip). Everything went fine.
I then applied CWM following this (same rename required).
Now it'll boot fine into the stock Android ROM if I do nothing, but if I press the home button to get it into recovery it gets stuck on the SAMSUNG logo screen. Getting it unstuck requires pulling the battery; upon reinsertion it'll again boot fine into stock, but get stuck into recovery.
I'd gladly apply the official update and THEN redo the whole thing if necessary, but now that I can't access the recovery menu anymore I don't get the option to flash anything from the SD card.
What to do?
Flash 2.3 through odin
Sent from my Sony Tablet S using xda app-developers app
Fallingwater said:
I have a friend with a S5830 (not S5830i, not S5830g; plain S5830). She would like ICS/CM9 installed on it.
The phone does NOT have the latest official update. Its stock recovery doesn't have a "apply update from SDCARD" option; rather, it has "apply sdcard/update.zip", which means I have to rename files I want to flash as update.zip.
I rooted it following this procedure (renaming Root.zip to update.zip). Everything went fine.
I then applied CWM following this (same rename required).
Now it'll boot fine into the stock Android ROM if I do nothing, but if I press the home button to get it into recovery it gets stuck on the SAMSUNG logo screen. Getting it unstuck requires pulling the battery; upon reinsertion it'll again boot fine into stock, but get stuck into recovery.
I'd gladly apply the official update and THEN redo the whole thing if necessary, but now that I can't access the recovery menu anymore I don't get the option to flash anything from the SD card.
What to do?
Click to expand...
Click to collapse
Hi Fallingwater,
You could try Clock Work Mod Recovery v5.0.2.6 Flashable via Odin
Good luck.
The latest firmware isn't requiered, having Gingerbread 2.3 version is enough so look at this:
ROOT + CWM 5.0.2.6.FIX
In the end I solved this by letting KIES update the phone to the latest official firmware. Rooted and CWMed and worked fine from there.
In retrospect I should have probably used Odin from the start.
I flashed a root kernel using Odin from here and that seemed to go fine. I then installed ROM manager from the Play Store, gave it root access when it prompted, and asked it to restart in clockwerk recovery so I could install a custom ROM. However, it would always boot into the stock recovery mode (version 2e, apparently), even If I tried manually. I then read somewhere online that if I chose the apply sdcard/update.zip option in the stock recovery menu it would go into clockwerk -- and it did. Cool. (Version 2.5.1.2) So from here I tried to install a couple different custom roms, but to no avail. One would give me error Status 0, the other would freeze at 'installing update...' (I left it for a couple hours and it didn't change. It used to give me error status 7 - i think - but i followed a guide to fix that)
I also tried changing to TWRP in rom manager, but i'd still boot into the default recovery mode.
Anyone have any clue? Thanks in advance.
TempestUK said:
I flashed a root kernel using Odin from here and that seemed to go fine. I then installed ROM manager from the Play Store, gave it root access when it prompted, and asked it to restart in clockwerk recovery so I could install a custom ROM. However, it would always boot into the stock recovery mode (version 2e, apparently), even If I tried manually. I then read somewhere online that if I chose the apply sdcard/update.zip option in the stock recovery menu it would go into clockwerk -- and it did. Cool. (Version 2.5.1.2) So from here I tried to install a couple different custom roms, but to no avail. One would give me error Status 0, the other would freeze at 'installing update...' (I left it for a couple hours and it didn't change. It used to give me error status 7 - i think - but i followed a guide to fix that)
I also tried changing to TWRP in rom manager, but i'd still boot into the default recovery mode.
Anyone have any clue? Thanks in advance.
Click to expand...
Click to collapse
After go to Clockwork recovery mod do the follwing:
1. Wipe Cache
2.Wipe Data
3.Advanced-> Wipe Dalvic cache
and after that try installing rom. If the same error u got means try without wipe in next step