I have a S7 that is an X rev and it only has one camera on it and it has a different ID than the current streak 7s, so I can't apply the update that tmobile put out.
So I rooted the S7 and ran ROM MANAGER and it insists that the clockworkmod is installed correctly, but I can't reboot into recovery from that program (I don't think it works on s7 anyway) nor can I do it with the volume+ and power. (All that does is to boot into android)
The fastboot seems to work fine, so is there a way that I can push one of the .ZIP file ROMs using fastboot? I was thinking the "Dell Streak 2.2.2 update with FULL ROOT" would be a good one to try, but there are many .img files in the zip file and when I try fastboot update, I get the following errors:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I know that the following lines will work, but there isn't a system.img in the .zip file.
$fastboot flash boot boot.img
$fastboot flash recovery recovery.img
$fastboot flash system system.img
Thanks
Maj
You cant use regular fastboot commands its something like "fastboot -l 0413e blah blah search my threads for "how to flash stock img. " at the bottom of first post you will see fastboot help link
Sent from my Dell Streak 7 using XDA Premium App
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Sent from my Dell Streak 7 using XDA Premium App
Hey thatruth I've never used fastboot -iowhatever. All my fastboot cmds are fastboot (cmd) (dir) (file). Op so when holding +volume and power it doesn't put you in the bootloader? Your device may not work with cwr. Being a X device. And op are you using ubuntu/linux?
Sent from a signal
to get into cwr you have to hold vol and power. Then at the android menu select option 2 update.pkg. it will then boot into recovery
you can also reboot into recovery via adb
adb reboot recovery
graffixnyc said:
to get into cwr you have to hold vol and power. Then at the android menu select option 2 update.pkg. it will then boot into recovery
you can also reboot into recovery via adb
adb reboot recovery
Click to expand...
Click to collapse
I have not found a way to get into recovery. Using adb, fastboot, reboot into recovery options, and attempting vol+ and power, just boots straight into android. It says "cold-booting linux" and boots into android. It seems as if there isn't a real partition to do that, so I somehow need to dump an image onto the s7 so that it will have all of these partitions.
I have a Droid Incredible in which I've hacked to death, so I know how to get into the other menus, they just don't appear to be there or accessible for some reason.
Hellzya said:
Hey thatruth I've never used fastboot -iowhatever. All my fastboot cmds are fastboot (cmd) (dir) (file). Op so when holding +volume and power it doesn't put you in the bootloader? Your device may not work with cwr. Being a X device. And op are you using ubuntu/linux?
Sent from a signal
Click to expand...
Click to collapse
Yah, the +volume and power just boots the phone right into android. ROM Manager tells me that my rooted s7 installs cwr just fine. (in fact I've tried every different version it offers) I use w7 x64.
MajikUF said:
Yah, the +volume and power just boots the phone right into android. ROM Manager tells me that my rooted s7 installs cwr just fine. (in fact I've tried every different version it offers) I use w7 x64.
Click to expand...
Click to collapse
did you try flash cwm through fastboot yet?
http://www.4shared.com/file/l2JpliG6/recovery-clockwork-3019-streak.html
use this to download cwm recovery img
jiwengang said:
did you try flash cwm through fastboot yet?
http://www.4shared.com/file/l2JpliG6/recovery-clockwork-3019-streak.html
use this to download cwm recovery img
Click to expand...
Click to collapse
Assuming that's the same cwm that I got in the streaksmart forum, yah. I flashed that using fastboot as the recovery and then issued the reboot into recovery command and it just booted up android.
At this point, I am assuming the build/version I have isn't a standard build and I will have to do something outside the normal channels to get it to work. I might just chuck this and get another. Especially since I heard that there will be a compatible version of honeycomb for devices with less than stellar resolutions like the s7.
I think the key here is to unplug usb from computer and hold down the power and Vol+ button to reboot into recovery mode.
I struggled with this for probably half a day figuring that out.
thx for your help and I finally figured out the fastboot and then recovery.img. So then I rebooted and seleted the software upgrade via update and it been stuck on that selection for awhile. is that normal?
by the way upper left hand it has in white lettering Booting recovery kernel image.
chavezop said:
thx for your help and I finally figured out the fastboot and then recovery.img. So then I rebooted and seleted the software upgrade via update and it been stuck on that selection for awhile. is that normal?
Click to expand...
Click to collapse
It should say Booting recovery kernel image and then take you straight into clock work recovery...
Mines doing the same thing just getting stuck when it says Booting recovery kernel image and the dell logo apears then when i press the power button it turns off if i boot the device up not plugged into my computer and hold the power and volume+ it will flash red the LED and turn off.
Resolved Yet???
I'm having the same issue... CWM says it's working fine but when I try to load ROM it reboots normally back into the menu... Red lights blinking and does nothing when trying to get into recovery mode. Fastboot is only thing that seems to work and that even doesn't work properly...
I'm stuck with a ROM that is constantly crashing. Every 10 min or so, it needs to go. Please anyone that may have a method I could try would be appricitated...
J
Hello,
ok so the problem is I tired to update to Jelly beam, i read about it here and i follow the steps. I make it to recovery and when i wanted to install files from zip it gave me error - Installation Aborted. I read somewhere that i have to update my Clockwork recovery so i tried and since then i can't do anything. When i press the power button i go to bootloader, from there if i chose Recovery the phone reboots and stucks on the colored X. When i type "adb devices" in cmd so i can try to apply some method list of devices is empty. I think it can be fixed if i make it to recovery but i can't. I looked a lot and maybe its because im mad or something but i can't find a solution, so if anyone can help me i will be very happy. I don't bother if im back to stock.
Use fastboot in bootloader, adb is only available in os and recovery
fastboot flash recovery recovery.img
Sent from my Nexus One using xda app-developers app
demkantor said:
Use fastboot in bootloader, adb is only available in os and recovery
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Tried that, stuck on : <waiting for device>
EDIT: I tried on my brother laptop and it worked but when i exucute the command, it says FAILED(remote: image update error)
EDIT2: Thanks i fixed it its working now. WOOHO!
when in bootloader have phone in fastboot mode, connect to pc via usb, make sure you have the proper drivers
HERE, THIS SHOULD HELP this is for a different phone so dont use the files but the concept is the same
Hey! So I rooted and installed cyanogenmod on my HTC One M7, and It was working fine for a while. Then recently it wouldnt turn on. I can access the bootloader, but my recovery - ClockWorkMod - was not working. I cannot enter recovery or factory reset my device. Also when I try to flash a new recovery via fastboot, it says that it failed to write, and my devices freezes on the fastboot screen. In fact any command I try via fastboot fails. I Hope to be able to restore my phone back to stock sense. Any help?
My sdcard is Fragmented
Glognaw said:
Hey! So I rooted and installed cyanogenmod on my HTC One M7, and It was working fine for a while. Then recently it wouldnt turn on. I can access the bootloader, but my recovery - ClockWorkMod - was not working. I cannot enter recovery or factory reset my device. Also when I try to flash a new recovery via fastboot, it says that it failed to write, and my devices freezes on the fastboot screen. In fact any command I try via fastboot fails. I Hope to be able to restore my phone back to stock sense. Any help?
Click to expand...
Click to collapse
My sdcard is fragmented:crying:
I only wanted to get root. I used to root phones with one click, but not this.
I unlocked it by doing various stupid things, then using fastboot.exe installed a custom recovery file with this command: fastboot flash recovery recovery.img.
Everything was succesfull.
Now when i want to get to recovery mode i see red text on HTC logo that is saying "this is for development purposes etc etc". It flashes for less than one second and go back to that menu when you can select Recovery mode.
How to fix it.
I just received my op3t and turn it on and then it said to update to latest firmware. Which I did. I updated it then it said failed. The device restarted and it is now stuck in bootload page. Anyone know a fix?
Also I cannot get into recovery mode. I can only get into fastboot mode. Not sure why it won't go into recovery.
Thanks!
Sent from my Nexus 6 using XDA-Developers Legacy app
Download full ROM of Oxygen OS here.
Download the stock Oxygen OS recovery image file from the same page (bottom of page under red "download" button).
Make sure your computer has fastboot installed, if not use something like minimal adb and fastboot.
Make sure your PC has the proper drivers installed for the OP3T.
Rename the stock recovery image file into something like stockrecovery.img
Boot phone into fastboot mode, connect to the PC and make sure the PC can detect the phone by inputting:
fastboot devices
If a serial number shows up, then enter the following two lines:
fastboot erase recovery
fastboot flash recovery stockrecovery.img
Reboot into recovery and use it to flash the full OOS 4.0.3 zip from a USB flash drive.
If the above doesn't work, the failed update may have damaged the firmware, in which case you will have to use the unbrick guide.