I updated my phone's SPL to "Danger SPL" and now my phone wont turn back on! I press power and the black Android screen with the little green android next to it comes up but wont boot my phone! The only thing I can do is get the white screen with the 3 android's skateboarding by pressing camera + power.
Ontop of that, I had tried to update my phone's recovery image too, and I erased the old one and now it would let me upload the NEW one! So not only do I have NO PHONE but NO RECOVERY either!
What do I do!? HELP!
can you get into fastboot? (back+power)
if you can, get adb running and flash your recovery image with fastboot
you are gonna have to fast boot in the screen with the three androids on it, either a rom or a recovery
guess you betta learn how to use adb
Yea I can get into fastboot, thats the ONLY thing I can get into. How do I flash my recovery image?
http://forum.xda-developers.com/showthread.php?t=566669
boot your phone into fastboot. plug in your usb cable to your pc. this should change the fastboot icon on the screen to fastboot usb. from there, load up adb on your pc and make sure you have the fastboot option available by typing fastboot devices. it should list your phone. once that is good, type:
fastboot flash recovery and the correct name of your recovery file.
for example:
fastboot flash recovery recovery-RA-dream-v1.2.3.img
**also note...put the recovery image in your android sdk\tools folder**
this should give you a recovery to boot into.
if you dont have adb on your pc, read this and follow the instructions
http://forum.xda-developers.com/showthread.php?t=532719
I did that already, it wont work.
C:\Android>fastboot flash recovery recovery123.img
error: cannot load 'recovery123.img'
i am gonna be the one to ask this question but did you put .s between 123 like 1.2.3.
you need to be in the tools directory, not the android directory.
c:\Android\tools>fastboot flash recovery recovery-RA-dream-v1.2.3.img
and you need the recovery file IN your tools folder for it to be found as well.
No I didn't put .'s between each number I renamed my file recovery123.img so thats the way I put it in.
ok, so go to the correct directory and input what you had the first time, WITH the file IN that same folder. and then report back.
i justed rename my recovery the shortest way i can like for amon ra"s i just put amon, less typing is always better
It says C:\Android\tools is not recognized as an internal or external command, operable program or batch file.
from your c:\> prompt type this:
cd c:\android\tools
(this is assuming you have the android sdk in the c:\android folder on your pc)
if it is saying its not a folder, then that is not where you installed the android sdk.
knowfear said:
and you need the recovery file IN your tools folder for it to be found as well.
Click to expand...
Click to collapse
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
If you use the above SPL you will need new drivers for Windows. They are located here.
Click to expand...
Click to collapse
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
what he said.
Binary100100 said:
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
Click to expand...
Click to collapse
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
innerspace said:
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
Click to expand...
Click to collapse
No problem. I just hate it when something this simple drags onto multple pages. Call it a peev. So many people get intimidated by the "Danger SPL" because they don't want to risk bricking their phones. The odds of bricking your phone are extremely small if you follow directions and read everything. And sure the possibility of accomplishing this by different means exists. But when you try to tell someone to put this file in that folder and type in the full names of the files to include all the dots and dashes, it's going to get confusing and intimidating and thus these posts keep popping up.
If someone follows those very short and simple directions they shouldn't have any problems. Granted that "**** happens" and things don't always go as they should. So in that case, search for your answer. If you've searched on XDA then search Google. Out of the MILLIONS of G1's that have been sold, I am fairly certain that someone out there has had a similar problem. If not then you and your phone are literally "1 in a million" (technically it was 1 in 1.5 million a year ago so you can bet that it's well over 2 if not 3 million by now). And if you really fall into that catagory then please post a new thread (in the appropriate catagory of course) .
well the good news is u didnt brick ur phone but try a enter adb and do a nadroid back up if u hav 1 that will bring u back 2 the way u want it
either flash a nadroid or flash dreaming.nbh....i had the same problem and a nadroid worked just fine
Related
well i happened to have some problems with a theme i was using that made the icons appear themed even in cyanogens roms , and i was told that i needed to flash the htc adp image to fix that
the problem comes here i flashed the htc adp image but i forgot to read what cyanogen said that i had to flash his rom before rebooting
so i just found that cyanogen gives us something to follow just in case it happens what happened to me here http://wiki.cyanogenmod.com/index.php/RE-recovery-img
i went to ''if you currently have an engineering or a Hard SPL'' and followed all the procedures until i got to number 4 where it asks me to Change directory to where you have saved your recovery image..i've tried lots of paths but none seems to work...ADB NOOB HERE so please help
when you didnt follow the process, you lost root.
you have to start from scratch.
.............................................................................
i typed
cd C:\recovery-RA-dream-v1.5.2.img
and it tells me the directory name is invalid what am i doing wrong?
recovery image is not a directory, it'a file. What are you trying to do?
borodin1 said:
recovery image is not a directory, it'a file. What are you trying to do?
Click to expand...
Click to collapse
im trying to flash amon ra recovery via fastboot
Easier to do it from adb
Code:
adb remount
adb shell flash_image recovery C:\recovery-RA-dream-v1.5.2.img
reboot
Just a tip: I usually rename files into something easier to type, like ra152.img. Up to you though.
You can also do it from terminal (place file on the root of sdcard)
Code:
su
flash_image recovery /sdcard/filename.img
reboot
If you must do it via fastboot
Start your phone in fastboot mode (camera/power)
Code:
fastboot flash recovery recovery-RA-dream-v1.5.2.img
fastboot reboot
borodin1 said:
Easier to do it from adb
Code:
adb remount
adb shell flash_image recovery C:\recovery-RA-dream-v1.5.2.img
reboot
Just a tip: I usually rename files into something easier to type, like ra152.img. Up to you though.
You can also do it from terminal (place file on the root of sdcard)
Code:
su
flash_image recovery /sdcard/filename.img
reboot
If you must do it via fastboot
Start your phone in fastboot mode (camera/power)
Code:
fastboot flash recovery recovery-RA-dream-v1.5.2.img
fastboot reboot
Click to expand...
Click to collapse
i would do this..but i cant since i messed up when flashing the htc adp image im following cyanogens tutorial http://wiki.cyanogenmod.com/index.php/RE-recovery-img and it says that i have to flash the new recovery through fastboot , and the part im stuck at is step 4 where he says that i need to Change directory to where you have saved your recovery image
if you can get into the main phone operating system via a boot up then use linda file manager to move them
when i type this
fastboot recovery recovery-RA-dream-v1.5.2.img
i get this message "error: cannot load 'recovery-RA-dream-v1.5.2.img
then i changed the directory to where the recovery image was and when i tried to flash i got this message
'fastboot' is not recognized as an internal or external command, operable program or batch file
Not sure, I'm not anywhere near my computer. Try putting your recovery image into different locations (i always put it on desktop) and rename it to something simpler, without any punctuation or special characters (i suggest rec.img). Also... make absolutely sure that you're NOT naming it rec.img.img . Make sure that your PC is not hiding your extensions.
Then, connect your phone to the computer, start your phone in fastboot mode (not Hboot or serial, if you see serial or Hboot on your screen then tap return button)
In command line type
Code:
fastboot devices
to make sure that you're connected
then type
Code:
cd desktop
your directory should change to something like C:\user\desktop (make SURE there are no spaces anywhere in user name, fastboot has problem with that. I had to rename my account to "EugeneAndLiz"a from "Eugene and Liza" because of that)
then type
Code:
fastboot recovery rec.img
fastboot reboot
and let us know how did it go for you. I'l be lurking around here for a while, hopefully we can resolve this.
Good luck
borodin1 said:
Not sure, I'm not anywhere near my computer. Try putting your recovery image into different locations (i always put it on desktop) and rename it to something simpler, without any punctuation or special characters (i suggest rec.img). Also... make absolutely sure that you're NOT naming it rec.img.img . Make sure that your PC is not hiding your extensions.
Then, connect your phone to the computer, start your phone in fastboot mode (not Hboot or serial, if you see serial or Hboot on your screen then tap return button)
In command line type
Code:
fastboot devices
to make sure that you're connected
then type
Code:
cd desktop
your directory should change to something like C:\user\desktop (make SURE there are no spaces anywhere in user name, fastboot has problem with that. I had to rename my account to "EugeneAndLiz"a from "Eugene and Liza" because of that)
then type
Code:
fastboot recovery rec.img
fastboot reboot
and let us know how did it go for you. I'l be lurking around here for a while, hopefully we can resolve this.
Good luck
Click to expand...
Click to collapse
im going to tell you step by step what i do
turn the phone off
hold power and back
i see the androids on skateboards and it says fastboot in red letters
i connect my phone via usb then the name changes to fastboot usb
run the cmd
once there i type where adb is located which is cd C:\android-sdk-windows\tools
then when i type fastboot devices
i see the serial number of my phone
now when i type cd desktop i get this message "the system cannot find the path specified"
and if i ignore that and try to flash
fastboot flash recovery rec.img (yes i did rename the recovery image)
it says that it cant load 'rec.img'
Got it! Put your image file into the "tools' folder and once you see your device in the fastboot just flash it from there
Code:
cmd
cd C:\android-sdk-windows\tools
fastboot devices
fastboot flash recovery rec.img
fastboot reboot
Sorry about all this complication... the main idea is that your recovery needs to be in the same directory as you're when you're flashing. So if earlier you went to tools folder then your file needs to be there as well.
Try it out.
it worked...it said sending 'recovery' <4456 KB>... okay
writting 'recovery'...okay
fastboot reboot
then when i go to the system recovery..its the same htc adp one
i tried to flash amon ra's recovery and cyanogens
oh nevermind..instead of rebooting the phone i just unpluged the device and wnet directly into the system recovery and YES i have cyanogens recovery thank you so much borodin1
hmmmm that's weird because you got confirmation....
1. Did you download right recovery? You had to becaue you tried 2 of them and you can only make the same mistake once lol
2. AmonRA's recovery has the same image in the background as HTCs, are you sure that it's still HTC's recovery?
Other then that... I'm clueless
Can you get su in the adb shell? Try flashing it from adb....
You got me stomped on this.... Anyone else wants to take a shot at this????
i dont know what happened but when i flashed the recovery image on fastboot and then rebooted the phone...then turn off the phone and went to the system recovery and the htc adp recovery appeared...blue letters and the scrolling options..but when i did not reboot the phone after flashing the image and went directly to the system recovery i had the recovery i flashed...then i applyed the updateand everything is good now
weird uh?
will that new recovery stick?... I'm starting to remember something but it's vague... give me few minutes Reboot couple of times into recovery and back for now and see what happens...
it did stick..i just rebooted into recovery and i have the new recovery..haha
Great! Happy modding!
Hi, I've looked around the forum and i haven't found any instructions on how to apply the ratio update, I'm a new Android user, so I don't really know much about it. I hope someone would help me...
there a 2 in development.
Be careful though, I believe radio and spl changes can brick your device. Unless that is not a problem on newer Android phones.
I believe its the same as flashing a ROM, haven't done it in a while..
fastboot flash radio radio.img
Jr33 said:
fastboot flash radio radio.img
Click to expand...
Click to collapse
can you do this in terminal emulator with the radio image on your sd card?
I can't find any thread in the development section that says how to flash it, it might be in one of the threads, but i don't want to start looking in 100+ pages threads.
can't any one just tell me how to do it?
what is the exact command i should write in fastboot?
as i said I'm not really knowledgeable in all that stuff.
Papichulo06 said:
can you do this in terminal emulator with the radio image on your sd card?
Click to expand...
Click to collapse
no, you have to be in the bootloader (hold trackball while powering on).
you type the command in your command prompt on your pc
Can someone just please tell me the exact command?
shaharhoch said:
Can someone just please tell me the exact command?
Click to expand...
Click to collapse
You mean like the one in Post #4?... Seriously, come on man.
have you flashed the recovery? if you have just put the radio on your sd boot to recovery and flash that simple.
Paul22000 said:
You mean like the one in Post #4?... Seriously, come on man.
Click to expand...
Click to collapse
Is that the exact command? shouldn't there be windows somewhere?
and gtrplr71 as far as i know (and that's not very far) i can't flash from recovery because it only recognizes zip files.
shaharhoch said:
Is that the exact command? shouldn't there be windows somewhere?
and gtrplr71 as far as i know (and that's not very far) i can't flash from recovery because it only recognizes zip files.
Click to expand...
Click to collapse
I did it that way
here it is
here is the link
http://forum.xda-developers.com/showthread.php?t=632187&page=11
post #108
flash the radio. radio update zip file is on this site. ERE36B / 32.26.00.24U_4.04.00.03_2 radio - update zip format. this is the current #'s
http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
only possible on phone if you unlocked your bootloader. will not work on stock phone
If the radio is in zip format then flash it using Amon_Ra
if it is image file then
fastboot flash radio radio.img
of course, you have to include the full path for radio.img, it could be C:/abc/xyz/radiowateverthefilenameis.img
Since I'm a total n00b as well, let me explain how to do this in the simplest of terms for anyone not up on all of the lingo. I for some reason was flashing the zip wrong or something because I couldn't get it to work that way. And if I can figure it out, anybody should be able to...
First power off your device and then turn it back on holding down the trackball and the power button to get into the bootloader. It should say something like Bootloader USB at the top. Plug your USB cable that is plugged into your phone into the computer.
OK, download THIS FILE. Take that file and put it in whatever folder your fastboot file is in. Your fastboot file will be the file that was created when you unlocked your bootloader and it is the file that allows your computer to communicate with your phone. I renamed it to 'radio' to make it easier. You don't have to put the .img at the end of the file either. I followed the tutorial over at theunlockr so mine was in c:\superboot. Next go to your command prompt and pull up that directory. (Run>type cmd and press enter)
Now get to that directory wherever your fastboot is located at. Type cd\ and then press enter. Then type cd\(whatever the directory name is where fastboot is).
Next type out the following:
fastboot-windows devices
and then press enter. You should see some sort of serial #.
OK, if you do, proceed. If not, your computer is not seeing your phone.
Next type:
fastboot-windows flash radio radio.img
and then hit enter.
And that's it. Now before doing this let someone else make sure I didn't forget anything. Then just REBOOT and you should be good to go.
For all you pros out there, I am just trying to help people out here who are COMPLETELY new to this. I hope this helps and remember to let someone more knowledgeable then me confirm this is correct.
That's a good walkthrough for newbs, but I would recommend using Shift+right click>Open command prompt here instead of opening the command prompt on C and having to change the directory.
I saw somewhere else say to do it that way but I don't think it works on XP...at least it doesn't on my computer
masse1369 said:
OK, download, THIS FILE. Take that file and put it in whatever folder your fastboot file is in.
Click to expand...
Click to collapse
This part is a little ambiguous. What is the fastboot file that people should have gotten previous to downloading the file you linked?
The other day my phone's touchscreen developed a dead spot. Verizon was kind enough to send me a "Like-New" replacement and requested that I return the old phone. The only problem with that was I had hacked the hell out of it and didn't want them to see what I did and charge me.
I had rooted the phone, installed Clockwork Recovery, set S-OFF with Unrevoked Forever, updated to the latest radio and installed all kinds of different ROMs before finally settling on CM6. Now I had to find a way to install either stock 2.1 or stock 2.2 with the correct radio for either one, flash back the stock recovery, and finally set the phone back to S-ON. If you find yourself in a similar situation, you'll probably want to read this instead of spending 6 hours pulling your hair out, like I did. Here's what I finally came up with:
STEP 1: Get ADB Running.
Make sure you have ADB up and running. If you're rooted with a custom ROM and you don't have ADB running you have more problems than I can help you with. If you use a Mac, see Step 1A below to make things a little easier when using ADB.
Step 1A: (Mac Users Only) Make Your Life Easier.
Let's add the android SDK tools folder to your .bash_profile. What does this do, you ask? It makes it so that you can run any ADB commands without having to be in your SDK Tools directory. How do we do this?
Open a terminal window. Type
Code:
nano ~/.bash_profile
This will open a text editor in the terminal and create a new text file in your home directory called .bash_profile, which will be invisible in the Finder.
Enter the following:
Code:
PATH=$PATH:/Applications/Utilities/android-sdk-mac_86/tools
export PATH
!!IMPORTANT!! I have my "android-sdk-mac_86/tools" folder inside my "Utilities" folder, which is inside the "Applications" folder. If you have your android sdk folder somewhere else you will have to change the above text to reflect the proper path to your folder.
Hit ctrl-x. Not cmd-x, ctrl-x.
The editor will ask you if you want to save changes. Press "Y".
It will ask you what you want the file name to be. Just press enter, as we've already named it .bash_profile.
Quit and re-open terminal.
You can now use any command in the SDK tools folder from any directory.
STEP 2: Install Fastboot.
Make sure you have the HTC Fastboot tool installed. If you don't, you can get it here: http://developer.htc.com/adp.html
Download it for your particular operating system.
Another tip for Mac users: Once you download and unzip it, rename it from "fastboot-mac" to just "fastboot", then place it in your SDK Tools directory.
STEP 3: Downgrade To 2.1 With Old Radio.
We now need to downgrade our radio and get back to stock 2.1. The best way I found to do this was explained in this thread: http://forum.xda-developers.com/showthread.php?t=757927
Download the zip and follow the instructions.
Hat tip to Berzerker7 for the write-up, and aiccucs for putting together the zip file in that thread.
The next step will be a little bit of backtracking, but it's mostly painless, and it still seems to be the easiest way to do this.
STEP 4: Set NAND To S-ON.
We now need to set the NAND to S-ON. Problem is, in step 3 we flashed the stock recovery back onto the phone. Not a huge issue.
First, go to unrevoked.com and download unrevoked3. Run it. This will re-root the phone and install Clockwork recovery. Once this is done, go here: http://unrevoked.com/rootwiki/doku.php/public/forever and download the unrevoked-forever S-ON Tool.
Copy this file to your SD card and rename it "update.zip"
You can do that with adb like this:
Code:
adb push /path/to/unrevoked-forever-son.zip /sdcard/update.zip
Reboot into recovery and use Clockwork to apply the patch, which will set the NAND back to S-ON.
STEP 5: Get The Phone To Accept Stock Recovery With S-ON
This was the biggest problem that I ran into. The phone would regurgitate every zip I found which contained a stock recovery when the phone was set S-ON. I finally found a way around that.
First, download this PB31IMG.zip file: http://d01.megashares.com/index.php?d01=CHoQD3B
This IMG file was posted by Diego Mejia, on a youtube video he uploaded. Thanks to Diego, his work was very helpful in this process.
Here's the catch: in order to apply this PB31IMG.zip, we need to downgrade HBOOT or we'll get an error, due to the fact that we had set S-ON in the previous step.
Here is a link to a post on androidforums.com with an attached zip file called "revert.zip": http://androidforums.com/incredible-all-things-root/123816-how-revert-back-earlier-version-hboot.html
Credit is due to adrynalyne for coming up with this process and posting the files, I just tweaked his instructions a bit to make them work for me.
Once the "revert.zip" file has been downloaded, follow adrynalyne's instructions on what to do with the files. Reposted below:
Boot the phone into Clockwork Recovery.
Go to partitions, and mount data.
Type the following commands in a terminal window:
Code:
adb push flash_image /data
adb push mtd0.img /data
adb shell
chmod 777 /data/flash_image
cd /data
flash_image misc mtd0.img
exit
adb reboot oem-78
Watch for your phone to reboot to a silver HTC logo.
Then type:
Code:
fastboot devices
Verify your device shows up/responds/etc.
Click to expand...
Click to collapse
If the "fastboot" command works you should see an "H" followed by a string of random numbers and letters. So far, so good.
STEP 6: Reapply Stock 2.1 With Stock Recovery.
Once you've run the "fastboot" command successfully, go ahead and pull the battery. Leave the phone off. Go back to the PB31IMG.zip you downloaded in step 5, and copy it to the root of your SD card. Put the SD card back in the phone and boot it into recovery. If you've done all this correctly, the phone should recognize the PB31IMG.zip as valid and ask if you want to apply it. Do so. This will reflash the stock 2.1 ROM with the stock recovery while the phone is set S-ON. You can now send your phone back to Verizon.
STEP 7: Profit.
--B
Hey Mods, any chance of a sticky?
--B
There's a much easier/faster way to do this:
Just S-ON before you downgrade a first time, and then flash_image misc right away. The PB31IMG will take and you'll be at 2.1 with a single RUU flash.
Berzerker7 said:
There's a much easier/faster way to do this:
Just S-ON before you downgrade a first time, and then flash_image misc right away. The PB31IMG will take and you'll be at 2.1 with a single RUU flash.
Click to expand...
Click to collapse
Interesting. I couldn't get RUU to jive for some reason and didn't happen upon the bit about the flash_image until I'd already gone around in circles for several hours. Cool if the shortcut works, though! Where was your info at one o'clock this afternoon when I needed it?
--B
xraystyle said:
Interesting. I couldn't get RUU to jive for some reason and didn't happen upon the bit about the flash_image until I'd already gone around in circles for several hours. Cool if the shortcut works, though! Where was your info at one o'clock this afternoon when I needed it?
--B
Click to expand...
Click to collapse
Not reading your topic. lol
I found it easier, to just since your rooted already, just put it to S-on, then run the stock RUU for 2.2. and your done in two steps. no need for all the codes.... I just did it, got my refurb yesterday,...
Thanks for the informative post! This will help a lot of people in the future.
This may void your warranty, cost you your soul, and cause your spouse to leave you - ALL OF WHICH I AM NOT RESPONSIBLE FOR!
So, if it's because you screwed up flashing something, bricked your tablet with an OTA update after you installed CWM, or whatever, this is how you get it back to its outta-da-box shape!
(Please note, this assumes you have both installed CWM on your DS7 AND have installed the latest SDK on your computer).
1. Download the three attached .img files
2. Boot into CWM (since there really isn't anything else you can do)
3. In CWM, mount your SD card (so that you can view files via USB)
4. Plug in your DS7 to your computer, and copy the three .img files to the root of your SD card
5. Unmount your SD card, but leave the USB cable plugged into computer
6. Mount as many things as you can (ie system, boot, etc)
7. Open up command prompt, and navigate to your Android/tools folder, and type "adb devices"
8. There should be a number that shows up, or a "?" - either at this point is fine
9. Type the following command:
Code:
adb shell
a hash tag should show up that looks like this:
Code:
#~
10. Now, type the follow two commands one at a time:
Code:
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
11. now, select "reboot" from DWM to reboot your device. It should boot and say something like "Formating Misc", and then it will reboot repeatedly
12. Use something small to push the RESET button on the DS7 (it's next to the SD card slot)
Your screen should go blank
13. Now, press and hold both the POWER button and the VOLUME - button until the screen comes on saying that the "fastboot downloader" is booted
14. Copy the three .img files into the your Android/tools folder
15. Now type the following code:
Code:
fastboot devices
16. There should be a number that shows up, or a "?" - either at this point is fine once again
17. Now type the following commands one at a time. The first will take a while to complete - this is okay:
Code:
fastboot flash system system_orig.img
fastboot flash recovery recovery_orig.img
fastboot flash boot boot_orig.img
Now, if after every command a "finished." is given, along with the total time each command took, you may continue.
18. You may now type the triumphant command:
Code:
fastboot reboot
Which will reboot your device.
Give it a little bit to boot, but when all is done you should see the original T-Mobile boot animation and everything.
Special thanks to DJ_Steve, bogdi1988, and [email protected] for all your help!
Needed files:
system_orig.img
recovery_orig.img
boot_orig.img
[Edit]
For those users who need the original "flash_image.zip" file, I have uploaded it and it is available here.
PS: As an added note: **** you Koush! From all of the DS7 community!
Just what was needed
sent from somewhere
thanks but if you would of search there was a thread made already but i am sure the more the marrier
mooch777 said:
This may void your warranty, cost you your soul, and cause your spouse to leave you - ALL OF WHICH I AM NOT RESPONSIBLE FOR!
So, if it's because you screwed up flashing something, bricked your tablet with an OTA update after you installed CWM, or whatever, this is how you get it back to its outta-da-box shape!
(Please note, this assumes you have both installed CWM on your DS7 AND have installed the latest SDK on your computer).
1. Download the three attached .img files
2. Boot into CWM (since there really isn't anything else you can do)
3. In CWM, mount your SD card (so that you can view files via USB)
4. Plug in your DS7 to your computer, and copy the three .img files to the root of your SD card
5. Unmount your SD card, but leave the USB cable plugged into computer
6. Mount as many things as you can (ie system, boot, etc)
7. Open up command prompt, and navigate to your Android/tools folder, and type "adb devices"
8. There should be a number that shows up, or a "?" - either at this point is fine
9. Type the following command:
Code:
adb shell
a hash tag should show up that looks like this:
Code:
#~
10. Now, type the follow two commands one at a time:
Code:
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
11. now, select "reboot" from DWM to reboot your device. It should boot and say something like "Formating Misc", and then it will reboot repeatedly
12. Use something small to push the RESET button on the DS7 (it's next to the SD card slot)
Your screen should go blank
13. Now, press and hold both the POWER button and the VOLUME - button until the screen comes on saying that the "fastboot downloader" is booted
14. Copy the three .img files into the your Android/tools folder
15. Now type the following code:
Code:
fastboot devices
16. There should be a number that shows up, or a "?" - either at this point is fine once again
17. Now type the following commands one at a time. The first will take a while to complete - this is okay:
Code:
fastboot flash system system_orig.img
fastboot flash recovery recovery_orig.img
fastboot flash boot boot_orig.img
Now, if after every command a "finished." is given, along with the total time each command took, you may continue.
18. You may now type the triumphant command:
Code:
fastboot reboot
Which will reboot your device.
Give it a little bit to boot, but when all is done you should see the original T-Mobile boot animation and everything.
Special thanks to DJ_Steve, bogdi1988, and [email protected] for all your help!
Needed files:
system_orig.img
recovery_orig.img
boot_orig.img
PS: As an added note: **** you Koush! From all of the DS7 community!
Click to expand...
Click to collapse
Thanked using the Thanks button and Thanks for your post!
Just to remind me a little as I may miss something,
why we **** Koush? It is not his fault that we stuck at CWM, or is it????
jiwengang said:
Thanked using the Thanks button and Thanks for your post!
Just to remind me a little as I may miss something,
why we **** Koush? It is not his fault that we stuck at CWM, or is it????
Click to expand...
Click to collapse
No its not his fault.. people shouldn't have tried to install the ota update while having cwr installed.. instead should have waited for a zip of the update that hell posted on behalf of did steve. As I have said if you have cwr you really can't get ota updates and install them the normal way. If the update was an update.zip you could flash through cwr but dell uses pgk files not zip.. so the only way to update is to wait for a dev to release a flashable cwr zip fike
Sent from my HTC Glacier using XDA App
The reason I made this post was so that we could have one concise, iD10t proof solution for people who were dumb like me. There's other posts, but you have to go back and forth to get the solution.
And the "Koush-****ing" was because of his unannounced abandonment of his projects, and those he was working with.
And thank you for the kind thanks!
Sent from my Dell Streak 7 using XDA App
mooch777 said:
The reason I made this post was so that we could have one concise, iD10t proof solution for people who were dumb like me. There's other posts, but you have to go back and forth to get the solution.
And the "Koush-****ing" was because of his unannounced abandonment of his projects, and those he was working with.
And thank you for the kind thanks!
Sent from my Dell Streak 7 using XDA App
Click to expand...
Click to collapse
Did he retire completely?
graffixnyc said:
Did he retire completely?
Click to expand...
Click to collapse
Think so!
From my CM7 UrBan Glacier
Hi,
I am the situation described above as I tried the OTA and am now stuck in CWR.
I followed the directions putting the 3 files on the root of my DS7 and am stuck at the following:
~ # flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
failed with error: -1
~ #
Any ideas.....?
Thanks
SkI
Error 1
Error 1 means that the file is not where it is supposed to be. In this case on the SD card. Check and make sure that you have the right file, with the right file name on the root of your SD card and try again!
Good Luck
What does
"Error scanning partitions" means?...
jiwengang said:
What does
"Error scanning partitions" means?...
Click to expand...
Click to collapse
nvm, it is solved. don't use your own flash_image. use the stock one.
dj_ski69 said:
Hi,
I am the situation described above as I tried the OTA and am now stuck in CWR.
I followed the directions putting the 3 files on the root of my DS7 and am stuck at the following:
~ # flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
failed with error: -1
~ #
Click to expand...
Click to collapse
+1 same here...
I find that at step 3... I mount sdcard... it shows on PC... I copy the 3 files to drive... unmount sdcard... mount everything else... run the other commands then get error... when I repeat the process I notice the files I copied are not there... ?
so I tried to adb push the files... they say they went thru correctly... but still get the same result as above...
any ideas?
dfspot said:
+1 same here...
I find that at step 3... I mount sdcard... it shows on PC... I copy the 3 files to drive... unmount sdcard... mount everything else... run the other commands then get error... when I repeat the process I notice the files I copied are not there... ?
so I tried to adb push the files... they say they went thru correctly... but still get the same result as above...
any ideas?
Click to expand...
Click to collapse
when you adp push to sdcard, make sure you mounted it already.
after that , it always help to adb shell ls /sdcard to make sure all files are there.
then you go to adb shell,
use the stock flash_image to flash. remember point to the path to flash_image
eg. flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
my understanding, if you don't mount sdcard, you canot see your sdcard FROM the tablet's perspective.
I mean, for table's flash_image to work, it has to be able to access its drive, in this case, is sdcard 's content.
so did you try leave sdcard mount and do the command above?
Hey Team...
can someone help me find the stock flash_image plz.....
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
chris73 said:
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
Click to expand...
Click to collapse
What command did you do.
Sent from my HTC Glacier using XDA App
chris73 said:
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
Click to expand...
Click to collapse
do I need to push flash_image to my tablet?
If I remember correctly it needs to be in the nvflash folder
Sent from my Dell Streak 7 using XDA Premium App
i chose to start this thread as an educational and informative way of answering simple question so new questions arent repeatedly asked.
first off try to use the search window as much as possible before you post a question, chances aer your question has been asked before, so you will find the answer somewhere.when you do have to post a question be patient, the answer will come either in the form of an informative response or with a link to an informative response.
in every thread or be it for a rom ,a mod a theme etc. there are instructions. follow them to the letter and you shouldnt have any problem.
most importantly, be grateful to the devs or members which might assist you , at least say thank you and hit the thanks button, and donate if you can. these individuals work very hard at what they do here to provide you with the information and freedom you need to do what you want to do with your HEROC.
say thanks,,,its not that difficult.
Root your HTC HERO200 CDMA...
there are many different methods of rooting your device, it depends on your particular device.
they all work you simply have to find the one that works for you. for instance myself i use the regawmod one click method. (thanks regaw) when
i tried to use it on an associates device it didnt work...you have to find the method that works for your device.
youll find the files and programs you need to perform whatever procedure you choose to try on the developers page.
make sure you read the instruction completly before you begin. when you do begin follow the instruction to the letter and you shouldnt have any problem.once again, dont get piussed at the dev because it didnt work, its not that the procedure doesnt work, it just didnt work for you...simply search for another method and try again.and you will succeed.
i was going to post some of the methods but dont have permission from the devs to do so, so for now youll have to search for the precedures yourself. if or when i do get permission ill edit this thread or post the link in order to help yo on your way,,,ehhh for now itll be good practice for using the search window.
method 1.
hhttp://www.gadgetsdna.com/how-to-root-htc-hero-cdma-stock-android-2-1/3628/
The HTC Hero 2.1 exploit is based on the EVO rooting method. Rooting HTC Hero Android phone provides full access to its system files allowing you to modify the phone’s firmware and install third party apps, themes and custom ROMs. You can then spruce up your HTC Hero handset with number of third party applications.
How to Root Sprint’s 2.27.651.5 Release for CDMA Hero (Stock Android 2.1)
Note: If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
Step 1: Download the Android SDK.
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.33 here. Run the installer, and reboot your computer when it is finished. Skip to step 4 once rebooted.
Step 4: Download the hero-root.zip. This zip contains everything you need to root your Hero.
(md5: c6e5058ed14f71c68fb099e10be142fb)
Step 5: Extract the 3 files inside hero-root.zip to the C:\android-sdk-windows\tools folder on your computer.
Step 6: Make sure USB Debugging is ON (checked) on your Hero. Navigate to Settings > Applications > Development > and make sure it is checked
Step 7: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is “Charge Only”, not “Disk Drive” or else this won’t work. You may restart your comuter when prompted to do so.
Step 8: Open a Command Prompt window by clicking the Start button and typing cmd into the search box and pressing enter. Alternatively, navigate to Start Menu > All Programs > Accessories > Command Prompt
Step 9: You enter the commands followed by pressing ENTER, one code at a time.
1 cd C:\android-sdk-windows\tools
You should now see C:\android-sdk-windows\tools>
Now type
adb devices
You will now notice your HTC Hero phone’s serial number. If you get “device not found” error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging on your phone. Continue on once you get the proper phone serial output.
You will now push the files needed to gain root to your sdcard in your phone with these following commands one by one:
adb push unrevoked /sdcard
adb push recovery.img /sdcard
adb push boot-patched.zip /sdcard
Now we run the exploit. Be patient, this may take up to 40 seconds.
adb shell
sh /sdcard/unrevoked
You should now see output that says this:
UNREVOKED
============================================================ unrEVOked: root for HTC evo and hero (http://unrevoked.com)
Now, on your phone, go to your app tray, and you will see that the Superuser Permissions app is in it, which is only possible on rooted devices.
Open the Superuser Permissions app. You will see a blank screen.
In the Command Prompt on your computer, type:
A prompt will appear on your Hero asking you to give /system/bin/sh privileges. Click Allow.
Go back to your command prompt, and you should see
$ su su #
Now Type
flash_image recovery /sdcard/recovery.img
Flashing the recovery may take many seconds to complete. Wait until the # symbol returns to proceed.
You should now see
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
#
This means it was a successful flash.
Now type
reboot recovery
Your phone will now boot to the custom recovery image you just flashed. In the Recovery Menu on your phone, choose the option:
Flash zip from sdcard
Then Select
boot-patched.zip
and press the Home button to apply. Once Recovery says “Install from sdcard complete” select “Reboot system now” from the menu.
Voila!! You now have full root access on HTC Hero 2.1!
Thanks to the guys at xda-developers and gadgetsdna
or, you can try regaw's one click root method. you can find it here on Xda, just use the search window,,,it's easy
both of these methods have worked well for me in the past, im sure one of them WILL work for you
-----------------------------------------------------------------------------
Flashing a ROM (from clockworkMod)
this is the method i use and i "never" have any problems
download the ROM of your choosing and move to the root of your sdcard
follow the devs instruction for installation which should be something like this;
1. do a nandroid backup
2. reboot into recovery
3. wipe data
4. wipe cashe
5. choose advanced, wipe dalvik
***OPTIONAL***
6. choose mounts and storage
7. format system
8. format data
9. formatcashe
10. go back. and choose install zip from sd card
11. choose, choose zip from sd card
12. find the rom you want to flash and choose yes
13. when its through flashing choose install zip from sd card
14. find the gapps you want to flash and choose yes
when its through with the flash the screen will return to the main menu and choose reboot system
the first boot will take a little longer than usual this is normal. setup your google s#@ts as usual and enjoy your new ROM.
follow these instructions and you shouldnt have any problems, if you do, go back to the thread you downloaded from post a reply to report it to the dev so they know theres a problem and they can determine if its a problem with the rom, a problem with the way you flashed or a problem with your system.
15. "ONCE AGAIN" most importantly, be grateful to the devs, at least say thank you and hit the thanks button, and donate if you can.
these individuals work very hard at what they do here to provide you with the information you need to do what you want to do with your HEROC.
say thanks,,,its not that difficult.
-----------------------------------------------------------------------------
themeing your new ROM
1. make sure the theme you choose is compatable with the rom you have flashed
2. since alot of the themes have a different procedure for installation,"READ AND FOLLOW THE DEVS INSTRUCTIONS"(sorry for the caps)
they are there for a reason.
-----------------------------------------------------------------------------
boot animations
1. Put the zip file in your tools folder from the android-sdk-windows
2. Load up Command Prompt (cmd) and go to your tools directory inside the android-sdk-windows folder
3. Load up your phone into recovery and mount /system
4. Type in command prompt
adb remount
adb push bootanimation.zip /system/media
adb reboot
or (compliments of user7618)
Boot animations are easier to change by sliding the .zip into /system/media or /data/local. That way, there is no need for adb commands, just a file explorer like root explorer. Make sure that it is named bootanimation.zip.
-----------------------------------------------------------------------------
Flashing a different recovery image
cd C:\android-sdk-windows\tools...got
cd C:\android-sdk-windows\tools>adb devices...got
(recognized phone)>>>>>
cd C:\android-sdk-windows\tools>adb shell
#flash_recovery image /sdcard/recovery-clockwork-4.0.0.2-heroc-20110611.img (enter)
mtd: successfully bla bla bla
#reboot....
or,,,
[edit] Method I
Flash recovery using: ADB
NOTE: This method will work while you are booting into the current recovery on the phone.
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.Copy the recovery.img to root of the SD card.
3.Boot the phone into recovery.
4.Open command prompt, cd to the Android SDK directory & type the following commands:
adb shell
mount /sdcard
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
5.Your phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
[edit] Method II
Flash recovery using: RomManager
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.On the SD card, go to /clockworkmod/download/koush.tandtgaming.com/recoveries.
3.Rename the old image there named recovery-clockwork-2.5.0.1-heroc.img to recovery-clockwork-2.5.0.1-xxx.img.
4.Move, then rename, the recovery.img you downloaded to recovery-clockwork-2.5.0.1-heroc.img.
5.Open RomManager and press Flash ClockworkMod Recovery and reboot the phone to recovery, you should see the orange text.
[edit] Method III
Flash recovery using: Terminal Emulator Note: Requires s-off, otherwise you'll recieve "out of memory" errors.
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.Move recovery.img to root of the SD card.
3.Open the Terminal Emulator on the phone & type the following commands:
4.:
su
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
5.The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
[edit] Method IV
Flash recovery using: H-Boot/S-Off Only HeroC Only
See S-Off for CDMA Hero if you are unsure what S-OFF is.
1.Download HERCIMG.zip
Newest Download: (version 3.0.5) HERCIMG.zip <--Updated 01212011
md5: 6dcd265a51cc7090824d7f9f889b370b
Alternate Download: (version 2.5.0.7) HERCIMG_clockwork-2.5.0.7 <--Updated 02-07-2011
md5: 0a367eb1d4445c72f8022769f7edc9dd
2.Move HERCIMG.zip to root of the SD card. Make sure the file is named HERCIMG.zip or H-Boot will not recognize it.
3.Power off the phone.
4.Hold the Volume Down & Power' button until the phone boots into the bootloader.
5.Wait for bootloader to scan and find HERCIMG.zip.
6.Press action to install.
7.The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
Retrieved from "http://romrepo.info/wiki/index.php?title=Flash_the_ClockworkMod_Recovery"
-----------------------------------------------------------------------------
Change sprint insignia (ON AOSP) to whatever you want
1. Download eri.zip
2. Unzip the file to wherever you please.
3. Right click on eri.xml and choose "Open with Notepad"
4. Once you open the file you will see "Sprint" in the 5th line.
5. Delete Sprint and place whatever you would like in it's place. I believe you have up to 16 spaces to work with if need be.
6. Save the file with an .xml extension. Important: Make sure it is eri.xml and not eri.xml.txt. This will cause issues.
7. Place the eri.xml in your /androidsdk/tools directory.
8. Pull up your Command Promt/Terminal/Etc
9. CD to your /androidsdk/tools directory and:
adb remount
adb push eri.xml /data/eri.xml
adb reboot
or, (thanks to user 7618 )
I threw together a simple app to change the Carrier Name in the status bar/lockscreen to whatever you want since my alot of people seem to ask how to change it. Feel free to use it. Tested on Incredible and Eris. Dev's feel free to thow it your roms if you want. No ads and free just a simple tool to change the text. Thanks to the great Eris community.
Currently only works for AOSP roms such as cyanogenmod.
V1.3
While trouble shooting some radio issues on a rom I realized there's no need to reboot the phone to apply the new carrier name. I only needed to cycle the radio so I changed the app to toggle airplane mode on and then back off after you input your text so the change should take place immediately. This should make it a little easier to test and try different things or just change it more often.
I also added some shortcut buttons at the bottom to quickly add the text for the ", < and > signs so you don't have to type it all out. Only tested this with cm7 but should still work with any rom's it worked with before. Again thanks to Psiphon for pointing these symbol fixes out.
http://www.multiupload.com/RO6RZUUL16
V1.2
Fix for phones that don't already have an eri.xml file there
Added version number to bottom of screen so people can be sure what version they are running.
http://www.androidphiles.com/files/g.../ccname1.2.apk
V1.1
Fixed force closes when using symbols.
You can now use symbols except for double quotes. Apostrophe (single quote) seems to work fine.
Some usefull info if you want to use quotes....
Originally Posted by Psiphon
You can use special characters like the quotation marks and greater/less than signs by using entity references (either using an entity name or number):
" (quotation mark) use "
< (less than sign) use either < or <
> (greater than sign) use either > or >
I hope this helps!
Added Toast popup to let you know the name has been set.
If reboot button does not reboot phone just reboot the phone manually
http://www.androidphiles.com/files/g.../ccname1.1.apk
This app does one thing. It takes the input text you type and creates and eri.xml file and puts it in data/ folder on your phone. Then you can reboot for change to take effect. You can uninstall the app after you change it if you want or you can leave it on there(it's pretty small) in case you like to switch it every now and then. If you flash a new rom you will have to rerun the app.
-----------------------------------------------------------------------------
hopefully there will be more info in the future to add to this thread that will make things easier for everyone all around.
-----------------------------------------------------------------------------
***TO ALL DEVS AND OTHER MEMBERS*** i myself cant thank you enough for the help and advice ive recieved in the past, if you might hace any information you feel would be helpful to this thread please feel free to PM it to me and ill see that i edit this post with your procedures. and ofcourse your names will be added to a list of thanks at the bottom of the post,,,Thanks again,
THANX FOR THEIR HELP TO ME IN THE PAST;
flipz
coffeehandle
MattCrystal
laie1472
user7618
PMGRANDS
kushdeck
bierce22
conap
psiphon
kifno(aspentree)
-----------------------------------------------------------------------------
all of the information i have provided here has been compiled from Devs and other membes in order to assist new memberslike myself , and to help the devs and senior members so they dont have to keep answering the same questions again and again.
*** i f you want to thank someone, thank them for passing on their knowlege to me as im passing it on to you***
enjoy,,,
please dont double post
Nice beginners guide.
-----
3vo. That is all that needs be said.
Nice beginners guide.
Also, an easier way to change the carrier banner:
http://forum.xda-developers.com/showthread.php?t=960099
Instead of all that goofy crap with files and whatnot.
Boot animations are easier to change by sliding the .zip into /system/media or /data/local. That way, there is no need for adb commands, just a file explorer like root explorer. Make sure that it is named bootanimation.zip.
-----
3vo. That is all that needs be said.
Thanks man ill keerp adding, i really hope this helps some folks
Kudos. Good guide.
#Root/Hack-Mod_Always*
Also we dont talk about "he who must not be named" around here so you might want to take that out of the credits.
lai and user know who im talking about lol.
Uhhhhh,,,Ooops. My bad....sorry bout that guys.
ha lol i was just kidding but seriously that guy went bannanas and had a severe case of schizophrenia lmao.
lol, i hear ya man, i feel credits given where credits due, but on the other hand,,,,aw well you know what i was gonna say
Yeah, dude was crackers, but if he helped you, then he helped you. I'd leave him in there, personally.
-----
3vo. That is all that needs be said.
Yup agreed. A if he helped he helped that's just how it is. Like the guy or not.
#Root/Hack-Mod_Always*
cool guys i do feel the same way, but dont wanna stir any bees nests either, ill put it back in but we'll just overlook it. thanx for understanding