Hi. I need to return my Dell Streak to O2, due to a fault that has developed with the speaker. Ie. when I make calls, I can't hear other people, but they can hear me. Calls work perfectly from speakerphone mode.
I have upgraded to 2.1, and thought that it would be a good idea to return it to a stock rom, before i return it under warrenty.
So, first of all, I copied the stock rom to the SD card, and called it Update.pkg, then tried to "update from Update.pkg" but it fails, saying that the sysem is up to date.
So i followed the thread, about using fastboot and then recover to 1.6 ( http://forum.xda-developers.com/showthread.php?t=752769 )
however, when i run the fastboot (as admin command prompt) it just says <waiting for device> even though the phone is connected to the computer in fastboot mode.
Any Ideas?
Regards, Dave
use fastboot -i 0x413c rest of command
Same Result
Thanks for the reply.
check the drivers (in windows) you may need to manually update them
Download the Dell PC Suite from support.euro.dell DOT com/support/downloads/driverslist.aspx?c=uk&cs=ukdhs1&l=en&s=dhs&ServiceTag=&SystemID=TBLT_STRK&os=ANDGL&osl=en&catid=&impid= and install. Download this folder www DOT mediafire DOT com/?yd21znuyj14 and unzip to the root drive i.e. c:\ and call it something like streak so you can navigate to c:\streak. Open up the new streak folder and find the fastboot application for your operating system and rename it to fastboot (leave the .exe file extension as it is). Put your Streak into Fastboot mode by powering on while holding the camera button. It will show a screen that says ‘Touch Calibration’ and ‘Fastboot’. Tap fastboot. You will now see ‘Wait for USB FastBoot detect....’. Connect your USB. The screen should display ‘FASTBOOT_MODE’. If not then try this. Go to device manager. You should see an errored item called Android 1.0. Right click Android 1.0, select Update Driver Software, select Browse my computer, select Let me pick, select All Hardware, scroll down to Google INC, select Bootloader and click OK.
what to do, if this happens on a mac? Still get only "< waiting for device >" in the terminal. With my N1 it was easier...
Thanks fards! This command worked when I was stuck at 'waiting for device'
Related
Hi
I have got a hero on the cheap currently using an iPhone boot looking to move over.
The hero has a custom rom on it, I would liketo try others. Holding down the home button and powering on just leaves it with the G2 boot screen. Holding down back button and power brings me into fastboot USB. When connected to the mac I am unable to see the device / list it using adb devices. If I boot into the os and connect to the mac not mounting the sdcard I can see the device with adv devices.
I'm trying to install a recovery image, this is proving dificult with not seeing the device in fastboot.
Has anyone any thought/suggestions on to resolve? Or point me in the direction of some threads to read.
Tia
deano
use fastboot devices when in fastboot...
HI,
thanks for the reply, when in fastboot on the device I use fastboot which i have downloaded from the andriod site and put in my "tools" folder when trying to lash a recovery image it just comes back with a prompt saying "waiting for device"
thanks
just to make sure: you turn off the phone, then turn it on again while holding down BACK. this brings you to a screen with a white background and fastboot written somewhere. then you plug in the usb cable and execute "fastboot devices". if it still doesn't recognize your device then you got a problem somewhere, no idea where though. not sure if windows needs drivers or anything for fastboot to work correctly...
Yes that's correct.
Phone is recognize in everything other than when connected by fastboot.
Thanks for your input
Guys, i have a slight problem here. I want to install a custom rom on my dell streak. The guide that i am following is from Benny's blog (http://leemn.wordpress.com/2011/02/...from-eclair-2-1-build-6941-to-stephens-1-5-1/)
What I've done:
1. Installed Android SDK (Updated the given updates, as in the screenshot. SCREENSHOT
2. Installed Dell's Windows Drivers from here (ftp://ftp.dell.com/Handheld/R288920.exe)
3. Installed Dell Mobile Sync
4. Downloaded the Fastboot tool from here (http://download143.mediafire.com/pcxqstv8scfg/yd21znuyj14/1.8.1.7-streak-clockworkrecovery.zip) , Renamed the fastboot-windows.exe to fastboot.exe .
5. Downloaded SteakDroid 1.9.0 and renamed it to Update.zip and copied it to the root of my SD card.
6. Downloaded the current version of the baseband as recomended.
7. Made a folder in C drive named Streak and extracted the clockworkrecovery.zip there. Copied the baseband into the same folder as well.
I believe these steps were all correct.
Now however, i am stuck .
8. After my streak is in the FASTBOOT_MODE , waiting for the usb connection, i connected the USB cable to my computer.
9. It said that a new device Android 1.0 has been found.
10. I choose to choose the drivers by my own, and The only drivers that were available is Android ADB interface and Android Composite ADB interface. If i were to click show compatible hardware, then only the Android ADB interface driver would be shown. SCREENSHOT
11. If i were to choose any 2, the drivers would install fine, and FASTBOOT_MODE would show up in my streak.
12. I entered into the commandline (run > cmd) and went to the C:\streak directory. Once i ran the command, fastboot devices, nothing is listed. When i ran the command fastboot reboot, all it says is waiting for device and that is it. SCREENSHOT
I tried this on a second computer, and its the same thing. I believe i should see the "ANDROID BOOTLOADER INTERFACE" driver, to proceed with the flashing. SCREENSHOT
However, i am not seeing such options on both computers, that are running Windows XP SP3.
What should i do?
It happened to me with my XP machine, no matter what I did, bootloader driver wont show up.
Ended up using a win 7 one with no problem installing the driver.
And "fastboot devices" command doesn't work for me no matter what i tried.
I would suggest you try "fastboot -i 0x413c reboot" w/o the quotes. If your streak reboots, that means fastboot it's working and you can go on with the flashing, e.g.
fastboot -i 0x413c flash recovery recovery.img
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash amss amss.mbn
etc.
"fastboot devices" wasted hours of my life without realizing fastboot is already working....
PS: one get around of NOT having a win 7 machine is to install pdanet program(google it). It will install the necessary drivers to get you started, just test with "fastboot -i 0x413c reboot" to see if your fastboot is working
PPS: NEVER do any erase with fastboot like fastboot -w or any sort, it will brick it... guarantee
asianftw said:
It happened to me with my XP machine, no matter what I did, bootloader driver wont show up.
Ended up using a win 7 one with no problem installing the driver.
And "fastboot devices" command doesn't work for me no matter what i tried.
I would suggest you try "fastboot -i 0x413c reboot" w/o the quotes. If your streak reboots, that means fastboot it's working and you can go on with the flashing, e.g.
fastboot -i 0x413c flash recovery recovery.img
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash amss amss.mbn
etc.
"fastboot devices" wasted hours of my life without realizing fastboot is already working....
PS: one get around of NOT having a win 7 machine is to install pdanet program(google it). It will install the necessary drivers to get you started, just test with "fastboot -i 0x413c reboot" to see if your fastboot is working
PPS: NEVER do any erase with fastboot like fastboot -w or any sort, it will brick it... guarantee
Click to expand...
Click to collapse
I tried installing PDA NET but it still installed with the same ADB drivers.
However, the command "fastboot -i 0x413c reboot" reboots the streak! So i shall try the flash
Edit:
Got everything working as in the steps, right until the update.zip part.
However, i ran into some error.
Here it is:
Steps followed:
Switch off the phone
Boot the phone into recovery mode by holding vol up + vol down + power simultaneously
You will see a black screen with white writing (vol buttons are up/down, camera button is enter/ok)
Select* ”Software upgrade via Update.pkg on SD Card”
You will now be on a black screen with green writing
Select* ”apply sdcard:update.zip”
Scroll* down to “Yes – Install /sdcard/update.zip)
This will load and install the update
Click to expand...
Click to collapse
Mine would say
Fotmatting System
Copying Files...
Creating Symlinks
Creating Some More Symlinks
Last Lot OF Symlinks Being Created
Setting Permissions
Kernel:Installing
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Then it would reboot the device after awhile, and i'll be back to the normal 2.2.2.
This is a screenshot of the error screen: SCREENSHOT
EDIT!! SOLVED MY ISSUE!! ITS FLASHED NOW!!
Quote from someone who guided me on a different forum. Thanks to him!!
1 - u need to install CWM via fastboot
2 - press on 2nd option will bring u to another new menu ...... if it start to install from update , means u failed ..... After installing CWM , DO NOT reboot into your ori 2.2 or else the CWM will get replaced by original recovery . Which means once u install the CWM , key in " -fastboot -0x413c reboot " and hold the 2 volume button while it reboot ..... it will take u to recovery straight after restart
3 - Choose option ( 2 ) which u bring to u to CWM
4 - Select Steven's zip file from there ....option 4 i think , cant remember correctly which is " install zip from sdcard "
Click to expand...
Click to collapse
arvin2212 said:
I tried installing PDA NET but it still installed with the same ADB drivers.
However, the command "fastboot -i 0x413c reboot" reboots the streak! So i shall try the flash
Edit:
Got everything working as in the steps, right until the update.zip part.
However, i ran into some error.
Here it is:
Steps followed:
Mine would say
Fotmatting System
Copying Files...
Creating Symlinks
Creating Some More Symlinks
Last Lot OF Symlinks Being Created
Setting Permissions
Kernel:Installing
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Then it would reboot the device after awhile, and i'll be back to the normal 2.2.2.
This is a screenshot of the error screen: SCREENSHOT
EDIT!! SOLVED MY ISSUE!! ITS FLASHED NOW!!
Quote from someone who guided me on a different forum. Thanks to him!!
Click to expand...
Click to collapse
Glad to hear Clockworkmod works for you!
Clockwork mod working
Yeah, I wasn't able to get the Clockwork mod to work for me, I kept getting a message about "E:can't find MISC:" and it would hang up from there. Would get the same message if I tried to do a nandroid backup also. So I installed Streakmod and my problems were solved. BTW I had to use a Windows XP computer to get my Streak flashed, none of my 3 W7 laptops would act right, pretty sure it was a driver problem but I was able to resolve it on those.
Another question while I am here, anyone know what has to be done to keep the Streak from random reboots????
cdzo72 said:
Yeah, I wasn't able to get the Clockwork mod to work for me, I kept getting a message about "E:can't find MISC:" and it would hang up from there. Would get the same message if I tried to do a nandroid backup also. So I installed Streakmod and my problems were solved. BTW I had to use a Windows XP computer to get my Streak flashed, none of my 3 W7 laptops would act right, pretty sure it was a driver problem but I was able to resolve it on those.
Another question while I am here, anyone know what has to be done to keep the Streak from random reboots????
Click to expand...
Click to collapse
Did you do a full factory reset?
Did you use the clear cache / dalvik cache option from the cwm menu?
I have done all those and have not had any random reboots.
**Just so you know, i've never experienced any random reboots with the streak.
Random reboots
Well I honestly think my problem has more to do with the battery cover than anything else.
Phone wise my streak doesn't lag, doesn't hang up. I can't remember the last time I got some type of error message from having to force close a program, thus taking that into consideration, I would be hard pressed to believe that I have a problem with my installation or maintenance.
I read somewhere about a fix for the battery compartment slide cover, but it's been a week now and I haven't been able to come across it again. Hoping someone else has seen it and can point me there.
cdzo72 said:
Well I honestly think my problem has more to do with the battery cover than anything else.
Phone wise my streak doesn't lag, doesn't hang up. I can't remember the last time I got some type of error message from having to force close a program, thus taking that into consideration, I would be hard pressed to believe that I have a problem with my installation or maintenance.
I read somewhere about a fix for the battery compartment slide cover, but it's been a week now and I haven't been able to come across it again. Hoping someone else has seen it and can point me there.
Click to expand...
Click to collapse
I believe i've read somewhere that the older versions of the streakdroid roms <1.9.1 has the sensors disabled for rebooting once the cover is loose. Try that
Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
trp6senile said:
Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
Click to expand...
Click to collapse
Take out the battery, put it back together, power on the phone while holding down the volume down key til you get the splash screen, that'll boot you to the bootloader...
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
trp6senile said:
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
Click to expand...
Click to collapse
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
acejavelin said:
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
Click to expand...
Click to collapse
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
trp6senile said:
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
Click to expand...
Click to collapse
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: http://www.htc.com/us/support/content.aspx?id=6196 once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
acejavelin said:
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: <link> once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
Click to expand...
Click to collapse
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
trp6senile said:
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
Click to expand...
Click to collapse
You can also use a live Linux CD like Ubuntu and boot that and install the Linux version of ADB, it works fine.
I bricked my opx I was able to bring it to life but the ****ty recovery doesn't let me flash anything so I am stuck no OS and boot loader locked and my computer isn't recognizing the dam thing I have installed SDK tools and google USB drivers but for some reason I am not able to get the Dan thing to connect right when I try via adb sideload it starts then the phone says fail...... Please help I am love this device and brand but I am getting really mad I am about a week in to trying to fix this but no luck I am using windows 10 also
We can try to unlock the bootloader as it is now, but that doesn't usually work unless you checked "OEM Bootloader Unlock" in the system settings before the device was bricked. Hindsight is 20/20 but as a word of advice for the future, never ever mess with a device unless you know the bootloader is unlocked or have made it possible to unlock it later without the OS. It also doesn't void the warranty on OnePlus devices to do so.
So first things first, the recovery will normally only flash the stock ROM as provided by OnePlus. You can download that file from here: http://downloads.oneplus.net/2016-04-02/opx/OnePlus_X_OxygenOS_2.2.1/. For future reference, when the bootloader on a device is locked the bootloader will not boot any software that isn't complete stock. If you try and change the OS or Recovery and it's not stock, the bootloader will not load it. This goes for any Android device.
If ADB sideload is working for you but hasn't been installing on the device (as-in, it sends the file but the device fails to install it) then you should be able to just sideload the zip file. It'll be slow though since it's about 780megs. If it doesn't send it then you can try using the ADB "push" command which is like copy and paste. You "push" the file from your computer to a folder on the device (you can see what folders are available using "adb shell" and then navigating with CD "change directory" and LS "list". If you can't find the sdcard you may have to mount it). Once again, it'll push slowly but once it does you should be able to install it from the internal memory.
If that works and it boots, go to Settings -> About Phone and tap the Build Number until it says you've enabled developer settings. Go to Settings -> Development and turn on "OEM Unlocking". Power the phone down. Hold the Power key and Volume Down until it shows the OnePlus logo and "Fastboot". I believe if you have the Android SDK you have the Fastboot program (it's commandline like ADB). Open CMD or Powershell and as long as it's the only device plugged into the computer you should be able to simply type "Fastboot oem unlock" and it will unlock the bootloader. Once again, it doesn't void your warranty.
Dear Firmware Gurus,
I received a gift from someone, the Huawei Mediapad 10 Link, and the Android version 4.1 + old firmware was making the tablet very slow. So I decided to:
1. Root device with framaroot --> Success.
2. Find and download newer official ROM for the table --> Success.
3. Install Rashr + install TWRP recovery through it --> FAIL And this is the moment I really regret. I didn't imagine that this application will give me boot loop forever.
Anyway, now I have bootloop and I can only access Fastboot by pressing Volume+ & Power Button. But when I connect the tablet on Windows OR linux, while on Fastboot screen, the adb + fastboot does not see any listed devices. Please help me with all kinds of instructions how I can see the device listed in adb and reset or upgrade the firmware from there. I am hopeless, and sad, and willing to donate with PayPal as appreciation if you can help me.
Hi , all you have here just follow carefully
http://www.teamandroid.com/2012/08/04/huawei-mediapad-10-fhd-fastboot-bootloader-mode/
Good Luck
Teddy Lo said:
Hi , all you have here just follow carefully
http://www.teamandroid.com/2012/08/04/huawei-mediapad-10-fhd-fastboot-bootloader-mode/
Good Luck
Click to expand...
Click to collapse
Thank you a lot. I have solved the problem and upgraded the firmware at the same time following the instructions in the link you provided but I also needed to do some things not in that link (because adb shell doesn't work I had to upgrade firmware through fastboot only).
This tutorial is made for all those who used the SHIIIII**** application called Rashrr that soft-bricks thousands of phones every day trying to install TWRP recovery. I've seen many people complaining about this but finally there is a way out for this device at least.
So here is the conclusion for everyone else in trouble:
1. Go to this link and follow instructions until you can install Google SDK studio + Google USB Drivers.
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/
2. Connect your device to the charger, click Power button + Vol+ to Enter into fastboot mode as in this link.
3. Connect the USB cable to your Windows computer and then go to Device Manager, you will most probably find your device as Unknown Device. Click on it and Update Driver. Pick this driver from a a list: Android Composite ADB Interface..
4. Then go to the SDK Platform Tools folder where the adb and fastboot commands are:
C:\Users\<Your_User_Account_Name>\AppData\Local\Android\sdk\platform-tools
Copy all the contents of this file inside it.
This archive includes the most updated firmware images of Huawei Mediapad 10 Link s10-wa (WiFi Only Version).
5. Run the cmd as Administrator and go to the same path where you put the files run the command "fastboot devices" and something like this should appear to indicate your device is being properly connected:
?????? fastboot
or
0x12d1 fastboot
If this line appeared it means that your device is being seen by fastboot and it will comply to your commands.
6. Run upgrade.bat while the device is connected in fastboot mode. Do not interrupt while your system is being upgraded.
7. Reboot device and enjoy! Don't forget that first boot takes some time seeing Huawei logo. Give it time!
My Huawei Mediapad 10 link+ start black screen after reboot..thi happens after I flashing the device why???
Did not worked for me
iamarto said:
Thank you a lot. I have solved the problem and upgraded the firmware at the same time following the instructions in the link you provided but I also needed to do some things not in that link (because adb shell doesn't work I had to upgrade firmware through fastboot only).
This tutorial is made for all those who used the SHIIIII**** application called Rashrr that soft-bricks thousands of phones every day trying to install TWRP recovery. I've seen many people complaining about this but finally there is a way out for this device at least.
So here is the conclusion for everyone else in trouble:
1. Go to this link and follow instructions until you can install Google SDK studio + Google USB Drivers.
2. Connect your device to the charger, click Power button + Vol+ to Enter into fastboot mode as in this
3. Connect the USB cable to your Windows computer and then go to Device Manager, you will most probably find your device as Unknown Device. Click on it and Update Driver. Pick this driver from a a list: Android Composite ADB Interface..
4. Then go to the SDK Platform Tools folder where the adb and fastboot commands are:
C:\Users\<Your_User_Account_Name>\AppData\Local\Android\sdk\platform-tools
Copy all the contents of this inside it.
This archive includes the most updated firmware images of Huawei Mediapad 10 Link s10-wa (WiFi Only Version).
5. Run the cmd as Administrator and go to the same path where you put the files run the command "fastboot devices" and something like this should appear to indicate your device is being properly connected:
?????? fastboot
or
0x12d1 fastboot
If this line appeared it means that your device is being seen by fastboot and it will comply to your commands.
6. Run upgrade.bat while the device is connected in fastboot mode. Do not interrupt while your system is being upgraded.
7. Reboot device and enjoy! Don't forget that first boot takes some time seeing Huawei logo. Give it time!
Click to expand...
Click to collapse
When I run the Upgrade.bat it says fastboot: unknown option -- i, and when I check the fastboot options for this i key did not found it.. Any help on this?
iamarto said:
Thank you a lot. I have solved the problem and upgraded the firmware at the same time following the instructions in the link you provided but I also needed to do some things not in that link (because adb shell doesn't work I had to upgrade firmware through fastboot only).
This tutorial is made for all those who used the SHIIIII**** application called Rashrr that soft-bricks thousands of phones every day trying to install TWRP recovery. I've seen many people complaining about this but finally there is a way out for this device at least.
So here is the conclusion for everyone else in trouble:
1. Go to this link and follow instructions until you can install Google SDK studio + Google USB Drivers.
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/
2. Connect your device to the charger, click Power button + Vol+ to Enter into fastboot mode as in this link.
3. Connect the USB cable to your Windows computer and then go to Device Manager, you will most probably find your device as Unknown Device. Click on it and Update Driver. Pick this driver from a a list: Android Composite ADB Interface..
4. Then go to the SDK Platform Tools folder where the adb and fastboot commands are:
C:\Users\<Your_User_Account_Name>\AppData\Local\Android\sdk\platform-tools
Copy all the contents of this file inside it.
This archive includes the most updated firmware images of Huawei Mediapad 10 Link s10-wa (WiFi Only Version).
5. Run the cmd as Administrator and go to the same path where you put the files run the command "fastboot devices" and something like this should appear to indicate your device is being properly connected:
?????? fastboot
or
0x12d1 fastboot
If this line appeared it means that your device is being seen by fastboot and it will comply to your commands.
6. Run upgrade.bat while the device is connected in fastboot mode. Do not interrupt while your system is being upgraded.
7. Reboot device and enjoy! Don't forget that first boot takes some time seeing Huawei logo. Give it time!
Click to expand...
Click to collapse
hey bro, your important files are down, please reupload them or make a hard brink post of this tablet. I would thank you from the bottom of my heart
Please reup
iamarto said:
Thank you a lot. I have solved the problem and upgraded the firmware at the same time following the instructions in the link you provided but I also needed to do some things not in that link (because adb shell doesn't work I had to upgrade firmware through fastboot only).
This tutorial is made for all those who used the SHIIIII**** application called Rashrr that soft-bricks thousands of phones every day trying to install TWRP recovery. I've seen many people complaining about this but finally there is a way out for this device at least.
So here is the conclusion for everyone else in trouble:
1. Go to this link and follow instructions until you can install Google SDK studio + Google USB Drivers.
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/
2. Connect your device to the charger, click Power button + Vol+ to Enter into fastboot mode as in this link.
3. Connect the USB cable to your Windows computer and then go to Device Manager, you will most probably find your device as Unknown Device. Click on it and Update Driver. Pick this driver from a a list: Android Composite ADB Interface..
4. Then go to the SDK Platform Tools folder where the adb and fastboot commands are:
C:\Users\<Your_User_Account_Name>\AppData\Local\Android\sdk\platform-tools
Copy all the contents of this file inside it.
This archive includes the most updated firmware images of Huawei Mediapad 10 Link s10-wa (WiFi Only Version).
5. Run the cmd as Administrator and go to the same path where you put the files run the command "fastboot devices" and something like this should appear to indicate your device is being properly connected:
?????? fastboot
or
0x12d1 fastboot
If this line appeared it means that your device is being seen by fastboot and it will comply to your commands.
6. Run upgrade.bat while the device is connected in fastboot mode. Do not interrupt while your system is being upgraded.
7. Reboot device and enjoy! Don't forget that first boot takes some time seeing Huawei logo. Give it time!
Click to expand...
Click to collapse
Please reupload yours files to make my tablet work :c
ahmed.elabd said:
Did not worked for me
When I run the Upgrade.bat it says fastboot: unknown option -- i, and when I check the fastboot options for this i key did not found it.. Any help on this?
Click to expand...
Click to collapse
you have the files bro?