[Q] Flashing PB00IMG - Droid Eris Q&A, Help & Troubleshooting

Hey everyone, just a quick question that I hope can be answered fairly simply. I have an Eris running Evil Eris 3.0 that I'd like to flash back to 2.1 (via PB00IMG). I know there's a tutorial, but I'm not very good with SDK. I downloaded the SDK and put the misc.img and flash files in the SDK/tools folder but I have no idea where to go from there. I'm trying to get my phone replaced, but I doubt Verizon would like me having anything other than the official releases on the phone, lol. Any help would be greatly appreciated! And I feel inclined to say, "sorry for being a n00b lololol," but I feel that's a little cliché. Thanks guys.

All you have to do is boot into recovery (hold volume up and turn the phone on) reset the phone to defaults and flash the zip file.

Related

[Q] shed a little (up to date) light on my nightmare of a new phone.

O.K. So my baby (HTC Dinc) was lost in a bunch of snow. I was running android 2.2 with scence UI 2.0 and never had any trouble finding new and exciting roms that were just a lot of fun to play with. So after doing little homwork and having the Verizon guy talk up this Samsung I made my next $200 plunge into my new favorite hobby. However I was not aware that this phones hacking community was so... confusing. So heres where im sitting I ran FascinateRoot_v02 which is a 1 click root and boom i get Superuser. Completely psyched to get a rom on that isn't plagued by Verizon advertisements and Bing Bull$#!t, alas i am stuck. rom manager went in and installed ClockworkMod 3.0.0.8 as its recovery. I download the SuperDark1.1-D101 and go to install it through ROM manager and nothing happens. then i realized that i must not have the right recovery. I am lost and hating the frustrations that are fallowing the events that led to me getting this phone. I know the hardware is good and all but Big Red and Bing (WTF is this doing on a google OS Phone) have turned the wonderful SuperAMOLED screen into an eyesore.
Here's what I need.
1.) someone to post what the OTA update did to my phone. (USB not recognized by PC)
2.) Someone to explain in very small words how to ROM this phone with the latest info.
3.) Someone to explain What VOODOO and NoN-VOODOO Kernels are and the benefits of both
4.)How to install the kernels
5.) Anything that i can do to help with 2.2 because running with limited/no flash makes me feel like im playing with an iphone original with a shiny new screen.
I'm very sorry for making a new thread that i am sure has questions that have been asked before on it, but for two days i have been lost on this. Please help a guy out!!!
Droidneedzsence said:
O.K. So my baby (HTC Dinc) was lost in a bunch of snow. I was running android 2.2 with scence UI 2.0 and never had any trouble finding new and exciting roms that were just a lot of fun to play with. So after doing little homwork and having the Verizon guy talk up this Samsung I made my next $200 plunge into my new favorite hobby. However I was not aware that this phones hacking community was so... confusing. So heres where im sitting I ran FascinateRoot_v02 which is a 1 click root and boom i get Superuser. Completely psyched to get a rom on that isn't plagued by Verizon advertisements and Bing Bull$#!t, alas i am stuck. rom manager went in and installed ClockworkMod 3.0.0.8 as its recovery. I download the SuperDark1.1-D101 and go to install it through ROM manager and nothing happens. then i realized that i must not have the right recovery. I am lost and hating the frustrations that are fallowing the events that led to me getting this phone. I know the hardware is good and all but Big Red and Bing (WTF is this doing on a google OS Phone) have turned the wonderful SuperAMOLED screen into an eyesore.
Here's what I need.
1.) someone to post what the OTA update did to my phone. (USB not recognized by PC)
2.) Someone to explain in very small words how to ROM this phone with the latest info.
3.) Someone to explain What VOODOO and NoN-VOODOO Kernels are and the benefits of both
4.)How to install the kernels
5.) Anything that i can do to help with 2.2 because running with limited/no flash makes me feel like im playing with an iphone original with a shiny new screen.
I'm very sorry for making a new thread that i am sure has questions that have been asked before on it, but for two days i have been lost on this. Please help a guy out!!!
Click to expand...
Click to collapse
Your mistake was a simple one, you simply used the wrong Clockwork Recovery, the ORANGE. Most of our ROMS are not compatible with that. You need the RED Clockwork Recovery 2.x.x, if you do some searching it is all over here. Your OTA update I have no clue about because you didn't even mention it in the original post except to ask what it did. If USB isn't recognizing, reinstall the Samsung drivers, and try toggling USB debugging. You are now NON-Voodoo, your file system is stock RFS, which is slow. What Voodoo does is change your filing system to EXT4, which is must faster. This does not mean your phone will be blazing through everything. It simply means that your phone will be much faster at writing data, I have not seen one person disappointed per se in it yet, I personally use it. Overall, it will increase the performance of your phone. Kernels, you flash using the RED Clockwork Recovery, which you will find downloads of and instructions for all over this forum, it is very easy. Once you get the correct Clockwork Recovery this will be easy man, so go get that, and flash a ROM like you normally would. Have any more questions, you can reply, or IM me. EDIT: Also, get a program called Odin, which is all over this forum as well. As you read more and more, and do more things, you will see why it is very useful.
Thanks! 1 problem... I cant set it back using rom manager. How else can you fix/downgrade to 2.x.x. Also the OTA update has my phone hidden on my pc through USB conectivity and I have never used Odin. I really do appreciate the help! I hate trying to learn new setups in 2 days
Sent from my SCH-I500 using the XDA mobile application powered by Tapatalk
Droidneedzsence said:
Thanks! 1 problem... I cant set it back using rom manager. How else can you fix/downgrade to 2.x.x. Also the OTA update has my phone hidden on my pc through USB conectivity and I have never used Odin. I really do appreciate the help! I hate trying to learn new setups in 2 days
Sent from my SCH-I500 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Okay, here is Odin, attached at the bottom of my post. I am also including Clockwork Recovery, the one you need, as well as the update.zip. First you need to place Update.zip on your SDCARD. Since your pc won't recognize your phone, you can use the Dropbox program to do this. Update.zip HAS to be on the root of your SDCARD. Now, Odin is the program you want to use to Flash the cwm.tar, okay? And ONLY that .tar. Open Odin and mess with NONE of the settings, NONE. Click the PDA Button, choose cwm.tar and then click on START. Note: In the upper left hand corner, if Odin detects your phone, it will be yellow. And make sure USB debugging is enabled. So, flash cwm.tar to your phone, boot into recovery by holding BOTH of the volume keys while powering up, then in Clockwork Recovery select "Install Update.zip", it will install and you will have the RED Clockwork Recovery. THEN you go flash your ROMS and such, as for your USB problems, could be very simple, just do some Googling. Oh, and in terms of ROMS? I HIGHLY recommend Adrynalyne's SuperClean.
One thing to note since you have been having problems, and because I didn't see it mentioned above.
For odin to work (for odin to see your phone) you need to have it (your phone) in download mode.
This is made possible by pulling the battery, plugging in the phone to your PC via the STOCK usb cable (I have read non OEM cables can cause problems), and holding down the "down" button on the volume rocker while holding the power button. You should boot into download mode. Yellow Triangle as some call it...because of the giant yellow triangle on-screen....
I had a hell of a time figuring this out through the guides but once you figure it out you will have no problems.
gkirby11 said:
One thing to note since you have been having problems, and because I didn't see it mentioned above.
For odin to work (for odin to see your phone) you need to have it (your phone) in download mode.
This is made possible by pulling the battery, plugging in the phone to your PC via the STOCK usb cable (I have read non OEM cables can cause problems), and holding down the "down" button on the volume rocker while holding the power button. You should boot into download mode. Yellow Triangle as some call it...because of the giant yellow triangle on-screen....
I had a hell of a time figuring this out through the guides but once you figure it out you will have no problems.
Click to expand...
Click to collapse
I KNEW I forgot something, thank you for adding that. I have so much going on but did not want to leave the guy hanging I rushed through the explanation.
There were some issues with the "stock" versions of CWM, and our devs have touched it up to work with our phones better. The latest "Orange" version you installed from Rom Manager uses a new method for installing updates/ROMs (Edify script). Almost all of the things available on these forums are still set up for the old method of installing updates/ROMs (Amend script). As a general rule of thumb, we don't update CWM through Rom Manager, and just use versions posted here. There were some compatibility improvements, but they also added Voodoo support and options.
Also, because of not using Rom Manager to update CWM, the "Install from SD Card" option in Rom Manager doesn't work. There's some kind of "*update.zip" in the clockwork folder on your SD card. If you copy the update.zip from the root of your SD card into the correct folder and rename it, the "Install from SD Card" might work. Sorry, I don't use Rom Manager anymore, so I don't have the exact names or folders.
The way a lot of people handle ROM installs is to reboot into recovery (hold volume up and volume down and power while starting up, and release only the power button when "Samsung" appears). Once you install the cwm.tar that Dread This Day posted, this method will take you straight into Clockwork Recovery. You can download ROMs from Rom Manager or directly from these forums.
Just a word of caution on Voodoo. There are some serious problems you can get yourself into if you don't know what you're doing with it. I strongly suggest you thoroughly research exactly what it does, the impacts of installing/using it, and how to properly remove it before you decide to use it.
Thanks for the info and the walkthrough. Gotta love expediant info. Ill be playing with it after I get off work. I have been using the micro usb from my Dinc so ill swap it out and see if it works.
Sent from my SCH-I500 using the XDA mobile application powered by Tapatalk
all i get from that is samsung recovery utils. lookin over the net and tried the whole emulator trick. this phone is aggravating I know its probably just me. So im going to run some tests to find out if i can get into the download mode via an cmd prompt or some such program.
In other news I FOUND MY Dinc! after a weekend of being in the snow a co-worker spoted a lighter and went to get it, at which point he found the phone under it. great news is that my case and screen protector saved it. no water damage, not even a red seal!
Edit:
The program is called terminal emulator not cmd prompt. sorry for the platform crossover.
In emulator
type in #su
agree to superuser
type in #reboot download
and done. i knew that computer class would pay off. lol next step is getting phone recognized by odin. more fun awaits...
abondon ship. htc thunderbolt is out in the next 3 weeks and im gonna be all over it. as my name infers deoid needs sense and samsung... well it has none and oit of the 5 phones ive rooted and romed this is by far the most anoying. ota updates that make a phone unrecognizable via pc and the need to run multiple programs just to get a phone to except root. no froyo in sight and... bing... they ruined a great phone by pretty much leaving it up to our devs to make it worth something. i shall miss my superamoled but not enough to birn an upgrade. thanks for the help, you guys are great, hope to see ya in the htc scene soon.
Sent from my SCH-I500 using the XDA mobile application powered by Tapatalk
In my opinion ROM Manager blows goats your better off downloading from xda and flashing in the orange clockwork
Sent from my SCH-I500 using XDA App
WhiteRocks said:
In my opinion ROM Manager blows goats your better off downloading from xda and flashing in the orange clockwork
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Most of the ROMs for the Fascinate won't work with orange clockworks. You will need the red version.
Sent from my SCH-I500 using XDA App
Sense really blows dude, I would cut my hand off before going back to buggy htc, 2.2 fascinate is way better, but to each his own...
Sent from my SCH-I500 using XDA App

[Q] Restoring everything to stock using RUU-extracted zip.

Hello.
My phone is starting to act funny, it has the quite common problem where the touch function on the bottom half of the screen stops working properly.
Since I'm going to send it in, I'd like to return everything to as close to the shipping state as possible. I don't care if I still have Clockworkmod left on it or if I make it unrootable, since I'm going to buy a new phone and sell this one when the contract runs out in a few months anyway.
I've tried searching for the info I need but there are still some things I'm unclear about.
The phone is currently running VillainMod and has ClockWorkMod installed as a bootloader. I was running CM on it until a few days ago, but I tried installing a Sense-based ROM to see if I could get the RUU .exe method to work, but it fails after the phone has rebooted and just says that it cannot update the phone. Any ideas what's causing this? (I used the file RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6.35.15.11_release_signed.exe)
So since the "official" method failed I found the rom.zip that is unpacked by the RUU program and copied it.
Here is where I'm not sure how to proceed. Should I sign the zip-file (using testsign.jar) and then do "apply update.zip" from ClockWorkMod OR should I extract the boot.img, data.img, recovery.img, system.img and radio.img files from the zip, generate a md5 file (how?) and restore it using the backup feature in Clockwork?
Or is maybe both of these ideas totally of the mark?
Any help is appreciated. Do tell if there is some more info you need.
I personally don't think you should go with that plan. I'm not a big scientist when it comes to phone development since I'm still learning. But I think you should go backwards and check what went wrong.
Edit:
I also think that the new rom might have different requirements from the previous one. Usually that causes a problem if you try to flash a rom without fitting the requirements.
No you need to rename the Rom.zip to heroimg.zip then shut down phone and reboot into hboot mode by using power and vol down

[Q] Switching back to Sense...

Ok, so here's the thing, I have a phone that's stuck with HBOOT 1.5. I used the HTC unlock and got my phone on MIUI awhile back, but the thing is, now it's gotten a bit aged and I'm kind of tired of the ROM. It's been about 4 months since then and I don't remember how to switch back to sense (I was hoping to get onto 3.5 so that I can get HTC's free dropbox space lol). I'd like to try another AOSP ROM, but I know they're all pretty unstable at this point (someone correct me if I'm wrong).
Here's the real problem though, at this point, not really remembering how I even got this thing unlocked and running, I've been reading through the forums again trying to figure out how to switch back to sense, and I've just gotten entirely confused. I'm not new to rooting/ROMing, I'm just confused by all the loops you have to jump through with HBOOT 1.5. Could anyone provide a slightly simplified, possibly even unified, set of instructions or at least point me at the right how-tos in order?
Please? I love you guys
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Sorry about that. I thought I had clicked Q&A when I came in, my bad xD
greatwithtoast said:
Ok, so here's the thing, I have a phone that's stuck with HBOOT 1.5. I used the HTC unlock and got my phone on MIUI awhile back, but the thing is, now it's gotten a bit aged and I'm kind of tired of the ROM. It's been about 4 months since then and I don't remember how to switch back to sense (I was hoping to get onto 3.5 so that I can get HTC's free dropbox space lol). I'd like to try another AOSP ROM, but I know they're all pretty unstable at this point (someone correct me if I'm wrong).
Here's the real problem though, at this point, not really remembering how I even got this thing unlocked and running, I've been reading through the forums again trying to figure out how to switch back to sense, and I've just gotten entirely confused. I'm not new to rooting/ROMing, I'm just confused by all the loops you have to jump through with HBOOT 1.5. Could anyone provide a slightly simplified, possibly even unified, set of instructions or at least point me at the right how-tos in order?
Please? I love you guys
Click to expand...
Click to collapse
there's 3 ways to flash ROMs correctly with 1.5:
1- use joekrims "flash image gui" app
2- use fastboot usb to boot recovery, then flash
3- use teamwin's new "htc dumlock" recovery tool
Thank you, but I actually was wondering if anyone could give me a bit more information than that. Let's go ahead and go back to assuming that I'm a complete noob who knows nothing other than what he just found from the first page of the forum search.
greatwithtoast said:
Thank you, but I actually was wondering if anyone could give me a bit more information than that. Let's go ahead and go back to assuming that I'm a complete noob who knows nothing other than what he just found from the first page of the forum search.
Click to expand...
Click to collapse
Fastboot method:
boot to bootloader > Select Fastboot (with your phone plugged into pc) > run cmd on computer > Change directory to where ever you tools for adb and recovery.img are (Im assuming you remember how to change directories through cmd if not goes like cd c:/(enter the folder here)) > Run fastboot command >>> Fastboot boot recovery.img > Wipe properly > Flash rom
Flash gui method:
run flash gui > select boot.img > run the program > reboot into recovery > flash rom > reboot and enjoy
Dont know the htc dumlock method yet but should be fairly simple also.

[Q] problem installing ROM after HTCDEV unlock

Okay, first let me totally come clean and admit I've been an idiot.
Secondly let me apologise for posting this in what may be entirely the wrong place, I'm needing help, challenged for time, and hoping that one of you knowledgeable people may be willing and able to give me some advice.
I've been a Cyanogen user for years (on HTC Magic), so when Vodafone UK sent me a spanking new HTC Desire S yesterday, (HBOOT – 2.00.0002), I explored it for a while then quickly wondered what it would be like running cyanogen 7.1.
Now things have changed since my happy old experimenting with nightly builds – we had twins a few months ago and time is not what it used to be. I rushed into things a bit. I unlocked the bootloader through HTCDEV then flashed CWM recovery "touch 5.8.1.5 saga". All fairly straightforward.
I then booted into recovery and attempted to flash "update-cm-7.1.0-DesireS-signed.zip"
I dare say you've spotted the foolish error already, yes, I didn't backup my current rom.
It was 2 a.m. and it was only a matter of time before one of the babies would wake up.
So now I'm stuck on the white screen of frustration.
Is it possible that the update.zip is corrupt? I downloaded it from the Cyanogen link: http://download.cyanogenmod.com/?type=stable&device=saga
but I can't seem to extract the boot.img, Winrar tells me the file is corrupt but that may be because it's not a standard windows format??
ADB is not finding the device so I can't logcat.
What should be my next step?
Can anyone suggest a reliable ROM to try instead?
You can call meanything you like for my foolishness, I'm sure you won't think of any names I haven't thought of myself – I should have left the darn thing alone if I didn't have time to do it properly.
Dead simple you total dork!
copy the boot.img from the ROM zip in windows explorer, put it in your adb folder then "fastboot flash boot boot.img"
Honestly, some people.

[Q] Help Restoring My Phone After Failed Changing Custom Rom

Hello,
I have an S-on 4g LTE unlocked with bootloader and running Viper 2.2. I've been getting those annoying update messages, so I thought I'd try a different ROM. I tried to switch to the Avatar ROM on the forums: http://forum.xda-developers.com/showthread.php?t=2207395, but I couldn't get it to take. I read somewhere that I needed to extract and load the boot.img file through ADB first, so I did that but it still didn't take. I could install the ROM, but I can't get it to boot past the "HTC: This build is for development purposes only" screen. It hangs there for a while, then the screen goes black, and eventually it loops back.
So then I decided to just go back to Viper 2.2, but that won't take. It's doing the same loop-back. I did a full backup before starting, so I tried restoring that but it made no difference. I thought maybe I needed to do the adb boot.img thing again using the boot.img file from the viper 2.2 file, but there's no boot.img in any of the viper files I have. So I tried looking on the forums, but all the boot.img file links I found were expired/dead/long gone.
So I need some help in figuring out how to get this phone back. I can get it out of the bootloop by pulling the battery and then do hboot via the downvolume + power button, and then I can get into teamwin recovery from there. But after that, I don't know what to do. Any advice/help to get back on my feet would be greatly appreciated!
Nevermind...got it! I tried installing the stock kernel from here http://forum.xda-developers.com/showthread.php?t=1770978 and it booted back up finally.
I kind of thought that's what I needed to do, but I was at the point where I didn't want to keep touching (or more like breaking!) more stuff until I knew what to do. Thanks anyway!

Categories

Resources