Background Information
NOTE: I am not responsible in any way for whatever may go wrong with you or your device by following this guide. What works for me may not work for you. Read the commands and understand what they mean before using them. If something doesn't look right, then stop. If you don't understand something, then stop. You use this guide at your own risk
The honor 5x has another separate recovery partition called eRecovery. It can be accessed by powering on the phone by holding the Power + Volume Up button at the same time, while the phone is connected to a computer via usb. Using those same keycodes while the phone isn't connected via usb will boot into normal recovery. (This was pretty confusing behavior for me at first until I figured it out). eRecovery looks like this screen:
{
"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"
}
Flashing this eRecovery partition with a recovery of your choice (such as TWRP) will give you a second choice in the event that the first recovery is corrupted or damaged. The core premise of this guide is saving the recovery image to the sd card, locating the erecovery partition using ADB shell, and then using dd to write the recovery image to the partition. For this guide, it is assumed you already have twrp installed into the main recovery, and intend to download another twrp image to write to the erecovery as well.
The Guide
Download the recovery image from here: https://dl.twrp.me/kiwi/
Open a terminal in the folder of the downloaded recovery image
Reboot to the main recovery using adb
Code:
adb reboot recovery
Push the recovery image to the external sd card
Code:
adb push ./twrp-3.3.1-0-kiwi.img /external_sd
Open up an adb shell
Code:
adb shell
Within this shell, locate the erecovery partition and save it to a variable for use later. (if the below command doesn't print out anything, try browsing through /dev/block/platform until you find the folders /by-name/erecovery, and then using that path in the below command)
Code:
DEV=$(ls /dev/block/platform/soc.0/7824900.sdhci/by-name/erecovery); echo $DEV
Write the recovery image from the external sd card to the erecovery partition
Code:
dd of=$DEV if=/external_sd/twrp-3.3.1-0-kiwi.img
The installation is now complete! Try it by connecting your phone to a computer, and holding the power + volume up button while turning the phone on.
you start from fastboot mode or eRecovery?
Related
Hello everyone!
i do the following step how to install Nanandroid on my HTC Touch HD.
1. Flash the latest HardSPL from OliNex
2. Extract the 'adb files & fastboot.exe' files to a folder
3. Format the microSD card fully as FAT32
4. Copy the 'BlacIMG.NBH' file and your selected ROM (zip) you wish to use to the root of the microSD
5. Boot in TriColour mode (Power button and Volume down button)
6. Whilst in the TriColour mode, connect the Blackstone to a USB port ('Serial' should now say 'USB')
7. Run 'BlackstoneRUUAdvanced' and select the 'Task 29' which is full wipe of the Blackstone
8. Once completed, insert the microSD card and reboot into the TriColour mode again
9. The Blackstone will auto-flash-install (after key confirmation) the 'BlacIMG.NBH' on the microSD card
10. The 'BlacIMG.NBH' must NOT be flashed via Windows using the RUU tool (it will only fail)
11. Once flashed with the 'BlacIMG.NBH' it will reboot to a new Fastboot screen (blue background)
12. After a short time the Blackstone in Fastboot mode with enter a USB connect ready state
13. Now connect the Blackstone to your Windows OS and open a CLi/Command prompt
14. Within CLi go to the directory where you place the 'adb files & fastboot.exe' files (from step 2)
15. Type: fastboot flash recovery recovery.img (this will flash install the custom CWR)
16. Then type: fastboot boot recovery.img (this will reboot your Blackstone into CWR)
and it's appear :
{
"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"
}
then i chose apply from sd card. but it's stuck.!!!!!
would you help me, please!!! :crying:
thanks in advance.
Why did you make a new thread for this? God, for some reason there is a thread for the ROM already...
Anyways, the phone is not stuck.
When you get into recovery press vol up, down, and up again, as it says on the instructions. Please read before asking.
unlock the power botton
mfsr98 said:
Why did you make a new thread for this? God, for some reason there is a thread for the ROM already...
Anyways, the phone is not stuck.
When you get into recovery press vol up, down, and up again, as it says on the instructions. Please read before asking.
Click to expand...
Click to collapse
dude, try press up, down and up
strictly abide these three steps, you can unlock the power botton
Hello.
I've repaired a nexus 4 screen and digitizer but I got it back because my friend can't recover access from a forgotten pattern lock.
He is running stock android 5 lollipop and he doesn't get the email recovery option when he inputs wrong pattern. I've searched even in google support but I didn't find a solution to recover his photos.
My main concern is to recover files and photos!!! There isn't a reason to suggest a factory reset....
--Phone Status---
Boot loader seems unlocked "Locked state is marked as unlocked in bootloder in red letters" while secure boot is enabled in green letters
USB debugging seems OFF: There is no android device listed in device manager. I only get a music player in disk drives which is empty.
adb devices command in bootloader recognises it
When entering to recovery I get the message "no command" along with the icon of an android under repair.
No dropbox no google+ photos backup
---What I've tried---
UPDATE: Managed to flash TWRP 2.7.1.0 I can see the files but since usb flash drive doesn't work I can't copy the files...
Android Device manager: Returns error that the phone is already locked and there is no need to apply new password.
Tried about 30 wrong patterns and it didn't came up the google mail recovery option.
Tried during a phone call to see the files but I only managed to turn on WiFi.
{
"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"
}
When you say the USB flash drive doesn't work, do you mean the USB port in the phone?
MTP doesn't always work in TWRP, meaning it won't show up as a normal usb drive on a pc. ADB will still work though, you have to set up ADB on your computer, boot into twrp on the phone and use 'adb pull' to copy the files to the computer. On windows you will need to download adb and the drivers, I use http://www.koushikdutta.com/post/universal-adb-driver
I'm trying to install the drivers for adb but I cannot find the right one.
Edit: Also it cannot be detected from boot loader now. I'll try in a pc that already has been connected and worked.
I have adb and fastboot installed already and worked with this and my own phones.
Edit: It seems to be a lost cause the phone fell down many times. Don't bother maybe I'll solder a usb port first... if it is possible with my less than basic equipment.
There are many methods on the following page,
http://forum.xda-developers.com/showthread.php?t=2620456
The way I did it was an alternative version of method 5 while in twrp.
Method 5 - alternatively, Mount system in twrp and delete the file /data/system/gesture.key
If it asks for a pattern on boot just try any random pattern it should let you in. I did this when a version before lollipop was installed but there is no reason it shouldn't work on lollipop as the same file is saved in the same location, just checked.
Using adb
adb shell rm /data/system/gesture.key
Click to expand...
Click to collapse
PERISIST ERROR IN TWRP WHILE FLASHING ANY ZIP.....? THEN HERE IS THE GUIDE
{
"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"
}
I am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
1. You get "e: cannot mount /persist" in recovery
2. Can't access to internal storage.
3. Boot loop on Lollipop 5.0 and above
4. IMEI number is lost even after formating cache and fastboot flash cache.img
5. No signal even after formating cache and fastboot flash cache.img
Then your persist partition have to be fixed
Follow instructions carefully to solve this issue
NOTE : UNLOCK your device bootloader first before doing this
1. Download this " persist file & ADB+&+Fastboot of yureka " provided by @Annabathina
2. extract them in PC
3. open ADB+&+Fastboot of yureka
4. place presist.img file which you have extracted in ADB+&+Fastboot folder
5. Hold shift key and right click on mouse and select Open command window here
6. Connect your device to pc..... and make sure that drivers are installed properly..... ( VERY VERY IMPORTANT )
a. Type : adb devices
If your device is connected you will get it in connected devices list
b. Type : adb reboot-bootloader
Your phone will restart into bootloader.
c. Type : fastboot -i 0x1ebf flash persist persist.img
7. Disconnect your device from PC and REBOOT
ADB+&+Fastboot : link
persist : link
@Annabathina............................for Guide
Ricks ............... for Presist file
YU YUREKA
YU YUREKA PLUS
Thanks man...you saved me ,i had almost given up on my yureka as even twrp was not working after i soft brick my phone last night
Thanks a lot!!!
Hello,
I am having problems with adb recognition on recovery mode. I did manage to contact codeworkx, but it seems it's just me, because for him it's working. The drivers are installed correctly, because adb sideload works just fine. I want to use the new adb backup function, to backup files right into my PC, but no recognition is stopping me. Has anyone ever had this problem? If so, any ideas on how to fix it are really welcome. Thanks in advance!
adb backup isn't particularly useful because it doesn't backup stuff like SMS.
By recovery, do you mean fastboot mode? And only the adb command doesn't work? That's strange. Have you tried switching the cable or trying a different PC? What error are you getting?
sk8223 said:
adb backup isn't particularly useful because it doesn't backup stuff like SMS.
By recovery, do you mean fastboot mode? And only the adb command doesn't work? That's strange. Have you tried switching the cable or trying a different PC? What error are you getting?
Click to expand...
Click to collapse
Hello, I understand that it doesn't backup things like sms, I just need the system, data, and boot backed up directly to my PC. By recovery I mean recovery and not fastboot. The adb command works, the device is just not showing up in adb devices, that's why I can't do adb backups, although this feature was implemented in TWRP a couple versions back. What's strange that when I try using adb sideload, the device is detected perfectly fine, which means not a driver problem.
Leaving a picture. First adb devices ran when in main recovery screen, second adb devices ran when in adb sideload mode. (Detected!)
{
"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"
}
punpun1 said:
Hello, I understand that it doesn't backup things like sms, I just need the system, data, and boot backed up directly to my PC. By recovery I mean recovery and not fastboot. The adb command works, the device is just not showing up in adb devices, that's why I can't do adb backups, although this feature was implemented in TWRP a couple versions back. What's strange that when I try using adb sideload, the device is detected perfectly fine, which means not a driver problem.
Leaving a picture. First adb devices ran when in main recovery screen, second adb devices ran when in adb sideload mode. (Detected!)
Click to expand...
Click to collapse
That's not recovery, that's simply adb.
Are you sure you're using the correct command? Read this: https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
I just tried using adb backup with my device and it works fine. You're supposed to do it from within actual ROM itself, not TWRP. So boot into your ROM and try again.
If my upgrade fails, how do I boot from the slot that I installed the crap on the inactive slot from so the phone boots to the old version before the update?
I wanted to know and found the answers. I'll post here in case anyone wants to know cause I found nothing on these forums:
How to Check if Partition Slot A or Slot B is Currently Active?via https://krispitech.com/check-partition-slot-a-b/
Make sure the smartphone is connected to the PC with a USB cable
Now boot the smartphone into Fastboot Mode
This process will vary from device to device but usually involves holding certain button(s) down during the boot cycle.
Open up a Command Prompt, Windows PowerShell, or a Terminal in the same folder as your ADB and Fastboot files
Type out the following command. . .
fastboot getvar all
. . .then press Enter on the keyboard
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device
{
"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"
}
In this instance, my device was currently using partition slot B.
How to Boot from One Active Partition Slot to Anothervia https://krispitech.com/change-active-partition-slot/
Boot the smartphone or tablet into Fastboot Mode
Connect the device to the PC with a USB cable
Open a Command Prompt, PowerShell, or Terminal and type out the following command. . .
fastboot --set-active=a
OR
fastboot --set-active=b and then press Enter on the keyboard
Make sure you get a successful OKAY response before restarting the device
So if my updates go pear-shaped, I should be okay. And if not, well, I'm not buying a OnePlus ever again cause I've had it with all the extra steps, headaches, and disappointments with this model.
Excellent guide, I like it.
Think check out TWRP too, I think ( not 100% ) but I think it can change slots for you too.