I rooted mt desire with lee driod but I am facing problem in flash contents on websites , they are not getting displayed and I am unable to uninstall and install flash player again , even if I install flash 10.1 file nothing happens
all the buttons are disabled on application management screen for that and its not working fine also ....
I want to restore to original software (HTC Original) how can I do that ...???
Karanchopra said:
I rooted mt desire with lee driod but I am facing problem in flash contents on websites , they are not getting displayed and I am unable to uninstall and install flash player again , even if I install flash 10.1 file nothing happens
all the buttons are disabled on application management screen for that and its not working fine also ....
I want to restore to original software (HTC Original) how can I do that ...???
Click to expand...
Click to collapse
This shouldn't be in the dev section.
Flash your RUU. Get it from
[ROM] Official HTC Desire RUU ROMS and OTA Update URLs
Be careful if you have SLCD screen.
Moved to Q&A. Please don't post question threads in Development.
I tried updating thru RUU
but I am getting this
that u do not have correct ROM update utility or some thimes that cannot connect to phone please check USB connection....
I want to fix flash player issue
it is not showing flash content even after installation
so i wanted to move to original version
please help I am totally frustrated with all this
wished I had never used these useless ROMs n all
plz help
Plz help guys
Karanchopra said:
I tried updating thru RUU
but I am getting this
that u do not have correct ROM update utility or some thimes that cannot connect to phone please check USB connection....
I want to fix flash player issue
it is not showing flash content even after installation
so i wanted to move to original version
please help I am totally frustrated with all this
wished I had never used these useless ROMs n all
plz help
Click to expand...
Click to collapse
flash works fine for me with leedroid, please respect the developers and there hard work, dont call there roms useless because you are too much off a noob to remove installflashplayer.apk from /system/app/ and install it manually.....
Sorry for that I did not knew these things are so important
I tried removing the file thru file manager but as it is write protected cannot be removed .... is thr ne other process to remove
Also shud I install ROM again , I hav clockmod in phone , is everything needs to be wiped out
also i tried original RUU: RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed
/but it always gives error 171 cannot detect USB connection
plz help experts
how to solve the flash prob
I removed flash n installed again also
but no success
I have a Samsung Galaxy W (i8150) that I bought from portuguese operator TMN (the only seller in Portugal for this phone). Obviously, it is strongly branded.
I would like to remove some useless (for me) applications that came installed and also the irritating operator logo at startup and shut down. Or, still better, to flash a new ROM.
I started by rooting the phone with "universal_gb_root_v17.zip" and installed Root Explorer and SuperUser from Android Market.
The Root explorer presents a button to mount the system in RW mode, but it makes nothing, not even calls SU to ask permission to access the system at root level. Trying to see attributes of any file or folder is not possible because "the system is read only" (it says).
BTW, after rooting there was an indication that "could not access system/csc/TMN/system".
The truth is that Root Explorer doesn't show this path. In system/csc there are only 4 visible files. If it really exists, it is very well hiden.
All this make me think there is some kind of lock preventing the entire system from entering write mode, even after rooting.
Assuming there is really such a lock, I have two questions:
1- Is it possible to remove it? How?
2- With the lock present, would it be possible to flash a new ROM with Odin Multi Downloader 4.43 (the version I've got) without bricking the phone? It seems that may be it is not possible for Odin to override that lock, I think...
Well, that's all. Any ideas? Any experience with this situation or similar?
I would appreciate some help from anybody. Thanks a lot
I think u dont have root access, try rooting via update.Zip
From My GWonder
Yes, yes, yes, that's it. Thanks a lot, you saved my day.
Now Root explorer has asked for root access permission to SU that has been instaled by Update.zip and the system is "turnable" to RW.
If I don´t abuse your kindness and your knowledge, do you think Odin can flash e new ROM without bricking the phone? I ask because when the phone shuts down with system on RW mode, at start up it goes back to read only.
I don´t know if starting in Odin update (vol down+home+on/off keys) the same thing hapens, preventing the loader to make the flashing.
Thanks a lot once more.
FR8148 said:
Yes, yes, yes, that's it. Thanks a lot, you saved my day.
Now Root explorer has asked for root access permission to SU that has been instaled by Update.zip and the system is "turnable" to RW.
If I don´t abuse your kindness and your knowledge, do you think Odin can flash e new ROM without bricking the phone? I ask because when the phone shuts down with system on RW mode, at start up it goes back to read only.
I don´t know if starting in Odin update (vol down+home+on/off keys) the same thing hapens, preventing the loader to make the flashing.
Thanks a lot once more.
Click to expand...
Click to collapse
if you doing it properly, it should not brick your phone. try to flash stock ROM first from http://forum.xda-developers.com/showthread.php?t=1654643
I would recommend you to install CWM first http://forum.xda-developers.com/showthread.php?t=1867870
Then do a full wipe
Before you flash the new ROM through Odin http://forum.xda-developers.com/showthread.php?t=1467128
Thank you all.
This is my first android phone and all this is new for me.
I've looked for advice from who knows before making something wrong and inutilize a beautifull phone (in all senses).
For the moment I´ve got to remove all marks from operator branding. Later maybe I flash a new ROM. I know, now, it should go without problems.
Thanks again
Hi, I recently got ATT note 2. I tried to root it and did the CF root from chainware and also tried galaxynote2root.com root. both didnt work, well it gave me root but I cant install a recoveery. I flashed it multiple times like 10 I think because my binary coutner says 10. idk what to do.Can someone help. plz post links if i need to download something. I do have all the drivers and stuff. its just that no recovery. im running 4.1.2 jelly bean
Not in any way am I trying to be rude or condescending. ...but
You need to stop and read the steps again. ...before you accidentally do damage to the device partitions or worse. ..
Custom recovery images are pushed to the device via Odin when the stock recovery still exists. ...and if done incorrectly. ..you can brick the device.
Please explain the method you are using to attempt the recovery flash. .and we can help correct the problem.
But by all means. ..don't attempt another flash of recovery until the problem is found.
Recovery is essential to do exactly as the term states. ..."recovery"...and without it. ..you will be in trouble with no way back but JTAG service.
Read and read again the recovery steps. ..and go slow here...
Your on the edge at the moment....g
gregsarg said:
Not in any way am I trying to be rude or condescending. ...but
You need to stop and read the steps again. ...before you accidentally do damage to the device partitions or worse. ..
Custom recovery images are pushed to the device via Odin when the stock recovery still exists. ...and if done incorrectly. ..you can brick the device.
Please explain the method you are using to attempt the recovery flash. .and we can help correct the problem.
But by all means. ..don't attempt another flash of recovery until the problem is found.
Recovery is essential to do exactly as the term states. ..."recovery"...and without it. ..you will be in trouble with no way back but JTAG service.
Read and read again the recovery steps. ..and go slow here...
Your on the edge at the moment....g
Click to expand...
Click to collapse
well first i downloaded the galaxynote2root zip file from the website. it gave the odin and a file to flash. then I put phone in download mode and flashed. successfully got root. I think its because I have the latest software. 4.1.2 everyone got root in 4.1.1 and the old one doesnt work anymore. what did u use to root.? I did all the steps exactly what max did. and he got root like that and installed cwm. i followed video and blog post. this is the video : http://www.youtube.com/watch?v=NFHZ535L7is
Is it better to use the toolkit that to use this method? toolkit users have had less problems.
ALSO NOW ITS DOWNLOADING SOME UPDATES WHEN I CONNECT TO WIFI. im already rooted so does that mean im going to brick if i update so im not even using the phone now plzz someone help me
thanks for reply
FIRST thing you need ro do is check and make sure you have a recovery.
Imo the number one reason noobs break there phones is with out realizing it they borked their recovery and try to root , flash a custom rom, OR take an ota.
No recovery = no ota or any other flashing.
Check you recovery by:
Power off> press vol up, menu, and home.
This is done all at once. As soon as you see the text appear in the top right corrner release. It takes a bit of practice but its not a biggie.
Now.. do you see recovery or are you in a boot loop?
If you have a boot loop while trying to get into recovery...it means u no have recovery!!!
Secondly Stop flashing root!!
Lol pick a single root method that has been verified to work by others. And stick to it.
Its sooo important to read.
In fact with some phones one variant of root wont work if you have an update and hence a different android version.
So you need to read.
If you have recovery click factory restore.
You can do this from the os or.. I prefer going into recovery and hitting factory restore. iTS THE SAME.
If you have a boot loop while trying to get into recoveru
Click my signature in web view.
Go do the kies efr thing as I explain it my tut. Get your phone back to a nice clean start.
Kies efr IS THE FASTEST AND SAFEST way for newbs to get back to stock.
Newbs should NOT be using odin unless they are 100% sure they know what they are doing and are comfortable doing so. My efr tutorial in my sig will teach you how to use KIES EFR (Emergency Firmware Recovery)
I prefer to send people the gn2 toolkit.
Its easy and also has plenty of options.
Just remember to uninstall kies first.
There are numerous ways to root.
Pick one. Lol.
sent from my T.A.R.T.I.S
(Time And Relative Tarts In Space)
Freakboy hit it on the head...
I won't try to add more into the responses, as this will just confuse the issue more...
Follow his lead, and his advice.....g
ok thanks a lot, i flashed twrp recovery now running jellybam rom, i was wondering if it supports transparent status bar? not just in one app in all of them.
The answer to that question is found in the respective thread for the rom you are using. .
Check there first. ...
General searches also yield great results. ...g
im going to switch to pac man rom soon, bc xda banned jellybam for not giving credits i think. anyway whats a good kernel to use? now im using the one that came with jellybam. im guessing u experminented a lot and give me some suggestions. i dont wanna overclock just looking for smooth performance.
For pac.....
Use the preloaded kernel ..
It is optimized for the build and you can get support ...
If you change kernels ...you may not get support ...g
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