Related
Hi there
i have alcatel pixi 7 (i213)
i root it then backuped with MtkDroidtools
now i want to install recovery cwm BUT
my recovery size is 16 mb
im unpacking - repacking stock recovery but after flashing its even not booting
flashing recovery 16 mb and its booting
after repack it is 5-6 mb
i think its uses other pack method
help PLS
blabla
if someone needs...
stock recovery : https://mega.co.nz/#!G4kDkJpL!CH3oWWqDm_6rDLGlHgoOISvg-jd436FXnNkdtCboGh0
CTRecovery_2.5 : https://mega.co.nz/#!jh82HKoR!D-BbITkkfHqMNy6hewgCLV_7Xw9xZJoX8YfezwqHpKQ
Hi!
I have bricked my pixi 7 (i213). After root i have started debloating stock firmware and misstyped some command and of course i didn't made a copy.
If anyone could upload and share custpack and system (android) images/partitions or whole stock firmware it would be great.
Xcore_Rj said:
if someone needs...
stock recovery : https://mega.co.nz/#!G4kDkJpL!CH3oWWqDm_6rDLGlHgoOISvg-jd436FXnNkdtCboGh0
CTRecovery_2.5 : https://mega.co.nz/#!jh82HKoR!D-BbITkkfHqMNy6hewgCLV_7Xw9xZJoX8YfezwqHpKQ
Click to expand...
Click to collapse
whats that custom recovery for?
is it compatible with my zeki quad core 4.4.2 android tablet?
i need one!! :fingers-crossed:
hmmm
emm
download mobile upgrade
here's the link http://www.alcatelonetouch.com/glob...n/PIXI_7/otu/mobile-upgrade-s-4-1-8-setup.exe
open it
select pixi 7 or i213
and follow steps
contact if any problems
glad to help
Sent from my I213 using XDA Free mobile app
Thanks for the reply.
Mobile upgrade pops up message that there is no new firmware for my tablet. I think its stock fw wasn't from alcatel. It's custom made by Orange telecomunication company ... don't know what to do next .
Marcin Tomczczyk said:
Thanks for the reply.
Mobile upgrade pops up message that there is no new firmware for my tablet. I think its stock fw wasn't from alcatel. It's custom made by Orange telecomunication company ... don't know what to do next .
Click to expand...
Click to collapse
mine is from orange too..but its updating...
so i can give my system.img..its already rooted..try so..
https://onedrive.live.com/?cid=b84e72ba94787c35&id=B84E72BA94787C35%211315&ithint=file,img&authkey=!ACvvZMgyUIoS2rU
if after flashing it will not boot flash boot.img too https://mega.co.nz/#!T80ihQAA!wiofxhYpc_5sfrKpUYIINSU-Vzb7vFqENI1EbaPyT-0
Thanks for the upload, share and help!
I was talking about polish part of the Orange corporation, not the international one. So this might be the answer why mobile upgrade not updating my tablet firmware . They don't give a f... .
Also still not booting after flashing system and boot images.
Does your firmware have custpack partition? It is partition with stock apk's and other stuff from alcatel. I was deleting packages from this partition also.
I know i'm asking a lot but if your firmware does have this partition, could you also upload it?
Could you also upload custpack partition? I have no other way to unbrick this tablet .
zzzz
Is this compatible with my l212? I think its not. Can you check my Dump System? If we are the same partition then i can flash that.
How to root?
Hello everybody.
I bought the tablet, and try to find a way to root it.
All the tools I found didn't make the job...
How do you root your device?
Thanks for your support!
Greetings
ThMusch said:
I bought the tablet, and try to find a way to root it.
All the tools I found didn't make the job...
How do you root your device?Greetings
Click to expand...
Click to collapse
I Had some problems with rooting this piece of crap the conventional way, but I managed to do it using iRoot. The bad thing is that iRoot's SU app will keep installing a lot of useless stuff in Chinese. To get rid of them, you first need to install SuperSU from the Play Store (If I recall correctly CWM Superuser will work fine as well, but ChainsDD Superuser won't, so keep this in mind) after rooting it and then using manually remove the Chinese SuperUser apk that comes with iRoot and once you get rid of it, you can uninstall the remaining Chinese apps the normal way.
Marcin Tomczczyk said:
Could you also upload custpack partition? I have no other way to unbrick this tablet .
Click to expand...
Click to collapse
I am in the middle of unbricking my Pixi 7 after failed installation of fonts (my font folder CHMOD got messed up and now the device is not booting as it can't reed it), and if I success, I'll post here about the process.
@edit
Okay, if anyone ever has problem with recovering their Pixi 7, here are the steps to make a clean installation using Mobile Upgrade S. The only requirement is to have the device already installed on at least one of your USB ports (otherwise your OS won't detect it, as it will try to install the drivers, but will fail because it sees the device to be disconnecting shortly after plugging it in – at least it was my case):
1. Download Mobile Upgrade S and SP Flash
2. Grab this scatter file.
3. Open the file you just downloaded. Find the following section:
...
partition_index: SYS3
partition_name: PRO_INFO
file_name: NONE
is_download: false
...
Click to expand...
Click to collapse
And replace is_download to true;
4. Open Flash tool and in your download section select your edited scatter file.
5. Go to Readback and select Add.
6. Double-click the added line and save it as pro_info.img
7. Set it as follows: Type : hex , Region EMMC_USER , start : 0x100000 , lenght 0x300000
8. Click Read Back, turn off your Pixi and connect it to your PC via USB cable. It should start the read immediately and after few seccond you should get a success messgae. If it's not the case, try a different USB port.
9. After you got your read, disconnect your Pixi and open newly created pro_info.img file in a hex editor.
10. Find your device version (it's soimewhere at the beggining, around adress 0xA3, and looks like XXXI213-XXXXXXX, where X can be any character, for example mine was COXI213-2DRGPL1) and change it to ENXI213-2BALGB1.
11. Replace your software version (Right after your device ver. Mine was AAZY1AAZ0Z0BD00) for AAZY1AAY0Y0BD00.
12. Save changes to your file.
13. Go back to your SP Flash tool > Download tab
14. Select your scatter file. Deselect all checkboxes. Leave PRO_INFO checked only.
15. Click on PRO_INFO location and select the file you just edited.
16. Select Download and connect your Pixi.
17. When done, run Mobile Upgrade S and follow the standard upgrading process (be aware, that it will take a lot of time to download the ROM, as the download speed goes around 20-50 KB/s. It took me aroung 8h to download it).
18. After installation run your Pixi for the first time and wait for it to boot (don't panic if it takes a bit of time. It will be booting for about 2-5 minutes for the first time).
Nidrax said:
I Had some problems with rooting this piece of crap the conventional way, but I managed to do it using iRoot. The bad thing is that iRoot's SU app will keep installing a lot of useless stuff in Chinese. To get rid of them, you first need to install SuperSU from the Play Store (If I recall correctly CWM Superuser will work fine as well, but ChainsDD Superuser won't, so keep this in mind) after rooting it and then using manually remove the Chinese SuperUser apk that comes with iRoot and once you get rid of it, you can uninstall the remaining Chinese apps the normal way.
I am in the middle of unbricking my Pixi 7 after failed installation of fonts (my font folder CHMOD got messed up and now the device is not booting as it can't reed it), and if I success, I'll post here about the process.
@edit
Okay, if anyone ever has problem with recovering their Pixi 7, here are the steps to make a clean installation using Mobile Upgrade S. The only requirement is to have the device already installed on at least one of your USB ports (otherwise your OS won't detect it, as it will try to install the drivers, but will fail because it sees the device to be disconnecting shortly after plugging it in – at least it was my case):
1. Download Mobile Upgrade S and SP Flash
2. Grab this scatter file.
3. Open the file you just downloaded. Find the following section:
And replace is_download to true;
4. Open Flash tool and in your download section select your edited scatter file.
5. Go to Readback and select Add.
6. Double-click the added line and save it as pro_info.img
7. Set it as follows: Type : hex , Region EMMC_USER , start : 0x100000 , lenght 0x300000
8. Click Read Back, turn off your Pixi and connect it to your PC via USB cable. It should start the read immediately and after few seccond you should get a success messgae. If it's not the case, try a different USB port.
9. After you got your read, disconnect your Pixi and open newly created pro_info.img file in a hex editor.
10. Find your device version (it's soimewhere at the beggining, around adress 0xA3, and looks like XXXI213-XXXXXXX, where X can be any character, for example mine was COXI213-2DRGPL1) and change it to ENXI213-2BALGB1.
11. Replace your software version (Right after your device ver. Mine was AAZY1AAZ0Z0BD00) for AAZY1AAY0Y0BD00.
12. Save changes to your file.
13. Go back to your SP Flash tool > Download tab
14. Select your scatter file. Deselect all checkboxes. Leave PRO_INFO checked only.
15. Click on PRO_INFO location and select the file you just edited.
16. Select Download and connect your Pixi.
17. When done, run Mobile Upgrade S and follow the standard upgrading process (be aware, that it will take a lot of time to download the ROM, as the download speed goes around 20-50 KB/s. It took me aroung 8h to download it).
18. After installation run your Pixi for the first time and wait for it to boot (don't panic if it takes a bit of time. It will be booting for about 2-5 minutes for the first time).
Click to expand...
Click to collapse
Great to hear that my instructions helped you and good that you posted it here http://forum.android.com.pl/topic/211918-stock-rom-do-pixi-7/?p=3776346
KINGROOT 4.5.2 works for my pixi7 (i213)
Hi, i've bricked my phone...someone knows how to unbrick.?
luisfernandoo.nunezfranco said:
Hi, i've bricked my phone...someone knows how to unbrick.?
Click to expand...
Click to collapse
Without any further details, it's going to be difficult to help. It's pretty hard to do so..... What did you do to brick it? Can you get into recovery. Do you have a custom rom? Provide some more details & someone might be able to help you
mightymaki said:
Without any further details, it's going to be difficult to help. It's pretty hard to do so..... What did you do to brick it? Can you get into recovery. Do you have a custom rom? Provide some more details & someone might be able to help you
Click to expand...
Click to collapse
>Hi Friend, i would appreciate yor help, my Nubua Z7 max is bricked after flashing the new(from needrom site) 5.0 stock rom and reflashing the original kitkat stock rom.
I need to repartition the phone storage , when i boot it appears only 4.0 Gbyte storage for programs , but no internal storage.
How can i repartition the internal storage?
Thank you
Simonis said:
>Hi Friend, i would appreciate yor help, my Nubua Z7 max is bricked after flashing the new(from needrom site) 5.0 stock rom and reflashing the original kitkat stock rom.
I need to repartition the phone storage , when i boot it appears only 4.0 Gbyte storage for programs , but no internal storage.
How can i repartition the internal storage?
Thank you
Click to expand...
Click to collapse
There are some instructions on the Z7 mini thread here on XDA. Have a search & follow the instructions
Unbrick Z7 max
mightymaki said:
There are some instructions on the Z7 mini thread here on XDA. Have a search & follow the instructions
Click to expand...
Click to collapse
Thank you but i did not find anything relevant by searching
[email protected] said:
Thank you but i did not find anything relevant by searching
Click to expand...
Click to collapse
You can follow this thread: http://www.androidiani.com/forum/zte-nubia-z7/446548-guida-di-unbrick-z7-max-mini.html
use google translate.
I am going to post a guide in English in about 2 hours. I have bricked mine and I followed the procedure from androidiani.
Guide to unbrick ZTE Nubia Z7 Mini
I have done this procedure on my device without any problem after a repartition failure, but I am not responsible about anything happens to your device (which is already bricked...)
The source is http://www.androidiani.com/forum/zte-nubia-z7/446548-guida-di-unbrick-z7-max-mini-27.html
1) We disable driver signature verification for windows.
- Windows XP https://mega.co.nz/#!30I1yLRD!kLblCqP9_LmiOXjpfzGbFL7m2zqAqKqZ8ciPFWMBDB0
- Windows 7 http://www.sabrent.com/support/knowledgebase.php?article=14
- Windows 8 http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
2) We download the drivers, which we extract in our desktop.
3) We connect the device while switched off to PC via a USB 2.0 port, and we launch Windows device manager. We press simultaneously Vol +/Vol -/Power button for ~5 seconds. We should see our device identified as QHUSB_BULK under Ports section in device manager. If we get prompted to format several drives we cancel all of the actions.
4) We right-click at device QHUSB_BULK > Update Driver > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Have disk > Browse, and we open Nuova cartella folder which we have extracted, containing the drivers.
We choose the driver named Qualcomm HS-USB QDloader 9008 and we install it.
We can see our device now identified with that name in the device manager.
5) We download Nubia Toolstudio , and Z7 mini files.
We extract them inside a folder in our desktop, and we run toolstudio as administrators, disabling our anti-virus, or putting the program to its' exceptions because it will be detected as malware.
In the prompt which will pop-up requiring a password, we enter the e-mail address found at the .txt file.
6) We select eMMC Download, we refresh and we should see our device identified like this.
7) We select browse, and we select the folder nx507J_files containing the Z7 mini files.
8) We select start all, and we wait until the procedure finishes.
The whole process has ended, we unplug our device and we can boot it. We will be with stock rom 1.28
Hi Stratos,
i was able bevor to google translate the italian text an d using the screenshots avaliable there i was able to flash the Nubia 7 MAX
software. BUT no imeis are in the Phone so now i have to find a method to type the IMEI numbers in the Phone dont know how..
I tried to create a flashable zip (as suggested by nano7mobile.blogspot) but did not work maybe becuase i dont know
the IMEI Folder location inside the Phone..
Simos
previously after bricked zte z7 max, can flash with ToolStudio : http://www.needrom.com/download/z7-max-2-13-android-5-beta_eng_chi/ (file: NX505J_CNCommon_V2.13.tar)
voila, phone revive.. thankyou..
Another Problem is Appear..
Imei,Meid, is gone.
i backup imei (blank) with Qpst, generate name: blank_imei.QCN ( ^^)
edit my own file : blank_imei..QCN (with blank imei,meid,esn)
the file is about 141 KB.
i open with hexa editor, feel confuse, don't know where to start, don't know the location of imei,meid,esn.
i don't know where "offset" position to be edit.
i google around,
i think need file : *.QCN from someone z7 max backup, to determine the position of imei,meid,esn. (cmiiw)
can someone help me, provide backup of Z7 Max *.QCN file?
i will Surely change it with hexa editor, edit it with my own imei,meid,esn.
or there is another way to fix this imei-meid-esn problem?
please help...
best regard's
stratos_21 said:
I have done this procedure on my device without any problem after a repartition failure, but I am not responsible about anything happens to your device (which is already bricked...)
The source is http://www.androidiani.com/forum/zte-nubia-z7/446548-guida-di-unbrick-z7-max-mini-27.html
1) We disable driver signature verification for windows.
- Windows XP https://mega.co.nz/#!30I1yLRD!kLblCqP9_LmiOXjpfzGbFL7m2zqAqKqZ8ciPFWMBDB0
- Windows 7 http://www.sabrent.com/support/knowledgebase.php?article=14
- Windows 8 http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
2) We download the drivers, which we extract in our desktop.
3) We connect the device while switched off to PC via a USB 2.0 port, and we launch Windows device manager. We press simultaneously Vol +/Vol -/Power button for ~5 seconds. We should see our device identified as QHUSB_BULK under Ports section in device manager. If we get prompted to format several drives we cancel all of the actions.
4) We right-click at device QHUSB_BULK > Update Driver > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Have disk > Browse, and we open Nuova cartella folder which we have extracted, containing the drivers.
We choose the driver named Qualcomm HS-USB QDloader 9008 and we install it.
We can see our device now identified with that name in the device manager.
5) We download Nubia Toolstudio , and Z7 mini files.
We extract them inside a folder in our desktop, and we run toolstudio as administrators, disabling our anti-virus, or putting the program to its' exceptions because it will be detected as malware.
In the prompt which will pop-up requiring a password, we enter the e-mail address found at the .txt file.
6) We select eMMC Download, we refresh and we should see our device identified like this.
7) We select browse, and we select the folder nx507J_files containing the Z7 mini files.
8) We select start all, and we wait until the procedure finishes.
The whole process has ended, we unplug our device and we can boot it. We will be with stock rom 1.28
Click to expand...
Click to collapse
I bricked it yesterday trying to downgrade from cm12.1 to Official nubia 3.01. Yesterday it showed up as QHUSB_BULK, but now it shows up as android cd rom drive and I can't do anything with it. Currently it will boot into the nubia recovery and it will charge, I can't enable it as mass storage device . I can see that all my files are there through the recovery but I can't gain access to them. Will it let me flash from External USB micro sd card as I am about to go buy one? If I turn it on it goes straight into nubia recovery and when I have it off it charges.
When you said 1.28 did you mean Official 1.82? The 1.82 did not work for me as I had an official 1.82 already downloaded. The file you linked I could not download due to poor connection. I was able to install Nubia 3.01 but I think I lost my imei because it says no sim detected. Fortunately, I do have an efs backup from HC-kTool - will I be able to restore that? Also all of this began as I went straight to V3.01 instead of V2.03, first . And then I went to cm12.1 which was extremely buggy so I try to downgrade to official v3.01 and then to Kitkat 4.4.4 v1.82 when something happened to the pc and phone lost connection during the downgrade.
What should I do next? I currently am on Lollipop 3.01 with no radios, baseband etc. My blue-tooth and wi-fi are working. Should I try to restore my efs.img I backed up with HC-kTool?
next4nextel said:
I bricked it yesterday trying to downgrade from cm12.1 to Official nubia 3.01. Yesterday it showed up as QHUSB_BULK, but now it shows up as android cd rom drive and I can't do anything with it. Currently it will boot into the nubia recovery and it will charge, I can't enable it as mass storage device . I can see that all my files are there through the recovery but I can't gain access to them. Will it let me flash from External USB micro sd card as I am about to go buy one? If I turn it on it goes straight into nubia recovery and when I have it oharges.
Click to expand...
Click to collapse
I'm in a similar situation with mine, self inflicted of course while I was trying to get the phone rooted with 3.01.
Anyway where it is now I can still boot to a point and I still have the Nubia recovery util fully functional. If you go into that and look under 'other' you will see that you have the ability to enable mass storage from there and yes you have the option of updating via SD,internal and OTG via the recovery util.
For me though unless I want to get nasty and do things from scratch it looks like I can only carry out an update using an official Nubia file and not just a recovery nor an earlier or current version of stock firmware which is kind of weird. And yes you have the option of updating via the SD,internal and OTG via the recovery util.
Thanks Parso, fortunately I followed the above steps and I restored to official 5.0. but then I lost my imei and had to sort that out. I actually like the official 5.0 except for 2 bugs one where I can't see the WiFi icon on the status bar unless I'm connected to Wi-Fi. And the other is sometimes when I get a call the screen never lights up and I can't swipe to answer the calls which is really annoying because I have to call them back.
I have the same situation right now.I upgraded my z7max 1.64 to 3.09.then I tried cm12 but there were so many problems with mobile data.
So I decided to change it.It was a big mistake to go back to 1.64 without reading anything.In the end it stopped working after a few trys.
Anyway I managed to enter toolstudio 4.6 and show it at por as com13 .Then I watched steps and flashed 3.09 to phone.It seemed like succesfull but it wasnt.Now it s not reacting and all black screen.
Also when I connected it to computer again at the beginning it was QHUSB_BULK with yellow sign.Then I tried to install Qualcomm CDMA Technologies MSM to set it up.Now it became worse.When I connect my phone it s written "unidentifed device" on device manager.
I guess we re missing one thing.For example this "Qualcomm CDMA Technologies MSM" or qhsusb驱动 folders are for XP, Vista or 7. I m using windows 8 right now and I think these files are not suitible as drivers.
So my phone is dead now.If I can set drivers up I guess I can fix it.But I cant find any other drivers and that s the biggest problem.
Hi everyone,
My feedback, After try CM12.1 i decided to return at android 4.4 and for that i used nubia updated tools and nubia studio.
After flash, no imei and only USA Band.
After restored my NV backup 1 IMEI of 2 come back ?!, After restore my
NV Value (values from opo guide, because NV Calculator give me a bad number ?) all band done USA, ENRO, JAPAN etc ...
BUT the phone lock/unlock (after enter my lock pin) every 5 secondes ?
Please help me, i have no ideas
buzz-27 said:
Hi everyone,
My feedback, After try CM12.1 i decided to return at android 4.4 and for that i used nubia updated tools and nubia studio.
After flash, no imei and only USA Band.
After restored my NV backup 1 IMEI of 2 come back ?!, After restore my
NV Value (values from opo guide, because NV Calculator give me a bad number ?) all band done USA, ENRO, JAPAN etc ...
BUT the phone lock/unlock (after enter my lock pin) every 5 secondes ?
Please help me, i have no ideas
Click to expand...
Click to collapse
For all those who are facing issues unbricking the phone as given above, use these Qualcomm drivers (5th post from top)
http://forum.cyanogenmod.org/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/page__st__40
Point to these drivers from Device manager (QHUSB_BULK). Your device should be identified correctly. Also follow the same steps exactly as given earlier. I managed to unbrick with completely working phone & IMEI.
If anyone is intersted in reading why Qualcomm devices cannot be bricked completely, read the links given below in 2 parts
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/
http://www.androidbrick.com/unbrick...oader-9008-if-you-have-the-right-kind-of-rom/
next4nextel said:
Thanks Parso, fortunately I followed the above steps and I restored to official 5.0. but then I lost my imei and had to sort that out. I actually like the official 5.0 except for 2 bugs one where I can't see the WiFi icon on the status bar unless I'm connected to Wi-Fi. And the other is sometimes when I get a call the screen never lights up and I can't swipe to answer the calls which is really annoying because I have to call them back.
Click to expand...
Click to collapse
Hello,
COuld you please tell me how you solved the problem, cause all imei and meid are:null
Please someone help me fix the imei problem, i have my imei nr's on the box, but i did not do a back-up.
Thank you
zte z7 mini
hi bad rom update and can not get back into recovey have looked at the posts but drivers link down and when i get Nubia Toolstudio i downloade 3 times put needs password ??? any help please i am runing on windows 10 64bit and win 7 32 bit if some can help on here or mail me on [email protected] going mad with this
Hi, this is my first post here. XDA-forums are great and I think here is the place where you would help me to solve the problem with my phone Nubia z7max.
The problem is that after a software (ROM) update in recovery TWRP from the stock 3.22 to Mokee (android 6 ) , the phone remained on logo "Nubia powered by Android". I have read probably everything written about that problem in all possible places that I found around the internet including Chinese NUBIA forum, Androidiani, 4PdA and so on. I followed all the steps which incidentally are the same everywhere for fixing the phone:
http://forum.xda-developers.com/zte-z7/general/unbrick-nubia-z7-mini-t3006268/page2
stratos_21 said:
I have done this procedure on my device without any problem after a repartition failure,
but I am not responsible about anything happens to your device (which is already
bricked...)
The source is http://www.androidiani.com/forum/zte-nubia-z7/446548-guida-di-unbrick-z7-max-mini-27.html
1) We disable driver signature verification for windows.
2) We download the drivers, which we extract in our desktop.
3) We connect the device while switched off to PC via a USB 2.0 port, and we launch Windows device manager. We press simultaneously Vol +/Vol -/Power button for ~5 seconds. We should see our device identified as QHUSB_BULK under Ports section in device manager. If we get prompted to format several drives we cancel all of the actions.
4) We right-click at device QHUSB_BULK > Update Driver > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Have disk > Browse, and we open Nuova cartella folder which we have extracted, containing the drivers.
We choose the driver named Qualcomm HS-USB QDloader 9008 and we install it.
We can see our device now identified with that name in the device manager.
5) We download Z7 mini files.
We extract them inside a folder in our desktop, and we run toolstudio as administrators, disabling our anti-virus, or putting the program to its' exceptions because it will be detected as malware.
In the prompt which will pop-up requiring a password, we enter the e-mail address found at the .txt file.
6) We select eMMC Download, we refresh and we should see our device identified like this.
7) We select browse, and we select the folder nx507J_files containing the Z7 mini files.
8) We select start all, and we wait until the procedure finishes.
The whole process has ended, we unplug our device and we can boot it. We will be with stock rom 1.28
Click to expand...
Click to collapse
The difference in my case is that the procedure for flashing have completed with no errors and the phone restarts and it is in the same condition without any change: the logo "NUBIA powered by Android".
I tried to maybe over 10 different drivers. The phone is detected by the computer as it should be. When downloading the ROM in to the phone with ToolStudio_4.6 or NX505J Nubia Tool V2.1.0, procedure runs without any problems but the result is the same. There is no possibility to enter into recovery, I was TWRP and accordingly have a backup made in TWRP ahead of time when my phone is working normally.
With the combination Vol+, Vol- & Power pressed together for about 7-8 seconds the phone is recognized by the computer as HSUSB_Bulk and a cuple of disc drives with a different volume. Drivers are installed correctly although hardware is 19d2 and the phone is recognized as Qualcomm HS-USB QDLoader 9008 (COM XX).
With the combination Vol+ & Power pressed together for about 7-8 seconds the phone is recognized as Android ADB Interface, on screen are Nubia logo. In this kind I can charge (at least visibly) TWRP through "Z7_Max_All_In_One_Tool_Created_By_Tigreos" (NeedRom), but after that I can not go into Recovery. With the same tool I can install stock recovery too but still can not login to recovery.
The biggest success I've achieved after many attempts, two weeks from now, are to initial animation pictures and melody at startup and phone suddenly goes off.
Pleace Help
Hi folks,
Today it's a great day for me : I have successfully patched the kernel to have a 100% working TWRP 3.2.1 for our Maze Alpha 4G.
I have port a Jemmini build for Bluboo S1 and I have patch the kernel to have a working touch panel
I have followed this Thead
For the Maze Alpha 6G version, you can test it and tell me please.
How to flash:
I Fastboot method (must unlock device) :
1- Reboot your phone in bootloader mode : adb reboot bootloader or phone off, press and hold at the same time POWER and Vol+ buttons
2- Connect your phone to your computer with adb/fastboot already installed
3- Unlock your bootloader : fastboot oem unlock (it will erase you data, only data)
4- Flash the recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
II SPFlashTool method (no need to unlock device) :
1- Download latest version of SPFlashTools.
2- Execute it and load the provided scatter (the recovery image must be in the same folder as the scatter and must be renamed to recovery.img) then press "Dowbload" button
3a- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3b- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Update : you can found here the latest version: TWRP 3.3.0 for MAze Alpha 4Ghttps://github.com/dreambo/android_device_maze_alpha/releases/tag/3.3.0
have a nice day.
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
super_sonic said:
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
Click to expand...
Click to collapse
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
dreambo said:
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
Click to expand...
Click to collapse
Thanks. Can you share stock recovery.img, if you have it? I have recovery-verified.img from V05 but I don't know if there is a new update and if size is correct: 11,54MB. Your TWRP recovery has got a size of 14.24MB...
Can you make a small procedure on how to install it? Will help many nOOb's out.
And people need to report back issues and successes !!!! Again I see many questions and people with issues that we seniors try to help out with that end up in no more response which to me is not done and not helping others.
I have a 6GB version that I could test on but at the moment I am using it for other stuff and I can't risk bricking it this week.
Would finally love to start some stuff happening on this phone.
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
lukesan said:
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
Click to expand...
Click to collapse
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
frumac96 said:
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
Click to expand...
Click to collapse
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
lukesan said:
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
Click to expand...
Click to collapse
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
frumac96 said:
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
Click to expand...
Click to collapse
This is the filename I used on Windows 10 VCOM Drivers (All MTK Devices & All Windows OS version).zip I think I downloaded it from XDA somewhere.
Also something you must know https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Another thing I experienced is that one USB connector is not the other one on a pc. Always connect it to the ones directly on the main board next to the other device outputs like audio etc. and preferably not go through ones that have been extended via a cable like the ones on top of the casing or so. Also a must have application is usbdeview.
Well should be easy to get it going if you can boot it into 'fastboot' then you can try as much as you want to. But djeeeeezzzz the letters are very small when you boot it with a power+volume up . Also check that volume up will toggle between 'fastboot', 'recovery' and 'normal start' and volume minus will select it, not the power button which would be more logical to me.
I might have another go at trying to get it working on my 6GB but it involves having a lot of time and knowing that I will get frustrated. Installing all apps and settings is also a time consuming thing. Once you have TWRP on it it all becomes easy to backup. So many things to test or try.
Maybe dreambo has an idea on how to get mine up to a 6GB one as it is probably only indicated in the kernel.
Anyway I will continue to write down my progress.
Ok more frustration. Done multiple things to try to get this running. It's good to know that the original rom is easy to install again after practice.
Take 1: Try to install clean 6GB rom and immediately install TWRP.
Results: Dreambo forgot 1 step and that is to allow OEM unlock in the developer options. If you do the adb command to unlock press volume up and it will unlock (very hard to see, very small letters on the display in bootloader mode)
Well TWRP starts but immediately I get a message 'mount decrypt data password' which I tried a couple of things but no go. Also googled... different solutions but always ending in a bootloop to TWRP
A possible solution that I read was to create a startup pin .... no go 'pin not valid'
Take 2: Take all the rom files and change the scatter file with the one dreambo provided.... Thought it was successful but ended up with the same Chinese recovery. Trying to figure out why since the filename was correct like indicated in the scatter file. Came to the conclusion that the original file was/is called recovery-verified.img and not recovery.img. Really really strange this one as in the original scatter file it also points to recovery.img. So this one I will have to investigate. Renaming the TWRP file to recovery-verified.img lead to a error during the initial scan of the flashtool.
So moral of the story is that I am back on square 1 and lost 2 hours today (plus putting all apps and settings back) today.
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
CYberdog11 said:
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
Click to expand...
Click to collapse
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
CYberdog11 said:
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
Click to expand...
Click to collapse
From another thread:
mmakdz said:
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Click to expand...
Click to collapse
dreambo said:
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
Click to expand...
Click to collapse
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
lukesan said:
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
Click to expand...
Click to collapse
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
dreambo said:
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
Click to expand...
Click to collapse
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
lukesan said:
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
Click to expand...
Click to collapse
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
dreambo said:
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
Click to expand...
Click to collapse
The thing is that I have no issue with flashing the software as I can perfectly flash the original rom. The problem is that when flashing the TWRP file, in both options by the way, so also via method 1, I get a boot loop.
I tried to change the Chinese Firmware to Global firmware to (Meizu Pro 7) and now I have a problem.
I followed this guide on this web:
chinahandys .net (I can't copy the link here since I have a new user
and so I deleted the file "boot.img"
I also couldn't open the Update.zip file with Winrar or another archive program.
then, I tried to do this :
"10. In FlashFire, select the small plus icon at the bottom right and select “Flash ZIP or OTA”. Select the “update.zip” file and confirm the pop-up with the tick at the top right"
but I couldn't find the “update.zip” file there.
finally, I tried to open the update.zip by pressing "Update".
since then my phone won't start.
The only thing i can do is pressing the "plus" button and another button below which will lead to me to a screen of Updating the system. when I try to do it's wrong because "firmware not found".
My phone is stock on the screen "flyme".
please help me!! I just bought this phone
(danhdongufixer) he is on Facebook.... He single handily brought my pro 7 plus back from the dead get ahold of him he's wizard .
I had same problem and this guy fixed my phone get in touch with him because there is nothing else you can do meizu left a lot of us hanging for over 3 months and no help . Good luck
You maybe don't use the good Firmware
maorsah said:
I tried to change the Chinese Firmware to Global firmware to (Meizu Pro 7) and now I have a problem.
I followed this guide on this web:
chinahandys .net (I can't copy the link here since I have a new user
and so I deleted the file "boot.img"
I also couldn't open the Update.zip file with Winrar or another archive program.
then, I tried to do this :
"10. In FlashFire, select the small plus icon at the bottom right and select “Flash ZIP or OTA”. Select the “update.zip” file and confirm the pop-up with the tick at the top right"
but I couldn't find the “update.zip” file there.
finally, I tried to open the update.zip by pressing "Update".
since then my phone won't start.
The only thing i can do is pressing the "plus" button and another button below which will lead to me to a screen of Updating the system. when I try to do it's wrong because "firmware not found".
My phone is stock on the screen "flyme".
please help me!! I just bought this phone
Click to expand...
Click to collapse
Hi,
For 3 month, I hope you have find the solution. If you don't, here is mine :
I had the same problème on my phone.
I couldn't reinstall it, I think the version that I downloaded wasn't compatible with the "Chinese" version of my mobile.
You need to find the good firmware !
Could you try with this chinese firmware : MEIZU PRO7 Standard Version -Flyme6.1.3.2A-7.0
It's worked on my phone.
So,
Press and hold the volume up and power button until the screen goes on recovery mode.
Connect the device to the laptop or PC, you can open the device. You will see an empty partition named recovery.
Now copy the downloaded firmware of your phone and place it in the recovery partition. Just copy update.zip to recovery partition.
Now in the phone select update firmware and clear data and press next.
The phone will reboot and install the firmware.
Wait, wait, wait 15mn be patient.
tell me if it's working on your phone.
excuse me for my poor English !
Math32 said:
Hi,
For 3 month, I hope you have find the solution. If you don't, here is mine :
I had the same problème on my phone.
I couldn't reinstall it, I think the version that I downloaded wasn't compatible with the "Chinese" version of my mobile.
You need to find the good firmware !
Could you try with this chinese firmware : MEIZU PRO7 Standard Version -Flyme6.1.3.2A-7.0
It's worked on my phone.
So,Press and hold the volume up and power button until the screen goes on recovery mode.
Connect the device to the laptop or PC, you can open the device. You will see an empty partition named recovery.
Now copy the downloaded firmware of your phone and place it in the recovery partition. Just copy update.zip to recovery partition. Now in the phone select update firmware and clear data and press next.
The phone will reboot and install the firmware.
Wait, wait, wait 15mn be patient.
tell me if it's working on your phone.
Click to expand...
Click to collapse
Hello!
Was everything, such as google playstore and english language, still working on you phone after you updated the firmware?
I was also wondering if theres need to backup the IMEI somewhere?
Im currently running a modified verision of 6.1.3.2A which doesnt have all the features for the 2nd display and hence looking for an upgrade.
Leone1 said:
Hello!
Was everything, such as google playstore and english language, still working on you phone after you updated the firmware?
I was also wondering if theres need to backup the IMEI somewhere?
Im currently running a modified verision of 6.1.3.2A which doesnt have all the features for the 2nd display and hence looking for an upgrade.
Click to expand...
Click to collapse
I used this chinese version less than 10mn. I would advise you to install the G firmware !
I didn't install the playstore (too thing in chinese in this firmware) that's why after running the version 6.1.3.2A, i used this tutorial :
https://forum.xda-developers.com/showpost.php?p=75297402&postcount=70
"Download the firmware Flyme 6.1.3.2G from here
http://www.flymeos.com/firmwarelist?modelId=88&type=1
after you can do the instructions in video
https://www.youtube.com/watch?v=aDp6oZL4Wx4 "
Be careful when you install superSU to do the same thing as in the video. I don't do the same than on the vidéo that's why i need to reinstall the chinese firmware. After the installation i wait 15mn and my phone stays on Flyme. i restart it and it worked for installing busybox and flashfire.
I wish you bon courage !
Math32 said:
I used this chinese version less than 10mn. I would advise you to install the G firmware !
I didn't install the playstore (too thing in chinese in this firmware) that's why after running the version 6.1.3.2A, i used this tutorial :
https://forum.xda-developers.com/showpost.php?p=75297402&postcount=70
"Download the firmware Flyme 6.1.3.2G from here
http://www.flymeos.com/firmwarelist?modelId=88&type=1
after you can do the instructions in video
https://www.youtube.com/watch?v=aDp6oZL4Wx4 "
Be careful when you install superSU to do the same thing as in the video. I don't do the same than on the vidéo that's why i need to reinstall the chinese firmware. After the installation i wait 15mn and my phone stays on Flyme. i restart it and it worked for installing busybox and flashfire.
I wish you bon courage !
Click to expand...
Click to collapse
Ah ok, so you only used it to be able to flash the global rom on?
Ive read multiple places that its not possible to update from A to G, thats why i was thinking about going to the 7.0.0.0A ROM instead. The shop i bought it from (CECT, who are not very well informed at all) told me it would brick the phone to go to G from A, my phone is apparently not intended for global sale thats why they make their own version and flashes it on...
So now im just looking for someone who can confirm that updating to the A-rom wont remove google play or english.
EDIT: I have the Helio P25 model
Hi all,
I recently got my hands on a screen-damaged Archos 50 Diamond (ac50da) running the latest stable stock Android 4.4.4 ROM (I didn't know that an Android 5.1 preview was available here : https://blog.archos.com/fr/lollipop-en-version-beta-sur-le-50-diamond/).
I bricked it by doing the following :
- Trying to install @phhusson TWRP from here : https://twrp.me/archos/archos50diamond.html, without upgrading to 5.1 first (as explained here : https://forum.xda-developers.com/ar...ment/twrp-support-thread-archos-twrp-t3468677).
This did not work, as when trying to enter recovery mode by holding VolumeUp while powering up the phone would now bring up a totally green, then totally red screen, but nothing else. No device is detected if I plug it in a computer (either Linux or Windows).
- Booting (not flashing yet) CWM from here : http://www.arctablet.com/blog/forum...50-diamond-root-procedure-recovery-cwm-v6051/
For some reason, I ended up rebooting (without installing CWM or anything else). But before rebooting, CWM warned me that my ROM wasn't rooted, and offered to install the su binary in /system/xbin/su. That's were I met my doom, because the device would then no longer boot.
- If I power up the device, the Archos logo shows up, then a black screen. Plugging the device on a Windows computer shows a dozen data drives, and the devices itself identified as QHSUSB_BULK.
- I thought of using QFIL (Qualcomm File Image Loader) to re-image the device : https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
I managed to get my hands on a stock firmware image (prog_emmc_firehose_8936.mbn or validated_emmc_firehose_8936.mbn) by paying here : https://firmware.gem-flash.com/index.php?a=browse&b=file-info&id=110067 but QFIL won't flash it as I don't have a driver for QHSUSB_BULK.
- However, I'm unable to find a proper driver for that device. I found several Qualcomm drivers, either for QHSUSB_BULK or the (apparently older) QDLOAD, but none of them include definitions for the Archos 50 Diamond.
- The device's USB identification is the following : USB\VID_05C6&PID_9057&MI_00
VID (Vendor ID) 05C6 = Qualcomm
PID (Product ID) 9057 = ??? (should be the Archos 50 Diamond but is not referenced anywhere)
MI (Master Interface) = ??? (no idea what that means)
- Other findings :
The .mbn files refer to a Qualcomm Snapdragon 610 MSM8936
Inside the stock image is an android-info.txt file that reads "board=msm8916"
So, can you guys help me out here ?
I think that finding a proper QHSUSB_BULK driver for VID_05C6&PID_9057 should be enough, but I'm open to any suggestion.
Thanks !
I think I found a driver for that device here : https://driverpack.io/fr/hwids/USB\VID_1D9C&PID_9057&MI_04
It's for a "Sonim XP5 HS-USB NMEA 9057", but whatever.
However, after installing the driver (just uncompress it using 7-zip), QFIL fails when trying to download the firmware image with "failed to switch to EDL mode" (EDL = emergency download).
Anyone has a better idea*?
VICTORY !!!
When trying to power off/reboot the device, I noticed that it could still boot in fastboot mode, by holding VolumeUp + power until the screen turns green, then release the buttons before the screen turns red.
I could then boot again in CWM (still unable to flash it though), and re-install a stock ROM from the manufacturer site : https://www.archos.com/us/support/support_tech/downloads.html?type=s&rlist=1&devid=240
Phew ! At last !
And now to try and install the 5.1 beta update…
Hello! I have Archos diamond 50 in qd 9008 mode always. Can you upload firmware that you download from gemflash? I want try unbrick device.
IDLeon said:
Hello! I have Archos diamond 50 in qd 9008 mode always. Can you upload firmware that you download from gemflash? I want try unbrick device.
Click to expand...
Click to collapse
Do you have any place I can upload it to ?
Hi.
I have the same problem and I cant find the flash file.
Can you please give me the .mbn flash file (prog_emmc_firehose_8936.mbn or validated_emmc_firehose_8936.mbn) ?
Thank you
karim-ps said:
Hi.
I have the same problem and I cant find the flash file.
Can you please give me the .mbn flash file (prog_emmc_firehose_8936.mbn or validated_emmc_firehose_8936.mbn) ?
Thank you
Click to expand...
Click to collapse
Do you have any place I can upload it to ?
Maybe Google drive or wetransfer.com
Thank you
karim-ps said:
Maybe Google drive or wetransfer.com
Thank you
Click to expand...
Click to collapse
If you can give me access to one of yours, I'll do it ASAP. I don't have one myself and don't plan to.
breversa said:
If you can give me access to one of yours, I'll do it ASAP. I don't have one myself and don't plan to.
Click to expand...
Click to collapse
I sent it through a private message.
Thank you
For anyone interested : I have some stock firmware files, but nowhere to store them (I'm not looking to register to yet another service). If you're willing to host them, please send me a private message. Thanks !
Thank you
breversa said:
For anyone interested : I have some stock firmware files, but nowhere to store them (I'm not looking to register to yet another service). If you're willing to host them, please send me a private message. Thanks !
Click to expand...
Click to collapse
I'm in the process of uploading the 50_Diamond.rar stock firmware to https://androidfilehost.com/
I'll give the link when it's done. Feel free to ping me if I forget !
Okay, here it is : https://www.androidfilehost.com/?w=files&flid=319661