Database Info

Stuck in bootloop and voodoo lagfix, unable to connect via USB

So I decided it'd probably be a good idea to finally upgrade as I was sitting on Emancipation AI So I tried flashing Dark Knight upon first flash everything worked, so I rebooted recovery from "green" to CWM 5.5.0.4 "Blue" I got the rainbow bug but was able to flash again, I then got stuck in the CWM 5.5.0.4 boot loop. I managed to get out of that by flashing Emancipation back but then I've been stuck in between Voodoo lagfix "red" and a bootloop of the samsung loading screen. I am now unable to get the phone out of voodoo recovery. And the kicker is that the DarkNight now gets errors while flashing so It fails to install:
assert failed: getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries" == getprop("ro.product.device") == "infuse4g" || getprop("ro.build.product") == "infuse4g" || getprop("ro.product.device") == "SGH-I997" || getprop("ro.build.product") == "SGH-I997" || getprop("ro.build.product") == "SGH-I997"
E:Error in /sdcard/download/I997_Dark_Knight_Infuse_4G_v6.3_beta.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
Normally I'd just boot the phone into download mode but for some reason none of my computers are able to recognize the device, so I tried 2 Win 7 x64 machines one sees that something is plugged in but automatically "installs" and empty driver for it even If I manually go through Device manager and try to upgrade to the actual driver but it says the driver is up to date and just reloads the empty driver, the other Win 7 x64 machine doesn't even recognize that the device is plugged in, I've tried to install the driver Via Kies for both the Infuse and the captivate didn't work on either machines I even found a rar named SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip that didn't work either, I then proceeded to try to get the phone to be recognized both on a laptop running MacOSX 10.6.5 and ubuntu 11.10 neither found the device either. I used multiple(3-4) USB cords all had the same result.
So any help is appreciated

Does heimdall work at all
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

nope heimdall/odin or anything used to interact with the phone via usb does not work. As no computers will recognize the device. I tried using the drivers manually through windows but kept getting errors. I even tried using the drivers included with Super One Click to no avail.

Try flashing emancipation again...might take two flashes...if that doesn't work the when in red cwm go under advanced and enable or disable voodoo lagfix...which ever its currently set to set the opposite
Sent from my HTC PH39100 using Tapatalk 2

I've tried flashing emancipation multiple times, I have also messed with the voodoo settings I was still stuck in bootloop, I'm going to try it again both ways but I doubt it will change.
EDIT:
Flashed emancipation with
lagfix :enabled
nextboot: disabled
/system lagfix conversion: no
debug: no
to no avail
Now going to try with everything enabled
Re-Edit:
Still stuck on boot

Hmmm...so you can't get any computer to detect it...you tried every port??? I'm really kinda at a lost...maybe your USB port is borked on the phone...idk, best advice I can give is to keep flashing....when the first cm9 was released, I flashed it while on vacation away from a computer...I was in the same situation as you...couldnt get it to boot into any Rom...just kept looping but I could still get recovery...so I just kept trying to flash...after an hour of flashing it finally took one of the flashes and booted me into a gb rom-don't remember which gb Rom...again this was a long time ago...when the first cm9 build was released for us...
I think I wiped everything in mounts and storage except the actual sd card or wherever the Roms were that I was trying to flash...
Sent from my HTC PH39100 using Tapatalk 2

alright yeah I've been flashing the rom constantly for 3 days now under different settings, I'll continue trying but I don't know if it will do anything. :/
EDIT: I also have an error while mounting and formatting /system
that's also why I can't use any backups
it says
E: Can't mount /dev/block/st19 (file exists)
error mounting /system/!

EDIT: I also have an error while mounting and formatting /system
that's also why I can't use any backups
it says
E: Can't mount /dev/block/st19 (file exists)
error mounting /system/!
Click to expand...
Click to collapse
Did you ever fix this?
I'm stuck on a CWM 6.0 boot loop and this is the error I'm getting.

[Q] roms won't flash. build.prop problem?

so my friend screwed up his optimus v. he said he did a factory reset, but im not sure how exactly he went about it.
anyway, now i can only get into his recovery (cwm 3.2.0.0). ive wiped everything but the sdcard, but no ROM i flash will work. Mirage and IHO both say:
assert failed: getprop("ro.product.device") == "thunderc"
and so on...
the overdrive rom says its installed when i flash it, but rebooting brings me back to recovery.
should i be finding a way to edit the build.prop or what?
any help would be much appreciated.

peopleface said:
so my friend screwed up his optimus v. he said he did a factory reset, but im not sure how exactly he went about it.
anyway, now i can only get into his recovery (cwm 3.2.0.0). ive wiped everything but the sdcard, but no ROM i flash will work. Mirage and IHO both say:
assert failed: getprop("ro.product.device") == "thunderc"
and so on...
the overdrive rom says its installed when i flash it, but rebooting brings me back to recovery.
should i be finding a way to edit the build.prop or what?
any help would be much appreciated.
Click to expand...
Click to collapse
There is a option in the Cwm " toggle assert " or something like that. Just toggle it to turn it off and try flashing again.
Also try to verify the md5 of rom to know whether it is corrupted or not.

[Q] How to recover A700, when continiuosly rebooting

A700 rooted with easy root 2, and it has worked flawlees for some weeks.
Today it went unresponsive, so I powered off. When i power on I see the acer logo and bootloader version (unlock mode). After a few seconds it reboots and it starts all over.
I have tried to set it back to factory defaults (ClockworkMod) and reboot. Same result.
I have tried to install the following ROMs:
OS_Acer_Acer.AV051.A700.RV09RC08.WW.GE_A41J_A.zip
Acer_A700_AV043.RV00RC00_AV043.RV22RC03_EMEA_DE.zip
They both fail.
Right now it seems like a brick. What can I do from here?
BR Steen

steen-p said:
A700 rooted with easy root 2, and it has worked flawlees for some weeks.
Today it went unresponsive, so I powered off. When i power on I see the acer logo and bootloader version (unlock mode). After a few seconds it reboots and it starts all over.
I have tried to set it back to factory defaults (ClockworkMod) and reboot. Same result.
I have tried to install the following ROMs:
OS_Acer_Acer.AV051.A700.RV09RC08.WW.GE_A41J_A.zip
Acer_A700_AV043.RV00RC00_AV043.RV22RC03_EMEA_DE.zip
They both fail.
Right now it seems like a brick. What can I do from here?
BR Steen
Click to expand...
Click to collapse
format system/data/cache/dalvik
Do it twice, for some reason CWM sometimes doesn't clean everything. Then reflash...
But what did you do, it never got a "spontanious"bootloop i supose..

herogjan said:
format system/data/cache/dalvik
Do it twice, for some reason CWM sometimes doesn't clean everything. Then reflash...
But what did you do, it never got a "spontanious"bootloop i supose..
Click to expand...
Click to collapse
I tried that and the IconiaN2.6 ROM from Vorbeth. The ROM installs without any faults reported, and the tablet now goes beyond the first screen with out rebooting. Unfortunatly it is now stuck with the acer logo with moving circles. It repeats the logo and the moving circles.
What I did? It was working playing radio over TunIn - then it stoped. I gave it some time to recover or move on, but it did not. Turned of the power and powered on - then the problems started.
BR Steen

steen-p said:
I have tried to install the following ROMs:
OS_Acer_Acer.AV051.A700.RV09RC08.WW.GE_A41J_A.zip
Acer_A700_AV043.RV00RC00_AV043.RV22RC03_EMEA_DE.zip
They both fail.
Click to expand...
Click to collapse
Can you elaborate on "fail"?

shawnboy99 said:
Can you elaborate on "fail"?
Click to expand...
Click to collapse
CWM sys for the first "Installation aborted". Thesecond it says
assert failed: getprop("ro.product.name") == "a700_emea_de"
E:Error in /external_sd/Acer_bla bla bla
(Status 7)
It is rooted and bootloader is unlocked, so that is why i think the factory ROM does not load.
Is there a way to lock the bootloader without any USB connection to a PC?
BR Steen

steen-p said:
CWM sys for the first "Installation aborted". Thesecond it says
assert failed: getprop("ro.product.name") == "a700_emea_de"
E:Error in /external_sd/Acer_bla bla bla
(Status 7)
It is rooted and bootloader is unlocked, so that is why i think the factory ROM does not load.
Is there a way to lock the bootloader without any USB connection to a PC?
BR Steen
Click to expand...
Click to collapse
Going back to ICS http://forum.xda-developers.com/showthread.php?t=2155388 it worked for nex86

Cant find a the full ICS ROM. Acer only have the updates for ICS available for download
BR Steen

steen-p said:
CWM sys for the first "Installation aborted". Thesecond it says
assert failed: getprop("ro.product.name") == "a700_emea_de"
E:Error in /external_sd/Acer_bla bla bla
(Status 7)
It is rooted and bootloader is unlocked, so that is why i think the factory ROM does not load.
Is there a way to lock the bootloader without any USB connection to a PC?
BR Steen
Click to expand...
Click to collapse
To go pass the "assert" error, you need to modify the stock ROM zip file, the modification is listed in step 4. You can download stock ROMs directly from Acer site. You can flash it from external SD card, or "adb sideload <rom.zip>" with current CWM recovery.
Once stock ROM is flashed, it will overwrite bootloader and hence re-lock it and replace recovery with stock (unless CWM prevented it from doing so).
It's very hard to brick A700, unless one has not a clue what one's doing.
---------- Post added at 11:34 AM ---------- Previous post was at 11:29 AM ----------
steen-p said:
Cant find a the full ICS ROM. Acer only have the updates for ICS available for download
BR Steen
Click to expand...
Click to collapse
The 300+ MB ROMs on Acer site are full ROMs. I only checked US site. They have both ICS and JB, and one update for each. If you install the ICS, you can also download OTA all the rest.

Thank's for the advice so far!
I found a stock JB version and had the assert error. Following that I modified the updater-script, which solved the installation issue. The updated seemed to install succesfully. Rebooting stated something like "installing EBT", then an automatic reboot. After that the newer ending reboot loop.
So one step further, but still not there

Flashed a stock ICS version, which also seemed to go fine. The message with "boolader unlocked" have disappered. I see the acer logo and the green bubles that transforms into the "Iconia Tab" logo, which remains on the screen - nothing else happens. Pressing updat (vol- and then power) gives the message "Recovery verified failed ...".

[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.

Problems when flashing custom/official ROM

Hi guys. this is my first post here. I'm brazillian, sorry if I make some language mistake.
Yesterday I tried to install this ROM. My girlfriend asked for it, we have the same phone model (C2104). so I tried to install it in mine, to check if it's good and so on. but I started making mistakes here.
I installed CWM, downloaded the ROM and downloaded gapps. according to the ROM page, I should flash it through fastboot. I didn't pay enough attention and tried to flash it through recovery... my phone got bricked, it wouldn't turn on. it would just keep vibrating if I held the power button. if I connected it to the pc or to the charger, the red led would just keep blinkin.
after a lot of trying & searching I'd found out I should reinstall the stock ROM. so I installed Flashtool and tried to flash a stock ROM with it, but I received the same message every time: "processing of loader.sin finished with errors". then I tried repairing the phone through pc companion and it worked. until 30 minutes ago I was using my phone as if it was brand new. note: when I repaired it through pc companion, my pc started recognizing it as c2105.
earlier this sunday, I tried to flash it through flashtool in fastboot mode (after installing CWM again), but I always received an error message. this time I downloaded adb and fastboot sdk, and I received the same error. then I tried unlocking bootloader, and voila. it worked. but after this my phone got bricked again...
now it shows the SONY logo, but it's frozen on this screen. the only way I can power it off is removing the battery. I can access the recovery (now the cyanogen recovery is installed), but there's nothing I can do there. I tried to install the ROM through the recovery, but it says: "this package is for device: c2105, c2104, c2105, c2104, taoshan. this device is .". I tried pc companion repair again, but it says my phone has a modified firmware and so it can't be repaired through that tool. yesterday I made a stock ROM using this tutorial, but if I try to flash it through flashtool I get the same error I was getting yesterday ("processing of loader.sin finished with errors").
I'm stuck here. I've made a full backup through cwm, but since I can't boot the phone I can't install it again. please help me :crying: I wouldn't mind using stock ROM again, but I've had enough of it, I wanted to use a custom ROM for some time...
EDIT: after some thinking and trying, I've found out that pc companion wasn't working because I had unlocked bootloader. relocked it and could repair my phone. but now I have some doubts:
- is it possible for me to get a TA backup from my girlfriend's phone and restore it to my phone? will it work?
- can you guys help me on installing that ROM?

cJames2 said:
- is it possible for me to get a TA backup from my girlfriend's phone and restore it to my phone? will it work?
Click to expand...
Click to collapse
NO, don't do it will hardbrick your phone.
Edit : for more info about TA go HERE

cJames2 said:
Hi guys. this is my first post here. I'm brazillian, sorry if I make some language mistake.
Yesterday I tried to install this ROM. My girlfriend asked for it, we have the same phone model (C2104). so I tried to install it in mine, to check if it's good and so on. but I started making mistakes here.
I installed CWM, downloaded the ROM and downloaded gapps. according to the ROM page, I should flash it through fastboot. I didn't pay enough attention and tried to flash it through recovery... my phone got bricked, it wouldn't turn on. it would just keep vibrating if I held the power button. if I connected it to the pc or to the charger, the red led would just keep blinkin.
after a lot of trying & searching I'd found out I should reinstall the stock ROM. so I installed Flashtool and tried to flash a stock ROM with it, but I received the same message every time: "processing of loader.sin finished with errors". then I tried repairing the phone through pc companion and it worked. until 30 minutes ago I was using my phone as if it was brand new. note: when I repaired it through pc companion, my pc started recognizing it as c2105.
earlier this sunday, I tried to flash it through flashtool in fastboot mode (after installing CWM again), but I always received an error message. this time I downloaded adb and fastboot sdk, and I received the same error. then I tried unlocking bootloader, and voila. it worked. but after this my phone got bricked again...
now it shows the SONY logo, but it's frozen on this screen. the only way I can power it off is removing the battery. I can access the recovery (now the cyanogen recovery is installed), but there's nothing I can do there. I tried to install the ROM through the recovery, but it says: "this package is for device: c2105, c2104, c2105, c2104, taoshan. this device is .". I tried pc companion repair again, but it says my phone has a modified firmware and so it can't be repaired through that tool. yesterday I made a stock ROM using this tutorial, but if I try to flash it through flashtool I get the same error I was getting yesterday ("processing of loader.sin finished with errors").
I'm stuck here. I've made a full backup through cwm, but since I can't boot the phone I can't install it again. please help me :crying: I wouldn't mind using stock ROM again, but I've had enough of it, I wanted to use a custom ROM for some time...
EDIT: after some thinking and trying, I've found out that pc companion wasn't working because I had unlocked bootloader. relocked it and could repair my phone. but now I have some doubts:
- is it possible for me to get a TA backup from my girlfriend's phone and restore it to my phone? will it work?
- can you guys help me on installing that ROM?
Click to expand...
Click to collapse
Ok you got far x) so now you got cyanogenmodrecovery....
-Download the rom you told (Ressurection) to pc
- Extract Meta-inf/com/google/android/updater-script from it
Open it with word ... Search for lines that looks like that
assert(getprop("ro.product.device") == "C2105" || getprop("ro.build.product") == "c2105" || getprop("ro.product.device") == "taoshan" || getprop("ro.build.product") == "C2104" || abort("This package is for device: taoshan; this device is " + getprop("ro.product.device") + ".");
If you find it delete it...
Then repack it to the zip.... Now you should be able to flash
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
Ok you got far x) so now you got cyanogenmodrecovery....
-Download the rom you told (Ressurection) to pc
- Extract Meta-inf/com/google/android/updater-script from it
Open it with word ... Search for lines that looks like that
assert(getprop("ro.product.device") == "C2105" || getprop("ro.build.product") == "c2105" || getprop("ro.product.device") == "taoshan" || getprop("ro.build.product") == "C2104" || abort("This package is for device: taoshan; this device is " + getprop("ro.product.device") + ".");
If you find it delete it...
Then repack it to the zip.... Now you should be able to flash
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
tried again right now, following your directions. now I received this error:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."

cJames2 said:
tried again right now, following your directions. now I received this error:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Click to expand...
Click to collapse
Oh i see...cyanogen recovery....
Download my fota flasher apk.... Open it as a ZIP ... Look into assets and extract fotatwrp.img ...
Put it on a sdcard and insert it into the phone
Start the phone in recovery and connect it to pc
Download and install " minimal adb and fastboot"
Open it and type:
adb shell
dd if=/storage/sdcard1/fotatwrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
then you got my newest recovery... That one should work
Sent from my Xperia T using XDA Free mobile app