Related
I picked up a Streak 7 Wi-Fi Only yesterday. I was playing around with it and tried out the honeycomb ROm posted here. Decided I wanted to go back to stock but my Nandroid backup is gone (I think it was on sdcard1 and not sdcard2). I managed to restore a stock image I found here someplace but it is the t-mo image and wifi does not seem to work. Anyone know where I can get the wifi-only stock image?
Wrong section
Sent from my LG-P999 using XDA Premium App
ledname said:
I picked up a Streak 7 Wi-Fi Only yesterday. I was playing around with it and tried out the honeycomb ROm posted here. Decided I wanted to go back to stock but my Nandroid backup is gone (I think it was on sdcard1 and not sdcard2). I managed to restore a stock image I found here someplace but it is the t-mo image and wifi does not seem to work. Anyone know where I can get the wifi-only stock image?
Click to expand...
Click to collapse
I have the nvflash files, and if necessary the images, you need. I'll get them up somewhere and post a link for you in a bit later today.
Edit:
Here are the files you need:
http://www.multiupload.com/OM0VO9HBO9
Just download these and use the same instructions here:
http://forum.xda-developers.com/showthread.php?t=1018809
Can the original poster please confirm if this worked? I bought a Dell Streak 7 Wifi yesterday and would like to know.
andyo70 said:
Can the original poster please confirm if this worked? I bought a Dell Streak 7 Wifi yesterday and would like to know.
Click to expand...
Click to collapse
I can confirm this works!! Thanks so much op. I used this to get back from dj_steves honeycomb b3, and i did have to take a couple of extra steps. Once everything completed I was stuck at the dell logo. So I booted into recovery, to see what i could do, which was almost nothing other than clear cache etc. The internal sdcard would not mount so I couldn't put steves streakdroid 1.3 on it to try and see if it would flash. At a brick wall, I decided what the heck and I flashed the original recovery through fastboot. I rebooted into recovery and preformed a factory reset and and to my amazement was greeted with the lock screen a short while later. However, I had a notification stating that my sdcard was unformated or not the right system type. (certain on unformated cant remember the second suggestion, but i believe thats close). I went to settings>sdcard & tablet storage and pressed "format internal tablet storage", then mounted the internal tablet storage. And thats it. Back on stock 2.2.2 (wifi-only). Mega thanks op.
Thank you for confirming. Now I can try out the Honeystreak!
worked
this worked perfect for me.
i might add
i might add, that i had flashed the honeystreak in the dev section and my 7 would lock up, go to sleep (or in my case, lapse into a coma) and boot when it wanted to. had to reset with pin in the hole all the time. did this for about 3 days and said heck with it. seems to be some power issue with that flash. thanks to solidsnake66 for uploading these files. now my 7 seems to be normal again.
ok, this will help me. When I used the t-mobile backup, the partitions were different, because of the t-mobile files...I only had (I think) 11 or so GB of free memory. If I remember right, I had 12 something before. Is the .bat in this re-written to give me the 12gb, rather than the 11gb? Even if it is the WiFi files, I would like the same amount of memory I had before.
EDIT: Nevermind, I think I'm wrong, and they both use the same partitions.
Clockwordmod
Hey guys. So I used this howto to revert my dell streak 7 running on honeystreak hd7 back to android 2.2.2. Once i rebooted into the system i noticed that although in stock android, it was still rooted. While I know how to unroot, i can't get rid of clockwordmod recovery. How do i do that? I tried to uninstall the clockwordmod, but it doesn't show up under my apps. i am at my wits end. I want to send in my dell streak 7 to dell for repair, but i want it in "fresh" condition with no root or clockwordmod recovery. Any advice will be greatly appreciated. Thanks.
Files now working for me
On my fourth attempt the files worked great.
solidsnake66 said:
I have the nvflash files, and if necessary the images, you need. I'll get them up somewhere and post a link for you in a bit later today.
Edit:
Here are the files you need:
http://www.multiupload.com/OM0VO9HBO9
Just download these and use the same instructions here:
http://forum.xda-developers.com/showthread.php?t=1018809
Click to expand...
Click to collapse
Do you have the stock "system" image for use with fastboot? for a wifi only streak? I can only find the tmobile one.
What I did was to an out of the box wifi only streak 7,
1. rooted with gingerbreak 1.2, renamed a couple .apks which were supposed to eliminate the cell standby battery drain.
2. restored the device to remove my google account (this device is for a friend and owned by her!!) It was stupid and I should have used her google creds first but she was not around. I didnt think it would hurt. The device was stuck at the android click to start screen and nothing I did could get it any further.
3. used fastboot to restore the system_orig.img posted by someone else, this fixed my issues, but it was a tmobile image so I am looking for the same thing system.img but in a wifi only flavor. THought you may have it.
Thanks much.
The links he gave are for Wifi version only. First download the first link then you have to get nvflash, unzip it onto your computer then unzip the files from the first link into the folder. He is advising you that you need to follow the directions on the 2nd link.
Berryblue said:
The links he gave are for Wifi version only. First download the first link then you have to get nvflash, unzip it onto your computer then unzip the files from the first link into the folder. He is advising you that you need to follow the directions on the 2nd link.
Click to expand...
Click to collapse
Actually, postb8822 is saying that the files in those downloads are ClockWorkMod Recovery and Rooted, not stock. The Root can be removed via Gingerbreak (I've done it, once...) but the CWR recovery images are all that I find in the files provided.
Berryblue, you said that you have a backup on an SD, right? Would you please place the recovery.img and boot.img (and system.img separate from those two perhaps) at some dropbox somewhere?
Thanks.
solidsnake66 said:
I have the nvflash files, and if necessary the images, you need. I'll get them up somewhere and post a link for you in a bit later today.
Click to expand...
Click to collapse
Downloaded all these files and then followed the directions in the other thread. Ended up stuck on dell logo. Then found this posting:
metal1f3 said:
I can confirm this works!! Thanks so much op. I used this to get back from dj_steves honeycomb b3, and i did have to take a couple of extra steps. Once everything completed I was stuck at the dell logo. So I booted into recovery, to see what i could do, which was almost nothing other than clear cache etc. The internal sdcard would not mount so I couldn't put steves streakdroid 1.3 on it to try and see if it would flash. At a brick wall, I decided what the heck and I flashed the original recovery through fastboot. I rebooted into recovery and preformed a factory reset and and to my amazement was greeted with the lock screen a short while later. However, I had a notification stating that my sdcard was unformated or not the right system type. (certain on unformated cant remember the second suggestion, but i believe thats close). I went to settings>sdcard & tablet storage and pressed "format internal tablet storage", then mounted the internal tablet storage. And thats it. Back on stock 2.2.2 (wifi-only). Mega thanks op.
Click to expand...
Click to collapse
This person's problem and fix seem to be exactly what I need to do. But what I don't understand is the "flashed to original recovery through fastboot" part. I can run fastboot and it sees my Streak but I don't know where I would find the recovery mentioned in the quote. Right now when I try to go to the recovery menu I see what seems to be the normal streak recovery menu but when I choose either factory reset I get to some other dialog I never saw before. I take it that this is some new recovery thing which is why I should be restoring the "original recovery" as mentioned in the quote.
To follow-up on my own posting: After staring at my bricked streak awhile, I decided that the poster must have meant the restore_orig file from the other thread. So I went back and reran the sequence. First the restore of all those img files then the fast boot recovery of the original restore img file. Boot with volume + to get to restore screen. Reset and reboot. Exactly what I'd done before but this time it worked. Perhaps the fact that the drivers were already installed helped since the sequence of operations wasn't interrupted by those driver installs. Perhaps I was more careful the second time. Regardless, it worked. I'm back and running. Even have root now; saving me from downloading gingerbreak. I'd assume if someone was doing this to return their Streak that they'd want to run gingerbreak to remove root. One additional caveat here: Once booted to the main Dell window (can't remember name of the Dell launcher) I had to reformat the internal disc. Not a big deal for me since I didn't expect any of my user data to survive. But just a warning for others.
solidsnake66 said:
I have the nvflash files, and if necessary the images, you need. I'll get them up somewhere and post a link for you in a bit later today.
Edit:
Here are the files you need:
http://www.multiupload.com/OM0VO9HBO9
Just download these and use the same instructions here:
http://forum.xda-developers.com/showthread.php?t=1018809
Click to expand...
Click to collapse
I(we) can really use the stock img files needed to flash to stock. I hope someone posts it.
ClockworkMod Recovery loop and error:-1 during solution
Sorry, I posted on the wrong section, Thanks Chemus!
The img files that mssahota1986 referenced are the t-mobile (3g/4g) images rather than the Wifi images.
However following the reposted instructions in your post shows that the t-mobile boot and recovery images can remove the CWM, which I thought was incorrect. Combined with the altered and rooted system images previously provided, I might be able to get close to stock on my wifi, since GingerBreak 1.2 was previously able to remove root from the Wifi.
If Dell ever actually upgrades to HC, I'll try the OTA updates...maybe I'll get lucky.
Still hoping for a drop of the actual WiFi stock images (apparently the System.img is necessary)
Update: No luck on combining different file versions for me. It seemed to work, but the WiFi would not turn on.
Chemus said:
Still hoping for a drop of the actual WiFi stock images (apparently the System.img is necessary)
Click to expand...
Click to collapse
My buddy just ordered a dell streak 7 off ebay. As soon as he gets it if it's all stock I'll create images from the device without the clockwork mod and root files. I don't know when he'll be getting it but I'll post the files ASAP
anyone else getting a white screen during the restore process near p11?
third time trying and i am stuck on dell logo. cant get into recovery at all.
any ideas.
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.
OK, I need some serious help here. I've had my nc since sept., I followed the guide to put cm7 on an sd card and have been using it since then. I wanted to update to the newest .4 version but it wouldn't let me, apparently the sd card installs CMR on the nook?? I didn't think it made any permenant changes but I was clearly wrong.
OK, so no update, I follow the directions here:
http://theunlockr.com/2011/02/14/how-to-restore-the-nook-color-to-stock/
to try to get it back to factory stock, but when I rebooted and took the sd card out it started this flashing thing. It turns on but after the nook boot screen it starts flashing, normal screen/black/normal screen/black. I tried to factory reset and delete cache and that didn't do anything. I tried the directions in this thread:
http://forum.xda-developers.com/showthread.php?t=1050520
and still the same problem.
Can you help me or did I really screw things up? I guess last resort is to go to the BN store and say the update screwed things up?
EDIT: Well, I tried to factory reset the nook after following the "Restore your nook" thread and it still doesn't work. Now it doesn't flash but it also doesn't allow me to download anything at all. I'm going to try one more time to factory reset things and see what it looks like after that. My computer won't allow me to transfer files to the nc when it's connected anymore either.
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?