Related
I did a CM nightly Update, which relocked my phone. I tried to unlock it but something went wrong. I can flash partitions but somehow can't boot into anything besides fastboot. When I try to boot into any recovery (even Stock) the phone just restarts after showing the Oppo logo for a moment. (Just as if I was trying to boot a custom rom from a locked device)
OEM-Info:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
Booting a recovery.img (Same reaction for every recovery):
Code:
fastboot boot twrp-2.8.7.2-find7.img
downloading 'boot.img'...
OKAY [ 0.355s]
booting...
OKAY [ 0.013s]
finished. total time: 0.368s
Phone Just reboots into a boot loop.
Flashing anything works fine but I'm getting boot loops again.
A strange thing that happens is that if i try
Code:
fastboot oem lock
the process just get's stuck showing three dots. (Same on Windows and Linux) That probably means that the bootloader is in some buggy way half way locked. (That sadly doesn't explains why the stock recovery won't work)
No idea how to fix it. Thank you in advance!
Jakob
Amazing tool here: forum.xda-developers.com/find-7/development/recovery-recovery-installer-7-t2819794
Hey !! I solved the pblm!!! what I did was just hit and trial but it worked. Now I will give the method:
Follow these steps and see if u are lucky enough!
step1: go to fastboot mod in your oppo f1
step2: flash stock recovery using adb. Type in "fastboot flash recovery stock.img"
step3: do not reboot your device and type in "fastboot flashing lock_critical".
step4: type in "fastboot reboot"
After these 4 steps I was able to boot back in Project spectrum. I haven't checked until that if I m able to go to recovery mode but I will update once I check. Check if you can boot.
Note: keep the stock.img file in the same folder in which you have your adb installed.
And I am not sure if this will work for you also.. but it is safe so go give a try!!!
THIS WORKED FOR OPPO F1f YOU CAN TRY YOUR LUCK BY USING THIS METHOD
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
When removing TWRP and flashing my phone back to factory images, I received a size issue on the main image. I then manually flashed each .img using fastboot. Lastly, assuming it was good, I was an idiot and locked the bootloader.
Is there any way to recover from this using adb and sideloading? I have the factory recovery image working, locked bootloader but nothing else. Any help would be greatly appreciated
nvrpunk said:
When removing TWRP and flashing my phone back to factory images, I received a size issue on the main image. I then manually flashed each .img using fastboot. Lastly, assuming it was good, I was an idiot and locked the bootloader.
Is there any way to recover from this using adb and sideloading? I have the factory recovery image working, locked bootloader but nothing else. Any help would be greatly appreciated
Click to expand...
Click to collapse
try to enter bootloader via adb reboot bootloader or key combination and issue fastboot oem unlock.
ulxerker said:
try to enter bootloader via adb reboot bootloader or key combination and issue fastboot oem unlock.
Click to expand...
Click to collapse
This does not work.
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
nvrpunk said:
This does not work.
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
try it with nexus root toolkit
or
download latest OTA image and adb sideload OTA.zip in recovery.
ulxerker said:
try it with nexus root toolkit
or
download latest OTA image and adb sideload OTA.zip in recovery.
Click to expand...
Click to collapse
Thanks, I am going to try the sideload of the OTA.zip And see if that works.
nvrpunk said:
This does not work.
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
I'm curious if you did anything other than what you listed, because Allow OEM unlocking that was set from Developer Options should still be one given what your described actions.
I waked up this morning and checked time on my Pixel XL, about 30 mins after I checked my phone which has been powered off. I tried to power on, it screens off right after the google logo showed on, and loop.
Then I entered bootloader, it shows:
Code:
BL: N/A
Baseband: N/A
Product/Variant: marlin-ROW-PVT
Serial Number: HT69Hxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 128GB Toshiba
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED
My Pixel XL is now on Dec 2016 7.1.1 (NMF26O). I tried to flash bootloader from NMF26O and NMF26U, it failed, showing:
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (32728 KB)...
OKAY [ 0.735s]
writing 'bootloader'...
FAILED (remote: Verify bootloader image failed on production device.)
finished. total time: 1.338s
It can't boot into recovery mode. I tried to temporarily boot into twrp-pixel-installer-marlin-3.0.2-0-RC1 it returns:
Code:
>fastboot boot twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
creating boot image...
creating boot image - 9072640 bytes
downloading 'boot.img'...
OKAY [ 0.240s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.653s
Does anyone here know how to fix this without wipe my data? I have super super important data on my phone.
-------edit--------
I asked a friend who is using Pixel to show me his bootloader info. I noticed his boot-slot is a, mine is b.
Any idea that I can switch the boot-slot back to a? Do you think switching back will work?
ghovik said:
I waked up this morning and checked time on my Pixel XL, about 30 mins after I checked my phone which has been powered off. I tried to power on, it screens off right after the google logo showed on, and loop.
Then I entered bootloader, it shows:
My Pixel XL is now on Dec 2016 7.1.1 (NMF26O). I tried to flash bootloader from NMF26O and NMF26U, it failed, showing:
It can't boot into recovery mode. I tried to temporarily boot into twrp-pixel-installer-marlin-3.0.2-0-RC1 it returns:
Does anyone here know how to fix this without wipe my data? I have super super important data on my phone.
Click to expand...
Click to collapse
So you can at least get into bootloader right? Does "fastboot devices" show your serial?
aholeinthewor1d said:
So you can at least get into bootloader right? Does "fastboot devices" show your serial?
Click to expand...
Click to collapse
Yes I can boot into bootloader, 'fastboot devices' shows my device correctly. But any 'fastboot flash' or 'fastboot root' returns failure. for example, I tried to flash boot.img, returns:
Code:
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (26229 KB)...
OKAY [ 0.611s]
writing 'boot'...
(bootloader) Flashing active slot "_b"
FAILED (remote: flash write failure)
finished. total time: 0.866s
@ghovik,
Try putting it on the charger for a while. I'm not saying your battery is dead, but it sure can't hurt.
Thanks. I have charged it for about 30mins. You remind me of another strange thing, when it is powered off and connected to the charger, the charging battery logo shows up for 1 sec and screens off. It loops for few times and the phone starts booting itself. So I put it into bootloader mode now while charging.
ghovik said:
It can't boot into recovery mode. I tried to temporarily boot into twrp-pixel-installer-marlin-3.0.2-0-RC1 it returns:
>fastboot boot twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
creating boot image...
creating boot image - 9072640 bytes
downloading 'boot.img'...
OKAY [ 0.240s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.653s
Click to expand...
Click to collapse
When you noted that you were trying to boot to TWRP via commands my first expectation was to see a fastboot command like this instead:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
I'm not sure why you are trying to boot the flashable ZIP instead.
^^^ What he said.
Too many links usually means a bad filename or bad path to the file.
muzzy996 said:
When you noted that you were trying to boot to TWRP via commands my first expectation was to see a fastboot command like this instead:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
I'm not sure why you are trying to boot the flashable ZIP instead.
Click to expand...
Click to collapse
Oh this is my fault. Now I tried 'fastboot flash twrp-3.0.2-0-RC1-fastboot-marlin.img', it worked but, first the google logo shows up and immediately screens off, then root loop as the same as I boot my device.
I asked a friend who is using Pixel to show me his bootloader info. I noticed his boot-slot is a, mine is b.
Any idea that I can switch the boot-slot back to a? Do you think switching back will work?
TonikJDK said:
^^^ What he said.
Too many links usually means a bad filename or bad path to the file.
Click to expand...
Click to collapse
muzzy996 said:
When you noted that you were trying to boot to TWRP via commands my first expectation was to see a fastboot command like this instead:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
I'm not sure why you are trying to boot the flashable ZIP instead.
Click to expand...
Click to collapse
cam30era said:
@ghovik,
Try putting it on the charger for a while. I'm not saying your battery is dead, but it sure can't hurt.
Click to expand...
Click to collapse
aholeinthewor1d said:
So you can at least get into bootloader right? Does "fastboot devices" show your serial?
Click to expand...
Click to collapse
I asked a friend who is using Pixel to show me his bootloader info. I noticed his boot-slot is a, mine is b.
Any idea that I can switch the boot-slot back to a? Do you think switching back will work?
ghovik said:
I asked a friend who is using Pixel to show me his bootloader info. I noticed his boot-slot is a, mine is b.
Any idea that I can switch the boot-slot back to a? Do you think switching back will work?
Click to expand...
Click to collapse
Fastboot set_active _a
TonikJDK said:
Fastboot set_active _a
Click to expand...
Click to collapse
It seems this is not a correct command because I tried this commend and it returns the usage help.
ghovik said:
It seems this is not a correct command because I tried this commend and it returns the usage help.
Click to expand...
Click to collapse
It's right. You either typed it wrong or have an older version of fastboot, or are using minimal fastboot.
From mine two seconds ago:
C:\Users\xxx\Desktop\SDK Tools\platform-tools>fastboot set_active _a
Setting current slot to 'a'...
OKAY [ 0.089s]
finished. total time: 0.091s
C:\Users\xxx\Desktop\SDK Tools\platform-tools>
TonikJDK said:
It's right. You either typed it wrong or have an older version of fastboot, or are using minimal fastboot.
From mine two seconds ago:
C:\Users\xxx\Desktop\SDK Tools\platform-tools>fastboot set_active _a
Setting current slot to 'a'...
OKAY [ 0.089s]
finished. total time: 0.091s
C:\Users\xxx\Desktop\SDK Tools\platform-tools>
Click to expand...
Click to collapse
I think you are right. I googled this command, all the websites said the same command as you told. It might be my fastboot version problem. May I ask what version are you using?
ghovik said:
It seems this is not a correct command because I tried this commend and it returns the usage help.
Click to expand...
Click to collapse
Try updating your ADB and fastboot. From here > https://plus.google.com/+ElliottHughes/posts/U3B6H3Sejvv
ghovik said:
I think you are right. I googled this command, all the websites said the same command as you told. It might be my fastboot version problem. May I ask what version are you using?
Click to expand...
Click to collapse
https://developer.android.com/studio/releases/platform-tools.html
@TonikJDK,
FWIW: the link that I posted above allows one to download just ADB and fastboot directly from Google. Tiny little package.
TonikJDK said:
It's right. You either typed it wrong or have an older version of fastboot, or are using minimal fastboot.
From mine two seconds ago:
C:\Users\xxx\Desktop\SDK Tools\platform-tools>fastboot set_active _a
Setting current slot to 'a'...
OKAY [ 0.089s]
finished. total time: 0.091s
C:\Users\xxx\Desktop\SDK Tools\platform-tools>
Click to expand...
Click to collapse
I've installed Minimal Adb and Fastboot just now. I tried the command it returns:
Code:
>fastboot set_active _a
error: Could not get suffixes.
cam30era said:
@TonikJDK,
FWIW: the link that I posted above allows one to download just ADB and fastboot directly from Google. Tiny little package.
Click to expand...
Click to collapse
My link is the link on the page he directs you to. Saves a click.
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
ghovik said:
I've installed Minimal Adb and Fastboot just now. I tried the command it returns:
Code:
>fastboot set_active _a
error: Could not get suffixes.
Click to expand...
Click to collapse
Dang it, stop using Minimal. It is old...from like March of last year. Our Pixels are different...they have dual partitions, they need the newer fastboot and adb.
TonikJDK said:
My link is the link on the page he directs you to. Saves a click.
Click to expand...
Click to collapse
Cool. Thanks.
---------- Post added at 11:38 AM ---------- Previous post was at 11:35 AM ----------
TonikJDK said:
My link is the link on the page he directs you to. Saves a click.
Click to expand...
Click to collapse
Well, all I see is the SDK package (which is a lot smaller than the full Studio). Unless I'm missing something, I don't see any link to just the ADB and fastboot....
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Just a shot in the dark but have you enabled oem unlocking in developer options?
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
no unfortunately not , thats the problem
amans90 said:
no unfortunately not , thats the problem
Click to expand...
Click to collapse
Okay well I hope you can get your phone sorted now , if I've helped then please leave a thumbs up on my post I really appreciate it...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Hi i have the same problem like you did you solve it ?
Dsn Fouad said:
Hi i have the same problem like you did you solve it ?
Click to expand...
Click to collapse
see below.
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Sent from my ONEPLUS A3003 using Tapatalk
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
I dont know i flashed the lastest os and the old with sideload but it stuck on 45%
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
Here
Dsn Fouad said:
Here
Click to expand...
Click to collapse
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Hmm, I thought he said he can enter bootloader and recovery. If so, reboot the phone in stock recovery and flash full Rom from local update.
Sent from my ONEPLUS A3003 using Tapatalk
tnsmani said:
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Click to expand...
Click to collapse
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Dsn Fouad said:
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Click to expand...
Click to collapse
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb and boot.
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
Oh i see now where can i find the lastest recovery and by how i need to flash it, in adb sideload (recovery.img) or fastboot flash recovery (oneplus recovery.img)?
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
I tried again but failed with official oneplus 3 recovery
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
jeffrey268 said:
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Nah it will still fail, all because of that oem and device state locked, lol i buy a new phone used it 1 month i was having a update available i updated it and then boom 370€ gone just like that, it took me 4 month to got it, i just want to kill people now im very depressed right now god bless people like you thanks for your help.
Been asking around for this in multiple threads and have gotten nothing. So I decided to just make a new one. If ANYONE has a backup I can use in order to restore it via TWRP, then PLEASE share it with me. Whether it's a Mate SE backup or an Honor 7x US variant backup, I'll take either.
That makes 2 of us
Any ideas why I can't seem to boot a recovery? Used to do this all the time in the Motorola world:
~/Downloads/Huawei$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
~/Downloads/Huawei$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.711s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.714s
chrisn812 said:
Any ideas why I can't seem to boot a recovery? Used to do this all the time in the Motorola world:
~/Downloads/Huawei$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
~/Downloads/Huawei$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.711s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.714s
Click to expand...
Click to collapse
Can you not use the hardware keys to get into the recovery? Also, what is the status of the recovery partition? Alive and well?
XandeR180 said:
Been asking around for this in multiple threads and have gotten nothing. So I decided to just make a new one. If ANYONE has a backup I can use in order to restore it via TWRP, then PLEASE share it with me. Whether it's a Mate SE backup or an Honor 7x US variant backup, I'll take either.
Click to expand...
Click to collapse
I am wiping my wifes phone today and I will do a clean backup via twrp and upload it to drive later today for ya
Ultraman666 said:
I am wiping my wifes phone today and I will do a clean backup via twrp and upload it to drive later today for ya
Click to expand...
Click to collapse
Thank you so much
XandeR180 said:
Thank you so much
Click to expand...
Click to collapse
Ok man here you go, hope this helps!! Its the least I can do since you helped me with all my questions
https://drive.google.com/open?id=1X2oB98XYngybIZpPPc7B51VMW8ID6F1c
chrisn812 said:
Any ideas why I can't seem to boot a recovery? Used to do this all the time in the Motorola world:
~/Downloads/Huawei$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
~/Downloads/Huawei$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.711s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.714s
Click to expand...
Click to collapse
1-first got to fastboot mode in phone(vol down+ power) then connect phone to pc doesn't matter if the hisuite pops up in pc or not.
2-after connecting open adb shell from the directory where you have installed it in your pc(go to the folder and press shift+ right click of mouse then select open command prompt option).
3- type - fastboot devices , if some number appears then it confirms that the device is connected, if it doesn't appear then close everything in pc and disconnected your phone then power off the phone and then connect it to pc then open adb and type adb reboot bootloader - this should restart your phone into fastboot mode.
chrisn812 said:
Any ideas why I can't seem to boot a recovery? Used to do this all the time in the Motorola world:
~/Downloads/Huawei$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.711s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.714s
Click to expand...
Click to collapse
It doesn't look like this is supported (at least not on MY L24 variant). I don't know if the mount points are identical from one variant to another but they are posted here: https://forum.xda-developers.com/honor-7x/development/mount-partition-layout-profile-xml-t3727990 (Nougat) and https://forum.xda-developers.com/honor-7x/development/mount-partition-layout-oreo-t3764506 (Oreo). (The TWRP versions in the Multitool are from the OP of these two threads.) And some other posts showed the adb shell commands (and batch file) to backup stock recovery to the external SD card. I think for Nougat, they are:
Code:
dd if=/dev/block/mmcblk0p29 of=/external_sd/recovery.img
dd if=/dev/block/mmcblk0p22 of=/external_sd/recovery2.img
Stock recovery for the L24(?) can also be found in one of the threads here. And finally, the 7X has dual recovery so I ended up flashing TWRP to eRecovery (fastboot flash recovery2 TWRP.img) leaving the stock recovery in recovery1 for OTA updates. Then I use "adb reboot recovery2" whenever I need TWRP.
XandeR180 said:
Thank you so much
Click to expand...
Click to collapse
So did that work for you?
Ultraman666 said:
So did that work for you?
Click to expand...
Click to collapse
For the most part, yeah. Booted up and everything but for some reason I couldn't install Magisk ?
XandeR180 said:
For the most part, yeah. Booted up and everything but for some reason I couldn't install Magisk ?
Click to expand...
Click to collapse
FYI, I installed supersu from https://forum.xda-developers.com/honor-7x/how-to/how-to-root-honor-7x-international-t3716056 using the TWRP from MultiTool on my L24 and it appears to be working okay.
iammudd said:
FYI, I installed supersu from https://forum.xda-developers.com/honor-7x/how-to/how-to-root-honor-7x-international-t3716056 using the TWRP from MultiTool on my L24 and it appears to be working okay.
Click to expand...
Click to collapse
Hmm. I'm more of a fan of Magisk, personally but I'll try SuperSU
XandeR180 said:
For the most part, yeah. Booted up and everything but for some reason I couldn't install Magisk ?
Click to expand...
Click to collapse
Sweet glad to help!!
Didnt work on my SE L34. Still boots into EMUI eRecovery. Oh well. I'll wait a bit longer.
I had to overwrite the recovery2 partition with TWRP to do it, but here's an almost complete backup of the stock firmware for my Mate SE: BND-L34C567B130.zip
Magendanz said:
I had to overwrite the recovery2 partition with TWRP to do it, but here's an almost complete backup of the stock firmware for my Mate SE: BND-L34C567B130.zip
Click to expand...
Click to collapse
By almost complete, what exactly is it missing?
XandeR180 said:
By almost complete, what exactly is it missing?
Click to expand...
Click to collapse
The original contents of the recovery2 partition, which had to be overwritten with TWRP to do the backup. I believe it was identical to the recovery partition, but I was never able to confirm.
Magendanz said:
The original contents of the recovery2 partition, which had to be overwritten with TWRP to do the backup. I believe it was identical to the recovery partition, but I was never able to confirm.
Click to expand...
Click to collapse
Pretty sure it is. I'd flashed the same honor 7x stock recovery image for both my partitions in the past. Regardless, both my partitions use TWRP at the moment, so this doesn't bother me. Thanks a ton!
Magendanz said:
The original contents of the recovery2 partition, which had to be overwritten with TWRP to do the backup. I believe it was identical to the recovery partition, but I was never able to confirm.
Click to expand...
Click to collapse
So restoring your backup was successful. However, for some reason the updater is completely missing. Therefore, I can't check for updates anymore. Also, in the "About Phone" section at the bottom it says, "Custom Version - CUSTC567D001" which I don't recall ever seeing before. Does this have to do with your recovery partitions being modified?