Related
Apologies for this stupid question resulting from a stupid mistake. Hoping somebody will be able to walk me through getting out of this.
I successfully rooted my sprint hero, then loaded modaco 3.0 (yes now I know that was bad). On reboot, the phone hangs on the black htc screen, and will respond to nothing.
The only thing I've been able to do is remove the battery, then turn it on in recovery mode. There, I did a wipe data/restore factory setting. Then I rebooted - and got the same boot screen, same problem.
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
When I try to restore, I get these:
(bart) error: run bart via adb
(nandroid) can't open file
Please help! I am out of ideas. Thanks very much in advance.
you'll probably have to take it back to the very beginning......
Get the Sprint RUU stock rom (a couple of posts below this one) and run that
then re-root your hero
Flash one of the roms ON THIS BOARD ONLY!!! Any other Hero rom is meant for the GSM version so it will give you the same headache again.
thanks
Thanks for the quick response! I'll try that.
Hmm, not looking good here. When I tried to install the stock hero RUU I got this error:
no signature
verification failed
which I presume is related to the htc sync requirement for that rom in the unrooting procedure that I did earlier.
Any idea for working around that?
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
david.danaan said:
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
Click to expand...
Click to collapse
Don't use 1.1, grab a later one.
Which recovery? 1.5.x won't let you go back to the main menu without disabling USB-MS again... I don't remember what 1.2.3 did. If worse comes to worst, reboot the phone after copying the file.
gu1dry said:
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
Click to expand...
Click to collapse
Yes, that's the one.
Using recovery 1.5.1. I can try a later rom, see if that works. I think I downloaded 1.3.
So first off yes, you aren't booting past the HTC screen because you flashed the wrong rom. However you aren't bricked. It's almost impossible to do once you're rooted and have RA's recovery installed unless you flash radios and stuff which you shouldn't.
Explanations for your other problems:
1. RUU doesn't work on the phones that are coming from the factory with 1.56. http://geekfor.me/news/sprint-ruu-fails/
There is a possible work-around but it's pretty detailed and I haven't gotten it to work. But you don't need to RUU if you can get in to RA.
2) (nandroid) can't open file is likely caused by RA 1.5.1. It had a bug that corrupted the backups. 1.5.2 is out. But for now don't worry about that cause your backup already sounds corrupted, nothing you can do.
3) can't open /sdcard/update.zip (bad). To me that sounds like your update was just corrupted.
How to fix it:
1. Boot in to recovery. With phone powered off hold your home button and then power.
2. Download fresh rom from http://geekfor.me/new-release/fresh-rom-1-0/ (what can I say... I'm partial. )
3. Within RA enable USB toggle and copy fresh rom to the root of your sdcard. Don't worry about renaming it to update.zip
4. Disable usb toggle. Go to flash zip from SD and choose fresh. That should be it. If you get the error saying the zip is bad then compare your downloaded copy with the md5 hash check on the download page (google it if you aren't sure how). If it matches then it's possible you have a bad sdcard. If it doesn't match then your downloads are crappy.
working!
Got it working by flashing the modaco v1.3a - must have been a bad update.zip before like you said. Thank you so much for the help and clear explanations, I was really worried I had bricked it.
David, now that it is working, I would recommend updating your recovery to 1.5.2.
I just want to thank everyone that posted to this reply I honestly thought that I bricked my phone and thank to you guys I was able to revive it. Thank you again.
Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.
This means you are on the leaked version now and there is nothing that can be done as of right now.
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.
sounds like you got a bad pb001.img file.
ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?
nevermind addressed my issue
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.
af man...seriously!
out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!
Hey guys.
I've been attempting this all morning and so far I've had no luck. I have a VodafoneAU Legend which I updated to the official 2.2 yesterday. But now I want to try root.
I've been trying to follow the HBOOT 1.01 guide but there's a few problems. First, I cannot connect to the phone with adb unless it's in htc sync mode. No other mode will work. So when it's time to copy testimage.zip to the card I have to change from sync mode to disk mode, whereby adb loses it's connection. What do I do about this? Is it a driver problem (in Win7 here) or something else?
Thanks,
Dave.
Ok, the first problem were drivers.
Now I can't finish the second guide. When I try using clockwork to install the firmware.zip, the phone just boots to the red triangle. What do I have to do?
Dave.
So I pressed the up button/power combo at the red triangle and get the Android system recovery. Selecting "apply update.zip" says it can't verify. What do I do? Is this guide for my phone or do I need to follow something else?
I don't understand this guys. Anyone help? I'm thinking since this is a step to root the phone, I'm not actually rooted yet so I can't use the clockworkmod? Then what is the guide for? The guides at unlockr don't mention what firmware/hboot they work for so I'm not keen to try them yet.
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
whitetigerdk said:
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
Click to expand...
Click to collapse
But isn't that what Rom Manager does? Download the update.zip then run it? Man this is getting even harder to understand.
Edit: And this is left out of the HBOOT 1.01 guide because.....????? When I work this out I'll write a PROPPER guide, lol.
Just checked and update.zip is on the card.
So which part of the guide am I getting wrong?
Decided to reinstall phone with the official froyo release and am now ready to try this again. Is there anyone that will walk me through the process? I will write a complete guide if the "gotchas" are still there.
i feel for you ... hope you get it fixed... thats one of the reason i havent dared messing with the phone because i've seen a few post like yours where something didnt go quite as described... for whatever reason... and im sure the answer is out there but just not within the guide instructions... i guess there is no way to gather all gotchas because there are so many environment variables...
good luck
and please share your technique
Just saw gobczak's thread in the developer forum having similar troubles with Vodafone UK phone, getting the red triangle at reboot. I'll keep an eye on his thread and see how he goes with it.
Did you run the stage1 and stage2 bats while in recovery?
dezzadk said:
Did you run the stage1 and stage2 bats while in recovery?
Click to expand...
Click to collapse
No because the guide didn't say to.
The thing is it seems I'm only stuck on the part where the firmware.zip file has to be flashed. The guide says to use clockworkmod for this. But when I try installing the clockworkmod recovery it gives some file verification error. Isn't there ways to do this via the pc, either through those batch files, adb etc? Or will that fake-flash update.zip file work?
jabbado said:
No because the guide didn't say to.
Click to expand...
Click to collapse
As I just posted on the other forum, I think you need to skip that step in guide 2 and go straight onto guide 3 after you have flashed the LEGEIMG.zip, rebooted, and then removed LEGEIMG.zip from the SD card.
Guys I've got to the point of downgrading to 1.31. But when I run the first batch file it just hangs at the "Writing zip" part, with the htc logo on the screen. Is there any way to fix this?
Can someone please explain this part of the guide:
Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard.
Click to expand...
Click to collapse
Ok, so I don't get an error. I get nothing. The phone just boots to the fastboot screen. If I press the power button it goes to the hboot screen and I can see the messages of loading LEGEIMG.zip. But the guide doesn't say to press anything.
So should I or shouldn't I press the power button? Also, if I try making the goldcard again, at which point in the guide do I start from again? The entire process or just copying LEGEIMG.zip to card then rebooting phone? I mean, will all the other things like flashing misc1-2.img still be there?
Guys I finally got this working.
The first problem was with the goldcards. For whatever reason formatting them with the win7 format tool just wouldn't work. I had to use the command-line format tool, setting the block size etc manually.
The second problem was the unnecessary steps in the guide. A few people helped me out with this (namely blackbart at the Aus Whirlpool forum), but basically in the second step you can stop after flashing the LEGEIMG.zip. The updating froyo part isn't needed - for my phone anyway.
Then when running the batch files in the third part, for whatever reason the first batch would keep hanging at 'writing zip...' and I needed to remove the battery to unfreeze the phone. flannigan, also from the Aus Whirlpool forums suggested to just go on to the second batch file. This worked!
So my Legend is now finally a true Legend
Anyway, thanks for the help everyone - couldn't have done this by myself.
Dave
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 / Stock Froyo to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Sent from my HTC Legend using XDA App
EpicSauce said:
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Click to expand...
Click to collapse
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Sounds good! Happy to help and add my 20c worth along the way. The existing guide has got the meaty bits, a new guide would cull the stuff not relevant, help fill in the gaps and alert to the pitfalls we've fallen into.
jabbado said:
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Click to expand...
Click to collapse
I agree... i've done my reading since june of last year but then didnt check for another 4 months... and so many how to's pop up with various ways of doing it depeding on the situation... a lot of those howtos were consolidated howtos which sometimes make intermediate steps unenecessary (may be in some cases causes more head aches since it didnt take into considerations on newer version of hboots...etc)... an updated how to will be much appreciated...
And you're right the most important pre requirement is to have a safety net ... so starting with how to create a back up in case you screw it up is a must!
but im glad it worked out for you!
As the thread title states, I'm looking for info on the steps to root my stock MT4g, and install the new ROM that's floating around. I'm pretty technically capable, but the info I've found looks slightly dated. When I was active in the iPhone jailbreak scene, using old directions could brick a phone pretty easy, or prevent future jailbreaking. I haven't kept up with this scene enough to be able to know what's dated and what isn't.
This is my current plan, please correct it if I'm missing anything or have it wrong.
(based on wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide)
I've got ADB going
I need a backup solution for app data right? What's my best option here?
Once backed up, I plan to install busybox, Superuser package & Temporary Root package via ADB
Use gfree to make that root permanent
Install ClockworkMod recovery
Reboot into recovery, and install faux123's ROM
Does that sound correct, and did I skip anything? Any input at all is welcome, I'd like to stand tall on the backs of giants.
There are two popular methods floating around
You can either use the Root.sh method [ Found Here ]
Or the ./gfree method [ Found here ]
Either method will work perfectly. I've used both and can say with confidence they work.
The Cyanogen method can be goofy at times. I've see alot of people say they cannot get it working for them. I'd rock one of the two above. You shouldn't have a problem either way.
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
For backing up apps and data, use titanium backup. for backing up your whole phone, use the backup feature in clockworkmod recovery after you've flashed it via rom manager after permarooting.
lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
The best way to back up your Data and Applications is like mentioned above is Titanium Backup. The free version will work well but i recommend the paid one.
as far as a snap shot of the entire ROM incase you want to go back to it. reboot into recovery > backup/restore > backup. And it will do the rest.
Well I made it halfway there, but didn't nail the whole thing. I've got permanent root access (yay) now, and was able to make backups via Titanium. I then rebooted the phone into "recovery" using the ROM Manager from Clockwork. First boot had a red exclamation mark, I unplugged the handset from the USB and tried a second time. After that, I was greeted with the Orange and black interface, and selected "restore to factory". I then started searching for the cache clearing, which changed verbage between 3.x and 4.x releases of Clockwork. After exploring the menus a little, the phone reboots itself from this screen. My blood-pressure goes up, and I worry my toy just became a b-word. Not all was lost though, and the phone happily booted into the stock t-mobile welcome wizard.
I still have superUser installed, and still have root (S=OFF I guess?). I install ROM Manager again, and do the "Flash ClockworkMod Recovery" (which now shows both current and latest recovery as ClockworkMod 3.0.2.4). When I choose Reboot into Recovery however, it reboots back to the MyTouch 4G logo screen (non-animated one), and hangs. After some reading I tried to force recovery boot via ADB, which produced the same result as the soft reset from ROM Manager. After that I tried doing it the manual way with holding the volume button, which launched me into what I believe is a stock recovery console (white with colored options, uses vol +/- and power to navigate). Choosing "recovery" from that screen *also* produces the white logo screen hang.
So my question now is, in it's current state; how can I get to the Clockwork recovery again? From there I bet installing the image will be easy street, but I believe I'm stuck for now.
Side-note: the phone functions fine on regular boots and pure vanilla mode; I just don't want to stop here when I'm pretty close to my 2.3 goal
Well good news and bad news. I was able to get Clockwork going by reverting it to 3.0.0.5 and just using that version. Was able to install ROMs, tested a few. Phone started freezing after/during installing packages. Started the clear cache/install ROM process, ran into this:
Code:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
http://forum.xda-developers.com/showthread.php?p=14389074
Totally stuck at boot screen, but able to get into Clockwork. All ROM zips off the sdcard produce this or an invalid zip error.
Other guy smight tell you what a status 7 might be, but with the flurry of flashing youre doing, you may have gotten some corruption on your sd
try formatting your sd card in the pc, or use another one so you dont have to back everything up on this one. put one rom zip on the root and see if that helps
also, i would make super sure you wiped/factory resetted every possible data/cache in CWM before flashing the zip
lastly, i would md5 test the download to make sure it matches the web page. Plus, after it's transferred to the cleanly-formetted sd, check it again either thru adb, or do the trans on the pc using an sdcard reader and check it once it's on the sdcard, then pop it into back your phone.
good luck
Thanks a ton for the uber fast reply. When I format on the PC, what format do I use, or is there a specific tool to properly format it for the phone?
When I'm wiping /data it's taking forever and I get the following message back:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log/last_log
E:Can't open /cache/recovery/log/last_log
Don't have an adapter at the office today for the sdcard, but I guess I can just grab a new one at lunch? All it would need is a fresh format then the .zip of the ROM in question at the root?
Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.
Jack_R1 said:
Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.
Click to expand...
Click to collapse
So I use the same PD15IMG.zip i did to start, flash it using Clockwork, then start the root > rom process over? I think that it currently tells me it can't find that zip anymore on the white screen pre console, is that expected? I just xfer it to the sdcard prior to fixing?
Yes, that's the right procedure. Move it to the card and start from scratch. Beware not to use the newer Panache/MT4G Gingerbread RUU, otherwise you'll be left with no way to root, or at least harder way.
Ok, so I didn't have a PD15IMG.zip to begin with, I see this thread:
http://forum.xda-developers.com/showthread.php?t=1059347
and that's proper that I'm flashing the radio itself for this process? Which of those images do I want to grab? I always like to double check when I read warnings that are pretty specific about bricking the device
No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.
acsi007 said:
No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.
Click to expand...
Click to collapse
Jesus, glad I asked before getting in there.
So I was going to offer you a beer sometime, I think I owe you a few rounds at this point...
Edit: this one right http://forum.xda-developers.com/showthread.php?t=924923 ?
Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...
acsi007 said:
Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...
Click to expand...
Click to collapse
I rooted gfree originally, and think I may be in the bad place
Fail-PU errors running the update from pd15img. Do I have any options at this point? I bought the phone from Wirefly.com, and since I can't get a recovery image going, I may be fuct here on a return eh?
looks like i'm moving to: http://forum.xda-developers.com/showthread.php?p=14487111#post14487111
Good luck Lars. Let us know that they did and if you had to pay.
I notices a few users have mentioned that they're dealing with trying to restore or unbrick their Continuum after flashing incompatible kernels and other problems.
I made this backup immediately after I got root, before I did anything else, to make absolutely sure I wouldn't be SOL if anything went awry. I've made absolutely certain this works, by unzipping and flashing on my own Continuum prior to uploading. It contains the system, recovery, and kernel partitions.
This file is also helpful if you need to get back to stock for warranty purposes, in which case you can manually un-root by using your favorite file explorer (I happen to prefer ES File Explorer), grant root permissions, mount system as rw, then manually delete SuperUser from /system/apps, su from /system/bin, and busybox from /systen/xbin. I hope this helps some of you who have been stuck.
You don't need to be rooted to flash this. Simply unzip, flash the .tar.md5, and you're golden. If you end up in restore mode after flashing, you probably need to do a hard reset, but this is unlikely as I tested it by flashing this a few times after installing various programs from the Market and never had to do a hard reset.
Don't forget to put your phone in Download mode by removing the battery, then holding the vol down button while inserting the usb cable. Good luck!
http://www.mediafire.com/?a897dbakz4j7k4f
Thanks for this. I had been messing around with the phone. I was able to get it back to stock.
Kay I try to flash this and it's telling me it's an invalid image type
Never mind, I got it. Thanks
Not a problem, glad I could help!
My phone was soft-bricked. This worked like a charm. Thank you so much!
I ran this and everything passed then when i boot up the phone with animations and sound after the animated verizonwireless logo is up for a while; everything goes black.
any suggestions? never mind I had to do a wipe then it worked
kingtuk1 said:
I ran this and everything passed then when i boot up the phone with animations and sound after the animated verizonwireless logo is up for a while; everything goes black.
any suggestions? never mind I had to do a wipe then it worked
Click to expand...
Click to collapse
Yup, gotta wipe! At first it's so easy to forget this step. When you get to customizing your installation, you'll get to used to having to wipe it'll become second nature!
I'm so glad to hear this is coming in handy for you all! Now that you got this done, get yourself froyo, courtesy of imnuts: http://forum.xda-developers.com/showthread.php?t=1197415
Ok after having installed EC03 Froyo via imnuts's thread. Everything was going fine except for some bugs here and there. Fast forward a couple weeks later and I try to fix those bugs by installing a stock odin rom via torque's thread (seems so foolish now that I look back on it). Which brings me to today and my bricked Continuum.
Well to explain further I tried to install the odin Rom only to receive a FAIL in the end (Selected the md5 file through the PDA option and proceeded to flash). Disconnected afterwards only to find out I can't even get the Samsung logo to show up or the phone to charge, but the phone will still go into download mode.
And this leads me to this thread with the same outcome. I've tried flashing this eclair? image only to end up with the fail message again. After the recovery.bin stage it just says "Complete(write) operation failed." Any help with this matter would be appreciated.
Edit: After some searching, gonna try it with imnuts' DL17 image. Will post results.
Edit2: No luck with that either. Guess I'll just wait until the Bionic gets released, but for now I'll have to dig up my dumbphone.
Native89 said:
Ok after having installed EC03 Froyo via imnuts's thread. Everything was going fine except for some bugs here and there. Fast forward a couple weeks later and I try to fix those bugs by installing a stock odin rom via torque's thread (seems so foolish now that I look back on it). Which brings me to today and my bricked Continuum.
Well to explain further I tried to install the odin Rom only to receive a FAIL in the end (Selected the md5 file through the PDA option and proceeded to flash). Disconnected afterwards only to find out I can't even get the Samsung logo to show up or the phone to charge, but the phone will still go into download mode.
And this leads me to this thread with the same outcome. I've tried flashing this eclair? image only to end up with the fail message again. After the recovery.bin stage it just says "Complete(write) operation failed." Any help with this matter would be appreciated.
Edit: After some searching, gonna try it with imnuts' DL17 image. Will post results.
Edit2: No luck with that either. Guess I'll just wait until the Bionic gets released, but for now I'll have to dig up my dumbphone.
Click to expand...
Click to collapse
Read the OP from pastorbennett here: http://forum.xda-developers.com/showthread.php?t=1203597 and try the unbrick process. You can do a search for pastorbennett and trailblazer. Both have posted "recovery processes", or at least links to others that have posted recovery processes. They've saved my butt a couple of times... Except on my first phone that wouldn't go into DL or Recovery Mode. It would just flash the Samsung logo, over, and over, and over again... That happened before pastorbennett posted the unbrick info. Oh well, Verizon replaced it under the hardware warranty. Thankfully.
Looks like I didn't search hard enough.
Thanks for the link Moon. I will be trying this ASAP.
Hit a little bit of a snag trying to get it to work. It told me to install drivers for my device, however my Phone does not show up in the dropbox and the only related thing I can find is "Gadget Serial".
I've tried uninstalling the drivers, but Win7 is being a fool and automatically installing drivers for me.
Does anyone know why i get a 'FAILED' after trying to flash this with Odin? My phone is soft-bricked btw.
Native89 said:
Looks like I didn't search hard enough.
Thanks for the link Moon. I will be trying this ASAP.
Hit a little bit of a snag trying to get it to work. It told me to install drivers for my device, however my Phone does not show up in the dropbox and the only related thing I can find is "Gadget Serial".
I've tried uninstalling the drivers, but Win7 is being a fool and automatically installing drivers for me.
Click to expand...
Click to collapse
Okay, if you can, grab a different computer (either Windows XP or Windows 7) and install the samsung drivers from this post: http://forum.xda-developers.com/show....php?t=1203597. The hint here with ANY Windows computer is to install the device drivers FIRST! (I've been a system administrator for about 20 years.) Then plug in the hardware. It usually makes the installations go MUCH smoother.
If you have to use your computer, try installing the Samsung drivers first, then plug the phone in.
zzir said:
Does anyone know why i get a 'FAILED' after trying to flash this with Odin? My phone is soft-bricked btw.
Click to expand...
Click to collapse
The key to odin seems to be this:
1. Start odin.
2. Click the PDA button and select the odin TAR or MD5 file. (You can only do one. Not both.)
3. Make sure the phone is not plugged into the computer.
4. Make doubly sure the phone is not plugged into the computer.
5. Put your phone into download mode. (With the phone off, hold the Volume Down button and turn the phone on.)
6. Then plug the phone into the computer.
7. Start the odin flash and you should be good to go. Also, before unplugging the phone, make sure it says either success or failed. If it doesn't say anything, or says loading (or something like that), WALK AWAY! Go get yourself a cup of coffee, a soda, a nice cup of tea... Something. I recommend waiting at least 10 minutes. If the progress bar has not moved, in that time, okay, then pull the cable and the battery and start again.
I tried to do this, but when it boots into recovery mode, it says update.zip is gone. Any ideas why this might be happening? Also if it's like this, will Verizon take it back within the 14 day return policy without charging me anything?
Tarheel487 said:
I tried to do this, but when it boots into recovery mode, it says update.zip is gone. Any ideas why this might be happening? Also if it's like this, will Verizon take it back within the 14 day return policy without charging me anything?
Click to expand...
Click to collapse
Did you flash the CWM Recovery in Odin? (cwm_recovery_test4_adryn.tar) Can be found here if not http://forum.xda-developers.com/showthread.php?t=1230072
is it possible to flash this with heimdall or only odin?
ntien said:
is it possible to flash this with heimdall or only odin?
Click to expand...
Click to collapse
I don't know, however, pastorbennett posted this http://forum.xda-developers.com/showpost.php?p=16600453&postcount=29. It might help? I use Linux at home to build most of this stuff, then use my wife's Windoze machine to flash. It just seemed easier.
Yes, you can use heimdall, you just need to extract this .tar and put the extracted files in the corresponding location in heimdall xD
Sent from my SCH-I400 using xda premium
yeah i saw that but in heimdall 1.3 the UI is different. i don't know where to put any of the stuff. i have the .tar but i dont know where to put the other stuff. here's a screenshot