Hi everyone,
this is my first post, hoping to don't break some rule
sorry for may not so perfect english
I spent last two days searching info and threads in the forum but no luck.
I own two Galaxy S2, one is for research and modding ^_^ the other one is for stock use and work.
all of two were branded H3G Italy.
the one i use for testing is an MP1.300, actually it has the CBR AOSP ROM
and everyting go smooth apart from some little bug I'm notifying the author 89luca89.
In the past month i flashed various rom, official and modded, and all went like a charm.
Now the second phone: it was a stock 2.3.5 H3G branded phone, everything was ok (apart a problem i will explain later)
two days ago i updated the phone using kies and got the ICS 4.0.3 H3G, everything went well but after the restart the phone didn't recognize the sim, i tryied reflashing wiping rooting triple wiping unrooting etc and then i discovered two strange beaviors:
1) i was wrong, the sim GET RECOGNIZED from the phone but if there is the pin protection active the phone don't shows the unblocking request so no gsm network at all, if i remove the pin protection from the sim the phone works normally.
2) the power button now switch off the phone without show the power menu with the classic fly mode - data on/off reset shutdown etc.
To be shure it was a software problem and not an hardware one i flashed on this phone the CBR AOSP ROM and the phone worked normally with or without the pin, the power menu is ok and so on.
the strange thing is... the hardware model of the phone is MP 0.600 inspite of classic MP1.200 or 1.300.
now i'm asking you some tips... and i'm curious if someone can explain me that strange HW model (MP 0.600)
Now the aforementioned problem
this strange beavior already happened some months ago and after some days the phone didn't switch on at all so i send everything at service center and the phone returned me simply reflashed with 2.3.5 (the same rom it has when the problem appeared the first time.
Probably there is a strange behaviour with the hardware but i'm wondering why the AOSP rom work well..
I forgot to write that the IMEI is correct and that the sim works well in other phones and other sims show the same beaviour on the unlucky phone
all the roms ICS AOSP e AOKP works well, only official stock samsung ICS (H3G XEU XEN etc.) show the problem.
finally i flashed various modem but nothing changes.
sorry again for my bad english.
CU
Luca "silverjingle"
in another post someone asked me how i saw the hardware version of my phone...
following the procedure i used (simply used service code...)
from the dialer insert the code
*#*#197328640#*#
then press:
[2] version info
then
[1] SW VERSION -> [5] READ ALL SW VERSION
(i can't post external link so cut, modify and paste the link in you browser...)
i46 dot tinypic dot com/w2ocx1.png
or
[2] HW VERSION -> [1] READ HW VERSION
i46 dot tinypic dot com/oh8zkp.png
No Idea?
it's possible that no other people had such issue?
I remember some month ago someone writing about the problem of the power menu disappeared... but I'm not able to find that thread...
So no luck...
Luca "Silverjingle"
silverjingle said:
No Idea?
it's possible that no other people had such issue?
I remember some month ago someone writing about the problem of the power menu disappeared... but I'm not able to find that thread...
So no luck...
Luca "Silverjingle"
Click to expand...
Click to collapse
Search for /efs/imei/keystr file fix.
WOW
I replaced the file keystr and now the long press of the power botton
shows the standard menu and...
the phone is requesting to insert the pin at boot for the sim.
Now the strange thing is that this normally happen AFAIK when you flash
and reflash and do something wrong with firmwares and wipes...
the strange thing is that this phone was stock, not rooted...
(now i rooted the phone to restore the file and to try with other firmwares tnah original).
i noticed in the efs folder there are other missing files respect another phone
but I don't know if they are files created on the fly in special cases.
(I noticed the file mps_code.dat contains the product code and varying after a flash and one or two wipe)
There is some guide to learn the use of every single file in the efs folder?
and... why aosp roms function well even without that file in the efs folder?
I think it would be interesting try to discover whats is causing such behaviour.
so, thanks and.. set this thread as resolved
Luca "Silverjingle"
Hey Guys I am really impressed about the device named goophone but in real according to the stock launcher it is a kuphone.
So first i can not image who this price is possible but good i accept
for only 70€ including dhl and some cases
So as second some information about this device:
Specs according to Shop: (dhgate)
Model i5C
Band 2G: GSM 850/900/1800/1900MHz
Sim Card Single SIM, Single standby (Micro SIM Card)
Shell Material Plastic
OS Android 4.2
CPU MTK6572, Cortex A7 dual core, 1.2GHz
ROM 4GB
RAM 512MB
Display Size 4.0 Inch
Type TFT, Capacitive touch screen
Resolution 800 x 480 pixels
FM Radio Yes, earphone needed
Earphone Port 3.5mm
Card Extend Support TF card up to 64GB extended
Camera/Picture Resolution Dual Cameras, front camera 2.0MP, back camera 2.0MP with flashlight, up to 1600 ×1200 pixels resolution
GPS Yes
WIFI Yes, 802.11 b/g/n
Bluetooth Bluetooth 2.0
Dimensions 124 x 60 x 8.9 mm
Net Weight(Including battery) 117g
So why i am creating a new thread ?
I observed that there are some bugs and the launcher is so slow and not really i0S7
I also noticed that some other i5c clones have better launcher, so possible to port some systemapps ?
I am not a developer but i can find some recouces for the phone
I also can upload my current rom( but how )
So if you have questions or have the same phone please support his thread for any roms :
You know if we dont care for this noone will do , and for this price, a softwaresupport from manufactor, it is a prank /fool
Sorry for my not ideomatic english , i am german
So stay unhurt and be happy ^^
KiPhone , GooPhone ! KuPhone
Hi ,i own a Goophone i5c , but i thing there is more a Kiphone i5c 2g.
Anyone of you know how to change the stock launcher and set it as default ? i download a few launcher but nothing i cant set them as default launcher ! i tray even a few app like home switcher and other but nothing seem to work , now im stuck with the stock launcher KuLauncher or something like this , but this launcher is very laggy .
Thank You!
Hello I have bought a goophone i5C or a kiphone i5C
apple logo at back (seems painted)
MTK6572/512M of RAM/ photo 2MP back
come with a rom which is a mix of IOS7 and IOS6
when I try a root method on reboot It Bricked so I need a dump or the original rom to flash it under SP Flash Tool
I have tried some Flash with SP Flash Tools with some device with mtk6572 with the same spec (MTK6572 1Ghz, 512 Ram, 4G Rom, graphic Chipset Mali 400MP, ...)
SP Flash Tool work but I have a black screen with a sound with start ...
If someone can give me a dump of your goophone i5C - Kiphone i5C It will be great
there is a tuto how you can do it
http://www.needrom.com/tutorial-backup-rom-with-mtkdroidtools/
Clean rom would be great
creasqui said:
So if you have questions or have the same phone please support his thread for any roms :
Click to expand...
Click to collapse
Great initiative, I received mine yesterday (gadgetdealer phone 5c-> same specs) I already lost a whole evening with mtk droid and sp flash tools. So far I managed just to make a dump of the current rom and noticed the kulauncher apk in there besides other non wanted apk's. But none of any threads is very clear of procedures and don't want to brick it.
For root: framaroot works (select supersu). Googlecalendarsyncadapter.apk 4.2.2 was required to get de calendar working with Google. And i had do update youtube manually to get it playing videos.
Update: I tried to flash it with the Goophone i5c rom you can find in several other threads. I am not really sure if it is compatible but so far I haven't been able to start the actual flashing... it seems it cannot find the device. Already tried by putting the phone in bootloader mode... no luck (but perhaps it saved me from a brick phone). Does anybody found a way to get a better notification bar that shows icons for messages like whatsapp, gmail,play store... ? I already installed the SystemUI.apk from Goophone i5c.. it's compatible but does not change anything.
Sup guys
I just received mine one day ago and I noticed that is going veeery lagy. I just started to fight with it. If I make any progress, I'll share my results with you. Btw This thread is a great idea!!!
Regards
Hello to everybody,
I have received one phone as described (bought on DHgate).
I have root it with farmaroot: ok.
But, I can not change the launcher, I have the launcher kuLauncher.apk. I have tried with different apps: home switch, home manager, ... but any of them can erase kuLauncher as the home launcher.
Does anyone reached to change it?
I´m in the same situation, I have a KUPHONE but this model includes GPS and 3G (WCDMA - 2100 MHz). The stock ROM has several mistakes and it is very laggy. Now I have added a problem after testing 2 different SIMs: I can´t start up my smartphone with a SIM because after enter the correct PIN, the screen gets frozen and I can´t access to the system. Without SIM it works OK...
I rooted it without problems in order to make work the GPS, but I was not able to make work the 3G (I had selected WCDMA in engineer mode and It did not work) .
There is no info about this phone on internet, the codes of Goophone do not work, and I am reading that the ROMs do not work neither...
Please I need a solution! A ROM that works well on this device.
Thanks a lot in advance, :good:
I have this phone as well and would love to put a new rom on it or change the launcher. Any progress on this? I will say there are menus when holding the volume buttons down and the power button. But that's mainly recovery and some add on side loading stuff. Then there's another menu but it's in full Japanese and I can't make any of it out.
Hi guys, I recently bought a GooPhone i5C, rooted it fine with VRoot, tried to update the ROM over the weekend, and ended up bricking my device.
I had taken a backup of my GooPhone at work, and also at home. I tried restoring from a stock KuPhone ROM, but this just left my phone on the Apple logo (had to take the phone apart to get to the little button near the power switch that kills power to the phone). Once back at work on Monday morning however, I restored (loaded the scatter file then hit Download), and my phone started working again.
So in short, I have uploaded my backup if anyone wants it, although you may have to use MtkDroidTools to 'prepare' the files for flash, and then use the scatter file that this creates. I pretty much just registered to post this, so I can't post the link to the backup just yet (PM me or something?).
help! i deleted kulauncher...
ChaosEn3 said:
Hi guys, I recently bought a GooPhone i5C, rooted it fine with VRoot, tried to update the ROM over the weekend, and ended up bricking my device.
I had taken a backup of my GooPhone at work, and also at home. I tried restoring from a stock KuPhone ROM, but this just left my phone on the Apple logo (had to take the phone apart to get to the little button near the power switch that kills power to the phone). Once back at work on Monday morning however, I restored (loaded the scatter file then hit Download), and my phone started working again.
So in short, I have uploaded my backup if anyone wants it, although you may have to use MtkDroidTools to 'prepare' the files for flash, and then use the scatter file that this creates. I pretty much just registered to post this, so I can't post the link to the backup just yet (PM me or something?).
Click to expand...
Click to collapse
please can someone help me i deleted my kulauncher and now it wont start up again it just keeps showing the boot up logo
i cant reach it with usb cause it wont show anything please help me..
kuLauncher
angularpainzzr said:
please can someone help me i deleted my kulauncher and now it wont start up again it just keeps showing the boot up logo
i cant reach it with usb cause it wont show anything please help me..
Click to expand...
Click to collapse
MascioSpam94 said:
Hi guys i deleted the kuLauncher.apk and now the phone bootloop on Apple logo.
I've found that we can use adb when the phone boot in factory mode but i can't find the kulauncher.apk file on the internet.
The phone is rooted but i can't have root shell via adb.
Days ago i had a backup of the rom whit MTK tool but if i try to flash it whit SP_flash tool it return me error 8038.
Anyone can help me?
Edit: the phone came from dhgate, if you wait (bad internet connection) a week i can upload my backup for you.
Ps: mine doesn't have the external sd-card installed but near the battery there is a free micro-sd card slot
Sent from my Galaxy Note II using xda app-developers app
Click to expand...
Click to collapse
Here you go
PS. Tell me if you need the .odex file aswell
PPS. I'm working my way throught the rom to find a solution for changing the stock launcher (iLauncher is sooo much smoother on the device) It's just the launcher thats laggy the phone itself is pretty smooth
rom kuphone i5c
i need rom kuphone i5c
need help
I also have same phone, mistakenly without taking its rom backup i deleted some system files,
now my mobile stop at booting - just adroid logo apprear (not goto main screen)
I cant do any thing with it because usb debugging is also off, can any one provide me its original rom, i will be very thankful to him plus i will pay him too.
waiting please reply
Clean rom
In my quest for a clean rom i came on this one: needrom.com/mobile/ px-c5s5 . Any chances it would work on our devices? Or could it help to mix up with our original rom... Just a thought.
My biggest frustrations with this phone.
Hi, I also bought this phone (for my daughter with her money) without knowing what it was. I believe it's a kuPhone due to a folder 'Kustore' on the device and the microphone hole which is very close to the left bottom screw and further away from the audio jack than on real GooPhone.
Anyway, this phone can be bought very cheap (65eur, free shipping ) and performs well.
However I see a general problem with signal reception:
Wifi: have to be in very close range to the router, about 5m maximum.
3G: rather slow, speed test reporting max. 1Mbps.
GPS: slow locking (several minutes) and not very precise, but still usable.
FM: worse than my other devices inside the house.
Other remarks:
Audio jack only fits 3 pin headphones, 4 pins with microphone do not work well enough to be usable (low volume, shallow sound).
Camera is only 2 megapixel and show green shading under artificial light and some angles. LED flash very weak, does not help.
Microphone mute is activated accidentally when calling (by your cheek pressing the screen at the mute icon, proximity sensor does not seem to work as expected.
When you go to recent call, the caller app crashes.
512 MB memory seems to fill easily, phone blocks and need to cold boot by pressing HOME+POWER buttons together for 10 seconds
Apart from these I do not see any of the problems mentioned in this forum, UI is response and working very well.
I'm prepared to share my ROM if this is of any use to someone, but he has to explain me how. I never did such a thing.
If anyone can help to improve signal reception, welcome!
Hi guys,
I bought a similar phone but I don't know if is agophone or a kuphone.
There is any way to understand what I bought?
There is a way to change the recovery boot in English, now is in Chinese and is not easy to manage
w1r3d said:
I´m in the same situation, I have a KUPHONE but this model includes GPS and 3G (WCDMA - 2100 MHz). The stock ROM has several mistakes and it is very laggy. Now I have added a problem after testing 2 different SIMs: I can´t start up my smartphone with a SIM because after enter the correct PIN, the screen gets frozen and I can´t access to the system. Without SIM it works OK...
I rooted it without problems in order to make work the GPS, but I was not able to make work the 3G (I had selected WCDMA in engineer mode and It did not work) .
There is no info about this phone on internet, the codes of Goophone do not work, and I am reading that the ROMs do not work neither...
Please I need a solution! A ROM that works well on this device.
Thanks a lot in advance, :good:
Click to expand...
Click to collapse
I have the same problem??? any fix?
DonSaffadu said:
I have the same problem??? any fix?
Click to expand...
Click to collapse
hi guys I solve this problem by setting my date and time, and the phone work fine now!
"I can´t start up my smartphone with a SIM because after enter the correct PIN, the screen gets frozen and I can´t access to the system. Without SIM it works OK..."
I've seen this on my phone too, but it's been a while ago and I was able to fix it. It's working since. I don't remember what I did to fix it, but it was not something difficult to do, so don't despair and try a few things.
bootloader
Anyone succeed to flash a boot loader on the kuphone?
(Feel free to move this thread to anywhere where it belongs, if it's an issue. And sorry for my non-native english).
Good night for everyone,
To make it short:
- I bought an LG G2 D802 from amazon.com (description says it's a factory unlocked phone).
- Tried to install a modified kitkat rom.
- The phone bricked into fastboot mode, but then I could repair the download mode and installed a Hong Kong (without noticing it and messed up the phone, because I'm form Venezuela and it went to a Locked state) stock firmware. But couldn't repair the recovery mode.
- When the phone booted it had an apparent screen calibration problem, where it doesn't respond accurately to touch, but going to the sensor->calibrate sensor option from settings menu didn't fix the problem at all. So I think it's something related to the Android system files (partitions maybe?) and not the settings or S/W at all.
- Installed an Open kitkat firmware hoping that it would fix the issue, but with no result. It correctly changed the S/W, but the screen problem persisted.
Some ideas that I have (but haven't found any propper methot to fix the phone) are:
1. If it applies: repairing the Android system files, to fix the touchscreen problem.
2. Rooting the phone and installing the best Recovery Mode to fix the phone.
3. Wiping the phone to blank.
4. Install a correct S/W from zero.
5. Hoping that it works
If it's possible doing it from a pc software or command line (connected to the phone obviously) I think it would be the easier solution, but don't know how to do it.
I would be really grateful with anyone who reads this and can help me fixing this...
Thanks.
I hope someone has some experience of this problem, I will do my best to explain in some detail.
It is as out of the box currently running version 4.0.4 firmware.
The history, initially stock firmware version 4.0.3 was running, the USB was a little loose, so I swapped the complete pcb with another S2 I have with a faulty display, to make things a bit more complicated I also put in a 2Gb SD card, when I rebooted the problem appeared, on pressing the power button to wake up, the screen comes on to the lock screen in dimmed mode, and it will stay like it for anything from 5 to 15 seconds, then the screen will go to full brilliance and the screen can be unlocked.
What I have tried, removed and rebooted with sd card removed, swapped back the original USB pcb, and swapped back again as the problem remained, also upgraded to firmware version 4.0.4, that is more or less where I am now, the problem remains.
Have tried researching but unable to find anything relating to this problem, do you have any ideas?
Update:
After further reading, it appears the original firmware may have been customised, because I was not able to get Kies to connect with the device and the CSC was stated as 'unknown', which from what I have read indicates a custom ROM.
Having flashed the stock firmware , on the recovery menu I get still the message #Manual Mode# Appling Multi CSC.... Applied the CSC code: XEU Successfully applied multi CSC, which was also present with original firmware but it never actually applied the code as it stated CSC 'unknown'. but I can now connect with Kies and the CSC code is stated as I9100XEULPA.
Is it normal to get this message at the recovery menu?
Is it a symptom of the same lock screen delay issue?
Solved
I spent 6 weeks trying to fix this, the most aggravating of problems are sometimes very easy to cure when you know the answer!
Disable auto brightness, easy, your long wake up delay has now gone.
Let me know if it helped you.:good:
Hello,
I have a Samsung Galaxy S4 (i9505) with a strange behavior (ghost touch, mainly). Anyway, I have installed a dozen of custom ROMs (even reinstalling the stock ones) with no success.
I've noticed that no matter what ROM was currently installed, I've got the same TSP values (when running *#2663# code):
Phone's TSP FW version: SYB0085C
Part's TSP FW version: SYB0085C
Config TSP FW Version: SGH-I337_SY_0608
TSP checksum data: NA
(btw, I actually have an i-9505 model but it prints SGH-I337 , as above)
Looks like the phone software was messed up by the former owner (or by a regular update).
I've tried to wipe/format all the partitions (I'm using TWRP recovery) but the TSP firmware is still there (as the TWRP itself uses the touch screen input only).
How to actually get rid of the current TSP firmware (complete wipe/remove) so I could install another version from scratch (along with a custom ROM or such)?
Does the recovery software (TWRP) use a custom (embedded) TSP firmware? (though I got the same ghost touches in TWRP, too).
Thank you in advance for any help.
I've just installed (downgrading) another TWRP version (hoping for a non-touch driven interface - with no luck).
Anyway, while testing the new recovery interface I've noticed that the ghost touches almost disappeared (and they were present in the recovery mode, too).
After restarting the phone, I've noticed the same reduction in ghost touches (though they're still "alive") but I wonder what could have been the influence of the new (actually, older) version of TWRP on touch screen firmware (or touch screen behavior, for that matter)?
Does the recovery software (TWRP) use it's own touch screen firmware and did it actually rewrite the former TSP firmware version?
Any ideas, please?
I've made some progress on chasing the TSP firmware.
I found that the "apnhlos" (by-name) partition is mounted as /firmware during regular operation (but was not mounted during recovery). Hence I have mounted it then I found out its content:
Code:
keymaste.b00 q6.b00 skmm_ta.b03 tima_key.b03 tima_pkm.b03 vidc.b03
keymaste.b01 q6.b01 skmm_ta.mdt tima_key.mdt tima_pkm.mdt vidc.mdt
keymaste.b02 q6.b03 tima_atn.b00 tima_lkm.b00 tzapps.b00 wcnss.b00
keymaste.b03 q6.b04 tima_atn.b01 tima_lkm.b01 tzapps.b01 wcnss.b01
keymaste.mdt q6.b05 tima_atn.b02 tima_lkm.b02 tzapps.b02 wcnss.b02
mc_v2.b00 q6.b06 tima_atn.b03 tima_lkm.b03 tzapps.b03 wcnss.b04
mc_v2.b01 q6.mdt tima_atn.mdt tima_lkm.mdt tzapps.mdt wcnss.b05
mc_v2.b02 skmm_ta.b00 tima_key.b00 tima_pkm.b00 vidc.b00 wcnss.mdt
mc_v2.b03 skmm_ta.b01 tima_key.b01 tima_pkm.b01 vidc.b01
mc_v2.mdt skmm_ta.b02 tima_key.b02 tima_pkm.b02 vidc.b02
Now that's the true challenge: which one is the TSP firmware (if any)?!
Any help, please?
I'm in the twilight zone, really.. I've tried to delete the whole content of "apnhlos" aka "/firmware" aka "/dev/block/mmcblk0p1" while in recovery mode, it shows an empty partition but after reboote the whole content is back!
I've even tried to format it (mkfs.vfat /dev/block/mmcblk0p1), it looks empty afterwards but then again, the data is back after reboot.
Now I really need some help.. how to actually get rid of that partition content?
Any help, please? I'm running out of ideas..
Meanwhile, my sensor hub (software) has broken, too (no sensor is working nor detected) hence I need to reflash that sensorhub firmware too.
I've tried the "*#2663#" method but it fails when I'm trying to update SENSORHUB.
I've flashed a lot of stock ROMs (using Heimdall tool) but no one seems to change the TSP or SENSORHUB firmware.
Are they stored on kenrnel or something?
Hi guys,
Still no luck on my quest of replacing my phone's touch screen driver.
I found the location of the driver (/sys/bus/i2c/drivers/synaptics_rmi4_i2c) but I don't know how to disable it (for testing purpose only) or how to actually replace it.
For instance, does anyone know how to disable (or unbind de touch screen device from the aforementioned driver) using an adb (shell) command?