Ok, so I unlocked my Nexus 7 (2013). Then I was trying to root it and after booting it into the bootloader, I typed:
"fastboot flash boot twrp.img" I was supposed to type "fastboot flash recovery twrp.img"
PLEASE HELP! My device boots into TWRP EXCLUSIVELY!
How do I get my os back? Is it gone? Can this be easily fixed?
I will be eternally in your debt if you can help me out, I feel so stupid, this is the first time I've bricked something and I've been unlocking, rooting, flashing android devices since my G1, then my Nexus One, which I even repartitioned the system partition so it could fit 4.2.2 Cm 10. I also unlocked, my touch pad and flashed cm dual booting with web os. Unlocking/rooting/flashingcustomrecovery on my Nexus 4 was a one click though so I guess I was rusty.
Edit: messed up a bracket in the title... Great...
I am not an expert, but I think you'll be fine flashing a ROM image as that will install the boot files. I'd get confirmation though.
But no crying!
Sent from my Nexus 7 using xda app-developers app
Coronado is dead said:
I am not an expert, but I think you'll be fine flashing a ROM image as that will install the boot files. I'd get confirmation though.
But no crying!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I don't have a rom image on my device though? How can I get one on there when I can only get into the bootloader or recovery...
Thanks for responding! I hope I can get this fixed...
In TWRP I think there is a way to mount USB and transfer it over. Maybe under advanced?
Sent from my Nexus 7 using xda app-developers app
Hmm maybe someone could make a .zip file to flash the boot loader in twrp
And there is always the option of getting the factory image from Google and using it over USB with fastboot on. Clean slate.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:54 AM ---------- Previous post was at 12:53 AM ----------
How to factory image restore:
http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Sent from my Nexus 7 using xda app-developers app
Flash any custom kernel, as it stands as "boot" partition.
Or just flash the boot image manually from the factory image:
Code:
fastboot flash boot boot.img
Then flash TWRP like normally you did before:
Code:
fastboot flash recovery recovery.img
Sent from my Galaxy S3 i9300
If you can go to bootloader or TWP, then you have many choices to fix your Nexus.
1. Download a factory image from Google, boot to bootloader and flash the whole thing. And remember to download the right factory image for Nexus 7(2013) (flo or razor). Check MD5 after downloading to make sure everything is OK. If you dont know how to flash a factory image, there is a couple topics in General and Q&A to assist you.
2. Or you can download a custom kernel in the Original Development area. THen boot to TWRP, use ADB to push the custom kernel file to your device, then install it by TWRP.
3. You can use a toolkit which I dont recommend.
Ok, so in my frantic attempts to fix this, I was trying to get adb sideload to work and was told to try and do a factory reset and wipe system and internal storage. I did this and still can't figure out how to get sideloading to work, I'm trying adb sideload rom.zip, and adb push rom.zip /sdcard which is what I read from another thread, but have not been able to get the factory image over.
Also, when I go to flash the .img that came with the factory image, fasboot says:
<code>sending 'boot' <2100 KB>....
OKAY [ 0.080s]
writing 'boot'...
FAILED <remote: image is not a boot image>
finished total time: 0.090s
</code>
OH GOD!
Download the Factory Image of Android 4.3 for ‘razor’ Nexus 7 tablet from here.
> this download contains the full system, bootloader, recovery and kernel boot img files.
Extract the ‘tgz’ factory image archive and place all contents into a single folder.
Next, you will need to edit a file so that your data will not be wiped. If you want to wipe data then you should skip this step.
> so, edit the ‘flash-all.bat’ for Windows or ‘flash-all.sh’ for Mac / Linux using a text editing tool:
- you will need to edit the ‘fastboot update’ command so that it will transform from ‘fastboot -w update image-razor-jss15j.zip’ into ‘fastboot update image-razor-jss15j.zip’. You will basically need to delete the ‘-w’ text, which is the command that tells fastboot to wipe data from your device.
- continue to the next step when you’re sure that the ‘-w’ text has been removed.
Now, power off your Nexus 7 2013 tablet.
Boot it into Bootloader Mode.
Connect it with your computer via USB cable.
Run the ‘flash-all’ script and wait for the factory image to be successfully installed.
Ok, so I did this, I downloaded the factory image, and ran the flash all command and that failed and now it's hard bricked! here is a screenshot of what the flash-all command output...
I will seriously pay someone to help me fix this at this point! I'm freaking out!
http://imgur.com/XsAJ4FV
mattj7 said:
Also, when I go to flash the .img that came with the factory image, fasboot says:
<code>sending 'boot' <2100 KB>....
OKAY [ 0.080s]
writing 'boot'...
FAILED <remote: image is not a boot image>
finished total time: 0.090s
</code>
Click to expand...
Click to collapse
You must have done something wrong. The boot.img that came with the factory restore is 6880KB not 2100KB.
Take things slow. You are still in a place where you can recover. If you make too many mistakes, you can make it even harder to recover.
Never mind, the problem had been solved.
sfhub said:
You must have done something wrong. The boot.img that came with the factory restore is 6880KB not 2100KB.
Take things slow. You are still in a place where you can recover. If you make too many mistakes, you can make it even harder to recover.
Click to expand...
Click to collapse
Yes, it was the factory image for the first nexus 7, I just ran the flash all on the right one and now I can boot just fine
WHEW
Ok guys, great job everyone!
Now I'm going to figure out if the custom recovery is still there, it probably isn't, and I can just flash it with fastboot now.
slamdunksaliby said:
Hmm maybe someone could make a .zip file to flash the boot loader in twrp
Click to expand...
Click to collapse
The only way is by the fastboot way, because it's an .img file
And don't forget that you can find all files that you need to this thread => [Index] REPO for all you need for your nexus 7 FLO (2013)
philos64 said:
The only way is by the fastboot way, because it's an .img file
]
Click to expand...
Click to collapse
Well, that is untrue. The bootloader .img is just a collection of other .img that get flashed to their respective partitions, such as aboot, sbl1, sbl2, sbl2b, sbl3, sbl3b, and rpm. :good:
Nburnes said:
Well, that is untrue. The bootloader .img is just a collection of other .img that get flashed to their respective partitions, such as aboot, sbl1, sbl2, sbl2b, sbl3, sbl3b, and rpm. :good:
Click to expand...
Click to collapse
Please I don't agree when you say it's untrue.
For most users, this is the easiest solution for this.
If you do a survey, I would like to see how many people know that you can flash by other means
philos64 said:
Please I don't agree when you say it's untrue.
For most users, this is the easiest solution for this.
If you do a survey, I would like to see how many people know that you can flash by other means
Click to expand...
Click to collapse
Well, I know you can flash by other means.
I don't think he said it was the easiest to flash from twrp. He just said it could be done, which it can.
I think far more people have done it through recovery than have known they have done it.
Everyone who flashes the JSS15J OTA will get the bootloader flashed in the way he described. If twrp is using the same kernel as stock recovery, then it can be done in twrp also.
philos64 said:
Please I don't agree when you say it's untrue.
For most users, this is the easiest solution for this.
If you do a survey, I would like to see how many people know that you can flash by other means
Click to expand...
Click to collapse
I'm not personally attacking you or anything and I am sorry if you took it that way.
I'm just stating that saying fastboot is the only way is not true. The partitions can easily be flashed through CWM/TWRP as they have been with, from my experience, Galaxy Nexus, Nexus 4, and Nexus 7 (2012).
sfhub said:
Well, I know you can flash by other means.
I don't think he said it was the easiest to flash from twrp. He just said it could be done, which it can.
I think far more people have done it through recovery than have known they have done it.
Everyone who flashes the JSS15J OTA will get the bootloader flashed in the way he described. If twrp is using the same kernel as stock recovery, then it can be done in twrp also.
Click to expand...
Click to collapse
Nburnes said:
I'm not personally attacking you or anything and I am sorry if you took it that way.
I'm just stating that saying fastboot is the only way is not true. The partitions can easily be flashed through CWM/TWRP as they have been with, from my experience, Galaxy Nexus, Nexus 4, and Nexus 7 (2012).
Click to expand...
Click to collapse
No problem
But as I said, almost users don't flashed by the way of the partitions.
It would be better to say the easiest way
Sent from my HTC One using Tapatalk 4 between sky and earth
Related
Hi all,
I updated my nexus 7 to 4.2 but decided to revert back to 4.1.2. So I downloaded SDK and followed the instruction by 2defmouze to restore to stock image for 4.1.2 but now it is stuck at the message sending 'system' <446268 KB> in the cmd window and nexus 7 is not responding in anyway with the volume and on/off buttons. The message has been there for more than an hour. Is there anyway to help to restore it back to anything operational?
Thanks for the help!
Same Problem
quastenflosser said:
Hi all,
I updated my nexus 7 to 4.2 but decided to revert back to 4.1.2. So I downloaded SDK and followed the instruction by 2defmouze to restore to stock image for 4.1.2 but now it is stuck at the message sending 'system' <446268 KB> in the cmd window and nexus 7 is not responding in anyway with the volume and on/off buttons. The message has been there for more than an hour. Is there anyway to help to restore it back to anything operational?
Thanks for the help!
Click to expand...
Click to collapse
Same Problem here.
Trying to flash Stock Rom 4.2 from google servers. Tried with the toolkit (Step9) first and then via flash-all.bat in cmd window.
No results, stuck @ "sending system". Before it stucks it says in the cmd window "archive doesn't contain 'boot.sig', 'Recovery.sig' and 'system.sig'.
Please anyone knows what to do and could help us fellas?
Thanks from Germany,
Trip
i have the exact same problem as the above poster except my Nexus is bricked, well not actually bricked but a bad flash and i ended up erasing data and trying to flash stock image JXO 54K, ,this is my second attempt to do this, yesterday ive no idea what went wrong, this evening ive got as far as "sending system 446268 KB" and its just stuck on that now for ages, i did notice that it said
archive does not contain "boot -sig"
archive does not contain "recovery-sig"
archive does not contain "system-sig"
so am i to assume this didnt flash properly or what could i be doing wrong?
jonny68 said:
i have the exact same problem as the above poster except my Nexus is bricked, well not actually bricked but a bad flash and i ended up erasing data and trying to flash stock image JXO 54K, ,this is my second attempt to do this, yesterday ive no idea what went wrong, this evening ive got as far as "sending system 446268 KB" and its just stuck on that now for ages, i did notice that it said
archive does not contain "boot -sig"
archive does not contain "recovery-sig"
archive does not contain "system-sig"
so am i to assume this didnt flash properly or what could i be doing wrong?
Click to expand...
Click to collapse
The sticky thread indicates it's supposed to say that. You can try flashing the images manually also.
Sent from my SGH-I777 using xda premium
korockinout13 said:
The sticky thread indicates it's supposed to say that. You can try flashing the images manually also.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok that's fine but it wouldn't move on from where it said "sending system", how long is it supposed to stay on that, after half an hour I gave up and me Nexus is still dead.
Another thing when I boot into fastboot mode and click on recovery it won't appear, instead I see am image of a "dead android",
Sent from my GT-I9300 using xda app-developers app
jonny68 said:
Ok that's fine but it wouldn't move on from where it said "sending system", how long is it supposed to stay on that, after half an hour I gave up and me Nexus is still dead.
Another thing when I boot into fastboot mode and click on recovery it won't appear, instead I see am image of a "dead android",
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
That's the stock recovery. Try flashing either CWM or TWRP via fastboot (I recommend TWRP), that should get you back into a usable recovery. From there you can push a flashable zip of some kind to it and flash it through recovery.
As for the original problem, have you checked either the MD5 or SHA1 checksum to make sure it was a good download? Have you tried downloading again? Not sure what else could be the issue here.
Anybody able to figure out why their Nexus became unresponsive. or how to get it to work?
Having the same issue. When flashing my Nexus was bricked during sending system does the same everytime I try to flash it.
rdelarosa3 said:
Anybody able to figure out why their Nexus became unresponsive. or how to get it to work?
Having the same issue. When flashing my Nexus was bricked during sending system does the same everytime I try to flash it.
Click to expand...
Click to collapse
A Nexus 7 is not "bricked" if it has a (correctly functioning) bootloader or a (working) custom recovery. It might be OK to call this "soft-bricked", though.
If you have a flaky connection between the PC and the tablet, the most likely place for a communication error to occur is when a whole lot of data is transferred. For flashing via fastboot, this usually tends to be the system partition, simply because it is tremendously larger than anything else which is flashed via fastboot. (The problem could also be on the tablet - a communication data corruption problem is only one of several possible hazards.)
So, there are at least two workarounds:
(1) avoid flashing where the file must be transferred (fastboot or adb sideload) - choose a "recovery-flashable" ROM and use the recovery to perform flashing of /system. Note that it is reported that you can NOT flash factory "system.img" files as a raw partition - apparently they are in a sparse ext4 image file format that bootloader (fastboot) understands, but are not the same as a block-by-block copy of an ext4 filesystem. So, we are talking about a "custom ROM" here, not a pure factory ROM.
(2) switch to a different cable / USB port on the PC, etc and see if you get a different result flashing the system.img file using fastboot.
(Note that if you experience stuff like this - strangeness in transferring files "across the wire", you should avoid flashing the bootloader using fastboot under any circumstances using the same setup - it is simply too dangerous to make a mistake with the bootloader. There are other ways to update the bootloader that are far, far, safer.)
good luck
Is it possible on an unlocked nexus 7 to effectively install a custom ROM from fastboot with the command "fastboot update </path/to/your/RomFile.zip>" without using a custom recovery such as TWRP?
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Fastboot is used to flash .img file not .zip
norcal61 said:
Is it possible on an unlocked nexus 7 to effectively install a custom ROM from fastboot with the command "fastboot update </path/to/your/RomFile.zip>" without using a custom recovery such as TWRP?
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
What you can do is fastboot flash system system.img.
system.img can come from a backup, a google stock image or make it yourself
So there is no way to flash an actual zip file via fastboot? I found this article here on xda http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Why would you want to? Flash recovery with fastboot and flash your ROM from there.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
Why would you want to? Flash recovery with fastboot and flash your ROM from there.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I want to be able to format my internal SD from TWRP which would wipe everything off the SD including any zip files then flash the zip from my computer from a command prompt with the tablet booted into the boot loader.
Sent from my Nexus 7 using Xparent Green Tapatalk 2
norcal61 said:
I want to be able to format my internal SD from TWRP which would wipe everything off the SD including any zip files then flash the zip from my computer from a command prompt with the tablet booted into the boot loader.
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
That's quite pointless to format everything... But in this case, you can adb sideload the zip from recovery. No need for the file on the sd card.
Sent from my Nexus 7 using Tapatalk HD
norcal61 said:
So there is no way to flash an actual zip file via fastboot? I found this article here on xda http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Only STOCK factory ROMs are flashable this way...
cf. this line from the flash-all.* script for the full factory image of Jellybean 4.2.2.. for 'grouper'.
Code:
fastboot -w update image-nakasi-jdq39.zip
In image-nakasi-jdq39.zip the following files are found...
boot.img
recovery.img
system.img
userdata.img
----
CUSTOM ROMs, however, can only be flashed via a CUSTOM RECOVERY, such as CWM or TWRP.
And as korockinout13 alludes to, it's a trivial matter to FASTBOOT FLASH a custom recovery... and then flash the ROM of your choice.
If you already have FASTBOOT (and your question suggests that you do)... then what's the problem?
Rgrds,
Ged.
The bootloaders of different Android devices have differing capabilities precisely because they are proprietary. Moreover, it is the bootloader that actually implements the heavy lifting of installs etc - the PC fastboot program does little more than send ASCII commands and push blobs of data across the USB cable.
Some Android devices have had bootloaders that understand how to unpack .zip files that contain other types of archives (.tar files, et cetera) but required that the .zip file is placed onto an external SD card using a standardized name for that device. (When the bootloader starts up, it would look for that file automatically). But this was for signed factory bundles, not for arbitrary aftermarket customization. In any event, this doesn't apply to the N7 afaik.
None of these behaviors are standardized though; each vendor decides how it will interpret and respond to fastboot commands from the PC.
The N7 bootloader clearly understands what a sparse ext4 image file is (for use with system.img and userdata.img files) - if it handled them as a pure binary blob, how would it be possible to use the same userdata.img file with 8Gb, 16Gb, and 32Gb devices? Moreover, the N7's "fastboot format" command clearly is capable of creating ext4 filesystems.
So would it be possible to create "sparse ext4" system.img/userdata.img image files corresponding to a custom ROM that could flashed in exactly the same way as the factory image using fastboot? Yes, absolutely. (I've done just that.)
But this is NOT the same thing as taking a custom ROM .zip file (intended to be processed by a recovery using an "edify" script) and flashing it with fast boot; it ain't that easy.
hi,
i have a nexus 7 and i want to flash a custom rom but i wiped everything and the zip gone from my tablet now the tablet is without os,please help!!
paul20 said:
hi,
i have a nexus 7 and i want to flash a custom rom but i wiped everything and the zip gone from my tablet now the tablet is without os,please help!!
Click to expand...
Click to collapse
Better to stick with stock and not attempt to flash custom ROMs if you don't know how to use a custom recovery or toolkit.
paul20 said:
hi,
i have a nexus 7 and i want to flash a custom rom but i wiped everything and the zip gone from my tablet now the tablet is without os,please help!!
Click to expand...
Click to collapse
Not a big deal. You need to download the factory image for your nexus 7 and find instructions on how to restore with fastboot. That will take you back to factory stock. Or another option is to fastboot flash TWRP custom recovery and use the adb sideload feature within TWRP to flash a custom ROM of your choice. You can find instructions on both of these procedures here at xda or with a simple Google search. Let me know if that works out for you. If you need more help I can give you a hand when I get home from work
Sent from my Nexus 7 using Xparent Green Tapatalk 2
everything okay i flashed stock rom with the toolkit and then the custom one,it's ok now i am not so noob but it's my first tablet without external sd card and i got panik
thanks everyone
paul20 said:
hi,
i have a nexus 7 and i want to flash a custom rom but i wiped everything and the zip gone from my tablet now the tablet is without os,please help!!
Click to expand...
Click to collapse
Fastboot flash a custom recovery. Then, there are many threads showing how to get the .zip to the device for flashing.
Sent from my Nexus 7 using xda premium
norcal61 said:
Not a big deal. You need to download the factory image for your nexus 7 and find instructions on how to restore with fastboot. That will take you back to factory stock. Or another option is to fastboot flash TWRP custom recovery and use the adb sideload feature within TWRP to flash a custom ROM of your choice. You can find instructions on both of these procedures here at xda or with a simple Google search. Let me know if that works out for you. If you need more help I can give you a hand when I get home from work
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Hey guys,
I made the same mistake as paul20 with my HTC ONE and your answer saved my morning, thanks! adb sideload feature rocks!
rebel1699 said:
Fastboot flash a custom recovery. Then, there are many threads showing how to get the .zip to the device for flashing.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Can you point me to one of those threads?
fastboot error
GedBlake said:
Only STOCK factory ROMs are flashable this way...
cf. this line from the flash-all.* script for the full factory image of Jellybean 4.2.2.. for 'grouper'.
Code:
fastboot -w update image-nakasi-jdq39.zip
In image-nakasi-jdq39.zip the following files are found...
boot.img
recovery.img
system.img
userdata.img
----
CUSTOM ROMs, however, can only be flashed via a CUSTOM RECOVERY, such as CWM or TWRP.
And as korockinout13 alludes to, it's a trivial matter to FASTBOOT FLASH a custom recovery... and then flash the ROM of your choice.
If you already have FASTBOOT (and your question suggests that you do)... then what's the problem?
Rgrds,
Ged.
Click to expand...
Click to collapse
========================================
the fastboot says --
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
i m porting the stock rom (it is a zip file) which has boot.img ,recovery.img ,system.img ,userdata.img into it yet the error comes.
the prob is that the rom is not detecting my sd card and neither the CWM i tried a different sd card yet it isnt detecting...i alst tried mounting sd card it showed error there also! plz help me! everything was working sommoth! this problem came after i ported droid_dd_gb_13.3 v3 ...my device is micromax a57 plz help mee!!!
GedBlake said:
Only STOCK factory ROMs are flashable this way...
cf. this line from the flash-all.* script for the full factory image of Jellybean 4.2.2.. for 'grouper'.
Code:
fastboot -w update image-nakasi-jdq39.zip
In image-nakasi-jdq39.zip the following files are found...
boot.img
recovery.img
system.img
userdata.img
----
CUSTOM ROMs, however, can only be flashed via a CUSTOM RECOVERY, such as CWM or TWRP.
And as korockinout13 alludes to, it's a trivial matter to FASTBOOT FLASH a custom recovery... and then flash the ROM of your choice.
If you already have FASTBOOT (and your question suggests that you do)... then what's the problem?
Rgrds,
Ged.
Click to expand...
Click to collapse
where do you get those .img files from?? bY the way im using sony xperia sp and bricked i guess ;(
no adb, can't enable USB debugging
korockinout13 said:
That's quite pointless to format everything... But in this case, you can adb sideload the zip from recovery. No need for the file on the sd card.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
What if you can't enable USB debugging because you accidentally formated /persist and can't get into your system? 16 hours of that arrow turning and nothing...
Can someone help me, I have same problem but i extracted my Zip file and have Boot.img if i flash that will it work again
My N10 no longer has any OS on it, and can't do anything other than boot into the bootloader or TWRP. How can I get my tablet operating again?
MrJazzbo said:
My N10 no longer has any OS on it, and can't do anything other than boot into the bootloader or TWRP. How can I get my tablet operating again?
Click to expand...
Click to collapse
I would recommend either flashing a new ROM or if you want to restore to bone stock factory out of the box condition I would recommend flashing the Nexus 10 factory image found here https://dl.google.com/dl/android/aosp/mantaray-jdq39-factory-d79f489e.tgz.
Sent from my SCH-I535 using xda premium
MrJazzbo said:
My N10 no longer has any OS on it, and can't do anything other than boot into the bootloader or TWRP. How can I get my tablet operating again?
Click to expand...
Click to collapse
I tend to take a FAT32-formatted flash drive, USB OTG cable, throw a custom ROM, Kernel, and Gapps onto the flash drive's root, reboot the tablet to TWRP, wipe everything (except USB OTG) and format data, reboot back to recovery, and then install ROM, Gapps, and Kernel (in that order).
In other words, if you have a flash drive and OTG cable, you can recover your device pretty easily If you don't have these though, you can adb push the zip's over to /sdcard I believe; it's been awhile since I've done this.
If you want to go back to factory stock, you can grab the latest factory image from the link shimp208 provided, and should be able to run the flash-all.bat included (may have to have platform-tools in PATH if running Windows, or cd into the folder).
I don't have a usb otg cable, how would I go about pushing the zips to my device?
Download Koushik's naked USB driver here:
https://github.com/koush/UniversalAdbDriver
Then you can use adb sideload while in TWRP's sideload mode.
dibblebill said:
Download Koushik's naked USB driver here:
https://github.com/koush/UniversalAdbDriver
Then you can use adb sideload while in TWRP's sideload mode.
Click to expand...
Click to collapse
Or use ADB (available under platform tools on android SDK) to push a ROM, all the bells and whistles, to /sdcard/. Yes, it's still available @espionage724
espionage724 said:
(may have to have platform-tools in PATH if running Windows, or cd into the folder).
Click to expand...
Click to collapse
The same applies to ADB binary.
Sent from my Nexus
bk201doesntexist said:
Or use ADB (available under platform tools on android SDK) to push a ROM, all the bells and whistles, to /sdcard/. Yes, it's still available @espionage724
The same applies to ADB binary.
Sent from my Nexus
Click to expand...
Click to collapse
I always have trouble sideloading in CWM/TWRP with the stock drivers. ADB never sees the recovery's sideloader.
MrJazzbo said:
My N10 no longer has any OS on it, and can't do anything other than boot into the bootloader or TWRP. How can I get my tablet operating again?
Click to expand...
Click to collapse
same problem....pls help me
Same problem to, tried stock image via fastboot. Oem Lock/unlock, removed added twrp. Sided loaded and flashed custom rom, but nothing works.
Sensing back to Samsung hopefully they'll cover it under warranty.
Sent from my GT-N7105 using XDA Premium HD app
Are you using the Nexus 10 Toolkit or Wugfresh's Toolkit? I once wiped all my data including on the SD (oops no files to flash), which is why I don't flash stuff after a few beers anymore. LOL In that situation, I was able to transfer the files (ROM & gapps) to the N10 while in TWRP using one of the toolkits.
Worst case, you should be able to odin back for factory as well.
These answers are good, but can't get fastboot to work. Can get into bootloader though
v941726 said:
These answers are good, but can't get fastboot to work. Can get into bootloader though
Click to expand...
Click to collapse
What problems are you having with fastboot?
shimp208 said:
What problems are you having with fastboot?
Click to expand...
Click to collapse
Can't get into it. I can only get into bootloader
v941726 said:
Can't get into it. I can only get into bootloader
Click to expand...
Click to collapse
Do you have fastboot setup on your computer correctly? In order for fastboot to function properly you must first boot into your devices bootloader then navigate to the directory where you have ADB and fastboot setup on your computer, and run commands from that directory (Or if you have fastboot and adb added to your system path you can run if from any directory).
Yes. Finally. When you don't have an external SD card and there is nothing on your tablet at all, it's tough. I couldn't get an answer till now. But I ended up figuring it out myself after countless hours. Wish I got this sooner. Thanks tons though
Sent from my Nexus 10 using xda app-developers app
v941726 said:
Yes. Finally. When you don't have an external SD card and there is nothing on your tablet at all, it's tough. I couldn't get an answer till now. But I ended up figuring it out myself after countless hours. Wish I got this sooner. Thanks tons though
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Great job. Unfortunately, I have been there before. I learned to never try to flash after a few drinks. You hit the wrong buttons and don't realize it. LOL
Very true.
Now I can't get krt16s to flash. Some metadata error. So I have a feeling that something happened with last fiasco.
SGS4
v941726 said:
Very true.
Now I can't get krt16s to flash. Some metadata error. So I have a feeling that something happened with last fiasco.
SGS4
Click to expand...
Click to collapse
I'm assuming your talking about the latest factory image? Are you trying to flash that in recovery or fastboot because you should use fastboot to flash the factory image. What you can do is manually erase each partition in fastboot (Backup your data first) and then manually flash each of the factory images partitions i.e boot.img, system.img, userdata.img, etc. to update your device.
shimp208 said:
I'm assuming your talking about the latest factory image? Are you trying to flash that in recovery or fastboot because you should use fastboot to flash the factory image. What you can do is manually erase each partition in fastboot (Backup your data first) and then manually flash each of the factory images partitions i.e boot.img, system.img, userdata.img, etc. to update your device.
Click to expand...
Click to collapse
Yes. The krt16s. Thank you for that. I will keep this for future use. But again I was ahead of you and got it to work with the nexus root toolkit v1.7.8. Your way is easier though it sounds.
hello everyone..
In serious need of help here and hope someone can help..
Due to the massive battery drain issue I have been having, I tried to flash the original stock rom on my nexus 7 and
things have gone downhill really bad..
in the past, I flashed using this guide (http://forum.xda-developers.com/showthread.php?t=1907796)
without any problems but last night.. I encountered errors when trying to flash the bootloader
and radio IMG files.. neeedless to say when it comes to flashing the rom in, it came out with errors and my nexus remain OS-less
the errors when trying to flash the bootloader and radio are
"failed (command write failed (Invalid Argument))"
can anyone help me?
p.s :- if anyone can even suggest me a easier way to flash custom roms in and so forth, your suggestion will be most welcomed..
also, I did try wug's rootkit plus the nexus 7 toolkit or something, both came out errors too when too do any flashing in relating to
the bootloader or system.. thanks
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Username invalid said:
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Click to expand...
Click to collapse
actually, my bootloader boots fine, it shows tilapia 4.18.
so does this mean I dont have to flash it?
if I dont have to flash the bootloader, do I have to flash the radio?
sorry, kind of a noob in these things..
Anyway, is it normal for the bootloader flash attempt to fail?
hamiksu said:
Anyway, is it normal for the bootloader flash attempt to fail?
Click to expand...
Click to collapse
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
korockinout13 said:
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
Click to expand...
Click to collapse
hmm, ok..
then I will go back home and do the system flashing and try and post out the errors it stated there..
really hope to get my nexus back on line...
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
hamiksu said:
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
Click to expand...
Click to collapse
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
it says my bootloader is already unlocked
hamiksu said:
it says my bootloader is already unlocked
Click to expand...
Click to collapse
Then it sounds like something happened to your system partition that should not have happened.
Are you sure the system image you're trying to flash is valid, do the md5 sums match?
How about flashing another system image?
Or flash a custom recovery, and install a new ROM from there?
ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
ameinild said:
Then it sounds like something happened to your system partition that should not have happened. Sorry, can't help you there...
Click to expand...
Click to collapse
meaning my system partition is screwed?
anyone knows how to go around this problem?
p.s :- anyway ameinild, thanks for trying to help
hamiksu said:
p.s :- anyway ameinild, thanks for trying to help
Click to expand...
Click to collapse
I edited my post with some more suggestions to try first
ameinild said:
I edited my post with some more suggestions to try first
Click to expand...
Click to collapse
yup, the image i tried a few.. even tried stock rom image.
tried both nexus 7 toolkit
as well as wugs nexus root tool kit.
they all seem to encounter problems when trying to "push" the rom images in or something.
is there a way to like format the entire thing and install from scratch>?
hamiksu said:
is there a way to like format the entire thing and install from scratch>?
Click to expand...
Click to collapse
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
ameinild said:
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
Click to expand...
Click to collapse
Yea, I hope someone will pop in and be my guardian angel too..
Thanks again, Ameinild
tried to flash stock rom using wug's rootkit..
this is what happens...
hamiksu said:
tried to flash stock rom using wug's rootkit..
this is what happens...
Click to expand...
Click to collapse
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Rirere said:
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Click to expand...
Click to collapse
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
I'm assuming you haven't tried this yet, if you have tried this just ignore.
1 - Download - http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.6.0.0-grouper.img
2 - fastboot flash recovery openrecovery-twrp-2.6.0.0-grouper.img
If flashes fine:
Power off Nexus, Hold Volume down and Power on, keep holding power down until you get to recovery.
Then:
Either - Get a USB OTG and put a ROM on a USB Stick, go to "install" - "Use external storage" find the rom and flash it.
or
Plug in to PC whilst in recovery, - Mount Storage - Now the Nexus should pop up on PC, Drag ROM to Nexus. Unmount and then try to flash.
Let me know how you get on with this.
Regards.
hamiksu said:
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
Click to expand...
Click to collapse
That's because you have stock recovery installed now and it's unable to verify that your device is in working order, hence the red mark. Find TWRP for your device, download the .img and try to flash it with fastboot flash recovery <path-to-recovery.img>. Since you can at least get into a recovery, it's possible you'll be able to use onboard recovery tools to see what state your internal partitions are in.
Until there's a little more info available, there's nothing I can say that's not pure conjecture.
I was restoring a twrp backup and when it reaches "flashing system image" in the restore process it just reboots. Ive tried a few things but cant get it going. It just bootloops.
dontbeweakvato said:
I was restoring a twrp backup and when it reaches "flashing system image" in the restore process it just reboots. Ive tried a few things but cant get it going. It just bootloops.
Click to expand...
Click to collapse
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Heisenberg said:
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Click to expand...
Click to collapse
That was my first rooted twrp backup on 6p. I checked everything under what to backup. It has a system and system image to backup along with everything else. I thought it was weird to have both of them because I've never seen that before in twrp.
Well im back to normal. I must of screwed up the restore with the "system" and "system image" business. What's the difference in twrp restore between the two?
dontbeweakvato said:
Well im back to normal. I must of screwed up the restore with the "system" and "system image" business. What's the difference in twrp restore between the two?
Click to expand...
Click to collapse
Honestly, I don't know. I only know that you only need to backup system, boot, and data (if you want your apps and settings).
Heisenberg said:
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Click to expand...
Click to collapse
I have a soft bricked phone... I have done everything in your thread and flashing all the files worked except i get an error when flashing the system.img
it says error unable to allocate xxxxxxx bytes...? i really want my phone back to normal.. PLEAS HELP
taylorleach said:
I have a soft bricked phone... I have done everything in your thread and flashing all the files worked except i get an error when flashing the system.img
it says error unable to allocate xxxxxxx bytes...? i really want my phone back to normal.. PLEAS HELP
Click to expand...
Click to collapse
Try to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files.
indian84 said:
Try to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files.
Click to expand...
Click to collapse
I am sorry what do you mean?? what commands should I try?
taylorleach said:
I am sorry what do you mean?? what commands should I try?
Click to expand...
Click to collapse
Try this.
Reboot Bootloader again
1. fastboot erase userdata
And then follow the guide. Hopefully this will help.
indian84 said:
Try this.
Reboot Bootloader again
1. fastboot erase userdata
And then follow the guide. Hopefully this will help.
Click to expand...
Click to collapse
so, just to clarify... run the command "fastboot erase userdata" then run all of the IMG files?
taylorleach said:
so, just to clarify... run the command "fastboot erase userdata" then run all of the IMG files?
Click to expand...
Click to collapse
My bad.
use command fastboot format userdata
This will erase everything on your phone. Including photos and all the media.
After this use below command
fastboot reboot bootloader
And then follow guide and flash all IMG files.
indian84 said:
My bad.
use command fastboot format userdata
This will erase everything on your phone. Including photos and all the media.
After this use below command
fastboot reboot bootloader
And then follow guide and flash all IMG files.
Click to expand...
Click to collapse
that did not work same problem
"load_file: could not allocate 2014315040 bytes
error: cannot load 'C:\angler\images\system.img"
all other .img files i get OKAY except for system.img
PLEASE HELP ME UGG I REALLY NEED MY PHONE TO WORK AGAIN. I even tried re downloading the 6.0.1 again and also tried rebooting PC and multiple USB ports...
taylorleach said:
that did not work same problem
"load_file: could not allocate 2014315040 bytes
error: cannot load 'C:\angler\images\system.img"
all other .img files i get OKAY except for system.img
PLEASE HELP ME UGG I REALLY NEED MY PHONE TO WORK AGAIN. I even tried re downloading the 6.0.1 again and also tried rebooting PC and multiple USB ports...
Click to expand...
Click to collapse
You need to update your fastboot on your PC update everything in Android SDK or install latest minimal adb and fastboot. The system needs to be sent/flashed in parts as it's a big file. That will/should fix your issue.
matt1515 said:
You need to update your fastboot on your PC update everything in Android SDK or install latest minimal adb and fastboot. The system needs to be sent/flashed in parts as it's a big file. That will/should fix your issue.
Click to expand...
Click to collapse
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
taylorleach said:
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
Click to expand...
Click to collapse
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
taylorleach said:
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
Click to expand...
Click to collapse
matt1515 said:
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
Click to expand...
Click to collapse
If you already have the Android SDK it probably isn't a good idea to start installing other versions. Just go to where you installed the SDK on your PC, open SDK Manager, and update the platform-tools package.
matt1515 said:
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
Click to expand...
Click to collapse
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
taylorleach said:
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
Click to expand...
Click to collapse
Yes that's why it was stuck in a boot loop, the version of SuperSU that's included in TWRP is incompatible. Which version of TWRP did you flash? You need the latest in order for it to be able to successfully decrypt your storage so you can view it.
Heisenberg said:
Yes that's why it was stuck in a boot loop, the version of SuperSU that's included in TWRP is incompatible. Which version of TWRP did you flash? You need the latest in order for it to be able to successfully decrypt your storage so you can view it.
Click to expand...
Click to collapse
To be honest, I moved the file to my phones directory from my PC and did not just copy it so I lost it lol. Could you please tell me what one I should flash so I don't mess anything up. PLEASE and THANK YOU
taylorleach said:
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
Click to expand...
Click to collapse
+1 on Heisenberg you should use Android SDK and update properly but I knew you needed to get back up and running and figured that was the fastest way to help you. Read his thread like you would a book you will learn all you need to learn! But glad to hear I was able to help! Always use latest TWRP and SuperSU and you will be fine if you can decrypt then install SuperSU that way if not just hit cancel and adb sideload it. Look in general thread for the TWRP thread. Good luck and enjoy your working phone again!