Hello All!
Relative noob here...but more seasoned all the time. Firstly my viewpad device info from FTM:
SWVer=3.410
Model: FM6-001
HWVer: 107
In a nutshell: My bluetooth wasn't turning on (would turn on..then off). So tried to fix by:
1) Rooting and install CWM 5.0.2.6 (awesome tool BTW) and various ROMs, all done with success.
2) No good, oh well now want to give up. Contacted Viewsonic got RMA to return unit..however now concerned they'll not honor warranty if I rooted the device (sigh). So thought I'd return to stock. I did backup..but was already rooted when I thought of it.
3) Trying to return to stock using many versions Sutl3 and Sutlr...and on different PCs none work..once it boots to CWM menu...just stalls with error eventually.
4) Tried to install Napster's CWM with Recovery Menu to be able to return to original state with stock recovery. My version of CWM won't install it...errors out (another great tool though by the sounds of it).
5) Can't use fastboot..never sees device...although ADB works OK. Believe that the Bluetooth issue may be a hardware problem and may be effecting devices ability to work in "download mode". Note that HS-USB device is never present in device manager in Windows even though driver is installed.
So...my question...how can I return my device to stock with one of the below .nb0 files without stock recovery, sutlr or sutl3?
Files I have:
FM6-3310-0-5029-A02.nb0
FM6-3350-0-1008-A01.nb0
Can I somehow use CMW? Can I somehow use adb and "flash_image"?
Will super appreciate any thoughts!
Many thanks in advance!
Johnster25
If I remember correctly, you use SUTL3 from Viewsonic on your PC with the *.nb0 file in the same sub/directory - and just run it to flash the stock ROM or return it to factory condition, you do NOT use CWM to flash or re-install the *.nb0 file ... Part of this process involved overwriting the CWM installed on your rooted device & reversing it to become unrooted, look under the Development subforum here in this section as there's a link/discussion about how to restore, please double check on the details written up.
Also, make sure you have a mSD card in the slot - and that the USB drivers are loaded & running (they should be installed already back then) - might want to power down & restart the PC and do the same to the Vpad7.
Let us know how it go & good luck !
Many thanks for your response.
Well, what has happened when I've used SUTL3 so far is that I select the .nbo image I wish to flash, then the program restarts teh VPAD7 into recovery mode.
From what I've read, after a few moments the phone is then supposed to enter some sort of "download mode" whereby the new image is pushed across the USB cable.
It's at this point with SUTL3 seems to error out, and the phone simply remains in CWM.
I've read a few posts that suggest that not using the correct image could produce a response like this, so I'll retry again this PM having tried re-downloaded the two .nbo files I've tried, and one I've not tried.
Will let you know how it goes!
J.
Hi Again,
OK I've retried it with a fresh copy of SUTL3, and new .nb0 files. Still no good.
Take a look at the enclosed pictures. The first time I try to run SUTL3 the device not configure error shows up. By this point CWM is showing on the VPAD7. I try to run SUTL3 again in this state and now the device not detect error shows up.
So all in all it seems to me that the device when in CWM mode is not exposing an interface to the computer...or the computer lacks the driver needed to utilize the interface.
I've also enclosed a picture of my windows devices when the VPAD7 is connected, as well a copy of the drives that show up when it's connected. The only time the drives change is when the VPAD7 is in CWM mode, at which time the H: drive (where the adb program are) is not present.
So am I missing a driver?
BTW: Have tried to copy down the synchronization program that is on the H: Drive and ran it while running SUTL3...thinking somehow it acted like a bridge to the VPAD7 (I've seen some posts that suggest this). Still no good.
J.
OK..one more piece to the puzzle...or maybe off the trail...but when trying on two differnt PCs when the VPAD7 is first plugged in I get one set of driver installs...and note that the HS-USB has an error.
Later when trying to run SUTL on it...another set of driver installs...again HS-USB error.
See enclosed.
try run sutl with viewpad in FTM mode that worked for me good luck
I have same problem before..n my solution is change back CWM with old ..mine to CWM 2.5.1..found that CWM 5.0.2.6 got problem with SUT L3..and everythind done successfully..as long u can still access ur Viewpad to change CWM its ok..
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Alleycatzero you're a genius! Running SUTL in FTM mode has done it!
THANK YOU!!!!!!!!!!!!!!!!!!!!!!
Johnster25 said:
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Click to expand...
Click to collapse
This is under the Development section - just d/l and unpack the zip file, copy to mSD card & follow the instructions. This verison should be the earlier one and I personally find it worked best together with ext3 and/or ext4 partitioning as needed.
http://forum.xda-developers.com/showthread.php?t=1015005
The issues with SUTL3 and other apps not working/running has to do with the usb drivers not auto-installing & running as they should, try to uninstall Vpad7 drivers, reboot the PC - turn off any firewall and anti-virus software, connect the Vpad7 and let it finish installing/rebooting both devices again. Then, turn back on antivirus & firewall so that you will have easier time flashing rom, connecting mSD card & copying/moving files, etc.
Have a Sprint TP2. Had Android running off my SD card last year and ready to try it again. My main computer is Win 7 64-bit, but I have access to other computers with Win 7 32-bit, and possibly another with XP if it is necessary.
-----------8<------------------
A few questions, if you please.
-----------8<------------------
I) To get a *complete* backup of my phone, I can use SPB Backup, right? (Will allow me to get *everything* back the way it is right now?)
II) Recommended Android ROMs are OMGB and GBX0*?
III) For OMBG:
.....1) I need to have ADB working (I installed it last night)
.....2) The readme said I needed to "have all the drivers installed". I don't know what that means.
.....3) The "How-To" also said I "must have Fastboot working".
.......a) Where do I get this? From here?
.......b) Is it difficult to install and/or run?
.......c) Found this, but no idea what it means
IV) For GBX0*, I need to download and install ClockworkMod Recovery. Where do I get this? From here?
You'll need the same things for Android NAND. They both require fastboot, and some sort of recovery. I prefer CWM.
Edit - Your links are pretty much all wrong. You should be getting pretty much everything from here.
Use whatever ROM you desire. Fastboot and CWM are agnostic to ROM.
For any NAND ROM to work, you need adb working. If adb works, fastboot *should* work.
Fastboot flashes from the NBH. If you flash the NBH for Android, you have fastboot (installed on the phone...)
It is a little difficult/tricky. Not for the feint of heart. Read a lot, test a lot, before you flash anything. Make sure you know the process and what you need to do.
Most importantly perhaps is a fully charged battery. I've seen a few users get stuck in fastboot mode because they let their battery die - and now without CWM or WinMo, the phone won't charge. Don't want to be in that situation.
If battery life is most important to you then OMGB is the way to go. If you need native tethering then GBX is the way to go. I use GBX as my daily. Either way read the threads, and you can see the features that work on either.
I am trying to get my Rhod 250 prepped. I have the flash program to unlock the Hard-SPL but the phone will not connect via USB and I am fairly certain attempting a flash over Bluetooth would brick the phone. I have tried disabling Advanced Network Functionality and have also tried installing the .cab file found in another thread but neither have made a difference. I am running Windows 7 64-bit Ultimate, and the Rhod is showing up as Unknown USB Device.
bigspoondude said:
I am trying to get my Rhod 250 prepped. I have the flash program to unlock the Hard-SPL but the phone will not connect via USB and I am fairly certain attempting a flash over Bluetooth would brick the phone. I have tried disabling Advanced Network Functionality and have also tried installing the .cab file found in another thread but neither have made a difference. I am running Windows 7 64-bit Ultimate, and the Rhod is showing up as Unknown USB Device.
Click to expand...
Click to collapse
Please make sure ADB works before you flash anything.
You need to do the unlock before you can flash any unsigned images regardless. HSPL is the first thing before flashing anything - custom WinMo ROM or Android.
All right, so you wanna Full Unlock your Nokia L710 device but you faced a website on the internet saying it was impossible, which turned you down. There's a little thing you should now: most site are whether wrong or outdated, so it is very possible to full unlock a Nokia L710 (and theoretically a Nokia L800 too). But instead if you just want to developer unlock your device here's a thread that might help you with steps to officially dev unlock your phone free of charge: http://forum.xda-developers.com/showthread.php?t=1569119
It is very easy to full unlock your phone, but you must know that some knowledge and some nerves are required... Here it goes my experience on unlocking my Nokia Lumia 710 device. Note it has not been tested on Nokia Lumia 800 and that the stock rom with Qualcomm's bootloader is for Lumia 710 devices only.
Step 1.
First we must know if your device has its bootloader unlocked. Nokia phones were previously (and prior to tango updates hold that too) shipped with Qualcomm's boot loader, which allows nand access (needed to flash roms) and allows us to unlock our phones. To do so you must turn your device off, then press Power and Volume Up key till it vibrates. Then connect it to your Windows PC, where you shall get a notification whether saying Nokia Dload (nokia's locked boot loader) or a Explorer pop-up asking you to format a flashdrive (do not do that). If you get the Explorer pop-up your good to go to Step 2 but if you got Nokia's Dload, don't panic.
You are able to downgrade the boot loader using an old rom (this one specific is from Russia) that holds the Qualcomm's unlocked one. For this you'll need Nokia Care Suite and the stock rom files. The stock rom files you might find here (http://forum.xda-developers.com/showthread.php?t=1599401), a great thread posted by Suzughia where you can learn more about this issue. Anyway, the file you need is in the FAQ session, second question/answer. The NCS file I used you can download here (http://www.4shared.com/file/0YxlvalR/Nokia_Care_Suite_5_20115126304.html?) from my 4shared account*, but for the latest release you'll might check the official site, just google it.
Once you got NCS installed you'll have to go to C:\Program Files\Nokia\Nokia Care Suite\Drivers\ and install WinUSB Drivers x86.msi (or, if you use Windows 64 bit, the respective file). Then go to C:\ProgramData\Nokia\Packages (note that ProgramData is a hiden folder) and create a new folder named Products. Within this folder you'll copy the folder you downloaded (and unzipped, its name shall be, in this case, RM-803).
Now on the start menu you search for Application Launcher, and the app that appears shall call the Nokia Care Application Launcher. There you choose Product Support Tool For Store, a tool that allows you to install any rom from recovery (even the phone you've already unlocked using this tutorial or bricked phones, by theory). Wait to app to load up and connect your device on the computer. Now select the “Automatic Product Selection” box and waits till it recognizes your device. Notice your device might restart once or twice.
Now, in order to install the rom on your phone you must firt open your device model (even if the program indentifies your phone). Go to File>Open Product and select your phone model (in this case the Nokia 710 RM-803). Now go to the sidebar and select Programming>Recovery, on Properties you'll see the information of the rom you downloaded. Select it and then click Start. Ready, your phone is being flashed with the rom 1600.3015.8107.12070, that holds the Qualcomm's bootloader. Wait for it to reboot and you're ready to go to step 2.
Step 2.
Now we're gonna install the custom fully unlocked rom to your phone over the stock rom we just installed. To do so you must have access to a Terminal prompt (wheter on a Linux distribution or on an emulator running on Windows; I strongly recommend you to use Linux, which is more reliable) which will allow you to write the rom image to the phone's flash memory. You'll also have to download the os image, which you can get from Lucifer3006 here (http://forum.xda-developers.com/showthread.php?t=1654415).
Once you have access to a Terminal prompt and to the os-new.nb file you're ready to go. It is discussed on the thread by Lucifer3006 the use o NSS (a Linux terminal emulator), which I don't have experience to share. For instance, I used Ubuntu 12.04 for the flashing.
First boot your phone into Qualcomm's driver mode (just turn off your device, and then boot up holding power + volume up untill you feel a short vibration and then connect your phone to the computer) . Now you have to know the "address" of your device (that's given by the system). Open up terminal and type:
fdisk -l
With this command you'll see a list of the registered blocks of the storage devices on your computer. Usually your device will be the second on listed (in the case you only have your hardrive and your device plugged to the computer) and it is named sdXY, where X is the name of your device and Y is the number of the partition. On my case my device was f.
Now navigate to the folder you saved the os-new.nb file in terminal (in my case I saved on the User's folder, where the terminal opens by default in Ubuntu, the distro I used, or in most Linux distros). To be sure verify if the file is there by typing "ls", it will show a list of the files on that folder. If everything's fine, now you should enter the command that will copy the os-new.nb file to the phone boot memory, so the rom will be literally installed when the phone is booted.
Type this command in:
dd if=./os-new.nb of=/dev/sdX9
Explanation: "dd" is the command that copies the "if" to the "of" partition with low level privilegies. In this case "if" is the os-new.nb file and "of" is the boot partition address of your device. Make sure to replace the X with your device name. For example, my device was named "f", so my address will be of=/dev/sdf9, where sdf9 stands for storage device f, partition 9**. The boot partition of Windows Phone is addressed as the nineth one of the device (it is not an statement).
Once done copying (it will give you no feedback but the blinking square, so when it's done you'll just see the prompt address again) you shall disconnect your device.
In order to boot your device you have to perform a hard reset (this will literally install the os-new.nb to your device). To do so you have to hold down power + volume up + camera key for 10 seconds, then release the power key but still hold the volume up and the camera key for more 5 seconds (this was said in other post I can't remember which, don't know if is the correct way, but it worked for me). If the device does not boot up you can remove the battery and place it again, now just turn it on normally, and it will boot into the custom fully unlocked rom.
Note that the WP Root Tool installed on the rom is the 0.9 version and as for up to today it has expired, so you won't be able to use it unless you set your device date to past August 2012. In Baazar you can install the newer version but for using it you must mark it as trusted in RootManager app included on the mod rom.
Post anything you have to say and if you have a doubt, just ask me and I might help with anything I'm capable of.
Notes:
Everything I posted here is upon my personal experience only. I do not own any rights over any file posted here through other threads. The responsability for them relies on the threads' holders then.
* I do not own any rights over this program and I just posted a personal link once I wasn't able to recall the original one. Also this is the only file who sucessfully recognized my device upon my experience.
** This is said just to make an example and clearify the idea, it is not its actual meaning for as long as I don't know its actual meaning.
All Links Used Here:
Nokia Care Suite version 2011.51.2.63046 5.0
http://www.4shared.com/file/0YxlvalR/Nokia_Care_Suite_5_20115126304.html?
Get Ubuntu Linux 12.04 for free
www.ubuntu.com
Nokia's 710 RM-803 Country Variant Russia direct download link:
http://narod.ru/disk/45935058001.2aaca38c9acf622332f4a81b5bf0e331/RM-803.rar.html (300mb)
How to Interp Unlock Nokia l710 original thread:
http://forum.xda-developers.com/showthread.php?t=1599401
RainbownMod v1.4 and older, also the original thread of discussion:
http://forum.xda-developers.com/showthread.php?t=1654415
Is it possible to get that ROM from somewhere else, all it does is download YandexBarChrome in russian!... lol
*nevermind... i installed the stupid bar and it let me get the file.
**I cant get this stuff to work.... I get an error when installing the NCS, it installs anyways, but then never detects my phone. Any help would be appreciated!!
XperianceIT said:
Is it possible to get that ROM from somewhere else, all it does is download YandexBarChrome in russian!... lol
*nevermind... i installed the stupid bar and it let me get the file.
**I cant get this stuff to work.... I get an error when installing the NCS, it installs anyways, but then never detects my phone. Any help would be appreciated!!
Click to expand...
Click to collapse
What operating system are you using? I usually get installation error and phone never detected when running it on Windows 7 or Windows 8 64bit.
You might try reinstalling the NCS, and if it holds the same error, check the official site for the updated program and try it.
When you connect your phone to the computer, does the program recognizes an unidentified handset or it doesn't recognize your phone at all?
Unlocked
Sent from my Lumia 610 using XDA Windows Phone 7 App
My problem is this:
File C:\Documents and Settings\All Users\Application Data\Nokia\Packages\Products\RM-803\RM803_059M5W4_Qualcomm_DLOAD.vpl has no signature.
I have a problem. After I copy the ROM to the memory, I can't seem to boot to it. I feel the vibrations but everything is black. Please any help
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