Broke phone backing up ROM - AT&T Samsung Galaxy S II SGH-I777

ATT Samsung I777
History: Updated phone to ICS 4.03 using update from Samsung. Rooted phone using Odin 3V185 to Siyah-v3.4.2-nomswap-I777. Phone has been working fine other than I cannot install apps that my carrier doesn't approve.
Update: So I decided I was going to install Semi_V16c. Downloaded it to my computer then transferred to my SD card. Then I opened ROM manager that was already installed on my phone from what I did a few days ago. Once open I selected backup ROM and it asked for the file name to save backup as. Then my phone rebooted automatically and never came up again. If I remove my battery and hit the power button It will show the Samsung Galaxy SII screev and says GT-I1900 under it and the yield sign. Then when that screen goes away the screen is just black. Not sure how backing up ttriggered this but any help is appreciated. I couldn't find a recovery tutorial in the Q&A sticky.

Forgot to mention that the ICS update I put on was done with Kies

I'm going to say that it was ROM manager that did it. ROM manager does very very bad things.

keeperofthecode said:
Forgot to mention that the ICS update I put on was done with Kies
Click to expand...
Click to collapse
First problem, you used ROM MANAGER, big NO NO.
So you can't boot into recovery using VOL - + POWER , during boot?

Don't. Use. Rom Manager.
The End
Sent from Team Pirate running AOKP

jthatch12 said:
First problem, you used ROM MANAGER, big NO NO.
So you can't boot into recovery using VOL - + POWER , during boot?
Click to expand...
Click to collapse
I can get it into download mode if that is the same. I held the V+ & V- and plugged in USB cable and it goes to downloading... page.

I swaer to god this Is the 10 the ROM manager fail post in like 2 days
Sent from my SGH-I777

keeperofthecode said:
I can get it into download mode if that is the same. I held the V+ & V- and plugged in USB cable and it goes to downloading... page.
Click to expand...
Click to collapse
If you can get into download mode then your okay. Look for a guide on how to use ODIN.
Try this link:
http://forum.xda-developers.com/showthread.php?t=1820112

122ninjas said:
I swaer to god this Is the 10 the ROM manager fail post in like 2 days
Sent from my SGH-I777
Click to expand...
Click to collapse
Sorry guys. I didn't know running a backup from ROm Manager could cause this. I was just going to run backup then follow instructions to install new one from the sticky.

jthatch12 said:
If you can get into download mode then your okay. Look for a guide on how to use ODIN.
Try this link:
http://forum.xda-developers.com/showthread.php?t=1820112
Click to expand...
Click to collapse
So I ran Odin and went back with the same one (Siyah-v3.4.2-nomswap-I777.tar) I used a few days ago and phone still does the same thing.

Using the top directions you gave me I downloaded the file and when I run it (I777UCKH7 OCD With Root) the top left doesn't come up yellow like the directions state so I stopped there.

keeperofthecode said:
Using the top directions you gave me I downloaded the file and when I run it (I777UCKH7 OCD With Root) the top left doesn't come up yellow like the directions state so I stopped there.
Click to expand...
Click to collapse
Try to install samsung kies to get the drivers you need.

122ninjas said:
Try to install samsung kies to get the drivers you need.
Click to expand...
Click to collapse
I got it to go by not putting the phone in download mode until after odin was already running. Other version of odin I used prior didn't require that. It ran and said pass then when phone rebooted it went to this message in recovery screen.
Andriod system recovery <3e>
--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
installation aborted

keeperofthecode said:
I got it to go by not putting the phone in download mode until after odin was already running. Other version of odin I used prior didn't require that. It ran and said pass then when phone rebooted it went to this message in recovery screen.
Andriod system recovery <3e>
--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
installation aborted
Click to expand...
Click to collapse
Went ahead and rebooted phone and it came up. Kernel 2.6.35.7 baseband I777UCKH7 ANDROID 2.3.4.
Can I go ahead with installing Semi 16 using normal instructions. Thanks for all your help.

Doing ANYTHING from rom manager on this phone will have terrible repercussions. Please please do your research and do everything manually in cwm. It isn't that hard.
Sent from Team Pirate!

Nick281051 said:
Doing ANYTHING from rom manager on this phone will have terrible repercussions. Please please do your research and do everything manually in cwm. It isn't that hard.
Sent from Team Pirate!
Click to expand...
Click to collapse
I'm just confused where to start now. My phone appears to be like it was from AT&T but some of the apps I installed are still on there. The version is not ICS anymore so am I still rooted? Do I start at step 4 in the directions for installing the new rom or do I go back to step two which is rooting?

keeperofthecode said:
I'm just confused where to start now. My phone appears to be like it was from AT&T but some of the apps I installed are still on there. The version is not ICS anymore so am I still rooted? Do I start at step 4 in the directions for installing the new rom or do I go back to step two which is rooting?
Click to expand...
Click to collapse
Depends on what exactly you flashed
Sent from Team Pirate!

Do a factory reset if u aren't on the stock ics kernel anymore. Then boot it up and install super user. If you can gain root access you're rooted. Another easy way to check is if you look at the rom u downloaded the name should say whether root was included or not.
Edit: u won't even be able to get into cwm if you have stock kernel installed. Which kernel is installed right now?
Sent from my SGH-I777 using Tapatalk 2

keeperofthecode said:
I'm just confused where to start now. My phone appears to be like it was from AT&T but some of the apps I installed are still on there. The version is not ICS anymore so am I still rooted? Do I start at step 4 in the directions for installing the new rom or do I go back to step two which is rooting?
Click to expand...
Click to collapse
Check your kernel to see if you are still rooted.

122ninjas said:
Check your kernel to see if you are still rooted.
Click to expand...
Click to collapse
Please make sure you know what you are saying before you post.
@OP,
The easiest way to see if you are still rooted is to look in the app drawer. If superuser.apk is still there, then most likely you are still rooted.
If you flashed the stock one-click downloader from the return to the store thread, then you are not rooted, so root first, then install a Gingerbread custom kernel, and then the firmware of your choice. From re-reading your posts, it looks like you flashed the stock plus root one-click downloader, so you should be rooted. In that case, you need to install a Gingerbread custom kernel, and then the firmware of your choice.

Related

[Q] CAN'T Flash?!

So I rooted my phone (2.3.4) and put the MiUi on my SD storage. I have CWM installed and when I go to install the ROM this pops up:
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installing aborted.
So this happens when I try to install the file from the CWM app while on the phone, but it also does this when I just try to boot into CWM.
Any help???
Chubby_Skunk said:
So I rooted my phone (2.3.4) and put the MiUi on my SD storage. I have CWM installed and when I go to install the ROM this pops up:
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installing aborted.
So this happens when I try to install the file from the CWM app while on the phone, but it also does this when I just try to boot into CWM.
Any help???
Click to expand...
Click to collapse
What kernel are you running? Your not using the cwm from rom manager right? Using one from a kernel? You could try and shut off your signature verification setting in cwm that should let you flash it. You'll find the option under the install from sdcard option then just toggle off your signature verifications.
Gutterball said:
What kernel are you running? Your not using the cwm from rom manager right? Using one from a kernel? You could try and shut off your signature verification setting in cwm that should let you flash it.
Click to expand...
Click to collapse
Yeah im using Clock Work Mod... :/
Where is the one that i'm suppose to use? I just want MiUi :/
Chubby_Skunk said:
Yeah im using Clock Work Mod... :/
Where is the one that i'm suppose to use? I just want MiUi :/
Click to expand...
Click to collapse
Like I said you could actually probably flash it with that but you just gotta shut off your signature verification option. Though people have said its not advisable. If you wanna do it the right way? Flash a kernel from development it has the correct cwm built into it.
Gutterball said:
Like I said you could actually probably flash it with that but you just gotta shut off your signature verification option. Though people have said its not advisable. If you wanna do it the right way? Flash a kernel from development it has the correct cwm built into it.
Click to expand...
Click to collapse
I'm still confused. So all I have to is flash a kernel and then it'll work???
Chubby_Skunk said:
I'm still confused. So all I have to is flash a kernel and then it'll work???
Click to expand...
Click to collapse
The correct kernel you need to flash is the siyaah kernel when you do this it will automatically install the correct cwm then you should be able to flash miui no problem.
Wow....................... I tried to install the Kernel in CWM like the dev said, and I get the same error message.... this is getting really annoying. The Atrix was less painful than this is being :/
Chubby_Skunk said:
Wow....................... I tried to install the Kernel in CWM like the dev said, and I get the same error message.... this is getting really annoying. The Atrix was less painful than this is being :/
Click to expand...
Click to collapse
Its just a little different then the atrix was but definetly better! Just gotta get used to some new stuff a little bit. I love this phone! Did you try toggling off the signature verification option??
Gutterball said:
Its just a little different then the atrix was but definetly better! Just gotta get used to some new stuff a little bit. I love this phone! Did you try toggling off the signature verification option??
Click to expand...
Click to collapse
uh, no. how do i do that? I just used Odin3 to flash the .tar file for that kernel.
Chubby_Skunk said:
uh, no. how do i do that? I just used Odin3 to flash the .tar file for that kernel.
Click to expand...
Click to collapse
Odins fine didnt realize you knew how to flash it that way. That'll work!
Gutterball said:
Odins fine didnt realize you knew how to flash it that way. That'll work!
Click to expand...
Click to collapse
Just tried it and i didn't change. it was still the same -_-
This is frustrating. The Captivate was 1000000000000000000000x easier to root and flash.
Gutterball said:
The correct kernel you need to flash is the siyaah kernel when you do this it will automatically install the correct cwm then you should be able to flash miui no problem.
Click to expand...
Click to collapse
SiyahKernel's included CWM has had a lot of problems lately.
The reference CWM kernel to use is codeworkx's CWM kernel - there is a thread on it in Development.
Chubby_Skunk said:
Just tried it and i didn't change. it was still the same -_-
This is frustrating. The Captivate was 1000000000000000000000x easier to root and flash.
Click to expand...
Click to collapse
When you flashed it in odin? you flash it as a pda in download mode right? If you did then you should have the right cwm now and miui should install through cwm.
Gutterball said:
When you flashed it in odin? you flash it as a pda in download mode right? If you did then you should have the right cwm now and miui should install through cwm.
Click to expand...
Click to collapse
well ill try it again.....
Chubby_Skunk said:
well ill try it again.....
Click to expand...
Click to collapse
If that doesn't work then use entropys kernel found here http://forum.xda-developers.com/showthread.php?t=1289460. It kicks ass but you cant use it with miui or cm7. but this will give you the proper cwm then install miui.
This is just f***ing ridiculous. So I tried it and when it works, when the phone boots up it shows:
Samsung Galaxy S II
GT-I9100
under than it shows an yellow triangle with a explanation point inside it. The phone boots up and CMW is nowhere to be seen.....
Chubby_Skunk said:
This is just f***ing ridiculous. So I tried it and when it works, when the phone boots up it shows:
Samsung Galaxy S II
GT-I9100
under than it shows an yellow triangle with a explanation point inside it. The phone boots up and CMW is nowhere to be seen.....
Click to expand...
Click to collapse
Heres the cwm link that entropy said to use http://forum.xda-developers.com/showthread.php?t=1285823 You gotta calm down and do a little research lol relax. That exclamation thing is nothing dont worry about it. Its perfectly normal!
Gutterball said:
Heres the cwm link that entropy said to use http://forum.xda-developers.com/showthread.php?t=1285823 You gotta calm down and do a little research lol relax
Click to expand...
Click to collapse
Thats the one i did and when the phone is back up and running, there is no Rom Manager anywhere on my phone. -_-
Chubby_Skunk said:
Thats the one i did and when the phone is back up and running, there is no Rom Manager anywhere on my phone. -_-
Click to expand...
Click to collapse
It doesnt need rom manager. You boot into cwm by holding your power button and volume up and down when the phone boots up. Thats your cwm.
Gutterball said:
It doesnt need rom manager. You boot into cwm by holding your power button and volume up and down when the phone boots up. Thats your cwm.
Click to expand...
Click to collapse
tried that too and nothing happened :/
it just waits a second and then goes to the AT&T splash screen and goes to the lock screen....

Now rooted, installed cwm.. but it fails.

Okay so I used "Odin3 One-Click Downloader Stock I-777 UCKH7" rooted with success and when i go to into clockworkmod, it says E:failed to verify whole-file signature and E:signature verification failed.. any idea's?
I've only had the device for a week.
I just got my device today, and have the same error.
I used SGH-I777-ATTGalaxyS2RootStockZedomaxKernel.tar with odin
Can anyone chime in on this?
Stop using rom manager?
Pirateghost said:
Stop using rom manager?
Click to expand...
Click to collapse
Okay? That doesn't really help. I uninstalled it. I was on 2.3.6 but now I seem to be on 2.3.4 after using odin for root.
Are you holding power, vol up, vol down to get into CWM?
getbuzzin said:
Are you holding power, vol up, vol down to get into CWM?
Click to expand...
Click to collapse
I'll retry, I was on 2.3.6 it seemed to downgrade my device, used the odin in the thread that didn't say it wasn't working with 2.3.6
http://forum.xda-developers.com/showthread.php?t=1285894
for Windows
getbuzzin said:
Are you holding power, vol up, vol down to get into CWM?
Click to expand...
Click to collapse
I did that, It booted into android system recovery. applied multi-csc, installed multi csc, then said can't access system/csc/ATT/system/ then said sucessfully applied multi-csc
Ok got it working, thanks. By stop using rom manager I guess you mean, don't use the reboot into recovery feature
kLAcK107 said:
Ok got it working, thanks. By stop using rom manager I guess you mean, don't use the reboot into recovery feature
Click to expand...
Click to collapse
What did you do? How do I back up my stock rom after gaining root?
xamadeix said:
What did you do? How do I back up my stock rom after gaining root?
Click to expand...
Click to collapse
guys
this is all covered in the damn stickies.....please read
Pirateghost said:
guys
this is all covered in the damn stickies.....please read
Click to expand...
Click to collapse
Show me.. and I'm set. I'm just trying to be careful.
I started fresh again and didn't mess with rom manager, just boot directly into Clockwork.
how do i boot directly into clockwork without rom manager?
Like he said above, you hold down vol up, down and power. The recovery menu you were getting is the android recovery menu, not CWM.
Do your rooting over and try it again. You should see the CWM logo when going into recovery, it is noticeably different.
kLAcK107 said:
I started fresh again and didn't mess with rom manager, just boot directly into Clockwork.
Click to expand...
Click to collapse
how do i do this? and do i need to flash something?
xamadeix said:
how do i do this? and do i need to flash something?
Click to expand...
Click to collapse
once again......
READ THE STICKIES.....
you are asking us to hold your hand, this is not a help desk, you help yourself
Pirateghost said:
once again......
READ THE STICKIES.....
you are asking us to hold your hand, this is not a help desk, you help yourself
Click to expand...
Click to collapse
Aware, I prefer to have someone that's aware of the situation rather I do something wrong... I'm not familiar with the process...
1. I was on 2.3.6, Flashed with Odin to gain root.
2. It downgraded me to 2.3.4. With root.
3. Just asking what to do next so I can back up my stock rom and be able to flash away.
xamadeix said:
Aware, I prefer to have someone that's aware of the situation rather I do something wrong... I'm not familiar with the process...
1. I was on 2.3.6, Flashed with Odin to gain root.
2. It downgraded me to 2.3.4. With root.
3. Just asking what to do next so I can back up my stock rom and be able to flash away.
Click to expand...
Click to collapse
i refuse to partake in holding your hand....
Pirateghost said:
i refuse to partake in holding your hand....
Click to expand...
Click to collapse
lol. great support.

[Solved] Yay another soft brick/bootloop!

Yes I have searched, yes I have tried google and yes I am still stuck...
I *think* I have tried just about everything and I have read through about 10 "soft brick" or "stuck on samsung screen after rooting on stock ICS" (and most combinations of) but nothing is working. I'm sure it's probably an easy fix but I just can't seem to get anywhere. Here's what happened.....
I googled rooting galaxy not after ICS update and found this http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
It was all I could find about rooting after the ICS OTA update, so I did it. Everything seemed fine. I had CW but no superuser so I DL it from the market as well as my old Titanium pro from back when I rooted my HTC. I rebooted my phone to get it all settled in and decided to run Titanium and get this party started. I got an error message that busybox was not installed so.... I installed it but when I clicked the app on my phone it said it would not install because I didn't have root access.... This is where the confusion starts to set in.
So I restarted to see if I could get into CW but when I rebooted the soft brick started.... I was stuck at the "samsung" screen.
I IMMEDIATELY ran to XDA and began my search. I can still get to DL mode, Odin and CW so I know there is hope. I tried the files listed in the "All in one guide for noobs" and the "Galaxy Note Super Everything Thread (I717)".
There was a suggestion to use Kies but when I put in my serial # and model name i get the "galaxy note does not support initializing" message.
I'm not new to flashing/rooting, although things are a bit different, I have a basic understanding of the process but I ain't no Einstein either...
I also tried to flash the stock Telus ICS rom but I got an error message and my lil droid guy went belly up....
Any help would be greatly appreciated! I love my note and this is killing me...
I have to go to work so if I don't reply immediately its because I have no email access at work.... Especially without my Note....
The steps are correct in the link you gave.
Did Odin3 say success?
Did you get CWM installed?
Did you flash superuser?
Is there a superuser icon in your apps?
Ranger is on it....
I'm thinking we dont have CWM on the device....????
And no SU flash, from within the recovery that doesnt exist....g
He has cwm, he did not flash superuser, Looks like he assumed flashing cwm would automatically root him.
Since you can get into recovery... i would just go ahead and download a Rom zip, transfer to phone by mounting in cwm (mounts and storage if you didn't know) and flash that sumbitch
Oh yep...found that.......Thanks brother....g
That means do or redo steps 13 to 16 in the guide you posted.
agreed....g
im back...
Just got in, thanks for the replies.
Yes I have CWM and can access it. I have tried to flash the CM roms as well as the stock telus ICS rom but was denied at install. I got a "assert failed getprop (ro.build.device)" message and 2 other "ro." error messages when I install the cm nightly quincyatt rom.
rangercaptain said:
The steps are correct in the link you gave.
Did Odin3 say success? Yes
Did you get CWM installed? Yes
Did you flash superuser? Yes
Is there a superuser icon in your apps?
Click to expand...
Click to collapse
Cant see my apps but when I first flashed CWM and was able to see my screen there was a SU app on my home screen because I DLed it from the market.
You need to update your CWM. Get it here:
http://forum.xda-developers.com/showthread.php?p=28040353
Look right under the big green arrow in the first post of the thread.
Readreadread. Then thankbigjoethankbigjoe.
Of course, come back here if further assistance is needed or you solve the issue.
I thought I was on the latest. Someone else suggested that also, so I flashed the touch CWM Updated 04/14
rangercaptain said:
You need to update your CWM. Get it here:
http://forum.xda-developers.com/showthread.php?p=28040353
Look right under the big green arrow in the first post of the thread.
Readreadread. Then thankbigjoethankbigjoe.
Of course, come back here if further assistance is needed or you solve the issue.
Click to expand...
Click to collapse
Yup, thats the one I flashed, its working and I get a successful message when I flashed SU so I assume its there also. Any recommendations of a rom to try and flash? Still hanging at the samsung screen.....
I appreciate the help by the way, I know how frustrating it can be to try and help with tech situations from emails and messages (Hi Mom ).
Thanks has been pushed....
That assert error is in the script used by CWM to flash and it is saying 'wrong rom for your device'. So for sure you have the correct CWM and rom for your phone? Just checking because errors at this point make your phone useless.
rangercaptain said:
That assert error is in the script used by CWM to flash and it is saying 'wrong rom for your device'. So for sure you have the correct CWM and rom for your phone? Just checking because errors at this point make your phone useless.
Click to expand...
Click to collapse
I got my CWM from the link you posted but the rom I am iffy about. Any suggestions for a rom to try and flash? something stable?
EDIT: going to try and flash this rom and modem http://forum.xda-developers.com/showthread.php?t=1801689
Downloading now..... Sloooooowly. lol
Holy McCrappy dance!
Okay... so I flashed the stock ATT with odin. just at start screen now.... Don't think it is rooted so now.... How do I get back to telus and root right the first time?
Edit: so it appears the ATT rom was a GB ver so I am assuming that I was somehow reverted to GB instead of my stock ICS. Now to try and flash a stock Telus GB rom, update then try to root.... AGAIN! Thank gawd I don't have a $600 paperweight now!
Thanks everyone
I recommend this rom:
http://forum.xda-developers.com/showthread.php?t=1766933
Select the pure stock. There is no point in using the Telus rom.
Please read carefully. Good luck.
^^^ what ranger said. No point in repeating trust and go!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
rangercaptain said:
I recommend this rom:
http://forum.xda-developers.com/showthread.php?t=1766933
Select the pure stock. There is no point in using the Telus rom.
Please read carefully. Good luck.
Click to expand...
Click to collapse
I would like my ota ICS back but I guess no bother huh? I am back on the stock telus GB and for some reason it wont let me update to ICS anyway.... LOL
Might as well root it up and go go go!
Thanks again Ranger.
WOW! that pure stock is a big ole file! lol
Ok, take it easy for a few days. Just read up and, now that you've survived the worst scenerio, you might want to try a more custom rom or other modifications. Pretty soon you will be pulling someone else's a$$ out of the fire. Good luck.
I think I'm okay now. Was a skeerty one though. Lol

Error when trying to install custom rom

Hi everyone,
I`m tryign to install criskelo rom (http://forum.xda-developers.com/show....php?t=1714091) and I followed every step, but when trying to install the rom I get the error bellow:
Installing: /emmc/Criskelo_6.0.1_Stock_XXBLG9_oat.zip
Finding update package....
Opening update package....
E: Can't open /emmc/Criskelo_6.0.1+Stock_XXBLG9_ota.zip
(bad)
Installation aborted
Anyone knows what I did wrong?
Thanks.
Ryudo0 said:
Hi everyone,
I`m tryign to install criskelo rom (http://forum.xda-developers.com/show....php?t=1714091) and I followed every step, but when trying to install the rom I get the error bellow:
Installing: /emmc/Criskelo_6.0.1_Stock_XXBLG9_oat.zip
Finding update package....
Opening update package....
E: Can't open /emmc/Criskelo_6.0.1+Stock_XXBLG9_ota.zip
(bad)
Installation aborted
Anyone knows what I did wrong?
Thanks.
Click to expand...
Click to collapse
Check the download again..compare the md5...probably a bad download..
Sent from my GT-I9300 using xda app-developers app
zoot1 said:
Check the download again..compare the md5...probably a bad download..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I've already tried to download the rom about 4-5 times and still not working. =/
Ryudo0 said:
Hi everyone,
I`m tryign to install criskelo rom (http://forum.xda-developers.com/show....php?t=1714091) and I followed every step, but when trying to install the rom I get the error bellow:
Installing: /emmc/Criskelo_6.0.1_Stock_XXBLG9_oat.zip
Finding update package....
Opening update package....
E: Can't open /emmc/Criskelo_6.0.1+Stock_XXBLG9_ota.zip
(bad)
Installation aborted
Anyone knows what I did wrong?
Thanks.
Click to expand...
Click to collapse
Have you tried flashing any other custom-rom??
I hope ur rooted and this has also happened to me few times and always the culprit was bad download
Sent from my GT-I9300 using xda premium
zoot1 said:
Check the download again..compare the md5...probably a bad download..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
There is nothing else which can go wrong here...check the md5 of the downloaded file...which recovery are you using?
zoot1 said:
There is nothing else which can go wrong here...check the md5 of the downloaded file...which recovery are you using?
Click to expand...
Click to collapse
I was using CWM.
I got it to work.... Everytime I downloaded the file it was from the first link I tried the sencond one and it worked.
Thanks everyone.
Off topic question: My kies is not working anymore this normal?
Ryudo0 said:
I was using CWM.
I got it to work.... Everytime I downloaded the file it was from the first link I tried the sencond one and it worked.
Thanks everyone.
Off topic question: My kies is not working anymore this normal?
Click to expand...
Click to collapse
Kies won't work with custom Rom......in fact forget kies ever existed, it is widely recognized as an unreliable POS!
Put the Update ZIP onto your SDCARD and try the install and also check the size of the zip file
I had a similar issue, my download didn't throw an error in CWM, but when I flashed it and rebooted I was greeted with constant force closes (so much, so quickly that I couldn't finish pressing ok). Went back into CWM and did a complete wipe and flashed again. No boot. I only got my s3 on Saturday so I was scared sh**less. After a quick trip to the bathroom to calm down I figured out the zip was corrupt and restored to a CWM backup then restored a TiBp. Flashed WanamLite with the theme linked in the OP instead. I wasn't really emotionally stable enough to try flashing criskelo again...
On another note, I always check MD5's but I couldn't find any for v6.0.1 of criskelo's ROM? Can anyone point me in the right direction? I just wanna confirm that the zips were corrupt..
slaphead20 said:
Kies won't work with custom Rom......in fact forget kies ever existed, it is widely recognized as an unreliable POS!
Click to expand...
Click to collapse
Yea... but I made contacts backup using the Kies any ideias on how to retrieve them without having to install the original rom again?
Thanks
Ryudo0 said:
Yea... but I made contacts backup using the Kies any ideias on how to retrieve them without having to install the original rom again?
Thanks
Click to expand...
Click to collapse
Use Google for your contacts in future! Then they are safe in the cloud! Only way I know is flash back to stock
flash back to stock, restore contacts using kies to your phone then either backup to google a/c or memory card
i chose the memory card option as restoring from google always gives me duplicate contacts. its the only way i think
Guess I will have to go back to the old rom and flash again. Thanks everyone for the tips.
I`ve been lazy to look into cloud stuff for like a year now =P... really stressing year... guess I can`t run from it now lolz.

Custom ROM Installation Problem (Status 7)

Hopefully, you wonderfully knowledgeable people can help with this one!
I recently rooted my Galaxy S3 with no problems and decided to install a Custom ROM, (Omni version 4.4.2). Followed the instructions on a page that the forum won't allow me to post a link of and got to the point of installing the new ROM. It then came up with "Installation Aborted" and "Status 7".
I then found an explanation of how to sort out the problem of Status 7, at which point I attempted to put the edited version back onto my phone, only to realise that my computer and phone are no longer mounted and I cannot access the SD Card. I've tried disconnecting and re-connecting with no joy, because I'm stuck in ClockWorkMod it won't show up on my PC.
Now here's the moronic part... I completely missed the big bold lettering of "Before you install a custom ROM, PLEASE MAKE A BACKUP ROM!!!", so I cannot restore to another point.
Any suggestions and feel free to assume I'm a complete idiot when describing any fixes.
Powello1 said:
Hopefully, you wonderfully knowledgeable people can help with this one!
I recently rooted my Galaxy S3 with no problems and decided to install a Custom ROM, (Omni version 4.4.2). Followed the instructions on a page that the forum won't allow me to post a link of and got to the point of installing the new ROM. It then came up with "Installation Aborted" and "Status 7".
I then found an explanation of how to sort out the problem of Status 7, at which point I attempted to put the edited version back onto my phone, only to realise that my computer and phone are no longer mounted and I cannot access the SD Card. I've tried disconnecting and re-connecting with no joy, because I'm stuck in ClockWorkMod it won't show up on my PC.
Now here's the moronic part... I completely missed the big bold lettering of "Before you install a custom ROM, PLEASE MAKE A BACKUP ROM!!!", so I cannot restore to another point.
Any suggestions and feel free to assume I'm a complete idiot when describing any fixes.
Click to expand...
Click to collapse
Download another stock rom from sammobile switch phone off and flash it with odin then factory reset Done..
You can then start again... By the way status 7 is usually caused by wrong recovery or old recovery.
Use Odin install latest original firmware then root then install latest CWM to get rid of status 7 error
Sent from my GT-I9300 using Tapatalk
Do we have a repository for Sammy UK ROMs that isn't Sammobile? It's downloading painfully slowly.
http://live.samsung-updates.com/index.php?device=GT-I9300
Sent from my GT-I9300 using Tapatalk
boomboomer said:
http://live.samsung-updates.com/index.php?device=GT-I9300
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
You sir, are a gent. Thank you kindly. :good:
Thought we'd got the problem sorted but it seems to not like ArchiDroid, still waiting on the stock ROM to download as there are server problems.
Out of interest, would a KitKat recovery work on a 4.3 ROM?
Powello1 said:
Thought we'd got the problem sorted but it seems to not like ArchiDroid, still waiting on the stock ROM to download as there are server problems.
Out of interest, would a KitKat recovery work on a 4.3 ROM?
Click to expand...
Click to collapse
I had that, it was an older version of CWM causing the status 7, would TWRP help ?
kennyboy1978 said:
I had that, it was an older version of CWM causing the status 7, would TWRP help ?
Click to expand...
Click to collapse
We're all sorted, it was a 4.0.4 CWM installed with a 4.3 ROM. Upgraded CWM and we're good to go! I don't think he's brave enough to attempt a KitKat install after 6 hours of being stuck in CWM, haha.
Thanks again to all that posted. :victory:
As Kalavere says, all sorted! Looks like the key to Custom ROMS is make sure you have the latest CWM!
Thank you all for your help!
yeah this has occured with me when i rooted my s3
i've tried to install a rom but then and totally out of the blue it told me that installation aborted so i became very disappointed and didn't know what to do cuz i've already followed the instructions written in the site
i just tried to re-root my s3 with a different root file Which I've got from xda too and everything ran ok again so just re-root with another root file
Sent from my SM-G900F using XDA Premium 4 mobile app

Categories

Resources