Related
How do you guys boot to fastboot if you have turned your phone off? I mean the actual fastboot ("black Huawei logo") not the recovery and not the pink bootloader. I can get to it if I reboot my phone if I press reboot and then bootloader, but is it possible without it?
Seems like there is no other way. Right now I can start it in fastboot mode with "adb reboot bootloader" and the custom ROM I have on right now. If anyone wants details, post here.
-e-
Weird discovery I made. While trying to flashall it says the device is "swordfish"... If I flash system.img separately it says "no partition table exists". Anyone has used fastboot before?
Nice. With the new Android version, the product shows MSM7630_SURF. It now properly boots to fastboot without going to charging too, so thats an update.
Blefish said:
Seems like there is no other way. Right now I can start it in fastboot mode with "adb reboot bootloader" and the custom ROM I have on right now. If anyone wants details, post here.
Click to expand...
Click to collapse
Thanks! I was trying to set up my UDEV (51-android.rules) and your post helped me boot into the bootloader mode to get the right idVendor & idProduct codes.
Blefish said:
Seems like there is no other way. Right now I can start it in fastboot mode with "adb reboot bootloader" and the custom ROM I have on right now. If anyone wants details, post here.
-e-
Weird discovery I made. While trying to flashall it says the device is "swordfish"... If I flash system.img separately it says "no partition table exists". Anyone has used fastboot before?
Click to expand...
Click to collapse
I tried fastboot, but I just get a black screen with huawei logo. No any function, no adb connection, no menu entries or anything and no buttons work. And I can exit only by remove battery. Is this right?
dancer_69 said:
I tried fastboot, but I just get a black screen with huawei logo. No any function, no adb connection, no menu entries or anything and no buttons work. And I can exit only by remove battery. Is this right?
Click to expand...
Click to collapse
There's an external tool called fastboot which handles that. There you can reboot or even continue the boot.
Fastboot is broken as far as I know, no partition table exists.
Sent from my U8800
You mean the fastboot from adb tools which can used from command line? This cannot work because there isn' t adb connection on bootloader mode.
Or is another tool which can be flashed or something to device?
dancer_69 said:
You mean the fastboot from adb tools which can used from command line? This cannot work because there isn' t adb connection on bootloader mode.
Or is another tool which can be flashed or something to device?
Click to expand...
Click to collapse
I think you are confusing pink screen with fastboot/bootloader. The fastboot is the node where it stays in the Huawei logo.
Sent from my U8800
No, I know the difference. I get this screen, but nothing else. On my previous device, fastboot has some functions included flash rom, reboot and some else that I don't remember. I also could from adb to use fastboot command.
On X5 I just get this screen.
Maybe they disabled that in B522 too, I am not sure. It was bugged anyway. I only tested it on B138 and B518.
Yes, I have 522 and I thought this too. I've tried on B138 1-2 times and was the same huawei logo screen only too. I didn' t tested it more because I thought that just this mode is disabled and used pink mode only. In B138 sould appear something else on screen, or only commands from adb work?
Hi all,
my nexus wont start after (failed?!) flashing with factory image. bootloader and recovery mode are accessable. i have no backup so i need to flash a new img, but my tablet wont be recognized by my computer anymore(adb drivers not working?!). i tried to deinstall and reinstall the adb drivers alrdy. Device manager shows nexus 7 as Android Phone with "Android Bootloader interface" i cant install adb drivers while in bootloader. in recovery mode i succeeded installing the adb drivers and the tablet is shown correctly in device manager... i need help dont know what to do :crying: .. any suggestions ?
ADB and fastboot drivers are different.
Pirateghost said:
ADB and fastboot drivers are different.
Click to expand...
Click to collapse
yes .. what are u trying to tell me? dont get it.. i used nexus root toolkit to help me apply those drivers.. but it wont work for bootloader/fastboot mode.. i cant flash my tablet because my device wont be recognized by my pc.. im stuck at the bootloaderscreen/fastbootmode....
http://bit.ly/Zqk7pm
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
oads said:
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
Click to expand...
Click to collapse
SMH
i filled it in for you.....
Pirateghost said:
SMH
i filled it in for you.....
Click to expand...
Click to collapse
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
no. ADB and fastboot require separate drivers. just install the drivers required for n7 fastboot. there was a link in that list.
there are tutorials here on xda, as well as youtube videos and tutorials on other sites. take a little initiative and learn the ropes. it will help you out later on.
oads said:
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
Click to expand...
Click to collapse
Just relax and take your time.
If your tablet can go into fastboot mode, it is fine and will get better; the only thing standing between it's current state and being brought back to life is a little learning on your part.
Now you see what the problems are with using a toolkit - because they hide all the gory details from you, when the smallest thing goes wrong you are totally helpless due to a lack of understanding about what things are going on underneath the hood. And as it turns out, what "goes on under the hood" isn't really all that complicated either if you do things the full manual way.
Which is not to say that you can not simply just use the toolkit again; if you previously successfully installed drivers that allowed you to talk to the tablet in all of these modes:
- fastboot
- adb w/ custom recovery booted
- adb with Android booted
then it is not evident that you need to be fooling with drivers.
I suggest you read this thread, from start to finish
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Then, go over to your toolkit thread and read it from start to finish. You will see that there are & have been plenty of people in circumstances nearly identical to yours.
good luck
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
oads said:
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
Click to expand...
Click to collapse
that does not sound like a problem to me at all.
You communicate with the device using the "fastboot" program when it is in bootloader/fastboot mode, and with the "adb" program when it is in custom recovery boot.
What you see in the device manager appears to be completely normal - In different modes it shows up in different places. It's not supposed to show up with the same driver in different modes.
Code:
fastboot devices
will show you whether you are communicating successfully with the device when it is in bootloader/fastboot mode, and
Code:
adb devices
will show you whether you are communicating successfully with the device in recovery mode.
I suppose your toolkit has some stoopid menu or buttons someplace that will allow you to test for exactly the same thing. Now all you need to do is stop posting here and read a little bit.
good luck
bftb0 said:
Now all you need to do is stop posting here and read a little bit.
good luck
Click to expand...
Click to collapse
well i did read quite a lot today :crying: i cant find my device when i type in adb devices, im pretty sure i have the right drivers installed since i followed the instructions step by step.
this guy seems to have the same problem: http://forum.xda-developers.com/showthread.php?t=1808076
could someone tell me if this could be a possible solution :http://stackoverflow.com/questions/...e-over-usb-via-adb-devices-from-windows-7-x64
also would it be possible to just get into the bootloader (since thats the purpose of adb drivers and i can do this) and just proceed with fastboot commands ? if i type in fastboot devices the tablet will show up...
In your first post, you indicated that you couldn't connect to the tablet that was in bootloader mode with adb.
And then you were told - once vaguely and once quite specifically - that *nobody* can communicate with the tablet using adb when the tablet is in bootloader/fastboot mode.
As stated previously, use the "fastboot" program when the tablet is in bootloader mode, and use the "adb" program when the tablet is booted to the custom recovery (or the regular android boot if USB debugging has been enabled).
You can use either one of these modes to effect a rescue so long as they are working correctly - they don't need to both be working. Eventually you would want that to be the case, but for the moment why don't you just stick with what is working for you.
If you get a device ID printed when you execute "fastboot devices" when the tablet is in boot loader/fastboot mode, that is all you need to reinstall a factory ROM, using nothing but fastboot.
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
oads said:
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
Click to expand...
Click to collapse
Well, I can't see what instructions you are following, and there is a possibility of sensitivity to an exact sequence. In particular, is a
fastboot reboot-bootloader
performed after the bootloader is flashed, but before the radio is flashed? It might be important that you are performing the radio flash from one bootloader vs. the other. Just a guess. (Along the same lines, do you see something unexpected happening, such as a boot to the recovery after the radio flash command?)
There are some other threads on this I think. (I have a grouper device not tilapia) But I thought that those threads were about problems with radio flashing when a custom recovery (rather than a stock recovery) was on the phone, but that was for applying the OTA package for tilapia rather than flashing directly from fastboot.
-------------------------------------------------------
[Edit] whoops, wait a minute.... "cannot load"
When you run fastboot from the command line, the file names you give are relative to the current directory. Did you move those image files into the same directory that you are executing the "fastboot" command from?
Alternately you can specify the full pathname to wherever you unpacked the files, for instance
fastboot flash radio C:\myfolder\unpacked\googlen7\4.2.2\radio-tilapia-1231_0.17.0_1025.img
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
oads said:
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
Click to expand...
Click to collapse
I would complete the rest of the steps first and see if everything is still working. Your device *should* still work just fine with an old radio firmware. (Boot it up and see what radio firmware the OS reports on the Settings... about device... status page).
I'll pull down the tilapia image and tell you what MD5 I observe for the radio image.
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Pirateghost said:
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Click to expand...
Click to collapse
yes
SHA1
0798439d363beb145d9223a42ed9edf3de1a30f4 nakasig-jdq39-factory-0798439d.tgz
bb824d449f44d2ad43c5d2a463fe1244d2faf525 nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
f406ae9133c56200306d5c7d64d151f21e0be3c4 nakasig-jdq39/image-nakasig-jdq39.zip
MD5
ee8db1ed6ff1c007fe12136d4bc65cd8 nakasig-jdq39-factory-0798439d.tgz
276cb738e5b9e18a088b6a3eef8155ad nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
4cfa996b6513a7fa53db7cbfd1134396 nakasig-jdq39/image-nakasig-jdq39.zip
radio image is 16,777,216 bytes long
---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------
the google - provided instructions (flash-all.sh) have 10 second sleeps after the bootloader resets - are you waiting long enough?
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot flash radio radio-tilapia-1231_0.17.0_1205.img
fastboot reboot-bootloader
sleep 10
Also - something to check since you are rebooting the bootloader - does the device show up correctly in the Windows device manager? (Sometimes with soft reboots I have found the need to pull the USB cable and plug it back in to the PC).
Hello All
I've rooted and installed TWRP recovery. And accidently wiped all partitions (system, data, caches...). Currently no OS installed.
Tried installing Cyanogen mods and also default ROMs via TWRP but getting error saying
====
Unknown command "screenshot"
E: Unable to mount /spare
====
Also tried flashing default ROMs...same error . No luck.
Tried wiping all partitions again.
connected to my linux lap
Device is connected and listed while running command "lsusb". (USB data connection working)
But not detecting under adb devices also not shown under fastboot mode. (So no luck to flash via PC).
All forums saying "check usb debugging" to show under adb devices. How can I ..if there is no ROM
Also TWRP is restarting after some time.
-------------------*******helppp******************************
Hi,
I have the same problem, few post below.
During my searching I found this post, but I get error during
fastboot erase spare
It hard to say what wrong is with this partition.
Maybe you will be have more luck
Elokwentnyemu said:
Hi,
I have the same problem, few post below.
During my searching I found this post, but I get error during
fastboot erase spare
It hard to say what wrong is with this partition.
Maybe you will be have more luck
Click to expand...
Click to collapse
In my case, the phone is not listed under fastboot devices But it's connected to computer in fastboot mode and we can see the device is listed when command lsusb is executed.
antoponline said:
In my case, the phone is not listed under fastboot devices But it's connected to computer in fastboot mode and we can see the device is listed when command lsusb is executed.
Click to expand...
Click to collapse
I checked on Manjaro and my phone is present under fastboot. Try reinstall drivers or use other PC to connect by fastboot.
so sad for both of you guys i've already encountered this before try this any of these.
- use adb sideload via TWRP using stock firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip
- if you have a back up restore it, then boot to fastboot and flash the fastboot, boot and recovery of this firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip then boot to recovery and side again using this firmware.
- try this link if it's work http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
sorry guys i forgot how i managed to solve this i will update this thread. just always remember use always this firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip and back your current rom even if it's stock or custom this is most important. if you can access bootloader just do the flashing fastboot, boot and recovery this would be easy if you can access bootloader.
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Anubhav074 said:
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Click to expand...
Click to collapse
You need to install fastboot in pc and then flash the device to make it work.
You can prefer this thread
https://forum.xda-developers.com/g5...-flash-stock-romfactory-t3691396/post74221633
Anubhav074 said:
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Click to expand...
Click to collapse
You cannot unlock bootloader anymore. So try flashing normally. If your hardware is not damaged then you might me able to make it work.
debdeep98 said:
You cannot unlock bootloader anymore. So try flashing normally. If your hardware is not damaged then you might me able to make it work.
Click to expand...
Click to collapse
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Anubhav074 said:
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Click to expand...
Click to collapse
K.. install adb(https://www.androidfilehost.com/?fid=745425885120698566 ). If you had installed moto assistant then you'll have the drivers. If not then google motorola drivers and install them(http://www.motorola.com/getmdmwin ).
Once it's done. Open the folder where adb is installed.
Hold shift and right click>open command promt here.
At this point boot into the bootloader on your phone (fastboot mode).
On cmd type fastboot devices.
If your device is detected then it will show on screen.
If you get to this part.
Start flashing thru fastboot.
Get the files from google( or https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL)
Instructions to flash are in xda.
If you get failed to flash: security version downgrade then you're probably flashing an older firmware. Download the latest.
If you get failed to flash: preflash validation failed then there's not much you can do. Or atleast i don't know a solution to that.
its not detecting my device
Actually the problem is that it is not detecting my device when i give this command, although i have installed device drivers and adb also....This is is the problem
Anubhav074 said:
Actually the problem is that it is not detecting my device when i give this command, although i have installed device drivers and adb also....This is is the problem
Click to expand...
Click to collapse
Did you lenovo moto smart assistant to flash the device, you can try that as it will flash the device for you.
riyan65 said:
Did you lenovo moto smart assistant to flash the device, you can try that as it will flash the device for you.
Click to expand...
Click to collapse
yeah i tried that but when it is not verifying my phone when i select id (which is xt 1686) it says that phone can not be verified try again.i have tried every given id but it is refusing to accept my device.
Anubhav074 said:
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Click to expand...
Click to collapse
Here's a guide to flash stock firmware.
Try the linked Mini ADB & Fastboot, if your device isn't recognised try to connect it to another usb port or use another usb cable.
Are you sure that you're in fastboot mode when you type the commands?
Read the guide carefully.
You need:
Latest signed stock firmware:
Europe (RETEU):
https://drive.google.com/file/d/13WuhoogtAdoincAyTwCLvRj0d-Z9kL0P/view?usp=sharing
India (RETIN):
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
US (RETUS):
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
flashallO.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
Motorola drivers:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=sharing
Mini ADB & Fastboot
https://drive.google.com/file/d/1lLYfimKN1U5CJ9cfpTCkhtMiuG8EfXBZ/view?usp=sharing
1) Download the 8.1.0_OPS28.85-17-6-2 Indian firmware (it's the last one for the Moto G5+ (potter).
2) Install Mini ADB & Fastboot (best place is the root directory of C:/ or how the partition/hard drive is named where your OS resists), not in program files or another folder.
3) Extract the firmware to that ADB & Fastboot folder.
4) Download my "flashallO.bat" and move it to that folder too.It removes the need for you to manually flash all partitions, just double-click it and it'll run all the commands for you.
5) Download and install Motorola device drivers.The program is called "Motorola Device Manager".
6) Reboot your phone to the bootloader. To do this, turn it off, then hold down the power and volume down buttons until you see a bugdroid undergoing open-heart surgery.
7) Connect the phone to your PC with your USB cable. Type
Code:
fastboot devices
to check if your device is connected. A serial number should be shown.
8) Run the flashallO.bat script. (Caution: This will wipe your device completely!) It will take some time to flash, just be patient and don't worry.
NOTE: If the command window appears for a brief moment then disappears, device drivers may not be installed. Ask again then.
9) Once the command window closes, it should have completed the flashing process and you are safe to press the power key on the phone to start Android. Just make sure that the text near the buttons reads "START".
Sent from my Moto G5 Plus using XDA Labs
Followed your guide this time my device is getting detected and when typed command adb devices its giving some number also but the image you provided is not flashing it.Dont know why please help
Anubhav074 said:
Followed your guide this time my device is getting detected and when typed command adb devices its giving some number also but the image you provided is not flashing it.Dont know why please help
Click to expand...
Click to collapse
You're always talking about ADB commands, it's Fastboot that you have to use, it's described above how you get there.
What image do you mean when you say it's not flashing?
The guide is complete, read it carefully.
You have to download a zip file, in your case the Indian (RETIN) variant:
XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unpack it to fastboot folder, use the flashallO.bat to flash the firmware.
Please clarify what image you're talking about and if you do the fastboot flash like described above please provide the recovery.log , you can do that in TWRP->advanced->copy log, if TWRP is installed.
Try to flash the firmware and immediately after that grab a log and attach it here.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
You're always talking about ADB commands, it's Fastboot that you have to use, it's described above how you get there.
What image do you mean when you say it's not flashing?
The guide is complete, read it carefully.
You have to download a zip file, in your case the Indian (RETIN) variant:
XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unpack it to fastboot folder, use the flashallO.bat to flash the firmware.
Please clarify what image you're talking about and if you do the fastboot flash like described above please provide the recovery.log, you can do that in TWRP->advanced->copy log, it will be stored in your internal storage.
Try to flash the firmware and immediately after that grab the log (with TWRP file manager) and attach it here.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Anubhav074 said:
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Click to expand...
Click to collapse
You don't need logs. Your phone is locked so you cannot flash twrp. Only thing you can do is flash using fastboot commands. Just download the firmware.. extract. Put all of those files in the adb folder and run the flashall.bat or individual commands like fastboot flash recovery recovery.img which ever you feel is easier for you.
Anubhav074 said:
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Click to expand...
Click to collapse
debdeep98 said:
You don't need logs. Your phone is locked so you cannot flash twrp. Only thing you can do is flash using fastboot commands. Just download the firmware.. extract. Put all of those files in the adb folder and run the flashall.bat or individual commands like fastboot flash recovery recovery.img which ever you feel is easier for you.
Click to expand...
Click to collapse
That´s what I´ve said. If you would have TWRP you would be able to send a recovery.log but all you want to do is to flash a signed fastboot firmware. That´s possible without TWRP or unlocked bootloader, just by fastboot. Unzip the indian firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
into your Mini ADB & Fastboot folder, place the flashallO.bat there too and double-click it, everything in fastboot mode as described before.
What happens when you do that? Are the commands executed in the command window of your Windows PC?
Can you make a screenshot of it? The guide I posted has everything you need in it, you have to tell me what happens when you try to flash the unzipped firmware.
Just to be clear, the firmware and everything has to be on your PC, not your moble device!
i tried to take screen shot of it but was unable to do it but was successful in copying the complete commands log in text file so here it is
View attachment batch.txt
Anubhav074 said:
i tried to take screen shot of it but was unable to do it but was successful in copying the complete commands log in text file so here it is
Click to expand...
Click to collapse
Ok, that doesn't look to good.
The whole process is failing right at the start when the device is trying to build the partition table.
Have you tried different USB cables and ports?
Imo there are only two possible solutions:
Your device isn't working with fastboot correctly or its a hardware failure, the eMMC (the internal SD) may be corrupted. As your device is locked and hasn't been modded in any way this is the most plausible scenario also because it crashed out of the blue.
The only thing you can try yet is to use a different ADB and Fastboot tool, this one for example:
Minimal ADB & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=drivesdk
If all that changing of ports, cables and tools doesn't help you have to bring your device to a service center, they will most probably change the motherboard which isn't a cheap repair so if your device isn't under guarantee anymore you have to consider it it's worth the money.
Good luck!
Sent from my Moto G5 Plus using XDA Labs
So i tried with different fastboot software which you provided but i get the same errors .On phone when these commands run i get these messages failed to validate bootloader image and some thing called piv is also not able to be validated.
So i think its the end of my testing journey. Now can you please tell me how much chances are there for software issue. And is there any thing else i could.Any way i got to learn so many things through this but if is there anything left. Or should i go to service center
Anubhav074 said:
So i tried with different fastboot software which you provided but i get the same errors .On phone when these commands run i get these messages failed to validate bootloader image and some thing called piv is also not able to be validated.
So i think its the end of my testing journey. Now can you please tell me how much chances are there for software issue. And is there any thing else i could.Any way i got to learn so many things through this but if is there anything left. Or should i go to service center
Click to expand...
Click to collapse
I think you've done everything that's possible.
The device wasn't rooted,modded,unlocked or something.
It showed the failure out of the blue.
You tried different fastboot tools, cables, ports and the correct firmware.
I asked someone with more knowledge about your log and the whole case and he is thinking the same as I do.
So the chance for a software problem is really small. I told you everything I know, maybe a service center has more options for software checks but as far as I know they use the good old Lenovo Motorola Software Assistant.
So I would recommend to go there and ask (before they do anything) what you have to pay if your eMMC is broken. Here in Germany they always change the whole motherboard, the costs are about the half of the price you paid for the device here.
If your still under guarantee it's a different story.
I'm sorry, I told you everything I know and I flashed my Moto G5+ several times.
My opinion is that the device has a hardware failure and visiting the service center is the only thing you could do now.
I really would like to give you better news.
Sent from my Moto G5 Plus using XDA Labs
Hi, please help.
I have factory unlocked Moto G5 plus. I never did anyrhing to. All factory.
Recently its stuck in bootloop.
I really want to save all my pictures and texts.
Please help
Thanks
phone crazy said:
Hi, please help.
I have factory unlocked Moto G5 plus. I never did anyrhing to. All factory.
Recently its stuck in bootloop.
I really want to save all my pictures and texts.
Please help
Thanks
Click to expand...
Click to collapse
Read this thread. You can flash signed Motorola firmware like discribed. If you don't want to lose your data you can try to omit the "erase user data" command. Just delete it out of the flashallO.bat.
https://forum.xda-developers.com/g5...ked-stuck-fastboot-mode-t3996599/post80792213
Sent from my Moto G5 Plus using XDA Labs
Hello xdadev,
i need some hint/advice for where to look and further search after a problem with fastboot.
The Device is an OnePlus 6t running with OmniRom. The Device works fine, adb works.
So the Problem with the Device is it is somehow missing fastboot. I tried to reflash it. But i can not get into fastboot mode any longer. Not with triggering it through adb nor with the buttons pressed.
The Fastboot logo appears and is stuck there.
My questions so far as it seems something have broken the fastboot.
1. is fastboot on an extra partition could i repair it somehow with only adb at hands (and no root, thats why i try to reflash it as i need root again)
2. do you have any links where i can read up more on fastboot or where fastboot is stored on the memory chip of the device?
3. anything related to understand fastboot or further examine this problem
thanks in advance