Database Users

I need help please... messed up loaded ROMs

Basically I unlocked bootloader and tried to load ROM. I tried the Desire and Cynagen. I was not successful at either. I manage to do a factory reset and the phone is working, except my wi-fi is shot, and when i recieve the initial OTA update it starts to download and then stops and I get the triangle of death as I call it with the lil android guy. I realy dont know what the hell Im doing and I need inch by inch restoring ROM for dummies instruction. I would like to go back to stock.I have been in threads but i get lost on certain things. I dont know what a adb is or how to acess it. I did read the noobies guide.. Please help as I am ready to chuck this thing out the window, i love my N1
I have searched the ORIGINAL SHIPPING TUTORIAL
and one other thread but i guess i cant post links.
please help!!!

do a search for adb for dummies on this site. it should help

Buck Shot said:
Basically I unlocked bootloader and tried to load ROM. I tried the Desire and Cynagen. I was not successful at either. I manage to do a factory reset and the phone is working, except my wi-fi is shot, and when i recieve the initial OTA update it starts to download and then stops and I get the triangle of death as I call it with the lil android guy. I realy dont know what the hell Im doing and I need inch by inch restoring ROM for dummies instruction. I would like to go back to stock.I have been in threads but i get lost on certain things. I dont know what a adb is or how to acess it. I did read the noobies guide.. Please help as I am ready to chuck this thing out the window, i love my N1
I have searched the ORIGINAL SHIPPING TUTORIAL
and one other thread but i guess i cant post links.
please help!!!
Click to expand...
Click to collapse
did you try to load rom in the recovery img? This also happened to me (triangle with the android guy) and I thought I couldnt flash custom roms. For some reason the regular reboot to recovery mode gives me the triangle of death as you call it.
I got around this by loading in into bootloader mode then going to my command console, getting to my skd tools folder, and then typing
fastboot boot (whatever recovery img you used)
Then everything worked perfectly.

They are going to move this to General....
You did not follow the steps correctly it sounds.
Did you Load Amon Ras Recovery?
IF YES,
GO into Recovery
WIPE data
Flash Cyanogen's Latest ROM
Flash Google Apps available on Cyanogen's front page Post
In future ALWAYS nandroid Backup...
If you did not load Amon Ra's Recovery, you should go do this from fastboot.

I'll try to explain it to you:
1. The Bootloader is unlocked (you see the open lock at the first screen)? If you don't see the lock this is the first you should do or send it directly in for repair!
2. Then you have to flash the Recovery ROM (http://forum.xda-developers.com/showthread.php?t=611829) This you need to flash an update.zip Exact instalation guide is in the Link.
3. The ROM. If you want Stock then here you'll find it as an update.zip: http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
Choose one without includet Radio ROM!!! (See below why!)
4. Copy the ROM to your SD Card Root
5. Go into Recovery ROM (Vol Down with Power and then select recovery with the Volume button). There you select wipe and choose the first entry there (wipe data and cache)
6. Stay in Recovery ROM and selct Flash from update.zip and select the update.zip. Wait until everything is done and you are promted to reset your N1.
(DON'T MESS AROUND WITH THE RADIO ROM IF YOU DON'T KNOW EXACTLY WHAT YOU ARE DOING. DON'T UNDERSTAND ME WRONG, I THINK YOU HAVE NO GLIMPS WHAT YOU ARE DOING SO BETTER LEAVE THE RADIO ROM ALONE!!! YOU MAY BRICK (DESTROY) YOUR PHONE WITH IT!!! If you dont believe: http://android.modaco.com/content/g...odaco-com/303716/nexus-cannot-on-after-flash/)
7. There should be no 7. Everything should be fine by now.
Hope I could help.
** 100 Posts **

Stheoft u are my hero!!! Now hold do I get the multitouch update? lol sorry
DID YOU EVERY KNOW THAT UR MY HERRRRRRROOOOO
edit: i got it, im back to square one... thanks alot for all ur help

@ Buck Shot, this is a development forum... threads with question shud go in the general forum... these are making the development forum a mess....

[Tutorial] Wanna Backup Before U Get Root?! Heres How U Can

ok first off this is a little more technical then the other root methods. all u really need from the root update is actually the spl (hboot.img) from that point u can fast boot and are pretty much in God Mode. so yeah i wanted to root my wifes Eris. but alo wanted to make a nandroid of her stock build with all her apps and stuff. just encase she didnt like the 2.1 build. anyhow heres how i did it.
before i start fastboot will be needed for this method. u can find it attached to this post. now fastboot is a very handy thing for a dev or anyone who may wanna flash boot.img, kernels, recoveries and really anything flashable. even update.zips. anyhow put it in ur working dirrectory rename it fastboot and excute as directed. this is a linux compiled fastboot so it will ost likely only be useful to those who are running linux.
i had to rename it "fastboot.zip" to upload to xda. download and rename "fastboot" and it will work fine
also look at the attached pictures on this post. they show what stock and GOD MODE hboot menus look like. that way u can confirm u have GOD MODE before pulling the battery. u will but just to remove all doubt i posted pics so one can confirm they are in fact in GOD MODE before they pull the battery. the top line in hboot menu is all that really says ur in GOD MODE. acutually it says... "PB00100 XC ENG S-OFF"
SO LETS ROCK AND ROLL
step one: get the PBOOIMG.zip from here (md5: 63eacc5ede3b179f95dc22d8ef585f94)
step two: put it on the root of ur sdcard and turn off the phone
step three: hold volume down while powering on. let it fine the PBOOIMG.zip and read it. at this point it will ask u to push the the jogball in to continue. BUT WAIT STOP RIGHT THERE. with that screen up pull the cover off the back of ur phone.
step four: ok now that were set with the cover off the back of our phone. get ready because this will go pretty quick. push in on the jog ball to continue with the install. the phone will reboot and when it comes back it will start looking for and reading the PBOOIMG.zip (we need to stop this or else itll flash the whole build) at this point pull the battery out. the hboot.img(spl) installed in that split second before it rebooted. which means u have GOD MODE.
step five: power the phone back on normaly. once ur booted in u need to remove the PBOOIMG.zip from the sdcard. i did it like this.
adb shell rm /sdcard/PBOOIMG.zip
step six: power the phone back of then hold volume down and power back on into hboot menu
step seven: get the recovery.img from here put in a directory u can remember on ur computer.
step eight: at this point with ur phone plugged into ur computer and in hboot menu. u will notice at the top it says..."PB00100 XC ENG S-OFF" <~~this is GOD MODE. anyhow look further down and u will see the fastboot option in orange. press send key to enable. wait a second or two and u will see "fastboot usb" in red. this means ur all setup to fastboot.
step nine: now were gonna fastboot flash the recovery.img to the recovery partition. u can do this buy this command: (btw i use linux and this is where it was on my computer)
fastboot flash recovery ~/Downloads/recovery-RA-eris-v1.6.2.img
if all goes well it should print this:
sending 'recovery' (3834 KB)... OKAY
writing 'recovery'... OKAY
step ten: press volume down to return to hboot mode. then volume up to reboot to recovery.
step eleven: then navigate through recovery to backup/restore>Nand backup or BART backup (ur choice) then select and wait for the backup to finish. once its finished u can just press volume down till u get back to the main screen and then just reboot.
were finished. now ur stock rom is not a root rom. so once u reboot back into it ur not gonna have su and #. u will still need to flash a custom update.zip via recovery to have a root build. but at this point u have a nandroid backup of all the stuff had. so if for some reason u ever wanna flash back stock ur set.
the spl (hboot.img) is all u actually need from the PBOOIMG.zip to be able to have root and flash custom roms. the radio.img from the PBOOIMG.zip can also be extracted from the zip and flashed via recovery or fastboot.

reserved::

toastcfh,
Awesome, makes perfect sense! I think this might be exactly what I was waiting for in order to loosen my grip on 1.5 and do the root dance.
I have a couple of questions though, I hope you don't mind:
My impression is that Amon_RA's recovery + Nandoid, BART, et cetera - (or fastboot+ S-OFF) allows you to backup/restore anything on a partition-by-partition basis, e.g. on the Eris we have
$ cat /proc/mtd :
Code:
dev: size erasesize name
mtd0: 000a0000 00020000 "misc" (normally skipped)
mtd1: 00500000 00020000 "recovery" (normally skipped so it won't get nuked accidentally)
mtd2: 00280000 00020000 "boot"
mtd3: 0aa00000 00020000 "system"
mtd4: 08200000 00020000 "cache" (normally skipped)
mtd5: 09f80000 00020000 "userdata"
...but I'll have to admit - my understanding about the flashing of hboot, radio, and nv images is little bit fuzzy about what is possible - specifically if it can be done without a signed zip (the way it normally happens is with the RUU update process).
They are neither backed up nor restored by by the recovery tools, correct? (Amon_RA doesn't mention them in his announcement thread)
I was under the impression that fastboot can't flash any of those images, well... one by one anyway. Is that what the "fastboot update update.zip" method is for, or is there some other way to avoid the zip-signature issue that the RUU/PB00IMG.ZIP+hboot methods use?
I'm probably missing something completely obvious - and of, course, I'm aware that we have the 1.5 image files (hboot, radio, & nv) from the RUUs - but how do you burn them to the phone, assuming the S-OFF bootloader and/or (Amon_RA) recovery are in place on the phone?
bftb0

Also...
- can steps 5 & 6 be skipped by ejecting the SD card after the battery pull (step 4), and re-inserting it just before step 10? (Delete the PB00IMG.ZIP file later - after everything else is done.)
bftb0

bftb0 said:
Also...
- can steps 5 & 6 be skipped by ejecting the SD card after the battery pull (step 4), and re-inserting it just before step 10? (Delete the PB00IMG.ZIP file later - after everything else is done.)
bftb0
Click to expand...
Click to collapse
well im sure it might work. but... if u eject the sdcard it will stil sit and search for the it and u will have to sit and wait for a bit. i say pull the battery because its prolly the quickest way to pull this off and its how i did it. if u wanna try to eject the sdcard instead of pulling the battery ur welcome to try. if u do it and it works well post and give feed back on what happened. i tried to make this as detailed as possible to clear up most questions. so a good post on what u did and how it went down would be great for me to update the my post. thanx

bftb0 said:
toastcfh,
Awesome, makes perfect sense! I think this might be exactly what I was waiting for in order to loosen my grip on 1.5 and do the root dance.
I have a couple of questions though, I hope you don't mind:
My impression is that Amon_RA's recovery + Nandoid, BART, et cetera - (or fastboot+ S-OFF) allows you to backup/restore anything on a partition-by-partition basis, e.g. on the Eris we have
$ cat /proc/mtd :
Code:
dev: size erasesize name
mtd0: 000a0000 00020000 "misc" (normally skipped)
mtd1: 00500000 00020000 "recovery" (normally skipped so it won't get nuked accidentally)
mtd2: 00280000 00020000 "boot"
mtd3: 0aa00000 00020000 "system"
mtd4: 08200000 00020000 "cache" (normally skipped)
mtd5: 09f80000 00020000 "userdata"
...but I'll have to admit - my understanding about the flashing of hboot, radio, and nv images is little bit fuzzy about what is possible - specifically if it can be done without a signed zip (the way it normally happens is with the RUU update process).
They are neither backed up nor restored by by the recovery tools, correct? (Amon_RA doesn't mention them in his announcement thread)
I was under the impression that fastboot can't flash any of those images, well... one by one anyway. Is that what the "fastboot update update.zip" method is for, or is there some other way to avoid the zip-signature issue that the RUU/PB00IMG.ZIP+hboot methods use?
I'm probably missing something completely obvious - and of, course, I'm aware that we have the 1.5 image files (hboot, radio, & nv) from the RUUs - but how do you burn them to the phone, assuming the S-OFF bootloader and/or (Amon_RA) recovery are in place on the phone?
bftb0
Click to expand...
Click to collapse
ok im gonna give this a shot for u. ok u got the partions listed here correctly which is good. ok when u flash amon_RA's recovery it flashes to the recovery partition. at that point u got the ability to use flash_image which is in the recovery. flash_image enables recovery to flash update.zips and some .img files. image ".img" files are whats inside the RUU ur talking about. a RUU is just a utility that whenn u run it, it will extract the includes image files to a file on ur computer. then flash those files via hboot. but it does it all automagic for u to avoid the user error part of life. just one thing about the image files though. u can flash via amon's recovery the radio, hboot, and boot.img using the flash_image comand while in amons recovery. the hboot u will never need to change most likely. it doesnt hurt to have full root (GOD MODE).
now as for fastboot. fast boot gives u the ability to flash all image files to all partitions. but it doesnt give u the big backup restore option like amon_RA recovery does. fastboot is more for dev purposes. giving a dev the ability to flash images without pushing them to the phone first and also the option to just boot the image instead of flashing it. so if it a image file doesnt do what was expected by the dev then he can just boot back into hboot menu and try the next, without having to take the extra steps of booting into recovery, pushing the next image file, flashing it and rbooting. hence the name fastboot. its fast but again this is really a dev tool. flashing or booting update.zips from fastboot i have never tried. as amon_RA recovery does this fine and lets me do a backup first.
for the use of this method of gaining root is the only time u should flash the recovery partition from fastboot. it can be done in root roms with ease if they are built correct.
there i hope i answered ur questions. sorry such a large post once u go root this way u will always have the reverse option. well as long as u have ur backup on ur sdcard. i did root this way for my wife and myself to have that security of knowing if she isnt happy with 2.1 or any other custom rom. she always has the build she knows she likes. 1.5 stock.

What exactly are Radios

toastcfh
[size=+2]AWESOME.[/size]
I'm running 1.5... with a S-OFF bootloader and Amon_RA's v1.2.6 recovery.
I need to figure out if there's any money in my Paypal account (haven't used it in 6 years), and buy both you and Amon_RA a coffee.
Gonna run out and get another SD card. Any suggestions about partitioning strategies, or whether you prefer Nandroid to BART for backup/restore, etc?
One thing you might edit in to the original instructions (step 9) is a mention to run fastboot from a root (Linux) or privileged account (Windoze), and check first that you are talking to the phone with a "fastboot devices" command. ( I got a small scare when I got to that step and forgot about needing root to write to the USB device under Ubuntu - I thought that the new bootloader was deaf for a minute there.)
bftb0

bftb0 said:
toastcfh
[size=+2]AWESOME.[/size]
I'm running 1.5... with a S-OFF bootloader and Amon_RA's v1.2.6 recovery.
I need to figure out if there's any money in my Paypal account (haven't used it in 6 years), and buy both you and Amon_RA a coffee.
Gonna run out and get another SD card. Any suggestions about partitioning strategies, or whether you prefer Nandroid to BART for backup/restore, etc?
One thing you might edit in to the original instructions (step 9) is a mention to run fastboot from a root (Linux) or privileged account (Windoze), and check first that you are talking to the phone with a "fastboot devices" command. ( I got a small scare when I got to that step and forgot about needing root to write to the USB device under Ubuntu - I thought that the new bootloader was deaf for a minute there.)
bftb0
Click to expand...
Click to collapse
Great man and I'm glad all went well. It was easy easy huh. Lol sorry bout not adding the whole root user deal. But thanx for the heads up. I will add it in as soon as I'm finished with this stupid windows install.( my hdd took a crap last week) anyhow about partitioning... I use nandroid for backups. But that doesn't make bart suck. It has some advantages over nandroid that I don't remember. Also for partitions I use ext 3 for a2sd on my heroc. But haven't hooked up the Eris yet. I will build a Rom soon that'll include a lot of goodies so keep an eye out

toastcfh said:
Great man and I'm glad all went well. It was easy easy huh.
Click to expand...
Click to collapse
When I saw your original post, I actually laughed out loud as soon as I got to the part about doing the battery pull.
I had noticed that little "flashing hboot" blip that occurs right before the 2nd reboot during the many times I had re-run PB00IMG.ZIP flashes - but I never put 2+2 together the way you did.
Very nice - anyone that wants the option of rolling completely back to "factory 1.5" has that option now.
bftb0
[Edit] PS - One more minor thing - I think that use of the trackball (step #3) for confirming operations in the bootloader menu wasn't present in the OTA 1.5 (HTC) bootloader - you use the End Key in step #3 if you have the factory/OTA 1.5 bootloader on the phone (7501a_1.47.0000_091023). Not a big deal, but thought I'd mention it cuz it might confuse folks - it never mentions the trackball in the menu with the factory 1.5 bootloader.

So just to make sure I understand this fully before I attempt, step 9 requires using the PC to type commands to the phone, correct?
I'm not sure I completely understand how to do that, but would like to learn.....

Sub-Standard said:
So just to make sure I understand this fully before I attempt, step 9 requires using the PC to type commands to the phone, correct?
I'm not sure I completely understand how to do that, but would like to learn.....
Click to expand...
Click to collapse
Yes.. ur gonna need to download the android sdk also to make fastboot. I gave all the resources u need for gettin the sdk making and using fastboot in my first post. I myself would suggest ubuntu as a os. As u can easily use wubi to dual boot it and its a noob friendly Linux distro. Most of the things u can do to ur phone are much easier to do in Linux

So download the SDK for windows starter pack, & download ubuntu, spend a little time reading up on how to use fastboot, then attempt the tutorial.....
So just to make sure I'm very clear, this is incase you want to have a backup to get your phone back to bone stock 1.5 for warranty issues etc.... are is this just if you want to store a backup of all of your apps, settings, files?

I posted links to both the full sdk and the fastboot wiki and cheat sheet. If ur gonna do it through windows u need to follow the windows constructions for the sdk. If ur gonna use Linux u need to follow Linux instructions to get the sdk from the link o provided.
As for what this will backup... it will backup ur entire system and boot partitions. Including all apps settings preferences and everything else u had while stock. Leaving u with the option to restore ur device to stock specs. This will not however back up ur stock recovery and hboot partutions. U would however be able to return to stock specs. But that's a whole new tutorial. This will just leave u with the option to return to ur stock setup if u ever desire too. Like a snapshot of ur setup before u went root. Instead of just aimlessly flashing an entire build and losing everything u had before root. It just was more practical for me to still have that stock option. So if my wife wanted to go back stock she could easily. In the end to just get root. U don't have to flash the entire root build u just need to flash the GOD MODE spl (hboot.img). After that's installed u can flash anything u desire through fastboot.

I'm assuming something stops this process from working on Leak 2.1? And it has been tried?
Having a recovery partition installed would be clutch.
Great tutorial, fwiw. You make this community better, sir.

pkopalek said:
I'm assuming something stops this process from working on Leak 2.1? And it has been tried?
Having a recovery partition installed would be clutch.
Great tutorial, fwiw. You make this community better, sir.
Click to expand...
Click to collapse
what stops the process from working on the leak is the fact u dont have the ability to flash anything. ur not root but in the event of having root a downgrade is very possible. unrooting and using an ruu i very possible also. but yeah once u can flash amons recovery to recovery u are all set as root. the reason the we can flash this is because of the spl not an actual exploit. the spl or hboot.img give the ability to flash any partition on the phone. thats why i say flashing the entire update.zip is kinda pointless. the only part of the entire build u need is the hboot.img the build is root i believe. but from the tests ive done on the build ive found its nothing to write home about. i would suggest to anyone to go and do their homework on how to use fastboot and the rest of the sdk and root this way. the installing and using of the sdk will help to get comfortable with the device and root. all the tools u need to contribute to this and any forum are in that sdk.
and as for making this community better. i dont think i do anything different then any good dev should or would. i share all my work for free, educate those who wanna learn, help all i can that are in need, and am very open about all my workings. i hope to see more dev theads on this forum and see everyone work together as a community. this forum can and will be a place to find lots of information.

very nice work toastcfh! I think this is exactly what I've been hunting for. Sorry to be obtuse, but just so I'm clear: with this method, I should be able to backup, go for the 2.1 root, and if I do not love the 2.1 root experience get back to "stock?" If I reverted to stock, is there any reason I wouldnt be able to get the long awaited 2.1 OTA? thanks for your patience with those still trying to understand all this.

los04 said:
very nice work toastcfh! I think this is exactly what I've been hunting for. Sorry to be obtuse, but just so I'm clear: with this method, I should be able to backup, go for the 2.1 root, and if I do not love the 2.1 root experience get back to "stock?" If I reverted to stock, is there any reason I wouldnt be able to get the long awaited 2.1 OTA? thanks for your patience with those still trying to understand all this.
Click to expand...
Click to collapse
well when u do this u will flash amon to recovery. once u do that u can backup ur stock 1.5 system and apps to nandroid or BART backup in the recovery. that will save a "snapshot" of exactly what u had stock. at that point u can flash any of the custom roms the guys around here are making. if u dont happen to like the builds they are making and wanna go back to 1.5(stock) u can and all the apps,setting,everything will be there just like u left it.
but... DO NOT try to flash the rest of the root leak as it will over right ur amon_RA recovery, but ... if u decide u want to anyhow. as soon as u flash amon_RA recovery and go in to backup/restore>restore u will still have ur 1.5(stock) snapshot on ur sdcard. well as long as u didnt wipe ur sdcard
anyhow yeah this wont give u the option to go back and flash the stock ruu that i know of but it will at least keep that stock snapshot for u to fall back on anytime u may want or need. ie for the hell of it or when u go into the verizon store .
as far as when verizon releases have no fear... ur root now. im sure either i or anothr dev will cook up a rom to be flash from recovery within the first hours of its release. i promise u that when ur root u dont worry about when the next release is. u just look foreward to the next leak. well the flashoholics do at least.

Followed these directions, worked flawless. Thanks for giving us the option to go back to 1.5.
I'm now running rooted 0.3 and happy with it so far...but of course the OTA came out hours after.....

droost said:
Followed these directions, worked flawless. Thanks for giving us the option to go back to 1.5.
I'm now running rooted 0.3 and happy with it so far...but of course the OTA came out hours after.....
Click to expand...
Click to collapse
thats why i say flashing the whole root build is a waist. all u really want and need is the spl.

Anyone know how to downgrade roms?

I have the updates installed but the unlock and selection sounds don't work. They were for a bit but then stopped. I tried to rename the rom update.zip but the phone stated it was an older version and could not flash it. It then forced me to reboot, end of story.
I want to reboot back to OG rom and then apply the updates over it.
Can anyone help me out.

Do it with paulobrian's method.

~~Tito~~ said:
Do it with paulobrian's method.
Click to expand...
Click to collapse
Assuming he knows what that is. OP, were you doing the fastboot flash method using the command prompt on Windows?

~~Tito~~ said:
Do it with paulobrian's method.
Click to expand...
Click to collapse
Now if i only knew what this really meant.
* Download the 1.19 stock ROM from here
* Download fastboot from here
* Extract the fastboot zip to the same directory as the ROM
* Turn your G2 on with the action button held (fastboot mode) I've never heard of an action button
* Type 'fastboot-windows oem rebootRUU' (case sensitive, replace windows with mac or linux as required) No where does it give me the option to type anything in.
* Type 'fastboot-windows flash zip PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459
signed.zip'
* Let this finish, then type 'fastboot reboot' and apply the OTA
P

EfemaN said:
Assuming he knows what that is. OP, were you doing the fastboot flash method using the command prompt on Windows?
Click to expand...
Click to collapse
I used this method to revert back to stock cuz i deleted the goggles. But, the click sounds only worked for an hours then stopped.
-------------------------------------------------------
Download PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b _26.02.01.15_M2_release_149459_signed
(the link is somewere in this thread)
*then read name it to PC10IMG.zip
*Put it on the root of your sd card.
*Power down phone
*Power up phone holding Vol Down and Power button.
*Phone will boot into fastboot i believe and then it will look for PC10IMG
*It will ask to flash it you use the vol key and power buttons to do that.
*Once it done it will reboot the phone and all your data will be gone and your be back at factory setting.
Then just rename the ota to update.zip and flash via recovery.
*remover the PC10IMG.zip from root of sd card
* Get back into the fastboot on the phone (setups up there^)
*this time use the vol button to go down to recovery.
*Once at recovery hold vol up and hit the power button.
*then vol down to flash update.zip

ddgarcia05 said:
I have the updates installed but the unlock and selection sounds don't work. They were for a bit but then stopped. I tried to rename the rom update.zip but the phone stated it was an older version and could not flash it. It then forced me to reboot, end of story.
I want to reboot back to OG rom and then apply the updates over it.
Can anyone help me out.
Click to expand...
Click to collapse
First make sure you media vol is on and up. If its not then u wont be able to hear it. And second you can downgrade the phone. All andiords are downgrade block unless we have custom bootloader. And the steps poste above are mines I orignaly posted them so I know it wont work after u applyed the ota
Sent from my T-Mobile G2 using XDA App

You cannot downgrade using either of the fastboot methods (fastboot-windows or fastboot on your phone) listed above after you have applied the OTA. It checks the version and then tells you that the downgrade version is old.
So far, I have not seen a solution to downgrade.

cparekh said:
You cannot downgrade using either of the fastboot methods (fastboot-windows or fastboot on your phone) listed above after you have applied the OTA. It checks the version and then tells you that the downgrade version is old.
So far, I have not seen a solution to downgrade.
Click to expand...
Click to collapse
This is correct, verified live in IRC by people in #g2root

Just call tmob and tell them your hinge is loose! Exchange phone, don't apply OTA.

All the sounds stopped working on my phone a day ago, had to do a hard reboot to get them working again.
OTA was applied.

Well, I called tmobile and told them my issue. I also told them I had already tried to reset my phone in attempts to fix the sound issue to no avail. I've got a new or like new G2 on it's way.
I'm going to be kinda bummed if it's a like new (refurbished) model, but then again it can't be older than the one I got now.

Sprint / HTC Policy

I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Call ahead of time and see what they say on the phone?
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)

I don't know what the policy is.... most likely, as soon as they see where you're at, the tech will figure out that you were trying to root your phone, and you'll be SOL.
Have you tried booting your phone via ADB? Maybe you can go into recovery via adb shell and see if you can go from there....

if you can get it to power up all is not lost, try pushing AMON's recovery via fastboot
Fastboot
Copy recovery-RA-evo-v1.8.0.img in your android-sdk-windows\tools\ folder
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)

Since your phone turns on and you can boot into fastboot. Bricked would mean nothing happens period. There's still hope. Try this thread: http://forum.xda-developers.com/showthread.php?t=780141. There's a video walk-through showing you how to unroot and return to s-on. Then you may be able to start over.
Good Luck!
-kp
Edit: Try GMan's suggestion above 1st.

Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks

Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.

indagroove said:
Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.
Click to expand...
Click to collapse
Sprint Insurance right? I don't... I might do that but that's my last resort.

josh4trunks said:
Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks
Click to expand...
Click to collapse
If you can boot into the hboot just run a ruu and restore the factory Rom, if all fail pm me your number and I will walk you thru it
Sent from my PC36100 using XDA App

shameless bump - completely changed opening post

I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week.
What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.)
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!

haplo1818 said:
I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week. What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!
Click to expand...
Click to collapse
Tried this multiple time with different PC36IMG.zip, always get Failed-PU
Partition Update Error, I might try the 3.30 version though just to make sure.

Won't like my opinion but, you knew the risks of rooting. If you can't fix your phone then you should add the insurance and suck up the deductible fee. You don't deserve (or anyone for that matter) a free replacement for ****ing up your phone. It sucks but that's the risk. They'll normally have you one the next day.

Your phone is definitely not bricked and is fixable. Do you have adb drivers installed on your PC? If not find them and install them then try this: http://forum.xda-developers.com/showthread.php?t=829045?
Since you are already s-off you won't have to do all the steps, but by reading the entire OP you could figure out where to start and what to do. Just to be on the safe side you may want to start at the beginning using HBOOT USB from this screen you posted ftp://eto.homeip.net/shared/IMAG0004.jpg and start completely over. you are not bricked. Just hang in there and someone here will get you hooked up. You are in the right place my friend.
Evo's are really not that easy to fully brick.

I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode

Have you tried using a different SD card? Is it possible that something is corrupt with it? I also hear that you need to have at least 1GB of free space on the card when your trying to flash it.....

Let me just say myself and this guy stayed up late last night working on this phone trying every possible root/unroot method you can think of.
The pc he is using has adb drivers installed but the computer wont recognize his device as a adb device. Fastboot on renders certain commands and we tried all with various recoveries. I hit up a dev and we went thru different things and cant seem to figure this one out
As I told the Josh it can not be bricked because we get the bootloader and fastboot screen, I think its not even the partition but the recovery. Also he has a modified hboot by someone on xda (josh please post the link) which I believe that pc36img is whats causing all the problems.
If anyone could help it would be appreciated!!

Jbcarrera said:
I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode
Click to expand...
Click to collapse
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.

craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
I'm sure he thought you needed the engineering SPL to be able to flash roms. When I rooted mine back in June with toast's method, that was the way to do it. I rooted my girl's new Evo last month using Unrevoked, and I also downgraded the hboot because I thought I had to in order to flash a custom rom. Fortunately, I was able to do so with no issues.

Cleared all the caches?

craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
The partition table is screwed but there has to be a way to reset it I knew that method was risky told my friends to stay away from it
Sent from my EVO at the edge of hell

LOL, it would appear I'm "that guy."

You know the guy I'm talking about: while he's sitting in the VD clinic with an itchy crotch, he's praying to God: "Oh God, please don't let it be herpes. If it's not herpes I swear I won't visit another whorehouse as long as I live."
Then, as soon as the doctor announces that he's just got a case of jock itch and he should put some anti-fungal on it, the guy runs to the whorehouse to celebrate....
Because, see, just a few days ago I semi-bricked my Evo running after a failed Unrevoked. Not sure why it failed, but the phone would lock up every 15 seconds. So I flashed a stock image to repair the damage, and then a newer one, and wound up with a phone that worked except it wouldn't read the SD card or USB port (charging would only occur if the phone was turned off).
So as I was working my way through the fix I kept promising myself that if I got it fixed I'd just keep it stock unrooted and be happy with it.
Then, thanks to the good fold here, I managed to get the device running again the way it should. Wheeew, I thought, I'm happy now.
But... of course... it only took a few hours before the "root" itch hit me again. Fixing the semi-brick issue required installing z4root, and that app gave me a taste of da root acces... and ooooh did it taste goooood! Problem with z4root, though is that you're still s-on, and it's my understanding that if you're s-on and take the new GB update, you're SOL (at least for the time being). And I wanted to be s-off for the peace of mind it offered.
So my desire for real permanent root got the better of me. I decided that the reason unrevoked had failed for me the first time probably had something to do with all the cr*p I had installed on my phone. So I used Titanium backup along with z4root to back up the stuff I'd installed since getting my phone back and re-flashed the stock 2.2 image that had worked for me, and started with afresh phone.
Tried unrevoked one more time and... viola! It worked!!!
I'm happy now... a happy, unrepentant sinner!
Anyway, if you've read through all this: bless you.
I do have a couple of questions:
1) Am I correct that being s-off means I can now install unsigned ROMs the same way I installed the stock image I am on? (basically, rename it PC36IMG.zip, put it on the root of the SD card and boot into the bootloader and let it install)?
2) do I need to run "unrevoked forever"? I'm not clear on this. Getting some conflicting information from searching. My best guess, from what I've read, is that the latest unrevoked includes all the stuff that unrevoked forever does.

-Is blessed-
1. You don't need to make a PC36IMG to flash a rom; just download the file, then backup your current rom, do a full wipe, then flash the rom zip
2. You don't need to flash the forever zip; it was used to give you nand unlock -s-off- in the older versions of unrevoked, and was incorporated into the new one.
And keep applying that jock itch.

And once you flash a couple roms, you will get the itch to start using the kitchen and playing with your own custom rom, its only a matter of time, lol

I probably try two a week now. Its amazing how much work these guys do.

Unrevoked forever is incorporated in Unrevoked now. So need for that.
Also, you dont flash them in the bootloader. Boot into the bootloader, then use volume down to go down to the option that says "recovery" then use the power button to select. It will boot into recovery menu which should have a list of options, go down to flash zip from sdcard, then select zip from sdcard. It will show you a list of everything on your sdcard. Navigate to wherever your rom .zip file is that you downloaded and select it. It will ask you if you want to flash, select yes.
PS dont forget to wipe before you flash. ("Wipe all user data/factory reset" option when your in recovery.)

RileyGrant said:
Unrevoked forever is incorporated in Unrevoked now. So need for that.
Also, you dont flash them in the bootloader. Boot into the bootloader, then use volume down to go down to the option that says "recovery" then use the power button to select. It will boot into recovery menu which should have a list of options, go down to flash zip from sdcard, then select zip from sdcard. It will show you a list of everything on your sdcard. Navigate to wherever your rom .zip file is that you downloaded and select it. It will ask you if you want to flash, select yes.
PS dont forget to wipe before you flash. ("Wipe all user data/factory reset" option when your in recovery.)
Click to expand...
Click to collapse
OK, so that's pretty much the same as with the Nook flashing Phiremod (a Cyanogenmod variant).