So I got an HTC Hero. I rooted, flashed custom ROMS, had much fun, but trouble started when I wanted to try out BEASTsense. Prepaired SDCard with EXT, flashed, all went fine. Like the fool I am, I removed the sdcard while ROM was working, so all apps disappeared. In order to fix that I rebooted. And then it started:
- Phone bootloops (not even reaching bootscreen) when the sdcard is in (yes, I tried another sdcard, yes, they had no EXT partition).
- Phone boots just right when sdcard is not in, and when I install it it doesn't detect it.
- RUU'd to stock, same problem
- HEROIMG'd to stock, same problem.
I would say it's hardware, but the bootloader/HBOOT reads and installs the HEROIMG from SD just fine. Help. Please.
(sorry for my relatively poor English)
EDIT: Before using RUU or HEROIMG, I tried booting into recovery and wiping everything, but the recovery itself wouldn't recognise my SD, so I could not flash another ROM or use my precious NANDroid backups. Just so you know
help!
Got the same issue, hero keeps rebooting, cant reach any menu, think i got it bricket.
Anyone has any idee, tryed hard reset.
With or without sdcard, same story
Try to wipe sd-ext in recovery... (it will delete your apps)
thanks
pirlouit2 said:
Try to wipe sd-ext in recovery... (it will delete your apps)
Click to expand...
Click to collapse
Got mine working now, now i got a strange batterydrain when i start the market or the internet browser. couple of minutes and the battery is out of order...
Related
First time I'm posting so hey.
I just bought a HTC Hero today and decided to load a custom ROM onto it.
I flashed it fine, and installed modaco earlier (file name: 2.8-update-hero-modacocustomrom-core-signed).
So when I powered it back on, it looked like it worked fine, but I must of went wrong somewhere.
The phone will boot up, stay on for like 5 seconds, and then restart. When it comes on, I can't do anything cause it freezes on the lock screen then just restarts.
I'm pretty sure I messed up by putting that ROM on a t-mobile UK Hero(which I unlocked). I aint sure as I'm only new to this.
Any advice on how to fix this?
did you do a phone wipe before installing the custom rom?
I formatted the SD card.... I think before I flashed it.
Then just put the ROM on the root of the SD card.
See it looked like it done everything fine with the ROM.
I held in the home/power buttons, loaded the boot menu.
I did a "Ndroid back up" (did I spell that right) - so I could restore in case something like this happened (which I did, since I need my phone lol), then picked "SD Choose", picked the modaco ROM and it seemed to install fine. Took a few minutes. Install complete. I rebooted the phone.
Then it loaded the normal boot screen, and would literally last only 1 second and freeze on the lock screen saying no signal, then it would reboot. And loop this pattern.
Neo-Dragon said:
I formatted the SD card.... I think before I flashed it.
Click to expand...
Click to collapse
A wipe has nothing to do with the SD card. It is essentially resetting your phones internal memory back to "factory" defaults. I take it you have a custom recovery image, as you mentioned making a Nandroid backup - you will find an option to wipe there.
Regards,
Dave
So if I wipe the phone before hand and then upgrade it should be fine?
If I do a nandroid back up, will I still be able to roll my phone back if it fails?
A wipe now may fix your problems with you needing to upgrade again.
My suggestion would be trying this first - if it doesn't help, restore your nandroid backup, wipe, and apply the new ROM again.
Regards,
Dave
Cheers mate.
After the wipe, I re-installed the ROM and it works perfect.
Thanks again.
Hi everyone,
So, I think ive damaged my internal memory...But let me give u some info first.
UK SGS3 i9300 on vodafone. I rooted it a while ago and have had several roms. I know the basics of android hacking since I've hacked several as well as my previous 2 contract phones. I was on paranoidandroid 2.22 or w.e. version it was, however I wanted to go back to a sammy rom, and decided to clear my internal sdcard n ext sdcard (more or less - leave my music folder on there foe example) at the same time. I only mention this because my lead has been a little touchy recently and during the process it disconnected a fair few times till i got the cable sat right. I didnt have easy ums or anything - it was mtp. I completed this and loaded my rom onto the extsdcard.
I then went into the cwm touch recovery 6.xx or w.e. selected factory reset, wipe cache n dalvik, then installed it. It just got stuck at the boot logo for a while, then kept boot looping. I then tried wiping a few times, and a couple of different roms, and during this time I noticed that when I click wipe data it rebooted recovery. I then downloads the appropriate stock firmware to flash via odin. I flashed it and it was still stuck on the boot logo. I then realized I couldnt get into recovery, so I flash cf-root via odin, I got the 5.xxx recovery that comes with it. I tried to wipe all again, and it just didnt seem to work, I was stuck in a bootloop. I then posted this:
http://forum.xda-developers.com/showthread.php?t=1948255
So yeah with adb, I got it to boot, but i had the wrong size internal memory capacity. Then tonight I flashed twrp (a recovery if u dont know) (latest version) via goomanager and then selected in goo manager ti reboot recovery. Now my phone just goes from the sgs3 logo to the twrp logo and back, even if I boot normally, it does that, and same for trying to boot recovery. I can still get into download mode, but thats it.
I have since tried flashing the stock firmware again to no avail, I'm going to flashing cf root to get recovery... but we'll see what happens...
so what can i do?!?!
Have you tried flashing complete stock firmware through Odin? Then start from there?
You say internal memory is wrong? Might have to flash .pit aswell with re-partition?
Carl.Brand.87 said:
Have you tried flashing complete stock firmware through Odin? Then start from there?
You say internal memory is wrong? Might have to flash .pit aswell with re-partition?
Click to expand...
Click to collapse
yes I have, several times, if u read it all... Where can i get teh CORRECT pit file? I've tried one, but it didnt help.
I've just flashed cf root (after a pass on stock firmware) and its booted the ultima rom again... and still got 12.1gb internal... so my phone boots again, but the internal is still wrong! help!
You know that some of the 16gb is taken for the system files right? My phone only reports like 11.6gb in total to use.
Android reserves about 4gb that's why you only have 12gb free there is no problem there.
mattyyey said:
yes I have, several times, if u read it all... Where can i get teh CORRECT pit file? I've tried one, but it didnt help.
I've just flashed cf root (after a pass on stock firmware) and its booted the ultima rom again... and still got 12.1gb internal... so my phone boots again, but the internal is still wrong! help!
Click to expand...
Click to collapse
That's normal, the 12.1GB is COMPLETELY normal.
Other memory is reserved by the system.
This is usual and it should work that way, stop messing with it.
32GB models should have about 25GB~.
idiot here
Skander1998 said:
That's normal, the 12.1GB is COMPLETELY normal.
Other memory is reserved by the system.
This is usual and it should work that way, stop messing with it.
32GB models should have about 25GB~.
Click to expand...
Click to collapse
oooookk, TT used to show 16gb tho.... i remember i like the fact it read 16gb sd & 16gb extsd. nvm, im just wrong. thanks. I'll use it as it for now, still not 100% convinced but ya know... never had this sort of trouble with my HTC's :/
I'd just like to thank fellow-idiot for this thread, had similar situation (semibricked device, flashed something I should not have been flashing), and now my Internal is 11.3, and I seem to remember it was 14.7, just like my external - but I may be wrong. Changing ROMs, formating Internal, changing recoveries (now on Teamwin Recovery) doesn't seem to change a thing about it. Oh well, not that I'm gonna need it, just wondering where it went (never said hallo either... no manners, today's internal memories..)
11.3 is what it should be
I read the wonderful "Don't Panic" sticky, but I think I need a more drastic fix.
SHORT VERSION:
TWRP keeps saying, "Unable to mount /sdcard", and "unable to mount internal storage". I can't boot past the HTC screen, and my attempts to flash a ROM have failed due to those errors.
LONG VERSION:
I tried using TWRP 2.2.1 and Cyanogenmod 10 today, my first time flashing a custom ROM.
My phone (HTC EVO 4G LTE) was already rooted using the plain ol' HTC bootloader unlocking method.
I booted into recovery and performed a backup first. That appeared to go okay, and verified a backup existed on my external SD card.
I booted back into the OS and used ROM Toolbox to download the ROM and gapps thingy, wiped the cache and dalvik's cache. The phone rebooted and started wiping the cache and stuff. I went away for a bit.
When I came back thirty or so minutes later, the phone was all black. No lights at all despite being plugged into the AC adapter.
I came back about thirty minutes after that, and the same thing. I rebooted. The phone went to the HTC screen and then blacked out again. I rebooted into recovery. I figured the ROM didn't get flashed right, so I went to flash it again. I used the file manager in TWRP and saw that the directories /sdcard /sdcard2 and /sd-ext were completely empty, except /sdcard had a TWRP directory, which was empty. I didn't see any of my storage!
I set up ADB on my Mac and tried mounting my sdcard. No dice. I tried using fastboot to flash a ROM. Everytime I tried to do that, I got an error in TWRP, "unable to mount /sdcard", "unable to mount internal storage". I tried using fastboot to flash the .zip on my Mac, and tried using "adb put" to move the .zip to the phone and install from there. Same result.
Any ideas?
GoogleFap said:
I read the wonderful "Don't Panic" sticky, but I think I need a more drastic fix.
SHORT VERSION:
TWRP keeps saying, "Unable to mount /sdcard", and "unable to mount internal storage". I can't boot past the HTC screen, and my attempts to flash a ROM have failed due to those errors.
LONG VERSION:
I tried using TWRP 2.2.1 and Cyanogenmod 10 today, my first time flashing a custom ROM.
My phone (HTC EVO 4G LTE) was already rooted using the plain ol' HTC bootloader unlocking method.
I booted into recovery and performed a backup first. That appeared to go okay, and verified a backup existed on my external SD card.
I booted back into the OS and used ROM Toolbox to download the ROM and gapps thingy, wiped the cache and dalvik's cache. The phone rebooted and started wiping the cache and stuff. I went away for a bit.
When I came back thirty or so minutes later, the phone was all black. No lights at all despite being plugged into the AC adapter.
I came back about thirty minutes after that, and the same thing. I rebooted. The phone went to the HTC screen and then blacked out again. I rebooted into recovery. I figured the ROM didn't get flashed right, so I went to flash it again. I used the file manager in TWRP and saw that the directories /sdcard /sdcard2 and /sd-ext were completely empty, except /sdcard had a TWRP directory, which was empty. I didn't see any of my storage!
I set up ADB on my Mac and tried mounting my sdcard. No dice. I tried using fastboot to flash a ROM. Everytime I tried to do that, I got an error in TWRP, "unable to mount /sdcard", "unable to mount internal storage". I tried using fastboot to flash the .zip on my Mac, and tried using "adb put" to move the .zip to the phone and install from there. Same result.
Any ideas?
Click to expand...
Click to collapse
this seem to becoming a more frequent problem maybe something TWRP is responsible for i came to this same obstacle when trying to flash a new rom like a week ago. i tried all the nifty moves i could but no luck even went to sprint looking for answers ultimately i was forced to format (with windows) both internal and external SD. end result. yep u got it i lost everything almost 26gigs of music and files i had backed up no where else. so i formatted (heart broken) got over it now i back up files daily on my laptop thats the only way ive come to see out of this one. but check around forums a solution might work for i saw a couple didnt work for me tho.
JB ROMs rewrites the addresses of your SD cards, good chance the internal is corrupted. Boot to recovery and go to mount/mount USB storage, if you have windows then as soon as you plug it in windows will tell you to reformat, if you have Mac or Linux manually reformat the card
Thanks for the replies, guys.
Tried reformatting, but that didn't seem to help. On #twrp on freenode, they said it looked from my recovery.log that the internal and sdcard storage is hosed, and the maintainer of TWRP said to RUU back to stock. SIGH. . . .
So, since I don't have Windows at work, going to try these at home tonight:
(Great. Was trying to post links, but wasn't allowed. Suffice it to say, I was going to post my recovery.log link and the links to the instructions I am going to follow to RUU back to stock.)
Well that sucks, I'm lucky that I haven't hosed my emmc yet. I can't decide whether to stay on aosp or not, must have flashed back and forth a million times by now
Argh!
I have tried every RUU scenario I can find, and remain unable to mount my sdcard or my internal storage, have no ROM, am contemplating getting drunk. Anyone have any other ideas?
Anyone know if Sprint will fix this, or should I just cash in on my phone replacement plan?
I'd like to know what happened to mess this up so I can avoid it next time. What must have happened for my internal storage to not only be wiped -- I think I get that part -- but why can't it be mounted???? I don't get it.
GoogleFap said:
Argh!
I have tried every RUU scenario I can find, and remain unable to mount my sdcard or my internal storage, have no ROM, am contemplating getting drunk. Anyone have any other ideas?
Anyone know if Sprint will fix this, or should I just cash in on my phone replacement plan?
I'd like to know what happened to mess this up so I can avoid it next time. What must have happened for my internal storage to not only be wiped -- I think I get that part -- but why can't it be mounted???? I don't get it.
Click to expand...
Click to collapse
Did you ever find a solution to this? I'm in the same boat...
llaen said:
Did you ever find a solution to this? I'm in the same boat...
Click to expand...
Click to collapse
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
onefasttreopro said:
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I had backed up my sdcard so I didn't really care about not losing it. I think the problem was at least partially caused by having it encrypted.
I ended up flashing to stock and it let me format the sdcard from within the phone - that did it.
Thanks for the suggestion.
onefasttreopro said:
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
This just advice just saved my life. I thought for sure I bricked my phone, and right before memorial day weekend toooo! I did run into issue with the latest Lollipop RUU. I had to resort to using the old Kit Kat RUU I had saved to my computer from before. It worked like a charm.
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
I'm updating this for anyone else who runs into issues like this: I went ahead and formatted the SD card from within windows, then relocked the phone, reinstalled the RUU and I'm back in a workable mode
itsmattgw said:
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
Click to expand...
Click to collapse
I had the exact same problem. I just reformatted the internal storage and that fixed a lot of my issues. I can't however get the RUU to work. Can't seem to find my phone, neither can HTC Sync. Is this just a problem caused by MeanBean? I use to run MeanBean but then switched to CM10 for a few months and was going to switch back. Never had an issue like this before.
hey guys, first post here: i just bought the atrix 4g, got it in the mail today, used the 1-click rooter to unlock the bootloader, then to root. then i installed cyanogenmod 9- i followed instructions appropriately, but the phone hangs at the motorola logo screen at boot-up and does nothing more. i tried re-flashing, fixing permissions, clearing dalvik cache, nothing works.
edit- i installed cyanogenmod9 through clockworkmod, by installing zip from internal
i was going to re-flash stock rom, but i cant get internal storage to mount from clockworkmod (no sd card), so i cant get the stock file over to the phone to flash, so im bricked.
any thoughts/advices? thanks in advance, after not having a phone for near a week, id kinda like to make a call
leopard_fist said:
hey guys, first post here: i just bought the atrix 4g, got it in the mail today, used the 1-click rooter to unlock the bootloader, then to root. then i installed cyanogenmod 9- i followed instructions appropriately, but the phone hangs at the motorola logo screen at boot-up and does nothing more. i tried re-flashing, fixing permissions, clearing dalvik cache, nothing works.
edit- i installed cyanogenmod9 through clockworkmod, by installing zip from internal
i was going to re-flash stock rom, but i cant get internal storage to mount from clockworkmod (no sd card), so i cant get the stock file over to the phone to flash, so im bricked.
any thoughts/advices? thanks in advance, after not having a phone for near a week, id kinda like to make a call
Click to expand...
Click to collapse
Did you try using fastboot to erase system, data, cache, and osh partitions?
Sent from my MB860 using xda app-developers app
edit
leopard_fist said:
hey guys, first post here: i just bought the atrix 4g, got it in the mail today, used the 1-click rooter to unlock the bootloader, then to root. then i installed cyanogenmod 9- i followed instructions appropriately, but the phone hangs at the motorola logo screen at boot-up and does nothing more. i tried re-flashing, fixing permissions, clearing dalvik cache, nothing works.
edit- i installed cyanogenmod9 through clockworkmod, by installing zip from internal
i was going to re-flash stock rom, but i cant get internal storage to mount from clockworkmod (no sd card), so i cant get the stock file over to the phone to flash, so im bricked.
any thoughts/advices? thanks in advance, after not having a phone for near a week, id kinda like to make a call
Click to expand...
Click to collapse
You bricked your phone, not cyanogenmod ...
Restore a backup, your phone should work.
hm, can anyone tell me, why i cant get internal storage to mount from clockworkmod? is this a common problem?
i dont understand what went wrong for me, when i followed the same steps that many others did.
epinter said:
You bricked your phone, not cyanogenmod ...
Restore a backup, your phone should work.
Click to expand...
Click to collapse
Your phone is not a paperweight, just not boot the operating system
You did a backup with CWM? restore a backup as Emerson says
You can borrow a sd card copy there CM7 and install from the sdcard
You can also use RDS to install a stock rom
Never install a rom without having an one that you know works 100%
AND ALWAYS READ ALL FAULTS AND SOLUTIONS BEFORE INSTALLING A CUSTOM ROM
ok guys, i went and bought an sd card, clockworkmod mouted it fine, i found and copied over to the sd card android 2.34 for atrix, it flashed fine and my phone is back up.
can you gentleman tell me, whats a good solid rom to flash? cyanogen mod 9 obviously didnt work for me. id like to get started setting up the phone, so i need a good rom to begin with.
thanks to everyone in advance
Go with montouri's version of cm7.2 ,mrom-Olympus you can find it in the developer section. Its my daily driver. Its the most stable and has the best battery life out of all the roms that I've tried
motoxrcr1 thanks for the recommendation, running m-rom now and it runs smooth.
the first time i tried to install it, it hung at the boot logo, then i got to thinking maybe i better try updating clockworkmod, turned out that clockworkmod 4.0X that was installed by the 1-click rooter, is rather old, so i found and updated to 5.XX. tried re-flashing m-rom again, and it worked fine that time.
older clockworkmod, that's probably what caused my original problem with cyanogenmod 9..
does mrom support overclocking? not that i guess i need it, but just to know for future reference
thanks!
the trouble i caused myself, was all due to flashing the rom from an older version of clockworkmod.. after updating to a newer version 5.xx, it flashed fine
delete