Lineage 14.1 OS I can download with Odin - Galaxy S 4 Mini Q&A, Help & Troubleshooting

Can't find a loadable Lineage 14.1 rom I can use with odin. Evidently tried to flash the wrong one, now my phone will only
boot into download mode. Alternatively I could use a stock rom for S4 i257 to flash it back and start over, thanx for any help.
Try to follow all the steps found in here, still doesn't work, keep getting error messages, "signature verification failed, etc.

Related

Cyanogenmod Install failed on Galaxy S3 [SOLVED]

Hi Guys,
This is my first time working with a custom ROM. I have an old S3 which sucks due to Samsung bloatware. So, I wanted to play and install Cyanogenmod on it.
I have a Rogers Samsung Galaxy S3 (Canada) and the model is SGH-I747M. I was following https://wiki.cyanogenmod.org/w/Install_CM_for_d2att to install the recovery image & Release build (https://download.cyanogenmod.org/?device=d2att&type=snapshot). I am using a Mac.
Steps I followed:
Installed Heimdall Suite on the Mac
Downloaded CM12 build & Google App and transferred it over to my phone's internal storage
Restared in download mode
Transferred recovery image
Restarted in recovery mode
Wiped/Factory settings
Apply Update -> cmbuild.zip file
It tried to install and then gave me a "Install Failed" error. I was then able to re-boot normally and get into the phone.
Any ideas, suggestions on what did I miss and what can I do? Is it ok to install the CM12 release build for my S3? Or do I need to go with CM11 or lower?
Thanks.
Flash twrp via heimdall to the s3. After flashing, boot into twrp and flash cm12.1 and gapps.
audit13 said:
Flash twrp via heimdall to the s3. After flashing, boot into twrp and flash cm12.1 and gapps.
Click to expand...
Click to collapse
Ok, so I tried what you suggested. I am still getting Install failed error.
The error says:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/d2att.zip'
UPDATE:
Fixed the problem by Formatting through TWRP and flashing CM12 & GApps again. Worked . Thanks for the help.
Glad you succeeded!

TWRP incorrectly states that no os is installed

So I have TWRP installed on my phone and am running the CM 13 custom rom. When I boot into TWRP and then hit reboot system, it gives me the warning "No OS installed! Are you sure you wish to reboot?" It gives me this error every time, even though I DO have an OS installed. The reason that this is a problem is that I need to flash a Gapps zip onto my phone, but whenever I try to, it says that I have no rom installed, and that I need to flash a rom before gapps. This is very annoying, because I DO have a rom installed, but yet these errors keep showing up. To find the guide I followed, type (I'm unable to post links yet) "How to Install CM 13 On T-Mobile Galaxy S2 Android Marshmallow 6.0" into google. It will be the first link. I followed those steps exactly, so I don't know why this is happening. Any possible fixes would be appreciated!
AndroidAllTheWay358 said:
So I have TWRP installed on my phone and am running the CM 13 custom rom. When I boot into TWRP and then hit reboot system, it gives me the warning "No OS installed! Are you sure you wish to reboot?" It gives me this error every time, even though I DO have an OS installed. The reason that this is a problem is that I need to flash a Gapps zip onto my phone, but whenever I try to, it says that I have no rom installed, and that I need to flash a rom before gapps. This is very annoying, because I DO have a rom installed, but yet these errors keep showing up. To find the guide I followed, type (I'm unable to post links yet) "How to Install CM 13 On T-Mobile Galaxy S2 Android Marshmallow 6.0" into google. It will be the first link. I followed those steps exactly, so I don't know why this is happening. Any possible fixes would be appreciated!
Click to expand...
Click to collapse
I would try to flash another version of TWRP. Sometimes, the latest TWRP is not the most compatible with all the ROMs out there.

Can't install stock ROM after trying to install Magisk

SOLVED
I installed handesROM via TWRP. It's not stock ROM but so far I like this ROM. Thanks!
* I don't know how to remove this post
----
Hi,
I tried to root my Samsung A5 (2017) (SM-A520F) and it worked with SuperSu but I am not an fan of SuperSu. So I tried to install Magisk and from there the trouble started. I tried to modify the boot.img file but I failed.... (I tried to install the boot.img through TWRP) And now I can't start the phone and I can't install the stock ROM firmware anymore through Odin.
When I try to turn the phone on, the message "Could not do normal boot. Invalid KERNEL LENGTH" flashes
From what I see on YouTube, people only have 1 file. But from the firmware i've downloaded 5 files, the 5 files:
- BL_A520FXXS4CRE2_CL13389536_QB18039097_REV00_user_low_ship.tar.md5
- AP_A520FXXS4CRE2_CL13389536_QB18039097_REV00_user_low_ship_meta.tar.md5
- CP_A520FXXU4CRD3_CP9435316_CL13389536_QB17696899_REV00_user_low_ship.tar.md5
- CSC_PHN_A520FPHN4CRD4_CL13389536_QB17716760_REV00_user_low_ship.tar.md5
- HOME_CSC_PHN_A520FPHN4CRD4_CL13389536_QB17716760_REV00_user_low_ship.tar.md5
When I put all these files into Odin, it FAILS. This really frightening me. I have had this kind of problems with my Samsung S4 but Odin always saved the day. Now it does not (yet?)
* TWRP is still working
Does someone has any idea how I can fix this? Tips? Thanks!

bricked/soft bricked please help

before /how i got here
i wanted to install a rom on my n5110
first I flashed twrp through odin and i could never access the recovery
so i tried to follow these instructions
https://wiki.lineageos.org/devices/n5110/install
which use heimball (i have used adb before, and i did have some trouble installing himball on el capitan, but managed to install version 1.4.1 since then i found that maybe it doesnt work anymore)
this is where the trouble started after flashing i was unable to access stock rom or recovery and was stuck at boot image.
after that I tried to flash this rom via odin (return to stock)
https://forum.xda-developers.com/showthread.php?t=2773712
now...
somehow this failled and i ended up with a screen that reads (firmware upgrade encountered an issue. please select recovery via kies....)
since then I have tried flashing again via the above method which failled
and another stock (N5110UEEMF1 from https://forum.xda-developers.com/showthread.php?t=2289441) which may have further confused things as realise that this is the out of the box stock and I was on kitkat
which gave the error " invalid magic string"
I have searched for a similar enough problem but not found please help
bump
Download the stock ROM from updato.com or sammobile.com and flash it with Odin. If it gets stuck in a bootloop after flashing the stock ROM, boot into recovery and perform a factory reset.
I recommend flashing with the original Samsung USB cable, a USB 2.0 port, and Odin 3.07.

(Sprint}Samsung Galaxy Tab 3 [SM-T217s]: Difficulty Installing RR with TWRP v2.7

Hello, the names Braadliiah,
I am having excessive difficulty figuring out how to flash any Rom that is beyond Kitkat, even though they, supposedly are "designed" for an "SM-T217s". As I had success flashing Cyanogen mod[cm-12.1-20160706-UNOFFICIAL-lt02ltespr], which is not even for my model of tablet, which is bizarre due to the fact that other ROM's of the same model do not successfully flash. The most recent custom Rom I had attempted to install with no avail, was the Ressurection Remix[[ROM][8.1.0]ResurrectionRemix v6.2.1[Official]]. This ROM was linked into google, under "SM-T217s" compatibility, but for the model "It02ltespr".
The way that I flash these ROM's are through TWRP, namely, version "2.7.0.0". The TWRP dialogue within the flash window, usually says something like, "failed to zip" and "Zip error". The reason I have not done the flashing via ADB & Fastboot is because I have not done this successfully yet, and truth be told, I am not sure it is even possible given the TWRP can't do it? Also, I do not use Odin, because this will remove TWRP, and there is no guaranty that the ROM will work, and then, I will have to re-install Stock Firmware and TWRP. I lack any desire doing double the work, as I have already done a bit of that through trial and error recently.
So is there any method, via TWRP, ADB, or ODIN, which will in fact work? Should I install another version of say, Cyanogenmod, to be able to install this ROM? I am looking for experienced, tech savvy people, as I am a curious noob, who wants a ressurected tablet that can do all modern conveniences via wifi, and be my study tab. Furthermore, I would like, say, Magisk Manager to Install Modules, but can not do so, without a newer Kernel, that is Lolipop and forward. And again, Lolipop and forward do not seem to Install.
I shall be ever greatful for anybody's help. Thank you. :angel:
Update:
Today I experimented with ODIN some more. I had a small victory, because I happened to take the TWRP v.3.1 flash Image, and converted him into a TAR file, and luckily ODIN managed to successfully install this update. However, when it came to TWRP v.3.2, there became an error installing. TWRP still failed to instal zip files from the below ROMs. Furthermore, ODIN seemed to flash the boot images of Custom ROMs well, when converted to TAR files. Yet, when I booted the ROM, this device remained on the Boot screen.
My process by which I installed these ROMs, went like so:
First, extract zip, then convert to TAR via 7zip
Open ODIN, flash TAR in PDA, Boot down android
Boot to Download Mode again, in PDA flash TWRP v3.1 TAR, Boot down android
Boot to Custom recovery, and install proper Gapps
Boot on, and Stuck.
I did this three times, while starting off with a full wipe, to rule some things out. When I tried to fix context, it said Error1
The Roms I attempted to flash were, Cyanogenmod 12, which worked entirely; Cyanogenmod 13 which was stuck on Boot screen, tried twice; Lineage OS 15, which I tried three times, and was stuck on Boot screen.
Do I need to apply more than one file? for instance, CSC, Phone, and PDA? Because I was only flashing boot Image as a TAR file in PDA.

Categories

Resources