SOLVED UPDATED TO LAST OTA AND DID THE WHOLE TUTORIAL AGAIN.
Tried different USB ports. ( 3.0 / 2.0 )
{
"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"
}
Tried in 2 different PCs and 6 usb ports 2.0 and 3.0
Windows 8 and windows 10.
Have you tried using cmd (administrator) istead of PowerShell?
Lamizure said:
Have you tried using cmd (administrator) istead of PowerShell?
Click to expand...
Click to collapse
Yes
It's really strange... Have you unlocked the bootloader?
Yes " Device State - Unlocked "
It's due to the filename being too long. I found a different fastboot which allowed long filenames. Rename it to one letter like r.img or something and see if it works.
Had exact the same problem under Linux
People mention to change to another USB port but that did not help
What helped... if all stuff is correctly installed (adb, root rights, etc.)
1. Reboot into the bootloader (even if you are in already)
adb reboot bootloader
Click to expand...
Click to collapse
2. Then directly (use the arrow up key to really be fast enough) send the command for flashing (my file was called twrp.img)
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
If this doesn't work you could try (under Linux) to write a little script with just the two above commands or try
adb reboot bootloader && fastboot flash recovery twrp.img
Click to expand...
Click to collapse
It seems to be a timing problem... One might need to play around with the time between this two commands. E.g. wait until the bootloader screen is on the phone and directly issue the flash command. Sorry after it worked for me I did not bother to investigate it in more detail.
Related
I've tried rooting my Nexus 7 and not sure what's gone wrong.
{
"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 when I load CWM.
Prior to this point what I did was unlock the bootloader and then process to flash CWM, then load CWM and flash SuperSU from sdcard but it's gone a bit wrong.
Anybody got an ides what the hell I've done wrong?
UrbanDesigns said:
I've tried rooting my Nexus 7 and not sure what's gone wrong.
This is what happens when I load CWM.
Prior to this point what I did was unlock the bootloader and then process to flash CWM, then load CWM and flash SuperSU from sdcard but it's gone a bit wrong.
Anybody got an ides what the hell I've done wrong?
Click to expand...
Click to collapse
Hi, UrbanDesigns...
Are you sure you have the correct version of CWM installed on your Nexus 7 ?
The references in your screenshot to an SD Card are a bit odd, given the Nexus 7 doesn't have an SD Card.
(...and the most recent version for Nexus 7 of CWM is 6.0.3.6... your screenshot shows your version to be 6.0.2.3).
Download the correct CWM recovery image from here for either your 'tilapia' (3G & WiFi) Nexus 7 or your 'grouper' (WiFi only) Nexus 7... whichever one you have.
And fastboot flash it with...
Code:
fastboot flash recovery recovery.img
...where recovery.img is the actual name of your recovery image file. Personally, I just think it's easier to rename it to recovery.img, and then flash it. Less scope for typos at the command prompt.
Hope this helps... good luck.
Rgrds,
Ged.
I was following this.
For some reason windows says it does not recognize my device now, it says "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
I was following this:
http://forum.xda-developers.com/showthread.php?t=2150661
So I assume everything was correct.
The only difference is I used Minimal ADB and Fastboot
The tablet is fully functioning now but won't get recognized by my PC, it's listed as "Unknown Device" under "Other Devices"
When I try to manually select where the driver folder is it instantly fails and says windows was unable to install your unknown device
Hello. Some time ago I flashed stock rom ALE-L21C22B160 and I got blank page in "Motion control" so I went to Huawei site and I downloaded C432B170. Then I extracted boot, recovery and system, then I flashed it without any problems.
{
"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"
}
Then I simply did "fastboot reboot" and my device rebooted with the old firmware, nothing changed at all.
I think you also need to flash to Cust.img
EpicBas said:
I think you also need to flash to Cust.img
Click to expand...
Click to collapse
Thanks, it worked, but I can't get proper firmware, I'm always getting one of those:
- blank "Motion control" page
- phone getting into rescue mode due to some problem with boot.img
Can you give me a link to firmware that actually works and has motion control? Thanks.
Lotherad said:
Thanks, it worked, but I can't get proper firmware, I'm always getting one of those:
- blank "Motion control" page
- phone getting into rescue mode due to some problem with boot.img
Can you give me a link to firmware that actually works and has motion control? Thanks.
Click to expand...
Click to collapse
@Lotherad Try one of these which matches your phone http://huawei-updates.ru/ALE-L21.html
EpicBas said:
@Lotherad Try one of these which matches your phone http://huawei-updates.ru/ALE-L21.html
Click to expand...
Click to collapse
It says "Attention! Please update system again Error! Func NO : 11 (recovery image) Error NO : 2 (load failed!)". Oh man, is there any hope for me? :crying:
did you unlock the bootloader ? and enabled USB bedugging ? ( sorry if it's stupid question )
any way , here is a thread that you do not need to flash with fastboot via commands ( C432B052 Rom version ) , it will automatically do the job , and i think it would work fine for you , and also if you want to have marshmallow , you can simply follow the reste of the thread
Link : http://tundevs.blogspot.com/p/huawei-p8-marshmallow.html
good luck
I'm 63 years old & could do with some help - trying to flash my Moto G4 but no luck
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
/https://imgur.com/a/NBfrIcZ
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does so it disappears from the ADB Diver Installer / APK Installer
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything. I don't understand what I am doing wrong and am very stuck sadly
{
"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"
}
Would really appreciate some help!
Great, my pictures don't work. I don't understand why. But basically when I write fastboot flash recovery twrp.img (it is in the same folder as Minimal ADB and Fastboot), it says not found to a bunch of things and no such file or directory.
George425 said:
Great, my pictures don't work. I don't understand why. But basically when I write fastboot flash recovery twrp.img (it is in the same folder as Minimal ADB and Fastboot), it says not found to a bunch of things and no such file or directory.
Click to expand...
Click to collapse
Ask your question here in moto g4 forum you will gets answers correctly ,because that's where you should have asked, buts it OK here is the link https://forum.xda-developers.com/mo...hread-question-noob-friendly-t3526598/page175
And upload the photos in Google drive and turn on the link sharing feature and post the link there there are many people there to help you out. Don't worry, everything will be fine.
Thank you Dhanush-raj I will do that now.
This is the Xiaomi Mi A2's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Thanks ! I used this tool in my zuk z2 pro and is fantastic
Is it possible to used it for enabling cam2api?
GK_NL said:
Is it possible to used it for enabling cam2api?
Click to expand...
Click to collapse
Unfortunately no
help
when i try to flash a recovery (booting a recovery) the name of files change to strange things like "1ZHqTVOIAgWdUqtIh5WLxD" or "c0kpXH7r0OESNfLgZQCsOZboc0TkvtiKKwOeEAVAp3H", not letting me flash anything.
Kaito Akimoto said:
when i try to flash a recovery (booting a recovery) the name of files change to strange things like "1ZHqTVOIAgWdUqtIh5WLxD" or "c0kpXH7r0OESNfLgZQCsOZboc0TkvtiKKwOeEAVAp3H", not letting me flash anything.
Click to expand...
Click to collapse
It's because actually decryption is not working in the twrp
If my upgrade fails, how do I boot from the slot that I installed the crap on the inactive slot from so the phone boots to the old version before the update?
I wanted to know and found the answers. I'll post here in case anyone wants to know cause I found nothing on these forums:
How to Check if Partition Slot A or Slot B is Currently Active?via https://krispitech.com/check-partition-slot-a-b/
Make sure the smartphone is connected to the PC with a USB cable
Now boot the smartphone into Fastboot Mode
This process will vary from device to device but usually involves holding certain button(s) down during the boot cycle.
Open up a Command Prompt, Windows PowerShell, or a Terminal in the same folder as your ADB and Fastboot files
Type out the following command. . .
fastboot getvar all
. . .then press Enter on the keyboard
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device
{
"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"
}
In this instance, my device was currently using partition slot B.
How to Boot from One Active Partition Slot to Anothervia https://krispitech.com/change-active-partition-slot/
Boot the smartphone or tablet into Fastboot Mode
Connect the device to the PC with a USB cable
Open a Command Prompt, PowerShell, or Terminal and type out the following command. . .
fastboot --set-active=a
OR
fastboot --set-active=b and then press Enter on the keyboard
Make sure you get a successful OKAY response before restarting the device
So if my updates go pear-shaped, I should be okay. And if not, well, I'm not buying a OnePlus ever again cause I've had it with all the extra steps, headaches, and disappointments with this model.
Excellent guide, I like it.
Think check out TWRP too, I think ( not 100% ) but I think it can change slots for you too.