wipe sd card from twrp - Nexus 4 Q&A, Help & Troubleshooting

so i accidentally wipe my sd card from twrp, and my N4 is not showing up on my computer, download the google usb driver and tried to mount sd within recovery, but my computer doesnt want to install the driver, tried 2 computers. so cant load rom to sd and reflash. tried adb push and adb sideload, but says "error devices not found". any other ideas? thanks

You were in recovery when you ran adb push right?
Also try installing Koush's usb driver.

claudiuslu2011 said:
so i accidentally wipe my sd card from twrp, and my N4 is not showing up on my computer, download the google usb driver and tried to mount sd within recovery, but my computer doesnt want to install the driver, tried 2 computers. so cant load rom to sd and reflash. tried adb push and adb sideload, but says "error devices not found". any other ideas? thanks
Click to expand...
Click to collapse
I did the same once. Tried alot of things but as I recall it it was of the toolkits that did it for me. So you should give them a try.

Related

[Q] External SD-Card error, please help

Hi
I have HTC hero with CWM recovery. I was in recovery and mounted the sd card, copied few files from sd-card to comp and then on the phone I just clicked back button then realised I should have Unmounted that, having done that on the next reboot it gave me an error to remove the card and insert it, I realised something is wrong so went back into the recovery and tried mounting it but it gave me the error - "unable to write to ums Lunfile".
I dont know what to do now, the card is 8GB and dont have any other card, everything was working fine prior to this.
Plug the card into your PC and format it
sorry mate, that did not work, I also used another 2GB card, formated but that does not work as well.
Using 2GB and going into CWM recovery, while mounting it still gives the same msg?
I also checked that 8GB card putting into the card reader and using it on Win-7, the card shows fine, it is showing that Fat32 partition, obviously it is not going to show me Linux partitions.
So the point is how am I going to use that 8GB card back into my HTC hero?
should I flash CWM again on the phone? will that work?
But the phone does not recognise any sdcard so I cannot flash as well..??
what to do?
Try to reflash jordfaz's CWM
Try that : http://forum.xda-developers.com/showthread.php?t=1780438
kemoba said:
Try to reflash jordfaz's CWM
Click to expand...
Click to collapse
That does not seem to be for hero gsm i guess
SANSYF said:
Try that : http://forum.xda-developers.com/showthread.php?t=1780438
Click to expand...
Click to collapse
this thread to be honest has got only 1 person replying and was quite annoyed as he couldnt do it and was gonna throw his phone then so I am worried.
Is there anyway I could either flash RA-Hero-1.7 recovery image through command windows, if that could solve this problem?
and how to if possible.
http://forum.xda-developers.com/showthread.php?t=1723409 here, copy the .zip to a SDcard via your PC and flash it with your existing recovery
kemoba said:
http://forum.xda-developers.com/showthread.php?t=1723409 here, copy the .zip to a SDcard via your PC and flash it with your existing recovery
Click to expand...
Click to collapse
My friend you didnt get it.
My sdcard itself is not recognised by the recovery, so obviously even if I put it on the sdcard, the card itself is not recognised so I cannot use it.
Thats why I asked if it would be possible to put xxxxxx.IMG file through FASTBOOT and if anyone can advise if that would work?
Else as I already have CWM 5.xx can I replace it with recovery-RA-hero-1.7xx.IMG file? will that solve the problem?
Try it, i taught you cant mount your SD card, are you S-OFF, if you are get Amon RA .img, reboot to fastboot, do fastboot flash recovery AmonRa.img
kemoba said:
Try it, i taught you cant mount your SD card, are you S-OFF, if you are get Amon RA .img, reboot to fastboot, do fastboot flash recovery AmonRa.img
Click to expand...
Click to collapse
No I am S-ON
will that be a problem?
suddenly now adb has stopped working.
what a day begins man
could you please give me the step by step commands to flash amonra.img please..
Can you boot into your ROM ? Does your ROM "see" your SD card. If both of these questions answer yes then do this. Mount your SDCard in your ROM and copy amonra.img to it. Then do
Code:
adb remount
adb shell
flash_image recovery /sdcard/amonra.img or flash_image recovery /mnt/sdcard/amonra.img
exit
adb reboot recovery
Hopefully it should go ok, if you get some errors copy output here and i'll help
I can boot into ROM but it cannot see the sdcard?
Now no matter what I do the "adb" doesnt see the devices as well -
I treid
adb kill-server
adb start-server
adb devices
and it says no devices found
I tried going in fastboot mode and then also adb does not see my device.
it has gone to a stage - helpless
Is USB debugging on ??? Are you on linux or windows ?
kemoba said:
Is USB debugging on ??? Are you on linux or windows ?
Click to expand...
Click to collapse
windows 7 and debugging is on
:S This is weird... It sure would help if you were S-OFF but now since no SDCard or ADB this is gonna be a tough fix. Only think i see posible is to get ROM Manager from market and flash CWM recovery from there, i think that ROM Manager will flash version 2.x.x.x
i checked that, there is no market on the phone now as everything was app2sd, market is gone as well
I have Ubuntu on one machine, it was there just for some trial and learning purpose
would anything help with that
Are you sure your USB cable is OK ? No device found is almost 100% bad cable connection, do you have a spare USB
My cable is ok, i have a spare one as well, tried that , same thing, adb doesnt find anything.
I also installed android sdk20 on another pc (64bit) and that doesnt recognise phone in recovery as well..
even while connected, it doesnt even show new drivers installing or nothing..

Stuck in recovery mode

Today, I wanted to reinstall the ROM on my Google nexus 4, and my phone was previously rooted months ago (with Google_Nexus_4_ToolKit_v2.0.0) and was installed with AOKP custom ROM. So I booted into the recovery mode, and accidentally I formatted the system, the cache, the data, etc. I thought when I connect the phone (in recovery mode) to my PC, the PC should recognize my phone and display it as a USB drive in my computer.
However, I was so wrong. With the right driver, the phone is recognized by my PC (as shown in device manager), but it won't show up as a USB drive. So I cannot put in any ROM/gapps file into the phone, I tried to use adb push to load the ROM/gapps into the phone, but I keep getting the "Read-only file system" error. I found the /storage/sdcard0/ can receive the pushed files, but in recovery mode, I cannot select these files for install.
I am now stuck in the recovery mode and cannot do anything. I need you guys help. How can I install a ROM now? thanks a million!!!!
Adb can only be used when your device is booted on android. If not then go to the boot loader and use fastboot.
Sent from my Nexus 4 using Tapatalk 2
rcholic said:
Today, I wanted to reinstall the ROM on my Google nexus 4, and my phone was previously rooted months ago (with Google_Nexus_4_ToolKit_v2.0.0) and was installed with AOKP custom ROM. So I booted into the recovery mode, and accidentally I formatted the system, the cache, the data, etc. I thought when I connect the phone (in recovery mode) to my PC, the PC should recognize my phone and display it as a USB drive in my computer.
However, I was so wrong. With the right driver, the phone is recognized by my PC (as shown in device manager), but it won't show up as a USB drive. So I cannot put in any ROM/gapps file into the phone, I tried to use adb push to load the ROM/gapps into the phone, but I keep getting the "Read-only file system" error. I found the /storage/sdcard0/ can receive the pushed files, but in recovery mode, I cannot select these files for install.
I am now stuck in the recovery mode and cannot do anything. I need you guys help. How can I install a ROM now? thanks a million!!!!
Click to expand...
Click to collapse
Of course you are able to use ADB in recovery mode. Have you tried
Code:
adb push nameoftherom.zip /sdcard/
or if you are using a recovery where you are able to use adb sideload
Code:
adb sideload nameoftherom.zip
Then it should work. Or try mounting the usb in mounts/storage -> mount usb storage
scream4cheese said:
Adb can only be used when your device is booted on android. If not then go to the boot loader and use fastboot.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Of course, it should work if the drivers are installed properly
Like others said use adb push to put a file on the device and then you can flash it with recovery.
If you don't have adb you can get it either by downloading android SDK or just downloading adb did
Sent from my Nexus 4 using xda app-developers app
Try flashing back to stock, then just root and put your ROM back on, I've had to do it once before
Sent from my Nexus 4

Problems with adb

Hello,
So a few days ago my nexus 4 got a virus that started hijacking my text messages and made it so that the phone would not mount as mass storage to a computer. Also adb wouldn't work and i did have usb debug on. Anyway so I have TWRP installed so I just did a storage format totally wiping android and the virus from the phone. After I did that I tried pushing a nandroid backup that I have over and adb told me that the device was not found. I tried pushing the file in the bootloader, the recovery and when its trying to boot an android that's not there. Then I tried re-installing all of the usb drivers and adb. Still nothing. The I tried the adb sideload in TWRP. Still nothing. So dose anyone have any ideas about what this could be?
Thanks a bunch,
You can't use adb commands in fastboot. You should be able to do an adb push while sitting in recovery; don't use sideload unless you are sideloading something. If you can't get it to work, flash a rom and do it from within android.

system deleted, TWRP ready

Hello,
i delete the System and Data on my LeEco Le Pro3.
TWRP is installed.
Can i flash a rom with an usb flash drive in TWRP or fastboot?
greeting gizez
Boot into TWRP and use MTP to transfer ROM file from your PC to Phone. Then flash the ROM.
I have this problem, but I can't see the phone when connected to a PC. adb sideload doesn't work (adb devices doesn't find anything). Do I need to install driver for the phone? I originally used fastboot to unlock the bootloader and flashed TWRP, then installed LineageOS and gapps just fine. I then proceeded to wipe system in TWRP (I was trying to get back to new phone setup so I can transfer stuff from old phone, which I skipped the first time).
Any idea how to get around this? I tried plugging in pen drive through an micro USB OTG and a usb-c to micro usb adapter, but it's not recognized in TWRP, either. Would very much appreciate any help!
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
marik1 said:
[...]
Go Advanced -> ADB Sideload, type "adb sideload aicp_zl1_n-12.1-NIGHTLY-20170516.zip" (zip of OS should be downloaded and put into "Minimal ADB and Fastboot" installation folder with name as same as the text of command). It should let you turn on system.
[...]
Click to expand...
Click to collapse
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
marik1 said:
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
Click to expand...
Click to collapse
Thanks, but unfortunately no luck. Both adb sideload and adb push said error - device '(null)' not found. It seems like the PC is not recognizing the phone. I checked device manager on the PC, it showed LEX727. I right-click and had it install the driver. It says driver successfully installed. Then device manager showed MTP device with a !. I again tried having driver installed, but this time it doesn't find any driver.
I'm at my wit's end... Any more suggestion?
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
marik1 said:
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
Click to expand...
Click to collapse
Actually, the problem is solved, by using another PC. This one showed LEX727 in windows explorer as soon as i plug in the phonr (in twrp). I was able to drag and drop the zip files to the phone and go on my merry way. Now back in business!

TWRP, No OS, ADB sideload not working: what to do?

Hey all,
I have a OnePlus 2, which had Resurrection Rom (and TWRP 3.0.2-2). However, I wanted to factory reset that ROM. Problem is: I wiped too much data.
I now have no more OS (TWRP -> Reboot -> Reboot System gives a message "No OS installed!").
I do have TWRP 3.0.2-2 and can boot to it.
I have no img of an OS on the device (as far as I know, since I wiped basically everything).
If I go to TWRP -> Advanced -> ADB Sideload, it will go "Starting ADB sideload feature...", hang there for a few minutes and then give a red FAILED on the top of the screen.
I have the phone connected with USB to my pc (Ubuntu 16.10), but I can't find it with lsusb and I can't seem to transfer files that way either.
So my question is: how do I get any ROM back on there? Stock OxygenOS without a custom recovery or whatever would be fine, as long as I can boot to an OS again.
Any help is greatly appreciated, thanks in advance!
Greetings,
Rien
rienheuver said:
Hey all,
I have a OnePlus 2, which had Resurrection Rom (and TWRP 3.0.2-2). However, I wanted to factory reset that ROM. Problem is: I wiped too much data.
I now have no more OS (TWRP -> Reboot -> Reboot System gives a message "No OS installed!").
I do have TWRP 3.0.2-2 and can boot to it.
I have no img of an OS on the device (as far as I know, since I wiped basically everything).
If I go to TWRP -> Advanced -> ADB Sideload, it will go "Starting ADB sideload feature...", hang there for a few minutes and then give a red FAILED on the top of the screen.
I have the phone connected with USB to my pc (Ubuntu 16.10), but I can't find it with lsusb and I can't seem to transfer files that way either.
So my question is: how do I get any ROM back on there? Stock OxygenOS without a custom recovery or whatever would be fine, as long as I can boot to an OS again.
Any help is greatly appreciated, thanks in advance!
Greetings,
Rien
Click to expand...
Click to collapse
Try connecting it to windows pc and mount storage internal storage will pop up if drivers are installed properly just copy and install rom.
Jitesh.saitawadekar said:
Try connecting it to windows pc and mount storage internal storage will pop up if drivers are installed properly just copy and install rom.
Click to expand...
Click to collapse
I tried installing the drivers I found through Google ("oneplus 2 usb drivers -> result on technobuzz).
After that I connected it to a windows pc and I got the message following message:
"USB device not recognized"
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
So I still can't access the storage.
rienheuver said:
I tried installing the drivers I found through Google ("oneplus 2 usb drivers -> result on technobuzz).
After that I connected it to a windows pc and I got the message following message:
"USB device not recognized"
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
So I still can't access the storage.
Click to expand...
Click to collapse
Might be usb issue try with some other usb .
Jitesh.saitawadekar said:
Might be usb issue try with some other usb .
Click to expand...
Click to collapse
Wow, never thought of that one... but it was the cable indeed.
Thanks for the help!

Categories

Resources