Related
Howdy all,
My phone broke, so I'm back on the hero. I forget any and all stuff of how to's on this phone so bear with me. Basically, I'm a noob for the hero now.
So, recently, I followed the Cyanogenmod Full Update wiki guide, rooting it with the rageagainstthecage exploit. However, after my first time, my phone would eventually be so slow that it would seem to freeze. It's just so so so so slow. It's unusable. The lockscreen would come up, and i would touch the lock icon, which would vibrate. I would slide to unlock, but the screen doesn't react. at all. then it would vibrate, indicating an unlock, but the screen doesn't change at all. Occasionally, I'm able to accidentally enter an app, but I cannot read texts, answer calls, or reply to texts. Or do anything else.
Occasionally, I'll get a "app is unresponsive" message, but I can't force close/wait.
Oh, btw, when this happens, I can't get into my recovery (CWM 3.0.0.5). Also, I don't see the boot animation.
I have done an RUU stock reset, which fixed it once. The problem occurred again while on CM7, and I did another RUU reset, but the problem is now consistent throughout the stock sense. Omigawd what do i do?
Since I am now on stock that has usb debugging disabled, I can no longer access adb.
I am currently on absolute stock (fresh-out-of-the-box like), not rooted, and have S-OFF.
I am fairly well versed in fastboot and adb commands. When I try to access the recovery, I am sent to a black screen. When I plug in while in recovery and do "adb devices," I get my model number with the message "offline."
I AM OUT OF IDEAS! Someone. Please helpppp.
Thank you for reading. Thank you for helping.
Try a re-root with regaws rooter (the old version if you can get it) i swear by it. or Z4 root. once you have reestablished root, get Rom manager and flash the 2.4.0.7 recovery. then in rom manager go to downloads and get the cyanogen mod download of your choice( myself i prefer 7.0.3) and flash. you should be good to go from there.
as far as your adb it looks like your pc either isnt recocnizing your phone or you dont have the proper drivers installed.
Bout all i can tell ya ,one noob to another,,,
BTW, if you want to start completly from scratch, since your s-off,you can get a HERCIMG.img i think in the development sectin of this forum that is flashable from fastboot,,,try that ,,,Later man and good luck
Luckily you are S-Off. Can you put a HERCIMG.zip on the root of your sd card with a recovery (even CWM 2.5.0.7 will do) and then maybe try downloading another rom. Maybe you have a bad download. I am a big fan of Jaybob's TeamHeroc Rom which is a great CM7ish type of rom. Make sure that you format boot, cache, data, and system (I do it 3 times for each to make sure that it is really wiped) before you flash whatever rom you choose. You might have some leftover stuff that is causing some issues. Just wiping data and cache might not be enough. Here is a HERCIMG with a 4.0.1.4 recovery that you can load from H-Boot. I'm pretty sure that it's the Orange Recovery that I use.
hugabu said:
Howdy all,
My phone broke, so I'm back on the hero. I forget any and all stuff of how to's on this phone so bear with me. Basically, I'm a noob for the hero now.
So, recently, I followed the Cyanogenmod Full Update wiki guide, rooting it with the rageagainstthecage exploit. However, after my first time, my phone would eventually be so slow that it would seem to freeze. It's just so so so so slow. It's unusable. The lockscreen would come up, and i would touch the lock icon, which would vibrate. I would slide to unlock, but the screen doesn't react. at all. then it would vibrate, indicating an unlock, but the screen doesn't change at all. Occasionally, I'm able to accidentally enter an app, but I cannot read texts, answer calls, or reply to texts. Or do anything else.
Occasionally, I'll get a "app is unresponsive" message, but I can't force close/wait.
Oh, btw, when this happens, I can't get into my recovery (CWM 3.0.0.5). Also, I don't see the boot animation.
I have done an RUU stock reset, which fixed it once. The problem occurred again while on CM7, and I did another RUU reset, but the problem is now consistent throughout the stock sense. Omigawd what do i do?
Since I am now on stock that has usb debugging disabled, I can no longer access adb.
I am currently on absolute stock (fresh-out-of-the-box like), not rooted, and have S-OFF.
I am fairly well versed in fastboot and adb commands. When I try to access the recovery, I am sent to a black screen. When I plug in while in recovery and do "adb devices," I get my model number with the message "offline."
I AM OUT OF IDEAS! Someone. Please helpppp.
Thank you for reading. Thank you for helping.
Click to expand...
Click to collapse
I like Regaw's for rooting too. I used it the last time I did an RUU.
Isnt that what I said just before you ??? Lol
BTW Pilot, Where have you been? One of the most active members of the Heroc forum and all of a sudden ,poof, gone like a fart in the wind ! And then as if by magic, Poof, your back.I knew youd return, they always always return to the ol reliable Heroc. Good to see you around again bud, Later man,,,
Sent from my HERO200 using xda premium
hey guys just got back from vacation. Thanks for all your feedback. I switched phones to a temporary one now. I don't really feel like switching back to the hero cuz it costs money to activate phones. Also, I talked to an app developer about my problems. He told me that 1. the phone is way to old to be running gingerbread. Some nasty software probably carried over from my last flash onto the stock RUU flash. and that 2. whenever the problem occurs, I should let the battery drain before I do anything. Turns out, whenever the problem happens nowadays, I just let the battery drain and its all fixed. OKAY WTF. But all smiles now. Its my ipod-touch-like device now. I used regaws root.
THANKS GUYS SO MUCH.
I had a problem a few days ago that i was having problems after rooting my phone so i brought it back to stock using RSD Lite and then tried to flash a new rom on the phone and it said my phone was not unlocked so i downloaded The Myth Tools and unlocked it that way but I am wondering if i messed it up because i did not really know what i was doing i just tried to see if i could figure it out and it seemed like it worked until today. I flashed Touchwiz on there a couple days ago and it worked fine i made a backup wiped the cache,dalvik cache and system now today it randomly freezes and is now stuck on the bootloader unlocked screen. I can hold down power and volume up and boot into recovery which is ClockworkMod Recovery v6.0.3.6 touch and it also says under that in the bottom right of the screen Warning No file_contexts now i dont know if it has always said that since i flashed this recovery or just started. I also once again tried wiping the cache and dalvik cache because i read it on another post of someone stuck on this screen so i tried that and rebooted it still the same result stuck on bootloader screen. At this point i have no idea what to do. If i have to start over from stock because i messed up unlocking it or completely wipe it again and reflash touchwiz or another rom. I have had nothing but problems since rooting this phone I have gone through atleast 6 to 8 roms because every single one of them gives me a problem somehow. The most common is when i make a call or recieve one and i put the phone up to my ear I know the sensor turns off the screen but when i take it away to end it or do something its completely off or apps force closing all the time still after i did the stock reflash. I am starting to wonder if its just my phone because everyone else i read about has no problems with there phones mine nothing but problems. Please if someone could help me or walk me through this process it would be greatly appreciated I love the things it can do with custom roms but i just wish it would run smooth.
bpc87 said:
I had a problem a few days ago that i was having problems after rooting my phone so i brought it back to stock using RSD Lite and then tried to flash a new rom on the phone and it said my phone was not unlocked so i downloaded The Myth Tools and unlocked it that way but I am wondering if i messed it up because i did not really know what i was doing i just tried to see if i could figure it out and it seemed like it worked until today. I flashed Touchwiz on there a couple days ago and it worked fine i made a backup wiped the cache,dalvik cache and system now today it randomly freezes and is now stuck on the bootloader unlocked screen. I can hold down power and volume up and boot into recovery which is ClockworkMod Recovery v6.0.3.6 touch and it also says under that in the bottom right of the screen Warning No file_contexts now i dont know if it has always said that since i flashed this recovery or just started. I also once again tried wiping the cache and dalvik cache because i read it on another post of someone stuck on this screen so i tried that and rebooted it still the same result stuck on bootloader screen. At this point i have no idea what to do. If i have to start over from stock because i messed up unlocking it or completely wipe it again and reflash touchwiz or another rom. I have had nothing but problems since rooting this phone I have gone through atleast 6 to 8 roms because every single one of them gives me a problem somehow. The most common is when i make a call or recieve one and i put the phone up to my ear I know the sensor turns off the screen but when i take it away to end it or do something its completely off or apps force closing all the time still after i did the stock reflash. I am starting to wonder if its just my phone because everyone else i read about has no problems with there phones mine nothing but problems. Please if someone could help me or walk me through this process it would be greatly appreciated I love the things it can do with custom roms but i just wish it would run smooth.
Click to expand...
Click to collapse
You can enter Recovery, right? What happens if you install a .zip? Right now your phone is stuck in the Motorola logo?
it wouldnt even go to the motorola symbol it just stayed in the first screen where it said your bootloader was unlocked. It would go into recovery and i tried to reboot it and it gave me the same screen. So i wiped it completely cache, dalvik cache and system and shut it off. Last night i plugged it into my comp to put it back to stock and it started up like normal and booted into a rom like i just installed one where you have to fill in all that info and setup wifi if you choose too which was weird because it wouldnt do anything before. Anyways i used RSD Lite and put it back to stock and thats where it is now. I am reading the Atrix HD Beginners Guide written by skeevydude right now and I am thinking about trying to root it again with the help of that article and maybe I will have better luck doing it that way hopefully haha maybe I can finally get a rom to run the way everyone else says they run smooth and fast. Any input though to help me would be much appreciated i am definitely new at this and want to learn its something that interests me alot ever since a friend rooted my phone the first time i cant stop playing with it I was trying to make it as fast as I can I had ProBam on there i think its called ive had touchwiz, motoblur, carbon, liquidsmooth, MIUI, and a couple others I cant remember also had a custom kernel i flashed on there and Pure performance so as you can see I have been trying everything.
bpc87 said:
it wouldnt even go to the motorola symbol it just stayed in the first screen where it said your bootloader was unlocked. It would go into recovery and i tried to reboot it and it gave me the same screen. So i wiped it completely cache, dalvik cache and system and shut it off. Last night i plugged it into my comp to put it back to stock and it started up like normal and booted into a rom like i just installed one where you have to fill in all that info and setup wifi if you choose too which was weird because it wouldnt do anything before. Anyways i used RSD Lite and put it back to stock and thats where it is now. I am reading the Atrix HD Beginners Guide written by skeevydude right now and I am thinking about trying to root it again with the help of that article and maybe I will have better luck doing it that way hopefully haha maybe I can finally get a rom to run the way everyone else says they run smooth and fast. Any input though to help me would be much appreciated i am definitely new at this and want to learn its something that interests me alot ever since a friend rooted my phone the first time i cant stop playing with it I was trying to make it as fast as I can I had ProBam on there i think its called ive had touchwiz, motoblur, carbon, liquidsmooth, MIUI, and a couple others I cant remember also had a custom kernel i flashed on there and Pure performance so as you can see I have been trying everything.
Click to expand...
Click to collapse
Good to know that is working now. I would recommend you to take it easy. Don't flash it everyday, use and know a ROM, then you can decice which one is better for you. Be sure to have a backup if something fails, also save a .zip (ROM) in the SD card. Just FYI, I haven't come across a ROM that is 100% smooth (Not even HoloBlur). They are very good, but maybe not the smooth level that you think.
Hey bpc87, I was wondering if you were able to get a custom ROM up & running after all that & if so, how?
I've had the same issue whenever I tried installing a ROM. It would install & boot okay the first time, but when rebooting, it would get stuck at the "bootloader unlocked" warning screen. I went back to stock using Myth Tools & now, after installing a ROM, a reboot leaves me stuck at the "Motorola Dual Core" screen.
Any help from you & the community would be awesome!
bsmitty said:
Hey bpc87, I was wondering if you were able to get a custom ROM up & running after all that & if so, how?
I've had the same issue whenever I tried installing a ROM. It would install & boot okay the first time, but when rebooting, it would get stuck at the "bootloader unlocked" warning screen. I went back to stock using Myth Tools & now, after installing a ROM, a reboot leaves me stuck at the "Motorola Dual Core" screen.
Any help from you & the community would be awesome!
Click to expand...
Click to collapse
dude i havent even tried to since i flashed it back to stock because i dont want the same thing to happen. The last time I just went to turn on bluetooth and it just rebooted on its own. Not too mention the other problems I had I am not going to mess with it again until I read more on how to root it because it is either that or my phone.
Yeah, I understand. Hopefully then some other users who run into the same problem will investigate & figure out what's goin on. I've seen several other threads of people who've encountered the same thing but unfortunately no answer. For me, this is the determining factor as to whether I end up keeping the AHD or not.
Thanks
I have the same problem. Everytime in moto logo after rebooting, but with stock firmware all ok. Is there any solution for this problem?
Gave my old LG Revo to a buddy, things POS, but its all he has at the moment. Anyways, I had a version of Ginger-volt rom on there, and it was acting up, so I was just gonna update everything and put the last version that came out on it, or go with whatever the newest most stable rom is....So I booted into CWM and did a nandroid back up, then wiped everything, cache, dalvik, etc etc, booted up fine, went through some stuff, then i went back to restore the back up i just made cause he forgot to tell me about some game data he wanted backed up.....
So anyways, i restored it, wiped the cache, then rebooted, and yea, then it went into boot loop, at first it was between the LG Logo and the Boot Animation, but now it just suts at the LG Logo for quite awhile, like 10min, and then restarts, and does it over and over. And I try and hold down Power and Vol-Down, but it doesn't work, can't get into recovery. So Need some help here. I've tried all the old tricks I remember from my LG Revo days, but nothing has worked thus far. Is there a way to like boot into something like ODIN and just flash the Stock Firmware. Like RSD-Lite maybe ? Can't remember if that was Moto only....Think it may have been lol
remembered about the exitrecover.zip thing did that, put sdcard back in phone, booted, holding down power and vol-dwn, and it worked, flashed the .zip and then rebooted, now its doing it once again. WTF. I want this thing back to Stock, and then I am gonna root it and flash a new rom. but before that obviously i need to fix this first. Can someone help me at all. I know there isn't a lot of people left on this forum.
BackSeatSuicide said:
Gave my old LG Revo to a buddy, things POS, but its all he has at the moment. Anyways, I had a version of Ginger-volt rom on there, and it was acting up, so I was just gonna update everything and put the last version that came out on it, or go with whatever the newest most stable rom is....So I booted into CWM and did a nandroid back up, then wiped everything, cache, dalvik, etc etc, booted up fine, went through some stuff, then i went back to restore the back up i just made cause he forgot to tell me about some game data he wanted backed up.....
So anyways, i restored it, wiped the cache, then rebooted, and yea, then it went into boot loop, at first it was between the LG Logo and the Boot Animation, but now it just suts at the LG Logo for quite awhile, like 10min, and then restarts, and does it over and over. And I try and hold down Power and Vol-Down, but it doesn't work, can't get into recovery. So Need some help here. I've tried all the old tricks I remember from my LG Revo days, but nothing has worked thus far. Is there a way to like boot into something like ODIN and just flash the Stock Firmware. Like RSD-Lite maybe ? Can't remember if that was Moto only....Think it may have been lol
Click to expand...
Click to collapse
Try the LG restore tool i think its LGPSNT or something like that, but you need a .TOT, and the you can reroot, flash a recovery, and install an updated ROM, gingervolt is OLD
betatest3 said:
Try the LG restore tool i think its LGPSNT or something like that, but you need a .TOT, and the you can reroot, flash a recovery, and install an updated ROM, gingervolt is OLD
Click to expand...
Click to collapse
well i fixed that stuff on my own, couldn't get anyone to respond so I just went based on what I remember, like i said, it's been awhile since i used that phone
BUT NOW ! I got a whole other issue, and its a lot more F'd up, and I have never dealt with this before, so I am just wingin it on what i've tried so far. But i've hit a wall. So after restoring everything and getting Broke-Out rom back on there and everything, I noticed after a lil bit that it had the No Sim-Card icon in the status bar, and couldn't make a call. Then it hit me, and i didnt wnna say it outloud just in case i was wrong, so looked at About Phone>Status, and yep, Completely zero'd out, IMEI/MEID etc etc. I have no idea what to do. I tried following that guide on here but that program DFS or whatever, I entered my IMEI number in this program and hit "Write" and now its in my phone, so i know its communicating with my phone, but that still didnt fix it, I am missing the HEX number, and where it is located on the phone behind the battery, has been complketely rubbed away, so i cant read it. I don't know if Verizon will tell me what the number is, and I didnt wanna call them cause what am I supposed to tell them, not that we care about the warranty on this phone cause its pretty much on its last legs anyways, but i dont wanna cause any problems on my account, cause I know verizon is pretty anti-custom development,
So any ideas on what to do ?
Anyone ? Any suggestion on how to go about fixing this ?
Okay, so.. Excuse me in advance if I'm in the wrong section of the forums, because this is the only Exhibit section I can find.. And also excuse me for the length of this post, as my problem is a bit detailed.
Long story short, I had issues with my texts not being received. I tried wiping the phone and re-rooting (using root-stock found on this website - I can link if need be?).. Anyway, I went so far as to do a factory data wipe, which clearly wasn't a very good idea (I'm a bit new at this root business)..
Anyway, I ended up to the point where I'd reach the Android Setup Wizard, and start to go through it and it would crash.. Upon reboot, the phone would completely freeze at the second "SAMSUNG" logo (the white lettering). After this, I tried using odin to just flash the stock ROM to the phone via the PC, but neither the PC nor odin actually "see" the phone. (I have the drivers, but PC reads the phone as "USB Hub" for some reason) I moved on to other things...
I used bluetooth to put cwm and root-stock back onto the internal memory after removing my external SD card, and flashed cwm no problem. Everything was going well, and it even said it installed the root-stock (I did a data wipe beforehand).. Upon reboot, I now reach "Samsung Galaxy Exhibit 4G" logo, and it continually reboots in a loop. I can still access recovery mode, but I don't want to proceed any further without some outside input, considering I don't fully understand what's going on.
I'm aware that the phone seems to be "soft-bricked," because before I flashed cwm and root-stock, it was "working" in terms of being able to receive calls (and make them, after opening the contacts from inside a call), as well as send and receive texts via the notification bar. But the weirdest thing is, before I went the route of re-flashing the root/cwm, it wouldn't show me a homescreen of any kind, I couldn't use my menu button, and my home button was pointless to touch because it went nowhere. It was just a black screen (not a background, but completely black void) with a statusbar at the top.
Anyway, I'm currently stuck in a boot-loop and I'm very curious if there's any way I can fix this phone without using odin, because the phone isn't recognized by it or a PC, so I'm stuck using the device itself to do things. I'm VERY hopeful that someone takes the time to read this and offer any input they can, because I'm currently without a device and I have no means of getting another phone at the moment.
Thanks in advance for reading this, and for any input that you guys have to offer. Hopefully some day I'm not so noobish at this >.<
Ok, I know you've said you wiped but try this then reboot. In CWM wipe data/cache and under advanced wipe dalvik. Also if you have a working CWM you can flash rooted community ROM or flash to stock found here http://forum.xda-developers.com/showthread.php?t=1686384 scroll down till you see them. But wipe 3x don't know why some people need to but try it.
Note: a working cwm can flash any custom ROM with root pre-installed and you should be fine if you wipe the three I mentioned 3x format system under mounts and storage and format internal sd works wonders too.
Sent from my SGH-T679 using xda app-developers app
---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------
If you need more help feel free to send me a pm
Sent from my SGH-T679 using xda app-developers app
Dvarl said:
Note: a working cwm can flash any custom ROM with root pre-installed and you should be fine if you wipe the three I mentioned 3x format system under mounts and storage and format internal sd works wonders too.
Click to expand...
Click to collapse
If I do a format of system or internal SD, I won't lose the ROM or CWM off of the system storage? If I lose these, I have no way of putting them back on the phone because I was doing it via bluetooth and the phone doesn't boot in order to do that anymore - The same applies to using a different ROM, sadly >.<
Also, I've already wiped the dalvik and cache several times, because that was the only way I could make the phone boot into a mode I could access anything at all on previous to installing the root again. I haven't tried doing this again as of yet, but I will do so and report back.
Just some extra information, because it wouldn't allow me to do so (being new and having to wait):
When I rebooted after the format (to the original stock rom/recovery, and even from recovery) it gave an "invalid argument" for /preload, saying it was unable to be accessed. It also said it couldn't access tmb/csc/system.. I'm unsure what these actually are, but I'm under the impression they may be at the route of my problem. Will formatting repair or otherwise help with these items being unable to be accessed?
Formatting internal will get rid of ROM, but not recovery. You'll be fine if you wipe system and reboot (ed: need to install a rom before reboot).
Try putting your ROM.zip on your external before wiping internal by mounting USB storage and copy ROM to external, then wipe internal and install ROM.
Formatting system (twice) didn't help anything at all - Still gets stuck at Exhibit logo and reboots after about 30 seconds.
Same thing with wiping dalvik/cache, even after 4-5 wipes of each. Should I be rebooting recovery after each of these?
I can't mount usb storage to PC, because PC doesn't recognize the device when I plug it in afterward (or even before mounting). It hasn't recognized the device for quite some time, but it used to act as if it were plug & play when I purchased it, and even well into the time it was rooted. A few months back, I installed the drivers for it (found via Google and ultimately this website), which didn't help it recognize the device. It only recognizes the device when in the "MTP" mode, which allows me to access and transfer data without issues(and I can't do this without being able to access the phone to turn it on ). Otherwise, it says "USB Device Not Recognized - One of the USB devices attached to this computer has malfunctioned and Windows does not recognize it"
I already have the ROM on my PC, but without any means of transfer back to the phone, removing it from internal storage would mean I have no physical way of accessing any ROM in order to restore my phone to working order. I'm at a loss as far as this is concerned, because I have the drivers installed. I'm unsure whether the phone itself is damaged, but I hope this isn't the case and that there's a way to resolve this issue directly.
My biggest concern isn't really the PC not recognizing the device, apart from needing it if I remove the ROM. My main concern is getting the thing to actually boot beyond the logos.. But if I remove the ROM, how will I put it back when it doesn't load to be able to bluetooth anything, and the PC doesn't recognize what it is?
EDIT -
I just realized something... Mounting USB storage doesn't seem to matter as far as moving the ROM, because I can just move them around via the external SD using CWM to flash them - But this is assuming that CWM will remain on the phone after formatting internal SD. Will it stay? If so, I'm going to try rooted community ROM, because the root-stock gives me the impression that it does nothing but apply root. The thread states "otherwise no changes to your phone," which implies (to me) that it doesn't actually include anything the phone needs in order to operate - It only changes certain things to apply root access... Not sure if this is true or not, but it would help explain what the heck is going on.
OH MY GOD! YOU GUYS ARE AMAZING!!
Thank you SO, SO MUCH for helping me. My device is no longer a useless paperweight :good: :good: :good:
I wish I could click the "Thanks" button a thousand times!!
Just incase anyone else has this issue and is able to access notification bar, this is what I did from beginning to end, without all the nonsense between times:
1) Turn Bluetooth on
2) Transfer Clockworkmod via bluetooth to internal SD. ((Tip: Use a separate android device to do this, if PC isn't capable) If already installed skip to step 4)
3) Re-flashed Clockworkmod
4) Place Rooted Community ROM (found here) onto external SD and insert SD into device.
5) Boot device into Custom Recovery (CWM)
6) Wipe cache/dalvik (I did it 4-5 times, just to make sure it was clear)
7) Format system AND rom AND SDCard (internal ONLY - I did all 3 times just to be sure)
8) Flashed Rooted Community ROM from external SD card (it takes some time to install - It will say when completed)
9) Rebooted phone via Custom Recovery - When clicking this, be sure to select NO when it asks to fix the root. I clicked "YES" the first time and it DID NOT FIX THE PHONE. It got stuck in another boot-loop.
10) Initial boot took a bit longer than usual (which is normal), but afterwards, I no longer have a phone that's soft-bricked.
I just wanted to say THANK YOU GUYS VERY, VERY MUCH. You've saved my life by helping me sort through this! Very, very appreciative and I hope both of you have a wonderful day :good: :good:
Good to know. I think you may have lost PNP from a windows update by samsung. To get that back, uninstall those drivers and look for 1.3.2410 or here if interested.
Still the same issue. Device isn't recognized with normal MTP (just plugging into the USB), and it acts as if I haven't even plugged it in at all when trying to use "Mass Storage" from the Network settings in the phone.
I just direct installed the drivers from the exe. Am I doing something wrong?
Try another port, cable, or machine. It worked before, so it could be a driver or something physical.
ed: When you're booted into your rom, can you change storage connection to ums? cwm might be mass storage instead of mtp.
Also, are you able to receive texts now?
I'm able to do everything the device is supposed to do out of the box, aside from access MTP.
I only have the one PC, and all ports have pretty much the same reaction to the device. I don't have access to another cable, because I only have the one that came with the device.
Mounting USB Mass Storage through CWM gives the same result on the PC "Device Not Recognized" etc, etc.
Not even ten days later and I've had to re-flash the ROM. The device kept turning itself off and back on again, so I decided to just remove all the programs I'd installed, thinking something I installed was causing an issue. After doing so, the device kept crashing. Not a reboot of the device or anything of the sort. Literally everything would pop up saying " ----- has stopped responding" and ask to force close. Not really sure what could've caused that, considering I've only installed things that were on Google Play, but it gave me the impression that I had an app that wasn't working correctly with the ROM on the device.
I've brought it back to "vanilla" and I'm not going to bother installing anything at all on it for a while and see if the issue comes up again. Not sure if anyone else has had this problem before or not, but I figured I'd just give my two cents since I made this thread with intentions to figure out what was going on with my phone. If anyone has any insight as to why this may have happened it would be greatly appreciated so I can avoid it happening this time. I'll report back if the issue comes up again, or becomes persistent.
Thanks again for all of your help, and sorry if you've wasted your time reading this.
EDIT -
Device still reboots randomly, but I suspect it's a stuck power button. Is it possible that it just needs cleaning? Sometimes it reboots, sometimes it comes up with the option to power off after touching the power button to activate the touch screen, then upon pressing the back button, it reboots several seconds later as if I were holding the power the entire time.
Stuck in boot-loop help!!!
Carefully followed instructions, and carefully selected 2 .zip files for my t679 http://click.xda-developers.com/api...4G - xda-developers&txt=<b>root-stock.zip</b> and http://forum.xda-developers.com/showpost.php?p=26860509&postcount=4 installed cwm successfully, but after installation of root-stock.zip system reboot now stuck in "boot loop" now what?
- zCHEMDAWGz
Following this in its entirety means you've wiped your phone's system clean. You'll have to use something other than root-stock, because that specifically states that it changes nothing other than granting root access. Everything that was on the phone from the factory is what root-stock uses, apart from giving you root access for things like Superuser, firewalls, etc. In this case, none of the stock items are present.
I used Rooted Community ROM. It's pretty much the same as root-stock, but it has a few goodies (BootyCall, and I think Busy Box) included. There are several other roms you could use, so you're welcome to look around a bit instead of just going with that one, but using that one for now would give you a working phone again until you find another you may like more.
BobScramit said:
Following this in its entirety means you've wiped your phone's system clean. You'll have to use something other than root-stock, because that specifically states that it changes nothing other than granting root access. Everything that was on the phone from the factory is what root-stock uses, apart from giving you root access for things like Superuser, firewalls, etc. In this case, none of the stock items are present.
I used Rooted Community ROM. It's pretty much the same as root-stock, but it has a few goodies (BootyCall, and I think Busy Box) included. There are several other roms you could use, so you're welcome to look around a bit instead of just going with that one, but using that one for now would give you a working phone again until you find another you may like more.
Click to expand...
Click to collapse
good call, community rom resolved this issue... now the only item left is the original problem - wifi/bluetooth "error". most of the easy fixes have already been attempted, aside from determining definitively if hardware issue.
Was the error your reason for rooting? (or re-flashing a rom)?
Are you running the phone completely vanilla now? (no apps, no app updates, even of "stock" applications?) If not, you should try running it that way and testing the wifi and bluetooth prior to updating or installing things.
If it were something you installed that caused a software or hardware issue, it would've most likely been something you installed a day or two beforehand.(When it broke the first time.) If you suspect it was a specific app, stay away from it (or them) in the future.
Considering that you're running a newly flashed rom, it's a little odd that the bluetooth/WiFi unctionality would error, unless it were a hardware issue. The rom you're using shouldn't affect either of those negatively, even if the phone were bricked and you managed to repair it.
BobScramit said:
Was the error your reason for rooting? (or re-flashing a rom)?
Are you running the phone completely vanilla now? (no apps, no app updates, even of "stock" applications?) If not, you should try running it that way and testing the wifi and bluetooth prior to updating or installing things.
If it were something you installed that caused a software or hardware issue, it would've most likely been something you installed a day or two beforehand.(When it broke the first time.) If you suspect it was a specific app, stay away from it (or them) in the future.
Considering that you're running a newly flashed rom, it's a little odd that the bluetooth/WiFi unctionality would error, unless it were a hardware issue. The rom you're using shouldn't affect either of those negatively, even if the phone were bricked and you managed to repair it.
Click to expand...
Click to collapse
The WiFi error existed prior to my ownership. I have never got it to function at all, except for when I was first programming the access point names settings for new mobile network, and fiddling with the other settings in the area, it did show my LAN, allowed me to attempt connection then failed the process early stage. It seemed logical that a new system would alleviate any antagonistic action executed by any previous owner. The only certain detail was it had not been rooted. I have been told loading custom Rom is 2 birds deal, freshness and increased control. Also, based on the behavior of the device and pop-up error messages that indicate software failure makes it seem related to software hiccup. but just a hunch. Been wrong before, really don't want to tear down phone but am open to learning something new. Thanks
- zCHEMDAWGz
I truly have no idea why the software would have any issues that arose directly after installing the new rom.
The only thing I can really suggest is using cwm to wipe everything several times prior to re-flashing the rom again, but I'm guessing you already did that. On the off chance it were hardware related, it probably wouldn't actually give error messages, so I'm gonna retract that from this entirely as it's very unlikely.
If you haven't, wipe your internal memory, system, cache/dalvik. Just in case, be sure you remove your external SD so you can keep the rom on it. Also, while you're at it, remove everything else except the rom from the external SD in case something on it is causing the issue, then try to re-flash the rom.
BobScramit said:
I truly have no idea why the software would have any issues that arose directly after installing the new rom.
The only thing I can really suggest is using cwm to wipe everything several times prior to re-flashing the rom again, but I'm guessing you already did that. On the off chance it were hardware related, it probably wouldn't actually give error messages, so I'm gonna retract that from this entirely as it's very unlikely.
If you haven't, wipe your internal memory, system, cache/dalvik. Just in case, be sure you remove your external SD so you can keep the rom on it. Also, while you're at it, remove everything else except the rom from the external SD in case something on it is causing the issue, then try to re-flash the rom.
Click to expand...
Click to collapse
Followed instructions, still having same issue... also the problem was there before I flashed New rom. I'm stumped...
Well, it being there before flashing the rom is a start, but that doesn't really explain why the new rom wouldn't have fixed whatever the issue was. I'm assuming (because I honestly don't know) that bluetooth and wifi are both controlled through the same hardware, with different softwares running them on the device. If both of them are messed up and refuse to work even after a re-flash, chances are it's just dead.
Have you actually formatted system, cache, etc after wiping, prior to a new flash? I had to format mine several different times in order to stop the boot loops and crashing. It could be something that's stuck in the system, cache, etc that didn't go away with a simple wipe. Other than that, it very well could be a hardware issue.
If it is a latent issue maybe doing full wipes through adb is the next step. I remember reading some people had some issues with doing wipes through cwm. It might be worth a try at the very least.
Sent from my SGH-T679 using XDA Free mobile app
ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
raynefr said:
ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Click to expand...
Click to collapse
Do you still have the memory issue? If so, try running a RUU, and see if that fixes your problem.
If not, just use adb sideload to sideload a ROM. Then wipe everything except internal storage and install the ROM normally.
EDIT: Looks like @BD619 ninja'd me XD
BTW sideload very rarely works when you wipe your sdcard.
BD619 said:
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
Click to expand...
Click to collapse
hey thanks for the reply. i followed the guide and after some effort, everything seemed good, but when i was trying to load 5.03 sense 6 rom, i got to the htc start up, then it defaulted back to the bootloader..i went with the deodex version of the download, should i try the odex? or a different version all together?
and now it doesnt want to boot into recovery mode either! going to try redoing the steps, but i just cant figure out what the problem is
**edit* i cant fix twrp. the title loads, but thats it. endless loop
ok i got it to seemingly work. restoring content now. sat in fron of my pc for 15 hours...not even sure where imat or if i got any closer to rooting..smh..thank you everyone who helped. if anyone comes across this
to get out of the endless cycle of recover/loading screen.. delete your twrp, or whatevs your using. even if you have the latest, just redownload it. worked for me. i guess there is a huge difference between the odex and the deodex.i had figured deodex was a more refined version, but maybe it had more complicated software. in any case, if you are at a point where you dont have a base os, and you make it this far, go with odex, it worked for me. htc is big on back up, so i was more worried about having to scrap my phone then i was regaining data, especially with most of my stuff backed up to google drive. hopefully you guys are careful.
now...about this backup issue i had in the first place. how can i fix the storage issue? i have a 32 gb phone minus partition leaves me with over 24gb..why is it going based off the separate phonememory slot? why cant i change it?