Develop Bugs

Trying to Root - Driver install issue

I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer

Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.

I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app

Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .

What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.

Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little

Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.

So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck

The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there

Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now

Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...

i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.

Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok

Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250

Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier

The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!

I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus

The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks

The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT

[Q] Please help a Noob

OK. I think I've done my due diligence. I've scrubbed the forums for 2 days, I've googled it and I still can't figure out what I'm doing wrong.
Friend gives me this rooted LG OGP. Awsome! Works great! Then AT&T or LG sends an OTA update that bricks it :crying:. Read Aryan1312's sticky thread in this forum and get all pieces together. By now I have the 3.8.1 drivers AND the newest 3.10.1 drivers, LGFlashTool 1.8.1.1023, along with the newest 10P TOT file. I got the Flashtool to stop asking for PW and I think I'm ready to go.
But then . . . Plug my phone in and Device Management doesn't know what to do with phone. Reinstall drivers pack from LG website. Still no dice. Hmm. Phone is in Team Win Recovery Project v2.6.3.0 recovery screen (I guess that's what it's called) and computer doesn't know what to make of it. Hmm.
Maybe I can put it onto a microSD card and copy stuff over to phone? Maybe flash a different ROM through TWRP? Let's try that. I copy files over to the external SD card, put it into the phone, restart phone, hello TWRP, Advanced-File Manager option, WHY CAN'T YOU SEE THE EXTERNAL SDCARD??? Isn't it supposed to be there under /extSD?? It's time to ask for help.
Question: How do I get my Win7 PC to see the phone as a removable drive/external drive/whatever you call it so that I can get this info over?
I know that I have to change Port #'s after Win7 sees the phone. I just can't get there . . . yet.
- What I've tried:
Reinstalled drivers (both versions) and restarted between trying to plug phone in.
Tried installing phone drivers manually. Still doesn't mount as external HD as far as Win7 is concerned.
Called friend to ask his opinion. He doesn't remember and tries to tell me this is why Apple is "better".
Scoured the web to see what to do. Found articles about this same thing happening and all point to Stickied Post on this XDA forum
I did RTFM and am still lost.
---- Sorry for the long post, I just thought that people who wouldn't mind helping would appreciate the extra info.

Drivers
landran said:
OK. I think I've done my due diligence. I've scrubbed the forums for 2 days, I've googled it and I still can't figure out what I'm doing wrong.
Friend gives me this rooted LG OGP. Awsome! Works great! Then AT&T or LG sends an OTA update that bricks it :crying:. Read Aryan1312's sticky thread in this forum and get all pieces together. By now I have the 3.8.1 drivers AND the newest 3.10.1 drivers, LGFlashTool 1.8.1.1023, along with the newest 10P TOT file. I got the Flashtool to stop asking for PW and I think I'm ready to go.
But then . . . Plug my phone in and Device Management doesn't know what to do with phone. Reinstall drivers pack from LG website. Still no dice. Hmm. Phone is in Team Win Recovery Project v2.6.3.0 recovery screen (I guess that's what it's called) and computer doesn't know what to make of it. Hmm.
Maybe I can put it onto a microSD card and copy stuff over to phone? Maybe flash a different ROM through TWRP? Let's try that. I copy files over to the external SD card, put it into the phone, restart phone, hello TWRP, Advanced-File Manager option, WHY CAN'T YOU SEE THE EXTERNAL SDCARD??? Isn't it supposed to be there under /extSD?? It's time to ask for help.
Question: How do I get my Win7 PC to see the phone as a removable drive/external drive/whatever you call it so that I can get this info over?
I know that I have to change Port #'s after Win7 sees the phone. I just can't get there . . . yet.
- What I've tried:
Reinstalled drivers (both versions) and restarted between trying to plug phone in.
Tried installing phone drivers manually. Still doesn't mount as external HD as far as Win7 is concerned.
Called friend to ask his opinion. He doesn't remember and tries to tell me this is why Apple is "better".
Scoured the web to see what to do. Found articles about this same thing happening and all point to Stickied Post on this XDA forum
I did RTFM and am still lost.
---- Sorry for the long post, I just thought that people who wouldn't mind helping would appreciate the extra info.
Click to expand...
Click to collapse
1. Is the first pic with the phone connected to the pc?
2. If yes, have you tried to manually update drivers, while in device manager
3. I know that this is going to sound funny but have you tried a different USB port. The reason I ask is I had the same problem LG Optimus M and the phone was down for a couple of days. I tried everything and was about to call it quits but for some reason when I changed USB port the computer saw the phone and I was back in business. I am not saying that will 100% work but it is worth a try.

TheMighyLoki said:
1. Is the first pic with the phone connected to the pc?
2. If yes, have you tried to manually update drivers, while in device manager
3. I know that this is going to sound funny but have you tried a different USB port. The reason I ask is I had the same problem LG Optimus M and the phone was down for a couple of days. I tried everything and was about to call it quits but for some reason when I changed USB port the computer saw the phone and I was back in business. I am not saying that will 100% work but it is worth a try.
Click to expand...
Click to collapse
Yes I have. I think I did figure it out though. I put the device into "download mode" and my computer could see, and communicate, the phone.
To put my phone into "download mode" I did the following:
I connected the phone to the computer physically with USB cable
I turned phone off.
I pressed BOTH volume buttons and held the power button while phone was attached to computer.
With BOTH volume buttons still pressed, I released the power button.
The phone screen was black with a little dialog box in the middle saying "download mode"
I could then use LGFlash Tools to flash Stock AT&T TOT file back into phone. Took 519 seconds to complete the stock flash.
New problem arises, After flash, I do NOT have any 3G/4G signal. I can use the phone to make and receive phone calls and text messages, but I CANNOT use mobile internet unless I have it connected via wifi.
I installed the Debloated ROM and "tried" to flash 980 Baseband.zip but when I tried to install baseband, CWM gave me a permission error and said install failed. I haven't been able to use mobile internet since. Any help???
-- Again, sorry for the lengthy post. I figured that I might not be the only person who has gone through this. I see a lot of viewers to the thread so I think other people might be having same troubles as me.

landran said:
New problem arises, After flash, I do NOT have any 3G/4G signal. I can use the phone to make and receive phone calls and text messages, but I CANNOT use mobile internet unless I have it connected via wifi.
I installed the Debloated ROM and "tried" to flash 980 Baseband.zip but when I tried to install baseband, CWM gave me a permission error and said install failed. I haven't been able to use mobile internet since. Any help???
-- Again, sorry for the lengthy post. I figured that I might not be the only person who has gone through this. I see a lot of viewers to the thread so I think other people might be having same troubles as me.
Click to expand...
Click to collapse
It sound like you need to manually set the APN. Do a Search for your provider.. ie AT&T T-Mobile the setting is under Network/Tethering & Networks/ Mobile networks/ Access point name/ Hit Menu Button and New APN

You are the MAN / WOMAN!! Thanks for the help. That fixed it.
For posterity and to help another "noob" stuck in my case later (maybe months down the line)
This is what I've done up until now in plain text:
Used LGFlashtool to flash AT&T stock "10k" build
Went into Settings Icon>General>Developer Options>check off "USB Debugging"
Used "E980 Universal Root" from forums to gain Root access (verified with "Root Checker" from Playstore)
Used FreeGee to get TWRP recovery installed (rebooted into recovery with "QuickReboot" from Playstore).
Used TWRP recovery to install "E980 Baseband.zip" from forums
Factory Reset
Setup new phone and input APN settings (located in Settings Icon>Networks>Tethering & Networks>Mobile networks>Access point names>Menu button "New APN"/input carrier values/Menu button "Save")
Now that I know how to get back here, I'm going to scrap the stock ROM and try to do this whole process with a custom ROM. . . and another flash-a-holic is born. The learning journey continues.

Welcome:beer:
*KCCO*2SHAYNEZ*E980*

That is what this forum is for.
I have been helped out a lot from the group and I just thought it was time to pay it back. It is good to hear that you got it up and running. But one last word of advise BACK UP, BACK UP, BACK UP, and when that is done, back up the back up to the computer.

[Q] Serious help fast!

ok so heres what happened. forgot my phone was rooted. i tried tmobile ota update. kicked me out into twrp. i messed aroun and bascily now i have no os or anything. i accidentally formatted everything in the phone. its the white 32gb tmobile version if that matters. to make things worse, i use ubuntu 14.04 LTS. no windows. cant even figure out how to get windows on the pc. and no i cant go buy it. noodle budget. i also messed with the fat32 thing and it said unable to make fat32 partition. basicly. its screwed. i need to know what to do about this. i have the lg flash tool, the original .dll and .tot ready to go. but theres the linux thing. everytime i try to connect it to the computer in download mode it said could not mount adroid device or something like that, now it wont even come on for me. i dont know what to do about this. no i couldnt get adb sideload to start, i couldnt mount in download mode, i could get adb to recognise the device but thats about it. i pushed a couple roms to it but nadda. after installing succesfully it just went right back to twrp. i need a video or something that i can slightly understand on how to fix this.

Your best bet is to set up a virtual box and virtualize it. I guess in twrp if you can still get access to it. Is to wipe system and all that fun stuff so it can reformat it to ext4 then try to adb sideload the rom that matches the update as close as possible. The only thing I can think of is that the update messed up partitions so when you flash a rom it can't all fit like it used too.
Sorry if I didnt help I'm just trying my method I had to do when I had my g2
Sent from my HTC One_M8 using XDA Free mobile app

NexusBarry said:
ok so heres what happened. forgot my phone was rooted. i tried tmobile ota update. kicked me out into twrp. i messed aroun and bascily now i have no os or anything. i accidentally formatted everything in the phone. its the white 32gb tmobile version if that matters. to make things worse, i use ubuntu 14.04 LTS. no windows. cant even figure out how to get windows on the pc. and no i cant go buy it. noodle budget. i also messed with the fat32 thing and it said unable to make fat32 partition. basicly. its screwed. i need to know what to do about this. i have the lg flash tool, the original .dll and .tot ready to go. but theres the linux thing. everytime i try to connect it to the computer in download mode it said could not mount adroid device or something like that, now it wont even come on for me. i dont know what to do about this. no i couldnt get adb sideload to start, i couldnt mount in download mode, i could get adb to recognise the device but thats about it. i pushed a couple roms to it but nadda. after installing succesfully it just went right back to twrp. i need a video or something that i can slightly understand on how to fix this.
Click to expand...
Click to collapse
Same situation happen to me, Im praying for someone to give me debrick.img so I can boot this G3 . This SD Card method but we need a working LG G3 that can give us that debrick file
http://forum.xda-developers.com/showthread.php?t=2660566

help fast!
xmagiicsx said:
Same situation happen to me, Im praying for someone to give me debrick.img so I can boot this G3 . This SD Card method but we need a working LG G3 that can give us that debrick file
http://forum.xda-developers.com/showthread.php?t=2660566
Click to expand...
Click to collapse
i dont have any windows keys nor any way to get it. so can u explain have to use virtual box to do that?

Just download a Windows img either that or use wine to emulate Windows apps on Ubuntu is a secondary option
Sent from my HTC One_M8 using XDA Free mobile app

This is my situation as well. No OS. Can't get a ROM to flash successfully via SD card. Bumping this thread for some serious assistance. What do we do?

weekendbiggs said:
This is my situation as well. No OS. Can't get a ROM to flash successfully via SD card. Bumping this thread for some serious assistance. What do we do?
Click to expand...
Click to collapse
Did you read the suggestions that were given in the thread?

doktor buknasty said:
Did you read the suggestions that were given in the thread?
Click to expand...
Click to collapse
you should be able to download a windows 7 and use for 30 days for free. after 30 days, you still can extend it to another 30 days. that should be enough to get you phone back

Wow... reading OP was like a mirror into my own experience except I am on W81 I have tried in every way imaginable to fix this issue with LG Flashtool and it constantly tells me that it can't boot into download mode even though it is already set into it. What other options are there to fix things? I am at wits end..

nekoarashi said:
Wow... reading OP was like a mirror into my own experience except I am on W81 I have tried in every way imaginable to fix this issue with LG Flashtool and it constantly tells me that it can't boot into download mode even though it is already set into it. What other options are there to fix things? I am at wits end..
Click to expand...
Click to collapse
You must have Windows Virtual Box if running Linux, Ubuntu, Solaris, or Mac. Start HERE. It can be tricky for some, you may want to read this whole page before attempting.
sent from my LG G3

joeyhdownsouth said:
You must have Windows Virtual Box if running Linux, Ubuntu, Solaris, or Mac. Start HERE. It can be tricky for some, you may want to read this whole page before attempting.
sent from my LG G3
Click to expand...
Click to collapse
I don't need a VM I have windows 8.1 installed native on my PC.

nekoarashi said:
I don't need a VM I have windows 8.1 installed native on my PC.
Click to expand...
Click to collapse
I misread, sounds like driver issue, have you tried to see if phone is recognized in ADB?
sent from my LG G3

[Q] Help!! Firmware gone and PC doesnt recognize my M9!!

I installed recovery to root my HTC One M9 yesterday. It seemed like I made some mistakes and now my firmware is totally gone and my computer doesn't recognize my phone anymore. However I still have access to recovery and I want to know if installing a Rom via SD-card is possible or not. If not, what should I do? Any help will be very appreciated. Thanks!!!

What recovery do you have access to? If it's twrp then yes you can load from sd card.. Have you tried an RUU for your phone? That should work as well.

enchanter100 said:
What recovery do you have access to? If it's twrp then yes you can load from sd card.. Have you tried an RUU for your phone? That should work as well.
Click to expand...
Click to collapse
Hello! Recovery I installed was PhilZ Touch CWM. I'm trying right now! Thanks.

Hi .. I think I made things confused a bit. What I meant by SD-card was external micro SD-card. Thanks!

Not sure what you mean by firmware. This is what you need to do:
Install the latest version of adb. Go to recovery, turn on sideload mode.
in cmd prompt-> adb sideload *location/name of rom.zip* e.g. c:\users\xxx\rom.zip
Restart and bam you are done

MadScientist2015 said:
I installed recovery to root my HTC One M9 yesterday. It seemed like I made some mistakes and now my firmware is totally gone and my computer doesn't recognize my phone anymore. However I still have access to recovery and I want to know if installing a Rom via SD-card is possible or not. If not, what should I do? Any help will be very appreciated. Thanks!!!
Click to expand...
Click to collapse
Does the computer recognize the phone in bootloader/fastboot/download mode? If you can enter recovery and download mode, then your phone is probably working fine (except for not having a working ROM) and your computer should see your phone on some level.
Are you using WIndows? I think you might need to get your device drivers on your computer working. Check Device Manager if you're in windows. With your phone connected, you should have 2 devices. One should be under a section called Android USB Devices (might be called My HTC) and the other is going to be under Portable Devices section (might be called HC One M9). If you don't have both, then you need to work on your driver issue on your computer.
Edit: Sorry if this is blunt, but since you seem to not really know some very basic terminology, i recommend that you do a LOT of reading on this forum so you can have a better understanding of what's going on with your device and how to solve your problem. I know you might feel like youre in panic-mode because your device won't boot, but you're going to get into more trouble if you just start trying a bunch of "solutions" without having any understanding of what you're doing. I know, because I've been there before.
Edit2: Also, it would help to steer you in the correct direction if you listed your location and carrier info

MadScientist2015 said:
Hello! Recovery I installed was PhilZ Touch CWM. I'm trying right now! Thanks.
Click to expand...
Click to collapse
FIRST THING, install TWRP 2.8.6.4, you can find it on captian_throwbacks thread here,

Aldo101t said:
FIRST THING, install TWRP 2.8.6.4, you can find it on captian_throwbacks thread here,
Click to expand...
Click to collapse
Actually, the beta version 2.8.6.4 is not recommendet anymore. Captian_Throwback now recommends using the official version 2.8.6.1. (Sidenote: The version number of the official one is lower because the numbering of the beta version is unofficial.)

Root method for Alcatel OneTouch Conquest 7046t

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