Related
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
Ye, great chance that the emmc is damaged. But it still looks to me as if it is software damaged, not hardware, because of the successful flash of recovery. And it is on the same memory module.
Just as in the other post of this phone can u try this and give me the output of especially the flash of gpt.bin (partition table file). I never got an exact answer to it, for my liking, maybe i read over it.
If that doesn't flash (give me the output then i know for sure ), try flashing the boot.img and see what happens. I assume nothing will change from flashing the boot.img, but u gotta try something.
Next we can do is have a look at that intel flashing file, it looks promising. I never had to go to this part so i am out of general ideas (think outside the box maybe?). Maybe we can fiddle something from here. It looks to me like it can flash more than fastboot can, u just need the right files and some we can make, hopefully if i read the sources available to us right.
Hazou
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash gpt gpt_s
igned
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'gpt' (32 KB)...
OKAY [ 0.358s]
writing 'gpt'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 1.094s]
finished. total time: 1.460s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash motoboot
motoboot
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'motoboot' (23273 KB)...
OKAY [ 2.635s]
writing 'motoboot'...
(bootloader) flashing image dnx...
(bootloader) flashing image ifwi...
(bootloader) flashing image bos...
(bootloader) flashing image logo...
(bootloader) flashing image ulogo...
OKAY [ 2.338s]
finished. total time: 4.981s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash boot boot
_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'boot' (11264 KB)...
OKAY [ 1.243s]
writing 'boot'...
OKAY [ 1.549s]
finished. total time: 2.799s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash recovery
recovery_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'recovery' (11264 KB)...
OKAY [ 1.338s]
writing 'recovery'...
OKAY [ 1.563s]
finished. total time: 2.907s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash motobp mo
tobp
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'motobp' (17091 KB)...
OKAY [ 1.714s]
writing 'motobp'...
OKAY [ 76.674s]
finished. total time: 78.396s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash system sy
stem_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 9.377s]
writing 'system'...
OKAY [ 2.576s]
sending 'system' (102400 KB)...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
OKAY [ 11.154s]
writing 'system'...
FAILED (remote failure)
finished. total time: 25.509s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash cdrom cdr
om_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'cdrom' (53258 KB)...
OKAY [ 4.891s]
writing 'cdrom'...
FAILED (remote: Preflash validation failed)
finished. total time: 6.273s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot erase cache
erasing 'cache'...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase cache fail
FAILED (remote failure)
finished. total time: 1.897s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot erase userdata
erasing 'userdata'...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
FAILED (remote failure)
finished. total time: 8.110s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>
So it looks like only few partitions are broken but how to repair it without unlocking bootloader??
Hmm, it does flash a part of the system if I read it correct. After the first one it gives errors to all partitions after it.
Can u reboot to recovery now, we finally flashed it right. Didn't work last time.
The things I wanted to do with the Intel thingy, are already done with flashing motoboot. So the things I had there are done.
Verstuurd van mijn GT-P5110
Nope, still red logo on recovery. The same was flashed by RSD and same errors appeared as on fastboot. Only different is after flashing RSD I can turn normal powerup and phone restarts to red logo from AP Fastboot but after flashing fastboot commands an error appeared.
Chamelleon said:
Nope, still red logo on recovery. The same was flashed by RSD and same errors appeared as on fastboot. Only different is after flashing RSD I can turn normal powerup and phone restarts to red logo from AP Fastboot but after flashing fastboot commands an error appeared.
Click to expand...
Click to collapse
Yep, this happens because it has nothing to start.
There is just 1 more think I can think off, because all others are closed (locked) or don't work. Or if unlocked we still don't have access.
Does the command "fastboot oem format" does something?
Verstuurd van mijn GT-P5110
Completely forgot about this command, I'll try it after work.
FAILED (remote: Restricted OEM command)
Then its over I think. We can't flash a custom recovery and fiddle around with it. Because maybe by not asking for system/data partition at start etc u can reformat the emmc with parted or other application.
Sorry, only Motorola can fix it. Or u need to replace the motherboard maybe? But that's something else.
Oh, try 1 more thing. Is it possible to load a custom boot image by the command "fastboot boot (image)"? Don't think so, but who knows. So u won't flash it.
Verstuurd van mijn XT890
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.412s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.614s
Bootloader blocks it??
Chamelleon said:
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.412s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.614s
Bootloader blocks it??
Click to expand...
Click to collapse
Yup, the defy could do it if i remember correctly. Hoped that this one would either. I am out of ideas now, but will have one more look. Don't expect anything, because we already tried most if not all the things we can do.
Edit:
All other things i can think of need to have adb access, and that can only be done by having an unlocked bootloader or root access. Because with root access u can flash a recovery even when u have a locked bootloader most of the time. But we don't have access to the system as well as the partitions, so we are stuck.
That Intel thingy can only flash the bootloader and the bootloader wont repartition the emmc. But we can try anyway if u want. Its a little bit different then the unbrick methode, just a little.
Verstuurd van mijn XT890
Today I flashed Samsung C3595 with partition table from S5610 and it's working well so "different" methods are not scary for me.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
Hi Chameleon.. i'm having a phone with similar issues (I created a post about it). I have tried steps one and two to no success. To unlock it do you do it via the official way (I ask because I don't know much, maybe there are other ways of doing it)
Yup, only official way.
Wysłane z Motorola RAZR i
here is the thing i talked about. Its just one more command with the unbrick method. But if u never try, u never know.
I assume u have all the files for the unbrick method still installed and on your PC. So u have the xFSTK driver and xfstk-dldr-solo.exe on your drive and working.
In the unbrick folder where the dnx and ifwi files are add the latest files from your latest firmware (dnx, ifwi and motoboot!).
Download the unbrick3.txt and rename to unbrick3.bat inside the folder with the original unbrick.bat
Now open a cmd shell inside the folder where the batch file is located. And then run unbrick3.bat.
After this try rsd lite again with the latest firmware u used.
Most likely it will not work... but ye, u gotta try.
I got this from an acer/asus device. It is the official unbrick methode from that device.
hey guys, i ve got the same problem. the phone stucks on the red M logo. i'm not familiar "aka" noob with this things. I wonder if anyone can give me a help?
I tried to wipe data and participation. the phone completes this commands but again stucks on the red logo.
hjahmetoglu said:
hey guys, i ve got the same problem. the phone stucks on the red M logo. i'm not familiar "aka" noob with this things. I wonder if anyone can give me a help?
I tried to wipe data and participation. the phone completes this commands but again stucks on the red logo.
Click to expand...
Click to collapse
Luckily, u don't have the same problem. U only have to search for a rsd lite flash guide. Flash your latest firmware that is available for your phone and country/brand. And all will most likely be good.
Hazou said:
here is the thing i talked about. Its just one more command with the unbrick method. But if u never try, u never know.
I assume u have all the files for the unbrick method still installed and on your PC. So u have the xFSTK driver and xfstk-dldr-solo.exe on your drive and working.
In the unbrick folder where the dnx and ifwi files are add the latest files from your latest firmware (dnx, ifwi and motoboot!).
Download the unbrick3.txt and rename to unbrick3.bat inside the folder with the original unbrick.bat
Now open a cmd shell inside the folder where the batch file is located. And then run unbrick3.bat.
After this try rsd lite again with the latest firmware u used.
Most likely it will not work... but ye, u gotta try.
I got this from an acer/asus device. It is the official unbrick methode from that device.
Click to expand...
Click to collapse
Yesterday I tried it and unfortunately nothing changed, still can't erase or write to those partitions.
XT890 Stuck on Red Logo. Probably damaged partitions
I woke up this morning to find that my Motorola XT890 is not working. I followed all the procedures for hard rest got the same result as listed below.
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
Contacted Motorola customer service, followed all the procedures as prescribed by Motorola customer service still stuck at Red Logo. Motorola has requested that I send it in for repair. The phone is 11 months old and under warranty. The unfortunate thing is that this is the second time I am sending the phone to Motorola for repair.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.
I've been trying other things with no success.
I've installed windows on a VM and rebooted the phone into fastboot mode. When I try to list devices in fastboot I get the '?' answer as if the phone wasn't recognised.
Device drivers seem to be installed as no missing drivers appear in the device manager.
How can I fix this?
Thanks in advance!
UPDATE: Added some more info
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.017s
antoniovazquezblanco said:
After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.
Click to expand...
Click to collapse
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.
g4b3rm4n said:
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.
Click to expand...
Click to collapse
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!
antoniovazquezblanco said:
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!
Click to expand...
Click to collapse
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too
g4b3rm4n said:
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too
Click to expand...
Click to collapse
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!
antoniovazquezblanco said:
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!
Click to expand...
Click to collapse
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?
g4b3rm4n said:
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?
Click to expand...
Click to collapse
Is this also happening to you?
I would like to be able to use fastboot boot for some kernel testing... It seems there's source code for kernel building both from Huawei and the comunity and it would be nice to have a free kernel as a base for cm devel...
It is also 00:50 here (Spain)... Tomorrow will be another day, no hurry
1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.
Kostyan_nsk said:
1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.
Click to expand...
Click to collapse
Thank you Kostyan_nsk! I really appreciate you sharing your knowledge .
About 2 I thought the same but I was not sure... so why not trying...
About 3 do you know what are the supported commands or where to find that information? It would be nice to have a post in the developers section with some documentation for those who want to perform tests with the device .
I have a T-Mobile version LG L90 D415 that I'm trying to flash with Lineage OS 14.1 but am having the worst luck.
Here's what I've got so far:
Rooted via DP Tools
installed flashify
installed TWRP using flashify (when running twrp it gave me some message about not being permanent...??)
flashed lineage os
forgot to flash gapps
tried to get back to twrp but its on stock recovery now
root missing
phone boots to lineage os but thats it
I wanna start over and recover this phone and do everything the right way. DP tools cant root the phone anymore and gets stuck after it pushes the files, says waiting for LG Serial port...
can someone please help?
flash kdz in download mode and startover. Search for tutorial on this forum.
kyva1929 said:
flash kdz in download mode and startover. Search for tutorial on this forum.
Click to expand...
Click to collapse
I followed the guide, it doesn't work.
The phone isn't recognized by the computer in download mode, and the flash program doesn't recognize the phone and doesn't proceed.
on top of all this, my computer BSOD when I turn on ADB Debugging and set the USB to "File Transfer"
not sure how to fix BSOD
Also, what is software download mode? Is that same as Download Mode when I turn off phone and hold up key and plug in usb cable?
Yo
AcuraKidd said:
I have a T-Mobile version LG L90 D415 that I'm trying to flash with Lineage OS 14.1 but am having the worst luck.
Here's what I've got so far:
Rooted via DP Tools
installed flashify
installed TWRP using flashify (when running twrp it gave me some message about not being permanent...??)
flashed lineage os
forgot to flash gapps
tried to get back to twrp but its on stock recovery now
root missing
phone boots to lineage os but thats it
I wanna start over and recover this phone and do everything the right way. DP tools cant root the phone anymore and gets stuck after it pushes the files, says waiting for LG Serial port...
can someone please help?
Click to expand...
Click to collapse
So you said it boots up to lineage OS right? if so go to setting and scroll down to developer options. if you don't see those then you have to go to ABOUT PHONE and tap build number 7 times. Then after you get into developer options, there is a ADVANCED RESTART which is usually unchecked . Check that and then download twrp from this link: https://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150 once you have it downloaded flash is using flashily. Then hold down the power button until you see the menu pop up with power of restart.. tap on restart and you will see many options and you need to tap on recovery. Once your'e in your recovery mode you can flash anything you want from there on it should work fine. Now you said you don't have any root access so you can't flash. If this is true then you need to flash the recovery with ODIN when flashing from Odin search on the internet on how to do that. I am also attaching the super su that you can flash using recovery this is for lineage OS only. I never use the Dp tools they never work my lg d415 for some reason. Hope you get your phone fixed. Sorry for my bad English.
AcuraKidd said:
I followed the guide, it doesn't work.
The phone isn't recognized by the computer in download mode, and the flash program doesn't recognize the phone and doesn't proceed.
Click to expand...
Click to collapse
This plus what you said about the bsod. You need to uninstall existing lg mobile driver, and reinstall ones found from guides.
Search how you can go in device manager and see ghost devices. Find the android devices that uses the lg driver which crashes your computer, uninstall the driver there and restart over.
edit: Just noticed you have a working lineage os. I think you might need to reflash laf partition to get the lg download mode back. Backup before you proceed.
kyva1929 said:
This plus what you said about the bsod. You need to uninstall existing lg mobile driver, and reinstall ones found from guides.
Search how you can go in device manager and see ghost devices. Find the android devices that uses the lg driver which crashes your computer, uninstall the driver there and restart over.
edit: Just noticed you have a working lineage os. I think you might need to reflash laf partition to get the lg download mode back. Backup before you proceed.
Click to expand...
Click to collapse
I have a backup of my laf from when I first started. How do I flash it?
Can you point me towards working LG drivers?
AcuraKidd said:
I have a backup of my laf from when I first started. How do I flash it?
Can you point me towards working LG drivers?
Click to expand...
Click to collapse
You don't need to reinstall the drivers on windows 10 for adb, just uninstall the drivers, unplug and then plug back in your phone with adb enabled to reinstall the drivers automatically with windows 10. Also when you try to boot into download mode do you see something about fastboot.
0000.0000.00 said:
You don't need to reinstall the drivers on windows 10 for adb, just uninstall the drivers, unplug and then plug back in your phone with adb enabled to reinstall the drivers automatically with windows 10. Also when you try to boot into download mode do you see something about fastboot.
Click to expand...
Click to collapse
I tried what you said, uninstalled all the old drivers and simply plugged in the phone with adb debugging on. Seems that computer no longer has bsod when setting the phone to usb file transfer while having debugging on
in terms of download mode, i attached a screenshot of what comes up. When trying to run root, the dialog box gets stuck at "waiting for LG serial port...." then "waiting for device"
AcuraKidd said:
I tried what you said, uninstalled all the old drivers and simply plugged in the phone with adb debugging on. Seems that computer no longer has bsod when setting the phone to usb file transfer while having debugging on
in terms of download mode, i attached a screenshot of what comes up. When trying to run root, the dialog box gets stuck at "waiting for LG serial port...." then "waiting for device"
Click to expand...
Click to collapse
Do you have fastboot?
0000.0000.00 said:
Do you have fastboot?
Click to expand...
Click to collapse
yes
AcuraKidd said:
yes
Click to expand...
Click to collapse
To flash the laf to get download mode back do fastboot flash laf.IMG where laf.IMG is the filename of the laf backup.
---------- Post added at 10:19 PM ---------- Previous post was at 10:17 PM ----------
Also, could you please run fastboot OEM device-info and send me the result of that command.
after running the fastboot OEM device-info command, i get < waiting for any device >
it just stays there...
if i do adb devices, i get
List of devices attached
LGD415a453b27c device
sorry, ignore the above, i forgot to go into download mode...
below are results after putting into download mode:
fastboot oem device-info
FAILED (remote: unknown command)
finished. total time: 0.004s
fastboot flash laf laf.IMG
target reported max download size of 536870912 bytes
sending 'laf' (22528 KB)...
OKAY [ 0.714s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.738s
AcuraKidd said:
sorry, ignore the above, i forgot to go into download mode...
below are results after putting into download mode:
fastboot oem device-info
FAILED (remote: unknown command)
finished. total time: 0.004s
fastboot flash laf laf.IMG
target reported max download size of 536870912 bytes
sending 'laf' (22528 KB)...
OKAY [ 0.714s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.738s
Click to expand...
Click to collapse
Maybe try https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429 then
0000.0000.00 said:
Maybe try https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429 then
Click to expand...
Click to collapse
I don't think I need this method as the phone is not bricked
Are there any other commands to try?
AcuraKidd said:
I don't think I need this method as the phone is not bricked
Are there any other commands to try?
Click to expand...
Click to collapse
Did you try reflashing twrp in flashify already?
---------- Post added at 11:31 PM ---------- Previous post was at 11:22 PM ----------
While booted into lineage, also try running
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
After that try rebooting into fastboot and flashing twrp.
0000.0000.00 said:
Did you try reflashing twrp in flashify already?
---------- Post added at 11:31 PM ---------- Previous post was at 11:22 PM ----------
While booted into lineage, also try running
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
After that try rebooting into fastboot and flashing twrp.
Click to expand...
Click to collapse
I cant flash twrp using flashify because i have no root, below are the results of your commands
C:\Users\Mark\Desktop\fastboot_adb(1.0.36)_110716_r24.0>adb shell
7[r[999;999H[6n8w7:/ $
w7:/ $ su
/system/bin/sh: su: not found
127|w7:/ $ dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
dd: /dev/block/platform/msm_sdcc.1/by-name/laf: Permission denied
1|w7:/ $ dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd: /dev/block/platform/msm_sdcc.1/by-name/laf: Permission denied
1|w7:/ $
C:\Users\Mark\Desktop\fastboot_adb(1.0.36)_110716_r24.0>fastboot getvar all
(bootloader) display-panel:
(bootloader) charger-screen-enabled: 0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x38400000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x102180400
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x80000000
(bootloader) unlocked: no
(bootloader) secure-boot: yes
(bootloader) version-hardware: rev_10
(bootloader) variant: w7_tmo_us Toshiba 8GB
(bootloader) serialno: LGD415a453b27c
(bootloader) kernel: lk
(bootloader) product: W7_TMO_US
all:
finished. total time: 0.018s
AcuraKidd said:
I cant flash twrp using flashify because i have no root, below are the results of your commands
C:\Users\Mark\Desktop\fastboot_adb(1.0.36)_110716_r24.0>adb shell
7 [r [999;999H [6n 8w7:/ $
w7:/ $ su
/system/bin/sh: su: not found
127|w7:/ $ dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
dd: /dev/block/platform/msm_sdcc.1/by-name/laf: Permission denied
1|w7:/ $ dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd: /dev/block/platform/msm_sdcc.1/by-name/laf: Permission denied
1|w7:/ $
Click to expand...
Click to collapse
Install kingroot and try to root your phone with it and then try flashing twrp with flashify.
Hi, Please help me, My P20 PRO CLT-L29 is bricked during re-branding. FRP is locked and boot-loader is re-locked. I am stucked at recovery. Factory reset from recovery finishes successfully but still the device doesn't boot up. E-recovery shows "gettting package info failed." Tried DNS e-recovery method through firmware finder but the DNS is not working!
Is there any way to unbrick my device?
fastboot oem get-product-model
(bootloader) CLT-L29
C:\Minimal ADB and Fastboot>fastboot oem get-build-number
(bootloader) :CLT-L29 8.1.0.160(C432)
C:\Minimal ADB and Fastboot>fastboot getvar vendorcountry
vendorcountry: hw/eu
C:\Minimal ADB and Fastboot>fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
C:\Minimal ADB and Fastboot>fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :CLT-L29 8.1.0.154(C185)
QuazIqbal said:
Hi, Please help me, My P20 PRO CLT-L29 is bricked during re-branding. FRP is locked and boot-loader is re-locked. I am stucked at recovery. Factory reset from recovery finishes successfully but still the device doesn't boot up. E-recovery shows "gettting package info failed." Tried DNS e-recovery method through firmware finder but the DNS is not working!
Is there any way to unbrick my device?
Click to expand...
Click to collapse
FINALLY SOLVED by flashing the firmware files through dload method via USB- OTG. You can search and download firmware files on https://androidhost.ru/search.html
Feel free to ask if you face any difficulties.
QuazIqbal said:
FINALLY SOLVED by flashing the firmware files through dload method via USB- OTG. You can search and download firmware files on https://androidhost.ru/search.html
Feel free to ask if you face any difficulties.
Click to expand...
Click to collapse
How did you flash firmware via usb otg? Could You please link tutorial?
forever_lol said:
How did you flash firmware via usb otg? Could You please link tutorial?
Click to expand...
Click to collapse
I didn't find any guide. I was in fact guided by Mr. oslo83 in a telegram group https://t.me/flashing_huawei
The process is very simple. I will try to reproduce the steps I followed as under :-
1) Download the correct firmware for your device according to your region from https://androidhost.ru/search.html and extract it. (Note :The downloaded firmware must be of the same build number installed or superior bcoz downgrading can hard brick your device)
2) After extraction you will find a folder named "dload" (This is our concerned folder, pay attention!)
3) Inside the 'dload' you will find one zip file named 'update_sd', extract its content within the dload folder but keep the un-extracted zip also as it is.
4) Apart from 'update_sd.zip' you will also find two subfolders inside 'dload'.
In my case the two subfolders were '... 'update_sd_CLT-L29_hw_eu' & ''update_sd_CLT-L09_hw_eu'
5) Since my model was CLT-L29 therefore I deleted the subfolder named 'update_sd_CLT-L09_hw_eu'
6) Now rename the subfolder "update_sd_CLT-L29_hw_eu" to "CLT-L29_hw_eu" and on opening it you will find a same named zip inside. Like before extract its content within the subfolder and also keep the zip file intact'
7) That's it. Your 'dload' folder is now ready to be transferred to the USB drive for flashing.
8) Attach your OTG-USB to your device and restart your device. While restarting keep pressing Volume UP & DOWN key simultaneously. Your phone will now enter into dload mode and will start flashing after verifying firmware.
9) Bingo! you have now fully working stock rom. (Bootloader locked, FRP Unlocked, E-recovery functional again)
Note: Before doing this operation make sure your USB drive is perfectly working and exFAT formatted. You can check your drive by H2testW on windows. In my case my first USB drive was faulty and that's why dload was giving me errors.
Thank You very much! Last question Did you format your sd card as FAT32 or exfat?
forever_lol said:
How did you flash firmware via usb otg? Could You please link tutorial?
Click to expand...
Click to collapse
forever_lol said:
Thank You very much! Last question Did you format your sd card as FAT32 or exfat?
Click to expand...
Click to collapse
Oops forgot to mention, exFAT.
[@dabakh Fall:
C:\Users\IWOL CAPITAL\Desktop\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot devices
D5F0218427005480 fastboot
C:\Users\IWOL CAPITAL\Desktop\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot oem get-model
...
FAILED (remote: Command not allowed)
finished. total time: 0.022s
C:\Users\IWOL CAPITAL\Desktop\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot oem get-product-model
...
(bootloader) CLT-L29
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\IWOL CAPITAL\Desktop\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot oem get-build-number
...
(bootloader) :Chipset-boston 8.1.0.001(0248)
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\IWOL CAPITAL\Desktop\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
C:\Users\IWOL CAPITAL\Desktop\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.037s
C:\Users\IWOL CAPITAL\Desktop\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :CLT-AL00 8.1.0.171(C00)
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\IWOL CAPITAL\Desktop\SRKToolHuawei-Lod-Chong-V2.0-20161002>CLT-AL00 8.1.0.171(C00)][/B]
QuazIqbal said:
4) Apart from 'update_sd.zip' you will also find two subfolders inside 'dload'.
In my case the two subfolders were '... 'update_sd_CLT-L29_hw_eu' & ''update_sd_CLT-L09_hw_eu'
Click to expand...
Click to collapse
Hi I've just made my own attempt and it eventually worked like a charm. only one thing: In my case those subfolders name were CLT-L29_hw_eu and CLT-L09_hw_eu. It's important not to rename them. (I removed L09 as my model is L29) Firstly I renamed it to update_sd_CLT-L29_hw_eu and software update failed. I restored then the original name (and also deleted meta-inf folders) and volia worked like a charm !
*Once again thank You very much for Your help. It can be life saver in future
forever_lol said:
Hi I've just made my own attempt and it eventually worked like a charm. only one thing: In my case those subfolders name were CLT-L29_hw_eu and CLT-L09_hw_eu. It's important not to rename them. (I removed L09 as my model is L29) Firstly I renamed it to update_sd_CLT-L29_hw_eu and software update failed. I restored then the original name (and also deleted meta-inf folders) and volia worked like a charm !
*Once again thank You very much for Your help. It can be life saver in future
Click to expand...
Click to collapse
I'm glad it worked. Yes... Yes.... I had also renamed it but forgot to mention it. I have updated the info. Thanks for pointing it out. In my case I didn't removed meta-inf folders and luckily it didn't pose as problem.
dabakh said:
[@dabakh Fall:
C:\Users\IWOL CAPITAL\Desktop\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
C:\Users\IWOL CAPITAL\Desktop\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :CLT-AL00 8.1.0.171(C00)
OKAY [ 0.000s]
finished. total time: 0.000s
[/B]
Click to expand...
Click to collapse
I think your case is of Xloader downgrade brick, as per your vendor country info I think you can try to flash CLT-L29 C432 build by the process mention above.
https://androidhost.ru/7BY
Hi,
Same problem after a rebrand but after done many "bullshits" my P20P have a black screen.
What is strange is that i can use fastboot.
Does OTG solution will help me?
Any sugestions for my trouble?
THX ^^
fastboot devices
AKC0218928000925 fastboot
fastboot oem get-model
FAILED (remote: 'Command not allowed')
fastboot oem get-product-model
(bootloader) CLT-L29
OKAY [ 0.002s]
fastboot oem get-build-number
(bootloader) :CLT-AL01 8.1.0.167(C00)
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :CLT-AL01 8.1.0.167(C00)
Click to expand...
Click to collapse
aux6d said:
Hi,
Same problem after a rebrand but after done many "bullshits" my P20P have a black screen.
What is strange is that i can use fastboot.
Does OTG solution will help me?
Any sugestions for my trouble?
THX ^^
Click to expand...
Click to collapse
I think OTG dload solution should work. Is your bootloader locked? What about FRP? What was the last firmware you flashed?
How l flash it with what tools?
dabakh said:
How l flash it with what tools?
Click to expand...
Click to collapse
No any tool is required. You just have to transfer the dload folder to your EX-FAT formatted USB drive and keep pressing the volume up & down during restart of your mobile. Your mobile will automatically detect the dload folder and start verifying and flashing the firmware.
The detailed steps is outlined in post no. #4 of this thread. Hope it well help you out.
QuazIqbal said:
I think OTG dload solution should work. Is your bootloader locked? What about FRP? What was the last firmware you flashed?
Click to expand...
Click to collapse
Bootloader unlocked & FRP unlocked.
I flashed the phone with the 9.0 CTL29 with FunkyHuawei but fail.
I tried OTG flash, nothing... Only fastboot access. Always BlackScreen ! lol
aux6d said:
Bootloader unlocked & FRP unlocked.
I flashed the phone with the 9.0 CTL29 with FunkyHuawei but fail.
I tried OTG flash, nothing... Only fastboot access. Always BlackScreen ! lol
Click to expand...
Click to collapse
Since your BL & FRP is unlocked you can try to flash system image of your original build CLT-AL01 (try the most recent) via fastboot.
There is a tool which will assist you doing that https://pro-teammt.ru/huawei-multi-tool/ though I haven't tried this but you can dig into it. It might prove beneficial to you. You may get more info from their telegram group. https://t.me/Multi_Tool_8_TeamMT
Good luck buddy
can you possibly do a CMD Tree of the Dload folder? its not working for me and i need help asap
---------- Post added at 04:29 PM ---------- Previous post was at 04:19 PM ----------
im in the same situation as OP too
I tried with the HuaweiTool to flash the phone with the original firmware CTL-AL01 :
System.img / Cust.img / Kernel.img...
But nothing work.
Blackscreen forever...
I'm done with this phone...
Can someone post a picture of how the files are layed out on the USB please
aux6d said:
Hi,
Same problem after a rebrand but after done many "bullshits" my P20P have a black screen.
What is strange is that i can use fastboot.
Does OTG solution will help me?
Any sugestions for my trouble?
THX ^^
Click to expand...
Click to collapse
hello i also have the same problem except that my phone is unlock and frp lock,
the usb-otg dload method can work with my version? knowing that i'd like to delete twrp and go back to stock recovery thanks you
fastboot oem get-product-model
(bootloader) CLT-L29
fastboot oem get-build-number
(bootloader) :CLT-L29 9.0.0.108(C432E5R1P7log)
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: 'FAIL:need all image flashed!')
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :CLT-L29 9.0.0.108(C432E5R1P7log)
Got my bootloader unlocked, but when trying to flash or unlock critical I get an error and it goes to a screen with the razer logo, "powered by android" at the bottom, and super small text in the upper left "press any key to shutdown"
and shows this in the cmd window:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.027s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a arter97-kernel-r9-20190607.img
< waiting for any device >
target didn't report max-download-size
sending 'boot_a' (30140 KB)...
FAILED (command write failed (No error))
finished. total time: 0.011s
I do have the full sdk package and used android studios sdk manager to get the latest google usb driver.
HTML:
EDIT: Also I'm on a global version (bought it on razer's website)
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
blackknightavalon said:
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
Click to expand...
Click to collapse
Running the flash_all script just throws it into that shutdowns again and keeps going into it anytime I go back into fastboot mode.
also gives me this
Code:
C:\Users\zacha\Desktop\platform-tools>fastboot devices
my S/N fastboot
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed.
or is just sits there likes this:
Code:
C:\Users\zacha\Desktop\platform-tools>adb reboot bootloader
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
blackknightavalon said:
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
Click to expand...
Click to collapse
Just does the exact same thing.
Cyclo_sarin said:
Just does the exact same thing.
Click to expand...
Click to collapse
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
BeardKing said:
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Have ya'll tried using this tool?? It works I'm telling you it'll solve any issues you have with ADB and or FASTBOOT period....
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445