Develop Bugs

[Q] Flashing system.img to a bricked handset

Ok, now i've read through various magic and dream forums, and i think i've got this, but i wanted to check...it's not my phone and i don't want to get fired
I could tell you all the background that got me to this point, but it's really long winded and would bore you to death.
Basically, i have been given a bricked phone that i need to recover for the company i work for. Someone tried to update it with a heroimg.zip file and it trashed it.
Fastboot and Hboot work fine and i only have the boot.img, system.img and recovery.img files to do it.
If i understand this right, i should be able to flash these img files to the device while in fastboot.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot recovery recovery.img
fastboot reboot
Should that work? I've happily used the amon RA recovery to do update.zip updates on my own phones, but company procedures and stuff won't let me do anything other than leave it as standard.
I don't claim to understand adb/fastboot really, but i think those are the commands i need to flash the img files across manually.
am i right? Just hoping someone here who is a lot more intelligent than I can just confirm it before i totally kill the damn thing!​

Don't know if this helps, but Paul has the 'stock' shipping (ie unmodified and unrooted) update.zip files on Modaco here
You could use the latest one of these after Fastbooting the latest AmonRA. That way, you're not flashing AmonRA to the device or anything like that. This should give you a stock Hero with no modifications to it.
But then again, your company might not like this either. In that case, I haven't tried those commands, but they should, in theory, work (I've used 1 or 2 to flash a custom boot.img so I could modify the ramdisk, but that's about it for me)

that's why i figured they might work...i've used the boot.img one to flash a recover on mine, but i was just working from a 'how to guide'.
still not got my head around the commands yet. Not as confident playing with these things as i was on WinMo in the past...

any chance you boot the custom recovery from fastboot and flash the update.zip from there?

maddie said:
any chance you boot the custom recovery from fastboot and flash the update.zip from there?
Click to expand...
Click to collapse
TBH, if you're not comfortable with the commands for flashing yet, I would not try and learn on a work phone.
To do it this way, as suggested before, download an update.zip from Modaco for the latest 'stock' official Hero build.
Now download the latest AmonRA recovery image and put it in a folder to hand. Rename it to recovery.img for ease of typing later on.
Install the Android SDK if you don't have it already, and boot the phone to fastboot (Power + Back IIRC)
Now type into a command prompt window
Code:
fastboot devices
and make sure the phone's serial number appears.
Code:
fastboot boot C:\recovery.img
to boot the custom AmonRA recovery image (not the stock one!)
Optional step here is to do a 'wipe' if there is something wrong with the data (user) partition, but this depends on circumstances.
Once in the recovery image, choose to apply a named update file, and point it to the file on the root of the SD Card (put it there from within Windows Explorer. You will need to use a card reader or another phone to do this since this one is 'bricked'.
Now wait patiently for the flash to happen. It is usually done for me in 10 mins when flashing a Modaco ROM, but if it stops working, DO NOT TURN IT OFF OR UNPLUG THE BATTERY!!! (sorry for caps, but it's really important as this seems to be no.1 cause of proper 'bricks')
Phone should then reboot into new ROM.

I should add ... that following the anon2122 guide will leave your phone "stock" as in... there will be no way to tell that anything has been done... no lasting recovery image, a stock ROM etc etc..
anon2122's method is the way to go.
Your method wont work unless the phone has an "S-OFF" SPL... You likely don't! If you happen to ... then your steps will work fine. Although ... You may also need to wipe the user data if the phone doesn't boot after your steps!
Code:
fastboot erase cache
fastboot erase userdata

Thanks for all the tips guys, they did indeed help.
In the end, it turned out that the phone was S-Off, as we do tend to get some test rigs in at various points.
I've got the recovery image already installed on my personal phone, but for various reasons couldn;t use it in this case.
But thatnks for the help, and it's all working now.
And yes, i did need to do a wipe afterwards.
Thanks all. That's some more commands i understand now.

Good to hear that it worked.
Thanks for letting us know, since it is all too often that the OP doesn't let others who may find this thread in future know whether the fix worked or not.

well, that's why i responded. It winds me up no end when people don;t bother to tell you if it worked or not.
And i did learn something new as i was not aware of the erase commands. Yet another thing to add to my little box of tricks....

BRICKED Galaxy Nexus - please help me restore/advice

Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
This ISN'T Resolved. I get errors when attempting to fastboot the stock image
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
If anybody has any ideas please let me know, I really don't know what to do at this point.

grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Okay your bootloader is unlocked which is good, but your MAC doesn't see your phone in bootloader mode?

grnmons said:
Plan B is to use a PC which I can only access later in the week.
Click to expand...
Click to collapse
Can you bootcamp or use a virtual machine?

grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Wrong section..but
I would def use a PC and use Odin ! Make your life easier...it takes like 3-5 Mins..takes it to stock!
Sent from my Galaxy Nexus using xda premium

All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Sent from my Galaxy Nexus using Tapatalk

Please uninstall and reinstall your phones drivers. Your just soft bricked is all. Once your computer sees the device you should be good.
sent from the Almighty One himself....

borgey said:
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Click to expand...
Click to collapse
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?

grnmons said:
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
Click to expand...
Click to collapse
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html

zephiK said:
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Thanks. Can you confirm that these are the steps?
1) Download the latest stock image( i will leave finding that image to you since this post can become outdated)
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock and Unrooted

~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'

anybody have any other suggestions to this? or a follow up?

It should be easy to fix. You do not seem to have the correct driver installed.
Sent from my Galaxy Nexus using xda premium

Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.

grnmons said:
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
Click to expand...
Click to collapse
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)

ogdobber said:
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
Click to expand...
Click to collapse
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?

grnmons said:
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
Click to expand...
Click to collapse
download the gnex-su.zip and put in in the root of your sd card. then in recovery select "-install zip from sdcard" then "-choose zip from sdcard" then select the gnex-su.zip. this will give you root and install the superuser app

not to get ahead (previous post), but after your computer recognizes the phone you need to flash clockwork recovery
you need to open a terminal in the platform-tools folder of the sdk (also put the recovery.img there) and then
Code:
fastboot flash recovery name-of-recovery.img

Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Just got your last post, I'm unfamiliar with SDK but I've since put the recovery file in there, not sure how to flash recovery. I have tried flashing recovery through terminal and surprisingly it says "-bash: fastboot: command not found"

grnmons said:
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Click to expand...
Click to collapse
that is for the nexus s
check your pm

ogdobber said:
that is for the nexus s
check your pm
Click to expand...
Click to collapse
If you are still having problems ...like I said before ...use Odin......since the simple process of fastboot is not working properly for you.Odin makes things so Much easier
Sent from my Galaxy Nexus using xda premium

[Q] Phone only starting in Clockwork and Fastboot

After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance

luminuss3 said:
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
Click to expand...
Click to collapse
Your boot image is missing...
When your phone boots in bootloadermode, it should (now, anyway) say: boot.img missing. Or something of that nature. Check this, flash it via fastboot, then everything should be back to normal...
EDIT:
It works with both: CDMA & GSM

luminuss3 said:
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
Click to expand...
Click to collapse
do you know how to use fastboot and adb?

Excuse my lack of knowledge, but how exactly do I flash something over fastboot? Thanks in advance again.
Edit: And I do know how to use adb, however it does not connect. I do not know how to use fastboot

After some playing around with fastboot, I now have a basic understanding. However, I am not sure where I should be flashing that file you have linked.

Today, a friend suggested I try mounting via, and copying roms over that way. However, even with all the drivers installed on my computer, I get nothing.
If anyone has ANY insight on this problem, it would be be greatly appreciated. My new toy is a brick at the moment
Thanks in advance!

luminuss3 said:
Today, a friend suggested I try mounting via, and copying roms over that way. However, even with all the drivers installed on my computer, I get nothing.
If anyone has ANY insight on this problem, it would be be greatly appreciated. My new toy is a brick at the moment
Thanks in advance!
Click to expand...
Click to collapse
I'd seriously try to go back to stock first. I'm not a Windows user but if you have adb, fastboot, and your drivers setup, it should be easy. Mark is a great help in this thread and you can use his script I guess:
http://forum.xda-developers.com/showthread.php?t=1400871
You need to also realize that if you have wiped everything to install a new rom, you have nothing to boot to. Also there is install-recovery.sh file that keeps re-writing your recovery to stock erasing custom recovery (CWR) until you rename or erase that file. So going back to stock would be the safest and then you can try again.
You can use adb in recovery and fastboot in bootloader. If you have everything setup correctly (sdk, adb, fastboot, drivers for windows) either of these commands should recognize your phone:
In Bootloader (the first screen you see with big arrow on top):
Code:
fastboot devices
In recovery:
Code:
adb devices
If you don't have a recovery, then use the first one. If you see your phone's serial number like this
Code:
List of devices attached
HT12HS005115 device
you can now use it to flash things onto your phone. As I said I am not a windows user so I can't be specific, sorry. But adb and fastboot, once you are at their prompt, should work the same.
In general, when fastboot is recognizing your phone in the bootloader, you can use:
Code:
fastboot flash zip YOURFILENAME.zip
changing yourfilename of course. This zip file could be a stock imaqe or a custom recovery. Again, you need someone with windows to give you exact steps, this is just general stuff.

if your phone is yakju build then you can get the stock images from google.
download and unzip the files to your fastboot folder and use these commands, the file names in these commands are for the Android 4.0.1 (ITL41F) build so you will have to change the filenames if you use a different build.
Code:
fastboot devices (to make sure your phone is connect to fastboot)
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip

[Q] bootloader help

im in bootloader menu on my htc. i lost superuser access, and all root apps wont work either. im tryin to update superuser but cant get anything to work. please help

It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM
If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?
For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.
Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?
If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.
Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en
ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu
Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053

projektorboy said:
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM
If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?
For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.
Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?
If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.
Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en
ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu
Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053
Click to expand...
Click to collapse
i ran rummer a month or so ago. i had s-off and on bootloader menu it says unlocked. when i click on recovery it just reboots. when i first did this i never flashed twrp. i did a root check when i did rumrunner it said root access granted. now when i check it it says no root access, and my superuser is gone. i tried dl all sdk again, but i cant get comp to find phone in cmp. i also tried to launch rumrunner again ,, it rebooted phone few times then ended with stupid problems with phone press enter to exit. im about to throw in towel after hours of trying different things..

projektorboy said:
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM
If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?
For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.
Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?
If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.
Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en
ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu
Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053
Click to expand...
Click to collapse
this also all started after verizon came out with update and phone automatically updated but unsuccusfully

Thank you for re-affirming my suspicion that an OTA put you in this position.
Rumrunner wasn't ever going to help you in your situation. Rumrunner is purely for achieving S-OFF. Since you're still S-OFF, it didn't have anything to do with your phone. Your root access is gone because the OTA wiped it out. It's important to always be careful about OTA updates because OTA updates assume that you NEVER modified your phone and will write whatever they want to wherever they want.
Since you can at least get to the bootloader, your phone can be saved. You said that you tried to update your SDK so that you could have the fastboot files available. When you run the SDK updater (I assume you're on Windows) you have to right-click and run as Administrator to make it work.
The files you want for fastboot are hiding in c:\program files (x86)\Android\android-sdk\platform-tools\
Take adb.exe, fastboot.exe, adbwinapi.dll, and adbwinusbapi.dll and copy them to a separate folder. (Such as C:\adb\) Navigate to that folder and do shift+right-click in a blank area of the folder so you can run a command prompt. You will want to put a ROM and a recovery file in this same folder too. (You sound like you want the stock ROM)
Use the command 'fastboot devices' to see if the phone shows up. If the phone doesn't show up, then you need to go to the HTC Website so you can install HTC Sync, then remove Sync (while leaving the drivers behind) so that your phone has the correct drivers to make it show up in fastboot.
If 'fastboot devices' ends up revealing a device, then you can grab a custom recovery image file and do "fastboot flash recovery filename.img" to put a custom recovery in your phone. Then within the custom recovery you can do adb sideload romname.zip to install a ROM and that should put your phone back into a usable state.

projektorboy said:
Thank you for re-affirming my suspicion that an OTA put you in this position.
Rumrunner wasn't ever going to help you in your situation. Rumrunner is purely for achieving S-OFF. Since you're still S-OFF, it didn't have anything to do with your phone. Your root access is gone because the OTA wiped it out. It's important to always be careful about OTA updates because OTA updates assume that you NEVER modified your phone and will write whatever they want to wherever they want.
Since you can at least get to the bootloader, your phone can be saved. You said that you tried to update your SDK so that you could have the fastboot files available. When you run the SDK updater (I assume you're on Windows) you have to right-click and run as Administrator to make it work.
The files you want for fastboot are hiding in c:\program files (x86)\Android\android-sdk\platform-tools\
Take adb.exe, fastboot.exe, adbwinapi.dll, and adbwinusbapi.dll and copy them to a separate folder. (Such as C:\adb\) Navigate to that folder and do shift+right-click in a blank area of the folder so you can run a command prompt. You will want to put a ROM and a recovery file in this same folder too. (You sound like you want the stock ROM)
Use the command 'fastboot devices' to see if the phone shows up. If the phone doesn't show up, then you need to go to the HTC Website so you can install HTC Sync, then remove Sync (while leaving the drivers behind) so that your phone has the correct drivers to make it show up in fastboot.
If 'fastboot devices' ends up revealing a device, then you can grab a custom recovery image file and do "fastboot flash recovery filename.img" to put a custom recovery in your phone. Then within the custom recovery you can do adb sideload romname.zip to install a ROM and that should put your phone back into a usable state.
Click to expand...
Click to collapse
Ty for walk through! Will try tomorrow! I wanna get kit kat on here. I think some problems were from files on comp in wrong folders. Hope this works

soft bricked!?

So I soft bricked my Nexus 7 (flo).... I have root access and I have TWRP installed still... just no files or anything... I could easily fix this if my PC had Windows but currently I only have Ubuntu. All the fixes and guides are for Windows and I need some help trying to sideload a rom in Ubunutu... I tried to adb sideload a rom but only get this error on my PC "cannot read sideload" . Any suggestions on what I can / should do?

You have Ubuntu, and you're sad? Dude, you're better off. Trust me. Now, when you say to t you don't have files, do you mean that TWRP shows 0mb for memory space, or that your internal memory is empty? Either way, I suggest flashing the stock image, if all else fails.
But for now, you could always try adb push to get the file onto the tablet.
And for the record, I only use Ubuntu for flashing nowadays. All you need to know are the right commands to use. Toolkits are an easy solution, but they leave you stranded when something goes wrong....just like now. Besides, you only need to use the commands listed in the Windows guides, and disregard the process of setting up everything for the PC to recognize the device. Linux recognizes Android by default since Android was built from it.
Let me fully explain my two options that I have given you.
Option 1) ADB push - http://forum.xda-developers.com/showthread.php?t=1667929
Locate the file that you want to push to the tablet, and copy it to the '/home' directory. You can always navigate to the file using the 'cd' command, but it's much easier to move the file. In recovery, make sure that the SD is mounted. In Ubuntu, use:
sudo su
adb push RomName.zip /sdcard/RomName.img
Then use the tablet to locate the file and flash it.
If that doesn't work, then you might need:
Option 2) Flash Stock img - https://developers.google.com/android/nexus/images
Download the img for razor. Boot into the bootloader (power + vol down). Then put it in your '/home' directory, and use:
fastboot erase system
fastboot erase userdata
fastboot flash system system.img
fastboot reboot --> When completed
I don't think that it is necessary to wipe before you flash the stock img, but it doesn't hurt to do it. So remember that the stock img will wipe everything, and perform a factory reset. The only thing that it will not do is relock your bootloader, I didn't think. Simply reroot your device
fastboot on unlock --> if necessary
fastboot flash recovery RecoveryName.zip
The flash SuperSU in recovery, or flash the rom of your choice (you will have to use adb push again).
I hope that this helps, and if any of my information is erroneous, please let me know. I'm not a pro at this, but I do know how to get myself out of sticky situations.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel

aarsyl said:
You have Ubuntu, and you're sad? Dude, you're better off. Trust me. Now, when you say to t you don't have files, do you mean that TWRP shows 0mb for memory space, or that your internal memory is empty? Either way, I suggest flashing the stock image, if all else fails.
But for now, you could always try adb push to get the file onto the tablet.
And for the record, I only use Ubuntu for flashing nowadays. All you need to know are the right commands to use. Toolkits are an easy solution, but they leave you stranded when something goes wrong....just like now. Besides, you only need to use the commands listed in the Windows guides, and disregard the process of setting up everything for the PC to recognize the device. Linux recognizes Android by default since Android was built from it.
Let me fully explain my two options that I have given you.
Option 1) ADB push - http://forum.xda-developers.com/showthread.php?t=1667929
Locate the file that you want to push to the tablet, and copy it to the '/home' directory. You can always navigate to the file using the 'cd' command, but it's much easier to move the file. In recovery, make sure that the SD is mounted. In Ubuntu, use:
sudo su
adb push RomName.zip /sdcard/RomName.img
Then use the tablet to locate the file and flash it.
If that doesn't work, then you might need:
Option 2) Flash Stock img - https://developers.google.com/android/nexus/images
Download the img for razor. Boot into the bootloader (power + vol down). Then put it in your '/home' directory, and use:
fastboot erase system
fastboot erase userdata
fastboot flash system system.img
fastboot reboot --> When completed
I don't think that it is necessary to wipe before you flash the stock img, but it doesn't hurt to do it. So remember that the stock img will wipe everything, and perform a factory reset. The only thing that it will not do is relock your bootloader, I didn't think. Simply reroot your device
fastboot on unlock --> if necessary
fastboot flash recovery RecoveryName.zip
The flash SuperSU in recovery, or flash the rom of your choice (you will have to use adb push again).
I hope that this helps, and if any of my information is erroneous, please let me know. I'm not a pro at this, but I do know how to get myself out of sticky situations.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Click to expand...
Click to collapse
I had the 0mb issue but I fixed it on my own! I also tried and push and it didn't work at all... Also I'm not sad I only have Ubuntu easily one of the best operating systems ever! Thanks for all the info I'll retry some of these methods when i get home later! If I still have issues I'll message back on here!

No problem.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel

aarsyl said:
No problem.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Click to expand...
Click to collapse
Thanks got it working!!! Was an idiot and typing in one of the commands wrong! Everything is a ok now! Might try some Ubuntu touch dual boot now!

Badouken said:
Thanks got it working!!! Was an idiot and typing in one of the commands wrong! Everything is a ok now! Might try some Ubuntu touch dual boot now!
Click to expand...
Click to collapse
Be careful with that, but have fun! Remember that you need MultiRom to get it to work. Later.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________