Database Info

[Q] Moto Droid. Ok, I blew it. Flashed Gingerbread ROM without kernel

First I rooted my Droid as per: Motorola Droid: Full Update Guide - CyanogenMod Wiki
Got the ROM Manager installed and working and then selected: Peter Alfonso's Stock Rooted Gingerbread ROM GPA 13 using the ROM manager, but didn't install the kernel!
Rebooted phone and it shows a M logo, blinks and gets brighter, but nothing from there.
Tried to repeat the rooting steps to reinstall the update.zip and got errors: e: update.zip install blocked and E;error in /sdcard/update.zip (Status 7) installation aborted.
Got a fresh sd card, loaded update.zip on it and repeated rooting instructions with the sbf flash. Got the update.zip to load by first selecting allow update.zip. Loaded update.zip and got message that it was successful, but still boots to M and hangs.
I would really appreciate your assistance in returning to an operating phone!

[Q] Clockwork and no backup

Howdy all, yay another newbie!
Phone is a droid 2, verizon network. I rooted it last night with the super 1click, have SU access, wireless tether and installed rom manager free version.
Flashed cwm recovery to 2.5.08, tried to backup existing rom and had an immediate reboot with no backup made. Tried repeatedly same results, reflashed cwm repeatedly same results. Tried to change the cwm recovery version, and have
2.5.08
2.5.1.4
2.5.1.3
2.5.1.1
listed. But trying to load any but 2.5.08 returns "An error occurred while downloading your recovery.
I tried going into CWM recovery through rom-manager but it immediately reboots back to normal, no recovery screen.
I entered into normal recover and tried to run the 'update.zip' which returns
E:Can't open /cacherecover/command
Install from sdcard
finding update package
opening update package
verifying update package
E:failed to verify whole-file signature
E:signature verification failed
installation aborted
I wiped back to factory through the normal recovery screen and started fresh and am getting exactly the same as before with everything above tried again.
I have not tried installing a new rom, don't want to go that deep until I know I can reset if needed.
Any help or other ideas? What I've been able to find by searching hasn't resolved the problem yet.

[Q] HTC Evo 3D bricked

Hi everyone, so i bricked my phone after rooting it and trying new ROM. Unfortunately i'm a noob and didnt make a backup before.. So now the phone is on loop mode and basically i've tried almost every guide that is out there to unbrick it, still no luck
It gives me installation aborted error message and even if the installation of new rom succeeds, it still keeps on looping :S
Is there a way unbricking it or should i use it as a hammer from now on..
Any help is appreciated, tnx!
EDIT: Maybe it helps to answer, if i write what i've done so far and describe the problem.
It's on the loop mode, which means it doesnt go further than the screen with green htc text. I can bootload and hit recovery with pressing power and down button on same time. Before Fastboot, recovery, factory sheet, simlock and image crc it tells sd checking and "no image". PB31IMG.zip is also on the sdcard and have tried to install that, still abort message..
I've tried with update.zip file, it gives me following error and the end:
file_getprop: failed to stat ''/system/build.prop'' no such file or directory
E:Error in /sdcard/update.zip
Status 7
Installation aborted.
Wiped cache, data and etc
Disabled signature verification
Tried with RUU, turned off unnessecary programs, disabled firewall and antivirus.
It gives error [170]:usb connection error.
Yes usb is connected to the pc and phone.
Phone has Revolutionary cwm
HBOOT-1.49.1187
RADIO-10.13.9020.08_2M
eMMC-boot
Jul 12 2011, 15:29:51
What else should i try ? I certanly can't think of anything

Fixed it myself after a 2 day marathon..
1. Put PG86IMG.zip and Virtuous_shooter-v.1.0.1 file on the sdcard..
2. Rebooted to recovery, PG86IMG image started the update.
3. Deleted the zip file from card and rebooted again.
4. Installed Virtuous_Shooter zip file and it started to update system and booted itself
Thats it!
Worked for me

PG86IMG should work almost every time.

mimmus said:
PG86IMG should work almost every time.
Click to expand...
Click to collapse
Well it did't many many many times.. maybe the file was corrupted or smth

awesome lol.

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] cyanogen mod 10.1.3 RC2 fails install with "status 7"

I am super excited to see an official cyanogenmod for the photon Q 4G LTE. I quickly installed the motorola drivers for the phone, android sdk, unlocked the bootloader with motorola's unlocker, installed ClockworldMod Recovery 6.0.1.3 using fastboot.
Now using cw recovery I am trying to flash cm-10.1.3-RC2-xt897c.zip off my external SD card. The process starts fine buts ends up giving an error.
Code:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /external_sd/cm-10.1.3-RC2-xt897c.zip
(Status 7)
Installation aborted.
I get the same result regardless if I "wipe data/factory reset", "wipe cache partition", and "advanced/wipe dalvik cache".
According to a google search, the status 7 means the rom does not think it is compatible with the phone its being installed to. Well, I checked META-INF/com/google/android/updater-script.txt as described and it contains an entry for
Code:
getprop("ro.product.device") == "xt897c" || getprop("ro.build.product") == "xt897c");
.
It seems like everything checks out. Any ideas why the install is failing?

nezzer said:
I am super excited to see an official cyanogenmod for the photon Q 4G LTE. I quickly installed the motorola drivers for the phone, android sdk, unlocked the bootloader with motorola's unlocker, installed ClockworldMod Recovery 6.0.1.3 using fastboot.
Now using cw recovery I am trying to flash cm-10.1.3-RC2-xt897c.zip off my external SD card. The process starts fine buts ends up giving an error.
Code:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /external_sd/cm-10.1.3-RC2-xt897c.zip
(Status 7)
Installation aborted.
I get the same result regardless if I "wipe data/factory reset", "wipe cache partition", and "advanced/wipe dalvik cache".
According to a google search, the status 7 means the rom does not think it is compatible with the phone its being installed to. Well, I checked META-INF/com/google/android/updater-script.txt as described and it contains an entry for
Code:
getprop("ro.product.device") == "xt897c" || getprop("ro.build.product") == "xt897c");
.
It seems like everything checks out. Any ideas why the install is failing?
Click to expand...
Click to collapse
If it was not compatible, you would get an "assert failed", not "status 7" (I would think?)
If you think it is the assert that is failing, remove that line. Also, that updater-script file shouldn't be a .txt file - it should have no file extension.
In googling that error, everyone does seem to agree tho that status 7 is a mismatch, so I spose try removing that line. I usually would get an 'assert failed' message if these didn't match up - but I use TWRP, maybe that's the difference.

Bad to worse. I had booted the phone multiple times into recovery trying to apply the firmware. No matter what, when I later try to boot the OS, it just stayed stuck at the "boot loader unlocked" warning message, presumably because the firmware was never applied successfully. I left the phone at that screen overnight connected to the computer via USB.
Today I figured I would go ahead and try flashing TWRP to see if that changed anything. Now I am unable to get the phone to power on at all. Pressing the power button has no effect. Same for pressing vol down + pwr. When I plug it into USB the LED turns green but nothing happens on the display. Running adb devices or fastboot devices both say nothing is connected.
The thing appears completely dead. I took the case off and unscrewed the battery terminals for 5 minutes before screwing them back on. Still nothing. The display backlight never powers on.
This is a real bummer. Anyone run across anything like this before?
*Update* It would appear that the phone was not charging when stuck at the bootloader unlocked warning screen despite being connected to my PC. I left my phone on the charger for about 10 minutes and it popped back on to the bootloader unlocked screen. I was able to reboot to the fast boot screen. Since the state is reported as "battery low" I cant flash anything. I will report back once I can flash TWRP.

Mystery solved.
I flashed openrecovery-twrp-2.6.3.0-asanti_c.img and tried installing cm-10.1.3-RC2-xt897c.zip again. No go. Thankfully twrp has some nice features including a great file manager. I tried chmod 777 on the cm zip. No change. I then copied the cm zip from my external sd card to the internal memory. This failed a number of times before it went through successfully. That was my first clue.
I was able to flash cm from the internal sd card no problem. My guess is that my external SD card is experiencing read errors which caused the prior flash attempts to fail. Its working now.

I thought those problems have been solved and/or are nearly not existent.
My SD-Card became defective a few month after using it with my Photon Q. (Got a replacement within warranty.)
I guess that the Photon Q is kind of sensible which mSD's are working and which not.
My current mSD is working flawlessly.
But I flash nearly everytime over the internal storage, just to be sure that I don't get "invisible read errors" during flashing.
You should check your file, a hash may be the way to go.
I had problems with TWRP and CWM with my old mSD. (The flash process was terribly long.)
OpenRecovery was much faster but some flashes were still with issues.