Samsung S9+ new ROM - Android Q&A, Help & Troubleshooting

Hello
So I was trying to root my Samsung Galaxy S9+ a couple hours ago. But I got stuck on a bootloop in the middle of the process so I started panicing and trying every button in the TWRP menu. I accidentally wiped all files including the OS. So then after a little bit of research I tried installing a custom ROM that I found on a firmware website. The custom ROM was the exact same model as my phone, Android 10 G965F. I had no idea how to install this kind of stuff so I looked it up on youtube. I tried doing it with Odin but I didnt know which .md5 file to do first (because there were 5 .md5 files in the .zip file) and whichever one I tried loaded forever. My phone is currently stuck on the Downloading screen.
Any help would be very appreciated A LOT. Thanks!

I would recommend you flash in factory os via odin. If you don't bother to follow instruction from the custom rom op, don't attempt to root the phone or flash a custom rom.
You mentioned you panicked and hit everything you can see in recovery. That's a big no no and seriously don't meddle with it. You'll brick the phone.
Custom rom is in zip file and you do not need to unzip it. You do not use odin to flash in custom rom.
Please follow the instruction from the custom rom op. Seriously follow it. Every single step.
Sent from my SM-G985F using Tapatalk

Related

[Q] Flashing ROMs without ClockworkMod - POSSIBLY BRICKED

Hi,
I am unsure about how to flash a ROM on to my phone.
I have already rooted it and installed a insecure kernel using Odin and the Samsung Quick Root tool (found here: http://forum.xda-developers.com/showthread.php?t=1125414). :victory:
I am still running the insecure kernel that I flashed with Odin, and did not install CWM as I do not know what to do.
ROM Manager is installed on the phone but I don't think CWM is actually installed.
Currently, I want to install the F1 Galaxy Nexus ICS ROM. (http://forum.xda-developers.com/showthread.php?t=1601518)
All I want to know is do I need to install CWM, and how to install and flash the ROM to my phone.
The exact model of my phone is i1900-XWLPI.
Thanks.
Hi.
Yes you need cwm.
How to install Rom always be a guide in thread...
Send form Galaxy S2. Using XDA Premium
I was following a guide on it.
Now I am worried
I think it is bricked as it is stuck on the yellow triangle screen.
I don't have a jig and I NEED IT WORKING.:crying:
Ok I managed to get it to go in to d/l mode and flashed kernel back to the one I had earlier.
I think I'll just leave it for today and try another time.
Too much happened today and I don't want to risk a permanent brick.

[Q] flashing cwm causes bootloop

Ok, because I was so happy with cyanogenmod on my galaxy s I decided to try to install it on my SII.
Silly me, I decided to follow the instructions. couldn't get my trusty odin working, even after a couple of reboots and reinstalls of kies. Heimdall turned out to be the 64 bit version so I needed to find the 32 bit version. Long story short, the instructions sucked...
Then, I tried to install the suggested cwm. After a reboot, my phone entered a bootloop. I could enter recovery but trying to flash cm10 gave me "Status 7 blabla".
So, I searched on the web for a stock rom to at least get my s2 working again, found one and flashed it. Market keeps on crashing and it's version 4.0.3.
I tried reflashing cwm, cf-root and time and time again it kept creating a bootloop after which I had to reflash the rom with the broken market to get everything working again.
My questions are:
where did I go wrong in flashing cwm? Is there a different version I should flash? what's up with the extremely bad cyanogenmod instructions? Can someone get the market working again?
can someone guide me step by step through the process?
Why don't you flash it via recovery?
Sent from the little guy
gastonw said:
Why don't you flash it via recovery?
Sent from the little guy
Click to expand...
Click to collapse
because it gives the error "status 7"
I can't install a cwm that doesn't bootloop (I can however enter recovery) and in recovery I can't flash a thing because it throws errors at me
Assuming that you are on stock samsung ICS ROM, flash Siyah kernel from Odin
http://d-h.st/Bcf
After this you will get CWM recovery from which you can flash any i9100 CM version.
Sent from my GT-N7100 using Tapatalk 2
quick follow-up:
I had another laptop laying around that was never poisoned by samsung kies, so I decided to give it a try. installed the usb-drivers and used odin to flash another stock-rom version (that actually worked this time )
Then, I flashed cf-root and upgraded to cyanogenmod without any problem.

Mega...semi-bricked??

So I have a Sprint Galaxy Mega and it seems as though it may be semi-bricked. It will not boot past the GALAXY MEGA logo. It will just continuously power cycle to and from that logo. If I attempt to put it in recovery, it will say "RECOVERY BOOTING" in blue letters as usual, then power cycle right back to the GALAXY MEGA screen. It will boot into Odin mode and accept Odin files, but after attempting do do a typical "stock Odin" scenario, nothing has changed. I looked around for the Pit but cannot seem to find it. Does anyone has a reliable link to the latest Odin stock restore and the PIT file that matches it?
Maybe an error with your system data. So you can't reboot into recovery ? If you can try to wipe data and cache and reboot.
It may be an abnormal re-partition when flashing stock rock, and then I can't help you (have the i9205 international model). Some members of this section have the Sprint version, try to send them a PM if nobody can help you
Nope, no recovery. I was considering flashing a custom recovery to it to see what it does but I don't wanna kill the phone any more than it already is...
Yes I understand. But flashing custom recovery can solve your problem, only if you can boot on it. I think it can't make more damages to your phone, he just always stuck on boot phase like a brick, but if you don't want to try, wait for a developer making you a PIT file. More safe, the Galaxy Mega have a too poor development support for risk anything...
Well I went ahead and flashed TWRP to it. It will boot into TWRP just fine. Tried flashing the stock L900 ROM zip and it still won't boot.
Well I installed a custom ROM, SlimKat, and the phone boots. If I install the stock ROM located in the following link, OP's signature, the phone goes right back to bootlooping. ???
I need either the stock ROM or a ROM with dialer codes because this phone will be flashed to a regional carrier.
what recovry version you use bro. maybe recovery problem. try use your custom rom to flash another recovery from philz. the latest one. some time recovery dont work properly to downgrade from 4.4.2 to stock 4.2.2.
Great, so with Philz Touch Recovery, I never had problems for downgrade and I do this often for testing roms. Now it should not bootloop if you reflash stock.
I am using "CWM-based recovery 6.0.4.7"
I will try Philz recovery
After trying Philz recovery to flash the stock file I found, it once again bootlooped. Is there another stock ROM floating around somewhere or possibly a custom ROM that has dialer codes such as ##3282# enabled?
No idea... But actually the most complete stock based custom rom is MegaFire I think. Flash V5 (not V5x !) it should be enabled.
I don't see what is the problem while flashing stock rom... Oh ! Maybe you haven't enabled USB Debugging, I forgot to do that one time and I had some issues, in case you try to flash a firmware where Knox or others features are on with a modem without these, may cause bootloop. I've searched for 2 days before solve that little problem...
Have you tried another firmware ? If you can flash custom rom, something went wrong before flash... Odin folder is complete ?
Strange...once again a boot loop after flashing the MegaFire ROM
I'm almost certain I need the PIT file. I cannot find it anywhere.
Well I got the phone to boot from that rooted stock ROM FINALLY. I don't remember for sure but I think what I did was first flash TWRP, then flashed boot.img.tar that I found somewhere, it was listed for the Sprint Mega. I then booted into TWRP and flashed the stock rooted ROM(zip) I mentioned before. It now boots perfectly and everything works except one tiny little detail. No WiFi, no cellular signal at all. Baseband version: unknown in About phone.Already tried flashing the Sprint stock modem from the same download link as the ROM and it didn't work.
I'm having the same problem too dude, I
I download n flash all.the firmware I could find online, since I have no idea what the country of origin is. But most of them work, but no WiFi, Bluetoothand the sim card slot don't read
VirtueToVice said:
Well I got the phone to boot from that rooted stock ROM FINALLY. I don't remember for sure but I think what I did was first flash TWRP, then flashed boot.img.tar that I found somewhere, it was listed for the Sprint Mega. I then booted into TWRP and flashed the stock rooted ROM(zip) I mentioned before. It now boots perfectly and everything works except one tiny little detail. No WiFi, no cellular signal at all. Baseband version: unknown in About phone.Already tried flashing the Sprint stock modem from the same download link as the ROM and it didn't work.
Click to expand...
Click to collapse

[Q] Installed CWM Recovery on Galaxy Note N7000 and got in a bootloop straight away

Hello dear community
This is my very first thread I am making on this website, so please pardon me if I am on the wrong page of this website.
Anyways, I'm more or less desperate. I saw a youtube tutorial on how to install Android 4.4 Kit Kat on a Samsung Galaxy Note N7000 and I heard I'd need root AND a custom recovery.
Because I'm a total newbie to this kind of stuff, I tried the very first thing I saw that had something to do with custom recovery, because I already had my phone rooted. So, I looked up a tutorial on youtube on how to install CWM custom recovery and ended up with installing it successfully, but now my phone is stuck in a bootloop. As I already mentioned, I am a newbie and therefore I am very desperate at the moment, you know.
The only thing I can do is go to Recovery Mode, but if I try to turn the phone on it gets stuck in a bootloop (It actually doesn't loop at all, it just freezes at the moment when the Samsung Galaxy Note logo appears and doesnt do anything after that.).
I think my problem is that I actually threw a new Kernel on my phone, because the video title says "How to install Kernel with CWM [...]"
I would be very very very very very grateful if anyone was kind enough to help me get out of this!
I really need help!
Thanks!
PS.
If this helps you help me:
This happened when I had Android 4.1.2 installed.
There's going to be 2 ways to get out of this:
1) Reinstall the stock firmware via Odin.
2) Install a custom rom via recovery.
Personally, I'd go with number 2 because a) you wanted to update anyway and b) if you have the right recovery and rom, it'll be easier as you can just put the files you need on an external SD card and install via the custom recovery. Now, not all recoveries are able to flash any file. Many times you need specific ones to install the newer android versions. So, if you are wanting to install something 4.4 based, then using a recovery that was made, say, last year, probably will not work well if at all.
Another thing to try first, is to wipe the cache and dalvik cache in recovery since you said you tried to install a kernel. It is always recommended to wipe these when installing (assuming you did pick a compatible kernel with what you were trying to install).

Phone stuck after flashing (urgent)

I went to cf auto root to find a root file for my phone and like an idiot, downloaded a boot+recovery file instead of the rooting file So I accidentally flashed a recovery+boot tar file on my galaxy j5 prime (SM-G570F) and ever since that it keeps restarting after the very first (samsung galaxy j5 prime, Powered by android) page. I flashed twrp and that works, I can use downloading mode and flash other things, I've tried a number of different boot image files, the problem remains, so Ive decided to flash a copy of stock firmware (latest update) instead. Will that fix it? If not, can I fix it, and how? Also pls provide a stock boot image if you can, I want to try that again one last time. Also please reply fast, If my parents find out, they'll kill me

Categories

Resources