I have SGP311 4.2.2 stock rooted with this kernel and regularly I am trying to install varius custom ROMS but I am always getting Error Status 7 and flashing stops. The only way to overcome this issue is to install first the boot.img from the ROM that I am going to install and then through the Recovery of the new boot.img I can install the custom ROM without errors.
I know this is not a normal behaviour and I am trying to figure out what's wrong. I tried to edit updater-script by removing all the getprop lines but then I got the same error when the set_perm command is executed.
Could you help me ?
Thanks!
i had the same issue
nikal said:
I have SGP311 4.2.2 stock rooted with this kernel and regularly I am trying to install varius custom ROMS but I am always getting Error Status 7 and flashing stops. The only way to overcome this issue is to install first the boot.img from the ROM that I am going to install and then through the Recovery of the new boot.img I can install the custom ROM without errors.
I know this is not a normal behaviour and I am trying to figure out what's wrong. I tried to edit updater-script by removing all the getprop lines but then I got the same error when the set_perm command is executed.
Could you help me ?
Thanks!
Click to expand...
Click to collapse
i had the same issue while i was flashing cyanogen mod 10.1.3 , any ways i kept trying, i still recieved an error
afterwards i tried to download the rom again and then i placed it into my internal sd storage, after soo many tries, i finally got it working
maybe its the issue with your zip file, try downloading it again, place it into your internal storage, not external, then flash it
hassanman1997 said:
i had the same issue while i was flashing cyanogen mod 10.1.3 , any ways i kept trying, i still recieved an error
afterwards i tried to download the rom again and then i placed it into my internal sd storage, after soo many tries, i finally got it working
maybe its the issue with your zip file, try downloading it again, place it into your internal storage, not external, then flash it
Click to expand...
Click to collapse
Hi and thank you for the reply.
I tried to install from the internal flash though I didn't believe that the result would be different and I had the message (set_perm Error Status 7). It's very strange that no other users mentiong this problem. I am thinking maybe it's something with my stock ROM or some other setting.
nikal said:
Hi and thank you for the reply.
I tried to install from the internal flash though I didn't believe that the result would be different and I had the message (set_perm Error Status 7). It's very strange that no other users mentiong this problem. I am thinking maybe it's something with my stock ROM or some other setting.
Click to expand...
Click to collapse
i think you have mentioned that you flashed the boot.img before you tried flashing the rom, i would recommend to flash the right boot.img again from the rom, this is the most common issue when u get status 7 error,
other wise, backup all of your important data, return to stock by using flash tool / factory data reset, root again and then flash the boot.img and then flash the rom
thats what i do when im desperate for the rom :laugh:
Related
Hi
I am running a Stock LSD 4.1.2 JB Rom on my I9100 and do not wish to Root my phone. Yes it was rooted once but I have a specific reason for not wanting to revert back to root.
On a few occasions over the past year I have wanted to flash an app via "Recovery Mode", a .zip file located on the phone's external SD card.
On trying to flash, the following is displayed in yellow: -
E: failed to verify whole-file signature
E signature verification failed
Installation aborted.
I have searched and searched this and other forums and although I can find many many instances when this has ocurred with other people I have not yet seen a generic solution to this problem.
It must ocurr because of a certain situation being prevelant within my phone and the references to it on forums usually suggest they are because someone is messing with a Custom Rom and/or a Rooted Kernal etc etc.
Could someone please tell what is happening, why this is the case and what can be done to sort it please.
I would say that my phone is just over 18 months old, never has had a problem, has been flashed with "Stock Roms" quite a few times and all without wiping or restoring to the factory settings. I do not want to wipe it to sort this problem out and am hoping an easy fix is available.
Hope someone can help
ps - I am trying to install the 4.2 Camera via the patched.zip and have tried to install the "Temporary" Clockwork Recovery" app with exactly the same problem. I stress I do not want to Root.
Anyone please?
rozel said:
Hi
I am running a Stock LSD 4.1.2 JB Rom on my I9100 and do not wish to Root my phone. Yes it was rooted once but I have a specific reason for not wanting to revert back to root.
On a few occasions over the past year I have wanted to flash an app via "Recovery Mode", a .zip file located on the phone's external SD card.
On trying to flash, the following is displayed in yellow: -
E: failed to verify whole-file signature
E signature verification failed
Installation aborted.
I have searched and searched this and other forums and although I can find many many instances when this has ocurred with other people I have not yet seen a generic solution to this problem.
It must ocurr because of a certain situation being prevelant within my phone and the references to it on forums usually suggest they are because someone is messing with a Custom Rom and/or a Rooted Kernal etc etc.
Could someone please tell what is happening, why this is the case and what can be done to sort it please.
I would say that my phone is just over 18 months old, never has had a problem, has been flashed with "Stock Roms" quite a few times and all without wiping or restoring to the factory settings. I do not want to wipe it to sort this problem out and am hoping an easy fix is available.
Hope someone can help
ps - I am trying to install the 4.2 Camera via the patched.zip and have tried to install the "Temporary" Clockwork Recovery" app with exactly the same problem. I stress I do not want to Root.
Click to expand...
Click to collapse
You need root access to flash apps or modify your system
pasanjay said:
You need root access to flash apps or modify your system
Click to expand...
Click to collapse
Ermm, do not think so. Please review this thread before making wild comments like this: -
http://forum.xda-developers.com/showthread.php?t=2082103
I know in some way though that you probably thought you were helping.
Surely this problem has a cause and a solution?
rozel said:
Ermm, do not think so. Please review this thread before making wild comments like this: -
http://forum.xda-developers.com/showthread.php?t=2082103
I know in some way though that you probably thought you were helping.
Surely this problem has a cause and a solution?
Click to expand...
Click to collapse
u have to first flash the 'Temporary CWM recovery .zip' then select 'reboot to recovery' option in stock recovery to enter 'temporary cwm recovery' there u select the 'Camera zip file' to flash.
PS- after flashing 'Temporary CWM recovery.zip' do not reboot ur phone the normal way by doing so u will lose ur temporary recovery.
each time before flashing any zip file u have to flash 'temporary cwm.zip' file first.
Hi thanks but I know this.
Can we get back to my topic please? I would not have posted if I could flash the Temp CWM Recovery. zip file
I just need to know what causes the error I am getting and how I can irradicate it.
rozel said:
Can we get back to my topic please? I would not have posted if I could flash the Temp CWM Recovery. zip file
I just need to know what causes the error I am getting and how I can irradicate it.
Click to expand...
Click to collapse
As the error indicates, it fails to verify the file's signature. You can't flash unsigned packages via stock recovery. The solution is exactly what was already mentioned to you:either root and install a custom kernel/recovery (you don't want it, that's fine), or use a temporary custom (non-stock) recovery. While I had problems with the stock recovery flashing unsigned zips (obviously), I never had an issue with flashing a temp recovery. Try redownloading and reinstalling it - it could be a corrupt file. Which recovery are you trying to use? I recommend the temp touch CWM by Phil (the dev of the PhilZ kernel; use link in his signature). Always works like a charm.
kt-Froggy said:
Try redownloading and reinstalling it - it could be a corrupt file.
Click to expand...
Click to collapse
Nice one! Thank you
It must have been a duff file (temp touch CWM by Phil) as the one I just downloaded, installed without a problem. It was the very same program file but from a different source.
Just installed the 4.2 Camera too so now going to play
Thank you again
Hello,
I searched in many threads as I could and although I learned that mediatek phones were virtually "unbrikable", I'm afraid it keeps getting worse and won't do more without your expertise.
So a few days ago I was wiping my phone to install another rom and besides wiping data and cache, I also made the huge mistake of wiping SYSTEM... My phone now just boots into recovery and nothing else.
I have an Efox Smart e4, equals to no.1 s6 and hdc galaxy s4 according to other posts here. MTK 6589, 1gb internal, 1,84gb internal sd.
The first custom rom that i installed was Essefour no.1 s6 by iceman and also the touch recovery. The rom performed great but I wanted to solve the issue that the phone kept switching between sd external and internal randomly. Also, I wanted to merge the internal memory with the internal sd so I was gonna try another rom. With this problem, was even trying the stock rom but to no avail.
When I try to install the Smart e4 factory rom for cwm and I get status 7.
E:Resource type (image) failed to load
Installing /sdcard/SMART-E4_V1.0_V01_2013-10-29_CWM.zip
Checking for MD5 file
Skipping MD5 check: no MD5 file found.
... Writing boot...
assert failed: write_raw_image("/tmp/boot.img", "boot")
Error in /sdcard/SMART-E4_V1.0_V01_2013-10-29_CWM.zip
(Status 7)
Click to expand...
Click to collapse
Other roms it just fails.
Right now, my computer windows 8.1 x64 can't identify correctly my phone, only access the sd. So can't do any adb push. In download mode it identifies as lenovo composite interface?? and cdc serial, the last I can't install. In other modes, I get gt-9500 but with the yellow triangle.
I would really really appreciate any help, thanks!
Might try to just edit the updater-script and remove the asserts.
Reference this for more info: http://forum.xda-developers.com/showthread.php?t=2522762
But I think your issue is that since you wiped the system, there's no /tmp folder to store the boot.img. However, if the last rom and this rom can use the same kernel (boot.img) then removing the assert for the boot.img install might do it since wiping the system does not affect the kernel.
What happened to the other rom you know is working somewhat? Can you just reflash that?
Otherwise, you'll just have to find the official way to flash with the scatter file and all that.
I searched for that updater and there are no lines for assert on the stock rom. Also inside the main zip, there are zips for system, boot, recovery and logo...
I'm trying to install the stock rom to play it safe since it was the same that came with the phone. The previous rom I talked about, I deleted it and now the phone isn't recognized on the computer..
Since I don't know if they have the same kernels, is it safe to try and reinstall the custom rom?
As of using scatter and such, maybe I need other pc to get the drivers running again.
Will let you know
I got it!!
The zip from the stock rom wouldn't let me install the kernel (boot). Managed to install only the rom, and as you said the kernel wasn't the same.
Eventually I reinstalled the custom rom and afterwards flashed a completely different rom via spflash tools since it connected successfully to my computer this time.
As I'm already restoring apps and data, I think everything is working properly.
Once more, thank you very much
hi i have sgh-i777 it has paranoid android 2.3.5 installed in it but it was giving me some issues so i changed it to Illusion-v2.5.alpha-UNOFFICIAL-i777 but now it is starting on its own without me touching it also when im trying to change the rom it is giving me an error message cant mound sdcard please help
Your current rom, Illusion-v2.5.alpha-UNOFFICIAL-i777, as it's name implies sounds rather unstable. If you are unable to flash from your current recovery, I would suggest that you flash back to stock using Odin, then root, install a custom kernel with CWM, and go from there.
creepyncrawly said:
Your current rom, Illusion-v2.5.alpha-UNOFFICIAL-i777, as it's name implies sounds rather unstable. If you are unable to flash from your current recovery, I would suggest that you flash back to stock using Odin, then root, install a custom kernel with CWM, and go from there.
Click to expand...
Click to collapse
Thanks it worked out just fine and now i need more help from you guys please tell me to which extent of firmware will my phone work without any battery drainage problems or other problems and also guide me to some thread where i could find that suitable firmware
thanks in advance
Hey,
I got a problem with my S2g. I'm currently on Android 4.1.2, with cwm 6 and blazing v-5 kernel. Both were flashed per odin and work fine. However I can't flash a custom rom. Every time I try it I'll get a Status 7 error. I've already tried 4 different ROMs and I'm really annoyed by now. I also tried to factory reset the phone before I flash the ROM, but it didn't make any difference. I also tried deleting the assert command in the updater-script file but somehow my changes in the file won't be saved.
If anyone could help me I would be really thankful!
http://forum.xda-developers.com/galaxy-s2/help/to-mod-s2-t3189884
I've just tried this, didn't work also. I even had to flash the recovery and the kernel again after trying to flash the file in the link, because the phone wouldn't boot normal or in recovery mode.
mcb25 said:
Hey,
I got a problem with my S2g. I'm currently on Android 4.1.2, with cwm 6 and blazing v-5 kernel. Both were flashed per odin and work fine. However I can't flash a custom rom. Every time I try it I'll get a Status 7 error. I've already tried 4 different ROMs and I'm really annoyed by now. I also tried to factory reset the phone before I flash the ROM, but it didn't make any difference. I also tried deleting the assert command in the updater-script file but somehow my changes in the file won't be saved.
If anyone could help me I would be really thankful!
Click to expand...
Click to collapse
Try using philz recovery on your phone. It should flash most ROMs fine.
gsstudios
gsstudios said:
Try using philz recovery on your phone. It should flash most ROMs fine.
Click to expand...
Click to collapse
I just did, I still get the Status 7 error. I tried to flash the cm 12.1 and the cm 13.0 nightly rom. I also tried deleting the assert command in the updater-script file but it still won't work. There was no Status 7 error but it still said "Installation aborted".
Does anyone else got an idea how to fix this?
http://forum.xda-developers.com/galaxy-s2/development/kernel-blazing-kernel-v16-t2275275
I used this Kernel, I just noticed, that it's only compatible with Android 4.1, 4.2 or 4.3.
I then tried to install the DorimanX Kernel for LP and MM (http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-dorimanx-lp-5-x-x-t3145879) but my phone stucks at the boot screen.
mcb25 said:
http://forum.xda-developers.com/galaxy-s2/development/kernel-blazing-kernel-v16-t2275275
I used this Kernel, I just noticed, that it's only compatible with Android 4.1, 4.2 or 4.3.
I then tried to install the DorimanX Kernel for LP and MM (http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-dorimanx-lp-5-x-x-t3145879) but my phone stucks at the boot screen.
Click to expand...
Click to collapse
Apologies, I only just noticed you have a i9100g, not a i9100. You can't just flash i9100 kernels as they simply won't work!
You can follow the guide in the CM13 OP here:
http://forum.xda-developers.com/galaxy-s2/development/rom-cyanogenmod-13-0-t3381511
gsstudios
Hi guys I hope that this is not a duplicate but I feel like I tried everything and still have the Error 7 with message that this is the rom for D6503 and your device is " ". I flashed stock ftf, flashed boot.img from ROM and recovery through fastboot, boot into recovery wipe everything and still getting that message. Even tried to edit and delete the lines in updater-scripts but with no succcess...I had some break from flashing so maybe I've missed something. Oh and I've tried few different recoveries as well.
Nobutadag said:
Hi guys I hope that this is not a duplicate but I feel like I tried everything and still have the Error 7 with message that this is the rom for D6503 and your device is " ". I flashed stock ftf, flashed boot.img from ROM and recovery through fastboot, boot into recovery wipe everything and still getting that message. Even tried to edit and delete the lines in updater-scripts but with no succcess...I had some break from flashing so maybe I've missed something. Oh and I've tried few different recoveries as well.
Click to expand...
Click to collapse
Use provided TWRP in rom forum and use the last one