Database Info

[Q] How to push rom to internal sd using ADB

SO here goes...
first off i am on a mac, rooted, have all appropriate drivers, etc, have used dab to root.
I am a total newb, and was experiencing issues flashing a new ROM. when trying to install the zip through cwm the phone said "signature verification failed" or something to that extent. so being the deductive thinker that I am, I formatted everything: boot, system, sd, etc. After doing this, I realized that I totally wiped out all the files on the internal sd.
so i downloaded the heimdall one click- it connects but fails regardless of whether i flash boot loader.
i can access red cwm and download mode.
now. i want to know if it is possible to push or even install a ROM through adb. I've been playing around with it all day and have gotten nowhere.
i thought maybe i could load up a rom to an external sd but obviously you can't mount an extsd in cwm.
am i screwed?
ill gladly donate through paypal if someone can help me get my baby up and running again. i do not want to be using my nokia from middle school anymore!!
thank you in advance for ANY help you can give me.
Rob

I replied in another thread, but here goes again.. since you have adb working, this should be fairly easy. In CWM, go to 'mounts and storage' and mount /sdcard. Then, just adb push your ROM .zip to /sdcard like so: adb push /path/to/zip /sdcard
You can then flash the zip in CWM.

LinuxBozo, I seems to have run into the same situation. Would you mind elaborating a bit? Should I have the phone connected when I mount /sdcard? My PC does not recognize it no matter what I do, so I cannot push the stock ROM onto it. Much appreciate your help if possible.

I had similar problems when I accidentally wiped /system without having a ROM on my internal SD. I was fortunate though that I had the Infuse Toolkit which has a ROM built in it so I flashed that.
However, before I did that, I was also trying to push a ROM via adb while in CWM. It seemed that for whatever reason, it just refused to work. I could get a shell open, but when trying to push files, I would get a protocol error (you have to leave it and wait a while to see the protocol error).
I'm curious to know if you get this working, because with the red CWM, I couldn't even mount an external sd, so I was a bit worried that there was no way for me to flash a ROM (I didn't realize there's special drivers for Heimdall, so I couldn't use any of those one-clicks either).

[Q] unable to mount USB storage with CWM

I trying to flash new ROM
PC is able to use fastboot utilities ok but just wont detect it as a removable storage device so i cant load any ROMS onto the SD
i try to mount USB with CWM and it gives the error E:Unable to write to ums lunfile (No such file or directory)
if i let the phone try to boot normaly i get about 10 seconds of home screen and it reboots and cycle continues.
but while phone is connected and running home screen i get a new CD drive which i cant access and also device manager reports HTC with drivers required.
problem is HTC dont have drivers and phone re boots within 10 or so seconds and when it does the device vanishes
ive read through all the threads with similar issues but none have solved my problem.
my phone is bricked until i solve this and im freaking out cause its only 5 days old.
ive been reading forum for past 2 days and nothing has helped me

USB mount has never worked on CWM for our device (Snapdragon S4 version of the One X). Its a known issue.
CWM doesn't really support our device, its just a port. And it has huge issues (USB mount being just one of them) because of that. You can install a custom recovery that actually supports our device, TWRP. Head over to the Development forum and find the TWRP thread, and it should tell you how to flash TWRP over adb.
Most (if not all) of our devs recommend being on TWRP.

I am not able to mount sd card from cwm
can't partition non -vfat error

[Q] stuck in boot loop

I've got my tf300t stuck in a boot loop when i turned it on today. (Ive looked around the forums for this issue already and been able to find little or no solutions that work for me)
I'm using cm10 and twrp. last night i shut the tablet off as usual and go to turn it on today and i cant get past the white asus logo and device unlocked screen.
I can access my twrp recovery menu, wiping dalvik returns a "E:Unable to mount '/data' (tw_mount)" cache wipes fine no errors.
I'm unable to flash another rom or restore from a back up as well.
Fastboot says its working but in cmd prompt it wont list the device. (computer recognizes it and it shows in device manager as android adb interface)
If there is any other information needed I will be more than happy to provide it.
any tips or help is greatly appreciated.
thanks in advanced.

I'm not yet very fammiliar yet with TF300, but from SGS 1 and ICS I remember one trick. If you have external microSD pluged, take it out or of you don't have it plug it in and then enter TWRP.
It probably won't work but you can try anyway.
Does TWRP have any file browser? I'm using CWM so I don't know much about TWRP.

stenc55 said:
I'm not yet very fammiliar yet with TF300, but from SGS 1 and ICS I remember one trick. If you have external microSD pluged, take it out or of you don't have it plug it in and then enter TWRP.
It probably won't work but you can try anyway.
Does TWRP have any file browser? I'm using CWM so I don't know much about TWRP.
Click to expand...
Click to collapse
Yeah it does have the file browser, upon initial booting i can browse an sd card ( i have a few of various sizes none seem to to be having any affect) and i can browse the internal storage as well. Booting both with and without the sd card in the device still leaves me in the boot loop.

So, can you copy new rom to sd card, then copy from sd to internal and install new rom? I think only option you have is to reinstall rom.

stenc55 said:
So, can you copy new rom to sd card, then copy from sd to internal and install new rom? I think only option you have is to reinstall rom.
Click to expand...
Click to collapse
I can and have tried but it wont let me flash with the "unable to mount /data" error. It tells that my external sd-card and whatever rom i attempt to flash has problems

Hagenator said:
I can and have tried but it wont let me flash with the "unable to mount /data" error. It tells that my external sd-card and whatever rom i attempt to flash has problems
Click to expand...
Click to collapse
Be sure your sdk is up to date.
1. If you hold volume down plus power button to get to fastboot.
2. shift + control right click fastboot folder on computer then open command prompt.
3. type devices... and if it is not showing a device there something is not right.
4. you can try adb push to apply a flash if your device is not wanting to flash from sd card.

M
Repairtech123 said:
Be sure your sdk is up to date.
1. If you hold volume down plus power button to get to fastboot.
2. shift + control right click fastboot folder on computer then open command prompt.
3. type devices... and if it is not showing a device there something is not right.
4. you can try adb push to apply a flash if your device is not wanting to flash from sd card.
Click to expand...
Click to collapse
I've tried this as well. It was my first thought. Also it states in my original post that fastboot doesnt list my device, adb doesnt list it as well. Both are recent and up to date. However device manager does recognize it and windows makes the little notification sound. In safely remove devices it shows up as fastboot when i enable fastboot on the device.

[Q] Soft Bricked tab, no custom recovery and no way of selecting USB debugging option

So i soft bricked my device while trying to install the latest 4.0.1 image. I tried hard wiping the device and wipe cache partion from Stock Recovery but didn't help, still wouldn't boot. I tried installing the image in Stock Recovery from Apply Update From External SD Card, but i got a few errors first "E:Failed to map file Operation aborted", i took a look at the file and it had about 1.67gb extra in "Userdata" i tried deleting that file and reinstalling from external sd card but then i got "E:footer is wrong" "E:signature verification failed" Operation Aborted.
Now i'm trying to install update from ADB (Surprisingly if i have the tab connected and im in Apply Update from ADB the tab is recognized in ADB
Code:
adb devices
serial # sideload and i have updated the drivers) But if i try to flash the recovery file 4.0.1 (provided from the developers site [cant post links]) "i just get waiting for device"
Anyone know how to get around this issue in ADB or properly install from external sd card without getting errors?
(Alternative read to my problem posted in the Nvidia Forums 98% sure i soft bricked my device [cant post links]

Did you ever find a fix? I'm having a similar problem.

Try to use fastboot restore everything.

I can't get it to connect to fastboot. When it loads the boot loader and I try to select fastboot protocol it fails.

Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!

rom fiend said:
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
Click to expand...
Click to collapse
Yes flash a ROM in recovery.
Try Resurrection Remix. It'll resurrect your device

Just tried flashing bliss 6.2 and it won't get past the nvidia screen. It says it flashes successfully but I still get a bunch of "can't mount such and such partition" errors during the flash sequence. Not sure what to do, I can post pics if you guys want.

If you got/can get TWRP on there now, the advanced wipe menu will allow you to check /data for errors. As for /system, wipe it. If you get errors that e2fsck can't fix in your TWRP log, you'll have to put on your data recovery hat on. If it's that important to you, my advice is to adb pull the right file under /dev/block. You won't get a block device, you'll get an exact image of your data partition. Once it's fully pulled (it'll be 10 GB or more on a 16GB device), make a copy of it first thing, and use data recovery tools (testdisk, or if you really know what you're doing, debugfs). If you don't have anything valuable on /data (remember that any backups you took from recovery go in /data/media by default), just format that and be done with it.
Pray that there are no errors after you format everything, because that usually means your NAND is toast.
If your errors are hardware ones, you're royally screwed. Same thing happened to my Nexus 7 2013 model a year ago. Only way to use it is to flash a modified kernel that will use an attached USB drive exclusively as storage. If the NAND is toast inside the boot partiti,try replacing recovery, otherwise, you have to tether boot it (fastboot boot) every time you want to run it, unless you have the guts to try repartitioning the NAND (unlike on PCs, messing up there is an instabrick).
Since the Shield Tablet can use SD cards, you're better off. No USB drive needed.

No touch screen in TWRP

Hi everyone, I was trying to return my moto g7+ to stock. I had wiped all partitions except internal, ext sd, and otg. I already had motorola_moto_g7_plus_xt1965-2_lake_retail_br_9.0_ppw29.98-66.zip on my sd card, but when I tried to install it it gave me an error message. I then downloaded it from motostockrom.com to my desktop. Then I copied it to a usb thumb drive and connected it to my phone via an otg cable. When I looked for it in TWRP, it wasn't listed. I removed the thumb drive and deleted everything but the .zip file and it still listed all of the files that I had deleted and not the .zip. I rebooted the phone and when it rebooted, I went into TWRP but my touch screen didn't work so I couldn't do anything. I tried to connect to phone via ADB but it wasn't being recognized. Strange thing, when TWRP starts, I can access the internal storage and the micro SD card folders on my computer. I've read other's posts with the same problems but I haven't seen any solutions. I'm using TWRP 3.5.2 _9-0. Any help would be greatly appreciated.

Can you enter fone gui? You need to revoke adb keys in dev options in fone in order to regrant them, then reboot back into twrp, and twrp adb should work, but if you can get in fone gui, and load adb, use Vysor, google it, Vysor gives your pc mouse control of your fone in your pc as if you were at the phone screen. Google Vysor.
An awfy long way to say screen dont work lol, Prob solved in 1 word.
If you cant enter gui, get back to me

Pachacouti said:
Can you enter fone gui? You need to revoke adb keys in dev options in fone in order to regrant them, then reboot back into twrp, and twrp adb should work, but if you can get in fone gui, and load adb, use Vysor, google it, Vysor gives your pc mouse control of your fone in your pc as if you were at the phone screen. Google Vysor.
An awfy long way to say screen dont work lol, Prob solved in 1 word.
If you cant enter gui, get back to me
Click to expand...
Click to collapse
I came across a post that mentioned using a mouse with the otg cable so I tried that. I was able to access the controls in TWRP. I was still getting the error message "invalid zip file format! Error installing zip file '/external_sd/Motorola_Moto_G7_Plus_XT1965-2_LAKE_RETAIL_BR_9.0_PPW29.98-111_(by_motostockrom.com) (1).zip".
Is there a spelling error, re: (by_motostockrom.com)? I tried to restore to a point that I had saved from 2020 which said that it had completed sucessfully but resulted in a boot loop. I tried to restore to the other save from 2021, but it gave an error "Cannot restore firmware -- mounted read only." In recovery, if I go to file manager, all of the entries are 20+ character alphanumeric, which I had experienced before when I tried to do a restore but my phone was encrypted.