This thread is only for people who "pseudo" bricked it(like me) because of a non-working CWM.
1. get ADB Tools and a working/suppoted CWM (I'll post mine)
2. navigate through CMD to the folder. example: cd C:\ADB
3. bring your device in the bootloader mode through "adb reboot bootloader" (without the "" ofc)
4. in bootloader mode your device should be recognized as "FASTBOOT USB", if it doesnt just plug out and in the USB cable and wait some seconds.
5. Once it is recognized as FASTBOOT USB you can start flashing your custom recovery through "fastboot flash recovery recovery.img" (again, w/o "" ofc)
6. To test if everything went well go into RECOVERY using your volume buttons for navigation & power for choose. Now you can restart your device and be happy with it!
Related
EDIT# FIXED
If you come across this problem this how you fix it.
Make sure you have a ROM installed that you can boot to with "Boot Android (No BP)" or "BP HW Diag & Boot AP"
Download ADB (you should have this as you would of used it to unlock the phone). Once downloaded open CMD and CD to the folder.
Boot the phone up and set it to Fastboot.
Then:
type "fastboot devices" Press Enter.
type "fastboot erase recovery" Press Enter.
type "fastboot reboot"
The phone will reboot as normal now. Once you are back into Android you can flash CWM with ROM Manager or TeamWin Recovery with GooManager.
So am I screwed?
I wanted to play around without flashing a brand-new image onto my phone. In other words, I want adb as root without using "fastboot flash".
It turns out that con247's TWRP port can do it with a bit of tweaking:
Unlock (using htcdev)
Reboot into fastboot mode ('adb reboot bootloader' or just turn on the phone holding 'volume down')
fastboot boot twrp_debug.img
adb shell
This is nice: the 'fastboot boot' command doesn't modify anything -- it just boots from ram once.
twrp_debug.img is attached. It has sha1 sum 0e5423c085adf6755b95964c7ba56537bf0398e3.
(It's con247's with default.prop modified.)
I am having a REAL BUGGER of a time with my Xiaomi Redmi Note 3 Pro (Snapdragon)!
1. It is not recognized by ADB in Fastboot mode.
2. I suspect it shipped wit a vendor ROM, and I'm trying to flash latest Official MIUI Global Dev (Marshmallow) ROM, but I keep getting errors in MI Flash (screenshot attached).
3. I want to Flash TWRP, BUT ADB isn't working, AND I cannot get to the download page for the cracked bootloader.
4. Seriously considering Resurrection Remix ROM, instead, but most of the above issues still apply.
I am NOT new to custom recoveries, flashing ROMS, ADB etc, BUT I am dealing with a new PC (Windows 10 Home, 64 bit, like my old (dead) laptop), and I'm new to this device.
PLEASE HELP. (Quite frustrated)
Fastboot won't recognize adb commands you have to use fastboot.
What you can try is booting into emergency download mode and using my flash to flash it from there. I think it's " adb reboot edl" while the device is on with USB debugging or using the mi updater app ( tap the three dots I think).
I think that this is not the correct section for your question, and i dont know the procedure that you follow but try to follow this procedure:
-Connect the phone at pc with USB cable
-Make sure that debug mode and OEM unlock was abilitate in dev settings
-Copy twrp.img in adb folder
-Shut down the phone and press power botton and - vol buttons for enter in fastboot mode
-Run this commands by terminal open in adb folder
fastboot devices
-If fastboot recognize correctly the device run this command
fastboot fash recovery nameoftwrp.img
-After reboot the device with this command
fastboot reboot
When the phone reboot press immediatily vol + for enter in twrp
Good luck
GOT IT! FINALLY!
-I finally got ADB to connect, and was able to enter EDL through ADB.
-Re-downloaded ROM from web.
-Re-extracted.
-FLASHED SUCCESSFULLY!
-SETUP COMPLETED SUCCESSFULLY!
-YAY!
(I think the original download was corrupted, somehow.)
You have own risk
<<<<ROOT HUAWEI Y6 PRO>>>>>
Prerequisites:
Huawei Y6 pro (TIT-AL00)
ADB drivers (link: https://drive.google.com/file/d/0BzFHE8ZlasNyX2hLRlZLX2hBc1k/view?usp=sharingg)
ADB / Fastboot software (link: https://drive.google.com/file/d/0BzFHE8ZlasNyOWVsTVdLZ0hRQ1k/view?usp=sharing)
CWM Recovery file (link: https://drive.google.com/file/d/0BzFHE8ZlasNyekNYLWhuTE5sLXc/view?usp=sharing )
PreRoot Stock Rom put sd card (link: https://drive.google.com/file/d/0BzFHE8ZlasNyMUFydW9HbnRIY0U/view?usp=sharing
Steps to complete:
1. Install ADB Drivers
2. Unzip ADB software in C: drive
3. put CWM.img in C: drive
---------------------------------------------
4. now
5.Go to settings>about phone>press 7 times builder number
6.Go to developer options, turn on OEM unlock,turn on USB Debugging.
7. Connect phone by USB to computer
-------------------------------------------------------------------------------
8. Startup command prompt (Windows key + R, type cmd, enter)
9. In command prompt, type "cd "
10.In command prompt “adb” to get to the adb directory
11. In command prompt check if device is recognized (typing "adb devices" in the command prompt should show you this)
12. Now reboot the phone into fastboot by typing "adb reboot bootloader"
13. This should reboot the phone into fastboot mode (black screen, only showing "fastboot>" on the bottom
14. In the command prompt, type "fastboot devices" to see if the device is recognized. and get device id number
15.just copy this id number
Your screen should look something like this:
The next command will unlock your phone AND make a hard reset... if any data or settings would need to be preserved, please make a backup!
16. Now type in the command prompt:"fastboot oem unlock XXXXXXXXX " where XXXXXXXX is the unlock code you copied
17,Now unlock conformation for volume + button.
18. Then type in command prompt: "fastboot reboot". After this, your phone will reboot and reset.
19. When Phone is rebooted, make sure USB debugging is on again
(same as point 7)
20. Now reboot the phone into fastboot by typing "adb reboot bootloader"
21. This should reboot the phone into fastboot mode (black screen, only showing "fastboot>" on the bottom
22. In the command prompt, type "fastboot devices" to see if the device is recognized.
23. Now we are going to flash CWM Recovery: type in command prompt: "fastboot flash recovery CWM.img"
24. reboot into recovery by typeing into command prompt: " "fastboot reboot" while holding VOL+ on the phone.
25. When the options screen on the phone appears, press VOL- to select the recovery mode. This will boot into CWM recovery.
26. In CWM recovery mod and wipe menu, wipe data and go back to menu and go to munt... and format System and go back to menu
-You should install the Rom( Install zip... and select the PreRoot Stock Rom) and waiting for install be finish there in step .
27. When flashing is done, type into the command prompt: "adb reboot" to reboot the phone.
7-Your phone boot after 5 until 8 minute.
Credit of: Mahmoud Khorsan(IRAN) andrik22
ArEvoun
Hey there!
so, I just upgraded my z5c from MM CyanogenMod to this nougat ROM > [ROM][7.0][Stock][.33][3.7 b7][Deodex][DeBloat][Font][Stereo][Vulkan™] Xperia Loop™
Before the update I could enter TWRP without any problems.
Now, everytime I try to boot into recovery the phone simply reboots...
Things I've tried:
• Typed "adb reboot recovery" on CM
• Downloaded TWRP App to re-flash and click on "recovery reboot"
• Power up phone holding Volume Down
The phone is rooted with SuperSU.
The main reason I wanted to regain access to recovery is to re-root the phone with Magisk.
Thanks for your time.
1. install fastboot and fastboot drivers on your pc (if you don't have them obviously)
2. plug the phone into the pc using the usb cable while holding the volume + button (this way you will skip the adb part)
3. wait for the notification light to go blue
4. go into the fastboot directory
5. download the twrp "recovery.img" file and put it into the fastboot directory
6. hold shift while right-clicking into the directory where fastboot is
7. use the option to open a cmd into the directory
8. type in "fastboot boot recovery.img"
if your phone's fastboot drivers don't have signature (like it happened to me) download Zadig and create a signature for the driver
Hope this helps... i had the same problem and solved by doing this