After along struggle to get my phone unlocked and rooted I have tried flashing many roms but every time I try I get:
assert failed: getprop("ro,product.device") == "p769" ......
and it shows the android with the red exclamation point in the background.
I have made sure that every rom I attempt to flash is for p769. Any advice?
The assert line can be removed in the flash script its one of the first few lines. If they are meant for your phone I'm not sure why you would get the error
Sent from my LG-P769 using xda app-developers app
I have the same issue, found a solution here:
http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/182438-solved-assert-failed.html
omgbossis21 said:
The assert line can be removed in the flash script its one of the first few lines. If they are meant for your phone I'm not sure why you would get the error
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Yeah I tried that yesterday and it soft bricked my phone. would give me security error at start up and I couldn't get to recovery. It was hard to get it back. Any ideas what would be causing this problem in the first place before I possibly brick my phone again.
So I looked at my device and my ro.product.device=u2
All the roms I try though also have u2 in the assert lines. So I assume it should work. I don't know very much about this assert stuff
every time i download the new CM anton release i unzip it and remove the assert lines, re-zip and works like a charm... if i dont i get the same error. never has my phone soft bricked. can you get into CWM? which rom are you trying to flash?
Strange that you need to do this. I set "u2", p769", and "p760" (for compatibility with older ROMs) as accepted devices in the assert. I wonder if it has something to do with CWM version that you are using. I use TWRP and it seems to work fine.
AntonX said:
Strange that you need to do this. I set "u2", p769", and "p760" (for compatibility with older ROMs) as accepted devices in the assert. I wonder if it has something to do with CWM version that you are using. I use TWRP and it seems to work fine.
Click to expand...
Click to collapse
that has to be it.. cwm i mean. I use Artas CWM.. maybe there is something in there that needs to be tweaked.
Where can I get a CWM or TWRP .img that I can flash on p769. Or are they they same for all optimus l9 versions?
AntonX said:
Strange that you need to do this. I set "u2", p769", and "p760" (for compatibility with older ROMs) as accepted devices in the assert. I wonder if it has something to do with CWM version that you are using. I use TWRP and it seems to work fine.
Click to expand...
Click to collapse
For me I still have to remove the assert every time I update CM. I use CWM 1.5 (from here http://forum.xda-developers.com/showthread.php?t=2095825). Not a big issue as I know how to edit zip file, but Anton I think you should investigate.
mrmathematica said:
For me I still have to remove the assert every time I update CM. I use CWM 1.5 (from here http://forum.xda-developers.com/showthread.php?t=2095825). Not a big issue as I know how to edit zip file, but Anton I think you should investigate.
Click to expand...
Click to collapse
I'm not sure what I can do about it. TWRP works just fine, the script seems to be correct and it's actually generated by CM build environment. Would be interesting to trace this CWM code and see why exactly does it fail. @artas182x, can you help?
well I tried to remove the assert lines again and now I'm stuck in with a security error again. I'm having troubles getting it back. I can only access s/w update and fastboot. Flashing the KDZ doesn't seem to find the phone. any tips or other threads you can recomend?
Artas182x recovery identifies phone as p940
It includes its own build prop with device defined as p940
Lelus said:
Artas182x recovery identifies phone as p940
It includes its own build prop with device defined as p940
Click to expand...
Click to collapse
Oh, that explains it.
I really don't want to add p940 to the script though, just don't seem right.
Related
First of all, I'm a newb here.
Second, i have watched the noob video when signing up. I must say, best TOS ever.
Third, I'm 14 years old. But that doesn't make me incompetent with technology, or grammar. I have successfully installed numerous leaked OSes on my BlackBerry Torch, and I fell very comfortable with both my Galaxy Tab and my Torch.
Alright, now to the question/issue.
When attempting to install CM10 (available at Droidbasement), I continually have CMR reply with:
"Installing Update.
Installation Aborted."
First, I must say, I did circumvent the first line in the update script to bypass the "p4" check, as it was giving me an error before (my device is the P7500R (Rogers)).
Second, perhaps I am just doing something wrong, but I cannot use fastboot or adb. Windows 8 does not seem to like any of the drivers.
Now, what could be causing this "Installation Aborted" error, and what can I do to solve it?
I am running the latest version of CMR Touch. I found an md5 and flashed it with ODIN (apparently odin works, but not fastboot)
Again, I apologize if I am a newb, but I'm tired of waiting for Samsung to release ICS, but by the time they do, it is already outdated by a few months! Sorry if I know nothing, but I am trying my best
First welcome here
In order to install rom from droidbasement you have to flash the recovery in the same folder than the cm rom
I don't know your device how it is different ? (7500R ?)
Can you say more about the error in CWM ? (Error code ?)
Sent with my GT-P7500 CM10
A) where is the supplied recovery?
B) The blof said I only had to use the supplied one if not on CMR5+, I am on a variant of 5.8 I believe
C) It isn't that my device is different, it is that it gave me an error on the "p4" check line
I apologize for any typos, sent from my BlackBerry
you should not modify anything in the zip. there is no reason to. the assert check is there for a reason.
to flash any of those builds, you need a recovery which supports it. CWM5 or CWM6 from DB both work. you can find these on droidbasement.
the server has been having issues, so your download may be corrupted in some form. the server is being worked on, and should be back by this weekend.
pershoot said:
you should not modify anything in the zip. there is no reason to. the assert check is there for a reason.
to flash any of those builds, you need a recovery which supports it. CWM5 or CWM6 from DB both work. you can find these on droidbasement.
the server has been having issues, so your download may be corrupted in some form. the server is being worked on, and should be back by this weekend.
Click to expand...
Click to collapse
Well, that did the trick. Installed 5.5.0.4 from DB, and it accepted it! I though using a new version would work better, but pershoot eveidently modified this one? (Correct me if I'm wrong)
Rebooting as I type.
Running now.
All I can say is WOW
This truly is amazing.
Amazing job from pershoot, the CyanogenMod team, and of course, Google!
asd
Nicocolton said:
Running now.
All I can say is WOW
This truly is amazing.
Amazing job from pershoot, the CyanogenMod team, and of course, Google!
Click to expand...
Click to collapse
hey bro, i have same problem/.
warning
:assert failed : getprop ("ro.product.device") == "p4" || getprop("rp.build.product") == "p4" E:Error in /sdcard/cm-10-20120814-EXPERIMENTAL- P4.zip (status 7) installetion aborted .
why?
crazyflower said:
hey bro, i have same problem/.
warning
:assert failed : getprop ("ro.product.device") == "p4" || getprop("rp.build.product") == "p4" E:Error in /sdcard/cm-10-20120814-EXPERIMENTAL- P4.zip (status 7) installetion aborted .
why?
Click to expand...
Click to collapse
Use this recovery. Flash it with ODIN.
droidbasement
.com
/db-blog/?p=2487
Look it isn't even my own link, I apologize to the mods if I am breaking a rule by circumventing the "no links to new users rule" but I'm just trying to help.
Nicocolton said:
Use this recovery. Flash it with ODIN.
droidbasement
.com
/db-blog/?p=2487
Look it isn't even my own link, I apologize to the mods if I am breaking a rule by circumventing the "no links to new users rule" but I'm just trying to help.
Click to expand...
Click to collapse
thank u very much ~~try it soon ...
---------- Post added at 03:24 AM ---------- Previous post was at 02:53 AM ----------
Nicocolton said:
Use this recovery. Flash it with ODIN.
droidbasement
.com
/db-blog/?p=2487
Look it isn't even my own link, I apologize to the mods if I am breaking a rule by circumventing the "no links to new users rule" but I'm just trying to help.
Click to expand...
Click to collapse
great!!!!!! thank u very much !!!! haha :good:
I'm running the latest stock firmware and Siyah kernel. I tried to flash the latest version of the LiquidSmooth rom and receievd the error:
assert failed: getprop ("ro.product.device") == "d2aat" l l getprop ("ro.build.product") == "d2att"
E: Error in /emmc//Liquid-JB-v2.0-RC5-d2att.zip
(status 7)
Installation aborted.
I did some searching and concluded that my outdated version of cwm is causing the problem. I first attempted to upgrade to the latest version of Touch cwm with Rom manager but was unable to install the update because apparently there was an "Error while downloading from server." I tried about 10 times on both wifi and 3g to avail. I then attempted to manually flash Touch v.6.0.3.5 from a .zip file in my current version of cwm (non-touch v.6.0.3.2) and although it said 'install from sdcard complete', when I reboot into recovery I'm still on the 6.0.3.2 version, the update won't stick. I tried multiple times but I just can't get it to overwrite my current version of cwm. Lastly I tried flashing Touch v.6.0.3.5 with a .tar file via oOdin. Odin said the flash was successful but when I tried to boot into recovery it got stuck on the Samsung logo. I just used Rom manager to flash back to 6.0.3.2 and now I'm back to square one.
All I want to do is update my recovery! Why is this so difficult? :crying:
I'd greatly appreciate any advice you can offer.
Anyone? Sorry, I know bumping is kind of obnoxious but I'm really stuck here.
kilgorcalrizian said:
Anyone? Sorry, I know bumping is kind of obnoxious but I'm really stuck here.
Click to expand...
Click to collapse
Try PhilZ Touch recovery. And as far as I know 6.0.3.5 isn't ready for the S3 yet so maybe that's why you're having problems.
kilgorcalrizian said:
Anyone? Sorry, I know bumping is kind of obnoxious but I'm really stuck here.
Click to expand...
Click to collapse
More to the point its against the rules .
As said try Philz do not use Rom Manager .
jje
Try PhilZ Touch recovery.
Click to expand...
Click to collapse
Thanks for replying. I successfully flashed PhilZ recovery so that's a step in the right direction. However I still can't flash Liquid Smooth. When I select 'install from .zip' and then 'choose file from sd card' the Liquid Smooth zip file isn't there (even though it is definitely the on the root of my SD card), it was detected on my previous version of cwm but not on PhilZ for some reason. When I select 'choose file from sd card' all I see is a directory called 'clockworkmod /', when I select that it just says 'no files found.' What am I doing wrong?
More to the point its against the rules .
Click to expand...
Click to collapse
Sorry, I won't do it again.
You don't sound too big on reading information, try following the instructions for philz interface as it sounds like you're looking at your internal sd card.
boomboomer said:
You don't sound too big on reading information, try following the instructions for philz interface as it sounds like you're looking at your internal sd card.
Click to expand...
Click to collapse
I actually did skim the entire page (http://forum.xda-developers.com/showthread.php?t=2201860) and couldn't find any help. After reading your post I also did a control+g search for the word 'sdcard' and couldn't find the information you alluded to. Anyway, I moved the Liquid Smooth zip to my external SD card as your post implied I should. I can see the zip now so thanks. However, when I try to flash it, I'm still getting the exact same error as I was on my original version of cwm:
assert failed: getprop ("ro.product.device") == "d2aat" l l getprop ("ro.build.product") == "d2att"
E: Error in /emmc//Liquid-JB-v2.0-RC5-d2att.zip
(status 7)
Installation aborted.
kilgorcalrizian said:
I actually did skim the entire page (http://forum.xda-developers.com/showthread.php?t=2201860) and couldn't find any help. After reading your post I also did a control+g search for the word 'sdcard' and couldn't find the information you alluded to. Anyway, I moved the Liquid Smooth zip to my external SD card as your post implied I should. I can see the zip now so thanks. However, when I try to flash it, I'm still getting the exact same error as I was on my original version of cwm:
assert failed: getprop ("ro.product.device") == "d2aat" l l getprop ("ro.build.product") == "d2att"
E: Error in /emmc//Liquid-JB-v2.0-RC5-d2att.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
EDIT: Just tried TWRP and I'm still getting the 'assert failed' error. This is getting so frustrating!
kilgorcalrizian said:
EDIT: Just tried TWRP and I'm still getting the 'assert failed' error. This is getting so frustrating!
Click to expand...
Click to collapse
Ask in the roms thread .
Or totally wipe your phone and start from stock .
jje
JJEgan said:
Ask in the roms thread .
Or totally wipe your phone and start from stock .
jje
Click to expand...
Click to collapse
I've already tried wiping so I'll head over the official Liquid Smooth thread and see if anyone there can help me out. Thanks for trying to help everyone, at least we've ruled out the possibility that it's a recovery issue.
Looking at the error you are trying to flash the AT& T VERSION!
slaphead20 said:
Looking at the error you are trying to flash the AT& T VERSION!
Click to expand...
Click to collapse
Thanks but I'm definitely, flashing the i9300 version, I copied the error from another thread and forgot to edit the version.
EDIT: I am the biggest idiot in the world. It turns out I was using the AT & T version, know idea how the hell I managed to miss that. I guess Boomer was right, I do suck at reading information. Sorry for wasting everyone's time. Thank you so much Slaphead!
kilgorcalrizian said:
Thanks but I'm definitely, flashing the i9300 version, I copied the error from another thread and forgot to edit the version.
EDIT: I am the biggest idiot in the world. It turns out I was using the AT & T version, know idea how the hell I managed to miss that. I guess Boomer was right, I do suck at reading information. Sorry for wasting everyone's time. Thank you so much Slaphead!
Click to expand...
Click to collapse
Well super thanks to you, I had the same issue... the rom didn't flash, but because you realised you made a mistake on the version I double checked mine :silly: as it turns out I was trying to flash the i900... not i9300 rom I feel so dumb
I got my lg l9, tried to go into recovery with vol up + home + power. Then I got a pic from LG service center, do I need to unlock bootloader before installing custom rom, if yes, how? If no, how I go into recovery?
IcemanGFX said:
I got my lg l9, tried to go into recovery with vol up + home + power. Then I got a pic from LG service center, do I need to unlock bootloader before installing custom rom, if yes, how? If no, how I go into recovery?
Click to expand...
Click to collapse
You must unlock your phone bootloader before install any custom rom.
For P768 (this should work with P765 & P760 but I think there're P760 thread somewhere in forum)
http://forum.xda-developers.com/showthread.php?t=2313794
For P769
http://forum.xda-developers.com/showthread.php?t=2277639
Please read about our phone in FAQ here first
http://forum.xda-developers.com/showthread.php?t=2242239
artit said:
You must unlock your phone bootloader before install any custom rom.
For P768 (this should work with P765 & P760 but I think there're P760 thread somewhere in forum)
http://forum.xda-developers.com/showthread.php?t=2313794
For P769
http://forum.xda-developers.com/showthread.php?t=2277639
Please read about our phone in FAQ here first
http://forum.xda-developers.com/showthread.php?t=2242239
Click to expand...
Click to collapse
HELP ME!!!!!!!!!!!!! I got the drivers installed correctly, but I think I've got a wrong version of the stock rom, can't get it unlocked, got a p760 too but okay, KDZ install thingy laggs and automatic close in itself HELP
IcemanGFX said:
HELP ME!!!!!!!!!!!!! I got the drivers installed correctly, but I think I've got a wrong version of the stock rom, can't get it unlocked, got a p760 too but okay, KDZ install thingy laggs and automatic close in itself HELP
Click to expand...
Click to collapse
What is your problem? Can you flash kdz successfully? Please give more information so other people can help you.
Your phone model is P760, right? What is your original rom version on your phone before flash new one?
Which kdz you flash?
And what the problem with your phone?
Got some really good problems now,
If I try to flash the V20H_00.kdz, the tool crashes, i don't know how or why, LG mobile support tool detects mobile, but doesnt want to install a software since the last version is installed already, indeed if I start up the phone, I get a white screen....
I NOW CAN COME INTO CWM, but problem is, I can't install rom because of a problem, it denies, number 7 fould. Maybe because my bootloader still isn't unlocked?
I really don't get it since I had a custom rom already before without any problems... ;S
IcemanGFX said:
Got some really good problems now,
If I try to flash the V20H_00.kdz, the tool crashes, i don't know how or why, LG mobile support tool detects mobile, but doesnt want to install a software since the last version is installed already, indeed if I start up the phone, I get a white screen....
I NOW CAN COME INTO CWM, but problem is, I can't install rom because of a problem, it denies, number 7 fould. Maybe because my bootloader still isn't unlocked?
I really don't get it since I had a custom rom already before without any problems... ;S
Click to expand...
Click to collapse
You can get status 7 error in cwm if your phone model is incompatible with rom.
But I want to make sure your phone boot loader is already unlocked. Did you unlock it? To check this please boot into S/W update mode and see if there're any text print at top of that screen.
artit said:
You can get status 7 error in cwm if your phone model is incompatible with rom.
But I want to make sure your phone boot loader is already unlocked. Did you unlock it? To check this please boot into S/W update mode and see if there're any text print at top of that screen.
Click to expand...
Click to collapse
Got phone fixed again.
THINK I fixed it since there stands unlocked w0000T.
Gooing to install cwm with the app and then try to install the ROM again [email protected]!!
OKay now, please link me a really easy guide to ROOT the phone
Wow, rooted phone succesfully, booted in cwm and got the next thing:
assert failed: getprop("ro.product.device") == "p760" etc etc
E:Error in /external_sd/cm-10.1.3-p760.zip
(status 7)
PLz help, need this done today!!!!!!!!!!!!!
IcemanGFX said:
PLz help, need this done today!!!!!!!!!!!!!
Click to expand...
Click to collapse
If your phone compatible with P760 rom, so you can open cm-10.1.3-p760.zip with zip tool
then browse to and double click
/META-INF/com/google/android/updater-script
open it with text editor and delete line like
assert( ... );
Save zip and try to flash it again.
artit said:
If your phone compatible with P760 rom, so you can open cm-10.1.3-p760.zip with zip tool
then browse to and double click
/META-INF/com/google/android/updater-script
open it with text editor and delete line like
assert( ... );
Save zip and try to flash it again.
Click to expand...
Click to collapse
Ill get this: http://gyazo.com/e51f0d41333dc5f2072da663aef1b28e
What do I need to delete? Please answer FAST
IcemanGFX said:
Ill get this: http://gyazo.com/e51f0d41333dc5f2072da663aef1b28e
What do I need to delete? Please answer FAST
Click to expand...
Click to collapse
Please open it with notepad++ and delete first line.then put it back to zip.
Sent from my Nexus 7 using XDA Premium HD app
artit said:
Please open it with notepad++ and delete first line.then put it back to zip.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Like this: http://gyazo.com/efaca25a0016225c78f799e47e592a3c ?
IcemanGFX said:
Like this: http://gyazo.com/efaca25a0016225c78f799e47e592a3c ?
Click to expand...
Click to collapse
Tried to do, didn't detect the ROM.
IcemanGFX said:
Tried to do, didn't detect the ROM.
Click to expand...
Click to collapse
Yes, that's right. For CWM don't detect rom problem may be you don't zip it properly.
artit said:
Yes, that's right. For CWM don't detect rom problem may be you don't zip it properly.
Click to expand...
Click to collapse
OKAY, this didn't work also, all other pthings like the gapps work with installing, how is it be able that I can't install any rom with a unlocked bootloader? !!!!!!
EDIT: I just get: installing update....
Installation aborted
IcemanGFX said:
OKAY, this didn't work also, all other pthings like the gapps work with installing, how is it be able that I can't install any rom with a unlocked bootloader? !!!!!!
EDIT: I just get: installing update....
Installation aborted
Click to expand...
Click to collapse
CWM recovery has save log to sdcard option (in advanced menu). Please try to save installation log to sdcard and find out what the problem.
What's your phone model? Did you try other rom?
artit said:
CWM recovery has save log to sdcard option (in advanced menu). Please try to save installation log to sdcard and find out what the problem.
What's your phone model? Did you try other rom?
Click to expand...
Click to collapse
I have a LG Optimus L9 P760...
I used the ROM (cm 10.1.3 P760)
I did try another ROM and I got the same error...
Ill wipe cache/factory reset/dalvik cache/mounts and storage wipe data and cache...
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
riekkir said:
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
Click to expand...
Click to collapse
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
es0tericcha0s said:
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
Click to expand...
Click to collapse
No I don't have it atm as I just wiped the data/cache last night but will I already have CWM, I just need to unlock the bootloader and try again...I'm trying to install this one:
Android 4.4.2 KitKat Mokee Rom, and it says the version is a nightly. Yes I'm positive it's the Bell Version as I purchased it at a Bell Store and my carrier is Bell. The error message is "Installation Aborted." It begins installing, and then halfway through I get that error message. How do I fix this?
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960
es0tericcha0s said:
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
Click to expand...
Click to collapse
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
riekkir said:
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
Click to expand...
Click to collapse
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
http://forum.xda-developers.com/showthread.php?t=2619489
For installing recovery:
http://forum.xda-developers.com/showthread.php?t=2262726
es0tericcha0s said:
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
For installing recovery:
Click to expand...
Click to collapse
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
riekkir said:
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
Click to expand...
Click to collapse
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
es0tericcha0s said:
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
Click to expand...
Click to collapse
Okay so I'm trying it now and the program won't even open :/
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
es0tericcha0s said:
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
Click to expand...
Click to collapse
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
riekkir said:
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
Click to expand...
Click to collapse
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
es0tericcha0s said:
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
Click to expand...
Click to collapse
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
riekkir said:
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
Click to expand...
Click to collapse
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
es0tericcha0s said:
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
Click to expand...
Click to collapse
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
riekkir said:
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
Click to expand...
Click to collapse
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
es0tericcha0s said:
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
Click to expand...
Click to collapse
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
riekkir said:
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
Click to expand...
Click to collapse
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
es0tericcha0s said:
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
Click to expand...
Click to collapse
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
riekkir said:
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
Click to expand...
Click to collapse
Oh yea, forgot you have to undo the screws on the bottom. So you scroll down to hit recovery and use the Power button to select and it doesn't do anything? That's odd.. Try and reflash the recovery since you can still get to fastboot. If that doesn't work, you're not totally screwed since you can still get to fastboot, that means you should be able to restore it to stock and start over.
Alternatively, if you have fastboot set up, you could make sure that philz touch is in the fastboot folder and use this command:
fastboot boot recovery nameofphilztouchfile.img
If you don't have fastboot, then just grab this one: http://forum.xda-developers.com/showthread.php?t=2317790 , drop the recovery img in that folder and open the CMD prompt on your computer and change directories to it and run the command.
ATTENTION EVERYONE (For everyone who attempted to install this ROM):
This ROM breaks the Tab splash screen and does harm to the Tablet.
I recommend calling 1-800-SAMSUNG, and ask for a factory re-flash. Do not say anything that you are / were rooted. This should be 100% free, they even pay for shipping. They did mine for free. I recommend doing this ASAP, before more damage might come to the Tablet.
Downloading and testing, do you need anything else? Like the twrp?
edit 1:
Impossible to install, the updater is badly configured, I can not locate the problem, even with normal recovery will not let me install, I will continue to try
edit 2:
Well I found the error, the rom is not well developed, did you do with some automated program? I remember that the tablet 10.1 has another processor and that the compatibility of a direct port without changing the drivers is impossible
jimmy999x said:
Downloading and testing, do you need anything else? Like the twrp?
edit 1:
Impossible to install, the updater is badly configured, I can not locate the problem, even with normal recovery will not let me install, I will continue to try
edit 2:
Well I found the error, the rom is not well developed, did you do with some automated program? I remember that the tablet 10.1 has another processor and that the compatibility of a direct port without changing the drivers is impossible
Click to expand...
Click to collapse
I made it on ES File Explorer, on my Nook, it took me an hour... I had ported it from Acclaim RC5 and Docker 6 Degaswifi, and I changed the updater script to say, "degaswifi", for the device. and I changed the build prop, to be the same cpu, exc... as the tab 4. I used Degaswifi Docker 6 boot.img and recovery folder, and some other important stuff in the system folder. What is the error are you getting?
secretwolf98 said:
I made it on ES File Explorer, on my Nook, it took me an hour... I had ported it from Acclaim RC5 and Docker 6 Degaswifi, and I changed the updater script to say, "degaswifi", for the device. and I changed the build prop, to be the same cpu, exc... as the tab 4. I used Degaswifi Docker 6 boot.img and recovery folder, and some other important stuff in the system folder. What is the error are you getting?
Click to expand...
Click to collapse
Even using other twrp I still can not install, use the recovery and the boot image I found 2 weeks ago, I even deleted the first line and it looked like it would install, but these errors appeared
jimmy999x said:
Even using other twrp I still can not install, use the recovery and the boot image I found 2 weeks ago, I even deleted the first line and it looked like it would install, but these errors appeared
Click to expand...
Click to collapse
Can I see what you had edited?
Only the first line of the updater inside google folder
jimmy999x said:
Only the first line of the updater inside google folder
Click to expand...
Click to collapse
What is in the first line? The new updated one, that you had did?
secretwolf98 said:
What is in the first line? The new updated one, that you had did?
Click to expand...
Click to collapse
this
jimmy999x said:
this
Click to expand...
Click to collapse
strange
I'll look into it later
jimmy999x said:
this
Click to expand...
Click to collapse
Question, after you flashed this rom, did the Splash Screen disappeared on the Samsung?
Because the both versions that I had made, broke my Samsung Splash Screen.
secretwolf98 said:
Question, after you flashed this rom, did the Splash Screen disappeared on the Samsung?
Because the both versions that I had made, broke my Samsung Splash Screen.
Click to expand...
Click to collapse
If, in fact, they stop seeing the logos of samsung when turning on and when entering the download mode, the only way to correct that is to install the official firmware
jimmy999x said:
If, in fact, they stop seeing the logos of samsung when turning on and when entering the download mode, the only way to correct that is to install the official firmware
Click to expand...
Click to collapse
so it did for you, when you flashed official PA1 firmware threw odin? did the screen that broke say, "Samsung Galaxy Tab 4 7.0 SM-T230NU Powered By Android"?
Interested to get this rom running smooth on our tabs