NOTICE
As i no longer own this tab, i will no longer be providing support for it.
As devhost is slowly and surely deleting my files, i have moved them
to androidfilehost https://www.androidfilehost.com/?w=files&flid=23547
As androidfilehost does not delete files, these recoveries will remain hosted indefinitely.
m
Update 1 Uploaded - Choose v2
i am doing a new build as i may have missed setting support for extended attributes.
will update shortly.
v2 is up - link updated
changed default security module to selinux and modified source /bootable/recovery-cm/updater/install.c
as follows:
<cm11 source dir>/bootable/recovery-cm/updater/install.c
in line 586 (under the function ParsePermArgs(int argc, char** args):
654:- parsed.has_capabilities = true;
654:+ parsed.has_capabilities = false;
mainly for testing. still functional as before.
on v2
okay,
i have been using v2 quite a lot since i posted it and it works pretty solidly.
A major note- to flash supersu update zip you must use most recent version from chainfire's site.
The adb experience is good provided you remember to mount data and system.
I will be getting to Philz Advanced after a little more practice with building.
Right now my attempt in th recovery arena will be to get aromafm built and working.
Both versions of my cwm build will remain posted.
m
edit- uploaded v2 Alien - i know, it's goofy but it looks pretty cool. =)
Philz Adv CWM 6.55.0 - CWM 6.0.5.0
sorted.
screen shots
Philz Adv CWM - Update August 2, 2014
Before all other things, @Hazou , Dude you rock !!
Unending thanks to @Phil3759 for making your source available.
okay so this is Philz Advanced Touch for GT-P5210 [fixed, no lag].
If anyone needs CWM rebuilt let me know.
This time i have released it in a flashable zip [CWM]. I wil be pulling the clunky one [Philz]
And with that, I think I am done with recovery building for now. Enjoy
the name of the file is PhilzAdvCWM-6_55_0-gtp-5210.zip. See OP for link.
m
AROMAFM
yup, aromafm :victory:
okay so,
issues are lag, resolution and possibly a ram related crash, in which event, force reboot [will return you to recovery] and then reboot normally.
i'm working on it. NOTE- enabling automount seems to reduce occurence of crash/hang.
in terminal ~#whoami
returns ~#uid0 :good:
busybox :good:
see OP for link. this is an initial offering and requires work.
thanks a million times to @amarullz for making his source available
thanks to @Hazou as ever :good:
please pm me to report bugs and issues. enjoy !
m
TWRP v2.7.1.0 for GT-P5210
Reserved for TWRP
Will be attemtping to improve/fix/sort terminal.
Didn't want to be unfair to TWRP users.
Will update.
m
Thanks @Siberian Tiger :good:
Okay so, TWRP is up. See OP for link.
I am still looking for what i need to know to make the terminal in twrp a less-suck experience.
No lag and, I am actually starting to like TWRP alot. I have tested on my tab, backup/recovery are good. aromafm installs and runs well. adb seems to be in order. I did trim the fstab leaving system, data/internal storage, cache, recovery, boot and external storage.
If other variants need different setup please let me know.
As always please do not post thank-you's. Bugs and issues only.
thank you for reading
m
Notes
I did not generate any new or additional code.
All sources are already available - CWM, PHILZ, TWRP, AROMAFM
However the patches applied to cm11 build environment are
@Hazou , infinitely thankable :good:
https://github.com/HazouPH/android_system_core/commit/54cf228097d58713d71a13a6c79794bfa373eab0
https://github.com/HazouPH/android_device_motorola_smi/blob/jellybean/patch/cwm_0001.patch
m
if i try to flash philz it keep saying my device is santos103g and not santos10wifi
i have 100% sure gt-p5210 it is on the back of the tablet
damian312 said:
if i try to flash philz it keep saying my device is santos103g and not santos10wifi
i have 100% sure gt-p5210 it is on the back of the tablet
Click to expand...
Click to collapse
hi,
you need to follow this thread from first post, hear me out,
you must first download, extract to /sdcard and dd write cwm 6.0.5.0 [recovery.img] with the following terminal command
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
from that point you can flash philz normally. the assert in the updater script is correct. it calls to your
/system/build.prop
and verifies whether or not you have the correct device. The issue is with your process and your build prop.
if you are unable to resolve the issue, you may extract the recovery.img from the zip and write it in the same
fashion as cwm 6.0.5.0 to your recovery block.
m
Thanks @stamatis
moonbutt74 said:
hi,
you need to follow this thread from first post, hear me out,
you must first download, extract to /sdcard and dd write cwm 6.0.5.0 [recovery.img] with the following terminal command
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
from that point you can flash philz normally. the assert in the updater script is correct. it calls to your
/system/build.prop
and verifies whether or not you have the correct device. The issue is with your process and your build prop.
if you are unable to resolve the issue, you may extract the recovery.img from the zip and write it in the same
fashion as cwm 6.0.5.0 to your recovery block.
m
Thanks @stamatis
Click to expand...
Click to collapse
Awsome. With the instruction spelled out to me, even I might be able to have a go att it.
BIG thanx for your patients with us end-users (that have no talent for coding )
/H
hmm...
Hey friend I have a question . How can we install twrp on the new 4.4.2 stock rom? I can't install it.it says some errors and reboots
FurFur_ said:
Hey friend I have a question . How can we install twrp on the new 4.4.2 stock rom? I can't install it.it says some errors and reboots
Click to expand...
Click to collapse
Read the OP completely.
moonbutt74 said:
Read the OP completely.
Click to expand...
Click to collapse
Of Course! thaaanks~~
moonbutt74 said:
dev-host link - http://d-h.st/users/moonbutt74/?fld_id=38524#files TO RECOVERIES
dev-host link - http://d-h.st/users/moonbutt74/?fld_id=38598#files TO AROMAFM - W.I.P.
NOTE- This is not a flashable/odin-able file. You must dd write to /dev/block/mmcblk0p11 [or appropriate recovery block]
Click to expand...
Click to collapse
"PhilzAdvCWM-6_55_0-gtP-5210.zip
Description: good 2 go kitkat kapable cwm flashable thanks Hazou @xda"
Is it flashable or not?
Edit it was not flashable, don't know why download states that.
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
"/dev/block/mmcblk0p11 Cannot open for write: Permission denied"
kgyirhj said:
"PhilzAdvCWM-6_55_0-gtP-5210.zip
Description: good 2 go kitkat kapable cwm flashable thanks Hazou @xda"
Is it flashable or not?
Edit it was not flashable, don't know why download states that.
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
"/dev/block/mmcblk0p11 Cannot open for write: Permission denied"
Click to expand...
Click to collapse
You need to execute the command as the root user, or what we call the superuser. Execute: su root. And then you are good to go.
Thanks @Divine_Madcat
m
moonbutt74 said:
hi,
you need to follow this thread from first post, hear me out,
you must first download, extract to /sdcard and dd write cwm 6.0.5.0 [recovery.img] with the following terminal command
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
from that point you can flash philz normally. the assert in the updater script is correct. it calls to your
/system/build.prop
and verifies whether or not you have the correct device. The issue is with your process and your build prop.
if you are unable to resolve the issue, you may extract the recovery.img from the zip and write it in the same
fashion as cwm 6.0.5.0 to your recovery block.
m
Thanks @stamatis
Click to expand...
Click to collapse
Okay i would like to flash this but because i currently have twrp installed and am not a fan cause it won't let me install 4.4. However i have know idea what this means. Can i flash this cwm using twrp?
Made TWRP Friendly
@jyerly
Okay so, this is Philz Recovery with the assert removed to be Old TWRP Friendly
TESTED, WORKING. I don't do it any other way.
devhost link - http://d-h.st/SSY
m :good:
HI Moonbutt74,
sorry for my maby silly question, but always just flashed via ODIN, CW; TWRP on my SGSII.....the Tab3 is differnet here and seems I have no clue .
I have rooted my Tab via the Root.zip and use the CWM from DutchDanny, still on stock firmware (see my sig).
I'd like to update to one of your new recoveries and go with Restl3ss Pimpdroid....but have no clue from terminal command.
Is there any hint how I execute the command you posted in OP?
Thanks for your kind help,
GeScha
Related
NOTICE: I no longer have a copy of the recovery image since goo.im went down. If anyone still has it, feel free to post a link. I'll leave the instructions here. Also, I won't be updating this since I no longer have a TF201 and ROM development seems to have shifted to a modified bootloader, which requires a different recovery image anyway.
Original post:
Warning: You must be on the 4.1.1 Bootloader to use this. Androwook and other stock based ROMs supply their own recovery.
With 4.4 based ROMs starting to come to our tablet, and official TWRP not flashing them, I thought I'd take a crack at updating it. As some of you may know, attempting to flash a KitKat ROM using the current version of TWRP fails, resulting in a "set_metadata_recursive" error. This updated version, based on the OmniROM fork of TWRP, fixes that.
Latest Version: 2.7.0.0-Voyager2k_v1.2
Instructions:
1.(Highly Recommended) Enable NVFlash if you haven't already. Check here for details.
2. Make sure you are on the 4.1.1 Jellybean Bootloader. If you are already running ParanoidAndroid or CyanogenMod, you're fine.
3. Download the recovery image here. The latest file is recovery1.2.img. EDIT: Links are broken. See above
4. You can use the same instructions that are on the TWRP page, but for convenience, I'll add them here. You have two options:
A. Fastboot. Boot the tablet into fastboot and use "fastboot -i 0x0b05 flash recovery recoveryX.X.img" (no quotes, replace X.X with whatever numbers are in the filename) from your computer to flash the recovery.B. Flash from terminal within the tablet. Open a terminal emulator within android and type "su" (no quotes) to get root access. Then type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4" (no quotes, replace X.X with whatever numbers are in the filename) to flash the recovery and reboot normally. This is critical, as the recovery won't flash until the system has rebooted normally.
If successful, the version number should read: "2.7.0.0-Voyager2k-vX.X" (X.X being my revision number)
Known Issues:
1. /system/media doesn't get backed up for some reason. Restoring backups works, but you won't have sounds or a boot animation. (I think this is fixed in the newest version, but I'm waiting on other reports before I remove this item)
Ususal disclaimer: I am not responsible if this messes up your tablet in any way.
Credits:
TWRP for making the recovery
Built from the OmniROM fork. Source is here.
Changelog:
Version 1.1 - 2/19/2014
Added support for the dock keyboard
Fixed /system/media not backing up properly
Synced with latest OmniROM recovery sources
Version 1.2 - 3/25/2014
Updated to TWRP version 2.7.0.0
A little cleanup behind the scenes
one more.
Works Great! Flashed without problems via fastboot :victory:
Thank You!
Now I just need an awesome 4.4. ROM to flash :fingers-crossed:
works also with the second instruction over the tablet
Excellent news
I tried through the Terminal but despite no error was presented it didn't worked. The recovery presented was the old CWM. After flashing through fastboot the new recovery popped out like a charm
Thanks.
thanks, it works through terminal. jut make sure to be root (su) and adjust the path of the recovery image
Sent from my EPAD using Tapatalk
thanks! This rec works and I have flashed cm11. Terminal works. U should insert "su" first
Sent from my GT-N7102 using Tapatalk
To use the second method you need to run su command first before using dd
Sent from my TF300T on OmniROM (4.4.2) using Tapatalk 4
Terminal
Just would like to ditto.
The process worked in the terminal on the device.
Thank you for this!
Bug report!
BUG REPORT!
There is a BUG in this version of TWRP:
It does not make any backup folder named media!
For example /system/media.
As result after recovery the folder /system has no this subfolder media and correspondingly missing boot animation and system sounds.
Dasdranamin said:
BUG REPORT!
There is a BUG in this version of TWRP:
It does not make any backup folder named media!
For example /system/media.
As result after recovery the folder /system has no this subfolder media and correspondingly missing boot animation and system sounds.
Click to expand...
Click to collapse
Thanks for the report. I'll look in to it.
Cyrozo said:
Excellent news
I tried through the Terminal but despite no error was presented it didn't worked. The recovery presented was the old CWM. After flashing through fastboot the new recovery popped out like a charm
Thanks.
Click to expand...
Click to collapse
Are you sure you placed the new "recovery.img" in the root directory of the sdcard? Won't work if the file is anywhere else.
Note 3 4.4.2
Does it work on note 3 with 4.4.2??
SAMERKAD said:
Does it work on note 3 with 4.4.2??
Click to expand...
Click to collapse
Nope, check your devices fora for compatible recoveries.
Bastaerd said:
Nope, check your devices fora for compatible recoveries.
Click to expand...
Click to collapse
can i bring back backed up data with other recovery?
SAMERKAD said:
can i bring back backed up data with other recovery?
Click to expand...
Click to collapse
You should be able to do so. Anyways, this isn't the recovery for your device.
Bastaerd said:
You should be able to do so. Anyways, this isn't the recovery for your device.
Click to expand...
Click to collapse
yeah i know, but i had it on 4.3 and backed up data via TWRP
now im on 4.4.2 with CWM Recovery...
want to restore my System data
Thankss
What bootloader is this compatible with? Does it work with the TF300T Bootloader? I am guessing not but someone from the Androwook thread might try it and that will not be good.
Seeing this is for kk support/ROMs, why would a wookie fastboot this?
Thank you Voyager for the ongoing support for the prime!
Sent from my VS980 4G using Tapatalk
Hi devs,
I've started to port CM11 4.4 to my beloved Original Padfone (A66).
The first step was to compile the kernel sources that ASUS made available (Kernel 3.4), which as far as I understand will work with KitKat.
Am I correct to assume this?
Also, if the kernel compiled correctly what will be the next steps to test it (flash) in my device? The bootloader is unlocked, but I'm still with the original recovery. I think I will have to flash CWM or simmilar, right?
Thanks!
rafatz said:
Hi devs,
I've started to port CM11 4.4 to my beloved Original Padfone (A66).
The first step was to compile the kernel sources that ASUS made available (Kernel 3.4), which as far as I understand will work with KitKat.
Am I correct to assume this?
Also, if the kernel compiled correctly what will be the next steps to test it (flash) in my device? The bootloader is unlocked, but I'm still with the original recovery. I think I will have to flash CWM or simmilar, right?
Thanks!
Click to expand...
Click to collapse
The 3.4 kernel should work with KitKat. In order to properly test any CM11 builds you'll have to compile Clockworkmod Recovery for your device first by pulling your stock recovery.img and then compiling Clockworkmod Recovery using that. Additionally to test your kernel the best way is to take the zimage that's produced from compiling the kernel and make a boot.img out of it and boot it using fastboot. Let me know if you still have questions I'll be happy to answer them.
Sent from my SCH-I535 using XDA Premium 4 mobile app
shimp208 said:
The 3.4 kernel should work with KitKat. In order to properly test any CM11 builds you'll have to compile Clockworkmod Recovery for your device first by pulling your stock recovery.img and then compiling Clockworkmod Recovery using that. Additionally to test your kernel the best way is to take the zimage that's produced from compiling the kernel and make a boot.img out of it and boot it using fastboot. Let me know if you still have questions I'll be happy to answer them.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've follow the XDA University guide for building CWM, at http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
But the second step is failing:
Step 2 : Now that the otatools are ready, we need to get a dump of our current boot.img. To do this, use ‘adb shell’ and launch this command
“ dump_image boot /sdcard/boot.img “
This command do not exist in my phone.
Do you have any tip on this?
Thanks in advance!
rafatz said:
I've follow the XDA University guide for building CWM, at http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
But the second step is failing:
Step 2 : Now that the otatools are ready, we need to get a dump of our current boot.img. To do this, use ‘adb shell’ and launch this command
“ dump_image boot /sdcard/boot.img “
This command do not exist in my phone.
Do you have any tip on this?
Thanks in advance!
Click to expand...
Click to collapse
You have a couple of options of obtaining your stock recovery image (It's better to use your stock recovery.img rather then boot.img when compiling recovery as the recovery.img has more information in it that will make process of building an actual working recovery image easier) the easiest way is to boot into stock recovery, wipe cache in recovery, then reboot the phone. Then from adb run the following command:
Code:
cat /cache/recovery/last_log
This should give you an output, if you read the logfile you will see that one of the partition blocks is called /recovery. Record the name of the recovery partition block and then run the following command:
Code:
su
cat /dev/block/{name=of-recovery-partition-block} > /mnt/sdcard/recovery.img
This will dump a copy of your stock recovery.img to your internal storage. That you can then use to continue in the CWMR compiling process. By all means if you still have questions let me know I'm here to help.
shimp208 said:
You have a couple of options of obtaining your stock recovery image (It's better to use your stock recovery.img rather then boot.img when compiling recovery as the recovery.img has more information in it that will make process of building an actual working recovery image easier) the easiest way is to boot into stock recovery, wipe cache in recovery, then reboot the phone. Then from adb run the following command:
Code:
cat /cache/recovery/last_log
This should give you an output, if you read the logfile you will see that one of the partition blocks is called /recovery. Record the name of the recovery partition block and then run the following command:
Code:
su
cat /dev/block/{name=of-recovery-partition-block} > /mnt/sdcard/recovery.img
This will dump a copy of your stock recovery.img to your internal storage. That you can then use to continue in the CWMR compiling process. By all means if you still have questions let me know I'm here to help.
Click to expand...
Click to collapse
OK, I was able to successfully compile CWMR, but when booting to recovery I only get a blank screen and the devices reboots to Android. Is there a way to find any information on the error?
I know that TWRP works in padfone, but I'm not sure if they are compatible.
rafatz said:
OK, I was able to successfully compile CWMR, but when booting to recovery I only get a blank screen and the devices reboots to Android. Is there a way to find any information on the error?
I know that TWRP works in padfone, but I'm not sure if they are compatible.
Click to expand...
Click to collapse
It's possible that something is wrong with your recovery's graphics. Try taking the zimage of the kernel sources you compiled and swapping that zimage with the one in your CWMR recovery.img (Replace the zimage in your CWMR .img with the one you obtained when compiling the kernel source from ASUS). You could also try compiling TWRP and seeing that results in the same problem there are times on devices TWRP has been working before CWMR was working properly.
shimp208 said:
It's possible that something is wrong with your recovery's graphics. Try taking the zimage of the kernel sources you compiled and swapping that zimage with the one in your CWMR recovery.img (Replace the zimage in your CWMR .img with the one you obtained when compiling the kernel source from ASUS). You could also try compiling TWRP and seeing that results in the same problem there are times on devices TWRP has been working before CWMR was working properly.
Click to expand...
Click to collapse
No way Simply not working
But TWRP is 100%
I've tested the original recovery back and it is perfect as well.
Only CWMR is not working
I've even used the builder tool without success.
I've followed this guide:
http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html
and this
http://forum.xda-developers.com/showthread.php?t=1877807
Anyway, do you think that TWRP will work to flash my CM11 (if I ever build one)?
I think that the next problem is related on how to get the proprietary binaries from the phone to place in the vendor/asus/padfone folder.
rafatz said:
No way Simply not working
But TWRP is 100%
I've tested the original recovery back and it is perfect as well.
Only CWMR is not working
I've even used the builder tool without success.
I've followed this guide:
http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html
and this
http://forum.xda-developers.com/showthread.php?t=1877807
Anyway, do you think that TWRP will work to flash my CM11 (if I ever build one)?
I think that the next problem is related on how to get the proprietary binaries from the phone to place in the vendor/asus/padfone folder.
Click to expand...
Click to collapse
The CWMR builder tool has been not working for a while now. If you were able to compile the latest version of TWRP and you said it was working 100% then that will be fine to test your CM11 test builds. For getting the vendor files I would take a look at this guide on the Cyanogenmod wiki regarding porting and pull vendor files. A extract-files.sh script for a pre-existing device such as the Sprint Galaxy Nexus is a decent place to start for getting an idea how to setup extract-files.sh.
shimp208 said:
The CWMR builder tool has been not working for a while now. If you were able to compile the latest version of TWRP and you said it was working 100% then that will be fine to test your CM11 test builds. For getting the vendor files I would take a look at this guide on the Cyanogenmod wiki regarding porting and pull vendor files. A extract-files.sh script for a pre-existing device such as the Sprint Galaxy Nexus is a decent place to start for getting an idea how to setup extract-files.sh.
Click to expand...
Click to collapse
Yes, TWRP is 100% working
I've checked the extract scripts but my main problem is to identify in the filesystem which files I should pull.
Anyway, I tried to use the "chipset" method and "guess" based on the system information which files/drivers I would need, but that was not very helpfull (http://specdevice.com/showspec.php?id=0429-3576-ffff-ffffa98be330).
Well, I'll continue my studies on this
rafatz said:
Yes, TWRP is 100% working
I've checked the extract scripts but my main problem is to identify in the filesystem which files I should pull.
Anyway, I tried to use the "chipset" method and "guess" based on the system information which files/drivers I would need, but that was not very helpfull (http://specdevice.com/showspec.php?id=0429-3576-ffff-ffffa98be330).
Well, I'll continue my studies on this
Click to expand...
Click to collapse
Another suggestion would be to take a look in the /vendor folder on your device to extract the proprietary files and use that as a starting point to build off. Then you could try and compile a test build using that. Studying other devices device tree's is like you said another way to gain hints about what to do for your own device.
shimp208 said:
Another suggestion would be to take a look in the /vendor folder on your device to extract the proprietary files and use that as a starting point to build off. Then you could try and compile a test build using that. Studying other devices device tree's is like you said another way to gain hints about what to do for your own device.
Click to expand...
Click to collapse
HURRAY!
This saved the day
https://www.codeaurora.org/cgit/qui...tree/proprietary-blobs.txt?h=aosp-new/idea133
It is not for Padfone, but it is close enough.
rafatz said:
HURRAY!
This saved the day
https://www.codeaurora.org/cgit/qui...tree/proprietary-blobs.txt?h=aosp-new/idea133
It is not for Padfone, but it is close enough.
Click to expand...
Click to collapse
Awesome! Glad you could find a very similar device, best of luck on your CM11 builds :good:.
shimp208 said:
Awesome! Glad you could find a very similar device, best of luck on your CM11 builds :good:.
Click to expand...
Click to collapse
After a few attempts I was able to finish a build for CM 10.2, but it will not boot
I found that maybe I did something wrong with the fstab.padfone, using the new standards with 5 settings instead of only 3.
Well, in order to eliminate these kind of problems, I will make a CM10.1 building, which still uses the old standards.
rafatz said:
After a few attempts I was able to finish a build for CM 10.2, but it will not boot
I found that maybe I did something wrong with the fstab.padfone, using the new standards with 5 settings instead of only 3.
Well, in order to eliminate these kind of problems, I will make a CM10.1 building, which still uses the old standards.
Click to expand...
Click to collapse
Does it not boot at all or does it get to the boot-animation at least? Did you try pulling a log to see if you could get any information on the problem? But best of luck on your building :good:.
shimp208 said:
Does it not boot at all or does it get to the boot-animation at least? Did you try pulling a log to see if you could get any information on the problem? But best of luck on your building :good:.
Click to expand...
Click to collapse
SO far I couldn't even flash the ROM
TWRP is build with name A66, and the ROM is based on padfone.
I tried to change it, but the build fails
I think that I need to continue my efforts to make a working CWMR. So far the issue is the same, I can build and flash the recovery, but it simply do not enter the recovery. I get a flash on the screen and the phone automatically reboots to enter android.
I wonder if there's any way to get logs or more information from this error, so I can at least start to understand why CWMR is not booting.
fastboot boot recovery.img fails as well.
Bad day
rafatz said:
SO far I couldn't even flash the ROM
TWRP is build with name A66, and the ROM is based on padfone.
I tried to change it, but the build fails
I think that I need to continue my efforts to make a working CWMR. So far the issue is the same, I can build and flash the recovery, but it simply do not enter the recovery. I get a flash on the screen and the phone automatically reboots to enter android.
I wonder if there's any way to get logs or more information from this error, so I can at least start to understand why CWMR is not booting.
fastboot boot recovery.img fails as well.
Bad day
Click to expand...
Click to collapse
To clarify the ROM fails to flash in recovery what is the error it gives you when it fails to flash? To get ADB working on your CWMR build so you can pull log information add these lines in the correct place to your init.rc file in your recovery ramdisk:
Code:
service adbd /sbin/adbd recovery
disabled
socket adbd stream 660 system system
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
#write /sys/class/android_usb/android0/enable 1
#start adbd
setprop service.adb.root 1
# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
shimp208 said:
To clarify the ROM fails to flash in recovery what is the error it gives you when it fails to flash? To get ADB working on your CWMR build so you can pull log information add these lines in the correct place to your init.rc file in your recovery ramdisk:
Code:
service adbd /sbin/adbd recovery
disabled
socket adbd stream 660 system system
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
#write /sys/class/android_usb/android0/enable 1
#start adbd
setprop service.adb.root 1
# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
Click to expand...
Click to collapse
Thanks man! I was able to get a working CWMR.
The GITHUB I created for the device is at:
https://github.com/rafatzbr/android_device_asus_A66
I was able to build CM10.1 to Padfone, but it simply wont boot
stucked in the initial screen (not the bootanimation).
Any help is much appreciated.
Thanks!
** UPDATE **
Still stucked in boot screen
Any ideas?
rafatz said:
** UPDATE **
Still stucked in boot screen
Any ideas?
Click to expand...
Click to collapse
The ROM build? If it's still stuck pull a log file and post the upload of the log here.
shimp208 said:
The ROM build? If it's still stuck pull a log file and post the upload of the log here.
Click to expand...
Click to collapse
Thanks!
The problems is that the device is not in a bootloop. It is stucked in the first screen (on nexus devices it's the first google screen).
How I can get any logs from there, and which logs I would need?
Based on our official TWRP with some fixes and features
Changelog: 7-13
Add USB-OTG support
Brightness setting persists through reboots
EFS Backup and restore
Double tap to wake
Code:
Install:
In fastboot mode
fastboot flash recovery recovery.img
Download
Recovery flashable version here
Credits: Dees_Troy
dr87 said:
Based on our official TWRP with some fixes and features
Changelog: 7-13
Add USB-OTG support
Brightness setting persists through reboots
EFS Backup and restore
Double tap to wake
Mount and unmount issues *may* be fixed (I haven't been able to reproduce them)
Code:
Install:
In fastboot mode
fastboot flash recovery recovery.img
Download
Credits: Dees_Troy
Click to expand...
Click to collapse
Awesome job bro! Running like a champ!!
Sent from my One using XDA Premium 4 mobile app
Thanks a lot!
Now I can run Mahdi without problems!
thanks for this- but it's still not working- will i need to reflash madhi? i just fastbooted the recovery across and it boots into the recovery no worries and recognises all partitions but rom won't boot...
***edit*** it just booted up, about 5th attempt.. no boot animation though...ignore me...
Flashed recovery.img, bootet into recovery, no partitions..
Klarooo said:
Flashed recovery.img, bootet into recovery, no partitions..
Click to expand...
Click to collapse
Which rom were you running when you rebooted into recovery?
Stock, so CM11s.
mine still is not good. i treid to reboot to get it to hold the no hardware buttons. didn't reboot. tried about 10 times. eventually booted intot this new recovery and reflashed rom and booted it up. it's a bloody weird looking boot- no boot animation- made me think it was screwed again.
did you have to do anything to get it working again? Wipe entire device or just data partition?
Working good here, but I had no issues with the official build. I have an international version, 64GB OPO.
It's nice to see some additional features added, though.
Just helping out, packaged in a flashable zip for those with current CWM or TWRP recoveries, tested and working, enjoy everyone.
Flashed with the zip in the post above, worked flawlessly, was able to backup my EFS partition which is what I was looking to do. Thanks!
Chris123NT said:
Flashed with the zip in the post above, worked flawlessly, was able to backup my EFS partition which is what I was looking to do. Thanks!
Click to expand...
Click to collapse
Guys i wonder when you press efs restore is it
fastboot format modemst1 & st2
or
fastboot erase modemst1 & st2
or may be both? in that case in what order?
I flashed the one in OP, but the system does not see any partition ?
Can I flash 15th without bricking the phone
[EDIT] I tried a second time, and now it´s ok, partitions are there and backup is currently running
Any chance at adding F2FS support direct for this recovery for the ONE Plus?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Looks like the official .img version has been incremented to 2.7.1.1
More here: http://techerrata.com/browse/twrp2/bacon
A flashable zip for v2.7.1.1 would be nice.
Changelog? Hopefully they fixed those Partitions issues
2.7.1.1-Bacon Recovery Flashable zip
Mikey said:
2.7.1.1-Bacon Recovery Flashable zip
Click to expand...
Click to collapse
Question - now I ask this to see how you may do this and possibly help others from waiting for a zip. Now are you simply renaming the image file from TWRP to recovery.img and placing it inside an already created zip file for flashing. A zip file that of course was created for an earlier version of TWRP lets say
playya said:
Question - now I ask this to see how you may do this and possibly help others from waiting for a zip. Now are you simply renaming the image file from TWRP to recovery.img and placing it inside an already created zip file for flashing. A zip file that of course was created for an earlier version of TWRP lets say
Click to expand...
Click to collapse
Correct, easy huh
Delete the twrp.img......drag and drop the new img into the zip......dont uncompress the zip and compress it again.
http://forum.xda-developers.com/xpe.../recovery-twrp-3-0-0-touch-recovery-t3309938/
This is deprecated.
In this thread I'll share the .img files of the latest TWRP available for our device, so you can flash them with Rashr/PhilZ/Cyanogen recovery.
Disclaimer:
you are responsible for what you do. If your device stops working after you follow this guide, it's not my fault. However, as usual, if you do things in a correct way, you won't face any problems.
Requirements:
any ROM with any kernel
unlocked bootloader
Don't flash it if you have got a locked bootloader!
Features:
up-to-date source
flashable signed zip
f2fs support
Changelog:
TWRP 2.8.7.0_8
- other cleanups
- startup now is not slow! It just takes 3 - 4 seconds!
- Reboot bug is fixed - maybe
TWRP 2.8.7.0_7
- optimizations and cleanups
TWRP 2.8.7.0_6
- f2fs for /system is supported (this is for Temasek users)
TWRP 2.8.7.0_5
- f2fs support improved
- minor optimizations
- less overheating
TWRP 2.8.7.0_4
- attempt to fix issues with reboot option
TWRP 2.8.7.0_3
- signed flashable zip added
TWRP 2.8.7.0_2
- f2fs bugs fixed
- fixed overheating
How to install:
flash the zip through any recovery (even Cyanogen recovery!)
Download from Android File Host:
[url]https://www.androidfilehost.com/?fid=24052804347826443[/URL]
Stock FOTAKernel to remove any recovery (included this one): [url]http://forum.xda-developers.com/xperia-sp/general/stock-components-flashable-zips-t3184111[/URL]
Be sure to select the right variant of your device!
Thanks to:
@[NUT]
@antr34
@TechnoSparks
This work in miui v6
Thanks a lot for this quick update :thumbup:
Working fine on AICP's official nightlies with stock kernel.
The TITAN has landed. Hide your works from this critic! The official maintainer of the XSP Lollipop and M Hub.
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
pilger said:
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
Click to expand...
Click to collapse
I use it and i cant flash nothing
Guizão BR said:
I use it and i cant flash nothing
Click to expand...
Click to collapse
What is the output of the command? Does it throw you an error or anything?
@pilger i'm here, what to do next?
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
pilger said:
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
Click to expand...
Click to collapse
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
J73 said:
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
Click to expand...
Click to collapse
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
pilger said:
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
Click to expand...
Click to collapse
Thanks to you! All's well now, I'm so glad to have TWRP again thank you!
pilger said:
What is the output of the command? Does it throw you an error or anything?
Click to expand...
Click to collapse
Sorry i Forgot to edit the play, this have more time to flash
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Tomoms said:
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Click to expand...
Click to collapse
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
kunal9007 said:
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Tomoms said:
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Click to expand...
Click to collapse
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
kunal9007 said:
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Well, strange. f2fs volumes couldn't be mounted.
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Adrian DC said:
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Click to expand...
Click to collapse
just realized that I didn't had tangerine installed i was on first build of official cm and then before flashing radium i formated to f2fs
Sent from my XT1033 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
and i flashed tangerine after atleast 1 day use of stock kernel
Sent from my XT1033 using Tapatalk
Bootloop of Death (BLOD) Workaround AnyKernel3 zip for Nexus 6P
osm0sis said:
Guys.. bad news.. my Nexus 5X just got hit with the BLOD.
Good news for everyone is I spent a bit of time tonight to first patch TWRP 3.2.1-0-FBE (File-Based Encryption support) image to be 4core, then made an AnyKernel2 zip which will patch the existing boot and recovery partitions on-device to add all the 4core fixes from @XCnathan32.
Should work over any ROM, any custom kernel, recovery, etc., can be added in queue after ROM, root zip + custom kernel to patch it from TWRP or FlashFire (so good for OTAs), and simplifies the initial process greatly since you can now fastboot boot any 4core recovery.img and then adb sideload my AK3 zip to fix the likely newer recovery you already had on your device.
Click to expand...
Click to collapse
Original thread posts: Nexus 5X, Nexus 6P
Now updated to an AnyKernel3 zip to support the SAR (system-as-root) and 2SI (2 stage init) ROMs that have popped up for Pie and Android 10+!
General Information
If you've found this thread then I'm sure you probably already know what the Bootloop of Death is - separation of the performance (perf) CPU cores - and that the only way to recover from it is to unlock your bootloader and patch to disable the faulty cluster. If you have not enabled unlocking your bootloader yet, the known methods to get it to boot long enough so you can go to System, then Developer Options and toggle "OEM unlocking" are:
super cooling the device in a freezer in a ziplock bag to keep out moisture,
super heating around the camera, and
letting the battery run all the way down before trying to boot.
For further details on these methods check out the original threads by @XCnathan32, linked in the "Thanks" section.
Some important notes before going any further:
Freezing at the Google logo likely points to it being perf cluster separation, but this could also be caused by other components separating.
Freezing at the boot animation suggests ROM/ROM data problem or could also potentially be a BLOD with other components now beginning to separate and that's what people have reported when the 4core mods suddenly stop working with no configuration changes - if you've tried the default boot.img for your ROM, patched with the BLOD AK3 and it still doesn't work, sorry but your device is a brick.
If no 4core recovery boots for you then you definitely have more components than just the performance cores separated, sorry but your device is a brick.
I haven't seen anyone say their devices only worked using a "1core" modification who had tried a proper 4core patched setup; 4core makes sense because it's the separate perf cores cluster becoming unsoldered, but if the 4 low power cores cluster also starts to come unsoldered logically not even a single core would work.. I think that's where the "Green Screen Of Death" comes into it.
DemiGod = Green Screen Of Death; unfortunately this (more components separating given more time - maybe the flash memory chip?) is why many call the 4core workaround only temporary.. there's not much that can be done after that from what I've read.
EX Kernel does not support FBE on these devices because the EX zip patches the fstab forcefdeorfbe flag to encryptable.
Android 10 does not appear to support FBE on these devices but the 4core FBE TWRP build can be used to BLOD patch the latest TWRP (see instructions in next post).
On Oreo, I was personally on stock ROM still, FBE enabled, rooted with SuperSU v2.82 SR5 + suhide and the latest Franco Kernel on my 5X. Then I bumped up the min freq on the low perf cores and it's working great - totally fine for general use, just anything creating a bit of heat like games maxing the low power cores for awhile, or charging, will make it pretty painfully laggy and risk further solder deterioration.
Even though SuperSU development is ostensibly dead, I still strongly recommend it on BLOD-affected devices using stock ROM for reasons I'll explain below.
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Step-By-Step Installation Instructions
Any quoted commands should be entered without quotes
1) Download and unzip platform-tools for your PC from https://developer.android.com/studio/releases/platform-tools.html
2) Navigate to https://androidfilehost.com/?w=files&flid=312881 (also mirrored below) and download N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip to your platform-tools folder as well as
2a) twrp-3.2.1-0-fbe-4core-bullhead.img (Nexus 5X), or2b) twrp-3.2.1-0-fbe-4core-angler.img (Nexus 6P)3) Hold Shift + right-click on your platform-tools folder and
3a) Open a command window here (Windows <10), or3b) Open a PowerShell window here, then enter "cmd" at the Windows PowerShell prompt (Windows 10+)4) Reboot your phone to bootloader and connect it to your PC with a USB cable
5) Enter "fastboot flash recovery twrp-3.2.1-0-fbe-4core-angler.img" into the cmd prompt
6) Reboot your phone to recovery and tap Advanced, then ADB Sideload
7) Enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip" into the cmd prompt
8) Reboot and cross your fingers that it works
For information how to seamlessly update to stock and custom ROM OTAs, see the following post
Source Code: https://github.com/osm0sis/N5X-6P-BLOD-Workaround-Injector
Status: No Longer Updated
Thanks:
- @XCnathan32 for researching and developing the 4core workarounds for both the Nexus 5X and Nexus 6P
- chetgurevitch (GitHub) for the original FBE supporting TWRP builds
- @Aukaminator for the original step-by-step write-up
Update Flashing Instructions
Keep N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip on your device sdcard, henceforth referred to as BLOD AK3 zip
The correct manual order for a clean flash is: ROM -> root -> custom kernel -> BLOD AK3
Always flash the BLOD AK3 zip last!
Reflashing the BLOD AK3 zip will likely be required after anything that could modify the boot.img or recovery.img, including (but not limited to): ROM updates, custom kernel updates, custom recovery updates.
ROMs:
On custom ROMs with built-in Flash After Update (i.e. OmniROM-based), place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/OpenDelta/FlashAfterUpdate/ ensuring the BLOD AK3 is last in the directory listing so that they will be flashed after each update.
On custom ROMs that do not have built-in Flash After Update (i.e. LineageOS-based), you may add my FlashAfterUpdate addon.d script to /system/addon.d/ and then place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/FlashAfterUpdate/ ensuring the BLOD AK3 is last for the same effect: flashed after every OTA.
On stock ROM rooted with SuperSU (SuperSU v2.82-SR5 recommended) instead of tapping "Reboot & Install" once the OTA is downloaded you should use @Chainfire's excellent FlashFire app to queue the OTA from /data/ota_package/update_s.zip then queue the SuperSU zip, custom kernel and BLOD AK3 zip, ensuring the BLOD AK3 is last. This is how I have mine set up, since this is by far the most seamless. Be sure to disable EverRoot since SuperSU v2.82-SR5 is newer than the SuperSU included in FlashFire.
On stock ROM rooted with Magisk you must uninstall Magisk from within Magisk Manager to restore your stock boot.img, reboot the ROM to restore your stock recovery partition, tap "Reboot & Install" once the OTA is downloaded, then go through the steps above to flash the 4core TWRP and BLOD AK3 zip again. I definitely recommend SuperSU on this device to avoid the hassle of unrooting and/or messing with factory images.
Kernels:
Custom kernels can be flashed from an app like Franco Kernel Manager & Updater, which can be set to flash without reboot for Franco Kernel updates, or "Flash only" can be chosen in the manual flasher. The FK app supports all types of AnyKernel3 zip so the BLOD AK3 zip may then be flashed after the custom kernel zip to repatch the new kernel's ramdisk.
For other kernel managers that don't support AK3 zips, simply reboot to recovery and flash the BLOD AK3 zip from there to repatch before attempting to boot the ROM again. Also see above under "stock ROM rooted with SuperSU", since FlashFire also works perfectly for this use-case, queuing the custom kernel zip and then the BLOD AK3 zip, with FlashFire's EverRoot option disabled since the device is already rooted.
Recoveries:
Download the updated custom recovery .img and, without flashing it, reboot to recovery, use TWRP's flash image feature to flash the new recovery.img, then without rebooting immediately flash the BLOD AK3 zip to patch it. You can then dump/backup the recovery partition if you want it as a recovery.img. Custom recovery updates can also be done from FlashFire, queuing the BLOD AK3 zip afterward, but the "Preserve recovery" feature must be disabled.
If you prefer to stay on stock recovery for some reason, you can still use TWRP to do the above without flashing TWRP to the device by using "fastboot boot twrp-3.2.1-0-fbe-4core-angler.img".
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Changelog
2018-01-15 - Original post in other BLOD threads.
2018-07-21 - Update AK2 Core+Backend files to latest, add searching of all init.*.rc files for problematic cpuset commands which were popularized by Franco Kernel and are now used by multiple custom kernels. (6758 downloads)
2019-10-30 - Update to AnyKernel3, add support for SAR and 2SI Treblized ROMs. (1720 downloads)
2020-01-16 - Update AK3 Core+Backend files to latest to fix AVBv1 signing in recovery on Android 10, update boot_signer-dexed.jar. (570 downloads)
2020-02-17 - Update AK3 Core+Backend files to latest to fix SAR mount support in fragmented TWRP and Lineage 16+17 Recovery. (1412 downloads)
2020-05-25 - Update AK3 Core+Backend files to latest to improve SAR mount support in Lineage 17 Recovery and AVBv1 signing. (1789 downloads)
2021-07-21 - Update AK3 Core+Backend files to latest to support Lineage 18.1 recovery and Android 11 ROMs.
Good luck and enjoy!
Glad to see this exclusive thread... just came here to report that I've been using your fix since Jan this year ( https://forum.xda-developers.com/ne...-6p-bootloop-death-blod-t3640279/post75220708 ) and yeah my phone's still alive and running fine. Kudos to your work... Great job you did there... saving hundreds of bucks... Really appreciated!
Thanks again.
Hi osmosis,
I have done everything you said and I got stuck in step 7, when I enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip", the return message is:
adb: sideload connection failed: closed
adb: trying pre-Kitkat sideload method...
adb: pre-Kitkat sideload connection failed: closed
I tried swiping where it says "Swipe to Start Sideload" and then doing step 7, but when I swipe my computer stops recognizing my device.
Thank you
SH15 said:
Hi osmosis,
I have done everything you said and I got stuck in step 7, when I enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip", the return message is:
adb: sideload connection failed: closed
adb: trying pre-Kitkat sideload method...
adb: pre-Kitkat sideload connection failed: closed
I tried swiping where it says "Swipe to Start Sideload" and then doing step 7, but when I swipe my computer stops recognizing my device.
Thank you
Click to expand...
Click to collapse
You need to let your computer install drivers for adb sideload. If your computer is having trouble with that for some reason and the recovery otherwise works then just adb push the zip to /sdcard and flash it from on the device instead of sideloading. :good:
osm0sis said:
You need to let your computer install drivers for adb sideload. If your computer is having trouble with that for some reason and the recovery otherwise works then just adb push the zip to /sdcard and flash it from on the device instead of sideloading. :good:
Click to expand...
Click to collapse
Thank you for answering. I had to adb push the file to /sdcard and then I flashed it using TWRP, however even after installing the file the phone is still stuck on the Google logo screen when booting up. I don't know what to do.
Thank you
SH15 said:
Thank you for answering. I had to adb push the file to /sdcard and then I flashed it using TWRP, however even after installing the file the phone is still stuck on the Google logo screen when booting up. I don't know what to do.
Thank you
Click to expand...
Click to collapse
That's weird. The fact that the recovery worked suggests the 4core fix works for you. Maybe flash the lastest factory image then the BLOD AK2 zip.
Can this be flashed on top of the Oreo img from the previous thread? Is this one for Oreo?
I've applied the previous Oreo one and my phone's past the Google logo loop and is now in the loading animation for Lineage OS.
FlameSting said:
Can this be flashed on top of the Oreo img from the previous thread? Is this one for Oreo?
I've applied the previous Oreo one and my phone's past the Google logo loop and is now in the loading animation for Lineage OS.
Click to expand...
Click to collapse
Please read the OP. It works over any ROM, any custom kernel, any recovery.
osm0sis said:
That's weird. The fact that the recovery worked suggests the 4core fix works for you. Maybe flash the lastest factory image then the BLOD AK2 zip.
Click to expand...
Click to collapse
Thank you very much! I flashed the newest factory image for Oreo and then re-flashed the BLOD AK2 zip and it worked. Thank you for your help! :good:
Idk if I'm in the right place.
I recently replaced my battery (2nd time this week, first one was bad) and everything was working fine. Then my phone started randomly rebooting. Googled it and apparently it's one of the first signs of BLOD. Followed this and the phone stopped shutting down randomly. Now the phone only works if plugged into a power source. Idk if I did something wrong or the battery is trash (even though it was working fine all day)
I'd appreciate an guidance [emoji24]
Sent from my [device_name] using XDA-Developers Legacy app
This saved my day! Thanks everyone! Got my 6P booted up again... and it's not even rooted
I want just only to thanks @osm0sis and it's genial solution!
Thanlks i recover my phone and saved a lot of money.
I understand it could be a temporary solution but thanks!!!
gabriele
After I flashed twrp and try to go to Recovery there is a message "Your device software cannot be checked for corruption. Please lock the bootloader." And after that it goes back to bootlloop. Any idea what to do next? Thanks
godd said:
After I flashed twrp and try to go to Recovery there is a message "Your device software cannot be checked for corruption. Please lock the bootloader." And after that it goes back to bootlloop. Any idea what to do next? Thanks
Click to expand...
Click to collapse
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
I had my phone hang on the google logo a couple times, but rebooting it fixed it. Is this an early sign of this problem? Just replaced battery and so far it seems fine.
osm0sis said:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
Click to expand...
Click to collapse
I am in this same boat... RIP N6P, this is my 2nd N6P Google replaced the first one due to the BLOD and now the replacement is dead.
Thanks for all the efforts and help.
osm0sis said:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
Click to expand...
Click to collapse
It seems the basketbuild site is down. Any chance you could throw the modded twrp for oreo and the 4core fix up here?
osm0sis said:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
Click to expand...
Click to collapse
Same as the guy above. Sites down need mirrors or something?
jbjcurly said:
It seems the basketbuild site is down. Any chance you could throw the modded twrp for oreo and the 4core fix up here?
Click to expand...
Click to collapse
CavyS said:
Same as the guy above. Sites down need mirrors or something?
Click to expand...
Click to collapse
Mirrored in the OP. Thanks!
Edit: And BasketBuild is also back! :good: