[Q] OpenSEMC to Cyanogen help - Sony Xperia S, Acro S, Ion

I somehow messed up by forgetting stuff from some tutorials. I was on Official Sony rom and wanted to goto Cyanogen and I ended up with being on OpenSEMC on my phone.
Since there are so many guides in guides and there are no real explanations what every guide/step does it's unclear what i can do now.
My Bootloader is unlocked, did that via Sony. I have no backups whatsoever.
I also have NO GAPPS on the phone itself, this is the part I forgot to actually put on phone/sdcard.
Wipe cache partition/dalvik's cache are formatted also if I recall.
So my phone is kind of useless atm

eXcLuSiVeFXP said:
I somehow messed up by forgetting stuff from some tutorials. I was on Official Sony rom and wanted to goto Cyanogen and I ended up with being on OpenSEMC on my phone.
Since there are so many guides in guides and there are no real explanations what every guide/step does it's unclear what i can do now.
My Bootloader is unlocked, did that via Sony. I have no backups whatsoever.
I also have NO GAPPS on the phone itself, this is the part I forgot to actually put on phone/sdcard.
Wipe cache partition/dalvik's cache are formatted also if I recall.
So my phone is kind of useless atm
Click to expand...
Click to collapse
What exactly did you flash, wich rom?

Thomson2412 said:
What exactly did you flash, wich rom?
Click to expand...
Click to collapse
Tyvm for your response
If iam correct, OpenSEMC-kk-beta3.zip
When I boot phone with volume up: TWRP v2.6.3.0
I forgot to put on the gapps.apk/zip on the phone so i can't install that one, and I already wiped Dalvik and another!

Nevermind, after having my phone for 2 years it now finally runs Cyanogen
I am missing stuff from gapps tho

eXcLuSiVeFXP said:
Nevermind, after having my phone for 2 years it now finally runs Cyanogen
I am missing stuff from gapps tho
Click to expand...
Click to collapse
You can still flash gapps, atleast I think so, not sure

Related

Stuck in boot loop...

So I tried installing a status bar icon replacement on Cyanogenmod and ended up getting stuck on boot loop somehow...
I went into recovery and wiped data, wiped my cache and dalvik cache and it's still stuck on boot loop...
help?
reflash rom
the rom isn't on the root of my device anymore and I can't exactly set it there without it turning on.
Causes a slight issue I imagine?
Aerolith514 said:
the rom isn't on the root of my device anymore and I can't exactly set it there without it turning on.
Causes a slight issue I imagine?
Click to expand...
Click to collapse
it doesnt have to be on the root of your device, as long as its in your storage. if its in the storage, find that location amd flash it. now what do you mean you cant exactly set it there without it turning on? you lost me there.
The rom isn't on my phone whatsoever.
I meant I need to be able to have the phone fully turned on in order to move the zip over to it.
Aerolith514 said:
The rom isn't on my phone whatsoever.
I meant I need to be able to have the phone fully turned on in order to move the zip over to it.
Click to expand...
Click to collapse
what recovery are you using? twrp has an adb sideload option, cwm might have something similar.
Just push another nightly zip over with adb, while in recovery. Simple! Don't understand what the fuss is all about.
Sent from my i9250
Using cwm.
adb? Sorry I've never bricked my device before, I have no idea what that is XD
Aerolith514 said:
Using cwm.
adb? Sorry I've never bricked my device before, I have no idea what that is XD
Click to expand...
Click to collapse
if u made a backup for ur stock rom, then restore it.
if not, the easiest way is to reflash factory image using fastboot mode. or see my thread in signature
Pardon my noobishness, but I really would rather not unroot my phone and set it back to stock 4.1.1 unless it's my only option.
Either way, I created a backup last night but it doesn't work. When I tell it to install it says "no file found".
At this point, I'm willing to let somebody take over via viewfinder if it'll help >_>
Flash new custom rom
And every modification SYSTEMUI.apk make sure permision each others
Aerolith514 said:
Pardon my noobishness, but I really would rather not unroot my phone and set it back to stock 4.1.1 unless it's my only option.
Either way, I created a backup last night but it doesn't work. When I tell it to install it says "no file found".
At this point, I'm willing to let somebody take over via viewfinder if it'll help >_>
Click to expand...
Click to collapse
so flash google image 4.2.1 using fastboot http://forum.xda-developers.com/showthread.php?t=1626895.
If u flash 4.1.1 i think u will receive update before rooting.
any way what cwm u are using??
Sigh...crisis averted.
I dug deep into my files (which are a friggen mess) and found a the December 21st nightly laying around somewhere odd. Everything's back to working order -- Just gotta set everything up again >_>
Although, it seems like i have nothing on my screen...
Nothing whatsoever
Aerolith514 said:
Using cwm.
adb? Sorry I've never bricked my device before, I have no idea what that is XD
Click to expand...
Click to collapse
that's the attitude that... nevermind.
http://forum.xda-developers.com/showthread.php?t=1812959
this is the thread you should have read BEFORE "bricking" your device. Which you didn't by the way. You don't want to know what a REAL brick is. Don't use the word lightly.
Sigh, one last question I guess -- even though I've asked a ton.
Now that I've flashed CM and my gapps, everything on the phone works except it shows that I have no installed apps...my messaging app, app tab..phone... nothing is there...
Aerolith514 said:
Sigh, one last question I guess -- even though I've asked a ton.
Now that I've flashed CM and my gapps, everything on the phone works except it shows that I have no installed apps...my messaging app, app tab..phone... nothing is there...
Click to expand...
Click to collapse
did you flash the right gapps?
gapps 20121212
Unless there's a newer one now?
Aerolith514 said:
gapps 20121212
Unless there's a newer one now?
Click to expand...
Click to collapse
in latest cm 10.1 there is a lot of bugs no icon for drawer, no long press on desktop, flash the previous one
Aerolith514 said:
gapps 20121212
Unless there's a newer one now?
Click to expand...
Click to collapse
that version is working fine here under custom aosp, so it must be cm problem like previous poster said.

new to the brick club?

Okay, after years of modding dozens of android devices and even editing a few kernels I find I may have bricked a tf300t doing something stupid . Installed jb cwm, no issues, clockwork mod 10.1, gapps, rebooted, nice CM screen, then 'oh crap, I didn;t unencrypt data' as it asks me for unlock code. No worries, type it in, accepted, and CM goes into endless loop.
Go back to cwm, try to wipe data, can't mount /DATA. Tried an ADB shell format, format isnt in this version. Went to restore backup, crap, whatever I did manage to wipe included backup.
Reflashed CM, reboot, no I don't get past ASUS screen.
Thoughts? Target practice time?
Thibble..
Although the TF300T forums are very, VERY friendly, this is still the Dev section.
You may get an answer quicker through Q&A section
(and sorry, I do not know how to help you out)
(Fastboot Flash) the latest TWRP version, do full wipes (except storage lol) and then try to clean install CM, CWM was the cause of many problems before...
btw contact a Mod to move this to Q&A Section
thibbledorf said:
Okay, after years of modding dozens of android devices and even editing a few kernels I find I may have bricked a tf300t doing something stupid . Installed jb cwm, no issues, clockwork mod 10.1, gapps, rebooted, nice CM screen, then 'oh crap, I didn;t unencrypt data' as it asks me for unlock code. No worries, type it in, accepted, and CM goes into endless loop.
Go back to cwm, try to wipe data, can't mount /DATA. Tried an ADB shell format, format isnt in this version. Went to restore backup, crap, whatever I did manage to wipe included backup.
Reflashed CM, reboot, no I don't get past ASUS screen.
Thoughts? Target practice time?
Thibble..
Click to expand...
Click to collapse
Hi !
Please, can you take a look here ? ...maybe it help you :good:
-angel* said:
(Fastboot Flash) the latest TWRP version, do full wipes (except storage lol) and then try to clean install CM, CWM was the cause of many problems before...
btw contact a Mod to move this to Q&A Section
Click to expand...
Click to collapse
Thank you! Yes after I posted I saw my mistake and then ...what...edit /delete won't let me delete....I went looking for the idiot stamp to hit my forehead with.
I'd probably try fastboot, flash/install official asus firmware

[Q] Need help with flashing roms Galaxy s3

I tried flashing two different roms (synergy and chemistry) on my sprint galaxy s3. It turns on but then wont go past the "galaxy s III" logo. I just restored my backup and all is well but I really want to get multi window on this thing so I could really use some help as to what is not letting me boot up all the way. The last thing i messed around with rooting was my DroidX and with that it really mattered a lot which version of android you were flashing from. I have 4.1.2 the most recent update. Is that why these roms are not working? Any help would be much appreciated I am very excited to get a killer rom on this bad boy.
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
CNexus said:
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
Click to expand...
Click to collapse
I boot into recovery after i put the rom on to my sd card. Then wipe the factory data, cache partition, and delvik cache. I do those steps twice, then install the rom. The install seems to go fine, it always says successful at the end, it just wont go past that screen. Does it mater which version of clockworkmod I use?
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
CNexus said:
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
Click to expand...
Click to collapse
Thank you so much for your quick response. As far as I can tell, I am wiping everything I should be. I use clockwork recovery mod version: and the choices it gives you are: Wipe data/factory reset, wipe cache partition, and wipe dalvik cache. From all the instructional threads I've read, those are the only things you need to clear out before the install. My clockwork version is v5.5.0.4 which i think might be really old. Could that be my issue? Does it matter how I rooted it? I just tryed to put jellybomb v14 on it and it didn't even give me the galaxy s III logo. Luckily it booted back into recovery though. I really don't want to hard brick this thing.
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
A-Shin said:
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
Click to expand...
Click to collapse
clockworkmod v5.5.0.4
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
Make the switch to TWRP v2.3.1.0 (newer ones I've heard have problems) but you will be thanking me later. It's way easier and much better than CWM... just an FYI for ya!
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
I suggest trying a flash with TWRP. If you are unsure how to install TWRP, just download the Goomanager app, then choose install Open Recovery Script. But, before you install or change anything, look around a bit on how to install it. Make sure you follow directions step by step. After you have installed TWRP, try flashing again. Good luck!
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
cchrisrollins said:
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
Click to expand...
Click to collapse
Samsung bootloaders come unlocked by default, so yes
Easiest way to switch is to download Goo manager from the Play Store and have it install TWRP for you
Generally speaking, CWM is great on most devices, but for the S3 it's TWRP that's the best and easiest to use
And when flashing new roms, make sure to always format system, it prevents corrupted files from showing up because you would be installing the new system right on top of the old one if you don't
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you made a nandroid backup in TWRP (I'd recommend to put it on the external memory, but that's just me), you should be good to try any ROM you want (only Sprint ROMS). Just follow CNexus's post (linked for posterity). Wipe system as well as factory reset, cache, and dalvik, prior to installing the ROM.
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you've already rooted, re-rooting isn't going to fix anything, so no need to go there.
As previously explained and detailed, do a full system wipe, and you'll be good to go.
Thank you guys so much for your very quick responses, thank you for bearing with my noobishness too haha. I am going to tryn reflash jellybomb tonight, I'll post on this thread how it goes (hopefully good).
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
cchrisrollins said:
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
Click to expand...
Click to collapse
It took me like 4-5 months to personally figure out that the problem was the kernel. You need to flash a kernel right after you flash the ROM. Either the stock kernels or better kernels like Anthrax will do. I know that for jellybomb, there's a kernel included in the Rom but for some reason,it got stuck on the gs 3 logo if I didn't flash another kernel.
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No prob, just hit dat thanks button do you know where to get the kernels?
Zin0 said:
No prob, just hit dat thanks button do you know where to get the kernels?
Click to expand...
Click to collapse
I tryed the KT47 AOSP Jellbean kernel after flashing jelly bomb and it did the same thing it did before, black screen after flashing the samsung logo
Now I did go into fix permissions and it did say failed, is that abnormal?
This is my exact procces:
1. boot into TWRP
2. factory reset
3. system wipe
4. cache wipe
5. Dalvik wipe
6. Install from external SD: jellybomb v14
7. Wipe cache/Dalvik
8. Install Kt47 kernel
9. Wipe cache/Dalvik
Anything wrong there?

[Q] Installing ROM mess up, help!

I've searched the forums and couldn't find anything on this, so i apologize if i over looked it somewhere and its actually there.
Basically I downloaded the new CM 10.2 and all of the Gapps. Got super excited and went ahead and booted it into TWRP.
Did my full wipe and everything else needed, but when i go to the download folder there are literally NONE of my files that i just downloaded for this.
No ROM, no Gapps, nothing.
I cant boot it cause of the full wipe, and i apparently lost my backup somewhere along the way? (yeah I have no idea how that happened, i back up everything)
How do i find these files or access them so i can flash this already?
Dustin7892 said:
I've searched the forums and couldn't find anything on this, so i apologize if i over looked it somewhere and its actually there.
Basically I downloaded the new CM 10.2 and all of the Gapps. Got super excited and went ahead and booted it into TWRP.
Did my full wipe and everything else needed, but when i go to the download folder there are literally NONE of my files that i just downloaded for this.
No ROM, no Gapps, nothing.
I cant boot it cause of the full wipe, and i apparently lost my backup somewhere along the way? (yeah I have no idea how that happened, i back up everything)
How do i find these files or access them so i can flash this already?
Click to expand...
Click to collapse
First time with CM Rom's? Follow this to ADB sideload your ROM. It's the first page "I don't have a zip." http://forum.xda-developers.com/showthread.php?t=2082084
engine95 said:
First time with CM Rom's? Follow this to ADB sideload your ROM. It's the first page "I don't have a zip." http://forum.xda-developers.com/showthread.php?t=2082084
Click to expand...
Click to collapse
normally wipe it all except internal storage....never wipe internal storage (well ive never)....follow engine advice..the man wont steer you wrong..
spleef said:
normally wipe it all except internal storage....never wipe internal storage (well ive never)....follow engine advice..the man wont steer you wrong..
Click to expand...
Click to collapse
+1 @engine95 is a wealth of knowledge
Sent from my LG-LS970 using xda app-developers app

touchscreen not working in cm12.1 official/unofficial

hi xda.
since i unlocked my bootloader i wanted to install cyanogen mod for sure.
did all step by step levels and it booted but no touchscreen, also tired unofficial and no hopes...
just posted this thread to know is there any solutions to make it work or not?
thanks
bigsmoke9250 said:
hi xda.
since i unlocked my bootloader i wanted to install cyanogen mod for sure.
did all step by step levels and it booted but no touchscreen, also tired unofficial and no hopes...
just posted this thread to know is there any solutions to make it work or not?
thanks
Click to expand...
Click to collapse
and i dont have this problem on stock roms kk,lp 368,and latest one
anyone???
I've never had it happen, but I have heard of it. It must be either a build issue or a bad flash. Try again with a different build, and make a full wipe, (system, caches,and data). Or try the same build with a full wipe. I bet it will work.
levone1 said:
I've never had it happen, but I have heard of it. It must be either a build issue or a bad flash. Try again with a different build, and make a full wipe, (system, caches,and data). Or try the same build with a full wipe. I bet it will work.
Click to expand...
Click to collapse
thanks for answering man,i did flashed again with wipes but still, meh ill return ti stock again

Categories

Resources