Develop Bugs

Ridiculous Boot Loop - Two bricked DINCs

Both experiencing the same problem,
One UD 8.0 got stuck in loop after I tried installing Koush Kernel
2nD one is running CM6.0.1, was fine until I tried using to read Phone #1s MicroSD to figure out what was wrong.
2nd phone (CM6) then restarted randomly while plugged into PC, which started the bootloop.
Tried everything, nandroid (Couldn't mount /Data), I wiped, factory reset, tried reflashing update.zip for CM6 phone.
Both phones are completely useless, not sure what to do at this point and CM6's owner was leaving town.
Any ideas? Ultimate way to unbrick a DINC? If you know of anything, please help.

A boot loop is not a brick. I would nandroid back to stock(you did this right?) or use an RUU.

grnmons said:
Both experiencing the same problem,
One UD 8.0 got stuck in loop after I tried installing Koush Kernel
2nD one is running CM6.0.1, was fine until I tried using to read Phone #1s MicroSD to figure out what was wrong.
2nd phone (CM6) then restarted randomly while plugged into PC, which started the bootloop.
Tried everything, nandroid (Couldn't mount /Data), I wiped, factory reset, tried reflashing update.zip for CM6 phone.
Click to expand...
Click to collapse
Does this mean you can get into hboot?
If yes, you should be able to ruu an official release..
Sent from my ADR6300 using XDA App

I do not have a great deal of experience, but since you can get in recovery, place King Kernel #3 on your SD card, boot into recovery and apply the KingKernals #3 zip file from your SD card for the 1st phone. See if that fixes it. Just sounds like incompatibility with the kernel if it happened right after you flashed it.

ziggymanILT said:
I do not have a great deal of experience, but since you can get in recovery, place King Kernel #3 on your SD card, boot into recovery and apply the KingKernals #3 zip file from your SD card for the 1st phone. See if that fixes it. Just sounds like incompatibility with the kernel if it happened right after you flashed it.
Click to expand...
Click to collapse
UD is an AOSP Rom, King's kernel does not support it at this time.
I would try a fresh install of the 8-26 leak. Do wipe first, then do dalvik wipe under advanced settings. Get deodexed version of rom Here
If that does not work let's get some information
Did you run unrevoked forever and get S-off status?
What radio version are you using?
You should not be borked if you are getting into recovery you should be fine.

@ToyTank
BOTH phones are - 2.05.00.6.11 S-ON, Neither are unrevoked forever.
Problem with phone 1 (UD) is that the SD card is completely messed up now. It's an 8GB that has nothing on it, the compuiter is reading it at 758MB. Any function of Recovery leads to errors mounting, so flashing stuff isn't working, nandroid as well.
Phone 2 (CM6) let's me flash stuff onto it, "Install from sdcard complete." but will continue into a bootloop when I restart the phone.
I attempted RUU last night and maybe I'm doing it wrong but the software is giving me an error connecting to USB. How should I go about installing the 8-26 leak? Just wipe > throw in PB31IMG and install?

I assume I don't need unrevoked forever for this, I tried 8-26 and flashed PB31IMG.zip, Device 2 Starts dancing until it says "Main Version is older! Update Fail". Anybody know a workaround?

Try formating the sd card to FAT32 using a computer. That might help with phone #1. Error with usb can be solved using these steps.
1. Try the RUU executable. it will give you that usb error, taking you to the black htc screen.
2. Exit the ruu program (leaving phone in that state) and run it again. This worked for me when I RUU'd mine.
Who knows though. It may have been a one shot deal.

sounds like you are trying a bunch of stuff without READING about what you are doing. you flashed kernels with a rom that CLEARLY states that they will not work and then you tried to flash unsigned roms through hboot which will not work without s-off and then you try to downgrade when you have the ota leak (radio 2.05) which will not work.
you either need to get the ruu working, get s-off applied or follow the steps to go back to stock hboot.
time for you to start doing your homework to get yourself out of this mess.

Neither are bricked. Ruu back to stock.

yeah bro not good practice

@Fretless, @Lafester, @GermanBrat. Thanks for the comments - going to try RUU 3.21.605 and report back.

Hey guys RUU worked for Phone 2 (CM6) but is not playing nice with Phone 1. USB connection error. I appreciate the help so far, any more ideas for this phone?
It's basically stuck in white htc inc screen and will go no further. It's completely wiped and nothing will mount in recovery. RUU can't detect a usb connection but the PC beeps when I connect via usb

In need of depsperate help!!!

Try to flash to JH2 (and repartition 512) - the stock B model firmware.
If it fails - try to push one of complete roms (doc_kalpik) and install it using clockwork.
Otherwise have no idea what is wrong.

.....
I will download the firmware files now,
any instructions on how to use clockwork? and install the complete rom?

Did you perform a repartition when you reflashed ?

ignore me wrong thread!

inshadesofgrey said:
I will download the firmware files now,
any instructions on how to use clockwork? and install the complete rom?
Click to expand...
Click to collapse
isnt there a install guide in doc-kaplik topic? In clockwork (might need to push update.zip and rom manually - dont remember how) choose install zip from sdcard and navigate to file you need.

i did......still didnt work

Sounds like what mine was doing when the internal SD died.

dupel said:
isnt there a install guide in doc-kaplik topic? In clockwork (might need to push update.zip and rom manually - dont remember how) choose install zip from sdcard and navigate to file you need.
Click to expand...
Click to collapse
will this work even if i didnt have clockwork on my phone?

I flashed the stock JH2 with 512.pit and reparition checked, but the phone goes to the samsung logo, and flash animation and to a blank screen with only the buttons lit up........ah, am losing all hopes really fast.

Now that you are on jh2 take out sim leave external sd inside charge it til full, turn on while and it will boot, saying no memory going internal or external.
So far that would be doa, unless someone found a way to fix or reformat external card but most people that sent it for repair with these symptoms had done doa exchange like me twice or samsung replaced external module meaning it was hardware issue. Sorry.
Sent from my i9000M

it's a long shot, but can I buy an external SD card and run android from there?

I am guessing the only hope is to buy a new phone then?

inshadesofgrey said:
Hi guys, I have been a silent observer of XDA for a while now and you guys have helped through the past 4-5 phones that I've had - but now, I am stuck, so I thought I'll ask for help.
I have a galaxy S (i90000-GT) - originally from Bell, Canada but unlocked. I was running the XJPH with lag-fix and two days ago, when the phone rebooted, it got stuck in a boot loop, samsung logo with black screen comes on, and it starts all over again. Now, I can get into download mode and I followed the process to install JM8, and the stock file (the US Vibrant stock file) and I tried this as well:howto-froyo-fw-i9000xxjpm-upgrade-via-odin-root-recovery-2e-lagfix/[
But to no avail. The boot loop is still there. With JM8, the phone boots up and the goes beyond the flash samsung logo (with the music) but loads to a black screen, with the lights on.
Am really frustrated as this is my only work phone (and I go back to work tomorrow). Without the phone, I am pretty much screwed. I dont care about the Data on the phone (have performed 3-4 data wipes during installing the above mentioned roms) . So anything you can advise, will help!
any ideas?
Click to expand...
Click to collapse
Have you wiped your data/factory reset & wiped your cache? Many phones get stuck at startup because of them.

[Q] Cannot boot after OTA 2.29.405.2

Hello,
After applying the latest OTA 2.29.405.2 I am unable to boot my phone.
The new firmware was successfully applied, because I could start the phone for the first time.
After I shut it down again it won't got past the HTC logo.
I can get start the hboot but I if i select fastboot or recovery I get stuck again with the HTC logo.
When i select the bootloader "I get no image or wrong image."
I did not root my phone.
Please help.

For a start, unless you have a PB99IMG.zip file on your sd card you will always get that message in the bootloader. It's just telling you it can't find any of the files it looks for on your card so nothing wrong there.
First thing I'd do is try manually reflashing the OTA update. you can get the OTA ZIP file here:
http://fotadl.htc.com/OTA_Bravo_Froyo_HTC_WWE_2.29.405.2-2.10.405.2_R_P_release8gn61bgo3rswcw24.zip
Rename it update.zip and put it on the root of your SD card. Then boot into recovery (if you manage to) and flash it.
If not, go into Fastboot and clear storage (wipe). This should sort you out. If not, download the 2.29.405.2 RUU from my signature and flash that in fastboot and it should see you right if you're still having issues

Did not work unfortunately. I will try to flash it. Any easy to follow tutorial I can use ? I never did this before.
Thank you kindly.

psycho.ro said:
Did not work unfortunately. I will try to flash it. Any easy to follow tutorial I can use ? I never did this before.
Thank you kindly.
Click to expand...
Click to collapse
What didn't work? What I put on my previous post is exactly what you need to do

I downloaded the file and renamed it ot update.zip and copied it to the root of my sdcard. when i select recovery it gets stuck in htc logo.
Then I've cleared storage/user settings and tried again, same thing.

So now do the last thing I suggested

this happened to me also. i downloaded the RUU and just did it via the pc. lost everything i did not backup, but that's my fault. all contacts were on google and and i used appbrain to pull down all my installed apps.

ok, i finally did it and it's fine now. I figured out what i was doing wrong. flashed it and it started now.
thanks for the support, really appreaciate it !

For reference, what were you doing wrong?

i did not go in the fastboot menu when i tried the last thing you suggested and because of this, my phone was not recognized by windows and the flash utility could not do its job.
but now it seems that my phone is restarting from time to time, somewhere between 5-10 minutes.

Might wanna do a hard reset just to make sure things flashed correctly

[Q] HELP frozen bootscreen / bootloader

Hey,
I was wondering if anyone could help me out with this issue I have. I have a rooted Evo, with my latest ROM being Fresh Evo 4.0.0.4 Beta by flipzmode. I was having some issues with the rom, so I was attempting to reflash the rom, however its beta 3 (one update older) version, first. I went through ROM Manager and did a complete backup, then chose install from SD Card and checked the boxes for Wipe Dalvik cache and the other check for wipe cache / data (i forget exactly what it says). ROM manager took over from there, rebooting into recovery and installing the rom, atleast as i thought it as doing. Once it was said and done, I now am at my problem area. It will not boot past the white htc EVO 4G screen. I've given it anywhere from 20-40 minutes to load. I've tried pulling the battery as well. I've even attempted to get into recovery by going into my hboot bootloader. However there, i have ANOTHER problem...I can't pick any of the available options. Its as if my volume buttons just don't work. When I have my SD card loaded and I go into hboot, it does some kinda search which yields five results of No Image Found! it then returns to the main menu where again, I can't scroll up or down the list. It says s-off so I assume that means I'm still rooted. I'm not an expert by any means, and overall I'd say I'm a noob to this stuff, but I am trying to figure it all out. If anyone can help me out with what to do to get my phone running again, I'd appreciate it greatly.
Thanks!

Hmmmm, that's odd. You can try putting a PC36IMG of the RUU on the root of your SD card. If you used unrevoked, you'll stay s-off, so all you'll need to do is reflash recovery to flash a rom or restore from a backup. However, you need to use your volume buttons to agree to the flash in the bootloader. In the odd case that it just won't navigate the menu, but the volume buttons are fine, it may still receive the confirmation from the button that you want to flash the PC36IMG.
If that's the case , download this file: http://goo-inside.me/supersonic/sto...15.00.11.19_NV_1.90_release_161482_signed.zip and rename it to PC36IMG, don't add a zip to the end because it's already there. Put it on the root of your SD card and boot into the bootloader, when it asks you to update, *try* to agree with the volume up button. If it works, hopefully that'll fix your problem.
It's not the greatest fix, and the chance of it working isn't all that high, but it's all I've got.
Oh, and obviously your volume buttons are fine if you can get into the bootloader, unless a button is stuck.
(from... Evo/MIUI/Tapatalk)

And don't use ROM Manager.....

Thanks plainjane,
Just a couple more quick details before I try to do what you said, I'm not sure which root method was used for me. My cousin did it for me and with my phone mia, I have no way to find out. Does that effect anything? Also, i'm pretty sure i've used ClockWorkMod recovery, as i remember flashing it through ROM manager a few days ago. I've realized that the volume buttons do work, but only when to accept the update for the pc36img..I read about that before so I tried putting one that I believe was for ClockWorkMod recovery on my sd card, but I wasnt sure if that was the right pc36img file i need. So I can replace that with the one you have linked me with. Will running that cause any problems with the addtional details? I just don't want to end up permanently bricking my phone, so I'd rather cover all my bases.
Thanks again!

I would do 2 things: 1 flash a new recovery, specifically amon_RA and then I would flash a rooted ODEXED stock rom.
Click on the word "amon_RA" above and download the PC36IMG.zip file and place it on the root of your SD card (not in any folder). Make sure there is NO OTHER FILE with that same name on the root of your card. Turn off your device and then boot it to the bootloader screen. After a pause, the file should be autodetected and you should be prompted to install. follow the easy instructions to install. Afterwards, you should be able to go into recovery and flash a rom. Download the rooted stock rom by clicking on "rooted ODEXED stock rom" above. Afterwards, put it on your SD card and flash it from recovery. Once you've successfully flashed a rom and if you're set on re-using ClockWorkMod recovery, you can always download the ROM Manager app and have it install ClockWorkMod recovery for you, but I recommend you stay with amon_RA.

!
plainjane said:
If that's the case , download this file and rename it to PC36IMG, don't add a zip to the end because it's already there. Put it on the root of your SD card and boot into the bootloader, when it asks you to update, *try* to agree with the volume up button. If it works, hopefully that'll fix your problem.
Click to expand...
Click to collapse
Thank you, thank you, thank you plainjane! I decided to just go for it and try your method, it took care of my phone not being able to boot-up. I'm now at what seems like a stock rom.
dougjamal said:
I would do 2 things: 1 flash a new recovery, specifically amon_RA and then I would flash a rooted ODEXED stock rom.
Click to expand...
Click to collapse
Thanks for your suggestion dougjamal, I actually attempted your method first, but I still wasn't able to select the recovery option from the hboot bootloader main screen after running the PC36IMG, so I couldnt flash the rom.
So, I still have a couple of the same problems. I still can't choose the recovery option from the bootloader menu, I've tried multiple times to use a PC36IMG for ClockWorkMod recovery and Amon_ra. Also, while using the actual phone, my power button seems to not work. It doesnt turn of the screen, nor does longpressing it allow me to shut off the phone. If it helps to diagnose the problem, since i'm pretty sure up until today my power button still worked, whenever I pull my battery and put it back in, the phone boots automatically without me pressing the power button. Anyone have any suggestions?
Otherwise, is there anyway for me to just go back to complete stock again and attempt rooting the phone again, and starting completely from scratch?
Thanks again for everyone's help!

Boot into the bootloader screen and see if you're still rooted (S-OFF). If it displays S-ON then you will not be able to make changes to your device.
posting & replying via the XDA Premium app.

dougjamal said:
Boot into the bootloader screen and see if you're still rooted (S-OFF). If it displays S-ON then you will not be able to make changes to your device.
Click to expand...
Click to collapse
Yes, it still says S-OFF. I don't understand why I can't scroll through the menu nor turn off my screen though. Even when it times out, I can't turn the display back on. I have to plug in a charger.

CM10.1 crashed and softbricked itself, can't access the file system

I have Cyanogenmod 10.1 (stable) installed; the other day it crashed while I was on Instagram, rebooted itself, and wouldn't go past the spinning circle screen. Tried rebooting it, now it won't go past the screen before that, with the blue Cyanogenmod man and the Samsung logo.
I have TWRP 2.5.0.0 installed with it, which I don't know how is possible being that the file systems are incompatible, so unless I used Odin to install CM10.1, I don't know how I did it without installing Clockworkmod Recovery over TWRP.
I've been trying to fix it for a couple days now (I'm kicking myself for not getting around to posting here sooner). When I go into TWRP it asks me for a password (which I've never set, I assume it's asking me because that's all it knows to do when the file system is incompatible), which I click cancel at every time, and when I try to do just about anything (including installing new ROMs or recoveries from within TWRP) it gets errors when trying to mount any partitions on the device, so I can't change anything on the phone at all.
I've tried re-installing TWRP AND Clockworkmod Recovery with Odin, and they succeed, but when the phone tries to reboot, the screen just turns off and nothing happens, and I have to take the battery out to do anything else.
So right now I'm totally screwed unless I can fix this thing. I'd like to not have to drop 200 on a Nexus 4 after only a year or having this phone I bought brand new, especially with the Nexus 5 already coming out later this year...can somebody help me???
EDIT: I should clarify that I can access recovery and download mode

If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.

FoxTrotz said:
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
Click to expand...
Click to collapse
I should've clarified that I've tried this with a bunch of roms, and it just shows SBA2 in the status box forever. I left it for a full hour before and it never changed.

According to this page http://www.alliance-rom.com/community/wiki/bricked-android/ reformating your external sd card may help. It also links to something I personally have never heard of but apparently this: http://forum.xda-developers.com/showthread.php?p=15330252 can help unbrick any samsung phone that's flashable with odin.