Related
We now know that the new vibrant phones have the hardware key disabled to enter recovery mode. But these phones are not defective. The hardware key has been purposefully disabled as part of a misplaced strategy to secure a phone that has basically no security built into it.
Therefore it is really easy to gain root access to these phones. However the process requires the use of the adb program that is part of the google android sdk. This program likes to run on a 32-bit linux distribution. Since it will not run on a 64 bit system, here is how I managed to gain root access to my phone:
1. Download the sdk from google.
2. Boot into linux on a 32 bit machine. (I used ubuntu live cd on an old Toshiba laptop with an available linux partition to mount on the hd. Your mileage may vary.)
3. If you are not using ubuntu make sure that your c library is compatible.
4. Install the google android sdk on the hd linux partition, e.g. /home/android.
5. Plug your Samsung vibrant into the usb port on the linux machine.
The following steps are specific to ubuntu. The important thing to remember is that the adb program must run its server as root to gain the access we desire.
6. Start the terminal app: Applications > Accessories > Terminal
7. Mount the partition and change to the sdk directory:
sudo mount /dev/sda2 /media
cd /media/*/home/android/tools
7. Start the adb server:
sudo ./adb start-server
8. Make sure your device is recognized:
./adb devices
If you do not see your device connected you have some troubleshooting to do.
9. Reboot your phone into recovery mode:
./adb reboot recovery
Congratulations! You just gained root access to your hardware locked vibrant.
This message has been posted by my old g4 laptop while tethered through t-mobile 3g using wireless tether on my brand new Samsung vibrant.
M_T_M said:
Hmmmm..good enough to stick!
Click to expand...
Click to collapse
Yeah it's good, but you should move this thread to Samsung Vibrant forum.
This works on any android phone.
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
r2d4 said:
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
Click to expand...
Click to collapse
Would this also work for the new T-mobile G2 4G ?
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
r2d4 said:
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
Click to expand...
Click to collapse
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Installing the root update
tjhart85 said:
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Click to expand...
Click to collapse
If you want to keep root after your next reboot, you need to update your filesystem. The first step is to install the programs busybox and su.
Before you boot into recovery mode, make sure you have the update.zip file downloaded onto your phone's internal memory card. Whatever is on this card will be left alone even upon a factory reset. But the phone's internal memory will be wiped. The update.zip file merely installs those two programs to the internal memory and doesn't wipe anything.
1. Download the root update for your phone. Rename the file update.zip and place it on the root directory of your device's internal flash memory.
2. Once you are in recovery mode, use the volume keys to scroll and the power key to select "reinstall packages". (This works on the vibrant. The g2 may be slightly different.)
3. Your phone will reboot and you will find the Superuser app has been installed. This app lets you grant root access to applications that need it.
Now you can download powerful apps from the market to gain even more control over your phone.
I hope this helps.
Does boot with a live CD of 32 bit ubuntu on my AMD64 work?? or do i need to boot on a computer with a 32bit processor as well?
Running the 32 bit distribution cd on your 64 bit system should be fine.
Need help
Hello I need help to unlock my samsung vibrant
can someone tell me where i can fin the link
thank you
r2d4 said:
If you want to keep root after your next reboot, you need to update your filesystem. The first step is to install the programs busybox and su.
Before you boot into recovery mode, make sure you have the update.zip file downloaded onto your phone's internal memory card. Whatever is on this card will be left alone even upon a factory reset. But the phone's internal memory will be wiped. The update.zip file merely installs those two programs to the internal memory and doesn't wipe anything.
1. Download the root update for your phone. Rename the file update.zip and place it on the root directory of your device's internal flash memory.
2. Once you are in recovery mode, use the volume keys to scroll and the power key to select "reinstall packages". (This works on the vibrant. The g2 may be slightly different.)
3. Your phone will reboot and you will find the Superuser app has been installed. This app lets you grant root access to applications that need it.
Now you can download powerful apps from the market to gain even more control over your phone.
I hope this helps.
Click to expand...
Click to collapse
Does boot with a live CD of 32 bit ubuntu on my AMD64 work?? or do i need to boot on a computer with a 32bit processor as well?
unlocking on root system
I was wondering if it was okay to unlock a Samsung Vibrant when it is already rooted?
the JI6 OTA update fixed this issue.
If you upgraded using Kies or ODIN, you may still be HWL, BUT, there is a fix:
If you can not get into download mode, please try this:
** Please note this is for JI6, if you are running froyo do not do this **
untermensch has a fix for those who are HWL'd that seems VERY effective. I always heard some who updated from JFD to JI6 had the HWL fixed automatically, but that was not the case for everyone. It appears those who updated OTA got the fix, but most who did ODIN or Kies did NOT get the HWL issue fixed.
Please see his excellent thread by clicking here. Hope this helps.
If you are using froyo, I imagine you could revert back to JI6 and flash this to fix the HWL.
HWL but scared to update.zip
Hi all. I am running Ji6 and i am still hardware locked. I just want to root my phone so i can delete some stock bloatware.
Can root my phone without having to "fix" HWL. I am wondering, how Kies successfully upgraded my phone to JI6 with HWL? If I upgrade to froyo (once available) will the upgrade access recovery? WIil the upgrade brick my phone?
I know for Froyo there is z4root which seems to be an easy, safe way to root..
So should i plan on waiting for Froyo??
Just fyi... I just had my vibrant warranty replaced through tmobile, when I registered it with samsung the manufacture date showed november. I had no issues getting to recovery using the keypresses.
The whole warranty swap went alot better than I was expecting, phone looks new not refurbed, it came in like 1 or 2 days from when I called, AND they unlocked it for me even though I was at my unlock limit since it was a warranty replacement, just make sure they specify that in the request.
Sent from my Samsung Galaxy S - powered by Team Whiskey™
Thanks for help, T-mobile's Vibrant is hardware locked.
Of course, you don't need either Linux or 32-bit, it worked just fine from a Windows 64-bit machine (and will from any that has a version of ADK for it). Just Shift+right-click in "android-sdk-windows\platform-tools" and select "Open command window here", enter "adb devices" to launch the daemon and make sure your device is connected properly (it needs to be in "USB debugging mode", which you can select in settings), and then enter "adb reboot recovery". Phone should restart, select "Reinstall Packages" using volume keys and power key to enter.
Bought Samsung Vibrant - SGH T959 - Have questions...
Hi all,
I joined the forums recently to learn about rooting my EVO. With the help of a number of people on the forums I was able to easily root my EVO and install a custom ROM. Still haven't flashed any new Kernels yet but I may do that soon.
Anyway, I bought a Samsung Galaxy S (Vibrant) which of course is T-Mobile phone. I got it from my friend for $50 because I know they sell on eBay for anywhere from $250-$350.
However, I recently upgraded the phone for him before I bought it to 2.2 (Froyo). This seems to be bad for me because now I want to Unlock the phone so that it can be used with any carrier, or a carrier aside from T-Mobile but I've read in the forums here that it's hard to Unlock the device if you've upgraded to Froyo via Kies.
Can anyone help me with Unlocking my device and could someone give me a quick rundown of what the key commands are for this phone too? Such as how to access recovery to flash a ROM. Although I am not going to ROOT this device unless it is required in order to unlock the phone.
Thanks in advance for any help!!!
Oh, and I won't get mad if my post needs to be moved to another thread either so please move it to the right place if it needs to be.
Thanks!
PAinguINx said:
Hi all,
I joined the forums recently to learn about rooting my EVO. With the help of a number of people on the forums I was able to easily root my EVO and install a custom ROM. Still haven't flashed any new Kernels yet but I may do that soon.
Anyway, I bought a Samsung Galaxy S (Vibrant) which of course is T-Mobile phone. I got it from my friend for $50 because I know they sell on eBay for anywhere from $250-$350.
However, I recently upgraded the phone for him before I bought it to 2.2 (Froyo). This seems to be bad for me because now I want to Unlock the phone so that it can be used with any carrier, or a carrier aside from T-Mobile but I've read in the forums here that it's hard to Unlock the device if you've upgraded to Froyo via Kies.
Can anyone help me with Unlocking my device and could someone give me a quick rundown of what the key commands are for this phone too? Such as how to access recovery to flash a ROM. Although I am not going to ROOT this device unless it is required in order to unlock the phone.
Thanks in advance for any help!!!
Oh, and I won't get mad if my post needs to be moved to another thread either so please move it to the right place if it needs to be.
Thanks!
Click to expand...
Click to collapse
Well now, I found this http://forum.xda-developers.com/showthread.php?t=761045 but is it cool to do this while running Froyo? And another question, since I bought this phone from a friend can I still have it replaced/fixed (if needed) if the warranty is still active on it?
Thanks!
Back to original ROM by Odin, T959UVJFD.tar and s1_odin_20100512.pit
in dounload mode (down + power)
First, Thanks to everyone that helped me along the way here... The thanks list is in Post #2
Second, The risk obviously here is your own. This tool is provided AS IS, and I am not providing any warranty or guarantee. So it doesn't cover hail damage to your home, Tornado's taking your dog away, or your phone not working properly after using it... (or anything else that you might try to pin on me )
For all of the processes, linux is required... use your own flavor of linux and use the following to set it up:
Extract the files to somewhere (home folder works best)
Gain a root command prompt (# instead of $) (sudo -s works for most)
Set permissions via "chmod 755 ultimate" (possibly 0755 depending on linux flavor)
Then run the tool using ./ultimate
Code:
/=================================================================\
|*******************************************************************|
|****************** EVO 3D Ultimate Recovery Tool ******************|
|*************************** Version 3.1 ***************************|
|*******************************************************************|
| |
| Please Select an Option |
| |
| 1. Create a backup partition from a bricked device |
| 2. Flash a custom partition to a bricked device |
| 3. Downgrade HBOOT |
| 4. Unbrick |
| 5. VM Radio Fix (CDMA ONLY!) |
| 6. Fix radio partition (Manual Radio Fix only) (CDMA ONLY!) |
| 7. Exit |
| |
| |
|*******************************************************************|
|**************** Copyright (C) 2013, Unknownforce *****************|
|*******************************************************************|
\=================================================================/
Latest version is Here.
(3/14/13) - URTLiveCD 1.0 is available Here -> http://d-h.st/blY
Recent Updates:
3.1
Added additional check for the misc partition detection
3.0
Fixed and re-implemented VM Radio Fix
3.0 ALPHA
Completely Redesigned and Re-Written
New menu interface
Removed the need for hboot/misc image files to be present, they are now embedded in the program and used as necessary
CID issue fixed for GSM devices
Misc detection implemented
GSM/CDMA detection implemented
Fixed a few missing things from the VM Radio Fix (CDMA Only)
Many minor bug fixes
2.5.1
Mistakenly used an older source of URT when coding 2.5, so I re-applied changes from 2.5 to the correct source and re-compiled. (No Difference for GSM, only radio fix was affected.)
2.5
Added support for GSM EVO 3D's! (add -g or --gsm)
No longer beta or RC or alpha or whatever!
Minor cleanup/optimization.
2.3 RC1
Fixed the ghost MEID issues. (This will not fix devices that got it from the first test, please contact me and I'll work with you to fix that)
Fixed some delays and timing in switching between fastboot and adb
Corrected some wording.
2.2 RC4
Second attempt at fixing output errors... Sorry :/
2.2 RC3
Attempt to fix "sh: 1: Syntax error: Bad fd number" error.
Add -f switch to attempt to fix I/O errors on possibly bad sectored emmc's (This will require being in a temp bricked state before using, if this successfully recovers them, I can add this into the process of the radio fix, for now I want to see if it's going to work at all, so it's a manual process for now, to brick device, Be S-OFF, flash custom hboot(anything but stock) and do fastboot oem writesecureflag 3, done) This is ONLY for those having I/O errors when trying to flash radio config. The usage is ./ultimate -f 19 (19 is partition 19/radio_config)
2.2 RC2
Fixed device detection at first step
Logging to log.txt
Fixed device "wait" after rebooting to system, it will now check properly that there is a device to reboot before issuing the command, rather than just rely on time.
2.2 RC1
Initial release to public
Radio Fix
Requirements:
1.13 (or 2.08) Stock Unrooted Rom. (MUST be stock, signed, unrooted, yadda yadda, RUU, or otherwise) - 1.13 Link - Mirror
S-OFF
ENG Hboot - Link
VM Firmware (duh) - Link
2.17 Firmware - Link
Ultimate Recovery Tool (Listed above, also included on the URTLiveCD)
Very basic Linux Experience (Helps, but not necessary if you use the URTLiveCD)
A PC (duh)
Functional device (The device does not have to be on an active plan, but it must currently have a functional radio/signal, Just keep in mind if it doesn't have a plan to it, it will continually try to Hands Free Activate after this process)
Instructions:
1.) First, Backup your current Partition 19, to do this, use the following commands (root required, or do from custom recovery):
Code:
adb shell dd if=/dev/block/mmcblk0p19 of=/sdcard/current19.img
adb pull /sdcard/current19.img
2.) Flash ALL of the following, IN THE ORDER LISTED... There are several Flashes here, After each flash you will need to let it boot all the way to the home screen, every flash, other than hboot, will wipe the data on the device, so it will take some time for each one, and you'll have to go through the normal device setup each time as well. Just get it to the home screen each time.
First - Flash 1.13 Stock
Second - Flash VM Firmware
Third - Flash 2.17 Firmware
Fourth - Flash ENG Hboot
3.) After this you're ready for the tool. Enable USB Debugging on the device. (Applications, Development, USB Debugging) and then boot up to linux and start ultimate or boot to the URTLiveCD, select the option for VM Radio Fix.
Follow the onscreen instructions to the letter, Plug in device when asked, unplug when asked, etc etc. Here is an example output, there are a couple other possibilities, but this is a standard output.
When it starts up, you will see it list out the device type, bootloader version, MEID, and ROM version, make sure these show up correctly.
It will then root the device and pull some more information it needs and then prompt with a message about whether or not you would like to fix rfg_1 (if it finds that it's invalid, it will not ask this and just go right into rebuilding it) if it asks, just tell it not to rebuild, as most of the time it does correctly read that rfg_1 is valid or not.
After it does this, it will reboot the device into bootloader, erase the current RFG_1, flash the fixed RFG_1, erase rfg_5 and flash rcdata.
It then reboots to fastboot once more and writes the secure flag to brick the device. After this it will ask you to unplug the device and remove the battery. Do exactly that, tell it yes to continue, and then plug it in when asked. (without the battery in)
It will reflash the partition and then do the unbrick process.
After it finishes everything properly. You will boot up, it will reboot once while booting up the first time (Normal, security flag toggling causes this) The second time it boots up it will do a Hands Free Activation. Let it go through and do this and the PRL update as well. (if you're on a plan, if not, just press cancel)
Then you will want to re-S-OFF of course so, revolutionary it. This will break activation again. But no matter, let it activate once more.
After that you should be good to go!
Downgrade/Unbrick
DO NOT BRICK YOUR DEVICE IF YOU ARE S-OFF, THE DEVICE WILL NOT GO INTO EMMC MODE AS EXPECTED, AND YOU WILL HAVE A TRUE BRICK IN YOUR HANDS!!!
If you're already S-OFF, but on 1.50, you can do one of two things... I have attached the PG86IMG.zip with the 1.40 bootloader on it, download it copy to sd card and flash via bootloader.
The other option is to simply re-run 1.13 RUU, this will downgrade it as well, but this will also erase all data in the process.
For S-ON... Things you'll need...
Linux and basic linux knowledge (not necessary if you use the URTLiveCD)
This PG86IMG file -> http://d-h.st/3p8 (the bootloader update package)
You'll also need the 1.13 RUU EXE (All the RUU's can be found here -> http://www.filefactory.com/f/4ef0ef536face67a/)
Download the ultimate3.0.zip in the link above or the URTLiveCD
Backup your apps/data if you need to, this process will wipe EVERYTHING
(If you're already bricked, start from Step 2)
First Step
VIDEO OF STEP 1 (video says Step 2, but just start here)
VIDEO OF THE WHOLE PROCESS: (Using Battery Pull method)
BRICK (Yes, I said brick) your device. BUT in a CERTAIN way.
You need to brick your device by corrupting the HBOOT during the HBOOT Update.
(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)
(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)
(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)
(If you are HTC Unlocked, you MUST RELOCK BEFORE starting)
1.) Take your PG86IMG file from above, put it on the root of your SDCard.
2.) With the phone on Battery power alone, Reboot to BootLoader, let it detect the zip and read and get to the point where it wants you to press Vol-Up to update. Do not press Update yet.
3.) Here you can do one of two things, the first being a little more easier than that second... (See Videos for examples)
3A.) The battery pull. You can interrupt the flash by pulling the battery at the right time. Tell the device to update, Pull off the battery cover (careful not to let the battery fall out) and then watch the screen and pull the battery out during or just before the orange bar shows up during the BOOTLOADER Updating.
3B.) The power pull. You can also do this by using the power cord to kill the power. Pull off the battery cover (again careful not to drop the battery out right away) then plug the device into AC power. Now pull the battery out. Tell it to update and pull the power cord at the right time.
The "right time" is different for all devices. The idea here is to completely interrupt the hboot flash so that it's corrupt. The best thing to do is to watch for the bar in the upper right hand corner, it will only show for a second (or even shorter)
If done correctly, you can plug in the device (to power or USB) and see the charge light very dim. It will need to be SOLID dim, NOT blinking dim.
The main indications that it worked correctly:
The device no longer turns on at all, no bootloader, no boot screen, nothing.
The SOLID, not blinking, dim light mentioned above.
The charge light no longer lights up when plugged in with a battery.
The device, when plugged into a windows PC, shows up as QHSUSB_DLOAD. (And MMC Storage Controller for the first 5 seconds)
The device is now bricked and ready for the next part.
Second Step
Video above shows this as well.
The next step is the linux part. Do not plug your phone in to the linux box until you are told to do so.
1.) Boot up to Linux (if you use URTLiveCD, skip to step 6)
2.) Extract your ultimate.zip file to the linux PC, Home folder is the best spot and is the easiest to work with.
3.) Open up Terminal, gain root, (su, or sudo -s)(give it your password)
4.) Run the command chmod 755 ultimate (if it's not in your home folder, add the full path to it)
5.) Type ./ultimate and press Enter.
6.) Select option for Downgrade HBOOT.
You will see the below output:
Code:
IMPORTANT: Do not plug in device until TOLD to do so.
Downgrade selected.
Ready to begin? (y/n):
Type y and press Enter.
Then you will see:
Code:
Plug in your device now.
Waiting for device...
[/CODE]
Now... plug the phone in and leave it plugged in, you should see something similar to the below:
Code:
Device Found!
Locating misc partition...
Misc found at partition 34.
Changing misc version...
Writing image file...
SUCCESS!
Flashing hboot and unbricking...
Writing image file...
SUCCESS!
All tasks Completed Successfully! Put your battery back in and boot up!
Press Enter to return to the main menu.
From there, pull your SD Card out (so it doesn't try to update from the PG86IMG.zip...) throw your battery back in, boot up to bootloader. 1.40.0000
(Some people have said that they needed to "let the device sit" for a few minutes here, mine works immediately every time, YMMV)
To get back to a bootable rom and revolutionary, select FASTBOOT, connect it to the PC and run the 1.13 RUU EXE all the way through, (NOT the zip) then just revolutionary (a few times) and have a beer.
A few side notes:
When you run Revolutionary, you might have to do it a few times... I also didn't get to the point where it asked to flash a recovery... so I did this via fastboot, and simply used TWRP 2.0 .img file.
DISCLAIMER This is NOT a guarantee... because I'm sure it could come back... But in basic terms... I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE, I have given you a method that worked for me, and SHOULD work for you, but if your house burns down, your car gets a flat tire, or your phone stops working... You are responsible for any and all of those things.
The Thanks List!
MOVZX
RussianBear
Fuses
Dexter93
TrevE
Crackanug
closeone
USSENTERNCC1701E
jcase
agrabren
chad.goodman
wwjoshdew
The Fer-Shiz-Nizzle
jlechner
The entire Revolutionary team
FAQ's
Can I do this on Windows?
Currently there is no way to do this on Windows. It's unlikely that there will be a way to do it on windows, Windows USB is too slow and doesn't detect the device the same as Linux does.
Can I do this in (Insert virtual PC software)?
The only one I've heard that works is VMWare, however You're again relying on Windows to pass the device to a virtual machine, which isn't ideal. I know for a fact that VirtualBox does not work, and Cygwin also does not work.
Common Errors
I can't get my phone to brick, I've tried a million times!
Patience is a virtue. This step is the hardest part of all, HTC Designed their phone to be brick proof for a reason. I believe the trick here is to let the device sit on the update screen for a minute or two, then do the update and count out 5 seconds. Also there's the update bar that appears in the upper right hand corner, much like the bar that is there when it's checking the zip file before the update prompt. The INSTANT you see that, pull the power. This is typically 5-6 seconds after it says updating, but only after it's been sitting for a bit... I believe the trick is to let it sit for a bit before pressing Volume up to update.
My PG86IMG.zip is not detected or the phone checks it and it doesn't prompt me to update it
There are several possibilities:
The phone is HTC Unlocked - You must re-lock.
The phone is S-OFF - Don't even try to brick it because you'll permanently brick it.
The phone is Re-locked, but still has a custom rom/recovery on it. - This will show a security warning and not allow the PG86IMG.zip to be flashed. - You must put the phone in FASTBOOT USB and run the RUU exe that matches your software version.
The File is not named correctly, it's PG86IMG.zip (Make sure it's not PG86IMG.zip.zip)
The PG86IMG.zip is either corrupt, not signed properly, or modified in some way. - Download another one.
I press Volume up to Update, and my phone shuts off
First make sure you're using a standard HTC A/C Adapter and cable. These are designed to charge at 1000 mA, other manufacturer's chargers typically only hit 900 mA. The phone needs it all to stay on and update properly without the battery in.
Second, make sure you're not using a higher end SD Card. This will draw too much power and not let the phone update when it comes to that time because the power drain to have the screen on, the sd card powered and the update running is more than what the A/C adapter can output. - My 16GB Class 10, shuts the phone off, my Class 4, 2 GB, does not. YMMV.
Third, if you're stuck with the high end SD card, or think it could be the cause, simply pull it after you pull the battery and BEFORE you press volume Up to update. The phone will still update. However, I don't know if this affects the speed of the update at all... so just watch it the first time and time it, then time your pull accordingly.
I'm getting Permission Denied when trying to run the linux commands
You don't have root, either type su or sudo -s, your prompt should have a # at the end and not a $.
Or, you didn't set the chmod correctly on the ultimate file. This is again chmod 755 ultimate (or /path/to/ultimate)
I get Misc image is missing!!! or HBOOT image is missing!!! or Recovery image is missing!!!
The hboot.img and misc.img and recovery.img files must be in the same location as the ultimate file, they are hard coded into the ultimate tool to be in the same location, their names are also hard coded, so don't rename them.
I'm getting Error 16 after running the radio fix.
This can happen, there are two things, most likely it goes away after attempting to place a few calls. If it doesn't, just remain on the line, and they can fix the problem for you.
Ultimate Recovery Tool[Box]
Here is the latest Ultimate Recovery Tool[Box] (Live CD/USB)
LATEST VERSION (of the live environment) - 2.3 RC1
Download
Windows Users:
This a bootable ISO for users who don't have a Linux distro installed, or do, and want a little more simplified interface.
This will not do anything to your currently installed OS.
_____
If you wish to use it on a USB flash drive, you must use Core2USB to make it bootable.
You can get that here.
A couple of modified guides from the HBOOT Downgrade Toolkit thread.
Burning the Ultimate Recovery Tool[Box] to a CD
Windows Vista/7
1. Download the latest version of the Ultimate Recovery Tool[Box] from above.
2. Insert your CD-R
3. Navigate to the location of the Ultimate Recovery Tool[Box] on your hard drive.
4. Right-click on the .iso file. Hover over 'Open with' and select 'Windows Disc Image Burner'
5. Select your CD burner from the drop-down menu
6. (recommended) Tick 'Verify disc after burning'
7. Click Burn
Other Windows Method
PoorCollegeGuy's guide to Burning an ISO to a CD
Mac OS X - Thanks MikeC84!
Open disk utility, drag the ISO to disk utility. Make sure "make disk bootable" is checked, Click burn....
Check out lpjzfan2005's Mac OS X tutorial for running the CD!
Note: Mac support is limited. It's been confirmed the [HBOOT Downgrade Toolkit] CD will run on a Mac though. [No tests have been done with the Ultimate Recovery Tool[Box] yet]
Click to expand...
Click to collapse
How to run the Ultimate Recovery Tool[Box] from a Flash Drive
I've realized that there is enough demand for being able to run the Ultimate Recovery Tool[Box] from something other than a CD-ROM drive.
Thanks to Disturb3d1/wwjoshdew and Mpgrimm2 for the suggestion!
What you'll need:
A 256MB USB Flash Drive (Almost any flash drive you have laying around)
Ultimate Recovery Tool[Box]
Core2USB
Step 1. Simply download Core2USB from here.
Step 2. Choose your USB Flash Drive and format it (This will delete all files from it, so back them up).
Step 3. Run the Core2USB software. It won't install anything on your computer.
Step 4. Browse to the Ultimate Recovery Tool[Box] ISO.
Step 5. Double-click on the letter of your USB Flash Drive. Make sure that this is the correct drive.
Step 6. Click Install
Step 7. Reboot your computer with the USB Flash Drive inserted.
Don't pull the flash drive out while you are booted into the Ultimate Recovery Tool[Box] Environment!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Obligatory Disclaimer - This software is distributed in the hope that it will be useful, but without any warranty. You take full responsibility for the usage of the software. I am not liable for anything that goes wrong with this Live CD, including, but not limited to, "bricked" (otherwise unusable) phones, or anything else that happens to your phone(s), computer(s), or anything else. You take full responsibility for your use of these tools.
Yes we are one step closer to the end! I am excited cant wait until the link to the CD is posted!
Thank you Unknownforce and closeone and the rest for your hard work you put into this it is very much appreciated.
If your phone's S/N starts with SH 18 then you might want to hold off until Unknownforce fixes the issue with the CD not recognizing the phones.
Unknownforce + closeone = amazing!
Thank you guys for everything!
I really appreciate closeone and Unknownforce for your work on this!! I am excited to try it out and get rid of the VM stuff.
Sent from my PG86100 using xda premium
MINE! Thanks Unknown!
You're not unknown now! lol
wwjoshdew said:
MINE! Thanks Unknown!
You're not unknown now! lol
Click to expand...
Click to collapse
His new name should be aFORCEtoBeReckonedWith
Minne. Front.. you da man. Thanks for letting me be a tester!
Sent from my PG86100 using xda app-developers app
Just a minute, and hopefully a CD will be in your direction. Just waiting for a quick nod of approval from Unknownforce.
Edit: It's up. Check post #3!
~co~
Splooooooge.
Sent from my EVO LTE.
Your not unknownforce you are THE FORCE we use you for our Android Jedi skills
Sent from my EVO3D using Tapatalk 2
Any mirrors of this 1.13 Stock?
Or is http://shipped-roms.com/index.php?category=android&model=Shooter the same 1.13 Stock?
It worked like a charm. I have the correct PRI and all. I just did revolutionary and am back in business!!!
I'm doing Hands Free Activation at the moment and it appears to have worked!
Success
EDIT: Re-did it. Took out my SD Card and kept it out when prompted to unplug device for bricking process. No buffer error this time.
so since i have a windows 7 comp...there is no way i can get my phone fixed???
jayseersts said:
so since i have a windows 7 comp...there is no way i can get my phone fixed???
Click to expand...
Click to collapse
it's a bootable cd, the os runs when you boot from it
Sent from my EVO LTE.
One question if i do not do the downgrade part of this...my phone would just be a stock phone without the vm virus we wanted to get fixed? only reason i ask is because i do not use my 3d anymore because i have the evo 4g lte and just want to sell the 3d. i just want all the vm **** out of it so i can get rid of my phone...
jayseersts said:
One question if i do not do the downgrade part of this...my phone would just be a stock phone without the vm virus we wanted to get fixed? only reason i ask is because i do not use my 3d anymore because i have the evo 4g lte and just want to sell the 3d. i just want all the vm **** out of it so i can get rid of my phone...
Click to expand...
Click to collapse
Unless you do the downgrade, there will still be vm stuff in there. This is the only way to delete it. It's easy man, it was made that way on purpose.
Sent from my EVO LTE.
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Potentional Tutorial
philipkroberts said:
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Click to expand...
Click to collapse
philipkroberts said:
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Click to expand...
Click to collapse
Also looks like im getting the Star N9589 just due to the more support available.
Anyhow until then, failing any answers from here, another chinese forum a spanish one and Yahoo answers I am going to go with the following method, If it dies, It dies this was my own fault for not doing enough research and at least it lets others know. I would send it back to DX But cba with postage fees and the hassle;
THIS IS DONE AT YOUR OWN RISK! -
APOLLO ONE - MTK 6589 K6589
Please note all tools and zip files mentioned I cant link to yet should you feel you want them please post in this thread and I will PM you, Gotta get my post count up first!
Guide by philipkroberts Twitter @philipkroberts
Revision 1 - People to be added to credits for leehed source, currently untested, concept only
Before anything try and boot into any form of recovery mode and backup if possible!
DISABLE UAC in WINDOWS 7
RIGHT CLICK RUN AS ADMIN ON ALL FILES
ALLOW NON TRUSTED DRIVER INSTALLATION (Google this if unsure)
On the phone install anububu on pc phone. - See what model it detects as and note it down.
Run MTK DROID TOOLS and connect phone see if drivers After a few seconds, the box should turn blue, and it should say "Apollo ONE or Other Name " besides it. The drivers are working.
If not try the other drivers in the drivers folder using device manager, there are many tutorials for this I cba typing one im so tired! and make sure you have the only trusted drivers thing turned off, if you constantly get unknown driver then your out of look and wil have to try and source some yourself.
Win7 (This method has not been tested by myself. Confirmation required.)
HOW TO MANUALLY INSTALL ANY DRIVERS IF NEEDED
a - Downloading This tool Called EASYBCD
b - Use it to restart your computer in advanced boot mode. (PRESSING F8 WHILST BOOTING UNTIL YOU GET THE OPTION FOR Disable signed driver enforcement)-Must be done everytime you wanna root a phone with this method.
c - Follow instructions and disable SDE.
d Manually install drivers, if above did not work (Yellow sign issue)
e Navigate to control panel - > Hardware and Sound - > Device Manager
f You should see a driver notice with a yellow warning sign next to it.
g Right click on it and choose "Update driver..".
h- Manually assign drivers, usually the choice furthest down.
i- In the window which should have appeared, navigate to the preload/Mt6590 folder and press OK.
j- If SDE is turned off, you should see a red warning window. This is normal, just accept the message prompted.
k- The drivers should now be successfully installed.
l - Once this is done open C:\Users\Hate\Desktop\Chinese Droid Rooting\MTKROOT TOOLS\Root_with_Restore_by_Bin4ry_v28\runme.bat Hope it ****ing works if so your rooted, If not try this next few steps, AGAIN at your own risk, no need to format just continue from here.
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
0 - Use PC to copy UPDATE-SuperSU-v.1.25.zip to the root of SD CARD, do not unpack just leave whole zip there.
1 - Turn off your phone, remove your battery. (Do not connect your phone to the computer yet!)
2 - Navigate to the "SP Flash Tool" folder, and run the tool.
3 - On the right side of the tool, there should be a button, iconed with a folder, named "Scatter-Loading". Click this.
4 - Navigate to the "Yulypis Recovery" folder, and double-click on the "Mt6589_Android_scatter-emmc.txt".
5 - You should be back at the SP Flash Tool start-screen, and there should have appeared a list of text and hex-codes.
6 - The "Recovery" line, should be ticked off, and preloader should be red.
7 - Now, click on the button named "Download", with a blue arrow on it. Press "YES" on the NOT ALL images has been correctly loaded warning.
8 - Connect your phone to a USB 2.0, with removed battery. The program should now work, and if drivers is set up correctly, the 0% will turn 100% and a green circle will appear in the middle of the screen. If your phone disconnects before the flashing tool is able to recognize your device, try putting the battery back into the phone before running SP Flash tool. Additionally, if this doesn't work, try using different drivers in the drivers folder
9 - Disconnect your K6589 from the computer when you see the green circle, insert the battery and boot the phone. Wait for it to get to the start screen.
11 - Installing SuperSU through Yulypis recovery
12 - Run "MtkDroidTools.exe" from the folder.
13 - Connect your device, and after a few seconds, information about your device should appear.
14 - Click on reboot, on the mtkDroidTools start-screen, and choose "..recovery".
15 - If recovery has been properly flashed, your device will now enter Yulypis recovery. Blue, with english text.
16 - Controllers: "Power = Enter, Initialize", "Volume down = Scrolling down". (Don't remember if volume up was bugged or not)
17 - Enter "Install zip from SDcard" - > Navigate to the earlier copied "UPDATE-SuperSU-v.1.25.zip and initialize it by pressing the power button.
18 - Follow the on-screen instructions, and it should be prompted to install after 1-2 more screens.
19 - Reboot the device by clicking on "+++++back+++++" and "Reboot now / Reboot Device".
Either way I am going to smash this in a week or so when the phone arrives from DX and will keep people update.
Peace
Please I want to buy this phone. Can you answer me a few doubts I have?
- How is the viewing angle? Cause i purchased a tablet from china and the angle is very bad.
- Has proximity sensor?
Are you ok with the phone?
thank you.
cabrote said:
Please I want to buy this phone. Can you answer me a few doubts I have?
- How is the viewing angle? Cause i purchased a tablet from china and the angle is very bad.
- Has proximity sensor?
Are you ok with the phone?
thank you.
Click to expand...
Click to collapse
I'm still awaiting the phone, hence why that guide is at your own risk.
However from what I have been told and gather that should root the phone no problems.
As for custom roms, I wouldn't even bother trying!
Once the phone gets here I will test my tutorial and re-write it into a more easy on the eyes fashion.
Thanks
http://www.fastcardtech.com/APOLLO-ONE-K6589?u=37825
They sell the phone, for an extra $3 they root before sending.
It cant be that hard, I'd love to know someone in that factory!
I'm looking for a link to download the full stock firmware for this device.
Anyone, please?
...or at least a firmware dump from a non-modified working phone.
One could use MTK Droid Tools and SPFlash to perform this task easily.
PM me for assistance if you need it.
Thank you.
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
Seeing how this phone just recently came out in January I haven't really found too much info out there so maybe this can be a start.
I've tried to unlock the bootloader but couldn't get fastboot to work and I tried kingroot and that failed. iIt has 12 requests for this phone so far.
So I'm pretty stuck right now on what to do I'm kinda a noob so maybe y'all can help me out a lil on what to do if anymore info is needed please let me know.
Thanks in advance
Greetings, I am noob too, but I am learning. I cannot answer your question about unlocking the bootloader, however, someone gave me an Alcatel Verso that had frp lock screen. Got limited access and installed an app called quickshortcutmaker. This allows running all the activities. There is a system app on mine called engineer mode. This reveals the actual file system as well as other info.
It appears there is not a reboot bootloader mode, it does have reboot recovery, but also I do not think it has fastmode. There is another mode called download mode, but I have not successfully used this for anything. Also, connecting usb abd in recovery mode yields device unauthorized.
If you are interested, I'll explain how I got frp partially bypassed. Added emergency contact, added an email, a prompt came up asking me which service to use, there were like four options like google, etc. I chose one I had not heard of that had the word executive, because it sounded official. When I chose it, another prompt came up saying that in order to use this service I had to set up a lock screen, make sure func is enabled. When I then turned the screen off and back on, I had a google search option from the lock screen. Pressed it and said "open settings", enabled install of unknown sources, used google search and said "open chrome". Used chrome to download quickshortcutmaker. Used google search and said "open file manager". Used file manager to install quickshortcutmaker. At this point I could have just used the phone from there, however... I added quickshortcutmaker to the func lock screen list by using google search to open settings. Then from the lock screen, I could launch quickshortcutmaker (or use google search). I then used quickshortcutmaker to run 'joy launcher' and voila, in. However, only the back button worked, and if I tried to log into google, it would bring up the frp lock screen. So, using the quickshortcutmaker, I ran every activity on the phone, and using the engineermode system app (I am pretty sure it was that one) I toggled an option called 'demo mode'. Upon exiting this system app and pressing the square button next to the home and back button, I saw an option to accept user agreement, or something like that. I scrolled down and checked the box, and voila, frp lock totally gone, and now I can log into google.
Now I am trying to root, but first I must unlock the bootloader.
diorthotis said:
Greetings, I am noob too, but I am learning. I cannot answer your question about unlocking the bootloader, however, someone gave me an Alcatel Verso that had frp lock screen. Got limited access and installed an app called quickshortcutmaker. This allows running all the activities. There is a system app on mine called engineer mode. This reveals the actual file system as well as other info.
It appears there is not a reboot bootloader mode, it does have reboot recovery, but also I do not think it has fastmode. There is another mode called download mode, but I have not successfully used this for anything. Also, connecting usb abd in recovery mode yields device unauthorized.
If you are interested, I'll explain how I got frp partially bypassed. Added emergency contact, added an email, a prompt came up asking me which service to use, there were like four options like google, etc. I chose one I had not heard of that had the word executive, because it sounded official. When I chose it, another prompt came up saying that in order to use this service I had to set up a lock screen, make sure func is enabled. When I then turned the screen off and back on, I had a google search option from the lock screen. Pressed it and said "open settings", enabled install of unknown sources, used google search and said "open chrome". Used chrome to download quickshortcutmaker. Used google search and said "open file manager". Used file manager to install quickshortcutmaker. At this point I could have just used the phone from there, however... I added quickshortcutmaker to the func lock screen list by using google search to open settings. Then from the lock screen, I could launch quickshortcutmaker (or use google search). I then used quickshortcutmaker to run 'joy launcher' and voila, in. However, only the back button worked, and if I tried to log into google, it would bring up the frp lock screen. So, using the quickshortcutmaker, I ran every activity on the phone, and using the engineermode system app (I am pretty sure it was that one) I toggled an option called 'demo mode'. Upon exiting this system app and pressing the square button next to the home and back button, I saw an option to accept user agreement, or something like that. I scrolled down and checked the box, and voila, frp lock totally gone, and now I can log into google.
Now I am trying to root, but first I must unlock the bootloader.
Click to expand...
Click to collapse
You can use this guide for your phone:
https://forum.xda-developers.com/canvas-juice/how-to/guide-unlocking-bootloader-rooting-t3705781
HIT THANKS IF FOUND USEFUL
No, it does not work. I am having several issues. First, I cannot get adb windows drivers to recognize this device, I have installed every qualcomm driver I could find, also tried the universal adb drivers and even the drivers that come with the phone. Nothing works.
However, I have a rooted tablet with an otc cable that does connect via adb. However, adb reboot bootloader simply reboots the phone. There is a download mode, but I do not have fastboot installed on the tablet, so I cannot check if download mode = fastboot.
I am able to adb push files to /data/local/tmp and running adb shell chmod 755, I have succesfully unstalled busybox and can execute commands such as vi. The user is still not root, but I feel I am close.
I tried to download the emmc internal memory using backup qualcomm tool, but I seem to not have the correct drivers for my phone. My plan was to edit ro.debuggable to 1 and reflash, so I can adb root and remount as rw.
Best I can do so far
So far cracking it is still undone...but I can offer up some advice...download 3c, advanced tools and dev tools. A notepad++ would help too so you can re-create rom commands to make your own. Use advanced tools to look for vendor. Once there you should see a few files that make you question Google's business practices. Go into them to make alterations using dev toolds. The rest of the files can be re-made from scratch using notepad and 3c's rom manager.
This phone is complete garbage, I ended up giving it away because the touch screen would go to random spots on the phone randomly. It appears to be a cheap phone I do not like. Got an LG that as far superior.
I may have a Root method for the 5044R and the 5044C, I need someone with the 5044R and 5044C to get in contact with me. Best way to do that is Telegram. Here is the Link: https://t.me/Android_General_Chat
I'm currently Testing Root on the 5044C
---------- Post added at 12:56 AM ---------- Previous post was at 12:42 AM ----------
Alcatel 5044C and Alcatel 5044R PWND and Rooted. Doing 5044C TWRP Recovery now.
UPDATE: TWRP Ported and WORKING. Now somebody make some custom Roms.
I'll have a Custom Stock Rom out for this soonishly if anyone is interested
Alcatel Verso Root Solution
I have an Alcatel Verso (Yes, the Qualcomm 5044c) and the solution from PizzaG works well. The bootloader is unlocked and the phone is rooted. It works better now than when it was new. Thank you, PizzaG!
-
Tip: carefully follow the instructions, try different USB ports and unplug any other USB cables / devices. You will need MS Windows, the .mbn file and Sugar_QCT (from PizzaG).
Where is the root method?
I am just curious of the method used, I do not have this phone.
mrhealthpatriot said:
I have an Alcatel Verso (Yes, the Qualcomm 5044c) and yes, the solution from PizzaG actually works. The phone boots properly, has Magisk, etc. Thank you, PizzaG!
-
Tip: carefully follow the instructions, try different USB ports, unplug any other USB drives and be persistent.
You will need MS Windows and Sugar_QCT (from PizzaG). The phone is rooted, working and more responsive.
Click to expand...
Click to collapse
Of course it works, otherwise I wouldn't have posted it along with modified boot and TWRP. Unsure if I released the modified stock rom or not?
@PizzaG Could you describe the method briefly, or post a link to the method, I am not seeing it.
diorthotis said:
@PizzaG Could you describe the method briefly, or post a link to the method, I am not seeing it.
Click to expand...
Click to collapse
I use the Alcatel Internal flashing software. It grabs the firmware files from their servers. I then swap their boot image for my modified image and then use the software to flash the device. It's then rooted and you can install TWRP or swap recovery files in the Flasher software and it will flash for you. Device must be bootloader unlocked from the factory but they disabled fastboot.
Thank you, do you have a link for instructions on how you modified the boot files, and which ones?
diorthotis said:
Thank you, do you have a link for instructions on how you modified the boot files, and which ones?
Click to expand...
Click to collapse
Once the program downloads the firmware, I was able to get some good info from the flashing logs that told me what every file is. So I just grabbed the B file which is boot and ran it through magisk manager to patch it. Pretty easy peasy. TWRP I just ported from another msm8909 device. The TWRP for 5044C also woks for 5044R models as well as the whole rooting procedure. I would build some more recoveries for it from source but I don't have the device so I can't be bothered with that unless someone wants to donate towards the cause.
Verso Unlocking
This is basically how I unlocked the phone. First, I went into developer options and allowed "OEM Unlocking* and "USB Debugging." Then I opened Windows and downloaded the Actatel drivers. I also installed SugarQCT and the *.mbn file from PizzaG's website. Once Windows and ABD recognize the phone., I launch SugarQCT. I used the version from PizzaG, but said no to any update requests. (It crashed after it updated itself.). In SugarQCT, I started the phone firmware flash process and pasted the *. mbn file into the "5044c" folder that the program creates during flashing. It is important to overwrite the existing *.mbn while SugarQCT is downloading the firmware files so that the newly pasted version is flashed to the phone. Once it is done, SugarQCT deletes the entire temporary folder. When the "flashing completed" or "success" message pops up, just reboot the phone and set it up as usual. I used Flashify to flash Magisk to the recovery since PizzaG's ".mbn installs SuperSu.
mrhealthpatriot said:
This is basically how I unlocked the phone. First, I went into developer options and allowed "OEM Unlocking* and "USB Debugging." Then I opened Windows and downloaded the Actatel drivers. I also installed SugarQCT and the *.mbn file from PizzaG's website. Once Windows and ABD recognize the phone., I launch SugarQCT. I used the version from PizzaG, but said no to any update requests. (It crashed after it updated itself.). In SugarQCT, I started the phone firmware flash process and pasted the *. mbn file into the "5044c" folder that the program creates during flashing. It is important to overwrite the existing *.mbn while SugarQCT is downloading the firmware files so that the newly pasted version is flashed to the phone. Once it is done, SugarQCT deletes the entire temporary folder. When the "flashing completed" or "success" message pops up, just reboot the phone and set it up as usual. I used Flashify to flash Magisk to the recovery since PizzaG's ".mbn installs SuperSu.
Click to expand...
Click to collapse
oh, did I really do it with SuperSU? My bad on that. Seems weird I'd use that. But yep, nice job of explaining the procedure. You should be nice and post your magisk patched version of boot.img or pass it to me to further modify it and i'll post it on here. I'd like to make it selinux permissive and remove the line of code that reflashes stock recovery on reboot. If you used my original SuperSu patched image and then repatched it with Magisk, then it wouldn't need to be repatched for selinux and such.
Flashing Files
Actually, I didn't patch the boot image or modify any files. I used the 5044C_TWRP.img and BVT4H1H0CL10.mbn that you posted. I have an Alcatel rom from Needrom, but I didn't use that either. I flashed Magjsk.zip with flashify, but I could have flashed it via adb. SuperSu was already installed..