Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
oppili said:
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
Click to expand...
Click to collapse
Yes, im sure. On bootloader mode is in red color - Phone unlocked, but i not using Linux, im on Windows 7 and this not help me....
Try fastboot oem unlock - command again.
If still not works, try fastboot erase of that *.img file before flashing that new img file.
oppili said:
Try fastboot oem unlock - command again.
When i try this command...
c:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.004s]
finished. total time: 0.006s
If still not works, try fastboot erase of that *.img file before flashing that new img file.
Click to expand...
Click to collapse
I know about this but im above when i try erase all after this fastboot send me "Failed..." and i will be have dead phone, tell me - when i try erase command for all partitions - will be phone work wit fastboot after this??
THX
Are you the only user in pc ? Do you have admin rights ?
or
try any other pc
or
use Ubuntu OS
Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
thilak devraj said:
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
Click to expand...
Click to collapse
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
then you should take it to the service center. the only best thing you can do now..
Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
erase cache command is blocked by huawei in fastboot irrespective of locked or unlocked state. somewhere i read unlock lost permissions after update. if you have not tried unlock after update try it. driver can also be an issue, install hisuite it comes with drivers.
Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
shady143 said:
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
Click to expand...
Click to collapse
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
zzztidurvirus said:
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
Click to expand...
Click to collapse
First...many thanks for your interest!
Look, about bootloader, on boot mode is in red PHONE UNLOCKED, i try this command in fastboot:
C:\Minimal ADB and Fastboot>adb reboot bootloader
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot oem backdoor info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ -0.000s]
finished. total time: -0.000s
so what is FB Lockstate??Is my bootloader unlocked or locked??
Here is another command which i try....
C:\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
Cant derermine partition type - is this problem?
I also try this....
C:\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 1.033s]
finished. total time: 1.831s
C:\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
It seems that fastboot write recovery (with your help i need use admin rights now this work) but i still cant boot to recovery no matter how...
I can also flash and backup boot and recovery via Flashify or Rashr and when i open backup with HEX editor it seems that i succesfully upload TWRP but still cannot acess TWRP recovery....
This is all what i try in this time, of course i read your help words about Huawei extractor etc. but not try at this time, i hope i explain more detailed my problem. Look im not a newbie, i allready flash etc. my Lenovo and P9 lite what i have here but not understand where can be problem in this Honor 4x, it seems like corrupted recovery partition or can be problem in read only/write partition - i play with this option before....
anyway - run as admin - this help me a lot i think, THX and wait your answer.
EDIT: one thing, you think that when i try flash stock recovery (i can, no problem of course) it will be work?
Update: Big success, i just try flash stock recovery B064b and now im in stock recovery menu, im surprised but what now? I want update to Marshmallow 6.0....?
But in stock recovery is: phone and the data cannot be recovered. Continue?
Oh sorry, this is about "not sd card inserted" problem
What will now progress? I have inside B130 firmware and want Marshmallow, also TWRP recovery must i flash now especially for B130 firmware for work?
Update: Yes, all working now, factory reset, recovery etc. you help me a lot, only if you can tell me what number of firmware must i upload for Marshmallow, thx
Last update: So finally, coz im too hurry and dont want wait for your answer :angel:, i just upload from local update first Android 5.1.1. after this 6.0 and all is perfect and working!
My big thanks and kisses goes to you zzztidurvirus, im lucky and still cant beleive that all works, again thx!!
I did once on Win to revert back to Stock from CM12.1 by using img from update.app file. For my case, it's the MM update.app not working, I couldn't flash img files into phone, then I tried to flash files from LP, it worked. I boot into LP ROM and update from there to MM.
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
I had faced same issue but get back by using the that method.
Sumea said:
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Click to expand...
Click to collapse
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Lulu_568 said:
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Click to expand...
Click to collapse
Sadly not, as I tried both running ADB fastboot as admin from administrator command line and I tried three different recovery images from huawei, 6.0 (because the flash went bad during attempt to flash a 4.1EMUI with 6.0 B506 ROM for CHE2-L11) - And it keeps denying the write attempt with the same message. More info on the flash: I tried to TWRP flash from 5.1 rom to the EMUI4.1 6.0 ROM following guide someone made with updateappflasher.zip or something, during the flash the phone just crashed 60% in the bar and after that the phone is boot looping into recovery but it can't do anything. Like said any attempt to flash a stock rom even if a recovery seems to exist when booting VOL+ & POWER at the same time, but it will fail if attempting to do wipe data/factory reset in 40% mark. Forced updater can also be accessed but again, thanks to the firmware situation the phone is in it does not flash anything beyond 5% without crashing and being stuck or just giving an error message outright.
Only thing I might have not have is the right kind of ADB drivers but googling about CHE2-L11 I really cannot find a ADB drivers for this phone for life of me and dealing with windows 10 these days makes it worse. At least it used to be that I was with windows 7, back when I myself unlocked the bootloader of the phone and rooted it myself, I have some memory of that being harsh to deal with too, as I had hard time getting drivers that worked right with the phone etc.
I will check into this... At this point my friend bought a new phone already but I still will try to fix the phone for him since I feel personally pretty bad for pretty big mess I made.
I will also try this with a windows XP machine I have still, it is meant entirely for different things but at times like these it is somewhat nice to have a XP around. At least the darn driver problems are not a problem.
UPDATES:
I unbricked the phone. The stock recovery was intact enough for just a normal dload install of a update.app from huawei - why it did not initially work was probably the USB connection to computer and/or 64gig microSD card my friend had, not being compatible with Huawei's recovery updater. I myself had a 8gig card around which worked and I restored the phone ultimately to a 6.0 official ROM. I also went ahead to root it - and final find really was that the reason why recovery etc. would not flash, was because I wrote "fastboot flash RECOVERY twrp.img" - instead of "fastboot flash recovery twrp.img" - the latter works, and the all caps for "RECOVERY" results in illegal command error - and it was no bigger than that.
Meanwhile even after sorting this all out my friend already ended up buying a new phone so it hurts but I hope some other people find some info here useful.
Guys, here's the problem:
I've clicked reboot to recovery in power menu in Pure Nexus ROM and now I'm stuck in recovery bootloop.
The phone tries to boot into recovery, shows the leeco recovery message and then flashes red triangle android robot and just shows black screen. If I connect to PC at that point, adb recognises a device in recovery mode. But I can't flash anything.
If I try long enough I can boot into fastboot, but then I get the "Android Bootloader Interface" in the device manager - but adb doesn't see the device.
Any suggestions? Can i somehow make ADB see the device so I can reflash TWRP?
ziembus said:
Guys, here's the problem:
I've clicked reboot to recovery in power menu in Pure Nexus ROM and now I'm stuck in recovery bootloop.
The phone tries to boot into recovery, shows the leeco recovery message and then flashes red triangle android robot and just shows black screen. If I connect to PC at that point, adb recognises a device in recovery mode. But I can't flash anything.
If I try long enough I can boot into fastboot, but then I get the "Android Bootloader Interface" in the device manager - but adb doesn't see the device.
Any suggestions? Can i somehow make ADB see the device so I can reflash TWRP?
Click to expand...
Click to collapse
Dear
Press and hold vol - and power button together, then your phone will boot into fastboot mode.
then simply you can use fastboot commond below to flash recovery.
fastboot flash recovery recovery.img
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
ziembus said:
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
Click to expand...
Click to collapse
I want to know which recovery you tried to flash through fastboot. It may not allow you flashing twrp ultill oem is locked. You can try flashing stocking recovery.
ziembus said:
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
Click to expand...
Click to collapse
When in fastboot mode, you can try to boot twrp from the pc with
Code:
fastboot boot nameoftwrp.img
JamBax said:
When in fastboot mode, you can try to boot twrp from the pc with
Click to expand...
Click to collapse
Tried that, it tells me that I can't do this because the phone os locked. Now I'm looking for Stock recovery IMG for x522
EDIT: Trying to flash stock recovery gets me this message:
target reported max download size of 536870912 bytes
sending 'recovery' (13904 KB)...
OKAY [ 0.435s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.451s
Its the same whether its TWRP image or stock recovery image.
I was thinking of using this:
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
But, unfortunately, there is no file for American x522.
It sucks to be able to get into fastboot and not be able to do anything.
Thanks for the suggestions so far
ziembus said:
Tried that, it tells me that I can't do this because the phone os locked. Now I'm looking for Stock recovery IMG for x522
EDIT: Trying to flash stock recovery gets me this message:
target reported max download size of 536870912 bytes
sending 'recovery' (13904 KB)...
OKAY [ 0.435s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.451s
Its the same whether its TWRP image or stock recovery image.
I was thinking of using this:
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
But, unfortunately, there is no file for American x522.
It sucks to be able to get into fastboot and not be able to do anything.
Thanks for the suggestions so far
Click to expand...
Click to collapse
Try Leeco AIO tool kit to reboot your device into recovery . It's working for me
leco le 2 x520 recovery problem
I have a problem with recovery in le 2 x520. It installs via fastboot by unlocking the bootloader but stops at the Le recovery logo and nothing else happens. I installed from version 3.0.2.0 to 3.1.1.1 and nothing happens, I do not have recovery and writes everything okey went. what is going on ??
I have same problem. how to fix
I have a new one (acutally two, got them for U$D 108.99 each one)
Using ADB devices it recognize the UID like 0123456789ABCDEF, so I think the recovery is corrupted, intentional or not, it is blocking fastboot and recovery to load normally.
At this point I can't do anything.... any suggestions?
You solved it ?
I having the same issue maybe the issue is with stock rom since i flashed in normal twrp,chinese twrp and also that stock recovery.
****!
I think so I have Bricked my Moto G 2014 Titan mobile!!
It happened as i was about to update TWRP latest version so I was installing the downloaded img format of latest TWRP (3.1.1) in my mobile ...while installing the image file 2 option were asked ROOT and something i dont remember I flashed the image in both options and when i tried to restart my mobile in boot mode it was giving below Error and I was unable to restart my device.
Error Msg :-
"Invalid Boot Image Size!"
failed to validate recovery image
boot up failed
Can anyone please HELP ME! to resolve the Issue
Abhishek_AroX said:
I think so I have Bricked my Moto G 2014 Titan mobile!!
It happened as i was about to update TWRP latest version so I was installing the downloaded img format of latest TWRP (3.1.1) in my mobile ...while installing the image file 2 option were asked ROOT and something i dont remember I flashed the image in both options and when i tried to restart my mobile in boot mode it was giving below Error and I was unable to restart my device.
Error Msg :-
"Invalid Boot Image Size!"
failed to validate recovery image
boot up failed
Can anyone please HELP ME! to resolve the Issue
Click to expand...
Click to collapse
Flash TWRP again via PC and reflash the rom.. It'll solve the issue
avrockz11 said:
Flash TWRP again via PC and reflash the rom.. It'll solve the issue
Click to expand...
Click to collapse
Hi
My phone is not detecting in PC via usb cable...even though I am connecting it to PC it's showing message on the screen as "Connect USB Data cable"..(it's staying in boot load selection menu). how can I flash TWRP again?
It's even not showing any adb devices when I am trying to install it via minimal ADB and flash boot software.
Could you suggest any another alternative method
Abhishek_AroX said:
Hi
My phone is not detecting in PC via usb cable...even though I am connecting it to PC it's showing message on the screen as "Connect USB Data cable"..(it's staying in boot load selection menu). how can I flash TWRP again?
It's even not showing any adb devices when I am trying to install it via minimal ADB and flash boot software.
Could you suggest any another alternative method
Click to expand...
Click to collapse
Have you installed the motorola drivers on your PC
avrockz11 said:
Have you installed the motorola drivers on your PC
Click to expand...
Click to collapse
Hi !!!!
After installing drivers i was able to see line "USB Connected" in Boot Mode Selection Menu but in ADB fastboot CMD.exe when i was typing "ADB Devices"
it was not showing my device it was showing line "List of device attached in written" but nothing was present......further i entered command "adb reboot bootloader".....
it throwed Error : Device not found.
Can you suggest me how can I install TWRP in my device in such scenario...........any video link or website links.
Abhishek_AroX said:
Hi !!!!
After installing drivers i was able to see line "USB Connected" in Boot Mode Selection Menu but in ADB fastboot CMD.exe when i was typing "ADB Devices"
it was not showing my device it was showing line "List of device attached in written" but nothing was present......further i entered command "adb reboot bootloader".....
it throwed Error : Device not found.
Can you suggest me how can I install TWRP in my device in such scenario...........any video link or website links.
Click to expand...
Click to collapse
Follow the first few steps of this thread
https://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818
If these steps doesn't work,try repeating the steps after installing android studio
2. If your device gets stuck in following situations it has soft bricked.
- Stuck on Motorola logo or "Unlocked Bootloader" screen.
- Stuck on boot animation or device restarts automatically (boot loop)
- Cannot boot into recovery mode.
- Can boot into fastboot mode only.
3. If your device gets stuck in following situations it has hard bricked.
- Cannot boot into fastboot mode.
- Cannot power on or cannot charge.
- Cannot boot into recovery mode.
further i noticed the above scenarios for finding Solution ....
I have one Issue in my mobile. Its showing connected in bootloader mode when connected via PC but not getting charged when connecting a charger for 6..8 hrs Its still at 0 % charge.
Is it a soft Brick or Hard Brick ?
Urgent HELP!!! Bricked MOTO G 2014 TITAN ( Issue RESOLVED !)
Thanks a lot avrockz11 for your help!!!
Hello friends!
My Cell was Soft Bricked and I have repaired it! :highfive:
I have made below Overview for those who could face such kind of Issues can follow below steps :
ISSUE:
Refer the above thread for my Issue.
If someone encounters such Issues please refer below steps to resolve it
What is A Brick?
A soft brick, is usually just when you're phone is stuck in a bootloop, and as the name implies, is caused by a software error, usually the lack of a system to boot from or some other minor software bug that glitching boot. They are easily fixable by reflashing your ROM in recovery.
A Brick Usually Occurs when you Flash a Wrong Firmware on your device or you try to downgrade your bootloader.
1. If your device gets stuck in following situations it has Soft bricked.
- Stuck on Motorola logo or "Unlocked Bootloader" screen.
- Stuck on boot animation or device restarts automatically (boot loop)
- Cannot boot into recovery mode.
- Can boot into fastboot mode only.
2. If your device gets stuck in following situations it has Hard bricked.
- Cannot boot into fastboot mode.
- Cannot power on or cannot charge.
- Cannot boot into recovery mode.
In my case the mobile was booting in fast bootmode plus it was not charging so I was confused whether it was soft Bricked or Hard Bricked later it was figured out. When I was pressing the Volume up key while selecting “Normal Power up ” nothing was happening i.e. it was not entering into TWRP mode. I was just able to see Power up mode showing Battery 0% (i.e bootup screen) for hardly 1 second after that it was reverting back to “boot load selection menu” throwing the below Error.(As Previously I had flashed lower TWRP image in it)
Error Msg :-
Invalid Boot Image Size!
failed to validate recovery image
boot up failed
Due to which I was neither able to enter in TWRP mode nor able to Flash new custom ROM’s. So to Resolve this Issue I tried some trick / Experiment i.e. by pressing the Volume up key for 10 second while selecting “Normal Power up ” while its connected to charger it got hanged to that screen showing 0 % battery I left it in that state for 4..5 hrs in hope it would get charged ..but after 5 hours it was still showing 0 % charge only. So I again restarted it into “boot load selection menu Holding “Volume Down + power key and Bingo it worked out ” Now it was showing “battery in Good/OK state” notification before it was showing “Battery Low ” State ,So my Trick worked out and my mobile was in charged state as to follow further Flash process (Which Confirmed it was Soft Bricked and not Hard Bricked).
Now the second challenge I faced. that was………. my mobile was not detecting USB cable of my Laptop thus showing message
“Connect USB Data Cable”
TIP: Use proper USB Data cable for connecting mobile to PC.
Minimal ADB + Fastboot Drivers v1.4.2
Install Motorola Device Manager Drivers v2.5.4
TWRP v3.1.1-0 for titan
SuperSU v2.82 Stable
(Motorola Drivers helps in detecting / connecting mobile to PC for flashing any ROM’s)
And installing it helped me out as the device status changed to
“Transfer Mode: Device Connected”
So Now I was free to install the TWRP. But in that also I faced one Error which I resolved by using below steps:
Please find the Attachment at the bottom of Errors in CMD.exe
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install via ADB
Open the folder where your TWRP Recovery .img file is saved.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and
then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into
bootloader/fastboot mode:
adb reboot bootloader
If your asks for permission to “Allow USB debugging”, tap OK.
Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery twrp-3.1.x.x-xxx.img
└ Here modify twrp.img with the name of your TWRP recovery .img file.
Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot
Commands for Flashing TWRP in Mobile Via PC
fastboot flash recovery twrp-3.1.1-0-titan.img
fastboot boot recovery twrp-3.1.1-0-titan.img
I connected my mobile to PC via USB data Cable and ran above commands in CMD.exe
The 1st command (fastboot flash recovery twrp-3.1.1-0-titan.img )flashed the TWRP properly (TWRP image should be of Latest
Verison )in my mobile (refer above pic)
But the 2nd command (fastboot flash recovery twrp-3.1.1-0-titan.img ) error out showing above Error (refer above pic). Don’t
worry your work is done in step 1 st only.
Just exit from CMD.exe and in your mobile scroll down by volume down and select “Recovery tab” and you are done. It starts
into boot loader mode and enters into your flashed TWRP mode…Done . Now you Can Install any Custom ROM’s of your
choice
and your mobile is ready to be used.!
Please Refer below links for Flashing TWRP (Steps) => By SharkcpN ( Best Explained in detail ). :good:
[GUIDE] ✮ Unlock + Root + Backup + Restore + Downgrade (Updated 01/08/17)
Please Refer below links for Flashing TWRP (Video)
Youtube Link of Video
THANKS!!!
:laugh: