I tried to install that paranoid android rom.I keep getting an error 7. it says no target device found. I've tried 1.9 .4, 1.9 .5, 1.9.6 and now 1.9 .7. It looks like an awesome rom but I can't install it. I get the same error with the cm 10. Presently I'm running the vicious ROM (jellybean). I wipe everything before trying to install the ROM but nothing works. I can install the maguro version with no problems other than I don't have phone service. I want this ROM bad and need some guidance.
Mr. Keith
How are you trying to flash the ROM? In recovery?
Sent from my Nexus 7 using xda premium
El Daddy said:
How are you trying to flash the ROM? In recovery?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yes, clockwork mod. I've also tried to manually do it in recovery, still get the status 7 error. I tried the supersu mod, no success. I have the Verizon gnex. This is week 2 of failed attempts. Do I have to start with a stock rom first?
Hope you are getting roms from Verizon thread not i9250
atifsh said:
Hope you are getting roms from Verizon thread not i9250
Click to expand...
Click to collapse
This.
The reason why you didn't have service with a maguro ROM is because that is for the gsm version.
You want the toro builds. Hopefully you can get your radio back.
if not you'll have to flash the stock Google image.
Sent from my Nexus 7 using xda premium
If you mean status 7 error, I have that with my Vibrant and have to change to a different version of clockworkmod. Try flashing an older version of CWM in fastboot.
eksasol said:
If you mean status 7 error, I have that with my Vibrant and have to change to a different version of clockworkmod. Try flashing an older version of CWM in fastboot.
Click to expand...
Click to collapse
This is likely the OP's issue. There are just too many incompatibilities with the newer recoveries. If you stick with 5.5.0.2 (for maguro), and 5.5.0.4 (for toro), you will see that you will have significantly less issues...
I have a Verizon galaxy nexus with paranoid rom all you do is go back to stick ics and use recovery to flash and it might get stuck in boot screen just take out battery and put back in and should just start up
Sent from my Galaxy Nexus using xda app-developers app
Sucess!!
Thank you, thank you, all of you. I finally installed the rom last night and its truly awesome. I didn't know that rom manager allows you to revert to older cwm versions. That did the trick. I now have some catching up to do.
Thanks again,
Mr. Keith
Related
I'm running AOKP with the CMPlus kernel. I want to encrypt my phone. Every time I try to start the encryption an android appears and the phone reboots. Then it doesn't even try to activate encryption. What can I do to get it encrypted?
Sent from my Galaxy Nexus using xda premium
I guess be glad it is failing. Don't encrypt if on custom rom, it will become difficult to flash ever again (without a full device wipe) and nandroids won't even work after.
good day.
chopper the dog said:
I guess be glad it is failing. Don't encrypt if on custom rom, it will become difficult to flash ever again (without a full device wipe) and nandroids won't even work after.
good day.
Click to expand...
Click to collapse
I'm aware of the difficulty that cones with encryption but since I rooted to record business calls, encryption is a really good idea. Any idea how to get it working? Thanks
Sent from my Galaxy Nexus using xda premium
Don't use a custom kernel, report issue to AOKP dev team.
Sent from my i9250
bk201doesntexist said:
Don't use a custom kernel, report issue to AOKP dev team.
Sent from my i9250
Click to expand...
Click to collapse
I didn't know you couldn't use a custom kernel. I'll try it with straight AOKP
Edit: Even with the stock kernel from AOKP it fails. Phone just reboots. AOKP site also seems to be down right now.
fbiryujin said:
I didn't know you couldn't use a custom kernel. I'll try it with straight AOKP
Edit: Even with the stock kernel from AOKP it fails. Phone just reboots. AOKP site also seems to be down right now.
Click to expand...
Click to collapse
Could be your recovery.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
Could be your recovery.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm using the latest CWM for Galaxy Nexus. What should I use? Thanks
fbiryujin said:
I'm using the latest CWM for Galaxy Nexus. What should I use? Thanks
Click to expand...
Click to collapse
Try going back to stock recovery and see if encryption works. Also, you could try twrp and see if it works there as well.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
Try going back to stock recovery and see if encryption works. Also, you could try twrp and see if it works there as well.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try TWRP first, but if that fails, how do I get stock recovery back? (I'm using the GSM maguro if that makes a difference)
fbiryujin said:
I'll try TWRP first, but if that fails, how do I get stock recovery back? (I'm using the GSM maguro if that makes a difference)
Click to expand...
Click to collapse
To get stock recovery, find your stock 4.0.4 google image and flash the recovery using fastboot.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
To get stock recovery, find your stock 4.0.4 google image and flash the recovery using fastboot.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Even with stock recovery it doesn't work.
Edit: Just tried it with CM9 nightly as well, and the same thing happens. I'd really like to get encryption working.
fbiryujin said:
Even with stock recovery it doesn't work.
Edit: Just tried it with CM9 nightly as well, and the same thing happens. I'd really like to get encryption working.
Click to expand...
Click to collapse
Try going back to stock 4.0.4 ics and encrypting there. If it works, there are some test recoveries that support encryption and you could possibly flash a custom rom on top of it.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
Try going back to stock 4.0.4 ics and encrypting there. If it works, there are some test recoveries that support encryption and you could possibly flash a custom rom on top of it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I'll give it a shot.
i would advise against that;
check this thread, 2nd post
bk201doesntexist said:
i would advise against that;
check this thread, 2nd post
Click to expand...
Click to collapse
Thanks for the warning but I'm aware of that. The latest TWRP can work with encrypted /sdcard though. Plus if I get stuck, I'm told "fastboot erase userdata" will format /sdcard and remove the encryption.
Hello,
New to android... I have searched and searched and read in a LOT of threads trying to get Cyogenmod 10 working on my i747m on Rogers.
I have found many guides and have managed to root my phone and tried installing Cy10 but got an error 7. I read that this was because of the wrong recovery version. I was told to get ROM manager and update through there. For me, however, the GS3 doesn't show up in the options.
Could someone please link me the correct files that I need? I think I know the steps, but it seems that all the files have different versions and are not compatible.
I'm trying to be very careful and not brick my phone, so I am reluctant to try anything that I'm not sure will work... I think that's why this is difficult (Rogers = AT&T? or not?, etc.)
Thank you in advance to anyone who is willing to take the time to help me.
I had the exact same problem as you and what I did was flash, if I remember, cm9 and go to ROM manager and then it would show me Samsung Galaxy s3(att).
You need to update your recovery I flashed the touch recovery from the toolkit and that worked for me
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
First: Thank you both for your replies!
zap12341 said:
I had the exact same problem as you and what I did was flash, if I remember, cm9 and go to ROM manager and then it would show me Samsung Galaxy s3(att).
Click to expand...
Click to collapse
Do you remember which version of cm9? I tried that last night and I still got error 7, but maybe I used the wrong version. All I could find were nightlies, no stable ones for d2att (which is what I was told was our phone)
offwiththeface said:
You need to update your recovery I flashed the touch recovery from the toolkit and that worked for me
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
What version of the toolkit? I can only find 1.0 which gives me recovery 5.5
I'm in the same place. Rooted tried cmw and touch recovery both giving errors. Rom manager from the play store doesn't have an option for a different recovery for me.
Sent from my SGH-I747M using xda app-developers app
onei0077 said:
I'm in the same place. Rooted tried cmw and touch recovery both giving errors. Rom manager from the play store doesn't have an option for a different recovery for me.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
I've been trying for 3 days.. I'll let you know if i find a solution (if this thread doesn't provide one that is)
(I'm in Ottawa too!)
Error 7 is means you don't have the right requirements to start with.
If you are trying to flash bell 4.1.1 on your Rogers device running 4.0.4, you must first install bell stock 4.0.4 from Sammy site or else things like will throw error 7 during install.
Read CM10 requirements carefully...
I had the same problem. I just upgraded the CWM version to the latest one using this (its the same step, just make sure you download the right recovery):
youtube.com/watch?v=rx8GuAKxzpA
Get recovery from the main CWM site:
clockworkmod.com/rommanager
Hello all,
I just downloaded liquids RC5 and attempted to install after doing a full wipe of my stock ROM. I've tried 3 times and each time it says "failed to install getprop" and "(status 7)". I was wondering if anyone could help?
Sent from my Galaxy Nexus using Tapatalk 2
are you trying to install a maguro rom on a toro device or vice versa?
No I'm using a Verizon model and attempting to install the toro ROM, so it should be working fine. When I rooted with the GNex Tool Kit though I had to use the GSM model root option (the LTE version didn't have an option for 4.1.1 and in another thread I was assured it would work fine - which it did) would that have somehow changed it to the maguro build?
Sent from my Galaxy Nexus using Tapatalk 2
Be a big boy and don't use toolkits.
If that maguro option flashed a maguro recovery...then very much so, yes. That is your problem.
Since you're rooted...just download Rom Manager and use it to flash CWM for your device (TORO).
Jubakuba said:
Be a big boy and don't use toolkits.
If that maguro option flashed a maguro recovery...then very much so, yes. That is your problem.
Since you're rooted...just download Rom Manager and use it to flash CWM for your device (TORO).
Click to expand...
Click to collapse
yeah. i bet he flashed the wrong recovery.
nomad3018 said:
No I'm using a Verizon model and attempting to install the toro ROM, so it should be working fine. When I rooted with the GNex Tool Kit though I had to use the GSM model root option (the LTE version didn't have an option for 4.1.1 and in another thread I was assured it would work fine - which it did) would that have somehow changed it to the maguro build?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Found your problem. You used a toolkit instead of learning how to actually root/ROM.
Edit: Man, I'm slow on the draw today.
Toolkits cause many problems.
-Brought to you by Marino's Galaxy Nexus-
Got it. Thanks for the help everyone!
Sent from my Galaxy Nexus using Tapatalk 2
Hi there,
I have a Galaxy SIII SGH-i747 from Virgin in Canada. As for as I know, its the same as Bell and every other SGH-i747. So tonight I tried flashing cyanogenmod 10.1 to no avail. I have rooted and installed CWM. When I try to install any ROM it comes up with the error "assert failed getprop status 7". I have searched around and have tried updating CWM recovery through ROM Manager from the play store, but the app doesn't allow me to select my phone model (says there is no official release of CWM for SGH-i747) and says the current version will do. This ROM does not want to install.
HELP!:crying:
disengage said:
Hi there,
I have a Galaxy SIII SGH-i747 from Virgin in Canada. As for as I know, its the same as Bell and every other SGH-i747. So tonight I tried flashing cyanogenmod 10.1 to no avail. I have rooted and installed CWM. When I try to install any ROM it comes up with the error "assert failed getprop status 7". I have searched around and have tried updating CWM recovery through ROM Manager from the play store, but the app doesn't allow me to select my phone model (says there is no official release of CWM for SGH-i747) and says the current version will do. This ROM does not want to install.
HELP!:crying:
Click to expand...
Click to collapse
Status 7 is an out of date recovery or incorrect recovery.
You need a d2att recovery. The Canadian models are d2can. Same phone but it is a system fail safe.
Flash either one in recovery, reboot back into recovery, wipe and enjoy cm10.1
http://d-h.st/8qP cwm
http://d-h.st/qft cwm touch
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
sending onalond
KorGuy123 said:
Status 7 is an out of date recovery or incorrect recovery.
You need a d2att recovery. The Canadian models are d2can. Same phone but it is a system fail safe.
Flash either one in recovery, reboot back into recovery, wipe and enjoy
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Just to be clear: Load the CWM you linked onto SD. Reboot into CWM, flash new CWM, reboot and wipe?
Also to clarify, I have a Canadian model SGHi747
disengage said:
Just to be clear: Load the CWM you linked onto SD. Reboot into CWM, flash new CWM, reboot and wipe?
Also to clarify, I have a Canadian model SGHi747
Click to expand...
Click to collapse
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Okay thanks, I will try later and reply with results.
KorGuy123 said:
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Also should I flash with ODIN?
disengage said:
Also should I flash with ODIN?
Click to expand...
Click to collapse
No recovery.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
No recovery.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Hi there, I tried flashing from recovery, choosing zip from sdcard, and I got the same exact error assert failed: getprop(" ro.product.device") == "d2att" || getprop( " ro.build.product " ) == "d2att" E:Error in /sdcard/CWM-recovery_ATT-6.0.2.3_2.zip
(status 7)
Installation aborted.
I tried exactly what you said, still nothing.
Bump.
Did you have the most recent stock rom before flashing cyanogenmod? The newer versions of the nightlies require that you have the most recent bootloader. If you had ics, it'll fail to flash until you update your bootloader. The most recent build before the bootloader assert that you can flash is rc2.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
Did you have the most recent stock rom before flashing cyanogenmod? The newer versions of the nightlies require that you have the most recent bootloader. If you had ics, it'll fail to flash until you update your bootloader. The most recent build before the bootloader assert that you can flash is rc2.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I think so. i have no idea how to check, forgive the noobness plz. My stock firmware is 4.1.1
Bump? Does anyone know how I can flash an updated recovery?
disengage said:
Bump? Does anyone know how I can flash an updated recovery?
Click to expand...
Click to collapse
The link I gave you is the most up to date recovery. There is a thread here for most recent stock roms. Quick search will assist you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
The link I gave you is the most up to date recovery. There is a thread here for most recent stock roms. Quick search will assist you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but I cannot flash the updated CWM. What am I doing wrong?
Okay, so I see people are trying to help me but it's so vague. Every article or how to, or help page ive read on this site or others, suggest conflicting ways to perform these mods. Why can't anyone just tell me straight up, you do this, then this, then that? I feel it shouldnt be this much of a headache and before I've even started modding, I'm getting very turned off. I am already frustrated beyond comprehension. Like I said, I've searched, and searched and nothing is helping. Everything is too vague.
So my question stands: I flashed an outdated recovery by accident, and I want to flash a new, UPDATED recovery. KorGuy provided me with instructions and a link to a new, updated recovery, however I cannot flash that from my current recovery.
What can I do to flash an updated CWM?
Can someone give me a hand?
You need to flash the most recent STOCK firmware through ODIN so you will have the most recent bootloader, then flash your recovery of choice through ODIN, boot into recovery, not system as the recovery will be overwritten iirc. Then flash cm in recovery
Sent from my SGH-T999 using Tapatalk 2
disengage said:
Okay, so I see people are trying to help me but it's so vague. Every article or how to, or help page ive read on this site or others, suggest conflicting ways to perform these mods. Why can't anyone just tell me straight up, you do this, then this, then that? I feel it shouldnt be this much of a headache and before I've even started modding, I'm getting very turned off. I am already frustrated beyond comprehension. Like I said, I've searched, and searched and nothing is helping. Everything is too vague.
Can someone give me a hand?
Click to expand...
Click to collapse
If you can't follow a guide like this and figure things out, maybe flashing ROMs just isn't for you. I'm not trying to offend, but this isn't for everyone.
danieljordanmaddux said:
You need to flash the most recent STOCK firmware through ODIN so you will have the most recent bootloader, then flash your recovery of choice through ODIN, boot into recovery, not system as the recovery will be overwritten iirc. Then flash cm in recovery
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I understand that I need to flash with ODIN. However, don't I need a .TAR recovery? I can't flash .img through ODIN...
Correct. Find the .tar of the recovery. I think you can find the TWRP .tar on their website
Sent from my SGH-T999 using Tapatalk 2
Root your phone and install a custom recovery. Most root guides will include instructions for flashing a custom recovery. Next buy "ROM toolbox" form android market, I say by because you will love this app so much you will want to buy it eventually anyway.
Open ROM toolbox and select cyanogen mod. ROM toolbox will flash your phone for you! It can also flash the custom recovery if you did not do this when you rooted your phone.
Annnother must have root app is titanium backup.
Hope this helps.
Sent from my Nexus 4 using xda app-developers app
Greetings! This is the first time I've felt compelled to post in the forums, so I apologize in advance if this happens to be in the wrong section. I've been running CyanogenMod 10.1 on my Samsung Galaxy S3 SGH-T999VVLLH2 (Mobilicity) for quite some time now, and have only recently been interested in downloading and installing the nightly installments that are released.
I haven't had any issues installing the new nightlies at all, until seemingly after revision 20130513. It seems that after this installment, I receive an "assert failed, get prop, status 7" error, upon the attempt at installing any newer nightly revisions. Now, I did a tremendous amount of digging around before I decided to make the post, and discovered that within the newer revisions, the updater-script now seems to flag certain Baseband versions of the phone, and prior to revision 20130513 (currently have), it didn't, and I had no issues installing.
When I go into the CyanogenMod settings, all of the nightly updates are available, as usual, up to the latest at the time of the post (20130524) but none will install. In the latest revisions the updater-script does show a similar version (T999VVLDLL1), which I've come to understand is an update for the software.
Am I required to do another update before installing the latest CyanogenMod 10.1 nightlies? Or is there another solution I haven't discovered yet? Any help regarding this would be greatly appreciated. Thanks!
On a side note, I am running the latest ClockWorkMod Recovery as well.
Im surprised that it happened to you on an AOSP recovery. Usually it happens when its a modded recovery with a kernel.
Try TWRP. Or check for an update.
Sent from my GT-I9505 using xda premium
You need to flash a firmware update that will update the bootloader. Not the UVDMD5 one though for sure because that's for T-Mobile. Maybe the other one. Lemme try linking you to the thread.
Edit : here read up on this before flashing http://forum.xda-developers.com/showthread.php?t=2290118
T999V VLDLL1 Bootloader + Modem (Flashable .zip)
Sent from my SGH-T999 using Tapatalk 2
TheLastSidekick said:
You need to flash a firmware update that will update the bootloader. Not the UVDMD5 one though for sure because that's for T-Mobile. Maybe the other one. Lemme try linking you to the thread.
Edit : here read up on this before flashing http://forum.xda-developers.com/showthread.php?t=2290118
T999V VLDLL1 Bootloader + Modem (Flashable .zip)
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Correct. Once I flashed this my random reboots completely stopped.
Sent from my SGH-T999 using xda app-developers app
yanikd said:
Correct. Once I flashed this my random reboots completely stopped.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I have same problem and same phone t-online Firmware is up to date but i rooted for first time with no problem but cyanagon wont instal status 7 error. Please help
The latest T999V firmware is VLDMF2. It's been out less than a week so many cm and aosp roms will not have added I to their asserts to allow install.
Downgrade to LL1 firmware for now and it should flash.
Or change the asserts in the updater script
Sent from my SGH-T999V using xda premium
DocHoliday77 said:
The latest T999V firmware is VLDMF2. It's been out less than a week so many cm and aosp roms will not have added I to their asserts to allow install.
Downgrade to LL1 firmware for now and it should flash.
Or change the asserts in the updater script
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
I have 4.1.2
Dunno i live in europe. thought firmware is different than us or so
First i used this i used "cm-10.1-20130716-NIGHTLY-d2tmo.zip" and "gapps-jb-20130301-signed" but Statuts 7 error than i tried : T999V_VLDLL1_noradio_v3 but there is also Status 7 error.
when i boot into recovery mods it says CWM-based Revovery v5.5.0.4 : : CF-v1.5 is this OK ?
yotaxd said:
I have 4.1.2
Dunno i live in europe. thought firmware is different than us or so
First i used this i used "cm-10.1-20130716-NIGHTLY-d2tmo.zip" and "gapps-jb-20130301-signed" but Statuts 7 error than i tried : T999V_VLDLL1_noradio_v3 but there is also Status 7 error.
when i boot into recovery mods it says CWM-based Revovery v5.5.0.4 : : CF-v1.5 is this OK ?
Click to expand...
Click to collapse
Well first thing you should do is update that old recovery. May be that's all you need.
The reason I mentioned the T999V firmware is because that's what the rest of the thread was for, so I assumed that's the model you had.
What model is your device? The T999 is a US only variant, the T999V is the Canadian variant. The European models should be the international ones, I9300.
If yours is international, do not flash anything you find here!
Sent from my SGH-T999V using xda premium
DocHoliday77 said:
Well first thing you should do is update that old recovery. May be that's all you need.
The reason I mentioned the T999V firmware is because that's what the rest of the thread was for, so I assumed that's the model you had.
What model is your device? The T999 is a US only variant, the T999V is the Canadian variant. The European models should be the international ones, I9300.
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
If yours is international, do not flash anything you find here!
i do not know if its internatianl oder t-mobile. but it should be t-mobile because starting the phone there is t-mobile logo and it is rent from t-mobile
anyway i installed new recovery 6. via google play but in recovery mode there is still Status 7. even its t-mobile. i can try every version because there is always status 7 so i can not damge phone installing wrong version i think. o the other hand i have always wipe chare/ factory before installing the cyanagenmod. i must restore data now and system setting by advanced backup thats kinda annoying. but next i should maybe try INT. now
If you don't know what model it is, don't flash anything!
Look under the battery.
Sent from my SGH-T999V using xda premium
They are adding the assert for T999VVLDMF2: http://review.cyanogenmod.org/#/c/45740/
[SOLVED!!]
i have this problem too when i want to install some roms like AOKP and JB 4.2.2 , i get same error !!
just go to recovery mode cwm then
go to mount and storage ---> unmount /system
now format /system and /data
try agian install cm rom , and it'l work :good:
HTC One
you guys got any ideas on the att M7 version of this problem. im almost positive i RUUd in order to flash CM but i couldnt get it to work. im on KitKat now cant get it to sideload or install from sd.
got any ideas?