I apologize ahead of time if this is the wrong section or my question has already been answered. I've been searching all day.
I am trying to get a custom recovery on an old SPH-D710 with a bad port so I am using wireless ADB but I can't get the recovery partition mounted. DiskInfo app and running
Code:
ls -l /dev/block/platform/dw_mmc/by-name/
both show recovery at /dev/block/mmcblk0p6 but I keep getting "No such device" error from mount.
I've tried a bunch of different filesystem types and its always the same thing.
I am new to mucking around with Android at the command line, or hacking the devices at all. I have always used Odin or a custom recovery to get things done. I am a pretty experienced *nix guy though and this has me stumped. The partition is right there in the list with the rest of them, is there something else going on in the version of mount on this device that's affecting it's visibility of that partition?
Why mount the recovery? You are just wanting to dump it so that you can build TWRP or other custom recovery for it, right? Or do you have a recovery, but just can't flash it?
To dump stock recovery
dd if=dev/block/mmcblk0p6 of=/sdcard/stockrecovery.img
Then to flash new recovery
dd if=/sdcard/customrecovery.img of=/dev/block/mmcblk0p6
Sent from my KYOCERA-C6745 using Tapatalk
From what I know, you can't mount recovery partition, as RealWelder said, you can dump it, then modify and reflash it
(sure, you need root to dump those images)
RealWelder said:
Why mount the recovery? You are just wanting to dump it so that you can build TWRP or other custom recovery for it, right? Or do you have a recovery, but just can't flash it?
To dump stock recovery
dd if=dev/block/mmcblk0p6 of=/sdcard/stockrecovery.img
Then to flash new recovery
dd if=/sdcard/customrecovery.img of=/dev/block/mmcblk0p6
Click to expand...
Click to collapse
Well first I need to say I feel like an idiot for trying to mount it. I read some old speculative post on a different forum that put that in my head. For someone claiming to have *nix experience I can't believe I didn't think to use dd. So now that is out of the way.
Output from DD reflected a successful write but "reboot recovery" and it was still stock.
The .img I flashed was from a TWRP .zip for that device. So what did I do wrong this time?
EDIT: I take that back, it was from philz touch (the modded CWM).
This was the relevant part of what I did in the shell if it matters:
Code:
[email protected]:/sdcard/external_sd # dd if=recovery.img of=/dev/block/mmcblk0p6
dd if=recovery.img of=/dev/block/mmcblk0p6
14909+1 records in
14909+1 records out
7633899 bytes transferred in 2.924 secs (2610772 bytes/sec)
[email protected]:/sdcard/external_sd # reboot recovery
reboot recovery
volDeus said:
This was the relevant part of what I did in the shell if it matters:
Code:
[email protected]:/sdcard/external_sd # dd if=recovery.img of=/dev/block/mmcblk0p6
dd if=recovery.img of=/dev/block/mmcblk0p6
14909+1 records in
14909+1 records out
7633899 bytes transferred in 2.924 secs (2610772 bytes/sec)
[email protected]:/sdcard/external_sd # reboot recovery
reboot recovery
Click to expand...
Click to collapse
You may also need to modify the boot.img to disable signature check on boot. On a lot of newer devices if the signature doesn't match, it will flash stock recovery at boot time...overwriting the philz.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
You may also need to modify the boot.img to disable signature check on boot. On a lot of newer devices if the signature doesn't match, it will flash stock recovery at boot time...overwriting the philz.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Ah that makes sense. More research for tomorrow
How to upload boot.img
RealWelder said:
You may also need to modify the boot.img to disable signature check on boot. On a lot of newer devices if the signature doesn't match, it will flash stock recovery at boot time...overwriting the philz.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
dear, how to modify the boot.img to disable signature check on boot?
This will help you understand, though it may not be of much help in actuality accomplishing your goal, depending on the device.
https://forum-xda--developers-com.c...g-boot-images-android-verified-t3600606/page1
Sent from my LG-Q710AL using Tapatalk
RealWelder said:
Why mount the recovery? You are just wanting to dump it so that you can build TWRP or other custom recovery for it, right? Or do you have a recovery, but just can't flash it?
To dump stock recovery
dd if=dev/block/mmcblk0p6 of=/sdcard/stockrecovery.img
Then to flash new recovery
dd if=/sdcard/customrecovery.img of=/dev/block/mmcblk0p6
Click to expand...
Click to collapse
Morning man..
I am sorry if I ask it in this thread, I am about to bring my whyred (redmi note 5 pro) back on.
Can I use this script to flash new recovery into my whyred??
I have an official unlocked bootloader whyred, with erased recovery, no twrp and only has fastboot mode.
But when I flash through
fastboot flash recovery xxx.img
It ends with :
Remote : error flashing partition : write protected
The only way to akses ADB is :
Fastboot boot xxx.img (twrp)
So I can akses
ADB devices
Xxxxxxxx recovery
Once more, I am so sorry if I write in wrong thread but I really need to pass the write protected partition.
Thank you..
Related
hi all,
I have followed MikeyCiggz's post:http://forum.xda-developers.com/showthread.php?t=1233154&page=2, thanks MIkeyCiggz first!
But I cannot find a suitable bootable recovery image for evo 3d:-(. I have tried twrp 1.0.3, twrp 1.1.1, twrp 2.0, it seemed that twrp image file is not bootable. I have tried:
dd if=./twrp-1.1.1.img of=/dev/mmcblk01 bs=1M
but the sd card it not bootable.
I have searched google but find nothing...so anyone can give any hints that where can I download the bootable recovery image, both twrp and cwm is ok. thanks in advance!
I don't have the answer to your question but, I don't think you should put ./ in the if= section. Your not executing the file.
Sent from my PG86100 using Tapatalk
megabiteg said:
I don't have the answer to your question but, I don't think you should put ./ in the if= section. Your not executing the file.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
./ means the current directory, ./twrp-1.1.1.img means twrp-1.1.1.img in the current directory
Anyone tried twrp 2.0 with bootable sdcard? please share your success story, thanks!
subaochen said:
hi all,
I have followed MikeyCiggz's post:http://forum.xda-developers.com/showthread.php?t=1233154&page=2, thanks MIkeyCiggz first!
But I cannot find a suitable bootable recovery image for evo 3d:-(. I have tried twrp 1.0.3, twrp 1.1.1, twrp 2.0, it seemed that twrp image file is not bootable. I have tried:
dd if=./twrp-1.1.1.img of=/dev/mmcblk01 bs=1M
but the sd card it not bootable.
I have searched google but find nothing...so anyone can give any hints that where can I download the bootable recovery image, both twrp and cwm is ok. thanks in advance!
Click to expand...
Click to collapse
Never heard of copying the recovery image directly onto the sdcard and then booting off of it.
As my understanding of the boot process goes, recovery mode will only load the recovery image for the specific recovery partition. Recovery mode doesn't search the device for recovery images in any random partition.
The link you provided had no directions or evidence to support it being possible. Perhap if there is more information on this process, it might seem more feasible.
hope that helps! good luck!
joeykrim said:
Never heard of copying the recovery image directly onto the sdcard and then booting off of it.
As my understanding of the boot process goes, recovery mode will only load the recovery image for the specific recovery partition. Recovery mode doesn't search the device for recovery images in any random partition.
The link you provided had no directions or evidence to support it being possible. Perhap if there is more information on this process, it might seem more feasible.
hope that helps! good luck!
Click to expand...
Click to collapse
I think a bootable recovery sdcard maybe the same as the command:
fastboot boot recovery.img
the above command should boot into recovery despite of the recovery partition on the inner storage of the phone. Is that right?
subaochen said:
I think a bootable recovery sdcard maybe the same as the command:
fastboot boot recovery.img
the above command should boot into recovery despite of the recovery partition on the inner storage of the phone. Is that right?
Click to expand...
Click to collapse
The above command will send the recovery.img located on the host computer, through the host computer's fastboot binary and USB connection to the device which is also in fastboot mode and will then temporarly booted into the transferred recovery image on the device.
Never heard of fastboot boot a full sdcard?
Not sure how that deals with sdcard ..
So, since Fastboot does not work apparently, what is another way to flash CWM Touch? I am not going to pay $1.99 for the convenience to flash it every time I get a new phone. Does ADB commands work, like doing it from terminal? And where is the recovery located? Do not want a brick here and am fine now on stock CWM. And please, don't just say use TWRP. I know about TWRP and just prefer CWM
I tried making a tar.md5 from the img file but it failed to flash...
OK, I am guessing I have to loki this recovery to work. Apparently I have to adb pull my aboot and then use loki patch to create a loki'd cwm recovery.
SO:
copied from djrbliss:
=============
Sample usage
=============
First, a developer must pull the aboot image from a target device:
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
Next, a .lok image can be prepared using loki_patch:
[email protected]:~$ loki_patch
Usage: ./loki_patch [boot|recovery] [aboot.img] [in.img] [out.lok]
[email protected]:~$ loki_patch recovery aboot.img cwm.img cwm.lok
[+] Detected target AT&T build JDQ39.I337UCUAMDB or JDQ39.I337UCUAMDL
[+] Output file written to cwm.lok
Finally, the .lok image can be flashed using loki_flash:
[email protected]:~$ adb push cwm.lok /data/local/tmp
[email protected]:~$ adb push loki_flash /data/local/tmp
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # /data/local/tmp/loki_flash
Usage: /data/local/tmp/loki_flash [boot|recovery] [in.lok]
[email protected]:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/cwm.lok
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!
Is there anything I should change for Verizon variant. Don't mind getting my hands dirty, just want to make sure I am doing it right!
You can flash it with rom toolbox, how I installed it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
You can flash it with rom toolbox, how I installed it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Figures there would be an easy way. So Rom Toolbox will flash CWM touch recovery image?
Broken said:
So, since Fastboot does not work apparently, what is another way to flash CWM Touch? I am not going to pay $1.99 for the convenience to flash it every time I get a new phone. Does ADB commands work, like doing it from terminal? And where is the recovery located? Do not want a brick here and am fine now on stock CWM. And please, don't just say use TWRP. I know about TWRP and just prefer CWM
I tried making a tar.md5 from the img file but it failed to flash...
Click to expand...
Click to collapse
The recovery needs to be loki flashed in place. Only the official recovery can be odin'd in. And if you flash the unloki'd recovery to the recovery partition, on reboot you will be greeted by a lovely note from verizon saying how you need to walk in and tell them why you messed up your phone.
Besides loki-patching the recovery .img the only way I know to get it installed properly is by using either ROM Manager Pro. Or using ROM Toolbox(both pro and lite I believe) Pro for sure, I never ran lite so I cant say. in RTP it is under rom management, flash recovery, pick.
TWRP is still better though. Just saying that a dalvik wipe and cache wipe should be convenient... Putting them in 2 separate screens is neither newb friendly or convenient.
woops late reply
Dubbsy said:
The recovery needs to be loki flashed in place. Only the official recovery can be odin'd in. And if you flash the unloki'd recovery to the recovery partition, on reboot you will be greeted by a lovely note from verizon saying how you need to walk in and tell them why you messed up your phone.
Besides loki-patching the recovery .img the only way I know to get it installed properly is by using either ROM Manager Pro. Or using ROM Toolbox(both pro and lite I believe) Pro for sure, I never ran lite so I cant say. in RTP it is under rom management, flash recovery, pick.
TWRP is still better though. Just saying that a dalvik wipe and cache wipe should be convenient... Putting them in 2 separate screens is neither newb friendly or convenient.
woops late reply
Click to expand...
Click to collapse
Well, just looked at rom toolbox and latest recovery it has is 6.0.3.2. I have 6.0.3.6 that I dl'ed. Looks like I will try loki flashing. Hope those commands djrbliss listed work on the verizon version lol..
Broken said:
Well, just looked at rom toolbox and latest recovery it has is 6.0.3.2. I have 6.0.3.6 that I dl'ed. Looks like I will try loki flashing. Hope those commands djrbliss listed work on the verizon version lol..
Click to expand...
Click to collapse
You can download the latest touch version for free from the clockworkmod website. Not sure if its patched though so youll probably have to patch it yourself.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
You can download the latest touch version for free from the clockworkmod website. Not sure if its patched though so youll probably have to patch it yourself.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, it isn't loki'd so am going to try that after I set up sdk again.
I have Huawei P6,
It stop booting at logo MIUI (so not possible to use IHM root file manager).
I would like to push a file from my PC to the device (Huawei P6 U06) using ADB Shell in recovery mode.
Push file to device mains push file to /system of device.
Does someone has steps guide or tools to do this?
LikeM8 said:
I have Huawei P6,
It stop booting at logo MIUI (so not possible to use IHM root file manager).
I would like to push a file from my PC to the device (Huawei P6 U06) using ADB Shell in recovery mode.
Does someone has steps guide or tools to do this?
Click to expand...
Click to collapse
Which custom recovery and version do you have installed? I would recommend taking a look at this guide here and following it up through step 10. Let me know if you still have questions.
shimp208 said:
Which custom recovery and version do you have installed? I would recommend taking a look at this guide here and following it up through step 10. Let me know if you still have questions.
Click to expand...
Click to collapse
Thanks Shimp for your time.
custom recovery is TWRP v2.6.3.3
The goal is to remove TWRP recovery by a stock one to perform an update with dload/UPDATE.APP from SDCARD.
To do this I would like to copy the file recovery-from-boot.p file in /system device to remove TWRP when boot to recovery mode.
As I said, the phone stope to boot at MIUI logo (error from TWRP E: unable to mount '/cache').
Sideload failed!
LikeM8 said:
Thanks Shimp for your time.
custom recovery is TWRP v2.6.3.3
The goal is to remove TWRP recovery by a stock one to perform an update with dload/UPDATE.APP from SDCARD.
To do this I would like to copy the file recovery-from-boot.p file in /system device to remove TWRP when boot to recovery mode.
As I said, the phone stope to boot at MIUI logo (error from TWRP E: unable to mount '/cache').
Sideload failed!
Click to expand...
Click to collapse
I apologize @LikeM8 for the delay in getting back to you somehow this thread got lost in the shuffle. In the guide I linked I would recommend using that to get ADB access in recovery going that way you can copy the file recovery-from-boot.p to your device, don't worry about the sideload part only use it to get ADB access in recovery mode :good:.
shimp208 said:
I apologize @LikeM8 for the delay in getting back to you somehow this thread got lost in the shuffle. In the guide I linked I would recommend using that to get ADB access in recovery going that way you can copy the file recovery-from-boot.p to your device, don't worry about the sideload part only use it to get ADB access in recovery mode :good:.
Click to expand...
Click to collapse
No problem @shimp208 thanks for your reply. Where I have to copy recovery-from-boot.p ? Where I could be find the stock file for my Huawei P6 U06? Regards!
LikeM8 said:
No problem @shimp208 thanks for your reply. Where I have to copy recovery-from-boot.p ? Where I could be find the stock file for my Huawei P6 U06? Regards!
Click to expand...
Click to collapse
You can get the stock recovery for your device from this thread here, also you won't even need to use recovery-from-boot.p as you can boot your device into fastboot mode to flash the stock recovery.
shimp208 said:
You can get the stock recovery for your device from this thread here, also you won't even need to use recovery-from-boot.p as you can boot your device into fastboot mode to flash the stock recovery.
Click to expand...
Click to collapse
Thanks for the link @shimp208, but when I flash these stock recovery from fastboot, I still again TWRP 2.6.3.3!!! Help please!!!
I thought I broke my maghine and order new one. Recovery SDcsrd works
LikeM8 said:
Thanks for the link @shimp208, but when I flash these stock recovery from fastboot, I still again TWRP 2.6.3.3!!! Help please!!!
Click to expand...
Click to collapse
Hello again @LikeM8 sorry again for the delay caused by my final exams (still in progress for the next two weeks), you can get the stock ROM for your device here in the index thread from the stock rom you can pull recovery-from-boot.p and attempt to install the stock recovery.
shimp208 said:
Hello again @LikeM8 sorry again for the delay caused by my final exams (still in progress for the next two weeks), you can get the stock ROM for your device here in the index thread from the stock rom you can pull recovery-from-boot.p and attempt to install the stock recovery.
Click to expand...
Click to collapse
Thanks @shimp208...pull recovery-from-boot.p from stock ROM??? Did you mean, I have to pull recovery-from-boot.p fill using adb (recovery mode)?
LikeM8 said:
Thanks @shimp208...pull recovery-from-boot.p from stock ROM??? Did you mean, I have to pull recovery-from-boot.p fill using adb (recovery mode)?
Click to expand...
Click to collapse
What I meant was put the stock ROM on your computer unpack and it and extract the from it then push recovery-from-boot.p from your computer to your phone, then re-flash stock recovery.
shimp208 said:
What I meant was put the stock ROM on your computer unpack and it and extract the from it then push recovery-from-boot.p from your computer to your phone, then re-flash stock recovery.
Click to expand...
Click to collapse
Ok @Shimp2008, I try and lets you know. Thanks for your time!
shimp208 said:
What I meant was put the stock ROM on your computer unpack and it and extract the from it then push recovery-from-boot.p from your computer to your phone, then re-flash stock recovery.
Click to expand...
Click to collapse
hello @shimp208, stock ROM I find in the page are dload/UPDATE.APP form, not zip file to unpack.
I have yet recovery-from-boot.p file. When from recovery and adb shell I put it on /system, after reboot, the recovery-from-boot.p file was been delete by the device???
What I did wrong or I have to perform to keep recovery-from-boot.p file in /system directory after reboot?
PS: Before operation, I perform "mount -o remount,rw /system"
LikeM8 said:
hello @shimp208, stock ROM I find in the page are dload/UPDATE.APP form, not zip file to unpack.
I have yet recovery-from-boot.p file. When from recovery and adb shell I put it on /system, after reboot, the recovery-from-boot.p file was been delete by the device???
What I did wrong or I have to perform to keep recovery-from-boot.p file in /system directory after reboot?
PS: Before operation, I perform "mount -o remount,rw /system"
Click to expand...
Click to collapse
TWRP may be overwriting the file on it's own, another possibility would be to follow the directions for the stock recovery flashing i linked to earlier and seeing if only fastboot booting the stock recovery image will let you re-flash the stock ROM.
I have twrp and root my phone but how can i unroot and back to stock recovery?
you can't yet
happyharrysco1 said:
you can't yet
Click to expand...
Click to collapse
someone can just fastboot boot twrp.img and back up stock recovery/boot partitions then share the backups for people to restore
since i haven't enabled backup for recovery partition, you can simply use from adb or terminal to create stock recovery.img:
Code:
dd bs=2M if=/dev/block/bootdevice/by-name/recovery of=/external_sd/recovery.img
the same is doable for boot (which flashing will unroot you):
Code:
dd bs=2M if=/dev/block/bootdevice/by-name/boot of=/external_sd/boot.img
bugger i could have done this but it's too late now :/ maybe put a request for this in the main thread?
Have you looked into flashing the KDZ here?
http://forum.xda-developers.com/lg-g5/development/stock-h850-10c-eu-kdz-flashable-zips-t3369794
Hi,
this is a small tutorial to show you how to flash the recovery, also eRecovery, via command line / adb shell within Android.
Flashify and other apps never worked for me, so I used commands to flash it without the need of fastboot.
It's a small tutorial for those who never worked with commands like this.
Please notify me if something went wrong or if you found any other issues.
I wanted to make a small script but I stopped it because of the lack of available commands in Android.
DISCLAIMER:
Read this tutorial first.
Never flash custom recovery to eRecovery.
Never flash recoveries from different devices.
Don't try to flash other partitions with this commands if you don't want to risk a brick.
Requirements:
- Oreo / EMUI 8 installed, Nougat hast other partition names. Pie isn't supported by me until final release.
- working root access
- terminal emulator app (I recommend Termius, it's easy to use and has nice features, it's free to use)
> or a PC, and USB cable and working ADB, also USB Debugging enabled in developer settings
- recovery img files on your phone, I recommend it to put them into your user root /data/media/0/ (internal memory)
NOTE: All commands are case sensitive!
Now open your terminal app or open the adb shell.
Type following command to enable root access:
Code:
su
SuperSU will ask you for root access, grant it.
Following command is needed to figure out, which type of memory your phone has:
Code:
ls /dev/block/platform
There are two possible outputs:
If you've a device with the faster UFS memory, it's ff3b0000.ufs, if eMMC it's hi_mci.0.
From now I'll write MEMORY instead of ff3b0000.ufs or hi_mci.0.
For flashing the recovery fire up following command:
Code:
dd if=/PATH/TO/YOUR/RECOVERY.IMG of=/dev/block/platform/MEMORY/by-name/recovery_ramdisk_a
Example: dd if=/data/media/0/twrp_3.2.1.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
The output should look like this:
Code:
65536+0 records in
65536+0 records out
33554432 bytes transferred in 0.247 secs (135847902 bytes/sec)
If not, check your command and file paths.
For flashin the eRecovery fire up following command:
Code:
dd if=/PATH/TO/YOUR/ERECOVERY.IMG of=/dev/block/platform/MEMORY/by-name/erecovery_ramdisk_a
Example: dd if=/data/media/0/ERECOVERY_RAMDI.IMG of=/dev/block/platform/ff3b0000.ufs/by-name/erecovery_ramdisk_a
IMPORTANT NOTE: DO NOT INSTALL TWRP IN THIS! Flash only stock eRecovery!
The dd command won't give you any progress output, so be a bit patient. It should be done in a few second, but don't close the terminal app or connection before you got any output.
Unix systems like Android will give an output if something went wrong, always.
I use this to flash new TWRP versions or to flash stock recovery before I update.
If you recently updated your phone, you still need to flash via fastboot, because you lost root during the update.
The dd commands also work with fastboot. Mostly you'll use "fastboot flash recovery_ramdisk", but if you need to flash eRecovery, you can use the dd command.
23. February 2019:
Pie should also work, but you have to remove the "_a" after the partition name.
Example:
dd if=/data/media/0/twrp_3.2.1.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk
Please report if it's working or not.
How to know the path to the recovery_ramdisk?? Is all devices the same?? I didn't get it right the 1st time .. it shows path is invalid
Sent from my VTR-L29 using Tapatalk
fr3ker said:
How to know the path to the recovery_ramdisk?? Is all devices the same?? I didn't get it right the 1st time .. it shows path is invalid
Sent from my VTR-L29 using Tapatalk
Click to expand...
Click to collapse
Should be the same on every device. Remember, case sensitive and use _ and not -.
Maybe it's different on non UFS devices, which one do you have?
Are you able to post a screenshot of your command and output?
Jannomag said:
Should be the same on every device. Remember, case sensitive and use _ and not -.
Maybe it's different on non UFS devices, which one do you have?
Are you able to post a screenshot of your command and output?
Click to expand...
Click to collapse
Maybe @fr3ker is not on Oreo? The recovery_ramdisk partition is only for Oreo. In Nougat it is just called recovery. I don't know how the Pie partitions are called.
M1chiel said:
Maybe @fr3ker is not on Oreo? The recovery_ramdisk partition is only for Oreo. In Nougat it is just called recovery. I don't know how the Pie partitions are called.
Click to expand...
Click to collapse
Also my thought, I wanted to add this to the requirements when I created this post but apparently I forgot this. Now it's added as first point.
Hi.
I have a hard bricked p10. When I connect to laptop it's says USB SER. It doesn't not turn on I can't access recovery with power + vol. I can't get into fastboot. Anyway I can access fastboot to flash kernel and erecovery?
Jannomag said:
I use this to flash new TWRP versions or to flash stock recovery before I update.
Click to expand...
Click to collapse
Is it mandatory to flash stock recovery before update? Is it applies only to ota update or ff method?
Yes, FF or OTA are using stock recovery to flash the update. With TWRP it won't work.
Updated?
@ Jannomag:
Have you checked this for Pie meanwhile?
I currently have the problem, not being able to enter fastboot with:
Code:
sudo adb reboot bootloader
Additionally, there's something I do not understand. For the dd-command for flashing, why is the input-file (if=) the file in "/dev/block/platform/..." and the output on the sd-card? Wouldn't mean flashing an img to the device, that if= on the sd (or connected PC) and of= the path to the device (phone)?
Blümchen Blau said:
@ Jannomag:
Have you checked this for Pie meanwhile?
I currently have the problem, not being able to enter fastboot with:
Code:
sudo adb reboot bootloader
Additionally, there's something I do not understand. For the dd-command for flashing, why is the input-file (if=) the file in "/dev/block/platform/..." and the output on the sd-card? Wouldn't mean flashing an img to the device, that if= on the sd (or connected PC) and of= the path to the device (phone)?
Click to expand...
Click to collapse
WTF....Why didn't I notice this terrible mistake! Thank you for reading my post completely, you're 100% correct, I'll correct this directly after I submit this post.
Huawei did also a small change at naming the recovery partition, which I'll update, too.
I had also the problem that I wasn't able to boot into fastboot by command before I fried my phone - I couldn't figure out the reason for this.
Again, thank you!
Jannomag said:
Again, thank you!
Click to expand...
Click to collapse
Your'e welcome! I did update now, but didn't need your (correct ) way to fastboot, because the method described by borgerapper did the trick for me to get into fastboot and flash the needed original recovery.
Thanks anyway!