Related
Hai ,
I downloaded my phones kernel source and compiled with some additional configuraton..
Now I got these files .vmlinuz,image,zimage,and a tar'ed archive of zimage with name kernel_......_.tar
how can I make odin flashable (or any how flashable) rom file from this?
I tried to make boot.img with mkbootimg and initrd extracted from original stock rom
Flashing was succes according to odin But It doesnt boot.
any one please help me
I also like to know is there any way turn off splash screen and see the debug msgs from kernel during boot?
Any one please help
My phone is galaxy young GT-S5360
Update:
I figured out that problem is not with the additional configuration options I given during kernel compilation.
Problem is with the tools (or incorrect usage of tools) .
I tried making boot.img with original kernel and initramfs and that also not worked (flashing was successful.but
Booting failed).
I don't have much experience in android.i only know some linux
Any one please help me
Please please please.......
Update:
Finally I think I found how to make boot.img from kernel(zImage).The problem was with the "--base-address" option in the mkbootimg toool. I found my device's base address from kernel configuration file (.config).
now , boot.img produced from the kernel which was extracted from stock rom works well.
but boot.img produced from my custom kernel boots,but nothing displys in the screen.
I dont know how to debug it . I cant even see the debug messages from the kernel
Any one knows any clues,hints or any thing regarding this please please help me
i dont know why any no one replay to my post.
I dont have privilege to post this question in developers thread.thats why i am asking it here
Is it a wrong way? I dont know.
Click to expand...
Click to collapse
Thank you sir to be the first succefully create custom kernel...
Far before anyone can create it...
I'm always waiting ur great work again into sgy device...
This kernel will provide you the standard stock kernel and also includes TWRP recovery.
( disclaimer )
I AM NOT TO BE HELD RESPONSIBLE IF YOU DAMAGE YOUR PHONE
Using Odin to flash this kernel WILL increase your binary counter.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
( features )
- Team Win Recovery Project 2.2.1
- CIFS Support
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
( how to install using Odin )
1. Restart into download mode by pressing Power + Home + Vol Down
2. Start Odin, and flash the attached kernel as PDA.
Remember to extract the attached file only once. if you end up with a kernel.bin.md5 you extracted twice!
Do not use the PIT, do not have any options checked except for "Auto reboot" and "F. Reset Time"
3. Wait for the device to reboot
( how to install using DD )
This method does not increase your binary counter, but your phone needs to be rooted so you can perform this!
IF YOU'RE NOT FAMILIAR WITH DD I RECOMMEND YOU TO AVOID THIS METHOD
1. Extract the attached file twice. You will end up with a kernel.bin.md5 file
2. Put the kernel.bin.md5 file to /sdcard
3. Start adb shell
4. Do the following commands:
Code:
$ su
# dd if=/sdcard/kernel.bin.md5 of=/dev/block/mmcblk0p15
# reboot
5. Wait for the device to reboot.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
( special thanks )
- Team Win for creating this awesome custom recovery.
- @Chris41g for starting the TWRP port.
- @hackbob for helping with the kernel issues.
( donations )
if you think that think that the work I put in this kernel is donation worthy,
then click the following link and buy me a beer/coffee/etc...
Donate via Paypal :good:
Enjoy! and don't forget to hit the thanks button
if you find any issues with this kernel, please report!
reserved.
Can you give me just compiled zImage i.e kernel image ASAP?
varun.chitre15 said:
Can you give me just compiled zImage i.e kernel image ASAP?
Click to expand...
Click to collapse
You can download the package and extract the kernel.bin.md5.
While building it's generated as zImage and after renamed to kernel.bin and md5ed for Odin
Well actually, that is not what I need because kernel.bin.md5 contains initramfs which is known as ramdisk usually. But I only need kernel i.e zImage which I am planning to repack to boot.img
Correct me if I am wrong
varun.chitre15 said:
Well actually, that is not what I need because kernel.bin.md5 contains initramfs which is known as ramdisk usually. But I only need kernel i.e zImage which I am planning to repack to boot.img
Correct me if I am wrong
Click to expand...
Click to collapse
Yep you are right, sorry for the misunderstanding.
I can build it (from Github) for you without the ramdisk but I'm not sure it will work correctly without the driver added from the ramdisk to the kernel image during the build.
---------- Post added at 05:27 PM ---------- Previous post was at 05:22 PM ----------
Just to be sure...
I'm trying to compile cm7 and the intrafms are added with the kernel while building the boot.img, because in the intrafms that we are adding to kernel image we are basically adding the modules for wifi,bt, etc...
You sure you don't need them?
hackbob said:
Yep you are right, sorry for the misunderstanding.
I can build it (from Github) for you without the ramdisk but I'm not sure it will work correctly without the driver added from the ramdisk to the kernel image during the build.
Click to expand...
Click to collapse
Ok can you do that, test it and report back ASAP?
This is needed before I release my ROM
btw I think we should move on to main DEV thread
Post your next reply over there
@varun.chitre15
you can try to build it from source...
the source code is available on github: https://github.com/diego-ch/android_kernel_samsung_janice
hackbob said:
[/COLOR]Just to be sure...
I'm trying to compile cm7 and the intrafms are added with the kernel while building the boot.img, because in the intrafms that we are adding to kernel image we are basically adding the modules for wifi,bt, etc...
You sure you don't need them?
Click to expand...
Click to collapse
Oh great!
Can you get me the boot.img compiled while building
I will take what all I need from it
---------- Post added at 09:01 PM ---------- Previous post was at 09:00 PM ----------
diego-ch said:
@varun.chitre15
you can try to build it from source...
the source code is available on github: https://github.com/diego-ch/android_kernel_samsung_janice
Click to expand...
Click to collapse
Well actually I am trying to avoid that because I have no experience in kernel development
Can i extract it from the rom? I got boot.img and recovery.img, is that you need?
Sent from my GT-I9070 using Tapatalk 2
Exactly!
Attach the boot.img
varun.chitre15 said:
Exactly!
Attach the boot.img
Click to expand...
Click to collapse
i sent you a pm
Hi,
I just flashed this using Odin and i cant see my sd card in TWRP so i cant flash any roms and also the device wont root using SuperOneClick it hangs on shell root #7 Waiting for device...
Would it be possible to create a kernel with recovery for Advance with NFC chip?
xCode195 said:
Hi,
I just flashed this using Odin and i cant see my sd card in TWRP so i cant flash any roms and also the device wont root using SuperOneClick it hangs on shell root #7 Waiting for device...
Click to expand...
Click to collapse
Have you setup USB drivers of your phone?
Waiting for device indicates, Superone click is unable to contact your phone.
Am I the only one with TWRP restore not Working properly?
Backedup the default partition (system, data and another that I don't remember), Restored, everything seems fine (no error on twrp) but after a reboot the phone goes into bootloop.
varun.chitre15 said:
Have you setup USB drivers of your phone?
Waiting for device indicates, Superone click is unable to contact your phone.
Click to expand...
Click to collapse
Yep I tried installing them again and it got stuck on the same step but now i also get Hardware ID Failed popup when I connect the device..
Should I reflash the kernel or do something else?
Iv backuped and restored a few times and its ok
Sent from my GT-I9070 using Tapatalk 2
hackbob said:
Am I the only one with TWRP restore not Working properly?
Backedup the default partition (system, data and another that I don't remember), Restored, everything seems fine (no error on twrp) but after a reboot the phone goes into bootloop.
Click to expand...
Click to collapse
I was testing antonio's rom yesterday and before that I made a full backup.
today I restored my backup and everything was fine.
get me a logcat, a dmesg log and also a recovery.log so I can take a look on whats wrong.
xCode195 said:
Hi,
I just flashed this using Odin and i cant see my sd card in TWRP so i cant flash any roms and also the device wont root using SuperOneClick it hangs on shell root #7 Waiting for device...
Click to expand...
Click to collapse
you can also use CWM Flasheable SuperSu from Chainfire instead of supéroneclick
do you have an external sdcard? it wont work with internal memory.
diego-ch said:
you can also use CWM Flasheable SuperSu from Chainfire instead of supéroneclick
do you have an external sdcard? it wont work with internal memory.
Click to expand...
Click to collapse
I would try that if I could get TWRP to read my sdcard,it says its browsing the sdcard but none of my files or folders are there and its just empty.When i reboot into the system everything is there but not in TWRP...
Has anyone else made any serious attempts at compiling a kernel? Prompted by doctorow's thread about the wakelock issue, I got interested in compiling a kernel so it could actually be fixed. For anyone who's tried at all, there are obviously some missing files in Lenovo's release.
I tried copying over the missing files from ASUS's Zenfone kernel release (since it uses the same SoC and their kernel had all the files that make was complaining about). Between that and commenting out some references to a nonexistent tablet_config.h header, it managed to at least finish compiling. Unfortunately I don't have a bootloader-unlocked device to test on yet, so I'm not terribly confident that it actually works.
P.S.: I'm not really sure if this belongs in the dev section or not? Sorry if it's in the wrong place, but I can't start threads there anyway at my current post count.
iampanis said:
I tried copying over the missing files from ASUS's Zenfone kernel release (since it uses the same SoC and their kernel had all the files that make was complaining about). Between that and commenting out some references to a nonexistent tablet_config.h header, it managed to at least finish compiling. Unfortunately I don't have a bootloader-unlocked device to test on yet, so I'm not terribly confident that it actually works.
Click to expand...
Click to collapse
Interesting, I haven't even gotten that far when I tried to compile them. The sources are most likely not up to date or even representative of the actual firmware kernel. For example, when I looked at the battery driver, I noticed in the published sources, the polling interval was hard-coded in such a way that it would completely ignore the setting of the poll_interval kernel parameter. But we know that this is not true for the actual firmware which is in fact respecting the setting of said parameter.
@Grarak and me have managed to get the messy "source code" of Lenovo to build. I have additionally added some security patches and stripped some kernel modules. Since we don't want to violate the GPL like Lenovo, we have pushed the kernel to GitHub.
Bear in mind that there may be some issues, given the kernel is a work in progress. It boots on stock as well as on cm-12.1, though.
Olivier said:
@Grarak and me have managed to get the messy "source code" of Lenovo to build. I have additionally added some security patches and stripped some kernel modules. Since we don't want to violate the GPL like Lenovo, we have pushed the kernel to GitHub.
Bear in mind that there may be some issues, given the kernel is a work in progress. It boots on stock as well as on cm-12.1, though.
Click to expand...
Click to collapse
Same kernel works for both 830f and 1050f?
Could you please post a compiled kernel? (which I assume can be flashed simply via fastboot)
Thanks!
raenye said:
Same kernel works for both 830f and 1050f?
Could you please post a compiled kernel? (which I assume can be flashed simply via fastboot)
Thanks!
Click to expand...
Click to collapse
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Olivier said:
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Click to expand...
Click to collapse
Hello, I have a 1050F too is somebody tried this kernel on 1050F? Is it possible to support wake gesture kernel extensions with this kernel?
Olivier said:
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Click to expand...
Click to collapse
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Looking forward to alpha-grade CM....
raenye said:
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Looking forward to alpha-grade CM....
Click to expand...
Click to collapse
Did you use.
Fastboot Flash recovery recoveryname.img.
or
Fastboot flash boot bootname.img
To send it to the tablet.
corasman said:
Did you use.
Fastboot Flash recovery recoveryname.img.
or
Fastboot flash boot bootname.img
To send it to the tablet.
Click to expand...
Click to collapse
The kernel goes to the boot partition. So 2nd option.
raenye said:
The kernel goes to the boot partition. So 2nd option.
Click to expand...
Click to collapse
Thanks ,I'll give it a try.
O.K tried this
I put the file in to my ADB folder
from a command prompt I typed Fastboot flash boot c:/adb/kernel-yt2-20160327.img and it returned
FAILED (remote: unknown command) any suggestion please.
corasman said:
Thanks ,I'll give it a try.
O.K tried this
I put the file in to my ADB folder
from a command prompt I typed Fastboot flash boot c:/adb/kernel-yt2-20160327.img and it returned
FAILED (remote: unknown command) any suggestion please.
Click to expand...
Click to collapse
Using windows? paths are c:\directory\file and not c:/directory/file
I used the fastboot executable from the tethered recovery package.
Checklist:
Did you unlock bootloader? it won't boot otherwise.
Did you backup current boot partition from TWRP/CWM?
Did you boot the tablet in fastboot mode? (down+pwr)
Can fastboot detect your tablet? (fastboot devices)
raenye said:
Using windows? paths are c:\directory\file and not c:/directory/file
I used the fastboot executable from the tethered recovery package.
Checklist:
Did you unlock bootloader? it won't boot otherwise.
Did you backup current boot partition from TWRP/CWM?
Did you boot the tablet in fastboot mode? (down+pwr)
Can fastboot detect your tablet? (fastboot devices)
Click to expand...
Click to collapse
Yes to all.
I wondered if the command slashes were the right way / or \ the way I used is what I used to unlock the bootloader and install TWRP.
I have tried the slashes the other way and get the same result, as in \ .
raenye said:
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Click to expand...
Click to collapse
Hmm, I'm getting a high battery_wake_lock (on the April OTA firmware) -- even when running this kernel!
Any idea how can this be?
Hi,
I was trying to play a little bit with kernel provided by @Olivier and @Grarak ...
1. Binary Image kernel-yt2-20160327.img boots up fine on 1050l, but LTE is not working. Rest seems to be fine...
2. In next steps I replaced initrd.img with a little modified stock one - and LTE started to work - I removed from initrd almost all modules leaving only bcm43241.ko.
3. Battery wakelock problem seems not be resolved - brief check at bq27x00_battery.c in repository shows that wake_lock is still set under bq27x00_battery_suspend_resume()
... so I trying to fix this battery driver but I have problem with kernel - I can compile it successfully, but it doesn't boot
@Olivier:
1. Which branch was used to build kernel-yt2-20160327.img?
2. Which config did you use ?
My procedure using android-ndk-r12b toolchain:
# git clone ...github.com/lenovo-yt2-dev/android_kernel_lenovo_baytrail
# export PATH=~/android_yoga/toolchain/bin:$PATH
# export CROSS_COMPILE=x86_64-linux-android-
# export ARCH=x86
# make cyanogenmod_YT2_10_defconfig --- if this right config?
# make -j8 ----- lot's of warninigs, but kernel is compiled sucesfully.
# abootimg --create boot_test5.img -f bootimg.cfg -k bzImage -r initrd.img ---- bzImage from arch/x86/boot
> fastboot.exe flash boot boot_test5.img
... kernel stuck somewhere, it's doesn't even come to Zygote phase (lenovo animation). Is there any way to see kernel boot messages ?
Hi
I would also like to experiment with the Kernel, but I need to unlock the bootloader. unfortunately the thread is deleted files and I can not, can anyone help me even for private?
I have a 1380F in KitKat
Kind regards
airmalaga said:
Hi
I would also like to experiment with the Kernel, but I need to unlock the bootloader. unfortunately the thread is deleted files and I can not, can anyone help me even for private?
I have a 1380F in KitKat
Kind regards
Click to expand...
Click to collapse
I used this procedure: mobility.forumsee.com/a/m/s/p12-9574-0973888--yoga-tab-unlocking-daaa-deee-daaa-dooo.html
Patched ESP file I found on another forum: forum.android.com.pl/topic/259763-odblokowanie-bootloader%C3%B3w-yoga-tab-2/#entry4598175
For me it worked on Lolipop, but I as know bootloader changed arch x32->x64 during Lolipop->KK upgrade... I don't know if this esp will work on KK (at least do backup of ESP and boot partitions before).
---------- Post added at 12:07 PM ---------- Previous post was at 11:52 AM ----------
BTW: I was able finally to compile and startup my modified kernel using CM building engine from this thread .
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
If anybody is interested i can attach img file.
Thx :good:
jasfasola said:
I used this procedure: mobility.forumsee.com/a/m/s/p12-9574-0973888--yoga-tab-unlocking-daaa-deee-daaa-dooo.html
Patched ESP file I found on another forum: forum.android.com.pl/topic/259763-odblokowanie-bootloader%C3%B3w-yoga-tab-2/#entry4598175
For me it worked on Lolipop, but I as know bootloader changed arch x32->x64 during Lolipop->KK upgrade... I don't know if this esp will work on KK (at least do backup of ESP and boot partitions before).
---------- Post added at 12:07 PM ---------- Previous post was at 11:52 AM ----------
BTW: I was able finally to compile and startup my modified kernel using CM building engine from this thread .
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
If anybody is interested i can attach img file.
Click to expand...
Click to collapse
jasfasola said:
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
Click to expand...
Click to collapse
Cool, could you push your patch to GitHub?
jasfasola said:
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
Click to expand...
Click to collapse
The kernel should be working, but the ALS is broken (seems to be a sensor from Avago) - you'll notice that if you use automatic brightness.
Olivier said:
The kernel should be working, but the ALS is broken (seems to be a sensor from Avago) - you'll notice that if you use automatic brightness.
Click to expand...
Click to collapse
Fixed. That was quite easy. Driver al3320 was in place. The problem was permissions set by script init.byt_t_ffrd8.rc in initrd. By default it's root/root, but it should be system/system. I already corrected paths and checked it - it's working. If you could give me permission to repo I can push the patch.
BTW: I see lot's of things are being hard-coded into initrd scripts. Since we changed config kernel, all those scripts must be checked. I can try to do it in free time...but some things are platform depended so, another original initrd from lolopop on 830f would be nice to compare...
jasfasola said:
so, another original initrd from lolopop on 830f would be nice to compare...
Click to expand...
Click to collapse
What do you need exactly? @jasfasola
Hello,
I am just new with Samsung smartphones, previously I was on some other devices such Nexus which are easier to mod.
I would like to tweak the kernel( I already got the sources) to add few things but I need for that eventually the ramdisk and the kernel image to make a boot image.
I wanted to download the latest firmware, hoping a default boot image was integrated in it and that I could unpack but I got issue and connection loss so I can't even take a look at it.
I think I will be able to get the boot image with the dd command but to do so I need to be in a mod recovery(such twrp) and currently I can't.
Thx u
Firstly you've created a voting thread. If this is a standard question I suggest in future you leave the options at default.
Why can't you use TWRP?
My build also supports raw image backup of the boot partition.
Sorry about creating wrong thread type
I have extended this feature to include BOOT
Click to expand...
Click to collapse
Woot Yeah I didn't know about that!
So I can just get the current boot image, unpack it, replace with my kernel image, repack and done.
And then flash the boot image throw a zip install or your extended function.
Btw, I am was looking over the net but couldn't find an exact answer to this extra Q, is there any fastboot mode ? So I can just boot in a custom kernel image before flashing it.
Yep, just backup the boot partition using twrp.
Locate the boot image backup in the twrp backup folder.
Unpack it, make your mods, rename it boot.img, copy it to internal or external storage and flash it with TWRP using the INSTALL button.
Samsung devices dont have a fastboot mode.
@ashyx answered my questions, thx to him!
>Samsung devices dont have a fastboot mode.
My latest Samsung Tablet has a fastboot mode but it was manufactured around the end of 2012 ... So it is not quite recent
I've never known a Samsung device to use FASTBOOT, so that's news to me.
Samsung uses its own proprietary ODIN mode.
Which device is this?
Ahhah you gonna say I am half of a lier.
It was my nexus 10. Built by Samsung and running the 5250 exynos chip
Okay boys Just got this phone like a week ago. Used it to replace my Samsung that was acting up. Convinced my wife I needed it and then proceeded to toy with it.
I unlocked the bootloader, flashed custom recovery (TWRP latest), and rooted (Magisk latest) to stick recovery. I was running full stock 8.1.0 no custom ROM yet I was doing reading before I wan
ted to flash. Got to feeling comfortable so I got everything ready files downloaded USB hooked up and decided to be safe and make one more back up.
So thats what I did, I made a full TWRP backup, every single partition onto an external USB. So I am safe, right? Best to be safe... But that's when I rebooted from TWRP it boot looped.
So now I am currently stuck at boot. I get the warning screen about the unlocked bootloader then "Google" logo boot screen then a black screen and back to the start again. I knew that wasn't right, so I booted into fastboot with Power + Volume Down, cycled to recovery and selected it then... boot loop. No recovery. Hmmm... That's not good. But keep calm... did some research and found a few things. So i did this...
Heisenberg said:
FAQ can be found in post #3!
[SIZE=+1]10. How To Flash The Factory Images (And Return To Stock)[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box. This will wipe everything from the phone. If you wish to flash the factory images without wiping your personal data from the internal storage please move on to the next section.
Go to Settings/Backup & Reset and perform a factory data reset. This will remove all of your user data from the device (apps, settings, photos, music, etc).
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
If you wish to you can also relock the bootloader with this command:
Code:
fastboot flashing lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all user data from the device.
Once all operations are complete you can reboot the device.
Click to expand...
Click to collapse
and that didnt work either so next I tried this
Train88 said:
Like other curious 6P users, I flashed the "full ota" zip to check out Nougat. Then I tried to restore my nandroid for Dirty Unicorns, and apparently TWRP 3.0.2-1 had a fatal flaw that borked the EFS backup. I tried literally everything I could think of, until I saw the process @be_vigilant did to revive his phone. I'm going to be using his process as the base for the guide, as well as linking you to my nandroid that has now helped two other people revive their device.
What you need:
*MMB29P factory image (although MTC20F also worked for someone).
Direct download link: https://dl.google.com/dl/android/aosp/angler-mmb29m-factory-616cf265.zip
*My nandroid backup (its stock MMB29P, decrypted and rooted)
https://www.androidfilehost.com/?fid=24686679545612465
*TWRP recovery image (3.0.2-0 or one of the newer builds that fixed the EFS stuff)
https://dl.twrp.me/angler/
*Android SDK or at least platform-tools (for fastboot, adb, etc)
The Process:
1. Extract the factory image into the location where you have fastboot.exe (mine is C:\Android\sdk\platform-tools)
2. Extract the nandroid backup - doesn't matter where, I'll explain later
3. Make sure you are in bootloader mode, and run flash-all.bat from the factory image
4. Flash TWRP (fastboot flash recovery twrprecovery.img)
5. Boot into TWRP, and make a new nandroid backup. This step is just to create the TWRP backup folder on your device
6. Now go to wipe, advanced wipe, click on each partition one at a time, choose "Repair or Change File System", then select "Repair File System" - do this for dalvik/art, system, data, internal storage, and cache. It may not work for all of them, but its ok.
***you must mount data again in TWRP after doing this, or you will not be able to see anything***
7. Copy & paste my nandroid onto your device in the correct location (sdcard/TWRP/BACKUPS/XXXXXX)
8. Restore my nandroid and try to boot.
9. If it still does not boot at this point, then you need to run these adb commands (while in TWRP) that @bogomil4e kindly reported to wipe the EFS partitions
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384 -and-
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Now you should be able to boot up and do anything you want again. Please do not mirror my nandroid or take advantage of it - I am making it available only for people to utilize as a way to unbrick their phone!
Click to expand...
Click to collapse
And that didn't work either. To be clear I left my bootloader unlocked. Each process works as far as flashing all the files via fastboot. But if I try to reboot or boot recovery, stock or custom, I boot loop. I have been looking everywhere and I dont see a solution and was hoping to get some help.
edit: Now I have also tried this... Doesnt seem to be the bootloop of death.
XCnathan32 said:
Read First: This method is relatively drastic, and will hurt device performance some. You should only use this as a last resort, if the more basic methods of fixing a soft brick didn't work (e.g, factory reset, flash stock firmware, etc.)
*Update 8/22: Android O is working with 4 Cores now! Big thank you to @xls654 for finding out how to get Android O to work.
*Petition:
I made a petition for Google to officially release and sign modified boot.imgs, so that people with locked bootloaders can fix their devices too. Check it out here. (I apologize for dumbing it down so much, I wanted to make sure everyone could understand it)
*Changelog:
8/25 - EX kernel for Android O added.
8/22 - Android O DPR6 boot.img and source added.
8/16 - Started making this fix open-source, source code section added in OP. Also uploaded modified Franco and Flash kernel & source.
8/10 - Added PA 7.2.2 and DarkROM boot images.
8/08, 2nd change - Uploaded modified boot.img for firmware 48C.
8/08 - Updated EX kernel to version 4.1.2. This updated zip adds the CPU utilization patch to the init.elemntalx.rc, instead of removing the old init.angler.rc and copying the new init over. That should mean more compatibility with Roms/kernels that modify the init.angler.rc. I also modified the camera-daemon to use cpus 0-3 instead of 0-2, so hopefully this should make the a camera bit faster too.
8/07 - Added boot.img that only uses 1 core. Someone suggested I make a boot.img that only uses 1 core, just to see if it works for devices that didn't work with the 4 Core fix.
7/30 - Added universal EX zip, this zip should modify your kernel to use only 4 cores, and it should modify it to utilize all 4 cores. You can flash this over most ROMs and it should work. Also added a donation url, and this changelog.
7/29, 2nd change - Added Pure Nexus and PA dev version boot images, modified to use 4 cores, and utilize all 4.
7/29 - Updated this fix to greatly improve performance. Before this fix, the device was only using 1 core for foreground tasks, now it will use all 4 cores. Also revamped OP.
7/21 - Fix created, stock boot.img, TWRP image, and EX kernel modified to use 4 cores.
*What this fix does, and how to apply it:
The problem:
The problem with most of the devices in a BLOD, is that a hardware failure related to the BIG cluster has occurred. This fix remedies the problem by disabling the BIG cores. Unfortunately, this does mean that you will take a performance hit. However, I am continually working on ways to improve the device's performance.
The update: If anyone remembers device performance with the first fix, it was hurt a lot, however, after finding out that the device was only using 1 core for all foreground tasks, I modified the ramdisk to utilize all 4 cores more effectively, and it helps a lot.
Requirements: For this fix to work, you need:
A brain
A computer
A bootlooping 6P with an unlocked bootloader/OEM unlocking enabled
The modified files of your choice
Fastboot on your computer (preferably installed system wide). If you do not know what this is, or do not have it, look at this post. Answer yes to all of the prompts to install it.
How to apply the fix:
Boot your phone into bootloader (hold power and volume down).
Connect your phone to the computer.
Go to the folder where you have the modified files, then hold shift and right click in a blank space, click on "open command prompt here" in the menu that pops up.
In the command prompt: type "fastboot flash boot [name of the file here]" and then press enter. If you're flashing TWRP, replace boot with recovery. (Linux users, make sure you're running as root)
Edit: With the new EX zip, you shouldn't need to flash the boot.img anymore, you can just flash twrp, and then flash EX in twrp.
Boot up your phone, and hopefully it should work!
*If your phone is bootloader locked/OEM locked:
You can try to get your phone to boot long enough to enable OEM unlocking. Some users have reported success by freezing their phone for a bit, then booting it. Others have let their battery drain all the way, and then tried to boot their phone, but the most successful method seems to be heating up your phone (a lot).
If you do attempt any of these methods, make sure you have time and patience, as it will take a long time.
To enable OEM unlocking and unlock bootloader:
Go to settings.
Go to developer options, if you do not see that, go to "about phone", scroll to build number, and then tap it 7 times. You should now see developer options in settings.
Once you're in developer options, click on "OEM unlocking" and accept the prompt.
Now reboot your phone to bootloader, connect your phone to the computer, and type "fastboot flashing unlock" Your bootloader should now be unlocked.
*Downloads:
Boot.img from stock 6.17, 8.0 firmware: Download | Mirror. This Image is the from the first official release of Android O, and is modified to use 4 cores. It also disables forced encryption as a bonus. Thank you to @xls654 for figuring out how to get Android O to work.
Boot.img from stock 48C, 7.1.2 firmware: Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
Boot.img from stock 48B, 7.1.2 firmware: Download |Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
TWRP version 3.1.1: Download | Mirror. This TWRP image is modified to use only 4 cores.
EX kernel version 5.03: Download | Mirror. EX kernel 5.03 works with android 8.0.0. This zip applies the 4 cores patch, but you will need to flash it over an already modified boot.img to work.
Elemental X kernel version 4.12, universal zip: Download | Mirror. This zip is EX kernel, modified to use only 4 cores. Update: I modified it to apply the CPU utilization patch too, so now this is a universal zip, flash it over almost any ROM, and you should now have the BIG cores disabled fix, and the little core utilization fix.
Flash kernel version 2.5: Download | Mirror. This zip is modified to use only 4 cores, and utilize all 4. Works with android 7.1.2. You can flash this over almost any ROM, including stock, and it should boot again.
Franco kernel r55: Download | Mirror. This zip is modified to use only 4 cores, and utilize all 4. Works with android 7.1.2. You can flash this over almost any ROM, including stock, and it should boot again.
You will most likely not need these images. It will be much easier, and much more universal to flash one of the custom kernel zips above ^^^
PA boot.img from PA version 7.2.2, build 8/10: Download | Mirror. Uses only 4 cores, and has core utilization patch.
PA boot.img from PA version 7.2.1: Download | Mirror. Boot.img from PA dev preview 7.2.1, uses only 4 cores, and is modified to utilize 4 cores more effectively. Flash it after you flash the PA zip, either with fastboot, or TWRP image flash.
Pure Nexus boot.img from Pure Nexus 7/25 build Download | Mirror. This image is modified to use only 4 cores, and it has a tweak to utilize the 4 cores more effectively. Flash it after you flash Pure Nexus, either with fastboot, or TWRP image flash.
DarkROM boot.img from 7/21 build: Download | Mirror. This image is modified to use only 4 cores, and has the utilization patch.
Boot.img modified to use only 1 Core. Some people were reporting that the 4 core images weren't working for them, someone suggested that I make a 1 core version to see if that helps at all. Edit: seems not to help unfortunately. Here it is: Download | Mirror
Unfortunately, I have not been able to get Android O working yet, but I am working on it right now.
If you have a favorite custom ROM or kernel you want to ported over to use 4 cores, let me know, and I'll put it up.
*Source code:
Flash kernel: source | Flash ramdisk/AK2: source.
Franco kernel: source | Franco ramdisk/AK2: source.
Android O boot.img: source.
p-0000000000000000000000000000007 (sorry that was my kitten)
*Tested custom ROMS/kernels
I have used Pure Nexus by flashing the modified EX zip over it, it has notably better performance than the stock ROM, and very good battery life. It's a clean, stable ROM, with plenty of good features that are actually useful.
I have also used Paranoid android dev preview, very good performance, definitely my favorite as of now. Battery life leaves something to be desired, but I have not tried a custom kernel yet. Also, 7.2.1 seemed smoother to me than 7.2.2.
If you have a custom ROM/kernel that worked for you, let me know and I'll put it up here.
*To improve performance slightly:
Flash a custom kernel. I will upload more kernels as I test more, so stay tuned.
Overclock the little cores. It can slightly help offset the lost performance, on my 6P, I have mine overclocked to 1632MHz, and it works perfectly for me. Edit: I actually recommend not overclocking. Many people have reported their Little cores failing, so I would go for longevity on this device, and keep it at stock clocks, or even underclock it. The speed difference you get from overclocking is negligible anyways.
Disable animations in developer options. Seriously, as soon as I found out about this tweak, I've used it on ever single device I've owned, it helps a ton.
Turn resolution down to 1080p. On a small screen, the difference in between 1080p and 1440p is not very noticable. To do this, first get root access, then download a terminal emulator. In the terminal, type "su" and grant it root access, then type "wm size 1080x1920", and finally, change the density "wm density 400". Personally, I like my density at 400, but you can expieriment with it. Lower density=Smaller items and text, Higher density=Bigger items and text. Also @Adithya FRK mentioned that you also want to put density in build.prop so apps display correctly. Change ro.sf.lcd_density=560 to your density, if you changed it.
*Credits:
@rchtk, His post here gave me the idea for how to modify the images.
@flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
@tr1gg3r.man, He made the the PA kernel, I just added a couple modifications. In no way am I trying to steal and/or discredit his work.
@BeansTown106, He made the Pure Nexus kernel, I just added a couple modifications. In no way am I trying to steal and/or discredit his work.
@Dark_Eyes_, He made the DarkROM kernel, I just added a couple modifications to it. In no way am I trying to steal and/or discredit his work.
@[U][COLOR="Purple"]The Flash[/COLOR][/U], He made The Flash kernel, I just made a couple modifications to it. In no way am I trying to steal and/or discredit his work. His posts have also helped me a lot with learning how to build a kernel from source, understanding how to use git more, etc. I recommend you check them out if you are interested in getting started with android development.
@[B]franciscofranco[/B], He made Franco kernel, I just made a couple modifications to it. In no way am I trying to steal and/or discredit his work.
@xls654, He found out how to get Android O working with 4 cores.
FAQs
What's the password for TWRP/Why is TWRP asking for a password? - In android 7.0, Google added forced encryption to the data partition. To get around this, click cancel when TWRP asks you for a password, and then factory reset the device. Then you can flash EX kernel/Magisk to disable forced encryption.
Why am I getting an error when I try to flash the images? - Your bootloader is probably not unlocked, try running the command "fastboot flashing unlock", If you get an error there too, then you will have to enable OEM unlocking before you can continue.
It's not working for me, how do I fix it? - My only advice for that is: "Flash the stock firmware for whatever version image you're trying to flash, then reflash the images again" If you're stuck on the boot animation, wait at least 20 minutes before you declare it's not working. If none of that works, chances are your device may have a different problem.
Does EX kernel have the new speed fix? - Yep, you can flash this over just about any ROM, and it should patch it to use only 4 cores, and use them well.
I would like to help as many people as I can, however, I am much more likely to be able to easily help you/reply to your post if you clearly state your problem and the steps you attempted to fix it. I will be much less likely to reply to posts such as "omggg i flashed the image and my phone won't boot helppp" Please read through post first, I did not spend time typing up this OP for no one to read it. If I can see that you read through the OP and have attempted all the steps, then I will be much more willing to help you.
I set up donations on my profile, for those of you who want to donate. I have spent countless hours modifying, flashing, testing, and helping, don't get me wrong, I love doing this and helping y'all out, but donations really keep me motivated to keep going, and donations also will help me fund new equipment and devices that will help further my android development. Every single donation is appreciated Donate to me here!
If this guide helped you, please click thanks, it means a lot to me
Click to expand...
Click to collapse
Please anybody if your willing to take a swing at helping me I would really appreciate it!
Thanks in advance!
Anybody have any insight?
Were you successful at returning to stock?
If not, I'm afraid you're suffering from the bootloop issue :'(
No i was not, but the standard 4 core fix isn't working for me either so I don't know what else to do.
I did something similar. Tried to update to latest may patch from custom rom. No sim found...so tried some radios..nothing. Thought I better get back to full stock. Similar to you tried the individual flashes and then the OTA as a whole. During that process I locked the bootloader. Now I get the yellow screen text says software isn't standard...then google logo...then the red text says os is corupt possibly...then google logo, forever. No loops it seems but just doesn't boot.
Anyone with thoughts?
i am on my 2nd 6p with the same problem after installing twrp. the first one i got operational by sideloading via twrp a factory img. to get the sideload to work i had to go back to android 6, 7 and 8 would not work. right now the google firmware site is not working, it has been out for a few days, so i have not been able to try it on the second 6p.
edit; now that i recall the factory img would not load after installing. i then went back to fastboot recovery and got the distress robot, twrp was of course gone. from there i did a factory reset which got me back to go and the long climb back to oreo.