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.
Related
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
Hey guys!
I need some help. A friend of mine came to me with a Dell Streak 7. The streak currently has 2.2.2 on it and at first seemed to be pretty stable. However, after navigating a bit on it, things were constantly force closing and crashing.
So I decided to do a factory reset, first through the settings, and when the Streak turned back on, everything was still the same. So my next try was through fastboot. Did full facory reset including user data, looked to work fine, until it turned on and it was EXACTLY the same!! I tried gingerroot to get root and then flash a new ROM and hopefully wipe it that way, but NOTHING, has work.
I am pretty good at this stuff and never ran into this type of problem. If ANYBODY has any ideas on how to get this completely wiped back to factory or even rooted with a clean boot image, i'm all ears!!
Thank you in advance for any information you guys can offer!!
-Matt
mylexon20s said:
[nonsense removed]
Click to expand...
Click to collapse
Blah blah, you don't have a virus. Meh.
khaytsus said:
D-Bag Comment Removed
Click to expand...
Click to collapse
If you have an idea on how to re-flash this thing back to stock for a friend, put in your 2 cents, if not, go troll somewhere else
mylexon20s said:
If you have an idea on how to re-flash this thing back to stock for a friend, put in your 2 cents, if not, go troll somewhere else
Click to expand...
Click to collapse
Well, thank Dell but you can't reset using the Android tools, you have to use their custom recovery to do it. Which is why it's exactly like it was, and it'll remain that way. You'll likely have to send it into Dell.
And yeah, douchebaggery is tagging your thread with "virus".
Restore to factory settings using nvflash the instructions r preety straight forward. Here's the link http://forum.xda-developers.com/showthread.php?t=1018809&highlight=nvflash
Just follow the instructions if ur not sure read them again and again. If u don't understand some of the terminoly just Google the search terms ull be OK.
There is a medicine for your bug its called honeystreak or should i call it the transformerfreak lol
Sent from my SAMSUNG-SGH-I897 using XDA App
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Whats been the outcome mylexon20s?
Hi there, sorry about the dramatic title, not sure what kind of help this need,s other than the general kind. It's my first post here and I'm asking for help already. I know you must hate it when people do this (I do on other forums haha) but I kinda need your help.
Basically, I bought a motorola milestone of gumtree (kinda like a UK craigslist) which was rooted with CM7. Everything worked fine when I got it, but today, when I tried to download stuff from the market, it gave me a force close message. The stock music player also needed to be force closed. I googled it, and did the usual restart the phone, take out battery etc... which didnt work. On the motorola website they say to do a factory data reset, which didn't appear to work. I then tried doing a manual reset, through the recovery screen I think, I pressed the factory reset button, but now my phone hangs on the motorola logo. I'm quite technical when it comes to most things, but i'm new when it comes to rooting. I presume doing that also wipes the ROM? I think/hope that all I need to do is put a rom on the SD and do the update from that, but I'm really not sure.
Thanks for any help
p.s while the phone is GSM and works with my SIM, the guy I bought it off got it from Korea, don't know if that makes a difference to anything
install OR (fufu or nadalback's , there is a link in cm7 thread), go into dev forum.
wipe everything from or and reboot. if that doesn't work try flash another rom. and yes you will lose data, you already did with the factory reset.
if you have cm7 you already have the device rooted.
edit: follow advice from moto, only if you have stock rom, and now you don't
i2gh0st said:
install OR (fufu or nadalback's , there is a link in cm7 thread), go into dev forum.
wipe everything from or and reboot. if that doesn't work try flash another rom. and yes you will lose data, you already did with the factory reset.
if you have cm7 you already have the device rooted.
edit: follow advice from moto, only if you have stock rom, and now you don't
Click to expand...
Click to collapse
Cheers for the input. Sorry to sound thick, but I'm new to rooting, so I'm not familiar with how to flash roms and stuff like that, If you could clarify it what you said, that would be awesome.
Thanks again
http://forum.xda-developers.com/showthread.php?t=983516
Sent from my GT-I9100 using Tapatalk
Cheers for that, had a quick skim through and it looks promising, only thing is I'm not sure what one I need to do to get it to boot. Do I have to install openrecovery? Do i need to revert it back to stock? Do I need to install a custom rom or is a combination of the 3? I'm sorry if these are basic questions, but I literally have no idea which one to select.
Also, if the phone was bought in korea, but is set to english, what SBF file do I download, a UK one, or a international one?
Cheers
himynameisnathan said:
Cheers for that, had a quick skim through and it looks promising, only thing is I'm not sure what one I need to do to get it to boot. Do I have to install openrecovery? Do i need to revert it back to stock? Do I need to install a custom rom or is a combination of the 3? I'm sorry if these are basic questions, but I literally have no idea which one to select.
Also, if the phone was bought in korea, but is set to english, what SBF file do I download, a UK one, or a international one?
Cheers
Click to expand...
Click to collapse
Right now, is your phone running CM7? If so, place the newest OpenRecovery on your SD Card and place the ROM you want in OR/updates. Because you are from the UK, you should try flashing a UK sbf if you need to revert to stock.
Sent from my Milestone using xda premium
Hi,
I am running FroyoMod, and i installed ROM manager. Through there i clicked 'flash ClockworkMod Recovery' and now i cannot enter into recovery at all.... the worst thing is that my phone cannot connect to wifi connection and i cannot go into recovery to clean Dalvik cache in order to test it if this sloves my problem.
Any suggestions?
Sent from my NOOKcolor using Tapatalk
Fekish said:
Hi,
I am running FroyoMod, and i installed ROM manager. Through there i clicked 'flash ClockworkMod Recovery' and now i cannot enter into recovery at all.... the worst thing is that my phone cannot connect to wifi connection and i cannot go into recovery to clean Dalvik cache in order to test it if this sloves my problem.
Any suggestions?
Sent from my NOOKcolor using Tapatalk
Click to expand...
Click to collapse
ROM Manager and CWM do NOT work on Milestone.. Even though it does say it works, it doesn't. OpenRecovery and any mod of it is the only thing that works.
Right now, you have a semi-brick. You need to reflash a stock SBF for your country (to get 3G/data) and then restart the rooting process with the VR, installing OR, etc.
http://and-developers.com/sbf:milestone221
There should really be a sticky for this. It wouldn't be too hard, and should be read by all before they flash a new ROM or ask this question
Oh god! Thanks...
So after 1,5 years i would have to start from scratch! :-(
At least i am not using 3g and at least i can use it as a phone...
Sent from my NOOKcolor using Tapatalk
Regardless, any custom ROM is better than stock 2.2.1, so I would say it's worth the effort to re-root and flash another custom ROM.
skadude66 said:
Regardless, any custom ROM is better than stock 2.2.1, so I would say it's worth the effort to re-root and flash another custom ROM.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1237473
Can someone help me?
i run my country's SBF through RSD, but i am stuck on the "android" logo at the start of the phone.
Anyway i can go past this?
The phone might be 100% bricked now?
OK Solved - had to find a non service SBF....
By the way almost all the links for the sbf's are not valid anymore! It would be a nightmare for someone trying to find old SBF's now...
Fekish said:
OK Solved - had to find a non service SBF....
By the way almost all the links for the sbf's are not valid anymore! It would be a nightmare for someone trying to find old SBF's now...
Click to expand...
Click to collapse
Gotta make sure you download them now I guess Thanks for reminding me, I might do that now
Running Beanstalk.
Have been having intermittent issues with mobile data, so I'm sadly familiar with toggling Airplane mode, changing the CMDA subscription, rebooting, etc. in order to jog mobile data into working again. Lately have been having a weird, sporadic problem with people I call only hearing static on my end, so I chatted with Sprint, got to the point where they suggest typing the code to reset/update PRLs into the dialer, and bailed.
Then, in my infinite wisdom decided to try flashing a Sense ROM, proceeding with the manual PRL update/reset, and then wiping and restoring my Beanstalk nandroid.
Now I can't make or receive calls or texts at all, no matter what I do. Have tried all the old toggles. Have tried a complete reflash of Beanstalk. I'm beginning to worry I seriously borked something up.
Is anyone familiar with this kind of situation? Did I screw up, and if so, how bad? Any solutions anyone can think of? I'd be most grateful for any and all help. Thanks guys.
Reinstalling ROM from scratch and if that doesn't work then running ARU.
EPayne123 said:
Reinstalling ROM from scratch and if that doesn't work then running ARU.
Click to expand...
Click to collapse
What's ARU? I did try reinstalling the ROM from scratch and it didn't fix it.
thedodus said:
What's ARU? I did try reinstalling the ROM from scratch and it didn't fix it.
Click to expand...
Click to collapse
Okay here is what you can do, there is an app floating around these forums that can allow you to manually write the prl, find that, and then use a stock prl for sprint. I believe this post will help:
http://forum.xda-developers.com/showthread.php?t=2296167
Let me know if that helps.
Oh and also yeah flashing a different rom wouldnt help because they do not contain any of that information, in fact i think all the carrier information is stored in a different partition for this exact reason -so they cant be easily overwritten.
I build the Beanstalk here and haven't come across that issue yet. Do you have a backup of your original stock ROM? You need to get back to straight stock, like out of the box stock. From there, you can update your prls or anything else OTA-style, check your functionality, then redownload the Beanstalk ROM from here, do a full wipe(no internal data), install the fresh DL, Gapps, fix permissions(PhilzTouch 6.0.3.3 only), and reboot. Should be good to go and should only need to toggle airplane for reboots and occasionally for the wifi. Let me know how it goes, either here, on the BS thread or by PM. Good luck....
If you have no original back up(after getting back to straight stock, MAKE ONE), then use Bigdaddy619s threads on getting back to stock. After that, then follow the steps above.
You should always make an original back up of stock directly after rooting and unlocking. ALWAYS
BMP7777 said:
I build the Beanstalk here and haven't come across that issue yet. Do you have a backup of your original stock ROM? You need to get back to straight stock, like out of the box stock. From there, you can update your prls or anything else OTA-style, check your functionality, then redownload the Beanstalk ROM from here, do a full wipe(no internal data), install the fresh DL, Gapps, fix permissions(PhilzTouch 6.0.3.3 only), and reboot. Should be good to go and should only need to toggle airplane for reboots and occasionally for the wifi. Let me know how it goes, either here, on the BS thread or by PM. Good luck....
If you have no original back up(after getting back to straight stock, MAKE ONE), then use Bigdaddy619s threads on getting back to stock. After that, then follow the steps above.
You should always make an original back up of stock directly after rooting and unlocking. ALWAYS
Click to expand...
Click to collapse
Thanks, both of you.
BMP - Beanstalk rules - it's definitely my fault. If I have a back-up made just after getting S-OFF, would that work?
matinm90 - thanks for the info...that explains exactly what the problem I'm having is.
I'll try these solutions out and post back. Thanks again guys.
Yes, it should as long as everything worked then. Driving right now. Try it and let me know. When I get home I'll help however I can.
Sent from my One using XDA Premium 4 mobile app
thedodus said:
Thanks, both of you.
BMP - Beanstalk rules - it's definitely my fault. If I have a back-up made just after getting S-OFF, would that work?
matinm90 - thanks for the info...that explains exactly what the problem I'm having is.
I'll try these solutions out and post back. Thanks again guys.
Click to expand...
Click to collapse
Your welcome and yeah it should defintely work, just make sure you use the right prl
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
thedodus said:
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
Click to expand...
Click to collapse
More than welcome. Glad you're up and running.:highfive:
thedodus said:
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
Click to expand...
Click to collapse
Your welcome glad you got everything straightened out
Sent from my HTCONE using Tapatalk