Database Users

A newbie who screwed up

Hi everybody. I'm Quistnix and I'm a compulsive tinkerer.
Whenever I get my hands on a new piece of hardware, I just have to fiddle with the software. My iPod Touch has been jailbroken, bricked, unbricked, re-jailbroken, broken, repaired and jailbroken. My pc has been running a lot of different editions of Linux and Windows, and has been screwed even more times when I tried to install those.
To the point: I'v got a HTC Magic (32b) and I'm very happy with it. However, I just had to go and put some custom roms on it. I was kinda overconfident and hopscotched from one guide to the other until I got a result I liked. Unfortunately, the end result turned out to be a phone running Android Dev Phone 1, Firmware 1.6 without any backups to restore to.
In it's current state wifi won't run, I don't have root access, Recovery Flasher returns "Flash FAILED.", Terminal won't give me SU rights and it's one of those 'perfect' devices that don't allow fastboot.
Apart from those issues everything seems to work fine, so if it's going to stay like this I'll still end up with a great and perfectly functional phone. Still, I'd like to ask if there is a way to either get it back to its original state, or to make it run a custom rom.
Any help is greatly appreciated.

Quistnix said:
Hi everybody. I'm Quistnix and I'm a compulsive tinkerer.
Whenever I get my hands on a new piece of hardware, I just have to fiddle with the software. My iPod Touch has been jailbroken, bricked, unbricked, re-jailbroken, broken, repaired and jailbroken. My pc has been running a lot of different editions of Linux and Windows, and has been screwed even more times when I tried to install those.
To the point: I'v got a HTC Magic (32b) and I'm very happy with it. However, I just had to go and put some custom roms on it. I was kinda overconfident and hopscotched from one guide to the other until I got a result I liked. Unfortunately, the end result turned out to be a phone running Android Dev Phone 1, Firmware 1.6 without any backups to restore to.
In it's current state wifi won't run, I don't have root access, Recovery Flasher returns "Flash FAILED.", Terminal won't give me SU rights and it's one of those 'perfect' devices that don't allow fastboot.
Apart from those issues everything seems to work fine, so if it's going to stay like this I'll still end up with a great and perfectly functional phone. Still, I'd like to ask if there is a way to either get it back to its original state, or to make it run a custom rom.
Any help is greatly appreciated.
Click to expand...
Click to collapse
have a look at the numerous threads on how to replace the perfect SPL with goldcard method. once you're done with that, replace the recovery, choose a rom and flash.

nmesisca said:
have a look at the numerous threads on how to replace the perfect SPL with goldcard method. once you're done with that, replace the recovery, choose a rom and flash.
Click to expand...
Click to collapse
Thanks a lot, I'll give it a shot tonight

In case somebody else stumbles upon this thread with the same problem:
Using Jester's guide I created a goldcard, and Amon's guide helped me to un-perfect it. After that I could one-click-root without trouble.
I'm currently using the build installed by the ROM v2.16.707.3 from Amon's guide, and it's great.
The only problem left is that I tried to install Amon's [ROM] [32A & 32B] [10-Oct-2009] RAv1.6.2 and got stuck with a never-ending boot screen. This was easily reverted with a backup. I´m going to try installing another rom soon, to see if that helps.

the reason you got stuck in a boot loop is because you didnt wipe your ext partition. you can do that using amon ra's newest recovery. easy peasy lemon squeezy. you need to wipe whenever you flash a new hero rom or any other now now-a-days. do you have adb set up?

edit: Never mind, it's all running beautifully. Thanks!

Unrooting then rooting again

Hey guys. So after one disaster after another, the G1 my friend has won't update the radio, which does not allow the speaker to play. Also, it won't boot up to recovery it just goes into that multi-color color screen whenever I try to boot it up. Now that I'm more experience with rooting android phones, does it seem to be a good idea to load up the dreaimg.nbh file and re-do the root from the start? Or should I just leave it as is. My main concern is that it will still not be able to install a recovery image. What do you guys think?

I would stay away completely from someone else's phone bacause if anything goes wrong - you're responsible. But, if you're determined, flashing dreaimg.nbh will reset your friend's phone to stock and, if anything, it can be updated to stock 1.6 firmware. Or you can try your luck and re-root it properly.

Easily gain root access without flashing
borodin1 said:
I would stay away completely from someone else's phone bacause if anything goes wrong - you're responsible. But, if you're determined, flashing dreaimg.nbh will reset your friend's phone to stock and, if anything, it can be updated to stock 1.6 firmware. Or you can try your luck and re-root it properly.
Click to expand...
Click to collapse
Try " universalandroot.apk 1.6.2-beta5 " works a charm on htc g1 allowing to switch between root and unrooted within seconds using the free app to install on your device, gives super user permission....No flashing involved to burn out your device..

[Q] g2 perm root help

So, this G2 is my first real phone, and I was really excited about rooting it and putting CM6 on it so I've been reading and trying to learn as much as I could so I wouldn't end up screwing things up. However, I'm stuck in a peculiar situation.
First, I'd like to point out I don't have a computer I'm able to download any programs to (android dev tools like adb). I can use my brothers computer to download files onto my phone, I just aren't able to install programs to his computer. So, any advice would be appreciated if it took that into consideration.
Anyway, I'd been keeping up with the VISIONary updates since about r8, and when it got around to r13 I tried to do the perm-root. It didn't work, and so I tried to read and troubleshoot the situation. I saw a couple people talking about temp-rooting, doing clockwork recovery, and then rebooting and it working out alright, so I tried that. What I did was I temp-rooted with VISIONary, did the clockwork recovery and then tried to reboot and perm-root the phone. Unfortunately, what's happened is that I can't get even get temp-root anymore.
So, I guess what I'm asking is simply this, is it possible to fix my g2 and get it rooted using only the phone itself?

Clockwork Recovery still starts on bootup

Ok, I installed Clockwork a while ago, then removed it and unrooted (I no longer needed root access, and I'm not doing any image flashing or anything that requires it). But after removing clockwork, it still boots to that first when I reboot my phone. In case if I ever have to take my phone in to VZ or something, how do I stop it from booting to that? I'm guessing it's not just a normal app, since I've reset to factory since then to try to resolve another issue, and it's still appearing, so I'm guessing it installed itself into the ROM.
I basically rooted my phone originally to install Titanium Backup before doing the factory reset, then I was thinking of trying some custom ROM's, but I decided not to (other than a performance increase, there's nothing else I really care about right now that custom ROM's would provide). So I installed Clockwork Mod and everything else RLM703 listed (http://forum.xda-developers.com/showthread.php?t=814299&highlight=guide), then removed everything after I decided not to mod it.

I can understand your concern on the not flashing, however if you do not flash i think you also still have the Superuser app (even ifyou dont have root rights) that itself would also void your warranty. The easiest, fastest, and safest way is to Flash it using the Method below.
Go To (droid-life .com /2010/09/21/how-to-return-droid-x-back-to-android-2-1/)
((**As a new user i cant post outside links so delete the spaces after life com in order to get the proper working link.))
**
You will download 2 things. The SBF for 2.1 (Which afterwards you can use OTA to reupdate to 2.2).
RSD Lite: This program is used by Motorola to flash phones so its not some unstable application that will mess up.
After you install the drivers, THEN install RSD Lite. You must Run RSD Lite as an administrator. Shift Click RSD Lite and choose Run as Administrator (Even if you are on an administrative account). Afterwards you just navigate from RSD lite to where you have your SBF Saved, Boot your phone into bootloader, then press start. Takes about 5 minutes and you are back to a brand new Droid X.
Like i said i understand your concern on this, and im deeply sorry if you get a rare case and it does decide to mess up, but i just flashed my phone 3 times yesterday using this method and never had a problem.
Hope this helps!

Ok, I know I created a backup through ROM Manager before I stalled Clockword Mod Recovery, but now I can't find it... However, I've been having some minor issues with my phone ever since I updated to 2.2, so maybe I'll just find a stock SBF and flash back to that... That link I posted has a droid x guide, with a link to a stock 2.2 SBF, so I can just grab that and flash it tonight or something. Or even just download it at home and keep it in case if I need it down the road...

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