So, for any rom I install I get a Status 6 error code and installation failed, blah blah.I know the status 7 code comes up when using the OG recovery for N4 roms, but that wasn't the case. After looking at some logs I got some lines about expecting various characters like '!' ')' and others in line 1 col 1, but in another it said something about missing the volume /emmc. I've tried everything I can think of, redownloading (multiple times), toggling assert check and verification check, like 3 different recoveries. If I can't get this solved, I'll probably just do the whole lgnspt deal and start from scratch, but dang, I'd really like to figure this out.
Did you do the 8gb to 16gb fix? If so, run parted and check that userdata and cache have a format. If there isn't a format, do fastboot format userdata then fastboot format cache. Wipe and you're good to go. I had this issue as well lol.
Sent from my Paranoid Neximus G
Yeah I'll try that next, but I probably did the conversion/16gb fix about a month ago, it's crazy that it would decide to act up now.
Sent from my Nexus G LTE
Did you flash a modem at all?
Sent from my Paranoid Neximus G
Neroga said:
Did you flash a modem at all?
Sent from my Paranoid Neximus G
Click to expand...
Click to collapse
Like ever? Yeah I've flashed a bunch of them. My guess if it's related it has to be the new att jb one.
Sent from my Nexus G LTE
Ugh I feel so stupid, the problem was I tried to toggle the script assert check and install them on the OG recovery, EVERY TIME. This broke the updater script, so it didn't work in any recovery. Thanks for the help, at least I have a squeaky clean userdata now...
Related
I have rooted and rom'd for a couple of years, first on the moment, then the EVO and now the evo 3d and have never run across this. E: error in tmp/sideload/package.zip I have tried 2 different roms and have gotten the same result. I have searched but have been unable to find an answer. Anyone know how to fix this?
nikiya said:
I have rooted and rom'd for a couple of years, first on the moment, then the EVO and now the evo 3d and have never run across this. E: error in tmp/sideload/package.zip I have tried 2 different roms and have gotten the same result. I have searched but have been unable to find an answer. Anyone know how to fix this?
Click to expand...
Click to collapse
What ROM are you trying to flash? Are any of the options under the flash menu checked or have an"X" beside them?
Have you tried reflashing the recovery? Are you using TWRP 1.01 or 1.0?
I am using twrp 1.0.1 and have been trying to flash gbsense-e3d-deck [0.2] and Chogardjr3D v0.9 - Re-Engineered Sense 3.0, I have tried redownloading, reflashing the recovery, I am doing full wipes before flash attempts. I am really at a loss as to what the issue is.
Did you check reboot after successful flash? I don't know if that's what fixed it for me but I had that problem the first time.
Sent from my E3D.
I know I had it checked when trying to flash Chogardjr3D v0.9 but not the other because I wanted to flash the netarchy kernel
nikiya said:
I know I had it checked when trying to flash Chogardjr3D v0.9 but not the other because I wanted to flash the netarchy kernel
Click to expand...
Click to collapse
Hmmm..I know others have had this problem. It seems perseverance is key. Keep wiping, factory reset, etc. It seems once it works once, your good.
Sent from my E3D.
I can't flash any roms. I am using twrp 1.0.1 downloaded early this am.
Also, I redownloaded twrp, and redid that so recovery is new.........
Just tried the mik rom, I got the same errors.
E:Error in /tmp/sideload/package.zip
and with sig verification on I get
E:signature verification failed
mik's rom is signed as well as synergy............
There have been a few others with this problem, but they seem to get past it. I wipe everything but still get these errors. And when I tried to restore with my nandroid, I get stuck on the htc screen, then I pull the battery, wipe, and restore the nandroid again, and it works, but it always takes me two times. Any one have an idea, never ran into this before............
I have no options checked, still get this error.......
B-Mod said:
I can't flash any roms. I am using twrp 1.0.1 downloaded early this am.
Also, I redownloaded twrp, and redid that so recovery is new.........
Just tried the mik rom, I got the same errors.
E:Error in /tmp/sideload/package.zip
and with sig verification on I get
E:signature verification failed
mik's rom is signed as well as synergy............
There have been a few others with this problem, but they seem to get past it. I wipe everything but still get these errors. And when I tried to restore with my nandroid, I get stuck on the htc screen, then I pull the battery, wipe, and restore the nandroid again, and it works, but it always takes me two times. Any one have an idea, never ran into this before............
I have no options checked, still get this error.......
Click to expand...
Click to collapse
This is exactly what is happening to me as well.
Do a reboot. Your system wont be there so reboot into bootloader and go back into recovery.
I had the restore problem too..had to double up.
Sent from my E3D.
B-mod you are the man! That did it.
Sent from my PG86100 using XDA Premium App
nikiya said:
B-mod you are the man! That did it.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
tehbeetus, and I both got it, I rebooted and selected factory reset, and it worked, tehbeetus just rebooted and got it to go. Not sure why some of use have to do it twice though. Mine is that way everytime I flash a rom, or nandroid.
My buddy has a Thunderbolt he got as a gift that froze and so he tried flashing another rom but came across a huge issue. He tried wiping data, cache, dalvik-cache, and system (I think this is where he messed up) and when he tried flashing the new rom, it kept aborting installation. After that his recovery kept showing a log error where it couldn't mount recovery logs and also it wouldn't mount system or cache. The recovery seemed damaged at that point, so he went into HBOOT and tried flashing some stock rom through it, I guess it didn't go well because it gave an error and said something about the installed version being lower, not really sure. Now it won't even boot into recovery. Oh and here's the worst part, S-ON.. he doesn't know how to mess around with Androids, he asked if I could fix it for him. Any help would be appreciated, I know the phone was a gift for his fiance and I feel bad, I wanna help before they send it back to HTC.
Sent from my LG-E739 using Tapatalk 2
Is the bootloader even unlocked and is he even rooted? From what it sounds like is he tried flashing a rom without even rooting or unlocking the bootloader at the least. I suppose you could try running the all in one tool and see if you can get root and everything and then try flashing a rom after that but it sounds like hboot and recovery are now corrupted.
Sent from my ADR6400L using Tapatalk 2
I am currently on CM9, I have had this ROM for over a year....I tried flashing PA and I get an error message that says
asset failed: getprop("ro.product.device") == "d2vsw".....
E:Error in /sdcard/pa_d2vzw-3.10-L13N-25FEB2013-152747.zip (Status 7) Installation aborted.
I have tried flashing multiple times
Is vzwd2 for the Verizon Fascinate or is it the fascinate mtd?
CC268 said:
I am currently on CM9, I have had this ROM for over a year....I tried flashing PA and I get an error message that says
asset failed: getprop("ro.product.device") == "d2vsw".....
E:Error in /sdcard/pa_d2vzw-3.10-L13N-25FEB2013-152747.zip (Status 7) Installation aborted.
I have tried flashing multiple times
Is vzwd2 for the Verizon Fascinate or is it the fascinate mtd?
Click to expand...
Click to collapse
YOU ARE ON A FASCINATE SO FLASH THE FASCINATEMTD THE D2 STABDS FOR A MOTO DROID2 JEEZ Lol sorry I went off but damn reqd the file name which one would it be the one that says fascinate or the one that says d2 lol please think a little next time
Sent from my SCH-I500 using Tapatalk 2
the link you are looking for is this
pa_fascinatemtd-3.10-L13N-25FEB2013-154112.zip
http://d-h.st/T0j
and bbrad the d2vzw is actually the Samsung Galaxy S III....
.
hhp_211 said:
the link you are looking for is this
pa_fascinatemtd-3.10-L13N-25FEB2013-154112.zip
http://d-h.st/T0j
and bbrad the d2vzw is actually the Samsung Galaxy S III....
.
Click to expand...
Click to collapse
I'm going pure stupid today I mentioned in another thread that the i9000 isn't even a galaxy phone and now this I think I've been staying up to late trying to build fken aokp lol please forgive me lol
Sent from my SCH-I500 using Tapatalk 2
---------- Post added at 05:36 PM ---------- Previous post was at 05:28 PM ----------
Of course droid 2 would make more sense lol
Sent from my SCH-I500 using Tapatalk 2
I figured it out...
CC268 said:
I am currently on CM9, I have had this ROM for over a year....I tried flashing PA and I get an error message that says
asset failed: getprop("ro.product.device") == "d2vsw".....
E:Error in /sdcard/pa_d2vzw-3.10-L13N-25FEB2013-152747.zip (Status 7) Installation aborted.
I have tried flashing multiple times
Is vzwd2 for the Verizon Fascinate or is it the fascinate mtd?
Click to expand...
Click to collapse
Correct, Your phone is different and not a fascinate. Not really sure what is workin for your guys as far as flashing. Every phone has its own personality. B brads acts like my one ex few a year or two ago! hahahaha But ya mine does that every time when coming back from stock or cm9 ( status 7 errors) after ics usually wiping data and cache flash 4.2 you might get status 7 3 or 4 times it should boot into the next recovery then flash 4.2 again. What I do now is (if coming from stock) I go right to 4.2. This last time i flashed the cwm recovery then flashed the 4.2. Usually it will boot into the cwm5 add your golden. Because of the change in partitioning if not going back to stock just wiping and flashing those few times should get you there. I had no issues with that though when I flashed right from stock and skipped ics. I explained i what I did HERE in post #7. Everyone does/finds what works after a bit of crack flashing lol If you still having issues one more thing you can try before having or decide to go to stock and back up is try flashing a 4.1.2 rom then 4.2.2. I seriously had to keep trying to flash the zip several times and getting status 7's every time before it took. What a pain!
Edit: Man b rrraaad....you need some sleep or somethin lol
LasVegasRomeo said:
Correct, Your phone is different and not a fascinate. Not really sure what is workin for your guys as far as flashing. Every phone has its own personality. B brads acts like my one ex few a year or two ago! hahahaha But ya mine does that every time when coming back from stock or cm9 ( status 7 errors) after ics usually wiping data and cache flash 4.2 you might get status 7 3 or 4 times it should boot into the next recovery then flash 4.2 again. What I do now is (if coming from stock) I go right to 4.2. This last time i flashed the cwm recovery then flashed the 4.2. Usually it will boot into the cwm5 add your golden. Because of the change in partitioning if not going back to stock just wiping and flashing those few times should get you there. I had no issues with that though when I flashed right from stock and skipped ics. I explained i what I did HERE in post #7. Everyone does/finds what works after a bit of crack flashing lol If you still having issues one more thing you can try before having or decide to go to stock and back up is try flashing a 4.1.2 rom then 4.2.2. I seriously had to keep trying to flash the zip several times and getting status 7's every time before it took. What a pain!
Edit: Man b rrraaad....you need some sleep or somethin lol
Click to expand...
Click to collapse
I got some sleep I'm happy now lol
Sent from my SCH-I500 using Tapatalk 2
Here's a thought. Why not put the files in different folders so people stop asking and getting confused?
Shakes The AssClown said:
Here's a thought. Why not put the files in different folders so people stop asking and getting confused?
Click to expand...
Click to collapse
Who's that intended for?
Got PIE?....Sent from my: €vil Hybrid~>
I converted my LGOG today, and everything went smoothly. I have CMW touch as my recovery (but i've tried TWRP too) and when I try to flash a rom (Pacman in this case) it aborts the install and tells me "error 7, something about assest failed getprop." The only thing I haven't done is do the fix for 8gb -> 16gb.
Any ideas?
Edit: I finally got 10.1 to install, looks like my Pacman download might have been corrupt. However, its stuck on the spinning cyanogenmod screen for the past 20 minutes.
xsaqzw said:
I converted my LGOG today, and everything went smoothly. I have CMW touch as my recovery (but i've tried TWRP too) and when I try to flash a rom (Pacman in this case) it aborts the install and tells me "error 7, something about assest failed getprop." The only thing I haven't done is do the fix for 8gb -> 16gb.
Any ideas?
Edit: I finally got 10.1 to install, looks like my Pacman download might have been corrupt. However, its stuck on the spinning cyanogenmod screen for the past 20 minutes.
Click to expand...
Click to collapse
Did you use a N4 recovery? Because you need one to flash n4 specific roms like Pacman. Also there was a step late in the conversion that involved wiping that you might want to look into again.
Optimus G recovery for our custom CM10.1 roms
N4 recovery for N4 roms
C2fifield said:
Did you use a N4 recovery? Because you need one to flash n4 specific roms like Pacman. Also there was a step late in the conversion that involved wiping that you might want to look into again.
Click to expand...
Click to collapse
I used the Optimus recovery at first, but later used the N4 recoveries. The N4 recoveries ran fine. I was able to install the ROMS, however each one hung at the boot screen (CyanogenMod screen and the pacman boot screen.)
After failing with that I went back to stock. Now my phone is hung on the "at&t rethink possible" screen. LGNPST got to 85% but I heard that was normal and to exit out and continue.
Now what?
tdnick said:
Optimus G recovery for our custom CM10.1 roms
N4 recovery for N4 roms
Click to expand...
Click to collapse
Yes, I used the N4 recovery.
Hey, man I just had this exact same problem under different circumstances so maybe I can help. When LGNPST finishes and reaches 85% wait for the pop up that says the device disconnected. Once it does that turn the device off. Now hold volume down and power and it should ask if you want to reset your device. Press power to reset it and it should boot up (it might feel like its taking a while after all this time your spending waiting and getting nothing, I know that feeling!). There you go! All fixed up! Someone helped me with that last night in a thread and I was sure I'd tried that but I was wrong and it worked! If it doesn't then it's possible you need to charge your phone and then do it. Let me know if that does or doesn't work, bud. Good luck!
Sent from my LG-E970 using xda app-developers app
What have I done wrong. I rooted a friends note as I did mine. Followed Canadian rooting guide. Went to install new cm10.1 and got a error. Blah blah blah error "bad". Redownloaded 4 times withe the same result.
What's my deal?
Sent from my SGH-I717R using xda app-developers app
thutchinson85 said:
What have I done wrong. I rooted a friends note as I did mine. Followed Canadian rooting guide. Went to install new cm10.1 and got a error. Blah blah blah error "bad". Redownloaded 4 times withe the same result.
What's my deal?
Sent from my SGH-I717R using xda app-developers app
Click to expand...
Click to collapse
Perhaps give TWRP2 a try as the recovery. I've had more success with it over CWM with newer ROMs and never went back to CWM.
When reporting an issue... it's a fantastic idea to describe your problem as clearly as you can.
"Error blah blah blah Bad ... blah blah blah" doesn't really help anyone to help you.
Cwm gave your an error, now I can only assume it was a status 7 error.
That means your recovery is older than the type of script used in the zip to flash the rom.
To fix this, do as the poster above said and get the latest twrp, or find an updated version of cwm.
I personally use twrp so I'm not 100% sure where to find the latest cwm if it's not here on xda.
Now... if this isn't the error you're getting. Do yourself a favor and just flash that rom and
POST EVERY SINGLE THING CWM SAYS.
LETTER FOR LETTER.
Hey Folks, The error I am seeing is on both TWRP and CWM. E:Can't open /sdcard/cm-10.1-20130303-NIGHTLY-quincyatt.zip(Bad) Installation Aborted.
studacris said:
When reporting an issue... it's a fantastic idea to describe your problem as clearly as you can.
"Error blah blah blah Bad ... blah blah blah" doesn't really help anyone to help you.
Cwm gave your an error, now I can only assume it was a status 7 error.
That means your recovery is older than the type of script used in the zip to flash the rom.
To fix this, do as the poster above said and get the latest twrp, or find an updated version of cwm.
I personally use twrp so I'm not 100% sure where to find the latest cwm if it's not here on xda.
Now... if this isn't the error you're getting. Do yourself a favor and just flash that rom and
POST EVERY SINGLE THING CWM SAYS.
LETTER FOR LETTER.
Click to expand...
Click to collapse
Your file is incomplete or corrupted. Redownload it.
I have redownloaded at least 4 times on both computer and transfered it over and on the phone via browser
Sent from my SGH-I717R using xda app-developers app
Download it from here: http://get.cm/get/jenkins/21559/cm-10.1-20130303-NIGHTLY-quincyatt.zip
And transfer to your phone/sd card via USB cable or SD card adapter on PC.
You did install CWM properly and aren't still using stock recovery?
Problem has been solved. I used the USSD code for reset, went to stock and re did everything and a way I go. Everything works no. What I did before is beyond me. Thanks alot to everyone who has offered their help! Greatly appreciated...
Agoattamer said:
Download it from here: http://get.cm/get/jenkins/21559/cm-10.1-20130303-NIGHTLY-quincyatt.zip
And transfer to your phone/sd card via USB cable or SD card adapter on PC.
You did install CWM properly and aren't still using stock recovery?
Click to expand...
Click to collapse
Help in 10.1 CM install
thutchinson85 said:
Problem has been solved. I used the USSD code for reset, went to stock and re did everything and a way I go. Everything works no. What I did before is beyond me. Thanks alot to everyone who has offered their help! Greatly appreciated...
Click to expand...
Click to collapse
Hi,
what did you mean you went back to stock? and what is USSD?
here are my issues:
Hi, I really love this CM 10.1 ROM I am running the 10.1 201330209-unofficfial-quinctatt. Everything works fine except when I reboot the phone it loads the boost screen starts up and then freeze once done with the boot screen.
SO I need to restart the phone a few times to be able to get it back on.
---also I have 5.8.4.3 CWM in stalled and try to use ROM manager when it works even got the paid version but booting into CWM works best.
I am unable to install the latest cm-10.1-20130306-EXPERIMENTAL-quincyatt-M2.zip. I get a.
--- "zip status 7 aborted message.
Also when I try to install cm-10.1-20130304-EXPERIMENTAL-quincyatt-M2.zip. it installs fine,
But when I try to place calls.
---there is no sound on the speaker or external or internal.
I would like to stay current on the nightlies but are these just some of the glitches that come with it?
---Also I tried installing the GB-modem because my GPS wont lock, I think that is when the phone quit allowing me to make calls(no sound on speakers) which help the gps a little I guess? not really.
I am now back on the i717UCLF6 baseband.
If it wasnt for my nandroid back up I would be totally LOST!
I mostly use liquid Mod it works best, love it! but would like to be on 10.1 CM. Still no gps lock though. I REALLY NEED GPS, i drive a lot for work.
I know there is a lot going on here buy ANY! help is very much appreciated!
Install the latest TWRP recovery ...IMHO And although I might get flames thrown for this, use recovery to flash directly, and not through the rom manager app.
It has caused users some grief...
Regarding your sound and boot errors, boot into recovery and wipe all caches ....cache/dalvik cache .....then reboot too test. It sounds as if your flash may be dirty somehow. And if restoring apps to your new roms by using titanium backup or other apps, restore only the APK and not the associated data stored by those apps.
CM nightly builds are buggy yes, and will have errors not found in stable builds. But having used the same build you are referring too only a day ago, I can tell you that my sound was okay with the M2 rom.
And I commend you on the creation of a proper nandroid backup. It seems all too often we find users in real trouble with no backup in their pocket to save them.
Call me anal retentive, but I flash bleeding edge tweaks every day, and I keep backups compatible to all 3 recoveries we have for the note just for this type of emergency.
The latest TWRP and a cache cleaning should help you with both the current build, and future builds to come.
Good luck, and happy flashing ...g
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app