I was able to apply unrevoked without any problem and then got greedy. I installed ROM Manager and attempted to install cyanogen mod. Eventually, I've worked myself into the following. The phone at this point, does not ever successfully boot.
When bootloader opens, it gives me the option to start update. If I say yes, it acts like it applies an update but won't load. If I say No, I can eventually get into ClockworkMod Recovery. From there I have tried clearing the cache and reloading the cyanogen mod. It goes through the update but when I reboot, it goes to the white htc EVO screen and does not progress. I have tried the things that I have been able to find so far (like clearing the cache). If anyone has some suggestions, I'd be grateful.
So I am able to get to a screen of nandroids. I've tried installing all of them (there are four) but each comes back with the same error - "Error while flashing boot image".
Woo hoo!! I'm all fixed. If anyone has a similar issue, I was able to boot into recovery, and then use the command line to push a newer version of cyanogen to the sdcard. That allowed me to flash cyanogen (latest version) which is now working just fine.
Related
Not sure how to fix it. Before it happened, I was rooted with a Cyanogen rom on 1.6. I also had a black and green theme on. I went to install a new rom called "OpenEclair". I downloaded it, placed it in my sdcard root folder, and tried to install it. I had an installation error and it aborted. At this point, I figured ok, I'll just reboot. It kept me at the G1 screen for over 25 minutes, so I knew something was wrong. So no matter what I did from here on out (trying to perform a backup restoration, flash a different rom, etc), I would be stuck on the G1 screen. Finally, I flashed a JesusFreke rom and it let my phone come back on, so I haven't tried anything since. However, this rom is ANDROID 1.1. It sucks. Is there any way I can get back to either where I started, or even get this OpenEclair 2.1 rom working properly? Any help would be greatly appreciated. When I try to install the OpenEclair rom (before and after downgrade) it will say
E:Can't chown/mod /system/xbin/librank
*No such file or directory)
D:Failure at line 221:
set perm 0 0 06755 SYSTEM:xbin/librank
Installation aborted.
Press Home+Back to reboot
I had this also. The problem went away after I installed DangerSPL which, as stated at the top of the OpenEclair thread, is required to install this on the G1.
If you don't have DangerSPL, OpenEclair will fail to install as it doesn't have enough room to place its files.
However, if you do have it...
I have noticed this with some of the 2.1 ROMs. I think the reason is that, since we flash using an "updater", it wont wipe the partition before flashing. This leaves the possibility that there are old files with different permissions that prevent the new ROM from properly taking.
Boot your phone into fastboot (for the G1, hold the camera button while powering up), set it into usb mode (by the "back" button, I think), then use the fastboot tool to clear the boot and system partitions:
/fastboot wipe boot
/fastboot wipe system
This will clear the "ROM" component from the phone, and you can then go and flash whatever ROM you want. Make sure to wipe the data partition via recovery.
If, after wiping the ROM and rebooting, the phone is stuck at the carrier screen and says "Fastboot USB", that means it tried to boot the usual way and found no data in the boot partition. You need to boot into recovery and flash a ROM. Using "fastboot reboot" or the reboot command from the phone's fastboot screen will cause this. Use the phone's fastboot "power off" button ("menu" in the G1), then boot it into recovery.
Also remember that any install that fails after the "verification" phase will destroy the existing ROM, since you will be left with a partially installed ROM on top of the older one.
Thanks a lot guys. will try all of this when I get off of work. Much appreciation!
Got everything worked out. Just had to install that danger spl :]
Just flashed FastTest rom, pretty freakin' nice I must say!
Is there a way to backup all my apps/contacts/texts before wiping and flashing a new rom?
Ok I have a massive problem here. Last night I decided to use the 1 click universal root app to root my phone and flash it to get CM.
I downloaded the app did the root, downloaded clockworkmod then did a clockworkmod recovery. After that finished i was given a pre-root option to backup my phone and wipe data/storage.
I only chose back up my phone. My nexus one then rebooted and proceeded to backup my phone then it went to install CM 6 RC2.. After this had finished it then rebooted and went to the multicoloured animation where the colours ceom from the left and right..
Here it would continuously loop and never do anythign else. With this I pulled the battery and loaded into recovery where I was in ClockworkMod. I then proceeded to use the recovery and as it was doing the recovery it just froze and the progress bar nor any words would come up.
From here I pulled the battery again did a soft/hard reset but it would hang on the loading animation again. I then did a wipe data/clean option and now it just hangs on the X logo.
On my sdcard I still have the clockworkmod folder with the backup, nandroid, system and all the other files as well. Vodafone Australia have no stock of the Nexus One at all and won't be getting anymore in since it's a finished product
I barely have any cash for a new phone and need to know asap what to do to fix this problem! If anyone can help!
When you installed Cyanogen CM6 did you install the proper baseband also or you just didn't write it down for us? If you had 2.2 on the phone before you rooted the baseband is ok for CM6.
Did you try hooking your phone with USB and try if ADB interface works? If your computer sees the phone via fastboot?
IF fastboot works, you could always restore your stock recovery and install a stock FRF91. (And then try again with CM6, this time installing the proper baseband AND WIPING like you should when installing CM6!!)
When installing custom ROMs always read the install instructions whole first then install.
http://forum.cyanogenmod.com/topic/...y-crap-its-full-of-awesome-v600-rc2-07252010/
Hello, I'm new to the forums and I feel bad I'm already screwing things up :/
Anyway on to the problem... I've had CM9 running on my phone for about two weeks now but I wanted to get rid of the rainbows in CWM and at boot. Today I downloaded Rom Manager from the market place, and when I ran it, it prompted me to install CWM recovery to my SD card, although I already had it installed I thought I'd give it a try. Bad idea, now I can't leave recovery mode, my phone will continually reboot into recovery, I've tried wiping all data and clean installing CM9 again and still nothing. I've even tried the exitrecovery.zip script to no avail
Any suggestions or ideas on how to fix it and boot into my ROM again?
Thanks!!
I would venture to say you might have to reflash...or start over from stock...
i would reload stock....then reload ics or the rom of your choice...
Thanks a lot! Worked like a charm, I used Odin and flashed factory stock 2.2.1, now I'm off to getting ICS back.
Thanks again!
Does anyone know why this happens? I've noticed that anytime I open CWM and choose the boot to recovery option is when I get stuck with CWM Recovery looping. I then have to go back to stock and start over again.
I'm not entirely sure why it happens, my guess was that it puts up a bad flag not compatible with ICS that keeps it from booting that, that was why I tired the exitrecovery script, I looked through it and it appeared to me to change a flag for booting. I'm not sure why it happens but I'd say just use the reboot to recovery option that the ROM provides in the shutdown menu, I know that always works.
Before I get into the gist of my current problem I think it might be relevant to provide some backstory. I decided I wanted to try and root my phone so I could install a new custom ROM. I had done some jailbreaking back when the iPod touches came out, back when jailbreaking was extremely ghetto and unreliable, so I figured I could teach myself this fairly easily. I unlocked bootloader using the htcdev method without an issue, and, following a guide, downloaded something called Rootboot to flash the phone. There was only one step to this portion, so I assumed it would be easy. Running the rootboot started rooting my phone, however after a couple of lines in the command prompt it said something about the adb, failed, and the phone was stuck in a boot loop with no roms on it at all. I stayed up all night with the damn thing attempting to fix it, and at one point, actually got it to load up the stock ROM from the computer using some combination of RUU's and fastboot commands. I have no clue how I did it, all I know is that it was not through adb sideload because the recovery I had at the time wouldn't work with adb sideload for whatever reason. It was the recovery that came with the All-In-One toolkit, for the AT&T / TELUS version. At this point I figured since the phone was working I would just install the VenomROM, and after a few hours of playing around with fastboot and the bootloader trying to get a ROM loaded, I figured I was familiar enough with all of them to load the ROM.
Which is what brings me to my current issue. I KNOW the boot.img is flashed to the device because I used the All-In-One Toolkit to do it, erased the cache, did it again using fastboot commands in the command prompt, erased the cache, and continued to use recovery to install the ROM. I got it to load and install, cleared the darvik cache, data, and cache, but when booting, the phone would get to the lock screen, upon which sliding to unlock, presented me with a white screen that says "htc" on it instead of a launcher. After a couple of seconds of waiting, it says, "setup has quit responding" and gives me the option to close or to wait. Either option results in the phone rebooting wherein I only see a black screen with the notification bar at the top displaying my battery and no internet/network connection. I have gone back and flashed the boot.img again and cleared cache, darvik cache, and data several times and just have no clue what I'm doing wrong to not get this phone to boot with the ROM. I can reflash at any point from my sideload.zip file and the installation process has an option to flash the kernel (boot.img) because it is included in the zip. Any help would be much appreciated. I highly doubt theres anything wrong with the ROM or boot.img, it is probably me just not doing it right.
I am using (or attempting to use) the 1.2.7 version of VenomXL+ on the HTC One X+ along with TWRP 2.5 as the recovery.
Hi Guys,
I have an AT&T One X that I unlocked and flashed TWRP recovery on. I have been using this for quite some time with a stockish HTC Custom ROM. However I wanted to see what the latest Cyanogenmod was like. So I flashed the latest snapshot after first flashing the specific recovery software linked on the cyanogenmod page. So far so good. Device booted up and was ready for use.
I wanted to install Gapps afterwards so I went to OpenGapps to download the aroma installer. However the Cyanogenmod recovery software doesn't seem to support this. So I wanted to go back to TWRP. Instead of doing the usual flashing in the recovery I decided to use the TWRP Rommanager since it seemed like a quick fix. Ooh how wrong I was.
After installing the recovery through TWRP manager I accepted the request of TWRP manager to reboot to recovery. However my phone greeted me with a black screen afterwards. Up till now I haven't seen anything pop up onscreen anymore and I tried numerous things. The only strand of hope I still have left as that when connecting to my pc I'm still able to see the phone is in fastboot mode.
However when trying to execute a new flash of my recovery partition my phone keeps saying "fastboot error; remote not allowed". I've searched through numerous articles without a solution up till now. Is my phone too far gone to revive?
Doesn't seem like a straightforward fix as no responses are coming in. Maybe an indication if there would be a fix is appreciated as well.