I tried to install
|ROM||AROMA|| Padawan JB V2 || PIE || Per App DPI ||4.1.2| 5|31 on my i717 using both CWM and TWRM and both give me the same error after flashing the ROM. It says encryption failure, and tells me to format all my data and try to encrypt it again. I don't have any encryption on my phone, and I did a full wipe of the device prior and after flashing the ROM. I then flash a stock AT&T rom using Odin which worked fine, but then when I reflashed the ROM using both CWM V5.5 and the latest TWRM I still get the same error. I read about how it can be caused by the OS unable to read those paritions, but I followed the directions and it doesn't seem like anyone else is having issues. Can anyone point me in the right direction? Not sure if it matters but I was upgrading off of CM v10
Scarpa_sd said:
I tried to install
|ROM||AROMA|| Padawan JB V2 || PIE || Per App DPI ||4.1.2| 5|31 on my i717 using both CWM and TWRM and both give me the same error after flashing the ROM. It says encryption failure, and tells me to format all my data and try to encrypt it again. I don't have any encryption on my phone, and I did a full wipe of the device prior and after flashing the ROM. I then flash a stock AT&T rom using Odin which worked fine, but then when I reflashed the ROM using both CWM V5.5 and the latest TWRM I still get the same error. I read about how it can be caused by the OS unable to read those paritions, but I followed the directions and it doesn't seem like anyone else is having issues. Can anyone point me in the right direction? Not sure if it matters but I was upgrading off of CM v10
Click to expand...
Click to collapse
If you reflashed the stock rom and put custom recovery did you check for root. I had same issue with a different rom so I went back to my stock backup and downloaded the rom and flashed again. But with Padawan Twrp will try to fix superuser but the Dev says don't let it.
Hope this helps. If all else fails PM the Dev he is always willing to help
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Scarpa_sd said:
I tried to install
|ROM||AROMA|| Padawan JB V2 || PIE || Per App DPI ||4.1.2| 5|31 on my i717 using both CWM and TWRM and both give me the same error after flashing the ROM. It says encryption failure, and tells me to format all my data and try to encrypt it again. I don't have any encryption on my phone, and I did a full wipe of the device prior and after flashing the ROM. I then flash a stock AT&T rom using Odin which worked fine, but then when I reflashed the ROM using both CWM V5.5 and the latest TWRM I still get the same error. I read about how it can be caused by the OS unable to read those paritions, but I followed the directions and it doesn't seem like anyone else is having issues. Can anyone point me in the right direction? Not sure if it matters but I was upgrading off of CM v10
Click to expand...
Click to collapse
FIXED
It had something to do with the SD card. I had a 32 gig card installed, this time I moved the rom to the internal memory and reflashed and it worked perfect. The external card cannot be in the phone. Odd thing is it happend with the official 4.1 release I flashed using Odin as well. Hopefully this will save some poor soul many hours of frustration.
Related
I am trying to install the jellybam 3.0.0 rom and am having no luck. I tried just following inst and that didn't work after about 45 sec the android guy fell over and a red triangle popped up. Then I saw you might have to change to siyah 4.3.3 so I downloaded the zip without micswap and flashed it after the Jellybam rom. Still no luck the rom loaded, but when I rebooted the ics symbol showed up then phone turned of. Can someone tell me how to get this to work. I have the ported version and works fine.
Any help would be greatly appreciated. Also thanks for all you guys and gals do your awsome.
Can't install Jellybam???
fountain79 said:
I am trying to install the jellybam 3.0.0 rom and am having no luck. I tried just following inst and that didn't work after about 45 sec the android guy fell over and a red triangle popped up. Then I saw you might have to change to siyah 4.3.3 so I downloaded the zip without micswap and flashed it after the Jellybam rom. Still no luck the rom loaded, but when I rebooted the ics symbol showed up then phone turned of. Can someone tell me how to get this to work. I have the ported version and works fine.
Any help would be greatly appreciated. Also thanks for all you guys and gals do your awsome.
Click to expand...
Click to collapse
I had the same error....i guess you must be getting a "status 7" error while flashing jellybam.....
I used to run SHOstock3 rom v1.4, and i got the same error while flashing jellybam, so i follwed the method given by one of the experts...
1. I did a factory reset, and flashed jellybam, after which i got a status 7 error...
2. I restored the rom via CWM
3. Flashed siyah v3.4.2 with micswap..
4. since that was siyah ics, i could not use my phone, but i was able to flash jellybam over it.....
5. Im running Jellybam without any bugs...
So basically, you can do a full wipe, flash siyah, and then flash J'bam......else use an older version of siyah like i did....Hope u r problem is solved....
Thanks
Aayush_13 said:
I had the same error....i guess you must be getting a "status 7" error while flashing jellybam.....
I used to run SHOstock3 rom v1.4, and i got the same error while flashing jellybam, so i follwed the method given by one of the experts...
1. I did a factory reset, and flashed jellybam, after which i got a status 7 error...
2. I restored the rom via CWM
3. Flashed siyah v3.4.2 with micswap..
4. since that was siyah ics, i could not use my phone, but i was able to flash jellybam over it.....
5. Im running Jellybam without any bugs...
So basically, you can do a full wipe, flash siyah, and then flash J'bam......else use an older version of siyah like i did....Hope u r problem is solved....
Click to expand...
Click to collapse
Trying now...
Its working
Aayush_13 said:
I had the same error....i guess you must be getting a "status 7" error while flashing jellybam.....
I used to run SHOstock3 rom v1.4, and i got the same error while flashing jellybam, so i follwed the method given by one of the experts...
1. I did a factory reset, and flashed jellybam, after which i got a status 7 error...
2. I restored the rom via CWM
3. Flashed siyah v3.4.2 with micswap..
4. since that was siyah ics, i could not use my phone, but i was able to flash jellybam over it.....
5. Im running Jellybam without any bugs...
So basically, you can do a full wipe, flash siyah, and then flash J'bam......else use an older version of siyah like i did....Hope u r problem is solved....
Click to expand...
Click to collapse
Thanks again for sharing the info very helpful.
did that work
fountain79 said:
Thanks again for sharing the info very helpful.
Click to expand...
Click to collapse
Hi All
Did the method of installing Siyah Kernel and then flashing JellyBam work to resolve "error code 7" issue ??
Hi all,
I've been on the CM 10.1 nightlies for some time now, but wanted to try out CM 10.2. I'm on the ICS bootloaders and was using TWRP 2.6.0.0. After wiping everything but the SD card, and attempting to install 10.2, I've had nothing but bad luck with any ROM I try to install. I can install and boot 10.2 Diamond ROM by AAcount, but as soon as I try to connect to wifi I reboot and get stuck at the CM animation. Any other rom (4.2.2 or 4.3) I try to install can't get passed the Samsung logo or the initial CM animation. I've wiped, reflashed bootloaders, tried CWM 6.0.3.6 and had to resort to adb sideloading my ROM's since I kept getting "failed" messages when trying to install the ROM from the tablet directly.
Does anyone know what I can do to help fix this? (At this point I just want ANYTHING to load/work)
I have the P4WIFI model.
Update 1:
One of the error messages I get when trying to install via TWRP -
"E:Unable to open zip file.
Error flashing zip '/sdcard/Download/gapps-jb-20130813-signed.zip'"
And via adb sideload -
"failed to write data 'protocol fault (no status)'"
Demonic240 said:
Hi all,
I've been on the CM 10.1 nightlies for some time now, but wanted to try out CM 10.2. I'm on the ICS bootloaders and was using TWRP 2.6.0.0. After wiping everything but the SD card, and attempting to install 10.2, I've had nothing but bad luck with any ROM I try to install. I can install and boot 10.2 Diamond ROM by AAcount, but as soon as I try to connect to wifi I reboot and get stuck at the CM animation. Any other rom (4.2.2 or 4.3) I try to install can't get passed the Samsung logo or the initial CM animation. I've wiped, reflashed bootloaders, tried CWM 6.0.3.6 and had to resort to adb sideloading my ROM's since I kept getting "failed" messages when trying to install the ROM from the tablet directly.
Does anyone know what I can do to help fix this? (At this point I just want ANYTHING to load/work)
I have the P4WIFI model.
Click to expand...
Click to collapse
Last time I experienced something like that, the culprit was inadequate memory. Take a look at that.
Secondly, when you said you wiped everything, hope it includes formatting system under Mounts and Storages. If it doesn't then you need to do it for a clean installation.
Cheers.
Sent from my GT-P7500 using xda app-developers app
John Kester said:
Last time I experienced something like that, the culprit was inadequate memory. Take a look at that.
Secondly, when you said you wiped everything, hope it includes formatting system under Mounts and Storages. If it doesn't then you need to do it for a clean installation.
Cheers.
Sent from my GT-P7500 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I formatted system as well. I should still have a few gigs free on the tablet.
Updated OP with more info.
Tried reflashing to stock?
Sent from my GT-P7500 using Tapatalk HD
eushaun99 said:
Tried reflashing to stock?
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
No, had an issue just flashing in general. I'm not sure how/why, but I wiped my entire internal SD and managed to install DiamondROM + PA Gapps and was able to boot up.
Ok so i previously flashed to both 4.2 and 4.3 JB roms, I then flashed to the newer kitkat cm11 rom and everything worked fine for about 3 days and all of a sudden google apps stopped accepting mobile data and only wifi would work. I then attempted to flash back to 4.3.1 and got the build prop error which is where i am now stuck. I have successfully got back to EH03 but anytime i follow the guide to flash to a JB rom i get the build prop error or if i remove that check from the zip it begins installing the rom and resets 3 seconds later to get stuck in bootloop only showing kernal and "Samsung CWM" screen. What am i missing here? thanks in advance.
I had this same problem. I just flashed the a 4.3 devil kernel from hhp's thread in the general section, rebooted to recovery, then flashed back to a 4.3 ROM.
Sent from my SCH-I500 using xda app-developers app
m3fletcher3 said:
Ok so i previously flashed to both 4.2 and 4.3 JB roms, I then flashed to the newer kitkat cm11 rom and everything worked fine for about 3 days and all of a sudden google apps stopped accepting mobile data and only wifi would work. I then attempted to flash back to 4.3.1 and got the build prop error which is where i am now stuck. I have successfully got back to EH03 but anytime i follow the guide to flash to a JB rom i get the build prop error or if i remove that check from the zip it begins installing the rom and resets 3 seconds later to get stuck in bootloop only showing kernal and "Samsung CWM" screen. What am i missing here? thanks in advance.
Click to expand...
Click to collapse
I always flash the sc3 rom before flashing a jb rom. Always works for me. If I don't flash, then I have problems depending on which jb rom i try to flash.
I was just on the MJ9 firmware had no problem flashing other roms using TWRP. I read that TWRP was having issues flashing ND7 and seen that using Philz was the best thing to use, so I downloaded Philz and saved it, uploaded it to my external SD card along with the other required files for ND7. Rebooted to the recovery formatted the internal storage,dalvik and cache. First thing I did was try to install Philz. I instantly got failed and this message "assert failed: getprop (ro.product.device") I thought it had something to do with the Kitkat update. But, then I read on the forum that one user was having trouble installing Philz also and the user installed the ND7 first then Philz and it installed. So, I decided to try that. The update installed just fine but Philz still gave me the same error. I decided to try to install the radio that gave me the same error. I already had Liquid smooth 4.4 downloaded on my SD card and that wouldn't flash either but the gapps installed. I have installed the newest version of TWRP still no luck. I can't even use Airdroid to transfer to either SD card or internal storage (Later found out its an app problem). What else can I do to get the ball rolling?
DCVR 614 said:
I was just on the MJ9 firmware had no problem flashing other roms using TWRP. I read that TWRP was having issues flashing ND7 and seen that using Philz was the best thing to use, so I downloaded Philz and saved it, uploaded it to my external SD card along with the other required files for ND7. Rebooted to the recovery formatted the internal storage,dalvik and cache. First thing I did was try to install Philz. I instantly got failed and this message "assert failed: getprop (ro.product.device") I thought it had something to do with the Kitkat update. But, then I read on the forum that one user was having trouble installing Philz also and the user installed the ND7 first then Philz and it installed. So, I decided to try that. The update installed just fine but Philz still gave me the same error. I decided to try to install the radio that gave me the same error. I already had Liquid smooth 4.4 downloaded on my SD card and that wouldn't flash either but the gapps installed. I have installed the newest version of TWRP still no luck. I can't even use Airdroid to transfer to either SD card or internal storage (Later found out its an app problem). What else can I do to get the ball rolling?
Click to expand...
Click to collapse
Seems like you still have the wrong TWRP for your device.
Here is a Philz Zip with the getprop asserts removed, so it should flash just fine in your current TWRP.
gr8nole said:
Seems like you still have the wrong TWRP for your device.
Here is a Philz Zip with the getprop asserts removed, so it should flash just fine in your current TWRP.
Click to expand...
Click to collapse
That installed and worked. The ND7 Radio also installed. How do I fix the getprop asserts?
gr8nole said:
Seems like you still have the wrong TWRP for your device.
Here is a Philz Zip with the getprop asserts removed, so it should flash just fine in your current TWRP.
Click to expand...
Click to collapse
Okay, I got liquid smooth installed along with the gapps. Thank you for all your help. What can I do to get this get props corrected?
DCVR 614 said:
Okay, I got liquid smooth installed along with the gapps. Thank you for all your help. What can I do to get this get props corrected?
Click to expand...
Click to collapse
It is already fixed now that you have a proper i605 recovery installed.
Sent from my SCH-I605
gr8nole said:
It is already fixed now that you have a proper i605 recovery installed.
Sent from my SCH-I605
Click to expand...
Click to collapse
OH! Thank you so much. I appreciate your help!
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