Develop Bugs

messed up with kernel, need help

hey guys so i stupidly installed franco.kernel 4.0.3 on my stock ROM 4.0.1.. and phone wont boot, I can only get to my CWM Recovery menu.
so what can i do, i want to put a custom ROM but I dont see how i can connect to my phone at this point... any way to mount it as USB storage, and upload custom ROM, and then install so it will work with this kernel
any advice?

UKROB86 said:
hey guys so i stupidly installed franco.kernel 4.0.3 on my stock ROM 4.0.1.. and phone wont boot, I can only get to my CWM Recovery menu.
so what can i do, i want to put a custom ROM but I dont see how i can connect to my phone at this point... any way to mount it as USB storage, and upload custom ROM, and then install so it will work with this kernel
any advice?
Click to expand...
Click to collapse
im pretty sure you can mount in CWM
go into mounts and storage and do usb mass storage ....i think, never had to use it so idk if it works. good luck!

you can mount to SD through recovery, in the "mounts and storage" section.
Did you not make a back up?
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
you can, but if you do not have the stock recovery, it might not work.
i have the unoffical touch-enable recovery and it wont mount to USB

kkl1993 said:
you can mount to SD through recovery, in the "mounts and storage" section.
Did you not make a back up?
Click to expand...
Click to collapse
no nandroid because it was just a kernel, didn't think ahead.. i dont seem to be able to mount in USB storage with CWM..

UKROB86 said:
no nandroid because it was just a kernel, didn't think ahead.. i dont seem to be able to mount in USB storage with CWM..
Click to expand...
Click to collapse
well you learned your mistake. always do a nandroid, before you flash something.
try flashing another kernel, or install a new ROM

kkl1993 said:
well you learned your mistake. always do a nandroid, before you flash something.
try flashing another kernel, or install a new ROM
Click to expand...
Click to collapse
problem is I cant connect to my phone in order to upload a ROM or Kernel to be flashed...

UKROB86 said:
problem is I cant connect to my phone in order to upload a ROM or Kernel to be flashed...
Click to expand...
Click to collapse
thats sucks. thats why i loved sd cards. stupid internal storage only
well i guess ur only option is to do a factory reset, if u cant get past the bootanimation.

You mean to say that you no ROMS at all on your SD card that u can flash just to overwrite the current kernal that is on there? You might have to do some reading on adb

ok guys I have uploaded a ROM to a directory i can install from CWM, so i'll do a wipe etc.. and install ROM?

UKROB86 said:
ok guys I have uploaded a ROM to a directory i can install from CWM, so i'll do a wipe etc.. and install ROM?
Click to expand...
Click to collapse
Yes,do a full wipe (data/factory, cache, and Dalvik) then flash ROM then flash Franco's kernel.

jdk82 said:
Yes,do a full wipe (data/factory, cache, and Dalvik) then flash ROM then flash Franco's kernel.
Click to expand...
Click to collapse
ok i did system wipe and then flashed the ROM, phone is back up and running. I thought the kernel would stay anyways? I need to reflash the kernel?

Yes, most ROMS come with a kernel, some stock some not.

jdk82 said:
Yes, most ROMS come with a kernel, some stock some not.
Click to expand...
Click to collapse
ok cool I'm going to throw on the franco.kernel with the Android Open Kang Project ROM. thanks for your help bro, thanks given.

Trying to install CM9 stable, stuck at boot logo.

My friend is currently running Arconium ICS on his Xperia, and now when I tried to install CM9 (Did full wipe > install CM > install gapps in CWM) it just gets stuck at the boot logo (SONY). After recovering the backup of Arconium in CWM it boots up fine again.
Since the boot logo didn't change, I'm thinking CM9 maybe didn't install a new kernel or something? Is there something I can do to make sure that CM9 fits as well as possible? If kernel switching is on the table I'd like to be able to do this from CWM.
Thank you!

bajsmumsaren said:
My friend is currently running Arconium ICS on his Xperia, and now when I tried to install CM9 (Did full wipe > install CM > install gapps in CWM) it just gets stuck at the boot logo (SONY). After recovering the backup of Arconium in CWM it boots up fine again.
Since the boot logo didn't change, I'm thinking CM9 maybe didn't install a new kernel or something? Is there something I can do to make sure that CM9 fits as well as possible? If kernel switching is on the table I'd like to be able to do this from CWM.
Thank you!
Click to expand...
Click to collapse
you must install the kernel "boot.img" through flashtool
is inside the zip file

krattos said:
you must install the kernel "boot.img" through flashtool
is inside the zip file
Click to expand...
Click to collapse
Do I have to do this via flashtool? No way to do it from inside CWM? Please excuse if this is a stupid question, I'm not still a 100 % sure what boot.img, recovery, kernel and all these are and how they fit together.

bajsmumsaren said:
Do I have to do this via flashtool? No way to do it from inside CWM? Please excuse if this is a stupid question, I'm not still a 100 % sure what boot.img, recovery, kernel and all these are and how they fit together.
Click to expand...
Click to collapse
Yes, through the FlashTool is safer.
For all your doubts see this link, is a little extended but very complete.
http://forum.xda-developers.com/showthread.php?t=1133650

bajsmumsaren said:
Do I have to do this via flashtool? No way to do it from inside CWM? Please excuse if this is a stupid question, I'm not still a 100 % sure what boot.img, recovery, kernel and all these are and how they fit together.
Click to expand...
Click to collapse
Boot.img is the kernel in a compiled file, which needs to be installed via fastboot. Flashtool includes fastboot aswell, so you can install the kernel(boot.img) using it.
Recovery is a certain 'program' used to install custom stuff, make full backups(Nandroid backup) and restore them, wipe/format partitions and some other stuff. Recovery can be included already inside the kernel, but there is also possibility to install it on /system partition for those who can't unlock bootloader and/or install custom kernel.
My recommendation - Don't do it if you don't understand anything. You should go and learn about the whole Android first, get yourself familiar with how to recover the phone(install stock firmware etc), what are the terms that we use, what is what etc, then come back. Else...you might get yourself a nice (temporary) brick and then you have another problem, how to get back the phone.

bajsmumsaren said:
My friend is currently running Arconium ICS on his Xperia, and now when I tried to install CM9 (Did full wipe > install CM > install gapps in CWM) it just gets stuck at the boot logo (SONY). After recovering the backup of Arconium in CWM it boots up fine again.
Since the boot logo didn't change, I'm thinking CM9 maybe didn't install a new kernel or something? Is there something I can do to make sure that CM9 fits as well as possible? If kernel switching is on the table I'd like to be able to do this from CWM.
Thank you!
Click to expand...
Click to collapse
Obviously you didnt flash the kernel..and before doing that u need to make sure if ur bootloader is unlocked..if it is unlocked then only you can proceed with flashing the kernel and then installing the ROM.

Same Here!!
but Nothin seems to b workin for me!! Ive Done everything as per da instructions!
I flashed the boot.img file which i unzipped from the cm9 nozomi.zip file!!
I formatted the data, the cache and the dalvik cache and then installed the cm9 and gapps files as well and then when i reboot my device from the recovery menu it just gets stuck at the boot screen of free xperia!!
(
pleasehelp!!

Assistere said:
Same Here!!
but Nothin seems to b workin for me!! Ive Done everything as per da instructions!
I flashed the boot.img file which i unzipped from the cm9 nozomi.zip file!!
I formatted the data, the cache and the dalvik cache and then installed the cm9 and gapps files as well and then when i reboot my device from the recovery menu it just gets stuck at the boot screen of free xperia!!
(
pleasehelp!!
Click to expand...
Click to collapse
Dude, nozomi is only for Xperia S device. You installed the wrong ROM!
Go check the supported devices list to find your device's codename.

Someguyfromhell said:
Dude, nozomi is only for Xperia S device. You installed the wrong ROM!
Go check the supported devices list to find your device's codename.
Click to expand...
Click to collapse
Dude mine is Xperia s is only!!
sorry i frgt to mention bout my phone earlier!!!

Assistere said:
Dude mine is Xperia s is only!!
sorry i frgt to mention bout my phone earlier!!!
Click to expand...
Click to collapse
Then you are at wrong forum.

[Q] Kernel related question

I have never flashed any kernels, just custom roms. From what I have read it goes down the same way, just flash the zip from SD in recovery and wipe cache. Correct?
Also, if I want to go back to stock kernel can I flash back to a JOP40C ( this one http://forum.xda-developers.com/showthread.php?t=1992483 ) even though my build is JOP40D ?

Robert00001 said:
I have never flashed any kernels, just custom roms. From what I have read it goes down the same way, just flash the zip from SD in recovery and wipe cache. Correct?
Also, if I want to go back to stock kernel can I flash back to a JOP40C ( this one http://forum.xda-developers.com/showthread.php?t=1992483 ) even though my build is JOP40D ?
Click to expand...
Click to collapse
just flash it in your recovery(if its a flashable zip). dont wipe a single thing, dalvik and cache have nothing to do with kernels. worst case scenario, it doesnt boot. then just reflash your rom in your recovery to fix it.

simms22 said:
just flash it in your recovery(if its a flashable zip). dont wipe a single thing, dalvik and cache have nothing to do with kernels. worst case scenario, it doesnt boot. then just reflash your rom in your recovery to fix it.
Click to expand...
Click to collapse
Ok thanks. Yes its a flashable zip, im going for the franco kernel.

Robert00001 said:
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Click to expand...
Click to collapse
franco is a good kernel. but most his kernels are in a img form, need fastboot for that. if its a zip, then flash it in your recovery, dont wipe a thing.

simms22 said:
franco is a good kernel. but most his kernels are in a img form, need fastboot for that. if its a zip, then flash it in your recovery, dont wipe a thing.
Click to expand...
Click to collapse
Yes I am sure this is a flashable zip. I found the img files and the zip files on the franco thread.
What about going back to stock? I just want to know if something goes wrong. Does flashing my rom get me the stock kernel back?

Robert00001 said:
Yes I am sure this is a flashable zip. I found the img files and the zip files on the franco thread.
What about going back to stock? I just want to know if something goes wrong. Does flashing my rom get me the stock kernel back?
Click to expand...
Click to collapse
It gets you whatever kernel was originally in the ROM.

063_XOBX said:
It gets you whatever kernel was originally in the ROM.
Click to expand...
Click to collapse
Okay thanks for the replies.

Robert00001 said:
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Click to expand...
Click to collapse
Even the .IMG files are easy enough to handle, OK so perhaps it might cost you a little money but within the Franco app (I don't know about others as not tried them) but you can simply just choose to restore a .IMG kernel file be it stock (which I have a copy of if you wanted it?) So you can swap and change as you wanted and the plus side of flashing this way is that you avoid the long reboot time dues to catch building again due to ram disk changes. I really think this is the best way of flashing kernels and certainly the easiest way if you wanted to carry on back to the OTA update route from Google.
For instance, I'm running stock takju rom 4.2.1 rom with Franco kernel and I have the stock boot loader and baseband and recovery and to install an OTA I just need to delete just one file and restore back to stock kernel that OTA update will install without troubles
Sent from my Galaxy Nexus

ROM new Lineage 14.1 Unofficial WhenICanlies d2tmo 4-10-18

I have been working on the sister models also. I saw no one was building these anymore so here it is I hope it can be enjoyed by all. Spread the word. provide feedback so other fans of this ROM may obtain it and work out any bugs if there are any. I will update once or twice a week depending on time and demand. I'm compiling for three different variants. Hit the thanks button and Enjoy. Dirty flash the updates not the initial flash of this rom but the updates to it. Initial install = Factory reset, wipe data and cache, install rom zip, install gapps zip, install su zip, reboot system. As of 9-3-18 i will be switching to Ubuntu 18.04 Bionic Beaver, that being said i do not know if i will have to change anything or do anything different to keep pushing these updates out but i will most definitely try to keep them coming.
4-10-18
https://www.androidfilehost.com/?fid=890129502657597436
4-13-18
https://www.androidfilehost.com/?fid=818070582850507491
4-17-18
https://www.androidfilehost.com/?fid=818070582850508419
4-24-18
https://www.androidfilehost.com/?fid=673956719939836620 If it's an update then dirty flash it if you already had SuperSU installed you will need to reflash the SuperSU zip if you are installing for the first time you just need to install the SuperSU app
5-4-18
https://www.androidfilehost.com/?fid=818222786056028546
Root is not baked in. Flash and root your preferable way.
5-20-18
https://www.androidfilehost.com/?fid=674106145207488021
5-31-18
https://www.androidfilehost.com/?fid=674106145207490572
7-28-18
https://www.androidfilehost.com/?fid=5862345805528060741
9-3-18
https://www.androidfilehost.com/?fid=1322778262903996744
10-07-18
https://www.androidfilehost.com/?fid=1322778262904022369
12-7-18
https://www.androidfilehost.com/?fid=11410963190603868411
12-16-18
https://www.androidfilehost.com/?fid=11410963190603876081
2-25-19
https://www.androidfilehost.com/?fid=1395089523397901582
3-24-19
https://www.androidfilehost.com/?fid=1395089523397924752
5-6-19
http://download1589.mediafire.com/7...q5/lineage-14.1-20190507-UNOFFICIAL-d2tmo.zip
10-13-19
https://www.androidfilehost.com/?fid=1899786940962607809
i recommend clean flash as i built with different computer
setprop persist.lineage.nofool true in terminal emulator with root privs (type su first grant permission then setprop persist.lineage.nofool true) gets rid of persistant notification
Bluetooth dialtone when playing music fix
Settings > Battery > tap in 3-dot menu at top right tap on Battery optimisation. To show all apps and services here, select the ‘All apps’ options under the dropdown. Tap on both of the Bluetooth services and change them to Don't optimise.

thanks bro... but is it rooted rom or use any method to root it ?

hasan.sy said:
thanks bro... but is it rooted rom or use any method to root it ?
Click to expand...
Click to collapse
I use SuperSU zip

the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it

hasan.sy said:
the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it
Click to expand...
Click to collapse
I appreciate the feedback and no worries mate I'm still trying to get the no sim bug worked out in the att variant no luck so far sprint variant is doing good also

Update posted 4-17-18

It won't boot up for me. I installed the ROM after wiping my entire system through TWRP, flashed Gapps, and installed SuperSU provided by TWRP. When it boots up it says system isn't responding.

Sammay_Boiii said:
It won't boot up for me. I installed the ROM after wiping my entire system through TWRP, flashed Gapps, and installed SuperSU provided by TWRP. When it boots up it says system isn't responding.
Click to expand...
Click to collapse
Wipe system, cache, and dalvik install rom zip install nougat Gapps and SuperSU all at the same time meaning do not reboot until you have flashed all three if it didn't work the first time try it again just make sure you wipe system, cache and dalvik and install the Gapps at the same time it sounds like it's booting up but conflicting with other elements otherwise it would be bootloop and not system isn't responding

Joker1716 said:
Wipe system, cache, and dalvik install rom zip install nougat Gapps and SuperSU all at the same time meaning do not reboot until you have flashed all three if it didn't work the first time try it again just make sure you wipe system, cache and dalvik and install the Gapps at the same time it sounds like it's booting up but conflicting with other elements otherwise it would be bootloop and not system isn't responding
Click to expand...
Click to collapse
Thank you for your rapid response! I will try that as soon as I get to my house and I'll let you know what happens

After doing what you said, it still says "process system isn't responding" I will try a few more times. Also, I'm flashing off nothing. There is no OS, no personal data, just TWRP. Does this have to be flashed on CM12 or something?

Sammay_Boiii said:
After doing what you said, it still says "process system isn't responding" I will try a few more times. Also, I'm flashing off nothing. There is no OS, no personal data, just TWRP. Does this have to be flashed on CM12 or something?
Click to expand...
Click to collapse
You need to Odin flash the latest stock firmware then root then flash recovery then flash the rom
This should help
https://forum.xda-developers.com/showthread.php?t=1949687

Joker1716 said:
You need to Odin flash the latest stock firmware then root then flash recovery then flash the rom
Click to expand...
Click to collapse
I will do that. Your rom needs to be flashed over stock rom?

Sammay_Boiii said:
I will do that. Your rom needs to be flashed over stock rom?
Click to expand...
Click to collapse
No this is lineage os 14.1 it's not mine I just build it because they have stopped doing it officially for this variant of the s3 but there's more to a phone than just the system and you have nothing but a recovery? There's bootloader modem, Efs etc. You wouldn't be able to even flash CM12. in TWRP are you going into advanced wipe or are you just swiping the slider?

Joker1716 said:
No this is lineage os 14.1 it's not mine I just build it because they have stopped doing it officially for this variant of the s3 but there's more to a phone than just the system and you have nothing but a recovery? There's bootloader modem, Efs etc. You wouldn't be able to even flash CM12. in TWRP are you going into advanced wipe or are you just swiping the slider?
Click to expand...
Click to collapse
What you said makes a lot of sense actually. Im used to just flashing back ups of other roms that I forgot how to flash fresh ones. I'm not used to this haha but I got it now. Stock rom 4.3 has been flashed via odin and the root method is currently on my screen.

hasan.sy said:
the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it
Click to expand...
Click to collapse
What was your system status before flashing the rom? What software? I'm having trouble flashing it on my S3

Sammay_Boiii said:
What was your system status before flashing the rom? What software? I'm having trouble flashing it on my S3
Click to expand...
Click to collapse
t999uvuenc2 firmware and bootloader 4.3 using twrp recovery 3.2.1-0..... you must update to latest official firmware t999uvuenc2 to flash any rom 5.1.1 lollipop and higher

hasan.sy said:
t999uvuenc2 firmware and bootloader 4.3 using twrp recovery 3.2.1-0..... you must update to latest official firmware t999uvuenc2 to flash any rom 5.1.1 lollipop and higher
Click to expand...
Click to collapse
Thank you. Ive been flashing this rom repeatedly and always received a "Process system not responding" then it falls into a boot loop

Update posted

Joker1716 said:
Update posted
Click to expand...
Click to collapse
Does it need wipe data and cash before flash or we can do dirty flash without any thing?(update from 13-4-2018 to this rooted update)

hasan.sy said:
Does it need wipe data and cash before flash or we can do dirty flash without any thing?(update from 13-4-2018 to this rooted update)
Click to expand...
Click to collapse
If it's an update then dirty flash it if you already had SuperSU installed you will need to reflash the SuperSU zip if you are installing for the first time you just need to install the SuperSU app

Help please, I broke my A5 2017. (A520F)

So, I was trying to add navbar buttons by editing the build.prop file, but it didn't work, now my phone won't boot and i'm phoneless, So I need someone, ANYONE to make/create/construct a CWM flashable zip that resets the build.prop file to an original one, I need help as fast as someone can possibly send. You will have my forever gratitude and a new discord buddy.

If no one has a better solution I would recommend you flash the ROM again so the system can be restored...
Sry I don't have anything else to suggest :/

nubry said:
If no one has a better solution I would recommend you flash the ROM again so the system can be restored...
Sry I don't have anything else to suggest :/
reflash it through odin by stock firmware mate
Click to expand...
Click to collapse

flash current rom again with TWRP. you don't need to wipe data,cache,dalvik or anything. if its not working flash stock rom using Odin.

raZorXz said:
flash current rom again with TWRP. you don't need to wipe data,cache,dalvik or anything. if its not working flash stock rom using Odin.
Click to expand...
Click to collapse
Is there really no way else, cause i have limited data and the stock rom is quite a big download :/

Airoblast said:
Is there really no way else, cause i have limited data and the stock rom is quite a big download :/
Click to expand...
Click to collapse
request build.prop flashable zip from another user or rom Dev that use the same rom you're currently using.