Database Develop

Reset Issue

Hi guys I wanted to go ahead and reload a different ROM. I had purehero 2.1 MOC (maps-oced) but I heard that the nonclocked version has better stability with wi-fi. I went ahead and tried to downgrade the rom without wiping and everything booted up fine. However wi-fi tethering was still not working I kept getting an error about unable to start wifi tethering etc. I went ahead and tried many roms (pure hero/alysious) all that wouldn't require wipe. I still kept getting same error. I went ahead and went to recovery I did a factory wipe/loaded rom and it just stays on the nexus X cross as if it's trying to boot but it doesn't it just keeps recyling over and over again. I went back to recovery and wiped data/factory and also dalvik cache ( i have a2sd enabled) then retried loading rom and same thing. I'm at the moment of wiping all mentioned plus eXt2 and reloading rom AGAIn. I hope this time it boots up.
Will something in my SD card possibly have my phone acting up the way it is? If so what solutions do u guys suggest? I hope after doing the last step I mentioned I can FINALLY log into my phone. At the moment i'm unable to do so. My aim name is crown510. If any of u can assist me I would appreciate it. Thank you!

[Q] How to fix Bluetooth on CM7?

Hey there, so i recently just flashed CM7 (cm_captivatemtd_full-133.zip). I used the method shown in the MobileTechVideos, using ODIN as well as the Speedstock kernal for the PDA. Everything worked out great! Backed up my apps via Titanium and got google apps through clockwork. Im loving CM7, but the problem is Bluetooth refuse to turn on! Every time i try and enable Bluetooth nothing happens. The icon gets greyed out and then reappears but nothing changes. Anyone know a fix to this?! Thanks!
I've tried fixing the permissions through Rom manager and rebooted a number of times. Nothing works. Also whenever i reboot the email app just FC on me :/
Edit: The process com.android.phone has stopped unexpectly shows up everytime i reboot as well!

Try to flash it again or try a previous nightly.
Sent from my Captivate

Alright, i'll give that a whirl and keep you posted! Thanks!

Did this work?
I've had the same problem, re-flashed numerous times to try and clear it (wiped my cache, dalvik, etc) but still it always happens, and then the FCs for com.android.phone keep coming intermittently.
So since my last flash, I haven't touched bluetooth, and guess what? No FC's at all.
Anybody have another idea?
I'm on 7.1.0 from 10-10-2011.

[Q] What am I doing wrong?

No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request

Shwaguy said:
No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request
Click to expand...
Click to collapse
In safe strap did you ever change to 'safe system' before you started wiping?
/Droid3

Yes sir. I followed Hashcode's procedures from his site. I am sure it is just something small and easy that will get me going in the right direction.
I have it back on the "non-safe" mode at the moment and now all I have is a wifi connection. I checked the APN and nothing was listed. Entered the Telus APN info and it doesn't save so I grabbed an APN manager from the market. It says it is active but still no connection. I am thinking of doing a factory reset to see if that will help.
I just turned 40 today and getting my phone working again would be a great gift.

Shwaguy said:
Yes sir. I followed Hashcode's procedures from his site. I am sure it is just something small and easy that will get me going in the right direction.
I have it back on the "non-safe" mode at the moment and now all I have is a wifi connection. I checked the APN and nothing was listed. Entered the Telus APN info and it doesn't save so I grabbed an APN manager from the market. It says it is active but still no connection. I am thinking of doing a factory reset to see if that will help.
I just turned 40 today and getting my phone working again would be a great gift.
Click to expand...
Click to collapse
My suggestion is to start over then..sbf your phone if you have one so you have atleast stock..then reroot it and do not install bootstrap or anything else..just instal safestrap..then go to nonsafe system..I don't think you need to wipe anything if its your first time but you can wipe anyway if you want lol then flash a rom (say cm9 or steeldroid or whatever) then reboot..it will take a while for your first boot but it should boot..let me know if this helps! Just don't boot up until after you flash a rom lol and remember safe rom is your stock rom and nonsafe is you're new rom that you're trying to flash
/Droid3

beard0 said:
My suggestion is to start over then..sbf your phone if you have one so you have atleast stock..then reroot it and do not install bootstrap or anything else..just instal safestrap..then go to nonsafe system..I don't think you need to wipe anything if its your first time but you can wipe anyway if you want lol then flash a rom (say cm9 or steeldroid or whatever) then reboot..it will take a while for your first boot but it should boot..let me know if this helps! Just don't boot up until after you flash a rom lol and remember safe rom is your stock rom and nonsafe is you're new rom that you're trying to flash
/Droid3
Click to expand...
Click to collapse
Non safe is the stock. Safe is the one you're flashing.
Sent from my XT862 using xda premium

Thanks beard0, I have not seen a sbf file for the 860 Bell. Found a system dump but thanks to the fbi it is unavailable.
Another problem popped up unfortunately. I lost connectivity. I just have wifi now. Last month when I got the phone I entered the apn info from the Telus website and everything was fine. Now when I try it I get a message saying that "mmc field must be 3 digits" I thought that info was grabbed from the sim? Regardless, I added the rest of the info required, saved, but it doesn't save the info?? I tried apn manager and it had Telus listed, selected that but still no luck. After much searching I just did the factory reset, added apn info and still have no connectivity.
I have spent so many hours on these problems and really don't know where to go from here. Going to root/safestrap etc now.

Out of curiosity I tried turning on simlock. It says no simcard detected. It worked fine for over a month and still works in my backflip though. I think the gf has a simcard in her phone so I am going to see if it reads hers when she gets here.

Shwaguy said:
No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request
Click to expand...
Click to collapse
Maybe dumb question..
After rthe steps did you Flashed the actual ROM????
Just askbecause i dont see it. Mentioned
Also, If you disable safe systemthen youshould be able to go back to regular stock.....
Enviado desde mi XT862 usando Tapatalk

Ya, I flashed the rom, tried the alpha 6 ics one also. It was after doing this then rebooting (still in safe) that i got the bootloop issue. I disabled safe system and went back.
Seems it doesn't really matter now though. It doesn't seem to be reading my simcard. No service (except wifi), Tried enabling simlock, says there is no card in it. Card works in my Backflip. I tried the g/f's Bell card and still no service, etc. Going to search around a bit and see if anything pops up but I may be sending it back. lol

Phone suddenly acting up need some help

I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.

whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery

Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....

send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too

The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....

whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.

[Q] Stock T-mobile Streak 7 not booting right Please Help!

My streak 7 just started acting up.
1.- I forgot to turn it off and the battery depleted and stayed without charge for about 4 days.
2.- At first it would not boot (after charging overnight) it would get stock on the pink animation.
3.- Contacted tech support and they had me do a factory reset (4 times).
- First time it got stuck on "Formatting DATA" (waited for it overnight)
- All other 3 worked fine.
The problem is that after it boots and I go trough the initial setup (google account, WiFi password - no sim card) it appears to be working properly, except when I turn it off and re-start it ask me for the configuration all over again. Just like if I had done an other system restore. If I try to install something from the market some times the tablet would crash (the screen would blink and then go black) and I have to use the reset pin.
I don't know what to do I'm completely new at this but I'm willing to learn. Any help giving me a direction to go will be greatly appreciated.
Thanks in advance.

You could try to NVflash back to Froyo with this file: http://d-h.st/iXc. What version were you on? This video is the first in a three part series by "giveen" which will show you how to load drivers to NVflash: http://www.youtube.com/watch?v=ydM7qkoCs00. This link will get you all the drivers: http://d-h.st/iqA. The links in the videos no longer work.
This page will get you the latest or last T-Mobile file link: http://forum.xda-developers.com/wiki/Dell_Streak_7#Official.

Thanks !
Thank you for the help. I will be trying this today.

Need more help
I tried doing the restore to factory 2.2 with the instructions above, the flash appeared to finish. But when I restarted the tablet I still have the same problem. Every time I turn it on it acts like it has just been restored to factory defaults.
I tried doing the HoneyStreak flash from here http://forum.xda-developers.com/showthread.php?t=1088225, and I got an error.
Formatting partition 2BCT please wait.. FAILED!
Could this be part of my problem? any other suggestions of what to do.
Thanks for your help.

luis_Hac said:
I tried doing the restore to factory 2.2 with the instructions above, the flash appeared to finish. But when I restarted the tablet I still have the same problem. Every time I turn it on it acts like it has just been restored to factory defaults.
I tried doing the HoneyStreak flash from here http://forum.xda-developers.com/showthread.php?t=1088225, and I got an error.
Formatting partition 2BCT please wait.. FAILED!
Could this be part of my problem? any other suggestions of what to do.
Thanks for your help.
Click to expand...
Click to collapse
You are in read-only status more than likely. Sucks.

OH NOOOOO
Does this mean I'm out of luck and pretty much have a worthless device now?
I've looked up read only mode and no one seams to have a way to get out of it (except for re-soldering components with some expensive machine)
I've also tried the "hold reset pin + capacitive buttons + power button for 2 minutes" with no luck.
And found one that calmed to have fixed it by flashing CWM to it but they did it with a version of CWM for 5.x and up and I'm still in stock 2.2
Please some one tell me there is a solution.

Yup.