Unbrick Oppo R5
Since oppo forums support is minimal and a lot of Oppo R5/ R5s owners are facing difficulties flashing new rom and since Oppo is unbrickable here are a guide as posted to oppo forum members by the member Ricky.
I had clear instructions not to post this tool anywhere BUT THEY DON’T SUPPORT ANY DEVICE and I have to break my promise as they broke any kind of support.
This community (XDA) is to help all members
The tool works with windows 10 and not only with windows 7 as they mention in their instructions
Packages you have to download first
1- Firmware ColorOS https://www.partage-facile.com/LM6Y85FF7Z/r8106ex_11_a.16_150806.tar.bz2.html
File Name: R8106EX_11_A.16_150806.tar.bz2
Size: 1.4GB
MD5: F85ED63BA637B559976D9BFF0AED0187
2- Instructions:
https://drive.google.com/file/d/0B3AWkNVCRSNVZGNRUE1rQW5YOFk/view?sid=
3- Driver : http://en.oppo.com/downloads/firmware/driverForFind5.rar
Mirror for driver http://www109.zippyshare.com/v/MEMiPlOv/file.html
Attention
a-Unbrick tool will wipe all data on your device including photos and music etc, if do you want to reserve your data please make o back up on your PC
b- After unbrick the first time power up take around 5-15 minutes
c- The most important things are to install the driver. For windows 10 you must enable unsigned signature verification through windows advanced settings (google it) prior driver installation.
d- In order to shut phone completely hold the power button for 8 -10 secs
How to use the tool
I tried to use the tool and the files you provided to revive my Oppo R5, but the layout of the tool which you provided is different from the one in the picture (you gave in the links). It is also in foreign characters so difficult to choose with option to tick.
In fact, the version that came with you package does not have as many option as the one in the picture. My confusion actually starts from when the program starts. There is a drop down menu to chose from a long list of 14005 to 15065. Which one do I choose for Oppo R5?
As for the qualcomm port, the device manager identified my phone on port 9006, whereas the picture shows 9008.
Please help me. I really need to get this phone to work. The phone would not do any thing is the buttons are pressed individually or in combination, other than being detected by the computer and enumerated in the device manager.
Many thanks in advance for your help.
amadoro said:
I tried to use the tool and the files you provided to revive my Oppo R5, but the layout of the tool which you provided is different from the one in the picture (you gave in the links). It is also in foreign characters so difficult to choose with option to tick.
In fact, the version that came with you package does not have as many option as the one in the picture. My confusion actually starts from when the program starts. There is a drop down menu to chose from a long list of 14005 to 15065. Which one do I choose for Oppo R5?
As for the qualcomm port, the device manager identified my phone on port 9006, whereas the picture shows 9008.
Please help me. I really need to get this phone to work. The phone would not do any thing is the buttons are pressed individually or in combination, other than being detected by the computer and enumerated in the device manager.
Many thanks in advance for your help.
Click to expand...
Click to collapse
For R5 use 14016.
mermigas said:
For R5 use 14016.
Click to expand...
Click to collapse
Thank you for your reply. I tried to use the tool again, but there is not option for 14016. The full list is here: 14005, 14006, 14023, 14037, 14039, 14040, 14041, 14042, 14043, 14045, 14046, 14047, 14050, 14051, 14052, 14061, 14062, 14065, 14068, 140083, 14085, 14097, 14098, 15005, 15005_4G, 15006, 1500_4G, 15007, 15007_4G, 15011, 15012, 15013, 15018, 15057, 15061, 15065.
The flash tool that I am using is V1.5. Is is possible that I am using a wrong version for what I need to do?
Many thanks for your attention.
amadoro said:
Thank you for your reply. I tried to use the tool again, but there is not option for 14016. The full list is here: 14005, 14006, 14023, 14037, 14039, 14040, 14041, 14042, 14043, 14045, 14046, 14047, 14050, 14051, 14052, 14061, 14062, 14065, 14068, 140083, 14085, 14097, 14098, 15005, 15005_4G, 15006, 1500_4G, 15007, 15007_4G, 15011, 15012, 15013, 15018, 15057, 15061, 15065.
The flash tool that I am using is V1.5. Is is possible that I am using a wrong version for what I need to do?
Many thanks for your attention.
Click to expand...
Click to collapse
Sorry mistyped
14061
Also there is an English Version for the flashing tool here
https://forum.xda-developers.com/r7-plus/help/oppo-r7plusm-msm-tool-t3313759.
Just download it and copy to the folder that there is the Chinese tool
For me the Chinese version works fine
Also there is a same guide here
http://community.oppo.com/en/forum.php?mod=viewthread&tid=51497&extra=
mermigas said:
Sorry mistyped
14061
Also there is an English Version for the flashing tool here
https://forum.xda-developers.com/r7-plus/help/oppo-r7plusm-msm-tool-t3313759.
Just download it and copy to the folder that there is the Chinese tool
For me the Chinese version works fine
Also there is a same guide here
http://community.oppo.com/en/forum.php?mod=viewthread&tid=51497&extra=
Click to expand...
Click to collapse
Thank you so much. it worked. Not my Oppo r5 is back alive.
Where is the download?
Is it normal that when I hit the download link there appear aliexpress??
I thought I had bricked my R5 but while trying to follow this guide it wasn't showing up in the "Ports" section of the Device Manager. I found that my phone still had fastboot, so I used it to install latest TWRP and then the repair rom. And now my phone is finally back to working condition! I hadn't modified in any way my phone and one day it got stuck at the logo. Anyway, thanks for the guide Mermigas!
anyone mirror pls
mega
[email protected] said:
anyone mirror pls
Click to expand...
Click to collapse
[dead link]
If it asks for a key leave it blank
Kushracer said:
https://mega.nz/#F!q8YFEJyB
If it asks for a key leave it blank
Click to expand...
Click to collapse
No asking for decryption key
mirror
Uploading here: R5S Unbrick Tools
Please help
After i have done all those instructions: my phone was completely dead(no more display and can't use any buttons).
Please what should i do for revive that.
Link Broken
cpuld you re-load the link of Color Os firmware please?
Its not valid now =(
Number for R5S?
Hi, I tried the 14061 for my OPPO R5S. Unfortunately it did not work. Now the phone is not starting.. help? Should I use another number?
Related
My chinese phone Galaxy GT-N9000 clone Mtk6572 was brick, i try almost every tutorial and rom from many forum but still i can't bring my phone back to life ... please there anyone can help me? :crying: :crying: :crying: :crying:
Korean Clone Version Note 3
ijal7785 said:
My chinese phone Galaxy GT-N9000 clone Mtk6572 was brick, i try almost every tutorial and rom from many forum but still i can't bring my phone back to life ... please there anyone can help me? :crying: :crying: :crying: :crying:
Click to expand...
Click to collapse
- Mine is N9000 Note 3 Korean Clone Version MTK6572, and i'm wondering if theres a way to root it. i know there's a lot of android professionals here, and i hope we can find some answers.
- Version 4.3 jellybean
- Baseband Version: MTK6572 MAUI.11AMD.WW1150.SP. V23
- Kernel 2.6.35.7 [email protected] #4
- Software Version: JSS15J.N900ZSUBMI5
- Hardware Version: 1.1.0
Base on CPU Identifier:
- Spreadtrum SC6820a 1000 Mhz
- (fingerprint Brand for Fake Samsung Market)
- SMDK4X12
- Mali-300
Answer
ijal7785 said:
My chinese phone Galaxy GT-N9000 clone Mtk6572 was brick, i try almost every tutorial and rom from many forum but still i can't bring my phone back to life ... please there anyone can help me? :crying: :crying: :crying: :crying:
Click to expand...
Click to collapse
There is no support for chinese devices anywhere.
The tutorials are made only for the original device.
Did you back up the stock rom in the first place?
This problem would have been solved if you had a backup of your stock rom.
Now you have no other go than to contact the manufacturer for getting the phone fixed.
Trying other roms will not help you in restoring.
ijal7785 said:
My chinese phone Galaxy GT-N9000 clone Mtk6572 was brick, i try almost every tutorial and rom from many forum but still i can't bring my phone back to life ... please there anyone can help me? :crying: :crying: :crying: :crying:
Click to expand...
Click to collapse
try this >
- install ABD Drivers MTK65xx on your pc
- install SP Flash Tools
- download a custom ROM from needrom BUT only for your model N9000, other ROM will be useless
now extract the new ROM and let the window open after extraction
- open SP Flash Tools and load the scatter img file ( is in the extracted folder, navigate to that folder and load the scatter text img file )
- turn your phone off, wait until it vibrates to be sure is off
- press Download button on SP Flash Tools and after 1 sec connect your phone to PC
you'll the Flashing process Start, wait until is finish, it may take more than 10 min in some cases... you'll see a green circle after the process is done
- disconnect your phone and Power On, Voilaa
NovelCaidy said:
- Mine is N9000 Note 3 Korean Clone Version MTK6572, and i'm wondering if theres a way to root it. i know there's a lot of android professionals here, and i hope we can find some answers.
Click to expand...
Click to collapse
use Shuame or Framaroot, if u need help, i'm here...
Guys anybody got a rom for thje same phone...I have it too and its bricked..nothing is working
Ahh!!
Today I faced Same Problem With Same Model But Lots Of Effort Finally I Have Done .
My Working ROM : https://drive.google.com/uc?id=0B35LZs4cp74ZYlRYUnhpejUyZFE
Regards,
filip_pine said:
try this >
- install ABD Drivers MTK65xx on your pc
- install SP Flash Tools
- download a custom ROM from needrom BUT only for your model N9000, other ROM will be useless
now extract the new ROM and let the window open after extraction
- open SP Flash Tools and load the scatter img file ( is in the extracted folder, navigate to that folder and load the scatter text img file )
- turn your phone off, wait until it vibrates to be sure is off
- press Download button on SP Flash Tools and after 1 sec connect your phone to PC
you'll the Flashing process Start, wait until is finish, it may take more than 10 min in some cases... you'll see a green circle after the process is done
- disconnect your phone and Power On, Voilaa
use Shuame or Framaroot, if u need help, i'm here...
Click to expand...
Click to collapse
Hi, thanks for your help, but the phone is still bricked.
When i try to switch power on, nothing happen :crying:
If i push volume button, up or down i can see appear and disappear on device manager the ALCATEL SINGLE RNDIS SINGLE INTERFACE #5 but never MT65xx Preloader driver. :crying:
Seems to be not full dead but i don't know what else i can do.
If you have an advice for us with bricked phone...will be much appreciated.
Very thank you for any help kind. :crying:
D4N13L0N3 said:
Hi, thanks for your help, but the phone is still bricked.
When i try to switch power on, nothing happen :crying:
If i push volume button, up or down i can see appear and disappear on device manager the ALCATEL SINGLE RNDIS SINGLE INTERFACE #5 but never MT65xx Preloader driver. :crying:
Seems to be not full dead but i don't know what else i can do.
If you have an advice for us with bricked phone...will be much appreciated.
Very thank you for any help kind. :crying:
Click to expand...
Click to collapse
you need to install proper driver in order for the PC to recognize the phone, ussualy the Preloader USB VCOM Driver does the job, sometime it takes much more effort, and ADB Drivers need to be installed...
- Proper way to install Preloader USB VCOM Driver -
Connect your phone to PC and wait for the New hardware Found wizzard to appear
Choose i will install the driver by myself, then navigate to the folder location were you have the .ini driver file...
- If the method above dont work, then connect your phone to PC, wait for the New hardware found to appear...
Then right click on My PC and go to the Device Manager
Here you should have a yellow Mark and a phone name or something like this
Right click and choose update driver
Now choose the folder where you have extract the .ini driver file ....
Restart your PC
Open SP FlashTools and be sure that u have the proper ROM for your Phone, otherwise you´ll face DRAM FAIL Error
try this ROM that the guy posted above...
https://drive.google.com/uc?id=0B35LZs4cp74ZYlRYUnhpejUyZFE
filip_pine said:
you need to install proper driver in order for the PC to recognize the phone, ussualy the Preloader USB VCOM Driver does the job, sometime it takes much more effort, and ADB Drivers need to be installed...
- Proper way to install Preloader USB VCOM Driver -
Connect your phone to PC and wait for the New hardware Found wizzard to appear
Choose i will install the driver by myself, then navigate to the folder location were you have the .ini driver file...
- If the method above dont work, then connect your phone to PC, wait for the New hardware found to appear...
Then right click on My PC and go to the Device Manager
Here you should have a yellow Mark and a phone name or something like this
Right click and choose update driver
Now choose the folder where you have extract the .ini driver file ....
Restart your PC
Open SP FlashTools and be sure that u have the proper ROM for your Phone, otherwise you´ll face DRAM FAIL Error
try this ROM that the guy posted above...
Click to expand...
Click to collapse
Thanks, i tried your guide, but with that ROM finaly appear 100% in red color, probably because this phone have MTK6582 and not 6572.
If i use a rom for 6582 at the end of process i can see the DRAM FAIL error
I use this link from XDA for that ROMs:
androidxda.com/download-hdc-stock-rom-models
Any other advice ????
Thanks
D4N13L0N3 said:
Thanks, i tried your guide, but with that ROM finaly appear 100% in red color, probably because this phone have MTK6582 and not 6572.
If i use a rom for 6582 at the end of process i can see the DRAM FAIL error
I use this link from XDA for that ROMs:
androidxda.com/download-hdc-stock-rom-models
Any other advice ????
Thanks
Click to expand...
Click to collapse
ok, take your battery out and tell me the exact model...
filip_pine said:
ok, take your battery out and tell me the exact model...
Click to expand...
Click to collapse
Model: SM-N9000
SSN : N9000GSMH
Made in Korea by Samsung
filip_pine said:
ok, take your battery out and tell me the exact model...
Click to expand...
Click to collapse
This is model:
D4N13L0N3 said:
This is model:
Click to expand...
Click to collapse
try this ROM´s... maybe one of them will make your phone alive ...
http://www.needrom.com/mobile/11-hdc-n9000-note-3/
http://www.needrom.com/mobile/hdc-note-3-mt6582-sm-n9006/
http://www.needrom.com/mobile/hdc-galaxy-note-3-mtk6582-1gb-4gb-2014-kernel/
filip_pine said:
try this ROM´s... maybe one of them will make your phone alive ...
Click to expand...
Click to collapse
Thanks.
I will try, then i tell you if i can use like a paper block
filip_pine said:
try this ROM´s... maybe one of them will make your phone alive ...
Click to expand...
Click to collapse
Nothing, or i mistake all and fail, or i miss some important step.
In attached the errors :
D4N13L0N3 said:
Nothing, or i mistake all and fail, or i miss some important step.
In attached the errors :
Click to expand...
Click to collapse
did u get this error on all the 3 ROM´s ? (((
is there any chance that u can contact your seller from where did you bought the phone ? ask him for the Original ROM...
filip_pine said:
did u get this error on all the 3 ROM´s ? (((
is there any chance that u can contact your seller from where did you bought the phone ? ask him for the Original ROM...
Click to expand...
Click to collapse
No, not all, but everyone go on 100% with red line and not green circle.
I don't understand what error i made.
I think one thing, but the AGENT is right MTK_AllOne_DA.bin or i need to use the one in FIRMWARE folder ??
The files are :
lk.bin
logo.bin
preloader_lcsh82_wet_jb5.bin
What do you thing about it ???
Hi Filip,
i tried to delete USB drivers with USB Deview, after that, i re-charge a new one driver of device and then charge the ROM, this is the result :
The second image appear after about 15 minutes of time out.
D4N13L0N3 said:
Hi Filip,
i tried to delete USB drivers with USB Deview, after that, i re-charge a new one driver of device and then charge the ROM, this is the result :
The second image appear after about 15 minutes of time out.
Click to expand...
Click to collapse
ok, it seems that the problems are not the driver, sience you manage to get the phone recognized by pc... the problem seems to be SP Flash Tool...
my advice would be : reinstall again the windows, install again the USB Preloader VCOM Driver ( the correct way ) and install latest version of SP Flash Tool....
Then try to install again one of the 3 ROM´s that i give you... maybe you have luck buddy, i dont know...
is the only way you could get back your phone.... as you know, these phones are clones and is very hard to find compatible ROM´s and replacements parts....
I was having the ghost touches on my SM-N900 Note 3 Clone and the only solution was to change the digitizer, but : i can´t change it, sience i dont find anywhere Note 3 Clone digitizer replacements... only solution was to put the phone in a box and dont use it... ((
filip_pine said:
my advice would be : reinstall again the windows, install again the USB Preloader VCOM Driver ( the correct way ) and install latest version of SP Flash Tool....
Click to expand...
Click to collapse
I tried on my laptop with new OS installed and no antivirus installed, but the problem is the same.
I tried this tools : SP_Flash_Tool_v5.1352.01
and this : SP Flash Tool v3.1332.0.187
and the tools inside the ROM folder, but nothing. :crying:
Could you link me please the USB Preloader VCOM Driver ( for win7 64bit ), i guess the problem is that i used the bad one
Very thank you again for your help. :good:
Code:
**** DISCLAIMER ****
This post is an EXPERT-LEVEL Post.
I am NOT RESPONSIBLE for what you do to your device.
Please not that I am still working on a solution to this brick.
Hello XDA-Developers,
I recently got my hands on a Meizu M3 note and, of course, wanted the newest - nougat - firmware on it. It seems I accidently flashed a incompatible (or currupted) Update (flashed an A Firmware on a G version phone). Sadly it broke down and showed only vertical stripes on it's display.
Image here: https://ibb.co/cpGunm
After some hours research I found some information on how to reflash the M3 note via SP Flash Tool here and here. Since the first tutorial is for the M3 and M3s and the second tutorial is for the M model of the device (I've got the L model) there are some changes needed for it to somehow magically work.
I exchanged files provided (such as preloader.bin, lk.bin etc) with the matching ones from the latest Official Global Firmware from Meizu. Just extracted them out of the update.zip. (Don't forget to select the Authentication File!)
Image here: https://ibb.co/k3zYDR
Short flashing tutorial: make sure your device is turned off and disconneced then click "Download" and connect your device via USB. Don't worry if it now shows an error like "Download DA Failed", just dismiss the error and click "Download" again. It should flash the device now.
Sadly it is not possible to flash the boot.img provided in the latest official update.zip from Meizu (you'll get an security mismatch error). BUT the boot-verified.img provided by the chinese archive is flashable and is accepted by the device. The device is now in a bootloop, fastboot is accessible via holding Vol - and Power, but no recovery access via Vol+ and Power
The files seem to be repaired now but the display still shows these stripes - I think the firmware actually fried something on the display chipset. I bought a replacement screen and then will update this thread as soon as possible. If you have any Ideas of how to unbrick the device feel free to discuss.
Update 18.11.2017
Thanks to @ncristian !
I did as he suggested, downloaded and flashed the files from the russian forum here (if you do not speak russian and want to get straight to the point: Direct Download Link)
I still have the stripes on my screen but the device booted up successfully and got recognized again by my computer! While booting up I could see the stripes changing their color slightly as the bootanimation of flyme was playing. I guess I will have to replace the screen to make the display error go away... I will update this post as soon as I did so
Update 10.11.2018
Sadly I never actually exchanged the screen, I'm running a Pro 7 Plus as a daily driver now and I'm loving it
Update 19.05.2019
I have attached the boot-verified.img as someone requested it
I had the same problem and I solved thanks to this: https://4pda.ru/forum/index.php?showtopic=739028&st=24480#entry65580668 and Google Translate; I downloaded the .zip, installed drivers, launched the flash tool and flashed files contained in the folder L691H (Remember to install drivers and disable antivirus or it will not work). Then I downloaded FlyMe 6.1.0.0G, went into recovery with vol up + power, copied the update.zip into the device "Recovery" and flashed it; the only problem I had is that the phone charged but he didn't recognize the battery level; by reflashing the files contained in the 4pda .zip, the battery level went up (obviously, after leaving the phone charging for about an hour).
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Rajdas26 said:
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Click to expand...
Click to collapse
Try reflashing via the original recovery, that might be your easiest solution. If that doesn't work you might try your luck with something like SP flash tool
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
shawn_mendes said:
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
Click to expand...
Click to collapse
I have attached the file to the first post. Good thing I never delete anything :angel:
m3shat said:
I have attached the file to the first post. Good thing I never delete anything :angel:
Click to expand...
Click to collapse
First of all, thank you mate I successfully downloaded the boot verified. But still it didn't turned on. Just no power but recognized by the sp tool. I'm starting to think that downloaded again the wrong firmware. I also found out that their are two main board(or whatever is that). So this global firmware can be flashed in the both L and M series. I'm wondering what firmware you used to flash. Again, thank you in advance ^_^
l got same problem .. (because I'm not read careful )l tired to flash using many firmware or using boot verified .. i tired that for 2 Days.. So l give up.. take my device to profesional service . and solved. solved with Emmc repair ..
my device is L681H.
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.
SORRY WAS INACTIVE FOR SOMETIME... NOW IM BACK YOU CAN ASK AGAIN...
ALL CHIPSETS UNBRICKING METHOD HAS BEEN POSTED
Hi you may ask me anything related to android and I promise to answer within 24 hours and m reply will definitely work for you.
*****************************************************
SPECIALIST IN ROOTING, DEVELOPMENT, HACKING, SECURITY BYPASS, RECOVERY, FLASHING, CUSTOM ROM'S
*****************************************************
SEE YOU SOON
*****************************************************
•NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE•
LG Aristo v10g Metropcs
How do i start configuring this phone without a google account?
A friend who was using it gave me this phone but forgot the boot password and the google account was not of him. So, now, we can´t use the phone.
Mephis96 said:
How do i start configuring this phone without a google account?
A friend who was using it gave me this phone but forgot the boot password and the google account was not of him. So, now, we can´t use the phone.
Click to expand...
Click to collapse
You mean to say that the phone is in frp mode?
(Factory reset protection)
Yes
FRP..... thanks, id did not know what it means.
Yes, it is in FRP
Mephis96 said:
FRP..... thanks, id did not know what it means.
Yes, it is in FRP
Click to expand...
Click to collapse
Can you please tell me the phone model and it's info.
LG Aristo v10g from Metropcs
x.ak**** said:
Can you please tell me the phone model and it's info.
Click to expand...
Click to collapse
Ita LGMS210 v10g.
What's more do you want me to send? I dont know which information do you need?
[PC] HOW TO CURE A BRICKED M-TEK DEVICE!!
///////////////////////////////////////////////////////////////////////////////////////////
• Download and Install the Android USB drivers for your device that I have mentioned below.
• Power Off your device and remove the battery (only if it's removable)
• Download the stock ROM or the Custom ROM on your PC that you want to flash. (GIVEN BELOW)
• Download and extract SPFT (Smart Phone Flash Tool) on your PC, you will be able to see the files shown in the picture below. (Pic 1.1)
• Open Flash tool.exe (Pic 1.2)
• Once SPFT is launched tap on Download tab. (Pic 1.3)
• In download tab click on Scatter-Loading button. (Pic 1.4)
• Now locate the Scatter File that you will find in the Stock ROM folder that you downloaded in step 3. (Pic 1.5)
• Click on Download button to start the flashing process.(Pic 1.6)
• After finishing a success message will appear. (Pic 1.7)
///////////////////////////////////////////////////////////////////////////////////////////
Downloads:-
https://androiddatahost.com/b9cyw (DRIVERS)
https://spflashtool.com/download/SP_Flash_Tool_v5.1744_Win.zip (SPFT)
https://www.needrom.com/download/lenovo-s850/ (ROM FOR LENOVO S850, REGISTRATION NEEDED ON WEBSITE TO DOWNLOAD THE ROM)
///////////////////////////////////////////////////////////////////////////////////////////
Mephis96 said:
Ita LGMS210 v10g.
What's more do you want me to send? I dont know which information do you need?
Click to expand...
Click to collapse
I was working on another project that you can see below give me 1 hour I'll get back to you ASAP.
Best tool like SetCPU for controlling CPU with profiles?
SetCPU doesn't allow core control though
Mephis96 said:
Ita LGMS210 v10g.
What's more do you want me to send? I dont know which information do you need?
Click to expand...
Click to collapse
How to BYPASS FRP LOCK!
Test conducted on Virtual Machine on my PC
****************************************************************
I am not responsible for any damage you may cause to your device!
****************************************************************
****************************************************************
Never wanted to upload it but did it because I aim at helping people.
****************************************************************
Google FRP (factory reset protection) is aimed at making a stolen phone less valuable.
We usually keep our phones locked with a password or pattern but once its stolen it is easy to erase the data (via Hard Reset) and reuse the phone. With Google FRP in place, whenever the phone is formatted using hardware keys it will ask for the last synced google account details before proceeding further.
///////////////////////////////////////////////////////////////////////////////////////////
Until now, everytime some sort of hack comes out to bypass this screen and then its patched with a security update very soon. Same is the case with LG Aristo. There is a working solution as of now but it may not last long. Let’s see how to get this working –
///////////////////////////////////////////////////////////////////////////////////////////
How to Bypass LG Aristo Google Account –
This process is lengthy, but it’s a sure shot method and works every time.
We need 2 apps to complete this bypass process. They are Shortcut Master Lite and Sidebar Lite. Download the zip file from below link.
DOWNLOAD
>Extract the zip file and transfer the apk files to a micro sd card. Install the SD card in your LG Aristo before proceeding further.
///////////////////////////////////////////////////////////////////////////////////////////
Mephis96 said:
Ita LGMS210 v10g.
What's more do you want me to send? I dont know which information do you need?
Click to expand...
Click to collapse
Done
Drop a like on all my replies so I can stay encouraged and help you further.
YeshYyyK said:
Best tool like SetCPU for controlling CPU with profiles?
SetCPU doesn't allow core control though
Click to expand...
Click to collapse
You may use Kernel Manager it's super useful and will do what you're asking for!
Hi ! Could you help me with my problem ?? https://forum.xda-developers.com/search.php?searchid=446201503
No one seems to be able to help me... thanks a lot!!!!
antoflos said:
Hi ! Could you help me with my problem ?? https://forum.xda-developers.com/search.php?searchid=446201503
No one seems to be able to help me... thanks a lot!!!!
Click to expand...
Click to collapse
I will definitely help you just give me one hour but can you post the following info:
Model Number:
Exact Problem:
How that problem occured:
Model Number: SM-G935F / Galaxy S7 edge
Exact Problem : I can't go back to the dock ROM
How that problem occured : Last week, I wanted to try to change my phone a SM-G935F on a custom rom " Minotaurus Oreo V10". I did it successfuly but didn't like it so much so I decided to go back to stock Rom.
I used Odin and a stock ROM for that but I think I made a big mistake by not wiping with TWRP before flashing with Odin.
It resulted that my phone was stocked on the S7 edge logo. Luckly I can go on download mode so it's not hard bricked but Odin failed on every flash I've tried. It stoped at the step "config.msi"
To flash I used this dock Rom : SM-G935F_1_20161201150115_pbdym44h2s_fac
x.ak**** said:
I will definitely help you just give me one hour but can you post the following info:
Model Number:
Exact Problem:
How that problem occured:
Click to expand...
Click to collapse
Hey man this quite difficult and i need to install this phone's firmware on my VIRTUAL Machine, basically I request you to wait for the time being so I can save your phone.
Drop a like on all my comments above to encourage me.
Huawei P10+ Firmware on Huawei P10 - by accident
Hi:
On my P10, I used Firmwarefinder for Huawei to find the firmware (Oreo with EMUI 8) and after verifying, I downloaded and upgraded the P10 to new firmware. After reboot, the dpi is seemed changed (as picture attached) and when I went to check it on about phone, it says Model is VKY (which is Huawei P10+) - picture attached.
Is there a way to rollback and install the correct firmware on this phone somehow?
antoflos said:
Model Number: SM-G935F / Galaxy S7 edge
Exact Problem : I can't go back to the dock ROM
How that problem occured : Last week, I wanted to try to change my phone a SM-G935F on a custom rom " Minotaurus Oreo V10". I did it successfuly but didn't like it so much so I decided to go back to stock Rom.
I used Odin and a stock ROM for that but I think I made a big mistake by not wiping with TWRP before flashing with Odin.
Click to expand...
Click to collapse
***********************************************************************************
I AM NOT RESPONSIBLE FOR ANY FURTHER DAMAGE THAT MAY BE CAUSED TO YOUR DEVICE...(UNLIKELY TO HAPPEN)
***********************************************************************************
For being able to make the downgrade operation you will have to use a Windows based computer on which you will then install Odin (an official program developed by Samsung and used on update types of operations).
***********************************************************************************
Download Odin on your computer; afterwards install the program by following on screen prompts.
The Samsung Galaxy S7 Edge USB drivers must be installed on your PC too – use Samsung KIES in that respect.
Download the stock / official Android OS for your S7 Edge – from SamMobile or from Samsung’s official website.
Power off your device and reboot into download mode: press and hold the Power, Volume Down and Home buttons for a few moments; then connect your phone with your computer with the help of the USB cable.
After making sure that Odin has recognized your device (the “added” message must be displayed and the ID:COM field should be turned yellow or blue) from the program select the PA option.
Load the firmware file; don’t select the Re Partition and Auto Reboot options; click on Start when done.
Wait while your SGS7 Edge is being updated; when done, remove the USB cord and reboot your phone.
For further info related to the update process reply to my thread
LIKE ALL MY COMMENTS TO ENCOURAGE ME TO HELP YOU.
xironimoh said:
Hi:
On my P10, I used Firmwarefinder for Huawei to find the firmware (Oreo with EMUI 8) and after verifying, I downloaded and upgraded the P10 to new firmware. After reboot, the dpi is seemed changed (as picture attached) and when I went to check it on about phone, it says Model is VKY (which is Huawei P10+) - picture attached.
Is there a way to rollback and install the correct firmware on this phone somehow?
Click to expand...
Click to collapse
No pictures attached!! and yes you can roll back to the stock ROM or even customize the DPI according to your phone [ROOT REQUIRED]
Let me know which one you prefer?
Also like all my comments above to encourage me to help you even faster.
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