Q&A for Unbrick Hard bricked Moto E
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Unbrick Hard bricked Moto E. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
please provide a working link to download stock firmware. thank you in advance
Not working... XT1025... hardbrick
moto e bricked
I downgraded from 5.0.2 to 4.4.2 then when updating to 4.4.4 the device got hard bricked. I approached the service center but they made me wait for 3 hours so I just left.I have given it to a mobile service center who assure to fix it using JTAG , delivery date is today.so let me see what they can do! I'll surely ask him how he fixed it (if they can do it that is).
---------- Post added at 12:59 PM ---------- Previous post was at 12:24 PM ----------
sheltoncyril said:
I downgraded from 5.0.2 to 4.4.2 then when updating to 4.4.4 the device got hard bricked. I approached the service center but they made me wait for 3 hours so I just left.I have given it to a mobile service center who assure to fix it using JTAG , delivery date is today.so let me see what they can do! I'll surely ask him how he fixed it (if they can do it that is).
Click to expand...
Click to collapse
He blames my battery and stuff...he then said the costs will be more than a new phone itself......I'm visiting the service center tomorrow...wish me luck
same here
sheltoncyril said:
I downgraded from 5.0.2 to 4.4.2 then when updating to 4.4.4 the device got hard bricked. I approached the service center but they made me wait for 3 hours so I just left.I have given it to a mobile service center who assure to fix it using JTAG , delivery date is today.so let me see what they can do! I'll surely ask him how he fixed it (if they can do it that is).
---------- Post added at 12:59 PM ---------- Previous post was at 12:24 PM ----------
He blames my battery and stuff...he then said the costs will be more than a new phone itself......I'm visiting the service center tomorrow...wish me luck
Click to expand...
Click to collapse
please bro tell me how much it costs in actual figure ..?? can they fix it around 1000 rs.
sandeep_7 said:
please bro tell me how much it costs in actual figure ..?? can they fix it around 1000 rs.
Click to expand...
Click to collapse
I'll give it to the service center tomorrow. The technician wasn't available today
repair costs and what happened
sheltoncyril said:
I'll give it to the service center tomorrow. The technician wasn't available today
Click to expand...
Click to collapse
so basically she didnt see whether it was on warranty or not, just took the device, details and a flipkart invoice copy.....no costs were told....people say they mostly will replace the mobo as the fix is not yet available (.mbn files) 10 days was the estimate given!
News
cwankhede said:
I hardbricked it too. But I took it to the service center in Mumbai today and they are going to fix it in under 10 working days. They didn't check if my bootloader was unlocked or not so its still under warranty. Go pretend like you still have warranty and you don't know what happened. I don't have to pay a thing
Click to expand...
Click to collapse
This is my experience.
Bricking of moto e
i did every thing as in the instructions......the problem is.....i am unable to go into fastboot by pressing the lock and vol down button......the screen stays blank....and...when ever i connect my device to a lap or charger led light blinks for some time.....but doesnt show any boot options
and my mobile doesn't on in normal mode either. need help urgent...........!!!!
krish003 said:
i did every thing as in the instructions......the problem is.....i am unable to go into fastboot by pressing the lock and vol down button......the screen stays blank....and...when ever i connect my device to a lap or charger led light blinks for some time.....but doesnt show any boot options
and my mobile doesn't on in normal mode either. need help urgent...........!!!!
Click to expand...
Click to collapse
That blank flash files sre intended for Moto G 1st gen. Goto service centre with invioce. I faced same problem with my Moto e. I got motherboard replacement in one week. There is no option. see this http://forum.xda-developers.com/moto-e/help/moto-e-wont-boot-t3045910
Awesome! Isn't there a way to use adb?
Very nice thread, it wold be a lot of help if i brick it, but there's not a way to use adb ? I would most likely prefer to use adb!
giumbai said:
Very nice thread, it wold be a lot of help if i brick it, but there's not a way to use adb ? I would most likely prefer to use adb!
Click to expand...
Click to collapse
If the phone hardbricked u cannot enter into fast bootmode no chance for adb not even it shows battery indicator when charging.
link dont work
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
C:\Users\john\Desktop\bl\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM5
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.000s]
identifying device
...serial = 0x21ABC51
...chip-id = 0x811
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.000s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.000s]
validating files
OKAY [ 0.000s]
switching to download mode
OKAY [ 0.000s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
OKAY [ 0.016s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
C:\Users\john\Desktop\bl\blankflash>pause
Pressione qualquer tecla para continuar. . .
help please, not working, moto e xt1025
If I restore my own CM11 backup from CWM on
my device running Blisspop,
will it get bricked ?
vkmcondor said:
If I restore my own CM11 backup from CWM on
my device running Blisspop,
will it get bricked ?
Click to expand...
Click to collapse
no it wont
Links not Working
Thanks for the post but links are not working. Can you please update ?? Also, my windows operating system was not able to search drivers for QHSUSB_BULK.. Please HELP!
My Moto E Phone Hard Bricked
Hello.
my moto e is not working its hard bricked , i have tried to downgrade from lolipop to kitkat. warranty is there, but i have unlocked boot loader, is there any chance they would know about boot loader unlocked.
Sorry for my bad english
Thank you
Rams
this is not working on my moto E XT1022 please help me!
wont work
its showing failed
Related
Hello guys,
so due to my phone getting bricked, when i fixed it, it no longer recognize the Cellular Network
as i asked in DC Phoenix Forum section (because that's the software that allowed me to unbrick my phone)
they said that now the problem is with my nv partitions and i need to flash it again
the problem is i don't have a back up of it, and it should be taken from a functional Honor 5X
so my request is for anyone out there who has this phone, to do a back up of this partition and send it to me to help me get my phone back and running
i'm looking forward for your help guy
Have a great day
zzmoubarek said:
Hello guys,
so due to my phone getting bricked, when i fixed it, it no longer recognize the Cellular Network
as i asked in DC Phoenix Forum section (because that's the software that allowed me to unbrick my phone)
they said that now the problem is with my nv partitions and i need to flash it again
the problem is i don't have a back up of it, and it should be taken from a functional Honor 5X
so my request is for anyone out there who has this phone, to do a back up of this partition and send it to me to help me get my phone back and running
i'm looking forward for your help guy
Have a great day
Click to expand...
Click to collapse
Please post in questions and answers section.......
Bharath kumar 007 said:
Please post in questions and answers section.......
Click to expand...
Click to collapse
Ok I'll do that thank you
hey developers. i need some expert advice about my phone, my phone is of lenovo model no. x3a40 (lenovo vibe x3). It got hard bricked last week, so i try to flash the stock rom using qfil and it flashed successfully still the phone won't boot up. Their are 3 stock rom versions, i tried them all but the phone won't boot up. i pressed the power button for atleast 1 hour or may be more still it wont boot. i checked the motherboard, no problem in that, remove and reconnect the battery supply, still no success.
so now for last resort i want some help about this issue, if any dev faced this problem and know the solution then please help me. i really need this device. :crying::crying:
tarun yadvendu said:
hey developers. i need some expert advice about my phone, my phone is of lenovo model no. x3a40 (lenovo vibe x3)...
Click to expand...
Click to collapse
I don't have this device but, I believe that the following, device specific, thread may be helpful for what you are looking for and don't be afraid to ask for some member guidance within it too.
https://forum.xda-developers.com/showthread.php?t=3328461
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I don't have this device but, I believe that the following, device specific, thread may be helpful for what you are looking for and don't be afraid to ask for some member guidance within it too.
https://forum.xda-developers.com/showthread.php?t=3328461
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
i am already active in that thread, and asked there but noone knows the solution. That's why i am asking from other devs. i can't find the solution for this problem. Thanks for your help
tarun yadvendu said:
hey developers. i need some expert advice about my phone, my phone is of lenovo model no. x3a40 (lenovo vibe x3). It got hard bricked last week, so i try to flash the stock rom using qfil and it flashed successfully still the phone won't boot up. Their are 3 stock rom versions, i tried them all but the phone won't boot up. i pressed the power button for atleast 1 hour or may be more still it wont boot. i checked the motherboard, no problem in that, remove and reconnect the battery supply, still no success.
so now for last resort i want some help about this issue, if any dev faced this problem and know the solution then please help me. i really need this device. :crying::crying:
Click to expand...
Click to collapse
i too had same problem did your get back to life or not?????
i have same problem, hope god send prophet to answer in this forum
sunilkjt said:
i too had same problem did your get back to life or not?????
Click to expand...
Click to collapse
were you able to fix this issue
Hi There , Idont Know How To Say This In Normal Way But Idont know How , So I Will Go Right Through The Problem
I Got This Moto X Pure Edition (style) X1572 | Retasia
And It Was On Android 5 On Locked
I Didn't Know I Have To unlock It Before Flashing So It's Lock
so I Tried To Update The Phone With Frimware That I Grabbed For Frimeware Center But It Was The Wrong Region( La )So I Tried Another (Eu)
Then I Found The Right Region By This Code : fastboot Getvar All and I Found That My Phone Is For Asia but I Can't Flash it because Of Gpt Partiton or bootloader Or Boot ، every Time I get the same errors
To sum up i want These Questions Answered
1 - is There any File For Region Asia With Android 7
2 - does my Phone Supports Deep Flash Cable Or Can I Flash it with Deep Flash Cable and How I Make Deep Flash Cable For Moto
3 - If I Couldn't Flash it Can It be flashed With a Box (like z3x for Samsung)
Please Help as Fast As You Can Im In deep Pain By This Phone and the Phone isn't mine I have to Return it By Tomorrow (1/8/2018) so Please Help To Solve This Problem Thanks
Mass_7596 said:
Hi There , Idont Know How To Say This In Normal Way But Idont know How , So I Will Go Right Through The Problem. I Got This Moto X Pure Edition (style) X1572..........
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is specific to your device.
https://forum.xda-developers.com/moto-x-style
With that guidance...
Your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3200852
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
UNDER TESTING
Hello XDA Community
I am new here, and 2 days ago i got my MI 8 Bricked and i saw a lot of users with that problem, so i want to revolution this
I tried to reverse engineering XiaoMIFlash and try to bypass EDL Authentification
I DONT HAVE TESTED IT, it took me 2/3 hours and i don't really know if it working (I Can't test it because i dont have any bricked phone at the moment)
I am alone doing this, maybe this community want to support me and help and make it a great bypass
DOWNLOAD LINK : https://mega.nz/#!rZZyRC7C!_EncWKE4rpt4JJv7Pz_pKgfRdhINnkvC0qWbvnPFVYg (NOT WORKING, FIXING)
(If someone have C# knowledge and want to give some help, i'm here <3)
How it works?
I tried to avoid EDLSign verification, using fake details and removing Exceptions
How to use?
Boot your phone in EDL Mode throw TEST POINTS
Connect your USB Cable to the phone
Login with your MI Account into the flasher
Select the correct rom (China = China, Global = Global) (China + Global = Brick) !!I Have removed the "Clean All and Lock" Option!!
Flash it
Let me know <3
Best regards
not working for me
hello, i tried to use the tool and its just keep stuck on flashing and count to 1000sec and more ,thanks in advanced
asitiyul said:
hello, i tried to use the tool and its just keep stuck on flashing and count to 1000sec and more ,thanks in advanced
Click to expand...
Click to collapse
Hello, it gives your an error?, Can u share here a screenshot and the log so i can understand what's wrong?
Hello. First of all thanks for that effort which community must thank of course. I'm not bricked now but just out of curiosity I'm wondering how did you unbrick your phone.
descarao81 said:
Hello. First of all thanks for that effort which community must thank of course. I'm not bricked now but just out of curiosity I'm wondering how did you unbrick your phone.
Click to expand...
Click to collapse
Hello, i unbricked it by paying a guy that have an EDL Account
But now i want to bypass this authentification and stop these scammers earning money easily
I'm going to fix this script as soon as possible , now probably doesn't work and my MI 8 is not bricked so i can't test to make sure is 100% working
I search for someone that know better than me how "QsaharaServer" works and give me help developing this crack
While my mi8 is not bricked this is great of you. I really hope you can make it coz a lot of people had their phones damaged because of stupid ARB.
Konskl said:
While my mi8 is not bricked this is great of you. I really hope you can make it coz a lot of people had their phones damaged because of stupid ARB.
Click to expand...
Click to collapse
That's what and why im trying to do this project
But i need someone testers, Today i found a new exploit and im going to publish it asap
I own a mi 8 global to remove the account on miui 10 already in Edl mode, if you can serve I can give you access to the device via USB on the internet or through a teamviewer session if you need to create a working program.
kajikita said:
But now i want to bypass this authentification
Click to expand...
Click to collapse
I guess you're aware of Whyred affair, someone finally found the bypass. There's a thread with a guide, in miui forums I think. The trick is of course in the ROM used to flash in EDL. Maybe you can contact the thread author and receive some guidance about the changes he made in the ROM.
Edit: there are plenty of threads with the same solution I was writing about but this is the original thread where everything began:
https://cafe.naver.com/xst?iframe_u...=27738104&articleid=273056&page=3&boardtype=L
descarao81 said:
I guess you're aware of Whyred affair, someone finally found the bypass. There's a thread with a guide, in miui forums I think. The trick is of course in the ROM used to flash in EDL. Maybe you can contact the thread author and receive some guidance about the changes he made in the ROM.
Edit: there are plenty of threads with the same solution I was writing about but this is the original thread where everything began:
https://cafe.naver.com/xst?iframe_u...=27738104&articleid=273056&page=3&boardtype=L
Click to expand...
Click to collapse
I already saw this note 5 trick, but i dont understand where is the "bug/exploit" that he used to bypass authentification, probably in "this.needEDLAuth" factor
I am going to look inside the files and find the solution
Hello,
Have you made any progress? I'm interested in this topic, because xiaomi services in my country lost their authorized accounts and they can't repair my phone now
Work in progress
KsaneK said:
Hello,
Have you made any progress? I'm interested in this topic, because xiaomi services in my country lost their authorized accounts and they can't repair my phone now
Click to expand...
Click to collapse
Fogghy360 said:
Work in progress
Click to expand...
Click to collapse
Great job, I Hope than you Will finished It.
Could anyone unbrick my mi8 for me?
I have a mi8 bricked if you wanna tester let me know .
KsaneK said:
Hello,
Have you made any progress? I'm interested in this topic, because xiaomi services in my country lost their authorized accounts and they can't repair my phone now
Click to expand...
Click to collapse
LMAO that's epic
---------- Post added at 06:18 AM ---------- Previous post was at 06:17 AM ----------
I'm following this thread too, just if mine gets bricked.
im stuck with bricked mi8 and so close to taking it to the trash
coliotte said:
im stuck with bricked mi8 and so close to taking it to the trash
Click to expand...
Click to collapse
My guess is that you bought a Chinese phone with global software?
If so, you are a victim of a corrupt vendor. I have read on Mi Forums the fastest solution to unbrick phones in this scenario is to contact the vendor and due to push back from Xiaomi management pressuring large distributors such as BangGood and TaoBao to do something about the scam , that many of these vendors are now willing to provide you with their Mi account and password which will allow you to unbrick for your device for no charge.
I am digressing a bit here. But I don't understand, how these 3rd party scammers are able to unlock devices that are not linked to their accounts. My Mi account has my Xiaomi phones and non -Xiaomi phones that I had previously used Miui Roms on.
Try contacting the vendor and report back here if that works, for you.
@ Damo1111
Don't fall for that scam, I tried unlocking my moms bootloader with my account and it didn't work because her phone is linked to her account.
coliotte said:
im stuck with bricked mi8 and so close to taking it to the trash
Click to expand...
Click to collapse
not yet, MOD EDIT: link removed
I am here with mi locked mi8. I dont have access to mi account bound to this phone. Tried s-unlock, they logged in with their account, i used test point method to enter qualcomm mode, phone flashed ok, but mi lock remained there. It seems that i payed for nothing!
If i can help, contact me here.
Hi i need help unbricking this. I flashed a img file to boot partition and my phone didnt seem to like it. How do i fix it. do i need boot.img file? does anyone who uses that phone have it? pls help if you know about mtk devices pls help me
I think i just need the stock rom
Ty in advance
kusti420 said:
Hi i need help unbricking this. I flashed a img file to boot partition and my phone didnt seem to like it. How do i fix it. do i need boot.img file? does anyone who uses that phone have it? pls help if you know about mtk devices pls help me
I think i just need the stock rom
Ty in advance
Click to expand...
Click to collapse
You can download Cubot X19 ROM from their website (cubot net/support/firmware/x19/)
Any idea how to root this device?
Official firmware URL in Cubot website
mega.nz/#!JVEx3YqR!lthU61ZF1_deyBrtrQyNeOJ4uUqw9C_V2SZfH3lfS9U
However, this firmware having problem.
After flash, Display has been showing "No write Google Key".
i.imgur.com/7NJuU5Q.png
I don't know about this message and having no idea erase.
---------- Post added at 03:12 AM ---------- Previous post was at 03:07 AM ----------
spirtosan said:
Any idea how to root this device?
Click to expand...
Click to collapse
Use Magisk.
But, problem in official firmware is not solved.
Use Magisk
Click to expand...
Click to collapse
Thank you , but can you make a little guide?
spirtosan said:
Thank you , but can you make a little guide?
Click to expand...
Click to collapse
Check this Guide.
https://forum.xda-developers.com/android/software-hacking/root-recovery-root-device-magisk-t3779454
This is Log in Windows Powershell.
PS C:\WINDOWS\system32> adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
0123456789ABCDEF unauthorized
PS C:\WINDOWS\system32> adb shell reboot bootloader
PS C:\WINDOWS\system32> fastboot devices
0123456789ABCDEF fastboot
PS C:\WINDOWS\system32> fastboot getvar unlocked
unlocked: no
Finished. Total time: 0.003s
PS C:\WINDOWS\system32> fastboot oem unlock <<-- You need Press Volume UP on X19-->>
(bootloader) Start unlock flow
OKAY [ 29.367s]
Finished. Total time: 29.368s
PS C:\WINDOWS\system32> fastboot getvar unlocked
unlocked: yes
Finished. Total time: 0.003s
PS C:\WINDOWS\system32> fastboot reboot <<--Reboot Android and Setup-->>
PS C:\WINDOWS\system32> adb shell reboot bootloader
PS C:\WINDOWS\system32> fastboot devices
0123456789ABCDEF fastboot
PS C:\platform-tools> fastboot flash boot "D:\patched_boot.img" <<--Select patched_boot.img on your PC-->>
Sending 'boot' (9404 KB) OKAY [ 0.520s]
Writing 'boot' OKAY [ 0.651s]
Finished. Total time: 1.176s
PS C:\platform-tools> fastboot reboot
Rebooting
Finished. Total time: 0.002s
http://forum.cubot.net/viewtopic.php?f=21&t=2375
spirtosan said:
You can download Cubot X19 ROM from their website (cubot net/support/firmware/x19/)
Any idea how to root this device?
Click to expand...
Click to collapse
yeah, they finally uploaded the rom there
rooting is easy, just download magisk, patch the boot.img and then flash it with adb
Thank you, this method worked.
Code:
C:\Users\mc>cd c:\adb
c:\adb>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
0123456789ABCDEF unauthorized
c:\adb>adb devices
List of devices attached
0123456789ABCDEF device
c:\adb>adb reboot bootloader
c:\adb>fastboot flash boot c:\adb\boot.img
Sending 'boot' (9993 KB) OKAY [ 0.675s]
Writing 'boot' FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
c:\adb>fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 25.885s]
Finished. Total time: 25.890s
c:\adb>fastboot flash boot c:\adb\boot.img
Sending 'boot' (9993 KB) OKAY [ 0.522s]
Writing 'boot' OKAY [ 0.133s]
Finished. Total time: 0.705s
c:\adb>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.003s
enotaes said:
Official firmware URL in Cubot website
mega.nz/#!JVEx3YqR!lthU61ZF1_deyBrtrQyNeOJ4uUqw9C_V2SZfH3lfS9U
However, this firmware having problem.
After flash, Display has been showing "No write Google Key".
i.imgur.com/7NJuU5Q.png
I don't know about this message and having no idea erase.
---------- Post added at 03:12 AM ---------- Previous post was at 03:07 AM ----------
Use Magisk.
But, problem in official firmware is not solved.
Click to expand...
Click to collapse
i had the same problem. in my case imei numbers were missing and after i contacted cubot, they helped me out and i got rid of that watermark
I'm bored too.
ADB is working, but fastboot doesn't get the right for the confirmed PC.
Concerning missing IMEIs I searched long time and finally solved it with https://androidmtk.com/download-sn-write-tool
Any one know where I can down load CUBOT_X19_9021C_2_V02_20190802 android 9.0 (current firware)? On Cubot website it shows old firmware CUBOT_X19_9021C_1_V08_20190627 android 9.0.
Thanks
Any one know where I can down load CUBOT_X19_9021C_2_V02_20190802 android 9.0 (current firware)? On Cubot website it shows old firmware CUBOT_X19_9021C_1_V08_20190627 android 9.0.
Thanks
Click to expand...
Click to collapse
Hi
The official website for the Cubot X19 Firmware is https://www.cubot.net/support/firmware/x19/.
I have heard / read, that they have tried a new firmware but this didn't work at the customers so they have retired it.
This may be the firmware you have written.
After my experience the developers have theyr professional environment where some things work fine, but on other PCs or in other networks with other pathes it doesn't work.
This is a general problem of developers, not only Cubot.
Even for me as experienced user (and not developer): They send me a fix for the Google-Key-Watermark which didn't work with theyr pathes. I adapted it for my environment, and it worked. But now I am adapting these changes general, for that it works for all users. Each detail is important, sometimes its good to make a break and to re-check it the next day (or some days later when other things are more important).
I hope they can integrate the next fix of the buggy recovery (no zip-file install possible) in the next update; or when the fix they are proposing to me will work, I will publish him here.
Best regards
Christopher
G3O_CH said:
Hi
The official website for the Cubot X19 Firmware is https://www.cubot.net/support/firmware/x19/.
I have heard / read, that they have tried a new firmware but this didn't work at the customers so they have retired it.
This may be the firmware you have written.
After my experience the developers have theyr professional environment where some things work fine, but on other PCs or in other networks with other pathes it doesn't work.
This is a general problem of developers, not only Cubot.
Even for me as experienced user (and not developer): They send me a fix for the Google-Key-Watermark which didn't work with theyr pathes. I adapted it for my environment, and it worked. But now I am adapting these changes general, for that it works for all users. Each detail is important, sometimes its good to make a break and to re-check it the next day (or some days later when other things are more important).
I hope they can integrate the next fix of the buggy recovery (no zip-file install possible) in the next update; or when the fix they are proposing to me will work, I will publish him here.
Best regards
Christopher
Click to expand...
Click to collapse
Thanks for replying. Actually the firmware I am looking for which is US version. I got the answer from Cubot after-sale support to me that: " Hello,
I asked our engineer for help. But he told me that we didn't have the US version firmware for this phone, the firmware all are the same, not special US version. "
Attached is my Phone US version Build number.
KimLe said:
Thanks for replying. Actually the firmware I am looking for which is US version. I got the answer from Cubot after-sale support to me that: " Hello,
I asked our engineer for help. But he told me that we didn't have the US version firmware for this phone, the firmware all are the same, not special US version. "
Attached is my Phone US version Build number.
Click to expand...
Click to collapse
Hi
The answer looks like written by Scarlett. She tries to make the support while the developers are doing other things, probably preparing the coming Cubot X20.
Scarlett writes quite good English, answers from develeopers (engineers) looks like have been written in Chinese and translated by Google. My English isn't well too (living in Switzerland I prefer German or French).
The actual Android 9 ROMs for the Cubot Phones are based on GSI-Treble-ROMS (https://forum.xda-developers.com/project-treble). These are international and adapted with drivers and settings for specific hardware (Cubot X19).
I don't think that your firmware is a specific US version. But it looks like they have installed on some devices a new firmware, which made problems and was retired.
If hou have big problems with your firmware, it could help to downgrade on the version from the website. If the problems are small, you better don't change too much.
Best regards from Switzerland
Christopher
G3O_CH said:
Hi
The answer looks like written by Scarlett. She tries to make the support while the developers are doing other things, probably preparing the coming Cubot X20.
Scarlett writes quite good English, answers from develeopers (engineers) looks like have been written in Chinese and translated by Google. My English isn't well too (living in Switzerland I prefer German or French).
The actual Android 9 ROMs for the Cubot Phones are based on GSI-Treble-ROMS (https://forum.xda-developers.com/project-treble). These are international and adapted with drivers and settings for specific hardware (Cubot X19).
I don't think that your firmware is a specific US version. But it looks like they have installed on some devices a new firmware, which made problems and was retired.
If hou have big problems with your firmware, it could help to downgrade on the version from the website. If the problems are small, you better don't change too much.
Best regards from Switzerland
Christopher
Click to expand...
Click to collapse
Yes, you are right. The answer was written by Scarlett.
I got Cubot X19 US version from GearBest : https://www.gearbest.com/cell-phones/pp_009514021249.html?wid=1349303#goodsDetail
The firmware support US Network.
Networks:
GSM: 850/900/1800/1900MHz
WCDMA: 850/1700/1900MHz
FDD-LTE: B2/4/5/7/12/17/28A+B
And it is different with EU Network.
Networks:
GSM 850/900/1800/1900MHz
WCDMA 900/2100MHZ
FDD-LTE B1/3/7/8/20
KimLe said:
Yes, you are right. The answer was written by Scarlett.
I got Cubot X19 US version from GearBest : https://www.gearbest.com/cell-phones/pp_009514021249.html?wid=1349303#goodsDetail
The firmware support US Network.
Networks:
GSM: 850/900/1800/1900MHz
WCDMA: 850/1700/1900MHz
FDD-LTE: B2/4/5/7/12/17/28A+B
And it is different with EU Network.
Networks:
GSM 850/900/1800/1900MHz
WCDMA 900/2100MHZ
FDD-LTE B1/3/7/8/20
Click to expand...
Click to collapse
Okay, compared with the official specifications on https://www.cubot.net/smartphones/x19/spec.html there are some significant differences.
When Scarlett couldn't solve the problem, she gave me a mail adress from a developer (engineer).
I don't want to publish this adress because this isn't the official way. But I will send you the mail adress with private message.
Best regards
Christopher
G3O_CH said:
Okay, compared with the official specifications on https://www.cubot.net/smartphones/x19/spec.html there are some significant differences.
When Scarlett couldn't solve the problem, she gave me a mail adress from a developer (engineer).
I don't want to publish this adress because this isn't the official way. But I will send you the mail adress with private message.
Best regards
Christopher
Click to expand...
Click to collapse
Thanks. :good:
Hi
I have the same problem with Red Google Key watermark but this watermark consist Chinese characters. ->
https://drive.google.com/open?id=1mRI7uTe4qc7UB019fJhlBlRNBjD-fNZ1
I wrote IMEI again by https://androidmtk.com/download-sn-write-tool and I can connect via phone and LTE, but I still have red watermark
Have you idea how to fix it?
Regards
Hi,
what for boot.img must I use for magisk?
boot-verified.img or boot.img?
micgeb said:
Hi,
what for boot.img must I use for magisk?
boot-verified.img or boot.img?
Click to expand...
Click to collapse
Hi
I used boot.img
For Android 9 commands in adb:
adb reboot bootloader
fastboot flashing unlock
fastboot flash boot magisk_patched.img
fastboot reboot
Regards