So one day I tried to downgrade my coustom ROM but figured out my recovery was too new so with the ROM I had I downgraded the recovery woth the "too new" of a ROM, now Everytime I boot up all I see is the logo. Can't get into recovery and can't get into download. How can this be fixed?
Related
ok, so i got this phone from a classmate. very nice: i9001.
problem is, the thing is stuck in download mode... wouldn't boot any other way.
i think, just reflash the rom and it will work again.
so i get it to be recognised by odin, flash the rom, and the thing starts getting stuck at samsung logo.
so i go to samsung service and they do the exact same thing. with the same results. since the phone had been dropped at one time, no warranty.
i can't let go, so i decide to flash CWM. HEY! the thing starts booting
but now it just reboots instantly after 2mins of usage.
does anyone have suggestions on what to try next?
currently i got it back to stock everything.
Hey,
I had the cm9 on my I9001, now i want to have the stock rom, i downloaded the Stock rom, ArriesVE.ops, and Odin.
Than i flashed the ROM on my phone, after this was done, it restarts, i can see the White Samsung Logo , after this i see the "Samsung Galaxy S Plus" Logo, this logo stays for a few seconds and than my phone restarts again and all repeats..
What should I do
Maybe this would help you http://broodplank.net/old/flashsamsungi9001.php
Same Thing...
Gnampf7 .. did u find a way past that.... have been stuck @ de same point whole day now... flashed the stock ROM thrice... cleared cache... cant do a factory reset thou... its asking for a passcode i dont have.
any ideas??
Bootloop on i9001
Hi guys, i gonna tell you about how my i9001 was stuck in a bootloop. Maybe you could help me. I'm sick of it.
Cause: I installed cm10 and cwm5 or 6 as recovery and upgrade my device by using Ota Updater. When I restarted my i9001, it got stuck in a bootloop.
What my i9001 can display: It can access to rampdump mode and download mode. In case I try to turn on my i9001 or access to recovery mode the Samsung logo is shown twice. It often gets stuck showing the typical grey battery flat (with a loading stopped) and the black screen alternately.
Attempts: i've tried everything except for the right solution. Lots of forum threads and nothing works for me. I've tried:
1.- Boot_loader for device boot.
2.- I've flashed an stock rom: XXKQP, and 2 more: BVKPC y XXKQ1. Each one are official.
3.- And then recovery-clockwork-5.5.0.4 and -6.0.1.2.
4.- I've tried, then, flashing feamodrecovery 1.2.
5.- Nothing works for me.
I've been using Odin 4.43. AriesVE in OPS section and when flashing these roms: one package. For recovery packeges: one package and pda (I tried these two options).
I can't reach at recovery mode. Any help would be greatly appreciated. Greetings!
http://forum.xda-developers.com/showpost.php?p=51290392&postcount=13
Hi guys,
Today I flash with Odin a Stock ROM for i9001. The process goes well buy when I started the device, it stays in the boot animation (the Galaxy S Plus animation). I tried to enter to the recovery to do a factory reset but it reboots the device.
What I can do??
Thank you!!
Solved... Sorry
Earlier i flashed my S3 with Odin to cyanogenmod 12.1
Because i want to sell my phone, i did a factory reset.
But now, nothing is working anymore. Only the downloadmode is working. Recovery mode gets to black dead screen :s
I tried to flash another recovery and cyanogen again, but no boot.
Am i doing wrong? Or what can i do to make the phone work again?
Thx!
fixed with parameter flash, and then stock recovery
Working again now
my phone suddenly started this problem with the mic and was frozen too
last week my phone was out of battery but when i charged it up and wanted to boot it, it went on bootloop (couldn't access recovery either)
So i kinda wanted to install TWRP (which I did) and tried a new custom rom.
but now even after a clean stock rom flash using Odin, phone wont boot at all. its stuck on samsung logo to Galaxy A71 logo back and forth. any solutions? please.
Thank you
If flashing full stock isn't working, then it could be a dead motherboard