Related
All right, so you wanna Full Unlock your Nokia L710 device but you faced a website on the internet saying it was impossible, which turned you down. There's a little thing you should now: most site are whether wrong or outdated, so it is very possible to full unlock a Nokia L710 (and theoretically a Nokia L800 too). But instead if you just want to developer unlock your device here's a thread that might help you with steps to officially dev unlock your phone free of charge: http://forum.xda-developers.com/showthread.php?t=1569119
It is very easy to full unlock your phone, but you must know that some knowledge and some nerves are required... Here it goes my experience on unlocking my Nokia Lumia 710 device. Note it has not been tested on Nokia Lumia 800 and that the stock rom with Qualcomm's bootloader is for Lumia 710 devices only.
Step 1.
First we must know if your device has its bootloader unlocked. Nokia phones were previously (and prior to tango updates hold that too) shipped with Qualcomm's boot loader, which allows nand access (needed to flash roms) and allows us to unlock our phones. To do so you must turn your device off, then press Power and Volume Up key till it vibrates. Then connect it to your Windows PC, where you shall get a notification whether saying Nokia Dload (nokia's locked boot loader) or a Explorer pop-up asking you to format a flashdrive (do not do that). If you get the Explorer pop-up your good to go to Step 2 but if you got Nokia's Dload, don't panic.
You are able to downgrade the boot loader using an old rom (this one specific is from Russia) that holds the Qualcomm's unlocked one. For this you'll need Nokia Care Suite and the stock rom files. The stock rom files you might find here (http://forum.xda-developers.com/showthread.php?t=1599401), a great thread posted by Suzughia where you can learn more about this issue. Anyway, the file you need is in the FAQ session, second question/answer. The NCS file I used you can download here (http://www.4shared.com/file/0YxlvalR/Nokia_Care_Suite_5_20115126304.html?) from my 4shared account*, but for the latest release you'll might check the official site, just google it.
Once you got NCS installed you'll have to go to C:\Program Files\Nokia\Nokia Care Suite\Drivers\ and install WinUSB Drivers x86.msi (or, if you use Windows 64 bit, the respective file). Then go to C:\ProgramData\Nokia\Packages (note that ProgramData is a hiden folder) and create a new folder named Products. Within this folder you'll copy the folder you downloaded (and unzipped, its name shall be, in this case, RM-803).
Now on the start menu you search for Application Launcher, and the app that appears shall call the Nokia Care Application Launcher. There you choose Product Support Tool For Store, a tool that allows you to install any rom from recovery (even the phone you've already unlocked using this tutorial or bricked phones, by theory). Wait to app to load up and connect your device on the computer. Now select the “Automatic Product Selection” box and waits till it recognizes your device. Notice your device might restart once or twice.
Now, in order to install the rom on your phone you must firt open your device model (even if the program indentifies your phone). Go to File>Open Product and select your phone model (in this case the Nokia 710 RM-803). Now go to the sidebar and select Programming>Recovery, on Properties you'll see the information of the rom you downloaded. Select it and then click Start. Ready, your phone is being flashed with the rom 1600.3015.8107.12070, that holds the Qualcomm's bootloader. Wait for it to reboot and you're ready to go to step 2.
Step 2.
Now we're gonna install the custom fully unlocked rom to your phone over the stock rom we just installed. To do so you must have access to a Terminal prompt (wheter on a Linux distribution or on an emulator running on Windows; I strongly recommend you to use Linux, which is more reliable) which will allow you to write the rom image to the phone's flash memory. You'll also have to download the os image, which you can get from Lucifer3006 here (http://forum.xda-developers.com/showthread.php?t=1654415).
Once you have access to a Terminal prompt and to the os-new.nb file you're ready to go. It is discussed on the thread by Lucifer3006 the use o NSS (a Linux terminal emulator), which I don't have experience to share. For instance, I used Ubuntu 12.04 for the flashing.
First boot your phone into Qualcomm's driver mode (just turn off your device, and then boot up holding power + volume up untill you feel a short vibration and then connect your phone to the computer) . Now you have to know the "address" of your device (that's given by the system). Open up terminal and type:
fdisk -l
With this command you'll see a list of the registered blocks of the storage devices on your computer. Usually your device will be the second on listed (in the case you only have your hardrive and your device plugged to the computer) and it is named sdXY, where X is the name of your device and Y is the number of the partition. On my case my device was f.
Now navigate to the folder you saved the os-new.nb file in terminal (in my case I saved on the User's folder, where the terminal opens by default in Ubuntu, the distro I used, or in most Linux distros). To be sure verify if the file is there by typing "ls", it will show a list of the files on that folder. If everything's fine, now you should enter the command that will copy the os-new.nb file to the phone boot memory, so the rom will be literally installed when the phone is booted.
Type this command in:
dd if=./os-new.nb of=/dev/sdX9
Explanation: "dd" is the command that copies the "if" to the "of" partition with low level privilegies. In this case "if" is the os-new.nb file and "of" is the boot partition address of your device. Make sure to replace the X with your device name. For example, my device was named "f", so my address will be of=/dev/sdf9, where sdf9 stands for storage device f, partition 9**. The boot partition of Windows Phone is addressed as the nineth one of the device (it is not an statement).
Once done copying (it will give you no feedback but the blinking square, so when it's done you'll just see the prompt address again) you shall disconnect your device.
In order to boot your device you have to perform a hard reset (this will literally install the os-new.nb to your device). To do so you have to hold down power + volume up + camera key for 10 seconds, then release the power key but still hold the volume up and the camera key for more 5 seconds (this was said in other post I can't remember which, don't know if is the correct way, but it worked for me). If the device does not boot up you can remove the battery and place it again, now just turn it on normally, and it will boot into the custom fully unlocked rom.
Note that the WP Root Tool installed on the rom is the 0.9 version and as for up to today it has expired, so you won't be able to use it unless you set your device date to past August 2012. In Baazar you can install the newer version but for using it you must mark it as trusted in RootManager app included on the mod rom.
Post anything you have to say and if you have a doubt, just ask me and I might help with anything I'm capable of.
Notes:
Everything I posted here is upon my personal experience only. I do not own any rights over any file posted here through other threads. The responsability for them relies on the threads' holders then.
* I do not own any rights over this program and I just posted a personal link once I wasn't able to recall the original one. Also this is the only file who sucessfully recognized my device upon my experience.
** This is said just to make an example and clearify the idea, it is not its actual meaning for as long as I don't know its actual meaning.
All Links Used Here:
Nokia Care Suite version 2011.51.2.63046 5.0
http://www.4shared.com/file/0YxlvalR/Nokia_Care_Suite_5_20115126304.html?
Get Ubuntu Linux 12.04 for free
www.ubuntu.com
Nokia's 710 RM-803 Country Variant Russia direct download link:
http://narod.ru/disk/45935058001.2aaca38c9acf622332f4a81b5bf0e331/RM-803.rar.html (300mb)
How to Interp Unlock Nokia l710 original thread:
http://forum.xda-developers.com/showthread.php?t=1599401
RainbownMod v1.4 and older, also the original thread of discussion:
http://forum.xda-developers.com/showthread.php?t=1654415
Is it possible to get that ROM from somewhere else, all it does is download YandexBarChrome in russian!... lol
*nevermind... i installed the stupid bar and it let me get the file.
**I cant get this stuff to work.... I get an error when installing the NCS, it installs anyways, but then never detects my phone. Any help would be appreciated!!
XperianceIT said:
Is it possible to get that ROM from somewhere else, all it does is download YandexBarChrome in russian!... lol
*nevermind... i installed the stupid bar and it let me get the file.
**I cant get this stuff to work.... I get an error when installing the NCS, it installs anyways, but then never detects my phone. Any help would be appreciated!!
Click to expand...
Click to collapse
What operating system are you using? I usually get installation error and phone never detected when running it on Windows 7 or Windows 8 64bit.
You might try reinstalling the NCS, and if it holds the same error, check the official site for the updated program and try it.
When you connect your phone to the computer, does the program recognizes an unidentified handset or it doesn't recognize your phone at all?
Unlocked
Sent from my Lumia 610 using XDA Windows Phone 7 App
My problem is this:
File C:\Documents and Settings\All Users\Application Data\Nokia\Packages\Products\RM-803\RM803_059M5W4_Qualcomm_DLOAD.vpl has no signature.
I have a problem. After I copy the ROM to the memory, I can't seem to boot to it. I feel the vibrations but everything is black. Please any help
I am putting this together because, after three weeks of study and four days of full-time work I have finally pulled together the information needed to do this. I will also offer a lead on how to make your phone a Development phone. Sorry, no pictures or vids for the kids, just solid useful information.
You will start with an XT910 or XT912 which is locked to a carrier somewhere in the world. To unlock you must buy an unlock code from one of the sellers on eBay. This will cost from 49 cents to 5 dollars, depending on your phone. I assumed that all the sellers could get all the codes, so I bought the cheapest one and sent him my IMEI. He responded that he does not do Motorola and refunded my 49 cents. So I found a seller who does the XT910, and bought his cheapest auction (for an Atria unlock code). He responded that I had bought the wrong auction as I have an XT910. So I ended up having to buy his XT910 unlock auction and got the code. Now the phone will work with any GSM carrier in the world.
Next is the firmware. I knew the phone is running Gingerbread because in Settings|AboutPhone it said the Android version is 2.3.6. I wanted to upgrade to Ice Cream Sandwich (4.0.4) or higher, and to the MIUI ROM which I've used happily for a year. I went through the (scattered) RSD insctructions to flash ICS, but it always failed on the first file. I finally discovered that the RSD method does not work with many phones at v2.3.6, so I went to an alternative method developed by kholk, which I'll describe here. This method will work when others fail.
The first thing to know is that I'm a Linux type, but kholk also offers a Windows method which I have not tested. His Linux script has a few bugs, which I have corrected in the script attached hereto. Also his Linux fastboot binary is an older version which can not handle the larger image sizes we have now, so I have attached hereto a newer one which the source code was recently leaked from Motorola;
The next thing to know is that when posts mention "Fastboot files" they mean the ROM image files which are divided so they can be installed with the fastboot executable. OTA files are not the same, nor are they desirable. I gather that an OTA file is installed -after- the fastboot files, and provide an incremental upgrade.
Stock and ICS fastboot image files for our phone are here:
http://sbf.droid-developers.org/umts_spyder/list.php
I am in Seattle, WA, and I bought my phone on eBay locked to Rogers Canada. So I and my phone are in the North American region. My stock Rogers is 'Rogers Canada' Gingerbread v2.3.6:
Rogers_XT910_SignedLATAM_167-SLC-M33.1_P042_A014_CFC_1FF_fastboot.xml.zip
http://sbf.droid-developers.org/umt...-SLC-M33.1_P042_A014_CFC_1FF_fastboot.xml.zip
My Rogers ICS is 'Unknown Carrier' Ice Cream Sandwich v4.0.4:
6.7.2-180_SLC-35_R02_SIGNLATAM_SPYDERICSROGERS_P012_A012_HWp2b_CFC_fastboot.xml.zip
http://sbf.droid-developers.org/umt...CSROGERS_P012_A012_HWp2b_CFC_fastboot.xml.zip
North American users, use these. If you're in Europe you want the Central Europe image, ninth from the bottom, for ICS.
It's important to understand that the software you have in the phone at the moment, is "signed" for your specific region of the world. So you can not install a European image to a Canadian phone -- it will fail with "Preflash validation failure". The individual files you unzip from the image zip file will be transferred to their specific locations in the phone, -after- signatures are checked, to make sure you have files for the correct region.
So, choose your image file from the above list, unzip the image file, and put the fastboot executable and script in that resulting directory. I have modified the attached script to work for the Rogers images, basically by adding a couple files which were missing in the original script.
Side Bar: In the file list above, you will also find Development images, and if the fastboot executable could be rigged to ignore signatures, you could install the Dev image and voila, have yourself a development phone! The fastboot source code is available, so maybe some talented coder could make that (dangerous) change. This is dangerous because a n00b could flash a Euro image on his Canadian phone and it wouldn't work. (This error is easily reversable by flashing the right image) Comment by Vatazhka: The signature check is implemented in the bootloader. Unauthorized image gives preflash validation error and causes the bootloader to stop booting with an appropriate message. Moreover, the bootloader can't be unlocked as it lacks support for appropriate fastboot commands. The only way to get around these restrictions is to get a Motorola-signed version of a bootloader which doesn't implement checks, which luckily happened to Atrix guys (Clueless Motorola employees put it into a regular SBF, which was subsequently leaked.).
- Make sure your phone is --fully charged-- or else it could run out of battery and leave you with an expensive brick. Comment by Vatazhka: There are $6 cables to repair bricked devices with no juice left on eBay. Been there, done that It's the standard USB data cable with two pins shorted and ideally should also include a resistor to bring voltage from 5 V supplied by USB down to 3.8 V as supplied by the battery.
- Put the phone in fastboot mode by turning off, then holding Vol+- and power on. Select Fastboot and Vol+.
- Connect the -original- USB cable (some USB cables do not have data lines, only power, and you must have data lines for this) and connect to
your computer. On the phone Fastboot screen it should say "Connected" at the bottom.
- On the Linux computer in a Terminal window, cd to the image directory and # ./FlashLNX.sh It should flash away with no errors. The phone will
reboot and you'll get the Android with rotating polyhedral heart; it will reboot a couple more times and you have ICS!
- Root the phone.
- If you have an XT910, for Recovery you want BootMenu Manager, and if an XT912 you want SafeStrap. Install from the Market. You MUST NOT jump the gun and try to install BMM or SS to Gingerbread. It will brick you. Get up to ICS, then lay down your recovery. Comment by Vatazhka: Not true. SS2 and SS3 can be installed to both XT910 and XT912 (just be sure to install the correct SS2 variant). Developer of BMM actually owns an XT909, which is similar to XT912, and uses BMM on it. Simply choose the one which works with a given firmware (Hopefully this will be solved soon, so you could install whichever suits you, not the firmware.). One caveat: If you intend to try or install MIUI, it WILL NOT WORK with SafeStrap. You need BMM (which includes CWM) for MIUI.
- Now flash whatever image you want.
http://forum.xda-developers.com/showthread.php?t=1792955
I like MIUI:
http://forum.xda-developers.com/showthread.php?t=1756659
- If you ever want to go back to stock, just use the above process and flash GB 2.3.6.
Comment by Vatazhka: This is usually not possible. Most ICS updates bump some of the partition version counters which are stored in the "partition table", which doesn't allow you to go back. You can forget about resetting it - there is a digital signature (eFuse as well?) on guard again. You can only flash partition images with version number which is not lower than embedded in the "partition table".
I'm also not sure about this fastboot update stuff, but I may have used different fastboot variants which haven't had implemented this.
- If you install MIUI directly to the first slot by rebooting to Custom Recovery and installing zip, you will lose Custom Recovery when done so it needs to be reinstalled. The newer MIUIs do not come with GApps (this Play) so you have to get them here:
http://www.miuiandroid.com/community/forums/miui-weekly-rom-releases.103/
... and get BMM here:
http://forum.xda-developers.com/showthread.php?t=1720351
Since I don't have phone service yet I downloaded these to my PeeCee, put them on a microSD card and popped them into the phone. Install BMM with File Manager, and use it to reboot to Custom Recovery to install GApps. Then I used Titanium Backup to remove all G**gle apps except for Play, Framework, and one or two others. (I don't trust the Greatest Data Mining Operation In The History Of The World) Speaking of which, I always install DroidWall and only allow the minimum apps to access The Internets.
Then I used BMM to install CM10 JB to the second slot, just for fun. So now I have dual-boot! MIUI and CM10. Either one can be set to default. Caution though, for the zip you will install to the second slot you must convert it, as per the link above. The resulting file will begin with BM, and -that- is the one you will install. At the same time you can add GApps to be installed right after the ROM. You can -name- your two bootable OS' like this: BMM|BootMenuSettings then tap the very name and a cursor will come up. Delete and rename; Mine are MIUI 2.10.19 ICS and CM10 16.56.44 JB.
MIUI is already rooted, always.
One pleasant surprise in all this is that the new ICS MIUI Backup app does recognize old GB MIUI Backup savesets. I had to install Android Terminal and cp -r them over by hand, but it did restore all my old logs, SMS, apps, etc, thankfully.. I notice that the new MIUI Backup offers Encryption! Well, this really means that you are enabling backups to their "Cloud". In Red China. Where they can pore over your contacts, texts, logs, calls, and friends at their leisure. Encryption? Pshaw. ('shared key') Velly ingenirous.
Recommended apps: DroidWall, AdFree, Snowstorm, RadarNOW!
Some additional tips:
To reboot the phone and put it in FASTBOOT mode.
# adb reboot bootloader
To reboot the phone and put it in RECOVERY mode. Still need to push Vol up + Vol down to use the stock recovery.
# adb reboot recovery
For normal reboot
# adb reboot
For OTA updates (normally not needed), try
# fastboot update ota_update.zip
If low battery and not flashed:
1. Connect your phone using ORIGINAL USB cable to to ORIGINAL wall charger
2. Press and hold both Vol+ and Vol- buttons at the same time and then press and hold Power button until bootloader menu appears with Normal boot already highlighted
3. Use Vol- to highlight BP Tools and press Vol+ to select it
4. Screen with red M will appear followed by a screen with the battery and number undeneath showing how much charge your battery has now which means phone is now in the battery charge only mode
5. Wait for a battery to charge which should take over 3 hours
CAUTION: This method will FAIL if you have not completely flashed the system image. When your battery gets down to about 1/3, fastboot will refuse to flash images and you'll be screwed. There is no way to charge it unless it's booted. If you get in this predicament like I was, put your phone on a hot item, like a laptop power brick, and pray it recovers the battery enough to flash at least system and boot images. Flash them manually (copying lines in the script) if you have to.
Much gratitude to kholk, eval-, and to Jack'O who got me through this.
Well done dude.
Sent from my XT910 using xda premium
Thanks for your help and support Jack'O.
This thread already has 248 views in its first hour of life, LOL.
Wow, that's one comprehensive guide. Just a few corrections:
Side Bar: In the file list above, you will also find Development images, and if the fastboot executable could be rigged to ignore signatures, you could install the Dev image and voila, have yourself a development phone! The fastboot source code is available, so maybe some talented coder could make that (dangerous) change. This is dangerous because a n00b could flash a Euro image on his Canadian phone and it wouldn't work. (This error is easily reversable by flashing the right image)
Click to expand...
Click to collapse
The signature check is implemented in the bootloader. Unauthorized image gives preflash validation error and causes the bootloader to stop booting with an appropriate message. Moreover, the bootloader can't be unlocked as it lacks support for appropriate fastboot commands. The only way to get around these restrictions is to get a Motorola-signed version of a bootloader which doesn't implement checks, which luckily happened to Atrix guys (Clueless Motorola employees put it into a regular SBF, which was subsequently leaked.).
- Make sure your phone is --fully charged-- or else it could run out of battery and leave you with an expensive brick.
Click to expand...
Click to collapse
There are $6 cables to repair bricked devices with no juice left on eBay. Been there, done that It's the standard USB data cable with two pins shorted and ideally should also include a resistor to bring voltage from 5 V supplied by USB down to 3.8 V as supplied by the battery.
- If you have an XT910, for Recovery you want BootMenu Manager, and if an XT912 you want SafeStrap. Install from the Market. You MUST NOT jump the gun and try to install BMM or SS to Gingerbread. It will brick you. Get up to ICS, then lay down your recovery.
Click to expand...
Click to collapse
Not true. SS2 and SS3 can be installed to both XT910 and XT912 (just be sure to install the correct SS2 variant). Developer of BMM actually owns an XT909, which is similar to XT912, and uses BMM on it. Simply choose the one which works with a given firmware (Hopefully this will be solved soon, so you could install whichever suits you, not the firmware.).
- If you ever want to go back to stock, just use the above process and flash GB 2.3.6.
Click to expand...
Click to collapse
This is usually not possible. Most ICS updates bump some of the partition version counters which are stored in the "partition table", which doesn't allow you to go back. You can forget about resetting it - there is a digital signature (eFuse as well?) on guard again. You can only flash partition images with version number which is not lower than embedded in the "partition table".
I'm also not sure about this fastboot update stuff, but I may have used different fastboot variants which haven't had implemented this.
Sent from my XT910
Thanks Vatazhka, I've added your remarks.
So what carrier are you going to use it with? Prepaid of some sort?
Sent from my XT912 using xda app-developers app
N, TMobile USA. It was locked to Rogers Canada but I unlocked it. It's working great. Been with TMo for seven years, and this time I asked them for a credit to buy the phone. (Last contract renewal I got $100 for the Nexus One) They wouldn't give me cash, but put me on a new "Value" plan with unlimited everything and $25 less than I've been paying, for $64/mo. Saving $25/mo over two years works out to alot more than the $280 I paid for the phone.
Here in Seattle we have HSPA+ and I've got fast internet. Supposed to have LTE next year, but HSPA+ is fine. TMo is moving everything to 1900MHz as fast as they can for iPhone compatibility, so we benefit.
Voice quality on this phone is far better than any HTC. The screen is so large I'm not used to it. Concerned that when I sit down I'll crack it in my back pocket, or it will slip out.
MIUI only allows 4x5 icons on the screen and I think I could use 5x7 so I've posted a request on miuiandroid.com.
Thanks
i want to upgrade my just bought vzn razr xt912 to ics and want to use as gsm phone here in india
can anyone help
which ICS ota file should choose from the list mentioned at the OP
and how to proceed.
regards
Get the one for Verizon Droid RAZR XT912.
Sent using a touch screen
Napisane na ekranie dotykowym
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.
Vodafone Smart tab 3 10 (aka Lenovo S6000H) and the "Please press button to set ..."
I have got a Vodafone Smart tab 3 10 (the one with the 10 inch display). It should be the same as Lenovo S6000H (as the Vodafone Smart Tab 3 7 is the same as Lenovo A3000H). It has 1gb ram and 16gb memory.
I received it quite bricked; I mean, when it was gave me (so before any action done by me) I turned it ON and it showed the Android logo and then it rebooted continuosly (loop). The person who gave it to me told me he tried to restore default configuration (the tablet was ok) with low battery. So low that during the restore action it switched OFF... bricked. Honestly, I don't know if this is true or of he tried to flash a rom (maybe a wrong rom).
Anyway, I flashed a standard Lenovo rom: now it doesn't show anymore the Android logo but the Lenovo label and it doesn't reboot anymore (till here is ok)... The fact it's that after showing the Lenovo label it shows the message "Please press button to set the Country Code" and I can't do anything (because even if I press on the display I haven't any result). I can only switch it OFF holding the power button.
I tried every stamdard rom placed here
http://lenovo-forums.ru/forum/182-lenovo-ideatab-s6000-официальные-прошивки/
but without amy success: same results.
- Any suggestion?
- And if i flash also the fac.img can I have something different (all rom I have flashed haven't the fac.img checked)?
- In recovery mode I can't do anything die to the fact there isn't any item that can be selected
Attached logs extracted during the latest flash
Many thanks
Hi, any help on this?
Hello my friend! I've been out of the MTK world a bit, but my daughter's A1000 is giving me fits, so I may be back! It too has a battery problem. It will not charge after the battery drains to a certain amount. Lenovo has a software patch -- but this POS A1000 won't go into programming mode most of the time. (I've also gone to Win7 from XP for flashing, it seems I knew how to work with the MTK drivers better in XP)
sverza said:
Anyway, I flashed a standard Lenovo rom: now it doesn't show anymore the Android logo but the Lenovo label and it doesn't reboot anymore (till here is ok)... The fact it's that after showing the Lenovo label it shows the message "Please press button to set the Country Code" and I can't do anything (because even if I press on the display I haven't any result). I can only switch it OFF holding the power button
Many thanks
Click to expand...
Click to collapse
I think I might be able to help. I suspect the difference between the Lenovo and the Vodafone is the partitioning. What I've found is my old Vodafone Tab 2 (and some other A2107A variants) has a FAC partition and others don't. This is the partition that has the code to select a Country Code. So you have one more partition on some OEM versions, and that partition is in the middle so it shifts down others. This causing your Country Code Selection to never get written properly, and loop.
So... the only way I was able to flash in those situations -- do a FORMAT in SPFT with a scatter that matched the new ROM. The FORMAT will re-apply the scatter partitioning to the device. I also had to re-write the bootloader code which I think is just a checkbox in the FORMAT screen to format WHOLE.
Caution -- Flashing a A2107A-H generic to a A2107A-F, I was able to use the FM Radio... which Lenovo claimed the -F didn't have. But... The -F with the -H firmware was VERY jittery. Just a word of caution about mixing ROMs with different devices.
I can look deeper into this if needed over the weekend.
syserr said:
I think I might be able to help. I suspect the difference between the Lenovo and the Vodafone is the partitioning. What I've found is my old Vodafone Tab 2 (and some other A2107A variants) has a FAC partition and others don't. This is the partition that has the code to select a Country Code. So you have one more partition on some OEM versions, and that partition is in the middle so it shifts down others. This causing your Country Code Selection to never get written properly, and loop.
So... the only way I was able to flash in those situations -- do a FORMAT in SPFT with a scatter that matched the new ROM. The FORMAT will re-apply the scatter partitioning to the device. I also had to re-write the bootloader code which I think is just a checkbox in the FORMAT screen to format WHOLE.
Caution -- Flashing a A2107A-H generic to a A2107A-F, I was able to use the FM Radio... which Lenovo claimed the -F didn't have. But... The -F with the -H firmware was VERY jittery. Just a word of caution about mixing ROMs with different devices.
I can look deeper into this if needed over the weekend.
Click to expand...
Click to collapse
Many thanks friends!
To be clear, I'm trying to flash the standard rom only because I can't find any rom related to Vodafone Smart Tab 3 10.
For me having the Vodafone rom or the standard one is the same.
Question:
1) Example, I have the standard rom related to Vodafone Smart Tab 3 7 (it should be the little brother of the 10 inch) that I've dumped when I had it... can I flash it to the 10 inch...?
2) In all tests I've done using SPFlashTool I have used the DOWNLOAD option (not the "firmware->upgrade" OR the "format" function), without checking the "DA DL ALL WITH CHECK" and without checking the FAC.img (infact when I load the scatter file provided with the rom this .img isn't checked)
I apreciate your help if you can give a look
Many thanks
syserr said:
Hello my friend! I've been out of the MTK world a bit, but my daughter's A1000 is giving me fits, so I may be back! It too has a battery problem. It will not charge after the battery drains to a certain amount. Lenovo has a software patch -- but this POS A1000 won't go into programming mode most of the time. (I've also gone to Win7 from XP for flashing, it seems I knew how to work with the MTK drivers better in XP)
Click to expand...
Click to collapse
eheh the old friend win xp!
sverza said:
Many thanks friends!
To be clear, I'm trying to flash the standard rom only because I can't find any rom related to Vodafone Smart Tab 3 10.
For me having the Vodafone rom or the standard one is the same.
Question:
1) Example, I have the standard rom related to Vodafone Smart Tab 3 7 (it should be the little brother of the 10 inch) that I've dumped when I had it... can I flash it to the 10 inch...?
2) In all tests I've done using SPFlashTool I have used the DOWNLOAD option (not the "firmware->upgrade" OR the "format" function), without checking the "DA DL ALL WITH CHECK" and without checking the FAC.img (infact when I load the scatter file provided with the rom this .img isn't checked)
I apreciate your help if you can give a look
Click to expand...
Click to collapse
You are going to have bad luck trying to use a ROM even for a slightly different model.
To add or remove or resize a partition (or you might call it a block) in the flash, you have to use the Format function. This is scary for sure though.
Side note:
Many people have broken their tablets and phones trying to resize partitions with tools, because the tool fixes exactly one model/variant. So if you use some slightly different model, it goes and tweaks things incorrectly.
My Chinese Android car head unit is stuck in a bootloop (the home screen shows but the unit reboots after a few seconds). I got a firmware zip file from the manufacturer (the zip contains files like scatter.txt, ramdisk2.img, boot.img and so on). However, I'm unable how to find out how on earth I can install this firmware and get out of my bootloop.
I have no access to Android itself (the system reboots too soon). There are no physical buttons to activate recovery mode. When I use a USB keyboard I can get into recovery by pressing ALT GR and PRT SCR but after a reset "no command" shows up and I'm stuck again...
Any help please?
Flashing instructions
[Apologies for the lengthy reply, I have to assume that you have no experience in flashing MTK SoC]
Sorry to hear that! I am also contemplating t buy a Chinese Android headunit with GPS but I am still contemplating. Reason being which model to buy? I am an avid Lenovo devices fan because in my part of the world models from Lenovo uses a lot of MTK SoC. (Any other other brand I buy is also a must to be on MTK SoC)
Ok! Now based on your short description I saw "scatter.txt" file mentioned so it is definitely an MTK devices, 100%.. When you boot loop you definitely will not be able to access any function, more so with a head unit that dont provide hardware buttons. I can only help you understand the method to reflash the firmware on MTK devices the rest you have to figure it out yourself.
The USB port is your key here. If the manufacturer did not provide you with USB "IN" (female) port which is not normal and only provide you with USB connectors you will have to decode/or just connect the wiring from the connectors to a USB female Port (which what China manufacturers do at the back of the head unit). There are also head units that provide ready to use USB port on the facia.
Whatever it is I cant tell you which port to use. This where you will have to experiment yourself.
Download MTK flashing tool "SP Flashtool" (find the ones that is suitable upto MTK device 6592 because it should be back ward compatible with older devices) The Chinese dont use the latest MTK SoC for their head units, that is only reserved for the high end heads.
Read up on how to install SP Flashtool on your PC and other accompanying Drivers you have to install, (if you only have a Mac go borrow somebodys Win7 or Win10 PC) there are no Mac SPFlashtool.
Once you have install according to SPFlashtool instructions you read. (It has to follow a certain sequence) e.g "1- ADB Driver" so on and so forth because if you dont follow the sequence it might fail to start the flashing operation. (You will not know it but I am pretty damn sure you will be cussing me).
First read up on how to install ADB driver for MTK devices correctly. Confident? Now try connecting your device to the PC experimenting to identify the correct USB port to use. If the ADB is installed correctly and you got the right USB from the device connected your PC wil give an audible sound( it should unconnected to condition evreytime you test). OK good connection! Only then try installing SP Flash tool and try a dry running the SPFT. If your installation is correct there should be either color changes to the SPFT window because it doesnt detect any devices.
You are good to go! Your MTK Android device should be in the "OFF" condition (after every shutdown there are still some operation running in the background,so it is a good practice to wait at least 5 seconds for it to be 100% OFF.) Run the SPFT fully loaded with the firmware dislayed in the SPFT window. Then initiate "Download" (make sure all indicators is at "download only" do not change this option or you are gonna have a really dead duck.) At this point the SPFT is active and waiting for you to attach the device to PC (before running make sure the PC and device is not connected yet!). If everything is per instructed ADB, USB Cables/Ports, SPFlashTool (download only) you will see color lines in the SPFT Window, wait till the end of process it will display notificatio. If the firmware is correct and you have attached and 12V DC source to the device it should boot up as fresh as new.(provided that the supplier gave you the correct firmware).
A word of advise these cheap head units normally bluff their actual Android version e.g actual KitKat advertised and displayed as Marshmallow. Best of luck!
The zip file attached are screenshots of the flashing process.
Thanks for your very elaborate information, but it won't work. The ZIP I got is an OTA zip file. The scatter.txt inside those zips isn't compatible with the SP Flash Tool.
wimpie3 said:
Thanks for your very elaborate information, but it won't work. The ZIP I got is an OTA zip file. The scatter.txt inside those zips isn't compatible with the SP Flash Tool.
Click to expand...
Click to collapse
Doesnt the seller provide you with the original firmware? He only gave you an OTA?? Oh $#it! The OTA file is small probably a few Mb? The full firmware in your case should be around 800Mb upwards. You are right an OTA cannot use SPFT it can only be flash through the original recovery (not custom recovery). If its a popular Chinese model ML-CK1018 or Joying brand ( I assume you bought a Joying? Thats the only brand that release an OTA not long ago) There is remote possibility of getting the firmware.Anyway just give your brand and model number. I will try to look on Russian or Chinese site but no promises! Will try.
But I am pretty sure it is an MTK SoC since you can unzipped and it shows "scatter.txt" file. Most other SoC arent normally in zip format and have scatter file.
Sent from my HT70 using Tapatalk
The OTA ZIP file is about 900MB.
It's a NAVITOPIA 9 inch 4G LTE WIFI Head Unit with Android 6.0 2G + 32G.
I'm in the same boat, have a plastic bookend at the moment, will not connect to the PC because flashed and formatted my device with the update firmware!!!