Database Users

[Q] Samsung Galaxy S i9000 slim bean rom base band & IMEI unknown

Hi Guys
I have a Samsung Galaxy s i9000 slim bean Rom the base band & IMEI unknown I can't seem to use it to sms or call a guy from the Slimrom site told the Rom has no modem, so how do i add one ? I realy like the Rom its much faster than the one I had before I had Cyanogen mod Helly bean before and about 2 weeks ago it got into a boot loop so I got a friend of a friend to root it for me twice and still have this no network issue! I can't ask him to do it again. So I am trying to find a solution here. How do I add a modem ? The wifi works fine but Whats app tells me that tablets are not supported... but this is not a tablet its a Samsung Galaxy s i9000 , will adding a modem fix the network issue and make Whats app work? Or do I need a new Rom? Please keep in mind that I'm not a Android Developer in any sense of the word!!
Thanks Reigncpt!!

try the latest Slimrom
Reigncpt said:
Hi Guys
I have a Samsung Galaxy s i9000 slim bean Rom the base band & IMEI unknown I can't seem to use it to sms or call a guy from the Slimrom site told the Rom has no modem, so how do i add one ? I realy like the Rom its much faster than the one I had before I had Cyanogen mod Helly bean before and about 2 weeks ago it got into a boot loop so I got a friend of a friend to root it for me twice and still have this no network issue! I can't ask him to do it again. So I am trying to find a solution here. How do I add a modem ? The wifi works fine but Whats app tells me that tablets are not supported... but this is not a tablet its a Samsung Galaxy s i9000 , will adding a modem fix the network issue and make Whats app work? Or do I need a new Rom? Please keep in mind that I'm not a Android Developer in any sense of the word!!
Thanks Reigncpt!!
Click to expand...
Click to collapse
..Hi,please try the latest slimrom, the thread is here
http://forum.xda-developers.com/showthread.php?t=2060374
..try a clean install just to make sure.

How do you do a clean install?
wilvic said:
..Hi,please try the latest slimrom, the thread is here
http://forum.xda-developers.com/showthread.php?t=2060374
..try a clean install just to make sure.
Click to expand...
Click to collapse
I followed the instructions on the slim bean site cleared cache partition and wiped dalvik cache and installed the latest version : Slim-I9000-4.2.1.stable.1.0-OFFICIAL .... but still the same issue IMEI and Baseband are unknown and I get no network. Did I do it wrong?
How do I do clean install? Do I need special software to do a clean install? If so where do I get it ?
I read somewhere on this forum that I need to flash the original rom to it to get it to find its IMEI and modem settings then flash the rom I want! Is the true? If so where do I get the original rom from as I got the phone with Cyanogen Helly bean on it so I don't even know what the original rom was??
Will really appreciate any help thanks!!!
Reigncpt

Try this
Reigncpt said:
I followed the instructions on the slim bean site cleared cache partition and wiped dalvik cache and installed the latest version : Slim-I9000-4.2.1.stable.1.0-OFFICIAL .... but still the same issue IMEI and Baseband are unknown and I get no network. Did I do it wrong?
How do I do clean install? Do I need special software to do a clean install? If so where do I get it ?
I read somewhere on this forum that I need to flash the original rom to it to get it to find its IMEI and modem settings then flash the rom I want! Is the true? If so where do I get the original rom from as I got the phone with Cyanogen Helly bean on it so I don't even know what the original rom was??
Will really appreciate any help thanks!!!
Reigncpt
Click to expand...
Click to collapse
Hi,
We can't be sure what the original ROM for your phone was, probably they we're referring to Eclair because that's the default. I have Galaxy S too so I wanted to help you. So here's what we will do, we might need to install an official stock ROM for it, we will not use froyo, instead this tutorial will let you install the latest GB for GT-i9000,GingerBread 3.6.
Here's the link (please hit thanks on the one who posted that if it will help you): http://forum.xda-developers.com/showthread.php?p=22555425
(You have to follow that tutorial up until this line only:
• When the phone reboots into the rom, wait for the setup wizard to appear and then just use the 3 key combo into the download mode again.
Close Odin and open it again> press PDA button and browse for CF-Root…file> Press START button and wait for the green pass notification in Odin.
**Lines after that, you don't need to do, since you will be flashing Slim rom. After that, your phone will reboot and you will be in the latest Gingerbread for Galaxy S, and a rooted one so you have a CWM)
After doing that, we will have to install Slim ROM. (a clean install, or fresh install, a clean install is this - wiping everything out, as in fresh install)
Here's what you need to do (straight from Slim Rom's website)
From another JB or ICS Rom to SlimBean
Download device_x.x.zip, slim_gapps.zip.
Enter CWM, wipe data, format system ( in mounts and storage)
Flash Device_x.x.zip***, then MUST flash slim_gapps.zip (other files optional)
*** - If the flash is too quick ( < 5 seconds or so), reflash device before flashing common or other zip files.
(So that's what you need to do, just download the latest rom and the gapps for galaxy s i9000,
put it in the root of your internal sd card
Go to Clockwork mod (Turn off, then press DOWN, POWER, HOME simultaneously)
wipe data, format system ( in mounts and storage)
Install zip from sd card and you will have the latest Slim rom and hopefully you get your IMEI back)
Please reply if you have more questions or clarifications needed, you can also message me, i will reply as soon as i can.

Slimbean IMEI unknown fix i9000
wilvic said:
Hi,
We can't be sure what the original ROM for your phone was, probably they we're referring to Eclair because that's the default. I have Galaxy S too so I wanted to help you. So here's what we will do, we might need to install an official stock ROM for it, we will not use froyo, instead this tutorial will let you install the latest GB for GT-i9000,GingerBread 3.6.
Here's the link (please hit thanks on the one who posted that if it will help you): http://forum.xda-developers.com/showthread.php?p=22555425
(You have to follow that tutorial up until this line only:
• When the phone reboots into the rom, wait for the setup wizard to appear and then just use the 3 key combo into the download mode again.
Close Odin and open it again> press PDA button and browse for CF-Root…file> Press START button and wait for the green pass notification in Odin.
**Lines after that, you don't need to do, since you will be flashing Slim rom. After that, your phone will reboot and you will be in the latest Gingerbread for Galaxy S, and a rooted one so you have a CWM)
After doing that, we will have to install Slim ROM. (a clean install, or fresh install, a clean install is this - wiping everything out, as in fresh install)
Here's what you need to do (straight from Slim Rom's website)
From another JB or ICS Rom to SlimBean
Download device_x.x.zip, slim_gapps.zip.
Enter CWM, wipe data, format system ( in mounts and storage)
Flash Device_x.x.zip***, then MUST flash slim_gapps.zip (other files optional)
*** - If the flash is too quick ( < 5 seconds or so), reflash device before flashing common or other zip files.
(So that's what you need to do, just download the latest rom and the gapps for galaxy s i9000,
put it in the root of your internal sd card
Go to Clockwork mod (Turn off, then press DOWN, POWER, HOME simultaneously)
wipe data, format system ( in mounts and storage)
Install zip from sd card and you will have the latest Slim rom and hopefully you get your IMEI back)
Please reply if you have more questions or clarifications needed, you can also message me, i will reply as soon as i can.
Click to expand...
Click to collapse
Guys. I have used Slim bean firmware on 2 i9000 with no issues but my third had imei unknown. I tried all options. Basically it would be there from 2.2 to 2.3 but once rooted and CWM added, and I installed Slim I would loose imei. Tried imei backups- no good. Fix was easy. Install Hellybean instead. Just worked. I suspect there is an issue in slim unfortunately...

This is a known issue with i9000 losing its IMEI... It was always recommended to have an EFS backup if it arose...

i've tried copying efs from backup using shady file root free but i still can't get my network back on infuse 4g

Clean Install Of Slim Rom
Hi Guys
I'm new to this whole rom experience, and want to up date my Slim Bean 4.2.1 -> the new 4.2.2 the slim rom site says I need to do a "Full wipe" goes on to say : "Means full data wipe and manual format of system partition."
So can any one please help me with a step by step walk through as how to do this on a GT i9000 with Semaphore Kernel?
Thanks so much you Guys!!!!
Reigncpt!!

Reigncpt said:
Hi Guys
I'm new to this whole rom experience, and want to up date my Slim Bean 4.2.1 -> the new 4.2.2 the slim rom site says I need to do a "Full wipe" goes on to say : "Means full data wipe and manual format of system partition."
Reigncpt!!
Click to expand...
Click to collapse
Full wipe means "wipe data/factory reset" in CWM recovery.

Elephone P7000 MIUI_V7_based on Android 5.0

Congratulations to all P7000 owners , here you can try MIUI on your P7000
Recovery: http://bbs.elephone.hk/thread-5011-1-2.html#.VeZR0_RAXX4
Tutorial reference: http://bbs.elephone.hk/thread-2865-1-1.html#.VeZUlPRAXX4
ROM download link: https://mega.nz/#!7w8yGZ6J!QsYGXj-D9y8nEmuM4EMjhZODM7dmRZVhtH-I3XJEF9Y
You'd better conduct factory reset and wipe cache partition first . Back up your phone before factory reset. If there are some errors during flashing, you can flash official rom first and then try again.
Known bugs:
Videos taken by the phone cann't be saved, but it can be solved to install a 3rd party camera APP.
Any other bugs, please reply here: http://bbs.elephone.hk/thread-7535-1-1.html

Elephone1 said:
Congratulations to all P7000 owners , here you can try MIUI on your P7000
Recovery: http://bbs.elephone.hk/thread-5011-1-2.html#.VeZR0_RAXX4
Tutorial reference: http://bbs.elephone.hk/thread-2865-1-1.html#.VeZUlPRAXX4
You'd better conduct factory reset and wipe cache partition first . Back up your phone before factory reset. If there are some errors during flashing, you can flash official rom first and then try again.
Known bugs:
Videos taken by the phone cann't be saved, but it can be solved to install a 3rd party camera APP.
Any other bugs, please reply here: http://bbs.elephone.hk/thread-7535-1-1.html
Click to expand...
Click to collapse
Did you forget the download link, mate?

Original thread: ELEPHONE P7000 MIUI_V7_ based on Android 5.0_20150831 (languages added))
Download link: https://mega.nz/#!uYEhVDrQ!6PUew_KT8PYiGUjiNBbog0HDMH_iMp8TrSxvUg18gfs
Download link for languages: https://mega.nz/#!7w8yGZ6J!QsYGXj-D9y8nEmuM4EMjhZODM7dmRZVhtH-I3XJEF9Y
Port was made by user @Deepflex

Elephone1 said:
Congratulations to all P7000 owners , here you can try MIUI on your P7000
Recovery: http://bbs.elephone.hk/thread-5011-1-2.html#.VeZR0_RAXX4
Tutorial reference: http://bbs.elephone.hk/thread-2865-1-1.html#.VeZUlPRAXX4
You'd better conduct factory reset and wipe cache partition first . Back up your phone before factory reset. If there are some errors during flashing, you can flash official rom first and then try again.
Known bugs:
Videos taken by the phone cann't be saved, but it can be solved to install a 3rd party camera APP.
Any other bugs, please reply here: http://bbs.elephone.hk/thread-7535-1-1.html
Click to expand...
Click to collapse
there is no source code provided. hence it is not development, nor allowed on xda. please fix this, or I need to report this thread to get it closed/removed.

How many languages does this Rom have?

Good job, the only problem i have is that I do not see SPANISH language for the installation. Could you please add this important language also????

Recovery after Flashing
Hi All
2 Problems I have but first let me say thanks for an awesome rom.
Love it.
1) After flashing Volume up, Power takes me to Chinese recovery. However MobileUncle will boot into CWM.
I forgot to check if Power - Volume Down might get me into CWM
2) Since I got this phone MTKTools 2.5.3 will not connect. I have a P3000s that connects every time as well as
an old HDC S5 SM-G900S ( bepa G900w ) connecting. Is a different driver required for the P7000?
I have tried 3 different computers and all the USB ports. Uninstalled and reinstalled driver.
Any help would be greatly appreciated.
Thanks in advance

Hey. I have mt6752 64bit device called xperia c5 e5553. Can some one port this rom to our device? There are not enogh developers to do it nor not enough people who know to do it. So how can i port this rom for e5553 or can someone port it for us?

Steps to install other variant ROMs (Including Galaxy S7 Port ROMs) on N910P

Guys, I'm making this thread for those people who are using Sprint's Note 4 (N910P) outside of US and are stuck with Sprint's ROM (or the ROMs that are based on it) and have certain issues in using the ROM.
For instance, I'm using the unlocked variant of N910P with a GSM carrier, so I was having problem in connecting to the Hot-Spot feature as all of my devices were stuck at "Obtaining IP Address" loop and eventually would never connect.
I did try various "hacks" present here on XDA for enabling Hot-Spot feature like using Galaxy Tools, using SQLite Editor, etc but wasn't able to overcome the problem.
Since, XDA is a great platform for sharing solutions to various problems, I decided to create a thread especially for those who don't want Sprint's bloatware but want to stick with "Stock ROM features" like S Pen.
Hence, here's the step-by-step guide for installing other carrier's ROM on N910P:
Before attempting all this,make sure to be on OK1 Bootloader & Baseband (Do not try this on Marshmallow Bootloaders) for N910P.
Step 1:
Install TWRP recovery version 3.0.1 (Yes, you read it right..it's 3.0.1 & not 3.0.2)
Once you have downloaded, flash it through ODIN (the TAR file) or through existing TWRP (using ISO image).
Step 2:
Make a backup of your current ROM so that you can revert to it in case of unsuccessful flash.
Step 3:
Go to Wipe (in TWRP)-----> Factory reset (do this 3 times.....yes, 3 times!)
Then, go to Advanced Wipe & wipe Dalvik/ART cache,Cache,Data,Internal Storage, System (Do not wipe external SD Card).
Hit the back button to come out of the "wipe window"
Step 4:
Click on "Install" and choose the files in following order:
a) Dr Ketan's ROM
b) Data Fix for the ROM
c) Kernel
d) SuperSU (I used beta 2.71)
Once the flashing process is finished, reboot the system and wait for the phone to boot.
It will take a long time (around 10-15 minutes) to boot.
Once you are on setup wizard screen, choose to apply "Dr Ketan's fix" and then you can proceed like you do in any other ROM.
Downloads:
TWRP: https://dl.twrp.me/trltecan/
(Choose TAR or ISO as per your choice and flash accordingly)
ROM:
http://www.drketanrom.com/n910g.html
(All credit goes to Dr Ketan for his hard work & awesome ROM)
(Its for G variant)
Data FIX:
https://drive.google.com/folderview?id=0B1I0vyV3onrjemR2YlY2V0s0ME0&usp=sharing
(Credit goes to @dr.ketan, & @Lanc-City for providing all the required info)
Kernel:
http://d-h.st/rb3d
(The credit for this Kernel goes to @Hani K.)
Super SU:
http://forum.xda-developers.com/showthread.php?t=1538053
(Credit goes to @Chainfire)
Note: I am in no way to be credited for all this as the links provided above are a result of hard work from the respective developers. I have just compiled all the links into one thread so that it can help anyone like me to switch to other ROM.
Also, neither I nor any of the above mentioned developers/members are responsible for any fault that may arise due to improper flash or other reasons..
Do all of it at your own risk!
Last but not the least, I would like to thank @ricohz for helping me out when I was stuck in some steps..
(In the screen-shot attached, the model number is 920T for obvious reasons...so don't ask why it's not 910P..)
Do note that the APNs have to be edited manually, else the data connectivity would not be there!
(This thread should benefit the non-Sprint users........)
Update:
There are some more ROMs that can be flashed successfully on N910P such as:
1. Maximum Overdrive
http://forum.xda-developers.com/note-4-tmobile/development/s7-portn910t-n910w8-t3375956
2. Nameless ROM
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-nameless-mm-lightfastdeodexed-t3363547
Kindly say Thanks to the developers on their respective threads for all their hard work.

Thanks for sharing im gonna give it a shot
But why did you say to be on ok1 if you have marshmallow version in the screen shot
Sent from my Not4 Mod using Tapatalk

NICE
SPRINT USERS IF YOU FLASH THIS TEXT WON'T GO OUT
MMS ARE FINE TEXT COME IN BUT WON'T GO OUT
this works for him because he's using a gsm sim card

Google Drive link is broken
Sent from my SM-N910P using Tapatalk

Data fix and Kernel fix link broken...

Anybody get text going I'd be happy too pay bounty

Jedi Aaris said:
Thanks for sharing im gonna give it a shot
But why did you say to be on ok1 if you have marshmallow version in the screen shot
Sent from my Not4 Mod using Tapatalk
Click to expand...
Click to collapse
OK1 bootloader has been suggested so as to avoid any incompatibility issues for the ROM!

Shiva758 said:
Data fix and Kernel fix link broken...
Click to expand...
Click to collapse
Links have been updated!

ricohz said:
NICE
SPRINT USERS IF YOU GLASH THIS TEXT WONT GO OUT MMS ARE FINE TEXT COME IN BUT DON'T GO OUT
thus works for him because he's using a gsm sim card
Click to expand...
Click to collapse
@ricohz: Yes,buddy...
For GSM carriers, this method works flawlessly..
Kudos to you for helping me out!

bddpolo said:
Anybody get text going I'd be happy too pay bounty
Click to expand...
Click to collapse
Some one said bounty?
Lol jk

I got boot loops what I do now right now I am on ok1 !!!!what mistake i did? Is that ROM marshmallw? May be I downloaded that one ? Which kernel we have to use ? When I go to download section it shows me three kernel variants ?
---------- Post added at 11:37 AM ---------- Previous post was at 11:33 AM ----------
Do we have to download n910pb6 mm firmware ?

I just messed my 4 hours on this ROM but every time I qm getting bootloops...I am on lollipop ok1 firmware and bootloader .I tried everything bit nothing works ..or may be its not complete clear what I download ?

Shiva758 said:
I just messed my 4 hours on this ROM but every time I qm getting bootloops...I am on lollipop ok1 firmware and bootloader .I tried everything bit nothing works ..or may be its not complete clear what I download ?
Click to expand...
Click to collapse
Tinkering and flashing custom ROMs on Android is not always a piece of cake...
Loads of patience is required and if the process is not carried out as stated/expected, time is bound to get wasted.
Anyway, here's what you need to do (Or at-least, expected to do..):
1. Take a backup of the current ROM.
2. Do Factory reset 3 times ( First time, do it again & do it yet again..making it three times)
3. Wipe everything(except External SD Card) again 3 times as above.
4. Flash the ROM.
5.Once ROM is flashed, do not reboot & flash the Data Fix.
6.Again, do not reboot and flash the Vitamin Kernel (originally meant for F variant).
7. Do not reboot yet again & flash the SuperSU (I FLASHED 2.71).
Now, reboot and wait for the setup screen to appear. It will take quite a long time to appear and the phgone will be stuck on Samsung logo for quite a while.
Now, if you have patience, wait for the process to finish, and if not, you know what to do..

Shiva758 said:
I got boot loops what I do now right now I am on ok1 !!!!what mistake i did? Is that ROM marshmallw? May be I downloaded that one ? Which kernel we have to use ? When I go to download section it shows me three kernel variants ?
---------- Post added at 11:37 AM ---------- Previous post was at 11:33 AM ----------
Do we have to download n910pb6 mm firmware ?
Click to expand...
Click to collapse
The direct link for the ROM is:
http://d-h.st/m9bj
The direct link for the kernel is:
https://www.androidfilehost.com/?w=files&flid=54698
Hope, this much of help will make things clear for you.

Finally it worked . Actually i am doing ( kernel) mistake .Thanks for providing direct links and for your kind help.

robinhood1808 said:
Guys, I'm making this thread for those people who are using Sprint's Note 4 (N910P) outside of US and are stuck with Sprint's ROM (or the ROMs that are based on it) and have certain issues in using the ROM.
For instance, I'm using the unlocked variant of N910P with a GSM carrier, so I was having problem in connecting to the Hot-Spot feature as all of my devices were stuck at "Obtaining IP Address" loop and eventually would never connect.
I did try various "hacks" present here on XDA for enabling Hot-Spot feature like using Galaxy Tools, using SQLite Editor, etc but wasn't able to overcome the problem.
Since, XDA is a great platform for sharing solutions to various problems, I decided to create a thread especially for those who don't want Sprint's bloatware but want to stick with "Stock ROM features" like S Pen.
Hence, here's the step-by-step guide for installing other carrier's ROM on N910P:
Before attempting all this,make sure to be on OK1 Bootloader & Baseband for N910P.
Step 1:
Install TWRP recovery version 3.0.1 (Yes, you read it right..it's 3.0.1 & not 3.0.2)
The reason for choosing 3.0.1 is that the ROM successfully booted using this version instead of 3.0.2 (Don't ask me the reason for it..)
Once you have downloaded, flash it through ODIN (the TAR file) or through existing TWRP (using ISO image).
Step 2:
Make a backup of your current ROM so that you can revert to it in case of unsuccessful flash.
Step 3:
Go to Wipe (in TWRP)-----> Factory reset (do this 3 times.....yes, 3 times!)
Then, go to Advanced Wipe & wipe Dalvik/ART cache,Cache,Data,Internal Storage, System (Do not wipe external SD Card).
Hit the back button to come out of the "wipe window"
Step 4:
Click on "Install" and choose the files in following order:
a) Dr Ketan's ROM
b) Data Fix for the ROM
c) Kernel
d) SuperSU (I used beta 2.71)
Once the flashing process is finished, reboot the system and wait for the phone to boot.
It will take a long time (around 10-15 minutes) to boot.
Once you are on setup wizard screen, choose to apply "Dr Ketan's fix" and then you can proceed like you do in any other ROM.
Downloads:
TWRP: https://dl.twrp.me/trltecan/
(Choose TAR or ISO as per your choice and flash accordingly)
ROM:
http://www.drketanrom.com/n910g.html
(All credit goes to Dr Ketan for his hard work & awesome ROM)
(Its for G variant)
Data FIX:
http://forum.xda-developers.com/not...guidehow-to-flash-dr-ketan-rom-6-0-1-t3364025
(Credit goes to @dr.ketan, & @Lanc-City for providing all the required info)
Kernel:
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-h-vitamin-t3364213
(The credit for this Kernel goes to @Hani K.)
Super SU:
It can be found here on XDA
(Credit goes to @Chainfire)
Note: I am in no way to be credited for all this as the links provided above are a result of hard work from the respective developers. I have just compiled all the links into one thread so that it can help anyone like me to switch to other ROM.
Also, neither I nor any of the above mentioned developers/members are responsible for any fault that may arise due to improper flash or other reasons..
Do all of it at your own risk!
Last but not the least, I would like to thank @ricohz for helping me out when I was stuck in some steps..
(In the screen-shot attached, the model number is 920T for obvious reasons...so don't ask why it's not 910P..)
Do note that the APNs have to be edited manually, else the data connectivity would not be there!
(This thread should benefit the non-Sprint users........)
Click to expand...
Click to collapse
what about flashing a stock N910F rom is it possible ?
if it is could you PLEASE, provide a flashable zip for N910F rom

Shiva758 said:
Finally it worked . Actually i am doing ( kernel) mistake .Thanks for providing direct links and for your kind help.
Click to expand...
Click to collapse
Glad to know that you finally made it to boot.

Hossam. AbdELHakim said:
what about flashing a stock N910F rom is it possible ?
if it is could you PLEASE, provide a flashable zip for N910F rom
Click to expand...
Click to collapse
I don't think that you can directly flash the stock ROM of "F variant" directly. Doing so might result in a bricked device.
My advise to you will be to carry out the procedure as stated in this thread.
The ROM provided in this thread is 99% stock so you will not face any compatibility issues.

got echoe data fix MO here I come fallow by Dr ketans data fix should apply to all roms with minor tweaks

ricohz said:
NICE
SPRINT USERS IF YOU FLASH THIS TEXT WON'T GO OUT
MMS ARE FINE TEXT COME IN BUT WON'T GO OUT
this works for him because he's using a gsm sim card
Click to expand...
Click to collapse
Will third party apps work for text?
Sent from my SM-N910P using Tapatalk

[GUIDE] [FIX] YUREKA (AO5510) Touchscreen Calibration Issue

​
Hurray! Finally, I fix the touch calibration issue; many many thanks to God who showed me the right path.
After suffering hard in last 15 days, even not getting any help from YU Officials, finally God bestowed upon me his blessings and provided me the hint to fix the issue.
What caused the Issue?
YU Televentures recently released a new batch of Yureka Plus (YU5510A-LP) devices with VoLTE feature. This created a storm in Yureka /Plus section of the forum. Some users even bricked after flashing the new firmware since it was totally different from the previous Yureka firmware. I got the backup of /system and /boot from a YU5510A-LP user. I deodexed the files and made a ROM out of it and flashed on my device to test whether it boots or not (a common process of ROM porting). It didn’t boot but it went beyond the boot logo and since the Kernel of YU5510-A didn’t have the correct display drivers for AO5510, I was getting strange characters on the screen. After that I rebooted to TWRP recovery. I was shocked the touch was malfunctioning. If I touch up it was working down, it was totally a mess.
This issue is much dangerous than bricking the device. Even if we brick, we may recover it by following @ricks guide, but with malfunctioning touchscreen phone is utterly useless. It can’t be fixed even after flashing the EMMC backup.
After that I reported to the YU Officials about the touch calibration issue, they didn’t provide any fix, but created a Warning thread regarding it. So sad.
They were even not ready to provide me the touch firmware of Yureka AO5510. They told me that they are also trying to find the cause of touch calibration issue and don’t have the required files. Here is the quote of the reply from YU Officials:
I am afraid that we don't have any files for fixing the issue. To make sure that such thing does not happen we internally test every case before releasing the software. In your case, you got the software from unknown sources and flashed it on your device with your own consent and understanding. Yes, we have devs but they work on cases which have higher reproducibility rate like the proximity sensor issue.
Click to expand...
Click to collapse
After that I analysed the YU5510A-LP VoLTE firmware and found that it was created by Coolpad, a Chinese Smartphone Company. So YU Televentures has imported not only the smartphone (YU5510A-LP) but also the firmware from Coolpad. That’s why it has some unknown bugs which the YU Offical Devs don’t know because they haven’t made the firmware. That’s why the devs didn’t have fix for touch calibration issue. YU is spending very less on service and devs, which very much disappointing. YU, an Indian brand made Yureka for tech freaks and that’s why so many devs engaged in it and even some noobish users like me became devs to raise the company above cheap Chinese brands. But now it’s status is deteriorating, it broke its partnership with Cyanogen and lost the support of so many great devs; and now it is left with some official noobish devs who are taking time like hell to provide a VoLTE patch for other users, this shows how irresponsible is the YU Company. And now it has already been provided by a YU Forum user. Even the Official YU OS is provided by our friend dev @AudioGod.
I hope my above words reaches to the YU Company and they take this criticizing in the right way and improve itself. I want to see this Indian Company rise beyond heights.
After lot of analysis and research I found that the cause of touch calibration issue was the kernel of YU5510A-LP ROM. It changed the TP-Firmware version and touch parameters of Yureka AO5510 (HD) according to Yureka YU5510A-LP (FHD) device and messed up the calibration.
This TP firmware is different in Yureka and Yureka Plus and it never changes after flashing any firmware (fastboot or ROM).
Yureka AO5510 : Each:GT970:0x1039:0x46
Yureka Plus YU5510 : Ofilm:GT970:0x1039:0x48
And mine was : Each:GT970:0x1039:0x47
Yureka (Plus) Touch Panel is manufactured by Goodix, a Chinese Touch Panel and Fingerprint Sensor company.
What didn’t fix the issue?
These are the things which didn't fix the calibration issue:
[/SIZE]
Flashing stock COS 12.1 ROM through recovery
Flashing COS 12.0/12.1 fastboot firmware
Flashing COS 12.0 CPB using YGDP tool (which threw an error of incompatible device before flashing)
Flashing all other partitons (=EMMC backup)
Using Annabathina’s Yureka Unbricking Tool
How did I find a Fix?
While surfing through internet I found a way to check the touch firmware version. Then I checked mine and also asked about it from other Yureka users. Then I searched about the firmware version and got an XDA Thread and also got to know about Goodix Touch Firmware and Goodix Firmware Upgrade Tool (GTP ADB Tool) from Elephone (another Chinese company) forum which I didn’t get from YU.
I read the XDA thread learned about the whole thing and created a Goodix TP Firmware/Config myself.
How to Fix Yureka AO5510 Touch Calibration Issue?
STEP 1: Download GtpAdbToolV1.7_20140424.zip and GT970_1039_AO5510-TP-Firmware.zip on your Windows PC and extract it. Go to the extracted folder of Gtp Adb Tool and run the GtpAdbTool.exe application. Then connect you YUREKA AO5510 to your PC (be sure USB debugging is enabled in your device). You will see the GTP ADB Tool window similar to the screenshot below:
​
STEP 2: Now click on the button as indicated in the screenshot below and navigate for the GT970_1039_AO5510-TP-Firmware.cfg file (that you extracted in Step 1) and select it.
​
STEP 3: Then click on the button indicated in the screenshot below to execute firmware upgrade process. Once completed, you can unplug your device and reboot. Voila touchscreen issue fixed!
​
NOTE (Important):
If the GTP ADB Tool doesn't detect your device or TP firmware, then flash any of the following ROMs:
Official Lineage OS ROMs
Hexagon ROM by @MoreSushant48
Or any other ROM
OR
Go to TWRP Recovery and mount all the partitions. Then connect your phone to the PC. It should detect.
If any of the above methods doesn’t work then try flashing
CoolUI 6.0 for YUREKA (Test build): https://www.androidfilehost.com/?fid=457095661767103935
(After flashing this ROM you may see a 'root' indication on YU LOGO, but you can fix that using Annabathina's Tool)
Important Files
GTP ADB Tool: https://www.androidfilehost.com/?fid=385035244224387037
YUREKA AO5510 TP Firmware: https://www.androidfilehost.com/?fid=385035244224387256
More information: https://www.osbusters.net/2016/10/fix-yureka-ao5510-touch-calibration-issue.html
Credits
Special thanks to @iamreal2 (XDA member) and @Ethan (Elephone forum member)
Special thanks to @darshan1205, @ricks and @Men_in_black007 who supported me in bad times
Special thanks to @manis99 for providing me YU5510A-LP VoLTE Firmware
Special thanks to @prasoon Mehra for providing me original Yureka AO5510 TP Config.
And finally thanks to me for making this fix.

Original TP Firmware Files for Different Devices
These are Original Stock Touch Panel Firmware/Configs for users who are suffering calibration issue not due to VoLTE firmware but due to other unknown causes.
YUREKA (AO5510) : https://www.androidfilehost.com/?fid=457095661767104421 (Thanks to @Prasoon Mehra)
YUREKA PLUS (YU5510) : https://www.androidfilehost.com/?fid=385035244224388338 (Thanks to @darshan1205)
Users of other YU Devices may share their working TP Firmware to help others....
Mirror Links
https://mega.nz/folder/Z4ckFbDA#bw4HnjUntLbiOLcdT-qpLQ (MEGA)

[Guide] How to Backup or Edit Touchscreen Firmware using GTP ADB Tool (For all devices with Goodix touchscreen)​For users of all devices. Backing up the current TP-firmware is useful for saving the device from any future accident.
STEP 1: Download GTP-ADB-Tool Zip on your Windows PC and extract it. Go to the extracted folder and run the GtpAdbTool.exe application. Then connect your smartphone to your PC (be sure USB debugging is enabled in your device). You will see the Gtp Adb Tool window similar to the screenshot below:
STEP 2: Now click on the Menu item as indicated in the screenshot below:
STEP 3: Now you will see a window similar to the screenshot below. Click on the indicated button to read the current TP configuration from your connected device.
STEP 4: Hereafter you will see a window similar to the screenshot below. Take a screenshot of your current window and click on the button indicated to export your current config. Save the resultant config file to your preferred place. Thereafter, if required, you can also edit the firmware by playing with the Hex values.
STEP 5: Upload the Screenshot and your exported config file and save it in a safe place. That's it.

Hello nitesh9,
I am also having the same issue and tried above steps.
My phone is not getting detected. in the GTP tool. My Phone is rooted and running STOCK ROM..
it is getting connected in stock rom and GTP tool recognize it in ADB mode but not detecting TP chipset and IC version.
as you instructed , I downloaded nuclearom and tried to install it via CWM_recovery but installation is getting aborted showing error "System7".
ANY OTHER IDEA TO GET THIS DETECTED. PLZ HELP.. ALSO , I REALLY APPRECIATE YOUR EFFORT SHARING THIS KNOWLEDGEBASE.

shailesh1985 said:
Hello nitesh9,
I am also having the same issue and tried above steps.
My phone is not getting detected. in the GTP tool. My Phone is rooted and running STOCK ROM..
it is getting connected in stock rom and GTP tool recognize it in ADB mode but not detecting TP chipset and IC version.
as you instructed , I downloaded nuclearom and tried to install it via CWM_recovery but installation is getting aborted showing error "System7".
ANY OTHER IDEA TO GET THIS DETECTED. PLZ HELP.. ALSO , I REALLY APPRECIATE YOUR EFFORT SHARING THIS KNOWLEDGEBASE.
Click to expand...
Click to collapse
Many Thanks to all of you guys.... who have put their efforts a lot.
finally I succeed to repair touch for Yureka. but in little bit different way.
GTP tool was not working in both the custom ROM mentioned above. hence I started in recovery mode and mounted everything, immediately it detected the TP IC and its version and then I flashed the config. and... its done.

shailesh1985 said:
Many Thanks to all of you guys.... who have put their efforts a lot.
finally I succeed to repair touch for Yureka. but in little bit different way.
GTP tool was not working in both the custom ROM mentioned above. hence I started in recovery mode and mounted everything, immediately it detected the TP IC and its version and then I flashed the config. and... its done.
Click to expand...
Click to collapse
I am glad that it worked for you...
BTW you better use TWRP Recovery to flash newer ROMs. CWM Recovery is very old and is abandoned and deprecated.

Hello Sir, does it works with Yureka plus device also? My devices half touch only works after updating to lollipop. Please help me. I can't use my device. Thanks in Advance, please reply as soon as possible.

dhrtlockeroo9 said:
Hello Sir, does it works with Yureka plus device also? My devices half touch only works after updating to lollipop. Please help me. I can't use my device. Thanks in Advance, please reply as soon as possible.
Click to expand...
Click to collapse
Added Yureka Plus TP firmware to the second post...Use that.
Sent from my YUREKA using Tapatalk

nitesh9
nitesh9 said:
Added Yureka Plus TP firmware to the second post...Use that.
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
Can I flash this file via fastboot I can't use my device to enable USB debugging mode because of touch malfunctioning. Please suggest me any other way to flash file sir & Thanks a lot for helping me Sir.

dhrtlockeroo9 said:
Can I flash this file via fastboot I can't use my device to enable USB debugging mode because of touch malfunctioning. Please suggest me any other way to flash file sir & Thanks a lot for helping me Sir.
Click to expand...
Click to collapse
Are you able to go into TWRP recovery?
If yes then mount all the partitions and then try the method.
You can also use mouse on OTG to use the phone.
Sent from my YUREKA using Tapatalk

Sorry Sir, every time when while I tried to install TWRP is stuck always & once I succeeded but Touch not works for me I don't know why? Downloaded my own device 5510A TWRP but than also it's not responding like that. Can you tell me whole process to flash TWRP with TWRP IMG file for my Yureka plus device?

dhrtlockeroo9 said:
Sorry Sir, every time when while I tried to install TWRP is stuck always & once I succeeded but Touch not works for me I don't know why? Downloaded my own device 5510A TWRP but than also it's not responding like that. Can you tell me whole process to flash TWRP with TWRP IMG file for my Yureka plus device?
Click to expand...
Click to collapse
Flash twrp through fastboot. Or use Yuware: https://drive.google.com/file/d/0B4X6UMHVd-NKTDQxdTBqaHlLb2M/view?usp=sharing
Sent from my YUREKA using Tapatalk

nitesh9
nitesh9 said:
Are you able to go into TWRP recovery?
If yes then mount all the partitions and then try the method.
You can also use mouse on OTG to use the phone.
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
nitesh9 said:
Flash twrp through fastboot. Or use Yuware: https://drive.google.com/file/d/0B4X6UMHVd-NKTDQxdTBqaHlLb2M/view?usp=sharing
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
Tried but TWRP touch also malfunctioning. I can't use it properly. ???

dhrtlockeroo9 said:
Tried but TWRP touch also malfunctioning. I can't use it properly. ???
Click to expand...
Click to collapse
Tried using OTG mouse?[emoji15]

nitesh9 said:
Tried using OTG mouse?[emoji15]
Click to expand...
Click to collapse
iS it possible if I flashed wrong firmware than also touch malfunctioning? But I flashed CM 12.1 official ROM.

dhrtlockeroo9 said:
iS it possible if I flashed wrong firmware than also touch malfunctioning? But I flashed CM 12.1 official ROM.
Click to expand...
Click to collapse
What is your device...Wrong may cause the issue... Fastboot error also may cause the issue. It can also be a hardware issue...
If the given method doesn't help then it must be a hardware issue. You must contact YU Service / Care.
Sent from my YU5510A using Tapatalk

nitesh9 said:
What is your device...Wrong may cause the issue... Fastboot error also may cause the issue. It can also be a hardware issue...
If the given method doesn't help then it must be a hardware issue. You must contact YU Service / Care.
Sent from my YU5510A using Tapatalk
Click to expand...
Click to collapse
I Have Yureka plus 5510A device. I don't know what happed my device again hard bricked. I don't know how to recover back. I tried QFil fastboot recovery but always getting error Sahara download failed.

dhrtlockeroo9 said:
I Have Yureka plus 5510A device. I don't know what happed my device again hard bricked. I don't know how to recover back. I tried QFil fastboot recovery but always getting error Sahara download failed.
Click to expand...
Click to collapse
Have you Yureka Plus Stock LP Edition with VoLTE and you are trying to flash CM in it?

nitesh9 said:
Have you Yureka Plus Stock LP Edition with VoLTE and you are trying to flash CM in it?
Click to expand...
Click to collapse
No it's KitKat version.

dhrtlockeroo9 said:
No it's KitKat version.
Click to expand...
Click to collapse
Still you are getting bricked now and then?
What are you flashing actually?

Redmi 2(1Gb ram,8gb storage,2014818 model indian variant)

I have a redmi 2 as mentioned in the title, i have rooted it and using it. i tried flashing all custom roms, from lolipop to nougat. it doesnt seem to respond properly, too many random reboots, or bootloops.
so i wanted to flash the stock firmware and downloaded from mi website. I am unable to get my phone detected on the mi flash what so ever. really would appreciate if i can get some help, to flash fastboot rom. also some method to flash a good daily driver custom rom (volte support is not mandatory) just LTE working is fine.
i have other devices where i am able to tinker, except this. I flashed a redmi note3 recently too, but not able to get this redmi2 appear on mi flash.
thanks in advance

I think i can help you.
First uninstall mi flash
Assuming that you are using windows 8.1 or above, you first have to set the test signing mode off.
Press Start->Search->cmd then right-click on it and click Run as administrator. In the CMD window type this
bcdedit /set testsigning on
and press enter. Restart PC.
Now reinstall mi flash again. when installing there might be 3 - 4 warnings about installing unsigned drivers. install them anyway.
Now connect your Redmi 2 in fastboot mode. connect it with a proper usb cable to the system and then open mi flash. Press refresh on the mi flash application. Your device must be listed.
If not press start and select restart while holding down the shift button. Then select troubleshooting. In the advanced startup menu, select startup settings. Press restart. In the coming boot options menu, press 7 or f7. Now open mi flash and press refresh. Device must now be listed. hope it helps.
As for a daily driver rom, i would suggest cyanogenmod 14.1 nightly on 25.12.2016( the last nightly date ). VOLte works in my device. It will if you have flashed the lollipop firmware on your phone previously.

SankarWayne said:
I think i can help you.
First uninstall mi flash
Assuming that you are using windows 8.1 or above, you first have to set the test signing mode off.
Press Start->Search->cmd then right-click on it and click Run as administrator. In the CMD window type this
bcdedit /set testsigning on
and press enter. Restart PC.
Now reinstall mi flash again. when installing there might be 3 - 4 warnings about installing unsigned drivers. install them anyway.
Now connect your Redmi 2 in fastboot mode. connect it with a proper usb cable to the system and then open mi flash. Press refresh on the mi flash application. Your device must be listed.
If not press start and select restart while holding down the shift button. Then select troubleshooting. In the advanced startup menu, select startup settings. Press restart. In the coming boot options menu, press 7 or f7. Now open mi flash and press refresh. Device must now be listed. hope it helps.
As for a daily driver rom, i would suggest cyanogenmod 14.1 nightly on 25.12.2016( the last nightly date ). VOLte works in my device. It will if you have flashed the lollipop firmware on your phone previously.
Click to expand...
Click to collapse
thanks for your reply...would definitely give a try....i mean im still on stock miui based on kitkat, havent flashed the lolipop firmware. I am running on windows 10, but what is the settings you recommended me to change on startup? i dint get that one. . . .
thanks in advance

I tried all the procedures, reflashed the stock firmware..and then booted with the latest cm14.1 nightlies..still my phone keeps on rebooting every 1min..
is it because of volte?i come from stock miui without volte enabled, and dont want either. i need a very stable rom like miui. . .but lighter one.
just in case i forgot to mention..i have the Redmi2 without volte, and 1 gb variant.
thanks in advance

srinikethan1392 said:
I tried all the procedures, reflashed the stock firmware..and then booted with the latest cm14.1 nightlies..still my phone keeps on rebooting every 1min..
is it because of volte?i come from stock miui without volte enabled, and dont want either. i need a very stable rom like miui. . .but lighter one.
just in case i forgot to mention..i have the Redmi2 without volte, and 1 gb variant.
thanks in advance
Click to expand...
Click to collapse
Do you got any custom rom without reboot issues?

RomEveryday said:
Do you got any custom rom without reboot issues?
Click to expand...
Click to collapse
nope...tough luck.,...havent got a single one running..so back on stock..desperately need one custom build running on it..

srinikethan1392 said:
nope...tough luck.,...havent got a single one running..so back on stock..desperately need one custom build running on it..
Click to expand...
Click to collapse
Mine is also the same version, i have tried validus, tesla, lineage os(installed rn working fine),RR didn't faced any random reboots.
Try to flash the redmi 2/prime firmware via boot-loader don't use mi flash flash via adb/fastboot if possible don't use custom kernel.
and a different battery if possible.
Tip:- remove sim cards before flashing and format data via TWRP then wipe every thing except micro sd. And don't restore back-up created via Titanium backup either via update.zip or from app (some roms don't support so the device keeps restarting)

incrysis said:
Mine is also the same version, i have tried validus, tesla, lineage os(installed rn working fine),RR didn't faced any random reboots.
Try to flash the redmi 2/prime firmware via boot-loader don't use mi flash flash via adb/fastboot if possible don't use custom kernel.
and a different battery if possible.
Tip:- remove sim cards before flashing and format data via TWRP then wipe every thing except micro sd. And don't restore back-up created via Titanium backup either via update.zip or from app (some roms don't support so the device keeps restarting)
Click to expand...
Click to collapse
Mine is the same model and for me everything works fine.And volte works bcz i fastbooted miui 8 lollipop.I have tried the same roms as you mentioned but whenever i place a call through volte it restarts.Sometimes it reboots after the call and sometimes when placing a call.Can't able to solve this annoying problem so i am back to miui bcz this is my primary device.But i hardly want naugat :crying:

Did you tired to repartition your device or use of custom kernel or any mod? Try to use another battery i think it might be creating prob. I will provide you proper link for fast boot firmware which i used. Might help you then you can try custom rom. Feel free to ask any question

incrysis said:
Did you tired to repartition your device or use of custom kernel or any mod? Try to use another battery i think it might be creating prob. I will provide you proper link for fast boot firmware which i used. Might help you then you can try custom rom. Feel free to ask any question
Click to expand...
Click to collapse
I normally flash fastboot rom via miflash.Is it ok?And i never remove the sim when flashing roms.(both custom and stock)

RomEveryday said:
I normally flash fastboot rom via miflash.Is it ok?And i never remove the sim when flashing ROMs.(both custom and stock)
Click to expand...
Click to collapse
Yes its Okay but select flash all option, you should try to flash removing sim cards and memory card i strongly recommend. You can keep memory card while flashing custom ROMs.

Bhavesh_khatri said:
Yes its Okay but select flash all option, you should try to flash removing sim cards and memory card i strongly recommend. You can keep memory card while flashing custom ROMs.
Click to expand...
Click to collapse
I think this may fix the reboot problem.Now i performed a super clean method of flashing. And can you explain why it is important to remove sim/memory cards while fastboot and flashing?