ok so heres the issue, i know im not the only one that has it, since ive gotten my ns4g ive been running netarchy's cfs kernel on it (very nice kernel btw ) but sdcard doesnt mount all the time when i reboot, just wondering if anyone knows/found a way to manually mount it after boot.
thanks in advance
The one time I had it happen to me I booted in to CWM and changed the sd card mount status (I think it was set to unmounted and i changed to mounted)... havent had a problem since. Been using Net's kernel since first day I had the phone.
yea, i know after you flash a zip it goes back to being unmounted, was hoping there was a way to set it once os is loaded
Are you using CWM, or amon?
Sent from my sometimes infected,MIUI,Kings UNleashed Ultra Supersonic EVO...
cwm 3.0.2.4
NYYFan325 said:
The one time I had it happen to me I booted in to CWM and changed the sd card mount status (I think it was set to unmounted and i changed to mounted)... havent had a problem since. Been using Net's kernel since first day I had the phone.
Click to expand...
Click to collapse
Been having this issue with my i9020T. How can you install CWM with no USB connectivity? You also need USB connectivity to root as well as unlock the bootloader.
shabbypenguin said:
yea, i know after you flash a zip it goes back to being unmounted, was hoping there was a way to set it once os is loaded
Click to expand...
Click to collapse
After changing it that one time, I've flashed zips since and it still works. Doesn't seem to be an issue after I changed it the first time in CWM
I haven't found any rhyme or reason to the unmounting issue, but it happens almost every time I reboot. I keep an audio widget on my homescreen, where the widget skin is moved to the sd card. So at glance, if I see the widget skin, I know to reboot into clockwork and fix How's that for a ghetto approach.
I'd love to know what's causing this, or if there's a way to mount outside of clockwork.
EDIT: I had seen reports that it might be related to Netarchy's BFS kernel. To test, I flashed the CFS version this morning, and I'll test to see if it makes a difference.
FWIW.
I've never used the BFS, only CFS and I had the issue once as previously stated. Don't think that is the cause.
Well, related or not, since I went from bfs to cfs, it hasn't unmounted yet. I've tested various reboots, power downs, clockwork flashes, etc. but I'll keep testing.
Shabby, have u experienced this on the cfs version of the kernel?
Sent from my Nexus S 4G using Tapatalk
same as me. i'm using stock rom with bfs or cfs netharcy kernels. I'd love to know what's causing this too...
Hi
I have that same problem with sd card not being mounted and I didnt even install anything yet.
Did you get your problem fixed b'cas I didnt see any reply to yours.
Related
Hey guys, ran into a problem, I was able to root mytouch 3g and installed
http://forum.xda-developers.com/showthread.php?t=538633 3.6.8 release 4. Problem is when the phone goes sleepmode (screen turns black) after you wake it up the screen turns fuzzy/blurry. Is there an easy solution to this problem? or should I install a different ROM? Any suggestions? I really like this rom besides the blurry screen issue.
thanks for any help!
Hey same thing is happening to me...I wiped and reflashed but still having the problem
This is a problem many of us has encountered, I don't know why, try other ROM's I have found 1 that works for me.
I think it's a issue with the refresh rate of the screen.
Ditto. I have this problem as well with Cyanogen v4.0.1.
I've done the customary wipe prior to installing the ROM but the problem is the same.
This is the ROM I am using at the moment with no blurry screen problem.
http://forum.xda-developers.com/showthread.php?t=549755
i'm not using cyanogen but i am experiencing this issue with ZeroXd's Casper-4.2r2. i'm going to wipe the phone again and start over. So far, the Casper ROM is the only one that won't work for me and it was working well too
I'm having the same issue, but have ONLY noticed it with HERO-based roms. The Cyanogen 4.0.1 rom looked/worked fine.
Interested in the "fix" here...
Screen turns blurry
I am having the same issue but ONLY with the Hero roms. Cyanogen's new 4.xx roms are the frackin bomb so I'm not too sad. They work great for me. Definately want to know how to fix the issue though.
alot of ppl have this problem most of hero roms there is no fix yet sucks i know
yipcanjo said:
I'm having the same issue, but have ONLY noticed it with HERO-based roms. The Cyanogen 4.0.1 rom looked/worked fine.
Interested in the "fix" here...
Click to expand...
Click to collapse
what fix >?
Just experienced it for the first time after installing Drizzy's NoName V3. Have installed 10-15 roms prior and never experienced it until now. Trying out another Hero rom at the moment, will let ya know.
Update: QTek's rom seem's to work alright for me without the blur.
format sd card
seems to fix the problem....at least it did for me...
korndub said:
seems to fix the problem....at least it did for me...
Click to expand...
Click to collapse
The v3 noname I tried was on a newly partitioned/formatted sd card. :-\ QTek's is still going strong though. With the v3, after the first sleep it was blurry. I've been running QTek's for about 30-45 minutes now and no issues.
+1 to this issue. i had the same problem with some cyanogen ports in the sapphire thread, but using new cyan roms has not given me any issues. also noted that formatting does not help.
possibly an issue with engineering SPL?
i also noticed that a rom would flash fine, but as soon as my screen would lock thats when the issue would occur.
i wonder if it is a kernel / spl incompatibility. I had this same issue with JACxROM that runs great on and ION and is bassically the same phone. So I am a little confused. I am going to try and use Cyanogens newest 4.0.1 build and copy the boot.img to a JACxROM v1.3 and see if it does the same thing or not. Will report back to let you know what happened.
I have tried to use following HERO ROMs but they all turns blurry after sleep mode (when I unlock screen by pressing menu or similar button)
Champion v2, Fullv2 No Name, Superlite Hero etc.
Installed on myTouch 3g after rooting it using one click.
arunchowdhary said:
Installed on myTouch 3g after rooting it using one click.
Click to expand...
Click to collapse
Is this possibly *part* of the issue here? I'm using the "1 click" root method as well. Also, my SD card does have the proper 3 partitions, if that means anything.
Just installed the JACxHEROskiv1.4 ROM, which does not appear to exhibit this behavior. Nice ROM so far!
yipcanjo said:
Is this possibly *part* of the issue here? I'm using the "1 click" root method as well. Also, my SD card does have the proper 3 partitions, if that means anything.
Click to expand...
Click to collapse
I used the gold card method to root and I am experiencing the same thing with all the HERO roms. When you try to reinstall Cyanogens ROM's afterwards you experience the same thing. Only way I found to fix it was to format the SD card.
:/
We really need a fix for this. I am dying to use some Hero ROM's.
Well I fixed mine, I clean wiped everything and installed the cyanogen 4.0.1 rom. All is good now. I haven't messed with Hero, but I am liking the new cyanogen rom and he fixed the screen problem as well.
timafey said:
Well I fixed mine, I clean wiped everything and installed the cyanogen 4.0.1 rom. All is good now. I haven't messed with Hero, but I am liking the new cyanogen rom and he fixed the screen problem as well.
Click to expand...
Click to collapse
how did you go about clean wiping everything? I went ahead and bought a brand new sd card just to see if a fresh sd card cures it as well.
this is a kernel that i compiled direct from toast's HTC-Supersonic-2.6.29 source. toast and netarchy all put in their fixes and enhancements so i take no credit but altering the kernel that netarchy posted in this http://forum.xda-developers.com/showthread.php?t=719763 thread.
this is based off his 3.7.1 kernel that enables around 55-57 fps on both epson and novatek screens. Like he said, it disables the HDMI so if you need that, don't use this. in fact, this kernel will have all the issues that netarchy's 3.6.2 might have, but the touchscreen does work and you should still get ~55 fps average on fps2d.
this means that the kernel also comes with overclock and undervolt, compcache modules, audio boost and everything.
the kernel that's included is only compatible with ClockworkMod recoveries, sorry for those who use Amon_RA! i can't seem to make a working boot.img, and koush's way of updating kernels also is a lot easier to use
i highly highly doubt this has the possibility to break your phone but if it somehow does, i don't take responsibility.
once again, all credit goes to netarchy, toast, and all other people who i may have missed.
if you're using this kernel and get around 40 or so frames per second, here's probably the best thing to do. go to setCPU into the Advanced tab, and set the Up threshold to a value between 65-75. I chose 65 and i consistently get 55-57 average with stdev of 4 or 5.
edit: i just compiled a new kernel straight from Netarchy's sources, as he says that he updates his to the latest at all times. so, the new version is 3.6.4, because that's what his is. remember, this is exactly the same as his kernel, except that i just modified something to make it work for Froyo ROMs.
enjoy!!
edit: wifi does work, i think it's just that for some people who are flashing it over a ROM it might not work. I re-flashed evolution v9 and wi-fi worked again
using amon ra 1.7.0.1 i got
E: Missing file:
system/lib/modules/bcm4329.ko
E: verification failed
Installation aborted
this DOES NOT work.... but thanks for playing
scooter185 said:
using amon ra 1.7.0.1 i got
E: Missing file:
system/lib/modules/bcm4329.ko
E: verification failed
Installation aborted
Click to expand...
Click to collapse
yeah i doubt it works on amon ra, cause it's something made for clockworkmod. could you flash clockworkmod and then try this kernel, and tell me if it works?
btw, the bcm4329 appears because i found a kernel that i could use so i just replaced the zImage inside it. the original one was supposed to put the bcm4329 in /system/lib but i took it out cause it wasn't necessary.
will this work on the froyo sense rom?
infamousjax said:
this DOES NOT work.... but thanks for playing
Click to expand...
Click to collapse
could you please explain a bit more what's not working?
http://www.failhorn.com/
Wow... brutal guys.
look, guys.
i'm not trying to trick you guys. why don't you guys tell me what's wrong instead of telling me "fail" and giving me some stupid crap like failhorn.com
it works 100% fine on my phone, running EVOlaunchv9 froyo. so why don't you tell me what's not working and NOT be douches about it?
Douches.
Thanks for making this, man. I've been waiting for this kernel to support Froyo. Works great so far. Only thing is Wifi Tether isn't working, despite trying to reflash the fix from ffolkes thread. Might have something to do with clockwork recovery, though.
warmthsound said:
Douches.
Thanks for making this, man. I've been waiting for this kernel to support Froyo. Works great so far. Only thing is Wifi Tether isn't working, despite trying to reflash the fix from ffolkes thread. Might have something to do with clockwork recovery, though.
Click to expand...
Click to collapse
thanks. yeah i just noticed that wifi in general isn't working... and i can't figure it out. there might be something else i missed... but i'll keep looking.
thanks I'll load this up later when I flash my froyo build again.
justinisyoung said:
thanks. yeah i just noticed that wifi in general isn't working... and i can't figure it out. there might be something else i missed... but i'll keep looking.
Click to expand...
Click to collapse
Can you not use that patch that is in the Nova FPS kernel thread for the 802.11 N and 4G. Just a thought, when I flashed to the kernel in that thread I lost my wireless too and then i flashed that patch and it started working again. I am new to this game, sounds logical to me lol.
Worked great on my phone, running Damage Control's newest. The only thing is that I had 5 points of touch with the kernel just for the novatek screen and 44fps. With this kernel I only had 3 points of touch and only 41fps. Still good work, dont let those other guys get you down. Thanks
Noticed this is based off 3.6.2
Maybe the wifi problem will go away if 3.6.3 is used instead. Looks like the audio boost patch was removed as it was causing problems with bluetooth, and no fluffy pink bunnies were harmed in the making of 3.6.3 so its peta approved
I had 5 touch points using Dotty on ffolkes kernel.. Only got two with this one.
Sent using the power of swype.
good god there are some real ******** on this board as of late !
op thx for the work when i flash a 2.2 ill give it a shot
Way to show this Guy support you tools!!!!!!!!
tried it running evolution v9. everything worked great except for wifi which was already stated. appreciate the work you've done. thx
when i get home from work i'll see if i can build the kernel again. it might be 3.6.3-based if netarchy and toast updated the kernel source on github, but otherwise we'll be stuck with this one till they do so.
sorry about the wifi guys, i spent a few hours and i could not get it to work. but if you flash the wifi/4g fix on ffolkes's kernel's page (the link is on the first post), you'll get wifi tether working at least
I've been flashing kernels through Clockwork, but I decided to download Kernel Manager Lite and I'm considering trying it. Has anyone had any experiences with it, good or bad? I'd appreciate any feedback before giving it a go. Thanks
it's works flawless for me, i use the free one.
The only problem I've run into was flashing a kernel while on BAMF 1.6, it worked but broke wifi. I flashed the same kernel using clockwork and wifi was back with no problem. I read someone else had the same problem.
Sent from my ADR6400L using XDA Premium App
That might have been me and more of a 1.6.1 ROM issue which has Kernel Manger Lite included. My story:
http://forum.xda-developers.com/showpost.php?p=13444295&postcount=351
icesteve said:
The only problem I've run into was flashing a kernel while on BAMF 1.6, it worked but broke wifi. I flashed the same kernel using clockwork and wifi was back with no problem. I read someone else had the same problem.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I was using kernel manager pro when I attempted, not the one included in the rom. I figured it had to be kernel manager because CWM flashed it perfectly.
Sent from my ADR6400L using XDA Premium App
Thanks for the responses. I'll probably give it a try. I guess I can always reflash through Clockwork if anything goes wrong. Or worse case, I can flash a backup if anything gets seriously out of whack.
bunklung said:
That might have been me and more of a 1.6.1 ROM issue which has Kernel Manger Lite included. My story:
http://forum.xda-developers.com/showpost.php?p=13444295&postcount=351
Click to expand...
Click to collapse
I had the same problem .. I never considered that it may have been kernel manager .. thanks for that
Sent from my ADR6400L using XDA App
For me the issue is this ...
No backup made prior to flashing ... I'm sticking w/ RM for kernel flashing
Based on my experience with BAMF rom and leanKernel, it appears that any customization scripts and/or files that the kernel developer intended for you DO NOT get flashed with Kernel Manager (I have Pro version). The people with broken wifi using KM but working wifi with RM proves the point. My experience was that 4G hotspot didn't work when flashing leanKernel from KM, but works fine with an RM flash. This is actually a common problem across several devices I've used. Many kernel devs modify the wifi driver and/or other things in a manner that they end up only working with their specific ROM. The do this by including the modified files in their zip package along with a script telling the phone what to put where. The issue becomes if you switch to a kernel that's relying on a stock wifi driver, and doesn't put it back on its own, then you've got a busted wifi. The only way around that is to manually push/restore a copy of a wifi driver known to work with the kernel you're using. I kind of regret paying for the pro version after finding this out; hopefully the KM folks can figure it out. The kernel itself is just the boot.img file; the add-ons files that go into the /system partition or where-ever. If you're interested in knowing what a particular kernel is pushing on your phone, just open the zip file and drill down through the folders to find what files are in /system tree. This is also a way to find files you need to go back to stock drivers, just find a stock rom that's flashable in RM and drill down to the files in /system/lib and push them back to the phone via adb or root explorer.
i bought the pro version and i wish i hadn't. i downloaded/flash one of protekks kernels through there and it sent my phone into a bootloop and by the time i'd flashed a nandroid backup the 15 minutes had gone by -_______-
why?
I haven't actually tried this yet, I guess the question for me is why? Does it do something that CW cannot do? I don't know much about the product so I am just trying to understand the benefit of installing it.
turbosrrgood said:
I haven't actually tried this yet, I guess the question for me is why? Does it do something that CW cannot do? I don't know much about the product so I am just trying to understand the benefit of installing it.
Click to expand...
Click to collapse
It will notify you of kernel updates, and you can filter kernels based on what you want
Sent from my ADR6400L using XDA Premium App
Just wanted to start off and say a BIG THANKS for LinuxBozo and his amazing infuse mod which lets us use the other samsung roms (JVQ restricted )
I have been experimenting ALOT with various roms and thought i would share some of which i have tested out so far, the only one which gave me some issues was Sensation 2.0 , seems like when you reboot, sometimes you get no netwrok, then reboot, and icons are missing, so its a question.
Obviously this isnt really an OFFICAL rom for the Infuse, but id like to know if anyone else has had nice experience or recommendations for use with this dude's rom.
Galaxy S I9000 ROMS
[ROM][07/07/2011] - Ryyu's EDB v1.3 [JVQ] -- New Improvements!
http://forum.xda-developers.com/showthread.php?t=1133395
[ROM] SpeedRom [JVQ][Fast & Stable] NEW NEW
http://forum.xda-developers.com/showthread.php?t=1189625
[ROM][19/7] GingerReal - V7.1.4 JVQ - Time to Downgrade - stability and speed
http://forum.xda-developers.com/showthread.php?t=1155623
[ROM] [22.07.2011] DarkyROM v10.2 ★ JVQ ★ What are you waiting for?
http://forum.xda-developers.com/showthread.php?t=814091
[ROM][02/08/2011] Tiramisu EVO 6.0/6.7 Summer Edition! JVP/JVQ BIG UPDATE OUT!
http://forum.xda-developers.com/showthread.php?t=1171476
Captivate Roms
[ROM][2.3.4][JVQ]Continuum v6.1 - v6.2 Beta Now Open!
http://forum.xda-developers.com/showthread.php?t=1136128
[ROM][2.3.4][JVQ][UPDATE: 7/31] DlevROM Version 4.2: Mods and Features Galore!
http://forum.xda-developers.com/showthread.php?t=1146176
{2.3.4 ROM} Mosaic VI {Team Phoenix}{7/30/2011}
http://forum.xda-developers.com/showthread.php?t=1061203
VIBRANT ROMS
[ROM] RevolutionRom JVQ Final Update 2 (2.3.4) 7.31.11 Definitely Fixed Bluetooth
http://forum.xda-developers.com/showthread.php?t=1192438
So this hack seems to be another way to get Gingerbread on your phone. Interesting.
I have been running Darky all day with no problems. Very fast and stable.
Sent from my GT-I9000 using XDA App
Just wanted to throw it out there I ran a JVP based ROM without issue for an hour or so. The only thing I had to do was add my APN settings back & all was well. Someone may need to test this a bit more but my experience went well.
Does the darky rom support HSPA+?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Auto-Android said:
Does the darky rom support HSPA+?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
Hellraiser uses the same Rogers RIL that Infused v2 does, so probably not. (RIL is one of the things that gets swapped out.)
It's often hard to tell for sure because many frameworks won't show HSPA+ even if the RIL/modem are operating in that mode. Hell, even our original Froyo ROMs were broken in that way - they displayed UMTS when in HSPA+ mode. (UMTS is plain vanilla 3G.)
GingerReal - V7.1.4 JVQ
Been running GingerReal V7.1.4 JVQ with Infusion GB kernel and I must say it's snappy. I have not had a single problem with anything. And from what I read Quadrant scores don't mean much, but I got a 3500 OC at 1.6. without Stagefright. I did'nt know Stagefright was til I Googled it. But my phone is very fast and I am very happy. Thanks Linux
Infiniti350GT said:
Just wanted to throw it out there I ran a JVP based ROM without issue for an hour or so. The only thing I had to do was add my APN settings back & all was well. Someone may need to test this a bit more but my experience went well.
Click to expand...
Click to collapse
Which ROM did you test for JVP , i might give it a whirl, i finally finished going through all those roms, The Vibrant rom wasnt very exciting, and seemed to lack the extended power menu drop down which has Reboot, recovery download mode and such, thats a big thing for me.
Darky was my favorite so far,I might try Sensation. If anyone wants to test out a couple JVP roms and try adding in the APN settings, lets see what comes up and post which rom you tested.
Thanks everyone for their input on this, im getting more interested now and i will be trying to use the Infusion Kernel with some of these roms and see if i get a performance boost.
Im not sure if its just me, but whenever i reboot ANY of those roms which are installed with Linux's software , it seems sometimes the icons on the app drawer l ike disappearing, then when i reboot, apps reappear, but the Network to ATT gets cut off, then i reboot again, and sometimes its normal..........Any ideas?
prasadudwadia said:
Which ROM did you test for JVP , i might give it a whirl, i finally finished going through all those roms, The Vibrant rom wasnt very exciting, and seemed to lack the extended power menu drop down which has Reboot, recovery download mode and such, thats a big thing for me.
Darky was my favorite so far,I might try Sensation. If anyone wants to test out a couple JVP roms and try adding in the APN settings, lets see what comes up and post which rom you tested.
Thanks everyone for their input on this, im getting more interested now and i will be trying to use the Infusion Kernel with some of these roms and see if i get a performance boost.
Im not sure if its just me, but whenever i reboot ANY of those roms which are installed with Linux's software , it seems sometimes the icons on the app drawer l ike disappearing, then when i reboot, apps reappear, but the Network to ATT gets cut off, then i reboot again, and sometimes its normal..........Any ideas?
Click to expand...
Click to collapse
BTW, the default behavior in Sensation is no extended power menu, but if you use the app "Theme Settings (included in the ROM) you can change this.
As to the other issues - that's a new one, I haven't seen it before.
prasadudwadia said:
Which ROM did you test for JVP , i might give it a whirl, i finally finished going through all those roms, The Vibrant rom wasnt very exciting, and seemed to lack the extended power menu drop down which has Reboot, recovery download mode and such, thats a big thing for me.
Darky was my favorite so far,I might try Sensation. If anyone wants to test out a couple JVP roms and try adding in the APN settings, lets see what comes up and post which rom you tested.
Thanks everyone for their input on this, im getting more interested now and i will be trying to use the Infusion Kernel with some of these roms and see if i get a performance boost.
Im not sure if its just me, but whenever i reboot ANY of those roms which are installed with Linux's software , it seems sometimes the icons on the app drawer l ike disappearing, then when i reboot, apps reappear, but the Network to ATT gets cut off, then i reboot again, and sometimes its normal..........Any ideas?
Click to expand...
Click to collapse
I ran Hawkish 4 http://forum.xda-developers.com/showthread.php?t=1032599
I chose it because I saw that the ROM included the background effect from the SGSII, which while I have the SGSII & this feature seems to throw my photos to the way over saturated side - its more appealing for home screen settings and every day use since everything just looked almost wet or gooey. But the setting didn't work I imagine a kernel conflict, but I'm sure this could be built into one of our ROMS later and I wouldn't mind helping out with putting it together.
Overall I thought this ROM was a little laggy for the phone, I'm sure there are others out there that could run MUCH better or smoother.
I find it funny that we get a stock phone and find it boring so we flash a brand new phone to something completely different within an hour and when the next phone comes out we want their stock stuff so we can see how it is on OUR phone...HAHAHA -addicted
Infiniti350GT said:
I ran Hawkish 4 http://forum.xda-developers.com/showthread.php?t=1032599
I chose it because I saw that the ROM included the background effect from the SGSII, which while I have the SGSII & this feature seems to throw my photos to the way over saturated side - its more appealing for home screen settings and every day use since everything just looked almost wet or gooey. But the setting didn't work I imagine a kernel conflict, but I'm sure this could be built into one of our ROMS later and I wouldn't mind helping out with putting it together.
Overall I thought this ROM was a little laggy for the phone, I'm sure there are others out there that could run MUCH better or smoother.
I find it funny that we get a stock phone and find it boring so we flash a brand new phone to something completely different within an hour and when the next phone comes out we want their stock stuff so we can see how it is on OUR phone...HAHAHA -addicted
Click to expand...
Click to collapse
I think those are controls for Voodoo Color which:
1) Is extremely difficult to implement on our device (significantly different screen)
2) Is not necessary on our device - our screen fixes most if not all of the problems VC was intended to fix.
Entropy512 said:
I think those are controls for Voodoo Color which:
1) Is extremely difficult to implement on our device (significantly different screen)
2) Is not necessary on our device - our screen fixes most if not all of the problems VC was intended to fix.
Click to expand...
Click to collapse
Yes sir, I believe you are exactly right. I normally don't like over saturation, but on a HUGE screen it looked great with some gooey gingerbread green stuff around it. My photography looked horrible especially HDR shots, worth it though. The colors on the SGSII and this phone are pretty different tho. But a lot to do with the same resolution on a smaller screen. The screen on the Infuse is a big (no pun) factor that held me to it rather than the SGSII
bigfau said:
Been running GingerReal V7.1.4 JVQ with Infusion GB kernel and I must say it's snappy. I have not had a single problem with anything. And from what I read Quadrant scores don't mean much, but I got a 3500 OC at 1.6. without Stagefright. I did'nt know Stagefright was til I Googled it. But my phone is very fast and I am very happy. Thanks Linux
Click to expand...
Click to collapse
i as well got the same results, but did you have a problem with the modem. mine would work for about 3 min and then i would no longer have network connection.
i had to change the modem to get it work really smooth, but yes this set is pretty good.
Infiniti350GT said:
Just wanted to throw it out there I ran a JVP based ROM without issue for an hour or so. The only thing I had to do was add my APN settings back & all was well. Someone may need to test this a bit more but my experience went well.
Click to expand...
Click to collapse
Man! I'm so upset. I flashed this ROM twice, but it would not boot. Did you flash from stock? I don't know what I did wrong.
tekgurl said:
Man! I'm so upset. I flashed this ROM twice, but it would not boot. Did you flash from stock? I don't know what I did wrong.
Click to expand...
Click to collapse
Okay heres me scenario, hope it helps understand.
1) started off with phone already rooted and such and previously had Infused V2.00 full., Downloaded a JVQ rom ( like Darky's ) , and then downloaded Linux Bozo's rom/mod ) Put both of the zips on the ROOT of the internal SD .
2) backup info and boot into Red recovery.( Shut off device, then hold Vol - and + while pressing power ), release power and continue holding both volume keys).
3) Perform the following
Wipe Data/Factory Reset, Wipe Cache partition, Wipe Dalvik Cache
Install zip from SD card and select the ROM you want to use
Do install from SD card again and this time select the Linux Bozo zip
4) Reboot and you will be in your rom after 10 minutes ( be patient, it takes time ). If you want better performance, install the Infuse GB Kernel. Get it here
http://forum.xda-developers.com/showthread.php?t=1212485
5) Enjoy the rom
prasadudwadia said:
Okay heres me scenario, hope it helps understand.
1) started off with phone already rooted and such and previously had Infused V2.00 full., Downloaded a JVQ rom ( like Darky's ) , and then downloaded Linux Bozo's rom/mod ) Put both of the zips on the ROOT of the internal SD .
2) backup info and boot into Red recovery.( Shut off device, then hold Vol - and + while pressing power ), release power and continue holding both volume keys).
3) Perform the following
Wipe Data/Factory Reset, Wipe Cache partition, Wipe Dalvik Cache
Install zip from SD card and select the ROM you want to use
Do install from SD card again and this time select the Linux Bozo zip
4) Reboot and you will be in your rom after 10 minutes ( be patient, it takes time ). If you want better performance, install the Infuse GB Kernel. Get it here
http://forum.xda-developers.com/showthread.php?t=1212485
5) Enjoy the rom
Click to expand...
Click to collapse
I've successfully flashed a JVQ Rom. I'm trying to figure out how Infiniti350 was able to flash a JVP Rom.
tekgurl said:
I've successfully flashed a JVQ Rom. I'm trying to figure out how Infiniti350 was able to flash a JVP Rom.
Click to expand...
Click to collapse
I just followed the exact instructions the OP posted up above. With 1 mishap, when I downloaded what I thought was the ROM....I only got the lock-screen (what happens when you read things way too fast & think you know what you did) which I already downloaded and flashed
I mounted the SD card while in recovery and pushed the file containing the ROM over to the phone - flashed it - flashed LinuzBozo's stuff - rebooted & things went well all I had to do was add APN's back.
I really like my current set up BUT I'll probably find something else, before I load the ROM I want I'll run this again with a JVP base and see how things go & defiantly let you guys know. Now I'm curious why it doesn't work for other people.
Infiniti350GT said:
I just followed the exact instructions the OP posted up above. With 1 mishap, when I downloaded what I thought was the ROM....I only got the lock-screen (what happens when you read things way too fast & think you know what you did) which I already downloaded and flashed
I mounted the SD card while in recovery and pushed the file containing the ROM over to the phone - flashed it - flashed LinuzBozo's stuff - rebooted & things went well all I had to do was add APN's back.
I really like my current set up BUT I'll probably find something else, before I load the ROM I want I'll run this again with a JVP base and see how things go & defiantly let you guys know. Now I'm curious why it doesn't work for other people.
Click to expand...
Click to collapse
I think sometimes people either have a bad flash or don't properly wipe data. Same reason lots of people randomly had problems with Infused. (I haven't tried JVP myself though.)
Well, i just finished wrapping up my favorite roms, and i keep jumping between the Sensation rom, and Darky's Rom .
BUT!
I always data wipe, clear cache, factory reset
Idk if this helps, but i saw theres a new Linuz BETA 6 , perhaps this might help problems that a few have been going through.
In closing, i really hope more ROMS designed for the Infuse come fast , i got a feeling with this new mod there will be many to come
Entropy512 said:
I think sometimes people either have a bad flash or don't properly wipe data. Same reason lots of people randomly had problems with Infused. (I haven't tried JVP myself though.)
Click to expand...
Click to collapse
This is a very good point. The data wipe is vital for the Infuse no matter what. I have tried it with and without the wipe & all sorts of very strange things go wrong at random. Market apps wont download - Errors when using data - Youtube errors - issues with email. Each time I did it different ones would act up too, never the same.
Full Wipe so far has fixed it without failure
*Edit - Full for me same as prasadudwadia said above - data, cache, and factory reset.
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.