Rom Flash Failed (But ADB says successfull) - HTC One X+

Hey guys,
well i have a pretty nasty problem:
I am flashing the latest Cyanogenmod nightly for the HTC One X+ onto my phone.
This works without errors. The adb sideload installation operation returns a "successfully completed", too.
But when i reboot the device, there simply is no cyanogen mod on it.
I tryed with adb push and manually selecting the .zip file, too.
Again successfully completed. And again no ROM installed.
Actually this not only happens with the CyanogenMod Rom.
It happens with the Carbon Rom, too.
I am very confused! Can anyone help?

which recovery (+version) are you using?
have you flashed the kernel (boot.img) seperataly?
wiped data/ factory reset?

hey, i was using 6.0.4.7 i think. well now i have flashed the boot.img out of the cyanogenmod.zip seperately as boot. now the phone only gets stuck into the HTC bootscreen and doesnt do anything anymore

I have now wiped my phone completely and redone all steps from the cyanogen wiki once again.
Runs smoothely now, have no idea what went wrong before. Thanks anyway.

Related

[Q] Problem installing any .zip through CWM

Hi guys,
I have unlocked my bootloader a few days ago, and also installed the CWM recovery, which I used to install the ATT 2.3.4 ROM (I own an International Atrix), and it was working flawlessly. Being annoyed by that bunch of bloatware, I decided to install the Alien-ROM, so I wiped data with fastboot -w, and entered CWM to erase the cache partition/dalvik cache and install Alien. The problem is, when I tried to install the .zip package, CWM threw at me "Installation Aborted", with no error message whatsoever, just before "Beginning Installation". At first I thought my .zip was corrupted, so I re-downloaded it and tried again, but got the same error.
Being unable to install the AlienROM, I fastbooted the ORFR ROM (surely a lot cleaner than ATT's) and installed the ROM manager app, and through it, updated my CWM to the latest version. And then there I was trying to install the .zip again, with no success. As a last effort, I uninstalled manually the install-recovery.sh file and the recovery partition, reinstalled Tenfar's CWM, but fell into the same error: "Installation Aborted".
Does someone have a clue of that is happening??
Thanks in advance.
Rom manager recovery does not work always.what I suggest is use tenfar recovery and then put alien zip on your ext.SD card and use tenfar recovery --- choose zip from SD card--- browse and select alien.zip and flash through it.
Hope this helps.
Well, I tried to install Tenfar's CWM, as I said at the end of my first post. I recently installed a new CWM-based recovery, and it also failed to install any .zip. Could it be because I'm using ORFR ROM? I've noticed the misbehaving os CWM when I uninstalled ATTs ROM...
Install rom racer's recovery.
I voided my warranty.
Use this link: romracer's custom CWM
Let us know if this helps
pedrohz said:
Hi guys,
I have unlocked my bootloader a few days ago, and also installed the CWM recovery, which I used to install the ATT 2.3.4 ROM (I own an International Atrix), and it was working flawlessly. Being annoyed by that bunch of bloatware, I decided to install the Alien-ROM, so I wiped data with fastboot -w, and entered CWM to erase the cache partition/dalvik cache and install Alien. The problem is, when I tried to install the .zip package, CWM threw at me "Installation Aborted", with no error message whatsoever, just before "Beginning Installation". At first I thought my .zip was corrupted, so I re-downloaded it and tried again, but got the same error.
Being unable to install the AlienROM, I fastbooted the ORFR ROM (surely a lot cleaner than ATT's) and installed the ROM manager app, and through it, updated my CWM to the latest version. And then there I was trying to install the .zip again, with no success. As a last effort, I uninstalled manually the install-recovery.sh file and the recovery partition, reinstalled Tenfar's CWM, but fell into the same error: "Installation Aborted".
Does someone have a clue of that is happening??
Thanks in advance.
Click to expand...
Click to collapse
May be you want to try installing the CWM from here... http://forum.xda-developers.com/showthread.php?t=1204500
This should most likely help you fixing the issue you are facing.
Good Luck.
Cheers!!!
Just tried the recovery mentioned above by you all... and nothing, I keep getting the same error -> "Installation aborted", right after "Beggining installation" (or something like that)
Any clues?
pedrohz said:
Just tried the recovery mentioned above by you all... and nothing, I keep getting the same error -> "Installation aborted", right after "Beggining installation" (or something like that)
Any clues?
Click to expand...
Click to collapse
How are you installing RomRacer's CWM? Flashing the .zip or via fastboot?
Sent from my MB860 using XDA Premium App
I've installed it through fastboot, as it's the only way I can do it... my problem resides solely on the fact that I can't install any .zip through it, I keep getting "Installation aborted", no matter what I try to install (Kernels/ROMs/etc)
Pedrohz... Are you using a Mac? If so do you have it set to unzip after downloading? Then are you re-zipping the file before you try to install? If so turn off the unzip feature. Just a thought... Hope it helps
Similar Issue, can't boot into anything :/ if you can help, read below :S
Ok, so I backed up using Oringinal CWM, and it said all OK. After this, I restored the backup, just to check all was working. I got the error error formatting /system. Rebooting, I found that my phone wouldn't boot. Thinking the only way out was to flash a new ROM, I flashed the new boot.img from evals Orange France 2.3.4 firmware, so that I would have the ram fix. After this, I wiped all the caches and the user data, and tried to install the ROM.
SAME FRIGGEN ERROR. no error code, just installation aborted.
Finally, I tried AGAIN with romracers cwm, but same error. Restoring from backup now gives the error - "Unable to flash new boot.img" or something along those lines.
If anyone cares, heres what my phones running
Firmware = Orange UK 4.4.20 (Android 2.2.2)
SBF= Bell_ihop (the international bootloader unlock sbf)
State= Won't boot past the big red M in the centre of the screen.

[Q] Messed with CWMs. How to properly set/restore it up?

Hi all.
Hope everyone is having a good day!
Lets start: in simple words, it appears I've got two CWM installed. Know it sounds crazy but this is how it looks.
I run Villain 2.4.2 with nynmphetamine 2.1.3 kernel and "some" CWMs
Previously I had also Villain but on CFRoot kernel that preloads a custom CWM
What I've done:
I tried to install CM7 "easy" way so installed ROM manager and when it asked me if I wanted to flash CWM with the newest one I pressed "yes" and stupidly overwrote it. Then downloaded CM7 and when ROM manager attempted to boot into CWM android logo with an expression mark appeared and the phone hung. I rebooted into recovery and it showed me I run CWM 4.0.0.2 (i think that's the custom from CFroot) but the ROM manager says I've got 4.0.1.5.
When I tried to install CM7 via 4.0.0.2 the installation itself went fine but the phone stucked on Samsung logo during post-instalation booting.
Could you give me an advice on how to sort this out? I mean to get properly set up kernel and CWM after some serious messing up
I'd be grateful for any help.
Cheers.
chalger
I dont know if its possible to have 2 CWMs (maybe app version is different), but this happens with CM7. You should wipe dalvik, factory reset, flash cm7 and boot. Phone will get stuck, shut down long pressing power, reboot in cwm and reflash (no wipe needed). CM7 should boot now.

Device stuck at boot screen after flashing VillainROM

Hi all,
Today I wiped all data and cache from my device and installed VillainROM from CWM Recovery Manager. Install looked fine it said that it finished, so I went to reboot.
The device was stuck on the Samsung Galaxy S II logo with the yellow triangle (!) for around 10 minutes. I then turned it off cause I realized it wasn't going to boot.
Anyone have any idea why this happened? I restored a backup of my previous ROM and my phone booted up real fast and it was fine.
Could just be a bad download?
Sent from my GT-I9100 using XDA App
Try flash it again before it boots. IE: Flash from zip, then go back and falsh from zip again.
I've had to do that with CM...
OK will try that, cause the same thing happened to me when I installed Cyanogenmod straight from Rom Manager. Thx
Update: No go, I also made sure Deluxe Settings was uninstalled before I went into recovery. It's stuck at the boot screen.
However, upgrading my previous ROM (WanamLite v4.0) to WanamLite 5.2 worked fine and the device booted. It was exactly the same procedure in recovery mode but a different ZIP file.
Will try another ROM like LiteningRom and see if anything changes. I don't think it's a CRC error because I open up the files before I copy to the device to see if WinRAR pops any CRC errors.
I'd start on the thread a few up from yours.... the one that mentions if you have a boot loop
Sorry, I didn't realize it was a boot loop because it wasn't actually looping, just stuck on the image. Is that considered a boot loop?

Help! Installation of ROM failed and now stuck on recovery

All help is appreciated, i successfully installed twrp, went to install Rom and the installation failed, now the phone only boots to recovery, sideload fails as well, the rom is in there but it fails installation every time, already installed CWM and nothing works. I can boot into bootloader and recovery perfectly just can't get it to install.
Never mind, figured it out, had an outdated twrp recovery, updated via fastboot to the new one and it worked perfectly.
thanks for those that looked anyway.

[Q] Soft Brick. Cyanogen recovery loop. Will you please help?

Hello, i will try to be thorough.
BUT, i am a noob and didnt write down everything i did.
Have a I717 at&t note 1. with the 4.1.2 update originally OTA installed by keis.
I recently rooted it using Saferoot. it went well and i didnt see any problems. i flashed a custom rom and didnt like it so using clockworkmod recovery i went back to the 4.1.2. I then tried pac lollipop >pac_quicyatt_lp.beta-1.unofficial_20150327< i liked this rom but needed to flash Gapps.
This is where the trouble started. i didnt/dont know the proper procedure to flash the Gapps on top of or into the rom.
I first tried >gapps-5.0.x-20150404-minimal-edition-signed.zip< and it looked like it loaded correctly. but nothing appeared in the phone. the pac rom was still working well.
I then did more research and tried >gapps-lp-20150222-signed.zip< , again it looked like it loaded well but nothing showed up "in" the phone.
right here is where things got screwy. i had been using clorkworkmod for recovery and rebooting. and i think somewhere in developer settings i clicked something about how rebooting is handled.
because after trying to install the Gapps it went into Cyanogen recovery... and loops.
no matter what i do it goes back to cyanogen recovery.
I never knowingly installed cyanogen and dont know why it all of a sudden is going into cyanogen recovery over and over.
a list of things that may have bearing:
1. i tried reinstalling the pac rom. it loads and completes but it still just goes to recovery.
2. tried different ways of clearing cache and data wipes.
3. computer, kies, and odin 3.09 do not recognize phone.
4. have proper drivers on computer. phone was previously recognized by kies and cpu (4.1.2).
5. currently the only way to get anything into phone is by pulling sd card and reinstalling with info on it then using cyanogen recovery.
6. i have searched for about 11 hours and tried a bunch of things. but just restarts in cyanogen recovery
7. i was scared to fully try things i found that wernt specifically for the i717.
8. i could not find an original gingerbread rom. they all seemed fishy (needed downloaders. or ended in .zip.rar)
9. had backed up with clockworkmod and with titanium recovery (while in 4.1.2).
I dont know if i can reach the clockworkmod save through cyanogen recovery.... if so it seems like a great option.
10. at the bottom of the screen while loading rom is.... ---->>> E: cannot load volume /misc
11. only pac rom will successfully re-flash (even though it still just goes back to cyanogen). any other flash and it crashes halfway through.... i then restart and it just loops back to cyanogen recovery.
I searched here and tried the five recommended posts.
I could not try a lot of the "fixes" because the phone isnt recognized by cpu or odin (computer does beep when connected but doesnt show up anywhere).
Can you help me get back my phone please?
Randall
added
This is the only site i am asking for help on. I am willing to reply quickly and put in the time!
Thank you very much for reading this far.
Randall

Categories

Resources