Related
Hello,
I am trying to install CM7, the stable (bbq) version, on my gfs n1. I downloaded the zip, did a nandroid backup just in case, applied zip and rebooted. It opened to the CM7 load screen and i thought everything was working. Waited on that blasted screen for 45 mins and nothing happened. Did a battery pull and restored from the backup and everything is working how it used to. I am trying to figure out why the CM7 install didnt work.
I think it is because of the radio. She is coming from 2.1, an old CM rom. I am not sure which one. I didnt update any radio before i flashed the rom. I didnt know which radio to flash. The newest radio is a Korean radio. Should i flash that before i do CM7 flash. Any advice would be great. Thank you.
yes, you should have the newest radio, korean radio is ok for usa use.
alright, ill flash radio, then flash rom, then reboot. Ill let you know if i blow anything up. Thank you =)
Did you wipe everything?
i would do a full wipe ...yes
Did you flash gapps file also?
Full wipe should include system partition also.
FYI radio 5.08 is what come with 2.3.x ota. Radio 5.12 should work no problems.
Stock Rooted OTA 4.08.605.15 710RD Rom
OUTDATED: NOT THE LATEST STOCK VERSION!! 4.08.605.19 is now available.
Thanks goes to soniclude for the ota pull.
Stock Rooted OTA 4.08.605.15 710RD rom. It is rooted, zip aligned, has busybox and comes in odexed or deodexed versions. Other than that it is untouched. Enjoy
[standard flashing disclaimer here]
Wipe everything in the mounts and storage menu in recovery, except sdcard and emmc. Then flash like any other rom.
DOWNLOAD ODEXED - MD5
DOWNLOAD DEODEXED - MD5
If you want a little more customized and tweaked rom check out Touch Of Blue, also updated to 4.08.605.15. Touch Of Blue v2.2
Current OTA or a leak?
nfiniti9 said:
Current OTA or a leak?
Click to expand...
Click to collapse
Latest ota that is being delivered in groups to people as we spaeak. This is a pull from someone who recieved the update yesterday.
?
What are the instructions on how to install this Rom? Wipe everything just like wildstang83s Rom.
ironside2011 said:
What are the instructions on how to install this Rom? Wipe everything just like wildstang83s Rom.
Click to expand...
Click to collapse
Correct, i think. It is probably safest to wipe everything, but might be able to be flashed over wildstangs rom.
cool
I'm gonna wipe everything. I've experienced 1 too many bootloops and hicupps specially with cyanogenmod. My Dinc just never seems to like those Roms
Thank you for this. Been thinking of going to a more stockish rom. The latest roms just have too many bugs and quirks for me.
Sent from my ADR6300 using xda app-developers app
1 more
I literally flashed over wildstang83 Rom . I'm gonna attempt another try but wipe the cache and delvik 1st. Wiping everything didn't do anything. I'll report back soon
Not booting..
Not getting to boot animation... I have tried 3 times now.. Wiped everything..Format boot/storage etc... Anyone get it to work?
I was actually surprised and excited to see this update this morning but thought it would be ICS.
Long ago I rooted my phone just for gaining control and removing bloatware but ended up flashing my first rom with WildStang's Gingerbread OTA. After that I applied the "Warm" theme and been happy with that thinking there would be no more updates to this phone.
To the point - my question for you all is what do you mean by flash over? When the OTA is pushed is it just a patch or do they somehow send and entire install which removes the previous version, saves your data, installs the new version, and puts back your data? I don't have a problem with wiping and starting fresh, and it sounds like that is what everyone is recommending, I'm just trying to understand how it would even work flashing "over" my current version.
Nobody has replied to my post and I have not seen anyone report a trouble free install here so I'm gonna sit on the fence for a while
Did a full wipe and all seems to be working well
?
Just downloaded VR superwipe. I'm gonna redownload this Rom and give it another shot.
wrigbone said:
I was actually surprised and excited to see this update this morning but thought it would be ICS.
Long ago I rooted my phone just for gaining control and removing bloatware but ended up flashing my first rom with WildStang's Gingerbread OTA. After that I applied the "Warm" theme and been happy with that thinking there would be no more updates to this phone.
To the point - my question for you all is what do you mean by flash over? When the OTA is pushed is it just a patch or do they somehow send and entire install which removes the previous version, saves your data, installs the new version, and puts back your data? I don't have a problem with wiping and starting fresh, and it sounds like that is what everyone is recommending, I'm just trying to understand how it would even work flashing "over" my current version.
Click to expand...
Click to collapse
Flash over is just how it sounds. Literally flash on top of your current rom without wiping your data out.
Sent from my ADR6300 using xda app-developers app
If you want to go completely back to stock can you ruu back to 605.2? Then re ota to .15?
Topsnake said:
If you want to go completely back to stock can you ruu back to 605.2? Then re ota to .15?
Click to expand...
Click to collapse
Yes
I have a question.
I am running an ICS ROM how does this affect me....
Well my QUESTION is this:
What are the procedures to installing this and can I just reflash the ICS ROM I was on before.
The only updates with this push seem to be SMS and Bluetooth, is it even worth it?
Thanks for your time guys....
I performed a data/factory reset, cleared the cache partition as well as did a dalvik wipe but after installing it gets stuck on the white Incredible screen. Any ideas? Perhaps my kernal/radio? I honestly lost track of what kernal and radio I have so I am not sure.
So what's up with this ROM, I flashed like 3 times And it boots up.....then it starts a random reboot and just bootloops continuously. Is there any fix?
EDIT: seems the OTA update was a bust check this out........
http://forums.androidcentral.com/ve.../182357-dinc-system-update-4-08-605-15-a.html
Sent from my Galaxy Nexus using Tapatalk 2
@ cmlusco
So guy - you put this out here and it seems like everyone is having problems. How about some feedback. I'm getting ready to sell this phone in two weeks and want it to be on the current version but I'm not touching this ROM until I hear it freakin works. There are always a few people with issues but I'm not hearing anyone saying "flashed it and running with no problems". Appreciate the effort to get this out there but if your gonna take the time follow through on your commitment.
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Worse than I thought!
So It's worse than I thought... I gave up and re-flashed slim (ICS)... and the same problem still exists... boots up, looks normal, can't touch anything.... eventually it reboots....
Suggestions?
Would ODIN flash do anything different? I9000 bootloaders?
ScruffMcG said:
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Click to expand...
Click to collapse
sorry I'm just going to post twice so I can post to development...
yeah... 10char
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
Slimmed Down V10 by cbalt
Wipe Data/Factory Reset/Wipe Dalvik
Flash http://www.mediafire.com/?9p212pempybwnj3
Then Flash http://www.mediafire.com/download.php?bdjabcmobz6aw6k
Then Fix Permissions
Then Reboot
Click to expand...
Click to collapse
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
So you think w/bootloaders will help?
I have flashed every odin w/o bootloaders that I have access too and all get me stuck at ATT bootscreen....
Little hesitant to reflash my bootloaders since I was/am already on GB bootloaders, but if it might help I may have to do it...
I actually was on that JB version (but with the normal gapps b/c I wanted google now...)... now I'm on no version of anything hahah
takeoutttt said:
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
Click to expand...
Click to collapse
I met a problem. I do not know wether or not it is common. The phone will reboot by itself sometimes.
Do you have the same problem?
same here
seems as though many of the problems experienced by one are shared by the other
this is logical as they share many common points including the same partition and both jellybean derivations
I was having issues... accelerometer and audio issues.
All came out right as rain after flashing back to stock and reflashing
ScruffMcG said:
yeah... 10char
Click to expand...
Click to collapse
I see people have less chances to deal with call issues if they install CM10 through the clean way.
Please DON'T vote if you didn't install CM10 "correctly" and DON'T mention another issues here beside network related.
I think everyone has issues with CM10 no matter what....
At least one bug I got all the time: You can't make a video call in gtalk, it gets FC'ed immediately.
LarsPT said:
I think everyone has issues with CM10 no matter what....
At least one bug I got all the time: You can't make a video call in gtalk, it gets FC'ed immediately.
Click to expand...
Click to collapse
he's talking about calling through the cellular network, not gtalk or other issues. Please keep on topic.
I did a clean install of CM10 from the very start and had no call issues. I did experiment with an SU660 baseband before returning to V21b - and that also required a clean install. I guess I'm one of the lucky ones.
The problem I see here is what do you consider a clean install? I am not so sure myself.
Is smartflashing a BB then install CM10 clean enough?
I think of my installation as clean because
1) I came from CM7 (Temasek's last kang) after a factory reset.
2) Before that, I came from NVflash of Homero's ROM to recover from a corrupted CM9 leak flash
Since the first Nightly, I didn't have the "no audio in network calls" EXCEPT once with a Viber call where the other side could not hear me. It was fixed with a reboot.
BTW, I smartflashed 1 time during the 2-3rd nightly, to match RC's BB...
Now on yesterday's Nightly, 6 November, with auto time zone working finally.
machoman1337 said:
he's talking about calling through the cellular network, not gtalk or other issues. Please keep on topic
Click to expand...
Click to collapse
Oops sorry, I missed the "call".
Anyways, I always do a clean install, and I always get the audio bug (First nightly, and nightlies 3 and 4).
i have no problem on clean install.. wipe data partition,wipe cache,then advance wipe dalvic cache then format/system and format/cache then install zip from sd card,then wait till finish then use it more than 2 mins then reboot again to recovery then flash the gapps,then reboot.. voila i have no call issue,so far.. BTW i came from CM7 of gueste v3.7..
new2city said:
The problem I see here is what do you consider a clean install? I am not so sure myself.
Is smartflashing a BB then install CM10 clean enough?
I think of my installation as clean because
1) I came from CM7 (Temasek's last kang) after a factory reset.
2) Before that, I came from NVflash of Homero's ROM to recover from a corrupted CM9 leak flash
Since the first Nightly, I didn't have the "no audio in network calls" EXCEPT once with a Viber call where the other side could not hear me. It was fixed with a reboot.
BTW, I smartflashed 1 time during the 2-3rd nightly, to match RC's BB...
Now on yesterday's Nightly, 6 November, with auto time zone working finally.
Click to expand...
Click to collapse
the problem i think like new2city posted is misconception regarding clean install (full wipe)...
i myself didnt know what full wipe was but i googled it as i needed for flashing paranoid android rom(as it was my first custom rom) n what i found was...
1) wipe data/factory reset
2) wipe cache partition
3) mounts and storage/ format cache,data and system
4) advanced/ wipe dalvik cache
i do this before every installation whenever possible..
correct me if im wrong
EDIT: oops sorry didnt read the above post properly..
Allways did clean install. First time had audio problem after a few calls. Problem was gone when i changed bb
Sent from my LG-P990 using xda premium
why wait for 2 minutes?, before installing gapps. every time i just install it right after the nightly install finishes
up untill nightly 05 (always with clean install) tried like 5 different basebands and still had problems, am back gueste hybrid for now or if someone actually makes a stock-like ics I'll go there cause I need stability over nice and new software and to actually be able to use the phone side of my optimus at all times . I LOVE CM but for now it's a only a hassle.
the issues with calls dont appear just after flashing a new rom..they take from some hours to a day or two to start.
i reverted to cm7 with a nandroid backup with a factory wipe and...
cm10 call bug and plugging in the charger bsod bugs showed up
Sent from my Optimus 2X using xda premium
I continue with the problem
clean is installed, it worked perfectly after a day the problem a terrible noise.
Reinstall one baseband and followed the problem ..
Even if nothing gets fixed, thanks for this thread, now I've REALLY flashed a clean install
I formatted everything, my phone was even unbootable!!! Put the latest nightly in the external sd card and had to hold volume down to access CWM! It might be random or placebo, but the instead of the phone being a bit unresponsive at first, like the other times I flashed, it was great right from the first boot!! Even if doesn't fix the audio bug, thanks for this
Cheers!
With latest nightly of CM10 and clean instal i have more issues then before... very strange... i have baseband v20s and i am from Romania
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...