• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][CM9 KANG][Alpha] Updated 3.5.5---6/27/12

no sweat man..i have no hard feelings..i try my hardest to help anyone out that i come across whos having a problem in general..i deffinetly dont want any problems with anyone...just not me..dont like arguing over a phone with someone in a another part of the country lol..i am open to suggestions from anyone about anything..all i want is a stable cm9 for everyone to use..nothing els

I'll second that. That last thing that we need in here is to be at each others throats. WE are a community and we're here to help one another. Unfortunately, some are a little more opinionated that others and wish to impose their opinions without considering whether or not they are actually right. Those people come and go like the wind, here one minute and gone the next. Good riddance I say! :D
 
LMAO!! Damn Biker, I'd swear you were talking about me!!! LMAO!! :p


LOL, man aren't you supposed to be guiding some people or something?

What are you still doing in here? This Forum is a BIG place with a lot of people that need helping. Be gone I say and get 2 work before you get fired on your first day! lol :rofl:
 
I'm not using that kernel I reflashed back to stock which flashed the stock kernel and what do u mean by renaming the restore file..I've just been unzipping and then going into the folder and putting the bottom file (with all the numbers) into the clockworckmod/backup folder. I did think that I saw the file with the numbers change but only a lil bit and not the internal contents of the file...right now I'm just trying to get back to beta 5 and this time no data 2ext...only problem is the file hroark links to in his op is broken....which I actually mentioned on that thread several weeks ago...if someone could point me in the direction of a link to a working copy of cm7 beta5 no ext I would be greatly appreciative
 
This link is working from Hroark's thread as of the time I'm posting it here, if you still can't get it I'll reupload it and give ya the new link, ok?? Lemme know...


cm-7-HROARK-beta5.zip



And yeah, as far as the md5 mismatch problem I was having while restoring the CM9 backup, solution was to rename the folder back to what it was with no spaces, like I mentioned earlier you may be able to rename the folder to whatever you want so you know what it is you just can't have any spaces in the name of the folder, that fixed the md5 mismatch error for me... :p

Confirmed
You can rename a CWM backup to just about anything you want as long as there are NO spaces. ;)
 
Okay so I've finally gotten it to restore I do thank all of you for the input and advice. I think what the problem was is that some how the md5 sum was missing a line or two of hexadecimal and text and therefore did not match the other files in the folder.once I re-un-zipped the packages a second time all the hex was present and in its rightful place casing success :D

Now comes the test drive :eek:
 
And by the way I didn't mean the ability to download the files he linked to but instead the functionality of the files that you are able to download.......ie I can download them just fine and in cwm the flash seems successful but I get no boot......in the past I had this problem after recovering stock with root but over came it by upgrading to beta 4 and then upgrading to beta 5 than for the link though. :p
 
I was always on ejo6 even on beta 5 I do have the latest cwm 5.0.2.6. I did not happen to check the log after getting the error because I figured it was something I was doing wrong and its long gone now.I did try again after Odin back to rooted stock still no luck I'm now getting this infamous md5 mismatch :D.I tryed making a backup of stock an placing that md5 in the restore file you provided still mismatch....while I was in there I noticed some differences in the md5s and also the fact that the md5s reflect the rest of the restore file maybe this is the problem maybe editing my stock md5 to reflect the contents of the cm9 file would be a possible answer.or maybe taking out nonessential parts of the cm9 file to match my stock md5 :confused: . Also I should mention I have gotten the same error in the past after changing from beta5 to data2ext beta when trying to do an advanced restore of non system items (apps).perhaps something to do with where the info on the restore file is coming from and the change in that when data2ext is applied.

I would also like to thank everyone on the forums.although I have only a few posts I've been watching from afar and always find posts helpful.....even the epic fails :cool:

just caught that. maybe this will resolve your problems.

http://androidforums.com/galaxy-prevail-all-things-root/390234-clockworkmod-v5-0-2-7-file-system-recovery-utility-update-01-12-12-fixed.html
 
Thanks ig I got it worked out...... I ended up using Odin to flash baseband ejo6 and then it worked..... weird thing is I was already on ejo6 and the text in about phone didn't change,but whatever :confused:
 
lol i have no idea what the cwm issue is with the above poster..if i had all the answers we would have a fully working CM9..Not saying its anything he is doing..but there is a number of things that act weird when flashing -backing up or restoring..we have all experienced strange things while doing one of the three..every phone is different..but all im saying is 180 downloads and one person reporting that error? also everything i upload for people to use is tested by me and other people that i trust to be honest..My op clearly states my reasoning for uploading a image to restore and not flash..I actually did it that way to cut down on the confusion for new people who were having trouble getting cm9 up and running..so im not sure what the deal is :D

I had a problem too with md 5 sum mismatch. I got rid of the ones on my sd card and put the ones of on my computer that I had backed up on the sd card. Everything works fine after that the sd card backups somehow got corrupt.
 
I had a problem too with md 5 sum mismatch. I got rid of the ones on my sd card and put the ones of on my computer that I had backed up on the sd card. Everything works fine after that the sd card backups somehow got corrupt.

md5 mismatch is cwm's warning that a file has been corupted usally having to do with data transfer i believe..something changes the md5 during the transfer from pc to phone via usb..not every time.. but it does happen..there are sevral things to try one of which would be to keep deleting the file from your sd and re transfering it again from your pc to your sd if you get the mismatch untill everything is in aline
 
md5 mismatch is cwm's warning that a file has been corupted usally having to do with data transfer i believe..something changes the md5 during the transfer from pc to phone via usb..not every time.. but it does happen..there are sevral things to try one of which would be to keep deleting the file from your sd and re transfering it again from your pc to your sd if you get the mismatch untill everything is in aline

yes, thanks, had figured that out on my own by trying that. like said, i tried all the backups on sd and none would work, every one (6 of them) all said md5 mismatch. so i deleted one, and put one that was saved on pc to sd and worked so removed all others and put on sd from pc and all work now. sorry for repeating myself here but might not have been clear in last post. so something corrupted all my backups on sd, but all is fine now:D:D:D
 
yes, thanks, had figured that out on my own by trying that. like said, i tried all the backups on sd and none would work, every one (6 of them) all said md5 mismatch. so i deleted one, and put one that was saved on pc to sd and worked so removed all others and put on sd from pc and all work now. sorry for repeating myself here but might not have been clear in last post. so something corrupted all my backups on sd, but all is fine now:D:D:D

Out of habbit i have always placed copies of CWM backups on my pc..just safe practice..plus you never know when the shit may hit the fan
 
Out of habbit i have always placed copies of CWM backups on my pc..just safe practice..plus you never know when the shit may hit the fan

That's a good habit to get in Johnny. I do the same thing and have had to use them on a few occasions.;)
 
i completely agree..i try to keep the backups current..after any serious changes ..or any changes for that matter
 
i didnt see your apology bro..but anyway i am no developer by any means dude..so i will do whatever i can to help ppl play with ics..if people are having trouble restoring i can make it flashable..but the problem with that is it breaks root and their are permission and su issues because of su binary..if any one has suggestions im all ears..

I'm not entirely sure but if you wanted to give it a try it'd be worth a shot. Basically as long as we have CWM our phones will always and forever be rootable. All you would have to do is include a second link to the Superuser cwm Zip

See thread here:
http://androidforums.com/galaxy-prevail-all-things-root/532266-root-fa19-users-cwm.html

Te most up to date version (including it's binaries) can always be found at Superuser downloads | /superuser

I'm not entirely sure if reflashing SU will require a re installation of busybox but even if so it's easily accessible via the play store.

Your istructions would just be download both files, place on sd card, flash CWM9, Flash SU.

Anyway It's worth a shot, I'm sure part of the reason this thread is less active than it could be is because of the installation method (not like I'm saying anything is wrong with it) because some users probably just don't feel comfortable flashing a backup rather than an installation zip.
 
the issue with superuser and CM9 is happening at download some now, you could download CM9 from Hroarks original thread via your pc and flash it and possibly have issues with SU binary..On the other hand you could download it from his original thread via the browser on your phone and have no issues..

for the longest time i thought it was something that i was changing that was messing with SU binary, but i dont think its the case..Its either happening from the download or the transfer i dont know..deffinetly above my pay grade....but you end up with a binary called Legacy and it will not update or grant SU privlages..i did research on it and came up with it a few times but no defenitive way to fix it..I tried everything..including new version of SU and everything flashable from the developers web page that you listed..nothing seemed to work..also i used a few different apps to check for root after you get the legacy binary and none of them would detect busybox..

Edit.. once i had a solid dl of Hroarks original that wasnt giving me SU issues..thats where i got started adding a few things and making a few changes..i originally had flashable zips uploaded in the OP but i got bombarded by pms of ppl having issues with SU..thats why i thought it would be easier for ppl to simply restore a backup
 
I don't know what to say about that one :/

Do you happen to still have a link to a broken flashable zip lying around? I'd like to take a look at it. I highly doubt I'll find anything but hey, you never know.

If you do just PM it to me so you don't get a bunch of users trying to download it thinking it's a secret update or something lol.
 
I don't know what to say about that one :/

Do you happen to still have a link to a broken flashable zip lying around? I'd like to take a look at it. I highly doubt I'll find anything but hey, you never know.

If you do just PM it to me so you don't get a bunch of users trying to download it thinking it's a secret update or something lol.

i dont have a copy of the old zips..but i know i can recreate it..ill whip it up tonight or tommorow and pm it to you..i apreciate the help
 
i dont have a copy of the old zips..but i know i can recreate it..ill whip it up tonight or tommorow and pm it to you..i apreciate the help

No problem but like I said, don't put too much faith in it. I'm just gonna poke around and see what I can find.
 
Back
Top Bottom