Related
I am an inexperienced user and have a few simple questions. I have a touch dual originally from orange uk. I've done the cid unlock thing and found that fairly easy.
I want to upgrade the system to 6.1 or 6.5. Can i copy the system on the phone already so I can revert back to it if the new version ***** up?
Is it better to put on a more worked out 6.1 rom than the new 6.5 which may have a few glitches since I'm not a great tinkerer or will the 6.5 provide a stable load and forget solution.
Finally which is the best rom out there for stability and features and user friendly.
to revert back, u'll need to fully backup your old wm6 before flashing the new ROM. if u don't like the new ROM, flash back your old ROM and restore from the backup and u're back to square one.
if u want stable, forget about wm6.5. stick to wm6.1.
I'm happy enough backing up my data side of thinggs. How do I back up my operating system or do I have to download a wm 6 operating system in the same way I down load the 6.1 system?
If you search around the forum there is a copy of the OrangeUK ROM on here (singed, with radio) I have it sat on my PC from a while ago.
Infact, I found it:
NetrunnerAT said:
Original Full OEM Roms!
RUU_Nike_HTC_PTG_13141009_Radio_Nike_1581627_signed_Ship
RUU_Nike_HTC_RUS_13141109_Radio_Nike_1581627_signed_Ship
RUU_Nike_HTCASIA_AUS_13171012_Radio_Nike_1582123_signed_Ship
RUU_Nike_HTCASIA_WWE_13170709_Radio_Nike_1581627_signed_Ship
RUU_Nike_ORANGE_UK_1316110_Radio_Nike_1581627_signed_Ship
RUU_Nike_SingTel_WWE_13187114_Radio_Nike_1581627_signed_Ship
THX to all guys, they have shared those Roms with me!
Click to expand...
Click to collapse
Taken from web page: http://forum.xda-developers.com/showthread.php?t=373452&page=1
Post 4
Wez.
that s excellent thank you very much. Can anyone recommend a good 6.1 with all the bells and whistles?
I personally use Salvy.C.83's ROM. Not found any real problems with it and the battery drain is much less than any other Manila 2D ROM out there.
Find it here
Happy flashing
Wez
Thank you for your help so far.
To do it to the hard SPL 1.22 do I need to go through the following routine
1. download the attached files
2. REMOVE SIM and SD CARDS !!
3. connect usb cable
4. copy sspl-1.16-nike.exe to your device and run it (usb cable must be connected!)
5. after a few seconds "USB" appears on the display
6. unplug and replug the usb cable
(OPTIONAL, better to skip it! step 7. if you only want to test the sspl try flashing the attached splash screen by running ROMUpdateUtility.exe from flash-splash-niki)
8. you can now flash the hardspl-1.15mfg-nike.nbh by running ROMUpdateUtility.exe from flash-uspl-niki
9. after installing the hardspl you can flash any rom
Just subsidising the new hard SPL 1.22 at line 8. Or can I miss out all the sspl part and just go straight in at line 8?
Sorry if I'm coming across as bit of an idiot.
Right routine:
1. download the attached files
2. REMOVE SIM and SD CARDS !!
3. connect usb cable
4. copy sspl-1.16-nike.exe to your device and run it (usb cable must be connected!)
5. after a few seconds "USB" appears on the display
6. unplug and replug the usb cable
(OPTIONAL, better to skip it! step 7. if you only want to test the sspl try flashing the attached splash screen by running ROMUpdateUtility.exe from flash-splash-niki)
8. you can now flash the hardspl-1.22-nike.nbh by running Nike CustomRUU.exe
9. after installing the hardspl you can flash any rom
10. Update your radio at last 1.65.xx (last official here)
Hey Xda-developers. Just quickly, I found this Forum from a few links on other websites (gizmodo, engadget) and some youtube videos of your awesome custom ROMs.
I for my HTC Hero in March, and I should be upgrading around christmas 2011. That's a while, and Android grows fast..much much faster than HTC update my device, so I'm thinking a custom ROM is what I really want.
I've done my research, but honestly I'm pretty much a noob here. I know I need to root the phone, but I've been unable to find any specific instructions for 3 UK, and as far as I can tell all the different carriers use different instructions (a different ROM to downgrade to?), so I don't want to use the wrong ones.
-
Phone Spec
Okay, this is a standard HTC Hero on a 24 month contract carried by 3 UK.
There has been no rooting, no major changes. I have done no more than officially supported. A complete from scratch root would be required.
Currently running 1.5.
UK, 3 Mobile, GSM.
No hardware replacements and no known issues with the phone.
-
I think that's about all, is somebody here able to point me to the right place for a 3 mobile root?
Thanks in Advance,
Callum.
I'm also on 3uk and i rooted my phone using the following guide:
http://androidforums.com/all-things-root-hero/54802-how-root-install-custom-rom-backup-more.html
Hope this helps.
Thankyou very much for your help! I'll be giving that guide a go later.
No probably m8, SenseHERO is a good custom ROM.
Any trouble just post up and ill try and help you out.
Hmm, if I could ask you to take a look at a post, that'd be really helpful. No worries if you don't have a clue though.
Hero, G2 Touch Android Development >
[Guide] Complete Newbie Guide to Install a Custom Rom & Newbie FaQ [Updated 02/05] >
Page 33, Post 1.
Sorry that link is so bad, but they won't let me post a proper one.
That thread was alternative 2 for the 3uk guide you gave me (goldcard section). I'm not sure whether you'll be able to help me, but if you could take a look that'd be massively helpful.
Cheers,
Callum.
I posted a reply to more or less the same problem earlier.
http://forum.xda-developers.com/showpost.php?p=6701261&postcount=268
Let me know how you get on.
Thankyou very much for your reply, but I have already done all of this. I've successfully performed a goldcard on my SD and I'm really close to getting a working custom ROM, but it's dying somewhere there. I have already installed the x64 drivers though.
HTC Sync works perfectly, picking up the phone and synchronizing on demand.
Thanks,
Callum.
What guide are you using, i used this was one to create a goldcard and downgrade:
http://forum.xda-developers.com/showpost.php?p=5855697&postcount=1
The only problem i had was syncing after installing the latest version. I fixed it by downloading a driver manager and updated the drivers for it.
I take it it lets you mount the SD card on your computer?
One thing that might be worth a try is to download the ROM again, it might be corrupt, a shot in the dark but worth a go.
That's the guide I ended up at, after following a link within the guide you provided above.
It does indeed allow me to mount the SD card, everything syncs perfectly. I'll give re-downloading the ROM a go, though. There was two available, so I'll try the other download.
Hmm, I've tried everything I can think of, and nothing is working on this Windows 7 machine. My brother's XP machine is broken, and my dad's away with the XP notebook.
Is there any way that anybody knows of to run XP as a virtual machine temporarily?
Here's a link for a virtual box:
http://www.virtualbox.org/wiki/VirtualBox
I dont know how to run it though.
Someone had a similar problem on win7 yesterday and sorted it by getting a new gold card. Might be worth a try?
Aha, I re-downloaded goldcard, and switched the driver to My HTC once with it normally plugged in, then with bootloader open. And it downgraded!
I've got the Scenehero on the SD card now, I'm just unable to launch the custom recovery screen. It will start normally by hitting power, but while the home button is also held it just loops the first hero screen. Is there any way past that, because I need to perform a wipe and flash scenehero.
Thanks so much for your help so far, you've been amazing!
If your all set up properley you should be able to connect your phone via usb to the PC,
then open a command window and type>"adb shell devices"
your phone should show in the window something like HTLK12345
now type> "adb shell reboot recovery"
this should boot your phone into recovery mode.
Hope this helps.
Thankyou very much for your help, I solved the problem by re-installing my recovery. Not sure what went wrong but it worked after that. All looks good now!
good stuff m8, glad your sorted.
what rom are you running?
I'm currently using the latest version of Sensehero. Really pleased with it so far.
I'm on branch 3, waiting for branch 5, should be here soon hopefully.
If you have'nt already m8 check out the site:
http://www.htcdevscene.co.uk/
Some top lads over there having a good time!!.
Firstly, Hello my names Jazmin
Thank you for taking the time to look at this!
Also - yes, I'm am a 'noob', and proud - got to start somewhere
So I decided it was about time to flash? my first rom. My friend Brandon has been installing ROMs and performing maintenance on my HTC HD2 since I bought it from him - which must've been annoying for him, so...
He gave me some XDA thread from which I could follow/learn from.
The ROM we decided to use came from this thread:
http://forum.xda-developers.com/showthread.php?t=1209474
I download the ROM and then went to downloaded the CLK NAND below the ROM download link and the file was corrupt/unavailable.
So I found this youtube tutorial:
http://www.youtube.com/watch?v=_KoOWyHZMNo&feature=player_embedded
I download the CLK Install.zip from the link he featured in he's description and used that. I incorporated the youtube found CLK into the tutorial featured on the ROM thread that I decided to use (switched out the steps for the CLK that was on the thread and incorporated the steps from the youtube video).
However, I got to the last part of the xda thread tutorial - step 4.
And didn't quite understand some of the step or didn't perform them properly, I know I know - I'm a spoon, but I'm still learning!
So it won't allow me to mount anything from the phone, cause the phone isn't being recognised by the computer anymore. I can't put the file on the SD card - I'm not even 100% sure on what file to put on the SD card to be honest. So I can't install the ROM on my phone
Now all I have is a black screen with this on it:
Codesmith's LK (CLK) v1.4.0.1
[2300] ptn 0 name='misc' start=00000219 len=00000008 end=00000221
[2300] ptn 1 name='recovery' start=00000221 len=00000028 end=00000249
[2310] ptn 2 name='boot' start=00000249 len=00000028 end=00000271
[2310] ptn 3 name='system' start=00000271 len=000004b0 end=00000721
[2310] ptn 4 name='cache' start=00000721 len=00000028 end=00000749
[2310] ptn 5 name='userdata' start=00000749 len=000007f8 end=00000f41
[2310] USB init ept @ 0x28023000
[2350] fastboot_init()
[2350] udc_start()
[2350] -- suspend --
[2530] -- reset --
[2530] --portchange --
[2690] -- reset --
[2690] -- portchange --
[3180] fastboot: processing commands
Obviously a hard reset isn't enough to get rid of this, however to be safe i tried it anyway.
So I need to know how to get rid of this screen, so that my phone will atleast boot to something other than the screen - so that way I can plug the phone in via USB cable and the computer can then recognise it so I can perform the whole tutorial over again. Any help will be muchly appreciated! Please please please!
Also, please no negative criticism - yes I am learning, yes I may make mistakes - congratulations! We've established that I'm human!
And, whilst I'm asking etc. In the ROM thread, step 4. What is and update-signed.zip? How do I recognise it if I don't know what it is? I understand its a file, but how will i know what one it is. Because when I downloaded the ROM file, I don't see anything in there related to update-signed.zip. So please, any help would be muchly appreciated.
Sorry for making you read this huge essay, your amazing if you can make it the whole way through! Thankssssss so much!
One Love.
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.