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
Related
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
I didn't to a NANDROID backup before trying to flash a new ROM (fail I know). I had factory reset my phone before flashing the new ROM, but the ROM that was flashed hasn't installed correctly and the phone no longer powers completely on. I would like to just throw a different ROM/gapps on the SD card, but I can no longer access it on my computer since the phone will not completely boot up.
Someone suggested somewhere that I mount the USB Storage from recovery, but in the mount + storage recovery section all I see is mount /data, mount /system, and mount /cache, none of which make the GNEX storage available on my computer.
Any suggestions for fixing this problem, or for simply accessing the SD card on my computer without the phone turning completely on?
Thank you.
You can adb push a ROM while booted in a custom recovery. You should check out the stickies in this forum & the general forum.
Download the factory image from google for your phone. Extract it and get system.img from it (you have to extract it a few times). Get adb/fastboot setup by installing the correct drivers and the android sdk (there may be files posted here at xda with just the files needed for adb/fastboot). Then put system.img in the same folder as fastboot.exe (assuming you use windows).
Connect your phone while in bootloader (both volume keys + power) and from a command prompt in that directory, type:
1) fastboot flash system system.img
2) fastboot reboot
It won't wipe anything other than /system.
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Paybacks1 said:
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Click to expand...
Click to collapse
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
mwalt2 said:
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
Click to expand...
Click to collapse
Paybacks1 said:
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Click to expand...
Click to collapse
I have the same problem. Going to take a look at what mwalt suggested tomorrow. Paybacks, if you find a solution, can you please post it here? Thanks.
mwalt2 said:
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
Click to expand...
Click to collapse
I was finally able to flash the system.img from Google, but see no change. What is expected to happen once this .img has been pushed?
EDIT: Ended up flashing the entire .zip installation instead of just the system.img file and I have a stock install atm. Thank you for the help!
To Man_Utd, I ended up just re-executing the superboot r5 while in bootloader and it seemed to help recognize the phone..-shrug-.
i'm having bootloop after installing 17/02/2013 CM10.1 rom on my gsm gnex. the issues are:
1. i don't have any previous working cm10 rom saved in phone's sdcard.
2. can't get adb working, maybe because i never enabled usb debugging mode before.
fyi, i have never flashed any other roms, just CM roms. please assist..
Go into recovery and transfer a new Rom download to your phone if you have a computer. There is an option to transfer files inside recovery.
eqjunkie829 said:
Go into recovery and transfer a new Rom download to your phone if you have a computer. There is an option to transfer files inside recovery.
Click to expand...
Click to collapse
that requires adb (adb_sideload- correct me if i'm wrong).. my adb is not working.. can't boot to android.. can't find a way to enable usb debugging mode.. so no adb..
Do you have a custom recovery or experience with fastboot? Boot a recovery image via "fastboot boot recoveryname*.img", and adb is enabled.
bodh said:
Do you have a custom recovery or experience with fastboot? Boot a recovery image via "fastboot boot recoveryname*.img", and adb is enabled.
Click to expand...
Click to collapse
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
[email protected] said:
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
Click to expand...
Click to collapse
Attached is clockworkmod touch recovery for gsm galaxy nexus, maguro. Phone in bootloader mode, open a terminal, cd to directory of fastboot and where you move this file to, type fastboot devices to verify device is connected, then "fastboot boot CWMT6023.img", without the quotes of course. This will temporarily allow you to use clockworkmod recovery, and thus adb, without having it on your device once you have selected "reboot now".
And if that didn't help, try consulting http://forum.xda-developers.com/showthread.php?t=1626895, since i'm thinking you haven't used fastboot in a terminal, but only know it's 'mode', and may need help with drivers.
You also might want to consider just straight out flashing cwm recovery, since YOU NEED TO MAKE BACKUPS!
[email protected] said:
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
Click to expand...
Click to collapse
If u don't have a custom recovery how did u flash cm10?
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
If u don't have a custom recovery how did u flash cm10?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
sorry, i got cwm. but what does fastboot have to do with cwm? i can't use cwm to restore because files can't be sent from computer to it.
as of fastboot in terminal, it seems the phone not connected to computer. is there anything has to do with my drivers? "fastboot device" command shows <waiting for device>
I gave you that link to set up drivers more than anything else. If you already have cwm, boot to it and now you can adb push a rom.zip to your sdcard and install it, wipe caches and perhaps a factory reset [if you're changing to a different rom], OR, you can first try and wipe cache and advanced, dalvik cache to see if that fixes the bootloop.
1. Why didn't you make a backup?
2. Why didn't you make sure you know how to get out of this situation before flashing new ROMs?
3. Search as there are LOTS of tutorials on how to use adb to side load a new ROM via CWM
EddyOS said:
1. Why didn't you make a backup?
2. Why didn't you make sure you know how to get out of this situation before flashing new ROMs?
3. Search as there are LOTS of tutorials on how to use adb to side load a new ROM via CWM
Click to expand...
Click to collapse
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
[email protected] said:
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
Click to expand...
Click to collapse
If you think that then you have no idea on how adb works...
That is ONLY applicable when Android is running. As it's not, it's irrelevant...
[email protected] said:
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
Click to expand...
Click to collapse
ADB should work in your custom recovery regardless of USB debugging being enabled or disabled.
I can't tell you how many times I have rebooted into recovery, wiped, then realized I forgot to put a file on my sdcard that I wanted to flash. I then use adb to push the file(s) from within the recovery.
Edit: I really need to refresh prior to responding.
so i can't get adb working because of the driver? thats why i got "waiting for device" when pushing file to phone?
edit: i've installed all the required drivers, it's not my 1st time doing it. MAYBE, this computer never connected to my gnex before, as i've formatted it a few days ago. So the gnex driver was not properly installed.. Is it possible?
If that version of cm 10 is for 4.2.2., then i think you may have an issue accessing adb without first getting the rsa verification, even in recovery (but im not sure). Looks like your only other option would be to fastboot flash stock images. And of course it sounds like driver issues, especially if your fastboot is not even working. Again, that link I posted will get you back up and running. http://forum.xda-developers.com/showthread.php?t=1626895
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
_______________________________________
Hello.
First, if this post is on wrong place, sorry. Please move it, if necessary.
So, I have a chinese clone of Sony C6. It is rooted, based on MT6580, but I don't know how or why, my kid messed up something, and now it is stuck at logo screen after restart. So, I searched for a way to flash it to brand new with a ROM dump I made some days ago with 'dd'.
It also was bootloader unlocked, but I don't know why, it locked again when I tried to flash the backup files I have (maybe I locked for so many tries to flash). It refused to re-unlock. Maybe I need to go settings and enable "allow oem unlocking" under developer settings, but as the phone don't boot, this is not an option. BTW, the fastboot mode of this phone don't have a lot of commands, is very simple. Don't have even the 'fastboot oem ?' command. It flashed boot and recovery when unlocked, but when I tried to flash system, it gives an error of 'unknow command' when erasing system. So, tried with -u option, but gives another error about 'unknow chunk size'. Searches about this don't give me anything helpful.
Some other things I tried:
Downloaded a compatible ROM for this phone (the original simply don't exists), checked the scatter file, and replace relevant files with my backup, to use with SP Flash Tools, but the download never starts. I checked the drivers and everything else and are all correct. Tried on another computer with different operating system, but it simply don't start the download. Maybe isn't compatible with my phone;
Use 'fastboot flash system', but as sayed above, with locked bootloader I can't flash the files anymore at this mode;
Make a flashable ROM on SuperR's kitchen to flash with adb sideload (as stock recovery can't flash this), but it ended with 'installation aborted' just after start;
Tried to make a CWM recovery through CWM builder, and flash the ROM made by kitchen, but it gives 'bad gateway' at the end. Tried to build one in a ubuntu virtual machine, but it can't sync the repo, so I can't build one.
On the kitchen, I sucessfully modified and flashed recovery to allow ADB commands (as the original gives me 'unauthorized'), but in the actual state, it even can't mount system, giving an '/system/bin/sh not found' error.
So, I have a working stock recovery with ADB and also fastboot mode working, but none of them helped. I need help to make that CWM, or another way to have the phone working.
Attached is the modified recovery and original boot images. Can someone please convert it for me?
Also, any suggestions in how I can put the phone working will be helpful.
Thanks in advice.