Hello guys!
Yesterday I made a huge mistake and installed a treble ROM as a normal one. I loaded (not installed) TWRP on my phone, deleted system, data and cache, installed the ROM, deleted cache and dalvik and officially bricked it.
This is where I stand now:
The phone OEM is unlocked.
USB debugging is not activated and I can't activate it because I don't have access to the OS.
There is no recovery whastoever. Booting into recovery starts a bootloop.
Regular booting starts a bootloop.
The only thing that work is fastboot mode and it has its limitations.
- Can't use MiFlash to install a new ROM (I left it working for 8 hours with no results).
- It auto shuts down with the error message press any key to shutdown, which is the error it shows when USB debug is not activated.
Is there a way I can unbrick it? At this point I don't mind opening my phone and manipulating its insides becuase the warranty is already void by some company legal gibber-gabber.
I also have access to Windows, Ubuntu (Debian) and Antergos (Arch) on my computers, if anyone knows how to solve this from these operating systems. I don't mind installing other OS if it's necessary.
OK GUYS. IT'S FIXED. HERE IS THE PROCESS:
Boot the phone into fastboot mode and open adb on terminal
Type adb flash recovery whateverrecovery.img
The phone disconnects but the terminal says < waiting for device >
Keep the phone plugged and reboot into fastboot, wait a bit and it will flash
The rest you know, reboot into recovery, flash your rom and move on to breaking other devices.
Thanks to averyone that helped. You are the best!
Groctel said:
Hello guys!
Yesterday I made a huge mistake and installed a treble ROM as a normal one. I loaded (not installed) TWRP on my phone, deleted system, data and cache, installed the ROM, deleted cache and dalvik and officially bricked it.
This is where I stand now:
The phone OEM is unlocked.
USB debugging is not activated and I can't activate it because I don't have access to the OS.
There is no recovery whastoever. Booting into recovery starts a bootloop.
Regular booting starts a bootloop.
The only thing that work is fastboot mode and it has its limitations.
- Can't use MiFlash to install a new ROM (I left it working for 8 hours with no results).
- It auto shuts down with the error message press any key to shutdown, which is the error it shows when USB debug is not activated.
Is there a way I can unbrick it? At this point I don't mind opening my phone and manipulating its insides becuase the warranty is already void by some company legal gibber-gabber.
I also have access to Windows, Ubuntu (Debian) and Antergos (Arch) on my computers, if anyone knows how to solve this from these operating systems. I don't mind installing other OS if it's necessary.
Click to expand...
Click to collapse
Simply flash recovery from fastboot and wipe everything and flash stock global/cn
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Wooby said:
Simply flash recovery from fastboot and wipe everything and flash stock global/cn
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Click to expand...
Click to collapse
I can't do that. Flashing recovery gives me an error that reads FAILED (command write failed (No error)). It happens with anything I try to flash.
Groctel said:
I can't do that. Flashing recovery gives me an error that reads FAILED (command write failed (No error)). It happens with anything I try to flash.
Click to expand...
Click to collapse
If You have access to fastboot, you should be able to flash everything without limitations, maybe some issues with drivers or start fastboot command line with admin rights
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Have you tried running flash_all.sh / flash_all.bat? It should be part of official fastboot rom package. You have to have fastboot + drivers installed.
Wooby said:
If You have access to fastboot, you should be able to flash everything without limitations, maybe some issues with drivers or start fastboot command line with admin rights
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Click to expand...
Click to collapse
What operating system do you suggest I use?
Can you guide me with the commands I should try?
Cubiss said:
Have you tried running flash_all.sh / flash_all.bat? It should be part of official fastboot rom package. You have to have fastboot + drivers installed.
Click to expand...
Click to collapse
I'm going to try, I'll update you on that.
Groctel said:
What operating system do you suggest I use?
Can you guide me with the commands I should try?
Click to expand...
Click to collapse
fastboot flash recovery "recovery.img"
And then boot with power + volume up
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Wooby said:
fastboot flash recovery "recovery.img"
And then boot with power + volume up
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Click to expand...
Click to collapse
It returns the error I told you before. Can't do that :/
Send me that error please, another method would be like that guy said above download latest fastboot MIUI
Groctel said:
It returns the error I told you before. Can't do that :/
Click to expand...
Click to collapse
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Cubiss said:
Have you tried running flash_all.sh / flash_all.bat? It should be part of official fastboot rom package. You have to have fastboot + drivers installed.
Click to expand...
Click to collapse
Checked that I had the drivers installed. Run fastboot devices and the phone went into press any key to shutdown mode.
Wooby said:
Send me that error please, another method would be like that guy said above download latest fastboot MIUI
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Click to expand...
Click to collapse
{
"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 from yesterday. I'm now on Antergos (Arch Linux) and can't even see that my device is attached using fastboot devices.
I recommend you to download minimal adb and fastboot, run fastboot devices and tell me if you see your device
Groctel said:
This is from yesterday. I'm now on Antergos (Arch Linux) and can't even see that my device is attached using fastboot devices.
Click to expand...
Click to collapse
Wysłane z mojego MIX 2S przy użyciu Tapatalka
What MIUI base is installed before it bricks? What kind of custom did you flashed?
Wooby said:
I recommend you to download minimal adb and fastboot, run fastboot devices and tell me if you see your device
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Click to expand...
Click to collapse
The first time I run it I see it. The second time I run it the phone enters into press any key to shutdown mode and turns fastboot off.
Muhdxzhafir said:
What MIUI base is installed before it bricks? What kind of custom did you flashed?
Click to expand...
Click to collapse
Latest MIUI 10 version and tried to install the unofficial treble LOS rom in this forum section.
Groctel said:
Latest MIUI 10 version and tried to install the unofficial treble LOS rom in this forum section.
Click to expand...
Click to collapse
Latest beta or stable?
"adb devices" works? try this if it could help, but.. just take a look http://en.miui.com/thread-528989-1-1.html
Muhdxzhafir said:
Latest beta or stable?
"adb devices" works? try this if it could help, but.. just take a look http://en.miui.com/thread-528989-1-1.html
Click to expand...
Click to collapse
I can't boot into twrp, that's my main problem. Every time I try to do it my phone disconnects and shows the press any key to shutdown screen.
Groctel said:
I can't boot into twrp, that's my main problem. Every time I try to do it my phone disconnects and shows the press any key to shutdown screen.
Click to expand...
Click to collapse
Uninstall all adb drivers you have on your computer, restart and install these adb/fastboot drivers:
https://forum.xda-developers.com/showthread.php?t=2588979
Try it on a different usb port on your computer (use the ports on the back!)
Use a windows computer.
If it does not work, try a different computer, use windows.
It's an issue on your computer, and not related to usb debugging
malimukk said:
Uninstall all adb drivers you have on your computer, restart and install these adb/fastboot drivers:
https://forum.xda-developers.com/showthread.php?t=2588979
Try it on a different usb port on your computer (use the ports on the back!)
Use a windows computer.
If it does not work, try a different computer, use windows.
It's an issue on your computer, and not related to usb debugging
Click to expand...
Click to collapse
I get the error : device not found after this command
adb reboot bootloader.
How to solve it ??? Thanks !
https://drive.google.com/file/d/1Re6YZkL8KXSK35Pea5K6Iw41AQ9nVT7u/view?usp=sharing
Please see the link above.
Related
hi all.
I need you help.
i do it somthing stupid and my mate 7 l09 have all the time bootloop.
What i do you ask me???
ok i write here
I update to 5.1.1 b317 and i dont do it backup. I erase all partition like system , boot , cust using twrp 2.8.7.0
Now i have only working stock recovery and working twrp fo lp.
I try flash b137 system, boot , recovery and cust using fastboot and flash succes but when i try coming to stock recovery from b137 its dont work.
Work only fastboot.
Now i flash stock recovery from lp and work but i can flash update zip 308 and 317 to.
Update.app flash but stok on 90 % and its dont go to 100%.
What i can do???
What you can do for me???
I need twrp backup from b317 ( system , boot and cust ) to reanimate my mt7.
If any one now how use adb and have su you can put to your sdcard all partition and i can flash using fastboot.
Please upload this file for me. thank's and sorry for my english
https://mega.nz/#!Y9NWwb6B!gSMMZGhfsEx23LqbPelCWFchMYhHtl3Ro6kv7Rpz-40
Use the recovery and boot image in the zip then b137 then you can update.
Sent from my HUAWEI MT7-L09 using Tapatalk
ive been playing again and find myself in the same situation, only i cant get into fastboot recovery at all. Any ideas?
snake65
thanks for this file. My mt7 alive again
What i do???
in my topic i write what i do.
Now i write what i do to repair
First i download from snake65. I use fastboot to flash boot.img and recovery.img ( before i have system, boot, cust from b137 and recovery from 5.1 )
Now i copy do my micro sd card b300 and dont push sd card to phone i go to download mode. when i see download mode i push my micro to phone.
Flash finish sukces. Now i do it wipe data and cache i recovery and copy to micro b137 and do it that same as b300.
My phone alive again. Thanks Snake65
Fastboot is not working with windows 10, is there another way to flash those 2 files ? i'm on miui 7 with cwm recovery, but i don't know how to flash stock rom.
Try an updated fastboot file I know one of them work on 10 as I've done it.
Sent from my HUAWEI MT7-L09 using Tapatalk
fenrir39 said:
Fastboot is not working with windows 10, is there another way to flash those 2 files ? i'm on miui 7 with cwm recovery, but i don't know how to flash stock rom.
Click to expand...
Click to collapse
First install hisuite because this program have good drivers
Fastboot work on win 10 pro x 64. I now because i use this Windows. Copy fastboot folder from snake65 but before change folder name to adb and copy to C:/
If you do it that.
Cmd administrator
cd C:/adb
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
It take a moment and flash.
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
chudy_85 said:
First install hisuite because this program have good drivers
Fastboot work on win 10 pro x 64. I now because i use this Windows. Copy fastboot folder from snake65 but before change folder name to adb and copy to C:/
If you do it that.
Cmd administrator
cd C:/adb
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
It take a moment and flash.
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
re-installing Hisuite worked like a charm, thank you buddy, you saved my day
@fenrir39 Good news and your mate work now i thing ?
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
chudy_85 said:
First install hisuite because this program have good drivers
Fastboot work on win 10 pro x 64. I now because i use this Windows. Copy fastboot folder from snake65 but before change folder name to adb and copy to C:/
If you do it that.
Cmd administrator
cd C:/adb
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
It take a moment and flash.
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
I have same prop but I have no os and when I tried to flash boot and recovery and press 3 bottom phone just restarting until battery empty
what should I do ?????
What mate 7 you have??? If you have L09 what firmware you have before you upgrade to lp. Download that same firmware and use Huawei extractor update app to take system.img and cust.img. Flash using fastboot. Then flash boot and recovery from snake65 copy to micro SD card full firmware lp and try flash using stock recovery or try take out all file you need from lp and flash as fastboot mode
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
chudy_85 said:
What mate 7 you have??? If you have L09 what firmware you have before you upgrade to lp. Download that same firmware and use Huawei extractor update app to take system.img and cust.img. Flash using fastboot. Then flash boot and recovery from snake65 copy to micro SD card full firmware lp and try flash using stock recovery or try take out all file you need from lp and flash as fastboot mode
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
when i done and reboot it reboot twice then take me auto to stock recovery
i try wipe cache but still take me to stock recovery
and when i try to flash lp it unable to go to flash it it just restart and take me again to stock recovery
and lp it's zip not img so cannot flash from fastboot
what should i do ??
Tomorrow i update you lp file in img on mega and you can download and flash
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
chudy_85 said:
Tomorrow i update you lp file in img on mega and you can download and flash
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
thanks alot i am waiting you
[email protected] said:
thanks alot i am waiting you
Click to expand...
Click to collapse
here you have with instruction in txt
https://mega.nz/#!V05ThIhC!rOP8M4Ocv4fq8Vuu1Qh1-6jEhh2MRBXUs3RoGyw8NP8
{
"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"
}
TeamWin's TWRP Touch Recovery for BLU Pure XL (and clones)https://twrp.me/
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom ROM like OmniROM.
Source to build TWRP you can find here.
SCREENSHOTS: HERE
Bugs:
If you find any bug I haven't noticed, please go here and send me bug report. It would help me solving most problems in further builds.
Flashing instructions:
Use Flashify, TWRP Manager or follow this thread.
WARNING!
Code:
This is custom recovery image.
Wait for progress but don't ask for ETA - I have my own life too.
You are flashing it at your own risk - don't do it if you don't know what it's used for!
I'm not responsible for earthquake, thermonuclear war or any damage on your phone. If you point finger at me for messing up your phone I'll laugh at you.
Changelog:
Code:
[B]3.1.0[/B] 2017-03-18[LIST]
[*]Release notes: [URL="https://twrp.me/site/update/2017/03/10/twrp-3.1.0-0-released.html"][link][/URL]
[*]Fixed partitioning problems.
[*]Added support for more partitions (/logo, /nvram etc.)
[*]Fixed restoring backups.
[*]Fixed CPU temp indicator.[/LIST]
[B]3.0.2-0 Official [/B] 2016-04-05
[LIST]
[*]Release notes: [URL="https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html"][link][/URL]
[/LIST]
[B]3.0.1-0 Official[/B] 2016-04-01
[LIST]
[*]Release notes: [URL="https://twrp.me/site/update/2016/04/01/twrp-3.0.1-0-released.html"][link][/URL]
[/LIST]
[B]3.0.0-1 Official[/B] 2016-02-26 (on AndroidFileHost)
[LIST]
[*][B]Recovery is now STABLE in usage![/B]
[*]Restoring backups is now [B]FIXED![/B]
[*]Mounting to PC should be now [B]FIXED![/B]
[*]Some improvments to code
[/LIST]
[B]3.0.0-0 Official[/B] 2016-02-20
[LIST]
[*]Added official support for this device
[*]Nothing changed since last build
[/LIST]
[B]3.0.0-beta3[/B] 2016-02-07
[LIST]
[*][STRIKE]Fixed backup restoring issue[/STRIKE] Seems not to be fixed, will be working on it
[*]Some iprovements
[/LIST]
[B]3.0.0-beta2[/B] 2016-02-07
[LIST]
[*]Fixed partitions problem - TWRP sees & mounts them now
[*]Fixed battery percentage indicator
[/LIST]
[B]3.0.0-beta1[/B] 2016-02-06
[LIST]
[*]Initial release
[*]TWRP can't mount partitions, doesn't read storage
[*]Any other bugs are related to problem mentioned above
[*]TWRP boots and reboots correctly
[/LIST]
Donwload: here (SourceForge)
Device tree: device_x2xtreme
Credits: Ethan Yonker aka Dees_Troy & whole TWRP Dev Team
XDA:DevDB Information
TWRP 3.1.0, Tool/Utility for the Blu Pure XL
Contributors
bemolx
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: v3.1.0-0
Stable Release Date: 2017-03-18
Created 2016-02-06
Last Updated 2017-04-03
Bugs & changelogs
What does work:
Everything.
What doesn't work:
Look at changelog. Thank you
No disrespect, bit did you compile this? I ask cause I am trying to compile the new TWRP for my device wich is a LG G Stylo and my touch input does not work. So I was wondering if you had this issue and if so how did you fix it?
T-Macgnolia said:
No disrespect, bit did you compile this? I ask cause I am trying to compile the new TWRP for my device wich is a LG G Stylo and my touch input does not work. So I was wondering if you had this issue and if so how did you fix it?
Click to expand...
Click to collapse
Yes, Ive compiled it without any errors at first time. I don't know how to help you at this moment. Ask TeamWin Devs
Cheers
Wysłane z mojego X2_Soul_Xtreme
bemolx said:
Yes, Ive compiled it without any errors at first time. I don't know how to help you at this moment. Ask TeamWin Devs
Cheers
Wysłane z mojego X2_Soul_Xtreme
Click to expand...
Click to collapse
bemolx said:
What doesn't work: CPU temperature indicator, mounting to PC
3.0.0-beta2
Fixed partitions problem - TWRP see & mount them now
Fixed battery percentage indicator
3.0.0-beta1
Initial release
TWRP can't mount partitions, doesn't read storage
Any other bugs are related to problem mentioned above
TWRP boots and reboot correctly
Click to expand...
Click to collapse
Olá, estou com problema em montar "cache" não consigo restaurar a rom stock... Backup feito com o novo twrp 3.0 beta 2... Alguma dicas.....
eualex said:
Olá, estou com problema em montar "cache" não consigo restaurar a rom stock... Backup feito com o novo twrp 3.0 beta 2... Alguma dicas.....
Click to expand...
Click to collapse
Can you provide me logcat or at least error shown while restoring your backup? It would help much.
PS. Next time write in English because it's better for me and other users in this forum to understand what's your problem.
Update: Yeah... I've bricked my device too. Now I know the problem and I am working on it. Wait for beta3
Wysłane z mojego X2_Soul_Xtreme
bemolx said:
Can you provide me logcat or at least error shown while restoring your backup? It would help much.
PS. Next time write in English because it's better for me and other users in this forum to understand what's your problem.
Update: Yeah... I've bricked my device too. Now I know the problem and I am working on it. Wait for beta3
Wysłane z mojego X2_Soul_Xtreme
Click to expand...
Click to collapse
The error was with TWRP 3.0 beta 3. Could not mount the cache for that reason did not finish the restoration, I reinstalled TWRP 2.8 per adb and got a mont in the cache. Now all ok with TWRP 2.8. Thank you for your attention, I am waiting for the first custom for blu pure xl. Summary error was to assemble cache error does not happen with TWRP 2.8.
eualex said:
The error was with TWRP 3.0 beta 1. Could not mount the cache for that reason did not finish the restoration, I reinstalled TWRP 2.8 per adb and got a mont in the cache. Now all ok with TWRP 2.8. Thank you for your attention, I am waiting for the first custom for blu pure xl.
Click to expand...
Click to collapse
Okay, I see In beta3 everything has beed updated - in beta1 you couldn't mount any partition because of bad recovery.fstab which is already fixed
Cheers
Sent from Nexus 5
bemolx said:
Okay, I see In beta3 everything has beed updated - in beta1 you couldn't mount any partition because of bad recovery.fstab which is already fixed
Cheers
Sent from Nexus 5
Click to expand...
Click to collapse
Edit, was using the TWRP 3.0 beta 3 ...... So I could settle with TWRP 2.8. Thank you
beta restore fail
Same issue at me. When I tried to restore the backup in twrp 3.0.0 beta 3 it stopped. And briked my phone.
I was needed to install twrp 2.8.6.0 back and restore the backup to boot again the phone.
AlexDC2013 said:
Same issue at me. When I tried to restore the backup in twrp 3.0.0 beta 3 it stopped. And briked my phone.
I was needed to install twrp 2.8.6.0 back and restore the backup to boot again the phone.
Click to expand...
Click to collapse
eualex said:
Edit, was using the TWRP 3.0 beta 3 ...... So I could settle with TWRP 2.8. Thank you
Click to expand...
Click to collapse
Restoring backup problems have been solved in v3.0.0-1. Please wait for upload at the official download page. Thank you
Wysłane z mojego X2_Soul_Xtreme
Help!! My BLU Pure XL will not go into Recovery
I try to go into recovery mode and the phone just reboots. I hold the
power and Vol up key like I did when I originally rooted it but now it will not go into recovery any longer. I'm trying to revert back to stock and upgrade to the latest release. Can someone please assist?
---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------
I can not get my phone into ecovery mode. I did the buttons as I have in the past but the phone just reboots. It's like my recovery mode was deleted and the phone just resets. Help!!!!
KingKe said:
I try to go into recovery mode and the phone just reboots. I hold the
power and Vol up key like I did when I originally rooted it but now it will not go into recovery any longer. I'm trying to revert back to stock and upgrade to the latest release. Can someone please assist?
---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------
I can not get my phone into ecovery mode. I did the buttons as I have in the past but the phone just reboots. It's like my recovery mode was deleted and the phone just resets. Help!!!!
Click to expand...
Click to collapse
Try to reflash the recovery img using fastboot method.
Wysłane z mojego X2_Soul_Xtreme
bemolx said:
Try to reflash the recovery img using fastboot method.
Wysłane z mojego X2_Soul_Xtreme
Click to expand...
Click to collapse
I would by I do not have root access.
KingKe said:
I would by I do not have root access.
Click to expand...
Click to collapse
You don't have to. Follow this thread.
Wysłane z mojego X2_Soul_Xtreme
bemolx said:
You don't have to. Follow this thread.
Wysłane z mojego X2_Soul_Xtreme
Click to expand...
Click to collapse
I started with this link.
Let me restate my issue and shed light on my environment.
Power Button + Vol up does not go to Recovery mode - My phone just goes to a black screen and reboots. So, if any procedure requires that I can not execute right now. I need recovery mode back.
I am running Windows 10 Professional 64Bit variant. My BlU Pure XL connects via MPT so I can not assign a drive letter to it so that I can navigate to it via CMD prompt.
Fastboot command comes and stating 'waiting for device' because I can not get my device into recovery mode. So, can someone walk me through this issue and get my recovery mode reinstalled/repaired (Also I am not rooted)?
KingKe said:
I started with this link.
Let me restate my issue and shed light on my environment.
Power Button + Vol up does not go to Recovery mode - My phone just goes to a black screen and reboots. So, if any procedure requires that I can not execute right now. I need recovery mode back.
I am running Windows 10 Professional 64Bit variant. My BlU Pure XL connects via MPT so I can not assign a drive letter to it so that I can navigate to it via CMD prompt.
Fastboot command comes and stating 'waiting for device' because I can not get my device into recovery mode. So, can someone walk me through this issue and get my recovery mode reinstalled/repaired (Also I am not rooted)?
Click to expand...
Click to collapse
1. If you have adb working (for some reason in my case, my Pure XL doesn't want to be detected by it), then launch cmd in the same directory as adb and fastboot (SHIFT+Right Click) and use the command adb reboot bootloader to put it into the bootloader (don't worry about the tiny text on the bootloader screen saying stuff about security).
2. Then, after you put the TWRP recovery.img in the same folder, use the command fastboot flash recovery recovery.img to flash TWRP back onto your device (not sure how you managed to corrupt/remove it in the first place).
3. If you don't have adb working (like me), download and use WinDroid Toolkit (which can be found on another post under "Pure XL Android Development"), connect your phone to your computer, select Pure XL under BLU in WinDroid Toolkit, go to the Commands tab, and click Bootloader under the Reboot section, then follow step number two listed above.
Short Circuit said:
1. If you have adb working (for some reason in my case, my Pure XL doesn't want to be detected by it), then launch cmd in the same directory as adb and fastboot (SHIFT+Right Click) and use the command adb reboot bootloader to put it into the bootloader (don't worry about the tiny text on the bootloader screen saying stuff about security).
2. Then, after you put the TWRP recovery.img in the same folder, use the command fastboot flash recovery recovery.img to flash TWRP back onto your device (not sure how you managed to corrupt/remove it in the first place).
3. If you don't have adb working (like me), download and use WinDroid Toolkit (which can be found on another post under "Pure XL Android Development"), connect your phone to your computer, select Pure XL under BLU in WinDroid Toolkit, go to the Commands tab, and click Bootloader under the Reboot section, then follow step number two listed above.
Click to expand...
Click to collapse
Fro no ADB, make sure you have debugging enabled in the dev options under settings (hidden menu you have to tap either kernel version or software version multiple times to unlock; i forget which, but its all over the forums and google...
Also if you have root (its unclear because you are saying you cannot get into recovery, and I honestly didnt read but the last post...) you can load terminal from play store and type "su"<enter> then "reboot recovery" <enter> and it will reboot into recovery
but Id look into the issue of the buttons not working, do they work fine else ware?
Short Circuit said:
1. If you have adb working (for some reason in my case, my Pure XL doesn't want to be detected by it), then launch cmd in the same directory as adb and fastboot (SHIFT+Right Click) and use the command adb reboot bootloader to put it into the bootloader (don't worry about the tiny text on the bootloader screen saying stuff about security).
2. Then, after you put the TWRP recovery.img in the same folder, use the command fastboot flash recovery recovery.img to flash TWRP back onto your device (not sure how you managed to corrupt/remove it in the first place).
3. If you don't have adb working (like me), download and use WinDroid Toolkit (which can be found on another post under "Pure XL Android Development"), connect your phone to your computer, select Pure XL under BLU in WinDroid Toolkit, go to the Commands tab, and click Bootloader under the Reboot section, then follow step number two listed above.
Click to expand...
Click to collapse
Thanks I am up and running and all is well. I can't get the update because I originally rooted the phone before all hell broke loose. But thanks for the help.
I get an error that it cannot mount '/cache' (invalid argument) after i do a factory reset
Hi,
I tried to install magisk on my Z3 with locked bootloader and fragment rom.
After hitting reboot the phone the screen turned black and my phone is dead. I doesn`t turn on.
Tried to flash a rom via flashtool but it says I have to turn on USB debugging. Thats not possible since my phone doesn`t start at all.
Fastbootmode is recognized, also flashmode.
What to do?
memphis77 said:
Hi,
I tried to install magisk on my Z3 with locked bootloader and fragment rom.
After hitting reboot the phone the screen turned black and my phone is dead. I doesn`t turn on.
Tried to flash a rom via flashtool but it says I have to turn on USB debugging. Thats not possible since my phone doesn`t start at all.
Fastbootmode is recognized, also flashmode.
What to do?
Click to expand...
Click to collapse
I had a problem like that.
Try using PC Companion by Sony. It worked for me
Worked
Gesendet von meinem D6603 mit Tapatalk
memphis77 said:
Worked
Gesendet von meinem D6603 mit Tapatalk
Click to expand...
Click to collapse
Just a little info about Magisk taken from the original thread:
"Sony Devices: If you're using stock kernel, it is using Sony's special ELF format.
Magisk will repack it to standard AOSP format, which requires your device to be unlocked"
Don't try to flash Magisk on a Xperia with locked bootloader.
I finally rooted my Nokia 8 PROTO with a custom TWRP recovery kindly provided by Chinese 7to forum.
Here's the procedure I did on my Nokia 8 PROTO:
1. I managed to extract boot.img manually by using WinHex manually. But I found the Recovery is combined into boot.img when analyzing ramdisk included in boot.img. This made Nokia 8 Custom Recovery difficult.
2. After maintenance purposed bootloader activated by OST LA, you could flash custom recovery by this command:
Code:
fastboot-android flash boot NB1-boot.img
Yes, that's boot partition instead of recovery partition. (Mine is TA-1012)
Sorry I've put the recovery for Nokia 5 by mistake, now replaced with correct one.
Click to expand...
Click to collapse
To activate maintenance purposed bootloader, you need to load original stock firmware with OST LA, then click "Edit phone data". When OST LA prompts "Boot FTM mode fail", the maintenance purposed bootloader is loaded.
3. Type this command but do not execute right now:
Code:
fastboot-android reboot
4. Press and hold Volume Up, then execute the command above. Keep holding Volume Up until you see the 7to logo.
5. The custom recovery doesn't include SuperSU ROOT package. I sideloaded "SR4-SuperSU-v2.82-SR4-20170918204844.zip" to the phone. The sideload option is in "高级" (Advanced in Chinese) catagory. I've never tested magisk on it.
6. You may want to remove verification feature in recovery. Reboot your phone.
I tested it on a Nokia 8 Retail Phone, it says "verification failed" after I reboot. So I wonder if anything wrong.
Here's the result if you're interested: https://twitter.com/Hikari_Calyx/status/917348942165155841
----------SEPARATOR----------
Here's how to enter Emergency Download mode:
1. Enter Download Mode by using OST LA.
2. After maintenance purposed bootloader activated by OST LA, type this command:
Code:
fastboot-android oem reboot-edl
In order to enter Emergency Download Mode. It may complex, currently it's the only way to enter Emergency Download Mode without disassembling.
3. Do something with your phone with QFIL.
----------SEPARATOR----------
I finally untrapped my Nokia 8 prototype, which has an unlocked bootloader.
Although Nokia 8 cannot enter EDL mode (Or 9008) with EDL Cable directly while Nokia 5 and 6 are able to enter EDL mode with EDL cable, I still figured out how to enter the EDL mode on Nokia 8 without any specific peripherals.
With @heineken78‘s nb0tools2016v2, I was able to unpack few of files from Nokia 5/6/8's nb0 firmware from @blackpanther0582, but that's only about bootloaders and rawprogram*.xml and patch*.xml, and I was not able to unpack any further, the program got overflow and terminated.
These files should be enough for unbrick your phone from full brick.
Anyway, that's off topic.
After I entered the EDL mode of my Nokia 8 prototype (with provided retail firmware installed), I used Partition Manager from QFIL included in QPST 2.7.460. I attached the screenshots of the partitions.
However, I noticed there's no recovery partition, which makes the TWRP port to Nokia 8 confusing.
(Although our Chinese Team ported TWRP to Nokia 6 and 5 recently)
And which partitions are important for bootloader unlocking?
Since we could enter EDL mode easily, it should be easy to unlock bootloader for Nokia 5/6/8 currently.
There not being a recovery partition would explain this. There is a obviously a recovery though, but it's accessed through the download mode. So my guess is the recovery is either hidden/baked in with another partition or it's inside the kernel like in the old days (more likely the former though). Unfortunately I know far too little about this stuff so I'm not of much help.
CazeW said:
There not being a recovery partition would explain this. There is a obviously a recovery though, but it's accessed through the download mode. So my guess is the recovery is either hidden/baked in with another partition or it's inside the kernel like in the old days (more likely the former though). Unfortunately I know far too little about this stuff so I'm not of much help.
Click to expand...
Click to collapse
Well, I got this information from Nokibar.
To enter Recovery for factory reset if you want to try it out, here's the method provided by HMD:
1. Power off your phone.
2. Press and hold Volume Up key and connect your phone to PC.
3. Waiting for Android robot on the ground displays along with NO COMMAND, release the Volume Up.
4. Press Volume Up while pressing power key to get Recovery menu.
Click to expand...
Click to collapse
It does have recovery, but I still can't figure out which partition includes it.
hikari_calyx said:
Well, I got this information from Nokibar.
It does have recovery, but I still can't figure out which partition includes it.
Click to expand...
Click to collapse
Thank you for the reminder that I found it
hikari_calyx said:
I finally rooted my Nokia 8 PROTO with a custom TWRP recovery kindly provided by Chinese 7to forum.
Here's the procedure I did on my Nokia 8 PROTO:
1. I managed to extract boot.img manually by using WinHex manually. But I found the Recovery is combined into boot.img when analyzing ramdisk included in boot.img. This made Nokia 8 Custom Recovery difficult.
2. After maintenance purposed bootloader activated by OST LA, you could flash custom recovery by this command:
Code:
fastboot-android flash boot nokia-ta-1004-twrp3.1.1-7to-recovery.img
Yes, that's boot partition instead of recovery partition. (Mine is TA-1012)
3. Type this command but do not execute right now:
Code:
fastboot-android reboot
4. Press and hold Volume Up, then execute the command above. Keep holding Volume Up until you see the 7to logo.
5. The custom recovery doesn't include SuperSU ROOT package. I sideloaded "SR4-SuperSU-v2.82-SR4-20170918204844.zip" to the phone. The sideload option is in "高级" (Advanced in Chinese) catagory. I've never tested magisk on it.
6. You may want to remove verification feature in recovery. Reboot your phone.
I tested it on a Nokia 8 Retail Phone, it says "verification failed" after I reboot. So I wonder if anything wrong.
Here's the result if you're interested: https://twitter.com/Hikari_Calyx/status/917348942165155841
Click to expand...
Click to collapse
So they did put the recovery inside the boot image like I first guessed. That's.... surprising to say the least as that's very old school. Like Galaxy S old school. Wonder why they did it that way, as it just feels stupid. Glad you figured it out though, now we just need a way to unlock the bootloader and we can get rooting.
CazeW said:
now we just need a way to unlock the bootloader and we can get rooting
Click to expand...
Click to collapse
HMD promised they'd unlock all Nokia phones one by one. It's just a matter of time till they reach Nokia 8.
But if someone can figure out how to do it before that happens, that'd be amazing
CazeW said:
So they did put the recovery inside the boot image like I first guessed. That's.... surprising to say the least as that's very old school. Like Galaxy S old school. Wonder why they did it that way, as it just feels stupid. Glad you figured it out though, now we just need a way to unlock the bootloader and we can get rooting.
Click to expand...
Click to collapse
And here's another problem: When I rooted the phone, it will destroy the recovery included in boot.img, so doing factory reset is tough for it.
hikari_calyx said:
And here's another problem: When I rooted the phone, it will destroy the recovery included in boot.img, so doing factory reset is tough for it.
Click to expand...
Click to collapse
Makes sense as SuperSU modifies the boot.img. Unless we (or HMD) somehow can put the recovery on a recovery partition, a custom/updated version of SuperSU is going to be needed. Not sure if Magisk root modifies the boot.img but I would suspect that it does.
hikari_calyx said:
I tested it on a Nokia 8 Retail Phone, it says "verification failed" after I reboot. So I wonder if anything wrong.
Click to expand...
Click to collapse
Prototype units are for development use, so most likely have secure boot disabled.
In retail unit or production unit with secure boot enabled, if you modified the bootloader (or its partition), the secure boot verification will fail.
CazeW said:
Makes sense as SuperSU modifies the boot.img. Unless we (or HMD) somehow can put the recovery on a recovery partition, a custom/updated version of SuperSU is going to be needed. Not sure if Magisk root modifies the boot.img but I would suspect that it does.
Click to expand...
Click to collapse
I updated the procedure of entering Emergency Download mode on topic. You can give it a try if interested.
How to enter recovery mode?
Wysłane z mojego Nokia 8 przy użyciu Tapatalka
Araa01 said:
How to enter recovery mode?
Wysłane z mojego Nokia 8 przy użyciu Tapatalka
Click to expand...
Click to collapse
Use adb : adb reboot recovery, then hold the power + volume up buttons.
gee2012 said:
Use adb : adb reboot recovery, then hold the power + volume up buttons.
Click to expand...
Click to collapse
When i off device combination power + up not work? I must use adb?
Wysłane z mojego Nokia 8 przy użyciu Tapatalka
Araa01 said:
When i off device combination power + up not work? I must use adb?
Wysłane z mojego Nokia 8 przy użyciu Tapatalka
Click to expand...
Click to collapse
No, don`t think so but for me thats the easiest method to get into recovery
gee2012 said:
No, don`t think so but for me thats the easiest method to get into recovery
Click to expand...
Click to collapse
Thank u! When we get oreo i must shoot full wipe so.. :d
Wysłane z mojego Nokia 8 przy użyciu Tapatalka
Interesting to see 'OEM Unlocking' in the Developer Settings.
Steve Geemaggio said:
Interesting to see 'OEM Unlocking' in the Developer Settings.
Click to expand...
Click to collapse
I tried to unlock the bootloader with Fastboot but I only get an error saying that it is not possible. That is with the setting turned on. So I guess the setting is still not active.
alexcannasV said:
I tried to unlock the bootloader with Fastboot but I only get an error saying that it is not possible. That is with the setting turned on. So I guess the setting is still not active.
Click to expand...
Click to collapse
I see! Well then I guess we got to wait for Nokia to step up and do it then.
Great to be running pure AOSP out of the box though. I'm grateful for that, but would love to be able to get rid of the mountain of Google apps pre-installed.
Glad Nokia changed their mind about unlocking the bootloader!
Steve Geemaggio said:
Glad Nokia changed their mind about unlocking the bootloader!
Click to expand...
Click to collapse
Hold your horses! Haven't seen any unlocked bootloaders yet...
I was reading today this http://neopodapsi.com/how-to-unlock-bootloader-on-nokia-8/
Is this for real or not? I was very interested in the Nokia 8 if they were unlocking the BL and releasing the kernel sources
To have root on EMUI 9.1 we need https://androidfilehost.com/?fid=11410963190603907556
and ADB on the computer.
1. connect the phone to the computer, turn on the USB debugging mode
2. In ADB: "adb reboot bootloader"
The phone will go off in fastboot mode.
The downloaded file is loaded with a command: "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00-b7f69238.img
5. We're rebooting with a command: "fastboot reboot, quickly disconnect the phone and hold the VOL+ at the same time (all the time from the restart)
The phone will enter the eRecovery mode and we normally click "Factory/WIPE" as if we were restoring the factory settings.
This will cause root (magisk) to save permanently.
Of course we need to unlock the bootloader, but now (10.06.2019) it is not a problem because they sell for $41 (I bought it on imei.by - paid PayPal)
I wrote this post because I've been working hard to get root for half a day and there were incomplete answers everywhere.
Translated with www.DeepL.com/Translator
File link is broken (file not found), please fix.
Repaired, sometimes a few times you need to refresh
I have rooted emui 9.1 mate 20x chinese but contact and dialer dont open ..any idea how to fix it?
Try flash https://androidfilehost.com/?fid=1395089523397950492
Wysłane z mojego EVR-AL00 przy użyciu Tapatalka
facet_ said:
Try flash https://androidfilehost.com/?fid=1395089523397950492
Wysłane z mojego EVR-AL00 przy użyciu Tapatalka
Click to expand...
Click to collapse
You saying to me?
---------- Post added at 11:06 PM ---------- Previous post was at 11:06 PM ----------
facet_ said:
Try flash https://androidfilehost.com/?fid=1395089523397950492
Wysłane z mojego EVR-AL00 przy użyciu Tapatalka
Click to expand...
Click to collapse
I don't have twrp
walkwitmeinhel said:
You saying to me?
---------- Post added at 11:06 PM ---------- Previous post was at 11:06 PM ----------
I don't have twrp
Click to expand...
Click to collapse
Maybe you flash busybox in magisk and unzip the downloaded file then replace the file in system with root explorer. Try and let me know also. Ps. I never try before.
I'm on a P20 Pro with EMUI 9.1 - 9.1.0.311
I cannot flash TWRP or Magisk boot img's, bootloader is still unlocked, FRP is fine, it's just not letting me play.
I pathced TWRP, Recovery_ramdisk, nothing is playing lol.
Perhaps it's the rom i'm on.
Thanks for the guide, but no good for the pro on 311 unfortunately.
Cheers
dladz said:
I'm on a P20 Pro with EMUI 9.1 - 9.1.0.311
I cannot flash TWRP or Magisk boot img's, bootloader is still unlocked, FRP is fine, it's just not letting me play.
I pathced TWRP, Recovery_ramdisk, nothing is playing lol.
Perhaps it's the rom i'm on.
Thanks for the guide, but no good for the pro on 311 unfortunately.
Cheers
Click to expand...
Click to collapse
If you unlocked bl you can flash patched img and root
walkwitmeinhel said:
If you unlocked bl you can flash patched img and root
Click to expand...
Click to collapse
Thats what i thought dude
boot to bootloader
put magisk patched img in adb folder
fastboot flash recovery_ramdisk magisk.patched.img
Remove cable, boot and hold up
device boots to the first screen for eRecovery
same problem with TWRP
I've even factory wiped and booted straight to bootloader before flashing magisk or twrp, had to install the stock recovery_ramdisk to perform the wipes required
at this point i've no idea what to do so i'm looking for a non service firmware to flash, only the ones i've found are all 311 not above, can't find 320
sucks
EDIT: Downloading this now
https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=145556
dladz said:
Thats what i thought dude
boot to bootloader
put magisk patched img in adb folder
fastboot flash recovery_ramdisk magisk.patched.img
Remove cable, boot and hold up
device boots to the first screen for eRecovery
same problem with TWRP
I've even factory wiped and booted straight to bootloader before flashing magisk or twrp, had to install the stock recovery_ramdisk to perform the wipes required
at this point i've no idea what to do so i'm looking for a non service firmware to flash, only the ones i've found are all 311 not above, can't find 320
sucks
EDIT: Downloading this now
https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=145556
Click to expand...
Click to collapse
Fastboot flash recovery_ramdisk magisk_patched.img
walkwitmeinhel said:
Fastboot flash recovery_ramdisk magisk_patched.img
Click to expand...
Click to collapse
Yep I know pal..doesn't work.
Have done this hundreds of times.
Don't worry about it, I'm getting rid of this turd of a phone.
1+7pro here I come.
dladz said:
I'm on a P20 Pro with EMUI 9.1 - 9.1.0.311
I cannot flash TWRP or Magisk boot img's, bootloader is still unlocked, FRP is fine, it's just not letting me play.
I pathced TWRP, Recovery_ramdisk, nothing is playing lol.
Perhaps it's the rom i'm on.
Thanks for the guide, but no good for the pro on 311 unfortunately.
Cheers
Click to expand...
Click to collapse
I have highlighted your problem above. This is a mate 20 x thread. You have a p20 pro.
facet_ said:
To have root on EMUI 9.1 we need https://androidfilehost.com/?fid=11410963190603907556
and ADB on the computer.
1. connect the phone to the computer, turn on the USB debugging mode
2. In ADB: "adb reboot bootloader"
The phone will go off in fastboot mode.
The downloaded file is loaded with a command: "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00-b7f69238.img
5. We're rebooting with a command: "fastboot reboot, quickly disconnect the phone and hold the VOL+ at the same time (all the time from the restart)
The phone will enter the eRecovery mode and we normally click "Factory/WIPE" as if we were restoring the factory settings.
This will cause root (magisk) to save permanently.
Of course we need to unlock the bootloader, but now (10.06.2019) it is not a problem because they sell for $41 (I bought it on imei.by - paid PayPal)
I wrote this post because I've been working hard to get root for half a day and there were incomplete answers everywhere.
Translated with www.DeepL.com/Translator
Click to expand...
Click to collapse
Does this also work on my Huawei Mate 9?
And did you just patch the EMUI 9.1 recovery_ramdis via magisk or something else?
Doesn't work for me I have AL00 135
i had the same prob: the trick ist to keep Vol up and (!) Power at the same time until the blue bootschreen from the honor appears. Do it NOT as in earlier times: Do NOT realese power after the first vibration as before. After flashing the modyfied patched recovery (modyfied by magisk), keep both buttons until the blue honor bootscreen apears, then release the buttons & you will see only one text line (not the three), which indicates that the v10 is booting with root!
Anybody want to sell their rooted mate 20 x? United States only
Thanks
Does this work for Mate 20 non-X?!
facet_ said:
To have root on EMUI 9.1 we need https://androidfilehost.com/?fid=11410963190603907556
and ADB on the computer.
1. connect the phone to the computer, turn on the USB debugging mode
2. In ADB: "adb reboot bootloader"
The phone will go off in fastboot mode.
The downloaded file is loaded with a command: "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00-b7f69238.img
5. We're rebooting with a command: "fastboot reboot, quickly disconnect the phone and hold the VOL+ at the same time (all the time from the restart)
The phone will enter the eRecovery mode and we normally click "Factory/WIPE" as if we were restoring the factory settings.
This will cause root (magisk) to save permanently.
Of course we need to unlock the bootloader, but now (10.06.2019) it is not a problem because they sell for $41 (I bought it on imei.by - paid PayPal)
I wrote this post because I've been working hard to get root for half a day and there were incomplete answers everywhere.
Translated with www.DeepL.com/Translator
Click to expand...
Click to collapse
I've been looking for a way to install Magisk on a Huawei Mate 20 Lite (running EMUI 9.1 before) for weeks, and you gave me the solution (= reboot to eRecovery then wipe before the first boot) ! THANK YOU !!!
What I need to do is to downgrade the OS to Android 9 so I can unlock the bootloader.
How can I do the downgrade? I already have the special Harmony cable for the downgrade.