So I started to dabble into flashing roms with my new HTC One V PrimoC and now im trying to figure out if im doing anything wrong. I tried the latest nightly build for CM10 PrimoC, wiped all the good stuff in CWM, flashed rom, fastboot flash boot boot.img(from rom zip), and I get these annoying pop-ups saying my Android keyboard AOSP stops responding over and over, I even cleared the data on it and it still pop-ups and bothers me. Is this an issue with the rom itself?
Next one, Did the exact steps as I did for the CM10 PrimoC but this time i went with AOKP JB PrimoC I grabbed the latest nightly and all I get is a black boot screen... wtf is going on lol? I keep feeling like im doing something wrong but im following the instructions given on each page.. either the instructions suck, the nightlies have issues, problem with the kernel?, or i'm definitely doing something wrong lol. Anyone?
For aokp. Flash the latest stable version. Black screen of doom is known issue. The latest stable is sick. What I'm using
Sent from my Full Android on PrimoC using Tapatalk 2
aaronrw said:
For aokp. Flash the latest stable version. Black screen of doom is known issue. The latest stable is sick. What I'm using
Sent from my Full Android on PrimoC using Tapatalk 2
Click to expand...
Click to collapse
Are you using any special kernel or just the one in the AOKP zip?
reID_entify said:
So I started to dabble into flashing roms with my new HTC One V PrimoC and now im trying to figure out if im doing anything wrong. I tried the latest nightly build for CM10 PrimoC, wiped all the good stuff in CWM, flashed rom, fastboot flash boot boot.img(from rom zip), and I get these annoying pop-ups saying my Android keyboard AOSP stops responding over and over, I even cleared the data on it and it still pop-ups and bothers me. Is this an issue with the rom itself?
Next one, Did the exact steps as I did for the CM10 PrimoC but this time i went with AOKP JB PrimoC I grabbed the latest nightly and all I get is a black boot screen... wtf is going on lol? I keep feeling like im doing something wrong but im following the instructions given on each page.. either the instructions suck, the nightlies have issues, problem with the kernel?, or i'm definitely doing something wrong lol. Anyone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1996665
all u need guide
Sick kernel 2
Sent from my Full Android on PrimoC using Tapatalk 2
i have aokp up and running, just using the one that was inside the zip
cybervibin said:
http://forum.xda-developers.com/showthread.php?t=1996665
all u need guide
Click to expand...
Click to collapse
too bad i was already was doing all that before i read that post, the problem was not in the method of how i was flashing but rather the nightlies i was using.
Related
I tried loading a couple Jelly Bean roms for my Verizon GNex.
It's unlocked and everything and it was on 4.0.4 Build IMM76K with superuser and CWM recovery. The whole deal.
I ran recovery and tried to load these 2 ROMS, 2 seperate times starting from a fresh 4.0.4 build each time:
BAMF you jelly v1.3: http://forum.xda-developers.com/showthread.php?t=1744389
and
Team Liquid Vicious-toro V3: http://forum.xda-developers.com/showthread.php?t=1738018
Someone suggested to try a different kernel, but I'm not sure what that means.
What should I do?
are you using the touch recovery?
Did you WIPE DATA first?
Sent from my Galaxy Nexus using Tapatalk 2
Try Team Vicious's again, and be patient. I remember when I first flashed V1 I waited about 2-5 minutes before it brought me to the welcome screen. The Kernel that comes with Vicious is fine, although I've been using Faux's Kernel and am LOVING it.
You can flash kernels the same way you flash ROMs, as long as it is in a ZIP file, you are good to go. Just make sure it is compatible with Jelly Bean.
Let me know what method you are using to flash ROMs and I will try to be more detailed if needed.
Yes I am using the touch recovery. Am I not suppose to?
iamTWOcats said:
Yes I am using the touch recovery. Am I not suppose to?
Click to expand...
Click to collapse
its been known to have issues. use the regular cwm
Did you fix permissions?
What loading screen? Google screen or boot animation?
Jeez, people need to search for real, like 3 threads on this already. Why don't you ask over in respective rom thread? Better yet, I don't believe bamf or vicious devs would release a rom without making sure it boots.
Sent from my i9250
Zepius said:
its been known to have issues. use the regular cwm
Click to expand...
Click to collapse
Been using touch for months. Never had an issue.
Sent from my Galaxy Nexus using Tapatalk 2
Did you wipe data or try flashing over your other ROM?
Sent from my Galaxy Nexus using Tapatalk 2
Same boat here ..tried 2 different rom and kernel.. stock in boot loop.. last week I manage to flash vicious jb rom and it works great..then I try to flash different rom last night and im stock in boot loop and now back to ics.. I hope someone can help us with this..
Sent from my Galaxy Nexus using XDA Premium App
GNex stuck at Jelly Bean ROMs boot animation loading screen
I'm in a similar situation. After I flashed my Verizon GNex to Vicious Jelly Bean V3 everything seemed fine. So I decided to try my luck at flashing a theme as well. The phone is stuck on an endless JellyBean animation screen. My laptop no longer recognizes the Samsung drivers ie. they won't load, so I have no way to talk to this thing. I've tried to initiate recovery mode on the phone and it won't work either. Anybody know something I could try? I'm obviously new at this so any help would be appreciated.
Same problem over here with a friends Gnex. Same JB that installs and boots fine on my Gnex will not run on his. Weird issue
bk201doesntexist said:
Did you fix permissions?
What loading screen? Google screen or boot animation?
Jeez, people need to search for real, like 3 threads on this already. Why don't you ask over in respective rom thread? Better yet, I don't believe bamf or vicious devs would release a rom without making sure it boots.
Sent from my i9250
Click to expand...
Click to collapse
Jeez why don't you try helping the OP?
Has anyone still been getting these nightlies? Just checked this and had an update for cm10.1 which I thought was odd because it says the romantic was abandoned and I installed the update and now there is no service on my phone. Wifi still works though anyone else have this problem?
Sent from my Nexus 7 using Tapatalk HD
What Rom are you running? And where did you get it?
Sent from my Jelly Flavored Epic Touch
Double check to make sure you are not running a JB Modem??
btaylor545 said:
Has anyone still been getting these nightlies? Just checked this and had an update for cm10.1 which I thought was odd because it says the romantic was abandoned and I installed the update and now there is no service on my phone. Wifi still works though anyone else have this problem?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Are you talking about CMTeamEpic's CM10.1 nightlies? If so, I have flashed them as well. Once I do (regardless of a CM10 --> CM10.1 or Stock rooted GB/ICS --> CM10.1), I get the same problem with the modem. Under the about tab of settings, I see "Baseband Version Unknown". As seen in the attached screenshot. I'm going to continue to play around with the builds to see if I can find a workaround. Have you found one yet?
EDIT: I have also tried flashing the build then flashing the FF18 modem and then FL24 modem (both are ICS modems from rwilco) to no avail.
EDIT 2: You might want to change (or ask a moderator to change) the title of the OP to CM10.1, since that's what you're asking about.
EDIT 3: I figured out what the problem was. Some files leftover after flashing conflict with the 4.2.2 CM10.1 build. What I did to fix it was this: backup any important files on the internal memory, flash back to a stock ICS build (I chose FF18), factory reset from within the build (this clears everything on the internal memory), flash to a rooted ICS build (again, I chose FF18), flash a safe CWM bootloader, and flash the nightly you want. Hope this helps. Respond or PM me if you want more details.
dastin is using phantom freaks build bot and will be generating his nightlies. that's what your seeing. The other dev works was abandoned.
clean flash since its an entirely diff kernel now.
Sorry tried a couple different ways then gave up and went to CM 10.1 wild on the night. But what had happened was I was on CMTeamEpic's CM 10 4.1.2 and it sent me a CM 10.1 nightly in the CMupdater and I Installed it and the modem was crap but now that there is a work around for Netflix on Wild I'm sticking to this one. sorry I responded so late been crazy busy with work and what not.
Sent from my SPH-D710 using Tapatalk 2
I Found JellyBam v7.2.0 epicmtd stable rom here http://goo.im/devs/JellyBam/Samsung Epic 4G - Epicmtd
I tried installing it but failed in the recovery anyone willing to fix it? thanks
JellyBam was abandoned, so all JellyBam thread was closed
Almost all device had a problem of that
Sent from my JellyBeer v.4.14 epicmtd (b3)
Dropple said:
JellyBam was abandoned, so all JellyBam thread was closed
Almost all device had a problem of that
Sent from my JellyBeer v.4.14 epicmtd (b3)
Click to expand...
Click to collapse
Oh ok thanks for the info, also dropple thanks for jellybeer! :thumbup:
Sent from my SPH-D700 using xda premium
Jshugzda said:
I Found JellyBam v7.2.0 epicmtd stable rom here http://goo.im/devs/JellyBam/Samsung Epic 4G - Epicmtd
I tried installing it but failed in the recovery anyone willing to fix it? thanks
Click to expand...
Click to collapse
Hi, I just made the same mistake as you except that I'm stuck with that boot animation going in a loop until I take out the battery, I can put the battery back in and boot into recoverybut I've got nothing to flash as I deleted the last ROM I was using (omega rom).would anybody know how to fix my problem ?
crrryan said:
Hi, I just made the same mistake as you except that I'm stuck with that boot animation going in a loop until I take out the battery, I can put the battery back in and boot into recoverybut I've got nothing to flash as I deleted the last ROM I was using (omega rom).would anybody know how to fix my problem ?
Click to expand...
Click to collapse
Open a help thread in your device's Q/A forum. Our device never had a rom called "Omega".
I'm using a galaxy note 2, which does have one. After I booted it to teamwin recovery I played around and got it to work, so thanks anyway
Sent from my Nexus 10 using xda app-developers app
Hi ryan and hugz
Over the past week i have been trying to find a good rom for my epic. I think i have a bad phone, as any rom i use still has the same problems as stock.
I thought i hard bricked my phone a couple of days ago. Follow this thread to Odin back to stock, then root as usual, if you can not resolve your issues. Once back to stock and rooted, you should be able to restore nand, if you made one, once you reinstall cwm or twrp.
http://forum.xda-developers.com/showthread.php?t=1052813
Always remember to backup with TiBu to keep reinstalling apps simple.
Sent from a rooted candy bar
Hi guys,as the title says i cannot flah rom.
Well i can flash them but every rom has problem,I tried PAC,CM,SlimBean nothing work(or if it works,no more than one day or 2)
CM gives me MD5 errors,slimBean UI keep crashing,PAC every time i try to flash something in recovery(after flashing the rom)keep rebooting and stays on loop.
I know i mentioned specific roms and whatnot but at this time i don't think it's rom related(or recovery,i tried 3 different recovery),the only thing working flawlessly is the stock rom with root.
You guys have some advice? i've had the phone for about 5 months now and i wanted to try out roms but apparently i can't.
Cheers
Dave
Did you wipe everything when you flash new ROM?
Sent from my LT28h using xda app-developers app
pharix said:
Did you wipe everything when you flash new ROM?
Sent from my LT28h using xda app-developers app
Click to expand...
Click to collapse
the first time with CM no because i followed a guide which didn't.
But with PAC and SlimBean yeah i wiped everything.
The first time with PAC recovery went bad(i guess)and didn't let me wipe or flash anything,i flashed a stock tft repeated the process,the flash worked but as i reboot and tried to flash the on screen button it gave me the same recovery error.
maybe i do something wrong,i came from an HTC desire HD and the whole process was easier and less problematic
Fastboot the opensemc kernel beta2 kernel and then try again. Some people were having problems with flashing and Rayman has fixed it in his kernel apparently
Sent from my 4.2.2 Xperia S via Tapatalk
Ben36 said:
Fastboot the opensemc kernel beta2 kernel and then try again. Some people were having problems with flashing and Rayman has fixed it in his kernel apparently
Sent from my 4.2.2 Xperia S via Tapatalk
Click to expand...
Click to collapse
yep. CM it's now good,i kept following a wrong guide apparently
thanks for the help!
WiFi is not working on any rom except CM. I have wiped everything clean and done clean installs of Liquid Smooth 2.9 and AOKP MR2 and still nothing. I have event switched recoveries from CWM to TWRP and the GAPPS im using are 20130301. I am totally out of ideas here. I can live with CM but I really want to try AOKP MR2 as I hear it is quite good.
greysonofusa said:
WiFi is not working on any rom except CM. I have wiped everything clean and done clean installs of Liquid Smooth 2.9 and AOKP MR2 and still nothing. I have event switched recoveries from CWM to TWRP and the GAPPS im using are 20130301. I am totally out of ideas here. I can live with CM but I really want to try AOKP MR2 as I hear it is quite good.
Click to expand...
Click to collapse
Sounds like you might have flashed a newer Kernel with update WiFi drivers. I've read where that's happened and you have to revert (somehow?) to the old drivers for compatibility. I think this was an issue in KT's kernals, but you might want to do some reading and research on your own.
Rick-SG3 said:
Sounds like you might have flashed a newer Kernel with update WiFi drivers. I've read where that's happened and you have to revert (somehow?) to the old drivers for compatibility. I think this was an issue in KT's kernals, but you might want to do some reading and research on your own.
Click to expand...
Click to collapse
I did download a bootloader package and flashed it with CWM the zip was titled boot_CWM_I747UCDLK3 could this be the source of my problem?
greysonofusa said:
I did download a bootloader package and flashed it with CWM the zip was titled boot_CWM_I747UCDLK3 could this be the source of my problem?
Click to expand...
Click to collapse
Could be. I'd go back and read the instructions and changelog for it. If it loaded a different driver, you will need to re-flash the stock wifi driver, not usually included with other ROMs. Not sure if flashing the modem files would include those either.
So where would I score the default driver?
Sent from my SGH-I747 using xda app-developers app
greysonofusa said:
So where would I score the default driver?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I dunno. I suppose you could flash back to stock using one of the "toolkits" available and go from there. That would probably be my choice, but is probably the long way home, too.
Where have you looked so far? I don't use CM, so I haven't read those forums for you, but I would assume you aren't the only one to switch from CM to some other ROM.