Related
Hallo everyone.
I have just tried to follow this guide to install Google Play and so on: http://forum.xda-developers.com/showthread.php?t=2256075
Guide:
I'm here for help you, and yes I bought K900
Here is the international .inb file to flash.
Part One: How flash international version:
1. create SDFUSE folder in the / of sdcard.
2. insert inb file there
3. go to fastboot mode (Vol+ + Power) and choose sdfuseupdate
4. done.
you'll get official international 47 rom (ROW region). It has google apps, it has play store.
INB file is here:
https://mega.co.nz/#F!xNdywAJA!AFbE_HikuoFODLpoc1j7Yg
But right after the message saying SDCARD UPDATE COMPLETED (as i remember it), the phone wont start again. The three buttons on the front flashes and nothing else happens.
Any clues to what might be the problem?
I hope you can help me!
Best regard
Jonas Kristiansen
Question
Hi Jonas,
Sorry to hear that.
Did you totally brick your phone? Can you still go into recovery or Hboot?
Is your phone recognized by adb and fastboot?
If you tell me more, maybe I can help.
Denis
Jonas Kristiansen said:
Hallo everyone.
I have just tried to follow this guide to install Google Play and so on: http://forum.xda-developers.com/showthread.php?t=2256075
Guide:
I'm here for help you, and yes I bought K900
Here is the international .inb file to flash.
Part One: How flash international version:
1. create SDFUSE folder in the / of sdcard.
2. insert inb file there
3. go to fastboot mode (Vol+ + Power) and choose sdfuseupdate
4. done.
you'll get official international 47 rom (ROW region). It has google apps, it has play store.
INB file is here:
https://mega.co.nz/#F!xNdywAJA!AFbE_HikuoFODLpoc1j7Yg
But right after the message saying SDCARD UPDATE COMPLETED (as i remember it), the phone wont start again. The three buttons on the front flashes and nothing else happens.
Any clues to what might be the problem?
I hope you can help me!
Best regard
Jonas Kristiansen
Click to expand...
Click to collapse
Same problem
Hello
I have same problem, i brick my K900. I try to start it, but phone is really little ignorant, absolutly not response to all. Flash using xFSTK is without chance.
Yep, Recovery and DroidBoot is unavilable. Phone only one flash touch buttons and nothing more... :crying:
Can you help me? I thing, hard-brick is too hard to solve.
Sorry for my english...
Maybe it will be usefull:
Volume down, hold it, then power button, Testing Menu appear, Droidboot, Recovery, Clear cache, Clear data (factory reset), reboot.
how unbrick ur k900 device
Jonas Kristiansen said:
Hallo everyone.
I have just tried to follow this guide to install Google Play and so on: http://forum.xda-developers.com/showthread.php?t=2256075
Guide:
I'm here for help you, and yes I bought K900
Here is the international .inb file to flash.
Part One: How flash international version:
1. create SDFUSE folder in the / of sdcard.
2. insert inb file there
3. go to fastboot mode (Vol+ + Power) and choose sdfuseupdate
4. done.
you'll get official international 47 rom (ROW region). It has google apps, it has play store.
INB file is here:
https://mega.co.nz/#F!xNdywAJA!AFbE_HikuoFODLpoc1j7Yg
But right after the message saying SDCARD UPDATE COMPLETED (as i remember it), the phone wont start again. The three buttons on the front flashes and nothing else happens.
Any clues to what might be the problem?
I hope you can help me!
Best regard
Jonas Kristiansen
Click to expand...
Click to collapse
(my english is veryyyyyyyyyy bad)
dont worry . there is a simple method :
this method work for hardbrick and softbrick too.
first download a favorite Rom you want
u can choice ur Rom from this page : http://m.kaskus.co.id/post/5300581ffbca17d47b8b457c#post5300581ffbca17d47b8b457c
download and install manufacturing flash tool and intel android device usb driver
https://dl.dropboxusercontent.com/u/26833962/K900 Tools/ManufacturingFlashTool_Setup_6.0.2.exe
http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
second Refer this : http://forum.xda-developers.com/show...postcount=3245
This method require computer with driver and software installed and USB cable for sure
( unzip ur rom and open xml file on ur rom with manufacturing flash tool softwre)
maybe this video can help you too :
https://www.youtube.com/watch?v=BhvA_T694kw
This method works on my hardbrick device succeesfully
tatu63 said:
(my english is veryyyyyyyyyy bad)
dont worry . there is a simple method :
this method work for hardbrick and softbrick too.
first download a favorite Rom you want
u can choice ur Rom from this page : http://m.kaskus.co.id/post/5300581ffbca17d47b8b457c#post5300581ffbca17d47b8b457c
download and install manufacturing flash tool and intel android device usb driver
https://dl.dropboxusercontent.com/u/26833962/K900 Tools/ManufacturingFlashTool_Setup_6.0.2.exe
http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
second Refer this : http://forum.xda-developers.com/show...postcount=3245
This method require computer with driver and software installed and USB cable for sure
( unzip ur rom and open xml file on ur rom with manufacturing flash tool softwre)
maybe this video can help you too :
https://www.youtube.com/watch?v=BhvA_T694kw
This method works on my hardbrick device succeesfully
Click to expand...
Click to collapse
hi tatu63
Me too got my K900 bricked while updating Rom from MFT .
Its not starting anymore. Complete black screen no menu lights at all.
When i connect my phone to usb cable it shows this in MFT tool and hangs up
07/01/14 12:47:15.886 DEBUG : New Android device -> serial: MedfieldEC710F76 status: 0 port: 1
and
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:
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
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?
Hello,
After try to flash the recovery on my device, the device stay lock on secure boot.
I have probably missing a step for the secure boot, well.
Archos send me the firmware and windows driver and DA file, i can link the files if you want.
But after many test with many version of SP flashtools I have always an error
On linux : STATUS_DA_HASH_MISMATCH (-1073283068) , MSP ERROR CODE : 0x00.
Can Help me ?
Thanks
buzz-27 said:
Hello,
After try to flash the recovery on my device, the device stay lock on secure boot.
I have probably missing a step for the secure boot, well.
Archos send me the firmware and windows driver and DA file, i can link the files if you want.
But after many test with many version of SP flashtools I have always an error
On linux : STATUS_DA_HASH_MISMATCH (-1073283068) , MSP ERROR CODE : 0x00.
Can Help me ?
Thanks
Click to expand...
Click to collapse
Finally the solution it was in the good files versions, I used this one :
- OS : WIN10
- Tools: SP Flash tool V5.1744
- Driver : MTK V1.0.8 and install DRIVER AUTO 1612
- FIRMWARE : ac70-20180912-1740-New
Hello buzz-27, it would be great, if you could tell me, where you can download the Firmware - same problem here Thank you!!!
buzz-27 said:
Hello,
After try to flash the recovery on my device, the device stay lock on secure boot.
I have probably missing a step for the secure boot, well.
Archos send me the firmware and windows driver and DA file, i can link the files if you want.
But after many test with many version of SP flashtools I have always an error
On linux : STATUS_DA_HASH_MISMATCH (-1073283068) , MSP ERROR CODE : 0x00.
Can Help me ?
Thanks
Click to expand...
Click to collapse
Hi,
I have recently bricked my AC70HELLO and tried uncessefully to flash stock firmware (from firmwarefile.com/archos-hello-7 ) but always got STATUS_DA_HASH_MISMATCH (with SP Flash Tools V5.1924 and V5.2020) or STATUS_BROM_CMD_SEND_DA_FAIL (with SP Flash Tools V5.1744) errors (with MTK_AllInOne_DA or DA_PL defaults DA).
Could you please share the Download Agent and the stock firmware from Archos ?
I have asked Archos for it in vain, they respond me "Sorry we don't have any FW available for this device. Thanks for your understanding," which got me a bit mad... I mean if my device's constructor doesn't have its stock firmware then who does ?
Here's the "latest" fimware from Archos http://update.archos.com/AFMv2/downloads/ac70hello_archos/20181101.075911/update.zip
Does anybody happen to have a reliable guides and reliable downloads to flash other firmwares to this Hello 7?
I tried several guides but somehow they are inconsistent, incomplete or simply not working. Some say I need TWRP without a link to a working image, others say I could use fastboot which generates "not allowed in locked state". I found out myself that I could work around that error by running "fastboot oem unlock" but after flashing, my Hello keeps hanging in a boot loop. (also after "fastboot oem lock")
Fortunately with @fraenK 's link, I could revert back to stock.
I have been using the Pixel Experience 10 GSI ROM from Expressluke so far. Other GSI ROMs should work as well. https://forum.xda-developers.com/t/gsi-expressluke-built-gsis.4003457/
fraenK said:
Here's the "latest" fimware from Archos http://update.archos.com/AFMv2/downloads/ac70hello_archos/20181101.075911/update.zip
Click to expand...
Click to collapse
Thanks but this is unusable without a working recovery wich I don't have since I'm bricked (corrupted logo.img so crash before booting in anything) would you know where I could find the download agent to use with sp flash tools ?
Archatos said:
Does anybody happen to have a reliable guides and reliable downloads to flash other firmwares to this Hello 7?
I tried several guides but somehow they are inconsistent, incomplete or simply not working. Some say I need TWRP without a link to a working image, others say I could use fastboot which generates "not allowed in locked state". I found out myself that I could work around that error by running "fastboot oem unlock" but after flashing, my Hello keeps hanging in a boot loop. (also after "fastboot oem lock")
Fortunately with @fraenK 's link, I could revert back to stock.
Click to expand...
Click to collapse
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ -> how to install a GSI (with fastboot or TWRP)
https://forum.xda-developers.com/t/aosp-10-0-2019-12-06-quack-phh-treble.3992559/ -> AOSP with or without gapps and stock GSI rom (if I recall correctly before bricking, the Hello 7 needs an arm64 A-only image)
Hello,
If I can help you, I create a zip file with Driver, Firmware and the compatible SP_Flash for this firmware.
I flashed my Hello with success and I don't sure of all step, cause many test before sucess.
Just put WIN10 in "Test Mode" can help
http://dl.free.fr/getfile.pl?file=/Zn8HQVpO
press "Valider et télécharger le fichier"
Now I am in GSI Android and the Hello work perfectly !
I got same problem with Archos hello 10 version where can i find stock rom for this device? @fraenK @buzz-27 maybe you know?
urkelz said:
I got same problem with Archos hello 10 version where can i find stock rom for this device? @fraenK @buzz-27 maybe you know?
Click to expand...
Click to collapse
http://update.archos.com/AFMv2/downloads/ac101hello_archos/20181114.085412/update.zip
Thanks alot @fraenK downloading now. Anyone got a DA file I can use? Probably will get DA hash mismatch.
Hi everyone,
I bricked my Archos Hello 7 by trying to flash TWRP.
I'm looking to flash my device but it's hard to find informations for this device and nothing works for me.
I tried with SP Flash tool V5.1744 and few drivers versions without results.
I always have STATUS_DA_HASH_MISMATCH or BROM_CMD_SEND_DA_FAIL.
Every time I plug my device, the detected USB is the "Mediatek PreLoader USB VCom", do you think it's the good driver ?
@buzz-27 can you (or someone else) upload your file again, the link on Free is dead.
@Dawnowl444 did you solve your flashing problem ?
Thanks guys.
CameleonTH said:
Hi everyone,
I bricked my Archos Hello 7 by trying to flash TWRP.
I'm looking to flash my device but it's hard to find informations for this device and nothing works for me.
I tried with SP Flash tool V5.1744 and few drivers versions without results.
I always have STATUS_DA_HASH_MISMATCH or BROM_CMD_SEND_DA_FAIL.
Every time I plug my device, the detected USB is the "Mediatek PreLoader USB VCom", do you think it's the good driver ?
@buzz-27 can you (or someone else) upload your file again, the link on Free is dead.
@Dawnowl444 did you solve your flashing problem ?
Thanks guys.
Click to expand...
Click to collapse
Hi,
My AC70HELLO is still bricked unfortunately. I've got a corrupted logo.bin and no way to flash stock rom except with SP Flash Tool. But I can't get passed STATUS_DA_HASH_MISMATCH error.
I tried this utility without much success...
GitHub - MTK-bypass/bypass_utility
Contribute to MTK-bypass/bypass_utility development by creating an account on GitHub.
github.com
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
With --force I still get STATUS_DA_HASH_MISMATCH and the utility says "Device secure boot: False ; Device serial link authorization: False ; Device download agent authorization: False" wich is weird...
Let me know if you got any more luck with that than me.
If your AC70HELLO is'nt really bricked you can try to flash back stock recovery via fastboot.
Hi Dawnowl444,
Thanks for your tips, I gonna try with bypass_utility but without hope .
Maybe we need to do some hardware tweak to allow to flash the device.
There is here a French tutorial to disassemble the Hello 7. http://rnc.free.fr/hello7/hello7.html
In the firmware I found online, the file Checksum.ini refers to the version 1708 of SP Flash Tool, I tried with itn but without success, maybe it can be successful for you.
Unfortunately, I can't boot into recovery mode, that's why I try to flash with the Flash Tool.
If I succeeded to flash my device I will let you known.
buzz-27 said:
Hello,
If I can help you, I create a zip file with Driver, Firmware and the compatible SP_Flash for this firmware.
I flashed my Hello with success and I don't sure of all step, cause many test before sucess.
Just put WIN10 in "Test Mode" can help
http://dl.free.fr/getfile.pl?file=/Zn8HQVpO
press "Valider et télécharger le fichier"
Now I am in GSI Android and the Hello work perfectly !
Click to expand...
Click to collapse
Hello @buzz-27 , could you upload the file again?
I was try update my Hello 7 and now it restarting continuously.
Hello, is not possible immediately but I try to push the file in a few weeks or before maybe.
Ok thanks. By mistake I'm flashed the Hello 10 ROM in my Hello 7, and now it restarting continuously. I can enter in fastboot but I cannot flash the ROM - error: FAILED (Remote: not allowed in locket state) Do you know another way to flash the correct firmware? I can not enter in recovery mode.
Hello guys for Hello device
Link below with SP tool, Driver and Firmware for Hello 7 this pack work on my Hello 7.
Upload files for free - Restore_Archos_AC70Hello.zip - ufile.io
Download Restore_Archos_AC70Hello.zip for free from ufile.io instantly, no signup required and no popup ads
ufile.io
enjoy !
Thanks buzz-27, unfortunately, it didn't work for me.
Can you tell us which DA did you use ? I have tried all DA from the SP Flash tool with no results.
Maybe we have a different model/revision, mine has the FCC ID : SOVAC70HELLO