Hey guys. My brother got himself a Nexus 7 which is his first Android, and he was playing with some tweaks or mods or something and tried flashing via recovery and has messed something up. I have tried using the Toolkits as well as doing it manually with fastboot. I am able to flash a recovery and use that, but lose it after boot (the permanent option doesn't seem to stick). But, when I try to do a factory restore with the google image, it doesnt matter if i'm doig it manual or with the toolkit, the all respond with a "archive does not contain... " boot.sig, recovery.sig, or system.sig. Here is my output:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (Unknown error))
finished. total time: 0.836s
Even if I do them manually, one at a time:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe flash boot nakasi-jro03d\image-na
kasi-jro03d\boot.img
sending 'boot' (4890 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.858s
I have also tried pushing a stock rom .zip to the /sdcard and it doesnt seem to make it either.
Feels like internal memory is corrupt. Any thoughts or ideas I can try? Also... should any custom recovery allow adb access? TWRP or CWM Touch don't seem to work.
Update... Just rebooted into bootloader and tried:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-jro03d-factory-e102ba72\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: 015d256898080e19
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4890 KB)...
OKAY [ 0.608s]
writing 'boot'...
OKAY [ 0.390s]
sending 'recovery' (5234 KB)...
OKAY [ 0.655s]
writing 'recovery'...
OKAY [ 0.343s]
sending 'system' (438656 KB)...
FAILED (unknown status code)
finished. total time: 3.292s
That's the most progress I can get. System seems to fail though. Tried multiple times.
Another note... If I boot into Recovery and adb push a file to the /sdcard, the transfer looks like it completes, but when I go to flash zip in recovery it gives me an E: Can't mount /sdcard/. Same thing if I go to the mounts and storage option and try to mount /sdcard.
Any ideas guys? Never seen this before.
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Mr. Monkey said:
Update... Just rebooted into bootloader and tried:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-jro03d-factory-e102ba72\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: 015d256898080e19
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4890 KB)...
OKAY [ 0.608s]
writing 'boot'...
OKAY [ 0.390s]
sending 'recovery' (5234 KB)...
OKAY [ 0.655s]
writing 'recovery'...
OKAY [ 0.343s]
sending 'system' (438656 KB)...
FAILED (unknown status code)
finished. total time: 3.292s
That's the most progress I can get. System seems to fail though. Tried multiple times.
Click to expand...
Click to collapse
The "archive does not contain *.sig" messages are normal. The FAILED messages on sending the system image is disconcerting. Use the platform tools from Google which includes fastboot. http://dl-ssl.google.com/android/repository/platform-tools_r16-windows.zip
There is a .bat file in the factory image archive that you can run to return to stock. If you don't want to run that, at least open it up and manually run the commands in sequence.
comminus said:
The "archive does not contain *.sig" messages are normal. The FAILED messages on sending the system image is disconcerting. Use the platform tools from Google which includes fastboot. http://dl-ssl.google.com/android/repository/platform-tools_r16-windows.zip
There is a .bat file in the factory image archive that you can run to return to stock. If you don't want to run that, at least open it up and manually run the commands in sequence.
Click to expand...
Click to collapse
I think that's the same thing I've been trying. I did download Google's platform-tools and try with that and still got the same error. Seems like I can't write to /system. Can't even erase it:
c:\android\platform-tools>fastboot.exe flash system C:\android\nakasi-jro03d\ima
ge-nakasi-jro03d\system.img
sending 'system' (438656 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.094s
c:\android\platform-tools>fastboot.exe erase system
erasing 'system'...
FAILED (command write failed (Unknown error))
finished. total time: 0.733s
c:\android\platform-tools>fastboot.exe format system
formatting 'system' partition...
FAILED (command write failed (Unknown error))
FAILED (command write failed (Unknown error))
finished. total time: 0.889s
What are my options? Flash stock recovery, re-lock bootloader and send it in for an RMA? Anyone else know what to try?
Mr. Monkey said:
I think that's the same thing I've been trying. I did download Google's platform-tools and try with that and still got the same error. Seems like I can't write to /system. Can't even erase it:
c:\android\platform-tools>fastboot.exe flash system C:\android\nakasi-jro03d\ima
ge-nakasi-jro03d\system.img
sending 'system' (438656 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.094s
c:\android\platform-tools>fastboot.exe erase system
erasing 'system'...
FAILED (command write failed (Unknown error))
finished. total time: 0.733s
c:\android\platform-tools>fastboot.exe format system
formatting 'system' partition...
FAILED (command write failed (Unknown error))
FAILED (command write failed (Unknown error))
finished. total time: 0.889s
What are my options? Flash stock recovery, re-lock bootloader and send it in for an RMA? Anyone else know what to try?
Click to expand...
Click to collapse
Two more thoughts - 1. try updating drivers. 2. verify the sha1 hash of the factory image
Did you try switching to a different usb port? Just a thought is all.
Wow. Can't thank you guys enough. Thought this was toast. I ended up trying all of the above, haha. Even though I had done it several times. I tried multiple computers, multiple factory images, multiple programs, multiple USB ports. But somehow, maybe your encouragement, something helped. I'll watch it and make sure nothing seems fishy, because I don't know how in the world that worked.... but it did. Thank you very much.
manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Hi there
I was having the same problem but when I try to flash the system.img (or the 'image-nasaki-jop40d.zip file too for that matter) I get the following error:
"error: cannot load 'system.img': Not enough space
I have done ALL the steps found in this guide without any issues until I get to that part
Help please my wife just gave me this N7 for christmas and I can't believe I may have just bricked it!!
My solution
I understand this is an old thread but I came across it when I was having the same issues earlier today.
Oddly, using the USB cable that came with the N7 seemed to fix the multiple "FAILED" I was getting.
Using my Samsung USB cable seemed to cause the issues.
Hope this can be a solution to others that may come by this thread by googling the issue.
manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
This one helped me!:good::good::good:
Thanks a lot.
manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Works, thanks. :good:
Unlock bootloader
Mr. Monkey said:
Hey guys. My brother got himself a Nexus 7 which is his first Android, and he was playing with some tweaks or mods or something and tried flashing via recovery and has messed something up. I have tried using the Toolkits as well as doing it manually with fastboot. I am able to flash a recovery and use that, but lose it after boot (the permanent option doesn't seem to stick). But, when I try to do a factory restore with the google image, it doesnt matter if i'm doig it manual or with the toolkit, the all respond with a "archive does not contain... " boot.sig, recovery.sig, or system.sig. Here is my output:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (Unknown error))
finished. total time: 0.836s
Even if I do them manually, one at a time:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe flash boot nakasi-jro03d\image-na
kasi-jro03d\boot.img
sending 'boot' (4890 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.858s
I have also tried pushing a stock rom .zip to the /sdcard and it doesnt seem to make it either.
Feels like internal memory is corrupt. Any thoughts or ideas I can try? Also... should any custom recovery allow adb access? TWRP or CWM Touch don't seem to work.
Click to expand...
Click to collapse
You need the bootloader to be unlock. First run the command " fastboot oem unlock " . It works flawlessly after that! Awesome!
nexus 7 (mobile)
shap4th said:
You need the bootloader to be unlock. First run the command " fastboot oem unlock " . It works flawlessly after that! Awesome!
Click to expand...
Click to collapse
Hi!
I bought a second hand nexus 7 rooted. I had a problem with updating os via wifi because it doesn't update. some kind a problem. I tried to do a hard reset hoping I could just restore the device manually but I messed up so I am now stuck with just a google logo and can only access bootloader with start, bootloader, restore and power off option. I don't know what to do. please help me. I am not a tech person but if you can give me a specific instructions, I know i can manage. i saw a lot off post here that they were able to restore their device so I have faith in this site and the members are highly recommended.
thank you in advance
manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Thanks man! This works for me..
manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Thanks. This one works for my friend.
Same case, solved on spanish forum.
/showthread.php?t=748207 on htcmania(dot)com
*Note: damn spam filter
Try this website. If you have any question ask me.
You will need to install files one by one.
SImply open flash bat file see what they are doing. and do same but one by one.
Flash bootloader and radio (radio does not appear on all devices, if it's not in your tgz, you don't need it)
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
NEXUS 9 ONLY - flash this as well
fastboot flash vendor vendor.img
If you want to wipe cache and user data (full wipe), flash these
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
Similar issue, please help
I'm using ubuntu 14.10 LTS. I had the same issue arise so i listened reextracted (even though boot.img, system.img & recovery.img were within .zip but im still getting "critical error: extent_create_backing: calloc: Cannot allocate memory
Mmap:invalid argument
Cannot generate image
FAILED()"
Anyone has a suggestion?
---------- Post added at 11:49 PM ---------- Previous post was at 11:18 PM ----------
So as my previous and maybe above msg said i was just about to attempt adb sideload to manually update to lollipop... From the bootloader i entered recovery... My nexus 4 shut down & got stuck @ wild new boot animation for lollipop. I waited 5 minutes while the fantastic yellow, red, blue & green orbs whizzed around, shut my 4 down & now "Android is upgrading... Optimizing app x of 68." How wild is this... But i still have to lock bootloader. Hopefully it doesnt screw anything up... I'll report back asap
---------- Post added 24th November 2014 at 12:19 AM ---------- Previous post was 23rd November 2014 at 11:49 PM ----------
So I relocked bootloader... Sent several test sms & so far so good. Wifi of course works, haven't tested bluetooth but ill report back. Boy I got lucky. No more linux for me... Jk
Everything You may need to install android 5.0.1
I'm writing this so that you all will not have to go through what I just experienced when trying to flash the android 5.0.1 OTA manual update. Here are some of the errors I've gotten out of and I will give you some tips to get fix these. I always seem to encounter issues that no one else has when flashing, so here we go.
Tip 1
1.)If you are trying to flash 5.0.1 (tip applies to any version) from the google website here: https://developers.google.com/android/nexus/images ....Make sure your computer can handle ".tgz" files. This took me a day and a half to figure out. If you try to download one of the files off this website without the proper software to do so you will simply get a ".tgz" file that you cannot extract the necessary files from.
*The solution is to download winrar from http://www.win-rar.com/predownload.html?&L=0 this website. Once you do and run it the ".tgz" file will become a folder (icon should look like stacked books) and you can proceed to actually follow the instructions on the page where you downloaded the file from. I learned this the hard way.
Tip 2
If you dont really understand how to us the "ADB" tools or "SDK" and everything related sounds like a foreign language to you then watch this video: http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/. It will explain how to copy files to your device while in bootloop. Pay special attention to the part about making sure your drivers are set up correctly. Drivers always get me when I installs. This knowledge will transfer over to downloading any rom or factory image in the future.
Links for Moving files to your device while in recovery:
Here are the appropriate drivers for copying files while in recovery to the nexus 5:
http://downloadandroidrom.com/file/drivers/Android/usb_driver.zip
Here is the fastboot link: http://downloadandroidrom.com/file/tools/fastboot.zip
Tip 3
The way I installed android 5.0.1 was:
1.)I downloaded the file from the google developer website that i pasted at the top
2.)I moved that file to a folder named "root" that i created on my desktop
*In this folder i have chainfire auto root http://autoroot.chainfire.eu/ in case i need to re-root my phone, I have the adb and fastboot.zip folders in my root folder as well.
3.)I moved the folder inside the FASTBOOT folder and extracted the file that i got from the developer website here. Once this is down there is another
3.)I extract the files here. After you extract there should be another folder called "image-hammerhead-lrx22c.zip." I copied those files to the fastboot folder as well so that they are outside of the zip file. I did not remove the zip file once I copied the insides to the outside. Right or wrong this is what I did.
4.)I used the Command prompt to navigate to this directory. Watch the how to copy files video to see how to navigate using the "cd" command
*basically i typed "cd desktop" which means change directory to the desktop. Then i did "cd root"....then "cd fastboot" ...YOUR PATH MAY BE DIFFERENT.
5.)Once i was here i could follow more of the instructions on the developer website. I could run that "flash-all.bat" command to begin flashing the 5.0.1. In order to run this command you literally type "flash-all.bat."
6.)After it finished it said,
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
helpful links: http://forum.xda-developers.com/showthread.php?t=1992063
This was okay, what you dont want is falures. While 5.0.1 is being installed, if you notice it say failure in the place where everything else is saying "OKAY" you have a problem. One guy on that xda link said:
"Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img"
You can type this into cmd and do each one by one and it may work.
7.)YOU MUST MAKE SURE TO EXTRACT THAT SECOND FOLDER inside the developer file! If you don't you will get failures because the program is looking for them. That's why manually installing them may work as well.
8.)IF YOU SEE THE ANDROID WITH NO LOADING BAR UNDERNEATH this does not mean that you are bricked. I thought it did and kept flashing 5.0.1 over and over and over again. Then i just waited a bit and my phone rebooted and i say the glorious dots rotating on my screen. I lived happily ever after.
9.)Once you are finished installing 5.0.1 you will loose root. Run that chainfire auto root program.You have to boot in to the bootloader screen...NOT RECOVERY...just the screen where you see the android and you can select "start" "recovery" etc. and open up that chainfire program and hit a key to start it. There are instructions on the actual program if you need help. If you are on the bootloader screen that i am talking about and you start the program it will "auto root" that is, automatically root your phone and thats that.
10.)Download root checker off the play store to see if you are actually rooted and have a blessed day. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Let me know if you need further explanation. I'm no pro but I've failed in soooo many ways i probably could help ya out! Jesus loves you all!
Related
My son brought me his Nexus S 4g and told me that it doesn't work anymore. He says that he didn't do anything and that it just started doing this on its own. Any help would be greatly appreciated.
When powered on, it quickly goes to the screen with the Google icon and a lock icon. It sits here for about 30 seconds, then reboots to the same thing. If I pull the battery and hold Vol Up and Power when inserting the battery I can get into Fastboot, but when I select Recovery or Reboot, I get the same Google screen.
When I gave him the phone, it was rooted with CWM recovery loaded and a ICS ROM running.
Any help would be greatly appreciated as I have been reading through threads all night long without finding much.
Sounds to me like you need to begin the rooting process again at the "fastboot oem unlock" part. Since you probably don't have anything on your SD card, you might have to push a new recovery via fastboot as well.
Look to this thread:
http://forum.xda-developers.com/showthread.php?t=1078213
for inspiration.
Once you get into the recovery loaded via fastboot, you can get whatever rom that you want onto the SD card by navigating to:
Mounts and Storage > Mount USB Storage
and leave it on that screen while you load the rom onto the SD card.
After that flash the new rom via CWM as normal.
Thanks for the reply. Since I was already unlocked, I followed the steps to return the phone to stock, including flashing boot, system, userdata, recovery and erasing cache. Now when I reboot, it just loops to the Google screen and reboots after 30 seconds. The only difference is that I don't see the lock icon at the bottom or the Google screen.
When I select Recovery, it just goes into the same Google loop. I am going to try to go through the root steps and see what happens. :-(
I was able to unlock the phone, but it will not boot into Recovery. I can get to Fastboot, but I am back to where I started.
When I gave the phone to my son, I had installed SetCPU and configured a profile to throttle the processor down when the screen was off to conserve battery. I am now wondering if he tried to overclock the processor and clicked "set at boot".
Any more suggestions? (please)
Did you successfully flash a recovery.img? Immediately after this you should hit Recovery, then mount the storage, copy a ROM over, do a Full Wipe and flash the ROM.
If all goes well, you'll boot fine. If not, it may be a hardware problem. Try to wipe most of it and lock the bootloader if you need to send it to samsung.
It looks like I successfully flashed a recovery image. I have tried version 5.x and version 3.x. Below is the result of the 5.x command. However when I select Recovery from Fastboot, I go to the Google screen loop.
C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery-cloc
kwork-5.0.2.0-crespo4g.img
sending 'recovery' (4136 KB)... OKAY
writing 'recovery'... OKAY
C:\Program Files\Android\android-sdk\tools>
OK, go to http://wonderly.com/bb/CRESPO4G/OEM/GRJ22IMAGES.zip
That will download the GRJ22 stock images of your phone. Unzip them in your PC. Next, use fastboot like this.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
After it finishes you can reboot your phone with "fastboot reboot". This will installed Stock GB 2.3.4 for NS4G. Setup your phone and you will get OTA to 2.3.5. After that you will get OTA again to 2.3.7. Good luck.
By the way, you must let it OTA all the way up to 2.3.7 to get the latest Radio and bootloader version.
Giving it a shot now. I'll let you know shortly how it goes.
Update: Same result. All commands completed successfully, but I end up in the Google logo boot loop. Is there a kernel .img file that I should flash, in case my son tried to flash an unsupported kernel?
C:\Program Files\Android\android-sdk\tools>fastboot flash bootloader bootloader
img
sending 'bootloader' (1536 KB)... OKAY
writing 'bootloader'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash radio radio.img
sending 'radio' (15232 KB)... OKAY
writing 'radio'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash system system.img
sending 'system' (174451 KB)... OKAY
writing 'system'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash userdata userdata.img
sending 'userdata' (18796 KB)... OKAY
writing 'userdata'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash boot boot.img
sending 'boot' (2904 KB)... OKAY
writing 'boot'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery.img
sending 'recovery' (3144 KB)... OKAY
writing 'recovery'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot erase cache
erasing 'cache'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot
rebooting...
C:\Program Files\Android\android-sdk\tools>
That included stock kernel.
Man you might just want to fastboot oem lock and send the phone. Those were factory images... if they don't work it means hw issues.
Sent from my Nexus S 4G using XDA
rasengan82 said:
That included stock kernel.
Man you might just want to fastboot oem lock and send the phone. Those were factory images... if they don't work it means hw issues.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
I agree. If this does not work, send the phone back to Sprint.
I really appreciate y'all trying to help. I will see if Sprint will be kind enough to exchange it. Thanks again.
I think i may have bricked my nexus 10.. I was trying to install the chainfire3d application from the market, and when it rebooted, it wouldnt go past the X logo. waited for a long time, so i tried a hard reset, and still nothing. So i figured i would try using the toolkit to help fix. tried to relock, flash, and re-unlock, and it wouldnt work..after the step where you go into factory reset/wipe, it woudlnt go further. I cant get a custom recovery to install, it wont save the file. tried doing that step separately, and it seems to stick on sending the file over. this seems to be a common issue with anything i try.
The screen says:
"sending TWRP touch recovery..
sending 'recovery' (7246 KB) ...
and is just stuck there. this seems to happen in several places, with a few different things ive tried. When trying to flash the stock image, it will get stuck in similar places, perhaps not with the recovery step, but with a portion of the stock image. Been at this for a couple of hours... any help would be greatly appreciated!.
Also, as of now... it wont boot past the google logo. I can get it into fastboot by holding down the buttons, and I can get it into the stock recovery, but thats it. I don't even think adb is detecting the device. I have a feeling that may be a major roadblock to getting this thing fixed. Does anyone know how I can get the tablet to be detected by adb if i cant even get past the google logo screen at boot?
Update 1:
Still cant unbrick my device. any time i try to transfer or flash files to it... it stalls, and if i disconnect the device, i get this error:
FAILED (data transfer failure (too many links)).
Your Device will now boot into Android and detect ADB mode.
problem is, it doesnt reboot, and even if it did, it wouldnt be able to boot into android, since it wont go past the google logo when the device turns on. in fact, i cant even turn it off. only way to turn it off would be to wait for the battery to drain.
If this helps, here is what it says on the fastboot screen:
Device Information
Product Name: manta
Variant: wifi
H/W version : 8
Bootloader Version: MANTALJ12
Carrier Info: none
Serial Number: *********** (not going to publish that, lol)
LOCK STATE: Unlocked
Reboot Mode Flag: none.
anyone have any ideas at all how I can salvage this thing? Im kindof embarrassed honestly. Ive had 5 android devices prior to this one, and have rooted, flashed, and reflashed each of them countless times, and never, ever ran into this before. I could really use the help.
Quick note:
I just noticed that when i try to flash anything to the tablet, the following appears under the rest of the info i listed above.
FASTBOOT STATUS - DATA00713800 (this text is highlighted in light blue)
Update 2:
ok, so i tried to do the factory restore, and am running into the same wall as always. here is the text from the window, perhaps that may clue you into the problem:
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.tg
z
Extracting mantaray-jop40c-factory-0d641789.tar
Everything is Ok
Size: 329369600
Compressed: 326396069
Now extracting flashable Images
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.ta
r
Extracting mantaray-jop40c
Extracting mantaray-jop40c\image-mantaray-jop40c.zip
Extracting mantaray-jop40c\flash-base.sh
Extracting mantaray-jop40c\bootloader-manta-mantalj12.img
Extracting mantaray-jop40c\flash-all.sh
Extracting mantaray-jop40c\flash-all.bat
Everything is Ok
Folders: 1
Files: 5
Size: 329358105
Compressed: 329369600
Factory Images extracted. Starting Flash Process.
Now Flashing Bootloader Image..
sending 'bootloader' (1280 KB)... OKAY [ 0.232s]
writing 'bootloader'... OKAY [ 0.113s]
finished. total time: 0.345s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
Now Flashing Factory Image: Boot, Cache, Recovery, System and Userdata..
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.002s]
sending 'boot' (4606 KB)...
Its just stuck on that last part, sending 'boot' (4606 KB)...
and under all the info on the fastboot page, the following appeared while this was happening:
FASTBOOT STATUS - DATA0047f800 (this line is highlighted in light blue)
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
can you link it?
cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
trying that....
so far so good... dont want to get my hopes up though... below is what ive got so far in the cmd screen:
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
Its been about 30 minutes now... and its still stuck on "sending 'system' (528847 KB)..." in the cmd window.... not sure what that means... it did take about a minute for the recovery to get sent over, and its about 100x larger in size, so i guess i will leave it connected like this for the next hour or so... and hope that it is just going REALLY slowly. Got my fingers crossed...
Battery died while waiting.... this is the complete text of the CMD screen while i was waiting.. forgot that it doesnt charge while in fastboot. got it plugged into an outlet for faster charging while its off.... hopefully when its charged up, i can try again and ill continue to progress
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3941.094s
Press any key to exit...
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
jodvova said:
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
Click to expand...
Click to collapse
I cant get it to load a custom recovery! any advice on how to get that going?
ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
Dumb question, if using a desktop PC are you using the front or rear USB ports? I had a similar issue where it would just get stuck on the "sending system" message. Switched the USB from front port to back port on my linux box and it solved my problem.
Sent from my Nexus 10 using Tapatalk 2
jodvova said:
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
Click to expand...
Click to collapse
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
ltracte said:
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
Click to expand...
Click to collapse
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
jodvova said:
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
Click to expand...
Click to collapse
couldnt get the command to work via adb, so i tried it using terminal inside TWRP, and this what it spit back at me:
/dev/block/platform/dw_mmc.0/by-name/system: clean. 11/51296 files. 6651/204800 blocks
i have no idea what that means, nor what else to do....
Fixed it!!!!
ltracte said:
Fixed it!!!!
Click to expand...
Click to collapse
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
mskip said:
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
Click to expand...
Click to collapse
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Whew! So glad you finally had success & thanks for sharing. I'm reading up, research, etc. I received my N10 yesterday. I'm getting ready to unlock/root today.
Sent from my Nexus 7 using Tapatalk 2
ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
Hmm, did you try the flash-all.bat file that comes with the factory image? It does those 3 commands, + erases all partitions automatically.
ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
That's exactly what I did. Just followed the factory image flashing instruction on google's page(where you download the image file for N10). Did you figure out why it wassnt able to transfer the first time?
Hey guys. Hoping to get some assistance here. My N10 seems to always freeze on the google (with the unlock icon) screen. I was coming from Mr Robinson's Buttered AOKP 4.2.2 to PAC MAN 4.3. I performed a factory reset and formated my data. Flashed the appropraite ROM and GAPPS after which I performed a reboot. This is when it decided to freeze up. Saw this and said to myself "no biggie" and repeated the aforementioned steps again just in case there was an error on my part. After performing this again it was a success. Started up the setup procedure and began downloading TBU to restore my apps. After downloading TBU I turned it off, took a break, and about 15 minutes later, powered it back on and to my surprise it was stuck on the Google screen again. I thought maybe the ROM file I flashed was corrupted so I tried flashing CM 10.2, and a few others. Every initial boot after installation I have no problems but any reboot afterwards brings me back to the frozen Google screen. At this point I'm stuck. Anyone have any ideas? Suggestions? Any help will be appreciated.
The Google screen represents the bootloader, and has nothing to do with the ROM. Two reasons I could think of.
1. Your bootloader's funky. I find that hard to believe, but it's possible. A full factory image flash(including manually erasing the bootloader) would fix this.
2. Your partitions are funky. You may have seen/heard about issues like this from the Kindle Fires I see in your signature. If even one partition is out of place(from a bad flash or otherwise) the system will refuse to boot. It sounds like it's either the userdata(media) or the cache partition, seeing as how the system boots fine once, but gets corrupted later(when these partitions get altered). Again, a full factory flash should fix this issue.
Or it could be something really simple, but that's all I've got. I've never heard of this issue before.
Just my luck to have an uncommon issue lol. I did notice now that when I boot into the bootloader on my way to recovery it always starts being stuck in download mode and only after holding down all of the buttons does it allow me to use the volume buttons to select starting up in recovery. The tablet also doesnt want to stay shut off and immediately reboots after powering off. What you said definitely makes sense especially with the two other issues I just mentioned. Definitely wont be the quickest fix and wqs hoping that there would be a quicker remedy but off course will do it if I have to. Are the root and unlock steps similar to the methods of the earlier versions of Jelly Bean? How does one go about manually deleting the bootloader?
Sent from my SGH-I317 using Tapatalk 4
Koopa777 said:
The Google screen represents the bootloader, and has nothing to do with the ROM. Two reasons I could think of.
1. Your bootloader's funky. I find that hard to believe, but it's possible. A full factory image flash(including manually erasing the bootloader) would fix this.
2. Your partitions are funky. You may have seen/heard about issues like this from the Kindle Fires I see in your signature. If even one partition is out of place(from a bad flash or otherwise) the system will refuse to boot. It sounds like it's either the userdata(media) or the cache partition, seeing as how the system boots fine once, but gets corrupted later(when these partitions get altered). Again, a full factory flash should fix this issue.
Or it could be something really simple, but that's all I've got. I've never heard of this issue before.
Click to expand...
Click to collapse
I think I have a similar problem myself. However, my device wont boot into bootloader. It won't turn on. How would you typically do a full factory image flash if that's the case?
I also got some message when I tried to flash my device saying that it failed to update the partition table, so that matches what you just said.
I'll update this post with a guide for both of you later tonight, as I'm out of town. IBalic, try to press and hold all 3 buttons to attempt to boot into fastboot. If that doesn't work, put it on the charger for awhile then try.
Sent from my MB855 using xda app-developers app
Koopa777 said:
I'll update this post with a guide for both of you later tonight, as I'm out of town. IBalic, try to press and hold all 3 buttons to attempt to boot into fastboot. If that doesn't work, put it on the charger for awhile then try.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
That would be much appreciated. I was searching around xda earlier and came across a factory 4.3 image thread that also had a seperate bootloader zip file. I'm assuming it wouldn't be that easy but just in case I asked them if there was a way that I could just flash (recovery/fastboot) it to replace the corrupted one.
IBalic said:
I think I have a similar problem myself. However, my device wont boot into bootloader. It won't turn on. How would you typically do a full factory image flash if that's the case?
I also got some message when I tried to flash my device saying that it failed to update the partition table, so that matches what you just said.
Click to expand...
Click to collapse
Hey. I saw a similar issue somewhere else, the tablet simply wouldn't boot, the problem was solved leaving it charging for 1h, then unplugging, putting back while trying to power on and leaving overnight charging. Maybe you can try this .
Gameraddikted said:
That would be much appreciated. I was searching around xda earlier and came across a factory 4.3 image thread that also had a seperate bootloader zip file. I'm assuming it wouldn't be that easy but just in case I asked them if there was a way that I could just flash (recovery/fastboot) it to replace the corrupted one.
Click to expand...
Click to collapse
To factory reset follow this:
Download and get the factory image, I'd recommend you getting them from http://developers.google.com/android/nexus/images.
Extract it and later I'll update this post with a link to a fastboot/adb environment, that way it'll ease your life, if you want to do this now, extract the zip to your fastboot folder, plug your tablet on bootloader mode and type the following:
Code:
flash-all.bat
After that, if worked, you may got it flashed back to stock. If you're with partitions problem, then I'll think a little more and try to solve your problems for you .
Disclaimer: I'm not responsible for any damage!
Cheers,
~Lord
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
XxLordxX said:
Hey. I saw a similar issue somewhere else, the tablet simply wouldn't boot, the problem was solved leaving it charging for 1h, then unplugging, putting back while trying to power on and leaving overnight charging. Maybe you can try this .
To factory reset follow this:
Download and get the factory image, I'd recommend you getting them from http://developers.google.com/android/nexus/images.
Extract it and later I'll update this post with a link to a fastboot/adb environment, that way it'll ease your life, if you want to do this now, extract the zip to your fastboot folder, plug your tablet on bootloader mode and type the following:
Code:
flash-all.bat
After that, if worked, you may got it flashed back to stock. If you're with partitions problem, then I'll think a little more and try to solve your problems for you .
Disclaimer: I'm not responsible for any damage!
Cheers,
~Lord
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I appreciate the help. I downloaded the factory image via the link you provided. When you say extracting the zip file to my fastboot folder do you mean my adroid-adb (aka. platform-tools) folder? Should I make a separate folder or just put everything in the root? Just to get the ball rolling I extracted the download to the root of the folder and ran the flash-all.bat command which started but kicked out some errors. I also noticed that the actual image is "zipped" inside the tgz file. Should I extract that as well or leave it be? Thanks
Gameraddikted said:
I appreciate the help. I downloaded the factory image via the link you provided. When you say extracting the zip file to my fastboot folder do you mean my adroid-adb (aka. platform-tools) folder? Should I make a separate folder or just put everything in the root? Just to get the ball rolling I extracted the download to the root of the folder and ran the flash-all.bat command which started but kicked out some errors. I also noticed that the actual image is "zipped" inside the tgz file. Should I extract that as well or leave it be? Thanks
Click to expand...
Click to collapse
As far as I remember the file you downloaded contains a folder with some files, if you feel more convenient copy all the files in the platform-tools to a new folder and copy also the files from the extracted download to this folder as well, then try again. If you don't get again, please send me the error report and the flash-all.bat file .
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
XxLordxX said:
As far as I remember the file you downloaded contains a folder with some files, if you feel more convenient copy all the files in the platform-tools to a new folder and copy also the files from the extracted download to this folder as well, then try again. If you don't get again, please send me the error report and the flash-all.bat file .
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Click to expand...
Click to collapse
I tried both ways just in case. One with the embedded zip file extracted and the other "as is." This is the error I'm receiving although afterwards attempting it seems everything (bootloader, recovery, etc) has been deleted just as the command prompt states but for some reason they weren't replaced by the factory items:
C:\Users\Ben>flash-all.bat
erasing 'boot'...
OKAY [ 0.027s]
finished. total time: 0.027s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.094s]
finished. total time: 0.095s
erasing 'recovery'...
OKAY [ 0.025s]
finished. total time: 0.026s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.149s]
finished. total time: 0.150s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.456s]
finished. total time: 0.457s
error: cannot load 'bootloader-manta-mantamd03.img': Unknown error
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
error: failed to load 'image-mantaray-jwr66v.zip': No error
Press any key to exit...
Gameraddikted said:
I tried both ways just in case. One with the embedded zip file extracted and the other "as is." This is the error I'm receiving although afterwards attempting it seems everything (bootloader, recovery, etc) has been deleted just as the command prompt states but for some reason they weren't replaced by the factory items:
C:\Users\Ben>flash-all.bat
erasing 'boot'...
OKAY [ 0.027s]
finished. total time: 0.027s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.094s]
finished. total time: 0.095s
erasing 'recovery'...
OKAY [ 0.025s]
finished. total time: 0.026s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.149s]
finished. total time: 0.150s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.456s]
finished. total time: 0.457s
error: cannot load 'bootloader-manta-mantamd03.img': Unknown error
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
error: failed to load 'image-mantaray-jwr66v.zip': No error
Press any key to exit...
Click to expand...
Click to collapse
Hmm... Let's try doing it manually then. The partitions are already formated so it's all cool. Extract the zip, you'll get a few .img files, copy them all to your fastboot folder, plug you Nexus in bootloader mode then open a cmd there. Type:
Code:
fastboot flash bootloader bootloader-manta-mantamd3.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot reboot
If this doesn't solve the issue I'll send you a reply later when I arrive home. Thanks for the patience
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
XxLordxX said:
Hmm... Let's try doing it manually then. The partitions are already formated so it's all cool. Extract the zip, you'll get a few .img files, copy them all to your fastboot folder, plug you Nexus in bootloader mode then open a cmd there. Type:
Code:
fastboot flash bootloader bootloader-manta-mantamd3.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot reboot
If this doesn't solve the issue I'll send you a reply later when I arrive home. Thanks for the patience
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Click to expand...
Click to collapse
Boom! This worked perfectly! Thanks so much for your help. I'm up and running again on PAC. Now if I can only figure out a way to restore my game backups for games that require extra downloads. Off to the forums again. Thanks again for your help :thumbup:
Sent from my SGH-I317 using Tapatalk 4
Yeah, I think the title is enough. The factory images are live now for volantis and volantisg. Maybe we can collect here some first impressions. I am unfortunately not able to flash atm.
https://developers.google.com/android/nexus/images
Flash-all script worked like a charm, setting everything up right now
But it's not February yet.
maarten08 said:
Flash-all script worked like a charm, setting everything up right now
Click to expand...
Click to collapse
Cool man , I'm waiting for your review, , but I'm sure to flash this into my N9 tomorrow . I'm just too eager to wait any longer
Good thing I reverted my n9 back to stock. Will flash tonight. No Ota also.
Flash.sh fail
maarten08 said:
Flash-all script worked like a charm, setting everything up right now
Click to expand...
Click to collapse
Mine fails at sending 'system' (2245234 KB)...
FAILED (remote: data length is too large)
Trying to do a manual flash now... we'll see!
I'll be flashing my 9 tonight too.
I kept my 6 on Lollipop rather than running the preview on it, but yesterday I did flash the preview so that it would use M's auto backup. That way I can flash it this week and not worry about signing into apps.....which is nice during tax season.
PhoenixIce22 said:
Mine fails at sending 'system' (2245234 KB)...
FAILED (remote: data length is too large)
Trying to do a manual flash now... we'll see!
Click to expand...
Click to collapse
Do u have latest fastboot? That error was happening to others because of old fastboot. Otherwise maybe just make sure the hash matches and u have a good download and usb debugging is on.
Sent from my SM-G900V using Tapatalk
Anybody tried flashing yet? I keep getting 'system cannot be loaded' error whilst carrying out manual flash. i.e. fastboot flash system system.img etc etc
I flashed each .IMG file separately, formatted date to remove encryption, flashed TWRP, flashed fed-patcher them FIRE-ICE kernel. Running great here
I was on 5.1.1 (Latest Image). I applied the 6.0 update, now I am just sitting at the black Google Screen and it won't boot. Any suggestions???
Diesel779 said:
I flashed each .IMG file separately, formatted date to remove encryption, flashed TWRP, flashed fed-patcher them FIRE-ICE kernel. Running great here
Click to expand...
Click to collapse
Do u need fed patcher if u flash a kernel that does not force encryption? I thought you wouldn't. Haven't tried it though.
Brian
Sent from my SM-G900V using Tapatalk
Is the installing process for rooted devices the same as for the former builds?
like here:
http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
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
gt43aw said:
Do u need fed patcher if u flash a kernel that does not force encryption? I thought you wouldn't. Haven't tried it though.
Brian
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
You don't need FED patcher if you flash an already un-force-encrypted kernel. FED patcher just takes the stock kernel and un-force-encrypts it.
Haven't updated my flashing VM in a while, so likely not. I know my ADB is 1.0.32, not sure what version of fastboot I have on there. I'm a bit of a Ubuntu noob, so I'm doing lots of web researching, LOL
Be sure to update the bootloader if getting a system partition size error! For M-preview this went from 3.44.1.0123 (LMY48M) to 3.48.0.0135 (confirmed the factory image is still this for MRA58K)... Otherwise you get system partition size errors (BIG update).
I will be making a rooted/no-force-encrypt ROM and kernel as soon as I see the newer manifests on googlesource... I am assuming selinux to permissive is still required for root. Once you have it unpacked:
fastboot flash bootloader bootloader-flounder-3.48.0.0135.img
fastboot reboot-bootloader
Then flash the system and boot images:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot flash system system.img
DO NOT DO THIS if your device is using a no-force-encrypt kernel! You WILL have to factory reset! Back up OFF the device to a PC or OTG FIRST... Then you can restore.
While flashing SYSTEM it will send the update in 5 chunks - from my device:
target reported max download size of 518205818 bytes
erasing 'system'...
OKAY [ 0.869s]
sending sparse 'system' (499853 KB)...
OKAY [ 26.326s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.701s]
sending sparse 'system' (495930 KB)...
OKAY [ 25.524s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 20.212s]
sending sparse 'system' (495450 KB)...
OKAY [ 25.732s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.792s]
sending sparse 'system' (443364 KB)...
OKAY [ 22.984s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.222s]
sending sparse 'system' (310634 KB)...
OKAY [ 16.188s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 12.593s]
finished. total time: 209.162s
NOOB Question:
where can I get the Information if my kernel is "no-force-encrypt kernel"?
I'm using the stock kernel 3.10.40 (28.jul) build LMY48M (rooted)
UDPATE:
in Settings -> security -> enrcypt tablet-> encrypted: means "force-encrypt kernel"?
Deleted
No force encryption stock kernel
For those who want to flash Marshmallow immediately but wanted to keep the device un-encrypted, download this zip, extract the boot image and flash through fastboot.
Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.
I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...
Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.
Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?
Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again
Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .
Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img