I was trying to use twrp in my device to install a custom ROM, but when after flashing it i cant boot into it, i used sp flash tool and it does not recognise my device.
when booting through cmd i get this error:
{
"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"
}
this is the error that i get, i have unlocked bootloader
this might be useful to you guys i guess:
so please help me guys.
keep holding Volume Up while rebooting. do not release until you successfully entered TWRP recovery
Code:
fastboot flash recovery TWRP_lenovotb_7304f-030818.img
fastboot reboot
https://forum.xda-developers.com/t/...l-tb-7304f-hard-bricked.3934944/post-81607437
aIecxs said:
keep holding Volume Up while rebooting. do not release until you successfully entered TWRP recovery
Code:
fastboot flash recovery TWRP_lenovotb_7304f-030818.img
fastboot reboot
https://forum.xda-developers.com/t/...l-tb-7304f-hard-bricked.3934944/post-81607437
Click to expand...
Click to collapse
it doesnt works, held volume up just after i typed the command and brought me back to boot modes. there are 3 modes there: recovery mode, fastboot mode and normal mode.
selecting recovery mode would just show a android robot saying no command.
recovery mode is the right option. the no command screen is half way to stock recovery, flash twrp again. on the no command screen, press Power + Volume Up again to continue into recovery
aIecxs said:
the no command screen is stock recovery, flash twrp again
Click to expand...
Click to collapse
so i keep flashing until it happens?
aIecxs said:
the no command screen is stock recovery, flash twrp again
Click to expand...
Click to collapse
but it doesnt even boot into recovery now just boots into normal mode when selecting recovery mode. (only when connected to pc) but when removed from pc it boots into recovery mode and doesnt connect back to pc so fastboot command shows waiting for device.
What does the "no command" screen mean? (Trying to execute hard reset Recovery)
"The No Command screen means recovery checked the normal area (/cache) for an update file, like an OTA, and it didn't find one, so it had 'No Command' to execute. Androids stock recovery is intended for the normal, everyday user, giving them a menu they could easily access could cause lots of potentially angry people who are just playing around and reset their device by accident. Stock recovery, and its menu, are specifically engineered so that you have to take special steps to do anything. The No Command screen, meaning no automated script, is part of that safe guard."
source @acejavelin
aIecxs said:
What does the "no command" screen mean? (Trying to execute hard reset Recovery)
"The No Command screen means recovery checked the normal area (/cache) for an update file, like an OTA, and it didn't find one, so it had 'No Command' to execute. Androids stock recovery is intended for the normal, everyday user, giving them a menu they could easily access could cause lots of potentially angry people who are just playing around and reset their device by accident. Stock recovery, and its menu, are specifically engineered so that you have to take special steps to do anything. The No Command screen, meaning no automated script, is part of that safe guard."
source @acejavelin
Click to expand...
Click to collapse
ok, now i understood about the recovery menu, so to access the twrp recovery i would need to delete stock recovery i guess, but it would in turn brick my device so that just means i cant root my device, still going into root checker it says root availability is yes but it is hard to do it. so now im stuck on a roadblock...
no need to delete stock recovery, it's opposite. you're just not booting straight into recovery right after flashing, so twrp recovery got deleted:
aIecxs said:
(if you accidentially boot into android, twrp is gone, reflash and try again)
Click to expand...
Click to collapse
actually there are three different methods to root that device (I have linked) it's even possible on locked bootloader
your bootloader is unlocked already, so using fastboot is safest and most straightforward method
aIecxs said:
no need to delete stock recovery, it's opposite. you're just not booting straight into recovery right after flashing, so twrp recovery got deleted:
actually there are three different methods to root that device (I have linked) it's even possible on locked bootloader
your bootloader is unlocked already, so using fastboot is safest and most straightforward method
Click to expand...
Click to collapse
THERE ARE 3 METHODS!!!?? so ill just do the thing and see what happens.
VoxPlays08 said:
so ill just do the thing and see what happens.
Click to expand...
Click to collapse
This is exactly how people brick their devices. You must not do anything without understanding what you're doing...
why not just repeat post #2
aIecxs said:
This is exactly how people brick their devices. You must not do anything without understanding what you're doing...
why not just repeat post #2
Click to expand...
Click to collapse
Ok I'll reply if anything happens
maybe repeat download and make sure checksum matches?
Code:
certutil.exe -hashfile TWRP_lenovotb_7304f-030818.img MD5
bcb6aa10333edd89054f3bddca7abbdc
aIecxs said:
maybe repeat download and make sure checksum matches?
Code:
certutil.exe -hashfile TWRP_lenovotb_7304f-030818.img MD5
bcb6aa10333edd89054f3bddca7abbdc
Click to expand...
Click to collapse
checksum matches exactly
so flash it from fastboot and keep holding Volume Up while rebooting, select recovery mode
Im at the exact same spot, I can do the "fastboot flash recovery" but when rebooting, no matter what I press (when reboot) it always go to fastboot or normal boot..
the fastboot says its flashed ok in recovery, but I guess its overwritten when booting..
Stuck here..
If I choose recovery in fastboot using the Lenovo recovery and from there trying to flash with adb and 18.1 it erros out after 40% isch
I can use it but.. old.. and work wifi blocks me cuzzits old.
Related
Hi!
I'n kinda new to XDA but anyway.. Im running CM7 and have a HTC Legend. Last week I was stupid enough and tried to update Superuser from Rom Manager and the result? Superuser wont open anymore.. It always force closes and I have lost my root access. I cant even get in to CWM
What am I going to do?
Please help me!
Easiest thing to do would do a restore from a nandroid backup. If you don't have one, then download a pre-rooted stock rom, or another rom. Hope this helps.
RQ7 said:
Hi!
I'n kinda new to XDA but anyway.. Im running CM7 and have a HTC Legend. Last week I was stupid enough and tried to update Superuser from Rom Manager and the result? Superuser wont open anymore.. It always force closes and I have lost my root access. I cant even get in to CWM
What am I going to do?
Please help me!
Click to expand...
Click to collapse
Simiply reboot into recovery, and reflash superuser. You can get it here: http://goo.im/superuser/Superuser-3.0.7-efghi-signed.zip.
Theonew said:
Simiply reboot into recovery, and reflash superuser. You can get it here: http://goo.im/superuser/Superuser-3.0.7-efghi-signed.zip.
Click to expand...
Click to collapse
How do I reboot into recovery ? Should I rename it update.zip or what?
Thnx for replies.
Press Power and selecPress down on the Trackball, hold Volume Down & the Power button until the device boots to the bootloader. Once in the bootloader, use Volume Down to select "recovery" and press the Power button and select reboot -recovery.
Or turn your phone off and:
Press down on the Trackball, hold Volume Down & the Power button until the device boots to the bootloader. Once in the bootloader, use Volume Down to select "recovery" and press the Power button to select.
Then you select install zip from sd and select the superuser zip.
i'm_ever_dreaming said:
Press Power and selecPress down on the Trackball, hold Volume Down & the Power button until the device boots to the bootloader. Once in the bootloader, use Volume Down to select "recovery" and press the Power button and select reboot -recovery.
Or turn your phone off and:
Press down on the Trackball, hold Volume Down & the Power button until the device boots to the bootloader. Once in the bootloader, use Volume Down to select "recovery" and press the Power button to select.
Then you select install zip from sd and select the superuser zip.
Click to expand...
Click to collapse
Thnx for helping but when im in this recovery, it only says " Apply SD Card: Update.zip " i cant choose Superuser
Can you take a photo?
i'm_ever_dreaming said:
Can you take a photo?
Click to expand...
Click to collapse
Here is a picture. This is as far as I can reach.. I cant choose Superuser, only update.zip..
{
"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 know a solution for LG phones but not for HTC, sorry.
You can flash(install) CWM in the bootloader, but i don't know how...
Edit: I'm not sure: Don't do it before someone says that this is correct.
I have no experience with fastboot, just with recovery etc.
You must go into the bootloader, connect your phone to the computer and open terminal, write
fastboot flash recovery (here you must write the name of the image, that must be on the computer in the same folder as fastboot[where you installed android sdk)
RQ7 said:
Here is a picture. This is as far as I can reach.. I cant choose Superuser, only update.zip..
Click to expand...
Click to collapse
Ok, that is the stock recovery. An easy way is to use this tool: http://forum.xda-developers.com/showthread.php?t=794638, flash CWM recovery, then boot into CWM recovery and flash superuser (you do not have to rename it).
Theonew said:
Ok, that is the stock recovery. An easy way is to use this tool: http://forum.xda-developers.com/showthread.php?t=794638, flash CWM recovery, then boot into CWM recovery and flash superuser (you do not have to rename it).
Click to expand...
Click to collapse
Does it work with HTC Legend?
Yes, i know, that this is stock...
Try it, install the tool and flash this image(attachment) if you could select your device.
Sorry, that was the wrong file - removed - now it's the right file
Theonew said:
Ok, that is the stock recovery. An easy way is to use this tool: http://forum.xda-developers.com/showthread.php?t=794638, flash CWM recovery, then boot into CWM recovery and flash superuser (you do not have to rename it).
Click to expand...
Click to collapse
I downloaded the tool but it wont open.. I tried on my Mac and XP but it wont open.. Always gives an error
Do you know how to work with adb?
Edit: Have you tried to root your phone again?
i'm_ever_dreaming said:
Do you know how to work with adb?
Edit: Have you tried to root your phone again?
Click to expand...
Click to collapse
I know how adb works but it's been a while so I think I dont remember it... I havent tried to root again cuz im to lazy for that
RQ7 said:
I downloaded the tool but it wont open.. I tried on my Mac and XP but it wont open.. Always gives an error
Click to expand...
Click to collapse
RQ7 said:
I know how adb works but it's been a while so I think I dont remember it... I havent tried to root again cuz im to lazy for that
Click to expand...
Click to collapse
Ok. Boot your device into fastboot. Then do:
Code:
fastboot flash recovery recovery.img
If you are using this exact command, make sure you rename the recovery to "recovery.img".
i'm_ever_dreaming said:
You must go into fastboot, connect your phone to the computer and open terminal, write
fastboot flash recovery (here you must write the name of the image(recovery-clockwork-5.0.2.0-legend.img, that must be on the computer in the same folder as fastboot[where you installed android sdk)
Click to expand...
Click to collapse
This is the same...
i'm_ever_dreaming said:
This is the same...
Click to expand...
Click to collapse
You said "bootloader" but he needs to boot into "fastboot".
i'm_ever_dreaming said:
This is the same...
Click to expand...
Click to collapse
Theonew said:
You said "bootloader" but he needs to boot into "fastboot".
Click to expand...
Click to collapse
Hi again and thnak you for helping me out. I have one little problem left then its all solved... when im in terminal, it says " error: cannot load "recovery.img" .. what am i supposed to do
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
Click to expand...
Click to collapse
You must write "the name of the image.img" instead of recovery.img
Or you have to rename it.
I've seen online people flashing su from stock recovery ..I've rooted and rommed one of these b4 simply wondering if there is a new simple root for this?
dovedescent7 said:
I've seen online people flashing su from stock recovery ..I've rooted and rommed one of these b4 simply wondering if there is a new simple root for this?
Click to expand...
Click to collapse
No not from stock recovery but you don't have to flash a recovery you can just boot once to twrp leaving your stock recovery in place. Just follow the instuctions to install TWRP via fastboot but instead of flashing it with the line
fastboot flash recovery recovery.img
just boot to it with
fastboot boot recovery.img
once booted to it you don't even have to flash anything just select REBOOT SYSYEM and TWRP will detect you are not rooted and ask you to swipe to root on its way out.
MiniBlu
Hey thanks man! I guess my main concern was having to go through HTC's online rigamarole all over again. What a nightmare..
If I recall correctly last time I did this every time I booted its stated my firmware was developmental or some sort of error message will simply booting TWRP once and rooting it cause that weird message to come up everytime I boot?
dovedescent7 said:
Hey thanks man! I guess my main concern was having to go through HTC's online rigamarole all over again. What a nightmare..
If I recall correctly last time I did this every time I booted its stated my firmware was developmental or some sort of error message will simply booting TWRP once and rooting it cause that weird message to come up everytime I boot?
Click to expand...
Click to collapse
no it won't. The red text will appear when you boot to TWRP via fastboot but nothing permenant is changed as nothing is being flashed it is just loading twrp into memory.
TWRP boot.img causes red text when booting as hboot detects it as a development build and overlays the red text. Same goes for JMZ boot.img .
If you want to disable the system write protection while keeping you stock kernel(no red text) I have compiled a loadable module to achieve this on stock kernels. It is tested on stock eu and stock asia but is untested for at&t yet.
MiniBlu
Okay so this is the weirdest thing.
Something is literally preventing me from getting in the fast boot. I've done this a million times and its not working for this device I use different computers ran from command prompt installed uninstalled and reinstalled HTC drivers major developer options and unknown sources and debug mode and absolutely nothing will get this in the fast boot. Different versions of Windows even... Wth
Fyi I haven't unlocked the bootloader. Running 4.4 on at&t desire 610 goPhone..
The strange thing is Windows is recognizing it and I can get into the files and it recognizes ADB drivers but I keep getting an error that device is not found..... Trust me, # I've installed Usb drivers!
dovedescent7 said:
Okay so this is the weirdest thing.
Something is literally preventing me from getting in the fast boot. I've done this a million times and its not working for this device I use different computers ran from command prompt installed uninstalled and reinstalled HTC drivers major developer options and unknown sources and debug mode and absolutely nothing will get this in the fast boot. Different versions of Windows even... Wth
Fyi I haven't unlocked the bootloader. Running 4.4 on at&t desire 610 goPhone..
The strange thing is Windows is recognizing it and I can get into the files and it recognizes ADB drivers but I keep getting an error that device is not found..... Trust me, # I've installed Usb drivers!
Click to expand...
Click to collapse
What version of adb fastboot do you have. In your adb fastboot folder run "adb version" to check. It should be "1.0.31" any older than that and you will need to update your adb and fastboot or you will have problems. If thats ok then boot phone normaly and ensure adb is enabled in developer settings and do "adb devices". If you device shows up as connected then run "adb reboot bootloader" to enter fastboot mode. Once phone has rebooted run "fastboot devices" to check if it can connect.
Hope this helps
MiniBlu
bump
MiniBlu said:
What version of adb fastboot do you have. In your adb fastboot folder run "adb version" to check. It should be "1.0.31" any older than that and you will need to update your adb and fastboot or you will have problems. If thats ok then boot phone normaly and ensure adb is enabled in developer settings and do "adb devices". If you device shows up as connected then run "adb reboot bootloader" to enter fastboot mode. Once phone has rebooted run "fastboot devices" to check if it can connect.
Hope this helps
MiniBlu
Click to expand...
Click to collapse
maybe you have a different variant but ive done everything with my at&t gophone desire 610 from BB which is locked fyi, have not gone through htc unlocking because i may in fact want to return this phone not sure if i like it.
ive got the newest adb ive even downloaded newest sdk toolkit, windroid, NOTHING will get me past this.. This will not allow boot twrp
ive got usb drivers, developer options,usb debugging.. ive done everything besides unlock BL
which variant of the 610 do you have which allows for twrp boot????
{
"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"
}
dovedescent7 said:
maybe you have a different variant but ive done everything with my at&t gophone desire 610 from BB which is locked fyi, have not gone through htc unlocking because i may in fact want to return this phone not sure if i like it.
ive got the newest adb ive even downloaded newest sdk toolkit, windroid, NOTHING will get me past this.. This will not allow boot twrp
ive got usb drivers, developer options,usb debugging.. ive done everything besides unlock BL
which variant of the 610 do you have which allows for twrp boot????
Click to expand...
Click to collapse
You still need to unlock your bootloader for this to work. It just means that you can keep your stock recovery and kernel which makes returning to stock to accept OTA updates or flash RUU easier. If done this way you just
- unlock bootloader
-boot to twrp
-use twrp to backup system partition to ext sd
-let twrp root on way out
then to return to stock
-boot to twrp
-restore system backup
-exit twrp saying no to rooting on the way out
-lock bootloader (fastboot oem lock)
Sorry for any confusion but from your original question I thought you just wanted to keep stock recovery.
MiniBlu
I just installed TWRP and after flashing SuperSU I couldn't get out of recovery anymore. On every restart the phone booted in recovery.
I decided to flash the stock recovery again. After I did that I got into rescue mode. I can not do anything anymore in there. No fastboot, no adb.
It just points to zh.ui.vmall.com/emotiondownload.php?mod=restore but in this list there is no download for the Honor 7.
Error messages are:
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
{
"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"
}
What can I do?
try to reboot on bootloader mode with volumes button combination
Doesn't work. I keep getting to this screen.
It looks like the bootloader but I guess it can not load the recovery.
Also fastboot does not work there.
I think i found the way
Hi-Suite installed on the PC. Phone off, connected to PC, press and hold Vol + and Power until the appearance of recovery.
Options available:
Reboot
Download the package
Switch off
Bootloader Mode (aka Fastboot):
Phone off, connected to the PC, press and hold Vol - Power up and appearance of the screen with the droid.
Or
Phone off, disconnected from the PC, press and hold Vol - and while holding down, connect to the PC.
Thanks for the help.
I can't get into recovery that way. When i press vol up + power I get into this screen again because recovery could not be loaded.
Unfortunately i don't think if there is a another way,,, contact with huawei
Try rumrunner on pc to get into fast boot mode.
Immediately close rum runner screen when it starts rebooting
sent with Huggzzz from my modded, non-OC'ed, very fast running S-Off ADR6425LVM on CyanogenMod 11 20150805 Rom with Tapatalk
etticat said:
I just installed TWRP and after flashing SuperSU I couldn't get out of recovery anymore. On every restart the phone booted in recovery.
I decided to flash the stock recovery again. After I did that I got into rescue mode. I can not do anything anymore in there. No fastboot, no adb.
It just points to zh.ui.vmall.com/emotiondownload.php?mod=restore but in this list there is no download for the Honor 7.
Error messages are:
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
What can I do?
Click to expand...
Click to collapse
Assuming that you have bootloader unlocked and adb debugging enabled. Otherwise, I guess, you're out of luck.
Extract RECOVERY.img of respective ROM you have installed using this method: http://forum.xda-developers.com/showthread.php?t=2433454. Copy dload of the same ROM to the root of sd card and insert it. Now turn off the phone and boot into fastbboot (bootloader): conect it turned off with usb to the pc, where you have drivers and platform tools installed. Then press and hold volume down and power on simultaneously as long as needed to boot to fastboot.
After that install previously extracted RECOVERY.img ([Guide]How to root Honor 7). Boot the system, enable adb debugging, go to settings-Updater-Local update and flash the ROM from dload.
Then you may flash custom recovery, replace the ROM, but never again without making nandroid first.
ǀcey said:
Try rumrunner on pc to get into fast boot mode.
Immediately close rum runner screen when it starts rebooting
sent with Huggzzz from my modded, non-OC'ed, very fast running S-Off ADR6425LVM on CyanogenMod 11 20150805 Rom with Tapatalk
Click to expand...
Click to collapse
Isn't rumrunner just for HTC?
Yea it probably is just for the resound. Idk.
I'm noob at all this.
What I do know is although my PC could see the phone perfectly before I tried to s-off. That once phone entered into never-ending boots the PC couldn't see the phone anymore. Hence I couldn't use abd or fastboot on the PC nor would the phone enter hboot, fastboot, + recovery on its own.
Somehow re-running rumrunner it was able to force the PC to see it enough to allow the phone to be forced into fastboot mode and that saved my poor phone.
At this point I think u [email protected] nuthin more to lose with trying it out. I hate to say that i'm sry.
In the least go read my post there maybe it's enough to help u to figure out how to undo what happened to yours.
If you do try to use rumrunner
Have phone powered on while hooked to PC
Say Yes twice in rumrunner
Rumrunner will try to selfupdate
Then it will try to force the phone to reboot
Watch phone screen..if it goes black
Immediately close rumrunner window on PC at that point.
We don't want rumrunner trying to s-off ur honor lol no and it will try soon as phone goes in fastbootmode. Keep phone plugged in PC.
If successful now load adb or whatever u need on pc
---------- Post added at 12:58 AM ---------- Previous post was at 12:57 AM ----------
http://forum.xda-developers.com/showpost.php?p=63595063&postcount=193
ooooo
فرستاده شده از HUAWEI Y330-U11ِ من با Tapatalk
hello.
i have a plk-l01 with stock 5.0.2 and stock recovery.
with multi-tool twrp and root flashed, than i would like to flash modaco rom v4.1 (MM)
now i have by booting "honor" logo and under powered by android.
i have flashed another custom rom (yoda 7.0) but is the same.
with stock recovery can´t flash any rom, while by 5% come error.
what methode will work to flash any rom or stock rom back to phone?
thanks
helpppp
Lefteris Fragiadakis (Frago) said:
try to reboot on bootloader mode with volumes button combination
Click to expand...
Click to collapse
i have same problem but i can access fastboot . i have downloaded stock rom in my pc is there anyway to flash stock rom from adb?
kosmoo said:
hello.
i have a plk-l01 with stock 5.0.2 and stock recovery.
with multi-tool twrp and root flashed, than i would like to flash modaco rom v4.1 (MM)
now i have by booting "honor" logo and under powered by android.
i have flashed another custom rom (yoda 7.0) but is the same.
with stock recovery can´t flash any rom, while by 5% come error.
what methode will work to flash any rom or stock rom back to phone?
thanks
Click to expand...
Click to collapse
You must flash the rom with twrp after wipe system, cache, data.
To install MM the basic version was to be the B330.
Now you have to reinstall the stock recovery and flash the rom complete B330 through the three button.
Inviato dal mio PLK-L01 utilizzando Tapatalk
AleAndroid96 said:
You must flash the rom with twrp after wipe system, cache, data.
To install MM the basic version was to be the B330.
Now you have to reinstall the stock recovery and flash the rom complete B330 through the three button.
Inviato dal mio PLK-L01 utilizzando Tapatalk
Click to expand...
Click to collapse
this method was good, thanks!
now have a stock recovery with stock b330 rom.
thanks
You can root it with twrp-3.0.2-0-plank.img and SuperSU 2.62
YOUTUBE /watch?v=eDyxj6C8eW8
etticat said:
I just installed TWRP and after flashing SuperSU I couldn't get out of recovery anymore. On every restart the phone booted in recovery.
I decided to flash the stock recovery again. After I did that I got into rescue mode. I can not do anything anymore in there. No fastboot, no adb.
It just points to zh.ui.vmall.com/emotiondownload.php?mod=restore but in this list there is no download for the Honor 7.
Error messages are:
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
What can I do?
Click to expand...
Click to collapse
dude, i hope you fixed you issue... i had the same problem just now... all normal until i installed a new version of supersu (2.7.4 i think) and i wiped the cache and dalvic cache (caused problems everytime) after that i couldnt boot the system, error 10 and 2 i think (boot and system).
Then, after the whole day was over and i didnt find a fix for my problem (my twrp worked) i backed up everything and then installed the original recovery i got some time ago from huawaiextractor, but it got worser. did the same like you, every damned step xD now i understood what you were talking about, before i didnt understand what you said...
so when i boot, it says error 10 ans 2 and when i want to start recovery it says 11 and 2 (recovery and boot).
i dont know why usb debugging didnt worked and why i coulnt use fastboot and adb like everytime. i once fixed a similar issue with the honor multitool and adb and fastboot.
Only thing i can do is connect it to my pc and hisuite, then a new menu shows where u can download a package or update, but it says failed everytime when i use it.
So what did you do with your bricked phone?
I had the same problems (errors) I managed to find a solution. Just extract boot.img cust.img repair.img system.img with huawei extractor. Than just make a full cache wipe. Flash this four .img and love your fully working, totally wiped, almost brand new phone!
PS you should find a way to use fastboot!! There is no other way!
ǀcey said:
Try rumrunner on pc to get into fast boot mode.
Immediately close rum runner screen when it starts rebooting
sent with Huggzzz from my modded, non-OC'ed, very fast running S-Off ADR6425LVM on CyanogenMod 11 20150805 Rom with Tapatalk
Click to expand...
Click to collapse
How did you do please ? i can't enter to fastboot mode too
can you help me please ?
etticat said:
I just installed TWRP and after flashing SuperSU I couldn't get out of recovery anymore. On every restart the phone booted in recovery.
What can I do?
Click to expand...
Click to collapse
With a stock boot.img sometimes you'll end up in bootloop like yourself. If you are still having issues follow below steps.
Boot into bootloader mode, if its looping very fast, then press and hold Vol DOWN button once the screen gets blank after a loop and simultaneously connect to PC, you'll land in bootloader mode.
Once in bootloader mode, flash system.img of your respective previous firmware, in your case just flashing system.img will do.
After doing that you can enter into system again. If you want you also can flash the whole UPDATE.APP package by three button combo
I hope this helps someone.
Will there be a TWRP version compatible with oxygen os V14 currently running on European Nord 2?
I tried previous TWRP guides for the Nord 2 but it didn't work.
Recovery OS's like TWRP works with all versions of the nord2 regardless of the update version.
More than likely you didn't follow all steps correctly. There are multiple mistakes you can make which results in the stock recovery OS being reflashed and the TWRP recovery being overwritten; I'm not completely sure of all the scenarios in which this happens, but you definitely made a miss-step somewhere.
I'm also running an EU nord variant with V14 and TWRP works fine, I've just noticed that after a few reboots TWRP partition gets overwritten by the stock OS again, in which case I just simply reflash the TWRP if i need to use it.
Zombnombs said:
Recovery OS's like TWRP works with all versions of the nord2 regardless of the update version.
More than likely you didn't follow all steps correctly. There are multiple mistakes you can make which results in the stock recovery OS being reflashed and the TWRP recovery being overwritten; I'm not completely sure of all the scenarios in which this happens, but you definitely made a miss-step somewhere.
I'm also running an EU nord variant with V14 and TWRP works fine, I've just noticed that after a few reboots TWRP partition gets overwritten by the stock OS again, in which case I just simply reflash the TWRP if i need to use it.
Click to expand...
Click to collapse
oh..ok i didn't know this. Thanls for the information
I actually followed the steps.
fastboot devices -> then flash the vbmeta -> then flash TWRP -> but then i cannot switch to the Recovery anymore.
Booting the phone works fine but i cannot access the recovery anymore and it always directly jumps me back to fastboot mode. I followed several videos and tutorials here but whatever i do what works for others seems to not work for me
Whenever i try it seems like the recovery is gone. Even stock recovery is not accessable anymore. I wonder what i did wrong or if i need to flash other files too.
Copaxy97 said:
oh..ok i didn't know this. Thanls for the information
I actually followed the steps.
fastboot devices -> then flash the vbmeta -> then flash TWRP -> but then i cannot switch to the Recovery anymore.
Booting the phone works fine but i cannot access the recovery anymore and it always directly jumps me back to fastboot mode. I followed several videos and tutorials here but whatever i do what works for others seems to not work for me
Whenever i try it seems like the recovery is gone. Even stock recovery is not accessable anymore. I wonder what i did wrong or if i need to flash other files too.
Click to expand...
Click to collapse
Assuming you've already unlocked bootloader and have all the mediatek drivers and ADB tools installed on your computer; Simply retry flashing vbmeta with the disable verity flag, then reflash twrp, and then reboot into recovery.
Make sure you've got a copy of the vbmeta.img and TWRP.img downloaded and place them in your ADB platform tools folder. Then run these commands
Make sure you shift-right click (for windows) on empty space in your platform tools folder and open powershel or command prompt (this is important), then send the following commands
Code:
fastboot devices
and wait for a response from your device to ensure it's connected
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
Code:
fastboot flash recovery [YourTWRPfileName]
eg my twrp file name is TWRPopn2.img so i type "fastboot flash recovery twrpopn2.img"
then
Code:
fastboot reboot recovery
Make sure your ADB terminal and phone both say the flash was succesful after each flash. If not, then you likely didn't flash the partition at all.
My guess is likely that you shift-right clicked to open the powershell window in the wrong folder, such as your desktop, in which case sending the flash commands cann't find the right file to flash? Just a theory. Definitely sounds like your recovery partition got wiped though. You could also try redownloading TWRP to make sure you're using the right version of it.
Zombnombs said:
Assuming you've already unlocked bootloader and have all the mediatek drivers and ADB tools installed on your computer; Simply retry flashing vbmeta with the disable verity flag, then reflash twrp, and then reboot into recovery.
Make sure you've got a copy of the vbmeta.img and TWRP.img downloaded and place them in your ADB platform tools folder. Then run these commands
Make sure you shift-right click (for windows) on empty space in your platform tools folder and open powershel or command prompt (this is important), then send the following commands
Code:
fastboot devices
and wait for a response from your device to ensure it's connected
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
Code:
fastboot flash recovery [YourTWRPfileName]
eg my twrp file name is TWRPopn2.img so i type "fastboot flash recovery twrpopn2.img"
then
Code:
fastboot reboot recovery
Make sure your ADB terminal and phone both say the flash was succesful after each flash. If not, then you likely didn't flash the partition at all.
My guess is likely that you shift-right clicked to open the powershell window in the wrong folder, such as your desktop, in which case sending the flash commands cann't find the right file to flash? Just a theory. Definitely sounds like your recovery partition got wiped though. You could also try redownloading TWRP to make sure you're using the right version of it.
Click to expand...
Click to collapse
Thanks for your help. I will try that again later.
What i can say i 100% opened the command prompt in the correct folder and the flash always said succesful.
I also thought about the command promt folder error before but it is correct. At least somehting got wiped (my recovery) but i simply cannot access it.
I will try again later and go over each step step by step and share ym results here. I hope i did a mistake because otherwise i don't know how to locate the problem.
Okey i did it again like the tutorial and also a second time like you said but it sadly didn't work.
{
"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"
}
This is my output from the command line. i use minimal ADB and fasstboot. But normal powershell by shift right click gives me the same output.
But when i try to reboot and boot into the recovery it just jumps to fastboot mode. So the stock recovery got flashed or removed then. But why i cannot boot into twrp?
Bootloader unlocked and based on the messages in the cmd everything fine.
Any ideas?
***Edit***
It worked now. If you ask me why, i don't know.
I did exactly the same in minimal adb and fastboot tools and on powershell. Both didn't work.
I did it in total 5 times and the last one in powershell randomly was succesful lol.
weird...
looks like the issue is more likely to do with your method of rebooting into recovery, as your reboot command did not seem to work.
Could be an issue with MinimalADB, or many other factors. If you're using the power button and volume keys combination, make sure you do it with your phone unplugged, as with the phone plugged in the combination boots to fastboot instead of recovery.
Zombnombs said:
looks like the issue is more likely to do with your method of rebooting into recovery, as your reboot command did not seem to work.
Could be an issue with MinimalADB, or many other factors. If you're using the power button and volume keys combination, make sure you do it with your phone unplugged, as with the phone plugged in the combination boots to fastboot instead of recovery.
Click to expand...
Click to collapse
Yeah might be true. I don't know.
Hello,
I'm trying to get a (permanent) TWRP installation on my OnePlus Nord 2. But after flashing the (latest official) TWRP image via fastboot to recovery I can enter it once if I press Power+VolDown directly during the reboot to recovery. But after the next reboot Power+VolDown starts the fastboot mode, Power+VolUp just boots the normal system and trying "adb reboot recovery" brings me to the standard recovery mode. For me it looks like the twrp image gets overwritten with the next reboot (something I found happens if you don't press Vol+PowerDown on your first restart after the installation but I did that [multiple tries]).
And when I try to directly boot the twrp image (without flashing it) it manages to send the file but fails on booting with "FAILED (Status read failed (No such device)). Same if I try with sudo.
Does anyone know what I am doing wrong or if it's a known bug I simply didn't find anything about?
Sincerely,
Sanaway
Hi, IIRC, right after flashing you have to boot into recovery using fastboot reboot recovery
Don't use the button combination, do it from the command line for the first boot (this should solve it if my memory serves me right)
Op_Flashpoint said:
Hi, IIRC, right after flashing you have to boot into recovery using fastboot reboot recovery
Don't use the button combination, do it from the command line for the first boot (this should solve it if my memory serves me right)
Click to expand...
Click to collapse
It works for the first boot (and if I reboot to recovery from TWRP again, even mutiply times) but as soon as I power off once and reboot normally it is gone again.
Sanaway said:
It works for the first boot (and if I reboot to recovery from TWRP again, even mutiply times) but as soon as I power off once and reboot normally it is gone again.
Click to expand...
Click to collapse
What exactly are you doing?
What you need to do is
1. Boot to fastboot
2. flash recovery fastboot flash recovery <recovery.img>
3. Once flashed, reboot to recovery, not system fastboot reboot recovery or fastboot boot <recovery.img>
I had this issue and if I boot to recovery it did not get overwritten
Op_Flashpoint said:
What exactly are you doing?
What you need to do is
1. Boot to fastboot
2. flash recovery fastboot flash recovery <recovery.img>
3. Once flashed, reboot to recovery, not system fastboot reboot recovery
I had this issue and if I boot to recovery it did not get overwritten
Click to expand...
Click to collapse
I did exactly that.
{
"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 it works so far that I can access TWRP once. But as soon as I power down from TWRP it's gone.
Sanaway said:
I did exactly that.
View attachment 5640407
And it works so far that I can access TWRP once. But as soon as I power down from TWRP it's gone.
Click to expand...
Click to collapse
Strange, maybe after flashing try fastboot boot twrp.img ?
Op_Flashpoint said:
Strange, maybe after flashing try fastboot boot twrp.img ?
Click to expand...
Click to collapse
Sanaway said:
I did exactly that.
View attachment 5640407
And it works so far that I can access TWRP once. But as soon as I power down from TWRP it's gone.
Click to expand...
Click to collapse
Found this in another thread, maybe try this as well
For that when we reboot after typing
fastboot reboot recovery
Immediately press volume down+ power button till you saw the recovery name at the bottom om the phone screen and leave the phone it will boots to twrp that's it.
Already tried both. In the end if it doesn't work I'll just reflash it every time I need it. Annoying but nothing impossible.
Sanaway said:
Already tried both. In the end if it doesn't work I'll just reflash it every time I need it. Annoying but nothing impossible.
Click to expand...
Click to collapse
HI. I think you need to flash Magisk or what ever root you want to use at first boot to TWRP.
It makes TWRP to stick
jis251 said:
HI. I think you need to flash Magisk or what ever root you want to use at first boot to TWRP.
It makes TWRP to stick
Click to expand...
Click to collapse
After I rooted the phone TWRP sticks but I can't start it by key combination. But that shouldn't be too much of a problem.
Sanaway said:
After I rooted the phone TWRP sticks but I can't start it by key combination. But that shouldn't be too much of a problem.
Click to expand...
Click to collapse
OK. I hope you know that Nord 2 doesn't like to be rooted. It will be soft bricked max 2 weeks or so ( usually) so make good backup (TWRP backup is hard to restore if at all). So be prepared and learn how to recover.
As long as you root a CLEAN ROM (I've explained multiple times in various threats what that is - stock rom (re)installed by OP, than rebooted to stock recovery, whipe, re-flash stock by OP servicepoint) and rooting will be damn fine. Mine runs for 3 months stable as hell. But. If you do not do as above, the question is not IF you are getting troubles but WHEN.