Related
The usual DISCLAIMER: Use at your own risk!
Fastboot mode usually comes up if something went wrong when trying to flash a recovery image, for example when flashing AmonRa recovery or ClockWorkMod. It happened to me several times so I tried to learn to revive it without reflashing the original firmware. Note: This tutorial works only if recovery is the only one broken. (If the ROM itself is broken, then that's a subject for another tut.) In this case, the most logical thing to do is just reflash the recovery image. So how do you do it in fastboot mode? Here's how:
Symptom
You tried flashing a custom recovery like ClockWorkMod or Thunderg, or you flashed an incorrect ROM, and when you rebooted, it showed this screen:
Code:
fastboot mode started
udc_start()
and the phone stays there. When you plugin the phone to your computer's USB, it is detected and the screen has this display:
Code:
fastboot mode started
udc.start()
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
You will need
1) Your PC and your USB cable for the phone
2) USB drivers for your phone (use B2C from LG).
3) Android SDK (download from here)
4) Java, required to run the SDK (but right now I am not sure if this is required to run fastboot!)
5) ClockWorkMod or AmonRa Recovery.
Here's what to do
1) Assuming phone is turned on in fastboot mode, plug it in to the USB of your PC. You will know that it is detected if you see the the lines "suspend", "reset" and whatnot on the phone's screen.
2) Extract the recovery image from the zipfile downloaded from step#5 above (e.g. LGp500-recovery-v12.img). Place the image file in the same folder where fastboot.exe is (usually in the tools\ folder in the SDK). For your convenience, rename the img file as recovery.img
3) Fire up your command prompt and cd to the directory where fastboot.exe is located. Then type the following command:
Code:
fastboot erase recovery
Once you get the confirmation that it was successful, type this:
Code:
fastboot flash recovery recovery.img
Once you get the success confirmation, reboot the phone, or you can also type (optional):
Code:
fastboot reboot
The phone will reboot itself, and with any luck you should be able to go back to your same old Android bootscreen. Note that no settings were modified here, so this is extremely useful for those who do not want a clean slate after a fastboot nightmare.
Also, note that if this is successful, you can now boot to recovery with the usual button-combos, thus enabling you to flash ROMs and other recovery zips.
Note: On some SDK versions, fastboot may not be included. For your convenience, I have attached the fastboot binary I got from my downloaded SDK. I have also attached AdbWinApi.dll which some user reported is missing in the SDK. Place the DLL in the same folder where fastboot.exe is located.
Questions, just drop me a line here
thanks dude, its very usefull
Nice tutorial for newbies like me, thanks...
Sent from my LG-P500 using XDA Premium App
We already have a tut like this.
@arvinoids
Good tutorial, but you forgot to say that LG USB drivers are needed and that fastboot.exe must be downloaded before (it's no more included in android SDK)
thanks man
d3s3rt_eagle said:
@arvinoids
Good tutorial, but you forgot to say that LG USB drivers are needed and that fastboot.exe must be downloaded before (it's no more included in android SDK)
thanks man
Click to expand...
Click to collapse
You are right! I should add that here. Also, I got the latest SDK to verify and found fastboot.exe under the "tools" folder. Can tell me which SDK version you downloaded?
Usefull, thank you
Sent from my LG-P500 using XDA Premium App
Kudos to arvinoids.
This will be of great help in times of need.
Sent from my LG-P500 using Tapatalk
arvinoids said:
You are right! I should add that here. Also, I got the latest SDK to verify and found fastboot.exe under the "tools" folder. Can tell me which SDK version you downloaded?
Click to expand...
Click to collapse
I have SDK r10 and cannot found fastboot under tools
So i had to download it from htc's website.
d3s3rt_eagle said:
I have SDK r10 and cannot found fastboot under tools
So i had to download it from htc's website.
Click to expand...
Click to collapse
Wow, that's strange. I have r11 and it is included there. For your convenience, I have attached the fastboot.exe from r11 on the first post. Thanks for trying this out.
i have a question... if we don't see the fastboot line on our breaked phone and we see just stuck at LG Logo and the Recovery is broken too, what we can do?! how we can enter in fastboot mode in this situation?
hey
I run the CMD
executed cd command but the next command
"fastboot erase recovery"
gives the following error ( see the image)
Please help
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
DJoptimus-One said:
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
Click to expand...
Click to collapse
Did rom manager messed up your phone?
Sent from my LG-P500 using Tapatalk
lekhwani said:
Did rom manager messed up your phone?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Yes. For the first time.
DJoptimus-One said:
Yes. For the first time.
Click to expand...
Click to collapse
How is your phone now?
Sent from my LG-P500 using Tapatalk
lekhwani said:
How is your phone now?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Revived now
DJoptimus-One said:
Revived now
Click to expand...
Click to collapse
Good to hear that. I think this is your 2nd or 3rd day and you came across worst o1 modding scenario and overcame it. Kudos to you.
Sent from my LG-P500 using Tapatalk
AdbWinApi.dll is included in platform-tools
DJoptimus-One said:
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
Click to expand...
Click to collapse
Hi. Sorry I was away for the weekend and just got back. Thanks for reporting this. I just did a search on my desktop and found out that AdbWinApi.dll is included in the platform-tools package. I will add the instructions to download the package from the SDK. I'm glad you were able to revive your phone. Thanks again!
pymebrahimi said:
i have a question... if we don't see the fastboot line on our breaked phone and we see just stuck at LG Logo and the Recovery is broken too, what we can do?! how we can enter in fastboot mode in this situation?
Click to expand...
Click to collapse
I'm afraid your issue may not be a subject for this tutorial. Fastboot mode is activated when the phone's recovery image is broken. May I know how you are sure that the recovery is actually broken?
Ok, So basically I accidentally formatted my entire phone while trying to flash SlimKat... Noobish, I know, lol. My question is: If I'm still able to enter recovery (TWRP) would I be able to flash a rom still or should I revert to stock 4.4.2?
vI Ragnarok Iv said:
Ok, So basically I accidentally formatted my entire phone while trying to flash SlimKat... Noobish, I know, lol. My question is: If I'm still able to enter recovery (TWRP) would I be able to flash a rom still or should I revert to stock 4.4.2?
Click to expand...
Click to collapse
if you can still enter recovery, you can adb push a rom/gapps to your phone and flash tbem.
simms22 said:
if you can still enter recovery, you can adb push a rom/gapps to your phone and flash tbem.
Click to expand...
Click to collapse
Ok, cool. Would you mind elaborating a bit, I'm not too familiar with using console commands to flash. Also, thanks for the help!!
vI Ragnarok Iv said:
Ok, cool. Would you mind elaborating a bit, I'm not too familiar with using console commands to flash. Also, thanks for the help!!
Click to expand...
Click to collapse
Please look at this thread, and read it thoroughly.
-Download ROM and Gapps, transfer it to your ADB folder and rename it to something easy (Eg : Rom.zip and Gapps.zip).
-Open CMD/Terminal, navigate to your ADB folder.
-Boot into recovery on your phone and plug in your phone, find something called ADB Sideload. It's under Advance in TWRP if I'm not mistaken.
-Type in "adb sideload *.zip" . Replace * with your zip name you have renamed earlier.
-Your phone should be flashing the zip. Simply reboot and you should be perfectly fine.
exb0 said:
Please look at this thread, and read it thoroughly.
-Download ROM and Gapps, transfer it to your ADB folder and rename it to something easy (Eg : Rom.zip and Gapps.zip).
-Open CMD/Terminal, navigate to your ADB folder.
-Boot into recovery on your phone and plug in your phone, find something called ADB Sideload. It's under Advance in TWRP if I'm not mistaken.
-Type in "adb sideload *.zip" . Replace * with your zip name you have renamed earlier.
-Your phone should be flashing the zip. Simply reboot and you should be perfectly fine.
Click to expand...
Click to collapse
Thank you, sir. Couldn't get adb sideload to work so I just flashed the factory image of 4.4.2. No big deal, I'll just have to Re-root. :/
vI Ragnarok Iv said:
Thank you, sir. Couldn't get adb sideload to work so I just flashed the factory image of 4.4.2. No big deal, I'll just have to Re-root. :/
Click to expand...
Click to collapse
Oh, that was probably a driver issue. No worries, you can always get into android, transfer the custom rom into your SD card, boot into recovery, wipe and flash if you want to try out a custom rom.
Hi All.
Hopefully someone is able to help me. I'll try to give as much information as I can.
I have followed the following guide to root my nexus 5.
I have rooted it successfully last month.
However, I have accidentally installed a OTA update from google this week (Android 4.4.3).
Just a while earlier, I have decided to flash a custom rom.
So, as usual, I reboot my phone into recovery.
However, the recovery shows the android with a red triangle, stating "no command".
I have read the forums and read that this is actually not an error but it is the default recovery for android. (Edit: Ok. Maybe its not the default recovery. Anyone able to give me advice on this?)
I guess that my recovery was returned to the stock recovery after the OTA update.
So I tried to flash CWM recovery using ROM manager, but it states "An error occured while flashing your recovery".
I decided to restart my phone and to try it again, now it stucks at 100% on ROM Manager.
I have also tried to flash recovery.img using fastboot. However, it didn't work too.
It returns with an error: "cannot open recovery.img"
May I know if anyone can help me with this problem?
More info on the current status of my phone:
Bootloader unlocked. (Checked by trying to unlock it again. System states that process has failed as it is already unlocked)
ADB Device: Detect-able.
Fastboot Device: Detect-able.
It is indeed the stock recovery. OTA returned it. It also removed root so rom manager won't work, but you shouldn't use rom manager anyway.
You'll need to download a recovery and flash it using fastboot .
Please describe the exact steps you took to get the fastboot error. Screenshot of cmd would be very helpful too please
Sent from my Nexus 5 using Tapatalk
rootSU said:
It is indeed the stock recovery. OTA returned it. It also removed root so rom manager won't work, but you shouldn't use rom manager anyway.
You'll need to download a recovery and flash it using fastboot .
Please describe the exact steps you took to get the fastboot error.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What I did is to check if the boot loader is unlocked.
And yes. It is unlocked.
So I carried onto checking if fastboot detects my devices by doing "fastboot devices". And my nexus5 gets detected.
Then I moved on to trying to flash recovery using " fastboot flash recovery recovery.img ".
But the error appears at this point. And I'm stuck.
Is this sufficient?
Do note that I did change the file name to recovery and not recovery.img as most files do not include the file type in the file name.
Try flashing the recovery using dd (You need root)
Boot the phone normally and push the recovery.img using adb and flash it:
Code:
adb push *Path to recovery.img* /data/media/0/
adb shell
# dd if=/data/media/0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I hope this helps.
You would be better served setting windows not to hide known file types to be honest.
A screenshot of your fastboot flash attempt and error would be most useful please
Sent from my Nexus 5 using Tapatalk
---------- Post added at 05:40 PM ---------- Previous post was at 05:28 PM ----------
chblg said:
Try flashing the recovery using dd (You need root)
Boot the phone normally and push the recovery.img using adb and flash it:
Code:
adb push *Path to recovery.img* /data/media/0/
adb shell
# dd if=/data/media/0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I hope this helps.
Click to expand...
Click to collapse
He hasn't got root. Fastboot is his only option
Sent from my Nexus 5 using Tapatalk
Well FWIW for anyone else reading, my assumption was going to be that the OP didn't put the full path to the recovery OR didn't put the recovery in the location the cmd prompt was running from.
Would have been nice to have seen this through to conclusion, but I cannot monitor forever so I'm unsubscribing due to lack of replies.
eg:
Code:
c:\Users\Administrator>fastboot flash recovery recovery.img
If there is no path to recovery image as above, then the asumption to cmd is that the recover image is in c:\users\administrator (Which it probably isnt)
If it is on the administrators desktop you would:
Code:
c:\Users\Administrator>fastboot flash recovery c:\users\Administrator\Desktop\recovery.img
Nukyi said:
Hi All.
Hopefully someone is able to help me. I'll try to give as much information as I can.
I have followed the following guide to root my nexus 5.
I have rooted it successfully last month.
However, I have accidentally installed a OTA update from google this week (Android 4.4.3).
Just a while earlier, I have decided to flash a custom rom.
So, as usual, I reboot my phone into recovery.
However, the recovery shows the android with a red triangle, stating "no command".
I have read the forums and read that this is actually not an error but it is the default recovery for android. (Edit: Ok. Maybe its not the default recovery. Anyone able to give me advice on this?)
I guess that my recovery was returned to the stock recovery after the OTA update.
So I tried to flash CWM recovery using ROM manager, but it states "An error occured while flashing your recovery".
I decided to restart my phone and to try it again, now it stucks at 100% on ROM Manager.
I have also tried to flash recovery.img using fastboot. However, it didn't work too.
It returns with an error: "cannot open recovery.img"
May I know if anyone can help me with this problem?
More info on the current status of my phone:
Bootloader unlocked. (Checked by trying to unlock it again. System states that process has failed as it is already unlocked)
ADB Device: Detect-able.
Fastboot Device: Detect-able.
Click to expand...
Click to collapse
rootSU said:
Well FWIW for anyone else reading, my assumption was going to be that the OP didn't put the full path to the recovery OR didn't put the recovery in the location the cmd prompt was running from.
Would have been nice to have seen this through to conclusion, but I cannot monitor forever so I'm unsubscribing due to lack of replies.
eg:
Code:
c:\Users\Administrator>fastboot flash recovery recovery.img
If there is no path to recovery image as above, then the asumption to cmd is that the recover image is in c:\users\administrator (Which it probably isnt)
If it is on the administrators desktop you would:
Code:
c:\Users\Administrator>fastboot flash recovery c:\users\Administrator\Desktop\recovery.img
Click to expand...
Click to collapse
Hi. Sorry for late reply. Was at work. I'll try out the full path. What I was told is to just put the recovery IMG into the same folder as fastboot and it should do the trick. Will post screenshots after trying out.
Nukyi said:
Hi. Sorry for late reply. Was at work. I'll try out the full path. What I was told is to just put the recovery IMG into the same folder as fastboot and it should do the trick. Will post screenshots after trying out.
Click to expand...
Click to collapse
Hi All,
Here's the screenshot of my cmd.
Please kindly assist and advise on what should I do.
Thank you.
Nukyi said:
Hi All,
Here's the screenshot of my cmd.
Please kindly assist and advise on what should I do.
Thank you.
Click to expand...
Click to collapse
Ok thanks.
Did you turn off "Hide known file types"? can you screenshot in Windows explorer, the location of the recovery image with hide turned off and in "details" view please?
rootSU said:
Ok thanks.
Did you turn off "Hide known file types"? can you screenshot in Windows explorer, the location of the recovery image with hide turned off and in "details" view please?
Click to expand...
Click to collapse
Yes. I did. Here are the images.
I'm using windows8. So it may look a little different.
Nukyi said:
Yes. I did. Here are the images.
I'm using windows8. So it may look a little different.
Click to expand...
Click to collapse
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
rootSU said:
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
Click to expand...
Click to collapse
Alright. I'll do it and get back to you shortly.
Thank you.
Really hope this fixes the problem.
rootSU said:
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
Click to expand...
Click to collapse
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Did you check if the MD5 of the recovery file is correct? (to rule out a bad download)
jj14 said:
Did you check if the MD5 of the recovery file is correct? (to rule out a bad download)
Click to expand...
Click to collapse
Re-downloaded it many times. Checked all of the md5.
Downloaded not only CWM recovery. But also other custom recovery.
Nukyi said:
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Click to expand...
Click to collapse
Now try and run cmd as an administrator if you are not doing
Nukyi said:
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Click to expand...
Click to collapse
no. the recovery.img is not in c:\users\username\
put that file there, then retry your command
OR
fastboot flash recovery c:\entire\path\to\recovery.img
Nukyi said:
Re-downloaded it many times. Checked all of the md5.
Downloaded not only CWM recovery. But also other custom recovery.
Click to expand...
Click to collapse
are you sure you downloaded the image and not the zip??
samersh72 said:
are you sure you downloaded the image and not the zip??
Click to expand...
Click to collapse
Pretty sure it is the image. Downloaded from the website itself. They only comes in .img and not in zip.
Nukyi said:
Pretty sure it is the image. Downloaded from the website itself. They only comes in .img and not in zip.
Click to expand...
Click to collapse
Ah. It just worked suddenly. No idea why. But I guess @rootSU 's suggestion works well.
And maybe also @Zepius 's suggestion.
Here's what I did to help others who have the same problem.
I did what rootSU asked me to do (changing the "path" part).
Then took Zepius suggestion and duplicated the recovery img in a few folders (the original folder i'm using, on desktop, on C drive root folder)
hi all
trying to flash manually. have read guides with no success.
have tried renaming the extracted file, saving to sd card, tried flashing the zip in twrp and still no luck.
question - does anyone know the commands to flash the BLOB file?
i found this article BUT want to know if i should be using the same commands.
http://www.androidauthority.com/eee-pad-transformer-prime-ics-9-4-2-13-us-firmware-56714/
Copy the “blob” file into the root of your tablet’s removable microSD card.
Open the Android Terminal Emulator app on your tablet.
In the Terminal Emulator screen, type “su” (without the quotation marks) and press Enter. This will allow root access to Terminal Emulator.
Type the command “dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4” (again, without the quotation marks) and press Enter. The command will take about 5 to 20 minutes to finish.
Reboot your device when the following is displayed in the app:
1068769+1 records in
1068769+1 records out
547210197 bytes transferred in 153.991 secs (3553520 bytes/sec)
As soon as the tablet is rebooted, the update process will automatically kick in.
thanks
azreal8 said:
hi all
trying to flash manually. have read guides with no success.
have tried renaming the extracted file, saving to sd card, tried flashing the zip in twrp and still no luck.
question - does anyone know the commands to flash the BLOB file?
i found this article BUT want to know if i should be using the same commands.
http://www.androidauthority.com/eee-pad-transformer-prime-ics-9-4-2-13-us-firmware-56714/
thanks
Click to expand...
Click to collapse
What kind of tablet are u talking about in your post ?
Thx Josh
hi josh..
its a tf700t.
also my micro SD slot is dead so obviously the command would be different as i'd be using my SD card slot on my dock.
azreal8 said:
hi josh..
its a tf700t.
also my micro SD slot is dead so obviously the command would be different as i'd be using my SD card slot on my dock.
Click to expand...
Click to collapse
Is your bootloader unlocked, with the asus unlock tool ?
And the tablet does boot into android ?
lj50036 said:
Is your bootloader unlocked, with the asus unlock tool ?
And the tablet does boot into android ?
Click to expand...
Click to collapse
yes it's unlocked and i'm running cromi-x 5.4 with hunds extreme tweaks kernel.
i want to flash to the stock firmware (.10) as i'll
1) be bringing it back to asus for a repair job - defective micro sd slot
2) want to flash roms which say i need .10 version bootloader.
i've looked at the manually flashing guides my tf doesnt detect nor does twrp flash it when i try to install.
azreal8 said:
yes it's unlocked and i'm running cromi-x 5.4 with hunds extreme tweaks kernel.
i want to flash to the stock firmware (.10) as i'll
1) be bringing it back to asus for a repair job - defective micro sd slot
2) want to flash roms which say i need .10 version bootloader.
i've looked at the manually flashing guides my tf doesnt detect nor does twrp flash it when i try to install.
Click to expand...
Click to collapse
Ok no worries let see if we can find a solution ..
What we will need
PC with working fastboot & adb
Stock blob from Asus website
That is about it, let me know if you have these things..
Thx Josh
lj50036 said:
Ok no worries let see if we can find a solution ..
What we will need
PC with working fastbot & adb
Stock blob from Asus website
That is about it, let me know if you have these things..
Thx Josh
Click to expand...
Click to collapse
thx..i have fastboot on my tf and the stock asus blob from their site
azreal8 said:
thx..i have fastboot on my tf and the stock asus blob from their site
Click to expand...
Click to collapse
We need fastboot on your PC also ..
I assume that you are running a windows PC
Head over here and set it up
http://forum.xda-developers.com/showthread.php?t=2588979
Thx Josh
lj50036 said:
We need fastboot on your PC also ..
I assume that you are running a windows PC
Head over here and set it up
http://forum.xda-developers.com/showthread.php?t=2588979
Thx Josh
Click to expand...
Click to collapse
yes win 8.1.
i installed fastboot on my pc to push thru twrp so i think i'm good to go.
azreal8 said:
yes win 8.1.
i installed fastboot on my pc to push thru twrp so i think i'm good to go.
Click to expand...
Click to collapse
Ok well make sure the blob file is with the fastboot.exe
plug the tab into the PC open CMD window as admin and run these command
Code:
fastboot devices
What is the output of this command ?
Thx Josh
lj50036 said:
Ok well make sure the blob file is with the fastboot.exe
plug the tab into the PC open CMD window as admin and run these command
Code:
fastboot devices
What is the output of this command ?
Thx Josh
Click to expand...
Click to collapse
sorry im back.
when i type "fastboot devices" i get:
015d3fb64d381a0d fastboot
azreal8 said:
sorry im back.
when i type "fastboot devices" i get:
015d3fb64d381a0d fastboot
Click to expand...
Click to collapse
Is the blob in that same folder with the fastbot.exe ?
Thx Josh
lj50036 said:
Is the blob in that same folder with the fastbot.exe ?
Thx Josh
Click to expand...
Click to collapse
yes but it's just named "blob" and was directly extracted from the asus file. i haven't extracted the meta folder from the asus file. do i need to?
azreal8 said:
yes but it's just named "blob" and was directly extracted from the asus file. i haven't extracted the meta folder from the asus file. do i need to?
Click to expand...
Click to collapse
No you will not need that just the blob ...
So from CMD window opened as admin run this command...
Code:
fastboot -i 0x0b05 flash system blob
Let it do its thing ....
Once it comes back to command prompt type
Code:
fastboot reboot
Let it boot into new rom with new bootloader and such ..
Thx Josh
lj50036 said:
No you will not need that just the blob ...
So from CMD window opened as admin run this command...
Code:
fastboot -i 0x0b05 flash system blob
Let it do its thing ....
Once it comes back to command prompt type
Code:
fastboot reboot
Let it boot into new rom with new bootloader and such ..
Thx Josh
Click to expand...
Click to collapse
thx josh! i followed your instructions and the TF went thru an updating process before booting to the home screen.
i checked the settings and the build says:
"J0P40D.WW_epad-10.6.1.14.10-20130801" so i assume thats all correct now?
QN - do you know where i can get the stock kernel? as i'll be returning it for a repair under warranty i assume i need to restore this too?
azreal8 said:
thx josh! i followed your instructions and the TF went thru an updating process before booting to the home screen.
i checked the settings and the build says:
"J0P40D.WW_epad-10.6.1.14.11-20130801" so i assume thats all correct now?
QN - do you know where i can get the stock kernel? as i'll be returning it for a repair under warranty i assume i need to restore this too?
Click to expand...
Click to collapse
That is the stock everything on there after the blob flash ...
it should end in 14.10 ....
Thx Josh
lj50036 said:
That is the stock everything on there after the blob flash ...
it should end in 14.10 ....
Thx Josh
Click to expand...
Click to collapse
awesome. was a typo. thanks so much for your help and quick response.
you're a champion!!!!
azreal8 said:
awesome. was a typo. thanks so much for your help and quick response.
you're a champion!!!!
Click to expand...
Click to collapse
Its why we are here .....
No problem can you add "SOLVED" to the thread title .... :good:
Thx Josh
lj50036 said:
Its why we are here .....
No problem can you add "SOLVED" to the thread title .... :good:
Thx Josh
Click to expand...
Click to collapse
For future reference, placing blob in the same folder as fastboot is not required. However you do need the blob folder to be the current folder for your terminal session.
FL00DY said:
For future reference, placing blob in the same folder as fastboot is not required. However you do need the blob folder to be the current folder for your terminal session.
Click to expand...
Click to collapse
Are you @_that in disguise!?
After unsuccessfully attempt to flash identity crisis phone not able to flash any other rom seems to me bricked, any solution?
Sent from my MI PAD using XDA Free mobile app
Fastboot flash the XT1033 5.0.2 Firmware Image for your phone from here:
http://forum.xda-developers.com/mot...y-firmware-t3110795/post60792279#post60792279
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If you have problems, provide a full and complete fastboot log (copy and paste the fastboot screen)
I am on cm 12.1 now.
I wanted to use your rom.
Sent from my MI PAD using XDA Free mobile app
Nishblueweapon said:
I am on cm 12.1 now.
I wanted to use your rom.
Click to expand...
Click to collapse
Something has happened to your phone. If you do what I describe above, any custom ROM should work.
Will try buddie
Sent from my MI PAD using XDA Free mobile app
lost101 said:
Something has happened to your phone. If you do what I describe above, any custom ROM should work.
Click to expand...
Click to collapse
in fastboot mode it says waiting for device.
To be sure i have installed latest drivers via motorola device manager.
Nishblueweapon said:
in fastboot mode it says waiting for device.
To be sure i have installed latest drivers via motorola device manager.
Click to expand...
Click to collapse
@lost101 i hope this could help him
it won't work that easy. On what window you are ?? I don't give a damn which driver you installed http://forum.xda-developers.com/showthread.php?t=2588979
just install the latest version from here.... Let it download and then i
MAKE SURE YOU HAVE USB DEBUGGING ON FROM DEVELOPERS SETTINGS
it will ask you for something like installing system wide adb and fastboot devices. Let it install at last skip the installing device software.
Now just go to c drive of your system or drive in which you have your window installed(drive) installed. Now you see adb named folder on the root of the drive.
Just press shift key first and right click then, you will see there a option of opening with command prompt or something.
Voila !!! you are now in adb .
To check you have right driver installed
give coomand like: adb devices this will show your device in the window...
if you see your device then type command: adb reboot bootloader this will bring you into bootloader menu...
TO check here that you are properly set yourself type command: fastboot devices
sachoosaini said:
@lost101 i hope this could help him
it won't work that easy. On what window you are ?? I don't give a damn which driver you installed http://forum.xda-developers.com/showthread.php?t=2588979
just install the latest version from here.... Let it download and then i
MAKE SURE YOU HAVE USB DEBUGGING ON FROM DEVELOPERS SETTINGS
it will ask you for something like installing system wide adb and fastboot devices. Let it install at last skip the installing device software.
Now just go to c drive of your system or drive in which you have your window installed(drive) installed. Now you see adb named folder on the root of the drive.
Just press shift key first and right click then, you will see there a option of opening with command prompt or something.
Voila !!! you are now in adb .
To check you have right driver installed
give coomand like: adb devices this will show your device in the window...
if you see your device then type command: adb reboot bootloader this will bring you into bootloader menu...
TO check here that you are properly set yourself type command: fastboot devices
Click to expand...
Click to collapse
I am on win. 7. It first gave me an error adpwinal.DLL file is missing from your PC while I was trying to flash those commands in cmd window, so I installed that file on my PC. Whenever I am in fastboot mode now it doesn't recognise me device. & normally it does. I think the problem with fastboot files, it shows USB connected. Will try what u said.
Sent from my Moto G using XDA Free mobile app
while flashing the system files it says file too large
To be sure i was on cm 12.1 (5.1.1) & i have flashed ASia retail 5.0.2?
Where i am wrong?
Nishblueweapon said:
while flashing the system files it says file too large
To be sure i was on cm 12.1 (5.1.1) & i have flashed ASia retail 5.0.2?
Where i am wrong?
Click to expand...
Click to collapse
Use mfastboot.exe: https://www.androidfilehost.com/?fid=24052804347778493
lost101 said:
Use mfastboot.exe: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
Got it to boot successfully. Thank u
What I did was flashed 1 more system I.e. 0 not mentioned in the op
Sent from my MI PAD using XDA Free mobile app