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!

[Q] Milestone flashing recovery issue

Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.

tclayson said:
Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.
Click to expand...
Click to collapse
GOT recovery? You have a Milestone then? You are on the wrong path then. Clockwork Recovery Mod doesn't work on the Milestone, nor does ROM Manager.
You need to reflash the stock sbf for your country, then flash the rootable sbf, place OpenRecovery on your SD Card, and root the phone, flash a custom ROM and reboot. Look at the tutorials in the Milestone development forum and ask here if you have any other questions.

I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks

tclayson said:
I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks
Click to expand...
Click to collapse
It doesn't work, even though it shows it as supported. Because the bootloader is not unlocked on the Milestone, it will cause a soft brick. You will need to follow my instructions to get your Milestone running on MIUI again. The OTA update for MIUI works for devices with CWM installed, so it doesn't really work with Milestone. You'll need to manually update MIUI when DannyDroid posts the updates.

Ah gutted, ok thank you for that. I will follow your instructions. Thanks for clearing it up for me.

Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?

tclayson said:
Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?
Click to expand...
Click to collapse
People say that ROM Manager MIGHT work on Milestone. I don't think so and I wouldn't risk it just for OTA updates, seeing as the miuiAndroid build is very basic compared to the one Danny releases. Better to just wait for his releases, a lot more worthwhile!

Ok, well thank you very much! Restored to stock and gonna keep on top of danny's releases. Thanks skadude.

[Q] Want to go from CM7 to ICS, need some help

The last time I flashed a custom rom to my phone was CyanogenMod-7.1.0-RC1-N1.
I'd really like to get ICS on it, but the process seems just so much more confusing this time around. If anyone give me a breakdown of what I'd need to do, or even if they could just point me in the right direction, I'd be grateful.

i never messed with that as they are always a lil buggy i like sense better ^_^ try asking people in that thread im sure they be happy to help you bro
sorry i couldn't help

Mintyass said:
The last time I flashed a custom rom to my phone was CyanogenMod-7.1.0-RC1-N1.
I'd really like to get ICS on it, but the process seems just so much more confusing this time around. If anyone give me a breakdown of what I'd need to do, or even if they could just point me in the right direction, I'd be grateful.
Click to expand...
Click to collapse
There are at least 3 ICS ROMs with 2 are in the working progress and the other we don't know what is the status of it. Spend some time to read first to gain some knowledge and procedures. They are in the Development section of Nexus One. And, remember, once you have Ice Cream Sandwich you don't want to have Gingerbread

u can flash this miui ics as like anyother roms before
http://forum.xda-developers.com/showthread.php?t=1479348
but for other ics roms u need to partition /system. for that first u need to know abt blackrose.
http://forum.xda-developers.com/showthread.php?t=1270589
Sent from my Nexus One using Tapatalk

The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.

Jaiy said:
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Click to expand...
Click to collapse
Restore apps from GB backup might bring FC. It is better to download them from the Google Play

taodan said:
Restore apps from GB backup might bring FC. It is better to download them from the Google Play
Click to expand...
Click to collapse
While, in theory, you are correct, I restored my GB apps using TB because it is very fast to do so. In practice, they all appear to be working just fine. I believe I have run every one of them to make sure.
But I agree that a better general procedure would be to restore the apps themselves from the Play Store then restore your former app data using TB.

Jaiy said:
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Click to expand...
Click to collapse
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?

Mintyass said:
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Click to expand...
Click to collapse
The instructions are in the Blackrose thread in the Development section, you don't need to use the manual if you're using Windows.

I would read the blackrose thread so you understand what you are doing and why. Easier to get out of trouble and harder to get into it. You probably did same for CM7. The blackrose hboot is not easy to work with without knowing what you are doing. The backrose thread has pre requisites in OP, like install of drivers if you don't have them.
You guys sure the fastboot command for the exploit has the word "recovery" in it or should be:
fastboot boot go.lol
where go.lol is exact name of exploit from the actual blackrose binary folder depending what version of blackrose you are fastbooting. could be "fastboot boot go2.lol" etc
just a suggestion--

So I was able to use blackrose to repartition my system cache, but now I've got a problem. In the bootloader, when I select "Recovery" the phone hangs on the Nexus "X" logo, and I'm unable to get my phone to reboot into anything but the bootloader.

you probably lost recovery and need to re fastboot it
i once had to fastboot erase system before the recovery would flash
all these issues are in the thread

Would this be the correct thing to do? http://forum.xda-developers.com/wiki/HTC_Nexus_One/Recovery_Images

good info but if you have sdk and know fastboot do this
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it. Usually tools folder.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc
type fastboot devices (to make sure that fastboot "sees" your phone)
type fastboot flash recovery recovery-RA-passion-v2.2.1.img or whatever exact name your recovery is

I was able to get into recovery, but now when I select "Flash zip from sdcard", I get an error saying that there was No Signature and that the Verification Failed.

Mintyass said:
I was able to get into recovery, but now when I select "Flash zip from sdcard", I get an error saying that there was No Signature and that the Verification Failed.
Click to expand...
Click to collapse
You need to disable the signature verification in the recovery and then flash the ROM

Thanks so much for everyone's help! I've got ICS up and running now thanks to you.
Since this forum account is too new to post in the BCM thread, I guess I'll try asking a question here instead.
So far there's two problems I've encountered that would be dealbreakers for BCM. I saw on the BCM thread that voice search is currently broken, but it seems like it's kind of unexpected and will likely be fixed. The other issue I have, that I can't find anyone else complaining about, is that I don't seem to have the Car Home app anymore. Has anybody else run into this issue, or know a fix? I use my phone in my car pretty much every day in my car dock, and make extensive use of both the car home app and the voice search feature for getting navigation directions.
If there's a better place to post these questions, feel free to let me know!
Thanks

audio has been ab issue for me and others on ics and sense roms lately, don't know why. i am back on CM7 Kangs atm bc of it. hope it is found and fixed. the current remedies don't work for me
glad you are up and running, all these roms have issues of some type for a few at least. goes with the territory--
someone should be able to get you a car home apk you can install or push thru adb--i always delete mine as i don't use--sorry. might be able to find it thru search/google
posting here is perfectly fine--it a couple general threads for a "meaningful" post and you will be to ten real quick
enjoy rom
ken

Mintyass said:
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Click to expand...
Click to collapse
Sorry, I wasn't watching this thread over the weekend and I see you have already moved past this. But to answer the question...
I thought the pre-partitioned blackrose-220-10-206 was in that zip, but I see now that I found it on the Evervolv ROM thread in the Nexus One development forum. Sorry for not remembering to mention that.
---------- Post added at 12:08 PM ---------- Previous post was at 11:58 AM ----------
Mintyass said:
Thanks so much for everyone's help! I've got ICS up and running now thanks to you.
Click to expand...
Click to collapse
You're welcome.
So far there's two problems I've encountered that would be dealbreakers for BCM. I saw on the BCM thread that voice search is currently broken, but it seems like it's kind of unexpected and will likely be fixed. The other issue I have, that I can't find anyone else complaining about, is that I don't seem to have the Car Home app anymore. Has anybody else run into this issue, or know a fix? I use my phone in my car pretty much every day in my car dock, and make extensive use of both the car home app and the voice search feature for getting navigation directions.
Click to expand...
Click to collapse
BCM Version RC3.3Ux has very broken voice input. Many folk (including me) have commented that no VoIP apps work with it. Hopefully this will be fixed soon. BCM3.2U2 works fine, so I have reverted to that version for now.
You can install the CarHome app from the Play Store; it doesn't seem to be included in the BCM zip file.

[Q] Unable to flash recovery - error

I am trying to flash twrp through fastboot, but am not having any luck. Here is what I've done so far:
Flashed cm10.1. This flashed fine using nvflash, it also booted fine...could not, however,boot to fastboot or recovery at all. Using nvflash I restored to stock using images p2-p14 in another thread. After flashing I rebooted into a bootloop. Powered it off and booted into recovery and did factory reset, then rebooted. Now currently back on stock 2.2.2 boots fine. I then hopped into fastboot and attempted to flash twrp using "fastboot flash recovery recoveryname.img" This is where I'm recieving the following error:
Code:
Failed to process command getvar:partition-type:recovery error(0x2)
Any ideas on what has happened here?
Thanks
devx

devastatorx said:
I am trying to flash twrp through fastboot, but am not having any luck. Here is what I've done so far:
Flashed cm10.1. This flashed fine using nvflash, it also booted fine...could not, however,boot to fastboot or recovery at all. Using nvflash I restored to stock using images p2-p14 in another thread. After flashing I rebooted into a bootloop. Powered it off and booted into recovery and did factory reset, then rebooted. Now currently back on stock 2.2.2 boots fine. I then hopped into fastboot and attempted to flash twrp using "fastboot flash recovery recoveryname.img" This is where I'm recieving the following error:
Code:
Failed to process command getvar:partition-type:recovery error(0x2)
Any ideas on what has happened here?
Thanks
devx
Click to expand...
Click to collapse
Why are you flashing TWRP? As there is no version for Android 2.2 available. Android 2.2. has a different layout than any TWRP setup I have created.

giveen said:
Why are you flashing TWRP? As there is no version for Android 2.2 available. Android 2.2. has a different layout than any TWRP setup I have created.
Click to expand...
Click to collapse
I've now got it on Honeycomb, and booting into fastboot to flash recovery presents an identical error
Code:
Failed to process command getvar:partition-type:recovery error(0x2)
Any ideas?
Update: I figured I'd try booting from the image file rather than try to flash just to see, oddly enough this works using: fastboot boot recoveryname.img. Now if I could get it to flash...

Again, I will ask you.
Why are you flashing a recovery on stock Android 2.2¿
Sent from my Nexus 7 using Tapatalk 2

giveen said:
Again, I will ask you.
Why are you flashing a recovery on stock Android 2.2¿
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm don't intend to be condescending, but I clearly state in my last post that I had since successfully flashed Honeycomb and was no longer working with 2.2. Since then I have attempted to flash both cwm and twrp with no success. I am able to boot either of them from fastboot and have flashed ics-b5 cm9 which is what I am currently running. So I'm working around by booting the image from fastboot rather than flashing. I'm curious as to why it is throwing the error and what the error means exactly.

Okay, where did you get the copy of fastboot.
And I don't mean to be condescending but i made the twrp port. I know exactly what it needs.
Sent from my Nexus 7 using Tapatalk 2

giveen said:
Okay, where did you get the copy of fastboot.
And I don't mean to be condescending but i made the twrp port. I know exactly what it needs.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using fastboot from the android sdk

devastatorx said:
I'm using fastboot from the android sdk
Click to expand...
Click to collapse
If you got it from the SDK, thats your problem.
Recently in the Android 4.2.2 update Google decieded to add ADB signing. This required an update to the ADB and fastboot program. This resulted in total breaking of our devices ability to flash with the updated program. I am still researching a work around.
Please go to the Streak 7 Android Development section, and at the top of the forum is a link to drivers. In that pack of drivers is a copy of ADB/Fastboot that will work.

giveen said:
If you got it from the SDK, thats your problem.
Recently in the Android 4.2.2 update Google decieded to add ADB signing. This required an update to the ADB and fastboot program. This resulted in total breaking of our devices ability to flash with the updated program. I am still researching a work around.
Please go to the Streak 7 Android Development section, and at the top of the forum is a link to drivers. In that pack of drivers is a copy of ADB/Fastboot that will work.
Click to expand...
Click to collapse
I'll give that a go, thanks giveen.

error getvarartition-type:userdata user(0x2)
Hi !
My DS7 dosn´t boot.
I did a master reset, factory reset (User data only), factory reset (user data and Internal tablet storage), but the table didn`t boot.
I download the fastboot + driver from http://forum.xda-developers.com/showthread.php?t=1484406, but when I run the command "fastboot -w", it doesn´t work.
Please help me!
Thanks!

santi1928 said:
Hi !
My DS7 dosn´t boot.
I did a master reset, factory reset (User data only), factory reset (user data and Internal tablet storage), but the table didn`t boot.
I download the fastboot + driver from http://forum.xda-developers.com/showthread.php?t=1484406, but when I run the command "fastboot -w", it doesn´t work.
Please help me!
Thanks!
Click to expand...
Click to collapse
1. Start your own thread, don't hijack others
2. Need more info , as in logs, more description on what happens when you press power, charge status, did you install the drivers after downloading them, did you put the device in fastboot mode, what color of underwear are you wearing etc etc etc

****deleted*****

[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...