Stuck in bootloops, not sure what to do - Hero CDMA Q&A, Help & Troubleshooting

I recently tried to flash Fresh Toast 2.1 and after 15+minutes my phone was stuck in a bootloop. I rebooted to recovery and deleted all the data and cache. Now no matter what ROM i try to flash it just keeps booting over and over. Anyone have any ideas? I was using apps2sd and completely formatted the sdcard, would this have affected anything? Also tried nandroid back up, but says "No files found" when I try to do so. Also when i try to format the sd:ext i get an error mounting sd:ext

In recovery try and format your sdcard with only a fat32 partition. Then try and enable ?MS-USB? and copy a ROM to your sdcard.Wipe data and dalvik and then flash ROM.
If that doesn't work try replacing your sdcard with another one.
Or you can push your ROM.zip to the sdcad through adb without mounting the sdcard
A2SD will only work if your sdcard is partition with EXT and swap. So if you don't have it partitioned then apps will install on your phone.

I gave it a shot but no luck, i am using the clockworkmod recovery 1.8.1.4.

I had the same issue happen the other day after a wipe and reinstalled rom... I have the same clock work mod you have also... what I noticed was that my phone only did that when I had the sd card in but once I removed it (after several hours of flipping out over it!) it booted fully.. but every time in reinserted the card, it rebooted.. so what I did was used paragon partition manager to create 3 partitions on the sdcard (i have an 8gb card) and made 2 Linux ext2 partition of 258mb or something close to it and the remaining was formatted at Fat32.. after I did this, I re-flashed my rom and everything has been working fine ever since... it may have been some corrupted files in the 2 Linux partition or something because I was running all my apps from the sd card and I had noticed the other day that every time I connected my hero to my laptop via usb, and launched pdanet, my phone rebooted...EVERYTIME.. and this is what led me down this road... If I made any mistakes here, I'm sure someone will correct me, as this is my first post...

27midwest1 said:
I had the same issue happen the other day after a wipe and reinstalled rom... I have the same clock work mod you have also... what I noticed was that my phone only did that when I had the sd card in but once I removed it (after several hours of flipping out over it!) it booted fully.. but every time in reinserted the card, it rebooted.. so what I did was used paragon partition manager to create 3 partitions on the sdcard (i have an 8gb card) and made 2 Linux ext2 partition of 258mb or something close to it and the remaining was formatted at Fat32.. after I did this, I re-flashed my rom and everything has been working fine ever since... it may have been some corrupted files in the 2 Linux partition or something because I was running all my apps from the sd card and I had noticed the other day that every time I connected my hero to my laptop via usb, and launched pdanet, my phone rebooted...EVERYTIME.. and this is what led me down this road... If I made any mistakes here, I'm sure someone will correct me, as this is my first post...
Click to expand...
Click to collapse
Would you mind posting the steps to do that? Im pretty computer savvy but I need some steps to go from. Would I be better off picking up a new SD?

pulled the SD and it booted, thank god lol. Thanks for your help guys!

no problem... glad I could help.. as for the new sd card, you could very well just get another, but I managed to keep the one that I had but just reformatting it and re-flashing my rom (Damage Control v2.08.1) and it's been working fine since then..

Related

My phone says sd card removed

It happened yesterday when I upgraded to xrom. I have formatted and repartitioned my sd card. Nothing is working. When I connect my sd card to my computer I noticed a lot of weird files were being stored on it. They reappear every time I delete them.
My phone is creating files like this "qxdm_20090910_184004_3.dm" (32 megs!)
hmm....very interesting... reboot into recovery and repair the ext files? it might work. most likely not, but its worth a shot.
I though about trying that but I don't have cyanogens recovery .
Mine just did the "sd card has been removed" thing half an hour ago.
I just copied a new theme .zip to my sdcard and then rebooted into recovery.
I could not apply the update since it could not mount the mmcblk0p1 partition. When boot all the way up to android i get the icon saying that the sdcard has been removed.
i just did an adb push of a file to my /sdcard from the recovery console and it returned no errors...but i cannot see any files on the card.
wtf.
Any ideas?
Yeah my problems still not fixed. I have searched the XDA, forums, Google, none have offered any solution. I have found a lot of people with this same problem.
are you using swapper? if you dont turn it off, this could happen.
i would recommend getting cyans recovery image, it has a lot of tools to debug.
get a live cd of linux/gparted and see if you can see all your partitions. if not, your sd card is most likely dead. try reformatting. if that doesnt help, you may need to get a new card.
if it does show up on your pc, but doesnt work on your phone, then post here again
Have the same problem. Got it right after updating cyanogenmod 4.1.2 I've also been looking for answers and I think I'm just gonna get a new one
I have never used swap. I tried installing cyans recovery image through terminal but it can't find my sd card. I can still update my rom through jfs utility. My sd card works perfectly fine on my computer.
Something like this happened to me a while ago. It first said Sdcard was damaged and i couldnt access it via any file manager. I rebooted and turned out all my apps went up in the air and dissapeared and my fat32 partition was gone to. i reccomend backing up your sdcard and reformatting your card then go froom there
I have already tried all that. Nothing so far has worked :-(. Man this is horrible. I can't even take pictures!

Is there any HOPE for my G1?

I tried to install Blur Hero 1.5.7, it did the boot loop thing, so I pulled the battery and tried again. After that did not work, I attempted to wipe and revert back to what I had using nandroid. No luck. So I got into the console and tried to start fresh by re-partitioning the sd in the hopes that I could reinstall and try again.
NOTE: Reason for the repartition step was because I was not able to access my sd through the phone. I tried (which has worked for me in the past) to hook it up through a camera of mine. Upon doing so it said that I needed to format, so I did.
Now I am in a world of hurt. My laptop will not recognize my device, it is still on the HERO boot loop, and when I try and connect using the cam, it says that it is in a RAW state instead of a FAT32.
IF any of this sounds familiar to anyone, please help.
Thanks for your time,
LJ
this has happened to me.
my problem was that after the boot loop, the ext3 (at the time) partition became mount, while the fat32 became mount-1. it normally, and should be the other way around.
you probably have to delete your ext, and then reformat your fat32 using gparted (ubuntu). then you can make another ext partition, and they will mount in the correct order.
also, when/if you get the mounts working, install one if cyanogens (god bless him) roms to make sure everything works. then you can try for hero again
a second time something similar happened to me, and it *bricked* my ability to create an ext partition on that sd card, tried multiple ways.
good luck
Have you tried to go into recovery and parted and format your card that way?

Can an SD Card be bad but not bad?

I just got an A-Data Class 6 4 gig card. I can format 3 partitions, upgrade to ext3, copy update zips and files to it, but it boot loops when i try to load up a new rom (any rom). My old class 2 4 gig card loads everything fine. It even runs the latest king hero really well.
Any ideas?
robkoehler said:
I just got an A-Data Class 6 4 gig card. I can format 3 partitions, upgrade to ext3, copy update zips and files to it, but it boot loops when i try to load up a new rom (any rom). My old class 2 4 gig card loads everything fine. It even runs the latest king hero really well.
Any ideas?
Click to expand...
Click to collapse
How did you partition your card?
using parted in console. I've re-done it several times as well.
So no matter what rom you flash your getting a bootloop. Do you have a nandroid?
I do. Using Amon_Ra's 1.2.3
On 2nd thought, do you mean a nandroid of a bootloop instance?
robkoehler said:
On 2nd thought, do you mean a nandroid of a bootloop instance?
Click to expand...
Click to collapse
Naw a nandroid of a rom that was working before you started flashing.
unfortunately no. i got partition crazy and removed the fat32 it was on right before i thought "did i back that up?"
With my old class 2, i've been able to get up and running on 4.1.999 and this king hero rom with no troubles.
Can a taco be bad but not bad? like, it tastes good, but it was made with bad ingredeints or a horrible chef.....
It sounds to me like your wiping after flashing.
You wipe data, Wipe ext, fix ext, flash rom.
If you wipe after flashing, or flash without wiping you will always get a boot loop.
The image doesnt run from your sd card, so the only thing that would cause the loop is the data on your phone.
Find a tested and working rom (i suggest either Mligns newest or Kings newest)
Go into recovery and turn on USB.
Move rom to sd card.
Wipe data
Wip EXT and fix
REBOOT INTO RECOVERY
then go to flash any ZIP (if you dont reboot, the rom file will not be seen correctly)
flash the rom
Fix ext again just in case
Reboot and leave the phone alone for a few mnutes.
EVERY phone is different. Some take 2 min some take 10-20 min
But if you have flashed properly, the best way to know is the shimmer on the HTC will continue to flow and not stop.
Sometimes it will fade, sometimes the noti bar will appear for 5 min then boot...
Just have patience and try.
EDIT- You typed while I was typing, It sounds like then maybe that card is bad then. If all works with older card, then the flash may be bad on the newer card. may want to return it unless you have other uses for it.
Just to add a strange twist to this. Just reformatted card so it was all Fat32, wiped, and flashed 4.0.4. Everything went fine. What on an SD card could crash Apps2SD?
robkoehler said:
Just to add a strange twist to this. Just reformatted card so it was all Fat32, wiped, and flashed 4.0.4. Everything went fine. What on an SD card could crash Apps2SD?
Click to expand...
Click to collapse
Possibly the upgrade from ext2 to ext3. Thats why I like to do mine in Ubuntu. Format the card using linux for a linux phone.
Decided to go a step further and go back to parted and resize fat32 and add a 500mb ext2. Rebooted and it fired up and shows the ext2 in the settings screen.
All that and it's not even Halloween yet. I'm going to try to flash 4.1.11.1 just to see if i can break it again
I'm sending it back. wiped flashed 4.1.11.1. Got to setup screen but everything force closes. com.android.phone, com.google.process.gapps, com.android.setupwizard.
Skipped wizard.
signed in with google account.
no service connection ever made so no account sync.
time to email newegg and try this again
robkoehler said:
I'm sending it back. wiped flashed 4.1.11.1. Got to setup screen but everything force closes. com.android.phone, com.google.process.gapps, com.android.setupwizard.
Skipped wizard.
signed in with google account.
no service connection ever made so no account sync.
time to email newegg and try this again
Click to expand...
Click to collapse
lol.....you give up quite easily.. those problems arent related to the sd card (they are on your /system partition)
try to reflash your rom and repair ext partitions then fix_permissions in recovery
hmmmm.....got card #2 and it appears to be the same case....boot loops. i can't believe that 2 sd cards would be bad only when it comes to apps2sd.
got adb running on my work pc and uploaded a log of the fail
again, everything boots just fine (just booted king's new 1.0) with my lexar class 2
updated logcat - 1st one was when i couldn't get off of the g1 screen.
this logcat is of the bootloop. any help would be great

Problems after apps to SD EXT2 format

Hi
I have some problems with my Dream now after an format fore EXT2 so I can use apps to sd.
I have CyanogenMod 4.0.4
Iv'e used an guide and console for formating my SD card 8gb class 6.
I've made an 7.2gb fat32
700mb ext2
50mb linux swap
After that I converted the ext2 to ext4, checked everything with print and it was ok.
Than when I've rebootet my phone it woudnt start up, it came to the android in blue, and that blinked some and than the screen went black.
So my plan was to upgrade the 4.0.4 to 4.2.5 anyway so I did that.
My phone was an 32B so I used the HTC_ADP_1.6_DRC83_rooted_base.zip
Everything went great with that, but when I tried restarting the problem was still there...
Dont know what to do know?
Remove the ext4 partition?
Try restoring your memory card to original and then try to partition it again.
Ive tried to restore my memory card, no help.
Ive tried to boot the phone with no memorycard, still no go...
Dont know what to try anymore..
1) Format the entire card as fat32
2) add other partitions
3) Wipe from recovery
4) Flash your rom
Also this sub forum is for development, which this clearly isn't.
Ok sry i thought this was the place to ask with this.
I got the phone booting up with 4.2.5 and it worked great.
All my programs waws gone so I need to install them again, but no worry.
So I now tried to format the memorycard again, looks like it didnt work again and im at my problem again...
Now it hangs on the T-mobile screen, so I guess out with the battery and try an reboot before I start all over again...
Maby I'm not supposed to have programs on my SD?
make sure you partition properly.
fat>ext>swap
you can install amon_RA's recovery and let that partition your card for you
Hi.
Ive sendt my phone back to originale software, and than upgraded again, and it seems like it's 4.2.5 and the ext partition that is the problem.
If I change SD card to one without the ext partition it's no problem to start after an whipe..
I've tried reinstalling 4.2.5 but no luck, maby I shall trie an ext3 insted of ext4?
Yes have followed the guide on the pratition, and Fat32, EXT than swap

Can't mount internal SD Card after installing Albinoman887's 1/12/14 KitKat Rom

So I have installed several versions of this ROM since it began, however when I upgraded to 1-12-14, all went well except my internal SDcard will not be recognized. This means I can't use the camera or Titanium Backup, etc. However, I can see and use the external sd card w/o any issue. Upon every boot I get the icon saying that I need to format SDcard0, but it never completes, only soft reboots and the icon is gone until the next full reboot. I flashbooted boot.img twice after doing a FULL wipe. I have tried reinstalling 3 times doing FULL wipes every time, still get the same. When I boot into recovery and try to wipe SDcard, I get an error saying
can't mount /dev/block/mmcb1k0p36 (Invalid argument)
Error mounting /internal_sdcard/!
Skipping format
I have also just tried the new 1-15-14 build and get the same results. I have fastbooted the boot.img each time. Please help. I have installed many ROMs on this device before w/o ever an issue. What did I do wrong and how do I fix it? TIA!
Reboot recovery
Mount USB storage...
Plug phone into computer...
Let windows format corrupt partition...
Profit
Sent from my Vivid 4G using Tapatalk
Just putting another method which worked for me (one time issue and fix, so it's a crap-shoot). I don't have the luxury of connecting to a computer via usb for anything except charging.
-properly flash a sufficiently different ROM (I had kitkat, so I flashed ICS)
-start ROM up, check if fixed (mine was not)
IF NOT FIXED, CONTINUE
-mount the SD card in your recovery (mine is WCX recovery)
-reboot your phone into the ROM
This method worked for me. I saw in a different forum that when this happens it's usually because a file that describes the partitions gets corrupted and that because ICS and GB partition the SD cards and internal storage in a different way than Jellybean or Kitkat, that flashing a different ROM (if problem is on ICS/GB, then flash KK/JB, and vice versa) will force an overwrite of the file in question.
This is not as easy as rignfool's method, and once my charge port arrives in the post, I will abandon this method and use Windows to repair the partition like a sane person
Also, it seems like all my media on the internal storage has been wiped, but wutevr :/
Might want to try a newer build where that bug is fixed.
http://www.chronic-buildbox.com/nightly/holiday/
Yuskow said:
Might want to try a newer build where that bug is fixed.
http://www.chronic-buildbox.com/nightly/holiday/
Click to expand...
Click to collapse
If this is directed at me, this happened after I installed the March 17th or 18th nightly (put a new one on every once and a while). And to be completely fair, I had accidentally selected factory reset in hboot (thought it was highlighting recovery, boy was I pissed).
The problem (or so I've read) with installing another kitkat/jellybean ROM is that the SD card is mounted the same (/storage/sdcard0, and external SD is only /storage/sdcard1) as opposed to ICS/GB (I only remember that you access external SD through /sdcard/ext_sdcard or something to that extent). Only when the SD cards will be mounted at differing locations will the system re-write the files specifying mount points.

Categories

Resources