So I installed TWRP and rooted the Samsung Stock ROM (following thsi thread: https://forum.xda-developers.com/galaxy-s9-plus/how-to/guide-root-s9-oem-fix-t3763974). Worked fine, OEM unlock option still present.
Now I wanted to install LOS 15.1 by formating data, wiping system, dalvic and cache, installing LOS-star2lte.zip, and opengapps-8.1 (and Magisk 17.4 but also tried without Magisk when it did not boot). It is stuck at the first SAMSUNG Galaxy S9+ Powered by android screen. Waited almost half an hour, nothing happens.
I am clueless, What should I do now (and what was my mistake)? I hope you can help me, thank you so much
I'll be happy to provide further information or try out any ideas you have.
try to install stock rom via odin
diiikaaaa said:
try to install stock rom via odin
Click to expand...
Click to collapse
What would I do differently the next time I try to install lineageOS after returning to stock? Also, why wouldn't I instead flash a stock ROM with OEM-unlock fix from TWRP so I don't have to wait 7 days?
You probably have a later vendor version. Lineageos doesn't boot on newer vendors than BRE5. It is mentioned several times on the thread with download links and instructions too.
As for how to get out of your current pickle, either flash stock rom via odin, or just flash the bre5 vendor and los should boot just fine
Also for the record: you shouldn't wait half an hour for a rom to boot. Specially at the splash screen. No rom takes that long
Rainbow_Dash said:
You probably have a later vendor version. Lineageos doesn't boot on newer vendors than BRE5. It is mentioned several times on the thread with download links and instructions too.
As for how to get out of your current pickle, either flash stock rom via odin, or just flash the bre5 vendor and los should boot just fine
Also for the record: you shouldn't wait half an hour for a rom to boot. Specially at the splash screen. No rom takes that long
Click to expand...
Click to collapse
Thanks for your help, so I have to flash the BRE5 vendor tar using odin. Which button do I use in odin? BL, AP, CP, CSC or USERDATA?
EDIT: Nevermind, flashed it as a zip file using TWRP. LOS boots, thank everyone who tried to help, especially @Rainbow_Dash
Related
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
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Check the bootloader compatibilty of these roms, if they r for the mm bootloader it ll not boot untill u upgrade ur bootloader, check the threads from wer u hv downloaded this...
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Exodusche said:
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Click to expand...
Click to collapse
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
check out this thread http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
I use Oxygen_14_OTA_18_all but there's a couple files posted on the bootloader upgrade threads that allow you not too flash the whole firmware just the partions you need to upgrade.
i am having same issue i was on oxygenos 3.1.3 firmware when i started to flash nogut roms every nogut rom works except cm. i flashed official cynogenmod 14.1 thinking that problem must have been solved but it wont boot it just shows oneplus logo. i have waited for 30 minutes but nothing happened if something worked out for you please tell me.
Well I've looked around XDA for soultion and this is it.
CM 14 has some Kernel problems, so only what you have to do is just install new kernel as Arsenic or Black Reactor kernel
I was running the new bootloader on cm13 nightlies and couldn't get it to boot either.
Even after a full wipe and reflash with v7 gapps
Gave up in the end and went back to the last cm13 Nightly
flash arsenic kernel after flashing rom and gapps it will boot. Read the posts in ashwin's official cm 14.1 thread.
Flash Black Reactor (recommended) or Arsenic Kernel.
The zip files that you have for CM are the unofficial ones. So I guess they're from Sarthak Narang. Or at least one of them. Those ROMs require the older bootloader to function. So if you have the newer bootloader, it won't work.
Hi, I am trying to install cynogenmod or mokee rom and the device always gets stuck at cyno/mokee logo. it never goes beyond that. tried to wait for half an hour(waited for one hour twice).
Here is what I am doing:
I used TWRP but it wasnt working so i installed CWM, in both the recoveries I was wiping everything except sd card storage as my zip files were in the card. after that i flashed zip files(ROM & GAPPS). after that i rebooted to system. Am I doing it wrong? I am currently on 4.4.4 stock rom. Need help.
Thank you.
No one to help?
How can TWRP not work on your device? Install again TWRP via adb.
Flash latest twrp 3.0.2 and try
rian_tama said:
How can TWRP not work on your device? Install again TWRP via adb.
Click to expand...
Click to collapse
Rajendran Rasa said:
Flash latest twrp 3.0.2 and try
Click to expand...
Click to collapse
The problem wasn't with the recovery and I wasn't doing anything wrong. It was really too bad to know that the rom version I was installing had a bootloop bug in it. So I had tried two previous versions but they too had the same bug. And unfortunately I tried CONTINUOUSLY for two long days to install those same bugged ROMS as if God has put me in frustration mode. Tech fooled me right, lol.
Grab the November 8 version of Cyanogemod. There are issues with the newer updates.
Hello all. After trying to get various Custom ROMs working, CM 11, 13 or Slimkat 9, unofficial 9.1, no version worked properly with phone signal.. I ended up experimenting with flashing modems or going back to stock firmware and doing all the steps from there but still couldn't make it work.
Stock firmware that came with the phone 4.1.2 (KIES_HOME_I9300XXEMG4_I9300OXAEMG4_1314436_REV00_user_low_ship) was perfectly fine also (I9300XXUGPE1_I9300AMNGPF1_I9300BVUGNB2_HOME) which it's 4.3 from orange spain was fine, tried one from my country and ran fine, also 4.3. Then I found out about this thread:
https://forum.xda-developers.com/galaxy-s3/help/guide-emergency-calls-problem-siii-i9300-t2752541 and by mistake I flashed first the patched modem following this order of events :
4.1.2 STOCK > 4.3 Movistar STOCK > Slimkat Unofficial 9.1 latest > all fine but no signal. Then:
4.1.2 STOCK > 4.3 Movistar STOCK > Slimkat Unofficial 9.1 latest > flashed patched modem from thread above, boot loop.
Then tried to flash the original stock from the phone, didn't work. Stock from my country doesn't work. Stock from spain doesn't work but it goes a bit further in the first boot going to android updating apps , it finishes updating apps and goes into boot loop. That's it. At the moment I can flash with odin or go into downloading mode. When the phone is off, it can manage to charge the battery without problem.
How should i proceed now?
Thank you, I hope you can help or advice me.
EDIT 1: I also tried to flash the firmware from the above thread, the i9300 UK (BTU) but no luck.
GU37 said:
Then tried to flash the original stock from the phone, didn't work. Stock from my country doesn't work. Stock from spain doesn't work but it goes a bit further in the first boot going to android updating apps , it finishes updating apps and goes into boot loop. That's it. At the moment I can flash with odin or go into downloading mode. When the phone is off, it can manage to charge the battery without problem.
Click to expand...
Click to collapse
Odin can't flash a stock ROM or you can flash a stock ROM but the ROM doesn't boot all the way?
audit13 said:
Odin can't flash a stock ROM or you can flash a stock ROM but the ROM doesn't boot all the way?
Click to expand...
Click to collapse
Hey again audit13. It can flash the ROM fine but it gets stuck in boot loop. I'm trying to find the stock ROM with the 3 files but no luck yet, im hoping that can get to do a proper reset factory of everything.
Are you flashing the latest stock ROM from sammobile.com? This file would have everything in one file.
audit13 said:
Are you flashing the latest stock ROM from sammobile.com? This file would have everything in one file.
Click to expand...
Click to collapse
This one ?
Code:
Date
2016-08-01
Country/Carrier
Spain (Orange)
Version
4.3
PDA
I9300XXUGPE1
CSC
I9300AMNGPF1
This one gets to passed the first time the loop till android updating apps dialogue, then goes to boot loop.
Are you performing a factory wipe using stock recovery before booting the flashed stock ROM for the first time?
audit13 said:
Are you performing a factory wipe using stock recovery before booting the flashed stock ROM for the first time?
Click to expand...
Click to collapse
Wiped, then did a reboot in the default recovery mode. All went to normal again. I still need to figure out how to get a Custom ROM without screwing up everything again.. Thanks for your quick support.
Glad you got it working. One thing I would not recommend is flashing a patched modem. The stock modem is the best modem in my opinion.
Somehow I feel like a noob. I wanted to see what the new stock Android 10 was like, so I installed it via Odin. But now I can't get back to a custom ROM because TWRP fails to flash. The tablet's bootloader is still unlocked and I've enabled Dev mode. Download the latest twrp-3.4.0-3-gts4lvwifi.img.tar and put it in AP. When I click start, I get this error "Can't open the specified file (Line 1892)"
edit: Still don't know what I did wrong the first time, but I started over from scratch, flashed stock 10 again, vbmeta, twrp and it worked. Of course I let it boot and set Dev mode between each flash. Once into TWRP, formated data, wiped and install cDroid and gapps and it is now working.
lewmur said:
Download the latest twrp-3.4.0-3-gts4lvwifi.img.tar and put it in AP.
Click to expand...
Click to collapse
Glad you got it working. Figured I'd mention though there is a newer TWRP. 3.4.0-4 didn't give me any issues.
lewmur said:
Somehow I feel like a noob. I wanted to see what the new stock Android 10 was like, so I installed it via Odin. But now I can't get back to a custom ROM because TWRP fails to flash. The tablet's bootloader is still unlocked and I've enabled Dev mode. Download the latest twrp-3.4.0-3-gts4lvwifi.img.tar and put it in AP. When I click start, I get this error "Can't open the specified file (Line 1892)"
edit: Still don't know what I did wrong the first time, but I started over from scratch, flashed stock 10 again, vbmeta, twrp and it worked. Of course I let it boot and set Dev mode between each flash. Once into TWRP, formated data, wiped and install cDroid and gapps and it is now working.
Click to expand...
Click to collapse
Stock a10 sucked?