Why TRWP is removed after every flash or reboot? - Nexus 5X Q&A, Help & Troubleshooting

I am working on my own ROM for my Nexus 5X, but i noticed when i install TRWP Recovery and i reboot my phone again that TRWP has been removed. Is this because my phone is not rooted?
Also i want to know how i can unroot my phone if i root it to do my stuff on it.

@Yzord: using the search function you would have found this thread with the same question. And your 2nd question is also answered yet many times.

You need to flash a modified boot.img or else it will restore the stock recovery every time you reboot. If you flash SuperSU, it will modify your boot.img for you.
Sent from my Nexus 5X using Tapatalk

rp158 said:
@Yzord: using the search function you would have found this thread with the same question. And your 2nd question is also answered yet many times.
Click to expand...
Click to collapse
Believe me, i am trying hard to read the forum through the (very) bad search function. But i can't seem to figure out how i do all of this. Apparently i get old topics above through the search function, because i needed to find out through Google that there is a Nexus Root Toolkit.
I am working with the Nexus Root Toolkit and did the Root option. The result was "Automated Rooting Procedure Complete" and it told me to push the SuperSu app to finish it. But i dont have a SuperSu app installed ( i do have a custom rom installed already) , and if i push busybox it tells me it has issues with opening a shell with root access.
So, i am a little bit confused. Like in the old days people are always the first to shout to use the search function of the forum, but the search function isn't really helpful. I have the phone already a week now and i really tried it to search through the forum before opening a topic. But no matter what i try, i keep unrooted (Android 7.1.1) and so i can't cook my own ROM like how easy it was in the old days.

@Yzord: reset and, as in the good old days, do it with basics, as described here. Worked flawless for me.

Happened with me too when the phone is encrypted, what i done is reset the phone or unencrypted.
Sent from my Nexus 5X using Tapatalk

Related

[Q] Problem after the new update GN

Hi,
I searched the forum but I couldn't find a similar problem, so Please I need some help.
Last week I got the new update 4.1.2 on my Galaxy Nexus gsm, so I went and installed it.
During installation when the device turned off and it was unpacking the update or even a little bit before that, I got a message which I really don't remember very much and didn't understand but i think it was from rom manager asking something maybe about flashing or something similar.
I remember as well, that it said that the action cannot be undone! and since I didn't understand very well what it was asking me, i chose something which seemed to me the safest at the time.
Which means, if it asked me to install something, I chose not to since it can't be undone.
I know I'm not giving as much information as i should but this is what happened.
After the installation was finished, I downloaded root checker to find if i had lost my root or not and it took awfully long time for the app to tell me that my device is rooted.
So, everything was okay and apps which needed root access were getting it from superuser app.
Today I decided to backup my rom so I opened rom manager premium and I was not able to backup the rom or even restart in recovery mode, so i uninstalled it and reinstalled it and I was getting always error that it was not granted superuser access.
So, i figured out that the problem is specifically with the rom manager because other app which needs root access were always getting it, so I went to titanium backup and rebooted through the app into recovery mode and it did but all i got is that black screen with the android icon in the middle having a red triangle on top. I had to take the battery off to restart the phone.
I tried again to reboot into recovery mode using the power and the volume button but I was unable to.
So, I'm asking whats the problem?
Am I still rooted? and how can i fix this problem?
I was thinking of using the nexus kit but I can't reboot in recovery mode at all so I guess it won't be much of a help.
I'm very sorry for the LONG question.
Thanks Guys
clouds73 said:
Hi,
I searched the forum but I couldn't find a similar problem, so Please I need some help.
Last week I got the new update 4.1.2 on my Galaxy Nexus gsm, so I went and installed it.
During installation when the device turned off and it was unpacking the update or even a little bit before that, I got a message which I really don't remember very much and didn't understand but i think it was from rom manager asking something maybe about flashing or something similar.
I remember as well, that it said that the action cannot be undone! and since I didn't understand very well what it was asking me, i chose something which seemed to me the safest at the time.
Which means, if it asked me to install something, I chose not to since it can't be undone.
I know I'm not giving as much information as i should but this is what happened.
After the installation was finished, I downloaded root checker to find if i had lost my root or not and it took awfully long time for the app to tell me that my device is rooted.
So, everything was okay and apps which needed root access were getting it from superuser app.
Today I decided to backup my rom so I opened rom manager premium and I was not able to backup the rom or even restart in recovery mode, so i uninstalled it and reinstalled it and I was getting always error that it was not granted superuser access.
So, i figured out that the problem is specifically with the rom manager because other app which needs root access were always getting it, so I went to titanium backup and rebooted through the app into recovery mode and it did but all i got is that black screen with the android icon in the middle having a red triangle on top. I had to take the battery off to restart the phone.
I tried again to reboot into recovery mode using the power and the volume button but I was unable to.
So, I'm asking whats the problem?
Am I still rooted? and how can i fix this problem?
I was thinking of using the nexus kit but I can't reboot in recovery mode at all so I guess it won't be much of a help.
I'm very sorry for the LONG question.
Thanks Guys
Click to expand...
Click to collapse
Try to flash recovery through fastboot from PC
polimeno said:
Try to flash recovery through fastboot from PC
Click to expand...
Click to collapse
Thanks for the answer.
Flashing recovery using what exactly? Gnexus Kit?
clouds73 said:
Thanks for the answer.
Flashing recovery using what exactly? Gnexus Kit?
Click to expand...
Click to collapse
Yeah, Galaxy nexus toolkit will work fine. You can also download the recovery (it is a .img file) and flash it manually through fastboot (fastboot flash recovery recoveryname.img)

Help ! I think i bricked my GNex!

So, i wanted to do a FULL wipe, like delete /system /data /everything i can wipe with TWRP. It's not the first time i did this, but it's the first time i did this with TWRP. When i did it with CWR, i installed a factory imaged with Gnex Toolkit and everything went smooth.
But this time, i have problems with the drivers or something, because the Gnex Toolkit can't find my device, neither does Windows, i can only hear that beep sound when i connect my phone, and that's all. The only program that recognise my phone is ODIN, wich crashes when i hit start with the official .tgz image from Google. :crying:
Guys I really don't know what to do anymore, if any of you have any idea please help me, i need this fast. Ask for any other information you need.
Thanks in advance!:fingers-crossed:
I need to transfer a flashable rar with a custom ROM so i can flash it with TWRP. A friend of mine said something about adb push but he didn't know much so i still don't know how to solve this..
Use google or efrants guide thats stickied toolkit boy
Sent from my Galaxy Nexus using Tapatalk 2
I find the problem. I was in Download mode not Fastboot when using Toolkit.. god i'm such an idiot ). Thanks anyway namtotbout.
Yes, you need .tar files, or .tar.md5 for odin. I think it's time you learn to do it with fastboot, then it's unlikely you'll need any help to recover from anything the phone can throw at you: http://forum.xda-developers.com/showthread.php?t=1626895. And you can learn about adb push, which will work in a custom recovery.
thanks to you too bodh.. I used to know all of this but i sold my GNex ~6 months ago and didn;t used Android since then, so i forgot most of these.

[Q] Rooting Question

Does anyone know if there is a more updated way or (cant think of the word for it) rooting a Samsung Galaxy SIII SGH I747? I've wanted to do it for months and months, but I was terrified of screwing something up, and when I finally over came my fear and heavily prepared, researching and everything ( different technique and all) none of them of them worked. I tried toolkits, XDA troubleshooting tips, all kinds of links and etc. I only get so far in the process where there is a quick flash of some sort in the Odin portion where you input the path from the C: drive part and stuff. I've just had so many issues. I feel like giving up so bad. But I'm not that type of person. I'M GOING tO GET THIS IF IT KILLS ME! Yesterday, I stayed on this thing from 9:00 am till 10:00 pm. Trying over and over, recapping my steps, making sure I read and reread the directions, jumping from site to site to see what other folks have tried.
I think I used quickroot method. I tried the toolkit before and it didn't work either. I finally found a correct root method in the i747 Android Development forum. Ill try to find the forum for you.
Sent from my SAMSUNG-SGH-I747 using xda premium
13 hours "trying" to root your phone with no success??? You're way over thinking it! Flash recovery to your phone through odin, then flash superuser through your newly installed recovery. Should take all of 10 minutes...
CF AUTO ROOT! It should take no more than a minute to root but it won't install a custom recovery so you'll need to use Rom Manager for CWM or GooManager to install TWRP after you root.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

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

Bootloader auto locks, can install TWRP but asks for password.

Hello,
New to the forums, I've come across a Nexus 5X that has got me stumped. I haven't had to create and post on xda-developers before because I could always find a solution. But this phone...I've even got the book (xda-developers Android Hackers Toolkit)
So I needed a Nexus 5 for a project. I went to ebay and ordered one from China/Hong Kong.
I've got TWRP installed but the device asks for a password. I've tried different versions of twrp. in the more recent version TWRP asks for a password. In earlier versions it just runs a script and reboots.
I cannot yet post links to images, being a new member.
I'm not sure what I'm doing wrong. I can run fastboot oem unlock and unlock the device. Then, if I try and flash a stock good android Nexus ROM the bootloader locks itself and reboots.
Is there something obvious I am missing? I just want to wipe the phone and install a stock nexus ROM. It's like the people who sold it have it loaded with something the prevents the phone from being wiped/modified.
I've never come across an Nexus phone that I couldn't wipe. I don't care about the data on the phone. I cannot securely use a phone if I cannot wipe it first. I can get to the bootloader and TWRP recovery. But there is no
point with TWRP because when it prompts for a password and I click cancel it runs a script, reboots and then locks the bootloader again.
Thanks
internetdenizen said:
Hello,
New to the forums, I've come across a Nexus 5X that has got me stumped. I haven't had to create and post on xda-developers before because I could always find a solution. But this phone...I've even got the book (xda-developers Android Hackers Toolkit)
So I needed a Nexus 5 for a project. I went to ebay and ordered one from China/Hong Kong.
I've got TWRP installed but the device asks for a password. I've tried different versions of twrp. in the more recent version TWRP asks for a password. In earlier versions it just runs a script and reboots.
I cannot yet post links to images, being a new member.
I'm not sure what I'm doing wrong. I can run fastboot oem unlock and unlock the device. Then, if I try and flash a stock good android Nexus ROM the bootloader locks itself and reboots.
Is there something obvious I am missing? I just want to wipe the phone and install a stock nexus ROM. It's like the people who sold it have it loaded with something the prevents the phone from being wiped/modified.
I've never come across an Nexus phone that I couldn't wipe. I don't care about the data on the phone. I cannot securely use a phone if I cannot wipe it first. I can get to the bootloader and TWRP recovery. But there is no
point with TWRP because when it prompts for a password and I click cancel it runs a script, reboots and then locks the bootloader again.
Thanks
Click to expand...
Click to collapse
"bootloop_after_lg_replaced_mainboard_bootloader reddit"
google it
https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
This is the droids guide you are looking for...
Hope this helps anyone else who lands here with the same issue.
First sorry my bad english. I guess you took wrong way.
I suggested safety and easy solution. TWRP needs password due to encrypted data partition.
If you can format userdata,TWRP require no password and you can flash any Rom.
I wish you success with your way.
Thank you for your reply.
I am following the instructions here; https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
I am stuck at the google logo. The bootloader is locked and I cannot unlock it because I cannot get the system up to enable developer tools and allow unlocking.
I don't really know what else to do.
The last resort
h ttps://ja.aliexpress.com/item/32846103543.html?spm=a2g0o.cart.0.0.74743c004Bny1g&mp=1
There is no longer anything that I can do for that.
I've managed to recover the phone using a combination for LGUP + tot files and sideloading an OTA from google.
I want to turn off encryption though... not sure how to do that..
Can you manage bootloader unlock?
O.K. following the tut of reddit thread and use fastboot tool this ver.
h ttps://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
h ttps://androiddatahost.com/265a2
Hiroki.S said:
Can you manage bootloader unlock?
O.K. following the tut of reddit thread and use fastboot tool this ver.
h ttps://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
h ttps://androiddatahost.com/265a2
Click to expand...
Click to collapse
I've tried to follow the reddit instructions. There are some missing files in the instructions where he links to xda-developers https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169
The files are not available. Same goes with Magisk Compatible phh's SuperUser not being available
Thank you though for taking the time to try and help me
h ttps://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169/page17
Hiroki.S said:
h ttps://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169/page17
Click to expand...
Click to collapse
I have that boot img and tried to flash it but nothing happens.. The phh-superuser-magisk is marked as obsolete here -> https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
thanks mate
Majisk latest
Probably no problem
Hi mate,
I managed to flash TWRP. I booted into TWRP and selected to keep the system read only. I then used 'adb push' to push Magisk to the SDCARD and successfully flashed Magisk. I can boot back into the system and I have root access. Where do I go from here? I would like to install a custom ROM
thanks mate.
OK.
So. I installed Magisk successfully. I setup the phone and rebooted into recovery. It no longer asks for a password. I was able to push a custom ROM to the SDCARD and flash using TWRP.. I have learned alot about android and the 5X in just a couple of days.
Thanks
internetdenizen said:
OK.
So. I installed Magisk successfully. I setup the phone and rebooted into recovery. It no longer asks for a password. I was able to push a custom ROM to the SDCARD and flash using TWRP.. I have learned alot about android and the 5X in just a couple of days.
Thanks
Click to expand...
Click to collapse
Everyone goes through the same thing.
Cheers.

Categories

Resources