Database Users

unrooting for warranty

So after hours of searching, and being on the verge of tossing my phone against the wall I am asking if anyone has the stock rom zip file that I can flash. Everything I am finding leads to broken download links, or corrupt files.
I have also tried to get HTC sync to work, so i can just flash the new update and be done with it. But I can not get HTC sync to see my phone, no matter what rom Ii flash before hand. I currently have a old reworked 2.1 rom, was hoping that would be seen by HTC sync.

Uhhh dude so are you trying to push it back to stock? If so, google FROYO 2.2 official mytouch 3g slide an their should be a thread on tmobile.com saying something like "ladies and gentlemen, froyo 2.2" (or a variation of that) an it will hav instructions on how to install Stock 2.2 froyo! I hav rooted and unrooted my phone 3x literally with it (if I get bored with root I go back to stock, and vice versa) and if you ever want to re-root, go to my thread in this forum (how to get the most out of your slide) and I hav a link on how to re-root your device. I really hope I answered your question!
Sent from my T-Mobile myTouch 3G Slide using XDA App

http://forum.xda-developers.com/showthread.php?t=946435

lolToasty said:
http://forum.xda-developers.com/showthread.php?t=946435
Click to expand...
Click to collapse
Thanks, going to do that one tonight. Not sure how I missed it, I must have assumed I already looked at the thread just from reading the title?

ended up unrooting it before work, and updating to 2.2 just to be safe. Everything went smooth, other then having to restart the update process when I hardly bumped my usb cord disconnecting it. But that was the reason for the warranty.

the stock esprimg.zip file can be flashed via rom manager OR recovery and then do the update to 2.2 using HTC sync, just FYI if anyone wanted to know.

I tried flashing the esprimg.zip through rom manager, and had no luck going that route. Its been so long since rooting it, I didn't think to load the esprimg using the vol down/power combo.

You're always safer doing it from recovery as you can get some bad results doing it through rom manager.

[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.

need to get rid of super user! tried almost everything please help

So i read off a guide how to get rooted from a chinese program etc. now i just want my phone squeeky clean just like how i bought it so i can follow a LEGIT guide on this forum to get ADB, root, TWRP or CWM and flashing roms working again. Iv never flashed one rom on this yet. If i download the stock LG G2 T MOBILE build and put it onto my phone. Will it remove the chinese super user/root off of it?
I can enter downloade mode so that is no problem.
Thanks again!
I just need my phone like it came from the manufacturer so I can start rooting knowing that there won't be issues in the future

[Q] Stuck. Anybody have T-mo Froyo SBF and/or advice?

Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?

richdaley said:
Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?
Click to expand...
Click to collapse
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.

richdaley said:
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.
Click to expand...
Click to collapse
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.

hotdog125 said:
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.
Click to expand...
Click to collapse
Beautiful. It worked perfectly.

[Q] Accidentally killed stock recovery

Hello everyone! I'm brand new to the forums so if I am breaking any rule or regulation, just give me a heads up. So, some basic information about my predicament.
- own a Samsung Galaxy Note 3 from Verizon.
- I use t-mobile network. Works great with no problems.
- phone was successfully rooted via towel root.
I was looking to get cynagenmod on the phone so I started looking up guides and such. Only thing I wasn't aware of was that carrier branded versions can't have their recovery flashed. That said, I used flashify and the clockwork apk. The app did its job, killed the stock recovery, but couldn't load the new one. Now the phone says error, no recovery when trying to access it during boot.
It should be said that the phone still boots and works normally but I really want to get the recovery working so I can at least try again the right way to get cynagenmod working.
My question is, is it possible to get my hands on the stock recovery for my phone and just flash it back to how it was? Basically, how do I fix this problem I put myself in. Of course, I didn't make backups. During the whole process, I figured "if I follow this tutorial word for word, why bother with backups?" look how wrong I was
Any help would be sincerely appreciated. I'm posting this from my replacement phone, not my note 3.