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
Related
I've been searching, and reading, and my eyes hurt. I normally don't like to post threads, but I'm left with no choice. If this topic has been covered, then I guess my searchin' skillz are stating to lack. Here is my delimna:
Rooted, Lagfix, enabled Side-loading, recently installed ClockworkMod, stock firmware. I ran a backup using ROM Manager/ClockworkMod. I was attempting to install the Mobile AP fix for WiFi Hotspotting from designgears. I downloaded the new kernel per instructions (Mobile AP ony). I first tried installing it using ROM Manager's boot option into Clockwork without renaming MobileAP.zip. Still received black screen when I open the Mobile AP settings that the new kernel was trying to fix. So I thought that the flash didn't work, so this time I renamed the kernel file to update.zip and did the standard method of flash using stock recovery mode.
Now the phone boots to the Galaxy S screen, then just a black screen. The bottom row buttons seem to be active, but nothing happens. Holding power....nothing. I have to pull the battery; however, I can boot into stock recovery.
Now here's the delimna. I can boot into recovery, but the update.zip file is NOT the one for ClockworkMod, its the modified kernel. Is there a way that I can browse the files on the phone so I can change the update.zip file? I want to put Clockwork's in place so I can restore using my backup made yesterday....It's not a huge order if I have to flashback to stock and lose everything as I usually do that everynow and again anyways (usually I'm prepared). I won't lose anything important that isn't already backed up except maybe some pictures....
BUT, I can't help but try. It's just me I like to break stuff and fix 'em. I want to try to run that backup I made. I have Odin, and I tried flashing the kernel back to stock (i had one hell of a time finding information on how to use it). As a matter of fact, I found instructions on HOW to use it, but I gave up trying to find useful information on how the program runs (like a user guide, what else can it do, that sort of thing....). I spent hours reading thread after thread........information overload I guess.
I figured someone might point me in the right direction. How can I browse/edit the contents of the phone while in Recovery or Download mode?
You could try letting the phone boot up, yes I know it's only a black screen, then plug in the usb to your PC and see if ADB works.
If so then just adb shell into it and work with command line.
I'm not sure if ADB would work in stock recovery mode but that's worth a shot too.
Excellent idea, but no luck. I can get the computer to recognize the phone in recovery mode, but ADB shows the device offline, and Windows Explorer shows 2 drives with the whole "insert disk into drive ..." message. Can't boot phone to enable "development mode", that might have something to do with it......unless I'm missing something?
swedishcancerboi said:
Excellent idea, but no luck. I can get the computer to recognize the phone in recovery mode, but ADB shows the device offline, and Windows Explorer shows 2 drives with the whole "insert disk into drive ..." message. Can't boot phone to enable "development mode", that might have something to do with it......unless I'm missing something?
Click to expand...
Click to collapse
Wasn't sure if that would work or not.
So, if you turn it on and just let it sit as long as a normal boot, then try adb does anything work?
I actually let it sit for ~15 minutes. computer doesn't even register the usb being plugged in. I'm going to give it another go or two, but in about an hour I'm going to have to call it quits and just flash it with Odin. Don't want to give up yet, but I am driving out of town later this afternoon and must have my phone for the trip. Maybe I'll break it again tomorrow and play with it over the weekend!
Let me know if you have any other ideas. I'll let you know when I give up.
While on that subject (watch someone tell me to move my post after this.....), maybe I'll experiment with a new ROM. Any recommendations? (without OC, device is fast enough). I haven't read much on the different flavors available at the moment (I think I read something about a 2.2 from I9000 or something?).
swedishcancerboi said:
While on that subject (watch someone tell me to move my post after this.....), maybe I'll experiment with a new ROM. Any recommendations? (without OC, device is fast enough). I haven't read much on the different flavors available at the moment (I think I read something about a 2.2 from I9000 or something?).
Click to expand...
Click to collapse
Hybrid from eugene is pretty fast especially if you add the voodoo kernel to it. Thats what I heard tho. Because when i tried it out it was pretty quick with out a lagfix and without autokiller. Only used it for 20 min tho as i couldn't get Titanium backup to work. I think the titanium problem is a hit or a miss.
well, I guess I'm going to have to load stock and wipe everything...oh well. Let's see how this goes. Then I'll start playing with ROMs this weekend. Thanks anyway!
swedishcancerboi said:
well, I guess I'm going to have to load stock and wipe everything...oh well. Let's see how this goes. Then I'll start playing with ROMs this weekend. Thanks anyway!
Click to expand...
Click to collapse
Well, if your going to do that take an extra 2 minutes and load Eugenes Hybrid R3 while your at it. It's extremely easy to do and in my opinion the fastest thing we can put on these phones right now.
Vibrant ROM? is that safe? I mean, I know they are all Galaxy S, but is the hardware really that identical?
I don't think eugenes captivate hybrid is actually a vibrant rom. I think he just borrowed some of the better parts.
Sent from my SAMSUNG-SGH-I897 using XDA App
Got it! I used the one click stock down loader to get the phone to boot. I then noticed that many of my files were still there, music, zips.....so I thought....maybe my backup is still there.
Instead of using my original root, I decided to try Unleash the Beast.applied it so I could load Rom Manager.i opened Rom manager and it showed my backup!
I tried restoring then without success (no update.zip) and had to flash clockwork (even though it showed it already loaded, guess it needed to be refreshed, makes sense since it is a fresh firmware), selected my restore and it ran like a charm.
I am just surprised. I thought the act of flashing the Rom would wipe everything. Apparently not if you never do the "master clear."
Thankfully I had just installed Rom Manager the day before and had a fresh backup. Looks liked I'm gonna have to start shelling out more beer money to the devs!
Now I can prepare to break it again and again. Let the fun begin!
Sent from my SAMSUNG-SGH-I897 using XDA App
Nice. Yeah, stuff you have stored on your "internal SD" is safe between flashes. Of course apps, contacts, etc get wiped, but that's an easy fix.
"the more you know," eh? Ha!
Sent from my SAMSUNG-SGH-I897 using XDA App
Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"
Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.
My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.
Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App
Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.
Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.
Okay, so I'm new to everything Android in general, so all of this is very confusing to me, so I'm going to be as specific and in-depth as possible.
I'm using an HTC Vivid on AT&T and I just recently flashed CM 11, and I absolutely LOVE it, except for two problems.
The first has been widely acknowledged, and it's the problems with MMS. On the stock ROM, MMS was sometimes a problem, but that was usually because the Vivid had mobile data problems in general (problems which I still have not encountered on CM 11, which is good news). It happened that when the Vivid couldn't send or receive MMS, it also couldn't use the mobile data at all, and this was usually fixed by a reboot (which was a pain because ICS had that bug where it would always "optimize apps" every reboot). This was the problem I first suspected, except I tested the use of mobile data in other apps, and they worked perfectly, leading me to believe that this is not the same problem. Data usage works fine, it's a specifically MMS problem.
The second issue is something that I haven't seen addressed yet, so I guess it's a problem that only I have come across. I can't use the camera at all, because every time I try to open it, it says I need to insert an SD card. Now I know nothing about technology, so is it referring to the internal SD card, or the external? I have an external SD card for the phone, and it works with the Apollo music app and such, so I'm not sure if that's where it's supposed to be going. I can't even take pictures or record videos, because it won't let me, since I don't have an SD card apparently. Is there any way to fix this?
Thanks everyone for any help or advice you can offer.
EDIT: I'm guessing the camera problem is an internal storage thing, because my phone registers no internal storage at all. Nor does TWRP, it doesn't register an internal storage either. I'm still at a loss at how to fix this problem.
Did you flash the most recent nightly, or the most recent stable? Probably a useless question, as the latest stable should be fine as far as the internal storage and everything (and I'm on the 1-28 nightly, which is not giving me any internal storage problems). I recommend flashing back to stock and seeing if the problem persists, because if so, then your problem is most likely not the CM11 rom. If the stock rom does not have any problems with your internal storage, then flash to the latest nightly of albinoman's CM11 and see if that does the trick.
Just to be extra careful, you are wiping the "data", "cache", and "dalvik-cache" using TWRP, then rebooting to the bootloader and flashing the boot.img from the zip file through fastboot, then flashing the zip file using TWRP, right? The order of wiping and flashing the boot.img can be switched, but they must be done before flashing the rom to try to prevent weird errors happening. Not trying to sound condescending, I just want to eliminate all possible causes.
teveisboss said:
Okay, so I'm new to everything Android in general, so all of this is very confusing to me, so I'm going to be as specific and in-depth as possible.
I'm using an HTC Vivid on AT&T and I just recently flashed CM 11, and I absolutely LOVE it, except for two problems.
The first has been widely acknowledged, and it's the problems with MMS. On the stock ROM, MMS was sometimes a problem, but that was usually because the Vivid had mobile data problems in general (problems which I still have not encountered on CM 11, which is good news). It happened that when the Vivid couldn't send or receive MMS, it also couldn't use the mobile data at all, and this was usually fixed by a reboot (which was a pain because ICS had that bug where it would always "optimize apps" every reboot). This was the problem I first suspected, except I tested the use of mobile data in other apps, and they worked perfectly, leading me to believe that this is not the same problem. Data usage works fine, it's a specifically MMS problem.
The second issue is something that I haven't seen addressed yet, so I guess it's a problem that only I have come across. I can't use the camera at all, because every time I try to open it, it says I need to insert an SD card. Now I know nothing about technology, so is it referring to the internal SD card, or the external? I have an external SD card for the phone, and it works with the Apollo music app and such, so I'm not sure if that's where it's supposed to be going. I can't even take pictures or record videos, because it won't let me, since I don't have an SD card apparently. Is there any way to fix this?
Thanks everyone for any help or advice you can offer.
EDIT: I'm guessing the camera problem is an internal storage thing, because my phone registers no internal storage at all. Nor does TWRP, it doesn't register an internal storage either. I'm still at a loss at how to fix this problem.
Click to expand...
Click to collapse
teveisboss said:
Okay, so I'm new to everything Android in general, so all of this is very confusing to me, so I'm going to be as specific and in-depth as possible.
I'm using an HTC Vivid on AT&T and I just recently flashed CM 11, and I absolutely LOVE it, except for two problems.
The first has been widely acknowledged, and it's the problems with MMS. On the stock ROM, MMS was sometimes a problem, but that was usually because the Vivid had mobile data problems in general (problems which I still have not encountered on CM 11, which is good news). It happened that when the Vivid couldn't send or receive MMS, it also couldn't use the mobile data at all, and this was usually fixed by a reboot (which was a pain because ICS had that bug where it would always "optimize apps" every reboot). This was the problem I first suspected, except I tested the use of mobile data in other apps, and they worked perfectly, leading me to believe that this is not the same problem. Data usage works fine, it's a specifically MMS problem.
The second issue is something that I haven't seen addressed yet, so I guess it's a problem that only I have come across. I can't use the camera at all, because every time I try to open it, it says I need to insert an SD card. Now I know nothing about technology, so is it referring to the internal SD card, or the external? I have an external SD card for the phone, and it works with the Apollo music app and such, so I'm not sure if that's where it's supposed to be going. I can't even take pictures or record videos, because it won't let me, since I don't have an SD card apparently. Is there any way to fix this?
Thanks everyone for any help or advice you can offer.
EDIT: I'm guessing the camera problem is an internal storage thing, because my phone registers no internal storage at all. Nor does TWRP, it doesn't register an internal storage either. I'm still at a loss at how to fix this problem.
Click to expand...
Click to collapse
Otay...
Try this...
Boot to TWRP
Go to mounts...
Mount USB storage...
Plug phone into computer...
See if windows offers to format your internal...
If yes... Reboot to OS... Problem solved...
DO NOT FACTORY RESET FROM HBOOT
Sent from my Vivid 4G using Tapatalk
projectisaac said:
Did you flash the most recent nightly, or the most recent stable? Probably a useless question, as the latest stable should be fine as far as the internal storage and everything (and I'm on the 1-28 nightly, which is not giving me any internal storage problems). I recommend flashing back to stock and seeing if the problem persists, because if so, then your problem is most likely not the CM11 rom. If the stock rom does not have any problems with your internal storage, then flash to the latest nightly of albinoman's CM11 and see if that does the trick.
Just to be extra careful, you are wiping the "data", "cache", and "dalvik-cache" using TWRP, then rebooting to the bootloader and flashing the boot.img from the zip file through fastboot, then flashing the zip file using TWRP, right? The order of wiping and flashing the boot.img can be switched, but they must be done before flashing the rom to try to prevent weird errors happening. Not trying to sound condescending, I just want to eliminate all possible causes.
Click to expand...
Click to collapse
rignfool said:
Otay...
Try this...
Boot to TWRP
Go to mounts...
Mount USB storage...
Plug phone into computer...
See if windows offers to format your internal...
If yes... Reboot to OS... Problem solved...
DO NOT FACTORY RESET FROM HBOOT
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
Hi guys,
Thanks for the replies, and sorry I'm so late, I had a few things to take care of over the weekend.
Anyway, good news, I solved the problem with internal storage by wiping the internal storage from within TWRP (didn't really know what I was doing, which is probably a bad thing, but it worked so I'm happy). Now the camera app works cleanly and everything.
The MMS problem continues to stump me, however. I've tried different APNs, different solutions that everyone has recommended, no luck. I will continue to search for a way to solve the problem
Thanks again.
projectisaac said:
The order of wiping and flashing the boot.img can be switched, but they must be done before flashing the rom to try to prevent weird errors happening. Not trying to sound condescending, I just want to eliminate all possible causes.
Click to expand...
Click to collapse
Actually, one more question. Was I really supposed to flash the boot.img first? Everything I read said to do it the other way around.... What kind of problems would that have caused? Maybe that's where I made an error, I flashed the rom first and then the boot.img afterwards.
teveisboss said:
Actually, one more question. Was I really supposed to flash the boot.img first? Everything I read said to do it the other way around.... What kind of problems would that have caused? Maybe that's where I made an error, I flashed the rom first and then the boot.img afterwards.
Click to expand...
Click to collapse
Y'know, looking at it again it probably doesn't matter, given the differing instructions here (http://forum.xda-developers.com/showthread.php?t=2423277) and here (http://forum.xda-developers.com/showthread.php?t=2524934). The main reason they would have you flash the boot.img first is because it may not let you boot into the rom, but as long as you go from flashing the rom to flashing the boot.img without booting up the rom, it should be fine.
projectisaac said:
Y'know, looking at it again it probably doesn't matter, given the differing instructions here (http://forum.xda-developers.com/showthread.php?t=2423277) and here (http://forum.xda-developers.com/showthread.php?t=2524934). The main reason they would have you flash the boot.img first is because it may not let you boot into the rom, but as long as you go from flashing the rom to flashing the boot.img without booting up the rom, it should be fine.
Click to expand...
Click to collapse
Ah, okay. Thanks for the help regardless.
Hi,
Since the kitkat update I get exchange errors all the time, and the nexus is slow as shi...
Factory Reset didn't solve the problem.
Any Help?
Version: 4.4.2
No one with this problems?
Di0g0 said:
No one with this problems?
Click to expand...
Click to collapse
You could try reverting back to 4.3 then update to 4.4.2 by installing a custom rom.
Hum,
But this problems are normal on the oficial 4.4.2?
Di0g0 said:
Hum,
But this problems are normal on the oficial 4.4.2?
Click to expand...
Click to collapse
Nope they are not
---------- Post added at 11:34 AM ---------- Previous post was at 11:26 AM ----------
By any chance your extreme lag also affects the audio performances? I and a friend of mine had in the same period (for 2 weeks) EXTREME lag, signal lost on mobile network. The lag was so powerful that even music was interrupted. The only way to get rid of this was rebooting the tablet.
The most awkward part is that the bug persisted over ANY KIND OF ROM/KERNEL. Even the official one from Google Developers (any android version).
Best part: It was fixed by itself. Lags started to be increasingly rare and at some point they stopped.
I tried to catch some logs...at the moment of failure, just once they pointed me to some lines in the source code...so I quit trying to figure it out what happens..
I had the same problem, I solved it installing SlimKat, but probably you can solve it with any custom rom, I tried many times to restore 4.4.2 but always the same, only installing custom roms seem to solve it...
I remember it, is like a nightmare to me, turn the tablet On and let it 5 minutes before open any app, open Google Play and see how it lags, installing apps always causing freezing... It remembers me my Windows XP years...
At the beginning i let it thinking it will solve itself, haha, after months I was about to broke it with a stone
Kilek_360 said:
I had the same problem, I solved it installing SlimKat, but probably you can solve it with any custom rom, I tried many times to restore 4.4.2 but always the same, only installing custom roms seem to solve it...
I remember it, is like a nightmare to me, turn the tablet On and let it 5 minutes before open any app, open Google Play and see how it lags, installing apps always causing freezing... It remembers me my Windows XP years...
At the beginning i let it thinking it will solve itself, haha, after months I was about to broke it with a stone
Click to expand...
Click to collapse
Ya it's my situation now...
al3x1393 said:
Nope they are not
---------- Post added at 11:34 AM ---------- Previous post was at 11:26 AM ----------
By any chance your extreme lag also affects the audio performances? I and a friend of mine had in the same period (for 2 weeks) EXTREME lag, signal lost on mobile network. The lag was so powerful that even music was interrupted. The only way to get rid of this was rebooting the tablet.
The most awkward part is that the bug persisted over ANY KIND OF ROM/KERNEL. Even the official one from Google Developers (any android version).
Best part: It was fixed by itself. Lags started to be increasingly rare and at some point they stopped.
I tried to catch some logs...at the moment of failure, just once they pointed me to some lines in the source code...so I quit trying to figure it out what happens..
Click to expand...
Click to collapse
Ya the tablet is extremely slow, and freezes sometimes for some seconds!
What do you mean with "rebooting the tablet"? Factory Reset on the original recovery menu?
Thanks.
Di0g0 said:
Ya it's my situation now...
Ya the tablet is extremely slow, and freezes sometimes for some seconds!
What do you mean with "rebooting the tablet"? Factory Reset on the original recovery menu?
Thanks.
Click to expand...
Click to collapse
If you want to keep the official rom you can just try to reflash 4.4.2 wiping everything, just copy to PC the files you want to keep and after flashing copy again to tablet, i would recommend you to copy only important data, not everything, and specially not copy the folders with strange names that you dont know what they are
Kilek_360 said:
If you want to keep the official rom you can just try to reflash 4.4.2 wiping everything, just copy to PC the files you want to keep and after flashing copy again to tablet, i would recommend you to copy only important data, not everything, and specially not copy the folders with strange names that you dont know what they are
Click to expand...
Click to collapse
How to reflash the 4.4.2?
It's necessary root?
Di0g0 said:
How to reflash the 4.4.2?
It's necessary root?
Click to expand...
Click to collapse
Before flashing anything try to restore the tablet, copy all your stuff to PC and format it by going to settings / backup and reset / factory data reset and checking to wipe all on internal memory/sdcard
It will wipe all your data, apps and everything, so be sure that you dont forget anything to be copied to pc.
Maybe it solve the problem without flashing
About root and flashing:
You dont need it, but you can root it if you want after flashing,
I dont know how much you know about flashing and all that, so Im gonna make you an quickly tutorial
Basically all you need is:
Nexus root toolkit from here: www.wugfresh.com/nrt/
4.4.2 firmware (can be downloaded directly from the Nexus Root Toolkit)
And be sure that you have copied to PC everything you dont want to be deleted, you can just copy all to PC and after flashing copy to tablet only what you want...
On tablet turn on USB debugging, on developer options (To unlock it go to settings /about tablet /build number and click it many times until it says "you are now a developer", then go back and you will see it)
When its done follow the Nexus Root Toolkit instructions to "flash stock + unroot" (by clicking a button with that text) you should select Android 4.4.2 (KOT49H) and check the option "automatically download"(dont remember what the option says exactly)
And the tool will download it and tell you when you have to do something. Just dont disconnect the tablet until the tool ends its job
Maybe you should install some drivers if you get an error message like "device not found"
If you want to know more about insalling drivers, you get any problem or something else just tell me, but maybe im gonna make you wait because tomorrow is my birthday and I wont be checking it for few hours.
Kilek_360 said:
Before flashing anything try to restore the tablet, copy all your stuff to PC and format it by going to settings / backup and reset / factory data reset and checking to wipe all on internal memory/sdcard
It will wipe all your data, apps and everything, so be sure that you dont forget anything to be copied to pc.
Maybe it solve the problem without flashing
About root and flashing:
You dont need it, but you can root it if you want after flashing,
I dont know how much you know about flashing and all that, so Im gonna make you an quickly tutorial
Basically all you need is:
Nexus root toolkit from here: www.wugfresh.com/nrt/
4.4.2 firmware (can be downloaded directly from the Nexus Root Toolkit)
And be sure that you have copied to PC everything you dont want to be deleted, you can just copy all to PC and after flashing copy to tablet only what you want...
On tablet turn on USB debugging, on developer options (To unlock it go to settings /about tablet /build number and click it many times until it says "you are now a developer", then go back and you will see it)
When its done follow the Nexus Root Toolkit instructions to "flash stock + unroot" (by clicking a button with that text) you should select Android 4.4.2 (KOT49H) and check the option "automatically download"(dont remember what the option says exactly)
And the tool will download it and tell you when you have to do something. Just dont disconnect the tablet until the tool ends its job
Maybe you should install some drivers if you get an error message like "device not found"
If you want to know more about insalling drivers, you get any problem or something else just tell me, but maybe im gonna make you wait because tomorrow is my birthday and I wont be checking it for few hours.
Click to expand...
Click to collapse
I tried to restore the tablet and that didn't worked (look at the first post).
I will try the 2º option, thank you !!
Di0g0 said:
Ya the tablet is extremely slow, and freezes sometimes for some seconds!
What do you mean with "rebooting the tablet"? Factory Reset on the original recovery menu?
Thanks.
Click to expand...
Click to collapse
No...just a simple restart. As I stated, I tried different resets and flashes and everything and nothing worked...
Di0g0 said:
I tried to restore the tablet and that didn't worked (look at the first post).
I will try the 2º option, thank you !!
Click to expand...
Click to collapse
Be careful about "Returning to stock" method as I think Google broke their "flash-all.bat" from the arcvive of Android 4.4. Flash every file by your hand. I used that idiotic flash-all on any android version, but on 4.4 it completely broke my motherboard by flashing wrong boot.img.
[QUOTW=Di0g0]I tried to restore the tablet and that didn't worked (look at the first post).
I will try the 2º option, thank you !![/QUOTE]
Okay, I was no sure that you also format "SD card" factory reset do not delete user data/sd card on some devices and Im not sure if in N7 you have to check the option
Try the 2° option but take a look at this comment:
al3x1393 said:
No...just a simple restart. As I stated, I tried different resets and flashes and everything and nothing worked...
Be careful about "Returning to stock" method as I think Google broke their "flash-all.bat" from the arcvive of Android 4.4. Flash every file by your hand. I used that idiotic flash-all on any android version, but on 4.4 it completely broke my motherboard by flashing wrong boot.img.
Click to expand...
Click to collapse
If thats true then try to flash 4.3 and install 4.4.2 by OTA, just select 4.3 instead 4.4.2 when you are about to flashing
Ok,
I flashed the nexus 7 2012 directly to the factory 4.4.2 using the nexus root toolkit, and everything is working fine without problems, at least for now.
The tablet isn't giving exchange errors, and doesn't hang everytime, but I only used it for some minutes, lets see how it works after some days/intensive usage.
Anyway, as I said, I flashed to 4.4.2 directly using the toolkit, and it worked without any problem
Thank You!
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?