[Q] My Phone Explorer Question - HTC Wildfire S

I lov using my phone explorer app, Everything works great except I used to be able to control my phone using my PC keyboard n mouse in the phone view.
I've upgraded my my phone to CM7 and it give an option to select My phone explorer as an external keyboard.
I cant get it working without selecting the option of external text in the appropriate input on my phone which sort of defeats the whole remote angle.
Can anyone help please ....

Bootloop solved
I read this thread trying to figure out why my phone (marvelc A510c virgin mobile) went into bootoop after trying to installing simonsense3.5 rom, and thought I'd share my success story. This is actually my first post. I want to hopefully save someone like me HOURS of heartache over a stupid solution.
Background (roughly):
Unlocked bootloader via htcdev, worked great.
Used Simonsimon34's htc utility and it worked okay. I still had to use the htc supertool to get root.
Got cwm 5.0.2.8 installed and made a backup rom
Downloaded simonsense3.5 rom and attempted to flash it, but phone hanged in recovery. After that, I was stuck in a bootloop. Could still get into recovery, but cwm would hang ALL the time doing things like wiping and I couldn't get it passed "Opening Update Package" when flashing new roms. I read forum after forum, reformatted my sd, wiped partitions, got a second sd, tried 3 or 4 roms people swore would work, did it all over again. Nothing! I found a thread that said to back cwm down to 5.0.2.6, but that didn't work. This went on for two days and I was getting desperate.
SOLUTION:
I finally found a thread (http://forum.xda-developers.com/showthread.php?t=1213229) that posted cwm 4.0.xx (the "previous version" link) and at my wits end flashed that, and wouldn't you know it, success! CWM was the problem the whole freaking time! I used the cwm partition creator to make a fresh 1024b partition on a fresh sd, wiped everything, put the rom on, and installed simonsense3.5 on the first damn try. The rom works okay, but I'm having some bugs... but that is another forum.
Good luck!

Related

[Q] How can i reset my HTC Desire?

Hello everyone,
first of all, im kind of new to rooting phones and stuff, what surely brought me to that problem i have.
I have an old HTC desire where i wanted to install a custom rom.
So i searched for a tutorial, i rooted the phone using unrevoked 3.21, worked fine. Then i wanted to install the custom rom, installed a backup tool first (something like "ClockwordMod Recovery") and made a backup on the sd card.
Then i wanted to install the custom ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1403113
Worked mostly fine, but when i wanted to start my phone i got stuck in the startup screen forever.
I searched for this issue and found some tips about clearing caches and clearing the sdcard, what i did - so here is the problem. The sdcard wipe propably killed my backup file and now i am pretty screwed, i still get stuck in the loading screen of the ROM, so i dont have access of the phone, and backup tool has no file to recover from.
So what to do now? I want to reset the phone to the rooted status and try to install the ROM again, but as i said i cant access to anything. Any suggestions?
Thanks
EDIT:
Allright, i have no idea why, but suddenly the phone starts up with the new OS. So this thread can be closed / deleted. Sorry for that
Checked bortak's troubleshooting guide??
http://forum.xda-developers.com/showthread.php?t=1275632
Sounds like you're sorted, can happen sometimes if it was your first CWM (nandroid) backup

[Q] Cyanogen 10.1 mod gone wrong.

AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
chazbot7 said:
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
Click to expand...
Click to collapse
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
BWolf56 said:
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Click to expand...
Click to collapse
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
chazbot7 said:
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
Click to expand...
Click to collapse
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
BWolf56 said:
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
Click to expand...
Click to collapse
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
chazbot7 said:
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
Click to expand...
Click to collapse
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
chazbot7 said:
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
Click to expand...
Click to collapse
No need to apologize. Glad you got it back up! And it was mostly to keep you from making similar mistakes in the future
Sent from my SGH-I747 using xda app-developers app
also one thing you need to know
First boot after you flash will always take longer than normal. After that, it's fine

[4.4.2][CWM Recovery][E98020h]LG Optimus G Pro CWM Recovery Error/FreeGee Error!

Recently, I have been introduced to Android Rooting and I have successfully rooted my phone with Towelroot. My friend installed Cyanogenmod 11 on his Galaxy S3 the other day and I have been having many problems doing the process myself. I have ripped xdadevelopers to pieces trying to find a solution, but nothing has ever been simple enough, well really efficient enough to fix my problem.
I have ROM Manager installed on my device and the latest CWM Recovery and when I get to the "Recovery" mode it does not give me all the options a normal "Recovery" screen would give me. I can not backup my current stock rom because there is no option. In doing this I accidentally wiped my phone and had no way to recover, so I lost a lot of temporary things, very frustrating.
Basically what I need to know is how to get CWM Recovery to work on my device, etc. Also I forgot to mention before that FreeGee messes up too. It says something about "loki" or something. I am sick of trying several methods that fail in the end. If you can tell me how to get CWM Recovery to work on my phone. I do have an SD Card and my phone is rooted. Please help me! I apologize if all the information is not present, but if you need to know anything specific I would be more than happy to answer your question!
RyeM8 said:
Recently, I have been introduced to Android Rooting and I have successfully rooted my phone with Towelroot. My friend installed Cyanogenmod 11 on his Galaxy S3 the other day and I have been having many problems doing the process myself. I have ripped xdadevelopers to pieces trying to find a solution, but nothing has ever been simple enough, well really efficient enough to fix my problem.
I have ROM Manager installed on my device and the latest CWM Recovery and when I get to the "Recovery" mode it does not give me all the options a normal "Recovery" screen would give me. I can not backup my current stock rom because there is no option. In doing this I accidentally wiped my phone and had no way to recover, so I lost a lot of temporary things, very frustrating.
Basically what I need to know is how to get CWM Recovery to work on my device, etc. Also I forgot to mention before that FreeGee messes up too. It says something about "loki" or something. I am sick of trying several methods that fail in the end. If you can tell me how to get CWM Recovery to work on my phone. I do have an SD Card and my phone is rooted. Please help me! I apologize if all the information is not present, but if you need to know anything specific I would be more than happy to answer your question!
Click to expand...
Click to collapse
Have you tried installing the recovery from G.Pro Recovery first? Freegee will not work for me, giving me similar errors, until I first do that. See the to the Bountyman G3 v4.x thread under 'Optimus G Pro Android Development' for more info. Works for me every time (though I choose TWRP; friggin' *hate* CWM).

[Q] Bricked my phone... Need Help.

Like I'm sure this topic hasn't come up before, but I've searched for hours and I'm probably just making things worse. I also just accidentally deleted this post halfway through. It's too late and I'm too tired and I have no working phone.
Bought an SGH-I747 on E-Bay. Got a Straight Talk SIM card kit, activated it, so far so good.
Rooted it with CF-Auto-Root. Worked pretty well, took a lot of reboots, upgraded the SU from the Play Store and it got rid of Knox. So far so good. Got everything all set up the way I like it. Happy.
It was running 4.4.2. I'm assuming it was the release prior to the November 12th OTA release, but I can't say for sure.
Phone downloaded and installed an upgrade automatically. Now, it won't boot. I get the SAMSUNG logo, then the Samsung Galaxy S III logo then nothing.
I retried the CF-Auto-Root, no change.
I booted into recovery (volume up, home and power on), did factory reset, no change.
Started looking around for a way to return it to stock. Found an upgrade43.zip file somewhere (I'm sorry I can't find where I got that now). Put it on the sdcard card and tried installing it with the recovery and it fails part way through.
At this point, I think I probably need to completely overwrite everything with something stock. I just don't know how to do that. I see posts on such subjects but they all have warnings that make me think I'm going to totally brick the phone, so I'm hoping someone can point me the right way. I'm not all that Android savvy, as you can tell.
Help.
Since your phone was running 4.4.2, do not attempt to flash any ROMs using that attempt to downgrade your bootloader to anything prior to 4.4.2.
Try this to get your phone up and running:
download the latest CM11 for the d2lte and save it to an external SD card: https://download.cyanogenmod.org/?device=d2lte
dowload the latest tar.md5 version of Philz Touch for the d2lte from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
boot phone in download mode, open Odin 3.07, do not check anything except f.reset.time, flash Philz via PDA box, remove USB cable when you see the word Reset appear in the status window, remove battery, replace battery, boot into recovery, format system, Dalvik, data, and cache, flash cm11, and reboot.
Thank you for your reply. There are a few things in there I don't quite understand, but I think I can figure it out.
I was going to attempt this...
http://forum.xda-developers.com/showthread.php?t=2658486
In fact, I did attempt it with TWRP last night after I posted here and new I still wasn't going to sleep. I kept getting an error about a bad ZIP file.
Is that stock restore a bad idea?
Do not attempt to flash an older bootloader. The mjb bootloader is from 4.3 and attempting to flash it could hard brick your phone.
I suggest doing what I suggested so you can confirm the bootloader and modem installed on your phone.
OK. Thanks. Probably a good thing I couldn't get it to work then.
Thank you so much. I have a working phone again. Now I just have to get it all set back up the way I like it.
I have to say, and it's probably words straight from the devils mouth, that I kind of wish I could have restored the Samsung stock software. It's just what I'm used to. But I will take what I can get.
A few questions. I like having root. But root is what got me in trouble in the first place. Is this going to be rooted now, or will I have to do that or am I better off just leaving it alone.
Second, I'm probably going to have questions since this is so different than what I'm used to (like I already can't find the Play store). Where is the best place to ask?
If you want root, one of the easiest ways to get it is to flash supersu from your custom recovery. Most ROMs are pre-rooted.
Many custom ROMs do not include Gapps. Just download and install the Gapps version for your ROM.
If you like the TW look, flash a TW-based ROM. Check out the development threads for different ROMs.
here is a thread for Q's that has some pretty good/friendly helpers on it if you need.
http://forum.xda-developers.com/showthread.php?t=2257421
"all i can really do , is stay out of my own way and let the will of heaven be done"
How to save in to external SD card
How do you save the file into the external SD card? I am having the same brick issue with my GS3.
To save a file to an external SD card, just put the card into a card reader and save the ROM to the SD card.

[Solved] Issues activating SGS3 SPH-L710 on Sprint with Custom ROM + lots of problems

Hello all!
This is my first foray into the world of custom Android systems, and I'm having a hell of a time with it... if somebody would be able to help me out, I would greatly appreciate it.
First off, the situation:
I am on Sprint, and I recently bought a Samsung Galaxy S3 (SPH-L710) from Sprint to use as a backup phone, I used it for a while on Stock, then deactivated it so I could give it to my wife. First though, I wanted to put a custom ROM on it, and experiment/play around a bit and see what this world of options could do for me. Long story short, I ended up flashing an AICP ROM, and everything seemed to go smoothly, but when I went to activate the phone on my account again and it would not work no matter what I tried (details below). I figured maybe I could activate on the stock setup then just restore my custom setup, so I tried to revert to my stock ROM backup and I couldn't do anything because I was constantly getting messages that various programs had closed... Then I tried to wipe and restore my custom ROM backup and I get stuck in a boot loop... so I tried to flash a stock recovery and I get stuck in a boot loop... I'm out of ideas here, and now I'm stuck with a phone I can't use or do anything with, and I can't activate.
Details:
The initial rooting/install process seemed to work ok, and was fairly straightforward. I followed various guides on http://galaxys3root.com/ to get my phone rooted and backed up (Don't recall which ones now, but I've read through so much by now I don't know if it matters...).
My phone:
Samsung Galaxy S3 (Sprint) SPH-L710
Modem: L710SPRDNJ2
My Desktop:
Debian Linux
Here's the steps I performed:
Rebooted phone in Odin mode
Downloaded CWM S3 Sprint Recovery from the http://galaxys3root.com/ website (can't find the link any more)
Flashed the CWM recovery using Heimdall then rebooted phone into CWM
Installed SuperSU through CWM, then rebooted
Checked that the phone was rooted successfully (it was), then ran Titanium Backup on the whole device to my SD card, then copied the backup files to my desktop computer
Rebooted into CWM, and performed a backup through CWM, then rebooted and copied the CWM backup to my desktop.
Downloaded AICP Rom for my phone from here: http://downloadandroidrom.com/file/GalaxyS3Sprint/roms/AICP/aicp_d2spr_lp-10.0-RELEASE-20150707.zip, put it on my SD card, then installed it through CWM and rebooted
At this point, I was happy with how everything was working, so I did some minor theme customizations then made another backup through CWM, and copied it to my computer, but I did NOT run Titanium this time...
After all of this, I tried to go ahead and activate it through the Sprint web service. This process failed continuously with an unhelpful error message of "Sorry, this device can't be activated right now". I then got on Chat to see if they could activate it manually, and then the problems began. They did their thing activating the phone, but when I booted up I got no data connectivity, and couldn't make calls, and the SIM was not changing over to the new number. I was on the chat with them for over an hour trying to get the situation resolved, but that finally ended when they started asking me to punch in ## codes, because I discovered that none of them worked on my custom ROM. Some quick research told me that this was non-trivial to get around so I had them switch everything back and I started researching the issue.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1626638&highlight=sph-l710 that looked like it would let me do what I needed from the custom ROM, but I couldn't tell if it would fix my problem for sure, so I figured "I'll just restore my stock setup from that backup I took, activate it and update, then start over". This is when things got really frustrating...
First I rebooted into CWM, went to 'backup/restore', and restored my stock backup
Rebooted, and as soon as I got past the lock screen, I get inundated with messages of various apps being closed unexpectedly.
I researched a bit, discovered the issue may be caused by stale dalvik cache, so I rebooted into CWM, cleared the dalvik cache, formatted the /cache partition, then tried to restore the stock backup again, but this time I get stuck in a boot loop.
I then rebooted into CWM, tried to restore the backup of my AICP ROM, only to be stuck in a boot loop as well.
Trying to get into any usable system, I rebooted to CWM, cleared dalvik cache, then formatted /cache, /data, and /system just to be sure, and re-flashed the base AICP ROM I started with. This worked fine, and before long I had stock AICP back
Since I still couldn't get the phone to activate in the custom ROM, and my backups are apparently completely useless, I rebooted into CWM, wiped dalvik, /cache, /data, and /system again and tried to install a different stock ROM I found in the XDA forums (here: http://forum.xda-developers.com/galaxy-s3-sprint/development/stock-rom-4-4-2-t3010642) only to be greeted by another bootloop
At this point I've spent well over 24 man-hours trying to get this to work, reading, researching, flashing, etc all to no avail. Nothing I do seems to work, and it seems like every article, tutorial, or forum thread I read either has nothing to do with my device, is too old, or doesn't describe my problem.
I'm at wits end, and am so frustrated I'm ready to just give up and smash this device and buy a new one... My questions to the community are as follows:
I know I screwed up on a couple of things, but in my initial research of doing this there was no indication that these were even things I needed to watch out for... Is there any more organized sources of information for doing this sort of thing?
Does anybody else out there use Sprint on a custom ROM, and if so how you you pull this off
Where else have I screwed up, and how can I fix this situation? (My end goal is still to get the S3 onto Sprint with a custom ROM)
What can I do differently next time? I would like to figure this out and do it to other phones and devices I have, but if it's this much trouble every time, I just don't have the time to mess with it.
Thank you in advance, and I appreciate any information that the community can provide.
This sounds like a CWM problem to me. If I were you, I'd boot the phone into Odin Mode and flash TWRP ( www.twrp.me ) then try flashing the latest aicp nightly downloaded from the official site ( www.aicp-rom.com ). Check the md5sums on everything! Then maybe try flashing a touchwiz ROM and activating your phone. Remember that you need to wipe the internal storage when you go between KitKat and lollipop.
I'm fairly certain you have to do activation with the stock Touchwiz roms -- once the phone is activated you can flash a custom.
You should go into recovery and wipe everything (System/data/etc) EXCEPT for the External SD Card
Power off - pull the battery for a few - power on directly into download mode
Odin NJ2 back onto the phone and reboot and activate it (skip through most of the setup since you'll flash a custom after)
Once you know it's activated and working under the stock Touchwiz, then again power off and Odin TWRP recovery
Then you can go back into recovery, wipe everything except External SD, and flash the custom rom back on.
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
afarris01 said:
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
Click to expand...
Click to collapse
Get rid of them. TWRP can't restore CWM even if the backup is good

Categories

Resources