Related
Ok first off I have to say that this site is great I have found alot of helpfull and some confusing topics here lol. the other day I downloaded the cyanogen mod 7 and everything is working perfectly on my htc evo sprint
my only problem I noticed is that I dont know how to revert back to The HTC Sense ui. My other question is that I noticed alot of different roms on here and some I have tried installing but some wont work for me and some freeze when i attempt to reboot. Can anyone help me out please!!!
To revert back to Sense from Cyanogen, you'll have to reflash the ROM that came stock on your device. You should be able to find this in the forum for your device (EVO).
There are many different ROMs available here, some will work for you and some you may experience difficulty with. Most Devs usually post step-by-step instructions for installing their ROMs in the Opening Post (OP) of the thread. If you follow these you'll usually be fine, and you can always flash back to stock and start again if you get into trouble.
Good luck, and welcome to XDA
Did you do a nandroid backup first? If not, you should always do one before flashing. If you did, just restore through your recovery & you'll be back where you were before.
If CM7 is functional but you just don't like it, I would go ahead and do a nandroid backup anyway, so if anything messes up you'll at least have something working you can restore.
If you want something like stock, I would suggest the Sprint Lover's Rom. Myn's Warm 2.2 would also be good, or you could try out Warm Z which is the new version of Sense. I'm assuming you like Sense as a UI & as a launcher?
I've heard great things about Mikfroyo as well. If you're new to rooting/flashing, I would suggest using a stable Rom instead of an experimental one - at least until you get the hang of it.
If you're having trouble flashing ROMs, try switching to Amon Ra recovery (I assume you're using clockwork) and try flashing again. You can do this through ROM Manager (it came with CM7). Just choose "flash alternate recovery".
Before rooting, modifying, and flashing ROMs, you're supposed to have a clear understanding of it all. I suggest reading the stickies in the Evo forums & any guides you can find. Read everything. Seriously.
I have an Evo as well, so if you need anything, I'm here. Just ask. If you need some guidance & handholding, send me a pm & I'll walk you through everything. Just be sure to educate yourself. There's no such thing as knowing too much when it comes to modifying your phone.
EDIT: If the phone gets stuck on the splash screen after flashing a Rom, it's most likely because you didn't wipe properly. Be sure to wipe data/factory reset, wipe cache & dalvik cache.
Thank u kindly
Both of you were helpful I will take my time and read and explore the forums in hopes of understanding clearly yes i am running clockwork is this ananran better? if so how can i use it ?
I'm new to the whole Android scene so let me know if I left out information and what not.
I'm currently running RCMix HD v5.9.3 and decided to flash my radio. I was using Radio_12.39.60.19_26.06.04.06_M - Cingular US 1.80.502.3 and every time I made a call, my phone beeps and then hangs up. I'll eventually make a call but its very annoying. I went ahead and flashed the suggested rom from this topic (Radio_12.28e.60.140f_26.04.02.17_M2_SF - HTC WWE 1.72.405.3 R2) and I thought that fixed the problem but it is starting to happen again and when I look down I will have almost full signal if not full.
Did I do something wrong while flashing it? Should I go back to stock?
All help is appreciated! Thanks
Did you do a backup (nandroid or otherwise) before loading the current ROM?
If so, you could start from there, restoring your backup and seeing if everything is fine. If you used either of the hack kits here, then the ROM you revert back to should be rooted and close to stock, meaning you have all of your basic functionality and can verify that the hardware is working.
Think back to when you installed your current ROM of choice - did you clear the cache and data when you did it? If not, then that could be a big part of your issue right there. Try reloading the ROM again after wiping cache and data.
You could also try a ROM closer to the stock ROM like ClearDroid - very nice one that I'm using at the moment, and the guys supporting it are active here and helpful with issues (though I myself haven't had any).
This would be my personal method of resolution - to pinpoint the issues and verify the source, be it hardware or software. Feel free to get a second (or more) opinion on this - I'm not "old hat" on the Android platform yet, but I have been tinkering with this and it doesn't seem like a phone that is terribly easy to brick.
Good luck with it, and post back with your resolution - maybe you can help someone else who's seeing the same issue.
The cell coverage in your area could be over loaded. Can you make calls at night or off peak without issues?
nightborne said:
Did you do a backup (nandroid or otherwise) before loading the current ROM?
If so, you could start from there, restoring your backup and seeing if everything is fine. If you used either of the hack kits here, then the ROM you revert back to should be rooted and close to stock, meaning you have all of your basic functionality and can verify that the hardware is working.
Think back to when you installed your current ROM of choice - did you clear the cache and data when you did it? If not, then that could be a big part of your issue right there. Try reloading the ROM again after wiping cache and data.
You could also try a ROM closer to the stock ROM like ClearDroid - very nice one that I'm using at the moment, and the guys supporting it are active here and helpful with issues (though I myself haven't had any).
This would be my personal method of resolution - to pinpoint the issues and verify the source, be it hardware or software. Feel free to get a second (or more) opinion on this - I'm not "old hat" on the Android platform yet, but I have been tinkering with this and it doesn't seem like a phone that is terribly easy to brick.
Good luck with it, and post back with your resolution - maybe you can help someone else who's seeing the same issue.
Click to expand...
Click to collapse
Thanks for the info. I'll do a backup and try going back to the rooted ROM I had with the hack kit later tonight. Thanks again for the ideas. I'm hoping something works *crosses fingers*
I was having the same issue as you when running cm7 or any gingerbread Tom using the stock radio. I ended up flashing a gingerbread radio and that solved the problem but now my upload speeds suck again :-(. Give it a shot
Sent from my rooted Inspire 4G using XDA App
I went ahead and wiped everything and basically went through the hack kit again to get root stock and everything seems to be working normally. I love the RCMix rom and will give start fresh from there and see if the same thing happens.
@nino313
I'll look at the gingerbread radio if things start messing up again.
Hi guys, please tell me what the heck I am doing wrong with ICS ROMs because I just feel powerless.
Tried some time ago OnceICS ROM (on 3.12 firmware), then switched to Virtuous Inquisition, then Virtuous Quattro (3.24 firmware) and now I'm on newest OnceICS on 3.24 unlocked firmware.
Every ROM change was dictated by the fact that my ROM kept turning off very randomly - on data transfer (I guess), after sending/receiving SMS, before/after phonecall - no rule, once it worked, another time I had like 10 turn offs per hour. Can't even do a logcat because it mostly happens when I'm out of home, where the signal can or is lower than at home (where I have full and barely no turn offs).
Every ROM change I hope this one gonna work but the problem still remains.
Sitting on supercid, did wipes, superwipes, fix permissions, battery wipe, no OC kernels, changed recovery to 4ext touch..
I flashed OnceICS yesterday I thought it is finally fine. But today it started rebooting like every before. probably today I will flash just once a sense rom like insertcoin, but I have no hope.
What is wrong with my phone? :\
insert-coin is not a de-sensed ROM
Did you by any chance restore data from a backup after flashing the ROM because this can often cause this sort of bugs
Whoops I meant "sense rom like insertcoin" because I tried roms with sense stripped out.
I do not restore data, I do titanium backup, sometimes use it to restore some apps but none of system stuff (contacts are synced by google, sms are restored by Go SMS Pro, everything else I configure on every reinstall). Like right now, I have plain OnceICS with only few apps installed from market but I had turn offs before I installed them too so I don't think they are the problem here :\
Maybe you should install a factory ROM first, to look if it solves your problem..?
tbeelen said:
Maybe you should install a factory ROM first, to look if it solves your problem..?
Click to expand...
Click to collapse
Agreed, try a Gingerbread ROM then you can figure out whether it's an ICS problem alone or possibly hardware related.
Yeah I will probably install gingerbread :/ But, damn, ICS is awesome, I like it very much, especially the way it behaves and looks. It's sad I need to go back to gingerbread
Don't give up, if Gingerbread runs well, just try again (maybe another) ICS ROM.
Cliff Edge said:
Yeah I will probably install gingerbread :/ But, damn, ICS is awesome, I like it very much, especially the way it behaves and looks. It's sad I need to go back to gingerbread
Click to expand...
Click to collapse
It's a bummer but if it's a hardware fault best to find it and get it sorted IMO.
It was fine before I switched to ICS. But ok, tomorrow morining, gingerbread strike back. What's the best 2.3 ROM right now? Because there is quite a mess in "android development" forums because of ICS.
Cliff Edge said:
Hi guys, please tell me what the heck I am doing wrong with ICS ROMs because I just feel powerless.
Tried some time ago OnceICS ROM (on 3.12 firmware), then switched to Virtuous Inquisition, then Virtuous Quattro (3.24 firmware) and now I'm on newest OnceICS on 3.24 unlocked firmware.
Every ROM change was dictated by the fact that my ROM kept turning off very randomly - on data transfer (I guess), after sending/receiving SMS, before/after phonecall - no rule, once it worked, another time I had like 10 turn offs per hour. Can't even do a logcat because it mostly happens when I'm out of home, where the signal can or is lower than at home (where I have full and barely no turn offs).
Every ROM change I hope this one gonna work but the problem still remains.
Sitting on supercid, did wipes, superwipes, fix permissions, battery wipe, no OC kernels, changed recovery to 4ext touch..
I flashed OnceICS yesterday I thought it is finally fine. But today it started rebooting like every before. probably today I will flash just once a sense rom like insertcoin, but I have no hope.
What is wrong with my phone? :\
Click to expand...
Click to collapse
MR. Edge, first let me say I feel your pain I myself went through exactly what you are going through. I thought I was going to have to get a new phone. But then I found this Post:
http://media.xda-developers.com/images/icons/icon2.gif
I know you said you did all these things but it wont hurt at this point to double check yourself and make sure everything is done correctly. I have had my sensation since June and have been rooted since july so I thought I knew everything there was to know about this phone. turns out I didnt lol and I still dont know what I missed but after I follwed this guide step by step I was able to load ARHD 6.1 without any issues. I have been auto off free for 3 days and counting.
and if that dosent work you can still go back to GB and ARHD has a nice rom for that as well. Good Luck
---------- Post added at 11:51 PM ---------- Previous post was at 11:49 PM ----------
Sorry new to posting here is the thread
http://forum.xda-developers.com/showthread.php?t=1472298
I'm on 3.12 F/W and happily run Virtuous Inquisition (or Quattro) and CM7 on the phone.
All the ICS based ROMs are a bit un-stable as they're based on un-released binaries from HTC. As you might tell from the ROMs I listed I'm more into AOSP based ones than Sense ones.
The battery life I have now is better than ever, TBH not certain if that's ICS, Radio or F/W.
gol_n_dal said:
I'm on 3.12 F/W and happily run Virtuous Inquisition (or Quattro) and CM7 on the phone.
All the ICS based ROMs are a bit un-stable as they're based on un-released binaries from HTC. As you might tell from the ROMs I listed I'm more into AOSP based ones than Sense ones.
The battery life I have now is better than ever, TBH not certain if that's ICS, Radio or F/W.
Click to expand...
Click to collapse
For AOSP ROM , I suggest Virtuous Inquisition till CM official released for sensation...
Thanks for answers, I gave up for now, switched to 1.17 fw and cm7. I miss ICS
So far it works fine but not as smooth as ICS. But the most I miss rotation animation
Jesus, what is going on :\ I'm on CM7 right now and it can turn off as well :\ Tomorrow I will install stock rom... Before I started playing with ICS everything was fine, no turn offs :\
If I were in your shoes I would reflash the RUU for your device and rule out a hardware failure. Not to mention if anything is left over from all of your flashes it can lead to problems. Just start over, don't ask for help and then be stubborn about the suggested solutions.
OK I will do so
I was about to post a thread but google pointed me here. I have the EXACT same problem as you do Cliff. I highly doubt it is caused by hardware, and as Tez recommended I followed that guide verbatim. Still having problems. It's so frustrating because I LOVE ICS.
Right now I'm on stock ROM, dedicated to my phone (rubbish Orange PL branding etc.), rooted it just to restore some games.
and it still can turn off from time to time :\ I've had no such issue before trying ICS. Dunno what else I can do.
For me, it's starting to seem more and more like the battery stats are way off. But no matter how many times I wipe them and try to re-calibrate, it still gets way off within a day or two.
Cliff, did your percentages jump around each time you turned your phone back on?
I have these problems too !! I'm going to s off and send to HTC
Sent from my HTC Sensation 4G with Beats Audio using xda premium
I just installed UCLD2 Smooth ICE 5.0 followed his instructions and I like the Rom, but I have an issue. My home button and search button do not work at all. I've gone into the settings to see if there is anything to change what the buttons do, but I've found nothing.
Does anyone know what could be causing this? Or what I can do to fix it.
I had the same issue with flashing sky is. I did a nandroid recovery, then reflashed the whole thing and allowed the system to settle longer than the suggested 5 minutes. It works great now. Buttons are fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Well as it turns out that was only one of a myriad of problems, I may or may not have permanantly bricked my phone. I let the system settle, but now the screen isn't very responsive when I try to do anything on it. I also tried returning to stock, and have had the same problems.
I don't have any idea what happened, but it seems to be like a kernel problem.
CrazyLineman777 said:
Well as it turns out that was only one of a myriad of problems, I may or may not have permanantly bricked my phone. I let the system settle, but now the screen isn't very responsive when I try to do anything on it. I also tried returning to stock, and have had the same problems.
I don't have any idea what happened, but it seems to be like a kernel problem.
Click to expand...
Click to collapse
If it turns on then its far from bricked. What was your method of returning to stock?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
There's been way too much of this nonsense recently. You don't even know what a brick is. All the new guys need to stop flashing everything they can get their hands on. Stop and read before you do this stuff to your phone. I read for almost a whole month, everything I could find before doing anything. Before I even flashed anything, I had everything needed to fix and return to stock, and made sure I completely understood what I was doing. Read and understand before you break stuff so you can fix it!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I...I....I give up Congrats noobs not just op you have killed my faith in humanity you all have won and destroyed my spirits
Sent from my SGH-T989 using Tapatalk 2
When most of us first installed the leak the fix was to install it again with the 1 click or factory reset.... Are you coming from stock gb or stock ics leak?
Edit: nrm and dx you guys crack me up
CM9 Skyrocket
I didn't flash whatever I could get my hands on thank you. I flashed NexusMod 4.3 Nexus UI first about a week and a half ago. Then I wanted to try and get something a little more like stock, but still ICS so after READING ALL THE INFORMATION on the post for ICS Smoothie v2 I flashed it after wiping data, cache, and dalvik and following the instructions regarding an ICS radio which I had not followed previously with Nexus Mod when I flashed it. Then the problems started.
There is no lockscreen even when the phone decides to work. When I start up the phone. Process.google.acore force closes as does process.google.gapps
Also when I unlock the phone the screen will respond to 1 maybe 2 swipes to find a homescreen then it'll hang.
I used ODIN to return to stock following the instructions on the Stickied post about doing so in the Development section. Also I'm sorry if some of what I said comes off rude I've just been trying to fix this for about 4 days with no luck and I really need some help.
Also I would've responded sooner, but it's finals week at my college so I've only got so much time.
Also I apologize for calling it a brick even though it was not. I do know what a brick is. It's when your device is unresponsive and will not turn on or do anything. It'a a paperweight or a brick.
I was freaking out my bad. I am sort of seasoned I was rooting my HTC Inspire when I got it almost a year ago, and I put ICS on it when the first leaks started coming out. I'm sorry I'm new to this phone. I will be getting better trust me. I just need some time to get used to the different quirks involved in this phone compared to my last one.
CrazyLineman777 said:
Also I apologize for calling it a brick even though it was not. I do know what a brick is. It's when your device is unresponsive and will not turn on or do anything. It'a a paperweight or a brick.
I was freaking out my bad. I am sort of seasoned I was rooting my HTC Inspire when I got it almost a year ago, and I put ICS on it when the first leaks started coming out. I'm sorry I'm new to this phone. I will be getting better trust me. I just need some time to get used to the different quirks involved in this phone compared to my last one.
Click to expand...
Click to collapse
My suggestion still stands use the ics leak 1 click then root see how you like stock ics twiz if you want a more custom rom then goto cwm and wipe cache , factory reset, then in mounts wipe sys, wipe cache and wipe data do all of these 3 times before installing rom and kernel always let.it sit a few minutes to settle....
CM9 Skyrocket
Ok I'm sorry for causing all of these issues I think I found a solution. In the General section and since I can't post links it is entitled:
[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989
Sorry I didn't look in General before posting this in Q&A the General section in the HTC Inspire forum wasn't usually gonna have fixes in it maybe root methods, but not fixes for stuff like this.
CrazyLineman777 said:
Ok I'm sorry for causing all of these issues I think I found a solution. In the General section and since I can't post links it is entitled:
[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989
Sorry I didn't look in General before posting this in Q&A the General section in the HTC Inspire forum wasn't usually gonna have fixes in it maybe root methods, but not fixes for stuff like this.
Click to expand...
Click to collapse
What radio did you flash?
I did realize I had done it wrong I flashed this: ATT-GALAXY-NOTE UCLC5 radio
but it was the one located in the post for Embryo 2.2 and I didn't flash the embryo rom, so the radio file which Mohan made specifically for his rom didn't go over well with the rom I flashed.
I did get back to stock eventually. It just took a few tries and the efs fix. I'm now putting CWM touch back on my phone and flashing a Gingerbread Rom because ICS on our phone is still a little too iffy for my likeing. I'll probably just wait till Samsung releases source for the kernel and cook my own rom.
CrazyLineman777 said:
I did realize I had done it wrong I flashed this: ATT-GALAXY-NOTE UCLC5 radio
but it was the one located in the post for Embryo 2.2 and I didn't flash the embryo rom, so the radio file which Mohan made specifically for his rom didn't go over well with the rom I flashed.
I did get back to stock eventually. It just took a few tries and the efs fix. I'm now putting CWM touch back on my phone and flashing a Gingerbread Rom because ICS on our phone is still a little too iffy for my likeing. I'll probably just wait till Samsung releases source for the kernel and cook my own rom.
Click to expand...
Click to collapse
I see, the note modem corrupts the efs partition. Glad you read some things and got it fixed!
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Same problem
CZory91 said:
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Click to expand...
Click to collapse
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
bmanderle said:
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
Click to expand...
Click to collapse
It's an AOSP problem based on the firmware of your camera when getting the phone from what I've seen.
http://forum.xda-developers.com/showthread.php?p=37072484#post37072484
Here's the thread I was talking about, however I'm confused about how to go about zipping and unzipping these files. Or even how to get to them to place the files in to begin with considering internal SD card is the only thing that comes up for USB storage. Unless you're supposed to move them in and out from within android.
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
CZory91 said:
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
Click to expand...
Click to collapse
I had the camera problem on MIUI...
Before flashing, I made a backup of my system with CW
I extracted the SlimISP_ZH.bin from my backup and
copied it to my /data directory and it worked fine.
Link: d-h.st/dwx
(I can't post links yet)
maybe... someone post the fix in this forum and make it sticky... lol
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
CZory91 said:
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
Click to expand...
Click to collapse
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
Click to expand...
Click to collapse
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
Click to expand...
Click to collapse
Yes, that is the post. I also tried MB1 out of curiosity, no dice on either of them. I had a perfectly working CM10. I dun goofed :\.
That was my next step (rerooting, installing that firmware AIO, and then installing CM10). However my question is this, what happens when more firmware comes out? I have to re root and start over again?
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
dandydon414 said:
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
Click to expand...
Click to collapse
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
bbqsfire said:
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Hmm, over the past couple days I've tried out a few different ROMs on my girlfriend's S3 here, and on each one I would get this "Could not connect to the camera" error, every single time upon opening the camera app. One of the Paranoid Android ROMs, Liquid Smooth, and Synergy (even the Touchwiz camera was broken on that!).
I can restore to the original backup I made of the stock ROM, and the camera works fine again. But as soon as I try a different ROM, no camera.
I'd love to get an AOSP ROM running on this phone, but having a working camera is a requirement, and I can't figure out what I'm doing wrong. Searching the individual threads for the ROMs yields little help, and I'm getting exactly the same error on different ROMS, so I feel like I'm doing something wrong on a higher level. Any chance that switching from TWRP to CWM would make a difference? I don't see why it would, but I suppose it's something I could try.
bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
CZory91 said:
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
Click to expand...
Click to collapse
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Watanuki-Kun said:
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Click to expand...
Click to collapse
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
CZory91 said:
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
Click to expand...
Click to collapse
Probably best, that would be my first thing to try if I had that problem, restarting from scratch. If all else fails, restarting from scratch will wipe out everything. If that failed, I would probably suspect hardware issue.
Watanuki-Kun said:
Have you tried odin back to MB1...
Click to expand...
Click to collapse
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
dandydon414 said:
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Click to expand...
Click to collapse
Well I would recommend liquid 2.5 with the kernel that comes with it and I never change any of the overclocking settings. I don't have to pull the battery at all on this one.
Sent from my SCH-I535 using xda premium
TunedReference said:
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
Click to expand...
Click to collapse
Yep, that's what I tried. Nothing.