Database Info

Can't get past htc EVO screen

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.

can't get CWM to work.

I had my phone rooted and and a few mods installed for the past while. I didn't like them so I went back to the origional Rogers ROM. I hated it, so I wanted to try out ICS for my phone. I can't get it to install CWM though. I've tried re-rooting it (and it completed, as far as I can tell). It should still be unlocked, again, as far as I can tell.
I've followed everything on http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
I've downloaded and isntalled Superuser repeatedly
and I've downloaded and isntalled CWM repeatedly.
when I try to "fix permissions" in CWM I get An error occurred while attempting to run privaleged commands!, but at the bottom it says complete.
Then when I try to restart in recovery mode I get
E:failed to verify whole-file signature
E:signature verification failed.
and then it shows that it's restarted in Samsung's recovery mode.
any ideas?

mac_angel said:
I had my phone rooted and and a few mods installed for the past while. I didn't like them so I went back to the origional Rogers ROM. I hated it, so I wanted to try out ICS for my phone. I can't get it to install CWM though. I've tried re-rooting it (and it completed, as far as I can tell). It should still be unlocked, again, as far as I can tell.
I've followed everything on http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
I've downloaded and isntalled Superuser repeatedly
and I've downloaded and isntalled CWM repeatedly.
when I try to "fix permissions" in CWM I get An error occurred while attempting to run privaleged commands!, but at the bottom it says complete.
Then when I try to restart in recovery mode I get
E:failed to verify whole-file signature
E:signature verification failed.
and then it shows that it's restarted in Samsung's recovery mode.
any ideas?
Click to expand...
Click to collapse
A couple of clarifications.
1. Rooting a phone only gives you access to root files (the OS). The superuse.apk, the su files.
2. Stock kernel do not give you the ability to flash insecure zip files. An insecure custom kernel is needed for this.
3. You don't need root to flash an insecure file in a modded cwm.
You are trying to flash an unofficial firmware or insecure *.zip with a secure stock kernel - not going to happen. There are two different ideas altogether.
To have the insecure cwm you are looking for, you need to flash the kernel on that post while in download mode.
Put your phone in DL mode. Flash the kernel then boot into modded cwm recovery

thanks for getting back to me. I had to step out to get some things before the stores closed.
doesn't Entropy's 4.4.2012 kernel do that though?

mac_angel said:
thanks for getting back to me. I had to step out to get some things before the stores closed.
doesn't Entropy's 4.4.2012 kernel do that though?
Click to expand...
Click to collapse
Yes it does. But you don't have it installed.

that's the SGH_I997 Entropy 4_4_2012-One-Click-Heimdall file that runs in Java? I've downloaded that and ran in repeatedly. Keeps saying completed and reboots the phone no problem.
I'm about to reboot in Samsungs recovery mode to try to flash the CWM-Superuser Busybox Root UCLB3 file. I'll wait for your response first.

mac_angel said:
that's the SGH_I997 Entropy 4_4_2012-One-Click-Heimdall file that runs in Java? I've downloaded that and ran in repeatedly. Keeps saying completed and reboots the phone no problem.
I'm about to reboot in Samsungs recovery mode to try to flash the CWM-Superuser Busybox Root UCLB3 file. I'll wait for your response first.
Click to expand...
Click to collapse
I don't remember if mac will flash the kernel correctly. If you check the CPU info and it shows entropy kernel and not the stock kernel, you should be able to boot into cwm recovery with the three finger technique. It will be a red recovery.
If cwm is blue, entropy is not installed.
If you are looking to install a different firmware, there is no need to root. Just flash the firmware you want in cwm. Chances are, the unofficial firmware is already rooted.

mac_angel was a nick I created about 18 years ago when I worked for Apple Canada. I haven't worked with a mac in God knows how long. My last IT job was IBM, lol.
Anyway, I'm not sure what happened. I went to restart in the Samsung's recovery mode again to flash with that file I mentioned and it booted in CWR. I cleared all the dev cache and everything, and flashed the ROM I had already moved over. Phone is still restarting, but it looks like I might be good. I didn't do anything from the time I first posted to now though, lol. I was about to try to flash that file and it worked. Only thing I can think of is that before I was always trying to restart the phone in CWR mode by selecting it to reboot in that mode from the application instead of the three finger salute (oh, wait, that's M$).

You got it going?

yes, thank you. Not sure if you can do it, but the thread can be closed now. Thanks for getting back to me, as well as your other great posts.

If I can get into the Fastboot screen I am not fully bricked??

I can boot with volume up and get to the recovery screen. I am combing threads and doing all I can now. Any help is greatly appreciated. Downloading the SDK on slow work internet now and attempting to get all files I think I might need as we speak.

give members more details [what did u flash etc], so they can help u.

No, if you have recovery mode available nothing is lost.
Just download a ROM you like, and try flashing it. If it doesn't work, try formatting and then flashing again.

I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.

In recovery you can still use adb to transfer files to the device.
Code:
adb push update.zip /sdcard

I am having trouble getting adb to work. I am following these instructions but something seems to be wonky?
http://androidadvices.com/how-to-install-set-up-and-use-adb-for-android-devices/#.UAWbt7Sm_Nk
can you point me in a better direction to get adb access

I just noticed at the bottom of my screen in slightly greyed out copy it reads: FASTBOOT STATUS - FAILINVALID COMMAND

magicwands said:
I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.
Click to expand...
Click to collapse
That small menu as you called it is fastboot.
That recovery is stock recovery.
Connect to phone to computer and use fastboot to flash a custom recovery. Boot into said recovery. Mount usb storage. Transfer rom over to phone. factory reset/format system and flash new rom.
If you don't know how set up and use fastboot. Look it up.

I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?

magicwands said:
I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?
Click to expand...
Click to collapse
Do a full wipe, re-download the rom ( make sure its the correct rom for your device) and try again.
If it still fails. Flash the official stock images and make sure that at least works

I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.

magicwands said:
I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.
Click to expand...
Click to collapse
Download the following files:
7-Zip from http://www.7-zip.org
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
http://android.kcomputerzone.com/stock/sojus-imm76d-factory_windows-scripts.zip
http://android.kcomputerzone.com/extras/crespo-drivers.zip (just in case you need them)
Install 7-Zip
Extract sojus-imm76d from sojus-imm76d-factory-10660f4c.tgz (You will need to go in multiple levels deep to get to folder) to your desktop.
Extract contents of sojus-imm76d-factory_windows-scripts.zip to the sojus-imm76d on your the desktop.
With phone in bootloader mode run flash-all.cmd in the sojus-imm76d folder.
If all worked it should be boot and be working.
That should restore yours to default firmware all using fastboot. Hope this helps.

This site (http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/) got me up and running with TWRP then I been having issues flashing roms, I am able to get a Peter Alfonso stock rom to boot but then if I try to flash I get the same error. I was able to ODIN the stock 4.0.4 but nothing seems willing to flash via clockwork or TWRP.

Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.

magicwands said:
Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.
Click to expand...
Click to collapse
That is the problem with One click root/unroot. I know the simplicity is awesome but the end user is learning nothing. Doing it the ol' fashion way teaches the user how to use SDK, ADB, and other important simple things. I always say use the guide and do it yourself. Problems happen and instead of having to start a new thread you can trouble shoot it yourself. :good:

[Q] Stuck in recovery some time after flashing cwm

Actually it might be a little more complicated...
Full story: I was trying to flash cyanogenmod so I unlocked the bootloader and flashed cwm and SuperSU. Until this point everything worked just fine. I copied the CM-zip to the root of my phone. When trying to install CM however I got an error saying "Some changes failed" (Status 7), basically this. Also I started having trouble booting the system normally. The phone would either get stuck at the bootloader unlocked screen or just boot into recovery. I had done a backup at some point (not prior to starting to try to flash CM, I didn't really think I'd need one since the phone was brand new and I didn't there was any data on it I'd miss... yeah, well...) and sometimes restoring it would enable me to boot normally. However, after the factory reset before my nth attempt to install CM, that was gone as well. After doing a bit of research I found this thread. Since I had version 6.0.13 of cwm as well, I flashed twrp v2.7.1.2 instead. The interface is a little friendlier, but other than that there have been no changes.
Now I can't boot the system normally, not even by selecting "System" when rebooting it from recovery, it will just keep booting into recovery. I can still fastboot, though. My CM-zip is gone since that infamous factory reset and I can't get it back on the phone, or anything else for that matter, since my pc only detects the phone when it's booted normally. I tried pushing CM with adb but when I try to mount any partition I get an error saying E: Unable to find storage partition to mount to USB.
Any ideas how I could fix this mess? Or suggestions on how to avoid ****ing it up any further...

If you can adb, you can adb push... You are just adb push'ing to the wrong place I suppose.
Code:
adb push blah.zip /sdcard/
Should work...
Or even better, just sideload (put phone in recovery & 'sideload mode' before running):
Code:
adb sideload blah.zip
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).

Sideload worked perfectly! Thank you so much!

cm11 working only TWRP here , with cwm appears same error

mmichaelalves said:
cm11 working only TWRP here , with cwm appears same error
Click to expand...
Click to collapse
Did you not read my post?
arrrghhh said:
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Click to expand...
Click to collapse

Messed up storage don't know how to fix it

A while ago I had a ROM running but switched back to OOS due to battery drain. Time passed and I wanted to give it another go and tried installing another ROM, after getting the recommended variant of TWRP running I tried doing the usual, wiping then installing, but as soon as I tried flashing the ROM it kept giving me this log:
Code:
Flashing A/B zip to inactive slot: A
Step 1/2
Error applying update: 26 (ErrorCode :: kDownloadMetadataSignatureMismatch)
Updater process ended with ERROR: 1
To flash additional zips, please reboot recovery to switch to the updated slot.
Error installing zip file '/sdcard/<insert filename>.zip'
etc
I thought maybe it was because the ROM had failed to download properly, so I tried a different ROM and downloaded the other one again, but it still gave me the same error. I tried several things like formatting the storage because I saw a youtube video doing that, but although my phone boots normally if I try to download anything it fails. Not sure why this is happening. I still can't flash any ROM.

If partitions have been corrupt
I think you have hetter to flash latest "oos fastboot"
then restart from a "kind new" phone
anyway,
tipically with .zip file, also a .md5 or .md5sum file Is published
if you start checking It, you will not run in this kind of problems

WayneKosi said:
A while ago I had a ROM running but switched back to OOS due to battery drain. Time passed and I wanted to give it another go and tried installing another ROM, after getting the recommended variant of TWRP running I tried doing the usual, wiping then installing, but as soon as I tried flashing the ROM it kept giving me this log:
Code:
Flashing A/B zip to inactive slot: A
Step 1/2
Error applying update: 26 (ErrorCode :: kDownloadMetadataSignatureMismatch)
Updater process ended with ERROR: 1
To flash additional zips, please reboot recovery to switch to the updated slot.
Error installing zip file '/sdcard/<insert filename>.zip'
etc
I thought maybe it was because the ROM had failed to download properly, so I tried a different ROM and downloaded the other one again, but it still gave me the same error. I tried several things like formatting the storage because I saw a youtube video doing that, but although my phone boots normally if I try to download anything it fails. Not sure why this is happening. I still can't flash any ROM.
Click to expand...
Click to collapse
Long shot but did you figure this issue out? Im running into the same issue with my Oneplus 7 Pro