Related
hi i tried searching for this but couldnt really find anything on it. i tried updating to the cyanogen recovery.img 1.4 using terminal as the guide said here http://forum.xda-developers.com/showthread.php?t=533731, however now whenever i boot into recovery, the bootloader screen comes up instead. i have tried reflashing the recovery numerous times but the problem still persists. am i doing something wrong? any help would be great. thanks in advance
also i am rooted currently running JF 1.5 rom with latest radio and hard spl.
Put the recovery image on the SD card yourself. Get the file from here http://forum.xda-developers.com/showthread.php?t=523558
i have also tried that. once i placed the file on the sd card, i opened up terminal and typed in the command:
flash_image recovery /sdcard/cm-recovery-1.4.img
after i pressed enter nothing happend on screen, so i turned off the phone and tried to boot into recover, but the bootloader screen still appears. am i typing in the wrong command or something?
Do it again and this time wait for the # to appear again. Then type reboot and hold home button while it's booting. Should take you to Cyan's awesome recovery screen
Good luck
... Have you tried flashing it from fastboot like cyanogen recommended if you ran into any issues?
djosiah said:
i have also tried that. once i placed the file on the sd card, i opened up terminal and typed in the command:
flash_image recovery /sdcard/cm-recovery-1.4.img
after i pressed enter nothing happend on screen, so i turned off the phone and tried to boot into recover, but the bootloader screen still appears. am i typing in the wrong command or something?
Click to expand...
Click to collapse
After you open the terminal, did you type "su"?
billquinn1 said:
After you open the terminal, did you type "su"?
Click to expand...
Click to collapse
yeah i did type in su. i have been away for a few days so i ma going to try the suggestions mentioned. and no i havent tried doing it using fastboot as i havent got adb set up yet. i will also try that later. thanks for the suggestions.
I have the same problem. When holding power+home, it flashes t-mobile G1, then the screen disintegrates and it reboots a couple times, finally stopping on a blank black screen.
I have no problem booting straight into the O.S., I've just lost my recovery.
I've done this before and it worked, but I recently had a catastrophic failure and had to start from scratch.
If all else fails or you don't fell like using adb, should be fine if you downgrade and re-root, etc.... unless there is something else messing up your recovery partition.
Put the recovery.img file on the root of your sdcard
Then try:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system
cat /sdcard/recovery.img > recovery.img
flash_image recovery recovery.img
I've gone from JF 1.5ADP to Modaco using the cyanogen 1.4 recovery without any problems.
when you flash using terminal, you need to wait till you get the # back, and then restart the phone
which recovery image were you previously using as I was using JF 1.43 recovery
djosiah said:
hi i tried searching for this but couldnt really find anything on it. i tried updating to the cyanogen recovery.img 1.4 using terminal as the guide said here http://forum.xda-developers.com/showthread.php?t=533731, however now whenever i boot into recovery, the bootloader screen comes up instead. i have tried reflashing the recovery numerous times but the problem still persists. am i doing something wrong? any help would be great. thanks in advance
also i am rooted currently running JF 1.5 rom with latest radio and hard spl.
Click to expand...
Click to collapse
Hi djosiah
did you read this post ?
http://forum.xda-developers.com/showthread.php?p=4569666#post4569666
(Please substitude by the file name "update-cm-4.0.4-signed.zip" by "cm-recovery-1.4.img" in my post - sorry, I was misaken as to the file name ...!!)
My problem was a corrupted cm-recovery-1.4.img (a few thousand bytes of the MBs were missing ...!) A new downloaded cm-recovery-1.4.img (from another URL) solved the problem finally. The rest was cream - totally happy now.
Good luck!
My problem was solved.
Unroot the phone
reformat sd card using gparted live cd to fat32
redo root
flash new radio
flash new spl
flash cyanogen rom
flash cyanogen recovery
tada
Firstly, my nexus one is Locked + Rooted with Stock FRF91.
OK, So I rooted with 1-click, installed a custom recovery (first Clockwork then Amon RA 1.8.0.0).
Did a full backup
Tried out a couple of Roms
Reverted to Stock from backup. All good!
Now 1 week later, I really want to try MiUI Rom so I power on phone with VOL-, select Recovery - all I see is the yellow exclamation in a white triangle with a green Android below. Isn't that normal / stock recovery???
Could the FRG83 OTA that I have not installed (it is still bugging me to do so ) have restored the stock recovery?
Did I clear something / do something wrong when performing the Stock backup or restore?
TIA for any advice.
The OTA update did install, and in the process replaced install-recovery.sh and recovery-from-boot.p, which meant that the stock recovery was automatically reinstalled by the OS on reboot.
Hi rusty, thanks for the reply. I have not installed the update, it is still asking to be installed. I even checked the build number in about phone - frf91.
Are you saying that with out my explicit permission the ota has modified my phone and restored the stock recovery - that certainly would explain it.
I misread your post, sorry about that.
However, restoring your backup is probably the cause, due to the same reasons above.
To simplify, you can lose your recovery in this fashion:
Start with stock ROM
Root
Install custom recovery without removing the .sh and .p files mentioned
Boot up phone
Now, if you install custom recovery using several automated methods, OR manually remove the files previously mentioned in thread, no problem. But if those files remain the stock ROM will automatically run them and restore the recovery image. Happens to a lot of people.
So likely that's what happened; restoring and using your stock ROM had those scripts in the image.
khaytsus said:
To simplify, you can lose your recovery in this fashion:
Start with stock ROM
Root
Install custom recovery without removing the .sh and .p files mentioned
Boot up phone
Now, if you install custom recovery using several automated methods, OR manually remove the files previously mentioned in thread, no problem. But if those files remain the stock ROM will automatically run them and restore the recovery image. Happens to a lot of people.
So likely that's what happened; restoring and using your stock ROM had those scripts in the image.
Click to expand...
Click to collapse
Thankyou both for your help. It makes a bit more sense now.
So in order to get back to a custom recovery, will I need to reinstall it or will removing these .sh and .p files do the trick?
Ps, what is the exact location of these and how would I delete them (i assume they are system/ protected)
Thanks, Steve.
You'll have to remove/rename the files and flash it again.
They are: /system/recovery-from-boot.p and /system/etc/install-recovery.sh
You could rename them:
Code:
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
or remove them altogether
Code:
rm /system/recovery-from-boot.p
rm /system/etc/install-recovery.sh
My advice would be to rename, just incase you feel like stock recovery again at some point.
Rusty! said:
You'll have to remove/rename the files and flash it again.
They are: /system/recovery-from-boot.p and /system/etc/install-recovery.sh
You could rename them:
Code:
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
Click to expand...
Click to collapse
Perfect. Understood.
I'll try to remember to update this thread with how I get on once i'm done but even if I dont, I think the info contained is pretty clear.
Thanks Rusty & khaytsus.
Also I'm pretty sure that if you use ROM Manager to flash custom recovery, it automatically zaps the files that would otherwise revert you to stock recovery.
Sent from my Nexus One using XDA App
I did use rom manager and I have since done clockworkmod through rom manager but when I go into recovery I get the stock one. that's why I did the manual process installing ra after clockwork the first time round.
Anyone else has that where rom manager seems to install the custom recovery but then when you go there its stock?
I was trying to fix my NC and install the 1.0.1 firmware. So I tried to format everything back to factory setting so I went into clockwork mod recovery and thought formatting the system partitions would restore me back to factory settings. Well I formatted "boot" and now it will not boot.
tl;dr I formatted boot, is it bricked?
help?
wolffboy212 said:
I was trying to fix my NC and install the 1.0.1 firmware. So I tried to format everything back to factory setting so I went into clockwork mod recovery and thought formatting the system partitions would restore me back to factory settings. Well I formatted "boot" and now it will not boot.
tl;dr I formatted boot, is it bricked?
help?
Click to expand...
Click to collapse
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Do "Method one: Eight interrupted Boots" and post what happens afterwards
As I understand it, it is not bricked. You need to go read both the Nookie Froyo thread and the Clockwork Thread in the Nook Color Development Subforum. There is a way to put Nookie Froyo on an sdcard. You then boot with that and there's a way to put stuff back on the NC.
Do you have a Clockwork backup?
If you can boot back into Clockwork, there are some copies of other folks nandroid backup available. You can then put that on your sdcard and restore it.
I don't have the exact answer for you, but I'm sure it can be fixed.
Geezer Squid said:
As I understand it, it is not bricked. You need to go read both the Nookie Froyo thread and the Clockwork Thread in the Nook Color Development Subforum. There is a way to put Nookie Froyo on an sdcard. You then boot with that and there's a way to put stuff back on the NC.
Do you have a Clockwork backup?
If you can boot back into Clockwork, there are some copies of other folks nandroid backup available. You can then put that on your sdcard and restore it.
I don't have the exact answer for you, but I'm sure it can be fixed.
Click to expand...
Click to collapse
Paul22000 said:
Do "Method one: Eight interrupted Boots" and post what happens afterwards
Click to expand...
Click to collapse
When I press the power button nothing happens. I.E. screen stays black. Would your guy's ideas work if you can boot at all?
wolffboy212 said:
When I press the power button nothing happens. I.E. screen stays black. Would your guy's ideas work if you can boot at all?
Click to expand...
Click to collapse
I had the same thing happen. I tried plugging it into my Macbook, but nothing happened. I plugged into my Windows PC, and it came back to life.
A nookie froyo SD card would work fine. Restore from there manually. Next time make a nandroid and do not delete things that you do not know...
Syco54645 said:
A nookie froyo SD card would work fine. Restore from there manually. Next time make a nandroid and do not delete things that you do not know...
Click to expand...
Click to collapse
i have a nandroid back up and i cant get into recovery mode.
Because you deleted boot. Use a nookie froyo SD card and put the contents of boot back manually.
wolffboy212 said:
i have a nandroid back up and i cant get into recovery mode.
Click to expand...
Click to collapse
Which button combo are you trying to use to boot into recovery mode? If you haven't already, make sure you're using the three-button method.
Sent from my Nooted friend...
I have gotten it to boot to froyo on my sd card.
Now I need help restoring the boot partition from there.
Thank you very much with the support so far
It is not three buttons. Only need home and power.
wolffboy212 said:
I have gotten it to boot to froyo on my sd card.
Now I need help restoring the boot partition from there.
Thank you very much with the support so far
Click to expand...
Click to collapse
I am not certain what to do exactly as I have never used nookie froyo. Generally you are going to want to do
modified /system/boot
mount -t vfat /dev/block/mmcblk0p1
then put the files back in there from in nookie froyo.
Someone else may have the exact way. Sorry I cannot be of more help but that will mount boot when in stock. Of course you will have to mount system as RW as well.
Syco54645 said:
I am not certain what to do exactly as I have never used nookie froyo. Generally you are going to want to do
modified /system/boot
mount -t vfat /dev/block/mmcblk0p1
then put the files back in there from in nookie froyo.
Someone else may have the exact way. Sorry I cannot be of more help but that will mount boot when in stock. Of course you will have to mount system as RW as well.
Click to expand...
Click to collapse
Bare with me I know very basic unix and linux commands but I do have the brain capacity to figure things out (not boot partitions).
I was on the command line and I couldn't get into the nook color stuff just the nookie froyo stuff on the sdcard.
suggestions?
Please read CW recovery thread. All answers are in there!
Really, please take time to browse through existing threads before posting questions which have already been answered several times.
Anyway, considering the number of people asking, here goes:
Note: You can do all this from the Nook, without the need of ADB, except for the fact that you will need gapps on nookie in order to install terminal and root explorer (although you could install those apps by directly installing APK's), see http://nookdevs.com/NookColor:_Nookie_Froyo_Tips, Third-party app support
Please read entire thread before attempting anything!
- Boot into nookie with market installed.
- Install terminal emulator.
- Install root explorer
- Create a new folder at root (/), for example "boottmp" => "/boottmp"
- Launch terminal emulator
- type: "su"
- type: "mount /dev/block/mmcblk0p1 /boottmp"
- type: "echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt" (this will force reset on next boot, as if you did 8 failed boots)
- open browser
- Download boot.zip from here: http://forum.xda-developers.com/showpost.php?p=10470539&postcount=268
- copy zip content to "/boottmp", by replacing existing files
- shutdown
- remove sdcard
- power up, you should see installation process after splash screen. Wait for it to finish, and it will reboot.
- power off
- Next you need to reset to factory settings:
- Boot while using power button and N button. Should boot to menu allowing reset. Proceed with reset.
Boot and be happy.
OR,
If you're able to access ADB (available when booting CW recovery and mounting /system and /SDcard, format from android required on SD to work here), CREDIT GOES TO Duloz, try this:
adb push uRecRam.bak /sdcard/
adb shell
su
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
mkdir /system/boot/
mount -t vfat /dev/block/mmcblk0p1 /system/boot
cat /sdcard/uRecRam.bak > /system/boot/uRecRam
umount /system/boot
rmdir /system/boot
Click to expand...
Click to collapse
Note: Don't worry about errors concerning unmount.
If you're not back in business, post your questions, being very clear about what worked and what didn't.
Thank you.
Sent from my HTC Desire using XDA App
Back from Clockwork Recovery to Virgin (Factory) Recovery ... works like a charm!
samuelhalff said:
Please read CW recovery thread.
- Boot into nookie with market installed.
- Install terminal emulator.
- Install root explorer
- Create a new folder at root (/), for example "boottmp" => "/boottmp"
- Launch terminal emulator
- type: "su"
- type: "mount /dev/block/mmcblk0p1 /boottmp"
- type: "echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt" (this will force reset on next boot, as if you did 8 failed boots)
- open browser
- Download boot.zip from here: http://forum.xda-developers.com/showpost.php?p=10470539&postcount=268
- copy zip content to "/boottmp", by replacing existing files
- shutdown
- remove sdcard
- power up, you should see installation process after splash screen. Wait for it to finish, and it will reboot.
- power off
- Next you need to reset to factory settings:
- Boot while using power button and N button. Should boot to menu allowing reset. Proceed with reset.
Boot and be happy.
Click to expand...
Click to collapse
Works perfectly, thanks! I actually used adb instead of root explorer to do the copy and mount (etc.) commands, and did a manual 8-times power start interruption, but essentially the same. This made my poor "sound-failing" Nook a virgin again so I can swap it out at the store today. Crossing fingers that they will provide quick and easy exchange service (and let me test the sound on the replacement before I leave the store!)... Then, back to Autonooking (and even back to Clockwork Recovery...) again; now that I know how to go back and forth.
Owe you (or y'all) a beer!
I have a rooted dell streak 7, flashed with clockwork mod recovery. today i went to download the over the air update t-mobile sent out for the dell streak 7 and the phone froze, when i reset it it loaded to clockwork mod and i can't get it to load the normal OS now. no matter how many times i reset it. I even went so far as to format the /system, /cache and all the others trying to get it to boot pass the CMW recovery screen and nothing works. any suggestions would be helpful.
i dont know if it will help if you format with stock recovery you might e stuck but if you can still get into adb shell then try this guide you have to search for files yourself
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
read post carefully
CMW boot loop problem
Hey Guy,
I am having the same issue..when try too adb commad it return:
fail with error -1
please help
thanks for the reply. this is all very new for me, but, in general i can usually handle my own tech stuff.
so let me just ask a real basic question. if I can open ADB and send commands to the phone through a DOS prompt, then that would mean the ADB shell is working, is that correct?
No you have to type "adb shell" and see if that works
Sent from my Dell Streak 7 using XDA Premium App
thatruth132 said:
i dont know if it will help if you format with stock recovery you might e stuck but if you can still get into adb shell then try this guide you have to search for files yourself
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
read post carefully
Click to expand...
Click to collapse
Hi I am having the same issue..........but not working...... CMW recovery screen and nothing works. any suggestions would be helpful.
CWM boot loop problem
that is correct I abble to see device through adb....I typed adb shell and get a #...I type the command above and it return fail error....
Should have the boot.img and recovery img on my external sd card or internal sd card
Sdcard2
Sent from my Dell Streak 7 using XDA Premium App
Thank sooo much for help...I think I missing the highlighted steps below
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/show...5&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/show...3&postcount=23
I was able to get the stock boot.img back on the device- however the recovery.img did not take after an unsuccessful update on a CW/rooted device. Now I have a partially corrupt device that I cannot get passed the FCs on... I cannot even get as far as to set the USB mount in debug. I can get ADB shell to see it and execute commands- however no dice on on recovery.
I can only gain read access to the file system on the device while running as well. ANyone have any thoughts on how to to push or write the recovery image so I can reflash this thing? Thanks for everything already.
Dont flash update with cwm recovery you can only flash custom roms with custom recovery
Sent from my Dell Streak 7 using XDA Premium App
when you say mount /system and /cache. is that through the ADB bridge? or the CMW recovery screen on the dell streak?
Cm
Sent from my Dell Streak 7 using XDA Premium App
thanks for all your help so far. I can run the ADB shell successfully and get the # on my dos prompt. I go in and mount /cache, /data, and /system on the streak itself, through the CMW "mounts and storage" screen. and i have copied both the uploaded files, boot and recovery, to my external SD card. but whenever i type the command in, i get "failed with error: -1"
would me having formatted the drives change what i need to type here : "flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img" ?
white99 said:
would me having formatted the drives change what i need to type here : "flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img" ?
Click to expand...
Click to collapse
i don t think you was suppose to format
I know. this was back when the problem first occured. did it in a bit of a panic trying to get past the CMW boot screen. i'm just wondering if the "flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img" would need to change at all considering the mistake.
white99 said:
I know. this was back when the problem first occured. did it in a bit of a panic trying to get past the CMW boot screen. i'm just wondering if the "flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img" would need to change at all considering the mistake.
Click to expand...
Click to collapse
i think you may need to call dell bro
think if i call it in under the warrant, they'll send it back damaged?
if you formatted you more then likely bricked it. call dell feed them some bs about when you tried to update it bricked your device they will send you a new one
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
I have read and tried everything
I attempted the adb method but can't get into fastboot... I believe I got the adb commands correct and I don't get an error but my the restore is not taking... at the reboot it goes right back into CWM 3.0.2.0 here's my adb shell read out...
C:\android\platform-tools>adb shell
~ #
C:\android\platform-tools>adb shell
~ # flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
usage: flash_image partition file.img
~ # flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
usage: flash_image partition file.img
~ #
I don't know what else to do, I can't find a thread that stays on track long enough to follow this issue all the way thru... please help... I have read and tried everything, i can't find a clear set of alternatives... am i missing a step?
ya, i'm stuck in the same situation. I either get a "error -1" or it says "usage: flash_image partition file.img"
does getting "usage: flash_image partition file.img" mean the file was successfully flashed?
dfspot said:
I attempted the adb method but can't get into fastboot... I believe I got the adb commands correct and I don't get an error but my the restore is not taking... at the reboot it goes right back into CWM 3.0.2.0 here's my adb shell read out...
C:\android\platform-tools>adb shell
~ #
C:\android\platform-tools>adb shell
~ # flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
usage: flash_image partition file.img
~ # flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
usage: flash_image partition file.img
~ #
I don't know what else to do, I can't find a thread that stays on track long enough to follow this issue all the way thru... please help... I have read and tried everything, i can't find a clear set of alternatives... am i missing a step?
Click to expand...
Click to collapse
You are missing the space between mmcblk3pX and /sdcard.
ok, thats what i thought. when i do it the other way i get the "failed with Error: -1" any ideas on that. also if i send it back to t-mobile under the warranty, they won't send it back as damaged since i had CMW installed o it will they?
thatruth132 said:
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Click to expand...
Click to collapse
great how to
white99 said:
ok, thats what i thought. when i do it the other way i get the "failed with Error: -1" any ideas on that. also if i send it back to t-mobile under the warranty, they won't send it back as damaged since i had CMW installed o it will they?
Click to expand...
Click to collapse
humz mine wont flash at all
Guys,
If someone can help people struck here like me, it would be great.. i get the same -1 error message... when i run the second command. the first one passes through and i get a # for flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img.
When we downloaded the file boot.img, how would boot_orig.img work? am i missing something?
The second command throws me an error..
Guys really waiting for help... bricked my streak in hours after i brought it..
where are you at in la
I need a little bit of help for an ex-ipohone user
Hey guys sorry to ask u a noob question, but can anyone give me an ideea how to remove/unistall CWM Recovery so i can send back my Streak 7 for repair? I have installed CWM thru fastboot an i am currently on stock 2.2.2 rom. Or if there is a thread that i didnt find please a little help would be much apreciated.
i have figured it out eventualy after 20 hrs of brain scratching ived used NVflash and worked fast and easy
thatruth132 said:
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Click to expand...
Click to collapse
OMFG I would so kiss you right now. I was stuck where I could only load up CWR and nothing else was working. You are my hero. *sigh*
No biggie just hit that thanks.button
Sent from my Dell Streak 7 using XDA Premium App
The links are down, any mirrors?
Same need files links re not working
IMG Reposted?
Hi Folks,
A couple of people have posted that the boot, recovery, and system image links respond with a "404 not found" error. This is still the case.
I recall reading somewhere else that the images may still live on the SD card on the device. If this is true does someone know where in the file structure they may be?
If not, does anyone know where to obtain the images?
Currently I'm in CWM reboot hades on my Dell Streak 7. Tried the Dell OTA update for Honeycomb...didn't know that was a BAD thing until it was too late.
I've tried flashing boot and recovery images from a backup I'd made earlier, but no luck, so thatruth's excellent guide here: http://forum.xda-developers.com/show....php?t=1006829 doesn't help much...unless I can get the recovery and boot images.
So to reiterate:
I can get to CWM and clear the caches and flash a recovery.
I can communicate with the device via ADB and have flashed it with the backup images.
I can mount the internal SD card via CWM and my pc.
After flashing with the backup images, Fastboot still does not recognize that the device is connected, and the device does not apper to go through the 'format steps'.
Cheers,
L2
Found 'lightly modified' roms (thank you DJ Steve!) for a T-Mobile streak on another XDA thread. Flashed using adb, and tadaaaa, it booted! sliiiight problem. Will not boot into recovery and no wireless.
Managed to install rom manager (AKA ClockWorkMod) via ADB but CWM wan't an internet connection to install the recovery rom. grrrrr.
One of the other modifications (aside from root) by DJ Steve is the installation of 'BusyBox', This actually seems to complicate things for me because I don't really know how to issue ADB commands from the BusyBox shell. I get a lot of 'invalid command' and the like... I was able to install CWM OUTSIDE the adb shell (adb install rommanager) but once I'm in the shell (adb shell)I don't know how to issue the proper commands.
What I want to do is either remove busybox, or use ADB inside busybox to flash the CWM recovery rom, then flash my backup roms. (and hopefully return to full functionality.)
Any suggestions on how to use ADB commands inside of busy box to flash a rom?
Can anyone upload the stock rom images? I need to flash back to stock :\