Database Users

Issue resolved.

Edited to add:
This is no longer an issue. A replacement phone is being shipped. If there is a way that the moderators can delete this thread, thank you in advance.
Hi everyone,
I'm very new to this forum, and to doing anything root wise on a phone. Here's my situation:
I'm using a rooted LG P509 (Optimus T), and tried to install a theme meant for the Nexus One (kind of why I'm posting here for help). The theme used was obtained here, it's the Lucid theme. I tried to install the theme using the latest version of clockworkmod in the Android Market. Everything went well, or so it seems, and I was asked to reboot my phone. I allowed the phone to reboot and now it's stuck on the LG symbol. I've (1) taken the battery out, (2) placed it back into the phone, (3) pressed the home, volume down, and power keys at the same time to get to recovery mode, and that doesn't work.
I now know that themes meant for certain phones should be used for the intended device. At the time I figured because I used clockworkmod, that it would work despite the difference in hardware.
I'm wondering if there's a way to get my phone back to normal? Thank anyone in advanced for helping this noob.
---
I've also asked for help in the forum where the theme was obtained.

you need to flash a custom recovery via ADB or fastboot, then data wipe(factory reset) your phone and reflash whatever rom you were on. if maybe you can get a recovery or ADB working, then your phone will be fine. flashing a nexus one theme onto your Optimus T isnt one of the brightest ideas. i would never consider trying to flash a theme from another similar phone onto my nexus, let alone a completely different phone.

If you have questions about using adb, there's a couple of helpful stickies up, make sure you read everything, but its pretty straightforward. And as Simms said, bad idea trying to cross themes.

I'll read the threads on ADB. Thanks guys.

Were you using ROM Manager? Or flashing manually via flash_image? Otherwise I don't know what you mean by Clockworkmod in the Market.
I suspect your phone never even got as far as flashing the theme. If you tried to flash Clockworkmod recovery, that's enough to mess up your phone, because you probably flashed a version intended for completely different hardware.
Now that you've borked the recovery partition, you probably need to get it into some sort of "download mode" that can interface with LG's proprietary software for reflashing phones. This would all be best dealt with in the Optimus One (P500) forum.

cmstlist said:
Were you using ROM Manager? Or flashing manually via flash_image? Otherwise I don't know what you mean by Clockworkmod in the Market.
I suspect your phone never even got as far as flashing the theme. If you tried to flash Clockworkmod recovery, that's enough to mess up your phone, because you probably flashed a version intended for completely different hardware.
Now that you've borked the recovery partition, you probably need to get it into some sort of "download mode" that can interface with LG's proprietary software for reflashing phones. This would all be best dealt with in the Optimus One (P500) forum.
Click to expand...
Click to collapse
Clockworkmod should have an icon of a black hat with an orange cog for a head.
I did attempt to flash a theme intended for different hardware.
The several computers I've gone on haven't recognized the phone, and my attempts to place any file on the SD card proved futile. Since the phone is under warranty, I called the store I purchased it from, and they're going to ship a replacement.

The icon you describe is the icon I see for ROM Manager. Clockworkmod itself is not an app you can download from the market but rather a partition you flash that has to be written for the exact hardware. Unless there's something you saw in your Market that I can't see in mine.
From within ROM Manager you can flash Clockworkmod. But if you flashed a version of Clockworkmod meant for other hardware, I'm willing to bet *that* mangled your phone, regardless of what you attempted to use it for..
Anyway, glad you're getting a replacement.
Sent from my Nexus One using XDA App

Interesting, LG will let you replace the phone even though you've clearly rooted it and caused the problems? Of all people, I'm surprised LG lets you do that. You've stated that it's under warranty but what you done should've voided the warranty. You sure they're okay with replacing your phone like that?

[Q] gt-i9500 and kitkat custom roms incompatibility? HUH?

As the title says I have an International GT_I9500 unlocked
Until now I was always able to install any custom rom I wanted , no problem, just wipe and install and away we went.
Now with KitKat, I AM COMPLETELY UNABLE TO INSTALL ANY OF THE CUSTOM ROMS FOR 4.4.2 -0 NONE WORKS. I can't believe i am jinxed.
I wiped everything, cache, dalvik, system and internal and also did a full wipe - NOTHING WORKED, There are 3 custom roms for 4.4.2 so far and NONE = NOT A SINGLE ONE WANTS TO INSTALL.
I downloaded one of Samsung original 4.4.2 firmware and using Odin I WAS ABLE TO INSTALL AND MAKE IT WORK, yet after doing this, I tried to install any of the 3 customs roms and BOOM, COMPLETE FAILURE
Can anyone help PLEASE GUYS, I feel like BROOMHILDA LONE PERSON WITH A CLOUD ONLY ON MY HEAD
I am curious as to why this is happening

maybe its a i9505 or i9506 rom

provide the Odin messages here.

custom roms failure, huh?
spamtrash said:
provide the Odin messages here.
Click to expand...
Click to collapse
I loaded the custom roms via recovery, not via odin,
so i go into recovery mode via TeamWin, wipe everything and load the custom rom, message says "successful" and i reboot system, that's it
the phone hangs into one of the boot animations and never finishes, left it for longer than 30 minutes, all of them , nothing loads.
go back the same custom roms but with android 4.3 and first shot, loads fine, all of them, same ones that won't load the 4.4.2 load the 4.3
most custom roms load via recovery not odin -
last try was load samsung original firmware 4.4.2 via download Odin, then root then install teamwin recovery. - worked fine
now removed it and reinstalled Thor 4.3 (thor 4.4.2 doesn't work) but tomorrow i'll wipe it and reinstall the samsung 4.4.2 unless you have an idea
*i hope)
sorry about the capitals - NO IT IS AN EXYNOS UNLOCKED GT-I9500 - almost a year after playing with nova settings, xposed and about a dozen custom roms, i THINK i know it's a 9500 - skip the silly suggestions - we're all noobs but not necessarily all boobs
thanks for your help - appreciated if we can solve it

custom roms failure, huh?
KingOfDope said:
maybe its a i9505 or i9506 rom
Click to expand...
Click to collapse
roms were downloaded exclusively from GT=I9500 AREA -
i don't go anywhere else because i know beforehand that they won't work - so why bother
thanks for your suggestion but obviously out of context - i don't live in the US in addition

Maybe wrong recovery ¿?

funny 4.4.2 roms
robertostorm said:
Maybe wrong recovery ¿?
Click to expand...
Click to collapse
i usually use teamwin version 2.6.3
and funny thing in one of the wipes even the teamwin was wiped so i wound using the regular android recovery, with the tiny tiny blue characters
that doesn't have all the teamwin recovery options - so even then it failed
after installing the saunsung 4.4.2 i downloaded a fresh teamwin version and installed via odin/download - like starting from zero. guess what
nope even then the roms freeze at the bootanimation - but the joke is ONLY IF THEY ARE VERSIONS 4.4.2 -they work fine with version 4.3
and when i mean wipe i mean wipe - cache/dalvik/system/internal - and even the other option where you have to type YES for the wipe to go on.
short of reformating the whole memory which i think is excessive, i THINK i tried with a clean clean memory install (according to me)
thanks for your patience
btw most of the custom roms install via recovery so there's no way to get a download install version

exlaval said:
i usually use teamwin version 2.6.3
and funny thing in one of the wipes even the teamwin was wiped so i wound using the regular android recovery, with the tiny tiny blue characters
that doesn't have all the teamwin recovery options - so even then it failed
after installing the saunsung 4.4.2 i downloaded a fresh teamwin version and installed via odin/download - like starting from zero. guess what
nope even then the roms freeze at the bootanimation - but the joke is ONLY IF THEY ARE VERSIONS 4.4.2 -they work fine with version 4.3
and when i mean wipe i mean wipe - cache/dalvik/system/internal - and even the other option where you have to type YES for the wipe to go on.
short of reformating the whole memory which i think is excessive, i THINK i tried with a clean clean memory install (according to me)
thanks for your patience
btw most of the custom roms install via recovery so there's no way to get a download install version
Click to expand...
Click to collapse
Once you flashed stock 4.4.2, your bootloader gets updated, so you can only use 4.4+ roms, also TWRP is full of bugs, just use cwm 6.0.4.5 and you're set.
Also, did you root the stock 4.4.2?

custom roms failure, huh?
robertostorm said:
Once you flashed stock 4.4.2, your bootloader gets updated, so you can only use 4.4+ roms, also TWRP is full of bugs, just use cwm 6.0.4.5 and you're set.
Also, did you root the stock 4.4.2?
Click to expand...
Click to collapse
as i said in a previous message - i used odin in download mode and flashed an original samsung 4.4.2 and it worked, i rooted and reinstalled teamwin
AFTER ALL THIS I tried to install one of the 4.4.2 custom roms - IT FAILED CONSISTENTLY - BY THIS I MEAN ALL ROMS DIED AT BOOTANIMATIONS - AND ALL FAILED TO START
thanks so much

Try with latest Philz recovery or any up to date CWM recovery.
And when coming from stock, you generally have to FULL wipe you phone

custom roms failure, huh?
ayedarts said:
Try with latest Philz recovery or any up to date CWM recovery.
And when coming from stock, you generally have to FULL wipe you phone
Click to expand...
Click to collapse
just downloaded cwm version 6.0.4.6 installed via recovery. launched recovery installed latest wanamlite for 4.4.2 - message was "installed successfully" please reboot
i rebooted and for the last 15 minutes all i have is a BIG SAMSUNG on the screen - nothing beyond
just another hitch with kitkat - i have a SONY XPERIA Z TABLET with wifi and sim - a couple of weeks ago i rooted it but the cwm version is not good because it's on the vertical side and you cannot see the bottom of the menu so it's useless - anyhow. i rooted it and left it at that.
i got notice from sony that a new os version (kitkat) was ready for install - so I just told the tablet to start - and the os install screwed the tablet,
there was no way to reload and it completely deleted the memory , it went to sony to reload - so i have a big hunch there is something not right somewhere -
anyway the phone still has the SAMSUNG and it ain't going anywhere while i am writing all this
very discouraging = sure as heck i ain't buying no more galaxys of any sort, i was ready to preorder the s5 at 455british pound, unlocked - but since this i am dropping samsung, i like very very much the xperia tablet it's faster than the s4 so perhaps i'll jump to the sony xperia fone and bbye korea

maybe i9505 rom

custom roms failure, huh?
i know you're trying to help - but if you read all the previous (long and boring) messages - there's no mistakes, there's no 9505
ALL THE ROMS I DOWNLOAD AND USE - ALL OF THEM WITHOUT EXCEPTION come for the i9500 development area, I DON'T BOTHER WITH
9505 - MOSTLY BECAUSE I DON'T HAVE A 9505
UPDATE - today after loading the latest cwm recovery i got lucky to be able to load ONE - READ IT - ONE CUSTOM ROM ( rom from HASAN)
this is the very only that i got to work, the other two just refuse to finish the boot - i don't know where they freeze.
even the wanamlite custom rom for 4.4.2 freezes - this is really annoying and a puzzle - this is my fourth samsung fone and never ever did i
find the bug that freeze everything. I hope that some of the other developers will come up with new kitkat versions for the 9500 and see if the bug persists or not -
any help will absolutely be appreciated, guys, some sort of boot log that can help pinpoint,
thanks again

You know the fact you keep using capital letters (so you might be trying to scream) is a little annoying.
I have a Samsung Galaxy S4 GT-I9500. I live in Costa Rica (so not in the US obviously).
I installed stock 4.4.2 using ODIN, then flashed ROOT and finally installed a custom CWM. First I tried Philz and ended up with 6.0.4.6.
I have already tried 2 different custom ROM's but I didn't like them so I went back to stock. I am very satisfied with the performance of my phone with stock, but that's not the point.
The thing is that I have the same phone you have, i installed the same software you installed, I followed the same steps you have followed yet I am able to install any custom ROM i like.
Maybe it is your phone, or maybe you're just looking for an excuse to quit Samsung and you're simply blaming kitkat your inability of installing ROMs now.
I'm just saying... there are several options you can tried if you quit being angry and actually try them.
Personally, I would start from scratch. Flashing via ODIN again, rooting accordingly with the right files, using a recovery that is recognized to work with 4.4.2, and finally using the right custom ROM.

custom roms failure, huh?
pinktheater said:
You know the fact you keep using capital letters (so you might be trying to scream) is a little annoying.
I have a Samsung Galaxy S4 GT-I9500. I live in Costa Rica (so not in the US obviously).
I installed stock 4.4.2 using ODIN, then flashed ROOT and finally installed a custom CWM. First I tried Philz and ended up with 6.0.4.6.
I have already tried 2 different custom ROM's but I didn't like them so I went back to stock. I am very satisfied with the performance of my phone with stock, but that's not the point.
The thing is that I have the same phone you have, i installed the same software you installed, I followed the same steps you have followed yet I am able to install any custom ROM i like.
Maybe it is your phone, or maybe you're just looking for an excuse to quit Samsung and you're simply blaming kitkat your inability of installing ROMs now.
I'm just saying... there are several options you can tried if you quit being angry and actually try them.
Personally, I would start from scratch. Flashing via ODIN again, rooting accordingly with the right files, using a recovery that is recognized to work with 4.4.2, and finally using the right custom ROM.
Click to expand...
Click to collapse
-------------------------------------------------------
First - The capitals I used were ONLY to emphasize certain aspects and not intended as screaming, which is the usual sense - That was not my intention,
Second - I have being using Samsung for the last 7 years, I was not intending to leave until I hit this brick and further I nearly went to Clove, UK (where I usually pre-ordered my last 3 Galaxy's - months ahead of delivery) so thumping me by saying I am looking for an excuse to dump Samsung, is way off base, so much so, that if that indeed was my intention, why for all heavens would i bother to find a solution, and waste so much time and effort to make it work
Third - I have being as polite as any person can be, with or without, this hitch, don't judge, about being angry or not, you don't know me well enough to know the difference, just stick to the point in question without getting personal.
Fourth - What I have described is EXACTLY to a tee what is happening to me, what happened to YOU , is IRRELEVANT, you may be one of the lucky ones who has no issues installing the roms in questions. so unless you do have a suggestion as to finding the reason the fone loops on boot, skip what you did or didn't do, they are IRRELEVANT, because they don't provide a solution.
Fifth - If you read my descriptions you will notice the many times I installed customs roms on the many galaxy's and Note's I have/had.That ought to clue you that i know a basic way on how to do the installations (Odin, recovery, teamwin. cmw,) you name it I've done it, and i've unbricked more than once my fones. so yes i do know how to use Odin
Sixth - For some reason I was able to install the "HASSAN" rom (the ONLY and ONLY) 4.4.2 custom that worked. the others they just won't, PERIOD
So if you have a technical solution as to how to get a log of the looping so we can tell exactly at what point the fone loops. or some other technical solutions, please let me know them asap I am dying to see my fone with a custom 4.4.2,
Seventh - Yes I am extremely disappointed that the S5 is just not fantastic enough to lay 455GBP to pre-order. there are a few more advances but it is "ALMOST" good = the bezel didn't disappear - the 2K display isn't there - the sharper casing is still missing - the better battery is still not there - the wireless charging - To have 2000 horse power engine under the hood of a beat up VW beatle. doesn't make you good looking enough to go cruising on a saturday nite and brag about your "car" -
BTW = I am absolutely no fan of the Iphone (yuk) nor of Sony (which is as restricted as apple)
Can you help solve my issue - thanks

Bricked Tegra Note 7

EVGA Tegra Note 7
4.3 jelly Bean
Used the Super Tool to flash drivers and unlock bootloader.
Installed TWRP Recovery
Rooted using SU
Everything is working great, at this point.
Failed to back anything up
Flashed Shaky's custom Kernal and I couldn't get past the tegra note 7 screen. - at this point I probably could have saved it but doing anything other than what happens next.
Flashed 4.4 stock Rom which has to have reset the Recovery and Debugging is now off.
Do not do what I did. Brick. Any ideas? I can still get into bootloader which is unlocked but my computer no longer recognizes it. Pretty much lost hope on this one. Surprise me if you feel inclined.

I've been trying to sideload via externalSD, the stock 4.3 ROM from the "Tegra Note Discoveries" thread. It actually gets halfway though installation then fails for reasons I can't begin to understand. Most likely because it's rooted and I'm flashing a stock rom. If anyone can find a way to flash the stock Kernel and 4.3 rom I would be grateful.

share_needles said:
I've been trying to sideload via externalSD, the stock 4.3 ROM from the "Tegra Note Discoveries" thread. It actually gets halfway though installation then fails for reasons I can't begin to understand. Most likely because it's rooted and I'm flashing a stock rom. If anyone can find a way to flash the stock Kernel and 4.3 rom I would be grateful.
Click to expand...
Click to collapse
In the recovery environment , ..... you are inside the ram disk of, whatever recovery you are running and root status of your system ROM doesnt matter .
Since from the 1st post you have recovered it to the point where you can access the recovery, I think its just matter of getting the correct backup re-installed.
You can request someone with same Branding ( there are 6-7 avent, XOLO etc ) to upload their cwm backup ( minus data, cache ).
Lack of developer / geeky user community is what you get when companies lock their bootloader under disguise of Warranty n stuff.
I havnt been able to gather the courage to play with TN7 like i do with my Nexus7, nexus 4 and Xperia J . ( XJ has some great XDA community btw even after closed BL)

kapil.git said:
In the recovery environment , ..... you are inside the ram disk of, whatever recovery you are running and root status of your system ROM doesnt matter .
Since from the 1st post you have recovered it to the point where you can access the recovery, I think its just matter of getting the correct backup re-installed.
You can request someone with same Branding ( there are 6-7 avent, XOLO etc ) to upload their cwm backup ( minus data, cache ).
Lack of developer / geeky user community is what you get when companies lock their bootloader under disguise of Warranty n stuff.
I havnt been able to gather the courage to play with TN7 like i do with my Nexus7, nexus 4 and Xperia J . ( XJ has some great XDA community btw even after closed BL)
Click to expand...
Click to collapse
Yea I jumped in the deep end without doing enough research. I have rooted and installed custom ROMs on my android phone without issue but I've never messed around with kernals or had to dig myself out of a device stuck in boot-mode. Instead of learning about a device then modding it, I forced a situation where I modded now need to learn how to fix it.
As novice as I am, still working on getting the correct drivers installed to sideload a backup. My computer will not recognize the ADB device in the stock bootloader but when I boot into recovery it does recognize it so there is definitely a driver issue there.

By kapil.git
You can request someone with same Branding ( there are 6-7 avent, XOLO etc ) to upload their cwm backup ( minus data, cache ).
Click to expand...
Click to collapse
I think more like a dozen brands of TN7.
You should at least tell your brand, would make it less mysterious.
Advent has a stock 4.3 install install via APX mode (although you seem to be only able to use it once, then it locks
the nvflash stuff).

I apologize I have the EVGA Tegra Note.

share_needles said:
I apologize I have the EVGA Tegra Note.
Click to expand...
Click to collapse
you are lucky ... this thread has many posts of the same branding EVGA..
Top posts & stickies also have a AIO post about recovering a unlocked BL device.. download and do it OP.

Hi Guys. Tablet is working fine now. I used multiple files from multiple sources to get this going. Here were the commands to get me back to stock. Obviously there was a lot of playing with commands etc that I cut out. I truly believe this device is unbrickable. I was just stuck in a bootloop.
in short, the issue was with the boot after a kernel flash. The TWRP recovery was flashed back to stock.
Got the drives from SDK download because I'm not slick enough to be able to do it myself.
In fastboot, make sure you have the fastboot file in the folder with your boot.img , recovery.img
fastboot boot boot.img ----got me out of the bootloop temporarily without flashing anything unnecessary
fastboot flash boot.img, flashed the boot.img from Vega Note 7 source files that are out there, I recommend every download those now.
fastboot boot TWRP_recover.img -----messing around be led me in a good direction
From there, I installed the below file from XDA User e8hffff
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
I believe that was a full backup of a 4.3 Evga Tegra Note 7 stock. This really helped me out a lot.
Thanks everyone for the help. You can see by the very few command that got this device up and running I am a total noob but I'm figuring it out little by little.
If anyone is in a similar circumstance in the future send me a PM and I may be able to assist you.

[Q] ANNOYING S4!! Help needed

Ok guys, here's the deal. i bought a secondhand s4 which was advertised as a google edition. it has a couple of annoying issues, first i noticed it switching itself off and on. the worst problem with it is that when my battery goes reeeally dead it just bootloops when i have recharged. the only way i can get it back on is to start it in recovery mode (which is clockworkmod v6.0.4.4) then do a factory wipe. so yeah thats a major pain. the s4 itself is a red model and behind the battery it says its a gt-19505, however in the settings on the phone it says its a gt-19505g.
my goal is to install an official firmware if possible that i may be able to update easily, the worry that i have is that i dont know if it would then accept my network as although it appears to run google edition custom firmware it may not once i install something official on it. this may be a nooby statement i know but a noob i am lol.
if its at all possible could i keep the cwm recovery?
and if its any help when i load the other boot loader thingy (with the green android on it) in the top left it says gt-19505, im just sayin cus im sure its vital which ever this phone actually is.
here are as many details as i can give but please ask if im missing anything
ANDROID VERSION 4.4.2
KERNEL VERSION 3.4.0-faux123-KK44-GE-Custom
[email protected]omain #20
Sun Dec 1 02:30:28 CST 2013
BASEBAND VERSION 19505XXUFNA1
BUILD NUMBER KOT49H.S001.131204
also upon booting in the top left it says "kernel is not seandroid enforcing
set warranty bit:kernel"
THANKS FOR YOUR TIME And please tell me where to start as i tried updating it via kies to fix it but it just wont connect, i assume due to custom firmware.

The Google Play Edition S4 devices didn't come in any color but white. Therefore, this is an I9505 with a custom ROM on it. The download mode screen reading GT-I9505 confirmed it.
Since this is an I9505 and not an I9505G, the main question is whether this device will work with your SIM card. For that, simply insert your SIM card and boot the device. If you get signal, you're good. Otherwise you'll have to unlock the device, either by purchasing an unlock code from one of the sites that sells them, or by trying the unlock methods available on the forums.
This will also help answer the question of which stock ROM you can install on the device. If the S4 doesn't prompt you to unlock the device, then you can install one of the unbranded S4 ROMs available on sammobile.com. After that, you can put the recovery of your choice on the S4, though I recommend TWRP over the other options.

Thanks for your help. I'm a little confused though, at the moment with this custom google edition ROM it does take my sim, in fact I bet it takes any sim, I heard that was a feature of google play devices. What I meant was after I install the stock ROM will it then not take my sim. So if it has already been unlocked How would I know which ROM to install? As I now know its not a google edition, is it possible to install an official google edition ROM? Do i use this download mode, Odin, or cwm to install a firmware. I'm just not sure what my starting point is. I don't wanna follow someone's guide yet to installing something just in case I'm jumping the gun and need to uninstall this custom ROM somehow.
Sorry for asking questions that I'm sure seem dumb I'm really just trying to learn at the moment I'm green as they come with android. BTW thanks for your suggestions so far, you def seem like you know what you're talking about, cheers

Google Play devices are carrier unlocked, but this is not a Google Play Edition S4. Therefore the device was carrier unlocked at some point in its past. The unknown here is how the original owner unlocked the device. If he or she used the unlocking methods found on XDA there is a chance the lock will be lost when installing a stock ROM.
If the S4 is unlocked, you aren't restricted to a particular region and can install any I9505 ROM using Odin, though I recommend the carrier unbranded ROMs. You cannot install a stock Google Play Edition ROM on the device as the model number of a GPE device is not the same as the device you have. However, you're already rooted and have a custom recovery installed. In I9505 Development here on XDA there is a Google Play Edition ROM that can be installed on your device. Download it to your S4, wipe everything in recovery, then flash the ROM's flashable zip in recovery. I've used said ROM and it works quite well.

OK I have found the 5.0.1 ge ROM , but in there it says I must use latest recovery or whatever plus it recommended one different to mine, is it safe to install using my version of cwm or do I need to learn how to change it??

Deleted by user

TWRP is recommended as there are people who are still maintaining it, unlike Clockworkmod and Philz. While you probably can get the ROM installed using the version of Clockworkmod you have, learning how to change recoveries is useful.

OK thank you for all your help my friend, I will now find out how to do this, I'm sure there is a section on this somewhere, BTW I think you are right about my device being rooted, but I wanted to check and I followed a guide and used super su but apparently its not rooted so I guess something must've gone wrong. Bit scary if I try to change my recovery or my firmware and this causes a brick hmmmmm

It's virtually impossible to brick the S4, especially as the recovery is flashed through Odin.

Phew that's a relief. Thanks man.... Well I'm gonna just risk using cwm for now as I'm new to this........ Thanks a whole lot for your time I really mean that.

KlLLFRENZY said:
Phew that's a relief. Thanks man.... Well I'm gonna just risk using cwm for now as I'm new to this........ Thanks a whole lot for your time I really mean that.
Click to expand...
Click to collapse
Use TWRP. CMW is outdated.

Lennyz1988 said:
Use TWRP. CMW is outdated.
Click to expand...
Click to collapse
I want to, I really do but I'm struggling here. Before I wrote that last comment I tried to find a guide on this forum for swapping to twrp, but couldn't and didn't wanna bug this guy as he had helped enough. Anyway I went to the place he told me and have hit another wall anyway because I don't know how to use the firmware the relevant kernel or the git. My life is so busy and I'm getting about an hour on this subject a day and its gonna take forever lol
If you can help me on my way even a little its much appreciated, I would like to use twrp and the 5.0.1 ge plus the right kernel of course

KlLLFRENZY said:
I want to, I really do but I'm struggling here. Before I wrote that last comment I tried to find a guide on this forum for swapping to twrp, but couldn't and didn't wanna bug this guy as he had helped enough. Anyway I went to the place he told me and have hit another wall anyway because I don't know how to use the firmware the relevant kernel or the git. My life is so busy and I'm getting about an hour on this subject a day and its gonna take forever lol
If you can help me on my way even a little its much appreciated, I would like to use twrp and the 5.0.1 ge plus the right kernel of course
Click to expand...
Click to collapse
https://twrp.me/devices/samsunggalaxys4internationalqualcomm.html
Follow the Odin guide. It's excactly the same when you flashed CWM.

@Lennyz1988: The S4 was bought secondhand and already had CWM on it from the original owner.
@killfrenzy: Follow the guide Lenny mentioned, but don't worry about the second paragraph. Our device isn't one of those that restores the original recovery on boot.

ok will do, i just tried the app install method but as i suspected, it said root is required for this app and promptly exited so i shall do the odin method, i heard that some people remove root or it could be that it was done wrong. also after reading a few posts here and there i found out that someone had similar issues with their phone random re-booting and they had custom ge with the wrong kernel so it seems once im done my issues should be history if i learn how to install fw + kernel, after this twrp thing i will be one step closer for sure. i also know ppl slate lollipop but once im all done with this im sure i will have picked up enough terminology to install cfw's to my hearts content. hooray for forums and people like you, sounds like im kissin ass but its just gratitude

so using the twrp install guide i gotta install using the odin method i have now got 3.07 odin but this is the next step.........
Odin Install Method (No Root Required):
You will need to download and install Odin on your PC. Once you have Odin installed, download the proper .tar file for your device from the download link above. Power off your device. Turn on your device using the proper key combo to get into download mode and attach the device to your computer via a USB cable. Use the PDA tab or button to browse to and select the tar file that you downloaded and flash the device.
lololol nothins ever simple i see the list of tar files in the link above but no mention at all as to which is the proper .tar for my device, i guess they assume the guide is for people who have done it before. more research tomorrow maybe i gotta be up early ugh

Lennyz1988 said:
https://twrp.me/devices/samsunggalaxys4internationalqualcomm.html
Follow the Odin guide. It's excactly the same when you flashed CWM.
Click to expand...
Click to collapse
Think you misunderstood, I have flashed nothing yet I got it like this. I'm completely green

Don't suppose anybody knows which is the tar file for my device?? S4gt-19505

OK now I get it, the list of tars in that section are all the same just newer builds of the same version. Seems obvious if you have done this before, but I wasn't to know that and cannot assume things. I'm also gonna guess and say Lenny thinks my s4 needs this particular version for an international, am I right?? Anyway it would've made a lot of sense but how does he know. I have no idea what this phone was I have never owned it new.

Different devices have different codes. For example, jfltexx is the I9505. A T-Mobile S4 would be jfltetmo, and so on.The link Lenny provided is for the I9505. Download the 2.8.6.0 version as its the latest.
As to how you were supposed to know, having never owned one, you weren't. There are tutorials in the General forum though that can help.

I need your Galaxy On5 (USA) ROM

Hi, I need the ROM for this phone, more specifically, the boot.img file, as the current kernel is for the older, Indian revision of the On5, and my revision, the USA version SM-G550T1, seems not to have any copies of its firmware floating around. I'm running an OS for the SM-G550FY, which has no audio or camera support. Even if the version isn't an exact match, if you bought this phone in the USA, new, in 2016, your boot.img will probably work. I need this kernel guys. Please, if someone has an On5 in the USA, can I please get a copy of your boot.img and possibly system.img? I really care about the boot.img.
Thanks guys
-Subsentient

Firstly, did you try the updated ones at these locations:
http://www.theandroidsoul.com/galaxy-on5-stock-firmware-2-86761/
http://firmwarefile.com/samsung-sm-g550fy
Secondly, why exactly do you need the boot.img, what problem do you think it'll solve? Is there any specific issue with your current ROM that you are trying to solve?

Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.

Subsentient said:
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Click to expand...
Click to collapse
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).

prahladyeri said:
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.

Subsentient said:
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Click to expand...
Click to collapse
There you are! I just cannot emphasize enough that why don't you guys backup your existing ROMs before flashing a new one? It hardly takes five minutes with CWM/TWRP recovery.
In any case, what happens when you flash the Indian ROM (5.1.1)? I guess that could be your only option.
Otherwise, you can put a request on the CyanogenMod thread for your particular Samsung model.
For future reference, perform device backups and all the research before flashing a custom ROM, not after the fact.
EDIT
If you can contact Samsung support, see if you can manage to get a stock ROM from them that you can flash using ODIN or something.

I contacted them already, they basically told me to go **** myself. The missing ROM is a result of bad parameters I accidentally put in to Heimdall/ODIN flasher. I wanted to back up, but ironically, my first attempt at installing TWRP is what destroyed my ROM.

I've downloaded the kernel source code from Samsung and I'll try compiling it myself. If I create a working boot.img, I'll post it here.

prahladyeri said:
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
boot.img is where the kernel is stored. I know, I decompressed it.

Subsentient said:
boot.img is where the kernel is stored. I know, I decompressed it.
Click to expand...
Click to collapse
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.

prahladyeri said:
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
Click to expand...
Click to collapse
The kernel on this device does not have loadable module support. It's entirely monolithic. And, I'm having one hell of a time building a kernel this thing is willing to boot.
I really would love just to get a ROM from someone else's SM-G550T or SM-G550T1.

locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know

bandtab said:
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
Click to expand...
Click to collapse
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.

Subsentient said:
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Click to expand...
Click to collapse
thank you!
however, i can't install twrp to my recovery partition anymore because i got FRP locked, and i can't go into my settings to disable it now. so i think my only option really is via odin. i'll see what i can do with this though, thank you very much. i did have twrp on there before but after i got frp locked i can't go into recovery mode at all.

I've been losing my mind trying to make this work.
I think if I installed the stock recovery.img it may work, but I can't find it in the files you sent. Would you or anyone else be able to make a copy of it for me? I would be eternally indebted to whoever could.

If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.

holydude92 said:
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
Click to expand...
Click to collapse
unfortunately smart switch is incompatible with this model phone for the time being.

I got four of these from T-Mobile when we switched from Verizon ($120 for 4 lines). Three of our Verizon phones worked well on T-Mobile (after a few APN tweaks), but my dad's old Galaxy S3 barely worked at all, and when it did, only got Edge for data. So I set one of the On5 phones up for him.
Everything was going great. I put the TWRP recovery on it, rooted it, froze all the bloatware, and backed up/restored his apps from the old S3. However, he wanted me to see if I could restore all his SMS/MMS. I tried restoring that, and the stock Messaging app started FC'ing. I installed Textra, which worked (and saw the old messages), but he never received new texts (even though he could send). So I tried removing Messaging and Textra, as well as the SMS cache (which seemed to be in "Dialer Storage (Phone SMS/MMS). I removed it, but now I'm getting an error every five seconds about "com.android.phone" and can't seem to get rid of it. I tried to restore the dialer storage backup again, but it just seems to sit forever without installing.
I've looked far and wide for a stock ROM... hoping I could just put this mess behind me, but I'm surprised to find it is nowhere to be found.
My other alternative would be to fix the com.android.phone error, but nothing seems to fix it.

Which cynogenmod or any custom os suits for Samsung Galaxy on 5.......please tell me guys.....I am bored with this official os

I was really hoping to come back to this forum and finally see stock ODIN files for this phone. I really, really want to get rid of the MetroPCS ROM I used to fix it.
Has anyone been able to find it?