Related
Hello,
The home button of my device (Magic) does not work at all. So, I can not confirm to install the CyanogenMod in the recovery screen.
Am I able to install the ROM via fastboot? or does anybody has another suggestion?
Regards,
Omer
Yes, you can flash ROMs via fastboot, but you'll need a system and data img for the ROM, and I'm not aware of a method to package them up based on an update.zip.
I checked inside the archive and saw the images but there also some scripts need to run. That's why; I couldn't dare to flash.
Is there a method I can follow?
osaatcioglu said:
I checked inside the archive and saw the images but there also some scripts need to run. That's why; I couldn't dare to flash.
Is there a method I can follow?
Click to expand...
Click to collapse
You don't need any scripts, just a system and data to flash.
fastboot flash data.img
fastboot flash system.img
You wont find these images inside the update.zip, the sys/data-imgs need to be created from the sys/data folders. Best bet is to ask someone to perform a nandroid backup, backup the imgs, wipe, flash cyan, send you those imgs, restore their old imgs.
Thank you. But, the someone's device should be identical to magic, right? I have dream also. So, I can use the nandroid backups of it. However; I don't think this would be possible. what do you think?
osaatcioglu said:
Thank you. But, the someone's device should be identical to magic, right? I have dream also. So, I can use the nandroid backups of it. However; I don't think this would be possible. what do you think?
Click to expand...
Click to collapse
I'm really not sure, but I think the device would need to have the same size data and system partitions as the Magic, which the Dream doesn't.
Use mkyaffs2 to make the System and Data .img Files
What operating system do you have because if you have linux or a linux virtual machine you could extract the update zip and use the mkyaffs2 utility code.google.com/p/yaffs2utils/ to make the system and data images.
There is also a much easier program called yaffey http://forum.xda-developers.com/showthread.php?t=1645412 but it is windows only
So this thread is kind of old, but I stumbled upon it looking for stuff.
Im using a google galaxy nexus and have a strange issue where I cant connect it via usb when in a different state than fastboot mode. I replaced the usb port (flex cable) already, but it doesnt help (if you got any advice on that, please tell me)
What I actually want to say is that I can't install cyanogen from recovery because I can't connect my phone when in recovery, but I can flash firmware normally via bootloader, I tried that already, so how exactly do I get the images for cyanogen? Because I don't fully grasp it yet.
Port recovery to any Device, snapdragon, mediatech doesn't matter
Hi guys...
Once again i am back with an Extreme guide...
Its about porting Recovery if you don't have source or if you like to use your own thing...
Ok lets start......
Do it with your own risk, I am not responsible for anything happens to your mobile, friends, family and etc
Click to expand...
Click to collapse
Requirements:
1. Android Kitchen or Android image kitchen (Search on xda or
google)
2.NOTEPAD++ (Search on google)
3. Flash tool (flashify, rashr etc)
4. Cygwin ( if you are using Windows)
5. Recoveries that you want to port, must be from same structured chip set device, and same resulotion
Tips: Search on Google on how to set up android kitchen with cygwin
Step:1
Frist take your stock boot.img, stock recovery.img and
any other recovery like CWM or CTR (Without
TWRP)
Tips: If you don't know how to get a dump of boot.IMG or recovery.IMG, Google is there to help you! You can also use Diskinfo to get partition info, download it from play
Now put them in safe folder and unpack boot.img in a
new folder, then unpack Stock recovery in another
folder and unpack your cwm or CTR recovery in
Another folder.......
All done!!
Tips: search Google how to unpack .IMG with android kitchen or android image kitchen
Click to expand...
Click to collapse
Step:2
Now go to your unpacked boot.img and then go to "ramdisk" folder then copy these files and paste it
to your recovery (whitch you want to port)
1.meta_init.modem.rc
2.meta_init.project.rc
3.meta_init.rc
Done! :3
Click to expand...
Click to collapse
Step 3:
Now go to your unpacked stock recovery and copy "(#Kernel)" and paste it to your unpacked recovery (Which you want to port).Then again go to unpacked stock recovery>ramdisk and copy these files and paste them in your unpacked recovery>ramdisk (which you want to
port) and replace them all...
1.fstab
2.ueventd.rc
3.ueventd.goldfish.rc.
Done!
Click to expand...
Click to collapse
Step 4:
Now go to your stock unpacked CWM or CTR and go to
ramdisk/etc and copy ( recovery.fstab ) and paste
it to you unpacked recovery (which you want to
port) /ramdisk/etc and replace......
Done!Now go to your unpacked recovery (whitch
you want to port) then go to ramdisk and open
default.prop and ask also open the default.prop. compare them, change the values of port recovery according to stock recovery.
All Done!
Click to expand...
Click to collapse
Finel step :
Repack the ported cwm, take it to your phone and open any flash tools and flash your new recovery!!
Click to expand...
Click to collapse
N.B.--> This method will not work in TWRP porting beacuse porting TWRP is different...
Sometimes your new recovery may not work...if it does not work then try again with new recoveries from different device or redo the whole thing
I hope this post was helpfull and if you
successed to port your new recovery then dont
forget to give me some credits
if you like this post then click on :good: button... It may increase the rate of
giving new guides... :highfive:
Hi, I am trying to do a CWM recovery for Amazon fire phone which is a Snapdragon 800 - unfortunately i cannot find any custom recoveries which have the amazon fire phones resolution of 1280 x 720 can you advise if there is a workaround for this situation?
Hey there, if you are porting cwm, the resolution isn't gonna be a problem. Find same structured device and you would be good to go.
Edit: the fonts will maybe look smaller.
But if you are porting CTR recovery the resolution would be a problem, it will cause you touch problem in recovery
Thanks. One problem right at the first hurdle is in step 2
i do not have these files in my boot ramdisk folder
1.meta_init.modem.rc
2.meta_init.project.rc
3.meta_init.rc
Attached is a screenshot of what i have in mine?!?
Can I get a screenshot of the unpacked recovery ( that you want to port)? I want to compare these files
The screenshot of the unpacked Recovery's ramdisk folder actually
Sure, attached. This is my recovery from my Amazon phone and also the recovery for a nexus 5 which uses the same processor
Init.rc, ueventd.rc, replace these two files
Snapdragon device's boot and recovery structure is different, I thing I have to do the tutorial again with snapdragon details
BTW is there any other version of cwm available for your device? You can take a look inside that recovery for more info. And if your device has source, I recommend that building it from source would be best for you
Hi, I actually just built from source but nothing happens when phone should go into recovery. Just stays on the Amazon screen. I then flash the stock recovery back and it works fine. I'm pretty sure that i compiled it correctly as i got no errors used CM11 as source. (Attached if it helps)
To be honest it was a shot in the dark anyway as the phones bootloader is locked and i was trying with flashify.apk
Have you tried grabbing a logcat after rebooting from recovery?
Thats my next step
And what does the logcat says?
Please help.
I have got an android device with Broadcom Processor with android 4.4.2. I had tried to learn using Ubuntu and tried to build recovery from source. But, it seems a clumsy path and hard to understand. I could not finish syncing repo and retired from my trial a month ago. Can I use this tutorial to port recovery to my device? How can I know which CWM for an android can be ported to mine?
bro this is not working for snapdragon devices. as i am not getting meta files into its recovery not even in the ported one.
I can't understand the which recovery is which, like in Step 3 you said Stock recovery and unpacked recovery (Which you want to port) where i guess stock is the original recovery and unpacked is CWM/CTR.
But on Step 4 you said:
"go to your stock unpacked CWM or CTR and go to
ramdisk/etc and copy ( recovery.fstab ) and paste
it to you unpacked recovery (which you want to
port) /ramdisk/etc and replace."
so stock unpacked CWM is CWM but which one is he unpacked recovery now?
bro i have micromax a108 with mt6582m chipset and i want to port ctr for my device but i am not getting and recovery developed for mt6582m devices
Please write a new guide for Qcom Chipset !
Sent from my redmi note 4 using xda Forums PRO
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
WARNING!!! Be careful what you do here. One mistake and the device is soft-bricked. I take no responsibility for bricked devices, lost warranty or even OTAs not working!! Booting and/or flashing files from this post is on your own risk.
Requirements
Unlocked bootloader
Lenovo Tab 4 Plus with and without LTE and both 8 and 10 inch versions (TB-X704L/F, TB-8704X/F) are supported
Known Issues
WARNING! Our device uses dm-verity (verified boot). The system partition should remain read-only. Otherwise a bootloop will occur. You can flash SuperSU to resolve this but OTA's are no longer possible! You have to restore a factory image or clean system backup to receive OTAs
Download
TWRP for TB-8704X/F (8 inch plus): AndroidFileHost
TWRP for TB-8704V (8 inch plus Verizon): AndroidFileHost (provided by @3m1k)
TWRP for TB-X704L/F (10.1 inch plus): AndroidFileHost
TWRP for TB-8504X/F (8 inch): AndroidFileHost (touch input may only work after connecting mouse)
TWRP for TB-X304L/F (10.1 inch): AndroidFileHost
Instructions
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Setup the tablet again and reboot again to the bootloader
Then run
Code:
fastboot boot twrp-3.2.3-0-<your-filename>.img
to temporarily boot into TWRP. You can also flash if you are sure
Select to keep system read only when TWRP starts to avoid modification which will make OTAs impossible
Backup at least system and boot partitions. Choose "System Image" for the system partition backup. Keep this backup for OTA updates.
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Writable System Partition
Some mods and root apps require write access to the system partition. By default the system partition is read-only to prevent any modification. Please note that if your system partition is modified in any way it needs to be restored to its original state before a system update (OTA) can be applied.
@dywersant has created a Magisk module here to achieve write access
@KreAch3R has updated the Magisk module to the latest version here
System Updates (OTA)
In order to successfully apply Lenovo system updates after root you have to restore the original boot, recovery (if you flashed TWRP) and system partitions from your current installed version (e.g. S000037) for your variant of the tablet. This will NOT delete your apps and data but will unroot. Note that OTAs are block based and always check the contents of most of the partitions. This means that all of these partitions (except your data) have to be original and have to be on the exact same version (e.g. S000037) for the update to succeed.
Credits
@wonderfulme - for testing the 8" version
@Teddy01 - for testing the 10" version
@3m1k - for providing the 8" Verizon version
TeamWin
Source
TWRP Manifest: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-7.1
Device Tree (TB-8704X): https://github.com/Matshias/twrp_android_device_tb_8704x/tree/android-7.1
Device Tree (TB-8704V): https://github.com/3m1k/twrp_android_device_tb_8704v
Device Tree (TB-X704L): https://github.com/Matshias/twrp_android_device_tb_x704l/tree/android-7.1
Device Tree (TB-8504X): https://github.com/Matshias/twrp_android_device_tb_8504x/tree/android-7.1
Device Tree (TB-X304L): https://github.com/Matshias/twrp_android_device_tb_x304l/tree/android-7.1
Changelog
v3:
Update to TWRP 3.2.3-0
v2:
Update to TWRP 3.2.1-0
v1:
Initial Release
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): no longer needed. Final version in first post
matshias said:
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): twrp-3.1.1-0-tb_x304l_testing1.img
Click to expand...
Click to collapse
I can test the 8 inch tomorrow. Thanks for building this btw.
---------- Post added at 02:01 PM ---------- Previous post was at 01:58 PM ----------
Wait, these builds are for the Plus variants only? They will not work with ZA2B0009US, correct? :\
w0rdie said:
Wait, these builds are for the Plus variants only? They will not work with ZA2B0009US, correct? :\
Click to expand...
Click to collapse
ZA2B0009US = TB-8504F so you can take the build for Tab 4 8 (TB-8504X/F) and hopefully it will work out of the box.
matshias said:
ZA2B0009US = TB-8504F so you can take the build for Tab 4 8 (TB-8504X/F) and hopefully it will work out of the box.
Click to expand...
Click to collapse
Just landed there myself. I'll give it a go tomorrow morning and update this post.
Thanks again.
I have tested on X304L work perfectly.
Only one thing when i'm on power via usb TWRP still turning off screen in 2min and seems that all operations are put in wait state until screen turned on again.
:good:
boza12 said:
I have tested on X304L work perfectly.
Only one thing when i'm on power via usb TWRP still turning off screen in 2min and seems that all operations are put in wait state until screen turned on again.
:good:
Click to expand...
Click to collapse
Thanks a lot for testing. I moved the TWRP to the first post.
In the TWRP settings you can switch off whether the screen goes off or not. Are you sure TWRP halts processing while the screen is off?
matshias said:
Thanks a lot for testing. I moved the TWRP to the first post.
In the TWRP settings you can switch off whether the screen goes off or not. Are you sure TWRP halts processing while the screen is off?
Click to expand...
Click to collapse
Yes It does - it happened to me last night also.
EggZenBeanz said:
Yes It does - it happened to me last night also.
Click to expand...
Click to collapse
Can you send me the logs (dmesg output and /tmp/recovery.log) after it happens?
Yes sure.
Is anyone able to make available a system image. I deleted my original back up after the update then messed the root up. I now getting setup app crash and can't get passed setup
EggZenBeanz said:
Yes sure.
Is anyone able to make available a system image. I deleted my original back up after the update then messed the root up. I now getting setup app crash and can't get passed setup
Click to expand...
Click to collapse
Download the factory image for your tablet from the Russian Lenovo forum (lenovo-forums.ru) . In there you will find a fragmented system image. You have to puzzle it together with a script according to XML file in the Image directory. If you wanna flash via fastboot you will have to convert it with img2simg to sparse format. You can also use dd command line TWRP with the raw image file. If you tell me your exact model number I can also upload what you need.
matshias said:
Download the factory image for your tablet from the Russian Lenovo forum (lenovo-forums.ru) . In there you will find a fragmented system image. You have to puzzle it together with a script according to XML file in the Image directory. If you wanna flash via fastboot you will have to convert it with img2simg to sparse format. You can also use dd command line TWRP with the raw image file. If you tell me your exact model number I can also upload what you need.
Click to expand...
Click to collapse
Thanks! That would be awesome if you could. I think I may brick it if I do what you suggest! My model is
TB-X704L/F (10.1 inch plus) could you include the boot image too?
EggZenBeanz said:
Thanks! That would be awesome if you could. I think I may brick it if I do what you suggest! My model is
TB-X704L/F (10.1 inch plus) could you include the boot image too?
Click to expand...
Click to collapse
Is it TB-X704L vor F? This is an important difference.
The boot image you can find as can be flashed in the factory image. You can start with this. When I have time I'll prepare the system image. Not sure when that is though.
matshias said:
Is it TB-X704L vor F? This is an important difference.
The boot image you can find as can be flashed in the factory image. You can start with this. When I have time I'll prepare the system image. Not sure when that is though.
Click to expand...
Click to collapse
Thanks!!!! Confirmed TB-X704F
matshias said:
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): twrp-3.1.1-0-tb_x304l_testing1.img
Click to expand...
Click to collapse
The twrp-3.1.1-0-tb_8504x_testing1.img flashes and boots fine but there is no touch input.
Logs: https://www.dropbox.com/s/vo2dvi4frpsf9hf/logs.zip?dl=0
(I connected a mouse via USB and got SU flashed)
On my Tab4 8 the touch is also not working with this image.
I think the following lines from dmesg.log are showing, that the touch driver ist not loading:
<4>[ 1.323216] [HXTP] Himax common touch panel driver init
<4>[ 1.323221] [HXTP][ERROR] himax_common_init failed, compare_tp_id = 1
w0rdie said:
The twrp-3.1.1-0-tb_8504x_testing1.img flashes and boots fine but there is no touch input.
Logs: https://www.dropbox.com/s/vo2dvi4frpsf9hf/logs.zip?dl=0
(I connected a mouse via USB and got SU flashed)
Click to expand...
Click to collapse
Do you have the TB-8504X or TB-8504F? Very strange that the touch driver won't load. if you have the F variant then maybe it has a slightly different hardware in which case I'll have to compile separate TWRP for this variant. Can you extract me your stock boot or recovery image and send it to me? I'd then build TWRP with the kernel from your tablet and we'll see what happens
EggZenBeanz said:
Thanks!!!! Confirmed TB-X704F
Click to expand...
Click to collapse
Here is the system image in sparse format for fastboot flashing: MEGA
matshias said:
Here is the system image in sparse format for fastboot flashing: MEGA
Click to expand...
Click to collapse
Amazing, thank you so much. All worked and back to normal. I'll root again with the screen off and provide logs
Sorry if this is off topic, but is there a way to convert the Chinese versions of the Tab 4 / Plus to the Global rom? I'm thinking of getting one from China when I'm there but the lack of Google Play support is a major deal breaker.
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
johnnyphive said:
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
Click to expand...
Click to collapse
Well, for starters do NOT take the OTA. It will either fail or boot loop your phone. Due to the fact you have a modified boot.img you will need to update manually using fastboot with the full image. Re-apply the modified kernel after you finish updating the partitions, but BEFORE booting the first time. You can follow most guides on how to manually update a full image using fastboot, just add the step of flashing the modified kernel before booting.
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
johnnyphive said:
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
Click to expand...
Click to collapse
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
v12xke said:
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
Click to expand...
Click to collapse
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
johnnyphive said:
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
Click to expand...
Click to collapse
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
v12xke said:
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
Click to expand...
Click to collapse
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied?
Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
johnnyphive said:
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied? Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
Click to expand...
Click to collapse
I don't think you can flash EX kernel from now on. I think you have to use a modded boot.img that will contain his kernel/ramdisk. This is my guess. You really should be getting your information in the dedicated thread where everyone is actually installing and using it. Google "oreo 4 core" and you will find the XDA thread is the first hit. Good luck. :good:
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.