Related
I know that this handset is not release yet but I'd like to know if there would be support for it from the community. I'm excited about it because I've been waiting for a handset that seems to meet all my niche requirements:
Medium size screen (4.5")
ARMv8 instruction set (Snapdragon 410)
Removable battery (According to quick set up manual)
MicroSD slot (full size SD would have been nice but this is good enough)
Dual Sim (not sure if it will be available in the UK though )
I know the screen is not the best and it probably won't support Qi charging but I don't think any other handset has all the aforementioned features. I'm not trying to sell the handset but this is in anticipation of posts like "why not get a Nexus" or "just get a Moto G"
It's a nice phone, I bought one for my wife
This one is not available in my region. I got the Y550 instead for a relative. Almost the same spec. Not sure about IO performance though as I didn't have time to check.
Solution?
So, I was searching Google for OT 5042 root (the internal name of Alcatel OT Pop 2 or Orange Roya (NOS Roya in Portugal)), and I've found these instructions on a russian forum. I have not tested them myself, but they do seem very legit, so if anyone who knows exactly what he's doing or has no fear of losing the phone can follow it up.
Disclaimer: The procedure that follows has not been yet tested by me. Proceed at your own risk. You are fully responsible for what happens to your phone from now on. If you have some knowledge on russian, please help translating the board mentioned on the Youtube video description (/watch?v=8tD4kR33vVE).
Note on translation: This post was initially writen in russian and translated with Google translate with some fixes here and there made by me. I'm not a native english speaker and therefore some engrish may be present. Please forgive me for it.
Note to users: This tutorial is regarding the dual SIM version of this phone. It may not work with the single SIM one.
Root dual SIM Alcatel Alcatel OneTouch 5042D POP 2 smartphone
Author: ruslan_3_ from 4pda.ru
Procedure:
1. Download the attached .zip file and extract it to some folder on your computer.
1.1. Install the phone's adb drivers (not needed under Linux or OS X; Windows drivers are available on the phone as a CD-ROM);
1.2 Copy update.zip to the root of your phone's internal memory or SD Card (one of the two may not work, and there is different feedback regarding this issue)
2. Turn on USB debugging
3. Turn on the phone in fastboot mode (press and hold both power and volume down buttons);
3.1 Connect the phone to your computer and wait for the drivers to finish installing (when applied);
4. Open a command prompt where you first extraced the files and type:
HTML:
fastboot -i 0x1bbb devices
It will list all devices connected to the computer on fastboot mode, for example a409dc4d.
6. Install CWM Recovery:
HTML:
fastboot -i 0x1bbb flash recovery image-new.img
7. Enter recovery mode (power + volume up)
8. Install update.zip
Once again, please be very carefully when executing this procedure. It can go really wrong.
If you're using Mac or Linux, paste the specific android SDK tools in the extracted folder and run fastboot with the command ./fastboot if you don't have an alias for it in your .profile or .bashrc (if you don't know what this is, ignore it ).
@imTos, Thanks for information, but you know if there is any custom rom (CM or MIUI) for this equipment, specifically for the version of the 5042A one SIM ??
Thank You ...
Regarding the root procedure, I was told on a portuguese board that it works for any 5042 model.
herbesi01 said:
@imTos, Thanks for information, but you know if there is any custom rom (CM or MIUI) for this equipment, specifically for the version of the 5042A one SIM ??
Thank You ...
Click to expand...
Click to collapse
Hey. I am not aware of any alternative ROM currently on the Internet, especially since Alcatel has not released the phone's source code yet. What I do know, however, is that there are three ROMs for this device: Alcatel's original ROM (build 010 03 single/dual SIM), Orange ROM (single SIM) and the portuguese NOS ROM (build 010 06, single SIM). Between the three, as far as I know, the portuguese one is the one that most ressembles AOSP w/ Google Play and with no bloatware installed by default, from what I've seen in pictures. I don't know if it is possible for the users of the different ROMs to make NANDroid backups and share them online, though it wouldn't be a full help. Keep in mind that both chinese and russian ROMS, from what I've read (and I have no way to confirm if this is true or not!), have a function to report stolen phones, and this text messages a foreign number if you're living outside these countries.
Offtopic: I waste more time trying to guess the captcha than replying to a post. Google, where's the new noCaptcha function?
imTos said:
So, I was searching Google for OT 5042 root (the internal name of Alcatel OT Pop 2 or Orange Roya (NOS Roya in Portugal)), and I've found these instructions on a russian forum. I have not tested them myself, but they do seem very legit, so if anyone who knows exactly what he's doing or has no fear of losing the phone can follow it up.
Disclaimer: The procedure that follows has not been yet tested by me. Proceed at your own risk. You are fully responsible for what happens to your phone from now on. If you have some knowledge on russian, please help translating the board mentioned on the Youtube video description (/watch?v=8tD4kR33vVE).
Note on translation: This post was initially writen in russian and translated with Google translate with some fixes here and there made by me. I'm not a native english speaker and therefore some engrish may be present. Please forgive me for it.
Note to users: This tutorial is regarding the dual SIM version of this phone. It may not work with the single SIM one.
Root dual SIM Alcatel Alcatel OneTouch 5042D POP 2 smartphone
Author: ruslan_3_ from 4pda.ru
Procedure:
1. Download the attached .zip file and extract it to some folder on your computer.
1.1. Install the phone's adb drivers (not needed under Linux or OS X; Windows drivers are available on the phone as a CD-ROM);
1.2 Copy update.zip to the root of your phone's SD Card (internal memory may not work)
2. Turn on USB debugging
3. Turn on the phone in fastboot mode (press and hold both power and volume down buttons);
3.1 Connect the phone to your computer and wait for the drivers to finish installing (when applied);
4. Open a command prompt where you first extraced the files and type:
HTML:
fastboot -i 0x1bbb devices
It will list all devices connected to the computer on fastboot mode, for example a409dc4d.
6. Install CWM Recovery:
HTML:
fastboot -i 0x1bbb flash recovery image-new.img
7. Enter recovery mode (power + volume up)
8. Install update.zip
Once again, please be very carefully when executing this procedure. It can go really wrong.
If you're using Mac or Linux, paste the specific android SDK tools in the extracted folder and run fastboot with the command ./fastboot if you don't have an alias for it in your .profile or .bashrc (if you don't know what this is, ignore it ).
Click to expand...
Click to collapse
this method for root work very well on my Orange Roya
thanks for share it
Worked like a charm on single sim
I would love to see running android l on this device! i mean into 5042a
Please
Hi, i did try to root this phone as you show but after some tries this stuck on load, and dont turn on ok...
i did try hard reset, wipe cache, wipe data, erase from fastboot and a lot of things but always keep on Logo... so could you do a backup from your handset and share it with me please?
i will apreciate it a lot. thanks in advance
I've asked for a backup in many online communities, but no luck. As I said, I didn't try the method myself since I didn't need to use root yet and my phone is still under warranty. Sorry.
imTos said:
I've asked for a backup in many online communities, but no luck. As I said, I didn't try the method myself since I didn't need to use root yet and my phone is still under warranty. Sorry.
Click to expand...
Click to collapse
lol mine is under warranty too.
Root it and if u need to send to warranty u can use Mobile Upgrade Q to restore original firmware.
I cant enter in fastboot can anyone help me please
rushwhq said:
lol mine is under warranty too.
Root it and if u need to send to warranty u can use Mobile Upgrade Q to restore original firmware.
Click to expand...
Click to collapse
Are you sure that can be restored By mobile upgrade?
if bricked : recover phone using Alcatel official tool
Mobile Upgrade Q 4.6.8 Setup.rar
goto http://www.alcatelonetouch.com/global-en/products/smartphones/pop_2-4-5.html
and select the "Support" tab, there download
Mobile Upgrade Q 4.6.8 Setup.rar
link:
http://www.alcatelonetouch.com/glob...OP_2-4-5/otu/mobile-upgrade-q-4-6-8-setup.rar
unrar, start and select 5042D, connect phone via USB cable, start flashing
I had my Pop 2 bricked (eternal boot loop) but got it back to life, 100%
---------- Post added at 10:10 PM ---------- Previous post was at 10:05 PM ----------
in the "russian" tutorial they tell you to copy "update.zip" to your SD card - that did not work for me !
- on the external card cwm did not find the file.
instead update.zip was only found once it was on the INTERNAL SD card !!
Hey guys.
I've found very useful information like stock recovery, stock images, and user custom images for this device on the same board I found the root method. I still haven't had the courage to root my device, though, and I feel kind of an hypocrite because of it, but this is my only phone, and if something had gone wrong I would have no money to buy a new one. I know I'm not the only one in this situation, and I do feel really bad for not helping users that have requested for my help.
I need to know if Mobile Upgrade Q can recognize the device and reinstall the ROM if anything goes wrong. To those who had any problem, was it able to fix it? Were you using stock recovery or CWM when you tryed it (I'm not sure if this is relevant)?
I will update this board (or create a new one?) regarding this device with useful information I've found online, and since stock recovery is already available (that was the main reason I didn't root in the first place (warranty)), I will provide a (not rooted) factory image of the custom build 010 06 when I have time to do so.
hey buddy
i restore my to thr original rom with mobile q. but looks like i upgrade the firmware, and now i cant root again, because i cant put in fastboot "vol - + pwr".
Which exactly build do u have ?
imTos said:
Hey guys.
I've found very useful information like stock recovery, stock images, and user custom images for this device on the same board I found the root method. I still haven't had the courage to root my device, though, and I feel kind of an hypocrite because of it, but this is my only phone, and if something had gone wrong I would have no money to buy a new one. I know I'm not the only one in this situation, and I do feel really bad for not helping users that have requested for my help.
I need to know if Mobile Upgrade Q can recognize the device and reinstall the ROM if anything goes wrong. To those who had any problem, was it able to fix it? Were you using stock recovery or CWM when you tryed it (I'm not sure if this is relevant)?
I will update this board (or create a new one?) regarding this device with useful information I've found online, and since stock recovery is already available (that was the main reason I didn't root in the first place (warranty)), I will provide a (not rooted) factory image of the custom build 010 06 when I have time to do so.
Click to expand...
Click to collapse
---------- Post added at 09:17 AM ---------- Previous post was at 08:32 AM ----------
lol i managed to enter fastboot mode via adb command.. =D
hi, mi alcatel pop 2 wass bricked. When I try to unbrick with Mobile Upgrade it say that my phone is updated and it stop.
how can i unbrick my phone??!!
Please a need a backup from a Alcatel POP 2 ROM, i had bricked. Please could anyone upload it?
seryioo write me PM
---------- Post added at 06:26 AM ---------- Previous post was at 06:11 AM ----------
imTos said:
Regarding the root procedure, I was told on a portuguese board that it works for any 5042 model.
Hey. I am not aware of any alternative ROM currently on the Internet, especially since Alcatel has not released the phone's source code yet. What I do know, however, is that there are three ROMs for this device: Alcatel's original ROM (build 010 03 single/dual SIM), Orange ROM (single SIM) and the portuguese NOS ROM (build 010 06, single SIM). Between the three, as far as I know, the portuguese one is the one that most ressembles AOSP w/ Google Play and with no bloatware installed by default, from what I've seen in pictures. I don't know if it is possible for the users of the different ROMs to make NANDroid backups and share them online, though it wouldn't be a full help. Keep in mind that both chinese and russian ROMS, from what I've read (and I have no way to confirm if this is true or not!), have a function to report stolen phones, and this text messages a foreign number if you're living outside these countries.
Offtopic: I waste more time trying to guess the captcha than replying to a post. Google, where's the new noCaptcha function?
Click to expand...
Click to collapse
Hi
Alcatel has release the source code for this model
OT_5042X_20150310.tar.xz
So now can cook some cm rom or anyelse?
rushwhq said:
seryioo write me PM
Click to expand...
Click to collapse
Hi, I have bricked my phone. I tried to restore with Mobile Upgrade and with a Backup from CWM that I did, but with no result.
I would like you did a backup with the last version of TWRP, all partitions and upload:
Download, install like CWM: https://mega.co.nz/#!tQRzibAA!7tPkqlc1BYsvCCeQRzaqn_VVs959GBsleB_4eNVq9JE
Sources TWRP Recovery: http://4pda.ru/forum/index.php?showtopic=645507&st=340#entry38938719
Thank you.
i don't know what to do... i think i read every tutorial for unbrick my phone but nothing works...
my situation:
-i unlocked my fone by unnoficial method, instaled twrp and everything was ok.
i decided to instal sMIUI, but nowhere i read that is necesary to delete emmc file... so i bricked my phone.
bootloader got relocked, i can't turn on my phone, mi logo appears during 1 sec > screen off > again mi logo during 0.001s > screen off
when i plug in my phone into my pc, i have black screen and red led, but it's not adb mode.
i can't enter adb, my pc (windows 10 x64), i use command "adb devices" and list is empty
i can't edl
i can enter in fastboot mode.
i can't flash nothing, "failed: device is locked"
anyone can help me?
if i unlock officialy my bootloader, can i flash again stable rom or something? i just had my phone during 2 weeks.
can i do anything?
thanks.
one more thing: i had guaranty, so, if i unlock my bootloader officialy, i lose it?
i don't want to try testpoint method, because of guaranty.
Well, welcome to the party.
Irrespective of how much u search, cry for help or open millions of threads like this instead of doing a little search, there is no solution except test point method. Now don't ask how to do it. Search and read a little u will get the necessary info.
sanjib734 said:
Well, welcome to the party.
Irrespective of how much u search, cry for help or open millions of threads like this instead of doing a little search, there is no solution except test point method. Now don't ask how to do it. Search and read a little u will get the necessary info.
Click to expand...
Click to collapse
thanks a lot for this kind help, i will do it, don't worry. :good:
Don't worry bro u will certainly do what is required. I was the first who reported a bricked device while unlocking bootloader by unofficial method. After extensive search and trying different methods I came to this conclusion.
Can any developer please please help me out quickly? i'm out of time seriously I need help but quick.
I'm trying to unlock my device Redmi Note 3 Snapdragon varient. All the other commands like
* adb devices
* adb reboot edl
* fastboot devices
* fastboot oem device-info
everyone of it is working fine but when I write
* fastboot oem unlock-go
I get the above mentioned error.
Does anybody know the solution to it? Before answering please consider that other commands are working except this one, I didn't found any proper solution that's why posted the problem here and I already did revoke USB debugging permissions and turned it on again but that didn't helped.
So please give me a working solution as quick as possible or else any help is appreciable.
enable oem unlock in developer options
Enable OEM Unlock option in Developer Options.
caesar13th said:
enable oem unlock in developer options
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
superboy123 said:
Enable OEM Unlock option in Developer Options.
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Gurkirat_Singh said:
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Click to expand...
Click to collapse
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
superboy123 said:
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
Click to expand...
Click to collapse
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Gurkirat_Singh said:
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Click to expand...
Click to collapse
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
superboy123 said:
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
Click to expand...
Click to collapse
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Gurkirat_Singh said:
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Click to expand...
Click to collapse
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
Thanks for all the support and help you gave me.
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
caesar13th said:
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Gurkirat_Singh said:
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Click to expand...
Click to collapse
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
superboy123 said:
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
Click to expand...
Click to collapse
I appreciate your help but the post you gave me is for non-asian countries so it will not work for me. As you already know I'm an Indian so that's why. Are you an Indian, only asking cause in that way you may already faced the problems i'm having.
I'm only familiar with only 2 4G networks for now. One is Airtel 4G, what they say have FDD LTE network, I don't what that is, but that's why it's not working on my phone, I contacted them and they said that my phone doesn't support it, I don't know why cause it support much more LTE Bands other than any smartphone in that price range. Second is Jio 4G, my sim gets detected, shows network in manual selection but doesn't get registered on them. I see only the message of 'No Service' or 'Emergency calls only' when I insert it.
@Gurkirat_Singh
It worked for me.
I had the same problem!
superboy123 said:
@Gurkirat_Singh
It worked for me.
I had the same problem!
Click to expand...
Click to collapse
What worked for you and how? Can you please answer/clarify my questions/doubts please also?
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
superboy123 said:
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
Click to expand...
Click to collapse
OK I'll try when got time and will update you with the result.
Hi @all,
Since a failed update, the ROM of my Hisense A2 just contains Chinese and English as selectable languages and no more german language and no Google Play Store anymore.
Meanwhile I've got a stock-rom from the chinese seller from 2017/05 (as I hope in multilingual and containing Google Play Store) for my Hisense A2.
But unfortunately I don't know what to do with this file.
It is not a "A2.img"-file but a rar-archive that contains some .bin, .img, .dat, .html, mbn and .xml-files.
Could someone explains, what to do with?
Have searched the web and found ADB as possibility to bring the new ROM onto my device.
Learned, just the .img-files are important and the rest is useless to me.
So I installed ADB and fastboot in V 1.43 (from: https://forum.xda-developers.com/showthread.php?t=2588979 ) for updating the .img-files.
"adb devices" give the serial number
"fastboot devices" also displays the serial number
but next order "fastboot flashing unlock" displays an error "FAILED (remote: unknown command)"
So my efforts are blocked at this point and I can't install the boot.img (10MB), ramdisk.img(1,7MB), recovery.img(11MB) and system.img(3,6GB)
Could someone help me to bring this ROM onto my Hisense A2, please?
It is really important to me, to get german language and Google Play Store back onto my smartphone.
Can I just copy the system.img into the root of the SD-Card and restart the smartphone with presses "Vol Up" key?
What's with the other files like boot.img and recovery.img?
If someone wan't to get this ROM also, I can upload it somewhere.
Will be very thankful, if someone could help me.
Kind regards
Veronika
Hi! Please upload this rom and send url to me!
Thanks!
Did you find any answers on how to install the rom? Can you upload the rom somewhere and send me the link?
hi,
all necessary files and manual how to install the firmware you will find now at:
https://forum.xda-developers.com/general/rooting-roms/flashing-rom-hisense-a2-qpst-t3673945
good luck?
Could help wit hisense A6？
As in the title, I have an, Alcatel Tcl Lx A502dl, Android phone, originally purchased from Walmart with a Trackfone Sim card (Now there is no sim card insterted).
I have spent all day, up until now, figuring out how to link abd and fastboot to the phone using USB debugging, and I have been successful this far. I had downloaded latest "platform-tools_r29.0.1-windows" from here on XDA, and I downloaded latest "fatsboot" from "HighonAndroid.com", for a quicker experience, without wasting time and effort on Java downloads. In addition to all this, I let the computer search the network for updating driver software, for my Alcatel phone. I also downloaded "UniversalAdbDriverSetup", from the former link, @highonandroid.com.
I linked both file pathways for corresponding "Fastboot", and "platform-tools", into the environment variables, under the term: "Path", yes, using a ";" with no spaces to add the new pathways.
I had success linking my phone onto the "abd" program, the phone is listed under "abd devices" command. I could not seem to get a listing of my phone serial number, under the "fastboot devices" command?
I have tried to get "platform-tools" to put the phone into "fastboot/bootloader" mode, but the phone simply reboots, back to the lockscreen. I have also tried on "Fastboot", to "fastboot reboot bootloader", and my Alcatel again reboots to the lockscreen. All the while, I activated the OEM unlocking switch/setting in the "developer options" of my phone, from the beginning, before I ever gave any commands?
Why won't my Alcatel phone reboot into the "fastboot/bootloader" screen, where I could command "fastboot oem unlock"? Why does my phone respond to both programs, yet still she loads the lockscreen?
I am new to all this, not really a tech savvy individual, just wanted a liberated operating system for my line of work...
I need bootloader unlocked in order to root my device via computer, correct?
I can not check to see if my bootloader is unlocked, not by abd tools, or by numerical code in my "dialer app". The app crashes, and any time I attempt the "fastboot oem device-info" command, no device is listed, only a <looking for a device> prompt of sorts appears. I have been told this may be because, the drivers were not installed properly, or the device was not properly connected under some other issue, and I can try to fix this error by reinstalling drivers... what would the issue be?
I need help, and I would appreciate some guidance on rooting my Android, as there are not any threads in the forum, on this model of Alcatel, that I am aware of?
I am doing all of this on a Windows 7 computer, in a Library, just so you all know. I ask for administrative approval for most things.
Thank you.
tcl trackfone
Hello i was wondering if you ever got your phone rooted?
me to i have that problem on my tcl lx
to
Temporary mtk- root. Use init.d for always root
Sonjouten said:
Temporary mtk- root. Use init.d for always root
Click to expand...
Click to collapse
I can't possibly express how much I would love for you to elaborate on the 'use init.d for always root' part. Anyone else who knows, please jump in. Start by pretending I am an idiot. Then stop pretending and explain it to me as if I were an adult who needs a full-time minder. First one to help me achieve "always root" on this terrible, wretched, little excuse for an electronic device gets my undying gratitude and um, maybe some Google Play money? I am open to ideas here on that score. To reiterate, need help rooting my Tracfone TCL LX A502DL that has a castrated recovery (seriously, you can't flash anything from adb, the option is flat-out missing) and apparently no fastboot access AT ALL. I could do another seriously in parentheses, but you need to take my word for it w/o a bunch of examples. The bright spot is the vulnerability the device has to the mtk-su exploit. Get a # in like no time at all. Time elapsed from executing the file to getting the prompt is too short for my flesh computer to register (unless you -v, then about 1.5 seconds.) So how do I turn a root prompt into full root?
I can't possibly express how much I would love for you to elaborate....
Click to expand...
Click to collapse
WHAT HE SAID
+1
X2
etc
Thank you, H
Did he get that?
So did he earn that Google Play Store money or was he just full of it?
Just bumping this thread in case anyone has ideas for me. Seems like Alcatel has bootloader mode hidden on some phones. Here's my story: https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
BTW - I am using mtk-su and have root and Magisk via init.d scripts, but still can't touch /system or flash recovery because of
Code:
/dev/block/dm-0' is read-only
which won't change unti bl unlocked...
I never did get her to root. Alas she is a broken phone now RIP. Sorry for the disappointments. But I move on more hopeful. ?
As posted by Viva La Android in another thread about the tcl a501dl:
The TCL A1 (A501DL) cannot be bootloader unlocked. Although the OEM Unlocking option can be enabled in the Developer Options menu, fastboot mode has been made inaccessible by TCL. Because the bootloader cannot be unlocked, it simply is not possible to flash a custom recovery or a patched boot image for systemless root support. System-wide root is not possible due to TCL's secure boot chain configuration and dm-verity. Until an exploit is found to bootloader unlock this device, rooting is not possible.
Click to expand...
Click to collapse
levone1 said:
Just bumping this thread in case anyone has ideas for me. Seems like Alcatel has bootloader mode hidden on some phones. Here's my story: https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
BTW - I am using mtk-su and have root and Magisk via init.d scripts, but still can't touch /system or flash recovery because of
Code:
/dev/block/dm-0' is read-only
which won't change unti bl unlocked...
Click to expand...
Click to collapse
I have tried everything, and can't even get temporary root on my A502DL. How did you do this, if you don't mind? Thanks!
fliproc said:
I have tried everything, and can't even get temporary root on my A502DL. How did you do this, if you don't mind? Thanks!
Click to expand...
Click to collapse
Sorry, I honestly don't remember now - I just happened to have tje phone for a short time at that moment, so I was messing around with it... I remember there was nothimg special about it. I jist followed the instructions from the mtk-root thread and it worked.
Amazing Temp Root for MediaTek ARMv8 [2020-08-24] | XDA ...
Braadleyah said:
As in the title, I have an, Alcatel Tcl Lx A502dl, Android phone, originally purchased from Walmart with a Trackfone Sim card (Now there is no sim card insterted).
I have spent all day, up until now, figuring out how to link abd and fastboot to the phone using USB debugging, and I have been successful this far. I had downloaded latest "platform-tools_r29.0.1-windows" from here on XDA, and I downloaded latest "fatsboot" from "HighonAndroid.com", for a quicker experience, without wasting time and effort on Java downloads. In addition to all this, I let the computer search the network for updating driver software, for my Alcatel phone. I also downloaded "UniversalAdbDriverSetup", from the former link, @highonandroid.com.
I linked both file pathways for corresponding "Fastboot", and "platform-tools", into the environment variables, under the term: "Path", yes, using a ";" with no spaces to add the new pathways.
I had success linking my phone onto the "abd" program, the phone is listed under "abd devices" command. I could not seem to get a listing of my phone serial number, under the "fastboot devices" command?
I have tried to get "platform-tools" to put the phone into "fastboot/bootloader" mode, but the phone simply reboots, back to the lockscreen. I have also tried on "Fastboot", to "fastboot reboot bootloader", and my Alcatel again reboots to the lockscreen. All the while, I activated the OEM unlocking switch/setting in the "developer options" of my phone, from the beginning, before I ever gave any commands?
Why won't my Alcatel phone reboot into the "fastboot/bootloader" screen, where I could command "fastboot oem unlock"? Why does my phone respond to both programs, yet still she loads the lockscreen?
I am new to all this, not really a tech savvy individual, just wanted a liberated operating system for my line of work...
I need bootloader unlocked in order to root my device via computer, correct?
I can not check to see if my bootloader is unlocked, not by abd tools, or by numerical code in my "dialer app". The app crashes, and any time I attempt the "fastboot oem device-info" command, no device is listed, only a <looking for a device> prompt of sorts appears. I have been told this may be because, the drivers were not installed properly, or the device was not properly connected under some other issue, and I can try to fix this error by reinstalling drivers... what would the issue be?
I need help, and I would appreciate some guidance on rooting my Android, as there are not any threads in the forum, on this model of Alcatel, that I am aware of?
I am doing all of this on a Windows 7 computer, in a Library, just so you all know. I ask for administrative approval for most things.
Thank you.
Click to expand...
Click to collapse
I have heard elsewhere that it's not possible to unlock the bootloader of a Tracfone. Sorry. But at least we know why Tracfones are sold for so cheap lol
$cronos_ said:
I have heard elsewhere that it's not possible to unlock the bootloader of a Tracfone. Sorry. But at least we know why Tracfones are sold for so cheap lol
Click to expand...
Click to collapse
unlock bootloader and root with https://github.com/bkerler/mtkclient
This device cannot be rooted. To date, there has not been a single validated claim of a rooted TCL A509DL. The bootloader cannot be unlocked, preventing root, custom ROM installs,etc.
UPDATE: After hearing from some members regarding the Hydra Tool, and doing a little bit of research on the method, it appears that I was completely wrong on my.statement. Members here on XDA as well as Hovatek have confirmed that the A509DL bootloader can indeed be exploited with the Hydra Tool method, opening the door to systemless root with Magisk. Thanks guys for the info and guidance. I have one of these devices and look forward to unlocking & rooting soon. Thanks @PrivyetCyka for the info.
Yes it can .. it was extremely easy to do so also..i have a rooted one in my hand as we speak the only issue is I was stupid and tried to flash the magisk zip in twrp and it set off secureboot so in working on fixing that .. but .. if you just use MTKClient you can pull the entire firmware , magisk patch then reflash the boot.img using the same tool and you can even install twrp I have the entire firmware , twrp, and magisk patched boot imgs for the device saved ,. If someone knows how to disable secureboot I would really appreciate it
Viva La Android said:
This device cannot be rooted. To date, there has not been a single validated claim of a rooted TCL A509DL. The bootloader cannot be unlocked, preventing root, custom ROM installs,etc.
Click to expand...
Click to collapse
I sure would like to give it a whirl, but I haven't had that phone in over a year
Anyway, I decided to stop buying devices made deliberately less functional by their manufacturers.
PrivyetCyka said:
Yes it can .. it was extremely easy to do so also..i have a rooted one in my hand as we speak the only issue is I was stupid and tried to flash the magisk zip in twrp and it set off secureboot so in working on fixing that .. but .. if you just use MTKClient you can pull the entire firmware , magisk patch then reflash the boot.img using the same tool and you can even install twrp I have the entire firmware , twrp, and magisk patched boot imgs for the device saved ,. If someone knows how to disable secureboot I would really appreciate it
Click to expand...
Click to collapse
I stand corrected on my statement. I was incorrect. Out of curiosity, does the Hydra tool require the dongle in order to unlock the bootloader?
@PrivyetCyka send me the Magisk packed boot image and I will unpack it and disable secure boot. I can then pack it back up and link it to you. Are you referring to only secure boot or also AVB 2.0/dm-verity?
I didn't use hydra tool I used MTKClient from GitHub and did an entire system read back to have a backup then just renamed boot.bin to boot.img used magisk to patch it and then used the same MTKClient tool to reflash it... I have a twrp I made for it also but I don't know how functional it is as far as flashing things and backups , the only thing I tried to flash was the magisk zip just to see what would happen and that tripped the secureboot , I used the mediatek secureboot tool and it says it's disabled but it's still not booting past the secureboot fail screen.. when I get home I'll get the files and upload them tonight