Related
Hi Everyone,
I know there are stupid people out there like myself that bought a crapy chineese tablet with model msm7227 shown that would like to know how to root the phone. Installing the Gingerbreak apk file and running it seems to do the trick.
I tried to take it a step further and upgrade the android version from 2.2.2 to 2.3.3 following instructions from a russian site that I translated.
Russian site link:
ublaze.ru/forum/ftopic1158.html
I translated the instructions in the website below. Refer to pdf attachment for instruction and pics:
Unfortunately I only managed to go as far as Step 3 G. Click Start to update ARM9.
Your tablet will automatically reboot after the upgrade.
For me after I click start the status changes indicating that it is Changing the Phone to Download Mode
It then switches off the unit and loses the com connection to the phone and the status changes to "Attempting to run Flash Programmer"
It fails then with the status "Software Download Aborted" Error "Could Not Communicate with Flash Programmer". I try an restablish the connection during the status "Attempting to run Flash Programmer" but it makes no difference.
So I have pretty much left it there. If any one else is game to give it a go and have better luck good luck. My unit still works after I reset it but its still on Android 2.2.2.
INSTRUCTIONS
Характеристики QUALCOMM MSM7227 FFA 3g
Код: Выделить всё
QUALCOMM MSM7227-1 Tablet PC with Mobile Phone function
Android 2.3 OS
512MB RAM +4GB Flash Memory
7 inch capacitive multi-touch screen
Built in 3G module and WiFi and bluetoothBuilt in GPS navigation
Built in 2.0MP/0.3 CMOS dual cameras
Support phone call and flash10.1 playing
ID устройства:
USB\Vid_05c6&Pid_9018&Rev_0226&MI_00
USB\Vid_05c6&Pid_9018&Rev_0226&MI_01
USB\Vid_05c6&Pid_9018&Rev_0226&MI_02
The firmware consists of 4 steps.
Step 1. Zhelateono have a PC running Windows XP, but I probyval and Windows 7 32-bit also works.
Step 2. Installing the USB driver
рис. 1
If the popup window does not appear automatically, go to the Device Manager> Other Devices
and click the right mouse button on the label Qualcomm HSUSB Device and select> Update Driver
pointing the way to the drivers for each Qualcomm HSUSB Device (see Fig. 2) as follows (see Fig. 1)
рис. 2
Step 3. update ARM9
A. Turn the tablet and connect it to your computer.
B. Go to Device Manager and check that, if the operating system your computer has defined the tablet (see Figure 3.)
рис. 3
C. Installing the program QPST.
рис. 4
D. Click Start, and then click the QPST Configuration. Add all the ports that are able to find (see Fig. 5)
рис. 5
Navigate to the Software Download tab and remove the check mark from C Auto Backup/Restore
рис. 6
рис. 7
Click Start clients and select Software Download, and then click Multi-image.
Click Browse and specify the correct path to the image (image).
Код: Выделить всё
...\Reflash Software\ARM9\image
Click Advanced, select the AMSS Apps Boot Ldr Hearder and AMMS Apps Boot Loader, then click OK
рис. 8
The tab Multi-image, uncheck Auto Backup / Restore
рис. 9
G. Click Start to update ARM9.
Your tablet will automatically reboot after the upgrade.
Step 4. update ARM11
A. Make sure your tablet is connected to your computer via USB-cable.
B. Open ... \ Reflash Software \ Android_Download_tools \ Arm11 V1.7_20110418 \ Android_download.exe
C. Click Connect and verify that the displayed fastboot device
D. Press the volume (Volume) and the power button, and then click the Reset button (Reset)
E. Hold down the volume (Volume) and the (what exactly, the instructions are not written - most likely the trigger) and then, in the program, click Connect again.
And then start flashing.
F. Click Run and wait for as long as see the word Done!!!
рис. 10
G. In this update is completed.
Note. If your tablet does not flash, as I have, in some cases, do the following:
1. Take the sd card and dump the sd card to the root of the archive here: update.zip
2. Insert the sd card into the tablet.
3. Hold the power button and press vol -.
4. Without releasing the two buttons we press on reset clip (located just below the buttons vol -)
Next tablet should enter into recovery mode, that's how it looks:
5. Next, we need to press the Home button (Home)
6. C Use the "vol +" and "Vol -" go to the inscription:
code: Выделить всё
apply sdcard:update.zip
and press the touch button with the four squares (just below the button home)
7. Upgrade process will start. At the end of reset the unit.
Download the firmware for Ipad QUALCOMM MSM7227 FFA 3g
Скачать прошивку для Ipad QUALCOMM MSM7227 FFA 3g
Use this tool to root it : http://www.only4download.com/2012/05/download-superoneclick-android-software.html
Don't forget the THANKS button
You Biscuit!!!!
Thanks guys for helping me to flash my device!!! Running 2.3 with full marketplace. WOO HOO!!!
Ok I had managed to root it before finding your post. ( I think it was UnversalAndroot if memory serves me right - tried so many! )
Used Chrome to translate the original Russian page to English. The USB drivers and the quickboot drivers are all in the file listed on that site. (2.3 software ) I used a Windows XP workstation to connect the device and load the drivers.
To get the device into fastboot:
turn on while holding the Volume UP + button. You should see the android robot.
Connect to PC and install the ADB driver.
Run the Android_download.exe and let it do it's magic. The device will reboot twice and will show a new logo on rebooting. ( at this point I installed the standard USB drivers )
The device will default to Chinese language. Find the settings icon ( blue rings on black ) and look for the icon with an "A" on it.
The network does not work - I assume its because of my region ( South Africa GSM 900 / 1800 / 2100 ) and something is missing in the drivers. It no longer detects a SIM or network.
At least I have a device that resembles a proper Android device now! Time will tell if it's any more stable than the brickware it came with.
Please don't ask me too many technical questions - I'm not a pro by any means!
Thanks
Finally
Finally found the time to get around to trying the flashing to Android 2.3.3 again.
It all worked great this time round. The issue I was having with installing the ARM 9 update was that everytime it changed the unit to download mode and rebooted it, the COM port would change and lose connecitvity after the reboot. But once I used the browse button in the QPST Configuration application and changed the port to match the new port allocated after the reboot it successfuly transfered the software across without the error.
Its so great now that the unit has Android 2.3.3 as now all the following things have been fixed and verified working
1) 3G data works properly now with Telstra
2) Phone and messaging works with Telsta
3) I dont get face book error in the news read section
Theres still a few android apps that are not compatible with the device like, Adobe Flash player but there are suitable alternatives.
But now its a nice workable unit. Very Happy :>
Some error has been solved
saintlypaul said:
Finally found the time to get around to trying the flashing to Android 2.3.3 again.
It all worked great this time round. The issue I was having with installing the ARM 9 update was that everytime it changed the unit to download mode and rebooted it, the COM port would change and lose connecitvity after the reboot. But once I used the browse button in the QPST Configuration application and changed the port to match the new port allocated after the reboot it successfuly transfered the software across without the error.
Its so great now that the unit has Android 2.3.3 as now all the following things have been fixed and verified working
1) 3G data works properly now with Telstra
2) Phone and messaging works with Telsta
3) I dont get face book error in the news read section
Theres still a few android apps that are not compatible with the device like, Adobe Flash player but there are suitable alternatives.
But now its a nice workable unit. Very Happy :>
Click to expand...
Click to collapse
I have solved some error when update rom for it. I attached it from file word
HELP ERROR update ARM9
Hi, I have a problem when star the process appear in red NAK: Invalid Address
I have read the manual 6 times and nothing, please how I can fix this error
Same Error
Hi
I am getting the same error as yours.
Where you able to move ahead an upgrade the tablet to 2.3 ?
my pantech sky vega a760s got soft bricked
here's what happened:
-the phone won't open unless connected to pc
-when connected, it will only go to charging mode
-when i try to enter recovery mode, this shows up:
"your phone will restart due to error occurred while running application "
i cannot access recovery mode, the only thing i can access is the s/w upgrade mode, which i don't know how to use since i'm not korean
and i can't understand pantech's website.
also, when i enter in fastboot mode, all drivers are installed except for a driver named "Android" which is too general for me to manual search (inlcuded an image attachment of the failed driver)
How can I unbrick my phone?
PLEASE HELP. THANK YOU IN ADVANCE.
same here..
same here my sky vega a760 stock on boot image anyone can help plsss how can i revive this..plsssss.
joekap said:
same here my sky vega a760 stock on boot image anyone can help plsss how can i revive this..plsssss.
Click to expand...
Click to collapse
You should re-install new room stook via home page iVeGa:good:
Re: Help..
tnx for the reply but how can i reinstall i dont know where to donwload and i cant understand in korean site.. plsss send me working rom for A760s plsss...tnx
[TUT]Recovery Mode Sky Vega Racer IM-A760S/A770K
joekap said:
tnx for the reply but how can i reinstall i dont know where to donwload and i cant understand in korean site.. plsss send me working rom for A760s plsss...tnx
Click to expand...
Click to collapse
To go into Soft/Ware download mode
1. Turn of phone
2. Simultaneously press: VOLUME UP + MENU + POWER
3. S/W Upgrading will now flash on the screen
To upgrade firmware back to version 1.47, you first need to have the UniUSBdriver installed on your computer.
4. After you have installed the driver, test your phone’s connection to the computer to initially determine all the required drivers were installed properly (this is while your phone is in S/W download mode). But before doing this, make sure that you have activated USB DEBUGGING on your phone.
Code:
>settings
>applications
>development
>usb debugging (must be checked)
5. Using Microsoft Internet Explorer v8 or v9, proceed to this page:
-------------->>> dmfile.isky.co.kr/NewSelfUpgrade/index.html?userid=&hpno
Notice when that page opens, it will prompt you to install ACTIVE X. Allow that installation to proceed.
6. After ACTIVE X has been installed, notice on the left side there is a something like loading prompt. Wait until it gets into blue bar with arrow up phrase noting USB with some Korean characters. Then boot to S/W mode your phone and plug it to your compurer then click the blue bar with arrow up.
7. Clicking the Blue bar with arrow up will turn it into a progressing bar. Notice the characters on top of the progress bar may change and at this point there is communication between the phone and the Sky download site. It may take a few minutes for the phone to establish a download connection between Sky’s services. Once a connection is established, the characters above the progress bar will turn into a progressing percentage bar starting from 1% and ending into 100%.
There will be two phases of the progressing percentage bar. The first phase is downloading the software while the second is loading the v1.47 software into the phone. After the 2nd phase, the phone will automatically reboot. The first phase will depend who slow or fast your internet connection is.
:fingers-crossed: Goodluck :fingers-crossed:
clearlangpo said:
To go into Soft/Ware download mode
1. Turn of phone
2. Simultaneously press: VOLUME UP + MENU + POWER
3. S/W Upgrading will now flash on the screen
To upgrade firmware back to version 1.47, you first need to have the UniUSBdriver installed on your computer.
4. After you have installed the driver, test your phone’s connection to the computer to initially determine all the required drivers were installed properly (this is while your phone is in S/W download mode). But before doing this, make sure that you have activated USB DEBUGGING on your phone.
Code:
>settings
>applications
>development
>usb debugging (must be checked)
5. Using Microsoft Internet Explorer v8 or v9, proceed to this page:
-------------->>> dmfile.isky.co.kr/NewSelfUpgrade/index.html?userid=&hpno
Notice when that page opens, it will prompt you to install ACTIVE X. Allow that installation to proceed.
6. After ACTIVE X has been installed, notice on the left side there is a something like loading prompt. Wait until it gets into blue bar with arrow up phrase noting USB with some Korean characters. Then boot to S/W mode your phone and plug it to your compurer then click the blue bar with arrow up.
7. Clicking the Blue bar with arrow up will turn it into a progressing bar. Notice the characters on top of the progress bar may change and at this point there is communication between the phone and the Sky download site. It may take a few minutes for the phone to establish a download connection between Sky’s services. Once a connection is established, the characters above the progress bar will turn into a progressing percentage bar starting from 1% and ending into 100%.
There will be two phases of the progressing percentage bar. The first phase is downloading the software while the second is loading the v1.47 software into the phone. After the 2nd phase, the phone will automatically reboot. The first phase will depend who slow or fast your internet connection is.
:fingers-crossed: Goodluck :fingers-crossed:
Click to expand...
Click to collapse
i need help. i just installed uniUSBdriver and it's successful. however, when i connect the phone there is one driver that is unable to install. the driver is just called "android" tried to look everywhere for a manual installer but the name of the driver is too vague to search. can you please help me with this one? it seems like the self upgrade site can't detect the phone without this driver installed.
Solution Soft brick, Android drivers in Fastboot
jimmygammi said:
i need help. i just installed uniUSBdriver and it's successful. however, when i connect the phone there is one driver that is unable to install. the driver is just called "android" tried to look everywhere for a manual installer but the name of the driver is too vague to search. can you please help me with this one? it seems like the self upgrade site can't detect the phone without this driver installed.
Click to expand...
Click to collapse
1. Connect your phone in Fastboot, and when your pc asks for 'Android' drivers, you need to install PDAnet, just google to download it.
2. then to Fastboot, and Install Recovery SWM v6 either normal or touch
3. Then go to Recovery and Install new stock/custom rom from SdCard.
thats all. :fingers-crossed:
bobby786pk said:
1. Connect your phone in Fastboot, and when your pc asks for 'Android' drivers, you need to install PDAnet, just google to download it.
2. then to Fastboot, and Install Recovery SWM v6 either normal or touch
3. Then go to Recovery and Install new stock/custom rom from SdCard.
thats all. :fingers-crossed:
Click to expand...
Click to collapse
can you post links where to get the recovery image and a link where to download roms? i'm trying to search but no luck. your help will be really appreciated. thank you very much :laugh:
stuck at s/w uploading
heeelp can anyone help me... my a760s dont turn on and if i plug a charger or into a pc the only thing that apears is "s/w uploading"
Did you fix it? results?
beakolang said:
heeelp can anyone help me... my a760s dont turn on and if i plug a charger or into a pc the only thing that apears is "s/w uploading"
Click to expand...
Click to collapse
Although its long enough for you to forget you once had Sky 760 but did you try the method posted by "clearlangpo"?
You phone reincarnated anyway?
clearlangpo said:
To go into Soft/Ware download mode
1. Turn of phone
2. Simultaneously press: VOLUME UP + MENU + POWER
3. S/W Upgrading will now flash on the screen
To upgrade firmware back to version 1.47, you first need to have the UniUSBdriver installed on your computer.
4. After you have installed the driver, test your phone’s connection to the computer to initially determine all the required drivers were installed properly (this is while your phone is in S/W download mode). But before doing this, make sure that you have activated USB DEBUGGING on your phone.
Code:
>settings
>applications
>development
>usb debugging (must be checked)
5. Using Microsoft Internet Explorer v8 or v9, proceed to this page:
-------------->>> dmfile.isky.co.kr/NewSelfUpgrade/index.html?userid=&hpno
Notice when that page opens, it will prompt you to install ACTIVE X. Allow that installation to proceed.
6. After ACTIVE X has been installed, notice on the left side there is a something like loading prompt. Wait until it gets into blue bar with arrow up phrase noting USB with some Korean characters. Then boot to S/W mode your phone and plug it to your compurer then click the blue bar with arrow up.
7. Clicking the Blue bar with arrow up will turn it into a progressing bar. Notice the characters on top of the progress bar may change and at this point there is communication between the phone and the Sky download site. It may take a few minutes for the phone to establish a download connection between Sky’s services. Once a connection is established, the characters above the progress bar will turn into a progressing percentage bar starting from 1% and ending into 100%.
There will be two phases of the progressing percentage bar. The first phase is downloading the software while the second is loading the v1.47 software into the phone. After the 2nd phase, the phone will automatically reboot. The first phase will depend who slow or fast your internet connection is.
:fingers-crossed: Goodluck :fingers-crossed:
Click to expand...
Click to collapse
Hello Hacker!
I am Zahid Gill and a software engineer by profession. Websites are my speciality. I love android and Korean phones. I have bricked/ unbricked fixed and patched many phone before (but only with XDA's help ) many
While flashing Sky vega 760s it stuck on some point. I waited long enough but thenI had to remove it and.... it was bricked.
I was still able to go to recovery, fastboot and bootloader. I tried wiping /system and others but cwm was not able to.
I tried flashing with offline flasher tool again but it went into red screen on bootloader, like here:
http://sphotos-g.ak.fbcdn.net/hphotos-ak-prn1/p206x206/26340_10200120329905648_1168156367_n.jpg
NOW, offline flashing stuck on 60%. I am unable to boot the phone in any other mode. Even putting on charging takes phone to this red s/w mode.
Are you able to help me with this? I shall be very thankful.
PS: I had stock ROM 4.1.2 originally updated with no custom tickling.
Did you find any solution
Hello I also stuck in same situation. My phone ima-760 got soft brick and red S/w upgrading only. Kindly help if any one has a solution.
Buddy
jimmygammi said:
my pantech sky vega a760s got soft bricked
here's what happened:
-the phone won't open unless connected to pc
-when connected, it will only go to charging mode
-when i try to enter recovery mode, this shows up:
"your phone will restart due to error occurred while running application "
i cannot access recovery mode, the only thing i can access is the s/w upgrade mode, which i don't know how to use since i'm not korean
and i can't understand pantech's website.
also, when i enter in fastboot mode, all drivers are installed except for a driver named "Android" which is too general for me to manual search (inlcuded an image attachment of the failed driver)
How can I unbrick my phone?
PLEASE HELP. THANK YOU IN ADVANCE.
Click to expand...
Click to collapse
I have the same problem but a lot of the answers are to re-install stock? Which part don't they understand...it's BRICKED ( and only shows the RED S/W Upgrading symbol) so it's impossible to Flash stock firmware in that state?
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
petoxxx said:
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
Click to expand...
Click to collapse
mine is not working i think mine is bricked completly
bricked my mobile...Help!!!!
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
sivakarthick said:
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
Click to expand...
Click to collapse
The thread called 'Problem with huawei vision' still seems to be active. You may want to try asking your question over there.
Huawei (u8850) unbricked
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
how to turn off huawei u8850 completely
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
bikeshrt said:
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
Click to expand...
Click to collapse
it's actually not difficult to remove the battery...
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Anyone here interested in developing a 3.x kernel? seems other phones with msm8255 have successfully got one...
u8850 power off
btsimonh said:
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Click to expand...
Click to collapse
now i have tried it, and no success.
However, what i have found to work - if your non-boot is actually booting the kernel, but failing to initialise the phone, then you can still use adb with it... I ran adb shell, and then used 'poweroff' to power off my phone, which then meant i could boot into CWM recovery....
i HAVE THE SAME PROBLEME? PLEASE CAN U HELP ME TO SOLVE IT BY GIVING ME DETAILS.
it is working, thank you bro
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
it is working thanks bro
Stock rom download plz.
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
HOLY GOD! F**K ME!!! I finally did it! THANKS A LOT, BRO! YOU'RE AWESOME!!!
This might be a long situp to write this, but i've experienced that a lot of the excelvan users do not really know, where to get support for their device. I've bought this device because the price was low. And so is the quality. It is assembled with a JTY mt10 smarphone mainboard, connected to a 10,1'' touch display.
I've bricked the device and getting help to retrieve it back to life was a pain. No support from excelvan, so I've experimented with it, to find the best possible solutions. In order to help you save time on rechearching this issue, I'll now post this, hoping it helps you getting the tablet back to life and running.
Notice: this is for excelvan mt 10 tablet only. I have no idea, if this works for any other product, so don't ask me, just look around the forum to find help. If the real hardware is bricked, this won't work either, your device should be repaired by qualified service persons to proceed with this.
1 setup your pc to get started.
I've installed the following software on my windows 10 desktop pc:
- The MTK Droid tools, links are supplied by this forum
- The MTK Sp Flash tool, you'll find links for that in this forum or get it from mediatek
- Philz recovery, use google to find it
- Kingo Root, you'll find it at the kingo root home page
- The Mediatek VCOM USB Drivers for Windows 10 (As for my PC) at Mediatek.
- The stock rom for excelvan mt10 tablet, you'll find it on needrom, download for registered users only
Installation of the software on your pc is straight forward, just follow the on-screen installation instructions and you'll be good to go.
Probably your device is bricked already, so no further action needs to be taken on your device.
The first thing you'll have to do is to see, if your drivers can connect to the device. To achieve this, follow the procedure below.
1. After setting up the drivers package, connect the device to your PC, using original USB cable. There are a lot of cables around there, but please use the original provided cable, as it is not sure, that other cables have all pins connected for this, so do yourself a favour...
2 Go to the device manager in your pc and look for your phone's name or the mediatek VCOM driver to run. If the device is booted up, you'll find them, if your device is bricked, you'll have to initiate the META mode of the 6572, to establish the connection. Luckily, the device has a reset button, so if it is bricked, you'll need to connect it to your PC, open up the device manager and press the reset button. (I've opened the device the very first time, to unsolder the battery leads, but I didn't know then, that there was a reset button...) The reset button is located between the micro USB and the Headset connectors on the right upper side of the device, the little hole there, use an insulated papar clamp to press it. In the device manager, you will see the driver popping up and after a short time, shut down. This is normal operation, sometimes it starts reconnecting over and over again, but that's allright.
3. First, you should try to get the preloader back on the system. This is very useful, many devices are bricked by shooting off the preloader. Open up SP Flash Tool, load the scatter file from the unzipped stock rom image for the device. You'll see the used blocks and partitions used by the software in the right pane of the flashtools program. Uncheck all blocks first, then click the checkbox at the 'Preloader', the first entry in the right pane..
4. Now connect your device with the USB cable to the pc. Yes, this comes first. Now press the 'Download' button, the dropdown bar should tell you 'Download Only'. If not, please select this from the dropdown and press download. Now the program waits for the connection, so press the reset button of your device. If all is setup correctly, your device will connect and download will start. First, you'll see a red bar running at the bottom part of the programs's screen, shortly followed by a yellow bar, showing progress of the download. If the download was successfull, you'll be notified accordingly. Disconnect your device and wait 10 seconds, then reconnect it to the pc. If your download was successfull, your phone will be recognised and stay connected, please look in your device manager on your pc, to see connection startup. You'll see the battery charging icon on your device, so it shows, that it is recovered back into it's life.
5. Now it comes to flash the rest of the firmware, so go back to SP Flash Tools, select the scatter file again, check all blocks EXCEPT the preloader and flash it to the device the same way, you've flashed the preloader. Now that you've selected more blocks to flash, you'll see that this takes much more time to download. So please be patient, do not tamper with anything, go ahead, get yourself a coffee or a beer and relax. If everything is okay, flashtools will inform you if the download of the firmware is successfull. If yes, you are good to go, for the first startup of your device.
Disconnect the device from your pc and power it on. If all is right, it will boot up android and you're ready to install and customize it for you.
But sometimes things just don't work this way, what can you do ?
Well, in my case, I've shot my preloader at the first try to flash the stock rom. Yes, I did not obey the rule that I should not tamper with this preloader, so it was checked also. This was a big mistake, after unsuccessfull download, the device did not react any more. The second time (I've bricked it again, because I would like to know, how to restore a bricked file system). So I've formatted all partitions, reinstalled everything and it worked fine. You can do this with the SP Flash Tools also.
I was tired of the 'Factory Recovery Mode', a standard piece of software, which seems to be some sort of rudimentary, so I'd like to install a CWM recovery for that. It would let me install a ZIP Update from the SD card, so it seems more usefull than that rudimentary factory recovery, but how to establish that ?
Searched the web for a long time. Used MTK Droid Tools for that, but this didn't work on the device. It could not create the recovery because of two errors:
- No found kernel GZ
- No found split boot image.
The search for the solution to these both errors resulted in just one thing: There seems not to be a solution for that.
If I can find the time, I will try to solve this but in this moment....
In this case, you'll have just one option left, install Philz Recovery. It brings touch capab8illity also, so it just seems ideal to have that. Besides the fact, that you can use the touch interface, the software brings a ton of usefull options with it, so it is the best choise for your device. I've extracted the ZIP file and dropped all items on my desktop to have a quick access to it.
This can only be done on a routed device, so you'll need to root it before continuing. Not rooting the tablet will result in hanging up the recovery program, so no use. I've rooted the device using kingo root. It runs on my pc and the only things installed on my device are the kingo root super user module and the kingo link module, for connectivity. The latter installations are done by kingo root and your PC, so you'll not have to do this yourself.
Rooting the device will take some time, so be patient. My device is connected as a JTY MT 10 Smartphone, when kingo root recognises it. It can take up to an hour to root. Probably there are other rooting programs out there, which could do the same, but I've tested a few of them, nothing else worked properly. I'll be using kingo root for this device in the future. Be aware, that the rooting with kingo root is session dependable, so after rebooting your device, you'll have to root it again.
You may now run the setup program for philz recovery. It can take more times starting up the program to successfully install the recovery on your device. I had to start the program 5 times, to get it installed completely, so if it is not working the first time, don't panic and start it over again.
The standard recovery image from the stock rom is not the same size as the recovery from philz. The program warns you for getting IMEI lost, so if you don't want this to happen, quit installation here. If you know what you do AND you have a backup of IMEI (NVRAM folders of the device) just go ahead. If installation of the recovery was successfull, you'll be notified by the program running on your pc. Now you can boot your device into recovery, by hitting the apropriate button presented by philz recovery setup program on your pc. To do this on the device itselft, power it off, wait 20 seconds, press the VOL + button and hold this while then pressing the power button. Hold these untill your screen lights up and select 'Recovery' from the menu, use VOL + for selecting, use VOL - to confirm. If the program starts, you'll notice, that it is 'Upside-Down'. That should not bother you, for this little inconvenience you get paid with a superb recovery.
In the next section of this post, I'll cover the backup and restore issues, using MTK Droid Tools, explain how to reinstall an IMEI, how to install a new MAC adress on the device. So stay tuned...
Joshi
Does anyone has custom recovery for Excelvan MT10?
Once you got into android modding, an unrooted phone becomes almost useless.
Now my problem is that I´ve got one.
Couple of days ago my Elephone P9000 arrived from amazon but I can´t connect it to a PC since it says that no device is detected.
Yes, the drivers are installed properly!
I thought that isn´t a problem because there is Kingroot.
Turns out the following rooting apps don´t work for me:
Kingroot (Kingoroot), iRoot, z4root, Framaroot, Towelroot, Oneclickroot, Universal Androot, Root Genius, Baidu
Custom Recovery isn´t installed because, of course, no root.
Now how do I root?
ThisIsMyMaster said:
Once you got into android modding, an unrooted phone becomes almost useless.
Now my problem is that I´ve got one.
Couple of days ago my Elephone P9000 arrived from amazon but I can´t connect it to a PC since it says that no device is detected.
Yes, the drivers are installed properly!
I thought that isn´t a problem because there is Kingroot.
Turns out the following rooting apps don´t work for me:
Kingroot (Kingoroot), iRoot, z4root, Framaroot, Towelroot, Oneclickroot.
Custom Recovery isn´t installed because, of course, no root.
Now how do I root?
Click to expand...
Click to collapse
The first thing you need to accomplish is to get your PC to recognize your phone, rooting from there is going to make life easier, but yes, I know you already know that. If your using windows 10, maybe check this thread out on Elephone Forum:
http://bbs.elephone.hk/forum.php?mod=viewthread&tid=12240&page=1&ordertype=1#pid129322
jotei66 said:
The first thing you need to accomplish is to get your PC to recognize your phone, rooting from there is going to make life easier, but yes, I know you already know that. If your using windows 10, maybe check this thread out on Elephone Forum:
(link removed)]
Click to expand...
Click to collapse
That´s the tutorial that I was going to do but when my phone is shut down, my pc doesn´t detect the device and flash tool neither.:crying:
ThisIsMyMaster said:
That´s the tutorial that I was going to do but when my phone is shut down, my pc doesn´t detect the device and flash tool neither.:crying:
Click to expand...
Click to collapse
Firstly is your PC finding your phone ok with the PC on? If yes.. all good - if no you need to sort this out first.
Then, ensure you have installed the MTK driver on your PC (these are the Media Tek drivers which will find your phone when it is off) instructions here:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Then flashtools should work fine with your phone off.
Just a tip using FlashTools (Im on windows 10 - I dont know if this applies to other windows)
In flashtools, press download first (without phone connected), give it 5 secs and then connect your phone to your PC with the volume up button pressed at the same time. Once you see FlashTools starting to flash your phone, release the volume button. I have to do this all the time in order for my phone to be found on Windows 10.
jotei66 said:
Firstly is your PC finding your phone ok with the PC on? If yes.. all good - if no you need to sort this out first.
Then, ensure you have installed the MTK driver on your PC (these are the Media Tek drivers which will find your phone when it is off) instructions here:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Then flashtools should work fine with your phone off.
Just a tip using FlashTools (Im on windows 10 - I dont know if this applies to other windows)
In flashtools, press download first (without phone connected), give it 5 secs and then connect your phone to your PC with the volume up button pressed at the same time. Once you see FlashTools starting to flash your phone, release the volume button. I have to do this all the time in order for my phone to be found on Windows 10.
Click to expand...
Click to collapse
To start of, I am using Windows 10 as you do.
When I connect my phone when it´s turned on, I get the small icon in the taskbar that allows me to remove the device safely or open devices and printer.
There, my device is put to a section called not specified and it has a small yellow icon.
Only is it called "P9000" which is alright.
Windows explorer acts like no device is connected at all.
When I connect my phone as it is turned off, I still get the notification "USB Device wasn´t recognized." and
windows explorer still doesn´t care as well as the flash tool.
The link you gave me isn´t the one I previously used to install the drivers so I gave it a try.
There are two different ways mentioned in the posts #1 and #4 so I started with the first one.
(Spoiler: Both don´t work for me!)
Everything worked until a step almost at the end where I am told to connect my off-switched phone to the pc.
The tutorial tells me that there should now be a preloader unknown device or something at Device Manager > Ports (COM & LPT) that I would need to proceed further.
I didn´t get that one.
Dead end for me so I went on to the next tutorial in post #4.
In that post I am told to remove a MTK USB Port at Device Manager > Ports (COM & LPT) right after installing the .inf driver files (Yes, I installed the 64 bit version and do have a 64 bit PC).
Ignoring that step didn´t help any of the problems I had before so I got a dead end here, too.
The "Volume-Up-Trick" did help me neither, probably cause of the not working drivers.
ThisIsMyMaster said:
To start of, I am using Windows 10 as you do.
When I connect my phone when it´s turned on, I get the small icon in the taskbar that allows me to remove the device safely or open devices and printer.
There, my device is put to a section called not specified and it has a small yellow icon.
Only is it called "P9000" which is alright.
Windows explorer acts like no device is connected at all.
When I connect my phone as it is turned off, I still get the notification "USB Device wasn´t recognized." and
windows explorer still doesn´t care as well as the flash tool.
The link you gave me isn´t the one I previously used to install the drivers so I gave it a try.
There are two different ways mentioned in the posts #1 and #4 so I started with the first one.
(Spoiler: Both don´t work for me!)
Everything worked until a step almost at the end where I am told to connect my off-switched phone to the pc.
The tutorial tells me that there should now be a preloader unknown device or something at Device Manager > Ports (COM & LPT) that I would need to proceed further.
I didn´t get that one.
Dead end for me so I went on to the next tutorial in post #4.
In that post I am told to remove a MTK USB Port at Device Manager > Ports (COM & LPT) right after installing the .inf driver files (Yes, I installed the 64 bit version and do have a 64 bit PC).
Ignoring that step didn´t help any of the problems I had before so I got a dead end here, too.
The "Volume-Up-Trick" did help me neither, probably cause of the not working drivers.
Click to expand...
Click to collapse
Ok first things first, lets make sure your P9000 is fine with your phone on. You said:
When I connect my phone when it´s turned on, I get the small icon in the taskbar that allows me to remove the device safely or open devices and printer. There, my device is put to a section called not specified and it has a small yellow icon.
Only is it called "P9000" which is alright.
Click to expand...
Click to collapse
(make sure in dev options on your phone USB debugging is ON and USB config is MTP)
So from that you simply need to (In Device Manager) right click > Update Driver Software > Browse My PC for Driver Software > Let me pick from a list of device drivers from my PC > then choose MTP USB Device
Once windows installs this, a box should pop up showing your P9000 internal storage and SD Card (if you have one in phone)
To ensure that your PC is now finding your phone ok, restart PC and plug your phone in - you should be prompted by windows to choose a default action when this device is connected (I choose transfer files or something similar). Then everytime you connect your phone, a box will pop up showing allowing you to access your P9000.
Now onto when your P9000 is switched off... (the important part for flashing etc)
I followed the instructions at post #4 as I believe due to the anniversary update on windows 10 (the January update I believe) .. if you do not have the January update installed on your PC you would use the instructions #1
Don't worry too much if you receive "USB device not recognised" initially, (from what I have understood this is normal with the Anniversary addition of windows 10) it should disappear after few seconds or so. From what I worked out following post #4 you are kinda installing a MTK device (just so you can install the drivers) and then uninstalling that device BUT keeping the drivers installed (its VERY important when you uninstall the device you untick the delete drivers too, otherwise you have essentially deleted the MTK drivers & would have to start from scratch from post #4)
For me, when I connect my p9000 when its off it still shows "USB device not recognised", then after a few seconds this goes away and I dont have any errors under Device Manager > Ports (COM & LPT) & flashtools works fine as long as I press vol up as I connect my phone.
Hope this helps, I had a headache when I tried to install MTK drivers with my windows 10 (Anniversay Update Edition) - good luck, it was kinda trial and error
jotei66 said:
Ok first things first, lets make sure your P9000 is fine with your phone on. You said:
(make sure in dev options on your phone USB debugging is ON and USB config is MTP)
So from that you simply need to (In Device Manager) right click > Update Driver Software > Browse My PC for Driver Software > Let me pick from a list of device drivers from my PC > then choose MTP USB Device
Once windows installs this, a box should pop up showing your P9000 internal storage and SD Card (if you have one in phone)
To ensure that your PC is now finding your phone ok, restart PC and plug your phone in - you should be prompted by windows to choose a default action when this device is connected (I choose transfer files or something similar). Then everytime you connect your phone, a box will pop up showing allowing you to access your P9000.
Now onto when your P9000 is switched off... (the important part for flashing etc)
I followed the instructions at post #4 as I believe due to the anniversary update on windows 10 (the January update I believe) .. if you do not have the January update installed on your PC you would use the instructions #1
Don't worry too much if you receive "USB device not recognised" initially, (from what I have understood this is normal with the Anniversary addition of windows 10) it should disappear after few seconds or so. From what I worked out following post #4 you are kinda installing a MTK device (just so you can install the drivers) and then uninstalling that device BUT keeping the drivers installed (its VERY important when you uninstall the device you untick the delete drivers too, otherwise you have essentially deleted the MTK drivers & would have to start from scratch from post #4)
For me, when I connect my p9000 when its off it still shows "USB device not recognised", then after a few seconds this goes away and I dont have any errors under Device Manager > Ports (COM & LPT) & flashtools works fine as long as I press vol up as I connect my phone.
Hope this helps, I had a headache when I tried to install MTK drivers with my windows 10 (Anniversay Update Edition) - good luck, it was kinda trial and error
Click to expand...
Click to collapse
I am running the Anniversay Update Edition and don´t get an popup window when connecting my phone turned on.
As far is I can tell, a working connection with the device running is more important in the first place.
Now I don´t quite understand your instructions at this point:
jotei66 said:
So from that you simply need to (In Device Manager) right click > Update Driver Software > Browse My PC for Driver Software > Let me pick from a list of device drivers from my PC > then choose MTP USB Device
Click to expand...
Click to collapse
In Device Manager right click, but where?
Blank space? Definetly not.
According to the linked tutorial, I´d have to right click on something like "unknown device" or something similar.
But that doesn´t show up in my list.
In the next section you said:
jotei66 said:
you are kinda installing a MTK device (just so you can install the drivers) and then uninstalling that device BUT keeping the drivers installed
Click to expand...
Click to collapse
I can understand the point but after installing that driver package, there is no MTK device in my device manager that I could uninstall.
I seriously need to thank you for wasting so much time on me:angel:
When you plug your p9000 (while its turned on) into your laptop/pc... in Device Manager, probably under Universal serial Bus Controllers do you see a unknown device, or anything with a question mark / unknown device beside it ? If so, that's where you right click and follow instructions above to get your PC to recognize your handset. At this point just concentrate on getting pc to recognise while its on, then hopefully we can then move to setting up when its off.
I seriously need to thank you for wasting so much time on me
Click to expand...
Click to collapse
lol its all cool
PS: Just to make sure, in device manager, press View from top menu and "show hidden devices".. maybe it could be hidden?
jotei66 said:
When you plug your p9000 (while its turned on) into your laptop/pc... in Device Manager, probably under Universal serial Bus Controllers do you see a unknown device, or anything with a question mark / unknown device beside it ? If so, that's where you right click and follow instructions above to get your PC to recognize your handset. At this point just concentrate on getting pc to recognise while its on, then hopefully we can then move to setting up when its off.
lol its all cool
PS: Just to make sure, in device manager, press View from top menu and "show hidden devices".. maybe it could be hidden?
Click to expand...
Click to collapse
I can´t believe how stupid I am...
jotei66 said:
Just to make sure, in device manager, press View from top menu and "show hidden devices".. maybe it could be hidden?
Click to expand...
Click to collapse
Well, that solved all of my problems...
Almost...
Drivers are fully working for me now so I wanted to flash TWRP with SP Flash Tool to be able to flash the superuser .zip file.
Since drivers work now, flash tool started flashing and gave me the error you can see in the attached screenshot.
Fortunately, my phone isn´t bricked or anything.
Edit: After a couple of reboots of all my devices, I get back to where I was before: USB Device wasn´t recognized and Flash Tool doesn´t do anything.
ThisIsMyMaster said:
I can´t believe how stupid I am...
Well, that solved all of my problems...
Almost...
Drivers are fully working for me now so I wanted to flash TWRP with SP Flash Tool to be able to flash the superuser .zip file.
Since drivers work now, flash tool started flashing and gave me the error you can see in the attached screenshot.
Fortunately, my phone isn´t bricked or anything.
Click to expand...
Click to collapse
All cool & its an easy thing to miss when your not looking for it (or for that matter if you dont know that menu even existed)
That error is a preloading error, I'm assuming your flashing TWRP Recovery and like you I had similar issue - I shared a simple solution here that worked for me here (it should work fine as long as you are on Stock Elephone 2016810 Base onwards so I believe, Elephone changed the preloader or something like that in later ROMS)
So Basically, you download the Stock Elephone 2016810 Base ROM from HERE & unzip
Grab Flash Tools ver v5.1612 (if your not using that version) HERE - https://www.androidfilehost.com/?fid=24591000424940027
Then download TWRP_3.0.2.8.zip HERE & unzip
Copy the the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_2016810 Rom folder.
In Splash Tools, first flash the Elephone_P9000_2016810 Rom open "MT6755_Android_scatter" from _810 file & ensure the recovery section location points to "recovery.img" in the _810 folder also
Once your stock _810 ROM is flashed successfully, you then flash TWRP (with only recovery ticked) and ensure the recovery location points to "recovery_TWRP_3028_P9000" and your TWRP should flash fine. Make sure your using Flash Tools ver v5.1612, that worked fine for me.
There maybe an easier solution someone can point you too, but I know this worked for me no problems - you should now have TWRP recovery on stock _810 ready for you to flash your chosen ROM
jotei66 said:
All cool & its an easy thing to miss when your not looking for it (or for that matter if you dont know that menu even existed)
That error is a preloading error, I'm assuming your flashing TWRP Recovery and like you I had similar issue - I shared a simple solution here that worked for me here (it should work fine as long as you are on Stock Elephone 2016810 Base onwards so I believe, Elephone changed the preloader or something like that in later ROMS)
So Basically, you download the Stock Elephone 2016810 Base ROM from HERE & unzip
Grab Flash Tools ver v5.1612 (if your not using that version) HERE - https://www.androidfilehost.com/?fid=24591000424940027
Then download TWRP_3.0.2.8.zip HERE & unzip
Copy the the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_2016810 Rom folder.
In Splash Tools, first flash the Elephone_P9000_2016810 Rom open "MT6755_Android_scatter" from _810 file & ensure the recovery section location points to "recovery.img" in the _810 folder also
Once your stock _810 ROM is flashed successfully, you then flash TWRP (with only recovery ticked) and ensure the recovery location points to "recovery_TWRP_3028_P9000" and your TWRP should flash fine. Make sure your using Flash Tools ver v5.1612, that worked fine for me.
There maybe an easier solution someone can point you too, but I know this worked for me no problems - you should now have TWRP recovery on stock _810 ready for you to flash your chosen ROM
Click to expand...
Click to collapse
I´m going to try this now.
Do I have to go back to Stock 20160810 if I have 20161107?
Do I have to go back to Stock 20160810 if I have 20161107?
Click to expand...
Click to collapse
I guess if you download the 20161107 ROM it should work, I'm really unsure, its a newer ROM so I guess it should
jotei66 said:
I guess if you download the 20161107 ROM it should work, I'm really unsure, its a newer ROM so I guess it should
Click to expand...
Click to collapse
It didn´t work.
I did all the steps you´ve told me and ended up with the exact same problem I´ve experienced before: USB Device not recognized and SP Flash Tool doesn´t do anything after pressing the download button.
I was going to reinstall the drivers like you told me form post #4 here: https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
That didn´t do anything, I still have the same problem of my pc not recognizing my phone.
At least connecting my phone when it´s running works now.
you have to press and keep vol + when connecting the turned off phone to the computer after clicking download in FlashTools.
Regards
Fran Montero said:
you have to press and keep vol + when connecting the turned off phone to the computer after clicking download in FlashTools.
Regards
Click to expand...
Click to collapse
Tried it, didn´t help
ThisIsMyMaster said:
Tried it, didn´t help
Click to expand...
Click to collapse
MMmmm .. have you tried a different USB port? maybe a different lead if you have one? (I have two leads and I know one doesnt work for me, dunno why)
Also, after pressing download in SplashTools.. count to say 7-10 secs and then press Vol UP and connect your phone.... (I know this sounds bit stupid, but it works for me, if I connect straioght away I get errors too ref driver )
jotei66 said:
MMmmm .. have you tried a different USB port? maybe a different lead if you have one? (I have two leads and I know one doesnt work for me, dunno why)
Also, after pressing download in SplashTools.. count to say 7-10 secs and then press Vol UP and connect your phone.... (I know this sounds bit stupid, but it works for me, if I connect straioght away I get errors too ref driver )
Click to expand...
Click to collapse
No, that doesn´t help either.
I think it has to do something with installing the drivers cause after installing them, in Device Manager no new drivers are displayed except for two Mediatek Preloader USB VCOM Port (COM5) and (COM6).
But those only become visible when I check "show hidden devices".
The tutorial said that some more things should have been installed but I didn´t get any error messages so I don´t understand what shouldn´t have worked.
Sorry Im at a loss really, maybe follow this tutorial my brother followed to reinstall the MTK and try again with all the above steps, good luck
https://www.youtube.com/watch?v=NbJCbdfPlF8
Make sure your PC is in driver signature disable mode when flashing etc btw
jotei66 said:
Sorry Im at a loss really, maybe follow this tutorial my brother followed to reinstall the MTK and try again with all the above steps, good luck
https://www.youtube.com/watch?v=NbJCbdfPlF8
Make sure your PC is in driver signature disable mode when flashing etc btw
Click to expand...
Click to collapse
Didn´t help either.
Current state:
Phone On > Everything working, I get the popup window and data transfer works :good:
Phone Off > USB wasn´t recognized, Flash Tool isn´t working, no recognition in windows explorer, phone is charging, vol+ doesn´t help
MTP and USB Debugging are activated
While installing the drivers I got no error messages and everything looked same as in the tutorial
ThisIsMyMaster said:
Didn´t help either.
Current state:
Phone On > Everything working, I get the popup window and data transfer works :good:
Phone Off > USB wasn´t recognized, Flash Tool isn´t working, no recognition in windows explorer, phone is charging, vol+ doesn´t help
MTP and USB Debugging are activated
While installing the drivers I got no error messages and everything looked same as in the tutorial
Click to expand...
Click to collapse
Good to hear you can atleast use your phone to transfer etc while on
Just curious (although Im sure you have followed the video / other tutorials to the letter) but
(1) did you ensure when following video tut that when uninstalling the legacy device you unticked the driver box to ensure the drivers were actually kept installed?
(2) Check Device Manager, under the Ports (COM & LPT) section and remember you shouldn't have anything referring to a MTK device in there - ie like MTK USB Port (Com 3) ? (If you have it needs uninstalling)
(3) Seems obvious I know but you are connecting your phone and using FlashTools when your Windows Driver Enforcement is disabled? ( Literally restarting with advanced options & choosng Disbale Driver Enforcement) Many users think once you have installed the driver you can use it with Windows Drivers enforcement enabled, but you have to be in disabled mode.
Finally if you doubled checked all of those, then maybe try a different version of FlashTools (worth a try) and also try running FlashTools as Administrator when you open it - good luck