Related
There seems to be a major issue with the 4.06 radio and my phone - every time I have tried to flash it (from both validated .img's and update.zips) my phone becomes extremely unstable afterwards.
It goes into booting loops, hangs at the X, when I get it to boot it crashes while using heavy 3G or WiFi data, reboots when plugged into USB and receiving a call and it becomes almost impossible to get into recovery mode etc, etc.
The only way to get back to a working phone is to revert to stock 4.04. I have tried 5 different times over the last 2 weeks now with the same results every time.
I am starting to wonder if it is a AT&T/Rogers N1 issue or something specific to my device. If it was my device I would think that flashing back to 4.04 would also cause problems but that is not the case. This makes me believe there is there maybe an incompatibility with the leaked Froyo radio.
Appreciate any thoughts/comments.
I'm not having that problem. I flashed Modaco's first FroYo repack with root and the new radio, and things have been fine. To be honest, the only thing I've noticed is that Bluetooth seems to sync a lot faster to the head unit in my car.
Did you do a complete wipe before you installed the update and what applications have you added that may not like the radio?
Edit to add: By the way, you guys have a kick-ass little HTC Magic up there. It may not be a Nexus One, but it more than holds it's own running cyanogen. I have an import that my wife is playing with. I really like it.
Have you tried the 4.6.00.12_7 radio as well ast the 4.6.00.2_2? The 12_7 is working flawlessly for me both on Froyo and on CM 5.0.8-derived ROMs.
I just verified my version - it's definitely the 4.6.00.12_7 Froyo radio firmware.
codesplice said:
Have you tried the 4.6.00.12_7 radio as well ast the 4.6.00.2_2? The 12_7 is working flawlessly for me both on Froyo and on CM 5.0.8-derived ROMs.
Click to expand...
Click to collapse
I tried the 12_7 last night and after flashing it using fastboot, my phone got stuck in a reboot loop. I could get back into fastboot and saw the new radio version on the screen but could not for the life of me get my phone to boot into either the rom or recovery mode - I pulled the battery, took out the SD card etc but nothing worked. This prevented me from flashing a ROM and I could not get into Recovery. After about an hour of trying, I managed to get the 4.04 radio flashed using fastboot and then my phone booted with no problems.
Previously, I tried the various Froyo builds and with no additional apps installed I would still get random roboots when using data via either 3G or WiFi - usually when I try to do something big like downloading/syncing a large file.
This is the story every time I try a 4.06 radio. 4.04 is rock solid.
Have you tried flashing the 4.6 radio via an update.zip as opposed to through fastboot? It's about the only other idea I can think of lol...
Just checked, I flashed the 2_2 last night, not 2_7.
I have flashed the radio via update.zip before and my phone worked but would be unstable. I will have to double check which version I used, could have been 2_2 as well.
codesplice said:
Come to think of it, that's the radio version I'm currently using, and that's where I got mine while I was running his ROM. So yes, flash that zip, flash Kangorama, and you should be square.
Click to expand...
Click to collapse
This is the same radio image I flashed two days ago and it worked for me quite well for an entire day (light 3G use) and then started crashing the phone when I tried downloading larger files (using the Audible app) via both WiFi and 3G in the evening. Once it started crashing I could not get into recovery until after I pulled my SD card. Once it booted OK without the SD card I put the card back and it booted ok again. It would still crash on heavy data use though.
Maybe try the 12_7 radio from http://forum.xda-developers.com/showthread.php?t=692609 ? I'm fairly certain that is the same radio update that I have applied on my AT&T N1.
edit: disregard....
I'm running out of ideas, dude
codesplice said:
I'm running out of ideas, dude
Click to expand...
Click to collapse
I appreciate your input. Thank you. I will try _7 again.
DvTonder said:
This is the same radio image I flashed two days ago and it worked for me quite well for an entire day (light 3G use) and then started crashing the phone when I tried downloading larger files (using the Audible app) via both WiFi and 3G in the evening. Once it started crashing I could not get into recovery until after I pulled my SD card. Once it booted OK without the SD card I put the card back and it booted ok again. It would still crash on heavy data use though.
Click to expand...
Click to collapse
Did you try not running/removing the audible app and see about stability then? What else are you using? Not every app is going to play nice with newer firmware.
attn1 said:
Did you try not running/removing the audible app and see about stability then? What else are you using? Not every app is going to play nice with newer firmware.
Click to expand...
Click to collapse
The crashes started just after I got the Rom installed.
I did the following:
- Nandriod backup (thank goodness for this!)
- I wiped all as per instructions
- Installed radio, rebooted OK
- Installed ROM (Rodriguesstyle 1.6)
- Booted OK into setup
- Configured my phone - first crash just after entering my gmail ID and the syncing of all the apps from the market started
- Rebooted, configured my phone again - apps installed this time but while configuring ChompSMS the phone rebooted again
- Rebooted, phone came up clean, ran OK all day
- Got home and tried syncing Audible content - phone crashed
- Could not get into recovery or boot the phone normally for almost an hour (pulling battery etc did not help)
- Pulled the SD Card and the phone booted, shut down, put the sd card in again, phone booted OK
- Got a phonecall, phone rebooted
- Got fed up and restored 4.04 radio and stock ROM
- Phone stable since
I was running the following apps:
- Autokiller
- Doubletwist Player
- Audible beta
- Silent Sleep
- ChompSMS 4.2
- Switchpro Widget
- Barcode Scanner
- ADW Launcher
- newsRob
- File manager
- Backgrounds
- Rom Manager
DvTonder said:
The crashes started just after I got the Rom installed.
I did the following:
...
- Installed ROM (Rodriguesstyle 1.6)
...
Click to expand...
Click to collapse
What kernel is the Rodrigessstyle ROM using?
Try Modaco's straight up Froyo repack - it has a stock kernel. I'd get as close to stock Froyo ROM/Radio as possible, see what I have and then go from there.
Also, make sure you're using an updated version of chompsms. I think I heard that reports were that it was not compatible with Froyo, but that it's been updated.
attn1 said:
What kernel is the Rodrigessstyle ROM using?
Try Modaco's straight up Froyo repack - it has a stock kernel. I'd get as close to stock Froyo ROM/Radio as possible, see what I have and then go from there.
Also, make sure you're using an updated version of chompsms. I think I heard that reports were that it was not compatible with Froyo, but that it's been updated.
Click to expand...
Click to collapse
I used the stock kernel. ChompSMS 4.1 and later is compatible and I was using 4.2. I am planning on trying the new Kang-o-rama 0.8b1! (CM-5.0.8+2.6.34 Kernel) rather than Froyo - if only I can get the radio to flash.
DvTonder said:
I used the stock kernel. ChompSMS 4.1 and later is compatible and I was using 4.2. I am planning on trying the new Kang-o-rama 0.8b1! (CM-5.0.8+2.6.34 Kernel) rather than Froyo - if only I can get the radio to flash.
Click to expand...
Click to collapse
Why not start with FroYo - the ROM the radio was meant to work with - before flashing anything else? If it doesn't run then, you have a real problem. otherwise, you have no idea where the problem is.
attn1 said:
Why not start with FroYo - the ROM the radio was meant to work with - before flashing anything else? If it doesn't run then, you have a real problem. otherwise, you have no idea where the problem is.
Click to expand...
Click to collapse
Point taken. Back to the basics.
I came straight from Rodriguesstyle 1.6 with the included add-on OV/UV kernel to Kang 0.8b1 without any issues. Even got the 720p hack working beautifully
well i am using the new froyo radio with my ATT nexus one, and its been no different than the old radio. no crashes or anything. however, i had NO idea that there were 2 froyo radios. is that what someone just posted on the first page?
I have had a simmilar experienc, but it is NOT froyo related.
I was rooted, on the desire ROM
It was restarting at seemingly random (and frequent) times through the day -
I reflashed to stock 2.1.
During setup, phone rebooted.
Got through sign-in. Installed some apps. Phone rebooted.
Phone was absolutely fine, as long as I didn't touch it. I would use it - browse, etc. Seemed to be fine. Would then reboot. FLashed it up to froyo. Same.
I think it's the bad RAM issue i've seen reports of, but I'm not sure. Sent in for a replacement.
Let's hope that's not OPs issue, though the problem seems to be pointed in that kind of direction. Hope you get your situation resolved under warranty.
chordmasta said:
I have had a simmilar experienc, but it is NOT froyo related.
I was rooted, on the desire ROM
It was restarting at seemingly random (and frequent) times through the day -
I reflashed to stock 2.1.
During setup, phone rebooted.
Got through sign-in. Installed some apps. Phone rebooted.
Phone was absolutely fine, as long as I didn't touch it. I would use it - browse, etc. Seemed to be fine. Would then reboot. FLashed it up to froyo. Same.
I think it's the bad RAM issue i've seen reports of, but I'm not sure. Sent in for a replacement.
Click to expand...
Click to collapse
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
Hey guys, I'm having a problem
Sorry if I'm posting this in a wrong area
Well, I'm using CyanogenMod 7.2.0 stable by Kabaldan for Milestone A853. Then I tried to install CyanogenMod 9 Nightly (from Skrilax build bot), the latest version. Everything was going well, then when I tried to boot, a screen about "Android is updating applications" appeared, and then after updating, the phone hard rebooted, back to the M logo. Then I left it booting again, and it rebooted again, though this time the update screen didn't appeared. Sometimes I get the first screen to appear, but I can't even touch the phone because it reboots before I try to do so. I tried installing CyanogenMod 10 (Skrilax nightly build bot again) and the same error happened! What is happening to my phone? I've never found anyone with this problem
Please help me! Thanks.
Did you perform a full wipe before applying CM9/10?
Eiertschik said:
Did you perform a full wipe before applying CM9/10?
Click to expand...
Click to collapse
If by full wipe you mean the three wipe options in OpenRecovery (Dalvik, Data and Cache) then yes. I even deleted the /system folder and nothing!
UPDATE: I tried to install CM10, removed system, data and cache through ADB and dalvik cache, installed CM10 and gapps. When booting, the first screen asking for language rapidly appears, and reboots. I tried to boot again, then I rapidly touched the screen when the screen appeared, and it didn't reboot! Well, that's better, but CM10 is too lagged for daily use, that's why I want to install CM9!
I'm using CM10 from couple of days..
I get enough RAM to run apps that I daily use...check for unwanted apps that are not being used, disable it through hwa setting app. Just use it for a day .. IMO CM10 is better than CM9.
BTW I removed gtalk, maps, email, exchange service and other unwanted apps from OR...which I don't use at all..
Sent from my Milestone using xda app-developers app
Hell Angel 1910 said:
Hey guys, I'm having a problem
Sorry if I'm posting this in a wrong area
Well, I'm using CyanogenMod 7.2.0 stable by Kabaldan for Milestone A853. Then I tried to install CyanogenMod 9 Nightly (from Skrilax build bot), the latest version. Everything was going well, then when I tried to boot, a screen about "Android is updating applications" appeared, and then after updating, the phone hard rebooted, back to the M logo. Then I left it booting again, and it rebooted again, though this time the update screen didn't appeared. Sometimes I get the first screen to appear, but I can't even touch the phone because it reboots before I try to do so. I tried installing CyanogenMod 10 (Skrilax nightly build bot again) and the same error happened! What is happening to my phone? I've never found anyone with this problem
Please help me! Thanks.
Click to expand...
Click to collapse
If nothing solves your problem, you should reflash the SBFs and start all over again. I had to do this sometimes. Formatting the SDCard (after backing-up your personal data) also helps to prevent this from ocurring.
Well, never mind, I was robbed saturday. Thanks for the help folks
Sad! But it's a chance to get a better phone. Good luck!
Tiago Costa said:
Sad! But it's a chance to get a better phone. Good luck!
Click to expand...
Click to collapse
Really sorry to know that you have said goodbye to your great milstone... Anyway, I'd like to share what I did when I was in your situation:
- Flash the stock ROM to come back to stock 2.1
- Erase and format SD card
- Partion the SD card angain
- Root the fone and flash to the latest CM10
And now, my stone works like a charm and I have not yet to have idea to change to a new phone now :victory:
Just for sharing!
justforlove said:
Really sorry to know that you have said goodbye to your great milstone... Anyway, I'd like to share what I did when I was in your situation:
- Flash the stock ROM to come back to stock 2.1
- Erase and format SD card
- Partion the SD card angain
- Root the fone and flash to the latest CM10
And now, my stone works like a charm and I have not yet to have idea to change to a new phone now :victory:
Just for sharing!
Click to expand...
Click to collapse
and BPSW for 2.1.1 is needed? or optional?
It's optional.
You only have to wipe data,dalvik-cache and data (you will lose all your information, so backup everything) and to create an ext partition on your sdcard.
Erovia said:
It's optional.
You only have to wipe data,dalvik-cache and data (you will lose all your information, so backup everything) and to create an ext partition on your sdcard.
Click to expand...
Click to collapse
yeah I know, I read the dev thread but can't make replies there. I am now on CM10 from 09/24 (last 4.1.1) and considering about CM10 4.2 but I was little bit confused about BPSW. And will there be problem If I will uprgade from 2.2? Because I don't have nandroid backup of 2.1
(FYI, the current CM10 is based on Android 4.1.2.
4.2 will be the next version of Android and probably CM11 will be based on it.)
Anyway, i upgraded from 2.2 to 4.0.4 and then to 4.1.1 and now 4.1.2.
I believe you can upgrade from 2.2 to 4.1.2 without any problem.
(but always make a nandroid before upgrading)
Yes, it's perfectly possible upgrade from 2.2 Stock ROM, although it's more difficult to root it.
I did it without any problems.
Is there any difference between upgrading from 2.1 or from 2.2?
Erovia said:
(FYI, the current CM10 is based on Android 4.1.2.
4.2 will be the next version of Android and probably CM11 will be based on it.)
Anyway, i upgraded from 2.2 to 4.0.4 and then to 4.1.1 and now 4.1.2.
I believe you can upgrade from 2.2 to 4.1.2 without any problem.
(but always make a nandroid before upgrading)
Click to expand...
Click to collapse
Yeah, sorry for that mistake, my fault. I upgraded from 2.2 to 4.0.4 and now I have 4.1.1. I tried to upgrade to 4.1.2 from 4.1.1 but it was laggy (10/16 and 10/17) so I restore it back to 4.1.1 which is pretty stable and I will wait to better time for this upgrade, because it is my main phone and my boss is upset when I am not available when he calls me
Tiago Costa said:
Yes, it's perfectly possible upgrade from 2.2 Stock ROM, although it's more difficult to root it.
I did it without any problems.
Is there any difference between upgrading from 2.1 or from 2.2?
Click to expand...
Click to collapse
I've read somewhere, that one must upgrade to 2.2 because upgrading from 2.1 will cause problem with some hardware module.
zemko said:
Yeah, sorry for that mistake, my fault. I upgraded from 2.2 to 4.0.4 and now I have 4.1.1. I tried to upgrade to 4.1.2 from 4.1.1 but it was laggy (10/16 and 10/17) so I restore it back to 4.1.1 which is pretty stable and I will wait to better time for this upgrade, because it is my main phone and my boss is upset when I am not available when he calls me
Click to expand...
Click to collapse
Kabaldan is working on it. It seems, if the CPU's clockspeed is under 600MHz, then something is wrong with the GPU performance. (So you should consider using Performance CPU governor.)
Erovia said:
Kabaldan is working on it. It seems, if the CPU's clockspeed is under 600MHz, then something is wrong with the GPU performance. (So you should consider using Performance CPU governor.)
Click to expand...
Click to collapse
I know that someone wrote it in dev thread for CM9 or CM10, but my battery is pretty weak, I am glad that with Juice defender it lasts for 12 hours and Performance governor is pretty aggressive to battery drain. Anyway thanks for answering my nooby questions
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...
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