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.
Related
First off, I don't know if this is the perfect place for this thread so I apologize in advance.
I have a HTC Evo 4G LTE and I accidentally wiped everything with TWRP. It can boot to the bootloader/fastboot menus and TWRP no problem, but I can't install anything. Maybe i'm just doing everything in the wrong order. Both the SD card and the Internal SD cards have been formatted to what they're supposed to be (caused me a bit of trouble at first). My phone is set to S-On, which is a pain in the ass, because from what I understand I can't turn it off to flash a new ROM without an OS, which I don't have. Every time I attempt to install the stock ROM for my device the phone restarts when attempting to install the kernel, included in the ROM. I borrowed my friend's identical phone, rooted it and installed TWRP, created a backup, moved the backup to my phone's ext SD card and attempted to recover off of that but my TWRP can't find any of the files, but they show up just fine with the file explorer.
I've properly srewed myself. Any advice?
windowpuncher said:
First off, I don't know if this is the perfect place for this thread so I apologize in advance.
I have a HTC Evo 4G LTE and I accidentally wiped everything with TWRP. It can boot to the bootloader/fastboot menus and TWRP no problem, but I can't install anything. Maybe i'm just doing everything in the wrong order. Both the SD card and the Internal SD cards have been formatted to what they're supposed to be (caused me a bit of trouble at first). My phone is set to S-On, which is a pain in the ass, because from what I understand I can't turn it off to flash a new ROM without an OS, which I don't have. Every time I attempt to install the stock ROM for my device the phone restarts when attempting to install the kernel, included in the ROM. I borrowed my friend's identical phone, rooted it and installed TWRP, created a backup, moved the backup to my phone's ext SD card and attempted to recover off of that but my TWRP can't find any of the files, but they show up just fine with the file explorer.
I've properly srewed myself. Any advice?
Click to expand...
Click to collapse
Since you are s-on you need to flash the rom twice.
BD619 said:
Since you are s-on you need to flash the rom twice.
Click to expand...
Click to collapse
I am new to ROM flashing, I just kind of got thrown into it, lol. Please elaborate? I'm assuming flashing is installing the rom with TWRP. I flash the rom, wipe cache/dalvik, then flash again? I'll try it then post results in a minute.
Result: Doesn't work, when it says "installing Kernel, please wait...", it stays on that message for a minute or so then the phone attempts to reboot into a nonexistant OS, effectively stopping itself so I have to restart into TWRP again with no progress made.
I think you want to let it reboot in between the two flashes. I have no idea why it makes a difference, but it does.
Sent from my EVO LTE using XDA Premium 4 mobile app
Read this:
http://forum.xda-developers.com/showthread.php?t=2443108
Some Sense ROM's include a kernel installer to help facilitate flashing while S-on. You'll need to check the ROM OP and see. Otherwise the kernel can be flashed via fastboot. For more info hit the top link in my sig.
Sent from my HTC device
fizbanrapper said:
I think you want to let it reboot in between the two flashes. I have no idea why it makes a difference, but it does.
Sent from my EVO LTE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It can't. It reboots while attempting to install the kernel then freezes because there's no OS to boot to.
Try flashing the kernel first. Extract the boot.img file from the ROM zip archive using your computer. Then, with the phone connected to the PC via USB, boot into the bootloader and go to fastboot. It should change to "fastboot USB". Then use the fastboot tool from a command prompt to verify connectivity and flash the kernel.
To verify connectivity, type fastboot devices. You should see your device's serial number of its connected properly.
To flash the kernel, type fastboot flash boot boot.img. If the boot.img file and fastboot executable are in different directories, you'll need to include the path to the file. Or just put them in the same directory.
Once you've flashed the kernel, try flashing the ROM through recovery again.
Sent from my EVO using Tapatalk
CornDogg said:
Try flashing the kernel first. Extract the boot.img file from the ROM zip archive using your computer. Then, with the phone connected to the PC via USB, boot into the bootloader and go to fastboot. It should change to "fastboot USB". Then use the fastboot tool from a command prompt to verify connectivity and flash the kernel.
To verify connectivity, type fastboot devices. You should see your device's serial number of its connected properly.
To flash the kernel, type fastboot flash boot boot.img. If the boot.img file and fastboot executable are in different directories, you'll need to include the path to the file. Or just put them in the same directory.
Once you've flashed the kernel, try flashing the ROM through recovery again.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Doesn't work. I can plug my phone in all I want but it will never change to fastboot usb. It stays in fastboot just fine and I can still boot TWRP, but there's no fastboot usb. I've reinstalled drivers and tried 32 bit LiveCD ubuntu. I may need to install firmware on this stupid phone.
From the main bootloader screen, you're pressing the power button on fastboot to go into fastboot, right? And from there you can never get it to go to fastboot USB?
Sent from my EVO using Tapatalk
If you're on the old partition layout have you followed my guide that I posted previously and tried to install MeanBean ROM?
Sent from my HTC device
CornDogg said:
From the main bootloader screen, you're pressing the power button on fastboot to go into fastboot, right? And from there you can never get it to go to fastboot USB?
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Yes, that was the case.
HOWEVER, I screwed up again. I reinstalled Ubunto on my laptop and now fastboot usb works just fine.
Sometimes it hurts to live. Now I just need to find out how to flash with fastboot on ubuntu.
windowpuncher said:
Yes, that was the case.
HOWEVER, I screwed up again. I reinstalled Ubunto on my laptop and now fastboot usb works just fine.
Sometimes it hurts to live. Now I just need to find out how to flash with fastboot on ubuntu.
Click to expand...
Click to collapse
Progress.
To get the fastboot binaries on Ubuntu, you can either download and install the Android SDK and install the platform tools or go download DirtyRacun from unlimited.io. The binaries are included in the .tar archive. You may need to use the chmod command on the fastboot and adb binaries to add permissions to execute the binaries.
Once you have the binaries executable, the commands are the same, except you'll have to elevate with sudo. So, assuming you're working in the directory where you have the fastboot executable and the boot.img file, the commands would be:
sudo ./fastboot devices
sudo ./fastboot flash boot boot.img
CornDogg said:
Progress.
To get the fastboot binaries on Ubuntu, you can either download and install the Android SDK and install the platform tools or go download DirtyRacun from unlimited.io. The binaries are included in the .tar archive. You may need to use the chmod command on the fastboot and adb binaries to add permissions to execute the binaries.
Once you have the binaries executable, the commands are the same, except you'll have to elevate with sudo. So, assuming you're working in the directory where you have the fastboot executable and the boot.img file, the commands would be:
sudo ./fastboot devices
sudo ./fastboot flash boot boot.img
Click to expand...
Click to collapse
fter I
{
"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 what happens. My phone just sits there, the screen doesn't change, but it does say Fastboot USB. I restarted my phone but it got stuck at the dev boot screen with legal warnings in red text.
Addition: Booted to recovery to flash the ROM zip, not just the boot image, still restarts when attempting to install the Kernel.
The screen on your phone won't change when flashing the kernel with fastboot. After flashing it, press the power button on Fastboot to go back to the main bootloader screen and go to recovery to get into TWRP. From there, flash the .zip of the ROM that you pulled boot.img from like you normally would from TWRP (Install, select .zip, wipe cache/data, etc).
CornDogg said:
The screen on your phone won't change when flashing the kernel with fastboot. After flashing it, press the power button on Fastboot to go back to the main bootloader screen and go to recovery to get into TWRP. From there, flash the .zip of the ROM that you pulled boot.img from like you normally would from TWRP (Install, select .zip, wipe cache/data, etc).
Click to expand...
Click to collapse
I just did this, and the phone gets stuck at the dev boot screen that says HTC with the red legal text.
Have you tried a different ROM? Maybe try CM or Viper 4G. If you go the Viper 4G route, try this one: http://forum.xda-developers.com/showthread.php?t=2124391
I think the newest Viper 4G changes the partition layout or something, so I think that would just further complicate things at the moment.
CornDogg said:
Have you tried a different ROM? Maybe try CM or Viper 4G. If you go the Viper 4G route, try this one: http://forum.xda-developers.com/showthread.php?t=2124391
I think the newest Viper 4G changes the partition layout or something, so I think that would just further complicate things at the moment.
Click to expand...
Click to collapse
Yeah, I think I'll try cyanogenmod or stock android. Thank you for the suggestion, now i'll go see if it works.
No problem. If you decide to go the CM route, deck's CM11 is pretty great.
http://forum.xda-developers.com/showthread.php?t=2518211
Good luck!
CornDogg said:
No problem. If you decide to go the CM route, deck's CM11 is pretty great.
http://forum.xda-developers.com/showthread.php?t=2518211
Good luck!
Click to expand...
Click to collapse
I went on with installing DirtyRacun (http://unlimited.io/jewel.htm) and made it to step 12. As my phone ws rebooting it once again got stuck at that HTC red text dev warning screen. So now i'm stuck again.
windowpuncher said:
I went on with installing DirtyRacun (http://unlimited.io/jewel.htm) and made it to step 12. As my phone ws rebooting it once again got stuck at that HTC red text dev warning screen. So now i'm stuck again.
Click to expand...
Click to collapse
I didn't use DirtyRacun to S-OFF (I used RumRunner), so I can't speak on this with much authority. Just to confirm I understand correctly, though, you flashed the RUU (step 9), rebooted into the bootloader (step 10), and re-did the HTC Dev Unlock (step 11). Then, as it's booting up into the ROM installed via the RUU, it gets stuck?
Were you able to get anywhere with flashing Cyanogenmod? Or did you just decide to go through the S-OFF process instead?
Forgive My Poor English
I already post the recovery to develop section at HERE
RECOVERY FOR MI 8 SE
DOWNLOAD
drive.google.com/open?id=1X39kp3oBz-SYD-fNK-uEgD6VlUUG-WMq
HOW TO FLASH
Power off your phone and press volume down key and press power key to boot to Fastboot Mode
Download Fastboot tools...(Sorry I can't provide this tool)
open a command line(cmd or powershell in windows) and change directory to the directory where fastboot tool locate(cd PATH/TO/FASTBOOT/TOOL), then you can use fastboot simplely
use
Code:
fastboot flash recovery [PATH TO THE IMAGE FILE YOU DOWNLOADED]
to flash
then use
Code:
fastboot reboot recovery
to boot the recovery
IF YOUR BOOTLOADER IS LOCKED,but you wanna try it
You can use
Code:
fastboot boot [PATH TO THE IMAGE FILE YOU DOWNLOADED]
to boot the recovery(not flash recovery)
(not sure 100% success)
Do anything on YOUR OWN RISK
Pictures(and How to set language to English )
Pictures:
And How to set language to English(almost TWRP recovery can use this way)
Decrypt data partition (input your password or you cant mount data partition)
{
"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"
}
Next screen is 'Keep system partition read-only'
Left bottom is keep system RO,Right Buttom is change Language(no pic )
this is the Main screen and you can follow these steps to change Language to ENGLISH
Finally, something to start with
bao lu your QQ number
i dont understand why the board name is sirius... there is one allready , some Sony xperia z2
I hope you will post a little more detailed installation ...
Xiaomi devices:
Install TWRP via Fastboot mode, then install our ROM
Code:
fastboot flash recovery twrp.img
fastboot boot twrp.img
This will be all?
I presume i have to rename the recovery-TWRP-3.2.1-0629-XIAOMI8SE-CN-wzsx150.img to twrp.img ?
marcel112 said:
I presume i have to rename the recovery-TWRP-3.2.1-0629-XIAOMI8SE-CN-wzsx150.img to twrp.img ?
Click to expand...
Click to collapse
You don't need to rename any file to flash. For simplicity yes if you like.
_katho_ said:
You don't need to rename any file to flash. For simplicity yes if you like.
Click to expand...
Click to collapse
ok, let me refrace:
If i like to flash this recovery for the SE, for it to work, i have to follow the two comments, after renaming the .img to twrp.img
fastboot flash recovery twrp.img
fastboot boot twrp.img
After format data - reboot to recovery - wipe dalvik/etc... Install xiaomi.eu rom.
Stuck by bootloop
marcel112 said:
ok, let me refrace:
If i like to flash this recovery for the SE, for it to work, i have to follow the two comments, after renaming the .img to twrp.img
fastboot flash recovery twrp.img
fastboot boot twrp.img
Click to expand...
Click to collapse
Yes, that should work, it's the usual way to flash twrp.
i tried today to flash twrp, unsuccessfully
I installed fastboot and adb drivers ( flashed miui 10 beat using mi flash tool allready )
I enter fastboot on device
i open cmd prompt
i first enter: fastboot devices, then i get respons with devices number
When i enter command: fastboot flash recovery recovery.img
i get :
target reported max download size of 536870912 bytes
sending 'recovery' (29856 KB)...
but thats it........ nothing happens anymore!!
I tried and waited long time
Who can tell me what is going wrong
---------- Post added 6th July 2018 at 12:40 AM ---------- Previous post was 5th July 2018 at 11:46 PM ----------
I can put the phone in fastboot mode....
As soon as i connect phone to laptop, it takes 1 sec , then phone goes out off fastboot and in de left top corner are very very small letters.
I believe it says, press key to reboot, but like i say, very hard to read.
Phone reboots , then it gives battery in center off screen.
When i pess power again.
All goes normall and i can use phone as it should.
When i use updater app, and choose: reboot to recovery, it does like it should.
I can chooose reboot, wipe data and use mi assistent i believe.
Any idea would be awesome
skolarek said:
After format data - reboot to recovery - wipe dalvik/etc... Install xiaomi.eu rom.
Stuck by bootloop
Click to expand...
Click to collapse
You can try 'Disable DM-verify in 'Advance'...
maybe it work
marcel112 said:
i tried today to flash twrp, unsuccessfully
I installed fastboot and adb drivers ( flashed miui 10 beat using mi flash tool allready )
I enter fastboot on device
i open cmd prompt
i first enter: fastboot devices, then i get respons with devices number
When i enter command: fastboot flash recovery recovery.img
i get :
target reported max download size of 536870912 bytes
sending 'recovery' (29856 KB)...
but thats it........ nothing happens anymore!!
I tried and waited long time
Who can tell me what is going wrong
---------- Post added 6th July 2018 at 12:40 AM ---------- Previous post was 5th July 2018 at 11:46 PM ----------
I can put the phone in fastboot mode....
As soon as i connect phone to laptop, it takes 1 sec , then phone goes out off fastboot and in de left top corner are very very small letters.
I believe it says, press key to reboot, but like i say, very hard to read.
Phone reboots , then it gives battery in center off screen.
When i pess power again.
All goes normall and i can use phone as it should.
When i use updater app, and choose: reboot to recovery, it does like it should.
I can chooose reboot, wipe data and use mi assistent i believe.
Any idea would be awesome
Click to expand...
Click to collapse
ehhh,
you can try run this
fastboot boot [RECOVERY IMAGE YOU DOWNLOADED]
and the phone will boot to the recovery(but it still not flash into your phone)
and use the recovery to flash recovery
if you still get a stuck at
sending boot ......
trying change a computer or change a cable and retry it
q792602257 said:
ehhh,
you can try run this
fastboot boot [RECOVERY IMAGE YOU DOWNLOADED]
and the phone will boot to the recovery(but it still not flash into your phone)
and use the recovery to flash recovery
if you still get a stuck at
sending boot ......
trying change a computer or change a cable and retry it
Click to expand...
Click to collapse
Well i upgraded to succesfull flash twrp
after that i used fastboot boot twrp.img
I booted in twrp, changed the lang to english.
Choose keep system read only
Can use it, but when i tried to backup i get backup failed.
I also cant seem to find the internal storage... i can use the fiel manager, but i dont find the folders like in normal working mode
So i cant backup, flash magisk, so i dont dare to wipe and flash , lets say eu.rom
marcel112 said:
Well i upgraded to succesfull flash twrp
after that i used fastboot boot twrp.img
I booted in twrp, changed the lang to english.
Choose keep system read only
Can use it, but when i tried to backup i get backup failed.
I also cant seem to find the internal storage... i can use the fiel manager, but i dont find the folders like in normal working mode
So i cant backup, flash magisk, so i dont dare to wipe and flash , lets say eu.rom
Click to expand...
Click to collapse
the first screen is use to deecrypt data partition ,if you select cancel or input wrong password,you can't modify data partition
if you dont know the password,you can simply format data partition,but you will loose all data(include internal storage)
q792602257 said:
the first screen is use to deecrypt data partition ,if you select cancel or input wrong password,you can't modify data partition
if you dont know the password,you can simply format data partition,but you will loose all data(include internal storage)
Click to expand...
Click to collapse
whats should be the pasword?
Is that my pin how i unlock my device?
Edit:
And if i choose format data, then my internal partition will be wiped.
How can i flash a new zip file, like magisk or eu.miui rom.
Or after format data i can backup current china beta 10 8.7.5.
Then reboot in system, copy this eu miui rom zip to internal and reboot to twrp again.
Wipe device and flash the eu miui zip file?
What if i wipe and can flash eu miui file.
Can i flash using fastboot a rom?
I mean, can i go back to china beta rom?
I have a ch image 8.6.28
marcel112 said:
whats should be the pasword?
Is that my pin how i unlock my device?
Edit:
And if i choose format data, then my internal partition will be wiped.
How can i flash a new zip file, like magisk or eu.miui rom.
Or after format data i can backup current china beta 10 8.7.5.
Then reboot in system, copy this eu miui rom zip to internal and reboot to twrp again.
Wipe device and flash the eu miui zip file?
What if i wipe and can flash eu miui file.
Can i flash using fastboot a rom?
I mean, can i go back to china beta rom?
I have a ch image 8.6.28
Click to expand...
Click to collapse
The password is your pin code to unlock your phone,and you can mount data partition success
if you can't successfully mount data partition , you can
In the Recovery : Click Advance-> ADB SIDELOAD
and connect your phone to PC
use
Code:
adb sideload [PATH TO ROM ZIP FILE]
to flash without copy that zip file to your phone
also since you can mount data partition successfully,you can connect to PC, copy that zip file to Internal storage to flash
If you change your ROM,you can easily flash that 'fastboot rom' back via fastboot(WARNING : Do not flash wrong ROM,it may replace the bootloader)
and you can go back to china beta rom anytime you want(Just need flash the phone again)
maybe a little hard to understand , sorry for my poor English
Guys problem..
I made backup off miui 10 beta chinese
I wiped system/cache/data/dalvik..
Flashed new eu.miui 8.6.28 rom... install is all good.
When i boot, it is stuck in bootloop
(tried to look for : Disable DM-verify in 'Advance
I can see it not in advance..
Now i am stuck with non working phone..
Who can help me ( fast ?
marcel112 said:
Guys problem..
I made backup off miui 10 beta chinese
I wiped system/cache/data/dalvik..
Flashed new eu.miui 8.6.28 rom... install is all good.
When i boot, it is stuck in bootloop
(tried to look for : Disable DM-verify in 'Advance
I can see it not in advance..
Now i am stuck with non working phone..
Who can help me ( fast ?
Click to expand...
Click to collapse
You have to format Data!!
Superwitschi said:
You have to format Data!!
Click to expand...
Click to collapse
ok, i did format data
Now all is empty.
I rebooted into TWRP again.
I used USB-OTG to install the rom again.
All going well in install, no error
When i choose reboot, no message: No OS installed...
But still in bootloop!!
marcel112 said:
ok, i did format data
Now all is empty.
I rebooted into TWRP again.
I used USB-OTG to install the rom again.
All going well in install, no error
When i choose reboot, no message: No OS installed...
But still in bootloop!!
Click to expand...
Click to collapse
You can try 'install root' in Advance
maybe the bootloop is cause by the dm-verify in the bootloader
Obs: these were the steps that i did to get it, try it by your own risk
----------------------update------------------------
Some people are saying that can't get the 11.1.021 via ota from zui10, but I got the information that this version of qfil 11.1.021 is getting ota to the 11.5, so you should try it just changing the files in the tutorial of step 1 and if don't get the ota, jump to the step 3
-------------------------------------------------------
I did the first part with my bootloader locked, and just got it working this way. I tried to qfil directly the 11.1.021 or use the version updated with the bootloader unlocked but i got error 7 later.
To start, you will need adb and fastboot, and you can get them from here
1- Qfil the zui 10 version from this tutorial
2- Set up a pin (it will be important) and update the zui to version 11.1.021 (right after you install the zui 10 it will pop the update, if not you can use the zui update app)
3- Now that you have 11.1.021 from ota you have to go to fastboot mode (adb reboot bootloader) and unlock your bootloader, if you do this on zui 10 or zui 11.5 you will got on bootloop and have to start all again (tutorial <- you can use this to lock your bootloader for start the proccess too)
4- Go again to bootloader and use fastboot flash recovery twrp.img (download twrp)
5- From fastboot mode, press volume down repeatly until you see "Recovery mode" then press power button, the phone will reboot twice and enter in twrp, you will need to put the pin set on step 2
6- Pass this update zip to your phone from the PC then select it on "install" section and swipe to flash (this was the step where i got error 7 with qfil version of 11.1.021, if you got this, the only solution i know is start all over again owith qfil zui 10)
7- After flash is done, go back to the home page of twrp, select "wipe" and mark "dalvik", "cache" and "data" then reboot system
Your phone will be on bootloop and this is the part that i discover after 2 days trying
8- Turn off your phone and turn it back pressing the power button and the volume down to enter in fastboot mode, you will see on last line that your bootloader will be locked again, and this is the cause of bootloop
9- Use the commands to unlock bootloader again (fastboot flash unlock your_unlock_img.img and fastboot oem unlock-go)
Your phone will boot and reboot in twrp that will do an automatic process, than will reboot again in ZUI 11.5.141 (may take some minutes)
Obs²: After this proccess, if you want to use TWRP to install a rom or something, you will need to flash it again
when I try to install just I got error 7 for everstep :S how can I solve it ?
brujaboy said:
when I try to install just I got error 7 for everstep :S how can I solve it ?
Click to expand...
Click to collapse
Did you try it from qfil the zui 10 with the locked bootloader?
Because i got this error when i ota updated from 10 to 11.1.021 with the bootloader unlocked
Astronomico said:
Did you try it from qfil the zui 10 with the locked bootloader?
Because i got this error when i ota updated from 10 to 11.1.021 with the bootloader unlocked
Click to expand...
Click to collapse
yes I did my friend I installed zui10 with QFIL after that I ınstalled 11.0.21 with twrp and when I try to install 11.5 I got error 7, I did edit with notepad++ but still have this problem
brujaboy said:
yes I did my friend I installed zui10 with QFIL after that I ınstalled 11.0.21 with twrp and when I try to install 11.5 I got error 7, I did edit with notepad++ but still have this problem
Click to expand...
Click to collapse
I think the problem is with the version you're installing in TWRP , after qfil zui10, wait for the OTA for 11.1.021 of the app zui update, it seems to exist some versions of 11.1.021 and the TWRP version is not the same of the OTA
The version of 11.1.021 that i've got by OTA with my bootloader already unlocked on zui10 got error 7 too, just the version i've got with the bootloader locked worked
Astronomico said:
I think the problem is with the version you're installing in TWRP , after qfil zui10, wait for the OTA for 11.1.021 of the app zui update, it seems to exist some versions of 11.1.021 and the TWRP version is not the same of the OTA
The version of 11.1.021 that i've got by OTA with my bootloader already unlocked on zui10 got error 7 too, just the version i've got with the bootloader locked worked
Click to expand...
Click to collapse
we need wait thank u bro
Microsoft Windows [Version 10.0.18362.657]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot> adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Fixed
this is whilest in fastboot.. ^^
{
"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"
}
View attachment 4951729
it pushes a command when phone was on but when in fastboot / bootloader nothing ? any ideas?
Fixed
every time i push recovery img twrp via ADB it gets bootloader loop
leerh said:
every time i push recovery img twrp via ADB it gets bootloader loop
Click to expand...
Click to collapse
That's weird, i've uploaded the same img i used on mine smartphone, it reboot twice, but starts after in my case, i just got bootloop after unlock the bootloader, but never after flash the twrp...
Try to turn your phone on holding the vol down button to enter in fastboot and check if it's really unlocked, since you flashed the twrp, you will need it
Btw, try to use the files of this tutorial
Astronomico said:
That's weird, i've uploaded the same img i used on mine smartphone, it reboot twice, but starts after in my case, i just got bootloop after unlock the bootloader, but never after flash the twrp...
Try to turn your phone on holding the vol down button to enter in fastboot and check if it's really unlocked, since you flashed the twrp, you will need it
Btw, try to use the files of this tutorial
Click to expand...
Click to collapse
yhyh it says device is unlocked ive used unlock image from lenovo site to unlock it.
im currently on 11.1.021 st cant install twrp affter installing keeps booting to bootloader (unlocked) from here i will need to use qfill to get stock firmware 10.5.304 cn version stock recovery still works
ive also tried on ZUI_10.5.304 same thing
qill emergency flash dose not lock bootloader for me? well i cant twrps anymore makes me feel its step away from total brick
do i need to lock it then qfill then 11.1.021st via OTA then unlock it
I've Just googled It and i found that flash magisk could repair the twrp bootloop, because magisk changes the boot.img that is the cause of the problem
You can download It on magiskmanager site, put it on your phone, than use twrp install session to flash it
And Qfil doesn't Lock your bootloader
Astronomico said:
I've Just googled It and i found that flash magisk could repair the twrp bootloop, because magisk changes the boot.img that is the cause of the problem
You can download It on magiskmanager site, put it on your phone, than use twrp install session to flash it
And Qfil doesn't Lock your bootloader
Click to expand...
Click to collapse
thanks for looking into it for me and i will try this out now and let you know the results done.
this a fresh from factory flash so there is no magisk modules. can you post the links to the information you found.. i cant flash any files affter installing twrps which is successful the via ADB but affter the reboot or trying twrps or access phone or recovery will bootloop my phone to go into fast boot every single time...
can i install twrps on 10.304 and 11.021 both are offical cn roms? device has to be unlocked right which it is? is there any place i can get stock recovry image?
i wanna try= fastboot flash boot_a stockboot.img=fastboot flash boot_b stockboot.img
but i dont think i should as qfil provides stock factory flash? means its fully fresh?
leerh said:
thanks for looking into it for me and i will try this out now and let you know the results done.
this a fresh from factory flash so there is no magisk modules. can you post the links to the information you found.. i cant flash any files affter installing twrps which is successful the via ADB but affter the reboot or trying twrps or access phone or recovery will bootloop my phone to go into fast boot every single time...
can i install twrps on 10.304 and 11.021 both are offical cn roms? device has to be unlocked right which it is? is there any place i can get stock recovry image?
i wanna try= fastboot flash boot_a stockboot.img=fastboot flash boot_b stockboot.img
but i dont think i should as qfil provides stock factory flash? means its fully fresh?
Click to expand...
Click to collapse
Oh, i thought you could access the twrp after install it, sorry
The tutorial on step 1 provides the official cn rom zui10, if you use it, your phone will probably boot normally.
I think you should lock your bootloader and use the official, you will have the updates via OTA, since you can't use TWRP, I think it will be the best for you, I don't know how help you more :/
I have a request anyone can share with my twrp back up clear update without data like zip file because I have problem with my QFIL and when I try to install zui 10.5 give me sahara error and I thought about this option
brujaboy said:
I have a request anyone can share with my twrp back up clear update without data like zip file because I have problem with my QFIL and when I try to install zui 10.5 give me sahara error and I thought about this option
Click to expand...
Click to collapse
Sorry, i didn't see it, but saraha error is probably caused because wrong version of USB drivers in your PC, or you're being too slow to press "download content" on qfil after plug the phone (I don't know exactly why, but you have to click it fairly fast)
Astronomico said:
Sorry, i didn't see it, but saraha error is probably caused because wrong version of USB drivers in your PC, or you're being too slow to press "download content" on qfil after plug the phone (I don't know exactly why, but you have to click it fairly fast)
Click to expand...
Click to collapse
doesn't matter, thank u so much for replying yesterday I installed all of driver versions but I saw still again and I find another method like pushing very fast download click button and I did successfully 11.1.021 thank u so much again for supporting
Astronomico said:
Obs: these were the steps that i did to get it, try it by your own risk
I did the first part with my bootloader locked, and just got it working this way. I tried to qfil directly the 11.1.021 or use the version updated with the bootloader unlocked but i got error 7 later.
To start, you will need adb and fastboot, and you can get them from here
1- Qfil the zui 10 version from this tutorial
2- Set up a pin (it will be important) and update the zui to version 11.1.021 (right after you install the zui 10 it will pop the update, if not you can use the zui update app)
3- Now that you have 11.1.021 from ota you have to go to fastboot mode (adb reboot bootloader) and unlock your bootloader, if you do this on zui 10 or zui 11.5 you will got on bootloop and have to start all again (tutorial <- you can use this to lock your bootloader for start the proccess too)
4- Go again to bootloader and use fastboot flash recovery twrp.img (download twrp)
5- From fastboot mode, press volume down repeatly until you see "Recovery mode" then press power button, the phone will reboot twice and enter in twrp, you will need to put the pin set on step 2
6- Pass this update zip to your phone from the PC then select it on "install" section and swipe to flash (this was the step where i got error 7 with qfil version of 11.1.021, if you got this, the only solution i know is start all over again owith qfil zui 10)
7- After flash is done, go back to the home page of twrp, select "wipe" and mark "dalvik", "cache" and "data" then reboot system
Your phone will be on bootloop and this is the part that i discover after 2 days trying
8- Turn off your phone and turn it back pressing the power button and the volume down to enter in fastboot mode, you will see on last line that your bootloader will be locked again, and this is the cause of bootloop
9- Use the commands to unlock bootloader again (fastboot flash unlock your_unlock_img.img and fastboot oem-unlock go)
Your phone will boot and reboot in twrp that will do an automatic process, than will reboot again in ZUI 11.5.141 (may take some minutes)
Obs²: After this proccess, if you want to use TWRP to install a rom or something, you will need to flash it again
Click to expand...
Click to collapse
Hi bro. I see a little error in your command: The second command in the 9th step is wrong, the correct command is: "fastboot oem unlock-go".
Greetings.
leerh said:
yhyh it says device is unlocked ive used unlock image from lenovo site to unlock it.
im currently on 11.1.021 st cant install twrp affter installing keeps booting to bootloader (unlocked) from here i will need to use qfill to get stock firmware 10.5.304 cn version stock recovery still works
ive also tried on ZUI_10.5.304 same thing
qill emergency flash dose not lock bootloader for me? well i cant twrps anymore makes me feel its step away from total brick
do i need to lock it then qfill then 11.1.021st via OTA then unlock it
Click to expand...
Click to collapse
i got step 1,2,3,4,5 and 6, got an error #7.
so i used the tutorial to flash the device in step 1
it was unable to update cuz bootloader was unlock
i locked bootloader and update to 11.1.021
so afther that, i unlocked again to install twrp.
intalled twrp and transfer file to phone
booted twrp and installed the zip, got the error 7 again.
lipeneiva said:
i got step 1,2,3,4,5 and 6, got an error #7.
so i used the tutorial to flash the device in step 1
it was unable to update cuz bootloader was unlock
i locked bootloader and update to 11.1.021
so afther that, i unlocked again to install twrp.
intalled twrp and transfer file to phone
booted twrp and installed the zip, got the error 7 again.
Click to expand...
Click to collapse
best thing is to try again an follow every letter and step this only way to install 11.5 (beta) did u set a pin it is needed ive not seen another guide to install android 10
Lombachita said:
Hi bro. I see a little error in your command: The second command in the 9th step is wrong, the correct command is: "fastboot oem unlock-go".
Greetings.
Click to expand...
Click to collapse
Ops, fixed
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.
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.