[Q] Problems after flashing (solved) - Galaxy S I9000 Q&A, Help & Troubleshooting

Solved. Not sure why, but the fifth time or so I threw a different PDA/CSC/MODEM on there Market downloads were working again and the errors at the recovery were gone.

Related

Clockwork Random Reboots SOLVED!

Ok Trying to flash a new rom and CWM is being very strange. I can boot into it fine, but im getting random reboots. I have tried re-downloading it in rom manager, and selecting to erase the current before flashing and im still getting the same problem. Any help would be great!
Oh this is a Droid, not a milestone.
I did have this problem before and i hit the flash button multi times and got one time to stick but that cant be the only solution.
Seemed to have solved it. While or wifi: Cleared downloads cache. Selected to delete current before flashing. Then flashed. Then after that was finished, changed the settings back to default. And flashed 3 more times. It seems to have stuck and is working properly.

[Solved] Going from ICS to GB = Multiply Problems

First thing first - I've read many threads with the same problem but yet non of those threads have solved my problem.
So I decided to flash back from ICS to GB on my friends phone since he was having major issues with it.
I downloaded
- Cooper v1.0.ops
- OdinDownloader_v4.38
- S5830XWKT7_S5830XWKT3_S5830OXFKT1_HOME.tar
Everything went well, the phone flashed successfully and restarts.
After he restarts, he simply goes though continues boot loop, shows the Samsung logo and reboots.
When I try to enter recovery to wipe everything, it shows me the Phone > Triangle > Computer.
Does anyone know what's causing this?
* Edit - 5 minutes after I created this post.
How typical is this? After I officially let you guys know that I'm a moron, the phone works. Outstanding! The phone seems to be working now..
You just got trolled by your phone

CM9 Infinite boot loop - Recovery Mode(no) - Download Mode(yes)

Hello guys,
I have the i9000m
a few months ago I installed CM9 on my phone. Everything was fine until today. It just kept telling me that I'm running low on phone space. So what I did was, move almost all of my applications to the SD card. The notification went away and 10minutes later it was back.
It told me that my message folder was full and that I could not receive new messages. As I was trying to fix this I installed an SMS backup application to move all my msgs to the SD. The phone started acting weird so I rebooted....! Ever since, it's been stuck in an infinite boot loop. I can't access the recovery mode, but I can access the download mode.
I really need my phone for work, and this has come at the worst possible situation. I had spent a lot of time trying to install CM9 and honestly I'm getting desperate with this. I saw in this forum that some people had similar issues and that installing a kernel with Odin fixed their issues. But I couldn't understand what they were doing.
Could someone please tell me to how to install CM7 or stock Samsung Froyo on my phone with Odin? I downloaded Odin but I'm just lost!
Thank you for your time,
Do you need your data like SMS, App etc?
If not I would flash a 3 file Rom with Pit file and repartition. You can download these Firmwares from samfirmwares.com.
If you need the data try just to flash a kernel.

[Q][i9001] CM9 and Gapps Problem

Hello.
I just successfully flashed CM9 Build 6 on my Galaxy S Plus. It was terrifying.
My problem lies in the fact that i can't seem to get Gapps working. I tried multiple versions, from the latest one to 20120429, which is currently the last one flashed on my phone. The apps don't appear, and trying to use a downloaded Google Play app from the web makes it start, but it just flashes a 'Loading' screen for a split second and then boots me back to the app menu.
Any ideas on what I could do next to fix this?
Have you tried wiping your entire phone and then reinstalling CM9 + gapps (the version provided by arco68)?
It's what I did the first time. Should I flash it again?
You should definitely give it a shot, maybe something went wrong while flashing.
What recovery are you using?
Apparently I had the stock one, that must of been the problem. Didn't document well enough.
I've just flashed 6.0.1.2 and I'll flash everything again once I download all the files.
Yep that was it. It runs as it should now. Thank you for your help.
Good to hear!
Slightly related, please note what's going on in the dev section (here). Certain combinations of recovery software and hardware may brick your phone if you try to wipe data. Playing with your new recovery could be dangerous right now, be careful!

stock rom lockscreen problems

Hi, this is my first post and im having problems with my A6.
I tried to install TWRP wich mostly worked fine, but i didnt follow the tutorial correctly wich left my device boot looping at the boot-logo (i didnt install the zip files needed),
so i thought i soft-bricked my device and i downloaded correct stock rom versions from [cant post outside link because im new, but it would go here]
and installed it with Odin3.
This has worked fine and i restored it again, but for some reason if i set the lockscreen protection (like PIN or Fingerprint) it first wont work (but it shows changed in settings)
and when you reboot the device it soft-bricks at the lockscreen and keeps showing the samsung logo then lockscreen for 1 second and samsung again etc. (this wont brick if i dont set any protection)
I have tried a lot of things like installing TWRP again and clearing cache but none seem to fix the problem (other than doing a factory reset).
so im asking here if someone has a clue to what is happening?
EDIT: i will try to install a older version and try to update it with the official updater and i will report back shortly
Results: It did fix my problem with the lockscreen but if i flash TWRP and install Magisk it wont work again
EDIT2: apparently if i wait long enough at the lockscreen-bootloop(atleast couple of minutes) it will grant me access but the protection still doesnt work
EDIT3: Im using Android 9 and i noticed that this is probably the cause, but i didnt find a updated version

Categories

Resources