spen issue on note n7000 - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hello folks, I post this thread after months of research and 2 kernel flashing:
I'm having an issue with the S-pen of my galaxy note n7000: it doesn't work, but I noticed the following :
- It works perfectly after a reboot for a moment, but when I turn the screen off and then when I turn it on a moment after : no response.
- the bug started after I updated my phone from GB to ICS. Now I flashed it to JB 4.2.2 and the problem still continue.
Here's the specs (as it's written on my phone) :
Band Version : n7000XXLT3
Core Version : 3.0.31 [email protected] #1
CM Version : 10.1-20130508-Asylum-n7000
Build Number : cm_n7000-userdebug 4.2.2 JDQ39E
eng.chasmodo.20130508.06 5158 test-keys
Could somebody could give a tip on how to fix it ? I found numerous threads about "hovering spen" not working but that's not my problem. Neither a screen detection issue (well, I don't think so.)
I would really apreciate if somebody could help me with Gnote who is not a Gnote anymore
Thanks a lot for the responses !!!

elsaphnite said:
Hello folks, I post this thread after months of research and 2 kernel flashing:
I'm having an issue with the S-pen of my galaxy note n7000: it doesn't work, but I noticed the following :
- It works perfectly after a reboot for a moment, but when I turn the screen off and then when I turn it on a moment after : no response.
- the bug started after I updated my phone from GB to ICS. Now I flashed it to JB 4.2.2 and the problem still continue.
Here's the specs (as it's written on my phone) :
Band Version : n7000XXLT3
Core Version : 3.0.31 [email protected] #1
CM Version : 10.1-20130508-Asylum-n7000
Build Number : cm_n7000-userdebug 4.2.2 JDQ39E
eng.chasmodo.20130508.06 5158 test-keys
Could somebody could give a tip on how to fix it ? I found numerous threads about "hovering spen" not working but that's not my problem. Neither a screen detection issue (well, I don't think so.)
I would really apreciate if somebody could help me with Gnote who is not a Gnote anymore
Thanks a lot for the responses !!!
Click to expand...
Click to collapse
have you tried the official stock 4.1.2 rom?

I would say even before answering above question, have you done a factory reset? (Be on a safe kernel of course)
Sent from my GT-N7000 using Tapatalk 2

yes, when Jellybean went out, I updated my phone hoping it would ok but no amelioration
and when I installed the last rom, I changed also the kernel and following the installation instructions, I did a full wipe and a dalvik cache. It is comparable to a factory reset ?
The only tips I figured out is that it could be a process or an application running on startup that would block the spen, but I'm a noob at it. Could somebody confirm or not ?

elsaphnite said:
yes, when Jellybean went out, I updated my phone hoping it would ok but no amelioration
and when I installed the last rom, I changed also the kernel and following the installation instructions, I did a full wipe and a dalvik cache. It is comparable to a factory reset ?
The only tips I figured out is that it could be a process or an application running on startup that would block the spen, but I'm a noob at it. Could somebody confirm or not ?
Click to expand...
Click to collapse
i suggest you download latest firmware from sammobile.com and flash using pc odin...

Mayank Chandwani said:
i suggest you download latest firmware from sammobile.com and flash using pc odin...
Click to expand...
Click to collapse
This advise is not going to help as it wont wipe the proper partitions. Dont follow that advise.
-----
Here is what you should Do. If this doesn't work, you 100% have damaged hardware and it is not a software problem.
1. Download latest philz kernel and latest prerooted and deodexed jellybean LT5 ROM in flashable zip format. Any ROM of your choice will do. Just make sure its a flashable zip or you will be stuck with no ROM and forced to flash a tar via PC Odin.
2. Flash philz from your external SD card if you don't have a stock recovery or using Mobile odin.
3. Reboot to philz touch recovery
4. Do a nandroid backup just in case
5. Wipe data system dalvik cache preload and .androidsecure
6. Flash the LT5 zip
7. Reboot to system and test spen
If it doesn't work after that it IS your hardware or the pen itself.

asf58967 said:
This advise is not going to help as it wont wipe the proper partitions. Dont follow that advise.
-----
Here is what you should Do. If this doesn't work, you 100% have damaged hardware and it is not a software problem.
1. Download latest philz kernel and latest prerooted and deodexed jellybean LT5 ROM in flashable zip format. Any ROM of your choice will do. Just make sure its a flashable zip or you will be stuck with no ROM and forced to flash a tar via PC Odin.
2. Flash philz from your external SD card if you don't have a stock recovery or using Mobile odin.
3. Reboot to philz touch recovery
4. Do a nandroid backup just in case
5. Wipe data system dalvik cache preload and .androidsecure
6. Flash the LT5 zip
7. Reboot to system and test spen
If it doesn't work after that it IS your hardware or the pen itself.
Click to expand...
Click to collapse
You really seem to be sure of you, cowboy!! OK I will try it as soon as I finished this message an d I'll tell you about it.
Thanks !

The theory is pretty simple... If you wipe out all traces of the past firmware, and the problem persists with new firmware, it is the hardware causing the issue.
Sent from my Samsung Galaxy SV using Tapatalk 3

asf58967 said:
The theory is pretty simple... If you wipe out all traces of the past firmware, and the problem persists with new firmware, it is the hardware causing the issue.
Sent from my Samsung Galaxy SV using Tapatalk 3
Click to expand...
Click to collapse
I agree to the principle : putting the cleanest installation, it's ok for me.:good:
now, I found those data:
http://forum.xda-developers.com/showthread.php?t=2274152&highlight=lt5
http://d-h.st/users/philz_touch/?fld_id=16061#files (PhilZ-cwm6-v5.03.0)
Could somebody tell me if they're effectively compatible and if it's OK to flash those without risk ?
I can't wait to see my Spen running again !

Hi!
I have exactly the same problem. I'm on a CM 12.1 and when I install it, after the first boot, Spen is working for a couple of seconds (10-20) and then suddenly stops (I presume there is something in the software that disable it). Then I reinstall CM 12.1 and same story again - it works for 10-20 seconds and then stops. Spen is working ONLY on the first run (not after every reboot).
Can it be the problem related to the kernel version?

georgekg said:
Hi!
I have exactly the same problem. I'm on a CM 12.1 and when I install it, after the first boot, Spen is working for a couple of seconds (10-20) and then suddenly stops (I presume there is something in the software that disable it). Then I reinstall CM 12.1 and same story again - it works for 10-20 seconds and then stops. Spen is working ONLY on the first run (not after every reboot).
Can it be the problem related to the kernel version?
Click to expand...
Click to collapse
When you say it stops working, does it mean it will give not response at all? I have tried spen on cm12. 1 and cm13 night owl and works on both.

Unfortunately yes - no response at all. It works fine for just about 10 or 20 seconds and then stops. I thought that it may be a hardware problem (maybe capacitors were empty), but in that case Spen will not work at all. And it works only when I do a factory reset or reinstall ROM. Weird...
Yes I red many posts where users said that Spen is working with night owl ROMs but I have this problem. And still didn't found any solution.

georgekg said:
Unfortunately yes - no response at all. It works fine for just about 10 or 20 seconds and then stops. I thought that it may be a hardware problem (maybe capacitors were empty), but in that case Spen will not work at all. And it works only when I do a factory reset or reinstall ROM. Weird...
Yes I red many posts where users said that Spen is working with night owl ROMs but I have this problem. And still didn't found any solution.
Click to expand...
Click to collapse
Did you ever find out was happened with your spen?
Yesterday I noticed this problem on my note. I thought it could be the latest kernel i've had flashed, so I flashed another one. I rebooted, tested my spen and everything was good, so I forget about it. But today my spen is not working at all. I wiped my phone and reinstalled the same rom and it worked at first, but then stopped working forever (I flashed a kitkat rom, then a touchwiz, and it never worked again). I don't know anyone else with this phone so I cannot test if it is the spen :/

Unfotunately not. I stopped thinking about it. I tought to buy new Spen from AliExpress (not expencive solution) and try it...

Related

[Q] [HELP] How to fix and identify my GT-i9000?

Hello World!
let me first explain my problem :
i got a GT-i9000 (Samsung Galaxy S) from my friend.
the device already installed with custom ROM (lidroid if i'm not mistaken).
problem is, many features of this sweet device is not working :
sound not working at all (no sound coming out from speakers and 3.5mm jack)
the accelerometer are inverted (tilting the phone up makes the ball on 'calibration' go right)
so i tried to install CM7, and then CM9 on this device.
but now all of the soft buttons doesn't work. (all 3 buttons doesn't work at all)
PLUS all the problems i described above.
i tried installing custom kernel for CM7/CM9
but the problem still there.
and then, i tried to install a stock ROM from samfirmware.
but i don't know what my device is from.
apparently, the box are missing too..
i already tried updating the phone software with Kies, but it always stuck at "connecting phone.."
oh, and strangely, the Baseband part of the about phone is always shown as "Unknown"..
is it has something to do with modem?
Sounds weird. I would suggest a complete reset/wipe and a flashing of a stock ROM (e.g. from Sammobile). Be sure you wipe anything, including dalvik cache and cache partition.
I think you may have a damaged I9000.
To be sure, try again flashing Samsung ROM from Samfirmware (important! with 'repartition' and 'bootloader update' options).
I recommend XXJVT 3-file.
Try to flash it to its stock ROM using your current location, if that's what you're problem, location shouldn't be a problem for now, you should try to make it work first. Then if all else fails, I think you gotta return that phone to your friend coz the ROMs you mentioned should be working properly (unless you didn't wipe your cache).
opt1user said:
I think you may have a damaged I9000.
To be sure, try again flashing Samsung ROM from Samfirmware (important! with 'repartition' and 'bootloader update' options).
I recommend XXJVT 3-file.
Click to expand...
Click to collapse
yes, i thought so too..
can you give me the links? i really confused with what i must download from samfirmware..
mvfajarda said:
Try to flash it to its stock ROM using your current location, if that's what you're problem, location shouldn't be a problem for now, you should try to make it work first. Then if all else fails, I think you gotta return that phone to your friend coz the ROMs you mentioned should be working properly (unless you didn't wipe your cache).
Click to expand...
Click to collapse
well, i want to connect my phone and update it through Kies, but the phone is always stuck at "connecting device"..
oh, and one more thing.. can changing ROM breaks the hardware of a phone?
you can use this tutorial (and files within) to flash to a stock rooted rom + CWM .
http://forum.xda-developers.com/showthread.php?t=1494493
If you wanna keep it stock just dont flash the ICS rom they're talking about in the topic ,use odin and thats it .
edit : changing roms cant break the hardware (as far as i know,unless ofc there are some features that force hardware over their limit ,for example if you force the audio volume too much your speakers will start making noises when playing music) ,though it can rarely brick the phone (if you rly mess up or odin crashes while flashing )
rekatluos said:
you can use this tutorial (and files within) to flash to a stock rooted rom + CWM .
http://forum.xda-developers.com/showthread.php?t=1494493
If you wanna keep it stock just dont flash the ICS rom they're talking about in the topic ,use odin and thats it .
edit : changing roms cant break the hardware (as far as i know,unless ofc there are some features that force hardware over their limit ,for example if you force the audio volume too much your speakers will start making noises when playing music) ,though it can rarely brick the phone (if you rly mess up or odin crashes while flashing )
Click to expand...
Click to collapse
yes. this is exactly what i do after i installed CM9.
i forgot to add this on my first post..
um, so now my device is using i9000XWJVZ. and the baseband is still showing "unknown", and those 2 problems i described above are still there..
any ideas?
baseband version = modem (if im not mistaken) . flash another modem maybe? i have baseband version I9020AUCKF1 (nexus modem)
hmm...we should make a test to make sure the hardware is working allright. Download Andro Sensor and see what accelerometer sensor says (do this with all roms).
Sent from my GT-I9000 using XDA
laehtis said:
hmm...we should make a test to make sure the hardware is working allright. Download Andro Sensor and see what accelerometer sensor says (do this with all roms).
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
i've just downloaded the app and the sensors are working just fine. it just.. inverted..
sionirvine said:
i've just downloaded the app and the sensors are working just fine. it just.. inverted..
Click to expand...
Click to collapse
Okay good to know that hardware isn't probably broken. Hmm...add me on google talk [email protected]
let's solve your problems!
Sent from my GT-I9000 using XDA

[Q] (NEED HELP) Phone restart itself into recovery after installing ICS/JB ROM's

Hi Seniors,
This became like a mystery for me..please help me to solve it.
Issue is like this if I install any custom or stock Gingerbread ROMS by phone works like a butter, no issue at all I can say.
But when I install any ICS or JellyBean ROM's it starts creating pain in my neck.
If I am using my phone it never restarts itself but when I lock my phone screen and keep it my pocket M finding that my phone is restarting into recovery mode itself.
Now here comes the strange part...If I play music using any music player and lock my screen it works fine,its not restarting itself ...but once I stop that music player and lock my handset screen in idle mode it goes to recovery in few secs
This only happens if I upgrade to ICS or JellyBean ROM's
One more issue...my wifi works fine If am having GingerBread install on my phone but when I install ICS/JB I cant even start it.
Have tried a lot to get it fixed....but
.....Even I want to taste ICS/JB Rom's like u guys...Please Help Your Rookie.
Thanks & Regards
D.J XactiX
Proud owner of Samsung Galaxy S i9000
----------------------------------------------------------------------------------------ANDROID ROCKS---------------------------------------------------------------------------------------------
Which ICS Rom did you try, and what guide did you use to follow?
The more detail you give the better we all can help you
EwOkie said:
Which ICS Rom did you try, and what guide did you use to follow?
The more detail you give the better we all can help you
Click to expand...
Click to collapse
Hey EwOkie,
Thanks for your courtesy mate...really appreciate it,
So here we go,
I had stock GB 2.3.6 ROM installed on my phone ;ie GT-I9000_XEU_I9000XXJW4_I9000OXAJW4_I9000XXJW4.zip,
after that I rooted my phone using CF-Root-XX_OXA_JW4-v4.4-CWM3RFS,
then I did factory reset,wipe cache and dalvik cashe and installed GamerzRom v11.0 which is a GB ROM,
so far no issue...wifi is working fine,phone is not at all giving me any auto restart issue...its was working like a charm,
then I found ICS_F4k_MOD_v4.0.4_I9000_r3.zip which is an ICS ROM,
I did factory reset,wipe cache and dalvik cache,the I installed ICS_F4k_MOD_v4.0.4_I9000_r3.zip using CWM Recovery console,
it was booted fine to home screen...later on I tried connecting my phone using my wifi router I found that WiFi was not switching on at all,
I locked my phone using lock button then after few secs I am finding my phone is restarting itself in recovery mode,
restarted my back to normal and again the same issue,
I ignored it,
Then I downloaded C-RoM Mix v7 Latest 4.2.1.zip in which had a wifi bug fix,
I did factory reset,wipe cache and dalvik cache,
I flashed it using clockworkmod recovery and had eactly that same issue which I had on ICS ROM,
for WIFI issue I tried flashing wififix.zip and found no resolution,
my phone went into boot loop of Samsung Logo,
then I flashed it back to original stock rom GB 2.3.6 and my phone started working like the way it should be.
This is the whole story
I moved from GB to ICS and then to JB.
Seriously brother I have no idea why its causing this weird issue...this is why I am looking for help from AndroidXperts on XDA site
Kindly help me to sort it out.
Thanks & Regards
D.J XactiX
Ok first up thanks for the info....
When doing a complete wipe before installing another rom make sure you wipe all 4 :
Data / Factory Reset
Cache Partition
Dalvik Cache
Battery Stats
Unless the Developer for the Rom States otherwise.
I know that there are a few ICS Roms that have a lot of bugs please check Info on them before Downloading
Should tell you whats working and whats notto save hassle
As I really only use GB Roms (my own preference)
Might help to try different Modems for your Romas this can help signal/network strength, where do you stay?
Yeah flashing back to 2.3.6 will work all the time as its basically stock.
No matter what Custom Rom I try I always flash JVU 2.3.6 then Root it > then the Custom Rom I want
I never just overwrite it with another Rom...
Hopefully someone with the same Rom as yourself may help as I dont want to give wrong info ....
Or Ask on the Rom site the issue your having with it
If you do need my help ... just ask
EwOkie said:
Ok first up thanks for the info....
When doing a complete wipe before installing another rom make sure you wipe all 4 :
Data / Factory Reset
Cache Partition
Dalvik Cache
Battery Stats
Unless the Developer for the Rom States otherwise.
I know that there are a few ICS Roms that have a lot of bugs please check Info on them before Downloading
Should tell you whats working and whats notto save hassle
As I really only use GB Roms (my own preference)
Might help to try different Modems for your Romas this can help signal/network strength, where do you stay?
Yeah flashing back to 2.3.6 will work all the time as its basically stock.
No matter what Custom Rom I try I always flash JVU 2.3.6 then Root it > then the Custom Rom I want
I never just overwrite it with another Rom...
Hopefully someone with the same Rom as yourself may help as I dont want to give wrong info ....
Or Ask on the Rom site the issue your having with it
If you do need my help ... just ask
Click to expand...
Click to collapse
Hi EwOkie,
Thanks for sharing your experience.
I am followed everything what u just mentioned in ur reply allready...but no go
Me & my GF we both have i9000 and I have followed same installation process on both the phones...her phones works like a charm but mine is like an incomplete soul.
One more thing mate,I really dont understand this ......can you tell me what difference it makes to have JVU 2.3.6 or some other version...how exactly its works....u know what I mean to say.
No idea why we use 2.3.6 JVU with CF Root (Kernel for Recovery) we just do ,, suppose its the best to start with before flashing a Custom Rom
So your partners phone works ok and yours doesnt.. did you try using the PIT File and re-partition?
Check my signature at bottom its a HOW TO Guide incase you get lost
As I says I dont have a lot of experience with ICS or JB Roms as the ones i flashed in the past werent as stable and had some bugs in them
Thats why i stuck with GB Roms
plz help me
today i install a custom rom lollipop in sony xperia c3 dual
but now my phone refused to start even same issue recovery mode... now my phone completely death.. when i try to start it red +green blink but fast mode work easily .. & when i connect my phone to charger it restart it self again & again ... its show only sony logo and its restart again ..plz help me

HOWTO: flash custom GB and JB roms for 9070P (NFC)

HOW TO PREPARE i9070 CUSTOM ROMS TO WORK ON 9070P​
disclaimer as usual - everything on your own responsibility still, seems to be quite safe, the worst ever happened is no gsm signal if using not appropriate /lib/tee folder files. no soft/hardbricks reported (yet )
technical details - scroll a bit down
----
part 1: /system/lib/tee folder to replace
Jelly Bean Stock ROMS and ones based on Samsung Stock ROMs (Harshjelly, PureVanilla, LightJB..)​the most important information: in order to get i9070P Jelly Bean modded stock ROMs working, you have to:
1. download this file: http://d-h.st/vUw
2. save the file on your sd card (preferably external sd, not the internal memory)
3. flash your desired rom, do all neccessary wipes and so on, but DON'T REBOOT YET!
4. you have to install the zip downloaded in step 1 (don't confuse the order of steps 3 and 4, otherwise your rom won't work for 9070P, ie. you won't have any radio modules working - gsm, wifi, bt)
5. reboot and enjoy
tested by users on various modded stock roms (read all the pages); the one above works on stock-based ROMs only,
----
CyanogenMod ROMs
for CM10, CM10.1 and CM10.2 file here: http://d-h.st/E9e
proceed exactly as steps described above
thx Mr.xD97 - files for /system/lib/tee extracted from his rom here http://forum.xda-developers.com/showthread.php?t=2278169
according to hannez_r
Tee folder from JB 4.1.2 TW works on CM11.
Click to expand...
Click to collapse
- thx for the info
-------------------------​
part 2: the build.prop incompatibility:​this happens if you attempt to flash custom roms straight from your 9070P stock ROM. once you successfully flash any i9070 ROM, you won't be bothered with the issue (until you reflash your stock ROM with odin again)
in case flashing of your target rom ends immediately with an error ("assert failed: getprop....") then you have to do something with your build.prop. The explanation for that happening is: there are build.prop entries stating that the phone is "9070P" and the updater-script prevents your target ROM from being flashed to an uncompatible device (not an "9070")
possible solutions:​either: 1. grab some build.prop editors prior to flashing anything and change all occurences of "9070P" to "9070" and "janicep" to "janice". like this one: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor or just edit your build.prop manually.
or: 2. unzip the target ROM .zip file, go to \META-INF\com\google\android and erase the lines starting with "getprop" (do NOT use windows notepad - it breaks the file, use notepad++ instead), save the edited updater-script and push it to the sd card. you're ready to flash the ROM
3. [automatically, to be tested] - waiting for your reports. ; use the build.prop.to.9070.zip to spoof your build.prop to i9070 model; it's a CWM flashable that should change the contents of your build.prop automatically. all credits for the script go to the author of this post: http://forum.xda-developers.com/showpost.php?p=19093919&postcount=20 - remember, not tested yet, in case you still get an assert:getprop error after flashing this .zip, try rebooting recovery and install the ROM .zip then method 3 most probably not working, so don't test unless you have lots of spare time to play with your phone
--------
source and inspiration:
I found that in galaxy ace 2 i8160/L/P forum - you have to replace /system/lib/tee folder (or 3 files inside) in order to flash custom roms made for i9070: there it is: http://forum.xda-developers.com/showthread.php?t=2159250
BUMP.
situation changed a lot. i9070P owners - try solution above
---
no more time today
btw. forgot to tell - take Gingerbread version of suppressed, no one knows what happens when you try with JellyBean version!
Woooow thank you
Gesendet von meinem GT-I9070P mit Tapatalk 2
If I understand properly, I should be able to download JetMod ROM. Replace the three files in the ZIP “tee” directory, “cops_ta.ssw, custom_ta.ssw, smcl_ta_8500bx_secure.ssw”, with the same named files currently in my phone, go to TWRP, Wipe System, Wipe Cache, Wipe Dalvik Cache, Factory reset, then install JetMOD zip?
Does this seem correct?
purplepizza said:
If I understand properly, I should be able to download JetMod ROM. Replace the three files in the ZIP “tee” directory, “cops_ta.ssw, custom_ta.ssw, smcl_ta_8500bx_secure.ssw”, with the same named files currently in my phone, go to TWRP, Wipe System, Wipe Cache, Wipe Dalvik Cache, Factory reset, then install JetMOD zip?
Does this seem correct?
Click to expand...
Click to collapse
yes, exactly. that way works for suppressed amoled/megatheme and for custom roms for ace 2 (ofc for ace 2 they use their /tee files respectively). so no reason it shouldn't work for jetmod.
---------
BTW curious to ask if anybody dared to flash any custom JB rom over recovery to 9070P? guinea pigs needed
You are awesome! Jetmod works great! Thank you!
thanks!!
Oh thank you very very much! I have one question... Now it is not possible try to flash a Jelly Bean rom for 9070 ok.. But in future owners of 9070P will get Jelly Bean probably this method will work also for Jelly bean custom roms for 9070?
FollonSaxBass said:
Oh thank you very very much! I have one question... Now it is not possible try to flash a Jelly Bean rom for 9070 ok.. But in future owners of 9070P will get Jelly Bean probably this method will work also for Jelly bean custom roms for 9070?
Click to expand...
Click to collapse
most probably - yes.
------
btw. I tried to run NFC on suppressed, but no go - deodexed NFC.apk, NFCTestmode.apk and Tag.apk, pushed to /system/app and set permissions, but still no way to run NFC. in case You people have any ideas, let me know fortunately not a dealbreaker to me.
adamuadamu said:
most probably - yes.
------
btw. I tried to run NFC on suppressed, but no go - deodexed NFC.apk, NFCTestmode.apk and Tag.apk, pushed to /system/app and set permissions, but still no way to run NFC. in case You people have any ideas, let me know fortunately not a dealbreaker to me.
Click to expand...
Click to collapse
If you have a native i9070p ROM... search the system folder for any file that contains nfc in the name, and copy it from the native i9070p ROM to suppressed. P.S. use windows search function
Another question: after flashing a custom rom for 9070 on 9070P is flashed also the kernel for 9070... Can we use kernel of the rom or we should change te kernel with CoCore-P? Thank you for the reply
FollonSaxBass said:
Another question: after flashing a custom rom for 9070 on 9070P is flashed also the kernel for 9070... Can we use kernel of the rom or we should change te kernel with CoCore-P? Thank you for the reply
Click to expand...
Click to collapse
as long as the kernel you currently use works OK - no need to worry; but check your CPU usage as some users reported excessive CPU usage all the time for older cocore kernels. I can confirm that cocore 4.1(for non-NFC version) and cocore-P don't have that issue
--
still no luck with NFC - the files I used are the only ones that can have anything in common with nfc. it gets even worse upon reboot as the NFC service app pops up FC window every three seconds and doesn't stop until I deleted it and rebooted again :|
adamuadamu said:
as long as the kernel you currently use works OK - no need to worry; but check your CPU usage as some users reported excessive CPU usage all the time for older cocore kernels. I can confirm that cocore 4.1(for non-NFC version) and cocore-P don't have that issue
--
still no luck with NFC - the files I used are the only ones that can have anything in common with nfc. it gets even worse upon reboot as the NFC service app pops up FC window every three seconds and doesn't stop until I deleted it and rebooted again :|
Click to expand...
Click to collapse
Are you sure you included all the libs ?
You also need to include all the NFC system apps as well
My life has more downs than ups, but I try to keep it a balance.
CallMeVentus said:
Are you sure you included all the libs ?
Click to expand...
Click to collapse
thanks for the suggestion. forgot to compare the differences in libs between 9070 and 9070P roms. will look into it
I have never flashed a new ROM. I want to try JetMod. It seems more I search, more restoring options are presented. (TWRP Restore or TB) Can someone recommend the safest and easiest method for restoring user apps and settings (SMS, MMS, & Contacts) on the new ROM? I have a TB and TWRP back up.
purplepizza said:
I have never flashed a new ROM. I want to try JetMod. It seems more I search, more restoring options are presented. (TWRP Restore or TB) Can someone recommend the safest and easiest method for restoring user apps and settings (SMS, MMS, & Contacts) on the new ROM? I have a TB and TWRP back up.
Click to expand...
Click to collapse
For Contacts I use the in-built backup feature....and SMS and MMS I usually use MyBackup Root for stock Messaging , otherwise when I'm using GO SMS Pro I use its in-built backup feature
My life has more downs than ups, but I try to keep it a balance.
Karsten95 said:
You are awesome! Jetmod works great! Thank you!
Click to expand...
Click to collapse
I must admit I tried Jetmod without success. Does not boot. Just startup screen being displayed.
I tried with default kernel and with cocore-P 1.0 kernel. Nothing worked. Might be something wrong with the installation (using TWRP in cocore-P 1.0). Installing system files seems to take just a fraction of second. And I suspect nothing was actually copied. I also tried replacing Aroma updater with the "regular one". Still the same...
Suppressed 2.2+2.5 worked. But it is not really my taste Should have tried 3.0 instead. But I would really like to try Jetmod. Any hints about the recovery?
Does CWM recovery for i9070 (non-P) http://forum.xda-developers.com/showthread.php?t=1987313 work for P devices? Anyone tried?
LaizyJumper said:
I must admit I tried Jetmod without success. Does not boot. Just startup screen being displayed.
I tried with default kernel and with cocore-P 1.0 kernel. Nothing worked. Might be something wrong with the installation (using TWRP in cocore-P 1.0). Installing system files seems to take just a fraction of second. And I suspect nothing was actually copied. I also tried replacing Aroma updater with the "regular one". Still the same...
Suppressed 2.2+2.5 worked. But it is not really my taste Should have tried 3.0 instead. But I would really like to try Jetmod. Any hints about the recovery?
Does CWM recovery for i9070 (non-P) http://forum.xda-developers.com/showthread.php?t=1987313 work for P devices? Anyone tried?
Click to expand...
Click to collapse
well, probably someone that's using jetmod on 9070P will tell you how to do it. but to be sure: did you start with 3.0, run the android wizard->rebooted to recovery->installed->3.1->rebooted to system->rebooted to recovery->installed 3.2 ? AFAIR when I was using i9070(non-P) I had to proceed these steps as flashing 3.0 + upgrades without reboots in the meantime caused bootloop or similar
as far as CWM is concerned - 1. it's temporary 2. it's meant for JB roms 3. never tried it on 9070P due to the fact TWRP always worked for me
Thank you very much adamuadamu... It worked very well for me... I installed jetmod 3.0 and i've done all the update to 3.2.2 without any problem
So none tried to do the same thing with Jelly Bean roms right?
FollonSaxBass said:
Thank you very much adamuadamu... It worked very well for me... I installed jetmod 3.0 and i've done all the update to 3.2.2 without any problem
So none tried to do the same thing with Jelly Bean roms right?
Click to expand...
Click to collapse
I'm pretty sure JB ROMs will have the same issues that GB non-P ROMs had....and we don't have the JB /system/tee files and kernel to deal with it
My life has more downs than ups, but I try to keep it a balance.
CallMeVentus said:
I'm pretty sure JB ROMs will have the same issues that GB non-P ROMs had....and we don't have the JB /system/tee files and kernel to deal with it
My life has more downs than ups, but I try to keep it a balance.
Click to expand...
Click to collapse
I think the lib/tee files are the main concern at the moment to get JB ported.
I have downloaded official kernel sources for i9070. And it includes config for 9070P as well. I managed to build the 4.1.2 kernel image for 9070P. But I don't really want to test it myself. I am not confident that it won't brick my device
So far, most of brave ones who have tried 9070 JB image on P-device have got a brick. If anyone could explain the reason, would be nice.
Does anyone know, if the reason is wrong kernel? Or is there something else in the JB installer that causes that. Some hboot partition or something?
Modem partition?

[Q] GT-S6500D (jenad) problems with WiFi and SD (internal sdcard0)

Dont stone me if repost, but believe it is not, I honestly tried to study this and other forums for last almost 2 weeks without any results:
I got Mini2 with GB stock ROM and first rooted (using Poot exploit) and upgraded gradually to CWM 6.0.4.5 and CM 10.1 and later CM 11. Didnt discovered any problems except for sdcard0 mount problem as described may times. sdcard0 is not mountable under CWM 6.0.4.5 and CM11 but I think that this can be solved using other threads in this forums, so not a matter here and now, however, it may hint you what is possibly going on. The main thing is, that after trying to experiment with OC kernel, my WiFi always indicates ERROR when trying to switch it on. No matter if in Stock ROM or CM (any version). I tried to reflash Stock and CM (10.1; 10.2 and 11), even repartitioned with ODIN (3.09) and reflashed Stock ROM. No improvement, no change.
Strange thing is, that it was said, that after flashin CM (or CWM not clear now), the offline battery charging does NOT work and phone alway reboots. That can be confirmed by me, but with that exception, that it does NOT work either after reflashing Stock ROM and Stock RECOVERY. Even after this, phone never switches OFF when connected to the charger, just reboots.
I have always did full WIPE (data,cache, format system).
Currently I have Stock ROM 2.3.6
kernel 2.6.38.6-1248583 [email protected] #1 dated Thu Nov 7 20:39:38 KST 2013
Baseband S6500DXXMK1
Recovery reports "Android system recovery (3e)
During last Stock reflash the baseband got upgraded. I am a PC guy, not an Android specialist, but from everlasting WiFi problems and offline charging not working even with Stock ROM and Stock recovery, it looks, like something somewhere got left from my tries with either OC kernel or CWM/CM and prevents Wifi from being switched on. Curently my Stock is rooted so I can get some logs/info anybody can need willing to help/investigate..
Any help or pointers to troubleshooting are highly appreciated as I really love my little cute Mini II.
Alternative
prgbear said:
Dont stone me if repost, but believe it is not, I honestly tried to study this and other forums for last almost 2 weeks without any results:
I got Mini2 with GB stock ROM and first rooted (using Poot exploit) and upgraded gradually to CWM 6.0.4.5 and CM 10.1 and later CM 11. Didnt discovered any problems except for sdcard0 mount problem as described may times. sdcard0 is not mountable under CWM 6.0.4.5 and CM11 but I think that this can be solved using other threads in this forums, so not a matter here and now, however, it may hint you what is possibly going on. The main thing is, that after trying to experiment with OC kernel, my WiFi always indicates ERROR when trying to switch it on. No matter if in Stock ROM or CM (any version). I tried to reflash Stock and CM (10.1; 10.2 and 11), even repartitioned with ODIN (3.09) and reflashed Stock ROM. No improvement, no change.
Strange thing is, that it was said, that after flashin CM (or CWM not clear now), the offline battery charging does NOT work and phone alway reboots. That can be confirmed by me, but with that exception, that it does NOT work either after reflashing Stock ROM and Stock RECOVERY. Even after this, phone never switches OFF when connected to the charger, just reboots.
I have always did full WIPE (data,cache, format system).
Currently I have Stock ROM 2.3.6
kernel 2.6.38.6-1248583 [email protected] #1 dated Thu Nov 7 20:39:38 KST 2013
Baseband S6500DXXMK1
Recovery reports "Android system recovery (3e)
During last Stock reflash the baseband got upgraded. I am a PC guy, not an Android specialist, but from everlasting WiFi problems and offline charging not working even with Stock ROM and Stock recovery, it looks, like something somewhere got left from my tries with either OC kernel or CWM/CM and prevents Wifi from being switched on. Curently my Stock is rooted so I can get some logs/info anybody can need willing to help/investigate..
Any help or pointers to troubleshooting are highly appreciated as I really love my little cute Mini II.
Click to expand...
Click to collapse
Alternatively, can someone direct me to steps to COMPLETELY WIPE EVERYTHING (I mean really everything to the bone and start with STOCK ROM from scratch?
Thanx.
prgbear said:
Alternatively, can someone direct me to steps to COMPLETELY WIPE EVERYTHING (I mean really everything to the bone and start with STOCK ROM from scratch?
Thanx.
Click to expand...
Click to collapse
Use this code:
*2767*3855#
Click to expand...
Click to collapse
What will it do? Need to know before I use it. Cannot afford to **** it up.
Thanks, Ondrej
prgbear said:
What will it do? Need to know before I use it. Cannot afford to **** it up.
Thanks, Ondrej
Click to expand...
Click to collapse
1 google search : https://www.facebook.com/kasmirnewsagency/posts/384662564983666

[Q] I messed up the RADIO on my i8190L and now stuck in bootloop

Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
You downloaded the wrong modem file. You need the one for the I8190L, but you flashed one for the I8190.
Sent from Tapatalk on my GT-I8190 running Novafusion's Carbon 4.4.2
chan1628 said:
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
Click to expand...
Click to collapse
Sorry but you are going to sleep on the couch tonight I suggest this:
You must download the original rom from SamMobile, install it through Odin and then install again through Odin the Recovery and through Recovery your "old" new Rom. When you are in the new Recovery check for the nandroid backup that you made . If it isnt there look for the couch because the phone is with the "old" new Rom without any of the past data.
Btw if you want you can upgrade your baseband from here:http://forum.xda-developers.com/showthread.php?t=2526831
Good luck
No recovery at all or bootloop in recovery as well?
Sent through time and space from my s3mini/CM11
chan1628 said:
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
Click to expand...
Click to collapse
Don't bother trying to flash it if nothing happens, drain the battery, return to seller and get replacement. I got free replacement from Amazon with my bricked rooted S3 mini.
jstath1972 said:
Sorry but you are going to sleep on the couch tonight I suggest this:
You must download the original rom from SamMobile, install it through Odin and then install again through Odin the Recovery and through Recovery your "old" new Rom. When you are in the new Recovery check for the nandroid backup that you made . If it isnt there look for the couch because the phone is with the "old" new Rom without any of the past data.
Btw if you want you can upgrade your baseband from here:http://forum.xda-developers.com/showthread.php?t=2526831
Good luck
Click to expand...
Click to collapse
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
KoolKid98189 said:
Don't bother trying to flash it if nothing happens, drain the battery, return to seller and get replacement. I got free replacement from Amazon with my bricked rooted S3 mini.
Click to expand...
Click to collapse
its not going to be that easy for me... i've had this phone for almost 2yrs already
tys0n said:
No recovery at all or bootloop in recovery as well?
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
no recovery at all... it bootloops if i power on normally
chan1628 said:
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
Click to expand...
Click to collapse
It depends on what country you're in and if the phone is locked to any specific carrier.
If it's not locked then I believe any i8190L firmware will do, just to get the phone running again.
chan1628 said:
its not going to be that easy for me... i've had this phone for almost 2yrs already
no recovery at all... it bootloops if i power on normally
Click to expand...
Click to collapse
It was a tough decision for me, it was either stick to a ****ty BlackBerry or get a free replacement and sacrifice the data. Some of it should be synced to your Google account
tys0n said:
It depends on what country you're in and if the phone is locked to any specific carrier.
If it's not locked then I believe any i8190L firmware will do, just to get the phone running again.
Click to expand...
Click to collapse
ok, i will give all this a try and hope for the best
thanks everyone for the quick responses :good:
You could also try to reflash just recovery thru Odin and see if it works.
Sent through time and space from my s3mini/CM11
chan1628 said:
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
Click to expand...
Click to collapse
You are in Canada but the L version is for the Latin America countries. So the firmware must be from one of that countries. Which one i can't tell you. You should ask your seller.
[problem solved]
Ok, I was able to restore the phone with /u/jstath1972's suggestion
1. I went to http://www.sammobile.com/firmwares/ and downloaded the latest 'L' firmware
2. I used ODIN to flash the firmware
3. the phone REBOOTED!!!
(once the phone rebooted, the rest was easy)
4. powered off and ODIN flashed the lastest TWRP
5. powered off and booted into recovery
6. RESTORED NANDROID so wife would stop giving me the look
7. updated baseband as suggested: http://forum.xda-developers.com/show....php?t=2526831
THANK YOU THANK YOU :good:
side note: i wish my work was this effective in resolving technical issues (just my 2 cents)
chan1628 said:
Ok, I was able to restore the phone with /u/jstath1972's suggestion
1. I went to http://www.sammobile.com/firmwares/ and downloaded the latest 'L' firmware
2. I used ODIN to flash the firmware
3. the phone REBOOTED!!!
(once the phone rebooted, the rest was easy)
4. powered off and ODIN flashed the lastest TWRP
5. powered off and booted into recovery
6. RESTORED NANDROID so wife would stop giving me the look
7. updated baseband as suggested: http://forum.xda-developers.com/show....php?t=2526831
THANK YOU THANK YOU :good:
side note: i wish my work was this effective in resolving technical issues (just my 2 cents)
Click to expand...
Click to collapse
Good sleep tonight, my friend ! :good:

Categories

Resources