Hello! I have a model plk-l01, with emui 3.1,, b140 version. I had rooted with kingroot app. Then I had installed flashify app, and tried to flash twrp recovery. Bad decision. Now when I want to reboot in recovery mode, on the screen appears that : rescue mode. Please update system again. Error Func no 11(recovery image) func no 2 (load failed).
I tried to reflash stock recovery through fastboot, but no chance. (it says ok, but after :command not allow). I tried with dlload method, but returned into that error. I tried to flash twrp with fastboot, but same error. So, my phone works well, but no recovery. I have no possibility to update to marshmallow... Please help if you can. Cheers!
Related
I have my Note 2 with TWRP and CM 12.1.
How can I restore my phone to normal Recovery (Mi-Recovery 2.0.1) and the stock ROM (7.5.1.0)?
I was able to remove the TWRP and restore the Mi-Recovery 2.0.1, but now on PC I don't see the device to add content to it.
Using MiPCSuite in Mi-Recovery mode give me "Reading device information failed"
Using MiPCSuite in FastBoot mode give me the chance to update, but I receive the message "Couldn't flash device"
Some help will be appreciated,
Thanks!
ALL-RS said:
I have my Note 2 with TWRP and CM 12.1.
How can I restore my phone to normal Recovery (Mi-Recovery 2.0.1) and the stock ROM (7.5.1.0)?
I was able to remove the TWRP and restore the Mi-Recovery 2.0.1, but now on PC I don't see the device to add content to it.
Using MiPCSuite in Mi-Recovery mode give me "Reading device information failed"
Using MiPCSuite in FastBoot mode give me the chance to update, but I receive the message "Couldn't flash device"
Some help will be appreciated,
Thanks!
Click to expand...
Click to collapse
Reinstall TWRP recovery, and flash stock rom via it and then just restore MI-recovery.
http://en.miui.com/download-274.html here you can download rom
Hi all,
Currently I'm on B371
I unlocked my bootloader, flash with TWRP 2.8.7.0 and then try to install SuperSU. After reboot my phone, it goes to permament bootloop.
When I'm in TWRP mode, phone memory is visible by my PC. When it's in bootloop and Honor logo is visible I can install HiSuite on my PC from phone and it's also visible by "adb devices".
What can I do to retrieve my phone?
Thanks for any help.
Flash this, it's the root package from WBT, I've got the same probleme after rooting on B371 and then I flashed this file, it fixed the problem.
https://drive.google.com/file/d/0B3O4DzQkXNR4aFoxbXk5cmZPRlE/view?pref=2&pli=1
Or you can flash your stock recovery.img with "fastboot flash recovery recovery.img" command in rescue(bootloader) mode. And after that you can install your B371 rom again by 3 button way. If you want to root again, use TWRP 3.0.2 and SuperSU 2.62.
Thanks! I used Nexx_ method. It works. If I can ask, what is WTB?
Zdzisiek89 said:
Thanks! I used Nexx_ method. It works. If I can ask, what is WTB?
Click to expand...
Click to collapse
Hi
WBT=WarriorBootloopTeam
From french site : Phonandroid.fr
You can find our roms in Honor 7 Android Development Section
Thank you experts
May I ask, how many members are there in WarriorBootloopTeam?
Hi friends,
So here's a thing:
I was trying to update my Nexus 9 to the latest Slimrom build , and I used Chainfire's flashfire app. It didn't work and sent the tablet in a boot loop. But it also wiped my recovery so I couldn't even select my recovery.
So no issues, I used the Wugfresh nexus toolkit to flash it back to stock and unroot. Bootloader is still unlocked, so I just root it again and go ahead and try to install the update using Wugfresh. It works, but says the vendor.img is wrong. So I downloaded the correct vendor.img and tried to flash it, but of course because the tablet is encrypted TWRP asked for a password. I hit cancel and tried to continue, but Wugfresh just hung at that step.
So I tried to manually flash the ROM, but now it gives me a vendor.img error and will not flash anything. Trying to flash anything sends the device in a bootloop.
TLDR; I can restore to stock and root, and also access the bootloader and recovery (TWRP) but can't flash anything without sending the device in a bootloop.
I've currently restored the tablet to stock via wugfresh's tool and rooted. So I'm back at the beginning, except with this vendor.img issue when I'm trying to flash a ROM.
Anyone have any ideas?
Hi, I am using P600 (note 10.1 2014 Wifi) XAR one
Yesterday I was trying to install magisk all day, but failed all
When I rooted device and instaled TWRP, in TWRP it made error number 1 and it says something like turn to stock boot, so I tried to reinstall stock firmware via Odin, but it didn’t change anything.
I guess it’s a problem with boot.img or the autoroot method I used.
So I tried to use fastboot to install TWRP without rooting, but this time it didn’t boot into bootloader from fastboot, it just restarted the tablet all the time.
So I tried to manually reboot into the download mode, but fastboot didn’t recognize the device then.
When I did it, I turnned on the USB debugging with no mistake since it’s just samsung.
So I booted into recovery mode(It can go into recovery mode without problem)
Then tried option “reboot to boorloader” and it just restarts the tablet again.
I guess something corrupted boot.img or bootloader somehow, while I was rooting or something.
Can I get factory boot.img and solve it? Or when I install stock firmware via Odin does it also fix boot.img and boot loader?
I tried to install stock firmwares and factory reset several times. It didn’t help anything. It did unroot or turn the recovery to stock recovery, but couldn’t get into bootloader.
Can anyone please help me or give me advice to solve this problem?
Bump
I have used king root app, and flashify to flash twrp recovery so i can root with magisk .
After i flashed twrp ,and tried to enter into recovery i get :
security error: this phone has been flashed with unauthorized software
Primary i have used the twrp app to make a back twrp image ,the app itself failed flashing it ,and after ,, success" from flashify i still have the error.
PS: i have developers opinions and OEM turned on .
_________________'_________________
I have find out that my bootloader is locked and that was the reason for the error