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.
Related
Hi,
I have the recommended clockwork mode (5.something) but when I do flash install, it just resets to my stock? I did do wipe data/factory reset as per install and then I install it afterwards, yet it just installs back to like I got the phone with google asking me about GPS and it's still got samsung apps etc.
When I install CM7 it does say installation complete in text form and the likes also.
Any help would be greatly appreciated.
Links: http://forum.xda-developers.com/showthread.php?t=1263292
shadowdogg said:
Hi,
I have the recommended clockwork mode (5.something) but when I do flash install, it just resets to my stock? I did do wipe data/factory reset as per install and then I install it afterwards, yet it just installs back to like I got the phone with google asking me about GPS and it's still got samsung apps etc.
When I install CM7 it does say installation complete in text form and the likes also.
Any help would be greatly appreciated.
Links: http://forum.xda-developers.com/showthread.php?t=1263292
Click to expand...
Click to collapse
So it looks like you're flashing a mod of CM7 for your device. After flashing CM7, and you go through all the standard set-up procedures, have you gone into your Settings > About phone and doubled checked which ROM is installed? In this menu it will list the ROM/Mod version, the kernel, etc.
Also, are you using the recommended Recovery from the ROM thread? Looks like it's v5.0.2.3...
Hi,
Yep I have got the latest on that thread. It is now blue text instead of orange from the official one. So far I have tried to mount /system /data before installing cm7 but still nothing changes.
I noticed on the 'installation' it only has [*] for installation complete.
Is that normal?
Or should be it [*] for all?, extracting system, setting permisions, flashing kernel all have just [ ]
shadowdogg said:
Hi,
I think I had to mount /system and /data but I accidently did format /system /data. That means i have to install back to stock and retry?
Edit: Forgot I had a backup
Ok, it still doesn't seem to like it?
Yeah I do have the one mentioned. Blue text update compared to official 4 one.
I noticed on the 'installation' it only has [*] for installation complete.
Is that normal?
Or should be it [*] for all?, extracting system, setting permisions, flashing kernel all have just [ ]
Click to expand...
Click to collapse
I'm having a little trouble following you.... in terms of flashing a custom ROM, you shouldn't need to mount any partitions manually. During the installation process those are taken care of automatically.
I think every file will say something slightly different when a flash is complete. I'm using 4EXT Recovery, which is based on Clockworkmod, and I believe when I flash CM7 (a nightly mod) it actually says "installation complete." But each one is a bit different so it's hard to say... but you are sure that when you boot into the phone after seemingly successfully flashing CM7 it's not CM? I only ask because the setup wizard process is very similar between lots of AOSP ROMs. Perhaps it just looks similar? It just doesn't make sense that you're flashing a ROM successfully, but then you're still on stock afterward. Especially because if you really did a factory reset first, then flashed CM and CM didn't install, there's no way your stock ROM would still be on the device. If anything, you'd have no OS...
Ditamae said:
I'm having a little trouble following you.... in terms of flashing a custom ROM, you shouldn't need to mount any partitions manually. During the installation process those are taken care of automatically.
I think every file will say something slightly different when a flash is complete. I'm using 4EXT Recovery, which is based on Clockworkmod, and I believe when I flash CM7 (a nightly mod) it actually says "installation complete." But each one is a bit different so it's hard to say... but you are sure that when you boot into the phone after seemingly successfully flashing CM7 it's not CM? I only ask because the setup wizard process is very similar between lots of AOSP ROMs. Perhaps it just looks similar? It just doesn't make sense that you're flashing a ROM successfully, but then you're still on stock afterward. Especially because if you really did a factory reset first, then flashed CM and CM didn't install, there's no way your stock ROM would still be on the device. If anything, you'd have no OS...
Click to expand...
Click to collapse
Hi apologies for misunderstanding. I shall try and explain what I meant. I presumed that [*] meant similar to a tick - wasn't sure if all of them had to go [ ] -> [*]
Well I look in the android and it is 2.3.3 and this should be 2.3.7. It also has samsung apps etc still there. All that happens is, I do it. Reboot, it shows "android" for 3 seconds - goes blank for a little while and comes back on but with samsung based one still.
shadowdogg said:
Hi apologies for misunderstanding. I shall try and explain what I meant. I presumed that [*] meant similar to a tick - wasn't sure if all of them had to go [ ] -> [*]
Well I look in the android and it is 2.3.3 and this should be 2.3.7. It also has samsung apps etc still there. All that happens is, I do it. Reboot, it shows "android" for 3 seconds - goes blank for a little while and comes back on but with samsung based one still.
Click to expand...
Click to collapse
Hmm... okay, this is very strange behavior. There are so many possibilities of things that could be responsible. Have you tried re downloading the ROM zip file? Or perhaps reflashing your Recovery image? If there is a specific thread for your device I would definitely post your issue over there. Perhaps even in the thread where you got the ROM from... who knows, maybe others with your device/Recovery version have experienced something like this.
I'm sorry I couldn't be more helpful, but without using your specific phone/Recovery/ROM I can't try to recreate the problem, and thereby help find a solution.
Yeah I would do but I need to randomly make up 10 posts to post there
shadowdogg said:
Yeah I would do but I need to randomly make up 10 posts to post there
Click to expand...
Click to collapse
Ah... to post in the development section? I see... well, perhaps you could try the Q&A for your device in the meantime. I don't believe there is a minimal post number required for that forum. Or, we could keep going back & forth here until you have 10.
Ahah! I wonder... I think I may have only flashed the 'fix' rather than the thing itself. It was only 5MB the fix which if I wasn't a complete noob I should have figured out thats rather small for a complete ROM right away
shadowdogg said:
Ahah! I wonder... I think I may have only flashed the 'fix' rather than the thing itself. It was only 5MB the fix which if I wasn't a complete noob I should have figured out thats rather small for a complete ROM right away
Click to expand...
Click to collapse
Oh yeah... ROMs can range from 70-120 MB. But never just 5 MB. Glad you figured it out.
Guess what - it works! Thanks for your help though
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:
When I install this rom, [ROM][XXLPH]Thebyani Rom V3.2_ICS for SGS2 (ICS Style), I get an error that says Signature Failed, Installation Aborted. How can I fix this? I tried renaming the ZIP to update.zip
Although the instructions to install that ROM don't appear to say that you need to do those things from CWM recovery, you do. Not stock recovery, which seems to be what you're doing.
However, if you're struggling at this stage, I would strongly advise against flashing any leaked, buggy, unstable ICS ROMs.
I actually managed to install it on a phone which had already been rooted before
I actually managed to install it on a phone which had already been rooted before
oinkylicious said:
Although the instructions to install that ROM don't appear to say that you need to do those things from CWM recovery, you do. Not stock recovery, which seems to be what you're doing.
However, if you're struggling at this stage, I would strongly advise against flashing any leaked, buggy, unstable ICS ROMs.
Click to expand...
Click to collapse
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
You can install a kernel to see if that will solve the issue, but as far as I can see, the Carbon devs do not provide a stand alone kernel for their rom. You could use AJK or one of the other kernels though. Or you could just reinstall the rom to see if it would clear up the problem.
Or, you could extract the zImage from the full rom and use Mobile Odin.
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
jjack0310 said:
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
Click to expand...
Click to collapse
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
creepyncrawly said:
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
Click to expand...
Click to collapse
I followed Step 3a on this post: http://forum.xda-developers.com/showthread.php?p=18576627#post18576627
Unfortunately, for some reason, ODIN Lite was not recognizing DD_03042012.zip file. So I went with Siyah and downloaded the TAR file used ODIN to get the clockwork mod. It worked.
Now the problem is I cant restore my backup. I know the same backup has worked before, not it is giving me an error "Error while restoring /system". wth!
I dont remember what version of Clockwork Mod I had. I know it was an older version, becuase it didnt have touch.
How do I get a previous version of CWM?
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Actually,
Creepyncrawly, thanks for your help.
I downloaded ShoStock 3 and flashed it to get the previous version of CWM, and then was able to do a restore.
Sigh.. no harm done.
You can have your thread back... good luck!!
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
Yes, as stated by creepyncrawly, u can use mobile odin or regular odin to flash a kernel.
But i would suggest doing a MD5 check on the Rom u downloaded, because the Rom u flashed may be that of a corrupted download. If MD5 doesn't match then redownload, check MD5 and if good, reflash the Rom.
.....or maybe the nightly is messed up.
Sent from my SAMSUNG-SGH-I747 using xda premium
Mighty_Rearranger said:
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
Click to expand...
Click to collapse
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
I can see why you could be upset that someone hijacked your thread.
I only see one question in your original post, which I believe I answered. You also requested assistance which I thought I provided.
Let me be a little more specific for you. Yes, you can flash just a kernel without re-flashing the system. However, you will need either an Odin flashable tar of the kernel, or you will need to install Mobile Odin and then you can flash a kernel directly from a zImage file.
However, I think 4-2ndtwin has the right of it. It was probably a bad flash, even though the phone booted normally. You should consider re-flashing the entire rom.
If you are not clear about anything, please ask questions.
Never mind.
I concluded it wasn't worth it just because I was lazy backing up stuff.
I used this: http://forum.xda-developers.com/showthread.php?t=1525821, then flashed a clean ROM.
Thanks for the help, you guys are awesome.
Hello everyone,
I'm having problems when I'm trying to install 4.4 roms I keep getting this error
set_metadata_recursive: some changes failed
E:Error in/sdcard/cyanaosp-v3.4.0_2.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
After looking into it most people say it's cause by old cwm version. However I couldn't find a newer version of cwm for my vibrant.
I currently have semaphore cwm recovery v6.0.3.8
Please help
SoulEater- said:
Hello everyone,
I'm having problems when I'm trying to install 4.4 roms I keep getting this error
After looking into it most people say it's cause by old cwm version. However I couldn't find a newer version of cwm for my vibrant.
I currently have semaphore cwm recovery v6.0.3.8
Please help
Click to expand...
Click to collapse
Have you tried reflashing right after that error? Please do so. Worked here.
CWM version doesn't have to do much if at all with this if you are above 6.0.0.0. Sometimes I use a March 2014 kernel (Semaphore) which has an older CWM (still above 6.0) and everything flashes just fine.
@nirogu325
Quick question for you that I didn't want to put in the CM11 thread. I have my old Vibrant that I gave to my son and it has Slim 4.3 build 1, Semaphore and CWM 6.0.3.8 on it. I wanted to put him on CM11 but when I flash it I get a Status 7. Normally, I know how to get around this but for some reason it is not letting me flash it because it says that my device is a I-9000. I've checked Settings>About Phone and it shows T959 and I've even checked my build.prop and nowhere does it say I-9000. The only thing that I have from the I-9000 is the GB Bootloaders.
Any ideas?
Woody said:
@nirogu325
Quick question for you that I didn't want to put in the CM11 thread. I have my old Vibrant that I gave to my son and it has Slim 4.3 build 1, Semaphore and CWM 6.0.3.8 on it. I wanted to put him on CM11 but when I flash it I get a Status 7. Normally, I know how to get around this but for some reason it is not letting me flash it because it says that my device is a I-9000. I've checked Settings>About Phone and it shows T959 and I've even checked my build.prop and nowhere does it say I-9000. The only thing that I have from the I-9000 is the GB Bootloaders.
Any ideas?
Click to expand...
Click to collapse
Status 7 sometimes tends to be the assert lines inside the ROM .zip. Check inside the zip (I use 7Zip on my PC): META-INF > com > google > android > updater-script. Check in that script (I use Notepad++ on my PC) the first lines. In the picture I attached, I show you an example of the assert lines. Delete those if present. If that doesn't yield resuls, it could be the GB Bootloader. Although I could flash the newer CM builds with them by deleting the assert lines I showed you. I no longer have the GB Bootloader, so I had to flash my way through JFD to ICS and then to KK again.
nirogu325 said:
Status 7 sometimes tends to be the assert lines inside the ROM .zip. Check inside the zip (I use 7Zip on my PC): META-INF > com > google > android > updater-script. Check in that script (I use Notepad++ on my PC) the first lines. In the picture I attached, I show you an example of the assert lines. Delete those if present. If that doesn't yield resuls, it could be the GB Bootloader. Although I could flash the newer CM builds with them by deleting the assert lines I showed you. I no longer have the GB Bootloader, so I had to flash my way through JFD to ICS and then to KK again.
Click to expand...
Click to collapse
I just did it in Root Explorer. Anyways what I did was I deleted those Assert lines, rezipped it up and flashed. Got a failure due to partition errors (probably because for some reason it was still reading as an I-9000) and said if I wanted to continue to reflash the package. So I flashed my "rebuilt" package and gapps. Was faced with the Set-Up Wizard FC issue, so I thought that maybe I would try to reflash the unaltered CM11 zip to see if it fixed it (before I searched for the solution). It went through the first time with no errors. Still have the Set-Up FC issue, but once I get in my house where there is wifi (no sim in this phone), I can fix that right up, cause I know how to use the search function.
Anyways, thanks for your help. If it came down to it, I would have flashed the Froyo BLs, but this was just as easy. If the next time the ROM updates and I can't get past that, I may have to flash them but I doubt it since I "sort of" tested that philosophy with my reflash from above.
Woody said:
I just did it in Root Explorer. Anyways what I did was I deleted those Assert lines, rezipped it up and flashed. Got a failure due to partition errors (probably because for some reason it was still reading as an I-9000) and said if I wanted to continue to reflash the package. So I flashed my "rebuilt" package and gapps. Was faced with the Set-Up Wizard FC issue, so I thought that maybe I would try to reflash the unaltered CM11 zip to see if it fixed it (before I searched for the solution). It went through the first time with no errors. Still have the Set-Up FC issue, but once I get in my house where there is wifi (no sim in this phone), I can fix that right up, cause I know how to use the search function.
Anyways, thanks for your help. If it came down to it, I would have flashed the Froyo BLs, but this was just as easy. If the next time the ROM updates and I can't get past that, I may have to flash them but I doubt it since I "sort of" tested that philosophy with my reflash from above.
Click to expand...
Click to collapse
The Setup Wizard FC only occurs if you flash everything at once (ROM + GApps). It's been happening since 4.4.4 was released a month ago. To bypass that you either:
1. Lower the notification panel and press the date on the upper left side. Calendar should open prompting you to enter your Google credentials along with Wi-Fi if not connected. Do so, then tap Back until you go back to the Setup Wizard. No more FC.
OR
2. Flash the ROM alone without GApps. Let it settle for 10 minutes after boot. Then you proceed to flash everything else.