--Mods please delete this thread since people are clearly misunderstanding the title--
I have dev's to test my roms and some people are just too impatient to see some results. I will post back in the Captivate Glide thread once I fix everything and it is pretty stable. Until then, you guys can make your own rom.
Thanks,
rkrishnan2012
downloading now...
will let you know how it goes...
The three main things I need to know asap:
1. Does it boot?
2. If not, does it go to bootscreen?
3. Does Wifi work?
doing backups first... gonna take a few
I would like to know the same!
Sent from my SAMSUNG-SGH-I927 using XDA
Backing up as well. Back Inna few!
Sent from my SAMSUNG-SGH-I927 using XDA
Awesome! Ill prolley do this tonight.
Sent from my SAMSUNG-SGH-I927 using XDA
Ok update.. I got install aborted... imma try another download and report back!
Sent from my SAMSUNG-SGH-I927 using XDA
Looks awesome. Downloading..
getting a status 0 error and installation aborts
Okay. Thanks Guys for testing it out! I will try to fix this up and post an update possibly tomorrow....
Edit: Maybe try with another clockworkmod in the mean time and try to get it to work?
Also, I will try to add the cranium kernel to this...
EDIT2: I have another zip for people to try:
Okay...Check this one out:http://www.mediafire.com/?f8tbghkypgx9oi1
Edit3; If this also doesn't work, I know exactly why it wouldn't work. I need to recompile the kernel and upload a new zip tomorrow...
I tried your second upload (with CWM) and also got a (Status 0) Installation aborted.
It showed this:
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cyanogen_galaxys2att-ota-eng.root.zip
(Status 0)
Installation aborted.
I just read on another forum that the cause of this error could be this: "The Author has an extra update-script in the command folder or go and delete the update-script~ from the archive." I'll see if I can try this.
Also, I made sure Signature Verification was disabled (in "install zip from sdcard" screen).
You do realize that you're flashing a ROM made for a Device with an Exynos SOC on a device that has Tegra 2 ?
That's not the only problem. I need to fix the kernel and it will work...I will release that today
rkrishnan2012 said:
That's not the only problem. I need to fix the kernel and it will work...I will release that today
Click to expand...
Click to collapse
With all due respect, again, how are you going to flash something developed for a phone that doesn't resemble on the minimum, to the glide ?
I know you're a Dev, and of course, I believe that this could be a misunderstanding between us, but, again, what you're saying just doesn't make sense.
Why don't we just use the gingerbread kernal that we already have?
Sent from my SAMSUNG-SGH-I927 using XDA
correct me if i am wrong, but i believe that cyanogenmod requires its own kernel
Hi,
Firstly, it's been a while since I last compiled a gingerbread rom to a phone, so I may just be blabbering about something that is not true.
My plan is to take the gingerbread rom for the samsung galaxy s2 and combine that with the Kernel you guys already have and tweak the galaxy's board config to include the tegra 2 processor you guys have. I did this and now I am trying to recompile right now. Also, I used the cranium kernel in this rom and some of the device drivers from the old gingerbread rom you had...This will hopefully make it at the very least boot up to the CM logo.
Also, I do not think that CM needs a special kernel. It will do with any kernel that supports gingerbread.
EDIT:
Here is a new version with your cranium kernel...hopefully this boots: http://www.mediafire.com/?yivbr0rq3t3h00b
EDIT2;
Someone tested this for me and reported that I screwed up the build.prop (so it wont install via rommanager). I will fix this and reupload a new rom...
Edit 3: Fixed, try this one...http://www.mediafire.com/?sm1u311kzp3j2tu
Edit 4: I needed to also update the update-script in the zip file. Also, I removed the stupid check for whether your phone is the right model. I really don't feel like debugging that right now without a phone to play with...Will upload in a few...
Edit 5: I already have a dev testing it but if you want to help, plz try this out:
http://www.mediafire.com/?w67tnio7200qjc4
Thanks,
Rohit
Do you plan on getting the device?
sent from my captivate glide
Unless someone donates...probably not
Related
I'm a noob, but not a noob, k?
I've flased a dozen roms already, but for the life of me, after cleaning up everything, took the following steps:
Wiped data/factory reset
Wiped cache partition
Advanced > Wiped Dalvik Cache
Then
Install .zip from sd card - Selected ThunderHawk-4.zip
It goes like this:
Opening a Black hole...
Initializing Systems...
Mounting File System...
MTD System Detected...
Reticulating Splines...
Formatting /System.....
Formatting /Cache......
Formatting /Data.......
Installing RandomROM...
file_getprop: failed to stat "/sdscard/clockworkm
od/options.cfg": No such file or directory
E:Error in /sdcard/ThunderHawk_V.zip
(Status 7)
Installation aborted.
I don't get it...
Can someone please tell me where I'm going wrong?
Suggestions would really help Ya'll are awesome!
follow RandomKing's instructions (as found on his blog site) for putting an options.cfg file in place before the install. His original doc mentions that it's optional but I think his installer is not creating a file if one does not already exist.
That WORKED!
Did exactly what you said, and it worked.
For future reference for others wondering:
Visit the blog
[(REPLACE "XX" with "tt") hxxp://randomkings.wordpress.com/android/samsung-epic-4g/gingerbread-2/ ]
Read under Installation Steps, you'll see Optional Customization all the info you'll need is right there.
Download the options.cfg file, open with notepad - edit to your preference, and send it to sdcard/clockworkmod/(paste-options.cfg in under backups) you'll be all set. Go into CWM Recovery and install from zip as you normally would.
Thanks so much for the tip, and helping me out!
Woooo!
ItalianFurby said:
Did exactly what you said, and it worked.
For future reference for others wondering:
Visit the blog
[(REPLACE "XX" with "tt") hxxp://randomkings.wordpress.com/android/samsung-epic-4g/gingerbread-2/ ]
Read under Installation Steps, you'll see Optional Customization all the info you'll need is right there.
Download the options.cfg file, open with notepad - edit to your preference, and send it to sdcard/clockworkmod/(paste-options.cfg in under backups) you'll be all set. Go into CWM Recovery and install from zip as you normally would.
Thanks so much for the tip, and helping me out!
Woooo!
Click to expand...
Click to collapse
no prob, I ran into the exact same thing this morning so i had recent experience. have fun! :-D
---------- Post added at 05:44 PM ---------- Previous post was at 05:00 PM ----------
oh one thing worth mentioning: RandomKing has released ThunderHawk V now. Interestingly, it carries a label saying FC09 but it's still actually using EL30.
I believe the reason behind that is to cut down on the "Install update" messages coming from Samsprint. He has started a new thread for ThunderHawk V in the dev forums.
It is FC09 just the kernel is EL30.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
It is FC09 just the kernel is EL30.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Kennyglass123 hence forth shall be known as kenoracle; because he sees and knows all
but you knew I was going to type this
I should have taken the red pill
ctinxp 1595
kennyglass123 said:
It is FC09 just the kernel is EL30.
Click to expand...
Click to collapse
ah ok thanks, i think i read that earlier today but apparently it didn't sink in. that will teach me to read XDA from work..and actually try to pay attention to work.
jdelano said:
Kennyglass123 hence forth shall be known as kenoracle; because he sees and knows all
but you knew I was going to type this
I should have taken the red pill
Click to expand...
Click to collapse
AKA Kenfuscious as well...LOL.
Sent from my PantechP4100 using xda premium
MattSF said:
follow RandomKing's instructions (as found on his blog site) for putting an options.cfg file in place before the install. His original doc mentions that it's optional but I think his installer is not creating a file if one does not already exist.
Click to expand...
Click to collapse
I've just uploaded a newer version. Don't flash it if you already have it working, but this is no longer a problem.
kennyglass123 said:
It is FC09 just the kernel is EL30.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yup. Most people don't seem to know, but you can use almost any Gingerbread Kernel without issue. But I'll be adding in an FC09 kernel soon enough thanks to Bbelos.
RandomKing said:
I've just uploaded a newer version. Don't flash it if you already have it working, but this is no longer a problem.
Yup. Most people don't seem to know, but you can use almost any Gingerbread Kernel without issue. But I'll be adding in an FC09 kernel soon enough thanks to Bbelos.
Click to expand...
Click to collapse
Great news and awesome news. thanks, RK!
Just thought I'd add, Bbelos gave me a custom FC09 kernel that's linked in my thread now as well.
It is up in development.
Sent from my SPH-D700 using xda premium
I rooted my Bell Galaxy SIII this afternoon using Mr. Robinsons method.
All good. Have root. Installed CWM (LTE Variant and other newer listed on Mr. Robinsons thread. One at a time, same error)
Booted into recovery and tried to install CM10 after factory reset, dalvick wipe, yada, yada yada.
I get the error:
Assert Failed: getprop("ro.product.device*) =="E:Error in /SDCARD/cm-10-20120912-nightly-d2Att.zip (Status 7)
Might be some left out as not all of the error code is shown.
Tried multiple times to download CM using different browsers and directly on the phone.
I am able to restore factory rooted image no problem.
I then installed TWRP v2.2.2.0
Same error when trying to install CM10-current nightly
I'm assuming that this is related to device ID and I'm trying to install ROM's not suitable for it?
I've tried with AOKP version from Task and get same error.
http://forum.xda-developers.com/showthread.php?t=1766684
Pretty sure these are good for Bell version....
Any idea's or confirmation that these won't work with my phone.
Thanks
Mike
You need cwm 6.0.1.2
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Not sure what the issue is but I can tell you that I have installed task aokp with twrp and cwm recovery versions back to 5.5.0.4 with no problems on my Bell phone.
liltitiz said:
You need cwm 6.0.1.2
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks,
Just so I learn something out of this...Why do I need this? I understand that both versions of CWM and TWRP I installed are used by people with the same hardware?
Just want to understand what I am missing.
Thanks,
Mike
EDIT: Okay, after doing some looking at the Build.prop file I see I have a D2Cann and the rom is listed as for D2ATT so the assumption I'm making is the older recoveries match that and won't proceed while CWM 6.012 doesn't? I'm downloading and going to install the latest CWM now to try and confirm this. Still not sure why this has worked for some people and not for me unless they are changing their build.prop but I haven't been able to find that to confirm it.
If you go in the cm10 thread in original developpenent, they specify which recovery to install with a link to download it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mikewestlake said:
EDIT: Okay, after doing some looking at the Build.prop file I see I have a D2Cann and the rom is listed as for D2ATT so the assumption I'm making is the older recoveries match that and won't proceed while CWM 6.012 doesn't? I'm downloading and going to install the latest CWM now to try and confirm this. Still not sure why this has worked for some people and not for me unless they are changing their build.prop but I haven't been able to find that to confirm it.
Click to expand...
Click to collapse
its not the recovery that does the actual check for the device. it's the assert in the updater-script of the rom that you're trying to flash. CM10 checks for "d2att" and if thats not what in your build.prop it will error out and refuse to flash. Either remove that line from the updater-script or edit your build.prop.
Also. you need to try your best to read the OPs of the roms you're thinking about flashing. In the CM10 thread they even give you the information of which recovery you need to use and where to get it.
task650 said:
its not the recovery that does the actual check for the device. it's the assert in the updater-script of the rom that you're trying to flash. CM10 checks for "d2att" and if thats not what in your build.prop it will error out and refuse to flash. Either remove that line from the updater-script or edit your build.prop.
Also. you need to try your best to read the OPs of the roms you're thinking about flashing. In the CM10 thread they even give you the information of which recovery you need to use and where to get it.
Click to expand...
Click to collapse
Thanks,
yeah, in this case, I thought I read everything and maybe got too much info. Still for coming from other devices (HTC DesireZ, Legend, couple of Asus transformers), having different device versions is a new step to tick off and learn.
Had the same issue with your rom too. Can I ask that you add a note to the OP about making sure Canadian versions change the build prop or only use CWM 6 cause I had the same issue with yours when trying to install. I'm not going to be the only guy that missed this.
Gonna install CWM 6 and change build prop to install your ROM. It looks good.
Thanks again.
Mike
mikewestlake said:
Thanks,
yeah, in this case, I thought I read everything and maybe got too much info. Still for coming from other devices (HTC DesireZ, Legend, couple of Asus transformers), having different device versions is a new step to tick off and learn.
Had the same issue with your rom too. Can I ask that you add a note to the OP about making sure Canadian versions change the build prop or only use CWM 6 cause I had the same issue with yours when trying to install. I'm not going to be the only guy that missed this.
Gonna install CWM 6 and change build prop to install your ROM. It looks good.
Thanks again.
Mike
Click to expand...
Click to collapse
Using ROM Manager helps you keep your CWM recovery up to date. You can find the app in the play store
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Sent from my SAMSUNG-SGH-I747 CM10 + KT747, 96-2106 MHz, noop, ktoonservative, undervolted, 3150mAh battery.
Thanks to: Ktoonsez, Task650 and Cyanogen for their amazing works!
Just got my gs3 today and decided to root using this method http://forum.xda-developers.com/showthread.php?t=1746682
Not really so tech-savy with this yet and after the whole root process of odin3 i reboot into recovery, wipe/cache/dalvik then flash the new miui 2.10.19 http://miuiandroid.com/community/threads/2-10-19.18540/ one i hit flash it says installation failed blah blah blah (status 7) getprop. Yeah all that junk, so i searched up on the forums and the only solution i find is to update cwm and i have, to 6.0.1.4 and still same thing!! installation error, aborted. Can someone please help me out :crying: I'm sorry if im a noob, just trying to flash a rom here
Update CWM via ROM Manager.
Download again
Sent from my SGH-T999 using xda app-developers app
use twrp
theexel said:
Update CWM via ROM Manager.
Click to expand...
Click to collapse
i did, still no luck
mt3g said:
use twrp
Click to expand...
Click to collapse
and this was my last thing i tried before bed last night and still didnt work! should i just unroot then re-root all over again?
How did you update to 6.0.1.4 when 6.0.1.2 is the latest version? And no, you don't need to re root. You don't need root to flash firmware.
Aerowinder said:
How did you update to 6.0.1.4 when 6.0.1.2 is the latest version? And no, you don't need to re root. You don't need root to flash firmware.
Click to expand...
Click to collapse
Looking on the forums someone posted a link to download an updated 6.0.1.4 so I tried that since 6.0.1.2 wasnt working. There's gotta be something simple to fix that I dont know about, ive flashed and rooted my htc sensation and mytouch4g easy and never had installation failure when flashing. Can someone walk me through what exactly I need to be fully rooted and flash a rom!?
How could cwm not be working if its updated to latest version? I dont think im downloading the wrong rom and its not a bad link. Even tried dragging it onto my internal sd wirh debugging off. Btw I have the 32 gb s3 with does not have an external sd.
The way I fix that was I rerootes my phone into latest clockwork recovery. I didn't remove the root I just rerootee it. Look for cwr 6 I think.
Sent from my SGH-T999 using xda app-developers app
From watching the video given for the toolkit, when in odin and have to open up pda then go to the toolkit files and then root all my files are in winRAR type and his are in tar archive type. Does that matter at all? And also when clicking on the pda then root you chose the file /boot-insecure-tmo-t99uvalem-cwm but when in odin and clicking this file on the little winrar icon to the left of the file name its the only one with a little like key lock, doesnt know if thats an issue or anything just something i noticed because when accessing the toolkit files on my c drive and going to the root folder, the key icon is no longer there.. Any ideas??
Reading about people flashing a kernal in recovery then flashing the rom and working but when you flash a rom isnt it flashing the kernal it comes with also? Or is this the problem
Well, I re ran the toolkit, re did the root and odin process same as i did the first time, downloaded rom straight from my phone flashed again still getting status 7 error/ installation aborted -______- ugh...
Brad4891 said:
Looking on the forums someone posted a link to download an updated 6.0.1.4 so I tried that since 6.0.1.2 wasnt working. There's gotta be something simple to fix that I dont know about, ive flashed and rooted my htc sensation and mytouch4g easy and never had installation failure when flashing. Can someone walk me through what exactly I need to be fully rooted and flash a rom!?
Click to expand...
Click to collapse
Look at my signature for the proper CWM. I don't know where you saw 6.0.1.4 for our device, but the main thread and the developers website show no sign of it. And download CM10 from get.cm, d2tmo. If you that doesn't work, you don't have a SGH-T999.
I can't believe I didn't see this before....what is the exact file name of the rom you are flashing?
I looked and did not see our phone listed in the op. Looks like the international one is there (codename m0?). But no d2tmo, d2att, etc.
Unless I just missed it there, you do not want to even try flashing that anymore! If I'm right you just got very lucky dude!
Sent from my SGH-T999 using xda app-developers app
Aerowinder said:
Look at my signature for the proper CWM. I don't know where you saw 6.0.1.4 for our device, but the main thread and the developers website show no sign of it. And download CM10 from get.cm, d2tmo. If you that doesn't work, you don't have a SGH-T999.
Click to expand...
Click to collapse
Okay, so i just followed and installed everything you had in your signature and it finally is flashing hellfire!! Hours of frustration i think i finally got it! Thank you so much
Brad4891 said:
Okay, so i just followed and installed everything you had in your signature and it finally is flashing hellfire!! Hours of frustration i think i finally got it! Thank you so much
Click to expand...
Click to collapse
I thought you were trying to flash miui...
Glad you got it sorted out.
Just for the future though, never flash anything not built for the TMobile SGH-T999 (codename d2tmo). If you do flash an international GS3 rom it will brick your device. I think this woulda happened had the miui rom from the link in op actually flashed.
Sent from my SGH-T999 using xda app-developers app
Aerowinder said:
Look at my signature for the proper CWM. I don't know where you saw 6.0.1.4 for our device, but the main thread and the developers website show no sign of it. And download CM10 from get.cm, d2tmo. If you that doesn't work, you don't have a SGH-T999.
Click to expand...
Click to collapse
DocHoliday77 said:
I thought you were trying to flash miui...
Glad you got it sorted out.
Just for the future though, never flash anything not built for the TMobile SGH-T999 (codename d2tmo). If you do flash an international GS3 rom it will brick your device. I think this woulda happened had the miui rom from the link in op actually flashed.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I was at first but then changed my mind, both werent working before hand though when i was getting the errors.
And im using hellfire and the rom is super smooth like butter. I have one problem though, its notifications. Whenever receiving texts i dont get a vibration or light pulse. Sometimes randomly i get a vibration. Anyone know how to fix?
So some of u know of thia status 7. Which is the updater script, checking for the right phone model. Some devs i guess mess up on this and they dont install correctly. My problem is the guide says to change updater-script by putting .txt to edit it. So i did what i had to do then i came back and the .txt was gone and now i cant rezip it.
Sent from my SPH-L710 using xda premium
Why are you editing it in the first place if it's checking for a different device model?
And on the Windows the extensions are hidden by default.
Becuz its on every rom. Ik for a fact its for the L710. But cwm current recovery is tweaked for some ppl and cant install roms. My problem is getting the updater-script file back to its original state after getting rid of the problem that aborts installing a new rom. How to do u see the extensions then.
And cnexus u mention using boot manager to dual boot. If u scroll down it says it definitely doesn't support samsung devices
Sent from my SPH-L710 using xda premium
unrevoked said:
Becuz its on every rom. Ik for a fact its for the L710. But cwm current recovery is tweaked for some ppl and cant install roms. My problem is getting the updater-script file back to its original state after getting rid of the problem that aborts installing a new rom. How to do u see the extensions then.
And cnexus u mention using boot manager to dual boot. If u scroll down it says it definitely doesn't support samsung devices
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Do you mean the AOSP roms?
My understanding the new cm10.1 based aosp roms check for the updated bootloader that comes with md4. All you have to do is flash the md4 aio firmware update that's in Freeza's thread. All the newer aosp roms will flash correctly. That's what I've been reading for a couple of weeks. Trying to alter it as you are is ridiculous in my opinion as the purpose is for it to check that your phone is on the newest bootloader for a reason.
Sent from the future via Xparent Green Tapatalk 2
My way is just as easy. Just take the updater-script and delete everything till you get to where it says "source". Its some peoples recoveries or something a dev messed up on. But i finally got out of rc2 and on to liquid smooth
Any rom not just aosp. Im assuming. Everytime u install a new rom it checks if u have the right phone. Well if somthen isnt right and u know u got the right rom u can edit it and basically hard install it
Sent from my SPH-L710 using xda premium
As of right now i can install any Rom from the T999 that does not require the new boot loader upgrade but i get a status 7 when i try to install the newer roms is there any boot loader for the T999L that supports the Roms
Edit the update script of the zip files to remove the bootloader asserts.
Aerowinder said:
Edit the update script of the zip files to remove the bootloader asserts.
Click to expand...
Click to collapse
How would i do that
There are lines in the with in the roms.zip
meta-inf>com>google>android>updater-script>
assert(getprop("ro.bootloader") =="t999.......) and the three other bootloaders it checks for.
I'm guessing you can remove these lines and rezip and it will flash, but I am not going to do so, and don't plan on trying... I can remove those lines and rezip it for you to try and flash and see how it goes. I would put 20$ down that it won't harm the phone but not 600 (new) or 180 (insurance) lol.
Until someone else tries i will wait
I edit lines in there when roms fail to install cause they are specific to att, just incase anyone else really wants it, just post and let me know. I'm off til Thursday so I have time at some point each day to do so. if anyone with more knowledge wants to confirm let me know, so that there is more comfort to this.
If you could edit it out that would be nice and upload the new package that would be nice
Bray90820 said:
If you could edit it out that would be nice and upload the new package that would be nice
Click to expand...
Click to collapse
I'll work on it in a little bit. Got to do one for an att rom I wanna try anyways. What rom did you wanna try?
Cyanogenmod 10.1 RC4
Wait are you going to be editing the rom or the bootloader
Updater Script in the .zip for the rom.
I was actually looking for the bootloader so i could install whatever rom i wanted
Bray90820 said:
I was actually looking for the bootloader so i could install whatever rom i wanted
Click to expand...
Click to collapse
Ohhhhh not possible yet. And if I remove those and it installs fine, you may still run into errors cause the CM team asks for people to be on the latest bootloaders to have it run no issues.
I'm sure your phone will be apart of the CM/AOSP builds soon enough.
Well I do have RC2 on it right now
That was before all the changes. My personal favorite
I Guess i'll just wait then
Bray90820 said:
Well I do have RC2 on it right now
Click to expand...
Click to collapse
How did you install this? Did you edit the updater-script or did it just flash over?
I'm using TWRP on a T999L and am looking to go custom ROM with CM10.1, but am trying to find more info. I know that I can always go back since @DocHoliday77 & @MotoDefier got the stock ROM all squared away: http://forum.xda-developers.com/showthread.php?t=2308514
DJ_SpaRky said:
How did you install this? Did you edit the updater-script or did it just flash over?
I'm using TWRP on a T999L and am looking to go custom ROM with CM10.1, but am trying to find more info. I know that I can always go back since @DocHoliday77 & @MotoDefier got the stock ROM all squared away: http://forum.xda-developers.com/showthread.php?t=2308514
Click to expand...
Click to collapse
The d2tmo has been updated tir the T999L and the latest nightly is fully working without any modifications needed
Awesome!! Thanks, I was thinking that I might have to flash the ROM then flash the T999L modem. What date are you using? Any issues?
Sent from my SGH-T999L using xda app-developers app
DJ_SpaRky said:
Awesome!! Thanks, I was thinking that I might have to flash the ROM then flash the T999L modem. What date are you using? Any issues?
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
No issues on june 18th