Hi everybody,
This is my second post at XDA and as an answer to my first post (List of Lollipop 5.1 custom kernels for the Nexus 5) This post guides you how get back the stock kernel (LMY47I).
Always remember: You flash at your own risk! This post is only for the Lollipop build LMY47I!
There are two ways to get the stock kernel back, the first with a custom recovery like TWRP or CWM and the second with FASTBOOT (UNLOCKED BOOTLOADER is imortant)
1. Download the STOCK-KERNEL.ZIP in the attachments and extract it (for example with WINRAR or 7-ZIP). Then you have two files. The only one you need is the Kernel.zip file! Copy it to your phone, then switch to the custom recovery navigate to the Kernel.zip file and flash it. Now reboot the phone. The stock kernel was succesfully flashed.
2. Download the STOCK-KERNEL.ZIP in the attachments and extract it (for example with WINRAR or 7-ZIP). Then you have two files. The only one you need is the boot.img! If you haven't downloaded the Android SDK yet download it now! Switch to folder where you installed the SDK and navigate to "platform-tools". Copy the boot.img file into it. Now reboot your phone into FASTBOOT (Bootloader) with POWER Button + VOLUME DOWN and connect your phone to your PC wait until the drivers are installed if you get an error install the latest Google drivers. Open CMD navigate to "platform-tools" and type: "fastboot flash boot boot.img". Reboot your Phone and disconnect the USB-Cable. The stock kernel was succesfully flashed.
Error
Can't flash the zip, says "Unable to execute"
falcon.prj said:
Can't flash the zip, says "Unable to execute"
Click to expand...
Click to collapse
What is the name of the .zip that you tried to flash?
some custom kernels also modify/replace other files in the system partition, so is flashing just boot.img enough to return to stock kernel then?
Wakamatsu said:
What is the name of the .zip that you tried to flash?
Click to expand...
Click to collapse
Kernel.zip
And the problem was with TWRP, sorry
and thanks!
iamelton said:
some custom kernels also modify/replace other files in the system partition, so is flashing just boot.img enough to return to stock kernel then?
Click to expand...
Click to collapse
Nope. So this thread is kinda pointless. You need to reflash your rom after hellscore, code blue, elementalx and probably franco (not used franco since kitkat)
From hells thread -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Related
Windows users should already have :
<<adb drivers>>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
<<usb drivers>>
------------------------------------------------------------------------------------------------------------------------------------------------------
so u did root. u unlocked bootloader. u flashed a recovery and u installed a new rom. one day u start "digging" things to see if u can delete all the unwanted files so u make the phone faster and accidentally u deleted an important file and now it cant boot and it cant go into recovery. you are wondering what you CAN do now ! The answer is : Everything !
You can either go back to stock rom or
you can re-flash the recovery and then reinstall the rom.
1. Download the platform tools for your machine ( windows , linux or mac-os ). Here i have the adb fastboot for you.
2. Copy the recovery image to a location on your computer thats easier for you. The recovery image should have .img extension. If it is in a zip file, extract the .img file from it before proceeding.
3. Connect the phone to the pc and open cmd inside the fastboot folder you downloaded ( windows ). The others not on windows must use cd [path to their desktop,inside the platform tools where they see the adb file].
** If you are on a boot loop but the pc gets to recognize the phone even for a second then
4. Type
i) adb reboot-bootloader
ii) fastboot flash recovery recovery.img ( the command is: fastboot flash recovery [recovery image path/filename] )
5. When its done , reboot. Hold Volume down and power button to see if u get in recovery mode. :highfive:
Install the rom now the way you already know. There are many guides for that so i won't make a new.
cheers :good:
**Windows users can use this fastboot to unlock bootloader too. Lite fastboot commands guide provided here
**Linux users don't even need to download it , they can just directly download it from their terminal
I hope this thread helps a little those that dont know what to do when they delete an important file. *Pictures coming soon*
I am not responsible for people bricking their devices because they haven't made a backup.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads
TWRP For P10 lite: HERE
ADB & Fastboot: HERE
The first step is to make a backup.
2. Download your Treble ROM, i recommend a GSI ROM.
In my case I'll be using Havoc-OS
Download: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/rom-havoc-os-8-1-t3819050
3. Go into TWRP and do a FACTORY RESET and then reboot into fastboot.
4. The only thing you need to do now is flash the ROM, so get your downloaded ROM & extract the .img file from it (if there is no .img file and you see other files, flash via twrp).
On your PC open the fastboot command prompt and type
fastboot -u flash system <YourImageFileHere>
Click to expand...
Click to collapse
After just type : "fastboot reboot" and wait until your phone boots into the system. You may need to flash google apps afterwards.
It is normal for the phone to reboot a couple times so be patient.
Congratz, your phone is not running a treble ROM with your stock ROM's vendor.
Click to expand...
Click to collapse
Video:
I just need backup Boot, System and data if i want go back to stock?
Bad idea to factory reset with TWRP, it doesn't do it clean enough.
You could get in serious problems by doing it, such as random apps crashing, sd unmounting and worse.
Safer option is to factory reset and wipe cache with stock recovery after every system flash.
I'm telling this from my own experience, I don't want people to mess up like I did :highfive:
Ret-Zero said:
I just need backup Boot, System and data if i want go back to stock?
Click to expand...
Click to collapse
Yes that should be enough, vendor stays the same anyway.. I recommend flashing roms designed for kirins cpus btw because there is a higher chance it will work
Hi guys.
While I was looking for an appropriate firmware, I found a website where I could get an update for the Chinese version, which provides the newest Flyme 8 for this device.
https://www.flyme.com/firmwarelist-138.html#3
Download update.zip from here. And download TWRP from here.
I flashed this build with TWRP. To use TWRP you need to have your bootloader unlocked.
To unlock this, please, follow https://remoteunlockservice.com/payment.php (paid). Then flash TWRP, I'm attaching here, using the fastboot mode:
Code:
fastboot flash recovery /path/to/new_recovery.img
I needed to remove lines until the line containing
Code:
delete_recursive("/cache/backup");
in file update-script by the path
Code:
meta-inf/com/google/android/
inside update.zip.
Then I put the modified update.zip to /sdcard and flashed that update.zip using TWRP
Enter TWRP (power + vol+, then release power and hold vol+ up to the vibration). Connect the device with a USB-cable and transfer tool-root_unlock-Testing-Pro7.zip and update.zip to the internal memory.
Flash update.zip and immediately flash tool-root_unlock-Testing-Pro7.zip which I'm attaching here.
Log in with your Flyme account on the phone.
To get the root access please follow the instructions under the link https://mroot.flyme.cn/index.html to make an application (press 申请授权) and download the root app from https://mroot.flyme.cn/download.html.
Filling out the application, you'll encounter some Chinese characters.
Here is some translation:
Flyme 账号 — Flyme Account
Root 授权设备 — Your Device
姓名 — Your Name
手机号码 — Phone Number, use fake Chinese phone number 12345678901
PSN — get this parameter from the root app you have installed
CHIPID — the same as PSN
申请理由 — tell the reason why you need the root access. As for me, I specified, "I need to install the Russian localization for the Chinese firmware."
Wait a few days or less. The single big button in the root app will become active (its color will change from light gray to blue). Pls remember, that you must be logged in your Flyme account. Tap that button and wait until the rooting completes. In the end you'll see a picture which implies your phone has been rooted (an open padlock beside a phone) .
Grats! Now you have the newest rooted firmware.
References: https://4pda.ru/forum/index.php?showtopic=902543
Reserved
Noob question. I'm using a meizu m8 and I was wondering if this method will work on my phone. Do I just have to upgrade my firmware and follow your instruction is that correct? My current firmware is Flyme 7.1.6.0G
Sorry, but I have checked the relevant thread on 4pda, and the method there is dramatically different.
Hi, did you have an idea of why with unlocked BL, fastboot tell me "FAILED (remote: not allowed in locked state)" ?
Device is pro7 P25 64Gb version
Thx !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
myxomop25 said:
I needed to remove lines until the line containing
Code:
delete_recursive("/cache/backup");
in file update-script by the path
Code:
meta-inf/com/google/android/
inside update.zip.
Then I put the modified update.zip to /sdcard and flashed that update.zip using TWRP
Click to expand...
Click to collapse
Should I delete up to delete_recursive("/cache/backup")
Or including this line ?
I tried both way but I always receive error 11. Also tried to copy updater-script from custom firmware
Also tried to install Meizu Pro 7 AOSP Beta V3.zip
That goes ok, no errors but phone starts only in twrp
Have no Ideea why
tintome said:
Also tried to install Meizu Pro 7 AOSP Beta V3.zip
That goes ok, no errors but phone starts only in twrp
Have no Ideea why
Click to expand...
Click to collapse
that means your phone still have orange state enable .
Try flashing magisk insatller zip v18 after flashing the Aosp rom.
Hello,
I have a mi A2 device that I unlocked it and flashed TWRP on it. I flashed TWRP on both slots and everything was ok.
After that, my USB board or charging board damaged for unknown reasons and the repairman could not fix it, Also, its charging board is very rare in my area and I can't find it.
So, my phone is never detected by PC but it can be charged, and I can't use fastboot commands.
A few days ago without knowing that DotOS has dedicated recovery, I flashed it with TWRP on slot A, and now I can't use TWRP on slot A anymore. But I think the TWRP is still installed on the slot B.
I really need root my device, so please help me.
1- Is there anyway to change slots without fastboot?
2- Can I install TWRP from anyway other than fastboot?
I tried to install TWRP zip file from DotOS recovery but it does not accept any file except DotOs official updates.
I can use adb commands with wireless debugging feature in android 11.
DotOS recovery options (Advanced option Does not include a useful option, just include reboot options and view logs)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. Download dotos offical update
2. Download the twrp in .img form
3. Rename twrp to recovery.img
4. Put the recovery.img into the dotos zip. If it asks to replace file, just replace it
5. Flash
LR7875 said:
1. Download dotos offical update
2. Download the twrp in .img form
3. Rename twrp to recovery.img
4. Put the recovery.img into the dotos zip. If it asks to replace file, just replace it
5. Flash
Click to expand...
Click to collapse
DotOS not include recovery.img in zip file, but it installed recovery too.
Does this solution still works?
DotOS zip file:
Oh no the dotos recovery and system is compressed in the payload bin file
What will happen if you delete the payload.bin and replace it with the twrp recovery.img
LR7875 said:
Oh no the dotos recovery and system is compressed in the payload bin file
What will happen if you delete the payload.bin and replace it with the twrp recovery.img
Click to expand...
Click to collapse
Not works, can't flash
So can you boot into system
And did you adb sideload?
LR7875 said:
And did you adb sideload?
Click to expand...
Click to collapse
I can't use adb sideload in recovery, because of damaged usb, I can boot system but can't use sideload command in system
Hello all,
I recently got my motherboard replaced after the pixel 5a died. The problem was covered under the extended warranty. Phone works just fine when I received it back. I tried rooting it using magisk to patch the boot.img file. After fastboot flash boot file.img, my phone would say device is corrupt and unable to start.
I downloaded the factory image from google. Tried using flash-all to completely restart the process. Used latest platform-tools (downloaded today). Bootloader is unlocked. I keep getting this error during the flash-all process and my phone is unable to boot. I'm still able to access fastboot. Where am I going wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is larger screen shot of the entire flash-all process.
The issue is a known bug with latest SDK platform tools. Download and install platform-tools ver 33.x and you'll be fine.
Cheers!
flash stock rom via chrome browser , then patch boot.img and flash again to root , i am in lastest version a13 and root work fine
Typhus_ said:
The issue is a known bug with latest SDK platform tools. Download and install platform-tools ver 33.x and you'll be fine.
Cheers!
Click to expand...
Click to collapse
This is the fix, download platform-tools 34.0.0
Typhus_ said:
The issue is a known bug with latest SDK platform tools. Download and install platform-tools ver 33.x and you'll be fine.
Cheers!
Click to expand...
Click to collapse
This was my problem. I used 33 and it worked fine, thanks. Anyone know when it'll get fixed for 34?
when flash patched boot.img and is corrupt!!! Than Patch the recovery.img and flash it to Recovery Partition, you must start the device with Buttons-Combo in Recovery-Mode to start the System with Root!!! think you have no Recovery-Mode on this Method, you must Flash recovery.img new to use Recovery-Mode!!!