Develop Bugs

Problems with ROOT, Am I bricked!???

I was rooted and running a 2.2 rom and wanted to install the damagecontrol 3.2 rom, which, as I understand it, requires NAND to be unlocked. I downloaded Simple Root and tried to unlock NAND.
When I turn on the phone I get stuck in a boot loop.
I try the recovery console. It takes a few minutes to load PC36diag.zip, the update for NAND which I already installed.
When I say no to the update and no to restarting I get into the menu, but if I try RECOVERY it loads the phone with the exclamation point, but I am unable to connect using the adb batch file I have always used before.
Also, when I try HBOOT USB the drivers aren't able to be installed. The device is read as "Android 1.0".
Can someone please help me?

devin.slick said:
I was rooted and running a 2.2 rom and wanted to install the damagecontrol 3.2 rom, which, as I understand it, requires NAND to be unlocked. I downloaded Simple Root and tried to unlock NAND.
When I turn on the phone I get stuck in a boot loop.
I try the recovery console. It takes a few minutes to load PC36diag.zip, the update for NAND which I already installed.
When I say no to the update and no to restarting I get into the menu, but if I try RECOVERY it loads the phone with the exclamation point, but I am unable to connect using the adb batch file I have always used before.
Also, when I try HBOOT USB the drivers aren't able to be installed. The device is read as "Android 1.0".
Can someone please help me?
Click to expand...
Click to collapse
Bootloop means you need to do a full wipe.
First thing's first, delete the PC36IMG.zip file from your SD. Then when you get the image of a phone with an exclamation mark, hold down the power and volume up key to get into recovery.
As for the last bit, I'm sorta' confused what you're problem is.

Part of my problem is that I can't delete the file from the SD card. Can't get into the OS and can't turn on USB.

Something similar happened to me. For me, instead of booting Damage Control, I switched it to Fresh and booted Fresh v3.0 and it worked and booted. Then I unlocked the Nand and made a nandroid. Then whipped everything 2 times and booted DC and it worked fine after that.

devin.slick said:
Part of my problem is that I can't delete the file from the SD card. Can't get into the OS and can't turn on USB.
Click to expand...
Click to collapse
You can get in to usb and put fresh on there by going to recovery mode and selecting one of the options that says USB, i can't remember the exact wording.
Added: I just checked it's called "USB-MS toggle"

devin.slick said:
Part of my problem is that I can't delete the file from the SD card. Can't get into the OS and can't turn on USB.
Click to expand...
Click to collapse
When you get the exclamation mark screen, hold down the Power and Volume Down key. Once in recovery mode, select the USB-MS Toggle feature, this mounts your SD card yto your PC. You should then be able to access the root of your SD card via the Removable Disk icon on your computer.

It wouldn't let me load USB from the console/whatever either... Another weird driver issue.
But after several more hard battery pulls I let it try again to boot and it showed me the "HTC, quietly brilliant" boot screen, which was different that what it had before.. I let it load and now I'm in android, but it says my SD card is removed.
Is this a part of the process necessary to unlock NAND?... Do I have NAND?

devin.slick said:
It wouldn't let me load USB from the console/whatever either... Another weird driver issue.
But after several more hard battery pulls I let it try again to boot and it showed me the "HTC, quietly brilliant" boot screen, which was different that what it had before.. I let it load and now I'm in android, but it says my SD card is removed.
Is this a part of the process necessary to unlock NAND?... Do I have NAND?
Click to expand...
Click to collapse
Check and see if your USB connection is in Charge Only or Disk Drive mode.

devin.slick said:
Is this a part of the process necessary to unlock NAND?... Do I have NAND?
Click to expand...
Click to collapse
no. You make your nand back up when you are in recovery mode and you select nand back up and it backs up everything. You'll need to follow through with the rest of the Nand unlocking instructions.
Did you download and follow the steps of the flash_image and mtg-eng.img etc etc...? Then the rest of the steps?

That's the first thing I tried to do when android loaded. It's not even an option. It says I removed my SD card.
I restarted, denied the update to get through to recovery, and I still can't connect with adb -it shows "Unknown Device" in the device manager.

devin.slick said:
That's the first thing I tried to do when android loaded. It's not even an option. It says I removed my SD card.
I restarted, denied the update to get through to recovery, and I still can't connect with adb.
Click to expand...
Click to collapse
are you connected with charge only? try hot sync (you need to install the program, which include drivers. this is on the htc website)
Mine worked for hot sync but not charge only

Looks like you may need to run through this. http://forum.xda-developers.com/showthread.php?t=695243

I've been reading that post.
When I select fastboot, it gives me other options.
bootloader
reboot
reboot bootloader
powerdown
If I select bootloader it takes me back to the main menu, if I select reboot, I get back to android and still do not have access to my SD card, so I can't get out of the debugging rom, or whatever it is.
I put another SD card in, so I don't have to wait on the update.zip to be read every single reboot, but that's all it did.
Am I doing something wrong?

Don't know then... sorry. You can try starting over from the beginning?
Best of luck.

FML.
Someone? I'm totally stuck.
And my phone says the the charger isn't delivering sufficient voltage... and I'm down to 8%.
HEEELLLPPP

its always an good idea to have a micro sd to sd adapter

After 3 locations, I found a Sprint store that actually existed... had them copy an update.zip that I brought on a flash drive onto my micro sd card. I tried booting into recovery and it didn't do the update. They suggested another store that does repairs, so I went to my 5th store, where I just dropped off my phone, hoping they'll reflash it fore me. I'm expecting a call back.
What a wonderful birthday this is turning out to be... lol. FML
UPDATE: I called them and they said the phone needs to be exchanged... but I don't know how they're going to react to it having the recovery/debug version of android on it.
Does anyone have ANY advice?

Just tell them to put in a fully charged battery for you. Then when you get it home try the Simple Root Guide you tried at first. This time post your issue (if you have any others) in that thread and myself or Jiqqa will help. Make sure before starting that guide that you have .NET framework and HTC sync installed on your computer. But you should be able to root phone and then be able to flash custom ROM after that.

Root/Rom Help Needed ASAP!!!

Here is my issue..I have been rooted since I got the phone and actually rooted both of my EVO's. Last week I decided to go back to Fresh Rom 1.0 and inadvertently flashed a new theme at the same time. Did not flash the ROM and then go back in and flash the theme. As a result, the phone went into a continual cycle of rebooting the loading screen ( for Fresh users you know it has the little guys and says FRESSSHHH). Well that happens over and over again.
The only option I have is to take battery out and go into the bootloader mode. MY problem is this:
* Once in bootloader mode, I can't reflash because when I go into the recovery mode, the recovery says " ADB server is out date" and scrolls thru a few lines an disappears. I've tried every thing suggested to me and still have not been able to fix that.
* Cannot access root of SD card because system doesn't recognize the phone is attached.
* Tried to load PC36IMG file on the card manually and that loaded but I can't get to the restart option. It finds the file but does not give me the restart commands.
I'm at wits end right now. I tried the OTA Recovery but since I cannot connect to the computer, it won't run either.
Please help......

Restore a nandroid.
RUU start over.

I tried to do that but the computer - htc sync won't recognize the phone so I can't RUU again. When I get to the end of the process it tells me either the phone isn't connected to the USB or the USB isn't connected to the computer.

You phone says the ADB server is out of date when you boot into recovery?
It sounds like you are not completely rooted.
You should be able to volume down and power on. Then choose recovery. From there you can restore a backup. That should also give you ADB access to the phone (if you are fully rooted)
If you are not fully rooted, and you have to run some bat file on your computer to get the phone into full recovery, you may be skrewed.

No, the computer says that when I go into recovery mode and have the black screen and red triangle on it. I then go to the computer and try and run the recovery file that I've been running as I've flashed 10-12 ROMS already. The CMD screen on the computer comes up as ADB Server is out of date...and another line or two scrolls by and then it disappears, never connecting to the phone and going into the next screen where I can wipe or flash from SD..etc..

Sounds like you did not complete step 2 of the root process. You should be able to enter recovery without the use of a computer.
Reboot your computer and try again, if you still get errors then I am out of tips.

Samsung S3 (tmo) soft bricked, encrypted, USB debugging off

Hi,
Summary: Was running Cyanogenmod 10.2.0 and tried to update to 10.2.1. Phone won't boot. Using CWM recovery 6.0.4.3. Factory Reset reports that it can't mount / clear /data (due to encryption?). Can get phone into CWM recovery and Download mode. Haven't been able to successfully connect to PC (ADB or Odin) even though I have samsung drivers.
I do have an unencrypted SD card in the phone so my normal way of flashing is to connect SD card to PC, download, then in CWM recovery to install ZIP from SD card.
Looking to get into any good state - Cyanogenmod 10.2.1, or 10.2.0, or heck go back to stock.
**** I think the answer might be use ODIN and flash back to stock, I see some guides but haven't been able to get ODIN to "see" my phone *****
Details
I had downloaded Cyanogenmod update to phone using "About this phone" menu and when I tried to "Install it" from that window the machine booted into recovery, immediately failed, and rebooted. The phone is encrypted (work requires this) and I discovered Cyanogenmod saves the download to encrypted phone storage and CWM recovery doesn't support encryption.
Downloaded 10.2.1 to my SD card and flashed it. (no back-up, no wiping of cache). Installed successfully, reboot asked me for my encryption password, Android optimized apps, rebooted, encryption password, then blue spinner spins forever.
From here I started my troubleshooting:
- I flashed back to 10.2.0 then flashed Gapps again, no change.
- Reading about boot.img I installed ADB and SDK Manager and tried connecting and flashing boot.img. ADB devices shows up empty. I have installed Samsung drivers.
- Researching going back to Stock points me to installed Triangle to reset my custom ROM count - but I can't boot.
Thanks in advance.
Matt

[Solved] This is for anyone who happens to read this wondering if their phone is screwed. Relax! If you can get into Download mode and Odin can see your phone, you'll be o.k.
Turns out the machine and cable you use do matter. I tried for days connecting using my MAC running Windows 7 Virtual Machine. Once I switched to my Win7 laptop and used the original Samsung cable things starting working out more smoothly.
Steps:
1) Get Odin (mine was 3.09) and run as admin. If you see an error in Korean it's because you have to unzip the entire Odin folder.
2) Get stock firmware for t-mobile. There's only 1 firmware file, I didn't need a PIT nor a specific recovery step. The t-mobile firmware includes everything I needed. Flashing failed in Odin saying Complete Write failure. This had me stumped for hours and hours. When I switched to stock cable and Win7 laptop it succeeded. I never had to check Nand erase all or repartitian (almost did in desparation though). Flash took about 10 minutes but eventually PASSED.
3) However, when it rebooted it asked for encryption key and my old one didn't work. Turns out their are more steps. This scared me.
4) Reboot into recovery (up, home, power) which gave a bunch of scary error messages. Actually those listed at the bottom in http://forum.xda-developers.com/showthread.php?t=1840030.
5) Factory Reset then Wipe Cache
6) Reboot
Now I'm back at stock and breathing a sigh of relief. Unclear if I'll ROM back to Cyanogenmod.
I spent hours and hours reading discussions and going down one dead end after another. I'd say it was like looking for a needle in a haystack but it was the complete opposite. It was like looking for a specific needle in a sea of needles. Every search query yielding tantilizing results and a plethora of step by step guides that ultimately didn't work. A very frustrating experience all around. Good luck to anyone who reads this.

Hi Matt
Similar thing happened to me last night. I am/was using Omni-Nightly build. I plugged it in to the charger before bed, and it rebooted, saying upon reboot - "Encryption Failed" and saying the only way to recover would be to wipe the machine and start again, it then rebooted and all I get is the Samsung boot screen.
Tried rebooting, wiping, everything, Odin, Android Toolkit, nothing works. It shows up on my Linux PCs but not accessible, but not windows at all.

[Q] Bricked Galaxy Nexus

So it all started out rather stupidly. I was attempting to flash a new ROM to my phone and I was deleting everything and accidentally deleted the OS by accident (mis-touched in recovery mode). I panicked and I attempted to push a file through adb but it was halting between 4MB - 8MB on a 200MB file. I knew this wasn't right. I ran cmd in administrator mode and tried again and got the same results.
I then moved to ODIN to attempt to flash the ROM. I ran ODIN in administrative mode. Bootloader was unlocked. I attempted to flash the new ROM but it stopped at about 1/8th of the progress (as shown in the download mode). This led to my phone having communication issues with my PC (displayed the phone with a hazard sign on the cord to the PC). I assumed it was bricked after googling around.
I then tried to use OMAPFlash as suggested by other people with the same issue. I did this, followed instructions perfectly, installed certificates. It got to the point where it was attempting to download a file. After 2 hours of waiting, I stopped it stupidly because it was making no progress.
Now my phone is completely black. I have no OS and I am not even sure if I have any files on it. Screen is black, phone not responding to button pushes and it isn't being recognised by my PC. I have tried unplugging it, removing battery and then plugging it in and inserting the battery again and that has failed.
I don't know what else to do. OMAP isn't picking up the phone anymore even though I have followed the instructions perfectly again. The one sign that my phone is still alive is the beeping noise from windows as I insert it meaning something must be happening. This however is soon followed by "Your device is unrecognised".
Can anyone help me on the situation as the phone is in perfect condition (physically) and I can't really afford a new decent phone at the moment.
Here is all the information you may need:
[Before incident]:
ROM: CM11
Rooted: Yes
Bootloader Unlocked: Yes
Ask for anything else.
[Attempted to change to]
ROM: XenonHD
Ask for anything else.

first off, why odin?
its a nexus you can flash back to stock from fastboot. I would suggest you download the factory images for the phone from here:
https://dl.google.com/dl/android/aosp/takju-jwr66y-factory-5104ab1d.tgz
then extract the images into a folder - remove the battery from the phone, put it back in the phone, power up while holding down vol + and vol - to get into fastboot
hopefully you have android sdk installed and fastboot working. use the flash-all script to flash every partition of the phone back to 4.3 stock.
good luck.

Well first thing, did you select the right zip file for your Gnex when flashing XenonHD. Bcz in my case few days ago i stupidly selected the wrong zip file (ROM for Nexus 5) to flash, but luckily i was saved by the CWM via "Status 7 Error".
But your case is more complicated i would suggest you to use Gnex toolkit with Google Factory Images, i hope that it will come for your rescue . Also try this method http://www.androidrootz.com/2012/08/how-to-restore-galaxy-nexus-i9250-to.html maybe it will do some miracle for you. Best of luck.

Progress
So after sleeping on it and spending some time deeply reflecting on the derp that I had made, I successfully managed to use omap to restore my device to the Phone-Exclamation mark sign as posted by another XDA user who ended up sending his phone back. If you search galaxy nexus brick in google images, you will see what I am talking about (can't post image).
I guess the best way to explain it is: [] -- /_\ -- [ ]
Basically it is a phone connected to a yellow exclamation mark sign and then that is connected to a computer.
Is there a way to force my phone into download mode from here. I can't seem to do anything. Some good news is that ODIN is now picking up my device. It is however crashing whenever I attempt to flash the stock ROM (either "odin3 communicator has stopped working" or "odin3 downloader has stopped working").
Any help fixing this?

Phone wont boot after trying to get back to stock

Hi there,
obviously I did something wrong, cause now my phone wont boot up. It is stuck on the HTC logo, and stays there for hours after hours. I can get into download mode etc, tried factory reset, but to no avail.
My phone is S-Off, but it is not recognized by adb anymore, so I cant get it to install TWRP.
My OS is 1.40.161.8 and my CID is VODAPE17
Any help would be appreciated.
Thanks,
Chris

Of course you can't get adb to work since it only works if you're booted to system. Did you try using fastboot?
(The answer of that question actually doesn't matter that much.)
To get your phone back to a working state you simply need to flash a RUU. Be aware that these methods will erase all data on your phone and it will downgrade its firmware version!
Do you have an external SD card for your phone that is not bigger than 32 gb? Format it to fat32, download this RUU and put it into the main directory of the SD card. Rename the file to "0PJAIMG.zip". (That's a zero, not an O.) Then put the SD card into your phone and boot to download mode. Follow the instructions on screen. Your phone will prompt you to power it down at the end by pushing the power button. Wait some seconds and you can restart it as you would normaly do. You can then upgrade your firmware to the latest version by using the OTA function in settings>about.
If your pc is able to detect your phone by using fastboot commands you can also use this RUU. Boot your phone to download mode, disconnect you pc from the internet (just for safety reasons because of the next step) and disable your firewall and your antivirus software (both can interfere negatively with this ruu). Then run the RUU.exe as administrator. Depending on the age of your pc it may take up to ten minutes until a new window pops up. It's recommended closing every window and programm you don't need. You don't have to do anything with your phone during this process although the ruu might say that your phone should be booted to system. At the end you need to upgrade your firmware, too, by using the OTA function.

Thanks for your help. It worked as a charm. So relieved to have it back up and running.