I have downloaded a few roms for my AT&T I717 Note.
WhenI try to install them via CWM I get an error STATUS 7 , "this package is for SGH-I717 quincyatt. devices; this is a i717"
Under the battery it shows it as a GT-I717.
I cant seem to find a Rom for it
I had flashed this ROM
KIES_HOME_I717UCMD3_I717ATTMD3_1117019_REV02_user_low_ship.tar.md5 before trying to install the other ROMs
confrontation said:
I have downloaded a few roms for my AT&T I717 Note.
WhenI try to install them via CWM I get an error STATUS 7 , "this package is for SGH-I717 quincyatt. devices; this is a i717"
Under the battery it shows it as a GT-I717.
I cant seem to find a Rom for it
I had flashed this ROM
KIES_HOME_I717UCMD3_I717ATTMD3_1117019_REV02_user_low_ship.tar.md5 before trying to install the other ROMs
Click to expand...
Click to collapse
Your recovery simply needs updated. Make sure you have the newer files.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
Your recovery simply needs updated. Make sure you have the newer files.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I'm having the same problem. Can define how to 'update' a recovery and point me to an explanation of how to do it? Thanks
pstrulm said:
I'm having the same problem. Can define how to 'update' a recovery and point me to an explanation of how to do it? Thanks
Click to expand...
Click to collapse
What recovery are you running now?
CWM 6.?.?.?.
TWRP 2.?.?.?
Are you getting status 7?
What are you trying to flash?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
What recovery are you running now?
CWM 6.?.?.?.
TWRP 2.?.?.?
Are you getting status 7?
What are you trying to flash?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks captemo. Checked CWM and it's 5.5.0.4. Sounds like a problem, doesn't it? The ROM was Beanstalk 4.4.4001 - 20140621 - quincyatt_2.zip. The bezel on my Note is not designated ATT, so I'm wondering if it will not accept this ROM. The label under the battery simply says "Samsung SGH-i717".
Thanks again for any help.
pstrulm said:
Thanks captemo. Checked CWM and it's 5.5.0.4. Sounds like a problem, doesn't it? The ROM was Beanstalk 4.4.4001 - 20140621 - quincyatt_2.zip. The bezel on my Note is not designated ATT, so I'm wondering if it will not accept this ROM. The label under the battery simply says "Samsung SGH-i717".
Thanks again for any help.
Click to expand...
Click to collapse
Thats a pretty old version and many KK roms wont flash with them.
There is a TWRP 2.7.1.0 from Gimmieorilltell in Development.
There is also an update CWM Touch, I beleive 6.0.4.7
Both of them are flashable zips. Download and flash like any rom. Once you boot up into whatever rom you are now on, or I guess you could pull battery, but next time you boot into recovery your new one will be there.
TWRP is super easy.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Wow! I'm feeling pretty dumb here, but when I attempt to flash the TWRP 2.7.1.0 zip through CWM 5.5.0.4, it returns:
"Installing update. . .
assert failed: getprop("ro.build.product") == "SGH - I727" getprop("ro.product.device") == "skyrocket"
getprop("ro.build.product") == "skyrocket"
E:Error in /emmc/jjd-openreovery-twrp-skyrocket-2.7.1.0.zip
(Status 7)
Installation aborted.
And when I attempt CWM 6.0.4.7, it defaults back to 5.5.0.4 when I reboot into recovery. Any ideas? These are not supposed to be installed through Odin3, are they?
pstrulm said:
Wow! I'm feeling pretty dumb here, but when I attempt to flash the TWRP 2.7.1.0 zip through CWM 5.5.0.4, it returns:
"Installing update. . .
assert failed: getprop("ro.build.product") == "SGH - I727" getprop("ro.product.device") == "skyrocket"
getprop("ro.build.product") == "skyrocket"
E:Error in /emmc/jjd-openreovery-twrp-skyrocket-2.7.1.0.zip
(Status 7)
Installation aborted.
And when I attempt CWM 6.0.4.7, it defaults back to 5.5.0.4 when I reboot into recovery. Any ideas? These are not supposed to be installed through Odin3, are they?
Click to expand...
Click to collapse
I'll help you get TWRP 2.7 on your phone. Download it here: https://drive.google.com/file/d/0ByoEy8x_JgpqTHRvRk5PVjhXTlE/edit?usp=sharing
Then use Odin 3.07 available here https://drive.google.com/file/d/0ByoEy8x_JgpqbUt3WEl3YzZxWFE/edit?usp=sharing to flash it with.
(You'll have to copy and paste the links because I'm still a new member.)
You will flash Odin in the PDA slot. Make sure only Auto Reboot and F. Reset Time options are checked.
Both of the links above are to my google drive so I know the files work. Good luck! Let me know how it went.
(I'm sure you know this but I'm tired and just to be safe, Volume down and power button on your phone at the same time for download mode. You'll need to enter it to use Odin.)
pstrulm said:
Wow! I'm feeling pretty dumb here, but when I attempt to flash the TWRP 2.7.1.0 zip through CWM 5.5.0.4, it returns:
"Installing update. . .
assert failed: getprop("ro.build.product") == "SGH - I727" getprop("ro.product.device") == "skyrocket"
getprop("ro.build.product") == "skyrocket"
E:Error in /emmc/jjd-openreovery-twrp-skyrocket-2.7.1.0.zip
(Status 7)
Installation aborted.
And when I attempt CWM 6.0.4.7, it defaults back to 5.5.0.4 when I reboot into recovery. Any ideas? These are not supposed to be installed through Odin3, are they?
Click to expand...
Click to collapse
This is making me think you are not reading OP. I have used both files and never had "skyrocket" anything. Did you get files from right place.
If you read OP's you may have seen that these are flashable zips. There are file that will go through Odin, but flashing like rom is just so easy.
Let us know how it goes and dont forget to thank the pereon who provided with Odin files. Sorry cant remember name while typing here.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Thanks to all, but I'm in a big mess now. I downloaded TWRP, downloaded through Odin, was up and running well. Backed up system in TWRP, re-attempted to flash Beanstalk, but no luck. Wiped and tried to restore original backup . . . nothing! Now after several attempts, my phone won't even turn on and go into TWRP. Am I finished? The Samsung Galaxy Note will not boot to anything. In fact there is no response with phone even with fully charged battery. Heeeellllllllpppppp!
pstrulm said:
Thanks to all, but I'm in a big mess now. I downloaded TWRP, downloaded through Odin, was up and running well. Backed up system in TWRP, re-attempted to flash Beanstalk, but no luck. Wiped and tried to restore original backup . . . nothing! Now after several attempts, my phone won't even turn on and go into TWRP. Am I finished? The Samsung Galaxy Note will not boot to anything. In fact there is no response with phone even with fully charged battery. Heeeellllllllpppppp!
Click to expand...
Click to collapse
You got right device file???
Can you get download mode???
Flick the back of phone a couple time with finger. Stuck power button can be common. Dont be afraid to flick pretty good. Dont hurt finger though. Button may sound or feel normal, but could still be stuck.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
try to pull the battery out, once out hold down both volume buttons along with power button, put battery back in while still holding all three buttons and see if it gets you into download mode. I had the same issue when upgrading cwm to twrp 2.7.1.0 a few days ago, I got stuck in a bootloop like you and only way I recovered was going back to stock and work my way back up to 4.4.4. I havnt upgraded to twrp yet but when I do this time I'm extracting the recovery. IMG and using flashify to flash it this time around.
Sent from my Half Baked Vibrant
I hate to ask this question but it needs to be asked. Are you absolutely positive that you have a Galaxy Note i717?
The reason I ask is that "Skyrocket" is the designation for the Galaxy II.....i727.
Sent from my SM-T310 using XDA Premium 4 mobile app
Related
Instructions
- Download the ED01 Update
- Rename is “update.zip”
- Place it on your SD card
- Power off your Device
- Boot into “Recovery Mode”
- Run “Apply sdcard:update.zip”
Congratulations, you are now on Android 2.2.1!
youdaman!
Now we just need to debloat it
Ya, will probably check it out once its debloated.
pntballer505 said:
Ya, will probably check it out once its debloated.
Click to expand...
Click to collapse
I'm sure Adrynaline is on the case right now
Mirror: http://filevo.com/pvoy6q2ou8uy.html
Can someone post the odin file for ED01 when you get a chance. Not a demand, but a simple request when you get a chance.
Can someone pull the new Browser.apk out of this please?
RacerXFD said:
Can someone post the odin file for ED01 when you get a chance. Not a demand, but a simple request when you get a chance.
Click to expand...
Click to collapse
Patience is virtue
Will this reset/delete all data for a stock 2.1 fascinate
Sent from my SCH-I500 using XDA App
bigmike88 said:
Will this reset/delete all data for a stock 2.1 fascinate
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Nope! It will keep your data
I have voodoo do I need to disable it? Do I delete the update.zip on sd already? Thanks for any help
Sent from my SCH-I500 using XDA Premium App
Error while updating.
I'm getting a assert failed : file_getprop("/system/build.prop" CH-I500/SCH-I500:2.1-update1/ECLAIR/EA28:user/release-keys" || file_getprop("/system/build.prop". "ro.build.fingerprint") == "verizon/SCH-I500/SCH-I500/SCH-I500:2.2.1/FROYO/ED01:user/release-keys"
E:Error in /sdcard/update.zip
(status 7)
Installaton aborted.
jatilq said:
I'm getting a assert failed : file_getprop("/system/build.prop" CH-I500/SCH-I500:2.1-update1/ECLAIR/EA28:user/release-keys" || file_getprop("/system/build.prop". "ro.build.fingerprint") == "verizon/SCH-I500/SCH-I500/SCH-I500:2.2.1/FROYO/ED01:user/release-keys"
E:Error in /sdcard/update.zip
(status 7)
Installaton aborted.
Click to expand...
Click to collapse
Same. And I know my system is on EA28......
You need to be on stock EA28, and you need to make sure it is update.zip not update.zip.zip
StDevious said:
youdaman!
Now we just need to debloat it
Click to expand...
Click to collapse
Correct me if I'm wrong, but I believe it has been stated about a million times that this is the same build as EC01 which has been released by Adryn—he has debloated and debinged it.
I also couldn't update from downloading from the thread. OTA went fine. Data is all there, but home screens all [email protected]#ed up. I don't remember what icons I had out there, damn it.
Will this work if i have removed a few pre installed apps like CityID, VZ Naz and Skype. these all shipped with the device but i have removed them.
I tried the OTA update and it failed.
Here's a question I've hot for everyone..
My girlfriends fascinate is stock...but hasn't been able to upgrade...she's still on dh12!! We search update and te di01 or w.e appears but always fails with some ip error or something?
I downloaded the official ed01 zip and put on her sdcard and booted into stock recovery...updated.zip.. and that failed....
Ideas?
Sent from my SCH-I500 using Tapatalk
Are you making sure that wi-fi is turned off prior to checking for an update? It will not working on older eclair versions if wi-fi is on.
the update turns off the wifi when its downloding the update, are you saying i should manually turn it off and then get the update?
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
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.
I am new to rooting devices only tried once with my nexus 4 which was unsuccessful
I have a koodo S4 and i am try to install GOOGLE EDITION 4.4.2 BY Danvdh, Kryten2k35 & Ktoonsez, everything went smoothly i use odin and root then i place my phone in recovery mode browse for the zip select it it run for a few seconds then it comes up e singnature verification fail continue running then the phone restart. can some one tell me what i am missing give me a link for each little step
viptoppa said:
I am new to rooting devices only tried once with my nexus 4 which was unsuccessful
I have a koodo S4 and i am try to install GOOGLE EDITION 4.4.2 BY Danvdh, Kryten2k35 & Ktoonsez, everything went smoothly i use odin and root then i place my phone in recovery mode browse for the zip select it it run for a few seconds then it comes up e singnature verification fail continue running then the phone restart. can some one tell me what i am missing give me a link for each little step
Click to expand...
Click to collapse
Are you flashing through a custom recovery, twrp, cwm etc ect? Original Android Development Roms like CM11, PA, Google Play edition usually have a device check in the beginning of their updater-scripts.. For exmaple:
Code:
assert(getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||
getprop("ro.product.device") == "t0ltecdma" || getprop("ro.build.product") == "t0ltecdma" ||
getprop("ro.product.device") == "i605" || getprop("ro.build.product") == "i605" ||
getprop("ro.product.device") == "SCH-I605" || getprop("ro.build.product") == "SCH-I605" || abort("This package is for \"t0ltevzw,t0ltecdma,i605,SCH-I605\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
This basically tells the phone which devices can be used, in laymans terms..
If you phone is not listed in that updater-script it will not allow you to flash it..
(BTW this is from a ROM from my phone, but same instance)
Report back I will try to help..:highfive:
lacoursiere18 said:
Are you flashing through a custom recovery, twrp, cwm etc ect? Original Android Development Roms like CM11, PA, Google Play edition usually have a device check in the beginning of their updater-scripts.. For exmaple:
Code:
assert(getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||
getprop("ro.product.device") == "t0ltecdma" || getprop("ro.build.product") == "t0ltecdma" ||
getprop("ro.product.device") == "i605" || getprop("ro.build.product") == "i605" ||
getprop("ro.product.device") == "SCH-I605" || getprop("ro.build.product") == "SCH-I605" || abort("This package is for \"t0ltevzw,t0ltecdma,i605,SCH-I605\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
This basically tells the phone which devices can be used, in laymans terms..
If you phone is not listed in that updater-script it will not allow you to flash it..
(BTW this is from a ROM from my phone, but same instance)
Report back I will try to help..:highfive:
Click to expand...
Click to collapse
i am not so sure where i should be looking for the device check if its when installing the rom i didnt see anything like that
Also is rooting your phone and returning to stock more than once a bad thing
viptoppa said:
i am not so sure where i should be looking for the device check if its when installing the rom i didnt see anything like that
Also is rooting your phone and returning to stock more than once a bad thing
Click to expand...
Click to collapse
No. Is your phone unlocked? Like did you go through a process to unlock the bootloader, so your were able to flash a Custom Rom, like the one you posted about? Rooting and Unlocking are two different things..Not being disrespectful/rude just not sure of your knowledge level and trying to help you..
Let me know
Goffered which
lacoursiere18 said:
No. Is your phone unlocked? Like did you go through a process to unlock the bootloader, so your were able to flash a Custom Rom, like the one you posted about? Rooting and Unlocking are two different things..Not being disrespectful/rude just not sure of your knowledge level and trying to help you..
Let me know
Click to expand...
Click to collapse
this is my second time trying to root a device so i have minimum knowledge but i was reading somewhere that the s4 doesnt require bootloader unlock to gain access if thats not the case can you tell me which program is available for the s4 bootloader
viptoppa said:
this is my second time trying to root a device so i have minimum knowledge but i was reading somewhere that the s4 doesnt require bootloader unlock to gain access if thats not the case can you tell me which program is available for the s4 bootloader
Click to expand...
Click to collapse
You need to search your model of your phone..specific carrier.. Post it here and we will do a dual search and ill try to help you figure it out..
lacoursiere18 said:
You need to search your model of your phone..specific carrier.. Post it here and we will do a dual search and ill try to help you figure it out..
Click to expand...
Click to collapse
SGH-I337M KoodoMobile (Canada)
Thanks for the help
Ok.. i found a little something..
http://forum.xda-developers.com/showpost.php?p=42246660&postcount=28
So if that look like your device that he is talking about then you are Unlocked..
Your next step should be to try to download a recovery through RomManager, which you can obtain free in the PlayStore..
Download it, on the main page it should say Recovery Setup. Click it. If you get a error message than there is no recoveries for your device (uh oh! =/) If there is some listed, CWM or TWRP pick one.. let it go through its process.. you should boot into recovery afterwards..
Get there and report back..
lacoursiere18 said:
Ok.. i found a little something..
http://forum.xda-developers.com/showpost.php?p=42246660&postcount=28
So if that look like your device that he is talking about then you are Unlocked..
Your next step should be to try to download a recovery through RomManager, which you can obtain free in the PlayStore..
Download it, on the main page it should say Recovery Setup. Click it. If you get a error message than there is no recoveries for your device (uh oh! =/) If there is some listed, CWM or TWRP pick one.. let it go through its process.. you should boot into recovery afterwards..
Get there and report back..
Click to expand...
Click to collapse
am goin to give this a try and will report back right away
lacoursiere18 said:
Ok.. i found a little something..
http://forum.xda-developers.com/showpost.php?p=42246660&postcount=28
So if that look like your device that he is talking about then you are Unlocked..
Your next step should be to try to download a recovery through RomManager, which you can obtain free in the PlayStore..
Download it, on the main page it should say Recovery Setup. Click it. If you get a error message than there is no recoveries for your device (uh oh! =/) If there is some listed, CWM or TWRP pick one.. let it go through its process.. you should boot into recovery afterwards..
Get there and report back..
Click to expand...
Click to collapse
so i have install flash recovery i was ask to upgrade to flash clockworkmod touch is that necessary if yes how do i do it manually
viptoppa said:
so i have install flash recovery i was ask to upgrade to flash clockworkmod touch is that necessary if yes how do i do it manually
Click to expand...
Click to collapse
You can try it.. some newer roms a spereatic when it comes to recoveries or it could be the other way around..Just hit yes and let it do it's thing..
Manually you can go unto CWM and find your device and recovery.tar or zip..
But let the app do it..:good:
lacoursiere18 said:
You can try it.. some newer roms a spereatic when it comes to recoveries or it could be the other way around..Just hit yes and let it do it's thing..
Manually you can go unto CWM and find your device and recovery.tar or zip..
But let the app do it..:good:
Click to expand...
Click to collapse
am intersted in google edition rom can any rom manager install it cause it fail once again
Post your recovery log here after attempting to flash. .
Sent from my SCH-I605 using xda app-developers app
viptoppa said:
am intersted in google edition rom can any rom manager install it cause it fail once again
Click to expand...
Click to collapse
Did you flash the recovery or update it? Or did you try just re flashing that Rom?
Sent from my SCH-I605 using xda app-developers app