Hello everyone first of all english is my second language and i can make mistakes please dont put sarcastic comments about how bad i type or how big noob am i. Secondly my issue is , i accidently pressed install update at my phone which was running at 4.2.2 .(4.4.2) OTA i guess then some think like fastboot mode 840 popped up.(i used to have htc one x) and this code seemed familiar to me so i downdloaded twrp recovery (latest version) unzipped it to get the recovery.img and used the command fastboot flash recovery recovery.img i thougt i fixed my phone but my got more bricked know it says boot verification and opens at a black screen when i plug it in i see somethink like this oi57.tinypic{dot}com/r888sg.png (i only have a driver c) others is somehow connected to phone itself . what can i do ? all help will be apriciated .
I might be a newbie at this stuff but i am trying my best . thank you sincerly
edit:when i try to use adb i get a massage like this
C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Minimal ADB and Fastboot>dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of
=/sdcard/fota-backup.img
'dd' iç ya da dış komut, çalıştırılabilir
program ya da toplu iş dosyası olarak tanınmıyor.
C:\Minimal ADB and Fastboot>adb push loki_flash /data/local/tmp/loki_flash
error: device not found
C:\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Edit : i used this code to alter my recovery and flash twrp which somehowed killed my phone
Code:
C:\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1862270976 bytes
sending 'recovery' (8650 KB)...
OKAY [ 0.335s]
writing 'recovery'...
OKAY [ 0.995s]
finished. total time: 1.334s
Flashing a KDZ from scratch doesn't help?
robogo1982 said:
Flashing a KDZ from scratch doesn't help?
Click to expand...
Click to collapse
i kinda fixed it but my cache partiton got corrupted . im in ubuntu and i cant install anythink i cant mount cache , when i try to install another rom it says permission denied
Related
Followed the other threads without success, in my stupidity yesterday i wiped the boot
have install android sdk and google driver, htc syc with drivers, tried an RUU without success, copied clockwork recovery and ran the following:
C:\android-sdk-windows\tools>fastboot boot recovery-clockwork-2.5.0.7-hero.img
but receive the following:
downloading 'boot.img'...
FAILED (remote: not allow)
finished. total time: 0.001s
Help please just getting fastboot usb on the htc splash screen, unable to physically get into the phone to make any dev setting changes.
Extracted AndroidSDK downloaded google usb driver, manually changed driver from HTC Bootloader to Google USB driver now showing as 'Android 1.0'
Tried 'via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors'
http://forum.xda-developers.com/showthread.php?t=561124
C:\AndroidSDK\platform-tools>adb shell reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Also tried
C:\AndroidSDK\tools>fastboot flash recovery cm-hero-recovery.img
sending 'recovery' (3972 KB)...
FAILED (remote: not allow)
finished. total time: 0.002s
Sorted
wasnt holding down the home key long enough after reboot to get into recovery
back on android 2.3.5
yeah it's pretty helpful to have a s-off bootloader. just in case something gets really fubar
Hello guys,
Frank is writing. Sorry for disturbing, but i´m in big trouble right now. I made a Factory reset, wipe Dalvik etc. and flashed the PA Aosp Mako 4.0 + latest Gapps.. Nothing special so far, but now my Nexus is still in a bootloop. If i go to the recovery mode, i have no access to TWRP just have the possibility to choose between Start, Start bootloader, Power off, or Recovery Mode. But if i go to the recovery mode the bugdroid is there and nothing happens further. After connecting the device to my mac there is a message on the screen that it´s in download mode?! i didn´t seen this before.. So if you have any solution, it would be great. a factory reset to if possible or even necessary.
Right now I am at my wits end. May someone has an advice for me what to do? i can´t imagine christmas without my beloved smartphone.. ;(
Thanks for your attention!
cheers
Frank
You need fastboot working on your computer, not sure of the exact steps for a mac, but if you download the Android SDK it will be in there. Then you can directly flash a factory image for your phone from the fastboot screen. (The one you describe with start, start bootloader, etc)
You can download the factory images here https://developers.google.com/android/nexus/images#occam
Android sdk for mac http://dl.google.com/android/android-sdk_r22.3-macosx.zip
hey.. thank you for your reply. i downloaded the required files but how to get the access with terminal when it´s still not possible to start the phone? If i type in ./adb devices in terminal just following popped up but nothimg else:
-bash: /Users/frankherrmann/Desktop/adt-bundle-mac-x86_64-20131030: is a directory
do u know what to do now?
At the dead android screen, hold the power button and press vol+. Does it get you to stock recovery?
unfortunately nothing happens the screen turns off, that´s all... ;(
You should try flashing a stock 4.4.2 occam image using fastboot. This would return you to stock and you can then root and install TWRP or CWM.
endxpen tyrants
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image. but anyway, it seems that i can´t get the access to the phone. if i go in the adt folder and use the command adb services in the terminal my device will not be recognized.
Frank-iMac:adt-bundle-mac frankherrmann$ ./adb devices
List of devices attached
Frank-iMac:adt-bundle-mac frankherrmann$
Do i type in something wrong? maybe it´s just a thinking error by myself
thanks againfor your help!
FrankHPunkt said:
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image and put it in the same folder that i named as adroid tools. i got the access to the folder and after type in the command ./fastboot devices my devices has been recognized and the number too. but if i try to flash the stock image it will not work. i typed in ./fastboot flash and the image name but the failure message -bash: ./flash: No such file or directory
so... i suggest that it´s been just a problem that i typed not the correct command, isn´it?
Franks-MacBook-Pro:Android Tools leherman$ ./fastboot flash /Users/leherman/Desktop/android\ tools/image-occam-kot49h.zip
unknown partition '/Users/leherman/Desktop/android tools/image-occam-kot49h.zip'
error: cannot determine image filename for '/Users/leherman/Desktop/android tools/image-occam-kot49h.zip'
Franks-MacBook-Pro:Android Tools leherman$
Click to expand...
Click to collapse
Sorry, I can't help you with flashing on Mac. Do you have access to a PC?
FrankHPunkt said:
FrankHPunkt said:
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image and put it in the same folder that i named as adroid tools. i got the access to the folder and after type in the command ./fastboot devices my devices has been recognized and the number too. but if i try to flash the stock image it will not work. i typed in ./fastboot flash and the image name but the failure message -bash: ./flash: No such file or directory
so... i suggest that it´s been just a problem that i typed not the correct command, isn´it?
Click to expand...
Click to collapse
Yes you got 2 options,run the flash-all script or flash the files manually for example typing fastboot flash recovery recovery.img or fastboot flash radio radio.img, you didn't specified the partition to flash
Click to expand...
Click to collapse
Hey Frederico,
thanks for your reply i did it as you told me and typed this in terminal : as you can see something should work, but it was not possible to flash the image.
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash radio-mako-m9615a-cefwmazm-2.0.1700.98.img radio-mako-m9615a-cefwmazm-2.0.1700.98.img
sending 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img' (45537 KB)...
OKAY [ 1.715s]
writing 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.718s
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash image-occam-kot49h.zip image-occam-kot49h.zip
sending 'image-occam-kot49h.zip' (429746 KB)...
OKAY [ 15.845s]
writing 'image-occam-kot49h.zip'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.848s
do u have an idea whats still not right. Seems to be on the right way!
thank you very much so far!
Federico_96 said:
FrankHPunkt said:
Yes you got 2 options,run the flash-all script or flash the files manually for example typing fastboot flash recovery recovery.img or fastboot flash radio radio.img, you didn't specified the partition to flash
Click to expand...
Click to collapse
Click to expand...
Click to collapse
FrankHPunkt said:
Hey Frederico,
thanks for your reply i did it as you told me and typed this in terminal : as you can see something should work, but it was not possible to flash the image.
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash radio-mako-m9615a-cefwmazm-2.0.1700.98.img radio-mako-m9615a-cefwmazm-2.0.1700.98.img
sending 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img' (45537 KB)...
OKAY [ 1.715s]
writing 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.718s
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash image-occam-kot49h.zip image-occam-kot49h.zip
sending 'image-occam-kot49h.zip' (429746 KB)...
OKAY [ 15.845s]
writing 'image-occam-kot49h.zip'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.848s
do u have an idea whats still not right. Seems to be on the right way!
thank you very much so far!
Click to expand...
Click to collapse
The right command is ./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.98.img, so it is ./fastboot flash <generic name of partition> <exact name of the file> hope this will work, but my suggestion is to run the flash-all script,it will do it authomatically for you, if you want do it manually,here at step D there are all the commands
Thanks a lot, you made may day! the phone is rebooting....
merry christmas!
cheers
Frank
First of all, I would like to apologize if this question has been answered in another thread. I have searched the xda forums and others with no success.
My situation is the following:
Running on Windows 8.1
1. Rooted Nexus 4 on 4.4 (if I remember correctly)
2. OTA update to 4.4.2 (loosing root, but device remains unlocked) (I think I also tried flashing the factory image manually, but failed, I don't remember exactly)
I rooted my phone when Kitkat was fresh and found there were no custom roms on 4.4 yet so I went back to stock because it was the easiest way to get the update. Right now I can not flash a custom recovery.
fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s
===================================================
fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
This is the same for both TWRP and CWM. I am very sure I did NOT misspell the name.
Does anyone have any idea why this is happening and how to fix it?
Thank you for taking the time to read this post!
You have to use this
fastboot flash recovery recovery.img
wrong syntax, must be: fastboot flash recovery recovery.img
Wow.... I am ashamed with myself. I cannot believing I missed that.
Thank you for the quick reply guys.
I was just doing the same here thanks!
command doesnt work for me
jd1639 said:
You have to use this
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
FastSl0th said:
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
Click to expand...
Click to collapse
In the xda forum, check carefully whether you are asking a question in the appropriate Q&A section for your device, because you are certainly not writing about Nexus 4.
.
FastSl0th said:
command doesnt work for me
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
Click to expand...
Click to collapse
Hopefully you may have already asked or solved this question. I am assuming you are issuing command from platform-tools folder. If you have a Windows 10 OS system then, I too could not found USB drivers for my system with windows 10. If 'fastboot devices' command returning some device id then maybe I have guessed wrong reason.
I entered "fastboot flash XXX.img" Too. hahaha
After i see this article, I entered "fastboot flash recovery flash XXX.img"
Thank you anyway.
unsolved
dan60 said:
unsolved
Click to expand...
Click to collapse
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How To Solve This Problem Brother..Please Tell me
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How to Solve This Problem Brother...Please Tell Me
d4_daman_ said:
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How to Solve This Problem Brother...Please Tell Me
Click to expand...
Click to collapse
Hi there!
It didn't work for me but you can try it >>>
jd1639 said:
You have to use this
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Hi guys, I found the same error when I've tried to install TWRP on mi Xiaomi Mi A3 by FASTBOOT on Linux Terminal.
After a lot of searching, I solved my problem using the syntax below:
"fastboot flash boot XXX.img"
"boot" is the partition about FASTBOOT are asking for.
Hope to be usefull.
Device is unlocked (A2017G)
Tried flashing twrp/root using axon7toolkit(version 1.2.0)
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Can anybody help with this?
still_living said:
Device is unlocked (A2017G)
Tried flashing twrp/root using axon7toolkit(version 1.2.0)
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Can anybody help with this?
Click to expand...
Click to collapse
edit: whatever, i'll let bkores help you with this
still_living said:
Device is unlocked (A2017G)
Tried flashing twrp/root using axon7toolkit(version 1.2.0)
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Can anybody help with this?
Click to expand...
Click to collapse
Do this in command prompt and tell me the output:
Code:
cd C:\Axon7Development\Axon7Toolkit
fastboot flash recovery twrp\twrp-3.1.1-0-ailsa_ii.img
Also failed
bkores said:
Do this in command prompt and tell me the output:
Code:
cd C:\Axon7Development\Axon7Toolkit
fastboot flash recovery twrp\twrp-3.1.1-0-ailsa_ii.img
Click to expand...
Click to collapse
This is what I got.
C:\Axon7Development\Axon7Toolkit>fastboot flash recovery twrp\twrp-3.1.1-0-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (14452 KB)...
OKAY [ 0.362s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.383s
Hi sorry i am kinda new to this type of stuff, i succesfully installed and rooted only one other phone before
So the problem im having is when i go to flash a recovery.img it fails, here is the copy and pasted stuff from the ADB
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
LGH872be734bc5 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery_h872_20180812.img
target reported max download size of 536870912 bytes
sending 'recovery' (25828 KB)...
OKAY [ 0.600s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.620s
C:\Program Files (x86)\Minimal ADB and Fastboot>
EDIT: i should mention i tried multiple .img files]
Did you unlock bootloader on your device first?
Montechristo said:
Did you unlock bootloader on your device first?
Click to expand...
Click to collapse
i did indeed buddy. Primed and ready haha
Gr8. USB debugging and Enable OEM unlock on?
Montechristo said:
Gr8. USB debugging and Enable OEM unlock on?
Click to expand...
Click to collapse
yeah mate. all done. it just wont flash
Is your device already rooted?
try the recovery from here :https://forum.xda-developers.com/lg-g6/development/twrp-t3828254
I had similar problem on H870 with official TWRP and notice: for root take magisk and not "super su"otherwise there are problems
Bunsenbrenner said:
try the recovery from here :https://forum.xda-developers.com/lg-g6/development/twrp-t3828254
I had similar problem on H870 with official TWRP and notice: for root take magisk and not "super su"otherwise there are problems
Click to expand...
Click to collapse
I will update you as soon as I reach my PC. Thanks bud. Hopefully works for me
Bunsenbrenner said:
try the recovery from here :https://forum.xda-developers.com/lg-g6/development/twrp-t3828254
I had similar problem on H870 with official TWRP and notice: for root take magisk and not "super su"otherwise there are problems
Click to expand...
Click to collapse
Hi dude, this was where i tried from before. only got a chance to check now, these do not work.