Related
Sorry for posting here, I realized after I posted it, I usualy read only this subforum, my bad, someone move it please. Sorry again!
Hey, I am scared out of my mind, the whole day i tried to install maxisma's latest ROM and I used switchrom to restore 2-3 times my slacerxs/dwang ROM.
My problem is that I gave up trying to install Maxisma's ROM and I restored with switchrom a ROM of mine and I see the T-Mobile Logo (recovery Works) and them the ROM's loading screen for 10-20 seconds, and then the screens turns black, it is backlighted, but blank screen, and it remains like that .... I tried to restore a even older ROM (original dwang1.13) and it does exactly the same.
What is the problem I really hope I didn't bricked my phone, of course I did all the wipe repartition ext things.
dont do a restore FLASH a new rom not restore you should be fine fyi post this in q&a next time hope they dont flame you to bad
r_dub said:
dont do a restore FLASH a new rom not restore you should be fine fyi post this in q&a next time hope they dont flame you to bad
Click to expand...
Click to collapse
Sh*t, didn't realize that! I am formatting my SD Card and then I will install a fresh ROM, no backups and so on.
m3s_4ev3r said:
Sh*t, didn't realize that! I am formatting my SD Card and then I will install a fresh ROM, no backups and so on.
Click to expand...
Click to collapse
Yeah flash a new rom sign in just to make sure its okay then you should probably be able to do switchrom back to one of your custom mods
Me too
I had exactly the same problem yesterday, no idea what the actual cause was but the only way to fix it was to do a Nandroid restore of a previous ROM.
r_dub said:
Yeah flash a new rom sign in just to make sure its okay then you should probably be able to do switchrom back to one of your custom mods
Click to expand...
Click to collapse
Thanks, I was 'trigger'(keyboard) happy, thing is maxisma's 2.0 ROM really pissed me off ), right then I really thought i did some damage to my phone through countless flashing. I think imma stay with my custom ROM(if I get it to work) for a while now, this can't be healthy, all this flashing )
EDIT:
ghostofcain said:
I had exactly the same problem yesterday, no idea what the actual cause was but the only way to fix it was to do a Nandroid restore of a previous ROM.
Click to expand...
Click to collapse
In my case by doing a nandroid restore it won't work, I will format my SD now(X-Tremely SLOWW, hard format) and let's hope for the best.
EDIT: SOLVED, a entire format really helped.
Hey all, I need some serious help for my Mytouch3G. My MT3G just stays at boot screen all the time now every time I flash a custom rom. The last rom that worked for me was Super D 1.6 blk and other roms before that. I don't know what's wrong now, I tried using my Nandroid restore, wiped everything, other roms. I even tried re-rooting, so I had to go back to stock (which worked so I know it's not bricked).
I know this is the G1 Q&A but I since MT3G is compatible with most roms I posted here.
Also, I can boot into recovery and fastboot. Please help? All I want now is to go back to Super D 1.6 .
Try re-rooting the phone.
you probably dont have the latest radio ,and (or) spl, also make sure you wipe before flashing.
Do you have apps on sd card? If you do - you may need to reformat your EXT, regular wipe doesnt to it. And yes, you do need correct SPL and radio.
Good luck.
I would also try posting in the correct forum next time. This is the Dream forum, I don't care how close they are in specs and such, this is the dream forum. There is a magic forum for you to try out next time
djluis48 said:
Try re-rooting the phone.
Click to expand...
Click to collapse
zachattack052 said:
you probably dont have the latest radio ,and (or) spl, also make sure you wipe before flashing.
Click to expand...
Click to collapse
borodin1 said:
Do you have apps on sd card? If you do - you may need to reformat your EXT, regular wipe doesnt to it. And yes, you do need correct SPL and radio.
Good luck.
Click to expand...
Click to collapse
Thanks guys, will try.
JAguirre1231 said:
I would also try posting in the correct forum next time. This is the Dream forum, I don't care how close they are in specs and such, this is the dream forum. There is a magic forum for you to try out next time
Click to expand...
Click to collapse
Hey thanks asshole, you're truly helpful. And I have tried posting in the magic forum and I got no response.
ElahC said:
Thanks guys, will try.
Click to expand...
Click to collapse
You should wipe via Amon_Ra when going rom to rom and wipe before using your backups.
There is no reason for foul language either
Please bear with me. I tried posting questions about this in the Q/A forum and received no real help.
I recently went from FRF50 to FRF83 and started getting random reboots. I'm on the 4.06.00.12_07 radio with the stock kernel. I wiped everything before flashing.
Today I wiped again and reflashed FRF50 and everything seemed to be okay aside from maybe 1 reboot.
I just flashed the stock FRF85B and rooted it and I'm back to rebooting. It's even worse now. It reboots the instant everything loads.
I got the last_kmsg:
http://pastebin.org/365407
Please let me know what's wrong. I'm dying to know. Is it hardware? Is it the battery? Am I going to have to pay a buttload of cash for HTC to fix it?
Thanks for any help
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
GldRush98 said:
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
Click to expand...
Click to collapse
Is it the wrong forum? Do people at the Q/A or general forum know about kernels/deeper info and do the people who know about that stuff venture over to those forums?
I tried getting info there, and I got none. This is the last place to turn.
What would wiping and starting from stock achieve?
No excuse for posting in the wrong location. But wipe data, all caches and reflash stock rom + radio. Report in General Section.
S_Dot said:
No excuse for posting in the wrong location. But wipe data, all caches and reflash stock rom + radio. Report in General Section.
Click to expand...
Click to collapse
How will this help me? Okay if stock works, but what about the update?
Why not maybe looking at using one of the moded versions of the Rom. If those dont work then maybe you need to think of going back to the Stock 2.1 and waiting for OTA to hit your phone. Going back to 2.1 will fix the problem and getting the OTA should work. Other wise wiping and reflashing is all that someone can tell you to do since I know i am using FRF83 right now with no reboots.
Just wipe everything inc dalvik-cache
Stock kernel keeps rooting so I guess its a framework issue
Prod1702 said:
Why not maybe looking at using one of the moded versions of the Rom. If those dont work then maybe you need to think of going back to the Stock 2.1 and waiting for OTA to hit your phone. Going back to 2.1 will fix the problem and getting the OTA should work. Other wise wiping and reflashing is all that someone can tell you to do since I know i am using FRF83 right now with no reboots.
Click to expand...
Click to collapse
leonnib4 said:
Just wipe everything inc dalvik-cache
Stock kernel keeps rooting so I guess its a framework issue
Click to expand...
Click to collapse
I'm going to try to go back to stock and see if it works. If not I can only assume that it is a hardware problem and I'll have to bite the bullet and pay for repairs.
What kind of a hardware problem could it be???
Can someone help me get back to stock properly?
See sticky.
Mod move to q&aplease.
leonnib4 said:
See sticky.
Mod move to q&aplease.
Click to expand...
Click to collapse
Sticky is full of bad info. I have new radio (4.06.00.12_07).
I'm assuming that if I get stock radio and the ERD79 update.zip I should be fine?
GldRush98 said:
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
Click to expand...
Click to collapse
You sir, are a complete asshole.
Sent from my Nexus One using XDA App
Yes the new radio won't work on 2.1 so change Ur radio and flash that update.zip and cross Ur fingers that Ur problem is fixed good luck let us know
Sent from my Nexus One using XDA App
FML. Hardware issue. Just went through CM 5.0.8. flash from scratch including re-flashing new radio and new recovery and I got a reboot during sign-in to Google.
God ****ing dammit.
Any logcat?
if you have an ext partition.. wipe that as well..
might be a battery issue. my battery had been overheated during navigation and right after boot it would give out turn off and boot again. just replaced it and worked fine.
To check battery issue, I suppose running with charger inserted would be enough.
Jack_R1 said:
To check battery issue, I suppose running with charger inserted would be enough.
Click to expand...
Click to collapse
What do you mean by this?
I'm pretty sure it is the battery. Been keeping minimal use today without USB charging and haven't had a reboot.
Any other ways I can confirm a bad battery?
Sent from my Nexus One using XDA App
If you can successfully boot and use the phone heavily while connected to a charger (preferrably AC charger - it can provide twice the current of USB cable), and you see no reboots - I believe that would point to your battery with a very high probability.
So for the past two days I've been trying to flash the new AOSP Gingerbread ROM, but although I follow everything straight from the wiki it always seems to get stuck on the HTC screen after the last reboot. Help me please!
EDIT: So I somehow got the rom to boot last night using RA recovery but after loading up a notice says Setup Wizard not being able to respond...etc, etc. Also after booting my home, call, and search buttons don't work at all. not even for other roms. PLEASE HELP!
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.
Make sure u install manually through clockworkmod mod first format boot system data and cache then install the rom let it boot then reboot and install gapps without wiping and reboot then you should be good I'm using the normal clockworkmod 2.5.2 and it works great
Sent from my HTC Hero CDMA using XDA App
okay thanks! ill try that and get back to you.
so no luck at booting. i'm still stuck at the HTC Boot screen.
i tried also and still no luck .. i hate this
to anybody having problems flashing GB, try these steps EXACTLY:
1) use clockwork 2.5.0.1 and follow the wipe/format process in the wiki
2) flash the rom then gapps
3) FLASH A CAPPED 691 KERNEL
This seems to be a continued issue, and I think it is because some phones can't handle high clock speeds like 768. The recovery currently posted by aosp (cwm 3.0.0.5) is overclocked and therefore will not boot, same with the kernel in the rom. Report back here if it works, I have already updated the wiki to advise people of this. Good Luck.
So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.
I'm upgrading aosp 2.3.2 rom from nightly build #188. Before flashing aosp rom plesae try to wipe everything like data, dalvik-cache, battery and rotate status. BTW, I'm using RA-Recovery not ClockworkMod.
i installed it after the standard wipes and thats it and its working just fine at 768 on my hero200. didnt have any issues and im loving the rom, but i am having one issue. this link is to my issue in q and a. if you can help feel free to hop on my thread and reply. other than that, i juast wanted to say this rom is great!
sai5o4 said:
So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.
Click to expand...
Click to collapse
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass
il Duce said:
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
I agree with that. He should try a recovery that's not overclocked.
Root-Hack-Mod-Always™
Yeah I'm using clockwork 2.5.0.1.
sai5o4 said:
Yeah I'm using clockwork 2.5.0.1.
Click to expand...
Click to collapse
Well, I hate to say it but you must be missing a step somewhere. FYI in the OP for gingerbread the cwm3.0.0.5 is now capped at 691, so try that one again. Wipe both wipe options, go to mounts and format boot,system,data,cache, then gn into advanced wipe dalvik twice. Flash the rom,gapps,deca #43 capped 691 kernel, reboot. The first boot should take a while so be patient. Report back here if you can't get it, and I would recommend going into the live help room (aospbot IRC) which in the OP for GB. Good luck.
So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App
sai5o4 said:
So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I think you should back up your sd card and then format it in your pc. Then start all over. From the recovery on down. Skip any mods till you get booted up. Like keyboards and boot screens etc. And try the capped cwm recovery. Hope it helps good luck
Something.About.Me.You.Dont
Like.Its.Cool.I.Understand.AWAH
Still no luck on booting aospCMod. Like they say no two heroes are the same. But that doesn't mean I'm still not going to try again and again and again (xinfinity).
got it to boot but...
so i somehow got it to boot using ra-recovery but right as i loads it says the setup wizard has unexpetedly stopped processing. any help?
sai5o4 said:
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.
Click to expand...
Click to collapse
Glad I could help man! Glad to see you got it worked out!
There's a readme in the Aosp 2.3.2 OP. It's right under the files, labeled README. I think it would help if anyone having trouble actually reads through this. skipping steps causes problems.
also, Factory reset skips over the /system partition. I recommend wiping /system partition if you're coming from another rom, or if you are decided to start fresh. You have to go into the partitions menu to actually format the /system partition.
mtran2988 said:
You have to go into the partitions menu to actually format the /system partition.
Click to expand...
Click to collapse
This is true if you use CWM (which I do not ) but if you fastboot wipe all the partitions you will have no issues w/ RA as the OP discovered once he used the instructions that I posted.
touble with vvm
uh not quite sure if this is rite place to post this but looked better than the rest, so i got the rom running fine and it is wonderful improvement to my what use to be my wifes stock hero. Only problem is with the visual voice mail, i copied it from the stock hero before flashing, than after flashing copied it back, it works in the sense that i can see the voicemail in the app and even the voicemail to text works, but 2 things are wrong, 1 is i cant clear voicemail notification in the status bar without rebooting phone, and now she gets a text from a 9069 that tells her phone has recieved a voicemail, found a work around for the second one i blocked the number using blacklist so the text dont come thru nomore, but how i can i fix the fact that the only way to clear the voicemail notification is to reboot the phone? Any help, comments or suggestions would be greatly appreciated. Or is there somewhere i can dl the latest sprint vvm app?? or are they device specific. Thank you in advance for any help
Hello all,
After flashing CyanogenMod the other day, I decided I didn't like it too much. ( Mind you, I just use my phone for basic phone stuff, so please don't flame me for it. xD ) So I used a nandroid to go back to my original (rooted) stuff.
However, in doing this, it seems that it messed up my Market app somehow.
Whenever I try to search, open, or do anything involving the Market App, it'll say: Attention. A network error has occurred. Retry, or cancel and return to the previous screen.
It's been like this for a while now. I can use internet, voice-to-text, and anything else that requires data ( not even WiFi works with Market ), but not Market.
What can I do to fix this?
Full wipe. Fresh install of rom+gapps.
Yea its Me Again With The
Modified Hero
@laie - he said he nanded back to rooted stock
@OP - try the nand restore again? Otherwise you could try adb shell fix_permissions?
laie1472 said:
Full wipe. Fresh install of rom+gapps.
Yea its Me Again With The
Modified Hero
Click to expand...
Click to collapse
Tried factory reset, that didn't work, I'll try that option last >.<
il Duce said:
@laie - he said he nanded back to rooted stock
@OP - try the nand restore again? Otherwise you could try adb shell fix_permissions?
Click to expand...
Click to collapse
It tells me that "fix_permissions: not found"
Edit: I've got it fixing now, will edit with update.
Edit(2): It didn't help, sadly.
I don't even remember, but does rooted stock 1.5 allow you to install non-market apps? If so, go find a market 2.3.6 apk on xda or google. Delete the one you have, boot into recovery wipe cache and then reboot, install the app - see if that'll work.
Nope, that didn't work sadly... Ironically, my Market worked perfectly without the updates installed. Is it possible just to block all updates for the Market apk?
this might work for you. a friend was having similar problem. this is what i did (note, i really really think that it was pure coincidence but...) go to SETTINGS -> APPLICATIONS -> MANAGE APPS. locate Market, if Force Stop is not greyed out. then click it, then click Clear Data.
like i said, his was having the same problem, i really think that it may have been a coincidence, but maybe not.
Vvh said:
Nope, that didn't work sadly... Ironically, my Market worked perfectly without the updates installed. Is it possible just to block all updates for the Market apk?
Click to expand...
Click to collapse
Yes, you need to delete the system app "marketupdater.apk". Also, if you go into settings/manage apps/all/market - can you click the button "uninstall updates"? If not, do you know what market version you had that worked? If so try to find and install that one using the same steps as I mentioned before. If that doesn't work, I'm at a loss.
Also what ngholson just posted is a good idea along with clear cache from the same menu.
I hope you get it figured out, good luck.
il Duce said:
@laie - he said he nanded back to rooted stock
@OP - try the nand restore again? Otherwise you could try adb shell fix_permissions?
Click to expand...
Click to collapse
Yea and??? He can still start fresh. He posted he did a nand back to his rooted stuff. Which means he can srart fresh. As in wipe data,cache dev-cache and sd-ext. Boot up and then reboot back into recovery reflash gapps. Boot up. Load tb go into settings, manage apps locate market force stop and clear data. Open tb up locate market updater apk. Uninstall. Reboot should be good.
Yea its Me Again With The
Modified Hero
ngholson said:
this might work for you. a friend was having similar problem. this is what i did (note, i really really think that it was pure coincidence but...) go to SETTINGS -> APPLICATIONS -> MANAGE APPS. locate Market, if Force Stop is not greyed out. then click it, then click Clear Data.
like i said, his was having the same problem, i really think that it may have been a coincidence, but maybe not.
Click to expand...
Click to collapse
Must have been, I tried it with no luck, but I'm glad it worked for your friend.
il Duce said:
Yes, you need to delete the system app "marketupdater.apk". Also, if you go into settings/manage apps/all/market - can you click the button "uninstall updates"? If not, do you know what market version you had that worked? If so try to find and install that one using the same steps as I mentioned before. If that doesn't work, I'm at a loss.
Also what ngholson just posted is a good idea along with clear cache from the same menu.
I hope you get it figured out, good luck.
Click to expand...
Click to collapse
The problem version is 2002306, oddly enough, I've overheard some other people having problems with it as well at a place a friend works. Maybe it's a stock hero thing. I'll revert to an older version, maybe one day this will clear itself out.
Thank you everyone for participating in helping me. At least it was a good effort.
laie1472 said:
Yea and??? He can still start fresh. He posted he did a nand back to his rooted stuff. Which means he can srart fresh. As in wipe data,cache dev-cache and sd-ext. Boot up and then reboot back into recovery reflash gapps. Boot up. Load tb go into settings, manage apps locate market force stop and clear data. Open tb up locate market updater apk. Uninstall. Reboot should be good.
Yea its Me Again With The
Modified Hero
Click to expand...
Click to collapse
Laie I was just telling you, don't get all frisky. If you read the OP again, you'll see he WANTS to be on stock 1.5. I couldn't tell you why lol. Maybe you forgot (it's been forever) but stock and sense based ROMs already contain gapps. You only flash those on AOSP based ROMs, so he can't reflash gapps. If he wiped and then nand restored it would've restored /system which is where the market would live in a stock ROM. His issue was likely a market auto-update which did not agree with old ass donut stock. Who knows. I wasn't bashing you, and I'm not now, calm down. Hopefully this info helps you help someone later. Peace.
OP- I have ONE MORE idea. Go grab a themed market zip from xda member "pendo" - he has green, blue, and red. They should flash from recovery. Delete your current market app FIRST, and clear cache and dalvik cache in recovery, flash and reboot. Good luck.
EDIT: 2 ideas I guess, copy the nand backup to your computer, find the "marketupdater.apk" in /system/app and delete it out of the nand. Copy that new nand to the same place as the current one you have and try to wipe all then restore that newish one.... I actally have NO idea if you can alter a nand or the system.img it contains, but it may be worth a shot. You could also just give up, and get gingerbread, because it's AWESOME.
il Duce said:
...You could also just give up, and get gingerbread, because it's AWESOME.
Click to expand...
Click to collapse
LOL agreed.
@OP - You could also try one of the *ahm* market replacements. like *ahm* applanet or something (not sure how 'legal' they are but...)
also, i know someone mentioned it before but did you ever get your permissions fixed? if not try that too, you can do it from ROM Manager.
ngholson said:
LOL agreed.
@OP - You could also try one of the *ahm* market replacements. like *ahm* applanet or something (not sure how 'legal' they are but...)
also, i know someone mentioned it before but did you ever get your permissions fixed? if not try that too, you can do it from ROM Manager.
Click to expand...
Click to collapse
or amazon app store.
il Duce said:
Laie I was just telling you, don't get all frisky. If you read the OP again, you'll see he WANTS to be on stock 1.5. I couldn't tell you why lol. Maybe you forgot (it's been forever) but stock and sense based ROMs already contain gapps. You only flash those on AOSP based ROMs, so he can't reflash gapps. If he wiped and then nand restored it would've restored /system which is where the market would live in a stock ROM. His issue was likely a market auto-update which did not agree with old ass donut stock. Who knows. I wasn't bashing you, and I'm not now, calm down. Hopefully this info helps you help someone later. Peace.
OP- I have ONE MORE idea. Go grab a themed market zip from xda member "pendo" - he has green, blue, and red. They should flash from recovery. Delete your current market app FIRST, and clear cache and dalvik cache in recovery, flash and reboot. Good luck.
EDIT: 2 ideas I guess, copy the nand backup to your computer, find the "marketupdater.apk" in /system/app and delete it out of the nand. Copy that new nand to the same place as the current one you have and try to wipe all then restore that newish one.... I actally have NO idea if you can alter a nand or the system.img it contains, but it may be worth a shot. You could also just give up, and get gingerbread, because it's AWESOME.
Click to expand...
Click to collapse
Duce were in the op does he say he's looking to get back to 1.5??? Humm think you might be reading to much " lol " eyes playing tricks on you??? He said he restored his rooted stuff. Not restored 1.5. And nope I remember 1.5 and I'm aware of the gapps only flash with aosp. I posted my comment because he didn't say 1.5 so I took a guess as he was not on 1.5 because he didn't mention it. So mabey this will help you help someone in the future slow it down when ya read. Because you know what happens when you assume. "" Read slow "" duce read slow lol
Yea its me again. With the
Modified Hero
Hm, well your right. Hey op, stock sucks. Get gingerbread.
sent from a series of tubes.
il Duce said:
Hm, well your right. Hey op, stock sucks. Get gingerbread.
sent from a series of tubes.
Click to expand...
Click to collapse
Super agree. Ditch stock. Who doesn't like cookies???
Yea its me again. With the
Modified Hero
@il Duce
Pendo's themed market wouldn't flash, sadly. And it's a shame too, because they look really great.
@ngholson
I looked into that, but it's permissions are a bit much.
@laie1472
I'm really sorry, you're right, I forgot to mention what I'm using.
It's:
Firmware: 2.1-update1
Build: 2.27.651.5
Again, I'm sorry for not mentioning that.
I redid everything on it, the only thing I haven't touched is the radio file.
When I tried CyanogenMod 6 at the start of this thread, it had me flash 2.42.01.04.27. Could that be the problem?
And I'm terribly sorry for the delay in replying. Other issues are stealing my time.
Ok let's start from scratch. What rom,recovery, kernel & mods are you using?? Also whats your prl, and are you s-off???
Yea its me again. With the
Modified Hero
Firmware: 2.1-update
Baseband: 2.42.01.04.27
Kernel: 2.6.29-bc0d2cff [email protected] #1
Build: 2.27.651.5 CL 169236 release-keys
Software: 2.27.651.5
Browser: Webkit 3.1
Pri: 2.62_003
PRL: 60677
ROM: Stock (and rooted) 2.1 Eclair.
Recovery: RA-heroc-v1.6.2
Mods:
Android Bios Boot animation
LauncherPro
That's about it. I think it's all worked flawlessly until the radio, but I'm not sure. If I'm missing any info, please let me know.
maybe consider starting completely over. download a new rom, i recommend aospcmod. download the latest version of gapps at the same time. if you don't already have it install ROMManager from errr. damnit your market doesn't work... hopefully you already have it. Open rom manager and install a custom recovery (i recommend clockworkmod) once that is done copy both the new rom and gapps zips to your sdcard, reboot to recovery (either manually or using rommanager) wipe everything. then select 'choose zip from sdcard' (or similar, can't remember exact verbiage) and install your ROM, then before you let it reboot, then use the same option and install gapps as well, then reboot. follow setup and it should work fine.