Database Users

[q] cant flash recovery??

Hello im very new to this rooting and roming and i have no idea why i cant or wont let me do flash recovery im using fastboot
heres what comes up when trying:
sending 'recovery' <1250 KB>...
FAILED <remote: not allow>
finished. total time: 0.016s
i push volume down and power after turning off phone
this is what i see:
Click PVT Ship S-ON
HBOOT-0.52.0001 (CLIC10000)
MICROP-0203
RADIO-3. 35. 07 . 20
Sep 22 2009, 14:40:39
i followed what it says to go about fastboot but nothing worked
is there anyway i could fix to work????
thanks

look here.
http://forum.xda-developers.com/showthread.php?t=950759
firstly install htc sync, to have driver. Then enable usb debugging mode.

You can download CWM 5.0.2.0 recovery img and put that downloaded file to your SD card, run Terminal emulator for your phone and install it manually.
Commands for Terminal Emulator said:
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Notice: You need to have su and flash_image files on your SD card before doing anything. (Root required)

[GUIDE] How To Root HBOOT 1.02/1.07 and gain S-OFF

I am in no way responsible if you turn your phone into an expensive brick. Unlocking bootloaders is technical, and can be hazardous to your devices health if you don’t understand what you are doing.
REQUIRED: ADB, fastboot, and all related drivers setup and working on your pc. If you do not have adb setup download this http://dinc.does-it.net/Guide_Root_New_Hboot/adb_fastboot.zip, and extract the files to some place like C:\adb and also download these required drivers http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install.
1. Head over to HTC Dev http://www.htcdev.com/bootloader/.
2. Create a account or sign in (you must use your real email address).
3. Go to unlock bootloader.
4. Select “HTC DROID INCREDIBLE*”.
5. Follow the directions and install all the software provided and you will end up with a unlocked bootloader with s-on. Save a copy of the unlock_code.bin to your pc, so you have it after dooing the froyo ruu.
6. Enter FASTBOOT again on your phone.
7.Open the command prompt again on your pc to where adb.exe is. (ie. C:\android-sdk\platform-tools or C:\adb
8. Download this - CWM recovery 5.0.2.0 http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, and place it in the same folder as fastboot (where you put unlock_code.bin ie. C:\adb).
9. For simplicity’s sake rename the above file to recovery.img if it doesn’t already save it as recovery.img.
10. In your command prompt navigate to the folder containing your fastboot files and recovery.img
11. Enter the following in the command prompt:
Code:
fastboot flash recovery recovery.img
Code:
12. Once that completes navigate to recovery on your phone and press power to select it.
13. Once CWM recovery boots on your phone use the volume up and down to pick "Mounts and storage" press the trackball to select it.
14. Select "Mount usb storage".
15. Take this zip and drag it to the root of your SD card http://dinc.does-it.net/Guide_Root_New_Hboot/su.zip
16. On your phone press the trackball to unmount your usb storage.
17. Select go back.
18. Select install zip from SD card.
19. Choose zip from sd card.
20. Select the su.zip file we just downloaded and press the trackball to flash.
21. Reboot the phone.
22. Once your phone is booted go to the market and search "superuser".
23. Download and install superuser.
24. Search "busybox".
25. Use one of the busybox installers and install busybox (hit allow on the su notification).
26. Enter superuser app, press the menu button on your phone, select preferences, then scroll down to su-binary.
27. Hit update, and allow the prompt, if all the output is in green then you have full root congrats!!!.
For Those who wish to take it one step further and achieve s-off with unrevoked.
This process will format your phone I recommend making a nandroid, and running a program like Titanium Backup along with MyBackup to backup all your apps/data, and sync your contacts to google before you go any further.
28. Reboot your phone, and enable usb debugging.
29. Place these 2 files, unzipped on the root of your SD card. Do not put them in a folder, just drop the files right to your card. http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip
30. Set your phone to charge only.
31. Open the command prompt on your PC and navigate to the same folder as your fastboot files in the step above for example: cd c:\android-sdk\platform-tools\ or C:\adb
32. Type the following into the command prompt pressing the enter key at the end of each line:
Code:
adb shell
You should get a dollar sign $
Code:
su
You should now get a pound sign #
Code:
cat /sdcard/flash_image > /data/flash_image
Code:
chmod 755 /data/flash_image
Code:
/data/flash_image misc /sdcard/mtd0.img
33. Now set your phone to disk drive mode and place this zip on the root of your SD card (do not unzip) http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip
34. Rename the above file to PB31IMG
35. Set your phone to charge only
36. At this step you have 2 options you can pull the battery of your phone and put it back in then hold volume down and pres power to enter the bootloader or you can go back to your command prompt and type the following:
Code:
exit
Code:
adb reboot bootloader
37. When your bootloader is done loading press volume up to flash the PB31IMG.zip
38. Your phone will reboot the bootloader once during this process, don’t be alarmed just wait for it to finish, when done it will ask you to press volume up to restart the phone
39. When done remove the PB31IMG file from your sd card
40. Congratulations you are now back to stock 2.2 froyo
41. Put the unlock_code.bin file in the same folder with the fastboote.exe file if its not already there. Go to fastboot on the phone. Open a commant prompt to the folder where the files are.
42. Type the folowing:
Code:
fastboot flash unlocktoken unlock_code.bin
Code:
43. Fastboot flash cwm recovery.img again.
Code:
fastboot flash recovery recovery.img
Code.
44. Flash the su.zip file thru recovery.
45. Flash the unrevoked forever s-off patch thru recovery http://dinc.does-it.net/Guide_Root_New_Hboot/unrevoked-forever.zip
You should now be rooted and s-off.

Reserved

do you know if this method enables fastboot? I never could get fastboot working on my slcd Inc and I don't know if there is an eng hboot that works for it.
Sent from my Galaxy Nexus using Tapatalk

tiny4579 said:
do you know if this method enables fastboot? I never could get fastboot working on my slcd Inc and I don't know if there is an eng hboot that works for it.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I believe it does. The new hboot is fastboot compatible, it is required to get the info for the unlock code. The 0.92 hboot is also fastboot compatible, i have always been able to use fastboot on it. Is that what you ment?

cmlusco said:
I believe it does. The new hboot is fastboot compatible, it is required to get the info for the unlock code. The 0.92 hboot is also fastboot compatible, i have always been able to use fastboot on it. Is that what you ment?
Click to expand...
Click to collapse
is there a reason why update hboot? any thing good come with it?

synisterwolf said:
is there a reason why update hboot? any thing good come with it?
Click to expand...
Click to collapse
No reason to update and is reccomended that you dont. This is just for people who got an inc recently that came with the new hboot.

cmlusco said:
I believe it does. The new hboot is fastboot compatible, it is required to get the info for the unlock code. The 0.92 hboot is also fastboot compatible, i have always been able to use fastboot on it. Is that what you ment?
Click to expand...
Click to collapse
I can use fastboot but I mean commands like fastboot flash and fastboot boot never worked for me. They should as I'm s-off but my conclusion is that the current boot loader doesn't allow fastboot to flash to a device.
I want it mainly to boot a boot.img without having to flash to the boot partition. Good for testing purposes.
Sent from my Galaxy Nexus using Tapatalk

cmlusco said:
No reason to update and is reccomended that you dont. This is just for people who got an inc recently that came with the new hboot.
Click to expand...
Click to collapse
thank you.

tiny4579 said:
I can use fastboot but I mean commands like fastboot flash and fastboot boot never worked for me. They should as I'm s-off but my conclusion is that the current boot loader doesn't allow fastboot to flash to a device.
I want it mainly to boot a boot.img without having to flash to the boot partition. Good for testing purposes.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I know the fastboot flash works for recovery and misc img, not sure about boot. I wrote this thread after helping my cousin root his inc with the new hboot that was ***locked*** (oow) s-on. After doing htc dev unlock, it did allow us to use fasboot to flash the cwm recovery img and the misc partition, and allow him to downgrade to 2.2. Then used unrevoked like normal to get s-off. He is now true s-off while still being on the new hboot. Now it says ***unlocked*** (oow) s-off.

cmlusco said:
I know the fastboot flash works for recovery and misc img, not sure about boot. I wrote this thread after helping my cousin root his inc with the new hboot that was ***locked*** (oow) s-on. After doing htc dev unlock, it did allow us to use fasboot to flash the cwm recovery img and the misc partition, and allow him to downgrade to 2.2. Then used unrevoked like normal to get s-off. He is now true s-off while still being on the new hboot. Now it says ***unlocked*** (oow) s-off.
Click to expand...
Click to collapse
To test you can dump the current boot.img or pull one from a nandroid to your pc and do fastboot flash boot boot.img. I'm just curious if that works for you as I couldn't do it but I might try again this evening.
Sent from my Galaxy Nexus using Tapatalk
Edit: Here is what I tried and it shows that fastboot boot fails for me:
Code:
D:\Users\Andrew\Desktop\droid>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.470s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.480s
D:\Users\Andrew\Desktop\droid>fastboot flash boot boot.img
sending 'boot' (3072 KB)...
OKAY [ 0.470s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.470s
D:\Users\Andrew\Desktop\droid>fastboot flash recovery recovery.img
sending 'recovery' (4608 KB)...
OKAY [ 0.698s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.700s

tiny4579 said:
To test you can dump the current boot.img or pull one from a nandroid to your pc and do fastboot flash boot boot.img. I'm just curious if that works for you as I couldn't do it but I might try again this evening.
Sent from my Galaxy Nexus using Tapatalk
Edit: Here is what I tried and it shows that fastboot boot fails for me:
Code:
D:\Users\Andrew\Desktop\droid>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.470s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.480s
D:\Users\Andrew\Desktop\droid>fastboot flash boot boot.img
sending 'boot' (3072 KB)...
OKAY [ 0.470s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.470s
D:\Users\Andrew\Desktop\droid>fastboot flash recovery recovery.img
sending 'recovery' (4608 KB)...
OKAY [ 0.698s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.700s
Click to expand...
Click to collapse
Yeah it does the same thing on mine 0.92 remote not allowed. I will check on my cousins phone next time i see him, and see if the new hboot can do it.

congrats on making it to the portal
http://www.xda-developers.com/android/root-and-s-off-for-the-htc-incredible-with-hboot-1-02-0000/

synisterwolf said:
congrats on making it to the portal
http://www.xda-developers.com/android/root-and-s-off-for-the-htc-incredible-with-hboot-1-02-0000/
Click to expand...
Click to collapse
Holy crap lol. I had no idea, thanks for telling me.

cmlusco said:
Holy crap lol. I had no idea, thanks for telling me.
Click to expand...
Click to collapse
your welcome.

When I try to run unrevoked for root and s-off it fails with Internal error: failed to unlock NAND flash?
I have no idea where to go from here anyone have advice?
Edit: I have run everything else in the guide successfully. I am downgraded to 2.2.

warpurlgis said:
When I try to run unrevoked for root and s-off it fails with Internal error: failed to unlock NAND flash?
I have no idea where to go from here anyone have advice?
Edit: I have run everything else in the guide successfully. I am downgraded to 2.2.
Click to expand...
Click to collapse
What version of unrevoked did you use 3.32, you should use version 3.22 http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe. Also make sure to go to the unrevoked menu and select custom recovery, and use this cwm img http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img before starting the process.

I did use 3.32 first. Then I decided to try 3.22.
I just read your post about using to custom recovery image and I just tried that with 3.22 unsuccessfully with a Failed to flash recovery image.

Can you access recovery, and when booted do you have root?

I can access the HTC recovery if that is what you mean. I lost root when I did the downgrade from 2.3.4 to 2.2

warpurlgis said:
I can access the HTC recovery if that is what you mean. I lost root when I did the downgrade from 2.3.4 to 2.2
Click to expand...
Click to collapse
Try flashing cwm with fastboot like in step 11. Then if you can access it flash the su binary, boot, install su app and busybox, and then try unrevoked again.

Hboot 1.02.000 Root/Cwm recovery help

so i unlocked my bootloader using the htcdev guide. this updated my hboot to 1.02.000 and when i try to flash CWM i get this error.
Code:
sending 'recovery' (1685 KB)... OKAY
writing 'recovery'... FAILED (remote: image error! (BootMagic check fail))

The Usual Suspect said:
so i unlocked my bootloader using the htcdev guide. this updated my hboot to 1.02.000 and when i try to flash CWM i get this error.
Code:
sending 'recovery' (1685 KB)... OKAY
writing 'recovery'... FAILED (remote: image error! (BootMagic check fail))
Click to expand...
Click to collapse
how (which method) are you trying to flash the recovery?

Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(boot.img can be found in ur stock ruu )
Type fastboot flash recovery 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.

help needed.
hey der. i have rooted my phone with s-on. but i am facing the same problem as i cannot boot in cwm recovery mode and hence cannot install a custom rom. i am no developer. so please can you elaborate your above method step by step. sorry i am a noob here.
thanx anywayz

Have you managed to install cwm?

HTC Magic - half bricked - RUU USB

Hello,
can anyone suggest how to recover HTC magic after flashing Rogers RUU official over custom rom.
ROM update was aborted on updating system partition.
Problem is that I can't upload any part of rom because phone is now S-ON. I'am getting signature error.
Flashed RUU: 42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP format]
ADB is no longer possible. Only FASTBOOT and RUU USB.
See attched photo for fastboot details.
Thanks in advance.

pero256 said:
Hello,
can anyone suggest how to recover HTC magic after flashing Rogers RUU official over custom rom.
ROM update was aborted on updating system partition.
Problem is that I can't upload any part of rom because phone is now S-ON. I'am getting signature error.
Flashed RUU: 42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP format]
ADB is no longer possible. Only FASTBOOT and RUU USB.
See attched photo for fastboot details.
Thanks in advance.
Click to expand...
Click to collapse
I went through a similar problem. My 32A was in the same state except for the radio; I had no system installed, S-ON, RUU mode, and a radio/spl mismatch. It looks like you at least have a proper radio/spl combo.
Before we do anything else, try flashing the RUU again. Were you using the ZIP file or the EXE? Use the ZIP, at least you won't have to load up that crappy HTC interface.
If the RUU fails again, see if you can find the log file from the installation. It'll be on your system's drive, probably in "C:\ruu_log" or something like that. It can tell us what error it found.
In my case, we (mumilover and I) had to upgrade HBOOT and "sort of unlock it" using HTCDEV's method. Then we were able to install a custom recovery, and then everything got very easy.
Let's see if the simple things work before we have to do the harder things

Thnak you very much for hint with HTCDEV. Now I have at least fastboot
RUU image allways fail at signature error. OI have tried three of them. Same error.
I have run RUU under fastboot usb.
Also I can't flash recovery image even I have successfully unlocked hboot with htcdev.
C:\ADB>fastboot flash recovery recovery-clockwork-2.5.0.7-magic.img
sending 'recovery' (2642 KB)... OKAY [ 0.923s]
writing 'recovery'... FAILED (remote: not allow)
finished. total time: 0.926s
Any other idea ?

pero256 said:
Thnak you very much for hint with HTCDEV. Now I have at least fastboot
RUU image allways fail at signature error. OI have tried three of them. Same error.
I have run RUU under fastboot usb.
Also I can't flash recovery image even I have successfully unlocked hboot with htcdev.
C:\ADB>fastboot flash recovery recovery-clockwork-2.5.0.7-magic.img
sending 'recovery' (2642 KB)... OKAY [ 0.923s]
writing 'recovery'... FAILED (remote: not allow)
finished. total time: 0.926s
Any other idea ?
Click to expand...
Click to collapse
Could you give me the new details of the fastboot page? Your HBOOT version will have changed, and it will say "UNLOCKED" or "RELOCKED" at the top and S-ON. If it says "RELOCKED", try running the HTCDEV unlock command from fastboot again (you should still have the Unlock_code.bin file in your email) and then reboot.
Let's see how that goes.

DasBub said:
Could you give me the new details of the fastboot page? Your HBOOT version will have changed, and it will say "UNLOCKED" or "RELOCKED" at the top and S-ON. If it says "RELOCKED", try running the HTCDEV unlock command from fastboot again (you should still have the Unlock_code.bin file in your email) and then reboot.
Let's see how that goes.
Click to expand...
Click to collapse
I have attached Fastboot details.Status is: UNLOCKED.
But when I try to flash recovery I get an error message which I already wrote.
I think it is because of S-ON which is checking signature.

pero256 said:
I have attached Fastboot details.Status is: UNLOCKED.
But when I try to flash recovery I get an error message which I already wrote.
I think it is because of S-ON which is checking signature.
Click to expand...
Click to collapse
Sounds reasonable. I wish I kept better notes That way I wouldn't have to re-learn things every time.
I just want to make sure I understand the timeline of events:
You said you tried to flash an RUU over an existing custom ROM install, right?
What was the configuration of your phone before you tried the RUU and ran into trouble? If you were running a custom ROM, did you have a magic SPL or a custom recovery in order to install that custom ROM?
Anyway, on to the work:
Let's see if we can get an RUU to work now.
Go to the command prompt and run "fastboot getvar version-main" and let us know what it is, for future reference.
Once we know that, we can find a higher-numbered RUU from this list of Official RUUs.
I think I ended up using BrightStar Brazil, but anything higher than your phone's reported main version should work.
Have you made a goldcard? If you try to use an RUU and it complains about your CID, this will help.
Before you try to install an RUU, you will need to relock the bootloader using "fastboot oem lock" (you'll be able to unlock it again using the Unlock_token.bin)
Place the SAPPIMG.zip of the RUU in the root folder of your SD card and reboot into HBOOT (or reboot to fastboot and select HBOOT).
After a few seconds it should start scanning your SD card and then it will try to use the SAPPIMG.
Let us know.

Yes I had custom rom with s-off. But can't remeber which version.
Than I tried to install RUU: 42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP format]
Than I get error while flashing.
Strange thing is that I get this now:
C:\ADB>fastboot getvar version-main
version-main: 3.54.0.0
finished. total time: 0.001s
So it seems that I have lower version than I tried to install
I didn't try to use goldcard for now.

I have created Gold Card using this link: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
I have to use another HTC phone (Wildfire) to get CID from HTC Magic SD card
I have tried to put 3.54.631.3 Rogers Canada rom as SAPPIMG.zip but HBOOT claims that there is no image.
I get: Loading...(SAPPIMG.zip) No image!

I forget to say that I have set HBOOT to RELOCKED state before using GOLD CARD and SAPPIMG.zip

pero256 said:
I forget to say that I have set HBOOT to RELOCKED state before using GOLD CARD and SAPPIMG.zip
Click to expand...
Click to collapse
1) Check the filename. Make sure it is "SAPPIMG.zip" exactly, with SAPPIMG in capital letters.
2) Run these fastboot commands and then switch back to HBOOT mode.
Code:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
This procedure has fixed SD card problems in the past.
3) Check the SD card using a computer or another phone to be sure that the file is on the card. I've had Windows unmount the card improperly a few times, so that's a possibility.
4) Compare a checksum of the original ZIP file to the checksum of the ZIP on your SD card. I use 7-Zip to get the checksum, but there are other ways.
5) You can download another copy of the SAPPIMG.zip file.
It also helps to wave a dead chicken over the phone as an offering to the phone god.

Unfortuntly can't get goldcard to work.
I have used 3 different SD card.
1. 2GB
2. 2GB
3. 1GB
Non of them works.
Also everything is fine in the process of creating them.
Problem is about loading to phone SAPPIMG.zip of 3.54.631.3 Rogers Canada rom.
Phone starts to Checking..(SAPPIMG.zip) and then after some period of time stops and waits to press:
1. (back) FastBoot Mode
2. (send) Simlock
I have try to start another flash but get the same result.
So it seems that the gold card is not working as it should because phone is still checking uploaded rom image.

Is there some SD card that works 100% ?

pero256 said:
你好，
任何人都可以建议如何在通过自定义 rom 刷新 Rogers RUU 官方后恢复 HTC 魔法。
ROM 更新在更新系统分区时中止。
问题是我无法上传 rom 的任何部分，因为手机现在是 S-ON。我收到签名错误。
闪烁的 RUU：42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP 格式]
亚行不再可能。只有 FASTBOOT 和 RUU USB。
有关快速启动的详细信息，请参阅随附的照片。
提前致谢。
Click to expand...
Click to collapse
You use what method to let it enter FASTBOOT

[Q] Bootloop after flashing, TWRP not available..

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