So I have installed CWM, flashed the kernel to the DooMKernel, updated the wifi modules and attempted to install all of the custom ROMs out there. Every tine I get past istalling the ROM, I go into a reboot loop at the splash screen, almost like a kernel panic or something. Any thoughts or assistance? It could just be a dumb n00b move, as this is the fist time I have attempted to play aroubd with an Android device.
Thank you!
have you tried a factory reset before flashing the rom?
UkranianDroid said:
So I have installed CWM, flashed the kernel to the DooMKernel, updated the wifi modules and attempted to install all of the custom ROMs out there. Every tine I get past istalling the ROM, I go into a reboot loop at the splash screen, almost like a kernel panic or something. Any thoughts or assistance? It could just be a dumb n00b move, as this is the fist time I have attempted to play aroubd with an Android device.
Thank you!
Click to expand...
Click to collapse
The first boot after flashing a custom ROM takes a while as the dalvik cache was cleared. Give it time. But you should have:
unlock bootloader
root using doomlord's method
flash(install) doomlord kernel
flash wifi module from doomlord
make nandroid backup of current rom(optional but always a good idea to practice backing up data)
wipe cache and dalvik cache
wipe data
install zip from sd card
reboot
(I think I listed everything lol, I'm at work proctoring an exam)
Those are the basic steps. Check out the forums for the exact steps in flashing the kernel and wifi module. If you need more help after running through this list, PM me.
UkranianDroid said:
So I have installed CWM, flashed the kernel to the DooMKernel, updated the wifi modules and attempted to install all of the custom ROMs out there. Every tine I get past istalling the ROM, I go into a reboot loop at the splash screen, almost like a kernel panic or something. Any thoughts or assistance? It could just be a dumb n00b move, as this is the fist time I have attempted to play aroubd with an Android device.
Thank you!
Click to expand...
Click to collapse
First of all, the ONLY "custom" ROM for the Jetstream is here: http://forum.xda-developers.com/showthread.php?t=1422413. So please clarify your statement about installing all of the custom ROM's out there?
UkranianDroid said:
So I have installed CWM, flashed the kernel to the DooMKernel, updated the wifi modules and attempted to install all of the custom ROMs out there. Every tine I get past istalling the ROM, I go into a reboot loop at the splash screen, almost like a kernel panic or something. Any thoughts or assistance? It could just be a dumb n00b move, as this is the fist time I have attempted to play aroubd with an Android device.
Thank you!
Click to expand...
Click to collapse
so far only one rom out there.
disconnect the USB cable and try to boot. sometimes that keeps it in the infinite loop.
Jetstream
Hi guys, I'm very new to my Jetstream and all the android world, I managed to root it and everything but when doing calls on the GSM network there is no sound, I tried using wireless headsets, wired ones and even speakerphone but no luck, any ideas about it?? I'm guessing that on the build.prop file where I enable the gsm calls must be something else that I need to activate in order to get sound. regards and sorry for the long post
its not working yet. your not the only one...
There is more than one ROM for the jetstream at the moment- four to be exact. Check the development forum.
Related
Hey all, I know this has been discussed to death but I had never had this issue til yesterday... I started having the sideload errors when trying to flash any custom kernel immediately after the ROM IN TWRP 2.0. I've now tried this on every version of TWRP and still can't get it to take. I am s-off and only do full wipes prior to any flashing, cache/dalvik between flashing of ROM and the kernel. Any input would be greatly appreciated... I'm at work right now otherwise I'd just unearth one of the old threads likely asking this same question. Anyone who can help me troubleshooting this will get well deserved thanks of course.
Just to add to this... I just went through and flashed a kernel by itself in TWRP 1.0.3 after clearing cache/dalvik. I just don't understand why I would be able to do this by itself, but not in the same recovery session as I've always done...
its a scripting error in the update-binary not your phone
Well this now seems to randomly happen with any of the .zips on my phone and using any version of TWRP. I can't imagine what caused this, It's just so frustrating... I basically have to reboot to recovery several times to get all the zips I need to flash.
joehunni said:
Hey all, I know this has been discussed to death but I had never had this issue til yesterday... I started having the sideload errors when trying to flash any custom kernel immediately after the ROM IN TWRP 2.0. I've now tried this on every version of TWRP and still can't get it to take. I am s-off and only do full wipes prior to any flashing, cache/dalvik between flashing of ROM and the kernel. Any input would be greatly appreciated... I'm at work right now otherwise I'd just unearth one of the old threads likely asking this same question. Anyone who can help me troubleshooting this will get well deserved thanks of course.
Click to expand...
Click to collapse
i would recommend d/l twrp 2.0.1 just released. make sure you wipe cache/devlic/system/factory default... I usually would do this in this order... a factory / sys/ dev/ cache wipe and then flash your new stuff and work with the new rom you wish to flash ... I did it and it worked well on 2.0.1 .... not the 2.0
Hey all,
I'm very new to Cyanogen, so sorry if this is a very n00b question.
The ROM Manager doesn't appear to work. It keeps telling me I'm not running ClockWorkMod recovery, and cannot connect to the web to download. I purchased the premium version thinking it would solve this (as well as to support the dev), but no luck. Is it just an issue with the nightlies not capable of handling ROM manager yet, or is it a setting of some sort that I'm neglecting? It's not a huge deal, but it looks like such a nice, simple way to stay up-to-date with the nightly builds as opposed to updating through CWM, wiping, etc.
I saw a post mentioning to go into developer tools and enable root access. The closest I found was in settings and I allowed apps and ADB root access, but this didn't help.
Any suggestions would be greatly appreciated, thanks!
I'm a bit confused, Why do you require ROM manager? The CWM that is built in with the ICS Kang releases should be doing everything that is required, then again, your reply would matter.
I think I am having the same issue. When I try to Flash ClockworkMod Touch in Rom Manager it keeps telling me I need to first install ClockworkMod Recovery even though I have Recovery 5.5.0.4 currently installed. It did the same thing when I had Recovery 4.0.0.4 installed.
I even tried to "Flash ClockworkMod Recovery" (First option in ROM Manager) and it does nothing.
Any ideas?
BEcause the same menu is in the CWM recovery lol
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
From what I've heard the ROM Manager doesn't really work for the tab yet. If you want to update without replacing all your apps you can just flash the zip file in CWM without doing a wipe. If it causes problems then you could do a wipe & reflash afterwards.
Dolfan058 said:
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
Click to expand...
Click to collapse
ROM manager works but it's wonky on the ICS kangs. It doesn't do anything that you can't already do in recovery, so there's no real advantage anyways. Oh, and don't use ROM manager to install a new recovery, and CWR touch doesn't work for the GT10.
^You saved me the trouble of insisting Why thank you good sir.
Thanks for the replies. I'll keep updating through CWM.
Coffeebeans, obviously I'm following your thread (thanks for the good work!) and I tried flashing over once but I got a ton of process media FCs so I figured wiping was the best way to go and have done so ever since. Probably should invest in titanium backup at this point so I don't have to reinstall from market everytime I wipe.
Thanks again for the help y'all.
It worked once with 4/17 build of CM9. After that, it has never worked again. It boots into recovery and pretends its flashing, but stops half a second later and restarts.
Something odd happened today when I tried to update. It rebooted and phone locked up and screen went black. I took out the battery and put it back in then held up and power to go into CWM. All of a sudden Rom Manager took over and flashed the rom as well as the additional zips successfully and rebooted. Everything works.
CWM tries to flash from /emmc. Rom Manager tries to flash from /sdcard and fails. It may be due to the swapped mount points on CM9. in CWM they are still swapped, even if you check the use internal storage box and everything shows up properly in CM9.
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
drsane1984 said:
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
Click to expand...
Click to collapse
jumping from one rom to another needs a full wipe i guess... when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
First of all, thank you for your reply!
Now, to adress each step
jumping from one rom to another needs a full wipe i guess.
Click to expand...
Click to collapse
Yup, did one (factory reset+system wipe) before trying to flash AW Rom.
when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
Click to expand...
Click to collapse
After the first three unsuccessfull attempt to flash the ROM did I wipe my internal SD, so it isn't the crawling looping intro's problem. And yes, I push ROMs via Adb, and trying flashing.
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
Click to expand...
Click to collapse
That was actually the last step I tried before asking for help. Even after I typed this post, I did it again. Flashed it, pushed AW, and flashed again. No success.
*Edit: I have forgotten a primary Troubleshooting technique. Downloading AW2.1 from a different source, will update.
sorry but im not much of a help i can see... hope somebody could. don't lose hope though...
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
drsane1984 said:
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
Click to expand...
Click to collapse
Hello Everybody! Guys, sorry for my english!!!!!
First of all, I have to present myself, my name is Marco, I'm italian, 25 years old and I'm in the Android world since about 12 Years.
I started whit a Galaxy S2, and after I bought an Asus Transformer Prime.
After just two week, I decided to put in a Custom ROM, on my devices, and I understood how the system work better instead of a Stock ROM!
And after, I understood, how the XDA Developers Forum is important for me, and expecially for all the people who like to learn about the Android World.
So, I just want to Thanks with all of you for the support that i receive EVERY DAY to solve my problems!
One of these was with flashing the Androwook, weeks ago I flashed the Team EOS 2.0, that was really amazing, but after a While, I found some slowdowns in some action on the system, so i decided to try a rom based on the stock rom, but with improvement and tweaks, so what's better then the Androwook?
The problem was, the same explained on this post, after all wipes, the prime was not boot, and stuck in bootanimation!
I solved, checking the box "Install custom ROM" as drsane1984 have done, and now the ROM is booted perfectly!!
Thanks another time! I'am convinced that if you are able to seach, you'll find for sure the solution to your problems! If not, just ask!
Bye!
Hi guys. I just rooted my DNA tonight but after getting it all done i find that i have no WIFI working. Can anyone help me figure out why this is happening??
Predtechhacker said:
Hi guys. I just rooted my DNA tonight but after getting it all done i find that i have no WIFI working. Can anyone help me figure out why this is happening??
Click to expand...
Click to collapse
not sure...but if you are properly rooted, perhaps just reflashing whatever current kernel you are on will cure that (and the proper modules). Not 100% sure that is the cure, but from flshing various Mods, kernels and rooted applications which "killed" my phone, whenever I used my nandroid to get back to a normal place I have had to reflash the kernel to make WiFi work
I'm having the same problem. I'm running a stock kernel, please reply if that works for you.
I've searched the problem the only thing I could come up with was to re flash the kernel but since Im running the stock kernel and haven't flash another in the first place that doesn't help me much.
ManOfMyth said:
I've searched the problem the only thing I could come up with was to re flash the kernel but since Im running the stock kernel and haven't flash another in the first place that doesn't help me much.
Click to expand...
Click to collapse
Ok, i got a LOT figured out with this phone last night. It seems that if you flash a custom kernel WITHOUT flashing the modules that go with that kernel in recovery, then you'll lose wifi and possibly some other stuff.
I had flashed a custom kernel and not correctly flashed the modules with it so therefore i lost wifi.
To fix this, simply reflash the kernel in fastboot and then go DIRECTLY into recovery from teh bootloader and flash the modules, then simply reboot. There's no need to wipe and cache or dalvik cache.
If you HAVEN'T flashed any custom kernel then just look for the stock kernel modules on this forum (a simple search will yeild results) and ket the unsecured stock kernel too and flash them and you'll be set to go.
Hope this helps you guys out
Q&A for [ROM][Player4][US/Intl] Cyanogenmod 11 for the Galaxy Player 4.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Question: CM11
Hi,
i tried to flash the cm11, but the flash didn´t start. Do i need root? I have the Steves Kernel, does this work with the CM11?
Thanks for reply.
Matthias
semmelbroessel said:
Hi,
i tried to flash the cm11, but the flash didn´t start. Do i need root? I have the Steves Kernel, does this work with the CM11?
Thanks for reply.
Matthias
Click to expand...
Click to collapse
Ok so first you need to use the terrasilent kernel. Then upon flashing the ROM, you need to wait 10 secs then you can force restart the device. After this, the installation process should continue on it's own. At the end. You will be rebooted a last time into CWM in which, you can flash the gapps if you want.
zaclimon said:
Ok so first you need to use the terrasilent kernel. Then upon flashing the ROM, you need to wait 10 secs then you can force restart the device. After this, the installation process should continue on it's own. At the end. You will be rebooted a last time into CWM in which, you can flash the gapps if you want.
Click to expand...
Click to collapse
THX, the Kernel flashing with odin? And then the rom by CWM? Correct? Do i need ROOT?
semmelbroessel said:
THX, the Kernel flashing with odin? And then the rom by CWM? Correct? Do i need ROOT?
Click to expand...
Click to collapse
Yeah, you flash the kernel with odin and then the rom with CWM. You don't need root to proceed with the installation of the rom.
Flashing Cyangenmod
What I don't understand is how to flash the zip. When going into recovery mode, the phone doesnt see it and I can't seem to use Odin because its the wrong file extension. So how do I do this?
msigalov said:
What I don't understand is how to flash the zip. When going into recovery mode, the phone doesnt see it and I can't seem to use Odin because its the wrong file extension. So how do I do this?
Click to expand...
Click to collapse
It's exactly the same procedure as the one on the beginning on the thread. Also be sure that the zip is in the internal memory of the device. (Not the external SD card, it won't be recognized otherwise)
Still not working
zaclimon said:
It's exactly the same procedure as the one on the beginning on the thread. Also be sure that the zip is in the internal memory of the device. (Not the external SD card, it won't be recognized otherwise)
Click to expand...
Click to collapse
So I booted into recovery, found the zip of the internal drive, and told it to install, but it cancels after a couple seconds saying that there is no space left on device, even though I factory reset it to ensure all the data was wiped.
have a stock Samsung Player 5.0 want to install Cyanogenmod11
new to an old thread, so much conflicting information, do i need to install cyanogenmod 9.0 first?
msigalov said:
So I booted into recovery, found the zip of the internal drive, and told it to install, but it cancels after a couple seconds saying that there is no space left on device, even though I factory reset it to ensure all the data was wiped.
Click to expand...
Click to collapse
Sorry for not having replying after so much time, I didn't get a notification and I don't visit the Q&A forum often so I couldn't see your reply. Do you still have this issue while installing CM11?
section128drunk said:
new to an old thread, so much conflicting information, do i need to install cyanogenmod 9.0 first?
Click to expand...
Click to collapse
As per the instruction on the CM11 thread:
Installation Instructions:
1. Reboot to recovery and make backup.
2. Do a full wipe.
3. Flash rom. You will see an error pop up. This is perfectly normal. Flash the rom again
4. Flash Gapps.
5. Flash US kernel if necessary
6. Have fun!
Click to expand...
Click to collapse
You don't need to install CM9 prior to install CM11. That said, at this time it is more recommended to install Carbon because it is updated and have more features than CM11. (like DT2W)
Reboots itself to recovery every once in a while
Great work on the new KitKat ROM. I have CM11 version 20141112 on my YP-G1 but I have one blaring issue.
I upgraded the ROM from 10.2 from the CyanogenMod Updates menu item in "About Phone", which booted it to recovery and I reflashed it twice again from there, wiping cache and data along the way. Afterwards, I flashed Gapps. Now it is installed and everything works and looks fine. However, now every few hours, the gadget would reboot itself into recovery with no error or anything. When I choose reboot from the recovery menu, the gadget would reboot to recovery again! I have to shut down, pull battery, then turn it on again so it would boot normally. So at least once a day I would be doing battery pulls on this thing just so it can boot normally.
Not sure if it's a common issue or is it because of my install method, maybe I forgot something?
Sad to hear that development might be discontinuing for this device. Seeing as I mainly use my smart devices for checking email, the only reason I stopped using it is because CM11 for some reason started locking up and draining the battery on a regular basis (although having it looked up to USB debugging and doing a logcat seems to keep it from ever locking up). Attached are two screen shots of the battery page taken while charging after two of those lockups in a single day (one mid day so I was able to catch it and reboot before the battery completely drained, the other overnight).
Any ideas what might be causing that? I just did a factory reset while flashing the new unofficial rom in recovery and flashed the minimal google apps so there's not much on there besides Google Chrome. The play services wake lock was fixed shortly before the first lock up by updating the Google Play Services.
Edit: After talking with zaclimon it seems like this is caused by something getting stuck in the system (presumably a bug with Google Play Services). Reverting back to stock, cleaning off the sdcard, and reinstalling CM seems to have solved the problem.