Hi,
first sorry for my bas english i'm french.
I try to build a custom kernel(foreA510) but i have a question that make me block :
-if i made a "bad" kernel (Cpu bad voltages settings for exemple or anything else) which that not allowed to start, could i always access to the recovery mod of CWM ?(to flash stock rom)
In other word the kernel partition lunch after the boot settings but is there voltages setings in the boots that allow me to flash a stock kernel ?
Thanks for answer
thomas
i find something :
to test kernel :
reboot in bootloader
and type : "fastboot boot zImage" that normaly is used to test a kernel but it doesn't reboot why ?
thanks
Related
Hello,
Sorry if this has been posted already , but i couldnt find anything similar.
When i flash something, from cwm, it does not make any changes.
When i flash a other rom, the old rom boots,
Kernel, the old kernel remains
I had the new Cwm 5.5.0.4? With the reboot problem.
So i installed a rom, which i found in dev section wthat included a older cwm 3.3.0.4 or something.
The reboot problem still remains, so i can only start with holding volume down and do a cold boot.
So if i try to flash the new fixed cwm, trough cwm or rom manager, still the old cwm shows up.
(Rom manager actually sais the new version is installed :S )
Also i tried alot of wipes, clear cache and dalvik before flashing, but this makes no difference.
When flashing i dont get any errors, just normal, like everything goes well.
Can someone help me out?
Thanks
Go here
http://forum.xda-developers.com/showthread.php?p=23256536
Yes i readed that thread, but has this anything to do with my rom and kernel not changing after flashing?
Firstly : is it even showing the flashing being done in the recovery? Should show loading bar and tell you what its doing.
Second : baseballfan is showing that thread because there's probably issue with your recovery.
Also, maybe you can just use gnufabios app in app thread " recovery installer ". It flashes roaches working cwm recovery for you, real easy. Download apk, open and hit install
Sent from my SGH-T959 using xda premium
Yeah you have a bad recovery, after flashing a "good" recovery you still need to
use terminal to remove the "bad" recovery or you will still be at square one.
Yes, the flashing of a rom or anything else goes like usual.
I will try to fix the cwm and see if it helps the problems with my tf stuck on a rom and kernel.
Hello guys,
I made some progress,
If i flash a kernel , it does successfully flash it.
When i go to recovery, it now sais : ClockworkMod Recovery v5.5.0.4
So thats better then before,
But now i have the following problem.
It still boots to the recovery if i dont hold vol. down.
I readed the instruction from the thread : http://forum.xda-developers.com/show...php?p=23256536
I flash the zip : cwm_recovery-5504_roach-tf101-r2.zip
Then when i try to ADB : adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
it gives me the error : Write error : No space left on device
I searched all threads on XDA, and i found that this error is normal because there is no space defined.
But after a reboot, it still doesnt boot the R2 recovery.
Just the old one
Anyone that has a solution?
Hi,
I wanna reflash sd-ext content from one sd card to another one.As CWM 5.0.2.8 is bad and does not restore sd-ext because it wrote some error message like sd-ext is not mounted even partitioned correctly, I choosed at CWM 5.0.2.8 RESTORE instead of normal ADVANCED RESTORE.As I previously backed up SD-EXT only, I had no back up of BOOT of course.CWM is so stupid it erased BOOT !!!! and then wrote error while flashing boot image
So at this moment I am at CWM , mounted and accessed USB by PC ( cant choose restart to download mode)
I would like to kindly ask someone to back up BOOT by this CWM version at G3MOD 2.5 kernel and upload it here.so I will be able flash BOOT only and normally work
I am sure after restart , phone will be hard bricked.
Update : 23 views and NOONE is able go to CWM , make FULL backup and post there or anywhere required files ? , guys , common ! help me please
try this
radek.god said:
Hi,
I wanna reflash sd-ext content from one sd card to another one.As CWM 5.0.2.8 is bad and does not restore sd-ext because it wrote some error message like sd-ext is not mounted even partitioned correctly, I choosed at CWM 5.0.2.8 RESTORE instead of normal ADVANCED RESTORE.As I previously backed up SD-EXT only, I had no back up of BOOT of course.CWM is so stupid it erased BOOT !!!! and then wrote error while flashing boot image
So at this moment I am at CWM , mounted and accessed USB by PC ( cant choose restart to download mode)
I would like to kindly ask someone to back up BOOT by this CWM version at G3MOD 2.5 kernel and upload it here.so I will be able flash BOOT only and normally work
I am sure after restart , phone will be hard bricked.
Update : 23 views and NOONE is able go to CWM , make FULL backup and post there or anywhere required files ? , guys , common ! help me please
Click to expand...
Click to collapse
Which ROM are you using and what version of it....nd did I try flashing the ROM again through Odin.....that usually works as the tar file has a boot img u can later use advanced recovery to restore I Ur ext-sd..
Hit thanks button if this helps
droidvoodoo said:
Which ROM are you using and what version of it....nd did I try flashing the ROM again through Odin.....that usually works as the tar file has a boot img u can later use advanced recovery to restore I Ur ext-sd..
Hit thanks button if this helps
Click to expand...
Click to collapse
Hi,
I am on this ROM :http://forum.xda-developers.com/showthread.php?t=1558936 , 4.0.4 , MPICS 3.0 updated to MPICS 4.0 CWM version
I need file "BOOT.IMG" backed up by CWM 5.0.2.8
My goal is restart safely phone and be able go to download mode, I dont care if I have to reflash ROM again.
But this is what I am affraid - At CWM I will click restart and never ever see anythink on my phone after that , until service repair ...
Update : Solved by :
"Marcellusbe provided me with zip file with some ZImage + info about replace included ZImage by required one, so by this and specially by
Originally Posted by hillbeast
Your phone is quite safe. CWM refers to the kernel as boot. Its not the bootloader (PBL or SBL) as those are write protected by Samsungs drivers. Just reflash G3MOD with ODIN or something. I suggest using an old version of G3MOD if the latest one is giving issues with CWM.
So I was not affraid to did it and had no problem go to download mode.I get some FC, but I can reflash ROM, so no problem
many many many thanks those 2 devs and another users PM me
Hi Guys,
I had CM 10 on my phone and I was able to use CWM successfully. But, then I flashed Pandroid 4+ (CM 11 based) Kitkat 4.4 ROm on my phone.
Now, I am not able to boot into recovery mode. As i try to enter into recovery mode, My phone gets stuck in the boot screen and does not boot up. After so many attempts of pressing power button, it starts. It's so painful.
I want to revert back to CM 10 stable rom, but I can't boot in to recovery mode.
I did some research and found a CWMFixed.zip as a solution. It contains a boot.img file. Please let me know how can i flash this file without entering into CWM.
Or if there is any other solution for this problem then please let me know.
It urgent.
@tysonraylee I hope you can help me in this as you had posted a similar query in other thread.
Thanks in advance.
My friend, If you would have only read the PA thread properly you would know that beta 5 has the bug where it breaks the recovery you would have avoided the problem altogether but anyways i would suggest that you flash an odin format (.tar) kernel using PC Odin which will get you a working recovery and from there it should be pretty easy, if you took a nandroid backup before you will be able to restore your previous rom and if you didnt you have to flash a different rom of your choice
flash this TW PC odin format (.tar) kernel by bauner https://www.androidfilehost.com/?fid=95784891001607164
make sure once you flash this to not let the phone boot into ROM, after flashing successful take off the battery and then insert back and boot into recovery.
Once you have a recovery then you need a SE Linux compatible recovery so for that connect the device to PC and mount the usb storage through recovery then transfer
This Bauner's KK kernel if you require CWM https://www.androidfilehost.com/?fid=95784891001608504
and this GeeckoDev Raw kernel if you require TWRP recovery http://forum.xda-developers.com/showpost.php?p=53978758&postcount=583 (download raw_kernel_r6_k44.zip)
once transfered to your device flash the one you require and remember we are flashing these kernel just for temporary use and once a rom is flashed they will get overwritten with the recovery that comes with the rom kernel so you dont have to worry about these kernels
Once flashed remember to reboot to recovery and not system, once the device boots into your desired recovery then either restore your previous rom from backup or falsh a new one
hope this helps and remember next time before flashing a rom read the OP and atleast 4-5 last pages. Believe me this will save you a lot of trouble in your future flashing endeavours
Hi
I'm running CM12.1 Nightly with Pure Performence MOD(CM version)
I'm trying to flash few kernel but nothing works.
I tried
1)Optimus Kernel
2)HurtSky(Extradt2w) Kernel
3)Elementary Kernel
When I flash the first one, my system reboots and shows " Finishing Boot" then again it reboots. This time its on a bootloop, the Cm boot animation appears and nothing else.
When I flashed the second one, it shows " Fastboot : Fail through-normal boot mode" That's it
When I flashed the third one, My screen starts flickering now and then in boot animation and after the boot too.
Does anyone know how to fix this ?
Do I need to change my SELinux ? Right now Its "Enforcing" ?
Your help will be greatly appreciated
Thanks in advance
no, kernel is not supporting your phone you just need to flash another kernel if you have in you internal memory or just restore backup
My phone has an unlocked bootloader. Rooted. Custom ROM (lineage OS Android 10). I want to underclock and undervolt it for increased battery but the current kernel is not capable of that. I am thinking of flashing a custom kernel but it appears most custom kernels for my phone were developed a long time before Android 10. Would it be safe to attempt to flash a kernel for an older Android version? If it were to not work, would it result in the possibility of a completely bricked device or would I be able to boot into TWRP and load a backup (do TWRP backups store the original kernel?)?
Thank you.
it would Hard-Brick or Soft-Brick.
Softbrick would happen because mismatching android versions will cause it to not boot.
Hardbrick would (unlikely) happen because custom kernels contain a device tree blob which if corrupted/incompatible would completely hardbrick the device. Not even fastboot would work because the little kernel (the kernel that handles fastboot/recovery/normal boot) for some reason stops working if the device tree blob is not working.
@Ali_Shaikh744
Android doesn't have an own kernel: In the world of Android its kernel is a modified Linux kernel matching a device's hardware. Using a wrong kernel makes the phone unuseable.
As said the Android kernel per se does not exist, but every manufacturer maintains a different Linux kernel for every device. This is partly due to the fact that every manufacturer cooks its own soup and wants to stand out from the competition with a special feature. Sometimes it's the driver of the camera module, which is not freely available, but usually the graphics drivers and many other modules remain closed source.
The Anroid recovery has it's own kernel and you can boot an Android independently of the boot partition ( i.e., booting up/from the recovery partition - that's what you do when you boot in recovery mode ).
xXx yYy said:
@Ali_Shaikh744
Android doesn't have an own kernel: In the world of Android its kernel is a modified Linux kernel matching a device's hardware. Using a wrong kernel makes the phone unuseable.
As said the Android kernel per se does not exist, but every manufacturer maintains a different Linux kernel for every device. This is partly due to the fact that every manufacturer cooks its own soup and wants to stand out from the competition with a special feature. Sometimes it's the driver of the camera module, which is not freely available, but usually the graphics drivers and many other modules remain closed source.
The Anroid recovery has it's own kernel and you can boot an Android independently of the boot partition ( i.e., booting up/from the recovery partition - that's what you do when you boot in recovery mode ).
Click to expand...
Click to collapse
So what you are saying is that boot has its own kernel and recovery also has its own kernel therefore only the boot kernel will be changed if I were to flash, meaning recovery will still be accessible?
Once you install TWRP device's Stock Recovery gets removed. So before flashing a new Linux kernel you might have to flash the full stock firmware to your device to get the Stock Recovery along and remove TWRP thereby.
Why don't you just boot your custom kernel over Fastboot? The bonus is that if it doesn't work, you can just reboot into the working kernel on storage.
xXx yYy said:
Why don't you just boot your custom kernel over Fastboot? The bonus is that if it doesn't work, you can just reboot into the working kernel on storage.
Click to expand...
Click to collapse
I thought old Samsung devices don't support Fastboot? I tried for multiple hours to get my device to reboot into fastboot mode even when I was using the stock kernel, stock OS and stock recovery. If I attempted "adb reboot bootloader" it would restart but go to the OS rather than fastboot. Even trying to get it into fastboot with the new OS doesn't work. I tried rebooting through 1.PC, 2. LineageOS settings, 3. wifi ADB shells through another Android device but nothing worked. Finally I came across information that old Samsung devices don't support fastboot
xXx yYy said:
Once you install TWRP device's Stock Recovery gets removed. So before flashing a new Linux kernel you might have to flash the full stock firmware to your device to get the Stock Recovery along and remove TWRP thereby.
Click to expand...
Click to collapse
But what is the problem if I were to flash using TWRP rather than stock recovery?
Ali_Shaikh744 said:
I thought old Samsung devices don't support Fastboot? I tried for multiple hours to get my device to reboot into fastboot mode even when I was using the stock kernel, stock OS and stock recovery. If I attempted "adb reboot bootloader" it would restart but go to the OS rather than fastboot. Even trying to get it into fastboot with the new OS doesn't work. I tried rebooting through 1.PC, 2. LineageOS settings, 3. wifi ADB shells through another Android device but nothing worked. Finally I came across information that old Samsung devices don't support fastboot
Click to expand...
Click to collapse
That's the 1st time here you say a Samsung phone is involved. Yes, Samsung devices doesn't know of Fastboot mode , the Koreans use the ODIN / Download mode instead.
Ali_Shaikh744 said:
But what is the problem if I were to flash using TWRP rather than stock recovery?
Click to expand...
Click to collapse
As I can see you understood nothing. Sorry to say this.
xXx yYy said:
As I can see you understood nothing. Sorry to say this.
Click to expand...
Click to collapse
Yeah I don't understand. I tried rereading. I still don't understand. Can you please elaborate as my comprehension skills are poor.