Related
I've followed all the guides to a T. and my SDK is able to run nicely. However, once I've made contact w/ my device in 'usb debugging mode', tested the connection w/ "adb devices" in command prompt, and set the device to bootloader w/ the "adb reboot bootloader" command, and finally I give it the command to "fastboot oem unlock", I get an unknown error!! Please help. I have all the path variables set, and my SDK is running good, and has all the newest updates.
This is a link to a video I made of the problem. Please watch. It'll help if you can see the problem! just copy paste into search bar - youtube.com/watch?v=2bROUZh7GRI
Thanks for your responses. I hope they come quickly!
V0nice said:
I've followed all the guides to a T. and my SDK is able to run nicely. However, once I've made contact w/ my device in 'usb debugging mode', tested the connection w/ "adb devices" in command prompt, and set the device to bootloader w/ the "adb reboot bootloader" command, and finally I give it the command to "fastboot oem unlock", I get an unknown error!! Please help. I have all the path variables set, and my SDK is running good, and has all the newest updates.
This is a link to a video I made of the problem. Please watch. It'll help if you can see the problem! just copy paste into search bar - youtube.com/watch?v=2bROUZh7GRI
Thanks for your responses. I hope they come quickly!
Click to expand...
Click to collapse
OK, I will first say that I'm not an expert, but have gone through this process and have had to use ADB a number of times, so
1) why did you copy all the platform tools into tools folder? It should be otherway around, but clearly you have it working, so OK with that,
2) do you have all the files you need in your tools folder (since that's what you are using)?
3) are you using the proper syntax? No additional spaces where they don't belong, and so on?
4) are you getting any messages at all on the Xoom itself when you enter these commands?
5) Review all of your steps. Start over. If no luck, why not try to chat with experts on Xoom Channel on IRC? Maybe they can help you pinpoint the problem.
It doesn't seem serious but I think you've maybe missed a step in your prep work or have something simple turned around.
Good luck.
-copied to tools folder, because that's what I was directed to do... Guess it works either way.
-I do have all the files needed.
-How do I know if I'm using proper Syntax or not? that might be where I went wrong. But idk...
-No messages AT ALL on the xoom screen. (actually, 1 time out of the hundreds of times, Below the 'fastboot' words, I got red words that said cannot process command, or something like that.)
okantomi said:
OK, I will first say that I'm not an expert, but have gone through this process and have had to use ADB a number of times, so
1) why did you copy all the platform tools into tools folder? It should be otherway around, but clearly you have it working, so OK with that,
2) do you have all the files you need in your tools folder (since that's what you are using)?
3) are you using the proper syntax? No additional spaces where they don't belong, and so on?
4) are you getting any messages at all on the Xoom itself when you enter these commands?
5) Review all of your steps. Start over. If no luck, why not try to chat with experts on Xoom Channel on IRC? Maybe they can help you pinpoint the problem.
It doesn't seem serious but I think you've maybe missed a step in your prep work or have something simple turned around.
Good luck.
Click to expand...
Click to collapse
-copied to tools folder, because that's what I was directed to do... Guess it works either way.
-I do have all the files needed.
-How do I know if I'm using proper Syntax or not? that might be where I went wrong. But idk...
-No messages AT ALL on the xoom screen. (actually, 1 time out of the hundreds of times, Below the 'fastboot' words, I got red words that said cannot process command, or something like that.)
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
V0nice said:
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
Click to expand...
Click to collapse
Do you know what you did to be able to unlock? I think you really have to be careful to type commands EXACTLY as shown. No extra spaces, but don't leave anything out either. Looks like commands aren't typed in correctly. Take your time. You'll do it.
V0nice said:
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
Click to expand...
Click to collapse
I had this error followed by "unknown partition". When I tried fastboot boot recovery.img, it would say it could not access recovery. I deleted every partition and sent the device the stock imgs. Recovery would still fail.
STRANGELY ENOUGH, I rebooted my PC, unplugged the cable from the Xoom, let the device boot, changed USB debugging to on (stock unchecked it when imaged), and it took the recovery flash that time. I can't explain why, but it worked for me.
eqppwqqep said:
I had this error followed by "unknown partition". When I tried fastboot boot recovery.img, it would say it could not access recovery. I deleted every partition and sent the device the stock imgs. Recovery would still fail.
STRANGELY ENOUGH, I rebooted my PC, unplugged the cable from the Xoom, let the device boot, changed USB debugging to on (stock unchecked it when imaged), and it took the recovery flash that time. I can't explain why, but it worked for me.
Click to expand...
Click to collapse
So is everything ok now?
okantomi said:
So is everything ok now?
Click to expand...
Click to collapse
Yes. I am not rooted. am I supposed to change the thread to solved or something?
different error on trying to flash this recovery
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
jesmitty said:
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
Click to expand...
Click to collapse
If you haven't already. Delete the .img file. and reinstall it. try the process again.
make sure you're inputting the full command prompt from the beginning. That was my problem. Hope that helps.
jesmitty said:
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
Click to expand...
Click to collapse
fastboot flash recovery(you missed this) recovery-Tiamat-R4c-100611-1150-cwm.im
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Disclaimer:
By following this guide, you will have to issue commands that risk to damage (aka. brick) your tablet or at least void your warranty. I won't be responsible for any damage made to your device. You've been warned.
Click to expand...
Click to collapse
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
And there you have ! You are now back to stock ROM with fully working 3G
Thanks a lot for this, I found these instructions on Wolf's thread but wasnt sure it would work with our devices, Thanks for taking the first big step.
Questions.
1. Does this wipe your data?
2. Does CWM still work after?
AFAIK, this will wipe your data, remove CWM and uninstall root. Your device's bootloader will still stay unlocked though.
You will have to flash CWM back using this guide: http://forum.xda-developers.com/showthread.php?t=1668173
Hi, followed the steps but it didnt work for me
Fastboot copies the file but after when it tries to flash it gives an error
sending 'system' (796653 KB)...
OKAY [137.443s]
writing 'system'...
FAILED (remote: ()
finished. total time: 138.477s
The Tab shows
Failed to process command flash:system error(0x170003)
The progress bar is showing under the USB logo with 1% blue, after hold power down I'm back into Onyx Rom
Any Thoughts?
I had the same problem and I just issued the same command a second time and it worked just fine
Try to format your /system (under the mounts and storage option) from CWM and wipe data and cache.
2nd time a charm!
Worked fine the second time i ran the command,
Im back to stock again :good:
I will wait for a 3G friendly Rom before flashing again
Thanks for your help
---------- Post added at 05:59 PM ---------- Previous post was at 05:42 PM ----------
Auliyaa said:
AFAIK, this will wipe your data, remove CWM and uninstall root. Your device's bootloader will still stay unlocked though.
You will have to flash CWM back using this guide: http://forum.xda-developers.com/showthread.php?t=1668173
Click to expand...
Click to collapse
Yip Sends you back to total stock
Stock Recovery
Stock Rom
only thing that sticks is Unlocked Bootloader
Thanks a million. This worked for me as well after 2 tries. Saved my $400!
Thanks heaps for this
I ended up in trouble when I flashed the TF300T firmware by mistake. It kept freezing and rebooting on me after that little stuff up.
Anyhow before I did that I made a backup with CWM, and after I restored it my 3G was gone but everything else worked fine.
Manual updates were failed though and they still do. At least I have my 3G back :victory:
So this method would probably work for upgrading to .40 as well, but it means a complete datawipe!
I'm sure there are many of us in the same boat now. I guess we will just have to wait and hope that some kind person makes a recovery image for the TF300TG?
Auliyaa said:
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
And there you have ! You are now back to stock ROM with fully working 3G
Click to expand...
Click to collapse
I got a question, i had problems with the touch since the last update, so i want to go back to the original, so my question is to perform this do i have to have the bootloader unlocked?
Auliyaa said:
Hi everyone,
[*] Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Click to expand...
Click to collapse
Hi, any idea why i dont have this 'USB icon' ?? i have 'wipe data' and an android icon that performs a cold boot.
Any idea why this will seemingly flash fine, but go to bootloop when I fastboot -i 0x0b05 reboot the tab?
Don't work for me
Auliyaa said:
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
And there you have ! You are now back to stock ROM with fully working 3G
Click to expand...
Click to collapse
Hi, followed the steps but it didnt work for me too
Fastboot copies the file but after when it tries to flash it gives an error
sending 'system' (796581 KB)...
OKAY [129.964s]
writing 'system'...
FAILED (remote: (InvalidState))
finished. total time: 182.134s
The Tab shows
signature mismatch
Can you help me?
hy
i'm having a problem with my tf300t...when i turn it on it shows the asus logo and in the upper left it show device is unlocked...but i can't enter the menu showing rck and the other 3 icons...i really don't know what to do...
then there is another thing...tried to install driver...i get to the part where the tablet is visible, but with the vol up and reset with a pin...it then shuts down and if i try to power it up it dissapears from the device manager...also...if i don't turn it up, the driver can't be installed...i tried every method...please help...
can i retun it to the repair service this way or i will loose my waranty?
sorry if the spelling isn't correct...i don't speak english fluently
waiting a response...thanks in advance
Auliyaa said:
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
fastboot -i 0x0B05 flash system blob
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
And there you have ! You are now back to stock ROM with fully working 3G
Click to expand...
Click to collapse
Using
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
is a tad wrong. It works, but only by accident.
You should be using
fastboot -i 0x0B05 flash staging blob
Click to expand...
Click to collapse
The technical reason for why your command works, is because the nvidia bootloader writes files to the staging area before writing it to the partition you specify.
What essentially happens is:
Blob is written to staging
Blob is copied to system (meaning non-booting system)
On reboot, blob is "extracted" from staging and properly flashed.
Step 3 is what makes it work in the end, but you are causing an extra unneeded write to the flash (step 2 is not really needed) (In this case it works, but it potentially increases the risk of bricking)
thx didn´t know that. So all the howto´s are wrong
benoitvdh said:
Hi, followed the steps but it didnt work for me too
Fastboot copies the file but after when it tries to flash it gives an error
sending 'system' (796581 KB)...
OKAY [129.964s]
writing 'system'...
FAILED (remote: (InvalidState))
finished. total time: 182.134s
The Tab shows
signature mismatch
Can you help me?
Click to expand...
Click to collapse
Your probably running Jellybean, if so this HOWTO does'nt work.
Question: What exactly is supposed to happen? First I tried it and got the fail and did it a second time and it seemingly worked. In my command prompt it ended with
"writing 'system' ... OKAY"
and wasn't doing anything after that in the command prompt and on the tablet there was a full status bar so it looked like whatever it was doing it was finished? So I held the power button and I think it was a boot loop ... it just was the ASUS screen with the spinning circle. So I just did it again, failed the first time did it again and now I am where I left off. I guess I will wait a while and see if it says "SUCCESS" on my tablet? And if not I will put in the reboot command? (I probably should have tried that last time instead of holding the power button I forgot about the last couple lines of the guide )
EDIT: Or is it cuz I am flashing the wrong SKU? I didn't know what one my tablet is supposed to be ... its a cyanogenmod build so I don't think I cant find what the SKU is supposed to be. I went with US SKU because I live in the United States but I don't know if that's what it is
EDIT2: After waiting a while with no "SUCCESS" Windows said that adb.exe crashed or something. So I put in the reboot command but now it seems to be stuck on the ASUS loading screen again.
Blackdrag said:
Question: What exactly is supposed to happen? First I tried it and got the fail and did it a second time and it seemingly worked. In my command prompt it ended with
"writing 'system' ... OKAY"
and wasn't doing anything after that in the command prompt and on the tablet there was a full status bar so it looked like whatever it was doing it was finished? So I held the power button and I think it was a boot loop ... it just was the ASUS screen with the spinning circle. So I just did it again, failed the first time did it again and now I am where I left off. I guess I will wait a while and see if it says "SUCCESS" on my tablet? And if not I will put in the reboot command? (I probably should have tried that last time instead of holding the power button I forgot about the last couple lines of the guide )
EDIT: Or is it cuz I am flashing the wrong SKU? I didn't know what one my tablet is supposed to be ... its a cyanogenmod build so I don't think I cant find what the SKU is supposed to be. I went with US SKU because I live in the United States but I don't know if that's what it is
EDIT2: After waiting a while with no "SUCCESS" Windows said that adb.exe crashed or something. So I put in the reboot command but now it seems to be stuck on the ASUS loading screen again.
Click to expand...
Click to collapse
I have a WW TF300T and had no problem flashing a US version.. so its no SKU problem how long did you wait on the ASUS screen with the spinning circle? It took up to 5 mins for me! just wait a lil bit longer next time.. And there comes no "SUCCESS" on the tablet! only a blue bar that should be full after SUCCESS comes up in your Fastboot-COMMANDLINE.. the reboot with the fastboot reboot command from the first page..just give your tab a bit more time.. its like a babe. handle it with care :silly:
Success!
Hazaa! I can confirm that I managed to flash back to stock by flashing the blob to the staging partition. Like so many other, the first flash failed but the second time worked. I now have working 3G again!
0nyx7 said:
I have a WW TF300T and had no problem flashing a US version.. so its no SKU problem how long did you wait on the ASUS screen with the spinning circle? It took up to 5 mins for me! just wait a lil bit longer next time.. And there comes no "SUCCESS" on the tablet! only a blue bar that should be full after SUCCESS comes up in your Fastboot-COMMANDLINE.. the reboot with the fastboot reboot command from the first page..just give your tab a bit more time.. its like a babe. handle it with care :silly:
Click to expand...
Click to collapse
Thanks for the reply 0nyx7!
I had waited a while, maybe 10-20 minutes? But I don't remember entirely. I tried flashing the stock firmware a few times but eventually I just gave up. I didn't like the possibility that my tablet was bricked so I just aborted mission and decided to go back to cm10 where it was safe. I just looked up a post on how to flash Clockworkmod Recovery with fasboot and then flashed a cm10 nightly I already had on my internal storage. So all is good... Mostly.
Hey guys, I'm currently trying to flash back to the new 4.3 factory image that I downloaded from Google, however, it all goes fine, I flashed the bootloader, flashed the radio and it all says it has been updated properly, then when I try and flash the system.img files and boot.img files they just say no such file or directory exists and stops, meaning the phone is unusable at the moment until I flash something.
Anyone know why this is happening?
BTW I'm using a mac.
Issue fixed, see below!
************************************************************************************************
Ok guys, the problem was solved in an odd way!
I got annoyed with the flashing errors, and flashed the old kernel and radio I was using with my Illusion rom which thankfully got me back to that even though I had lost all of my data (backed up though).
For anyone having this problem and wants to unroot to go back to 4.3 or is trying to flash the legit 4.3 rom from Google and then maybe unroot or just use the 4.3 rom direct from Google...
DOWNLOAD THE LEAKED 4.3 ROM AND FLASH USING STANDARD CWM METHOD.
DOWNLOAD THE .84/.83 KERNEL AND FLASH THIS AS WELL.
After this I got the legitimate OTA update which was only 3.4mb and it even fixed root so I am now back to complete stock, locked bootloader and no root!
Hope this helps
Click to expand...
Click to collapse
Easiest way of flashing the system image is to just use the flash-all script included in the TGZ - just extract it out and run it when the phone is connected in fastboot mode. Personally, I do the following:
1. Extract the entire TGZ (including the update.zip)
2. Move all the IMG files into one folder
3. Rename them to easy names, e.g. bootloader, radio, system, userdata, boot, recovery, etc.
4. Flash them all in turn, rebooting the bootloader each time
5. Once all done, erase/format the cache (fastboot erase cache and fastboot format cache)
6. Boot into recovery and clear cache again and then do a factory reset (this makes sure the unit see all the internal memory)
7. Reboot the phone
Should all work now
siravarice said:
Hey guys, I'm currently trying to flash back to the new 4.3 factory image that I downloaded from Google, however, it all goes fine, I flashed the bootloader, flashed the radio and it all says it has been updated properly, then when I try and flash the system.img files and boot.img files they just say no such file or directory exists and stops, meaning the phone is unusable at the moment until I flash something.
Anyone know why this is happening?
BTW I'm using a mac.
Click to expand...
Click to collapse
Maybe you have corrupted files? Retry the download from google and unpack all with 7zip.
I did that yesterday and all works fine.
4.3 (JWR66V)
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
7zip
http://www.7-zip.de/
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
http://forum.xda-developers.com/showthread.php?t=2010312
EddyOS said:
Easiest way of flashing the system image is to just use the flash-all script included in the TGZ - just extract it out and run it when the phone is connected in fastboot mode
Click to expand...
Click to collapse
How would I do that on a mac? I tried typing:
./fastboot flash flash-all.bat
but do I need to use the .sh version?
info.brandenburg said:
Maybe you have corrupted files? Retry the download from google and unpack all with 7zip.
I did that yesterday and all works fine.
Click to expand...
Click to collapse
Did that, same thing happened. I tried flashing the entire .zip and then I tried separately and it still didn't work.
Ok so I know it is just the system.img file that doesn't work, as all the other files have just flashed fine! Going to re-download and see if that helps.
siravarice said:
How would I do that on a mac? I tried typing:
./fastboot flash flash-all.bat
but do I need to use the .sh version?
Click to expand...
Click to collapse
You just run the script, you don't flash it. It's a batch file which then does all the fastboot commands. You also use flash-all.sh as you don't have Windows
EddyOS said:
You just run the script, you don't flash it. It's a batch file which then does all the fastboot commands. You also use flash-all.sh as you don't have Windows
Click to expand...
Click to collapse
Still doesn't work.
I used: bash flash-al.sh
And it just said fastboot not found in certain lines for the command and did nothing. I thought it fixed itself when I swapped USB ports but when it got to the system.img it just gave me the same error again. It flashes everything else ok but not this file, it's the third time I have downloaded it and now I have no way to get it back to being useable as when I press start it just gives me a black screen
HELP PLEASE!
I would but I use Windows and it's all fine. Might be worth downloading the factory image again, checking the md5 and trying to flash the system image again
EddyOS said:
I would but I use Windows and it's all fine. Might be worth downloading the factory image again, checking the md5 and trying to flash the system image again
Click to expand...
Click to collapse
Im trying to install some Samsung Android Drivers on my old laptop but the thing is so slow it's basically impossible to work from now
I've redownloaded the files, I don't know how to check the MD5Sum though. Still nothing doing. I get this error:
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (6166 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6664 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (531281 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
edue3e4:4.2unrootnexus4 Simon$
It really doesn't want to write the system.img file, or maybe it doesn't want to write to system?
What happens if you extract the system.img file and flash it via fastboot manually?
fastboot flash system system.img
I always use this guide if I forget:
efrant said:
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked. See the notes section at the end of this post for information on re-locking the bootloader.
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this
Click to expand...
Click to collapse
EddyOS said:
What happens if you extract the system.img file and flash it via fastboot manually?
fastboot flash system system.img
I always use this guide if I forget:
Click to expand...
Click to collapse
That's exactly what I have been doing, I prefer doing it manually as I don't like using Toolkits and finding a good one for mac is hard enough.
It just says that it cannot send it because the file or directory does not exist, yet if I unplug the phone it does go back into my old rom I was using before that, even though I flashed a new radio and recovery.img, boot.img, user data.img, everything except system.img as it doesn't work
Something clearly wrong with the partition but no idea what...
I know right, I've gone back to the ROM I had previously and downloaded the leaked 4.3 rom and flashed it through flashify. If it works I will simply lock the bootloader again and it should be good to go!
i did the same way through nexus tool kit 2.0 n p.s i guess the file was corrupted that y it failed in the mid. ill try it again
Hmmy 4444 said:
i did the same way through nexus tool kit 2.0 n p.s i guess the file was corrupted that y it failed in the mid. ill try it again
Click to expand...
Click to collapse
Let me know if you get anywhere with it!
it worked.. jst copy the image n dont rename it n go to google nexus 4 toolkit folder n there u would see a folder named *put googlr factory image here* paste it there n before starting ur bootloader must be unlocked.. so thats that.. after that that open the nexus 4 toolkit n then click on number 9 whch says download extract + flash google factore stock rom n then after that type 2 whch says flash google factory image... n thats it. it will automatically flash it.... gv me thanks too
Sent from my Nexus 4 using xda app-developers app
Hi there, same issue with me on a mac
Plus can you tell me how you went back to the previous rom, my phone is unusable right now and i do have a nandroid backup so.
Have either of your tried to flash the 4.2.2 factory image? Would be interested to see if it works
Sent from my Nexus 4 using xda premium
EddyOS said:
Have either of your tried to flash the 4.2.2 factory image? Would be interested to see if it works
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I dont mind, can you direct me towards a post where they show how to, i m not sure of all this and dont want to mess around with wrong files.
UPDATE: I tried and that works just fine. Rebooted to 4.2.1
Hello, my name is noob. I have an addiction...
...to my Nexus 7! Unfortunately, I have not been able to update to 4.3!
My device was previously rooted (it no longer is) and I have tried everything I know and more. When it was rooted, I did not install a custom ROM or anything. I essentially just used root capabilities to get some apps and mess around with some apps a little.
When I try to update to 4.3 automatically as Google has me do it, I get the "signature verification failure".
I also tried to update it manually by downloading the update from androidpolice.
Then, I disabled system verification and tried to install the update and got a different error:
"Warning: No file_contextsVerifying current system... assert failed: apply_patch_check("/system/lib/libSR_AudioIn.so", "9c386ff759d8553e312e5ffc5773449ae6634748", "bcc09f67f497c6a6edece202942bc4c45f712f62"
E: Error in /sdcard/0/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip
(Status 7)
Installation aborted.
What can/should i do?
Any help is greatly appreciated! Also, given my noob status, the simpler you can put things, the better. I am good at following step by step instructions, but give me some acronyms and use fancy language and I might fail.
Thank you!
Edit 1: I forgot to mention that I also did a factory reset and tried to update to 4.3, but that didn't help either.
I am also having the same problem. an error like this. any ideas why and how to fix it? and after it aborted when my n7 booted up and i check for updates it says ur n7 is up to date, but then the version is stil 4.2.2 not 4.3. so any solution guys? is it because i'm using custom kernel? i'm using franco kernel rite now.
There are many threads dealing with these problems ... Please use the search function before starting a new thread.
To answer your question: you have a non stock system so the OTA update is failing. You need either return to stock or do the update manually. Btw. in my blog there is an article how to do so.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
There are many threads dealing with these problems ... Please use the search function before starting a new thread.
To answer your question: you have a non stock system so the OTA update is failing. You need either return to stock or do the update manually. Btw. in my blog there is an article how to do so.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well, I did search the forums and didn't find anything that helped. And, like I said, I tried doing it manually and it didn't work.
Tomorrow I will check out your blog though and see if the instructions are any different than what I found elsewhere. Maybe i did a step wrong or something?
Success! I had to incorporate some steps from a slightly different method of updating, but it finally worked!
Thank you!
ItsDare said:
Success! I had to incorporate some steps from a slightly different method of updating, but it finally worked!
Thank you!
Click to expand...
Click to collapse
Hi! I am having the same problem and getting Status 7 error in CWM Touch.
Can you please let me know as well which method did you use? Thanks
ItsDare said:
Success! I had to incorporate some steps from a slightly different method of updating, but it finally worked!
Thank you!
Click to expand...
Click to collapse
Could you provide the detailed step-by-step instruction? I'm on the same (noob) level as you were just before you started this thread.
pawelzielak said:
Could you provide the detailed step-by-step instruction? I'm on the same (noob) level as you were just before you started this thread.
Click to expand...
Click to collapse
http://anddisa.blogspot.de/
You can use the instructions here (although he left a bit out)
1. install http://www.droid-life.com/2013/04/08/koush-releases-universal-adb-driver-for-windows/
2. install https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
3. install http://www.7-zip.org/download.html
4. download https://developers.google.com/android/nexus/images#nakasijwr66v
5. open the folder fastboot/adb installed to
6. open the image (#4) with 7zip (#3)
7. extract bootloader.img, boot.img and system.img into fastboot folder(#5)
8. run fasboot (should be in start menu), brings up command prompt)
9. type at command prompt "fastboot flash bootloader bootloader-*********.img" *** = use the file name that you extracted (#7)
10. type at command prompt "fastboot reboot-bootloader"
11. type at command prompt "fastboot flash boot boot.img"
12. type at command prompt "fastboot flash system system.img"
13. type at command prompt "fastboot reboot"
14. enjoy 4.3
gallahad2000 said:
You can use the instructions here (although he left a bit out)
1. install
....
14. enjoy 4.3
Click to expand...
Click to collapse
Oh, so you did it via PC.
I still would like to try with OTA. My problem is checksum on build.prop. I modified it and now I reverted changes but there still may be some white character difference. Could anyone attach build.prop file (along with its checksum) of stock n73g a4.2.2? I'll give it one more try.
With N73G
What I found most helpful in fixing my issue was this thread!
http://forum.xda-developers.com/showthread.php?t=1907796
It is a guide to flashing the factory image to return it to stock, but can be used to update to 4.3 as well!
What I did to fix my specific problem was:
Download the 4.3 update files from androidpolice.
Extracted these three files from it as suggested on AndDiSa's blog:
bootloader-grouper-4.23.img
boot.img
system.img
Plugged my N7 into my computer and since my device doesn't show up in my computer in MTP mode, but does in PTP, I switched to PTP and typed the following code into a command window:
> adb reboot-bootloader
I personally found it necessary to erase boot, cache, recovery, system and userdata to get my update to work. However, if it works without erasing those, that is definitely preferable, and you can skip these commands:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
Then type these commands:
> fastboot flash bootloader bootloader-grouper-4.23.img
> fastboot reboot-bootloader
> fastboot flash boot boot.img
> fastboot flash system system.img
Then I rebooted my N7 and Voila, I was using 4.3!
Verification fail on 4.3 update
I am using the galaxy nexus, i had rooted it and was using another custom ROM - ParanoidAndroid 3.60. I currently have the 4.2.2 and i'm trying to update it through my system update but it loads and then gives the error message "verification failed"
I've tried it using the OTA RootKeeper procedure too but the same error turns up. Please help!
This guide will help you unlock your bootloader, flash a factory image, and return you to a stock device. It is wriiten assuming you have a windows PC (MAC users, see post 2). This can be helpful if you need to RMA your device or if you are getting erratic behavior or messed something up.
Tools and Files You’ll Need
If you don’t have adb and fastboot installed on your PC go here for a quick install of the necessary files, thanks to @Snoop05, http://forum.xda-developers.com/showthread.php?t=2588979
For MAC users go here. http://forum.xda-developers.com/showthread.php?p=32305619
For Linux users, http://forum.xda-developers.com/showthread.php?p=10746225
For the factory image go here, https://developers.google.com/android/nexus/images You’ll download a .tgz file. Use winrar or 7-zip to extract the file to its own directory and remember where that directory is. Inside is another zip file, extract that too. You’ll need those image files if you use the long method to install the factory image. It’s also good to know where they are as they come in handy as you get more familiar with fastboot and what you can do with it.
How To Unlock the Bootloader
If you don’t have developer options enabled on your device go to settings, about device and tap on the build number 7 times.
In settings, developer options enable oem unlock
Now you get to use fastboot! Boot you device into the bootloader, vol up + power with your device shut off. Once booted into the bootloader connect it to your PC with the usb cable and open a command window on your PC. Once connected type the following command in the cmd window:
fastboot devices (Your device serial number should show up and this will ensure fastboot is working properly)
Then type:
fastboot oem unlock (This will unlock the bootloader and you’re now good to go)
NOTE, UNLOCKING THE BOOTLOADER DOES WIPE YOUR DEVICE SO BACKUP OFF YOUR DEVICE FIRST
How To Flash the Factory Image, SHORT METHOD
Open a command window on your PC in the same directory as you extracted the factory image. In that directory shift, right click in an open area and use “Open a command window here”
Boot your device into the bootloader and connect it to your PC. Then simply double click on the flash-all batch file. Note that there are batch files in there that will work for Windows as well as Linux machines
Let the batch file run and when it’s done you’ll be back to stock.
NOTE THAT FLASHING BY THIS METHOD DOES WIPE YOUR DEVICE SO MAKE SURE YOU BACKUP OFF YOUR DEVICE FIRST.
How To Flash the Factory Image, LONG METHOD
In this method each factory image is flashed separately. This should be used if you have problems with the short method and as you get more familiar with fastboot you’ll be able to flash only the images that you need for your specific requirement. For instance, you might want to only flash the stock recovery if you’re trying to take an ota and you’ve installed a custom recovery. The order that you flash the images is not important.
In the folder you extracted the factory image it’s easiest if you re-name the bootloader image file to simply bootloader and radio. Then open a Windows command window in that folder and use the fastboot commands:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w (NOTE, this command does wipe your device. It’s possible to flash the factory image without this command but if you’re going from different revision numbers of android it’s highly recommend to wipe the device)
Now open a Windows command window in the same folder that you extracted the zip file in, the one where you find recovery, system, etc. Then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img [Note, flashing system takes a long time, so let it do it's thing]
fastboot flash vendor vendor.img
Congratulations, you’ve now flashed a factory image and learned how to use fastboot!
For MAC users, proceed each fastboot command with a ./ e.g. ./fastboot flash boot boot.img
This should be made a 'sticky'...
An excellent well written tutorial... succinct, clear and to the point.
Far better to use fastboot instead of a toolkit... Everything is more transparent, and you actually gain a better understanding of your device as a result.
Rgrds,
Ged.
GedBlake said:
This should be made a 'sticky'...
An excellent well written tutorial... succinct, clear and to the point.
Far better to use fastboot instead of a toolkit... Everything is more transparent, and you actually gain a better understanding of your device as a result.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks @GedBlake. I would have responded sooner but I had to get home and check my tablet. Actually both work, vol up + power and vol down + power.
Sent from my Nexus 9 using XDA Free mobile app
But.... Toolkit so easy?
(agreed... Toolkits not the best choice)
Thread stuck. Great guide @jd1639!
If we get enough guides, tutorials, how to's and other great info threads.... I would suggest a "sticky roll up" thread, so too many stickies aren't created.
Food for thought.
Edit : That ^^^^ was a hint to other members to get your guides, tutorials, info threads, FAQ... Etc... Going..... This is a Nexus section after all. :silly:
Darth said:
But.... Toolkit so easy? ?
(agreed... Toolkits not the best choice)
Thread stuck. Great guide @jd1639! ?
If we get enough guides, tutorials, how to's and other great info threads.... I would suggest a "sticky roll up" thread, so too many stickies aren't created.
Food for thought. ?
Click to expand...
Click to collapse
I'll keep an eye it and do a roll up when the need arises
Sent from my Nexus 9 using XDA Free mobile app
cant flash system.img
I Xubuntu 14.04 I can't seem to flash the system.img I get the following error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.032s
nyasha1935 said:
I Xubuntu 14.04 I can't seem to flash the system.img I get the following error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.032s
Click to expand...
Click to collapse
It's possible that you need to update your Android SDK to the latest. There was a recent change (within last 6 months) to fastboot to allow flashing these large .img files.
cam30era said:
It's possible that you need to update your Android SDK to the latest. There was a recent change (within last 6 months) to fastboot to allow flashing these large .img files.
Click to expand...
Click to collapse
Ok thanks gonna try on windows, im a noob on linux
nyasha1935 said:
Ok thanks gonna try on windows, im a noob on linux
Click to expand...
Click to collapse
You'll be sorry.....
cam30era said:
You'll be sorry.....
Click to expand...
Click to collapse
Ok back to linux, how do I update android SDK
nyasha1935 said:
Ok back to linux, how do I update android SDK
Click to expand...
Click to collapse
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Is it possible to flash a factory image using a custom recovery like TWRP?
Sent from my Nexus 9 using Tapatalk
iamroddo said:
Is it possible to flash a factory image using a custom recovery like TWRP?
Click to expand...
Click to collapse
Is it possible to extract the .img from the volantis-lmy47x-factory-3efdc8d4.tgz from https://developers.google.com/android/nexus/images and flash them individually with TWRP (with the exception of recovery.img, which I guess would over-write TWRP)? Can it this be done directly from 5.0.1 or would I need to first upgrade to 5.02?
Hi, I'm Italian so i'm sorry if my english is bad xD what happens if i flash a different kernel? Will i lose my warranty?
If yes, if i flash the factory image, will i have my warranty again?
And, again, sorry for my bad english
Leoncino said:
Hi, I'm Italian so i'm sorry if my english is bad xD what happens if i flash a different kernel? Will i lose my warranty?
If yes, if i flash the factory image, will i have my warranty again?
And, again, sorry for my bad english
Click to expand...
Click to collapse
No need top apologize. You're English if fine.
There's a lot of discussion and lack of agreement about what affects the warranty on the Nexus 9. HTC says that even unlocking the bootloader "may void the warranty".
My advice would be to do what you want to it, but make sure you understand what you are doing. Ask a lot of questions before you do something you're unsure of.
Unlock your bootloader (if you haven't already). Do not relock bootloader if something goes wrong (this does not solve anything). With an unlocked bootloader, you can recover from almost any problem.
And you can flash the Google factory images anytime you want to return to stock.
I'm sorry there's not a clear answer to your question.
cam30era said:
No need top apologize. You're English if fine.
Click to expand...
Click to collapse
Thanks
So it's like Samsung knox, we don't know what happens to our device.
An other little question? Is the same if i root my device? Need to unlock bootloader?
Leoncino said:
Thanks
So it's like Samsung knox, we don't know what happens to our device.
An other little question? Is the same if i root my device? Need to unlock bootloader?
Click to expand...
Click to collapse
Bootloader has to be unlocked to root, install custom recovery (TWRP). And note that when you unlock bootloader, it will wipe the contents of your SDcard. If you have anything important there, back it up on your PC.
cam30era said:
Bootloader has to be unlocked to root, install custom recovery (TWRP). And note that when you unlock bootloader, it will wipe the contents of your SDcard. If you have anything important there, back it up on your PC.
Click to expand...
Click to collapse
And what happens if i lock again my bootloader, will i restore the warranty?
Leoncino said:
And what happens if i lock again my bootloader, will i restore the warranty?
Click to expand...
Click to collapse
That's a good question, without a clear answer (unfortunately).