[Q] Downgraded, Next Step: Debranding - Legend General

I have one of those Legends that require a downgrade before you root, but I decided to chicken out and after I downgraded to 1.31 or whatever it was, I decided to debrand my Bell Legend and chicken out to get the worldwide Froyo OTA. Plus, it was getting late, I didn't want to accidentally screw up the rooting because I was tired.
Anyway, after I downgraded, I installed a system update that brought me to Eclair-update-1. I don't think that was a really good idea.
Because afterwards, when I tried installing the debranded RUU from the debrand thread, it resulted in an error and I have to keep what I have right now.
UNLESS YOU GUYS HELP.
What did I do wrong? I'm only still a kid. Hell, I thought I bricked my phone halfway through installing the first RUU because there was something wrong with the drivers, I ALMOST TEARED UP FFS.
Oh yeah, and wtf is up with this BS where you format the SD card to turn it into a Goldcard, and HTC Footprints just decides to move its crap into the SD card RIGHT AFTER I FORMAT IT. It's not important, but I was just wondering.
I might have been missing some details (it's late) so please post below and tell me what I'm missing.
Thanks in advance!
PS: Oh yeah, have I voided my warranty yet? Technically, I mean. I COULD still clean it up somehow, and make it seem like I didn't do anything to it, right?
PS2: OK, now I'm getting USB errors 171 and 170 when installing RUUs. I can't get out of the RUU I'm on. Oh crap.
PS3: I just got Error 140, BOOTLOADER Error. What did I do wrong here?
At least I'm at the phone's home screen now, no more unfamilar scary-ass HTC LOGO territory.

Basically the update to "2.1-update1" brought you back to where you were before the downgrade. Your phone is stock right now.
So first relax and get some sleep
Do the downgrade again. DO NOT UPDATE.
Continue the debranding/gold card procedure.
good luck
p.s. your warranty might technically be void when you install another ROM or debrand or root, mostly they don't care as long as you didnt drop it in water . There is always a way to bring it back to stock/unroot

Oh my goodness I love you. I just noticed (while I was tired, wow, that's strange) that the strange ROM number within the About Phone menu finally clicked with what I've been doing! NO UPDATE.
So I decided to call it a night after I try once more.
So I downgraded to w/e. It was fine.
And I tried the debranding RUU. Then I got a bootloader error. I guess I'll try to find out what that means when I wake up, I'm super sleepy. (Unless you guys can help me 'til then )
It was error 140 or something like that, but it booted me fine to my downgraded ROM, so I'm good for the time being.
Good night!
EPIC ACHIEVEMENT EDIT:
Alright, I rooted it. Sweat all over the place, but hey, don't blame me. The problem above is still experienced by many people all over the internet, unfortunately. Too bad I can't answer it.
Just a question before I flash my first ROM with ClockworkMod: What about fixes? How do I flash those? Super noobish, but yeah.

Related

CONFIRMED CRC1 can be rooted! Downgraded anyhow :)

I have tested the rooting of the G1 with the CRC1 update (with my boss`s phone ) He accidently got the update and installed it yesterday on his non-rooted G1 and while we were at work tonight we flashed it back down to the RC29 with NO troubles at all ... only thing left to do was download the spl and the recovery image and type telnetd, download telnet connect to local host, and run some script... which all should work just fine since it did let us downgrade. I havent seen anyone here or on google that has tried that yet so I wanted to let everyone know it will let you downgrade to the lower version.
Now if you have a rooted phone and install the update .. you will more than likely loose the root .... but you should be able to get root back by re-rooting the phone and going with a non CRC version until a modified image comes out.
OK we finished the rooting today and it flashed with the new ROM and everything. It now is on the JF1.51MOD with the updated radio.
Yup, read this post:
http://forum.xda-developers.com/showthread.php?t=538536
and this post:
http://forum.xda-developers.com/showthread.php?t=538456
/Close
andonnguyen said:
yup, read this post:
http://forum.xda-developers.com/showthread.php?t=538536
and this post:
http://forum.xda-developers.com/showthread.php?t=538456
/close
Click to expand...
Click to collapse
NEITHER of these 2 threads say anything about anyone testing or confirming that you can downgrade FROM CRC1 and get root again.... the JF thread is saying pretty much dont install it and if you do it wont update anyhow. The other thread was cyogen making an altered CRC1 version that has been patched for updating.
Still no threads like this one that I found
/OPEN
Strapt said:
until a modified image comes out.
Click to expand...
Click to collapse
Which JF will come out with, as posted in my previous post, but good to know that its still downgradable (is that even a word?) to RC29. This thread should be posted in the general Dream section BTW, as its not pertaining to any development topics.
/CLOSE
LULZ.
andonnguyen said:
Which JF will come out with, as posted in my previous post, but good to know that its still downgradable (is that even a word?) to RC29.
Click to expand...
Click to collapse
ya which will be nice when he does come out with it so people can run the phone with that version .. but this inst about who is going to be comming out with a modified image to KEEP root access ...This is to rest peoples fears about NOT being able to re-root the phone if they accept the CRC1 update or not able to root it in the first place... which no one has seemed to have tried/confirmed until now. and .. downgradeable a word?..well ... it is now!
Strapt said:
ya which will be nice when he does come out with it so people can run the phone with that version .. but this inst about who is going to be comming out with a modified image to KEEP root access ...This is to rest peoples fears about NOT being able to re-root the phone if they accept the CRC1 update or not able to root it in the first place... which no one has seemed to have tried/confirmed until now. and .. downgradeable a word?..well ... it is now!
Click to expand...
Click to collapse
So yeah I'm just upping my post count now since I'm bored. lol. Mmm, family guy is funny.
Strange...as far as I know, I have been able to downgrade to RC29 from all official releases, RC30, RC33 and 1.5, since I have had 4 separate G1's since initial release (I'm extremely clumsy and rough with my phones sometime - usually halfway through a bottle of scotch).
Hmm.
Nevermind - apparently alcohol also affects my ability to read thoroughly.
so,here's what I did, I accepted the cr1 update on my stock 1.5 stock g1,
then, I downgraded to RC29 with no problems at all, I also followed the instructions and rooted my phone ( apparently ), after that, I tried to flash a few different roms, but none would load, my g1 will always freeze at the G1 screen, until I install back the stock rom again,
am I doing something wrong?
'cuz am not that new at this, and I feel stupid.
There was never any question of it.
The only firmware known to be easily rooted is RC29.
Downgrading to RC29 is completely independent of what firmware version is actually ON the device -- it is strictly related to SPL version. Since CRC1 is an OS update and NOT an SPL update, it can't possibly have any affect on whether or not you can downgrade to RC29, hence it definitely CAN still be rooted when CRC1 is installed.
funny...
i was at a friends house last night and he wanted me to root his g1. i was there for hours trying to figure out why i couldnt get the bootloader screen to switch to grey. I downloaded DREAIMG.nbh from several sources with several different sdcards. i even have a dedicated card i named ROOTER with all the neccessary files and updates but couldnt get nothing cooking.
el_plebillo said:
so,here's what I did, I accepted the cr1 update on my stock 1.5 stock g1,
then, I downgraded to RC29 with no problems at all, I also followed the instructions and rooted my phone ( apparently ), after that, I tried to flash a few different roms, but none would load, my g1 will always freeze at the G1 screen, until I install back the stock rom again,
am I doing something wrong?
'cuz am not that new at this, and I feel stupid.
Click to expand...
Click to collapse
what ROM are you going to?? if its Hero you HAVE to have the latest spl. If it has autoappsstosd you need to have your sdcrd partitioned right (fat32 first and then ext2) I recommend using the sdsplit method.
oneG said:
funny...
i was at a friends house last night and he wanted me to root his g1. i was there for hours trying to figure out why i couldnt get the bootloader screen to switch to grey. I downloaded DREAIMG.nbh from several sources with several different sdcards. i even have a dedicated card i named ROOTER with all the neccessary files and updates but couldnt get nothing cooking.
Click to expand...
Click to collapse
hmm intersting .. the only time I have seen that is if someone was placing the entire.zip file on the sd card instead of just the DREAMING.nhb file on there. I would just reformat the card to fat32 and place that file only on it again and then try it again and see if anything goes different. Dont know if it makes a difference but i got the DREAMING.nhb off the how to root the g1
Strapt said:
I would just reformat the card to fat32 and place that file only on it again and then try it again and see if anything goes different. Dont know if it makes a difference but i got the DREAMING.nhb off the how to root the g1
Click to expand...
Click to collapse
Yeah that was my initial reaction but to no avail. Like i said earlier, i tried dl the img. from several sources.
Anyway he's not that into his G1 as much as we here are and like my g/f, despite the many features its capable of, only uses it for calls and text. He's excited about tethering tho but kinda paranoid with all that could go wrong like bricking and all that, so yesterday he was a little reluctant for a second attempt due to the day before's problematic flash. I did happen to get his phone to start ringing again without the call going stragiht to voicemail and the lock screen works now, which was the real reason i was over there in the first place.
But as far as root and CRC1 go, i might sneek my g/f's G1 away so i can test there
oneG said:
Yeah that was my initial reaction but to no avail. Like i said earlier, i tried dl the img. from several sources.
Anyway he's not that into his G1 as much as we here are and like my g/f, despite the many features its capable of, only uses it for calls and text. He's excited about tethering tho but kinda paranoid with all that could go wrong like bricking and all that, so yesterday he was a little reluctant for a second attempt due to the day before's problematic flash. I did happen to get his phone to start ringing again without the call going stragiht to voicemail and the lock screen works now, which was the real reason i was over there in the first place.
But as far as root and CRC1 go, i might sneek my g/f's G1 away so i can test there
Click to expand...
Click to collapse
lol ya you should take her and try ... I finished rooting my boss`s CRC1 yesterday. after flashing the .nhb file we added the JF1.51MOD thats found on lucids page .. mainly because it has the radio and the rom in one update. But anyhow he has a rooted G1 straight from CRC1 ... wonder what radio you guys had on that phone and if it needed to be updated before going to the ROM you chose
I needed this!
I needed to root a friends phone. He just bought it, and it had RC29. By the time he got to me, it was CRC1. Regardless, I found this post which showed it worked.
I flashed RC29, Then rooted it. Flashed latest radio, CM 1.4 Recovery, then JF1.50, and finally CM 3.9.7.
It worked beautifully! Thanks for the confirmation post!
SoTacMatt said:
I needed to root a friends phone. He just bought it, and it had RC29. By the time he got to me, it was CRC1. Regardless, I found this post which showed it worked.
I flashed RC29, Then rooted it. Flashed latest radio, CM 1.4 Recovery, then JF1.50, and finally CM 3.9.7.
It worked beautifully! Thanks for the confirmation post!
Click to expand...
Click to collapse
You are very welcome!! Thats why I posted it to let people know that they werent screwed when/if they got the Crc1 update. Glad that it went well for you!
I just got a g1 (and use linux since 1999), and LOVE this phone...sofar.
i would want to root it, and plan to.
i have the 1.5 firmware, and crc1 and am planning this on saturday.
is there a way to take screen shots of it all ? (from the phone)
any tips/ links etc is appreciated.
"run linux, stay happy".
Bellevue Washington
doing the root in Kirkland
Pizza or soda (or beer) on me.

[HOW TO] Steps to Take to Prepare a Rooted Phone for Warranty Exchange

I recently had to give up my rooted preordered Incredible for a refurb due to heat issues and reboot (loop) issues. For those looking for a guide as to what to do if you have to return your phone to Verizon and want to unroot. I welcome any comments to update/add to this information:
1) Make a NANDROID Backup if you want to simply port it over to your new phone
2) Mount your phone as DISK DRIVE
3) Walk the directories and delete any cached thumbnails of web sites you have visited
4) Copy any pictures you want to keep which were saved on the phone
5) Reboot into ClockWork recovery
6) Wipe the Dalvik Cache
7) Wipe the Data/Factory Reset
8) Go back
9) Wipe Data (main menu)
10) Power Down your phone
11) Remove your SD Card
12) Download one of the RUU's which are hosted around the web:
http://www.shipped-roms.com/shipped/Incredible/
13) Turn on your phone and plug it in to your USB
14) Run the RUU and let it do it's thing. When its done, so are you
15) If you have a screen protector, remember to remove it.
Any additions are welcome!
Yes it will revert everything back to normal, that's called an RUU btw
Cool
Anyone know if this also removes the more hidden data, such as the cached images of the web sites you have visited? In other words, if I run the RUU, is the phone ready to just be handed over?
if i root and uninstall some apps, will this restore my phone to stock and allow me to get all future HTC updates?
jdmba said:
Anyone know if this also removes the more hidden data, such as the cached images of the web sites you have visited? In other words, if I run the RUU, is the phone ready to just be handed over?
Click to expand...
Click to collapse
I don't think so, but it's easy enough to do a wipe and then apply the RUU (and hey, for the hell of it, you could wipe again).
Steps?
[deleted ... first post updated]
I'm pretty sure the RUU will completely wipe your phone. However, you can take giantcrazy's advice and wipe before running the RUU.
One more try
[deleted ... first post updated]
Ok, here is what you want to do.
there would be two things you need to un do before sending them back this phone.
make sure it says S-ON.
and then make sure you have stock recovery.
If you have these two things, your gold bod.
Probably to noob to know any better
After going through a lot of threads this one seems appropriate. I am looking for how to go back to stock DI. After Unrevoked3, ota leak and unofficial froyo leak, my DI wont connect to VZW anymore, all out going calls are busy. Talked to my VZW guys, they are cool with me, tried to help nothin'. Today tried Unrevoked forever and official froyo leak, still no VZW connection. I looked into this a lot before I tried these mods I don't know what went wrong, I would not have been able to do this with out such easy tools as are provided today. "I NEED HELP" to get back to stock, "PLEASE". I have looked into SDK and Adb, as I have been lead to believe there is no way to return to 2.1 and the right radio without these tools. At this moment I have not been able to find clear enough explanations on how to use these tools, this is where I maybe over my head. I assume my radio is fried, I don't care if no "S on", I just need those obvious things; version, kernel, baseband, to be stock. Any help will be appreciated, big thanks for any suggestions
A Lex and Er said:
After going through a lot of threads this one seems appropriate. I am looking for how to go back to stock DI. After Unrevoked3, ota leak and unofficial froyo leak, my DI wont connect to VZW anymore, all out going calls are busy. Talked to my VZW guys, they are cool with me, tried to help nothin'. Today tried Unrevoked forever and official froyo leak, still no VZW connection. I looked into this a lot before I tried these mods I don't know what went wrong, I would not have been able to do this with out such easy tools as are provided today. "I NEED HELP" to get back to stock, "PLEASE". I have looked into SDK and Adb, as I have been lead to believe there is no way to return to 2.1 and the right radio without these tools. At this moment I have not been able to find clear enough explanations on how to use these tools, this is where I maybe over my head. I assume my radio is fried, I don't care if no "S on", I just need those obvious things; version, kernel, baseband, to be stock. Any help will be appreciated, thanks
Click to expand...
Click to collapse
Ok, there is so much here I will do my best.
number one, having s-on is just as important as having a radio thats either 2.15x or 1.x, now that the OTA 2.2 update is sending out, you can send the phone back with 2.2 and 2.15x radio.
what you need to make sure of, is two things, you have s-on,
and you have stock recovery.
ACD168 said:
Ok, there is so much here I will do my best.
number one, having s-on is just as important as having a radio thats either 2.15x or 1.x, now that the OTA 2.2 update is sending out, you can send the phone back with 2.2 and 2.15x radio.
what you need to make sure of, is two things, you have s-on,
and you have stock recovery.
Click to expand...
Click to collapse
Thank you, and really they wont know if the ota was pushed to me? I found the S on tool, I didn't know there was one, I had only read on about S off. I don't know how to find/replace stock recovery, I will start searching though. Much appreciation, my better half is not as thrilled about my learning experience as I am.
I already rooted and unrooted once, will I get stock recovery back after unrooting?
A Lex and Er said:
Thank you, and really they wont know if the ota was pushed to me? I found the S on tool, I didn't know there was one, I had only read on about S off. I don't know how to find/replace stock recovery, I will start searching though. Much appreciation, my better half is as thrilled about my learning experience as I am.
Click to expand...
Click to collapse
Your welcome, I'm happy to see you are learning so quickly. S-on is very helpful for those warranty returns of the phone.
Verizon has no idea whether or not you got the ota, or better yet what version you have or if you are rooted, ect.
If you tell me what your hboot it, radio, software version, s-on or s-off, if rooted or not, and if you have the stock recovery or clockwork and I will try and guide you to where you want to be..
if you need help getting to the stock recovery this must mean you are rooted, and this can be achieved by downgrading the phone by un-rooting, I'd suggest running s-off while you are rooted, then
androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html
sorry can't post links yet,
to help you un-root and get that stock recovery back.
A Lex and Er said:
I already rooted and unrooted once, will I get stock recovery back after unrooting?
Click to expand...
Click to collapse
To find out real fast if you have the stock recovery or clockwork-mod recovery, boot into HBOOT, (power off phone, hold vol down and power til screen turns on) and then vol down to select recovery and push the power button I think to select and then if you get a red triangle that means stock recovery.
Also need to return phone
I just got off with Asurion and they are over nighting a replacement. I had rooted my phone, installed some root only apps like wireless tethering and set cpu, removed some bloat like CityID and Tweet/Peep, and changed the boot animation. No custom ROM or radio update.
Then I wanted to get the OTA update so I applied s-off and flashed back to stock recovery.
So what do I need to do to return this phone. I know I will need to apply s-on. Then should I flash a stock 2.1 or just revert the changes I made to boot animation, restore the bloatware, and remove the root apps? Do I need to remove any other files that go with being root?
Thanks.........MM
ACD168 said:
Your welcome, I'm happy to see you are learning so quickly. S-on is very helpful for those warranty returns of the phone.
Verizon has no idea whether or not you got the ota, or better yet what version you have or if you are rooted, ect.
If you tell me what your hboot it, radio, software version, s-on or s-off, if rooted or not, and if you have the stock recovery or clockwork and I will try and guide you to where you want to be..
if you need help getting to the stock recovery this must mean you are rooted, and this can be achieved by downgrading the phone by un-rooting, I'd suggest running s-off while you are rooted, then
androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html
sorry can't post links yet,
to help you un-root and get that stock recovery back.
Click to expand...
Click to collapse
Hello,
I wanted to thank you again for the help this last weekend. I apologize for not returning for more of the help you offered me. My wife only has every other weekend off and we have an 18mo. old son, both of whom deserved my time more than my DI. I love my DI but it wasn't giving me much love.
Although VZW isn't always the nicest to my pocket book, I have never been taken care of as well by any other provider(s) employees, thank you. As I mentioned in my first post, my VZW guys are cool with me. Yesterday I went into the store and the manager offered to help me. He managed to reconnect my DI to the network but no 3g's. He believes my problem is just a coincidence because he had another customer with a similar problem over the weekend, with no mod's. Still I need to exchange my DI, it doesn't look like 3g's is going to turn on.
My real issue is still getting custom recovery off and stock recovery back on, then unrooting will be a breeze. The videos you lead me to are one of the sources I have been working with, however to reverse the leaked ota, Downgrade leaked ota video, requires SDK and adb knowledge, this is where I am noob. At this time my VZW manager who is in school for programing is attempting to help me (he has a over clocked Palm Pre Plus, 1Ghz), this is very cool of him, well beyond what is expected. (I am in no way encouraging anyone to rely on their VZW employees for this kind of help, this is a unique situation, I have been building a relationship with my VZW guys for two years+, not all VZW employees have a clue about mod's, and mod's technically void the warranty) I am hoping to learn enough about these tools, SDK and adb, to help myself before the next time, and I will hopefully be gaining some of this knowledge from my friends at my VZW store soon. I will also be looking forward to the help I receive from fine people such as yourself and people in this community in future endeavors.
I will stop basically hijacking this thread now
Thanks to all of the people who support these community's, with out whom many of us would never get our foot in the door. Much appreciation to ACD168 for being there to help me.
Take the time and learn to do it right the first time.
A Lex and Er said:
Hello,
I wanted to thank you again for the help this last weekend. I apologize for not returning for more of the help you offered me. My wife only has every other weekend off and we have an 18mo. old son, both of whom deserved my time more than my DI. I love my DI but it wasn't giving me much love.
Although VZW isn't always the nicest to my pocket book, I have never been taken care of as well by any other provider(s) employees, thank you. As I mentioned in my first post, my VZW guys are cool with me. Yesterday I went into the store and the manager offered to help me. He managed to reconnect my DI to the network but no 3g's. He believes my problem is just a coincidence because he had another customer with a similar problem over the weekend, with no mod's. Still I need to exchange my DI, it doesn't look like 3g's is going to turn on.
My real issue is still getting custom recovery off and stock recovery back on, then unrooting will be a breeze. The videos you lead me to are one of the sources I have been working with, however to reverse the leaked ota, Downgrade leaked ota video, requires SDK and adb knowledge, this is where I am noob. At this time my VZW manager who is in school for programing is attempting to help me (he has a over clocked Palm Pre Plus, 1Ghz), this is very cool of him, well beyond what is expected. (I am in no way encouraging anyone to rely on their VZW employees for this kind of help, this is a unique situation, I have been building a relationship with my VZW guys for two years+, not all VZW employees have a clue about mod's, and mod's technically void the warranty) I am hoping to learn enough about these tools, SDK and adb, to help myself before the next time, and I will hopefully be gaining some of this knowledge from my friends at my VZW store soon. I will also be looking forward to the help I receive from fine people such as yourself and people in this community in future endeavors.
I will stop basically hijacking this thread now
Thanks to all of the people who support these community's, with out whom many of us would never get our foot in the door. Much appreciation to ACD168 for being there to help me.
Take the time and learn to do it right the first time.
Click to expand...
Click to collapse
First off, you are very welcome my friend, anything I can do to help do hesitate to ask!, and your not hijacking any thread brother, that's what these threads are for!!!
Thats real cool of the VZW employees!!
adb and sdk isnt that difficult I can help you!!
Read my post about warranty exchange.
I know alot of people are "better safe than sorry" mentality. but I have returned 2 phones that were fully rooted, updated, s-off running custom roms and I had no issues. in fact ive never had an issue using warranty exchange. ive exchanged phones that I broke (like broke.. with pieces coming off). I just call and tell the operator lady my phone doesnt work, i dont know why.. it was just working earlier and now it wont turn on.. they send me a new phone and I send back the broken one and everyone is happy.
They only confirm that the numbers on the phone match your account. Not the reasons you are sending it Back. the warhouse guy that opens your box isnt the same guy you talked to, nor do they have information about your phone call to the tech. They simply open the box, scan the numbers and move on.
dont stress to much about it
Great info here
Thanks to every one of you on this thread. I am finally breaking free from WinMo and getting Dinc after a lot of research. I like Verizon but hate the bloatware they pack onto Androids and all the other phones, so I will be fiddleing with ROMs. If I screw up I am looking here first to see how to get it back to stock so I can get my new one with the insurance coverage.
Everytime I get to serouosly looking around these forums I learn great new stuff. I will donate to the XDA someday soon!
Okay. so im a noob. Just need to ask. What do you guys mean by stock recovery? I just rooted my phone but need to unroot to send it in for work at Verizon. Could you help me out?

HELP! Failed to boot! Can't start RSD or Fastboot support

I am currently unable to boot into anything, no RSD, no Fastboot nothing. I try holding down up volume and down volume. Here's what it says when i try to power up.
SVF 105:1:2
Failed to boot 0x1000
Here's what i did.
I followed the steps exactly to install the stock 2.3.4 ATT update. Everything was fine. Then i decided to start over and install kennethpenn's custom rom. So i tried to flash the 1.8.3 sbf.
i foolishly started surfing other websites and didn't pay any attention to my phone. then when i looked back it was completely black screen and RSD lite said:
Failed flashing process. Failed flashing process. Phone {0000}: Error switching phone to BP Pass through mode (0x70BE); phone disconnected
Thats it. now i can't do anything. Please help.
It's called "bricked". Now search for that term and you'll find answers!
Yeah, I think you're screwed their man... Kennethpenn had the same issue with his Atrix I think.... $600 brick
doesnt sound good...
where in the process exactly did you decide to start over and install kenneths custom rom?
i know its bricked. i'm just wondering how bricked...
i was in the process of starting over to install kennethpenn's ROM. i was flashing the full 1.8.3 sbf.
do you think ATT will take it back under warranty if i play dumb?
b3nman said:
i know its bricked. i'm just wondering how bricked...
i was in the process of starting over to install kennethpenn's ROM. i was flashing the full 1.8.3 sbf.
do you think ATT will take it back under warranty if i play dumb?
Click to expand...
Click to collapse
Well you got nothing to lose.
i
i have the same problem gonna play dumb and get a new one today under warranty
yokozuna82 said:
i have the same problem gonna play dumb and get a new one today under warranty
Click to expand...
Click to collapse
Nice. Tell us how it works out, good luck!
yokozuna82 said:
i have the same problem gonna play dumb and get a new one today under warranty
Click to expand...
Click to collapse
What did you do to cause it? Same thing as OP?
I'm tellin ya I think there is something wrong with that damn 1.83 sbf itself! The older ones never had any problems! I'm done with it!
LayzeeEyez said:
What did you do to cause it? Same thing as OP?
Click to expand...
Click to collapse
yeah, has anyone else tried to flash back to 1.83?
b3nman said:
i know its bricked. i'm just wondering how bricked...
Click to expand...
Click to collapse
If it does not go to the moto logo screen that means something messed up your IPL/Bootloader, which means you are pretty screwed.
b3nman said:
i was in the process of starting over to install kennethpenn's ROM. i was flashing the full 1.8.3 sbf.
do you think ATT will take it back under warranty if i play dumb?
Click to expand...
Click to collapse
You could just say that you never got around to updating to 1.8.3 (kind of a long shot since it reminds you every hour), and when you installed the update it would not restart. If you have a backup phone, you could just wait till the new update releases and use the same excuse.
If you hard bricked, there is most likely no way they can check if you were messing around with anything. It is worth a shot, but like you said just play dumb
http://forum.xda-developers.com/showthread.php?t=1160408 <- For future reference
im sorry this happend to you guys, i hope everything goes well with insurance and what not. i made a warning on the guide for people not to flash back until a safe method is found!
i had ur problem a few seconds ago!
rsd stoped at " switching phone to BP Pass through mode " at 33%.
and after a hour nothing happend!
i decided to disconnect the phone but after that i lost RSD,fastboot,.....
i removed the battery for a while and after that i powerd the phone up but it was the same as before.
i left it on moto red logo and after a few second it said:
failed to boot 4
starting RSD mode
and now its working!
but i didnt get " Failed flashing process " like you!
i got one coming through warranty be here no later then tuesday
i guess i didn't understand the warnings. now i see them, only too late. it seems like att will send me a new one.
b3nman said:
i guess i didn't understand the warnings. now i see them, only too late. it seems like att will send me a new one.
Click to expand...
Click to collapse
anyone have a cwm backup pre 2.3.4 they can try?
att is sending a new one. it was easy since i'm still within the 30 days of opening my account. lesson learned:
THOROUGHLY READ ALL WARNINGS!!! I hope my fail can prevent others from going through it. THANKS EVERYONE!
is this 4.5.91 specific? I flashed between 4.5.40 and 1.83 sbf a few times without problem.

[Q] HELP: myTouch 4G Soft Bricked After Downgrade

Hello, xda-developers,
I have a myTouch 4G that was updated to the 2.3.4 Gingerbread software and wanted to root it. In order to do so, after many research, it states that there is no root for the 2.3.4 Gingerbread software and for it to be rooted you'll have to downgrade it.
The reason why I wanted to root it is because I am having a problem with the WIFI connectivity in my home and was wondering if it will fix it. Same reason why I update it to the 2.3.4 Gingerbread software in the first place. The myTouch 4G that I have will "RARELY" connect to my wireless router in my home but for some reason it doesn't fail me when connected to other wireless routers outside of my home even when having the same router. But this is now not the problem.
As you can read, the title says it all. My problem now is that I just soft bricked my myTouch 4G after a downgrade that I followed here: http://forum.xda-developers.com/showthread.php?t=1178912# Like the noob always say when something goes or went wrong, "Boohoo, I don't know what I did wrong. Someone, please, help me." But I THINK I know what I did or went wrong.
I followed the guide strict and carefully hoping I don't brick it but then I said to myself, "It's a 99.9% chance I won't, I think... what can possibly go wrong?" Everything went well. I did everything it says and once the update bar fills up to the top, BAM! It hits the "T-Mobile myTouch 4G" boot screen. I was happy. Very happy because I felt accomplished and one step closer to excitingly freeing my phone. But my hopes went down when it stayed like that for hours on end. I pulled the battery out and reboot it and nothing was fixed. Although it was stuck, I still can access the bootloader. I pulled out the battery again and boot it to the bootloader and re-updated it again and nothing was fixed. I yanked out the battery one last time and deleted the PD15IMG.zip file from the SD card to keep it from asking to update everytime I boot it to the bootloader so I can factory reset it but, still, that didn't help.
Like I said. I think I know what I did or went wrong. Examine the guide. The "Gaining Temp Root" part I did right. The "Changing Version Number to Allow Downgrade" I did correct and the results on the command prompt came out the way it stated it should come out. THEN! I yanked out the battery to reboot it after that. When I've done so I continued to the next procedure and everything went how it says it should go but, instead of the end results, I got it stuck on the "T-Mobile myTouch 4G" boot screen after the update. I think that's where I messed up. When I yanked out the battery to reboot it after the "Changing Version Number to Allow Downgrade" part. I believe it kicked it out from root. It is a temp root by the way and I read it somewhere that said, "Once you're rooted you CAN downgrade it." Something like that which made me think it wasn't rooted after that reboot and the downgrade wasn't a success. I also have two other guesses in which I think soft bricked the phone. I either have a bad eMMC-boot or the PD15IMG.zip was bad. These are my thoughts in what went wrong. I'm asking for your help. So can you help me find the solution to this problem?
Thank you very much in advance for your time and effort into reading this and helping me out. I really appreciate it.
-Victor​
P.S. Here's the information on the myTouch 4G's bootloader:
GLACIER PVT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Apr 14 2011,13:18:22
Again, Thank you.
wow, same thing happened to me.
You could try updating it back up to the 2.3.4 RUU. If that works, nothing lost at least.
You used a wrong PD15IMG, most probably.
If you have used the correct one, your bootloader would be 0.86.0000, but it isn't.
Please re-download the correct PD15IMG and try again. When it works, if it throws any messages - write them here, so someone will be able to help you. If you see "Fail-PU" - your phone is dead.
Your mistake might have been removing the battery instead of typing "adb reboot bootloader". Yanking the battery off a working phone can destroy its eMMC. If that's what happened to you - well, you can replace your phone under warranty and follow the instructions better next time.
It was definitely the part where you yanked out your battery. You lost temp root then. Why you did it, not sure. But it's already been done so Let's not linger.
Have you tried starting over from step one?
Sent from my HTC Glacier using XDA App
You used a wrong Rom to downgrade or it is corrupted during download.
Download the official 2.2.1 rom, put it to the root of your sdcard, and try to update.
The original bootloader is 0.86.0000
You can download it here
Rename it to PD15IMG.zip before updating.
Do what he said
Do what the last guy said and rename the image and flashing.
Here is what has happened, you were probably installing a signed downgrade to a previous version. Either you got the wrong file, your download was corrupt (THANKS TO CHROME), or you didn't clear your cache dalvik needs to be clear if you run a different kernel. The main cause of hanging at the bootscreen is the incorrect cache either regular or dalvik. Thats what I've noticed from threads and just in general.
You don't appear to be running clockworkmod recovery. If you are going to mess with the system, DO IT ALL THE WAY! Don't get confused with this one... if you are planning to write radios, flash updates, or do anything YOU WILL NEED ROOT. This is because something could go wrong and you could be locked out. If you aren't willing to commit to basic root privileges, do not attempt to downgrade. Either go all the way, or don't go at all. That's just some friendly advice cause people will make the misconception if they just downgrade thats fine, but getting root is more dangerous... not true! If you have root, you can actually gain control of the phone and restore even a 'broken' one.
ROOT is mostly gained from within the phone in the operating system. You use an APP to gain root privileges. Once you get root, you need to get SU a program to grant privileges to programs that request them. Then you need to get clockworkmod rom manager so you can flash a recovery (internet and market access is required unless you can install from the .apk and use adb). ONCE YOU HAVE THAT RECOVERY you can downgrade, upgrade, flash, flex, backup, restore all with a simple push of a button, no expertise required!!
You can even revert to stock easier when you have root.
Once you get that recovery installed then look for ways to turn s-off and unlock your sim so you don't have to worrry about stuff.
And remember, they might not honor your replacement phone if you hack or modify it... but if you lose the phone they will replace it for you.
Big Thanks For the Help!
Hello, xda-developers,
Thank you, all, for your help! I've figured out the problem.
It was because of the PD15IMG.zip file. It was a bad one and I figured it out by downloading another one BUT, instead of downloading it from the same site I got it from, I downloaded it from a different site. I've barely figured this out and I could have fixed this problem way earlier if I had checked back my post.
Big thanks, again, to you guys for taking your time and helping me figure out this problem. It has been a month since I've been "Android-less" and now I am going to treasure it more than usual and I can not lie... I miss its awesomeness.
My phone is now back and it is officially perm-rooted! Love this phone more than ever with all the things it can do now. Rocking this phone out now with the Virtuous Unity rom and it blows... me... away!
-Victor​
Well..... at last you figured it out.....Iam happy for you....Try Virtuous Unity 2.39 you will really love it.
By the way, where did you get the PD15IMG.zip file???? Can you post the link, so that it will be easy for others with similar problem.
Thanks! You're right, I am trying out Virtuous Unity 2.39 right now and I love it. I was actually looking for an android "bone-stock" gingerbread rom but I can't seem to find one without the customization. Then I bumped into this one. They say sense 3.0 were only made to work on dual-core phones... they were wrong. I really love this rom and I'm sticking to it. Until I find a stock gingerbread rom that has been perfected for the myTouch 4G. You know, the one without the customization.
Oh! Here's the link where I got the radio (PD15IMG.zip) from: www1240.megaupload.com/files/89ce9e2eeb86bb659eceb64baa356c4b/PD15IMG.zip
Since I'm a new member of the xda-developers forum, I couldn't post a link. So, instead, here's the address.
So have you tried the link in my post? Did it work for you?
The link for the PD15IMG.zip radio? Nope. I went onto googling it and finding one myself. The link for the stock myTouch 4G 2.3.4 rom? Nope. Not a big fan of the myTouch 4G's overlay.

Semi-bricked DHD

Evening all,
I have a DHD that is stuck in HBOOT/FASTBOOT, or at least that and the stock recovery program is all I can get to.
I tried an AAHK, and it basically tried to do a downgrade and has left the phone with no data, still at s-on, and I can't find an operator RUU(three uk) to flash it back to a useable state.
Is there a three RUU available?
I'm running around in circles as I can't make a gold card, due to not having another DHD available to retrieve the MMC2. All I need is a goldcard and then I can flash a WWE, but I cant find anywhere to make one without the phone or a similar one.
I dont think it turned the microsd properly into a gc, before it tried to downgrade. Is their anyway I can test to see if the memory card has been successfully goldcarded?
Any help would be greatly appreciated.
Thanks
James
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Teichopsia said:
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Click to expand...
Click to collapse
Mine has a lot of those symptoms to be honest. If I vol down/power to get to Hboot, it sits there with no keys being able to be pressed, just highlighted blue FASTBOOT and not even checking for files on memory card
If I just turn it on, it sits at the three splash screen, which i assume is the equivalent of the HTC one for branded phones.
I have now turned it on and left it on as per those linked threads, in the hopes the sd is a proper gold card and it is just slow. Fingers crossed.
Thanks for the pointer
James
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Teichopsia said:
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Click to expand...
Click to collapse
Well what I did, was follow the AAHK instructions, cleaned up my environment etc, went through the install. When it asked to do the downgrade, I said yes, then it asked about wiping and was I sure, so I said yes. It then rebooted the phone and it is now as it is. I pulled the battery and tried vol-down/power, which brings up HBOOT, but it doesnt let me do anything, vol keys and power do not work and it doesnt start looking for image files.
From that thread, it was mentioned it just could be going very slow, and people have just left it overnight. This is what I have done now, and will see if it has accessed the files on the memory card and downgraded properly in the morning.
Thanks
James
Have you tried looking for the RUU here?
Last I remember when aahk downgrades, you will be asked to reboot to basic recovery twice
Panic over, thankfully! Not my phone, you see!
It was so easy to root my S2 and the X10 before that, and the iP3G before that(and custom winmo, and nokia etc etc), I said give it to me, i'll sort you out with some ICS rom action.
Then it all went wrong as explained in my previous posts.
2 days later, i finally found the H3G RUU I needed to get an system on it. Silly branded phones. Took 4 hours to download as it was on a throttled download service(my 100MB leased line usually eats 300MB in seconds, but not this time)
So long story short, into FASTBOOT USB, ran the RUU and it completed and put froyo on the phone, and as a happy coincidence it was at a level that didn't need a downgrade, so AAHK ran through like a trooper, busybox installed and hey presto, ENG S-OFF. IceColdSandwich installed through cwm and one happy mate, who then proceeded to ring his wife and tell her to rent a film, as he would be tinkering with the phone all night lol
It was getting to the point I was going to have to give him my S2, and as I've just taken possession of a Sony SmartWatch, I didn't want to do that!!
Thank for everyone's help and pointers, not sure what went wrong the first time(probably a memory card/incompatibility/goldcard problem), but all sorted now.
James

Categories

Resources