Related
plz help, I tried to flash my phone today and now the usb does not work under fastboot anymore, when i try to put the phone in fastboot and type the command in cmd it just says *waiting for device* and i have to use cmd for flash the boot.img so in theory i think my phone is brickt, but i can access my sd card and all that stuff but my phone wont boot, can sombody plz help?
HBOOT 2.02.0002
RADIO-3831.10.00.11_M
ROM: sabsa_prime_V10.0
S: on
GBmaster said:
plz help, I tried to flash my phone today and now the usb does not work under fastboot anymore, when i try to put the phone in fastboot and type the command in cmd it just says *waiting for device* and i have to use cmd for flash the boot.img so in theory i think my phone is brickt, but i can access my sd card and all that stuff but my phone wont boot, can sombody plz help?
HBOOT 2.02.0002
RADIO-3831.10.00.11_M
ROM: sabsa_prime_V10.0
S: on
Click to expand...
Click to collapse
Are you trying fastboot commands or adb?
Try this, when in android
"adb reboot bootloader"
then when its in bootloader,
"fastboot devices" and see if your serial number comes up
markj338 said:
Are you trying fastboot commands or adb?
Try this, when in android
"adb reboot bootloader"
then when its in bootloader,
"fastboot devices" and see if your serial number comes up
Click to expand...
Click to collapse
trying fastboot commands yes, but the phone does not go into usb mode
C:\android>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
that did not work either
is there anyway to flash the boot.img file from cwm? thats what i need to get the phone working again!
Do you Use Win8?
Silversniper said:
Do you Use Win8?
Click to expand...
Click to collapse
no i use windows 7! tryd on every computer i have and still the same, no usb in fastboot
Nobody knows how to fix it?
Sent from my GT-P5110 using xda app-developers app
I am having a similar issue, the phone boots and the USB port works fine in recovery and when booted but nothing happens when it is plugged into the PC in fastboot mode. It is not the PC as other phones work fine in fastboot etc. It seems like the fatboot part of the hboot does not recognise USB, there is not even any device appearing in the device manager (unknown or known) when the phone is in fastboot and connected to the PC, it should change on the phone to say "FASTBOOT USB" when connected to the computer, It makes unlocking the boot loader a bit difficult as I cannot execute the fastboot oem command to get the unlock code from htcdev.com
Ok guys, so I was trying to flash the software on my Sprint HTC One with a custom one, while drunk. Needless to say it didn't work. I suspect that chrome f*cked up downloading the rom, because it was only 800mb, and should have been about 1gb. Now, the phone isn't working. When I try to turn it on it shows the htc logo and then boots up in fastboot. Fastboot still receives cmd commands, but I still havent found a way to flash an RUU on it. Tryed with twrp as a recovery- cant mount to computer. Tryed sending the file to phone through cmd- some error about not working radio came through. I'm cutting corners explayning all the methods I tryed to make it work, but there were a lot of them and I dont remember all. I have flashed the boot and the recovery back to the stock ones, bootloader IS unlocked. Phone vertion (as shown in the bootloader screen):
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT- 1.44.0000
OpenDSP-v31.120.274.0617
eMMC- boot
Jul 5 2013,17:19:22:-1
My question is how do I return it to stock condition (or unlocked to all networks if possible)? Please, I've been trying to fix it on my own for over a week now, and am getting desperate. If possible please give links to step-by-step tutorials and/or files I'll need. Thank you in advance.
PS.: Also, for some reason my computer does fails to install the HTC MTP device driver. Could it be from that, and if it is- will using a different computer solve the problem (tryed a million times to fix that as well- no luck)?
drobalqk said:
Ok guys, so I was trying to flash the software on my Sprint HTC One with a custom one, while drunk. Needless to say it didn't work. I suspect that chrome f*cked up downloading the rom, because it was only 800mb, and should have been about 1gb. Now, the phone isn't working. When I try to turn it on it shows the htc logo and then boots up in fastboot. Fastboot still receives cmd commands, but I still havent found a way to flash an RUU on it. Tryed with twrp as a recovery- cant mount to computer. Tryed sending the file to phone through cmd- some error about not working radio came through. I'm cutting corners explayning all the methods I tryed to make it work, but there were a lot of them and I dont remember all. I have flashed the boot and the recovery back to the stock ones, bootloader IS unlocked. Phone vertion (as shown in the bootloader screen):
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT- 1.44.0000
OpenDSP-v31.120.274.0617
eMMC- boot
Jul 5 2013,17:19:22:-1
My question is how do I return it to stock condition (or unlocked to all networks if possible)? Please, I've been trying to fix it on my own for over a week now, and am getting desperate. If possible please give links to step-by-step tutorials and/or files I'll need. Thank you in advance.
Click to expand...
Click to collapse
It sounds like you have the same problem that a lot of people are getting into around here, myself included. You tried to flash a non-cdma compatible rom onto your phone.
There are numerous postings about how to fix this, however, it depends on the condition of your phone which step you take.
If you have recovery installed and you have access to recovery you will take different steps than if you only have access to fastboot.
You need to have a recovery installed and you need to relock your phone to fastboot ruu. Once that is done you basically start from scratch and unlick your phone again and then you can reinstall the recovery and then flash the correct cdma compatible roms.
MrFixit007 said:
It sounds like you have the same problem that a lot of people are getting into around here, myself included. You tried to flash a non-cdma compatible rom onto your phone.
There are numerous postings about how to fix this, however, it depends on the condition of your phone which step you take.
If you have recovery installed and you have access to recovery you will take different steps than if you only have access to fastboot.
You need to have a recovery installed and you need to relock your phone to fastboot ruu. Once that is done you basically start from scratch and unlick your phone again and then you can reinstall the recovery and then flash the correct cdma compatible roms.
Click to expand...
Click to collapse
The recovery I can install in a matter of seconds, same with relocking. I have the lastest vertions on both TWRP and Clockwork. Which one do I install and how do I proceed after? Thank you
drobalqk said:
The recovery I can install in a matter of seconds, same with relocking. I have the lastest vertions on both TWRP and Clockwork. Which one do I install and how do I proceed after? Thank you
Click to expand...
Click to collapse
do you have adb access? or only fastboot access?
MrFixit007 said:
do you have adb access? or only fastboot access?
Click to expand...
Click to collapse
adb- Im not sure. How do I check? Fastboot- I think so. It accepts my cmd commands for flashing recovery and rom (although when I tryed to flash rom it failed).
drobalqk said:
adb- Im not sure. How do I check? Fastboot- I think so. It accepts my cmd commands for flashing recovery and rom (although when I tryed to flash rom it failed).
Click to expand...
Click to collapse
In your command window in the same directory you run fastboot from, you should be able to run adb.
The easiest way to check is to type: adb devices
this should return a value if you are booted into recovery.
it will give you nothing if you aren't in recovery.
if you cannot get into recovery then you need to make sure your phone is unlocked and then fastboot a recovery onto your phone.
MrFixit007 said:
In your command window in the same directory you run fastboot from, you should be able to run adb.
The easiest way to check is to type: adb devices
this should return a value if you are booted into recovery.
it will give you nothing if you aren't in recovery.
if you cannot get into recovery then you need to make sure your phone is unlocked and then fastboot a recovery onto your phone.
Click to expand...
Click to collapse
I currently have the stock recovery flashed on it. Is that one going to work or should I flash TWRP/ Clockwork?
drobalqk said:
I currently have the stock recovery flashed on it. Is that one going to work or should I flash TWRP/ Clockwork?
Click to expand...
Click to collapse
as long as you can boot into recovery, it should work. i personally favor twrp, but any recovery should work.
try out some adb commands and see.
adb sevices
adb shell
if you get anywhere with those while booted into recovery you should be ok.
MrFixit007 said:
as long as you can boot into recovery, it should work. i personally favor twrp, but any recovery should work.
try out some adb commands and see.
adb sevices
adb shell
if you get anywhere with those while booted into recovery you should be ok.
Click to expand...
Click to collapse
adb devices returns no values
adb services returns big list of commands
adb shell returns error device not found.
I'm into TWRP v.2.6.1.0 start screen.
drobalqk said:
adb devices returns no values
adb services returns big list of commands
adb shell returns error device not found.
I'm into TWRP v.2.6.1.0 start screen.
Click to expand...
Click to collapse
did those adb errors or no devices found occur while your phone was showing the twrp start screen?
if yes, then we need to reboot into the bootloader-- to fastboot.
if no then try adb shell again while showing the twrp start screen.
MrFixit007 said:
did those adb errors or no devices found occur while your phone was showing the twrp start screen?
if yes, then we need to reboot into the bootloader-- to fastboot.
if no then try adb shell again while showing the twrp start screen.
Click to expand...
Click to collapse
Yes, I was IN TWRP recovery home screen. I'll try the commands in fastboot as soon as I come back from work. Thank you for the time you spend trying to help me, I do very much apreciate it.
drobalqk said:
Yes, I was IN TWRP recovery home screen. I'll try the commands in fastboot as soon as I come back from work. Thank you for the time you spend trying to help me, I do very much apreciate it.
Click to expand...
Click to collapse
It seems like you need to fastboot flash recovery onto your phone again.
Here are the steps as I think they should work to get you back up and running.
**Make sure your phone is unlocked. (it should display ***UNLOCKED*** at the top of the bootloader screen)
if you ARE unlocked do the following(+++see below if you are NOT unlocked+++)
1. from bootloader select fastboot - connect phone to computer. fastboot should change to fastboot usb when you have a good connection.
on your computer:
2. open a command window and navigate to the folder where adb and fastboot are located
3. type in "fastboot flash recovery xxxxxxxx.zip" where xxxxxxxx.zip is the name of recovery zip file without quotes. Make sure you download a good copy appropriate for your phone. I would use this one: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.1.0-m7wls.img
4. type fastboot reboot
on your phone:
5. once it is rebooted and in bootloader select recovery and boot into recovery.
on your computer:
6. once your phone shows recovery main screen then typeat the command prompt: adb shell
7. no matter what the prompt looks like type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
8. no matter if it errors or not type: adb reboot bootloader
9. type: fastboot oem lock
10. type: fastboot oem rebootRUU
11. type fastboot flash zip xxxxxxxxxxxxx.zip where xxxxxxxxxxxxx.zip is the name of the ruu.zip file. i would use this one: http://www.androidfilehost.com/?fid=22926241640219526
12 reboot your phone once that is successful!! If you get the "flush image again immideately" error message then repeat step 11. then reboot your phone.
you should now be running a stock sprint phone.
you can now unlock your phone again and reinstall a recovery.
to unlock your phone the second time:
13. boot your phone into bootloader then go to fastboot - make sure the phone is connected to the computer
14. on your computer type in: fastboot flash unlocktoken Unlock_code.bin
15. on your phone select unlock with volume rocker and press power once unlock is selected
16. on computer type: fastboot flash recovery xxxxxxxxx.zip where xxxxxxxxxx.zip is the same recovery zip file we used above in step 3
17. reboot your phone and you are now unlocked and you have a custom recovery installed and you can download a CDMA compatible rom to your phone and install it with the recovery like normal. or you can continue to run stock.
MAKE SURE YOU ONLY DOWNLOAD CDMA COMPATIBLE ROMS FROM THE SPRINT HTC ONE FORUMS.
enjoii!!
+++if you are NOT unlocked+++
try the following:
step 13
step 14
step 15
step 16
step 4
step 5
step 6-17
make sure you complete all the way through 17 after you do step 6. good luck and let me know what your results are.
MrFixit007 said:
It seems like you need to fastboot flash recovery onto your phone again.
Here are the steps as I think they should work to get you back up and running.
**Make sure your phone is unlocked. (it should display ***UNLOCKED*** at the top of the bootloader screen)
if you ARE unlocked do the following(+++see below if you are NOT unlocked+++)
1. from bootloader select fastboot - connect phone to computer. fastboot should change to fastboot usb when you have a good connection.
on your computer:
2. open a command window and navigate to the folder where adb and fastboot are located
3. type in "fastboot flash recovery xxxxxxxx.zip" where xxxxxxxx.zip is the name of recovery zip file without quotes. Make sure you download a good copy appropriate for your phone. I would use this one: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.1.0-m7wls.img
4. type fastboot reboot
on your phone:
5. once it is rebooted and in bootloader select recovery and boot into recovery.
on your computer:
6. once your phone shows recovery main screen then typeat the command prompt: adb shell
7. no matter what the prompt looks like type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
8. no matter if it errors or not type: adb reboot bootloader
9. type: fastboot oem lock
10. type: fastboot oem rebootRUU
11. type fastboot flash zip xxxxxxxxxxxxx.zip where xxxxxxxxxxxxx.zip is the name of the ruu.zip file. i would use this one: http://www.androidfilehost.com/?fid=22926241640219526
12 reboot your phone once that is successful!! If you get the "flush image again immideately" error message then repeat step 11. then reboot your phone.
you should now be running a stock sprint phone.
you can now unlock your phone again and reinstall a recovery.
to unlock your phone the second time:
13. boot your phone into bootloader then go to fastboot - make sure the phone is connected to the computer
14. on your computer type in: fastboot flash unlocktoken Unlock_code.bin
15. on your phone select unlock with volume rocker and press power once unlock is selected
16. on computer type: fastboot flash recovery xxxxxxxxx.zip where xxxxxxxxxx.zip is the same recovery zip file we used above in step 3
17. reboot your phone and you are now unlocked and you have a custom recovery installed and you can download a CDMA compatible rom to your phone and install it with the recovery like normal. or you can continue to run stock.
MAKE SURE YOU ONLY DOWNLOAD CDMA COMPATIBLE ROMS FROM THE SPRINT HTC ONE FORUMS.
enjoii!!
+++if you are NOT unlocked+++
try the following:
step 13
step 14
step 15
step 16
step 4
step 5
step 6-17
make sure you complete all the way through 17 after you do step 6. good luck and let me know what your results are.
Click to expand...
Click to collapse
Nope, adb still doesn't work. Could it be something wrong with the drivers my computer installs? Because when I'm in recovery my computer detects the device in "Other Devices" as "M7WLS", and I don't have a driver for that and neither does microsoft update. Any suggestions?
drobalqk said:
Nope, adb still doesn't work. Could it be something wrong with the drivers my computer installs? Because when I'm in recovery my computer detects the device in "Other Devices" as "M7WLS", and I don't have a driver for that and neither does microsoft update. Any suggestions?
Click to expand...
Click to collapse
Did you install HTC Sync or did you install the naked drivers from here?
Otherwise, where in the process did you get stopped?
EDIT: You can always PM me your teamviewer info and I can work on it.
hello,
I buyed a moto g, it's my first smarthphone... it's a XT1069 Dual Sim
I followed this tuturial http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245 ,
I get to unlock the bootloader, but when I get to this point
4. Flash Recovery through fastboot mode/bootloader mode
and Go into your adb+fastboot folder and Type in CMD prompt
Command :
Code: fastboot flash recovery TWRP2801-titan-motog-2014.img
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
RastaFATian said:
hello,
I buyed a moto g, it's my first smarthphone... it's a XT1069 Dual Sim
I followed this tuturial http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245 ,
I get to unlock the bootloader, but when I get to this point
4. Flash Recovery through fastboot mode/bootloader mode
and Go into your adb+fastboot folder and Type in CMD prompt
Command :
Code: fastboot flash recovery TWRP2801-titan-motog-2014.img
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
Click to expand...
Click to collapse
There's no need to make multiple topics, my friend...
Remember that the TWRP IMG file must be in the same folder as your Fastboot files.
So, you can copy TWRP2801-titan-motog-2014.img file to the directory where your Fastboot is.
Or, you can type the directories correctly. For example, if your TWRP2.8.0.1 IMG file is located on your Desktop:
So, your command should be: fastboot flash recovery C:\Users\"username"\Desktop\TWRP2801-titan-motog-2014.img
Instead of typing, you can also drag-and-drop the TWRP2801-titan-motog-2014.img file into the CMD window.
Got it?
rafaelbrunner said:
There's no need to make multiple topics, my friend...
Remember that the TWRP IMG file must be in the same folder as your Fastboot files.
So, you can copy TWRP2801-titan-motog-2014.img file to the directory where your Fastboot is.
Or, you can type the directories correctly. For example, if your TWRP2.8.0.1 IMG file is located on your Desktop:
So, your command should be: fastboot flash recovery C:\Users\"username"\Desktop\TWRP2801-titan-motog-2014.img
Instead of typing, you can also drag-and-drop the TWRP2801-titan-motog-2014.img file into the CMD window.
Got it?
Click to expand...
Click to collapse
I'm sorry about multiple topics... my bad.... but you can erase the other in general topic....
but to flash i need to be in recovery mode at boolloader, no?
i can do this command in bootloader menu?
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
Fastboot and recovery are two different things. If you can get to Fastboot (bootloader) mode you should be able to flash recovery from there as stated by rafaelbrunner.
Hi Guys !
I'm facing a problem on rooting my Moto G 2014.
I've easily unlocked the bootloader but i can't flash the TWRP recovery.
I've read everything I could read about the process and I think I'm doing it the right way (the recovery file in the adb folder, etc...) and everything seems to be ok.
I've just a purple line at the end of the TWRP flashing procedure saying:
Mismatched partition size (recovery)
This post says that it's not really a problem: http://forum.xda-developers.com/showpost.php?p=48294073&postcount=6
Then, when I reboot the recovery, the phone reboots and the system starts normally (instead of restarting with the custom recovery ?). When I switch it off and switch it on in recovery mode, I still have the stock recovery.
Tried several times with TWRP 2.8.0.1
I can't say if it's because of a problem with TWRP (it's said here that it is buggy) or because I'm doing something wrong that I don't succeed.
I saw that there was a 2.7.1.1 release of TWRP for Moto G 2014 but it's no more available anywhere for now. I would have liked to try it...
Do you know if there's some known issues about flashing the Moto G 2014 recovery or can you help in any way ?
Hi guys !
I'm still investigating my problem and still trying to root the phone.
Here is what I get with adb:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWAP2801 titan-motog-2014.img
target reported max download size of 536870912 bytes
sending 'recovery' (9738 KB)...
OKAY [ 0.344s]
writing 'recovery'...
OKAY [ 0.353s]
finished. total time: 0.700s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
error: device not found
C:\Program Files <x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
The device seems to be seen when it's about writing the file on the storage but it's no more found when it's about rebooting the recovery...
Can someone help ?
magmatik said:
Hi guys !
I'm still investigating my problem and still trying to root the phone.
Here is what I get with adb:
The device seems to be seen when it's about writing the file on the storage but it's no more found when it's about rebooting the recovery...
Can someone help ?
Click to expand...
Click to collapse
First of all Uninstall ur old Moto Usb Drivers and fastboot drivers and Reboot your Pc And Again Install Ur Usb Drivers.
2987
jbanti said:
First of all Uninstall ur old Moto Usb Drivers and fastboot drivers and Reboot your Pc And Again Install Ur Usb Drivers.
Click to expand...
Click to collapse
Hi !
Thanks for your answer !
What do you mean exactly ? I didin't have any "old Moto usb drivers before". I installed them for the first time few days ago to unlock my bootloader.
Do I still have to uninstall these drivers (that are not that old) and install again the same ones ?
magmatik said:
Hi !
Thanks for your answer !
What do you mean exactly ? I didin't have any "old Moto usb drivers before". I installed them for the first time few days ago to unlock my bootloader.
Do I still have to uninstall these drivers (that are not that old) and install again the same ones ?
Click to expand...
Click to collapse
You can use "adb reboot recovery" only if the phone is turned on in normal android os ( in bootloader mode it'll only recognize fastboot commands ), and you must be sure also to have debug usb option enabled under settings/developer settings.
1932
eskamhl said:
You can use "adb reboot recovery" only if the phone is turned on in normal android os ( in bootloader mode it'll only recognize fastboot commands ), and you must be sure also to have debug usb option enabled under settings/developer settings.
Click to expand...
Click to collapse
Hi eskamhl,
I warmly thank you for trying to help me.
I'had enabled usb debbug, no problem about that.
I"m not sure I understand what you mean when you say that the phone has to be " turned on in normal android os". I thought that the device had to started in recovery mode to install TWRP.
I tried to install TWRP with adb reboot recovery and with the phone turned on in normal android os.
adb says <waiting for device> when i paste and execute flash recovery TWRP2801-titan-motog-2014.img
magmatik said:
Hi eskamhl,
I warmly thank you for trying to help me.
I'had enabled usb debbug, no problem about that.
I"m not sure I understand what you mean when you say that the phone has to be " turned on in normal android os". I thought that the device had to started in recovery mode to install TWRP.
I tried to install TWRP with adb reboot recovery and with the phone turned on in normal android os.
adb says <waiting for device> when i paste and execute flash recovery TWRP2801-titan-motog-2014.img
Click to expand...
Click to collapse
Adb is one thing, fastboot is a different one.
If you give a "fastboot command" from the command prompt the phone must be in bootloader mode, instead if you give an "adb command" you must have the phone normally turned on.
Having said that, I didn't understand what's your problem... are you tryin' to boot into recovery mode or trying to flash twrp recovery?
It seems that you already flashed/installed a custom recovery ( TWRP ) from what you wrote, isn't it?
eskamhl said:
Adb is one thing, fastboot is a different one.
If you give a "fastboot command" from the command prompt the phone must be in bootloader mode, instead if you give an "adb command" you must have the phone normally turned on.
Having said that, I didn't understand what's your problem... are you tryin' to boot into recovery mode or trying to flash twrp recovery?
It seems that you already flashed/installed a custom recovery ( TWRP ) from what you wrote, isn't it?
Click to expand...
Click to collapse
That's the point, I'm trying to flash a custom recovery (TWRP) in order to be able to flash SU.
I'm sorry about my poor english. I'm french and I confess that I'm absolutely comfortable in english.
For now the only thing I succeeded to do is to unlock the bootloader.
What I understand is that I have now to install TWRP with adb, am I right ?
magmatik said:
That's the point, I'm trying to flash a custom recovery (TWRP) in order to be able to flash SU.
I'm sorry about my poor english. I'm french and I confess that I'm absolutely comfortable in english.
For now the only thing I succeeded to do is to unlock the bootloader.
What I understand is that I have now to install TWRP with adb, am I right ?
Click to expand...
Click to collapse
No, you're not
You already did the installation of the custom recovery since you said that you received this message "Mismatched partition size (recovery)", now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select ).
If it won't boot maybe you should check the md5 of the downloaded recovery .img, probably it's a corrupted download.
eskamhl said:
No, you're not
You already did the installation of the custom recovery since you said that you received this message "Mismatched partition size (recovery)", now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select ).
If it won't boot maybe you should check the md5 of the downloaded recovery .img, probably it's a corrupted download.
Click to expand...
Click to collapse
When I try to boot into recovery from the bootloader (what I already did before), the screen turns black, 1 sec later the led switch on for half a sec and nothing else happends.
So, as you say, the recovery I downloaded was maybe corrupted. I'll check.
Guys, I've found the solution !
I think everything was ok from the beginning. The only thing that I did not understand was that I have to press vol- in fastboot to focus on "recovery" and to press vol+ to launch the recovery.
I didn't read it anywhere, i just see this in this video : https://www.youtube.com/watch?v=jr14wNgazOw&hd=1 (see at 7"15).
Anyway, thank you for trying to help me and see you soon for all the good things coming for this phone !
magmatik said:
Guys, I've found the solution !
I think everything was ok from the beginning. The only thing that I did not understand was that I have to press vol- in fastboot to focus on "recovery" and to press vol+ to launch the recovery.
I didn't read it anywhere, i just see this in this video : https://www.youtube.com/watch?v=jr14wNgazOw&hd=1 (see at 7"15).
Anyway, thank you for trying to help me and see you soon for all the good things coming for this phone !
Click to expand...
Click to collapse
My friend... a few posts above
eskamhl said:
now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select )
Click to expand...
Click to collapse
I successfully installed twrp recovery system but I can't do any backup, the system reboot in the process...
eskamhl said:
My friend... a few posts above
Click to expand...
Click to collapse
You're right... my bad
Hey,
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
S-ON, no-debugging usb, Bootloader locked and can't unlock him... I already tried with htc-dev, everything works but nothing appair on my screen to confirm the unlocking.
I'm really stuck, searched lot of things on google, ....
I used fastboot, and ADB, the first one recognize my device, but the last one not. I can't boot on RUU mode neither.
Any ideas?
AzweL said:
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
Click to expand...
Click to collapse
The very first thing I recommend you to do, is to download the right recovery and install it via command
Code:
fastboot flash recovery recovery.zip
Let me know if you run into any further troubles.
AzweL said:
Hey,
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
S-ON, no-debugging usb, Bootloader locked and can't unlock him... I already tried with htc-dev, everything works but nothing appair on my screen to confirm the unlocking.
I'm really stuck, searched lot of things on google, ....
I used fastboot, and ADB, the first one recognize my device, but the last one not. I can't boot on RUU mode neither.
Any ideas?
Click to expand...
Click to collapse
Hi,
Frist in boot loader check your OS version it should be something like 2.19.401.2 or lower than this.
NB: ALWAYS TRY WITH MORE THAN 75% BATTERY, AND THAT FOR ANY CODE TO WORK PROPERLY, MAKE SURE TO SELECT FASTBOOT BY POWER KEY IN BOOTLOADER
Anyway, if you can enter fastboot, then you have some chance of recovering your device and because you have S-Off it is going to be a bit difficult.
First download this stock boot file : https://mega.nz/#!lEAVwRSL!wrP2hi6GEYLeJaPf2ssZo9wCtSi7E4yfyUHgh3Q3XSs
Then place this file in the ADB folder, then run command :
To flash boot file command is:
Code:
- Fastboot Devices (this command is important to know if the device is connected and accepting and responding commands)
- fastboot flash boot boot_signed.mg (assuming this is the name you saved the file with)
- fastboot reboot bootloader
Also download Stock Recovery: https://mega.nz/#!gVJE1Bxa!6SwXStAD8p-XlnQiPkRcdNo_ITFD1ykn-tN6wIBVi1I
Place this in ADB folder and run command:
Code:
fastboot flash recovery stockrec.img // (assuming that is the name you have saved the file with), only after flashing this you will know if the device has any OS, if OS exists it will boot up.
fastboot erase cache
Attempt and let us know how it went...Good Luck
Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.
Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.
To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.
From the bootloader you should be able to flash the raw image again, it should flash everything
Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.
Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.
Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?
I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.