i format my Nexus 4 on twrp recovery using advance wipe and i checked all the box there, and when i rebooted its stuck on google logo, what should i do?
Well why would you do that? If you selected everything under advanced in twrp, that means that you have also wiped the system partition so there is no rom to boot into, hence why you are stuck at the google logo. You will need to use adb to copy a rom onto your phone, and then flash it via twrp. Instructions:
1. Setup adb: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
2. Install Koush's universal adb driver (google this for the download)
3. Put the phone into twrp
4. Download a rom on your pc and move it to your desktop. Rename it to "rom.zip".
5. Open a command prompt window and run the following commands:
Code:
adb devices
If your phones serial number shows up, continue. If not, reinstall drivers.
Code:
cd Desktop
adb push rom.zip /sdcard/
6. After its finished pushing, go to install within twrp and flash it.
when i typed in cd desktop it says "The system cannot find the path specified". and when i continue to adb push rom.zip /sdcard/ it says "cannot stat rom.zip: no such file or directory"
it worked, thanks for your help.
I hope you realized when you checked all the boxes, you checked to wipe the internal storage which holds all your personal data.
And you checked to wipe /system partition which house the operating system, of course there wouldn't be anything to boot into.
sent from xda premium app
Related
I need to flash a ROM, but I can't start my phone up to be able to transfer the file over. There used to be a Mount Storage Device option on my old DHD, but I noticed that on the N4, CWM does not have this option (maybe to do with MTP).
How can I copy a file over onto SDCard so I can flash it? I tried:
Code:
adb push file.zip /sdcard/file.zip
When I try and flash it, it says "Can't open /sdcard/file.zip (bad)
Flash TWRP via fastboot and mount the phone via usb the same drag it into the phone.
Alternatively as a last resort, flash back to stock using stock images provided by Google vis fast boot and then drag it onto the sd as well as reinstalling the recovery.
Sent from my Nexus 4 using xda premium
stefandunn said:
I need to flash a ROM, but I can't start my phone up to be able to transfer the file over. There used to be a Mount Storage Device option on my old DHD, but I noticed that on the N4, CWM does not have this option (maybe to do with MTP).
How can I copy a file over onto SDCard so I can flash it? I tried:
Code:
adb push file.zip /sdcard/file.zip
When I try and flash it, it says "Can't open /sdcard/file.zip (bad)
Click to expand...
Click to collapse
Remove the "file.zip" after the sdcard:
Code:
adb push file.zip /sdcard/
Also ensure the real file name doesn't contain spaces.
Edit: the command as you were typing it was telling adb to take the CONTENTS of file.zip and place them in a FOLDER called file.zip. Out of adb's range of abilities
Alternatively, if you're using CWM, you can use the "Install zip from sideload" option. Once you're in, push the file from adb using "adb sideload filename.zip"
The adb command you tried should work fine in recovery. Maybe you weren't in the correct folder where file.zip was located when you executed the adb command?
Also, if you don't have adb set in your PATH, then the adb app will need to be in the same folder as file.zip.
http://forum.xda-developers.com/showthread.php?t=1667929
se1000 said:
Alternatively, if you're using CWM, you can use the "Install zip from sideload" option. Once you're in, push the file from adb using "adb sideload filename.zip"
Click to expand...
Click to collapse
Thank you very much!
I deleted Rom file in sdcard. I cant flash a rom. I have recovery, root and Philz Touch.
How can i copy Rom zip file from computer to Phone? Any idea. I have rooted KK, i dont want to do all things again.
How to: Copy ROM zip file to the freshly wiped device
I found and share with you, it worked.
Have you ever been in a situation where you mistakenly (or not) wiped the content of the internal storage (including system partition and virtual SD card) on your phone or tablet and unfortunately it doesn't support external storage? Now you can't flash desired custom ROM because you removed it and the device can't be booted due to wiped system partition. Don't worry - it's very easy to fix!
Here are the steps you need to follow to copy the correct rom.zip package to your internal storage:
Download this mini-sdk package and extract it to c:\mini-sdk
Rename the custom ROM package you want to flash to "rom.zip" and copy it to c:\mini-sdk
Connect your device to the PC
Boot your device in recovery mode
Open a command prompt on the PC (cmd.exe), type and confirm each command with ENTER:
cd /d c:\mini-sdk
adb shell
mount /data (error might mean that /data partition is already mounted)
on Android 4.2 and above: mkdir -p /data/media/0
on Android 4.1.2 and below: mkdir -p /data/media
exit
on Android 4.2 and above: adb push rom.zip /data/media/0
on Android 4.1.2 and below: adb push rom.zip /data/media
Wait for a few minutes until the file is copied. It will looks like command shell is not responding, but that means it's still copying. Wait patiently until you'll see blinking cursor again.
Depends on your custom recovery, use the navigation keys to flash the custom rom.zip package in a typical way you used to flash custom ROMs. It should be on your internal storage now. Done! http://android-revolution-hd.blogspot.com.tr/2013/12/how-to-copy-rom-zip.html
easier solution:
*bring device in recovery mode
*open cmd, go to adb.exe
*type adb.exe push *filename.zip* /sdcard/your path **/sdcard is already linked to /data/media/0
*wait after pushing the file, reboot recovery again
*choose file and flash
*** other method ***
*use the sideload function in recovery
*adb.exe sideload *rom.zip* in cmd
it says usb device descriptor failed...is it due to bad cable??
it says usb device descriptor failed...is it due to bad cable??
I did something stupid and I am embarrassed to say I don't know how to get out of it.
I didn't back up my ROM, and I ended up wiping everything. I lost the zip file that I had and now I can't flash it. I am unable to use TWRP's menu to mount the USB. The only option I see mount USB-OTG but it says unable to mount. How do I mount and transfer the zip file? I guess I have to use adb. But I am unable to get it to work. I've tried:
adb push update.zip
after setting the recovery in sideload mode, but nothing happens.
EDIT: never mind. I figured it out. For anyone else, here is what I did:
1) download adb 1.08
2) Put the zip file in the same folder as the adb.exe
3) Run adb usb
4) Do NOT put the tablet in sideload mode. Do nothing there. In fact I rebooted back into recovery.
5) Run adb push <name of zip file> /sdcard/
Nothing will appear to happen for a minute or so. Then you'll get a line to the tune of <kb> in <s> or something. That means it pushed the file to /sdcard/
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4.
TWRP ADB Sideloading
Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery
Moto G (1st Gen) has no SD Card slot. This creates a problem for people converting their phones to GPE and back; as the entire internal storage needs to be formatted (wiped.)
Fastboot images can be used to get android onto your phone after formatting, but there is another way.
NOTE: TWRP needs to be restarted whenever 'data' is changed to a different filesystem.
Example 1:
GPE user wants to flash Stock Motorola ROM.
1) In TWRP, format ‘data’ to f2fs
2) In TWRP, enable ADB Sideloading
3) On PC, use command: ADB sideload stockrom.zip
Example 2:
Stock Motorola ROM user wants to run GPE.
1) In TWRP, format ‘data’ to ext4
2) In TWRP, enable ADB Sideloading
3) On PC, use command: ADB sideload gperom.zip
How to access ‘Recovery mode’ ADB:
On a Linux laptop, this is what happens when I use the 'adb devices' command while in TWRP. No drivers are required. I suspect the same applies to Mac OS.
[email protected]:~$ sudo adb devices
List of devices attached
TA53307V38 recovery
On Windows, it seems not everyone is able to use ADB when in TWRP. The reason for this is that the Motorola drivers installed on the PC are not adequate.
15 Seconds ADB installer includes a generic android driver that may be the solution for people with this problem.
I'd appreciate any tips and insights into how to make this work on different versions of Windows.
Thanks for the guide
some other methods of doing same
Method-1. TWRP 2.8.4.0 supports MTP mode. (Main Menu >> Mount >> Enable MTP) Drivers required for windows. zip file can be copied in MTP mode (Though MTP mode available in 2.7.1.0 it was not working for me but TWRP2.8.4.0 works ). flash via recovery
Method-2. using ADB: place ROM.zip in the adb folder. type following command
Code:
adb push rom.zip /sdcard/
rom will be copied to sdcard. but it does not show the transfer process. flash via recovery
I will report as soon as I will reach home. Well this was needed for people who have issues with adb..
Sent from my Moto G using XDA Free mobile app
For those getting error:
Code:
C:\Users\username\moto>adb sideload sideload.zip
loading: 'sideload.zip'
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
In TWRP, go to restart > Recovery mode and try again, after the reboot!
Then it works:
Code:
C:\Users\username\moto>adb sideload sideload.zip
loading: 'sideload.zip'
sending: 'sideload.zip' 100%
Can i sideload any type of zip, like BootAnimation zip or System app zips etc, instead of only ROM zips???
subroto1427 said:
Can i sideload any type of zip, like BootAnimation zip or System app zips etc, instead of only ROM zips???
Click to expand...
Click to collapse
You can sideload any zip that you could also install from local storage.
reversegear said:
Thanks for the guide
some other methods of doing same
Method-1. TWRP 2.8.4.0 supports MTP mode. (Main Menu >> Mount >> Enable MTP) Drivers required for windows. zip file can be copied in MTP mode (Though MTP mode available in 2.7.1.0 it was not working for me but TWRP2.8.4.0 works ). flash via recovery
Method-2. using ADB: place ROM.zip in the adb folder. type following command
Code:
adb push rom.zip /sdcard/
rom will be copied to sdcard. but it does not show the transfer process. flash via recovery
Click to expand...
Click to collapse
It seems Lineage 14.1 uses boot loader 0x4111, instead of 0x411A.
Edit: The following resolved it
https://forum.xda-developers.com/moto-g/general/falcon-bootloader-upgrader-tool-t3093793
So i've been having a hell of a time getting the latest image working on my phone... For a bit, I was soft bricked, even after running deuces and formatting user data and what not. For a while had to go back to android 8.1 (kinda nice having PIP/split screen mode!!). Finally figured it all out today... Download: The latest Magisk, the latest TWRP both .img and installer .zip. Then latest factory image, extract with winrar, go to extracted folder and extract the big .zip again with winrar, load deuces into that folder, put phone in fastboot (hold vol - and power or adb reboot bootloader).
Open an admin command prompt (admin maybe not necessary) and here we go: fastboot --set-active=a
Run Deuces, once finished go to admin command prompt and: fastboot boot twrp-3.3.0-0-taimen.img adb push twrp-pixel2-installer-taimen-3.3.0-0.zip /sdcard adb push Magisk-v19.4.zip /sdcard
Reboot, took a while to start, open magisk, says not installed, so click install, download zip only or patch boot? I just went to the factory image folder, pushed "boot.img" to phone, and selected that.
Read a bunch of threads saying like, find/extract your own boot image (which i don't think was necessary) but if you did want to do that, the location for pixel 2 xl is: /dev/block/sde8
Hopefully that makes sense, let me know if you have comments/questions/smart remarks
noob
Zooandbio4me said:
So i've been having a hell of a time getting the latest image working on my phone... For a bit, I was soft bricked, even after running deuces and formatting user data and what not. For a while had to go back to android 8.1 (kinda nice having PIP/split screen mode!!). Finally figured it all out today... Download: The latest Magisk, the latest TWRP both .img and installer .zip. Then latest factory image, extract with winrar, go to extracted folder and extract the big .zip again with winrar, load deuces into that folder, put phone in fastboot (hold vol - and power or adb reboot bootloader).
Open an admin command prompt (admin maybe not necessary) and here we go: fastboot --set-active=a
Run Deuces, once finished go to admin command prompt and: fastboot boot twrp-3.3.0-0-taimen.img adb push twrp-pixel2-installer-taimen-3.3.0-0.zip /sdcard adb push Magisk-v19.4.zip /sdcard
Reboot, took a while to start, open magisk, says not installed, so click install, download zip only or patch boot? I just went to the factory image folder, pushed "boot.img" to phone, and selected that.
Read a bunch of threads saying like, find/extract your own boot image (which i don't think was necessary) but if you did want to do that, the location for pixel 2 xl is: /dev/block/sde8
Hopefully that makes sense, let me know if you have comments/questions/smart remarks
Click to expand...
Click to collapse
I have just bought my pixel2xl, and recieved it the DAY 10 came out.
I have not had an a/b device, my last phone was the note 4 verizon, and the tabs2 i currently have.
could you perhaps make a simple list, of what this has ?
Currently i can adb devices with linux in my phone, and fastboot reboot bootloader ?
what is "run Deuces"
i presume fastboot --set-active=a means you are setting to write to the a partition ?
the first part,is where do i download the factory image ? google ? then unzip and sideload " push boot.img ?" the file to the /sdcard folder with the other files for twrp and magisk ?
thanks a lot for the announcment. i seriously just got my usb cable attached and ran fastboot, when i searched in xda and found your post. thanks alot
Ok.
I got it kinda figured out.
Gonna make a how 2 for noobs
Step 1. Download magisk and Google image for your device to your favorite machine.
Step 2. Dow load the newest adb tools from Google to your machine. Install and make sure your adb tools are in your $PATH
On my Linux machine, I unzipped the files and copied them to my local binary folder in ~/bin
3. Extract the Google image for your device, the extract the partitions zip file.
4. Go-to the folder and Sidleload the image to your phone
Code:
adb push *.img /sdcard/
5 . GOTO where you downloaded your magisk*.apk
And install with adb
adb install *.apk
6. Open your phone, and open magisk.
Patch the boot.img file you placed in /sdcard/
7. Pull the new patched file from your phone to your computer.
adb pull /sdcard/Download/*.img
That's as far as I got this morning.
Will update you all with the finished commands then copy it over to a how-to guide for noobs.
Yayy
Everytime uninstall magisk and get it working reboots bootloop, and or I try to install a module it boot loops