Database Info

[Q] Working on ICS...

Hello people,
This is my first post here, so I hope I am putting this in the right place. If not, sorry, please move it.
Anyway, as you all are aware, ICS source code was released a couple days ago, so I decided that I would see if I could begin constructing a ROM based off AOSP for the G2x.
As predicted, it did not go well. I pulled the build makefiles and the like from CyanogenMod (hope that's okay), and tried to use those as device-specific build instructions. I got everything to compile with no errors, and the ROM successfully installed, but does not boot.
Best I can tell, the phone gets through the kernel boot alright, but halts at the "A N D R O I D" screen (no boot animation file is included). The touch panel seems to be responsive.
Does anyone have any suggestions as to what might be wrong? Any help is greatly appreciated.

nerdman said:
Hello people,
This is my first post here, so I hope I am putting this in the right place. If not, sorry, please move it.
Anyway, as you all are aware, ICS source code was released a couple days ago, so I decided that I would see if I could begin constructing a ROM based off AOSP for the G2x.
As predicted, it did not go well. I pulled the build makefiles and the like from CyanogenMod (hope that's okay), and tried to use those as device-specific build instructions. I got everything to compile with no errors, and the ROM successfully installed, but does not boot.
Best I can tell, the phone gets through the kernel boot alright, but halts at the "A N D R O I D" screen (no boot animation file is included). The touch panel seems to be responsive.
Does anyone have any suggestions as to what might be wrong? Any help is greatly appreciated.
Click to expand...
Click to collapse
I think there were two other devs in this thread trying to get ICS up and running as well. They could probably help.
http://forum.xda-developers.com/showthread.php?t=1309620&page=3

Thanks for the link. I am working on changing the init.rc as per one particular post. I'll see if that works.

nerdman said:
Thanks for the link. I am working on changing the init.rc as per one particular post. I'll see if that works.
Click to expand...
Click to collapse
We have 3 people working on it... your assistance would be of great help

Okay, so I tested the idea of changing the bootclasspath in init.rc, and it didn't seem to be helping much. In fact, it may have hindered things. Before the modifications, the phone would finish going through the two lg splash screens. Now, it hangs on the second. Suspect bad merge of ramdisk and kernel. But as for now, sleep is calling. I will work on it more tomorrow.
And I'm glad I can be of help. If you would like, I could throw what I have on megaupload, see if what I have is valuable.

You don't have ICS built device drivers and the kernel needs to be built for ICS. If you do not get it to boot nothing will work except maybe the touchscreen if you are lucky.

Right. Device drivers. But we were able to port Gingerbread to this device with Froyo drivers, yes? What about compiling the ICS kernel source (if it is out) for the G2x. Would that yield any kind of results?

nerdman said:
Right. Device drivers. But we were able to port Gingerbread to this device with Froyo drivers, yes? What about compiling the ICS kernel source (if it is out) for the G2x. Would that yield any kind of results?
Click to expand...
Click to collapse
This is sounding a lot like the Hackintosh driver hacks, which I've done, to get the Mac OS to run on PC hardware of various kinds. In that world, drivers from previous iterations and versions of the Mac OS are merged into the Mac OS to enable various PC hardware which Apple didn't support in the new OS version. One example is the video drivers which Apple supplies for very few video cards but have been hacked to run other, non-supported video cards. As well, Apple is notorious because it orphans perfectly useable and upgradeable Apple Mac hardware by not providing video drivers for it in new releases of the Mac OS. When Mac OS 10.7 was released some people used the Mac OS 10.6 hacked and/or unhacked video drivers and hacked video drivers for OS 10.7 to keep their PC display hardware working. Keep trying.

Got the kernel source. I'll start messing around with it today.

[Q] Complete flashing noob help

Hello all,
I've been lurking the XDA forums for a couple months now. I had a couple posts in the past referring to my phone and my girlfriends phone and was looking for help mainly with hers at the time... Hers is fixed... Perfectly even, despite her phone being a total piece of garbage (an LG Optimus.... *barf*).
I have a SGH-T959V.
I have read the 10 commandments.
I KNOW my phone is NOT a Vibrant OR an i900.
I have read the noob guides.
I have become completely confused.
Here's my details:
I have running the stock GB that I installed with Kies Mini some time ago.
Phone Data:
Firmware Version: 2.3.6
Baseband Version: T959VUVKJ6
Kernel Version: 2.6.35.7-T959VUVKJ6-CL694130
Build Number: GINGERBREAD.VUVKJ6
I rooted my phone with one of the one-click apps after the stock GB update so that I was at least able to overclock it and get rid of the T-Mobile bloatware, etc.
I notice that my phone reboots entirely on it's own completely randomly, has random application hangs, all the bad icky stuff that sucks... (right????)
Anyways, I've looked at some of the Custom ROMs available and I'd like to check out some of them, but I'll be quite honest, I've read the instructions for how to do it, but I'm getting extremely confused as the current instructions seem rather daunting.... It's like information overload...
Now, don't get me wrong, I'm not some kid that really doesn't know what he's doing... I'm 33 and work in IT for The Nielsen Group... so I kinda know what the heck I'm doing MOST of the time. This is something I'm unfamiliar with and am being EXTREMELY cautious about because i don't want to brick my phone....
Question time!:
1. Is there a COMPLETELY SIMPLE step-by-step process/Video Demonstration for the CORRECT method of how to put a custom rom on the SGH-T959V?
2. Does it matter that I ALREADY rooted my phone in respect to me loading a custom rom? (ie. is my already rooted phone going to have issues loading a different rom?)
3. I would like to stay with a GB based rom unless there is absolute NEED to use a Froyo based Rom - Or is this a non-point when using custom roms?
4. If i want to load a custom rom to my phone, do I need to use a specific loader? (Like, does Odin work for everything??? Loading roms and unbricking your phone? Or do I have to have different loaders for the specific roms that I want to load and try out????)
5. Please don't jump down my throat with the "read the guide" responses... I HAVE been... really. As many as I've found... and every time I read a new one, rather than feeling like I'm coming out of the darkness of knowledge and into the light of understanding the correct process for how to do this, I feel like I'm being cast deeper down the confusion pit.
Would someone KINDLY please help me. Really... I don't want to screw up this thing... I'm not worried about the warranty. From what I've read, these things are mostly fixable unless it's an actual hardware issue or if it's totally fried. I just want to do it once, do it right, move on to my next project.... Dig?

First and foremost, we keep the most updated information in the wiki:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G
We've been updating it a lot lately so you're better off checking there. I'm sure you'll wanna bookmark it since you know what you're doing already.
1) Specifically you'll want to look at this section:http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G#Installing_a_ROM
2) If you're using Odin/Heimdall you won't need to be rooted since this bypasses the phone's OS and flashes firmware directly to the phone which may or may not be pre-rooted. The only Odin 2.3.6 KJ6 rom that's out right now does NOT come with root though, it's just the stock version you're already running.
3) For our phone you're either going to use Odin/Heimdall (learn Heimdall, it's much more useful) and CWM Recovery. Most roms available right now are for CWM.
Here's the list of custom GB roms:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G_ROMs
4) Honestly the forums are too cluttered and as I stated above, knowledgeable senior members are the ones who update the wiki, so that'll be your most useful resource.
If you already have some experience with computers I'll gladly help you, you're already asking the right questions.

Please use the Q&A Forum for questions Thanks
Moving to Q&A

FBis251 said:
First and foremost,
...
2) If you're using Odin/Heimdall you won't need to be rooted since this bypasses the phone's OS and flashes firmware directly to the phone which may or may not be pre-rooted. The only Odin 2.3.6 KJ6 rom that's out right now does NOT come with root though, it's just the stock version you're already running...
Click to expand...
Click to collapse
When I last played with my phone, I had used Odin on Windows... I have replaced Windows with Linux... I have installed Heimdall and did an initial test. So it is working.
My question is: Is Heimdall a valid replacement for Odin? In other words, I am wanting to use your guide, but it only refers to Odin. Can I go through those steps replacing Odin with Hamdall?

Yes it should work fine. The csc files for kc1 should be extracted over the pda files though
Sent from my SGH-T959V using XDA App

FBis251,
Thank you so much for the quick reply! I had seen it immediately after you responded, but was driving home from work and went right to bed. I'm back at the office now for the evening and perhaps may have some time to look into these tonight... I don't know as of right now.
If you are serious about the offer of some assistance, I would be more than open to it if I honestly felt it was needed. I am MORE than experiences with computers, i'm a full on uber-geek (just not with smartphones...... yet....), so VNC, etc would not be an issue.
I will most certainly get back to you about this in the next few days (perhaps even tonight). Let me see how my work load looks this evening and I will update the thread later.
Thank you again so much!

I'm usually in #teamnerd on freenode if you do IRC.

It doesn't take much to confuse me these days...
Moved my issue into a new question in the Q&A forum...

Hey, just an FYI (even tho I'm sure that ultimately you don't really care - just being realistic, not a douche... ), I haven't had a single moment to look into this beyond briefly skimming the Wiki's you linked up for me. (thanks for that one). I've had a butt-load of server issues at work that have taken a lot of my time. I'm HOPING to be able to look into some of this stuff a little deeper tonight (god willing)....
I will drop a note if I have issues....
Thanks again!

[GUIDE][INFO] The beginner's info thread (aka. the noob helper)

This guide is intended to be an all-in-one resource for people coming to Samsung phones after using other devices. It is a general introduction to the S4 and a glossary/explanation of terms you may see here in the forums.
This thread is slightly out of date but the info is still good, I will be updating again soon!!! Remember to hit thanks if this was useful
Disclaimer "Just because I am trying to be helpful does not make me responsible for anything that you do to your phone. Playing with any of this stuff could destroy your phone"
The layout of this post is as follows:
Welcome
FAQ
Glossary of terms
First off, welcome to XDA
The XDA community is home to the most talented and helpful phone developers on the planet.
These developers spend lots of their free time working on making all of our phones better. You should be nice and respectful to them and follow the rules. WHY? If the statement above isn’t enough reason then think selfishly, the less time they are dealing with redundant questions, the more time they have to develop stuff for all of us!
Help them help you by following the following basic rules:
1.If you are confused or have a question, the first thing to do is READ! Read lots, look things up both on xda and using google.
2.If after searching you still have not answered your question, then post in the Q&A forum.
3.Asking for ETAs on ROMs, updates, etc. is considered rude.. DON’T DO IT!
4.Don’t report bugs to a developer unless:
a.You know 100% that it hasn’t already been reported,
b.You know how to reproduce it
c.You can get a logcat of the problem (more on this later)
Some advice if you are new to all this and don’t want to ruin your phone:
1.Be patient. Don’t be the first or even the tenth person to flash anything. Wait until you see others using whatever Rom or kernel with success.
2.If you have any doubts about what you are doing, read more. Don’t flash.
3.Make sure you are in the forum for your device, not some similar or related device.
FAQ:
Q. Is my bootloader locked?
A. Only if you have an AT&T or Verizon phone
******* Info for AT&T users *******
Q. What is LOKI?
A. Loki is an exploit for phones with locked boot loader that allows us to bypass the locked boot loader in order to install custom roms or recoveries. More Loki info down below
Q. Whats the deal with MF3?
A. MF3 is the current firmware from AT&T that comes on any new phone. Your phone may also auto update to MF3 if you are not careful. MF3 patched the ability to use Loki to install custom roms/recoveries so if you are on MF3 things are much more difficult.
Q. How can I keep my phone from updating to MF3?
A. If you want to avoid the update, you should root your phone and freeze the following three apps using titanium backup or some similar app.
1. AT&T Software update Vxx_x_xxxx_x_x
2. FWUpgrade x.x.x
3. LocalFOTA vx_xxxx_x_x​
Why flash?
by flashing your device you can make your phone act differently, look different, and enable new or disabled options. you could ,for example:
enable native tethering
enable call recording
change the look of your phone
add custom toggle buttons
overclock or undervolt
increase battery life
etc..
Kernel vs Rom vs Recovery vs Modem
Kernel is the layer between the phone hardware and the rom. it controls things like Wi-Fi power, touch sensitivity, possible range of screen brightness, phone logging, and processor max and min speed. kernel must be designed not only for your device but also for the type of rom you are using (Sammy rom or Aosp) some kernels support all roms, others are specific.
Rom is the operating system of your phone. there are three main categories of roms.
roms that are based off of the Samsung stock rom (Sammy rom)
roms that are based off of Android open source project aka AOSP (AOSP, AOKP)
roms based off of the miui project (these used to be a branch of AOSP but recently they have also used Sammy base for miui)
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs4) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
modem is a file that controls the cell radio of the phone. Helps determine what frequencies to use and settings for a particular network. It is important when flashing a radio that you flash a radio that is for the AT&T sgs4
Methods for flashing files - Odin vs mobile Odin vs. clockworkmod(cwm) vs adb
Odin is the internal Samsung tool for flashing. I believe it only exists on Windows platform. This tool is mostly used to initially flash an insecure kernel or rooted kernel, OR to return to completely stock rom.. Files for flashing in odin generally should end in .tar or .tar.md5 although sometimes they come zipped and the tar is inside the zip. Read more about Odin before using it as it can easily break your phone. !!!as a general rule make sure you never check the "partition" checkbox EVER!!!
Mobile Odin (THIS TOOL DOES NOT SUPPORT ALL S4 MODELS...make sure you check that it specifically works with yours first. I think at this time it works on your phone unless you have locked bootloader but STILL DOUBLE CHECK) is a phone based version of Odin made by the very talented developer Chainfire. It can be installed on a rooted phone and used to flash the same .tar based files as the desktop version. Mobile odin has a few advantages. 1 you can use it from your phone. 2 it can auto root a stock rom (nice if you want to try out a brand new update that has not been rooted yet)
clockworkmod(cwm) or TWRP is recovery based tool that can make backups of your entire phone, flash new roms, kernels etc.., and do many other useful tasks. Once you have this on your phone my guess is that most of your flashing will be done through this tool. The files for flashing through clockworkmod are .zip files.
ADB is the android develpment bridge. It allows for command line interface with your phone through its debugging options. ADB can do most anything as I understand it. In my several years of flashing I have only had to use it once, and i could have waited for someone to come up with another solution. In general as a noob i recommend you stay away from ADB.
open source vs Samsung base(aka Touchwiz or TW) vs miui
Open Source Roms such as AOSP/AOKP are built using Google's open source android code as a base. The developers then add functionality specific to the device. The advantages of these builds are that they often have tons of options built in to the rom that change the behavior and look of the phone. They usually allow you to change the toggles in your notification pull down, change the battery display, make all kinds of adjustments to sounds, vibration etc... Some people also prefer the "vanilla" android look and feel. These roms often provide "bleeding edge" concepts, design, and modifications. The Disadvantages of these roms is that some of the hardware coding is done closed source by the phone manufacturers, which means that things like Infrared, bluetooth, camera, video recording, and MHL video out often don't work or take much longer to get working by the developers. Basically anything that relies on the Samsung framework will not work in an open source build. This means Svoice, Snote, and the Samsung camera app will not work.
Samsung based roms (aka Touchwiz/TW) are taken from the Samsung original phone software and modified by the developer. Usually, these roms are modified in order to be faster and to make changes to some of the features. Expect to see changes to the stock rom like: debloated (ATT and samsung software removed), de-odexed (explained later), enable tethering, unlimited sms recipients, added notification toggles, etc. Most of these changes are made to: make the phone faster, improve battery life, make the phone easier to theme. The advantage of these roms is that they still use the Samsung framework so all the proprietary stuff like camera, bluetooth, MHL still work, the disadvantage is that they will never be as customisable as open source roms.
MIUI is a rom that focuses on theming. Official MIUI (Chinese) gets updated weekly on Friday and then there are lots of miui developers who adapt it to other languanges and make some tweaks to it. MIUI can be built from AOSP source or Samsung source and depending will have different features. The first MIUI rom for our phone just appeared in these forums and it is based off of AOSP. MIUI has a unique look and is also highly customizable through theming. There are tons of themes available for download through the rom itself and you can mix and match any part of any theme you want. This includes icons, lockscreen style, etc.. Some people criticize while others praise MIUI for being very "iphone like". This is because the icons look more iphone like and there is no app drawer in the MIUI launcher. However, you can still use any launcher you like within MIUI.
odexed vs de-odexed
odexed is how the phone comes stock from Samsung. Odexed means that system files and apps are split into two pieces and kept in different places on the phone. This is done to speed things up a bit. However, it makes it harder to theme the phone because the apps are split up. Most custom roms choose to de-odex (basically regroup the files back into one) so that custom themers can make themes more easily for the phone.
Flashing "dirty" vs flashing "clean"
Clean
Doing a clean install of a rom means erasing or formatting all the data from the previous rom before you flash the new one. This is the prefered way to flash a rom to ensure that it will run smoothly. It is necessary if you are switching from one rom type to another (CM to Samsung base). In order to do a clean flash you need to boot into recovery and select the following options: wipe user data (this wipes all apps and personal data, but not your photos/videos), wipe cache, advanced>wipe dalvik cache, storage/mounts>format system. This will ensure that no trace of the former rom is left on the phone. Beware that at this point your phone will not boot until you install a new rom. I suggest using titanium backup to backup apps and smsbackup+ for texts to make getting your new rom configured easy.
Dirty
Doing a dirty install means just flashing a new rom right over the top of the old one without wiping any data. The advantage to this is that you don't lose any apps or account info. The disadvantage is that you open up the possibility for problems. Generally you only want to flash this way if you are upgrading a rom (CM10 nightly to the next nightly, or from one samsung based rom to another). If you decide to flash over the top and have any issues, you should not report bugs, but try flashing clean first.
Logcat
Logcat is a way to access the android system log for everything that is going on behind the scenes. This tool is used to help developers pinpoint problems in a rom. If you want to actually be helpful to a dev when reporting a bug, you should really learn to use this tool. I am no expert on logcat but you can find some good information in this post: http://forum.xda-developers.com/show....php?t=1726238
What is the Bootloader?
The bootloader is basically what it sounds like...it loads the boot image of the device. Basically it is one of the first things to run on the phone and it shows the phone where to find the boot image and how to start. The bootloader is also responsible for allowing access to the recovery part of the phone.
Locked Bootloader?
This seems to confuse a lot of users so here goes: The AT&T and Verizon versions of our phone have a locked bootloader. What does this mean? To the noob, it means that the devs had to figure out how to bypass or unlock this part of the phone in order to be able to boot custom recoveries such as CWM and TWRP. Getting a custom recovery means being able to backup the phone as well as flash custom roms. Luckily for us, Djrbliss (make sure and thank him! his thread is here:http://forum.xda-developers.com/showthread.php?t=2292157) figured out how to bypass the locked bootloader. The exploit he used is known as Loki. Please remember that the loki exploit is not the same thing as unlocking the bootloader, it is a bypass/trick. AT&T and Verizon have fixed the exploit that allowed loki to work in there newest firmware. Loki patch will not work for MF3 firmware or later.
Loki
refers to the exploit that allows us to run custom recoveries as well as custom roms. You only need to have a loki'd rom if you have a model with a locked bootloader (AT&T). Thankfully, you can install a custom recovery that will auto-Loki any rom you flash so that you can install almost any rom built for our model phone (see below). I strongly recommend flashing an auto loki recovery if you have a phone with locked bootloader. I use this one here: http://forum.xda-developers.com/showthread.php?t=2291956
Compatible Roms
you should be able to run any rom built for AT&T, TMobile, or the I9505 international model (NOT I9500!!) as long as you flash with an auto loki recovery. You can check out this thread for more info. Make sure and thank TheAxman! http://forum.xda-developers.com/showthread.php?t=2295557
You may have to manually set the APN. If you encounter problems with the rom look in that roms thread for answers.

Sticky!!

Well damn, I thought I knew a lot, but after reading this thread, I really didn't. Well done. :good:

Incredible resource for those coming in from a different ecosystem.
Thanks much!!

Thread stuck!! Nice work!

Got my new At&t Samsung Galaxy S4 and this will definitely help me!!

this is another thread that really helped me as well these two have really helped me so far i have rooted several divices and just relied on everyone else and not i am starting to take a lot more of an interest ant these threads have been the most helpful
http://forum.xda-developers.com/showthread.php?p=42055644#post42055644

WoW
Great work! I'm sure this thread will be very helpful to a lot of people (Myself included). Tanks bro! :victory:

More! More! :d

I've been searching high and low ive read everything and maybe im not understanding but after I root my phone how do I do the whole loki thing??... I'm eager to start flashing roms... Ive read of some recoveries that do this is that an accurate assessment??

KINGDROID25 said:
I've been searching high and low ive read everything and maybe im not understanding but after I root my phone how do I do the whole loki thing??... I'm eager to start flashing roms... Ive read of some recoveries that do this is that an accurate assessment??
Click to expand...
Click to collapse
What exactly are you trying to do?
If you want to install a custom ROM or kernel, you need a custom recovery. The ROM or Kernel developer will have LOKI-fied it for you.
For TWRP (my custom recovery of choice) Download GooManager from the Play Store and install.
Inside the goo.im app, go to menu>Install OpenRecovery Script
then you can boot into recovery to apply kernels, ROMs, etc to your hearts desire

joeybear23 said:
What exactly are you trying to do?
If you want to install a custom ROM or kernel, you need a custom recovery. The ROM or Kernel developer will have LOKI-fied it for you.
For TWRP (my custom recovery of choice) Download GooManager from the Play Store and install.
Inside the goo.im app, go to menu>Install OpenRecovery Script
then you can boot into recovery to apply kernels, ROMs, etc to your hearts desire
Click to expand...
Click to collapse
Its tht ez just root and add custom recovery??.. The whole loki thing is what's been throwing me off
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

KINGDROID25 said:
Its tht ez just root and add custom recovery??.. The whole loki thing is what's been throwing me off
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Yes... the difficult part is if you are a developer. They make our lives much easier.

joeybear23 said:
Yes... the difficult part is if you are a developer. They make our lives much easier.
Click to expand...
Click to collapse
Thanx ima root tonight I jus need to get a copy of the stock firmware
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

KINGDROID25 said:
Thanx ima root tonight I jus need to get a copy of the stock firmware
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Stock Firmware:
http://forum.xda-developers.com/showthread.php?t=2261573
That is a HUGE download, but the process is simple.

im not a newb but i need to boost my post count lol...soooo spam

KINGDROID25 said:
I've been searching high and low ive read everything and maybe im not understanding but after I root my phone how do I do the whole loki thing??... I'm eager to start flashing roms... Ive read of some recoveries that do this is that an accurate assessment??
Click to expand...
Click to collapse
I have updated the OP to explain Loki, hope that helps :good:

Noob here first time posting I rooted my phone and installed cwm using casual method, created backup and installed mint rom love it but after a couple of post I see I didn't backup EFS should I be worried?

I'm not sure what the deal is with backing up the IMEI number on our phones yet. I have not seen anyone post about losing their IMEI yet so I wouldn't be too worried. On the s3 only the international model phones could be backed up by saving the efs folder. The backup process for AT&T phones was much more complex. I assume the same holds true on the s4. Will update when I find out more
Sent from my GT-I9505 using xda premium

I wanted to make sure Thx. Is it to late to back EFS or can I just restore my backup and do it?

Is there Any beta version for k20Pro/Mi9T which doesn't Require Pc and Other things? Just download Package and install.

Hi,
I'm MadWolF_x. My Question is - Is there Any beta version for k20Pro/Mi9T which doesn't Require Pc and Other things? Just download Package and install.
Not me alone, there are lots and lots of people Asks and Seeks this question.

madwolfbad1 said:
Hi,
I'm MadWolF_x. My Question is - Is there Any beta version for k20Pro/Mi9T which doesn't Require Pc and Other things? Just download Package and install.
Not me alone, there are lots and lots of people Asks and Seeks this question.
Click to expand...
Click to collapse
If there are that many people looking for it and none have found it, then that is quite a bit of evidence that suggests it probably doesn't exist, otherwise, one of you would have found something.
If you are like the rest of us and use mobile devices all the time and you want to be able to flash, update, modify or repair the devices yourself then you need to invest in a PC whether you like it or not. If you do not want to invest in a PC then be prepared to not be able to do these kinds of things with your devices.

Droidriven said:
If there are that many people looking for it and none have found it, then that is quite a bit of evidence that suggests it probably doesn't exist, otherwise, one of you would have found something.
If you are like the rest of us and use mobile devices all the time and you want to be able to flash, update, modify or repair the devices yourself then you need to invest in a PC whether you like it or not. If you do not want to invest in a PC then be prepared to not be able to do these kinds of things with your devices.
Click to expand...
Click to collapse

Oh Good God. I just did. And thank you for letting me know that there are * None * how about I create one? Ttyl soon Senior Member

madwolfbad1 said:
Oh Good God. I just did. And thank you for letting me know that there are * None * how about I create one? Ttyl soon Senior Member
Click to expand...
Click to collapse
It may out there, who knows? It doesn't hurt to keep looking. As for making your own, as far as I know, there is no way to officially sign whatever you might create in order for it to flash at all via stock recovery, adb sideload or stock system update center.

Droidriven said:
It may out there, who knows? It doesn't hurt to keep looking. As for making your own, as far as I know, there is no way to officially sign whatever you might create in order for it to flash at all via stock recovery, adb sideload or stock system update center.
Click to expand...
Click to collapse
Don't get hurt man. As we all own flagships and some of us doesn't like what rom we use. I've been reading threads after threads, doing things my own, sleepless nights, weeks!!!! At some point i thought lets just post something which is most searched.
Reaching Finish line sometimes looks tough but i believe maybe I can. And don't get offended about what i wrote because * Own A Pc * comment made me go nuts. Not everyone knows about xda. They search on YouTube. Instead of reading people chooses to listen. I know how it feels to actually reading what you wrote. Well i should be thankful to those who made me feel bad, cause if i Never felt bad, i would never had any clue about my true potential.
I work alone, i don't have people helping me out. I've never found someone who works more for others, never found someone who can handle mental pressure like i do. And definitely, you will never know with whom you had this conversation \Peace/

madwolfbad1 said:
Don't get hurt man. As we all own flagships and some of us doesn't like what rom we use. I've been reading threads after threads, doing things my own, sleepless nights, weeks!!!! At some point i thought lets just post something which is most searched.
Reaching Finish line sometimes looks tough but i believe maybe I can. And don't get offended about what i wrote because * Own A Pc * comment made me go nuts. Not everyone knows about xda. They search on YouTube. Instead of reading people chooses to listen. I know how it feels to actually reading what you wrote. Well i should be thankful to those who made me feel bad, cause if i Never felt bad, i would never had any clue about my true potential.
I work alone, i don't have people helping me out. I've never found someone who works more for others, never found someone who can handle mental pressure like i do. And definitely, you will never know with whom you had this conversation \Peace/
Click to expand...
Click to collapse
Can you unlock your bootloader or is it already unlocked? If either of these is yes then you have a chance if the stock source code for your device is available. If the stock source is available, you might be able to build your own custom recovery and custom ROMs. If the stock source code isn't available then true custom ROMs are out of the question but you could still try making your own modified stock ROMs using your stock ROM as a base then modifying it with elements from other devices that have your exact same CPU architecture/chipset. Or you could port stock ROMs from other similar devices with the same architecture/chipset using your device's stock ROM as a source to convert the other device's ROM to be compatible with your device. Mind you that any part of all of that will require an unlocked bootloader and TWRP custom recovery.
You can also try finding a GSI ROM that is compatible with your device's CPU architecture/chipset but that will also require unlocked bootloader and TWRP.

Well, Thank you
Droidriven said:
Can you unlock your bootloader or is it already unlocked? If either of these is yes then you have a chance if the stock source code for your device is available. If the stock source is available, you might be able to build your own custom recovery and custom ROMs. If the stock source code isn't available then true custom ROMs are out of the question but you could still try making your own modified stock ROMs using your stock ROM as a base then modifying it with elements from other devices that have your exact same CPU architecture/chipset. Or you could port stock ROMs from other similar devices with the same architecture/chipset using your device's stock ROM as a source to convert the other device's ROM to be compatible with your device. Mind you that any part of all of that will require an unlocked bootloader and TWRP custom recovery.
You can also try finding a GSI ROM that is compatible with your device's CPU architecture/chipset but that will also require unlocked bootloader and TWRP.
Click to expand...
Click to collapse

Well thank you. That was helpful. Everyone is trying almost same thing. I'm trying something which is unique and different. Can't say much. Publicly i don't post anything, or write. This post was worth it. Being only a listener is bad which i Realized.
Your an Amazing Person, be Amazing. Will you please leave your personal email address? Thanks

Are MediaTek 6563 and 6567 ROMS interchangeable?

I have an RFinder B1+(14) that works fantastic, it has the 6567 chipset. I also have an RFinder B1 Classic with a 6563 chipset that will not boot into Android 8 on the way, and the ROM has not been easy to find.
I suspect they are NOT compatible, but if I did flash the older radio with newer firmware, I'd be able to reverse the damage as long as I didn't overwrite the preloader.
If the two are, in fact, compatible, it would save me some time.
Are they compatible?

N
shadow460 said:
I have an RFinder B1+(14) that works fantastic, it has the 6567 chipset. I also have an RFinder B1 Classic with a 6563 chipset that will not boot into Android 8 on the way, and the ROM has not been easy to find.
I suspect they are NOT compatible, but if I did flash the older radio with newer firmware, I'd be able to reverse the damage as long as I didn't overwrite the preloader.
If the two are, in fact, compatible, it would save me some time.
Are they compatible?
Click to expand...
Click to collapse
Not without porting them from one to the other, "IF" the sources to do so are available(either stock firmware for the two devices or at least the stock source code for the device the ROM will be flashed on.

I have tried without success to compile software. Of course it can be done, I just haven't got the hang of it (I need to learn though).
If there are other things I can do, learn, etc from this thread, I'm all ears. If not, thank you for the info.

shadow460 said:
I have tried without success to compile software. Of course it can be done, I just haven't got the hang of it (I need to learn though).
If there are other things I can do, learn, etc from this thread, I'm all ears. If not, thank you for the info.
Click to expand...
Click to collapse
There really isn't a 100% all in one get it right the first time guide out there. There are lots of guides that give a general idea of how to port stock ROMs but it will still require trial and error to iron out the details. Do some research to see if there are any specific security features preventing the ported ROM from flashing/booting then see if there are any tricks to bypass those specific features. You may need to unlock the bootloader and dig into trying to modify the bootloader.img located in the copy of your devices currently installed stock firmware file(or the last "official" firmware that was installed on your device before you tried to modify it).