Related
(I'm new here, and I did search the forums and didn't find anything helpful.)
I've followed the instructions for installing speedmod kernel here:
http://forum.xda-developers.com/showthread.php?t=893880
I installed the samsung usb drives, Odin was able to see the phone, and..yeah, did everything it said.
Installation takes less than five seconds, my phone reboots, then sits on the screen that says "Galaxy S SGH-I897" and never gets past that.
I know speedmod was installed for the most part, because when I go into recovery mode I now see options for both clockwork and speedmod. I also tried using a recovery image to get back to where I was before, but I get this error:
E:Can't mount /dev/block/st19 to /system with parameters auto llw.check=no
(File exists)
Can't mount /system/!
Any ideas?
I tried flashing many different versions of the speedmod kernel, but all of them result in the same problem.
Thanks.
EDIT: changed "motorola" to "samsung"
Motorola usb drivers?
What rom were you running?
Why odin flash and not cmw?
Sent from my I897 using XDA Premium App
Motorola usb drivers?
Click to expand...
Click to collapse
Oh whoops, I meant "Samsung USB drivers"
Look under this:
1) What USB Drivers should I get for my computer to recognize my Captivate?
Click to expand...
Click to collapse
in
http://forum.xda-developers.com/showthread.php?t=858765
I originally used Odin without the drivers, but when I read closer, I read that I needed a Samsung USB driver. So installed that and got no different behavior from Odin or the installation of the kernel.
What rom were you running?
Click to expand...
Click to collapse
CyanogenMod. I don't remember which version, but definitely CM7 from last week.
Why odin flash and not cmw?
Click to expand...
Click to collapse
I am able to boot into recovery mode that ClockworkMod originally made. I think I mentioned in my first post that I see that SpeedMod has made an extra selection item in it, but recovery mode cannot recover anything.
In addition, I have tried wiping all the cache, but that also didn't effect anything.
I also have no idea how much battery life I have left, and how I can charge my phone without it (potentially) burning out the screen.
Thanks for the help.
That kernel will never work with cm7. Several issues but most of all it can not handle the system partition. you should be able to flash the rom again if you can get into recovery, or flash stock start over
Sent from my I897 using XDA Premium App
Alright. I'm able to get into recovery, which I assume means I can load up another CyanogenMod onto the SD card and hopefully be able to install it (the "cannot mount /system/" kinda worries me about that part). If I have to wipe everything and revert back to stock, that is perfectly fine...I have another phone that I can use in the meantime.
Thanks a lot for the help.
I should ask this now, which roms do support speedmod? Or should I look for another kernel (again, I'm pretty knew, I only know of these things from some people I know, but clearly there are a lot of options).
Cm7 kernels
Glitch
platypus
Kernel de jour
Speed mode is froyo
Sent from my I897 using XDA Premium App
Ootawata said:
I should ask this now, which roms do support speedmod?
Click to expand...
Click to collapse
Any Froyo ROM if you want a GB rom check out the I9000 roms. (combine those with the talon kernal)
The reason speedmod wont work it that CM7 runs off of yaffs2 and speedmod runs off of ext4/rfs and, well, you should see the problem with that
And to fix it you will have to use either the JF6 or the haikaidos flash back to stock package.
So you can repartition.
Good afternoon,
I'm sorry i'm creating a new thread about an old subject, but i just can't get my X8 to work with custom kernel+rom. I've searched the forum for the same issue but none of the solutions described worked. Until this moment i had to use PCC to flash my smartphone back to normal about 10 times and it's starting to get very annoying. I've followed the devs instructions on all procedures thoroughly, rooting, bootlader unlock, flashing kernel and installing ROM, and it always gets stuck on the kernel logo wether is it before or after flashing the rom (unless i press the back button). To this moment, i've tried nAa-14 and alfs v09 kernel, GingerDX and Zaraki roms, followed guides step by step. I'm a newbie in the smartphones area but not when it comes to computers. Throughout my 'voyage' i had a number of bumps i had to overcome, like having the installation aborted (bad) error when trying to install a rom, which i solved by downloading the zip directly to the SDcard like described here in the forums. GGdrivers are installed, and so are the SE USB drivers, phone is recognized by PCC with no problems.
I honestly have no idea what might be wrong, and as i said, i've done a search before creating a new thread but nothing helped, or maybe i'm just missing a tiny detail. I would really like the help since this is my first smartphone and i would like to play with my new toy!
Thanks and sorry for any inconvenience.
EDIT: I forgot something. In the kernel installation guide is requested that after flashing it, to check in the phone settings if everything is ok. I can't even boot the phone after flashing the kernel (gets stuck on kernel logo) which means my problem is related to something previous to it? Maybe bootlock? I'm pretty sure i'm doing what's required.
Appreciate the fast answer.
I get stuck on the logo wether is it before or after flashing the rom. The only way i don't get stuck is to press the back button to boot into cwm.
Yes i've tried to wipe after and before, and it didn't work. And these were the only roms and kernels i've tried.
There's no problem with hardbricking my device by the way, 11w03.
I'll have to get out for a while, but i will come back later to check all the answers, this is a priority for me at the moment
emaz1ng said:
Appreciate the fast answer.
I get stuck on the logo wether is it before or after flashing the rom. The only way i don't get stuck is to press the back button to boot into cwm.
Yes i've tried to wipe after and before, and it didn't work. And these were the only roms and kernels i've tried.
There's no problem with hardbricking my device by the way, 11w03.
I'll have to get out for a while, but i will come back later to check all the answers, this is a priority for me at the moment
Click to expand...
Click to collapse
Don't full wipe two times,either before or after,you can see this at the rom thread.
One basic detail that many forget is that you must have baseband that lasts to 15,so it would be like this xxx015
Sent from my X8 using xda premium
I didnt full wipe when trying gingerdx, as you said its not requested, only wiped with zaraki. I can confirm my baseband is xxxx015.
Sent from my E15i using xda app-developers app
emaz1ng said:
I didnt full wipe when trying gingerdx, as you said its not requested, only wiped with zaraki. I can confirm my baseband is xxxx015.
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
You have to full wipe,don't full wipe two times,gingerdx needs full wipe before installing the rom....
Sent from my X8 using xda premium
I tried again using the correct wiping method for gingerdx and it still freezes on kernel logo. the weird thing is that it freezes the first time it boots after flashing the kernel, meaning it has nothing to do with the rom, right? and maybe even not related to the kernel itself. i'm completely clueless about this, i wish i had a friend who could do it for me, because i can't detect anything done wrong.
What version of cwm are you using?
Sent from my X8 using xda premium
i'm not quite sure what's the version of cwm since it installs itself along with nAa-14 kernel, but i think it was v5.0.2.8
IAmNice said:
I think its the cwm that comes with the kernel.
For the OP. No idea what to do. You have a weird problem
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
please don't destroy my hopes of having a working custom rom on my phone jokes aside, i get your point, but doesn't it seem not logical that i'm the only one who can't get it to work? it's weird enough i can't boot my phone after flashing the kernel....
i could post a video, sure, but it's pretty straightforward. after i flash the kernel, unplug the phone from PC and boot it up, IF i don't boot into cwm, it will freeze on the kernel logo, making it impossible to even check the phone settings as requested in gingerdx thread. AFTER i install the rom and reboot the phone, it will still show the kernel logo and freeze again (if i understand correctly this is not supposed to happen, what's supposed to show on the screen after the rom is installed are the normal SE logos.)
So, summing up. Flash kernel, turn phone on, freezes on kernel logo if i don't use back button to go into cwm. If i enter cwm, install rom from sdcard, reboot, it shows the kernel logo and freezes if i don't use back button again.
Don't know if it helps but the only way to turn the phone off when it freezes is removing the battery. Sometimes after placing the battery again it will automatically turn on.
Dunno what's wrong,why don't you try with stock kernel and gdx,or why don't you try different rom(yea neither gdx nor gzr)
Sent from my X8 using xda premium
you mean formatting partitions after flashing the kernel or before? i assume there's an option for it under cwm?
stamatis16 said:
Dunno what's wrong,why don't you try with stock kernel and gdx,or why don't you try different rom(yea neither gdx nor gzr)
Sent from my X8 using xda premium
Click to expand...
Click to collapse
sure i can try other roms, but the fact that it freezes before installing the rom seems to point towards another problem?
the phone was bought in 2nd hand by the way, maybe there's something that could have happen before it got to me?
You have to format the partitions after flashing the kernel. In CWM recovery, go to 'mounts and storage' and format all the partitions except /sdcard.
feherneoh said:
Try to format all of the partitions (yes, ALL of them), then install ROM again.
After installation turn off the phone, take out the card, then turn phone on.
I hope it will work.
Click to expand...
Click to collapse
Lajbymester said:
You have to format the partitions after flashing the kernel. In CWM recovery, go to 'mounts and storage' and format all the partitions except /sdcard.
Click to expand...
Click to collapse
Just did it and the same thing happened. Flashed nAa-14, booted into cwm, full wipe, full cache wipe, wiped all the partitions but sdcard, installed rom, rebooted and it froze on the logo. Tried again with removing the sdcard and turning the phone on, froze on logo. Flashing it back to stock using PCC atm
By the way, it didn't let me format sd/ext.
Have you tryed with older version of naa? Naa 14 is buggy, naa 11 is the best
Sent from my p970 using xda premium
emaz1ng said:
Just did it and the same thing happened. Flashed nAa-14, booted into cwm, full wipe, full cache wipe, wiped all the partitions but sdcard, installed rom, rebooted and it froze on the logo. Tried again with removing the sdcard and turning the phone on, froze on logo. Flashing it back to stock using PCC atm
By the way, it didn't let me format sd/ext.
Click to expand...
Click to collapse
Try some other roms like minicm7. Do it in this order
Flash the kernel
Boot to cwm
Format system,data,cache
Fullwipe/Factory reset
Install Rom
Reboot
....wait .....
I do this every time i install a new rom..
Make sure The rom you have downloaded belongs to x8..
ElmirBuljubasic said:
Have you tryed with older version of naa? Naa 14 is buggy, naa 11 is the best
Sent from my p970 using xda premium
Click to expand...
Click to collapse
I will do that right away. I will also download a few others roms (and respective kernels) and try them all out. Only one thing, I was going to download MiniCM10 and i saw this in its post: "MiniCM10 is an unofficial port of CyanogenMod 10 for the SEMC msm7x27 devices." What does it mean 'for the SEMC msm7x27 devices'? Is it related to bootload unlock? Because i get Setool2 Certificate instead of SEMC. Does this make my problem a little easier?
EDIT: Ok, i've just tried ICZaraki+nAa-04-ics, minicm10+nAa-jb, gingerdx/gingerzaraki+nAa 11, and guess what, none worked.... We have to start thinking this is not related with the kernel or rom maybe? Any suggestions? When i tried the nAa-11 kernel, when i booted up the phone a white led popped up instead of a green one. I'm not worried if this takes a whole month to fix, i'm up for any suggestions and ideas of any kind, just throw them at me.
emaz1ng said:
I will do that right away. I will also download a few others roms (and respective kernels) and try them all out. Only one thing, I was going to download MiniCM10 and i saw this in its post: "MiniCM10 is an unofficial port of CyanogenMod 10 for the SEMC msm7x27 devices." What does it mean 'for the SEMC msm7x27 devices'? Is it related to bootload unlock? Because i get Setool2 Certificate instead of SEMC. Does this make my problem a little easier?
EDIT: Ok, i've just tried ICZaraki+nAa-04-ics, minicm10+nAa-jb, gingerdx/gingerzaraki+nAa 11, and guess what, none worked.... We have to start thinking this is not related with the kernel or rom maybe? Any suggestions? When i tried the nAa-11 kernel, when i booted up the phone a white led popped up instead of a green one. I'm not worried if this takes a whole month to fix, i'm up for any suggestions and ideas of any kind, just throw them at me.
Click to expand...
Click to collapse
This happen with alfs too? Have you followed all istructions to unlock bootloader?
Ah please..provide logcat! Big devs like rohin,eet, etc maybe can help you with logcat
ElmirBuljubasic said:
This happen with alfs too? Have you followed all istructions to unlock bootloader?
Ah please..provide logcat! Big devs like rohin,eet, etc maybe can help you with logcat
Click to expand...
Click to collapse
Yep, happens with all the kernels i've used, nAa-11/14, nAa JB, ICS, etc....
Googled logcat, i understand its use, but how do you want me to use it?
Yes, bootload is unlocked, i have the "r". Or is there any chance that even with the "r" it's still locked? Anyway, i followed the guides with no problem.
emaz1ng said:
Yep, happens with all the kernels i've used, nAa-11/14, nAa JB, ICS, etc....
Googled logcat, i understand its use, but how do you want me to use it?
Yes, bootload is unlocked, i have the "r". Or is there any chance that even with the "r" it's still locked? Anyway, i followed the guides with no problem.
Click to expand...
Click to collapse
you can try to use my automated tool at my siggy. Just upload the logs at here and the devs will do their jobs
wcypierre said:
you can try to use my automated tool at my siggy. Just upload the logs at here and the devs will do their jobs
Click to expand...
Click to collapse
am i supposed to specify a device (device id?) or just log all and upload them here?
Hi I was using NIK's Project X v4.1 on INCS for quite some time, on which the wifi was working properly, than I changed the rom to Sabsa Prime v14.0 after which my wifi stopped working and showing me an error sign and not starting... so than i went to ViperVIVO_2.1.4 and there also the wifi shows the same error message. Thus to check I restored to my backup of NIK's Porject X 4.1 where my wifi started working, so I again went back to ViperVIVO_2.1.4 in which still the wifi error is showing. I read somewhere that this due to kernel issue, so I flashed Redux_0.3_ProjectX kernel and after that Kernel_Redux_0.8_ViperIncS_boot.img but still wifi is not working. please help... I am on Android Version 4.0.4, HTC Sense version 4.0, with kernel 3.01 16-g693e8e9 [email protected]#1 PREEMPT with baseband version 20.4802.30.0822U_3822.10.08.28_M. I have rooted the phone with HTC dev unlocked with S-on. Thanks in advance
andzy said:
Hi I was using NIK's Project X v4.1 on INCS for quite some time, on which the wifi was working properly, than I changed the rom to Sabsa Prime v14.0 after which my wifi stopped working and showing me an error sign and not starting... so than i went to ViperVIVO_2.1.4 and there also the wifi shows the same error message. Thus to check I restored to my backup of NIK's Porject X 4.1 where my wifi started working, so I again went back to ViperVIVO_2.1.4 in which still the wifi error is showing. I read somewhere that this due to kernel issue, so I flashed Redux_0.3_ProjectX kernel and after that Kernel_Redux_0.8_ViperIncS_boot.img but still wifi is not working. please help... I am on Android Version 4.0.4, HTC Sense version 4.0, with kernel 3.01 16-g693e8e9 [email protected]#1 PREEMPT with baseband version 20.4802.30.0822U_3822.10.08.28_M. I have rooted the phone with HTC dev unlocked with S-on. Thanks in advance
Click to expand...
Click to collapse
Because your phone is s-on you need to fastboot flash boot boot.img
When you flash a zip you are installing wifi drivers/files but the kernel cannot call upon them because it is not the right one for that kernel.
Reflash whatever rom you have, then take out the boot.img from the rom zip and flash it via fastboot (google fastboot flash boot boot.img and it should tell you)
Basically you are flashing everything but the kernel. HTC unlock doesn't let you flash the kernel in recovery. I know this because your kernel version should say something like 3.0.46-redux or something like that
Hey Mark, thanks for the quick reply, when I was on NIK Project X 4.1 my kernel was 3.0.16-g693e8e9 [email protected]#1 and now its 3.01 16-g693e8e9 [email protected]#1 PREEMPT. Can you please explain as what I should flash first than what and when to wipe the cache and dalvik cache???
andzy said:
Hey Mark, thanks for the quick reply, when I was on NIK Project X 4.1 my kernel was 3.0.16-g693e8e9 [email protected]#1 and now its 3.01 16-g693e8e9 [email protected]#1 PREEMPT. Can you please explain as what I should flash first than what and when to wipe the cache and dalvik cache???
Click to expand...
Click to collapse
That would be right.
1. go to recovery and flash the ROM of your choice
2. Wipe cache and dalvik cache
3. From recovery after you flash it, boot it to bootloader
4. Using fastboot, whilst in bootloader mode flash your boot.img (from the ROM you flashed). If you don't know how to do it, google it cause there is plenty of information about that
5. Reboot
Thanks once again Mark. I know how to flash the img file. For the past 10 minutes I am stuck at sending the recovery files on my computer as I was flashing the recovery img, thus going from CWM to 4ext... is this normal i.e. does flashing take such a long time, as I dont remember flashing taking such a long time...
andzy said:
Thanks once again Mark. I know how to flash the img file. For the past 10 minutes I am stuck at sending the recovery files on my computer as I was flashing the recovery img, thus going from CWM to 4ext... is this normal i.e. does flashing take such a long time, as I dont remember flashing taking such a long time...
Click to expand...
Click to collapse
Why are you sending recovery? You only need to flash boot.img from your computer. You flash the ROM from your phone in recovery
markj338 said:
Why are you sending recovery? You only need to flash boot.img from your computer. You flash the ROM from your phone in recovery
Click to expand...
Click to collapse
Once you manually flash using the computer it will send something to flash the boot.img.
Sent from my HTC Incredible S using xda premium
Reflash boot.img for the ROM plz...
Sent from my HTC Incredible S using xda premium
Thanks to all the people who helped me and also the moderators and this forum... got my problem solved... the problem was with the HTC drivers had to uninstall them and reinstalled them and lo i could flash my files and now my wifi is back working.... Great and thanks once again...
Thanks for the tip :good:
Helped me too.
andzy said:
Thanks to all the people who helped me and also the moderators and this forum... got my problem solved... the problem was with the HTC drivers had to uninstall them and reinstalled them and lo i could flash my files and now my wifi is back working.... Great and thanks once again...
Click to expand...
Click to collapse
I have exact problem
How did you uninstall and reinstalled drivers of HTC ?
Mitan, firstly i uninstalled the htc sync manager from the computer, than downloaded the htc drivers from the net and lo got everything working....
uprockin said:
Thanks for the tip :good:
Helped me too.
Click to expand...
Click to collapse
andzy said:
Mitan, firstly i uninstalled the htc sync manager from the computer, than downloaded the htc drivers from the net and lo got everything working....
Click to expand...
Click to collapse
I just upgraded again to 4.04 (viper ROM) and flashed boot.img but still wifi doesn't turn on? any suggestion ?
its a kernel problem... if i remember correctly there is a thread in the viper vivo section wherein someone has mentioned how to get the wifi working.. you just need flash the kernels... please check that thread and it wifi will work...
All the best!!
Wifi error
Many a time this error occurs because people don't format the system, due to Kernel issue.
Make sure you always format /system in advanced in recovery. (Especially when coming from a Sense Rom)
Also, S-on guys make sure you push the boot.img file manually everytime you flash a new rom.
This is definitely a kernel problem. I always format the system and have had this problem with some kernels, in particular the z13 kernel. Z14 is out now and it doesn't occur.
I have never done this before. I had one of my friends root and unlock my phone for me. I have a htc vivid. He installed the holics 1.3 version for me and he is in a different country now so I can ask him. My wifi wont work. he sent me a link for a kernel but it says that the installation is aborted. the name of the kernel is:
0816holics-kernel-for-son(pc).zip
but this wont work.
can someone please tell me what to do to start my wifi again?
Are you S- On or S- Off? If you're s- On you have to flash the boot img before flashing the rom. That will fix wifi. If I'm no mistaken you should have a boot img saved in your ad card folder.
You also have to do this via fastboot. Also when you flash the rom you must select the S-On option, if you did you'll find the boot img you must flash in your phones sd or internal storage.
chivor said:
I have never done this before. I had one of my friends root and unlock my phone for me. I have a htc vivid. He installed the holics 1.3 version for me and he is in a different country now so I can ask him. My wifi wont work. he sent me a link for a kernel but it says that the installation is aborted. the name of the kernel is:
0816holics-kernel-for-son(pc).zip
but this wont work.
can someone please tell me what to do to start my wifi again?
Click to expand...
Click to collapse
You have to unzip "0816holics-kernel-for-son(pc).zip" and the boot.img is inside
HTC VIVID 4.0.4 SENSE 4.1
Actually that won't work, his phone will boot, but he will still have problems with wifi cuz the rom generates the boot.img acoording to the selections made in the aroma installer so he has to flash the rom and then get the boot.img and flash the rom again. Try using WCX recovery its easier and it let's you flash the boot.img from recovery instead of doing it via fastboot.
Trying to root my Nexus 6 with Marshmallow
I installed the modified boot from Chainfire using fastboot, it succeeded, then restarted bootloader, then installed TWRP 2.8.7.1, it succeeded, then booted to TWRP and installed the 2.52 beta of SuperSU and restarted and the phone is saying the 'device is corrupted', gives me some crap URL (g.co/ABH) and doesn't start, is there any way to fix this?
Edit: sort of fixed by using Despair Kernel, however, isn't there a way to do this without installing a custom kernel?
wrsg said:
Trying to root my Nexus 6 with Marshmallow
I installed the modified boot from Chainfire using fastboot, it succeeded, then restarted bootloader, then installed TWRP 2.8.7.1, it succeeded, then booted to TWRP and installed the 2.52 beta of SuperSU and restarted and the phone is saying the 'device is corrupted', gives me some crap URL (g.co/ABH) and doesn't start, is there any way to fix this?
Edit: sort of fixed by using Despair Kernel, however, isn't there a way to do this without installing a custom kernel?
Click to expand...
Click to collapse
yea, you just ignore the message, press a button, and let it boot. it has NOTHING to do with root being broken. its a message that appears, using the stock kernel, if you have unlocked your bootloader. next time dont freak out, lol :silly:
Well if that had worked I would have not said I already tried doing that...
wrsg said:
Well if that had worked I would have not said I already tried doing that...
Click to expand...
Click to collapse
then you are the only one that it did not boot up afterwards.
simms22 said:
then you are the only one that it did not boot up afterwards.
Click to expand...
Click to collapse
It has happened to someone else. If you touch the system partition at all with the stock kernel you will get the warning. Only way is a modified kernel (or boot?). You can use a stock kernel that has a small mod to remove the message.
I switched to the vortex kernel mm beta and am very happy with it. No problems at all and way more responsive.
johnciaccio said:
It has happened to someone else. If you touch the system partition at all with the stock kernel you will get the warning. Only way is a modified kernel (or boot?). You can use a stock kernel that has a small mod to remove the message.
I switched to the vortex kernel mm beta and am very happy with it. No problems at all and way more responsive.
Click to expand...
Click to collapse
using despair/elementalx myself
johnciaccio said:
It has happened to someone else. If you touch the system partition at all with the stock kernel you will get the warning. Only way is a modified kernel (or boot?). You can use a stock kernel that has a small mod to remove the message.
I switched to the vortex kernel mm beta and am very happy with it. No problems at all and way more responsive.
Click to expand...
Click to collapse
We are talking about two different things: one is the red triangle, and the other is shutting down if rooted.
In this case pressing the power key while showing the triangle is what turns the phone off. It is so if somebody else tampered with your phone to stop it from booting and messing with your stuff.
On the other hand, stopping if rooted can be avoided if you have a custom kernel with all SELinux turned off, or using Chainfires boot.img that dabbles with the security settings so the kernel is satisfied and boots. You will have the red triangle, just let it boot.
And if the red triangle troubles you then by using a modified ramdisk, it can be switched off.