Database Develop

Cant flash anything on a DEV G1!

Hello all.... I am working on a group project where we will be using a dev G1. The phone was shipped to a another group member and before I can get my hands on it, he decided to upgrade the firmware from 1.0 to 1.6, having very little knowledge of android beforehand and therefore he cant really tell me what exactly he did either. He followed the directions on the HTC website. As far as i can tell, I do have the 26I radio, engineering SPL and 1.6 installed currently, not sure about the recovery though (i.e. stock 1.0 or 1.6). When I got the phone, root access was gone but followed some simple steps on this website to regain it. By way of typing in "su" in terminal emulator and in ADB shell, I now also have su. However I still cant flash anything. When trying to flash cm 4.2.5 in the recovery, the system verifies it and then aborts installation. I then tried to install the Amon-RA recovery to no avail. Tried fastboot, ADP, terminal, im not sure how to access the /data/ partition on the phone and there is no option for acessing the console in the recovery menu. Installing through ADB dosnt work, no test-keys in current recovery. In fastboot it says "okay" for both sending and writing the recovery but rebooting into recovery shows that it didnt work. In terminal it says "flash_image: not found". I'm kinda lost and need some help....
All I need is cm4.2.5 on the phone with root.
Thanks in advance.....
Edit: I triple and quadruple checked the name of the recovery image when trying to install through terminal. I'm pretty sure it cant find the command "flash_image" and not the file itself. Just wanted to clarify...

You could try downgrading to RC29: http://wiki.cyanogenmod.com/index.p...ngrading_to_RC29_.28US.29_or_RC7_.28Europe.29

halr9000 said:
You could try downgrading to RC29: http://wiki.cyanogenmod.com/index.p...ngrading_to_RC29_.28US.29_or_RC7_.28Europe.29
Click to expand...
Click to collapse
Tried that, already... That method only works for the stock T-Mobile G1's which have a different SPL. The Dev G1's come with engineering SPL and I have no idea how to flash the .nbh image from that. All it does I think is enable Fastboot, I cant get it to do anything else.

This fails?
fastboot flash recovery recovery.img

Nope... No luck, it says:
sending 'recovery' <4456kb>.... OKAY
writing 'recovery' <4456kb>.... OKAY
and then I reboot using "fastboot reboot", wait till the homescreen loads, and then go back into recovery and it still shoes the the triangle and the !.....

Bump...
Anyone?? Right now we just have a reallly expensive paper-weight in our hands ANY help/thoughts/comments would be very appreciated...

This thread is meaningless since there is NO SUCH THING as a "DEV G1".
alilbitanuthin said:
Hello all.... I am working on a group project where we will be using a dev G1. The phone was shipped to a another group member and before I can get my hands on it, he decided to upgrade the firmware from 1.0 to 1.6, having very little knowledge of android beforehand and therefore he cant really tell me what exactly he did either. He followed the directions on the HTC website. As far as i can tell, I do have the 26I radio, engineering SPL and 1.6 installed currently, not sure about the recovery though (i.e. stock 1.0 or 1.6). When I got the phone, root access was gone but followed some simple steps on this website to regain it. By way of typing in "su" in terminal emulator and in ADB shell, I now also have su. However I still cant flash anything. When trying to flash cm 4.2.5 in the recovery, the system verifies it and then aborts installation. I then tried to install the Amon-RA recovery to no avail. Tried fastboot, ADP, terminal, im not sure how to access the /data/ partition on the phone and there is no option for acessing the console in the recovery menu. Installing through ADB dosnt work, no test-keys in current recovery. In fastboot it says "okay" for both sending and writing the recovery but rebooting into recovery shows that it didnt work. In terminal it says "flash_image: not found". I'm kinda lost and need some help....
All I need is cm4.2.5 on the phone with root.
Thanks in advance.....
Edit: I triple and quadruple checked the name of the recovery image when trying to install through terminal. I'm pretty sure it cant find the command "flash_image" and not the file itself. Just wanted to clarify...
Click to expand...
Click to collapse

Pretty sure there is...
http://developer.htc.com/adp.html

Bump...
anyone?

alilbitanuthin said:
Pretty sure there is...
http://developer.htc.com/adp.html
Click to expand...
Click to collapse
Do you see ANYTHING on there that says "G1"?
Answer: No you definitely do NOT.

If I remember correctly, after you use fastboot to flash the new recovery image, you can't let the phone reboot or it will overwrite the recovery with the stock recovery image
The solution would be to use fastboot to flash either Cyanogen's or Amon_RA's recovery image, and be quick here, but when you send the fastboot reboot command be holding down the home button on the phone so it will boot to the custom recovery image

lbcoder said:
Do you see ANYTHING on there that says "G1"?
Answer: No you definitely do NOT.
Click to expand...
Click to collapse
lol, no need to nitpick, about the name no less. Thats the least of my worries
As long as you get the message across...
jackslim said:
If I remember correctly, after you use fastboot to flash the new recovery image, you can't let the phone reboot or it will overwrite the recovery with the stock recovery image
The solution would be to use fastboot to flash either Cyanogen's or Amon_RA's recovery image, and be quick here, but when you send the fastboot reboot command be holding down the home button on the phone so it will boot to the custom recovery image
Click to expand...
Click to collapse
That maybe it I'll give it a try as soon as I get back home. Thanks a lot for the help!!

Thanks a lot jackslim, finally got it to work!

S-ON again after AlphaRevx instructions

For maybe some more like me that want to go back to what it use to be with the hboot S-OFF, S-ON issue.
I had my phone S-OFF with alpharevx beta. Used CM7 -stable for couple days but decided i wanted to go back to all original. I first RUU my phone with the RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe file. Boot it up, made sured it runs, then did what is instructed below here;
To be able to do this you need HTC USB drivers installed. Install the HTC pakage, reboot, uninstall the HTC-
Sync software, keep the drivers! reboot PC again.
Power off your phone. Plug in your USB cable to phone. Press volume down and powerup your phone. After it
settle navigate down and choose fastboot option.
1. Unpack these files to your c:\fastboot
2. Open up your windows command promt (WinVista/7 users rightclick choose run as Administrator)
3. in command promt type CD\ then press enter
4. then your should be in C:\
5. type cd fastboot
6. then you should now be in dir C:\fastboot
7. Im bored to death typing, look below. Beware of each command ends with enter. After success, reboot.
C:\fastboot>fastboot oem mb 9C068490 1 30
... OKAY
C:\fastboot>fastboot flash hboot hboot_buzz_7225_1.01.0001.nb0
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... OKAY
Files needed (Windows version): megaupload.com/?d=UO9L74I9
Works perfectly for me.
* NOTE: Im not responsible for your phone if you brick/kill it. These steps worked for me!

This should help a lot of people. Cheers for your post.

Tanks a lot man, this should be Sticky

can flash hboot-0.80.0008??????

I just have a question, ehm if i want to RUU my WF, do i have to follow the procedure you described in the first post Before or After using RUU***.exe?

gabryel48 said:
I just have a question, ehm if i want to RUU my WF, do i have to follow the procedure you described in the first post Before or After using RUU***.exe?
Click to expand...
Click to collapse
After is better to avoid potential problems with Custom Recoveries and ROMs. Which is precisely what the OP says as well.
I first RUU my phone with the RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed.exe file. Boot it up, made sured it runs, then did what is instructed below here;

I had to triple check what I typed out of fear of brick, but alas, it worked like a charm!
Small Edit: This method also works with AlphaRev X (version 0.2pre5) that they just released.

Is it possible to keep the root and to flash the stock hboot to get the s-on?

shiranmotha said:
Is it possible to keep the root and to flash the stock hboot to get the s-on?
Click to expand...
Click to collapse
Seems like no one tried it yet. For such a kind of thing, just after ruu, one should root the phone with superone click root method and then go for hboot flashing. But can't expect how the results will be. I think it will not brick since it is a fast boot flash. The possibility is the stock OS then becoming instable and unbootable. If so, just think there will not be alpharevx s-off option then, since it needs a full booted phone. And since there is no custom recovery, I think it becomes hard to make it normal (don't know if Su binary can be cleared from hboot menu through clear storage).
A better thing to try is retaining the custom recovery and flashing stock hboot. But still I can predict nothing. Ofcourse it might not brick the phone. But before doing anything, it is better to take the suggestion of the devs.
Sent from my HTC Wildfire using XDA App

ok im the frist to try relocked my hboot and keeping clockwork recovery it recovery still flashes roms wipes phone still boots and rooted but if i copy anything to system it it wont let me add anything if i do all the memory on system is droped
Sent from my Blade using XDA App

thank you very much it works!!!!!!!!!!!
alpharev x logo removed and again s-on ......thnx

Has anyone tried to flash 0.80?

can you please post hboot 1.01.0002 the latest one....

rickwyatt said:
ok im the frist to try relocked my hboot and keeping clockwork recovery it recovery still flashes roms wipes phone still boots and rooted but if i copy anything to system it it wont let me add anything if i do all the memory on system is droped
Sent from my Blade using XDA App
Click to expand...
Click to collapse
The S flag is there to prevent you from damaging your phone by messing around with its system partition when the phone is on, NOT when it is off or in recovery mode!!!

can you please post hboot 1.01.0002 the latest one....and also the stock recovery for froyo wildfire

Thanks so much for this..
Downgraded from AlphaRevX to hboot 0.80.007 this morning worked prefect. (hboot_7225_0.80.0007_100809.nb0)
Buzz PVT Ship S-ON
HBOOT -0.80.007
Aug 9 2010,22:37:43
This was done on a Telstra stock rom
RUU_Buzz_Froyo_Telstra_WWE_2.38.841.1_Radio_13.55.55.24H_3.35.20.10_release_167270
I ran the Rom throw Kitchen and removed all the Telstra Apps before for installing the Rom..

Fr3ddY303 said:
Downgraded from AlphaRevX to hboot 0.80.007 this morning worked prefect. (hboot_7225_0.80.0007_100809.nb0)
Buzz PVT Ship S-ON
HBOOT -0.80.007
Aug 9 2010,22:37:43
This was done on a Telstra stock rom
RUU_Buzz_Froyo_Telstra_WWE_2.38.841.1_Radio_13.55.55.24H_3.35.20.10_release_167270
Click to expand...
Click to collapse
How did you do that. What is the fastboot command for downgrading from alpharevx hboot to stock hboot 0.80
Sent from my HTC Wildfire using XDA App

bharatgaddameedi
I just used the fastboot commands that was listed.
C:\fastboot>fastboot oem mb 9C068490 1 30
C:\fastboot>fastboot flash hboot hboot_7225_0.80.0007_100809.nb0
Thanks to DeCex
From this thread http://forum.xda-developers.com/showthread.php?t=1160251
But if you try an use unrevoked v3.32 their is and error (version is to new)
So will try sometime today and go to hboot_7225_0.80.0004_100610.nb0

Fr3ddY303 said:
But if you try an use unrevoked v3.32 their is and error (version is to new)
So will try sometime today and go to hboot_7225_0.80.0004_100610.nb0
Click to expand...
Click to collapse
Use Unrevoked 3.14 - 3.21. It will work.

lex25288 said:
The S flag is there to prevent you from damaging your phone by messing around with its system partition when the phone is on, NOT when it is off or in recovery mode!!!
Click to expand...
Click to collapse
yea! I have tried the s-on hboot1.01 and 0.80 with DK ROM ^^
It works well =D

[Q] cannot root: hboot 2.0 ver. 2.3.5

Hello community!!
I'm new to the HTC/Incredible S world, I have a rooted/cfw LG P500 and now I bought this great phone. Problem is that I updated it to the last official version before this try.
So I went to the official site and I followed successfully the HTC site steps to unlock the bootloader (golden card?) and now I'm trying to follow the guide
http://forum.xda-developers.com/showthread.php?t=1385084
But I have some problems.
First of all clearly the revolutionary program doesn't work (HBOOT 2.0).
I booted to the bootloader (power+volume down) and I had the error "main version is older" then I copied on the SD card the file for the recovery PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip, I renamed it PG32IMG.zip, it loads it but when I press recovery it gives me an allert icon (the phone with a red triangle + red "!" ) and it does nothing.
I installed the SuperUser app like it is written in the post but when I type SU under the adb shell and it gives me "permission denied".
What could I do?
Is it even possible to downgrade it to a rootable/customable version?

If someone write a guide for rooting with the last update installed from original s-on step to step will be very util and a lot of people will be gratefull!
Inviato dal mio HTC Desire usando Tapatalk

Bootloader unlock and goldcard are 2 seperate things. Bootloader unlock is required at the moment for flashing recovery and superuser for rooting the phone.
Gold card is required for flashing another carriers rom.
Read this thread about recovery http://forum.xda-developers.com/showthread.php?t=1104765
After that you can enter recovery mode and flash a superuser zip file http://goo-inside.me/superuser/
My guide should be able to downgrade your rom and get s-off after that (if after researching you decide you require it) http://forum.xda-developers.com/showthread.php?t=1373697
Hope this helps

Thanks, I'm going to try this as soon as I can, I'll write back the results
edit:
It seems like I can't even pass the first step, the 4EXT Recovery Updater doesn't work, it crushes at EVERY menu item....
(I waited 5+minutes and I had the internet connection on).
I checked and the boot loader says "unlocked". Notice that my device is, of course, NOT rooted (at least for what I know for "rooted", it is still unlocked by the HTC official method)....

you need root to use the recovery updater.
download the recovery image and flash it in fastboot

Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...

sariel82 said:
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
Click to expand...
Click to collapse
Could I get a couple of screenshots to help with debugging please?

Sure, ASAP

Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.

edit:
It seems I cannot post the images, too noob ....
Anyway:
I had a photo of the phone in the custom recovery mode, another of the phone with the 4EXT recovery successfully flashing his recovery, another of the script of your post running with this message:
(no errors)
Do you have an unlocked bootloader from htcdev.com (I have)
y OR n:y
<waiting for device>
...
(bootloader) Lock successfully..
FAILED (status read failed (Too many links))
finished. total time: 0.239s
Note: run the RUU in fastboot mode
If all steps etc etc
Now if I try to run RUU NOT in fastboot mode I receive the message:
The Utility of ROM udating can't update the Android device.
Take a valid ROM updating Utility and try again
(I'm translating from Italian)
If I try to go to fastboot after running the script I need to go to hboot using volume down+power since you can go to fastboot only through bootloader and HIS first step is to check the bootloader file (am I right?)
so, since it is again LOCKED the custom boot file I was using PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed
doesn't work anymore and the old one neither so I have to unlock it again and it goes the loop......
So this is the situation, I hope I will be able to post some image soon...

sergiopat said:
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
Click to expand...
Click to collapse
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.

sariel82 said:
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
Click to expand...
Click to collapse
OK, I thought you only wanted to root.

Thank you anyway

You don't need s-off for CFW's, just the unlocked bootloader. I cannot help you any further until I see screenshots as I'm getting lost in your descriptions. Ctrl prtscrn, paste in paint.

Well, I have the screenshots but I can't post web links in the forum (new user).
Let's see if I can flash some cfw in the mean time

Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)

sariel82 said:
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
Click to expand...
Click to collapse
After you flash a custom ROM in recovery, you have one last step to do to prevent the hang. You extract the boot.img file from the ROM's zip file and then manually flash it in FASTBOOT mode on the phone:
FASTBOOT flash boot [path to boot.img]

That totally solved the problem
Thank you ALL!!!

sariel82 said:
That totally solved the problem
Thank you ALL!!!
Click to expand...
Click to collapse
Hi,
Please list the methods you use from the start. I have also 2.3.5 and hboot 2.0. cant manage to downgrade, i always getting an error.
Thanks

htc developer site -> unlock bootloader
find and download this file:
PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio _20.2810.30.085AU_3805.06.03.16_M_release_199684_s igned.zip
copy it on the sd card and renamto to pg32IMG.zip
reboot in power+volume down mode
go in fastboot
from your pc use fastboot to flash this recovery:
http://forum.xda-developers.com/showthread.php?t=1104765
copy to sd card the superuser file:
http://goo-inside.me/superuser/
enter recovery mode and flash the zip
Then if u want to flash a custom rom you dont need to downgrade, just copy the zip into the sd card, flash it, copy on the sd card the boot.img you find inside the rom zip file and reboot in fastboot (power+volume down)
FASTBOOT flash boot [path to boot.img]
and reboot and the job is done!

[Q] HTC Incredible S stuck in limbo :(

Well here's the story, someone gave me their phone to root (i'm the official rooter in my city ) and i accidently skipped over a major step, infact a few of them.
1: I unlocked the phone and flashed clockwork touch recovery
2: Did not backup the original non rooted rom
3: Did not S-off the phone
4: Flashed Android Revolution HD
Now No rom is working, IT gets stuck on the white HTC logo. At least tried 2-3 of them. Cyanogen and ARHD to start with. Tried a few RUU but those aren't going through too. Tried extracting rom.zip from the RUU and flashing manually but they dont work.
Attached is an image with the details of the Firmware on the phone and radio atm
I checked the HTC CID and it's 044 ... Any sort of help would be appreciated.

I feel bad for your city where did you get cwm touch recovery?
Have you flashed the boot.img in fastboot?

If flashing the boot doesn't work. Couldn't you just attempt to s-off through fast boot and flash the RUU etc?
Sent from my Incredible S using xda premium

I feel sorry for them too, now that i screwed up, for the first time though
Well my hboot version is 2.01 and it wasn't supported in revolutionary.io 's s-off method. Didnt think it would work any other way. I dont know how to downgrade it to 1.13.
I got my clockwork recovery from http://forum.xda-developers.com/showthread.php?p=14693680 this post. If only i can find the original rom/RUU which i can flash and just reset it to the original factory rom. :| i tried 3-4 of the RUU in the filefactory folder that's listed in the incredible s shipped rom section but none of them work.
Can i change the CID in teh android_info text file in the rom.zip of the RUU ? would that work ? apparently the zip is claimed to be corrupt when i try adding the same file back.

shani248 said:
I feel sorry for them too, now that i screwed up, for the first time though
Well my hboot version is 2.01 and it wasn't supported in revolutionary.io 's s-off method. Didnt think it would work any other way. I dont know how to downgrade it to 1.13.
I got my clockwork recovery from http://forum.xda-developers.com/showthread.php?p=14693680 this post. If only i can find the original rom/RUU which i can flash and just reset it to the original factory rom. :| i tried 3-4 of the RUU in the filefactory folder that's listed in the incredible s shipped rom section but none of them work.
Can i change the CID in teh android_info text file in the rom.zip of the RUU ? would that work ? apparently the zip is claimed to be corrupt when i try adding the same file back.
Click to expand...
Click to collapse
I'll ask again, have you flashed the boot.img in fastboot? The link you provided has no touch recovery in the OP or am I required to read all 29 pages?
If you're using cwm from the OP, you should update. Here's the newest version I know of http://www.clockworkmod.com/rommanager
To your question about flashing an ruu with a modified android_info on an s-on device: no.
You can find what ruu you need by entering the command
Code:
fastboot getvar version-main
the number returned corresponds to the ruu that you should be looking for.
As you are an experienced rooter you probably already know to wipe cache and usually data when you flash a new Rom.
@vizzy how would you gain s-off in fastboot mode?

HTC Incredible S/Vivo cwm-4.0.1.4-vivo.img
md5 : a556a81054cd8cfe623eed5f4b8e518b
this is hte file i posted from the link i shared before. Which exact boot.img are you talking about ?? Also most of my rootings were done with either unrevoked or alpharev which required minimal tweaking . I'm no pro, just try to give it my best
Also the version that the fasboot command gave me was 3.11.707.1. (thanks for that tip, i'll remember it). Going to search for it
Also how can i S-off in hboot or fasboot atm ??

shani248 said:
HTC Incredible S/Vivo cwm-4.0.1.4-vivo.img
md5 : a556a81054cd8cfe623eed5f4b8e518b
this is hte file i posted from the link i shared before. Which exact boot.img are you talking about ?? Also most of my rootings were done with either unrevoked or alpharev which required minimal tweaking . I'm no pro, just try to give it my best
Also the version that the fasboot command gave me was 3.11.707.1. (thanks for that tip, i'll remember it). Going to search for it
Also how can i S-off in hboot or fasboot atm ??
Click to expand...
Click to collapse
Because the phone is s-on, the way you need to flash a custom rom is as follows:
Install zip from sdcard in cwm, then extract the boot.img file from the zip file and flash it in fastboot I.e
Code:
fastboot flash boot boot.img
these steps are included in the newbs guide sticky

THANKS !!!
Nonverbose said:
Because the phone is s-on, the way you need to flash a custom rom is as follows:
Install zip from sdcard in cwm, then extract the boot.img file from the zip file and flash it in fastboot I.e
Code:
fastboot flash boot boot.img
these steps are included in the newbs guide sticky
Click to expand...
Click to collapse
You, sir, are a gentleman, and a hero. I salute you for your help. ! The phone is fixed ! I see what i did wrong there, and thanks alot for helping me with it. I learned something that was quite frankly logical.
Again, thanks !!!!

[Q] How can I reinstall a good image after flashing my boot with CWM?

My question is similar to 'nikpmr's troubles but different enough I think they deserve a separate post.
The Problem as Understood​I was trying to root my device following the guide at this website. It's so simple it's a wonder I messed up. I think my failure was that I thought the drivers installed when I connected the phone were enough so I skipped that step. Then when running fastboot flash recovery.img the install failed. So I saw on some forum that it was supposed to be fastboot flash boot recovery.img of course now I know if anything it ought to have been "recovery" not "boot".
What I've Tried & Partial Solution​At first I was just stuck in a boot loop and selecting "sideload" from the CWM recovery failed to allow me to connect with ADB or fastboot. i.e. Running "fastboot devices" and "adb devices" both returned as having no devices connected to my computer. So I installed the HTC Sync and promptly uninstalled the non driver parts of the app. Then I installed USBdeview and used it to uninstall all the USB devices associated with my HTC First. After doing that I learned booting into HBOOT allowed me to connect to the computer using fastboot and after then booting to the CWM Recovery I was able to connect using ADB to do a sideload. So I guess I'm about halfway there. Unfortunately after looking up the newest RUU and attempting to sideload it using "adb sideload OTA_MYST_UL_1.08.502.1-1.08.502.4.zip" the sideload failed. After selecting "- install zip from sideload" I get a message twice of "failed to open driver control: No such file or directory". It also failed when I attempted it with a similar fastboot command. So from all that I surmise my ROM is ruined and just needs to be replaced.
Question​So how do I go about replacing this ROM and boot partition? And, which ROM should I use? Is the one I got from the RUU site suitable? And what about the radio? I just need my phone to work. I can worry about rooting later. At this point I think I know what's happened but I don't know where to begin reading to figure out how to fix it myself.
Thanks for reading,
Relevant HBOOT text:
Code:
*** TAMPERED ***
*** UNLOCKED ***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:1682

1. you had to type in fastboot flash recovery recovery.img NOT fastboot flash boot recovery.img

Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload

abrahammmmmmm_ said:
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
Click to expand...
Click to collapse
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.

bnjo said:
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
Click to expand...
Click to collapse
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread

Success!
abrahammmmmmm_ said:
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Click to expand...
Click to collapse
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!

bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
Great! glad to hear I could help. Yes it's always nice knowing when something I've said has helped someone in any way

bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.

russian392 said:
usually after changing a kernel, it takes a while to boot cause...well you get it right?
Click to expand...
Click to collapse
Yes I get it.
russian392 said:
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
Click to expand...
Click to collapse
That's what I thought happened. If I had stopped to read the help on fastboot before running "fastboot flash boot recovery.img" I wouldn't have made that mistake because I would have seen I wanted to flash recovery. One thing I *did not* know, which I'm glad to know, was that the boot.img contains the kernal. I was thinking Android was more similar to IBM style PCs than it is and therefore the boot.img was analogous to a bootloader like grub or lilo.
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?

bnjo said:
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
in a nutshell yes, the boot.img uses the fstab
btw 10 posts you'll be "verified"

So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
Yep that's correct.
The name correlation is booting up requires kernel there for kernel is called beet.IMG
Thing about custom kernels, they aren't like that and simply contain modded files and pretty much an in packaged kernel.
Sent from my HTC first using xda app-developers app

stock recovery
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted

astrit1995 said:
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
Click to expand...
Click to collapse
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!

Serupo said:
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Click to expand...
Click to collapse
Thank you for your help,i solved my problem yesterday but i think im gona need this sometime...