I had my first run in with the dreaded boot loop last night trying to install a transparent notification bar and window. The one I had tried from another site must have needed a CynogenMod Rom or something cause it didn't end well for me. Thank god for Clockwork! Anyway, I'm really not good at all with the adb shell commands and I was hoping someone could point me to a .zip that I can use in Metamorph that is compatible with stock OTA 2.2.
I searched the threads here and didn't come up with anything.
Thanks!
folks - i used almost methods to switch from non-CM to CM9 based ROMs on my rooted phone. I see the transition from RED to BLUE screen but still un-successful. Everytime i have used super-one-click to unbrick the phone.
My question is: is there a super-one-click way to start cleanly with any version of CyanogenMode for infuse?
You might try posting in the Q&A section.
saawan said:
folks - i used almost methods to switch from non-CM to CM9 based ROMs on my rooted phone. I see the transition from RED to BLUE screen but still un-successful. Everytime i have used super-one-click to unbrick the phone.
My question is: is there a super-one-click way to start cleanly with any version of CyanogenMode for infuse?
Click to expand...
Click to collapse
Simple answer is no. There is no simple way. IT is either the right way or the wrong way. You have to follow all instructions step by step without taking any shorcuts. And yes that means doing a full wipe of your device and setting all your settings, widgets and apps up again.
Please post in the correct forum. Thread closed
I've tried searching for the solutions to this, but some of them are difficult to search and I'm struggling to get relevant results. So I apologize if any of this has been covered elsewhere.
Anyhow, I just installed the ParanoidAndroid ROM last night, and it all went very smoothly, and I was pleased. But, there seem to be a couple issues that either I need to iron out, or that the devs need to. And I'm fully willing to believe it's an issue on my end and not theirs, so, here we go:
1) In CWM, the top half of the screen or so has the rainbow glitch going on and there's a de-centered kind of effect happening that makes it very difficult to use.
2) I'm unable to get my external SD card to mount. I've seen plenty of threads about this similar issue, and I've tried tweaking the build.prop entry regarding this, but nothing I'm doing is helping.
3) The flash only works once per boot, even with included flashlight app. I haven't tested the flash's functionality in the camera yet. But in the flashlight app, the flash will turn on, and when I turn it off, it won't come back on until after a reboot.
4) I now have two installations of the stock Gallery app (com.android.gallery3d and com.google.android.gallery3d). I'm sure I can just uninstall one, but is there one that would be wiser to uninstall?
Otherwise, everything else seems to be working just fine. Thank you all very much in advance.
I've since discovered and fixed a new problem. My phone was apparently not sending or receiving any MMS messages, over WiFi or otherwise. But the APNs described in this post fixed that entirely:
http://forum.xda-developers.com/showthread.php?p=23806717#post23806717
As problem #4 from above goes, I deleted the com.android.gallery3d app and kept the com.google.android.gallery3d app as there were internet and syncing features that were omitted or nonfunctional from the former one.
Just so you know, if you read through the paranoid thread in the dev section or any of the ics ROM threads actually, all of your questions r covered. I cangive you answered/jumping off points for your questions.
1. The rainbow distortion comes from having Froyo bootloaders instead of GB. To fix this you will need to use Odin or Heimdall to flash the GB bootloaders. Look in the ISET Super Everything thread that's stickied in the dev section. BE SURE to flash something else with Odin or Heimdall (whichever you choose) before you try flashing the bootloaders. If you lose your connection while trying to flash bootloaders, you can hard brick your phone which basically means you have a shiny coaster.
2. Your external sd card is found in the emmc folder on ics ROMs. You need a root enabled file explorer to open it.
3. Using your camera flash as a flashlight which I believe is referred to as torch is one of the few known remaining bugs on Infuse ics ROMs. The flashlight app that is included is currently the only way to get it working. The flashlight should turn on everytime you open the app but it won't turn back on if you turn it off while in the app.
4. MMS is an issue with the APN settings. Look at the last few pages in the dev section. I know it was recently covered on a couple different ics ROMs threads. To get to the APN settings, go through the following path in the settings.
More (under data usage) > Mobile Networks > Access Point Names, click on the AT&T listing, then change MMS Proxy to 66.209.11.32
I'm pretty sure that is all you have to do to fix MMS but read some dev threads for more info. I think you can also try to look in the Dev Tools app if it is included with the ROM. In the app, click connectivity then start MMS. Again, further reading should give you more info.
Boz™
Sent from my SGH-I997 using xda app-developers app
Yeah, the flashlight thing, I knew was a known bug. But the latest update claiming that "all bugs squashed" misled me, I guess. Because that bug obviously persists. But, c'est la vie.
As the rainbow glitch goes, I never installed Froyo on here, I went from stock to Gingerbread to... actually, here's specifically what happened:
•Initially, I installed 3e Recovery and CWM on my stock Android 2.2 per the instructions here, http://www.youtube.com/watch?v=Y09p-J_g_Rg, and everything went fine.
•Then I flashed Gingerbread UCLB3 per this thread, http://forum.xda-developers.com/showthread.php?t=1508619, but unfortunately, I made a dumb mistake. I neglected to disable Voodoo Lagfix first and softbricked my phone.
•So, I went back to the Infuse Super Everything Thread and found this fix, http://forum.xda-developers.com/showthread.php?t=1092021, brought my phone back to stock, just fine.
•Then I flashed to UCLB3 the same way as before, only this time disabling Voodoo and it all worked perfectly.
•Then I immediately flashed to ParanoidAndroid and everything went as described in the thread and now here I am with the CWM glitch.
So I've only been stock or Gingerbread ever before on my phone.
Anyone know how to simply change the font or install a new one?
Sent from my SGH-I997 using xda premium
I use ROM Toolbox Pro.
Edit: Check the Paranoid Android dev thread end of page 32 and beginning of page 33. The guy that maintains the PA port just posted a link and instructions for the fix to rainbow recovery.
I'm no expert so I may b wrong but I'm pretty sure that if you had a stock AT&T infuse then it most likely came with Froyo originally. Just bc you flashed a GB ROM doesn't mean you got the bootloaders. To get the GB bootloaders, you need to run Heimdall a second time with the "Install Bootloaders" checkbox checked. I'm not exactly sure how it works in Odin but I think you have to have a file in the PDA slot in order to get the bootloaders installed.
I do know that if you have rainbows, it is bc you have Froyo bootloaders. Our at least that is the only reason I've ever heard of and I've read of people with the issue numerous times. I would just read through some of the dev ics threads bc there have been a few times in the last week that I've seen people pay steep by step instructions explaining exactly which Heimdall or Odin to use. I just know that you have to take extra steps to install GB bootloaders. With Heimdall that means checking the flash bootloaders checkbox. They do this bc it can hard brick your phone so they don't want you to install them unless absolutely necessary.
Boz™
Sent from my SGH-I997 using xda app-developers app
Ah-ha! Very good, someone else is having my same problems, lol. I'll definitely be using Odin, as that's how I fixed my softbrick issue and I could never get Heimdall to install on my computer properly (Java issues or something, couldn't figure it out and Odin worked anyway).
Do you know if flashing the bootloader will cause any loss of information or settings? Or will it affect nothing else?
I'm not 100% sure on that one. When I did it, I was using Heimdall to fix my soft bricked phone at the same time so I was basically starting fresh. I'm not sure if it is possible to just flash bootloaders in the Odin PDA slot and keep everything else. I would assume that you would lose everything and have to reflash the ROM from recovery but that's just an assumption.
I would get titanium backup (if u don't already have it) and backup everything and sync with your Gmail account just in case. That way u can save it apps and their settings.
You may b able to ask that question on the PA dev thread and get a better answer.
Boz™
Sent from my SGH-I997 using xda app-developers app
There's an XDA Forum restriction on newbies. I can't post in any Dev forums until I've... done something, I forget. Ten posts or ten thanks. I forget what. Either way, I'm not allowed in there yet. lol
Anyhow, based on some threads I've found, it seems possible to flash only the bootloader in Odin. I'm still just waiting to find out how much information is lost in the process before I dive into it.
But yeah, I do have Titanium, and now that I have everything installed and set up just the way I like it, it is time for a backup anyway.
Supposing I need to, is there any problem restoring system apps and data once I do this? Because everything will be identical, minus the bootloader. I just know I've read enough about the dangers of restoring system data on the threads here to be cautious. Even though I'll just be going from ParanoidAndroid to the same flash of ParanoidAndroid, plus a new bootloader, but better safe than sorry.
Thanks for all your help, man.
Appears as though that question's already been answered here:
http://forum.xda-developers.com/showthread.php?t=1603220&page=5
Bottom of page 5 states somewhat affirmatively that no data will be lost. So, lovely. Now I've just got to flash the bootloader, and then work on my forum searching skills. I can never find ****, when clearly it's somewhere. lol
dstarr3 said:
2) I'm unable to get my external SD card to mount. I've seen plenty of threads about this similar issue, and I've tried tweaking the build.prop entry regarding this, but nothing I'm doing is helping.
Click to expand...
Click to collapse
Figured out the emmc part but how do you actually open the external SD on your pc?
i would like to preface this by acknowledging that this was a serious mess up on my part. i tried to root my sprint nexus s 4g the other night. I used a guide on nexusshacks dot com due to its simplicity and detailed instruction.i did all necessary steps but the first time i tried to boot into clockwork recovery i got a dead android and a red triangle error message. my phone restarted a few minutes later and i was able to fix that problem (or so i thought) and boot into recovery. i applied the correct zips and such that came in the download and i went off to sleep. the next day i tried accessing super user and realized it didn't work. i went back to that guide and noticed that its was for ginger bread and there was a new guide linked at the top for ICS . this is were i need assistance. is it enough to just do a hard factory reset and start over or is there more to it than that. also, will such a guide work on jelly bean or should i find another guide. i only use that site for the fact it has a well done step by step tutorial and all needed files compiled into one download. i am aware this site is much better for such things, but i'm, new here so i felt a tad intimidated. anyway, any help is appreciated, i already looked for similar problems but no one else made the dumbass mistake.
(i cant post links because this is my first post, so i apologies for the inconvenience)
I have been a long time lurker of XDA. Usually with some diligent searching and several hours of reading threads to understand, I can figure out what I need to do. I spent five hours yesterday and feel I'm no closer to a solution than I was when I started. So I think I need some help dissecting my problem so I can focus my searches better.
My wife and I both have a Samsung S3. It is my standard practice to throw on my own Recovery, snag the earliest possible nandroid backup, and then root. I like to run CM but my wife prefers the stock ROM. With my wife's S3 when a new OTA update is available and nagging her I would roll back to the backup that would take the OTA update. I haven't figure out why some do and some don't. Once fully updated I snap another backup and on she rolls.
Now my problem and you've probably already figured it out. I am getting a Status 7 on just about anything I do. I tried tons of stuff and all of it resulted in a Status 7. This is the first time that I have to ask for Android help because I don't understand the moving parts of the problem I'm having. Any pointers would really help.
I would like to list everything I tried, but I'm not sure I would paint an accurate picture since I was furiously searching and trying things in any fleeting direction yesterday for over 5 hours. I can list some bullet points, but don't assume any of them are fully explored, or done in proper order.
I read about knox'd firmware and ROMs. I'm not certain if that's related to my problem space.
I read something about RUU, but I seemed to have lost the bead on that one.
I could comment out the assert that is failing, but that is a huge risk that I'm not sure I want to take unless I can get out of it.
I upgraded to latest CWM and the status 7 still happens.
I have done factory resets and the status 7 happens.
I'm not exactly clear on what I did, but I recall wondering what had changed to cause the status 7 because I couldn't do updates from old backups that I used to be able to do updates from. It's like something changed on the phone.
If someone has any ideas, could you point me in the right direction?
Hi there!!
There seems to be many threads about status 7 errors, for the s3 as well as other devices. Its a common error.
If you search on status 7 and s3 you will find a lot.
But I found a couple very detailed guides.
This one is non device specific....
http://forum.xda-developers.com/showthread.php?t=2302599
This is about the S3's boot loader....causing status 7 errors. Perhaps you are not on the right boot loader for what you're trying to do?
http://forum.xda-developers.com/showthread.php?t=2302599
And this is how to return to stock, which is an option if nothing else works. Then you can start fresh....
http://forum.xda-developers.com/showthread.php?t=1725839
I'm not sure which S3 version you have, so be sure you use files made for your version if its not one of the models mentioned in the above guide.
Good luck! ?
KJ said:
Hi there!!
There seems to be many threads about status 7 errors, for the s3 as well as other devices. Its a common error.
If you search on status 7 and s3 you will find a lot.
But I found a couple very detailed guides.
This one is non device specific....
http://forum.xda-developers.com/showthread.php?t=2302599
This is about the S3's boot loader....causing status 7 errors. Perhaps you are not on the right boot loader for what you're trying to do?
http://forum.xda-developers.com/showthread.php?t=2302599
And this is how to return to stock, which is an option if nothing else works. Then you can start fresh....
http://forum.xda-developers.com/showthread.php?t=1725839
I'm not sure which S3 version you have, so be sure you use files made for your version if its not one of the models mentioned in the above guide.
Good luck! ?
Click to expand...
Click to collapse
I have the Samsung Galaxy S III L710.
I did try the recovery version issue. That didn't help. I think my best option is to return to stock. I will see if there is a return to stock thread for my phone.
Thanks!
You could try twrp.... Just be sure whatever recovery you use, that it is definitely for your model. Or that can give you status 7 errors too.
---------- Post added at 12:00 PM ---------- Previous post was at 11:57 AM ----------
Here's a return to stock for your model... http://forum.xda-developers.com/showthread.php?t=2591818
Though I'm not a big one click fan, or toolkits. Lol
And here's another.... http://forum.xda-developers.com/showthread.php?t=2605812
KJ said:
You could try twrp.... Just be sure whatever recovery you use, that it is definitely for your model. Or that can give you status 7 errors too.
Click to expand...
Click to collapse
I will give TWRP a shot since that's easy to do. I will post back what works, and what doesn't.
If twrp doesn't work...return to stock might be simplest answer. ?