So i just unlocked the device and Re-flashed it with mi flash tool, now the Phone is stuck at Fastboot mode.
i get this
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
finished. total time: 0.001s
Click to expand...
Click to collapse
is my bootloader unlocked?
also when i do set active a, this happens
C:\Users\user>fastboot -set active=a
< waiting for device >
I have tired every solutions i found online still no luck.
Connect the phone to pc and type in "fastboot devices" - do you see any device listed?
Also the correct command is:
fastboot --set-active=a
_mysiak_ said:
Connect the phone to pc and type in "fastboot devices" - do you see any device listed?
Also the correct command is:
fastboot --set-active=a
Click to expand...
Click to collapse
Yes i do but the command doesn't exist in fastboot please help
PS C:\tmp\platform-tools> fastboot --set active=a
C:\adb\fastboot.exe: unrecognised option `--set'
Click to expand...
Click to collapse
Also it says waiting for device it has been more then 30 minutes.
Now the Phone is rebooing at Andriod One Logo.
SpectreZ said:
Yes i do but the command doesn't exist in fastboot please help
Click to expand...
Click to collapse
Again, type it correctly.
In other words, spot the difference
fastboot --set-active=a (what I wrote)
fastboot --set active=a (what you wrote)
Do you see android/fastboot device in your device manager on the PC when you connect it to the PC in fastboot mode?
Edit: also replace fastboot.exe and adb.exe in c:\ADB\ folder as this one is being used. Or remove this folder from Windows PATHS.
_mysiak_ said:
Again, type it correctly.
In other words, spot the difference
fastboot --set-active=a (what I wrote)
fastboot --set active=a (what you wrote)
Do you see android/fastboot device in your device manager on the PC when you connect it to the PC in fastboot mode?
Edit: also replace fastboot.exe and adb.exe in c:\ADB\ folder as this one is being used. Or remove this folder from Windows PATHS.
Click to expand...
Click to collapse
I see Kedacom USB Device - Andorid Bootloader interface.
and i cannot remove the folder from C adb.
I have used mi Flash tool and while checking the log i saw boot was flashed at B so i erased the b boot useing fastboot also a
then I Reflash the B as 1st and A as 2nd the phone was able to make thru Recovery but when i restarted i went back into 0 again
SpectreZ said:
I see Kedacom USB Device - Andorid Bootloader interface.
and i cannot remove the folder from C adb.
I have used mi Flash tool and while checking the log i saw boot was flashed at B so i erased the b boot useing fastboot also a
then I Reflash the B as 1st and A as 2nd the phone was able to make thru Recovery but when i restarted i went back into 0 again
Click to expand...
Click to collapse
Are you sure that phone is in fastboot and not in recovery? What do you see on the phone screen?
You are doing too many things at once, focus on one thing and once you get it solved, move to another one. Also please provide answers to all questions, they are essential for troubleshooting.
1. Reinstall drivers and ADB - https://forum.xda-developers.com/showthread.php?t=2588979
2. Reboot phone in fastboot, connect it to the PC and type in "fastboot devices" - do you see any device connected?
Phone is now Started so what i did was.
* erased system_a
* erased system_b
also
* erased boot_a
* erased boot_b
I think the system is in B now.
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:35a1981490a2
(bootloader) product:laurel_sprout
(bootloader) max-download-size:804261888
(bootloader) kernel:uefi
all:
finished. total time: 0.438s
C:\Users\fahim>
Click to expand...
Click to collapse
and now the device started successfully still i think i messed up and i did everything you said.
Answer: i was on the Bunny screen Fastboot and yes " Fastboot devices " showed my device,
Can you kindly Guide me how do i factory set it? so i won't have any problem i Messed up because i didn't saw the note at StockRom in this forums where something is wrong in slots
C:\Users\fahim>fastboot --set-active-a
fastboot: unknown option -- set-active-a
Click to expand...
Click to collapse
SpectreZ said:
Phone is now Started so what i did was.
* erased system_a
* erased system_b
also
* erased boot_a
* erased boot_b
I think the system is in B now.
and now the device started successfully still i think i messed up and i did everything you said.
Answer: i was on the Bunny screen Fastboot and yes " Fastboot devices " showed my device,
Can you kindly Guide me how do i factory set it? so i won't have any problem i Messed up because i didn't saw the note at StockRom in this forums where something is wrong in slots
C:\Users\fahim>fastboot --set-active-a
fastboot: unknown option -- set-active-a
Click to expand...
Click to collapse
I guess you again did not follow given advice. You are still using old fastboot. In this case use "fastbot set_active a"
_mysiak_ said:
SpectreZ said:
Phone is now Started so what i did was.
* erased system_a
* erased system_b
also
* erased boot_a
* erased boot_b
I think the system is in B now.
and now the device started successfully still i think i messed up and i did everything you said.
Answer: i was on the Bunny screen Fastboot and yes " Fastboot devices " showed my device,
Can you kindly Guide me how do i factory set it? so i won't have any problem i Messed up because i didn't saw the note at StockRom in this forums where something is wrong in slots
C:\Users\fahim>fastboot --set-active-a
fastboot: unknown option -- set-active-aI guess you again did not follow given advice. You are still using old fastboot. In this case use "fastbot set_active a"
Click to expand...
Click to collapse
My Apologies, My Mind was rushing
Which one is the latest? can you tell me? please
Click to expand...
Click to collapse
Click to expand...
Click to collapse
1) update your ADB/Fastboot from the link I provided and use "fastboot --set-active=a"
or
2) keep what you have and use "fastboot set_active a"
_mysiak_ said:
1) update your ADB/Fastboot from the link I provided and use "fastboot --set-active=a"
or
2) keep what you have and use "fastboot set_active a"
Click to expand...
Click to collapse
Oh God thanks it worked, Can you tell me why there is A and B ? i mean 2 slots? also how do i get the device into factory fresh ?
Like the 1st time when i bought this. thank you soo much + Liked
If i use Mi Flash tool again, So am gonna be in Danger again too?
You can use MiFlash, but before flashing you need to make sure that your active partition is A (with commands mentioned before).
To restore to 100% stock:
1. set partition A as active
2. run MiFlash WITHOUT locking bootloader (or run script flash_all.bat)
3. start the phone, if everything works, move to the next step (ONLY IF PHONE WORKS)
4. run MiFlash with bootloader lock (or run script flash_all_lock.bat) or run "fastboot flashing lock"
5. after reboot, your phone should start as if it came from a factory
_mysiak_ said:
You can use MiFlash, but before flashing you need to make sure that your active partition is A (with commands mentioned before).
To restore to 100% stock:
1. set partition A as active
2. run MiFlash WITHOUT locking bootloader (or run script flash_all.bat)
3. start the phone, if everything works, move to the next step (ONLY IF PHONE WORKS)
4. run MiFlash with bootloader lock (or run script flash_all_lock.bat) or run "fastboot flashing lock"
5. after reboot, your phone should start as if it came from a factory
Click to expand...
Click to collapse
Thanks Everything is now great. However what is slot count? and what happens when it hits 0? also i locked the device via fastboot flashing lock.
It should be number of slots. 2 = boot_a + boot_b
It it hits 0, I guess you have serious problem as bootloader doesn't see any boot partition.
More info in the source code: https://android.googlesource.com/pl...otctrl/+/refs/heads/nougat-dev/boot_control.c
Related
This phone has never been even mentioned on xda so there is nothing to search for.
Anyways i have gone thru some threads of similar phones and tried some one click root methods. They didnt work.
So i thought i should unlock the bootloader.
Just for the sake of it i tried to boot into recovery and was successful.
Then i started following those htcdev.com instruction which required me to go into the bootloader mode.
But whenever i try doing that it either:
-Remains stuck at htc logo screen (the 1st one and not the bootanimation)
-Boots normally
then i saw that i had to press this button release this after so many seconds and......
so just to be sure that im not making those silly mistakes i tried to go into bootloader thru adb which always remains stuck at the htc splash screen (htc - powered by android).
then i tried to go to recovery but now even that isnt possible.
so in short: i cant get into the bootloader so i cant unlock or root. I cant get into the recovery either. The phone otherwise is working pretty normal. But on trying to get into any modes i remain stuck at the 1st htc screen (and not the bootanimation) and then i have to remove the battery to get it booting normally.
It is HTC Desire 516 Dual sim and is on JB 4.3 (if u needed this)
and finally i got this log from a unlock tool if it makes it easier for you
adb: reboot-bootloader
adb out:
Reboot success!
fastboot: devices
fastboot out: 0123456789ABCDEF fastboot
fastboot: oem lock
fastboot timeout
lock_failed
adb: reboot-bootloader
adb out:
Reboot success!
fastboot: devices
fastboot out: 0123456789ABCDEF fastboot
fastboot: getvar version
fastboot out: version: 0.5
finished. total time: 0.003s
fastboot: getvar version-bootloader
fastboot out: version-bootloader:
finished. total time: 0.003s
fastboot: getvar version-main
fastboot out: version-main:
finished. total time: 0.003s
fastboot: getvar serialno
fastboot out: serialno: 0123456789ABCDEF
finished. total time: 0.003s
fastboot: getvar product
fastboot out: product: MSM8610
finished. total time: 0.003s
fastboot: getvar modelid
fastboot out: modelid:
finished. total time: 0.003s
fastboot: getvar cidnum
fastboot out: cidnum:
finished. total time: 0.003s
fastboot: getvar build-mode
fastboot out: build-mode:
finished. total time: 0.003s
fastboot: getvar boot-mode
fastboot out: boot-mode:
finished. total time: 0.003s
fastboot: getvar security
fastboot out: security:
finished. total time: 0.003s
fastboot: getvar imei
fastboot out: imei:
finished. total time: 0.003s
fastboot: oem get_identifier_token
fastboot timeout
get_device_info_failed
Click to expand...
Click to collapse
pls do help if u can :highfive: :fingers-crossed:
noone? @psych.half suggest anything?
T3snake said:
noone? @psych.half suggest anything?
Click to expand...
Click to collapse
Remove your battery before trying to boot into fastboot.
If you can't remove your battery, go to Settings->Power options And disable fast boot
dummie999 said:
Remove your battery before trying to boot into fastboot.
If you can't remove your battery, go to Settings->Power options And disable fast boot
Click to expand...
Click to collapse
yea tried that..
same result
btw volume up brings up recovery and down brings bootloaderr
is fastboot a different mode or u call bootloader mode and fastboot the same..?
T3snake said:
yea tried that..
same result
btw volume up brings up recovery and down brings bootloaderr
is fastboot a different mode or u call bootloader mode and fastboot the same..?
Click to expand...
Click to collapse
Yes fastboot and bootloader are the same
Have you tried booting into bootloader with "adb reboot bootloader"
Info
You are not alone !
Now can have all the stock files here .
dummie999 said:
Yes fastboot and bootloader are the same
Have you tried booting into bootloader with "adb reboot bootloader"
Click to expand...
Click to collapse
yea both recovery and bootloader isnt accessible by adb
joldisadrian said:
You are not alone !
Now can have all the stock files here .
Click to expand...
Click to collapse
but there are only kernel sources
T3snake said:
yea both recovery and bootloader isnt accessible by adb
Click to expand...
Click to collapse
How do you mean isn't accesible? What do you see when you type those commands? What is the output?
I have this device, and i booted it in fastboot mode successfully. Open ADB and type "adb reboot-bootloader", the phone will reboot and remain stuck in the boot logo (the first). Now open fastboot and type "fastboot devices" and it will be recognized. I can't unlock bootloader, because when i type "fastboot oem get_identifier_token" it remains stuck, and it's so annoying because i want to root this device, can you help me? :crying:
I'm having the same problem. The bootloader is not accessible. I tried all possible root methods but none work. Kinda regretting now buying this phone
dummie999 said:
How do you mean isn't accesible? What do you see when you type those commands? What is the output?
Click to expand...
Click to collapse
As I said it reboots but remains stuck at HTC logo until removal of battery
Sent from my SM-T211 using Tapatalk
AceXer said:
I have this device, and i booted it in fastboot mode successfully. Open ADB and type "adb reboot-bootloader", the phone will reboot and remain stuck in the boot logo (the first). Now open fastboot and type "fastboot devices" and it will be recognized. I can't unlock bootloader, because when i type "fastboot oem get_identifier_token" it remains stuck, and it's so annoying because i want to root this device, can you help me? :crying:
Click to expand...
Click to collapse
So since its stuck and we can't do anything
BTW we had an 110 mb update just a few days ago but since my phone can't get into recovery the final steps don't take place where it goes to recovery and finishes up(in my case it remains stuck at HTC logo so device remains as it was when I boot it normally)
Sent from my SM-T211 using Tapatalk
rakeshz said:
I'm having the same problem. The bootloader is not accessible. I tried all possible root methods but none work. Kinda regretting now buying this phone
Click to expand...
Click to collapse
Well if they gave us an app2sd feature I ccud forgive em a bit.
I contacted the customer service and when I mentioned a stuck up screen they immediately asked if I WS rooting. So maybe htc did it intentionally or maybe some1 fishy intervened or something
Sent from my SM-T211 using Tapatalk
T3snake said:
Well if they gave us an app2sd feature I ccud forgive em a bit.
I contacted the customer service and when I mentioned a stuck up screen they immediately asked if I WS rooting. So maybe htc did it intentionally or maybe some1 fishy intervened or something
Sent from my SM-T211 using Tapatalk
Click to expand...
Click to collapse
Yes, seriously we need the move to sd card feature. The whole reason of having a feature phone without being able to install any apps or big games sucks
rakeshz said:
Yes, seriously we need the move to sd card feature. The whole reason of having a feature phone without being able to install any apps or big games sucks
Click to expand...
Click to collapse
I calculated and found that u can get Max 1.7 GB free (as indicated by the mobile) but if u use mtp or reach 1.5 GB u will not be able to put anything more since there shud always be 200mb free
So we get only 1.5 GB after disabling all the preinstalled apps
Sent from my SM-T211 using Tapatalk
So I'm able to boot into fastboot mode, I'm able to boot into recovery mode. But how can we unlock the bootloader?
AceXer said:
So I'm able to boot into fastboot mode, I'm able to boot into recovery mode. But how can we unlock the bootloader?
Click to expand...
Click to collapse
Go to htcdev.com
If u can get into fastboot mode u can run some commands to get a token paste the token at the place indicated and follow the steps
Sent from my GT-S5282 using Tapatalk
T3snake said:
Go to htcdev.com
If u can get into fastboot mode u can run some commands to get a token paste the token at the place indicated and follow the steps
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
Yes, but this device isn't in the list, and when I type (in fastboot mode) "fastboot oem get_identifier_token" it stuck and three dots appear.
All command work, but if i type "oem" after "fastboot" (ex. "fastboot oem command list) it stuck with three dots. Help meeeee pleease!
AceXer said:
Yes, but this device isn't in the list, and when I type (in fastboot mode) "fastboot oem get_identifier_token" it stuck and three dots appear.
All command work, but if i type "oem" after "fastboot" (ex. "fastboot oem command list) it stuck with three dots. Help meeeee pleease!
Click to expand...
Click to collapse
Hi,
I have same device and same problems. I think I tried all solutions I've seen so far. I had HTC wildfire, Motorola XT530, Huawei Ascend G300, HTC Desire X, and I have some expirience rooting, but this phone makes me sick. Just sent an rage mail to HTC, saying that they made great little piece of hardware with software making it almost unusable. So far I tried SuperOneClick, RootGenius and adb root, but nothing works.
I am trying to fix my soft-bricked phone that's stuck in a bootloop. Phone was rooted and working fine until I flashed an incompatible TWRP recovery through Flashify and rebooted. I've Googled for weeks and put up a few other related posts here asking for help but haven't gotten much traction. I do have a backup of the stock recovery in .IMG format, as well as a complete Nandroid system image, also in .IMG format.
With those, I figure I should be able to re-flash it and be done, but that would be too simple. ADB debugging was enabled on the phone before it broke, but ADB commands are out since it doesn't make it far enough in the bootloop to connect to my PC. Fastboot works. If I remove the battery from the phone and plug in the USB it boots directly into fastboot. Device manager lists it under Android phone: Android ADB interface, and some fastboot commands work. fastboot devices returns my phones info, and fastboot reboot bootloader will reboot the phone back into fastboot. Anything else however, is a no-go. I've tried fastboot erase recovery, fastboot boot recovery.img, fastboot flash recovery recovery.img, etc.
All either hang (i've waited up to an hour) or give me the error "command write failed (no error)". I've tried Googling the error and haven't found a concrete answer on what it means or how to fix it.
So far I have tried:
Running fastboot from a command window with admin privileges.
Five different USB cables.
Used every USB port on my PC (at least two, if not all of them are USB 2.0. I know fastboot doesn't like 1.0 or 3.0 ports.)
Using the latest version of fastboot.
Tried a slew of different drivers for the phone (at least seven).
Tried using three different OS's (Win 8, Win 8.1, and Ubuntu).
Tried a few different fastboot GUIs just to make sure I was getting the commands right.
All to no avail. The only thing I haven't tried is another PC and that's only because I din't have one. So, bottom line, the only two ways to unbrick the phone without some special piece of hardware are ADB commands or something that relies on ADB connectivity like SP phone tool or QFIL, or by fastboot comands. ADBs out and fastboot won't play nice. At this point i'm tempted to have a round of phone V. blender. Seriously though, i'm out of ideas. If anyone sees anything I haven't thought of please let me know.
Jesseb342 said:
I am trying to fix my soft-bricked phone that's stuck in a bootloop. Phone was rooted and working fine until I flashed an incompatible TWRP recovery through Flashify and rebooted. I've Googled for weeks and put up a few other related posts here asking for help but haven't gotten much traction. I do have a backup of the stock recovery in .IMG format, as well as a complete Nandroid system image, also in .IMG format.
With those, I figure I should be able to re-flash it and be done, but that would be too simple. ADB debugging was enabled on the phone before it broke, but ADB commands are out since it doesn't make it far enough in the bootloop to connect to my PC. Fastboot works. If I remove the battery from the phone and plug in the USB it boots directly into fastboot. Device manager lists it under Android phone: Android ADB interface, and some fastboot commands work. fastboot devices returns my phones info, and fastboot reboot bootloader will reboot the phone back into fastboot. Anything else however, is a no-go. I've tried fastboot erase recovery, fastboot boot recovery.img, fastboot flash recovery recovery.img, etc.
All either hang (i've waited up to an hour) or give me the error "command write failed (no error)". I've tried Googling the error and haven't found a concrete answer on what it means or how to fix it.
So far I have tried:
Running fastboot from a command window with admin privileges.
Five different USB cables.
Used every USB port on my PC (at least two, if not all of them are USB 2.0. I know fastboot doesn't like 1.0 or 3.0 ports.)
Using the latest version of fastboot.
Tried a slew of different drivers for the phone (at least seven).
Tried using three different OS's (Win 8, Win 8.1, and Ubuntu).
Tried a few different fastboot GUIs just to make sure I was getting the commands right.
All to no avail. The only thing I haven't tried is another PC and that's only because I din't have one. So, bottom line, the only two ways to unbrick the phone without some special piece of hardware are ADB commands or something that relies on ADB connectivity like SP phone tool or QFIL, or by fastboot comands. ADBs out and fastboot won't play nice. At this point i'm tempted to have a round of phone V. blender. Seriously though, i'm out of ideas. If anyone sees anything I haven't thought of please let me know.
Click to expand...
Click to collapse
Your computer must not be properly communicating with your device, Have you tried ANY other fastboot commands other then what you mentioned?
Can you provide a screenshot of your fastboot commands failing? Perhaps something else is going on other then what you've provided. You never know.
As mentioned in the post #2, uninstall any drivers you have and install the latest fastboot and adb drivers v1.4.2
(here) and the drivers given by your OEM, followed by a reboot and then type these:
Code:
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot erase customize
Flash the stock boot.img
Code:
fastboot flash boot filename.img
Then boot into your recovery:
Code:
fastboot boot filename.img
Then perform a factory reset from the recovery itself.
Sent from Lord Tywin's athene (xt1643)
tywinlannister said:
As mentioned in the post #2, uninstall any drivers you have and install the latest fastboot and adb drivers v1.4.2
(here) and the drivers given by your OEM, followed by a reboot and then type these:
Code:
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot erase customize
Flash the stock boot.img
Code:
fastboot flash boot filename.img
Then boot into your recovery:
Code:
fastboot boot filename.img
Then perform a factory reset from the recovery itself.
Sent from Lord Tywin's athene (xt1643)
Click to expand...
Click to collapse
Thanks for the reply. I picked up a new cable today just to be absolutely sure that wasn't the cause of my problems. I've tried several already, but most of those were dollar store cables and iffy at best. No luck though, even with a brand new semi-good quality cable (Duracell) it still doesn't work.
I followed all the above steps. First I made sure the correct OEM drivers were installed. Device manager shows "Android phone: Coolpad Android ADB Interface" when I plug the phone in. I'm not 100% sure that this is the correct driver for my phone, though it is a Coolpad, and I know there is some universality between drivers. I've used both ADB and fastboot commands on my Kindle fire many times with only the generic Google ADB / fastboot driver and never had a problem. Also, the Coolpad driver I found was on a Chinese file sharing website (Baidu) listed under the Coolpad section and was just titled phone driver.rar so i'm guessing it's universal for Coolpads. That, and the fact that the phone does respond to some commands makes me think that the driver isn't the issue either. Next, I followed the posted link and downloaded the latest ADB and fastboot files and installed them. I then moved my recovery.img and my 801es.img (nandroid backup) to the ADB / fastboot folder and opened an admin command window. Here are the results:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
1edf2f7a fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\Program Files (x86)\Minimal ADB and Fastboot>
These would seem to indicate that fastboot is working properly, but upon trying your suggestions I don't get past the second command.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
Then nothing. I've waited 10 minutes and no change. I get similar results trying to erase recovery, boot the recovery.img, and flash the recovery.img.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (10240 KB)...
All these net a similar response. Waiting 10 to 15 minutes after each command and still no activity.
I'm stumped.
Just a minor update. I got a second-hand Kindle fire for my son. I thought it was one of the 50 dollar ones they're selling now since it was in plastic behind glass in a locked case and all it said was Kindle fire 7 inch. Dated 1-3-17. For 20 bucks I thought what the heck. Well, upon getting it home and tinkering with it, I quickly discovered it was a Kindle fire 2nd gen from 2012. Still not bad for 20 bucks as the thing was pristine, but I hated the UI. After a little bit of digging, I discovered that you could easily install TWRP, Gapps, and Cyanogenmod 11 on it. All info I found here (surprise surprise, I love this site.) Now that's done and my son loves his tablet. It's just like a proper Android tab.
Anyway, anyone who's tinkered with older Kindle devices knows about fastboot cables (and yes, I did need one, dang bootloops!). I thought I would try the fastboot cable on the stubborn Coolpad. Still no go. So at this point, either the images I have are invalid and I can't get new ones (weeks of Google searches have turned up zip as far as a stock rom for this phone), or the phone is locking me out due to some non-standard security feature. I'm thinking the second. I can understand if the images I have are bad, but that shouldn't affect things like querying the lock status of the bootloader, or trying to erase the boot partition and not getting a response.
I'm out of ideas. If anyone knows anything about this, specifically if this is unique to Coolpads, please let me know. Otherwise, the phone is going to end up in a drawer, probably forever. Thanks.
Jesseb342 said:
I am trying to fix my soft-bricked phone that's stuck in a bootloop. Phone was rooted and working fine until I flashed an incompatible TWRP recovery through Flashify and rebooted. I've Googled for weeks and put up a few other related posts here asking for help but haven't gotten much traction. I do have a backup of the stock recovery in .IMG format, as well as a complete Nandroid system image, also in .IMG format.
With those, I figure I should be able to re-flash it and be done, but that would be too simple. ADB debugging was enabled on the phone before it broke, but ADB commands are out since it doesn't make it far enough in the bootloop to connect to my PC. Fastboot works. If I remove the battery from the phone and plug in the USB it boots directly into fastboot. Device manager lists it under Android phone: Android ADB interface, and some fastboot commands work. fastboot devices returns my phones info, and fastboot reboot bootloader will reboot the phone back into fastboot. Anything else however, is a no-go. I've tried fastboot erase recovery, fastboot boot recovery.img, fastboot flash recovery recovery.img, etc.
All either hang (i've waited up to an hour) or give me the error "command write failed (no error)". I've tried Googling the error and haven't found a concrete answer on what it means or how to fix it.
So far I have tried:
Running fastboot from a command window with admin privileges.
Five different USB cables.
Used every USB port on my PC (at least two, if not all of them are USB 2.0. I know fastboot doesn't like 1.0 or 3.0 ports.)
Using the latest version of fastboot.
Tried a slew of different drivers for the phone (at least seven).
Tried using three different OS's (Win 8, Win 8.1, and Ubuntu).
Tried a few different fastboot GUIs just to make sure I was getting the commands right.
All to no avail. The only thing I haven't tried is another PC and that's only because I din't have one. So, bottom line, the only two ways to unbrick the phone without some special piece of hardware are ADB commands or something that relies on ADB connectivity like SP phone tool or QFIL, or by fastboot comands. ADBs out and fastboot won't play nice. At this point i'm tempted to have a round of phone V. blender. Seriously though, i'm out of ideas. If anyone sees anything I haven't thought of please let me know.
Click to expand...
Click to collapse
First off, the information contained in your post doesn't really gives anybody a clue on how to help you. Phone model, previously working android version, rooted or stock etc. That would be a good place to start
Iamst.ralph said:
First off, the information contained in your post doesn't really gives anybody a clue on how to help you. Phone model, previously working android version, rooted or stock etc. That would be a good place to start
Click to expand...
Click to collapse
The phone is a Yulong Coolpad model 801 ES. I was running stock 4.1.2 JB ROM rooted with Kingroot. Developer options were unlocked and allow ADB debugging was checked. ADB and Fastboot drivers were installed and working properly as I was able to make a backup of my recovery partition and a "Nandroid" image. Note, the Nandroid image wasn't made using a custom recovery, it was made using DFS Evolution phone tools. It said Nandroid backup, and it did generate a file named 801es.img that's roughly 248 mb. I can't tell what partition it is since it has a non-standard header. Every image kitchen I've tried to use tells me bootmagic is missing when it tries to unpack.
The phone was working fine until I flashed an incompatible TWRP recovery. Now I'm stuck in a bootloop. I can get into fastboot mode, but every command I send other than fastboot devices and fastboot reboot ( like fastboot boot recovery.img, fastboot flash recovery recovery.img, fastboot erase recovery, fastboot flashing unlock, ...) just hang. I've waited for over an hour on some and they still didn't complete. I've tried every USB port on my PC, 6 different cables, three different OS's (Win 8, WIn 8.1, and Ubuntu), and a second PC (my laptop) to try and eliminate all possible problems. All that and still no luck. This phone just will not respond to fastboot commands like it should and I have no idea why.
Hopefully that answers all your questions. Maybe you have some ideas.
Your phone is obviously a MTK phone hence fastboot commands get stuck. Search for the firmware of your phone on Google and download it, download Sp flashtool. When you're done downloading, post here
I have similar issues with a Coolpad Defiant 3632A. All commands except for [fastboot devices] and [fastboot getvar] everything else returns - "FAILED (remote: unknown command)".
My fastboot has a Secure Phone text in white at the bottom left of the screen when im in the bootloader. Not long back this was not the case and i'm not sure what is causing it.
GETVAR Results
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version:0.5_emmccid_secureboot
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4082000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1ff00000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x10dffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x80000000
(bootloader) serialno:1f59cc3d
(bootloader) kernel:lk
(bootloader) product:QC_REFERENCE_PHONE
all:
finished. total time: 0.100s
stuff you need to download to root your vivo v9/v9+
SuperSu
ADB Drivers
TWRP Recovery
1. First of all, keep it in mind that the rooting process requires the installed custom TWP Recovery on your device.
2. When it comes to enabling USB debugging, you need to visit Settings -> About Phone -> Tap on Build number till to see the message on display screen like “You are now a developer.”
3. You can now have the developer option, so visit Settings -> Developer options -> Enable USB debugging and make sure to enable OEM to unlock.
4. It is necessary to download TWRP recovery image for a device
5. Now, the user can connect the device to PC using the USB cable. Make sure to check that the PC has all Vivo V9 USB driver gets installed. You can now create a folder and name it as Fastboot and copy to the TWRP Recovery img in Fastboot folder.
6. You can now press the Right keys click + left shift to open the command prompt window and choose the Open command window here.
7. By following the given below command, you can now boot the device Vivo V9 into the fastboot mode.
fastboot reboot bootloader
Mac: ./fastboot devices
Windows: fastboot devices
8. The user can now check the connected device list by entering the command below.
fastboot devices
Mac: ./fastboot devices
Windows: fastboot devices
9. To flash TWRP recovery follows the command below
Fastboot Flash TWRP recovery.img.
Mac: ./fastboot devices
Windows: fastboot devices
10. Finally, thus the TWRP recovery is successfully installed on your device.
11. To reboot your device make sure to follow the command Fastboot Reboot
For more information go to https://techcyder.com/
How To Root Vivo V9 from TWRP [STEPS]
1. It is necessary for the users to download rooting package in Vivo V9
2. You can now place the root zip on the SD card
3. Make sure your device to boot it into TWRP recovery mode
4. Hold the keys Power + Volume down to boot in custom recovery mode
5. Once if you entered TWRP recovery mode, you could release the keys
6. Get set to click on Backup and complete the backup process of a current OS. It will help during the flashing process in case if anything goes wrong.
7. The user can click on the option “Install” and get SuperSU zip file.
8. You need to swipe the button to confirm the process of installation.
9. Finally, the rooting process is done successfully, and you can tap reboot system.
9. Thus the rooting is done on your device with the help of SuperSU.
Conclusion: Root Vivo V9 and Install TWRP Recovery
So, the Vivo V9 users who all are looking forward to customizing their device for many exciting features to experience can check out the above process. It is necessary for the users to follow all the steps without skipping it.
To know how to root Vivo V9, check Androidtek.com. You will find Root Vivo V9 and install TWRP recovery article there.
What? People use sites other than XDA?
Is it work on Vivo V9 with Snapdragon 450? Because here in Indonesia, Vivo use Snapdragon 450
ferlie said:
Is it work on Vivo V9 with Snapdragon 450? Because here in Indonesia, Vivo use Snapdragon 450
Click to expand...
Click to collapse
Yes this method will work for your device
how?
hi, how can I root vivo v9 without losing updates from o.t a? Im afraid i might lost updates
Kenfabz said:
hi, how can I root vivo v9 without losing updates from o.t a? Im afraid i might lost updates
Click to expand...
Click to collapse
U need to install red wolf twrp recovery so that you can still get ota updates
Thanks for sharing us......
no root, no twrp download, any ideas?
Hi!
kingoroot not worket for this phone
Download TWRP Recovery for Vivo V9 (Link added soon) in url http://androidtek.com/how-to-root-vivo-v9-and-install-twrp-recovery/
How download twrp for this phone?
OEM_Unlock enable , developer mode enable , USB debugging enable.
adb reboot bootloader ENTER
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3828000
(bootloader) variant:MTP eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
fastboot flashing unlock ENTER
FAILED (remote: unknown command or device is lock)
finished. total time: 0.009s
download this adb
https://forum.xda-developers.com/general/rooting-roms/how-to-unlock-bootloader-vivo-phones-t3686690
fastboot bbk vivo_bsp unlock_vivo
FAILED (remote: unknown command or device is lock)
finished. total time: 0.012s
princebhat115 said:
U need to install red wolf twrp recovery so that you can still get ota updates
Click to expand...
Click to collapse
Do you have link to red wolf twrp version for vivo v9?
zeroonea said:
Do you have link to red wolf twrp version for vivo v9?
Click to expand...
Click to collapse
I believe it doesn't even exists. Vivo V9 have already dead development. Like LG G6.
latest kingroot not work for me
It stuck at 1%
method2 not success.
problem with command Fastboot flash recovery.img
It's say (remote: unknown command or device is lock)
i have adb driver installed. OEM_Unlock enable , developer mode enable , USB debugging enable.
phooza said:
latest kingroot not work for me
It stuck at 1%
method2 not success.
problem with command Fastboot flash recovery.img
It's say (remote: unknown command or device is lock)
i have adb driver installed. OEM_Unlock enable , developer mode enable , USB debugging enable.
Click to expand...
Click to collapse
The correct command is "fastboot flash recovery recovery.img"
Will this work with the Y71?
Hi there,
I am very new to this topic and have never worked with Adroid before, so please bare with me
Will this process work for the new Vivo Y71? (released in China 1 month ago)
I bought it in Shenzhen a few weeks back and went into a shop in Honk-Kong to have them install Google Play Store. Now, I don't know whether they already rooted the device to install Google Play. How can I see if the device is already rooted?
I have the problem, that some of the system prompts (like, error messages) are still in Chinese. The rest of the OS is in English. I would like to eventually install a ROM with support for German or at least full English support.
I know, lots of questions. Sorry if they're stupid!
best
But there is no custom recovery for Vivo V9 yet. Correct me if I am wrong.
edeoldi said:
Hi there,
I am very new to this topic and have never worked with Adroid before, so please bare with me
Will this process work for the new Vivo Y71? (released in China 1 month ago)
I bought it in Shenzhen a few weeks back and went into a shop in Honk-Kong to have them install Google Play Store. Now, I don't know whether they already rooted the device to install Google Play. How can I see if the device is already rooted?
I have the problem, that some of the system prompts (like, error messages) are still in Chinese. The rest of the OS is in English. I would like to eventually install a ROM with support for German or at least full English support.
I know, lots of questions. Sorry if they're stupid!
best
Click to expand...
Click to collapse
Kingroot is not working with my fone
invincible authority said:
The correct command is "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
thank you but I use correct command
fastboot flash recovery recovery.img
not work. It's still "unknown command or devices is lock"
may be i think stock rom v9 is lock for install twrp fastboot mode
akalifa said:
Hi!
kingoroot not worket for this phone
Download TWRP Recovery for Vivo V9 (Link added soon) in url http://androidtek.com/how-to-root-vivo-v9-and-install-twrp-recovery/
How download twrp for this phone?
OEM_Unlock enable , developer mode enable , USB debugging enable.
adb reboot bootloader ENTER
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3828000
(bootloader) variant:MTP eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
fastboot flashing unlock ENTER
FAILED (remote: unknown command or device is lock)
finished. total time: 0.009s
download this adb
https://forum.xda-developers.com/general/rooting-roms/how-to-unlock-bootloader-vivo-phones-t3686690
fastboot bbk vivo_bsp unlock_vivo
FAILED (remote: unknown command or device is lock)
finished. total time: 0.012s
Click to expand...
Click to collapse
U need to unlock ur device first
U need to unlock your device first
princebhat115 said:
U need to unlock your device first
Click to expand...
Click to collapse
How?
a bit similer with this case
my friend bought it 20 days ago and he unlock it
but he cant flash twrp as like guides
he had no expirience before this
so i get tablet and tried to solve the problem but
fastboot doesnt work properly
fastboot devices/reboot/device-info works
but
fastboot flash recovery twrp.img/ flash boot boot.img(guide on carbon rom)/boot twrp.img/and etc that for flashing or change any system
does not work
massage like failed(long link/bigger than max allowed)
changing everytime i try
i though there might some issues when my friend unlock the bootloader
so i 'fastboot oem lock' and try to unlock again
but from then fastboot not work properly
can be boot or 'adb reboot fastboot' to fastboot
but it become unknown device on windows device manager
fastboot command not work
when mi flash try to detect device, fastboot mode end and 'press any key to power off' screen came out
some times it working for few seconds so i try unlock with official xiaomi tool but tool said 'already unlocked'
right after i locked bootloader i used 'fastboot oem device-info' and checked bootloader is locked
i can switch oem unlock on/off in developer option but it doesnt change anything
i searched as i can and edl mode looks last
but few things to consider
1. its official chinese rom and working now
2. i dont know broken fastboot can be restored with flashing rom with edl (i flash rom with update app in settings but not solved)
3. adb reboot edl doesnt work it just rebooted(should teardown it but i dont know what pin to short)
the reason why i trying to install custom rom(or eu rom) is my friend and i not live in native english country
hope i get some help
thx
Ryzen CPU?
thE_29 said:
Ryzen CPU?
Click to expand...
Click to collapse
ryzen 1, 2, intel sandy etc
tried all i got
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
KrakmanCz said:
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
Click to expand...
Click to collapse
nope
cant go into edl mode until i teardown it
miflash 2018 doesnt connect with pad on fastboot mode
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
chocodesk said:
ryzen 1, 2, intel sandy etc
tried all i got
Click to expand...
Click to collapse
Ok, when you also tried Intel.. But Ryzen CPUs have major problems with the flash tool and the tablet. Would not do anything on Ryzen PCs.
KrakmanCz said:
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
Click to expand...
Click to collapse
on basic
with was detected as fastboot before
but know its unknown on device manager
update driver doesnt work
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Dannyboy3210 said:
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Click to expand...
Click to collapse
i tried 2.0 and 3.0
not work
tablet owner decide to use it on stock chinese rom
not in my hand now
$ adb reboot bootloader
List devices on fastboot :
$ fastboot devices
XXXXXX fastboot
Check if bootloader is unlocked :
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.003s
Flash TWRP recovery :
$ fastboot flash recovery recovery.img
Sending 'recovery' (54400 KB) OKAY [ 1.540s]
Writing 'recovery' OKAY [ 0.410s]
Finished. Total time: 1.952s
Reboot your device
$ fastboot reboot
Rebooting
Finished. Total time: 0.000s
I installed TWRP on MIUI 10 using this description. On the end , after TWRP installed - I rebooted again to TWRP and installed stock rom at once . I not tested , but theory says , MIUI will reflash recovery if it will be booted in this situation .
Sorry to piggy-back off this post, but I'm having a similar issue with my Mi Pad I just received:
I can boot it into Fastboot mode no problem, even see it listed when I use the "Fastboot devices" command. When I run the OEM info everything comes back true for unlocked.
However, when I try to flash anything I get the max size error or just a "FAILED" and it kicks the Mi Pad to a black screen with the white text "Press any key to shut down".
Any ideas?
*edit*
I've continued testing, and I'm really at a loss here. See the response I'm getting using fastboot:
\minimal_adb_fastboot_1.4.3_portable>fastboot flash boot kernel.img
target didn't report max-download-size
sending 'boot' (15060 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I can transfer files in windows no problem... I can use adb commands no problem... fastboot just doesnt seem to work.
I figured out my issue. You cannot use USB 3 ports to connect and run fastboot commands. I bought a cheap USB 2 hub, ran the cable from that and had no problems at all.
Hello.
I requested help on wrong forum, first person that responded redirected me here.
Here's the copy-pasted contents of that post.
I have a Motorola. I typically leave my cellphone attached to my computer with USB so it can charge, slowly but surely.
When I wanted to get on my way I noticed my phone wouldn't start which I found interesting.
I left it on a charger for some time and when I held the power button to power up, I noticed it got stuck at boot.
What it typically does is open boot screen with Motorola logo, vibrate, start an animation and after mid-boot say "halo Moto" and then leave me at home screen.
But this time, it just get stuck on a boot screen. It shows the boot screen with Motorola logo, vibrates and then does nothing (until battery dies, I left it for an hour?)
I pressed the volume down and power button to enable debugging.
I get a "FastBoot AP Flash Mode" menu.
The options are:
Start (which puts me back into stuck boot)
Restart Bootloader (which restarts the FastBoot)
Recovery Mode (which gives me this: "No Command" with an Android icon, does nothing more]
Power Off (which powers off the phone)
Bootloader Logs (which changes some text to: "Fastboot Reason: Reboot mode set to FastBoot" or "Volume button down")
Switch Tools Mode (which toggles text between Tools Mode Config: DISABLED and ENABLED, no idea of other effects)
BARCODES (which probably shows scannable code so that professionals needn't type the ID)
I wanted to send it back to the seller, but they claim that they take no responsibility for loss of information, all my data is stuck on 128GB on the internal memory.
I would like to go to service for data recovery, but I due to COVID-19 everything's closed.
What could I potentially do to restore my phone? And if I can't, I can send it back, but how do I backup my data?
It's Motorola One Zoom.
Click to expand...
Click to collapse
I suggest we try the following solution to your problem.
First, check which boot slot the phone is in. It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot.
Command to verify:
Code:
fastboot getvar current-slot
Make active Slot A:
Code:
fastboot --set-active=a
Then reboot the bootloader:
Code:
fastboot reboot bootloader
Perform user data wiping:
Code:
fastboot -w
And install the latest firmware for your model via fastboot.
ilia3367 said:
I suggest we try the following solution to your problem.
First, check which boot slot the phone is in. It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot.
Command to verify:
Code:
fastboot getvar current-slot
Make active Slot A:
Code:
fastboot --set-active=a
Then reboot the bootloader:
Code:
fastboot reboot bootloader
Perform user data wiping:
Code:
fastboot -w
And install the latest firmware for your model via fastboot.
Click to expand...
Click to collapse
I tried getting fastboot installed, but it got stuck at "waiting for any device" on the first command. After some painful entire hour of investigation I found out that I need USB debugging enabled, which I haven't done when the smartphone was working.
" It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot."
I didn't update anything, nothing's changed about hardware and it had no access to Internet, so it couldn't update itself. Neither I nor any of my apps had the means to flash the phone.
yeetusAAA said:
I tried getting fastboot installed, but it got stuck at "waiting for any device" on the first command. After some painful entire hour of investigation I found out that I need USB debugging enabled, which I haven't done when the smartphone was working.
" It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot."
I didn't update anything, nothing's changed about hardware and it had no access to Internet, so it couldn't update itself. Neither I nor any of my apps had the means to flash the phone.
Click to expand...
Click to collapse
USB debugging has nothing to do with fastboot.
If it's in fastboot mode, and fastboot commands are not working could be a driver issue.
How is is it listed in Device Manager?
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
USB debugging has nothing to do with fastboot.
If it's in fastboot mode, and fastboot commands are not working could be a driver issue.
How is is it listed in Device Manager?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
The situation changed slightly since I came back from work.
Previously device appeared as unknown device.
With name "fastboot parker S", I have it in search history.
After rebooting (and installing 50 drivers) my device appears as "Motorola ADB Interface", however execution of commands don't end successfully.
Code:
X:\Applications\MinimalADBFB>fastboot -help
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw <bootable-partition> <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader|emergency] Reboot device [into bootloader or emergency mode].
reboot-bootloader Reboot device into bootloader.
oem <parameter1> ... <parameterN> Executes oem specific command.
stage <infile> Sends contents of <infile> to stage for
the next command. Supported only on
Android Things devices.
get_staged <outfile> Receives data to <outfile> staged by the
last command. Supported only on Android
Things devices.
help Show this help message.
options:
-w Erase userdata and cache (and format
if supported by partition type).
-u Do not erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide either
a serial number or path to device port.
For ethernet, provide an address in the
form <protocol>:<hostname>[:port] where
<protocol> is either tcp or udp.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <slot> Specify slot name to be used if the
device supports slots. All operations
on partitions that support slots will
be done on the slot specified.
'all' can be given to refer to all slots.
'other' can be given to refer to a
non-current slot. If this flag is not
used, slotted partitions will default
to the current active slot.
-a, --set-active[=<slot>] Sets the active slot. If no slot is
provided, this will default to the value
given by --slot. If slots are not
supported, this does nothing. This will
run after all non-reboot commands.
--skip-secondary Will not flash secondary slots when
performing a flashall or update. This
will preserve data on other slots.
--skip-reboot Will not reboot the device when
performing commands that normally
trigger a reboot.
--disable-verity Set the disable-verity flag in the
the vbmeta image being flashed.
--disable-verification Set the disable-verification flag in the vbmeta image being flashed.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message.
X:\Applications\MinimalADBFB>fastboot -getvar current-slot
fastboot: unknown option -- g
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: 0.016s
X:\Applications\MinimalADBFB>fastboot -set-active=a
fastboot: usage: no command
X:\Applications\MinimalADBFB>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: -0.000s
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: 0.000s
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: -0.000s
X:\Applications\MinimalADBFB>fastboot -set-active=a
fastboot: usage: no command
X:\Applications\MinimalADBFB>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.016s
X:\Applications\MinimalADBFB>fastboot reboot bootloader
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.016s
X:\Applications\MinimalADBFB>
About all those "remote" failures, the commands do appear in "Bootloader Logs", and the text is something like:
"cmd: getvar:slot-count" and "cmd: set_active:a". As someone with Android unrelated programming background I see nothing that would indicate an error on the phone.
Manually rebooting to fastboot doesn't change anything, rebooting the device in general doesn't solve the issue.
After rebooting I redid my steps:
Code:
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: 0.004s
X:\Applications\MinimalADBFB>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (status read failed (Too many links))
finished. total time: 0.005s
X:\Applications\MinimalADBFB>
Too many links? Corrupted file system?
Try to update the adb & fastboot drivers.
Phone is downloading into Recovery?
Ejects from the attached archive adb folder to the root of the C:\ drive.
I didn't have a problem with these drivers.
ilia3367 said:
Try to update the adb & fastboot drivers.
Click to expand...
Click to collapse
How? There doesn't seem to be official link to fastboot, every next website I visited has different edition. Half of links are dead, others have viruses. Even manufacturers of phones seem to have different drivers.
Phone is downloading into Recovery?
Click to expand...
Click to collapse
No, the phone is stuck at boot. It doesn't automatically fallback into Recovery, nothing changed since last time I entered "Recovery Mode".
Ejects from the attached archive adb folder to the root of the C:\ drive.
Click to expand...
Click to collapse
I placed the files in plain C:\, executing your commands invoked following response:
Code:
C:\>fastboot getvar current-slot
< waiting for any device >
current-slot: a
Finished. Total time: 0.001s
C:\>fastboot --set-active=a
fastboot: error: Device does not support slots
How is a device determined by a computer in Device Manager?
What does the "fastboot devices" command say?
---------- Post added at 13:57 ---------- Previous post was at 13:55 ----------
Your phone is in the correct boot Slot A, where you should install the firmware.
---------- Post added at 13:58 ---------- Previous post was at 13:57 ----------
Is the bootloader unlocked?
ilia3367 said:
How is a device determined by a computer in Device Manager?
What does the "fastboot devices" command say?
---------- Post added at 13:57 ---------- Previous post was at 13:55 ----------
Your phone is in the correct boot Slot A, where you should install the firmware.
---------- Post added at 13:58 ---------- Previous post was at 13:57 ----------
Is the bootloader unlocked?
Click to expand...
Click to collapse
Device Manager calls my phone "Motorola ADB Interface".
fastboot devices says:
Code:
C:\>fastboot devices
ZY226KZGT5 fastboot
"Your phone is in the correct boot Slot A, where you should install the firmware."
Is there a way to recover data first?
"Is the bootloader locked?"
I have no idea.
Screen mentions:
"oem_locked"
"AP Fastboot Flash Mode (Secure)"
Code:
C:\>fastboot flashing get_unlock_ability
(bootloader) use "oem get_unlock_data" and web portal
(bootloader) http://motorola.com/unlockbootloader
OKAY [ 0.005s]
Finished. Total time: 0.008s
"Is there a way to recover data first?" - Are you sure there's something left? Then remove the line "fastboot erase userdata" from the .bat executive file and your data will be saved.
ilia3367 said:
"Is there a way to recover data first?" - Are you sure there's something left?
Click to expand...
Click to collapse
I had 120GB of data on it, before it crapped out on me.
Then remove the line "fastboot erase userdata" from the .bat executive file and your data will be saved.
Click to expand...
Click to collapse
Which file? Tehre's no bat file in the zip you provided.
yeetusAAA said:
I had 120GB of data on it, before it crapped out on me.
Which file? Tehre's no bat file in the zip you provided.
Click to expand...
Click to collapse
I have written some instructions for flashing firmware
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
I have written some instructions for flashing firmware
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
- After four subsequent link clicks to "[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot", the post mentions "Your Cedric will boot normally again", but I have Motorola, other of your post say that you shouldn't downgrade flash, also the adb shell dd if=/dev/zero of= writes null to the given partition. No further instruction on how to get into "TWRP" boot. No way of knowing if it will preserve my data.
- Verizon Tool detects my cellphone but after half an hour its still not done initializing.
- Lenovo Assistance requires USB debugging.
- RSD Lite's instructions say: "WARNING Restoring your Motorola firmware will factory reset your device and you will loose all data on the device and have to set it back up like a new phone.", can I recover my data before hand?
No recovery instructions, tree of links and still no answer, can I restore the data?
It seems that people read only first 10 words and then copy link on "I've written tutorial on how to fix failed flashing" and they skip past "I want to backup my data" and "I haven't flashed my smartphone, it just happened".
Every next poster seems entirely oblivious of the main post and every post that comes before the post they respond to.
I get it, you're educated on the topic and have everything figured out, I don't. Why do you assume I would know how?
yeetusAAA said:
- After four subsequent link clicks to "[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot", the post mentions "Your Cedric will boot normally again", but I have Motorola, other of your post say that you shouldn't downgrade flash, also the adb shell dd if=/dev/zero of= writes null to the given partition. No further instruction on how to get into "TWRP" boot. No way of knowing if it will preserve my data.
- Verizon Tool detects my cellphone but after half an hour its still not done initializing.
- Lenovo Assistance requires USB debugging.
- RSD Lite's instructions say: "WARNING Restoring your Motorola firmware will factory reset your device and you will loose all data on the device and have to set it back up like a new phone.", can I recover my data before hand?
No recovery instructions, tree of links and still no answer, can I restore the data?
It seems that people read only first 10 words and then copy link on "I've written tutorial on how to fix failed flashing" and they skip past "I want to backup my data" and "I haven't flashed my smartphone, it just happened".
Every next poster seems entirely oblivious of the main post and every post that comes before the post they respond to.
I get it, you're educated on the topic and have everything figured out, I don't. Why do you assume I would know how?
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Code:
C:\>fastboot getvar all
getvar:all FAILED (Status read failed (Too many links))
Finished. Total time: 0.005s
yeetusAAA said:
What does getvar all say?
Click to expand...
Click to collapse
As I said in your other thread.
You cannot backup data with locked bootloader.
If you want to save the data, take it to a shop that has the special tools required.
Sent from my ali using XDA Labs
sd_shadow said:
As I said in your other thread.
You cannot backup data with locked bootloader.
If you want to save the data, take it to a shop that has the special tools required.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
I see. Thanks.
bricked phone
so i tried installing firmware on the one zoom and ended up having problem where now it wont boot at all i get no connection from computer and only the logo lights up is there any way to revive my phone ,also holding down the volume down and power button wont do anything is there anything i can do?
death1426 said:
so i tried installing firmware on the one zoom and ended up having problem where now it wont boot at all i get no connection from computer and only the logo lights up is there any way to revive my phone ,also holding down the volume down and power button wont do anything is there anything i can do?
Click to expand...
Click to collapse
Does it show up in device manager?
Sent from my Moto E (4) using Tapatalk
does not show up in device manager
sd_shadow said:
Does it show up in device manager?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
no unfortunately it does not already tried placing it in edl mode with a cable but no to avail also installed Qualcomm drivers just to be sure uncertain what i can do at this point