I’m having problems with the vibrant and am hoping people on the forum could help me with it. I have tried to research on the xda and also android forums but I haven’t come across anyone with similar problems I have encountered.
I first got the vibrant last December and did one upgrade through the software update on the phone. Since then I have rooted the phone (with the tips posted on the sticky board on xda forum) and flashed a custom rom once with ease (Eugene – Ginger clone final R2). I was on Ginger clone for a month and was pretty happy about it.
I recently tried to flash new roms (Eugene – Vibrant 4G and TW – Bionix Frost 2.2.1) without success. I kept getting the error about “signature verification failed”. After several attempts, I brick the phone.
I was able to get to download mode, used Eugene’s no brick, and odin it back. Now the phone is running on Éclair; JFD and kernel 2.6.29. I was able to flash Eugene Vibrant 4G, but not TW Bionix Frost. I even odin it back to stock JFD, but I still got the same signature verification error. Do you know why I keep getting this? I remember reading from the forum that TW rom is based on Éclair and there shouldn’t be any problem flashing TW rom if I’m on Éclair.
Then I went back to Eugene Ginger clone final R2. After several days, the stuff on the main screen were disappeared, i.e. clock, date, and widgets/icons. I odin it back to JFD, but this time I can’t even root the phone!! I tried the three button method and also SuperOneClick, but it didn’t work. The SuperOneClick said the phone was successfully rooted, but Titanium Backup said I didn’t have root right. Below is the message on the screen when I applied the three buttons method:-
Installing update…
assert failed: getprop(“ro.product.device”) == “GT-I5800” || getprop(”ro.build.product”) == “GT-I5800” || getprop(“ro.product.device”) == “GT-I9000” || getprop(”ro.build.product”) == “GT-I9000”
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Also I have tried to odin the phone to JI6 but it went dead at the booting screen.
Can you please advice on getting the phone rooted and getting through the signature verification failed issue? I have seen a post relating to solving signature verification failed on the forum, but believe it’s not for Éclair. I’m now on JFD and the phone is so slow.
Any helps are much appreciated.
Does your phone turn on, if yes, its not bricked, if nothing happens at all when you try to turn it on then your are bricked...
Another question, why are you flashing all these roms, I understand if you want to try them out but by the looks of it you don't know what you are doing... provide some links as to what you've flashed for reference
Sent from my GT-I9000 using XDA App
Thanks for your response, Stefan. The phone is working now. What I’m trying to do now is to get the phone rooted and solve the signature verification fail issue; maybe go back to Ginger clone rom that I had used for over a month. I wanted to try these roms as their performances and options are different.
Here’s the links to the roms:-
Eugene – Ginger clone http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=144
TW – Bionix Frost http://forum.xda-developers.com/showthread.php?t=966688
Related
I originally set out to upgrade to the latest CM7 build, but got an error about proper load EDITstatus 7) and it would not upgrade. So I decided to just put the official 2.3 on my Vibrant, however now it seems I have a different bootloader, the I9000 bootloader.
Ultimately I would like to get back to full stock, including bootloader so I can start fresh and hopefully get CM7 installed or at least the official 2.3 installed. I currently have stock JFD installed (using Odin).
If there is a way with my current install (i9000 bootloader and JFD) to get CM7 nightly I would love to know how to do that. I have tried the wiki instructions, but I am not able to get Heimdall Suite to work (I have Lion installed on my Mac, and it just does not want to find the phone no matter what on my pc). I have Rom Manager Premium but I do not see CyanogenMod listed under downloadable roms.
I have a ton of bookmarked pages of how to install CM7, but I think my problem is the bootloader as I can not seem to get CM7 to install from recovery. Perhaps there is a way to put CM7 on my T959 using Odin?
I have also found one download with a boot.bin and sbl.bin inside a .rar, but since there were not decent instructions for how to load these using Odin (if that is even how you do it), I didnt want to attempt bricking my phone.
I would say im a pretty advanced user, I have in the past installed with out any problem many different roms (Bionix, Miui). Any advice is welcome. Please help me get back to my precious CM7
When trying to install the CM7 kernel from recovery i get the following error:
assert failed: getprop("ro.product.device") =="galaxys2" || getprop("ro.build.product") == "galaxys2" .... Status 7
Click to expand...
Click to collapse
and so on.
I got my kernel from here and have tried kernels from the CM7 wiki, as well as roms from there as well. I know it normally means it is a miss match between the phone and software (status 7), but I have a T959, and I have tried from the official vibrant wiki at CM7.
AK
austindkelly said:
I originally set out to upgrade to the latest CM7 build, but got an error about proper load and it would not upgrade. So I decided to just put the official 2.3 on my Vibrant, however now it seems I have a different bootloader, the I9000 bootloader.
Ultimately I would like to get back to full stock, including bootloader so I can start fresh and hopefully get CM7 installed or at least the official 2.3 installed. I currently have stock JFD installed (using Odin).
If there is a way with my current install (i9000 bootloader and JFD) to get CM7 nightly I would love to know how to do that. I have tried the wiki instructions, but I am not able to get Heimdall Suite to work (I have Lion installed on my Mac, and it just does not want to find the phone no matter what on my pc). I have Rom Manager Premium but I do not see CyanogenMod listed under downloadable roms.
I have a ton of bookmarked pages of how to install CM7, but I think my problem is the bootloader as I can not seem to get CM7 to install from recovery. Perhaps there is a way to put CM7 on my T959 using Odin?
I have also found one download with a boot.bin and sbl.bin inside a .rar, but since there were not decent instructions for how to load these using Odin (if that is even how you do it), I didnt want to attempt bricking my phone.
I would say im a pretty advanced user, I have in the past installed with out any problem many different roms (Bionix, Miui). Any advice is welcome. Please help me get back to my precious CM7
AK
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1117990
Thanks for the thread. This seems to have a the original bootloaders, and a lot of other nice bootloaders for gingerbread. I will test it out tonight and let you know if this worked for me.
If you happen to have a link for installing CM7 with Odin please let me know.
austindkelly said:
Thanks for the thread. This seems to have a the original bootloaders, and a lot of other nice bootloaders for gingerbread. I will test it out tonight and let you know if this worked for me.
If you happen to have a link for installing CM7 with Odin please let me know.
Click to expand...
Click to collapse
glad its what you wanted, i was in abit of a rush and just read the thread name so posted that
I have been trying some stuff, the official bootloader from there didnt pass MD5 check in odin. please read my update/edit if you can help.
I, too, have been messing around with the Vibrant way too many times and it has bricked on me at least 6 times already because (stupid me) I went from ROM to ROM without Odin-ing back to stock.
Pertaining to your matters, Im not sure exactly where you're stuck right now. If you're stuck ODIN-ing, check to see if you have the right PIT file. If anything, redownload the stock JFD and stock PIT file and re-do it again. I've read somewhere, you really cant "brick" an android unless its hardware related or you throw your phone out the window.
If you're stuck trying to get CM7 on your vibrant then... wait, why are you trying to get Nightlies on your vibrant? I say you're better of flashing CM7 Trigger Redux (which is what I'm using now). I've heard its much better with more features (working GPS and more) than Nightlies. In case you wanted to check it out, heres the link:
http://forum.xda-developers.com/showthread.php?t=1156123
But anyhow, you're decision. From past experiences, after I ODIN back to stock, I rooted the stock and downloaded ROM Manager and then flashed the ROM that I wanted like Trigger Redux or Bionix. This pretty much worked for me. Hope this helps.
I've searched and scoured the earth for an answer to this issue but have drawn a blank so far, so thought I'd ask the experts.
Basically I'm not able to install any ROMs on my GT-P7510UW 32 Retail Wireless tablet.
I'm able to get CWM on, I'm able to Root it, but when I try installing a ROM I get a variety of different issues. For example trying to install the Bonsai ROM I get the following :
assert failed: run_program("/tmp/install-script") == 0
E:Error in /sdcard/Bonsai_GT-P7510_v0.3.0.zip
(Status 7)
Installation aborted.
On the StarBurst ROM it just seems to install REALLY quickly, then when I reboot I'm stuck on the Samsung startup screen forever (the very first one reading "Samsung Galaxy TAB 10.1" before you get to Download/Recovery
I've used Odin to get back to Stock, still can't install ROMs.
Any ideas what I'm doing wrong?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
MetaAsmo said:
I've searched and scoured the earth for an answer to this issue but have drawn a blank so far, so thought I'd ask the experts.
Basically I'm not able to install any ROMs on my GT-P7510UW 32 Retail Wireless tablet.
I'm able to get CWM on, I'm able to Root it, but when I try installing a ROM I get a variety of different issues. For example trying to install the Bonsai ROM I get the following :
assert failed: run_program("/tmp/install-script") == 0
E:Error in /sdcard/Bonsai_GT-P7510_v0.3.0.zip
(Status 7)
Installation aborted.
On the StarBurst ROM it just seems to install REALLY quickly, then when I reboot I'm stuck on the Samsung startup screen forever.
I've used Odin to get back to Stock, still can't install ROMs.
Any ideas what I'm doing wrong?
Click to expand...
Click to collapse
Try task's rom. I run that with pershoots kernel and its perfect. It does take a long time to boot the first time you boot after you flash. Also, after you flash the rom, stay in CWM and format the cache and everything. Then give it some time on the first boot
Hm. How long should it take to actually install the ROM within CWM? It only takes about 10 seconds, if that. Then it says its finished, and I manually initiate a reboot.
I've left it on the loading screen for about 30 minutes and nothing happens after that, so I get the feeling the ROM install just isn't working...
But I'll try Tasks ROM and see how that goes
Same Issues
Is anyone else running into the same problem? I'm getting the exact same issues here.
It is highly recommend not to install 3rd party ROMs. None of the ROMs created by the hobbyists here are as stable and reliable as the stock ROM.
It is highly recommend not to listen to 3rd party posts. None of the posts created by the hoboist here are the mark of a stable and reliable mind
5thElement said:
It is highly recommend not to install 3rd party ROMs. None of the ROMs created by the hobbyists here are as stable and reliable as the stock ROM.
Click to expand...
Click to collapse
I'm still getting this issue, and it would seem that nobody has an answer?
I've tried about 5 different ROMS, all fail. So it's not a ROM problem.
I've followed all the instructions to the letter, I've read various guides and confirmed I'm doing it right. So is there something different about my Tab that it seems to be screwed and won't allow any ROM installs??
I've also restored to Stock, used a .pit file so re-partioned also. Cleared every sort of data/cache you can mention.
My deepest apologies if this is not in the right place. I have been fighting with this for two days now with no luck.
I'm trying to install Cyanogenmod in my Samsung Galaxy S 2. I have followed Cyanogenmod's Wiki (erm, I was linking to the guide here but the site won't let me, so my apologies), step by step by step every time, but:
1) This guide is awful. Clockwork recovery can't see my SD card, so I have to put the files in the phone's memory itself.
2) I have tried to do both methods tried there: The first method gives me this error:
assert failed: get prop("ro.product.device" == "click" || getprop("ro.build.product" == "click" || getprop("ro.product.board" == "click"
E:Error in /sdcard/update-cm-7.1.0-click-GalaxyS-signed.zip
(Status 7)
Installation aborted.
And the second one gives me a "File not Found" after a short while. WTF.
I really want to try Cyanogenmod. I have Googled for this problem but unfortunately I have only seen HTC owners with this problem, so I'm afraid their fixes are specific for HTC phones. Any help to install Cyanogenmod will be highly appreciated.
Are you trying to install stable or nightly 116?
An Stable release. There's only stable under the S2's page and lots of Nightlies.
I would link you directly to the page that has the one I'm trying to install, but the forum won't let me until I get around 8 posts. Sorry
Looks like you're trying to install something which is named for Samsung Galaxy S and has an assert check for the HTC Tattoo Click, rather than anything to do with the Samsung Galaxy S II.
Follow the instructions in the first post of [NIGHTLY][ROM][GWK74] CyanogenMod 7 (w/ Gingerbread 2.3.7) for Galaxy SII Q&A if you have an I9100.
Thanks a LOT. That worked. I just hope it's not too unstable or buggy since I am using a nightly build.
I appreciate your help a lot!
Leonne said:
My deepest apologies if this is not in the right place. I have been fighting with this for two days now with no luck.
I'm trying to install Cyanogenmod in my Samsung Galaxy S 2. I have followed Cyanogenmod's Wiki (erm, I was linking to the guide here but the site won't let me, so my apologies), step by step by step every time, but:
1) This guide is awful. Clockwork recovery can't see my SD card, so I have to put the files in the phone's memory itself.
2) I have tried to do both methods tried there: The first method gives me this error:
assert failed: get prop("ro.product.device" == "click" || getprop("ro.build.product" == "click" || getprop("ro.product.board" == "click"
E:Error in /sdcard/update-cm-7.1.0-click-GalaxyS-signed.zip
(Status 7)
Installation aborted.
And the second one gives me a "File not Found" after a short while. WTF.
I really want to try Cyanogenmod. I have Googled for this problem but unfortunately I have only seen HTC owners with this problem, so I'm afraid their fixes are specific for HTC phones. Any help to install Cyanogenmod will be highly appreciated.
Click to expand...
Click to collapse
I'm having this same issue but im using the correct Cyanogenmod.zip file. Here is the steps that i took to get me here...
I have CWM installed and my phone (AT&T Samsung Galaxy S2 SGH-i777) has been rooted
1.) Downloaded the .zip file for Cyanogenmod 7.1 "update-cm-7.1.0-GalaxyS2-signed"
2.) Went into mass storage mode and stored .zip file in usbstorage folder.
3.) Went into recovery mode and wiped data and cache.
4.) Installed Cyanogenmod but did NOT install a second time...the guide i was using at the time did not tell me to do this...
5.) Got stuck in boot mode so i went back into CWM recovery to restore my phone with a previous backup. Restored phone to previous backup. The backup was done after i rooted my phone.
Now when i goto install Cyanogenmod i get the same errors as the user above. I've redownloaded the .zip a couple times and put it back on my phone with no luck...any ideas?
stratdude83 said:
I have CWM installed and my phone (AT&T Samsung Galaxy S2 SGH-i777) has been rooted
<snip>
any ideas?
Click to expand...
Click to collapse
You do not have an I9100, you have an I777.
oinkylicious said:
You do not have an I9100, you have an I777.
Click to expand...
Click to collapse
Yes, completely different phone.
"galaxys2" = GT-I9100
stratdude83, you might want to try here: http://download.cyanogenmod.com/?device=galaxys2att but please verify before flashing anything. Only 20 nightlies, so do some searching to see if it's "stable".
It says that is my phone model "SGH-i777" but it also shows GT-I9100 when it boots up...not the same thing?
stratdude83 said:
It says that is my phone model "SGH-i777" but it also shows GT-I9100 when it boots up...not the same thing?
Click to expand...
Click to collapse
I've never held the SGH-i777; In this section of the forum however the vast majority of people will have the "International Version" of the Galaxy SII, there are some that have an extra letter in the model that are identical (e.g. my phone is (err...was) a GT-I9100M), but aside from the M that the carrier felt they had to add it was the same in every other way, there are others as well. Some phones with other letters following the model number are different; the GT-I9100G for example.
Did/does your phone say GT-I9100 when you're on the stock ROM, or was this just after flashing CM7 and getting stuck on the boot screen? It's just an image and if you're somehow stuck with the incorrect one now (I can't recall whether this is saved in a back up, I don't think it is) you can find the appropriate param.lfs file to get back to normal. I've used Hellcat's K-Tool to replace my boot logo image, I'm not sure whether your phone is supported by that app.
Finally after fiddling with the situation for what seemed like forever ive narrowed it down to the .zip file i downloaded. Still dont really understand why this was the issue since i got it directly from Cyanogenmod.com...perhaps another thread
I used the guide posted GalaxyS2root.com. I can't post the link because im new...but goto GalaxyS2root.com -> AT&T Galaxy S2 ROMs then scroll down to the very bottom and you'll see "CyanogenMod 7.1 ROM for Rooted AT&T Galaxy S2! [SGH-i777]" follow this guide and use the .zip files from here.
Transfer both Google apps (if you want it) and the Cyanogenmod .zip files onto your internal memory and install from CWM recovery mode. Look up "Samsung galaxy s2 mass storage mode" (its easy).
Now follow the guide but you will most likely have to install the Cyanogen .zip file twice. If you get stuck at the Samsung boot image after the first install then install Cyanogen again and everything will work. Don't clear your cache or data again. Only do this the first time you install Cyanogenmod.
There's also instructions at the CyanogenMOD wiki site as well as on XDA.
Here's the nightlies Development thread for the AT&T version in the SGH-I777 forum: http://forum.xda-developers.com/showthread.php?t=1286192
Enjoy CM7, I can't go back to a Samsung ROM now.
mudferret said:
There's also instructions at the CyanogenMOD wiki site as well as on XDA.
Here's the nightlies Development thread for the AT&T version in the SGH-I777 forum: http://forum.xda-developers.com/showthread.php?t=1286192
Enjoy CM7, I can't go back to a Samsung ROM now.
Click to expand...
Click to collapse
You like it that much? I dont know im kindof torn i guess...yea Cyanogenmod has cool stuff but i like the Touchwiz and UI of the stock Samsung more...i guess for me i figured im not really going to utilize the ROM as much as i thought in the first place...or i dont even realize its full capability yet
stratdude83 said:
You like it that much? I dont know im kindof torn i guess...yea Cyanogenmod has cool stuff but i like the Touchwiz and UI of the stock Samsung more...i guess for me i figured im not really going to utilize the ROM as much as i thought in the first place...or i dont even realize its full capability yet
Click to expand...
Click to collapse
If you came from a stock ROM it's a big jump, and you "lose" a lot. CM7 = ~100MB, stock ROM = ~5x that size, a lot is related to system structure, but much is manufacturer app related. I "worked" my way to it. A modified stock ROM removes varying degrees of apps typically. I moved from lighter ROM to lighter ROM ending up at CM7, and even Insanity which is CM7 based but 47MB.
A lot of the stock apps I'd previously missed weren't doing much for me in hindsight, currently my phone does everything I require. I won't dispute that it's not a one size fits all ROM.
stratdude83 said:
It says that is my phone model "SGH-i777" but it also shows GT-I9100 when it boots up...not the same thing?
Click to expand...
Click to collapse
Always follow what it says on the label on the phone underneath the battery. That tells you what hardware it has. Whatever it shows when it boots is just the software version. Someone could easily change the GT-I9100 text it shows at boot to "Your Crappy Phone".
Hi All,
I am facing the same issue with GT-I9100G and flashing the firmware twice does not. Please help me out here
[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:
Hey All,
I've been looking for an answer for over a day now, but can't seem to find anything about my specific problem. Here's what happened:
I had flashed to ICS 4.0.3 on my Samsung Vibrant about a month ago and everything was working great until yesterday when I woke up to find the "Encryption Unsuccessful" screen on my phone. I did a little research to find out that there is a fix to this and to NOT reset the phone. So, I took the steps to ODIN the phone back to Stock Eclair in hopes that starting from the beginning again would be easiest way to fix the problem. The ODIN process finished completely fine (PASSED), but now when it reboots, I only get to the first "Vibrant" screen, then it shows the battery and spinning circle icon. Apparently it won't fully reboot. I've tried to ODIN it back to stock several times, and I keep getting the same results. I can get it into download mode and plugged into my computer, but that's about it.
From the posts I've read, it sounds like my phone might still be okay to recover since it does power up, but I can't seem to find a solution to get it fully back up and running.
Any help/recommendations would be greatly appreciated!
Thanks in advance!
Maybe your JFD file is corruption. Check with your MD5 sum if there any error or mismatch.. Just give you an idea.BTW what Odin are u using. I recommend Odin 1.7 I stay away the older Odin or the newer Odin
You are screwed.
Sorry to tell you this but i had the exact same problem and found no solution whatsoever to fix the phone. I finally gave up and bought a Galaxy Nexus. You can try flashing Eugene's Unbrickable Froyo Rom which is flashable through odin as a .tar package along with the pit file. You might be able to fix it but i highly doubt it. I flashed Eugene's rom and got the same results as you described. By any chance did you click "Reset Phone" when the "Encryption Unsuccessful" showed up? If so well yeah your phone is pretty much paperweight as of now...until someone finds a solution. Like you i am also able to access download mode. So i guess there may be a way to fix your phone. Not saying it's impossible...hopefully someone finds a solution soon.
Here is the link to Euguene's rom: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Good luck.
OP, what ROM were you running (specifically. Not just ICS 4.0.3-what is the name of the ROM)? Also what kernel?
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Check here out for a possible solution/workaround.
Replacement Vibrant Coming
Thanks for your recommendations/help guys.
I decided to go to T-Mobile and complain and they are sending me a replacement phone. Apparently it's still under warranty, so it won't cost me anything, and if my data is lost, then so be it...at least all my contacts will still be in tact through my Google account.
Merio - I did NOT hit the Reset Button when I saw the Encryption Unsuccessful screen. Before doing anything I did a little research and I found a forum here on xda that said to not hit that button, and tried to explain a way to fix it using the Heimdall One-Click. Basically it sounded like I'd be flashing back to a Gingerbread ROM. So, instead I just went ahead and tried to flash back to stock Eclair. The results of that were obviously not good.
Woodrube - I was running the Passion 13 ROM (ICS 4.0.3). Was really enjoying it until I got the Encryption "Screen of Death"
I don't know what Kernel it was, actually, I don't really know what a Kernel is...
Thanks again guys. Hopefully I'll be up and running on my replacement phone soon!
Hey folks. Found several threads with similar questions, but none for this device.
I've had my TF201 for around a year now, more or less. In the last month or two I managed to flash CyanogenMod onto it in order to effectively emulate KitKat. Recently however I've decided that in the long run I much preferred the native Asus image for a number of personal reasons.
I'm having serious issues reverting to the stock ROM. I'm using the recovery image found on the second page of this thread. This is the only one I've managed to get operating at all - I tried the 5.8.3.4 version from the CWM site, but it doesn't seem to boot at all.
I attempted to install the stock ROM from the Asus website (I bought the tablet in Canada, so I've tried both the US and WW versions), but I keep getting the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in data/media/0/Download/WW_epad-user-10.4.2.18.zip
(Status 7)
Installation aborted.
I've done plenty of Googling, but haven't been able to find anything of much help - this thread doesn't seem to apply to TF201 anymore, and most of what else I read tells me to try with other recoveries, but none of these recoveries seem to work. The one I linked to above is the only one I've been able to actually get to boot.
I'm at my wit's end with this. I have no idea what I'm doing wrong, or what else to try. I'm at a loss. I'd greatly appreciate anyone who could walk me through successfully restoring my tablet to its original state.