Heyho guys,
stumbled over a problem trying to flash my nexus
im not really a noob flashed a lot of devices but have no in depth knowledge with android
unlocked, installed recovery (using wugs toolkit), flashed faux kernel now i wanted to try out some of the cumstoms around here
trying to flash the rom in twrp the installation always aborts before it even started
assert failed getprop (ro.product.device) = flo
seems the installationroutine tries to check if the device is a nexus 7 (2013) and fails to verify it?
anyone knows how to fix this ? i seem not to be the only one with this problem but could not find a solution here
using the wifi version
thanks in advance
seems it has something to do with twrp
cwm does the job
Related
Hey guys!
So I finally decided to take the leap and install CM9.1
I rooted my phone and installed the "fake" recovery from x-parts.
Then I proceded to flash CM9 baseband for my phone,
then flashing the kernel, boot into recovery and then flash CM9.1 from my sd-card
Problem is I'm getting status 7 when I try to install it!
I checked around the forum and came across this one http://forum.xda-developers.com/showthread.php?t=1818280
I'm getting the same lines as the guy there says;
assert failed: getprop("ro.product.device")=="LT18i""
What do I do now?
Help would be appreciated!
http://forum.xda-developers.com/showthread.php?t=1884746
thought I read them all (that's why I came here), will continue reading
thanks
Hi, so I'm trying to make this quick so that i can install CM10 tonight...
so I rooted my phone tonight, did everything right and stuff, but I went to go download the CM10 nightly build for my phone which is the Rogers (Canadian version). So I download the d2att version, did a backup, wiped everything and I tried installing it using CWM-Based recovery v5.5.0.4. But when I tried install it gave me status 7 aborted. I installed cwm using odin3 v1.85, what am I doing wrong, am I trying to install the wrong version? Sorry if this is a noob question but I'm new to this stuff :/
thanks for any help
Can anyone explain to me how I can update CWM? I downloaded the latest img from their website, but idk how to install it...I'm really confused...and I really need help :crying:
Go look at QBKing77 videos on YouTube or QBKing77.com he has the best videos in my opinion and installing CM10 and CWM. I am on CM10.1 without any problems.
hmm, did you use the v5 recovery? Did it work, because the version i had was cwm 5.5 and I couldn't update because of system 7 error, which is because the CWM version was too old.
If possible, could you link me the one you used?
Ok..so now I installed TWRP and I tried flashing CM10 it still didnt work and gave me status 7 error and it says:
assert failed: getpro ("ro.product.device")
E: Error in /sdcard/cm- 10.....d2att.zip
Is this because with goomanager i installed it for the d2can version and now I can't install the d2att even though thats the only version i can use? goomanager only lets me get d2can...and when I try to install the never cwm recover img using android terminal it keeps giving me No such file or directory.
Can anybody help me with this...
PhoenixBlitz said:
Ok..so now I installed TWRP and I tried flashing CM10 it still didnt work and gave me status 7 error and it says:
assert failed: getpro ("ro.product.device")
E: Error in /sdcard/cm- 10.....d2att.zip
Is this because with goomanager i installed it for the d2can version and now I can't install the d2att even though thats the only version i can use? goomanager only lets me get d2can...and when I try to install the never cwm recover img using android terminal it keeps giving me No such file or directory.
Can anybody help me with this...
Click to expand...
Click to collapse
have you tried flashing another ROM, like an-aosp or aokp-based one? If you followed their instructions, it may help you determine whether it was a bad download or something s more specific to your device. just throwing this one out there....
captican said:
have you tried flashing another ROM, like an-aosp or aokp-based one? If you followed their instructions, it may help you determine whether it was a bad download or something s more specific to your device. just throwing this one out there....
Click to expand...
Click to collapse
oh...hahaha
I just flashed AOKP and everything worked great! Thanks for that little suggestion! Custom ROMs are now my favorite!
PhoenixBlitz said:
oh...hahaha
I just flashed AOKP and everything worked great! Thanks for that little suggestion! Custom ROMs are now my favorite!
Click to expand...
Click to collapse
If you want to flash a CM ROM you will need to be on the most current d2att recovery for either CWR or TWRP. If you were getting a status 7 error, I'm going to assume that you have a d2can phone.. make sure you have a d2att recovery and you'll be able to flash anything. ROM Manager will let you install CWR or Goo Manager will let you install TWRP (which is what I use).
BAM1789 said:
If you want to flash a CM ROM you will need to be on the most current d2att recovery for either CWR or TWRP. If you were getting a status 7 error, I'm going to assume that you have a d2can phone.. make sure you have a d2att recovery and you'll be able to flash anything. ROM Manager will let you install CWR or Goo Manager will let you install TWRP (which is what I use).
Click to expand...
Click to collapse
Yes, I highly recommend TWRP.
Sent from my SPH-D710 using xda premium
HeadBlader911 said:
Yes, I highly recommend TWRP.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I tried using TWRP but when I installed it through GooManager it installed the d2can version so I couldn't install CM10. Unless there is a way to manually select which TWRP version to install through GooManager, then I'm more or less stuck on CWM.
edit: Just got TWRP for d2att installed so now I can flash whatever I want, man TWRP seems a lot better than CWM!
I am new to all this root and custom ROM, but I have spent hours searching forums and need help so thats why I am posting.
I have an AT&T Samsung Galaxy S3 I747. I am using Mac OSX 10.6.8. I managed to root my android using CASUAL (http://forum.xda-developers.com/showthread.php?t=2189536) and install Clockwordmod recovery v6.0.3.6
I then download and install #SuperUser. Followed by ROM Manager. (My internet research told me rom manager is the easiest to use for mac users)
I run rom manager, flash clockwork, then look to install the latest "stable" build for CM. I select install CM, format and erase, It downloads, downloads gapps, reboots looks to install CM, then I get the below error message:
Finding update package
Opening update package
Installing update
Assert failed: getprop(ro.bootloader”)==i747
(followed by many more lines of error/failed)
my phone then reboots into the stock AT&T. What am I doing wrong? What do I need to do to wipe my whole phone, factory reset, then install a custom ROM like CM using ROM Manager? or should I be doing something else?
Thank you in advance for your help.
Regards,
Tim
I was able (after many hours of reading posts) figure out my problem.
The new CM mods require a specific version of your phone's "bootloader." I switched it to: I747UCDLK3 then re-flashed CM 10.1.2-dtatt with Rom Manager and it worked!
You'll need to download and flash the appropriate bootlegger.
This thread was very helpful: http://forum.xda-developers.com/showthread.php?t=2321310
I have to say all in I invested a good 8 hours this weekend of reading posts, troubleshooting, and research as I rooted my phone for the first time, then installed my first custom rom. It wasn't easy rooting on a mac 10.6.8. Every step of the way I ran into obstacles and had to do a special workaround to root, get java 7, type commands in the terminal, install clockwork recovery, update bootloader, reflash cm rom.
Good luck!
tim1182 said:
I am new to all this root and custom ROM, but I have spent hours searching forums and need help so thats why I am posting.
I have an AT&T Samsung Galaxy S3 I747. I am using Mac OSX 10.6.8. I managed to root my android using CASUAL (http://forum.xda-developers.com/showthread.php?t=2189536) and install Clockwordmod recovery v6.0.3.6
I then download and install #SuperUser. Followed by ROM Manager. (My internet research told me rom manager is the easiest to use for mac users)
I run rom manager, flash clockwork, then look to install the latest "stable" build for CM. I select install CM, format and erase, It downloads, downloads gapps, reboots looks to install CM, then I get the below error message:
Finding update package
Opening update package
Installing update
Assert failed: getprop(ro.bootloader”)==i747
(followed by many more lines of error/failed)
my phone then reboots into the stock AT&T. What am I doing wrong? What do I need to do to wipe my whole phone, factory reset, then install a custom ROM like CM using ROM Manager? or should I be doing something else?
Thank you in advance for your help.
Regards,
Tim
Click to expand...
Click to collapse
**** IGNORE THIS POST AS FIX WAS INCLUDED IN PREVIOUS POST ********
Status 7 is from you having an outdated bootloader. follow this http://forum.xda-developers.com/showthread.php?t=2321310 and do as instructed
I just bricked my galaxy nexus by trying to install Shiny ROM. I've got a (europe) maguro galaxy nexus which ran PA before, but I wanted to update as it became extremely slow at times.
Using TWRP v2.5.0.0 I did a factory reset(data, cache and dalvik wipe). I then tried to install ShinyROM, but it gave the following error:
Updating partition details...
Formatting Cache using make_ext4fs...
Done.
Wiping data without wiping /data/media ...
Done.
Updating partition details...
Installing '/sdcard/modsnstuff/ShinyROM_maguro_a
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
Installing Shiny ROM build 062114
for maguro
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/modsnstuff/ShinyROM_
Updating partition details...
Click to expand...
Click to collapse
I also put a new PA version on the phone, which gave a similar error.
I tried using the android toolkit to get into adb recovery and flash a new rom somehow. I did not succeed to install the drivers successfully, which is probably because I am not able to boot into android. I do not see how I can use the toolkit now, and since I barely know what it does and I would not know how to install the drivers.
What can I do to correctly install the new ROM, or at least get it to boot in any version of android?
inasm said:
I just bricked my galaxy nexus by trying to install Shiny ROM. I've got a (europe) maguro galaxy nexus which ran PA before, but I wanted to update as it became extremely slow at times.
Using TWRP v2.5.0.0 I did a factory reset(data, cache and dalvik wipe). I then tried to install ShinyROM, but it gave the following error:
I also put a new PA version on the phone, which gave a similar error.
I tried using the android toolkit to get into adb recovery and flash a new rom somehow. I did not succeed to install the drivers successfully, which is probably because I am not able to boot into android. I do not see how I can use the toolkit now, and since I barely know what it does and I would not know how to install the drivers.
What can I do to correctly install the new ROM, or at least get it to boot in any version of android?
Click to expand...
Click to collapse
Search for using fastboot to return to stock Google image(stock ROM). Then install custom recovery again and flash a ROM.
This phone is nearly impossible to brick
DR3W5K1 said:
Search for using fastboot to return to stock Google image(stock ROM). Then install custom recovery again and flash a ROM.
This phone is nearly impossible to brick
Click to expand...
Click to collapse
Thanks a lot for the reply, trying it now. Apologies if I misused the word brick btw.
inasm said:
Thanks a lot for the reply, trying it now. Apologies if I misused the word brick btw.
Click to expand...
Click to collapse
No need to apologize just didn't want you to think that you were stuck.
Also it will be very beneficial to study up on adb along with fastboot.
If you learn these two things you will be able to get out of just about any sticky situation you run into.
PS The most difficult part is getting the drivers installed.
DR3W5K1 said:
No need to apologize just didn't want you to think that you were stuck.
Also it will be very beneficial to study up on adb along with fastboot.
If you learn these two things you will be able to get out of just about any sticky situation you run into.
PS The most difficult part is getting the drivers installed.
Click to expand...
Click to collapse
Would you happen to have a link to a post of some sort? I tried downloading the drivers, then installing them using device manager which didn't work, since windows said they were up to date already. All other guides I found to install the right drivers were with a working android version. Even the soft brick guides assume you have installed the drivers already.
inasm said:
Would you happen to have a link to a post of some sort? I tried downloading the drivers, then installing them using device manager which didn't work, since windows said they were up to date already. All other guides I found to install the right drivers were with a working android version. Even the soft brick guides assume you have installed the drivers already.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1583801. Use this for driver issues.
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895 use this to return to stock.
With these guides you can fix it!
DR3W5K1 said:
http://forum.xda-developers.com/showthread.php?t=1583801. Use this for driver issues.
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895 use this to return to stock.
With these guides you can fix it!
Click to expand...
Click to collapse
The driver still seems to refuse to work. It keeps saying the latest driver is installed. I am using Windows 7 in stead of 8, which is why the guide might not apply 100% to me.
When I use the Android ToolKit and I try to flash the google ROM, it does detect a device in ADB MODE, and it gets the serial number, but it gets stuck on "Waiting for adb Mode". Does this mean the drivers are already correctly installed?
EDIT:
I remembered that I downloaded an old version of PA a long time ago using goo manager, which was still on my phone. ADB drivers are also installed now it seems, now I just have to install the 4.4 version correctly.
Thanks a lot for your help!
inasm said:
The driver still seems to refuse to work. It keeps saying the latest driver is installed. I am using Windows 7 in stead of 8, which is why the guide might not apply 100% to me.
When I use the Android ToolKit and I try to flash the google ROM, it does detect a device in ADB MODE, and it gets the serial number, but it gets stuck on "Waiting for adb Mode". Does this mean the drivers are already correctly installed?
EDIT:
I remembered that I downloaded an old version of PA a long time ago using goo manager, which was still on my phone. ADB drivers are also installed now it seems, now I just have to install the 4.4 version correctly.
Thanks a lot for your help!
Click to expand...
Click to collapse
Your welcome but you should have been using fastboot instead of adb. For future reference they are two different things
Hello! I am new to the site so please be serious! Ok, so here's the problem: I rooted my Galaxy Nexus from Verizon to install CyanogenMod 11, Once I got the rom onto my phone I entered recovery using TWRP Recovery, then I tried to install the rom. After that it failed and I can't remember why, but I was being stupid and clicked the format sd card button and bricked my device. Now I'm trying to flash the rom again through ADB and Windows sends the .zip file to the phone, then while trying to install it gives the error of "E: Error executing updater binary in zip" and I cannot figure out a way to fix it. I need help as soon as possible and it would be greatly appreciated, thank you!
Nobody? Nobody has had this issue or a solution?
Duelist_Shay said:
Hello! I am new to the site so please be serious! Ok, so here's the problem: I rooted my Galaxy Nexus from Verizon to install CyanogenMod 11, Once I got the rom onto my phone I entered recovery using TWRP Recovery, then I tried to install the rom. After that it failed and I can't remember why, but I was being stupid and clicked the format sd card button and bricked my device. Now I'm trying to flash the rom again through ADB and Windows sends the .zip file to the phone, then while trying to install it gives the error of "E: Error executing updater binary in zip" and I cannot figure out a way to fix it. I need help as soon as possible and it would be greatly appreciated, thank you!
Click to expand...
Click to collapse
as long as you can get to the bootloader see this thread to return to stock: http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895