Related
Thanks for taking an interest in my problem and trying to help.
Here's what I've figured out. I tried doing Toast's root method for linux and the directions weren't idiot proof because I screwed them up. I've explained how far I've gotten in other threads. If that's relevant just ask and I'll explain exactly what I did.
Anyway my phone does the basics. It allows me to make phone calls, text, and look at the internet on the phone so this isn't an emergency but it I am worse off than I was before I tried to root because I can no longer use easytether.
I had no problem with easytether prior to the root attempt, and it still works when I hook it up with my wifes untampered evo. with my phone but with my wife's evo, I've never messed with that one, I have no trouble connecting with easy tether.
Some of the things I've noticed about the device since the attmept...
-I can't update to 2.2 via the OTA or any other method, my device says no updates are available.
-Simple root wasn't so simple, the phone never shut off and rebooted into boot screen like the red screen said it would in step 1.
How do I reset the device to the way it was the day it was purchased. I've got everything I need backed up. I'm ready to reset just tell me how.
Thanks.
Please?
I know it bothers people here when they think someone didn't research anything first but I really did. The problem was I'm on linux so most of the stuff I researched didn't seem to apply, not to mention I'm quite illiterate in the terminal... but working on it. I'd really like to get this phone back to stock so I can try again.
Can anyone help?
what ROM are you running? base on eclair 2.1 or froyo 2.2..
try this http://shipped-roms.com/index.php?category=android&model=Supersonic
They are the Stock Unmodified ROMs for your EVO 4G the first 3 are Eclair (2.1) and the last 2 are Froyo (2.2)
Just know that if you use any of this you will LOSE Root..
Hope it helps..
I recomend you try 1.47.651.1 first ...
Good Luck
hortstu said:
Thanks for taking an interest in my problem and trying to help.
Here's what I've figured out. I tried doing Toast's root method for linux and the directions weren't idiot proof because I screwed them up. I've explained how far I've gotten in other threads. If that's relevant just ask and I'll explain exactly what I did.
Anyway my phone does the basics. It allows me to make phone calls, text, and look at the internet on the phone so this isn't an emergency but it I am worse off than I was before I tried to root because I can no longer use easytether.
I had no problem with easytether prior to the root attempt, and it still works when I hook it up with my wifes untampered evo. with my phone but with my wife's evo, I've never messed with that one, I have no trouble connecting with easy tether.
Some of the things I've noticed about the device since the attmept...
-I can't update to 2.2 via the OTA or any other method, my device says no updates are available.
-Simple root wasn't so simple, the phone never shut off and rebooted into boot screen like the red screen said it would in step 1.
How do I reset the device to the way it was the day it was purchased. I've got everything I need backed up. I'm ready to reset just tell me how.
Thanks.
Click to expand...
Click to collapse
I bet a friend told you about root without giving you all the details, right? Haha. Ok, back to business. Rooting will make it impossible to receive ota updates. This is not a problem, because devs post rooted ota updates that you can flash manually. As far as I know, root is 100% permanent, but you don't know the goods. First of all, search wireless tether root in market it should have a green wifi icon. Second, try some custom roms and themes. I bet you will cry when you see yourself asking to go back to stock....
jadehawk said:
what ROM are you running? base on eclair 2.1 or froyo 2.2..
try this http://shipped-roms.com/index.php?category=android&model=Supersonic
They are the Stock Unmodified ROMs for your EVO 4G the first 3 are Eclair (2.1) and the last 2 are Froyo (2.2)
Just know that if you use any of this you will LOSE Root..
Hope it helps..
I recomend you try 1.47.651.1 first ...
Good Luck
Click to expand...
Click to collapse
I never got to the point where I could flash a ROM or got root. S was never off.
just in case it makes a difference.
firmware= 2.1-update1
baseband version= 1.39.00.04.26
kernel version= 2.6.29-a2443432
build#= 1.32.651.1 CL171253 test-keys
software#= 1.32.651.1
I think the rest is up to date.
I bet a friend told you about root without giving you all the details, right? Haha.
Click to expand...
Click to collapse
Actually I'm a bit of a forum junkie and as soon as I got this phone I found the android forums and have spent a ton of time there trying to maximize the utility of this device. I've done the opposite.
Ok, back to business. Rooting will make it impossible to receive ota updates. This is not a problem, because devs post rooted ota updates that you can flash manually. As far as I know, root is 100% permanent, but you don't know the goods. First of all, search wireless tether root in market it should have a green wifi icon. Second, try some custom roms and themes. I bet you will cry when you see yourself asking to go back to stock....
Click to expand...
Click to collapse
I only want to go back to stock so I can get rooted! I can't root because I can't get 2.2 so I can't use unrevoked 3.21. I can't use simple because of some problem I had with the toast linux method that seems to be screwing up everything since. I appreciate the input I hope I've explained myself better.
hortstu said:
Please?
I know it bothers people here when they think someone didn't research anything first but I really did. The problem was I'm on linux so most of the stuff I researched didn't seem to apply, not to mention I'm quite illiterate in the terminal... but working on it. I'd really like to get this phone back to stock so I can try again.
Can anyone help?
Click to expand...
Click to collapse
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
grouse130 said:
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
The problem is I don't think I'm rooted.I flashed pc36img.zip and never made it any further. Am I rooted. Do I need to undo this or can I do a hard reset?
grouse130 said:
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
OK so here's why I think I'm not rooted, when I follow step one of the detailed directions,
Power off the phone and reboot into the recovery by holding VOL DOWN + POWER until it boots to the white screen. Then select RECOVERY.
Click to expand...
Click to collapse
I get a screen with an evo, a red triangle, and a red exclamation point.
Where do I go from here?
Any direction will be immensely appreciated.
To find out if you're rooted, simply try to run an app that requires root access. Try downloading Titanium back up, and as soon as you install it, hit the "Problem?" button on the lower right and install busybox. One of the first lines on the main screen of the app says:
Root access => OK (Busybox 1.16.0 from app)
If it does not say "root access => OK" and you cannot use the app, then you don't have root.
hortstu said:
OK so here's why I think I'm not rooted, when I follow step one of the detailed directions,
I get a screen with an evo, a red triangle, and a red exclamation point.
Where do I go from here?
Any direction will be immensely appreciated.
Click to expand...
Click to collapse
From this screen, if you hold volume up and press the power key, it will take you to the hboot menu.
Have you flashed a recovery img?
Sent from my PC36100 using XDA App
rugedraw said:
From this screen, if you hold volume up and press the power key, it will take you to the hboot menu.
Click to expand...
Click to collapse
OK so I'm at the "hboot" screen.
Code:
Android system recovery <2e>
Use volume...
click power key...
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Then in yellow, below the device picture, triangle, and exclamation I have
Code:
E: Can't open /cache/recovery/command
Not sure where you're steering me rugedraw but thanks for the help...
hortstu said:
OK so I'm at the "hboot" screen.
Code:
Android system recovery <2e>
Use volume...
click power key...
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Then in yellow, below the device picture, triangle, and exclamation I have
Code:
E: Can't open /cache/recovery/command
Not sure where you're steering me rugedraw but thanks for the help...
Click to expand...
Click to collapse
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
To find out if you're rooted, simply try to run an app that requires root access. Try downloading Titanium back up, and as soon as you install it, hit the "Problem?" button on the lower right and install busybox. One of the first lines on the main screen of the app says:
Root access => OK (Busybox 1.16.0 from app)
If it does not say "root access => OK" and you cannot use the app, then you don't have root.
Click to expand...
Click to collapse
Finally went back and checked on the titanium backup download. When I first opened it I got the message that it didn't have root access. So I clicked on "problems?" and installed busy box. Now it says,
Root access v=> OK (BusyBox 1.16.0 from app
Click to expand...
Click to collapse
Plus some other stuff... so I guess I have root but not S-off.
hecklbrg said:
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
Click to expand...
Click to collapse
Should I still do this or is the info from titanium backup enough?
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
Click to expand...
Click to collapse
Yes I tried doing that but like I said I'm on a linux computer and had some trouble with the steps. What I'd really like to do is just go back to stock and try rooting with unrevoked 3.21.
My concern is that selecting factory reset from the hboot screen won't take me back there. If it did I could probably get the 2.2 update over the air, I suppose now I have to worry about getting this other update that everyone is talking about at the same time. Can I get 2.2 and avoid the update that came out last night? How.
Will a factory reset get me back to stock? I've already got everything backed up that matters.
Thanks for all the help.
OK...I think this should work for you:
go here and download the file on the page:
WRONG FILE>>>WILL FIND THE CORRECT ONE.
rename it update.zip and put it on the root of your SD card.
Boot into HBOOT then into recovery and go to apply update.zip -- choose the file you put on there.
let it run and you should have the stock non-rooted version of the 1st software release from sprint. from there you can update it as far as you want to root it the method of your choice.
hecklbrg said:
OK...I think this should work for you:
go here and download the file on the page:
WRONG FILE>>>WILL FIND THE CORRECT ONE.
rename it update.zip and put it on the root of your SD card.
Boot into HBOOT then into recovery and go to apply update.zip -- choose the file you put on there.
let it run and you should have the stock non-rooted version of the 1st software release from sprint. from there you can update it as far as you want to root it the method of your choice.
Click to expand...
Click to collapse
Thanks hecklbrg,
I assume since I'm half rooted a factory reset won't get me there?
I'll wait for the link to that file...
if you put this on your card and run it from HBOOT...you will get a rooted version of the latest sprint OTA with a custom recovery and the latest radios.
http://forum.xda-developers.com/showthread.php?t=791019
I'm still looking for a non-rooted version to run...but I would think this would work for you to get you the latest OTA in a rooted form.
Second thing is that I don't think you really screwed up your root process. You have only done part of the process and haven't installed a custom recovery. If this works for you, it will give you a custom recovery and you will have a fully rooted phone.
Hecklberg is right. I don't think you even need to rename it update.zip. If its a
pc36img.zip your hboot will automatically scan for it, find it and run it when you put it on your SD card and open hboot.
Also consider, I rooted my phone without any computer, all done from my Evo, using fastRX8 thread in here about how to root for newbies. It involves putting the files on your SD card, then installing terminal emulator from the market and typing a few commands to install flash_image, then custom recovery. You are root, just don't have flash image, custom recovery, and superuser yet. Basically toast part 2, it can be done with no computer, but same files.
Read real quick Whitslack thread on rooting, and fastrx8 thread, even just the 1st post, and it will make sense to you where you're at and what's left to do. You'll see how close you are.
Once root, and superuser installed, you won't need easy tether, Android wired tether is what I use (doesn't require installing any software on the host pc)
(Actually, if you use the threads I mentioned method, don't use the recovery amonra1.7.0.2, there's a newer one to download, its at 1.8 now, just Chang the recovery file name you type in terminal app accordingly-don't worry, it won't go thru if you do it wrong, but won't 'break' anything)
Hope any of this helps, but yeah, hecklberg is right too, just different methods. One requires no computer.
And yeah, with the devs around here, you don't need any Sprint OTAs, most of the time, they seem to have em available before Sprint releases them. These guys are good.
scottspa74 and hecklbrg,
Thanks for the help. I havent had time to look at this or act on it over the last 24 hours but I will try to get to it tonight and let you know how it works. Sounds like you've gotten me out of the woods.
Thanks again.
I think it is $ if you are rooted and# if you aren't because I know I'm rooted and it shows money signs, unless terminal emulator is messed up,i have nvr used it.
hecklbrg said:
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
Click to expand...
Click to collapse
Sent from my netarchy_toast, froyo beast of a machine evo!
evohack99 said:
I think it is $ if you are rooted and# if you aren't because I know I'm rooted and it shows money signs, unless terminal emulator is messed up,i have nvr used it.
Sent from my netarchy_toast, froyo beast of a machine evo!
Click to expand...
Click to collapse
Nope you are incorrect my friend.. try typing " su " on the terminal emulator see if you get the "#" ... # ==> Root and $ ===> User(I Think) But I know for sure "#" is root access
I've successfully permanently rooted my Sprint Intercept with the latest 2.2 froyo on it without installing custom kernels and wanted to share steps I took since there is some confusion and differences.
Original guide link.
Things you'll need:
Root files.
Samsung drivers.
Windows 7/vista/xp 32 bit.
Steps:
Install Samsung drivers
Reboot your PC
Reboot your phone, connect it to your PC with a usb cable
Put your phone in debugging mode (menu->settings->applications->development)
Extract root files to your c:\intercept-root folder (or any folder you wish)
Start windows command line (start->run->CMD)
Change to your "intercept-root" folder
Execute START_ROOT command
Follow instructions
Once done, don't forget to install Superuser apk.
after you rooted it you were able to put a different rom on it right. trying to clear out the garbage that comes on it.
shonok said:
after you rooted it you were able to put a different rom on it right. trying to clear out the garbage that comes on it.
Click to expand...
Click to collapse
No, this is just simply to root and remove stuff you don't want. I suggest Titanium backup. There is no proper recovery for the intercept that I know of. The one existing can be flashed and it does work but has some issues with what it backs up and what it restores. It's not complete and may create problems.
If you are rooting the latest 2.2 froyo, after removing all sprint apps you are left with true bare stock so there is really no need for anything else. Make sure you don't remove the sprint vm even if you are using google voice. It needs to be on because of system integration.
you mae one error. the drivers can't be installed on windows 7. I have gotten the drivers from the moment to work once but now its nothing. my computer no longer recognizes the phone when i plug it into the computer. which means that i cant root it or anything. sucks and i need serious help.
hmmm, same problem
Find a friend with a XP laptop and use that?
Glad to know - i have failed at rooting my intercept a few times and have been using my windows 7 box. Trying these instructions from a laptop - will report back!
Success
Using nothing but a old crappy dell laptop runing windows XP I was able to gain perma root using the instructions provided here. On my first run of the script the process failed, I simply did what the program told me to (run the script again) and it worked like a charm.
OP - thank you so very much for taking the time to post.
Question for anyone: now that I have root, I *really* want to be able to use my Intercept as a wi-fi hotspot. Can I do this? Where do I start?
No errors. I got drivers under Windows 7 working but I clearly said it has to be 32 bit as 64 does not work. Check your version.
entropy.of.avarice said:
Using nothing but a old crappy dell laptop runing windows XP I was able to gain perma root using the instructions provided here. On my first run of the script the process failed, I simply did what the program told me to (run the script again) and it worked like a charm.
OP - thank you so very much for taking the time to post.
Question for anyone: now that I have root, I *really* want to be able to use my Intercept as a wi-fi hotspot. Can I do this? Where do I start?
Click to expand...
Click to collapse
Download wireless tether app. I've had troubles with it in the past so if that one doesn't work try Barnacle.
how to flash cmo1 custom recovery after phone is rooted?
Just throw intercept root on sdcard and run
All I had to do it throw the root on the sdcard. Run it from the file manager, and then download barnacle. Sweet! Done!
Ignorance1 said:
how to flash cmo1 custom recovery after phone is rooted?
Click to expand...
Click to collapse
I don't believe there is a supported recovery for the intercept. There is one hacked up but there are some issues with it so I don't recommend it.
Sent from my Nexus S 4G using XDA App
obsanity said:
I don't believe there is a supported recovery for the intercept. There is one hacked up but there are some issues with it so I don't recommend it.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
There is no problems with the custom recovery. I recommend it if you want to try custom roms/themes. Check sdx for all things intercept
Sent from my PG06100 using Tapatalk
Can you fix/update the links, please? I need to files for root, drivers, etc. Everything I need to root my backup phone, please.
ThunderOKC said:
Can you fix/update the links, please? I need to files for root, drivers, etc. Everything I need to root my backup phone, please.
Click to expand...
Click to collapse
Yeah, me too.
Looking to root my Intercept, but the 4shared link is broken
UPDATE: OK, I think this is what he was linking to. But my Antivirus doesnt like it. It says it's a virus. A severe virus.
Ok i rooted the phone when it was on 2.1 & it worked just fine, after the root it said system update, so i said ok to froyo, now i can't for the life of me seem to be able to root this phone the Samsung one click root dosen't work, & my PC won't recognize the phone so i can't use Odin, It's really pissing me off, if anybody can help me i'd sure be greatfull.
jaaydogg said:
Ok i rooted the phone when it was on 2.1 & it worked just fine, after the root it said system update, so i said ok to froyo, now i can't for the life of me seem to be able to root this phone the Samsung one click root dosen't work, & my PC won't recognize the phone so i can't use Odin, It's really pissing me off, if anybody can help me i'd sure be greatfull.
Click to expand...
Click to collapse
Make sure you have the latest drivers from Samsung installed on your PC. Reboot the phone, reboot the PC, start as fresh as you can. Best way to go about it is to Odin EC05, One Click root with CM3 (purple version) and go from there.
Check the stickied thread with the old stickies in it, you'll find everything you need in there. And last but not least, for the love of everything holy, don't use the stock cord. Get something decent, blackberry cables seem to work the best for me. Make sure the port you're plugged into on your PC is on the back (so it's direct into the board) not one of the front ones.
Well first off, having the thread title as "???" does not help anyone with searching for answers.
I'm trying to understand your situation: So you say you were on Eclair and rooted, and then was able to upgrade to Froyo while rooted? That's not possible. The update would have failed after seeing a file system mismatch.
For Eclair and Froyo, the 1-click root method works. However, for Gingerbread you have to Odin a custom kernel and recovery, then install the Superuser app. Once you have CWM installed you can flash any EL30 rom you wish. The modem is upgraded manually. Look in the dev section for the sticky thread that has the thread link in it.
Video 1: http://youtu.be/kwFRzzIqouE
Video 2: http://youtu.be/jWOLEXqAeCc
To follow up on your Odin woes: use a different USB port that is directly on the motherboard; and a different cable.
http://forum.xda-developers.com/showthread.php?t=1009997
Go to that thread, and it will tell u everything u need to know
Sent from my SPH-D700 using xda premium
2.1? Froyo? You know the Epic has official Gingerbread right? And stable ICS?
Sent from my SPH-D700 using Tapatalk
Well i know that but the site wouldn't let me name it anything, I mean like 15 different titles that i wasan't allowed to use. Anyway I was able to fix the phone up, i was having a driver issue & that's what was stopping Odin from detecting the phone in downloader mode.
Yeah I'm a bit confused at the methods. One guide tells you to use the official website, other threads take you to that same one. I havent had an Xperia Play since late 2012 - early 2013 and I found this one back in my old stuff. Sony website tells you to check with the dialer and see if it says yours is allowed to be unlocked. Mine has NOTHING. So what I'm supposed to suffer about 3-4 years later in the future because Verizon still decides they want to continue hiding whatever secrets this device packs?
I'm trying to experiment with custom roms. Stock is boring and would also love to root (which I can't because I'm on 2.3.4 since I'm an idiot).
We didn't even know about jellybean when I first had this thing. Now we have KitKat which is also aimed and claimed to run on a minimum of 512mb ram.
Any help?
Anybody? Its very frustrating as this phone has some potential.
Crossvxm said:
Anybody? Its very frustrating as this phone has some potential.
Click to expand...
Click to collapse
Hi Crossvxm,
You can definitely unlock the bootloader on your phone. The Verizon Xperia Play doesn't show the bootloader unlock status in the service menu, but it's been confirmed in lots of other posts where R800x owners have unlocked their bootloaders. I have also done it personally with the Sony Official method. Here's the link to the Sony website if you want to give it a go: http://developer.sonymobile.com/unlockbootloader/
You can also root your R800x while it's still on 2.3.4 using the Eroot method. See this thread for more information on Eroot: http://forum.xda-developers.com/showthread.php?t=2240285. Please make sure to hit the thanks button for Nabeel, wym986, Vokal1992, and any others who helped bring this root method to us. The direct download link for the Eroot version that I have used is: https://www.dropbox.com/s/jnwl5r3fnsssbuu/Eroot_V1.3.4.exe. If you want to check the MD5 checksum after downloading it, it should be: 459d8bdda203a5f5e9d28231fa6df6b0
Here are some instructions that I made for my friend to help him root his R800x, but the thread mentioned above also has instructions...
-Eroot Instructions-
1. Disable the anti-virus software on your computer to prevent it from stopping the root exploit
2. Go to your phone Settings/ Applications/Developer Options and Make USB Debugging is enabled. (I don't know if it's necessary, but I also check the box to allow Unknown Sources).
3. Plug your phone into the computer with a USB cable and make sure your phone is recognized by the computer before proceeding
4. Right click on the Eroot application and run it as Administrator
5. Eroot should recognize that your phone is connected and after a brief moment, it should prompt you to click on a green “Root” button. Click that button and it will show steps 1-4. Once it completes its process, your phone should be rooted with the Superuser app installed.
(PS: After it roots the phone, it will turn off Wifi. Just go back into your phone's settings and toggle the Wifi back on to get it working again).
I had some trouble getting the Superuser binaries to update after completing the above steps... so I used Titanium Backup Pro to wipe data/clear cache and uninstall the Superuser app. I then went to the Play store and reinstalled it. (This is the Superuser version I am using and it works fine: https://play.google.com/store/apps/details?id=com.koushikdutta.superuser&hl=en ).
Good luck.
mattnmag said:
Hi Crossvxm,
You can definitely unlock the bootloader on your phone. The Verizon Xperia Play doesn't show the bootloader unlock status in the service menu, but it's been confirmed in lots of other posts where R800x owners have unlocked their bootloaders. I have also done it personally with the Sony Official method. Here's the link to the Sony website if you want to give it a go: http://developer.sonymobile.com/unlockbootloader/
You can also root your R800x while it's still on 2.3.4 using the Eroot method. See this thread for more information on Eroot: http://forum.xda-developers.com/showthread.php?t=2240285. Please make sure to hit the thanks button for Nabeel, wym986, Vokal1992, and any others who helped bring this root method to us. The direct download link for the Eroot version that I have used is: https://www.dropbox.com/s/jnwl5r3fnsssbuu/Eroot_V1.3.4.exe. If you want to check the MD5 checksum after downloading it, it should be: 459d8bdda203a5f5e9d28231fa6df6b0
Here are some instructions that I made for my friend to help him root his R800x, but the thread mentioned above also has instructions...
-Eroot Instructions-
1. Disable the anti-virus software on your computer to prevent it from stopping the root exploit
2. Go to your phone Settings/ Applications/Developer Options and Make USB Debugging is enabled. (I don't know if it's necessary, but I also check the box to allow Unknown Sources).
3. Plug your phone into the computer with a USB cable and make sure your phone is recognized by the computer before proceeding
4. Right click on the Eroot application and run it as Administrator
5. Eroot should recognize that your phone is connected and after a brief moment, it should prompt you to click on a green “Root” button. Click that button and it will show steps 1-4. Once it completes its process, your phone should be rooted with the Superuser app installed.
I had some trouble getting the Superuser binaries to update after completing the above steps... so I used Titanium Backup Pro to wipe data/clear cache and uninstall the Superuser app. I then went to the Play store and reinstalled it. (This is the Superuser version I am using and it works fine: https://play.google.com/store/apps/details?id=com.koushikdutta.superuser&hl=en ).
Good luck.
Click to expand...
Click to collapse
Giving this a try right now
Cool man. I hope you can get the bootloader unlocked and get rooted so you can experiment with some of the newer ROM'S. I recently bought my Xperia Play really cheap off eBay and I'm having fun playing with it. I'm really only using it as a gaming device because I have a rooted/ROM'ed Samsung Note 2 as my daily driver.
Let us know how things turn out.
mattnmag said:
Cool man. I hope you can get the bootloader unlocked and get rooted so you can experiment with some of the newer ROM'S. I recently bought my Xperia Play really cheap off eBay and I'm having fun playing with it. I'm really only using it as a gaming device because I have a rooted/ROM'ed Samsung Note 2 as my daily driver.
Let us know how things turn out.
Click to expand...
Click to collapse
It worked, my bootloader seems to have successfully unlocked. I also used the root tool you mentioned and in about 3 tries it actually rooted it! And BTW, i found this Xperia Play in a box from when I moved to NYC and i forgot all about it. I also use it for games that cant be playes on a touchscreen like Megaman X4 and Super Mario World. But I use my G2 for everything else. Its just hard to run and jump on Mario with touchscreen buttons when you have to use your entire thumb for both of those and your other thumb to move.
Now my question is, how do i install a custom recovery? I used the X-Parted apk and a CWM installer apk from the same dev, and it seems to flash the recovery, but when i click for it to reboot into recovery the device reboots normally. Also, when I try to manually reboot it into the custom recovery, it just powers off after the android symbol and restarts normally. Has me stumped as to why.
Crossvxm said:
... Now my question is, how do i install a custom recovery? I used the X-Parted apk and a CWM installer apk from the same dev, and it seems to flash the recovery, but when i click for it to reboot into recovery the device reboots normally. Also, when I try to manually reboot it into the custom recovery, it just powers off after the android symbol and restarts normally. Has me stumped as to why.
Click to expand...
Click to collapse
Cool man. That's great that you can ressurect your Xperia Play and enjoy using it again. I'm having a blast with using emulators. My friend recently introduced me to Quake and I've been playing it a lot lately. (If you have any interest in Quake, I just started a thread in the Theme and Apps section with instructions on how to get it running on the Xperia Play using the FTEDroid port and Gamekeyboard+, which allows you play it with the phone's hard key controllers). .
Anyway... I also had trouble using the Xparts app to install CWM. I found another thread that provides a command script to install it, and it's worked perfectly for me every time.
Here are some instructions that I typed up a while back when I was helping my friend root his R800x... The credit for this should go to the original poster in the thread and to all of the people who helped develop the CWM .
--------------------------------------------
INSTALL INSTRUCTIONS FOR CWM
**I believe that around 2 MB of Internal Storage is needed to install this CWM version on the Xperia Play
1. Go to this thread ( http://forum.xda-developers.com/showthread.php?t=1390771 ) to find and download the file "CWM-Install.rar"
2. Unzip the contents of the downloaded package into a file folder where you can find it later
3. Make sure USB debugging is enabled on your phone and plug your rooted R800x into the computer via USB cable
3. Navigate to the folder on your computer where you unzipped the .rar file. (Per the above thread's instructions, you need to run the command script for "install-cwm1.cmd." You can do this by locating that file and double clicking on it. This should start a command terminal window to install CWM...just follow the prompts in the command terminal and you should have CWM installed on your phone
**In order to boot into the CWM Recovery on the Stock Kernel, you need to press the phone's Power Button and then repeatedly tap the Volume Down button as it boots up. Once you are in the CWM recovery, use the Volume keys to navigate up and down, the Home key to select, the Back key to return to the previous menu.
mattnmag said:
Cool man. That's great that you can ressurect your Xperia Play and enjoy using it again. I'm having a blast with using emulators. My friend recently introduced me to Quake and I've been playing it a lot lately. (If you have any interest in Quake, I just started a thread in the Theme and Apps section with instructions on how to get it running on the Xperia Play using the FTEDroid port and Gamekeyboard+, which allows you play it with the phone's hard key controllers). .
Anyway... I also had trouble using the Xparts app to install CWM. I found another thread that provides a command script to install it, and it's worked perfectly for me every time.
Here are some instructions that I typed up a while back when I was helping my friend root his R800x... The credit for this should go to the original poster in the thread and to all of the people who helped develop the CWM .
--------------------------------------------
INSTALL INSTRUCTIONS FOR CWM
**I believe that around 2 MB of Internal Storage is needed to install this CWM version on the Xperia Play
1. Go to this thread ( http://forum.xda-developers.com/showthread.php?t=1390771 ) to find and download the file "CWM-Install.rar"
2. Unzip the contents of the downloaded package into a file folder where you can find it later
3. Make sure USB debugging is enabled on your phone and plug your rooted R800x into the computer via USB cable
3. Navigate to the folder on your computer where you unzipped the .rar file. (Per the above thread's instructions, you need to run the command script for "install-cwm1.cmd." You can do this by locating that file and double clicking on it. This should start a command terminal window to install CWM...just follow the prompts in the command terminal and you should have CWM installed on your phone
**In order to boot into the CWM Recovery on the Stock Kernel, you need to press the phone's Power Button and then repeatedly tap the Volume Down button as it boots up. Once you are in the CWM recovery, use the Volume keys to navigate up and down, the Home key to select, the Back key to return to the previous menu.
Click to expand...
Click to collapse
Worked 100%! I owe you big time! I am now running Super Jellybean 8.0 along with Turbo Kernel and honestly the performance on this rom alone is "godly!" I first tried Racing Speed rom but reading on the features of Super JellyBean made me want to try it out. Although the touchpad support breaks (no more Mario 64...) its overall performance makes up for the loss. Either way i do use the buttons more anyways on ps1 and snes games.
I now feel like the Xperia Play "caught up" with my other devices, it was the only Gingerbread device i have touched in a year.
I would love to see the KitKat rom thats currently a work in progress someday work completely.
Since KK was said to be able to run on 512mb ram, i think it would further improve this device's potential.
That's good to hear you're rooted and unlocked and glad I could help. I know that I found it frustrating when I was trying to figure out how to root and unlock the bootloader for our Verizon version of this phone. I kept reading that you couldn't root it on build 2.3.4, but finally stumbled onto Eroot. It seems there's not a lot of Verizon R800x users in the Xperia Play threads... so we got to stick together, lol.
:thumbup:
if i unlock the bootloader i can install twrp with problems? im thinking og buying an xperia play r800x to install twrp and android 4.4.4 with cm 11 designed for xperia play
Crossvxm, can I mail you my xperia play? I wanted to know if you'd unlock the bootloader and install a custom rom. I want a more modern version of the android os running on the play. Please help
Looking for any information and help on rooting this device. Thanks in advance.
jslow3 said:
Looking for any information and help on rooting this device. Thanks in advance.
Click to expand...
Click to collapse
I managed to root this device today using king root. The first try failed. I ran it a second time and got it to work. I installed titanium backup which gave a warning that the superuser binary was functional but may cause problems. I installed supersu from the play store and tried to update the binary, which failed, even after a restart. Not sure what that means, perhaps someone more knowledgeable can tell me. I also installed other root apps, SD maid pro and rom toolbox pro, both of which seem to function as they should. I have yet to confirm root with a root checker but I intend to shortly. Hopefully this information will help with further development of this device.
The above listed method works. I did it this morning by fluke. I just tried it thinking it wouldn't work but it did. I have lollipop v 5.0.2 and the kingrooy file I downloaded was from google searching "king root" without apk. Half way down you should see the 4.6 link.
Current version is 4.6x which works on most newer mid grade phones. Then I used kingroot to SuperSU files and setup which I got from Google. Can't remember link but search kingroot to supersu and it should be the first link. Run and reboot enter supersu and update binary. You ready to install root apps, debloat, and customize. Haven't found any customs kernel, ROMs, recovery, or anything so I will be working on that soon. Keep an eye out in the near future. Unregistered user until I finish posting.
sosthenisRR
King root
King root version 4.5.0 works for Alcatel one touch conquest thank you very much. Titanium backup doesn't like the manager and anticipates problems and recommends superSU. I was unable to install the binary normally but haven't tried using the cwm or twerp option. Busybox 26 installed and I'm new to xda and will continue on the subject.
sosthenisRR said:
The above listed method works. I did it this morning by fluke. I just tried it thinking it wouldn't work but it did. I have lollipop v 5.0.2 and the kingrooy file I downloaded was from google searching "king root" without apk. Half way down you should see the 4.6 link.
Current version is 4.6x which works on most newer mid grade phones. Then I used kingroot to SuperSU files and setup which I got from Google. Can't remember link but search kingroot to supersu and it should be the first link. Run and reboot enter supersu and update binary. You ready to install root apps, debloat, and customize. Haven't found any customs kernel, ROMs, recovery, or anything so I will be working on that soon. Keep an eye out in the near future. Unregistered user until I finish posting.
Click to expand...
Click to collapse
Success! thank You
Yep, that method works great. I was looking for a.method to.root this device. The only difference was I used this link to switch from KingRoot to SuperSU
androidmtk.com/replace-kinguser-with-supersu
Thanks for the OP
Does anyone have a link to the stock firmware and or the version of Ono Touch Upgrade for this device?
Need stock rom!!
bmk072 said:
Does anyone have a link to the stock firmware and or the version of Ono Touch Upgrade for this device?
Click to expand...
Click to collapse
my device is bricked! i have the alcatel onetouch conquest 7046t for boost mobile....i read this thread and decided to do exactly what everyone who posted on the thread said to do...i i got kingroot version 4.6, and it worked on the second try....but no root apps would work... netspoof said that i might have not given it superuser permissions ( which i did...when kingroot asked i clicked allow) and titanium backup pro said it failed to get root and that it recommends supersu....i installed superuser from chains sd and tried to update the binaries, but it failed......i notcied that in superuser it said that i had root and it said something about kinguser in superuser...so it bacame clear to me that i need to switch kinguser with superuser...or supersu like titanium backup and this thread suggested
so i followed the directions and found kingroot to supersu on google and let the app "supersu me" do its thing...
while supersume was uninstalling kingroot, and installing supersu....something popped up and asked me if i wanted to delete all the files associated with kingroot...i clicked yes....and thats what i think caused my phone to brick
when it said supersu was successfully installed, i went to the app and successfully updated the binaries...right....well it told me that i should reboot the phone because i just updated the binaries so i clicked the reboot now button that the app offered me and the phone went to reboot....but stayed at the alcatel onetouch screen and all i can access is the recovery mode....in recovery logs it says something about no such file or directory for dev/tty0 or soemthing. it said it again in something about the bootloader....
so i think what happened is when i told supersu me to delete all files associated with kingroot it went ahead and deleted a bootloader file or something....normally i would just reinstall the stock rom but this damn phone is so new there isnt one online anywhere
so anyways....can anyone tell me where to get the stock rom or how to unbrick my phone.....i want to just put the stockrom on an sd card and apply it as an update to restore whatever file that is missing and keeping it from booting up....i was thinking (since i happen to have a duplicate phone) that i could make a backup of the same exact phone in twrp and put it on the sd card, switch it to the bricked phone...recovery mode...apply update from phone storage...and bam...that shoulod work! right?
the only thing is....can you put twrp on this phone yet? there is really no development on it at all
so here are the questions i need answered
does anyone have a stock rom of this phone they could put in this thread?
can i get the stock rom straight from alcatel?
has anyone got twrp or cwm recovery onto this phone
i have never bricked a phone and not been able to fix it...i refuse this to be the one
mistaweeks said:
my device is bricked! i have the alcatel onetouch conquest 7046t for boost mobile....i read this thread and decided to do exactly what everyone who posted on the thread said to do...i i got kingroot version 4.6, and it worked on the second try....but no root apps would work... netspoof said that i might have not given it superuser permissions ( which i did...when kingroot asked i clicked allow) and titanium backup pro said it failed to get root and that it recommends supersu....i installed superuser from chains sd and tried to update the binaries, but it failed......i notcied that in superuser it said that i had root and it said something about kinguser in superuser...so it bacame clear to me that i need to switch kinguser with superuser...or supersu like titanium backup and this thread suggested
so i followed the directions and found kingroot to supersu on google and let the app "supersu me" do its thing...
while supersume was uninstalling kingroot, and installing supersu....something popped up and asked me if i wanted to delete all the files associated with kingroot...i clicked yes....and thats what i think caused my phone to brick
when it said supersu was successfully installed, i went to the app and successfully updated the binaries...right....well it told me that i should reboot the phone because i just updated the binaries so i clicked the reboot now button that the app offered me and the phone went to reboot....but stayed at the alcatel onetouch screen and all i can access is the recovery mode....in recovery logs it says something about no such file or directory for dev/tty0 or soemthing. it said it again in something about the bootloader....
so i think what happened is when i told supersu me to delete all files associated with kingroot it went ahead and deleted a bootloader file or something....normally i would just reinstall the stock rom but this damn phone is so new there isnt one online anywhere
so anyways....can anyone tell me where to get the stock rom or how to unbrick my phone.....i want to just put the stockrom on an sd card and apply it as an update to restore whatever file that is missing and keeping it from booting up....i was thinking (since i happen to have a duplicate phone) that i could make a backup of the same exact phone in twrp and put it on the sd card, switch it to the bricked phone...recovery mode...apply update from phone storage...and bam...that shoulod work! right?
the only thing is....can you put twrp on this phone yet? there is really no development on it at all
so here are the questions i need answered
does anyone have a stock rom of this phone they could put in this thread?
can i get the stock rom straight from alcatel?
has anyone got twrp or cwm recovery onto this phone
i have never bricked a phone and not been able to fix it...i refuse this to be the one
Click to expand...
Click to collapse
same thing here, except I can't boot into recovery or download. fflashcustom custom twrp from the aforementioned. still won't boot into recovery, hangs at the alacatel logo. what I did was hold down volume and power til it reboots 3&4 times, than it seems to boot back to a android. I even tried the factory restore and it wouldn't do that either. *shrug* imma hafta do more research and find out wtf. but ya, that should fix your sh*t. also. and haven't found the boost stock rom yet either. it's a custom rom, it's not actually lollipop.
Alcatel Onetouch Conquest 7046t rooting, etc.
jslow3 said:
Looking for any information and help on rooting this device. Thanks in advance.
Click to expand...
Click to collapse
I couldn't find the Alcatel Onetouch Conquest 7046t listed in the list of devices on this site at all, other than in a few posts. Maybe people don't think it's a worthy device to work on? Anyway, enough of that rant, what I would like to contribute here is that I tried using kingroot for my old Motorola xt912 which I had install Dirty Unicorns KitKat ROM on successfully, but lost root on. First it said it couldn't root it, then, after trying again, said it could. I started receiving alerts from Avast staying it has detected viruses, and it seemed to install it's own version of super user, when I already had the one by chain installed.. Which struck me as suspect activity and rose yet more red flags.
I also find it suspect that the users posting here on this thread seem to only be newbies.
Any thoughts or feedback is greatly appreciated. Thanks for reading.
P.S. .. And yes, I am interested in rooting this phone, debloating it, installing custom rooms, etc.
mistaweeks said:
my device is bricked! i have the alcatel onetouch conquest 7046t for boost mobile....i read this thread and decided to do exactly what everyone who posted on the thread said to do...i i got kingroot version 4.6, and it worked on the second try....but no root apps would work...
does anyone have a stock rom of this phone they could put in this thread?
can i get the stock rom straight from alcatel?
has anyone got twrp or cwm recovery onto this phone
i have never bricked a phone and not been able to fix it...i refuse this to be the one
Click to expand...
Click to collapse
Rusty, it's possible that the reason your phone bricked is that it was not fully/properly rooted in the first place. So when SuperSu tried to Un-kingroot it, something went terribly wrong. By the way, had you remembered to turn Developer Options on and set USB Debugging on before running the KingRoot app?
Anyway, there are a couple of options to easily unbrick since you have an identical device.
Note that you can't unbrick by installing TWRP or CWM on your working device, then flashing the bricked device, UNLESS you already have the same custom recovery installed on the bricked device and can boot into that recovery. These recoveries do not provide their backups as a flashable zip, nor are they compatible with each other, which is why you need the identical custom recovery on the bricked phone.
Here is how you can unbrick your device. Go to Alcatel's website and download and install their Mobile Upgrade S software - you will find the link in the support tab for most of their models (or use Google to find it). This is the official Alcatel tool that you would use to flash their stock ROMs onto your bricked phone.
That's the easy method. But if you want a learning adventure, let's pull out your working device. Lol. Go ahead and root it with the King Root app. You may have to try several times to get it fully and properly rooted. Make sure you run a root checker app to confirm that it's rooted. Do not use the SuperSu Me utility yet.
Once you've confirmed it's rooted, install busybox. I prefer the Busy Box X app from Rob Nedi over Stericson's.
Ok, so now we want to install the MTK Droid Tools on your computer. On your phone, make sure USB Debugging is still on. Now connect your phone to the computer and let the drivers for the phone automatically install. Once the drivers are installed, run MTK Droid. It should automatically detect your phone. Next select the Blocks Map button. Then save the scatter.txt file it gives you. Make a folder somewhere because you're going to next use SP Flash Tool to backup the ROM from your phone.
Use Google and XDA to learn how to use MTK Droid and SPF. Here's a helpful link:
http://freaktab.com/forum/mtk-based-devices/mtk-phones/13919-some-useful-tools-for-mtk-phones
Once you've installed SPF on your computer and created the ROM_0 readback of your ROM, go back to MTK Droid Tools and let it break the ROM_0 down into all the partitions that are contained in the ROM. You do this on the root.backup.recovery tab of MTK Droid. Select the "To Process File ROM From Flash Tool". Note that during this process, the Tool will give you the option to create the ClowWorkMod recovery for your phone!
Once the ROM partition files are created by MTK Droid, place them in that folder you created. At this point, you can use SPF to flash the stock ROM to your bricked phone. This will unbrick your phone.
(There's an even simpler way to unbrick your phone with SPF. Instead of backing up the entire ROM of your working phone with SPF and then processing that ROM woth MTK Droid, in this case, you will just READBACK the ROM up to the recovery partition and no further. Then do a direct MEMORY WRITE of that partial ROM to your bricked phone. This will unbrick it. But this approach will not allow you to create the CWM recovery.)
Finally, once you've unbricked your phone, you can install either the Flashify or Rashr app on your phone, and use that to flash the CWM recovery image you just made with MTK Droid onto your phone's recovery partition. I usually also flash the boot_patched boot image, which was also created by MTK Droid, to the boot/kernel partition.
Long post, but I wasn't sure if you were up to an adventure. Please note that there is always a risk that you brick your working device if you make a dumb mistake along the way. It's going to be really hard to brick your working phone because you're pretty much just reading from it and not writing anything to it except when you are rooting it....but just be careful. You've been warned. Lol. But I suspect that like me, a bricked device is just a learning challenge. So enjoy.
Don't forget to thank me!
Sent from my Nexus 7 using XDA Free mobile app
I'm not a newbie y
Ya I've been doin this for awhile and have an extensive list of phones I have rooted, debloated, installed custom roms on etc....and I have never had as much trouble with a device as I have with this phone....this pos phone isn't even on their site! I got another phone from boost (same one) And did the same root method....bricked it.....but I still have the one bricked phone....waiting for a stock ROM
Ya man........get a different phone.....
mistaweeks said:
Ya I've been doin this for awhile and have an extensive list of phones I have rooted, debloated, installed custom roms on etc....and I have never had as much trouble with a device as I have with this phone....this pos phone isn't even on their site! I got another phone from boost (same one) And did the same root method....bricked it.....but I still have the one bricked phone....waiting for a stock ROM
Ya man........get a different phone.....
Click to expand...
Click to collapse
Rusty they sent that phone to you special delivery from HELL! They're just testing you, bro. Lol
But seriously, I think if you could somehow get the scatter.txt for the demon (without having to risk rooting and bricking a good one), then it would be possible to use SP Flash to simply read back the ROM of a properly working phone (up to and including the recovery partition) then simply do a direct memory write onto any bricked device. Should wake it up immediately after the flash. The only exception would be if the custpack partition had something really stupid done to it...like someone messing with the buildprop.txt file! That would put it into a head-spinning bootloop.
So the key here for this demon is for someone on this thread to post the scatter.txt file PLUS a working stock ROM. Is there anyone out there who has already successfully rooted who can post a ROM? Or at least post the scatter.txt?
Sent from my Nexus 7 using XDA Free mobile app
CVAngelo said:
Rusty they sent that phone to you special delivery from HELL! They're just testing you, bro. Lol
But seriously, I think if you could somehow get the scatter.txt for the demon (without having to risk rooting and bricking a good one), then it would be possible to use SP Flash to simply read back the ROM of a properly working phone (up to and including the recovery partition) then simply do a direct memory write onto any bricked device. Should wake it up immediately after the flash. The only exception would be if the custpack partition had something really stupid done to it...like someone messing with the buildprop.txt file! That would put it into a head-spinning bootloop.
So the key here for this demon is for someone on this thread to post the scatter.txt file PLUS a working stock ROM. Is there anyone out there who has already successfully rooted who can post a ROM? Or at least post the scatter.txt?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
i tried rooting the new alcatel the same exact way ( usb debugging was enabled both times) and ended up bricking it....i was doing this for my friend...we ended up just going to boost and telling them that there was a defect in the phone they gave him the day before and told them to give him the moto e ( which has so much developement on it its insane)
anyways my friend just gave me the other bricked alcatel one touch conquest and said that if i can fix it i can have it. so i no longer have a duplicate device to work with . can i even flash a stock rom with the original recovery ? im going to try to download the program from alcatels website like you said and see if that works
then if i get it working im going to get the program you were talking about where u said i can make a clockworkmod recovery for it....
CVAngelo said:
Rusty, it's possible that the reason your phone bricked is that it was not fully/properly rooted in the first place. So when SuperSu tried to Un-kingroot it, something went terribly wrong. By the way, had you remembered to turn Developer Options on and set USB Debugging on before running the KingRoot app?
Anyway, there are a couple of options to easily unbrick since you have an identical device.
Note that you can't unbrick by installing TWRP or CWM on your working device, then flashing the bricked device, UNLESS you already have the same custom recovery installed on the bricked device and can boot into that recovery. These recoveries do not provide their backups as a flashable zip, nor are they compatible with each other, which is why you need the identical custom recovery on the bricked phone.
Here is how you can unbrick your device. Go to Alcatel's website and download and install their Mobile Upgrade S software - you will find the link in the support tab for most of their models (or use Google to find it). This is the official Alcatel tool that you would use to flash their stock ROMs onto your bricked phone.
That's the easy method. But if you want a learning adventure, let's pull out your working device. Lol. Go ahead and root it with the King Root app. You may have to try several times to get it fully and properly rooted. Make sure you run a root checker app to confirm that it's rooted. Do not use the SuperSu Me utility yet.
Once you've confirmed it's rooted, install busybox. I prefer the Busy Box X app from Rob Nedi over Stericson's.
Ok, so now we want to install the MTK Droid Tools on your computer. On your phone, make sure USB Debugging is still on. Now connect your phone to the computer and let the drivers for the phone automatically install. Once the drivers are installed, run MTK Droid. It should automatically detect your phone. Next select the Blocks Map button. Then save the scatter.txt file it gives you. Make a folder somewhere because you're going to next use SP Flash Tool to backup the ROM from your phone.
Use Google and XDA to learn how to use MTK Droid and SPF. Here's a helpful link:
http://freaktab.com/forum/mtk-based-devices/mtk-phones/13919-some-useful-tools-for-mtk-phones
Once you've installed SPF on your computer and created the ROM_0 readback of your ROM, go back to MTK Droid Tools and let it break the ROM_0 down into all the partitions that are contained in the ROM. You do this on the root.backup.recovery tab of MTK Droid. Select the "To Process File ROM From Flash Tool". Note that during this process, the Tool will give you the option to create the ClowWorkMod recovery for your phone!
Once the ROM partition files are created by MTK Droid, place them in that folder you created. At this point, you can use SPF to flash the stock ROM to your bricked phone. This will unbrick your phone.
(There's an even simpler way to unbrick your phone with SPF. Instead of backing up the entire ROM of your working phone with SPF and then processing that ROM woth MTK Droid, in this case, you will just READBACK the ROM up to the recovery partition and no further. Then do a direct MEMORY WRITE of that partial ROM to your bricked phone. This will unbrick it. But this approach will not allow you to create the CWM recovery.)
Finally, once you've unbricked your phone, you can install either the Flashify or Rashr app on your phone, and use that to flash the CWM recovery image you just made with MTK Droid onto your phone's recovery partition. I usually also flash the boot_patched boot image, which was also created by MTK Droid, to the boot/kernel partition.
Long post, but I wasn't sure if you were up to an adventure. Please note that there is always a risk that you brick your working device if you make a dumb mistake along the way. It's going to be really hard to brick your working phone because you're pretty much just reading from it and not writing anything to it except when you are rooting it....but just be careful. You've been warned. Lol. But I suspect that like me, a bricked device is just a learning challenge. So enjoy.
Don't forget to thank me!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
strike the alcatel mobile upgrade S off the list of possibilities...
first of all.... the alcatel onetouch conquest 7046t is not even listed in supported devices, and when i downloaded/ installed mobile upgrade to my windows computer it said " pick your device " and it wasdnt listed in the dropdown menu there either
i still tried selecting the 7047 , because it was closest to 7046, and tried to run the program and it just said it was scaning my device for an ungodly amount of time
so im looking for other methods
mistaweeks said:
strike the alcatel mobile upgrade S off the list of possibilities...
first of all.... the alcatel onetouch conquest 7046t is not even listed in supported devices, and when i downloaded/ installed mobile upgrade to my windows computer it said " pick your device " and it wasdnt listed in the dropdown menu there either
i still tried selecting the 7047 , because it was closest to 7046, and tried to run the program and it just said it was scaning my device for an ungodly amount of time
so im looking for other methods
Click to expand...
Click to collapse
Uh oh! I think I see the problem here. The Conquest runs a QUALCOMM chip! All along, I've been running with the assumption that this Alcatel was running the MTK chipset. Everything I've described here is thus for naught! Those tools, like SPF and MTK Droid, only work with phones that use the MTK platform. They will not even recognize the Conquest.
My sincere apologies, but I don't even know what tools would even work with this sucker. Oh my God... I'm beside myself with embarrassment...I can't believe I made such a serious mistake.
Sent from my Nexus 7 using XDA Free mobile app
Root Alcatel conquest 7046t
Kingroot rooted mine
can the phone work with GSM sim card. i have one piece which is locked i guess coz am overseas and it doesn't work says invalid simcard
Mcrome1018 said:
Kingroot rooted mine
Click to expand...
Click to collapse
Did you get full root with KingRoot? Do your root apps actually work properly? Please confirm as others have reported that the root with KingRoot did not function properly or with all root apps.
Another question several people have is where to get the flashable stock firmware for this phone?
Sent from my Nexus 7 using XDA Free mobile app
CVAngelo said:
Did you get full root with KingRoot? Do your root apps actually work properly? Please confirm as others have reported that the root with KingRoot did not function properly or with all root apps.
Another question several people have is where to get the flashable stock firmware for this phone?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Mine all works, ad away, root browser etc no clue for firmware though