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
Hey ! I Have Google Nexus 4
My System Has Delete >> And I Cant Move Rom To Phone Because Need USB debugging
My Recovery TWRP
Please Help Me
And Sorry For Bad English !
Penguin997 said:
Hey ! I Have Google Nexus 4
My System Has Delete >> And I Cant Move Rom To Phone Because Need USB debugging
My Recovery TWRP
Please Help Me
And Sorry For Bad English !
Click to expand...
Click to collapse
You can copy the file over from TWRP. Just connect to the computer boot into TWRP, go under Mounts, and Mount USB. You can just copy and paste from your computer to the phone, then unmount, and flash the file in CWM
Otherwise,
1. Open your cmd and navigate to the folder with the adb files(the folder where you flashed your roms, kernels, or recovery).
2. Access the cwm at your phone and connect an usb cable to the computer.
3. Put the files that you wanted to send to your phone at that particular folder
4. Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
4.1. Depending on your OS, you may want to add "./" at the front of the command if you're using unix based os(this is an oversimplified version)
5. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
6. Wait for a while or reboot your cwm so that the filename will appear and just reflash the file.
So i am having a issue with my oneplus 5 and hope someone could help me out
So i have ended up wiping the entry phone in recovery, getting rid of all the internal data, including sdcard & operating system. At the moment the only thing i can get access to is fastboot & TWRP. I am trying to sideload or push a rom zip to the phone, but all i keep getting is the below:
adb sideload "Zip folder name and extension".
loading "zip"
cannot read "zip"
or i get an error that just says "Closed.
Now i have update to the latest drivers and adb and when i type "adb devices" my phone is showing...
I have also flashed the oneplus 5 recovery via fastboot, however when i go on to adb sideload, the phone doesnt show in CMD.
any help here will be appricated, as i am out of ideas.
Thanks in advance.
Make the file names shorter.
Alternatively, you should be able to use a flash drive through OTG and install the stuff from it.
Rhoban said:
Make the file names shorter.
Alternatively, you should be able to use a flash drive through OTG and install the stuff from it.
Click to expand...
Click to collapse
Unfortunately, OTG isnt a selectable option and i have also tried shorting the file a names but still no look.
Thank you for the input
Use another recovery. OTG should be there, I know somebody that flashed ROMs this way.
KrypticGT said:
...
adb sideload "Zip folder name and extension".
loading "zip"
....
Click to expand...
Click to collapse
Two things I'd try:
1. Change your directory to the one containing the zip file so the command ONLY has the filename.zip in it
2. Download the zip file again and make sure you do a md5sum check on it just in case its corrupted.
Try this:
- Boot your phone in TWRP
- Open cmd.exe on your PC
- Type adb devices (if everything is ok, it should show some numbers followed by the write "recovery")
- Move your ROM inside a folder on your PC and rename it "Rom.zip" (ie inside the folder "download")
- Using CMD.exe, move inside that folder typing "cd C:/...."
- Type "adb push Rom.zip /sdcard"
- Wait til a confirmation message will appear on CMD.exe
- Flash the ROM using TWRP
So for future reference to anyone that might have the same issue.
I fixed this issue, by flashing a older version of TWRP. This allowed me to use ADB sideload without issue & also allow OTG_USB. It also allowed me to flash files with long names.... I have tried to go back to the latest version of TWRP for OP5 but i get the errors i was getting before.
Strange, but did the fix.
Thanks all for the help & input.
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
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12
Visit this thread for more information
________________________________________________________
CAVEAT
I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be universally helpful as it's using your own boot.img so there's no need to find a matching package for your variant and os version.
CREDIT
The steps were buried across a few threads, I'm posting this so it'll be easier for others to find the information. All credit goes to xb360, FullOfHell, and TheUnkn0wn.
INFOThe basic rundown is:
Use the semi-broken TWRP package to give yourself temporary su access through adb.
Extract the boot.img your phone is currently using to your pc.
Reboot to OxygenOS, copy over the boot.img you just extracted and then use Magisk to patch it.
Copy the boot.img back to your pc and use adb to temporarily boot your phone with it, giving you root access until reboot.
Use your temporary root access to allow Magisk to patch your internal as-yet unmodified boot.img to give you permanent root.
There seems to be some confusion in the thread, I'll try to clear up what's happening and why:
The primary issue at hand is that you can't root your device without already having root privileges, for security reasons. Without a custom recovery like TWRP, there are a few more steps than usual (but mostly simple stuff).
Because we don't flash anything with this guide, it shouldn't cause any permanent bootloops if you use the wrong boot.img, if you get stuck in one just power cycle your phone.
Updating with OTAs should be the same process as the other guides here.
Because of changes in Android, devices that launched with Android 10 and above will not allow you to modify the system partition, even with root. This is not a fault of this rooting method.
Prerequisites:
ADB and Fastboot installed.
An unlocked bootloader and USB debugging enabled.
Android 11. (Android 12 introduced problems with this method, per other users. See link at top of page)
________________________________________________________
STEPS:
1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. On your computer open a terminal/cmd prompt. Set the directory (on your pc) you want to work from, I'm using the desktop:
for Windows, type cd C:\Users\Yourname\Desktopfor Mac, type cd desktop or cd /Users/yourname/Desktop
Spoiler: How to set up adb and fastboot properly
To usb adb and fastboot commands outside of the folder those programs are located in, you'll need to add their location to the PATH list so your terminal can still find them when it's pointing to a different folder. If you want to skip this step, set the directory to the folder that contains adb instead of the desktop.
3. Next, use the terminal to check which A/B partition is active on your phone:
Code:
fastboot getvar all
a. You'll find it on this line: (bootloader) current-slot:a/bb. For simplicity I'll be referring to boot_a.img throughout the guide, make sure to use boot_b.img if that's the one marked as active on your device.
4. Download the semi-broken TWRP package to your desktop. We'll be using it to extract a copy of your active boot_a.img. It will give you temporary su access via adb, but there won't be a gui. Only boot from it, DO NOT FLASH IT:
Code:
fastboot boot recovery.img
adb shell
dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
exit
adb pull /sdcard/boot_a.img boot_a.img
adb reboot
5. Copy the extracted boot_a.img file to a user accessible area of your phone, like your downloads folder.
6. Install the latest Magisk Canary apk on your phone. Open it and:
a. Select the Install option.b. Use Select and Patch a File on boot_a.img
7. Copy the patched magisk_patched_a.img file back to your computer. In terminal, type adb reboot bootloader to get back to fastboot mode.
8. Temporarily boot with the patched image that corresponds to the active partition, DO NOT FLASH IT:
Code:
fastboot boot magisk_patched_a.img
Spoiler: Why we're booting and not flashing.
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
9. By booting with the patched image, you now have temporary root access. To make it permanent open Magisk:
a. Select the Install option.b. Use Direct Install (Recommended) to root your internal boot.img
10. Reboot and verify it worked.
Forgot to tag it... if an admin is able to do so I'd appreciate it.
Just applied for a bootloader unlock today. When i get approved ill attempt this guide.
I am currently on T-Mobile 11.0.5.7.KB09CB.
Unlike other methods prvoided here for the 8T I got this method to work. Thank you very much!
clarification update: I own the t-mobile kb2007 model of phone
a couple of notes for any either newBs or old OPO users rejoining the party with a new onplus phone..
Some prework I had to do for my OnePlus 8T KB2005
-ensure you have the correct ADB driver installed, I installed the "15sec adb installer 1.4.2" found here on xda, watch the videos provided.
-ensure to unlock your bootloader first (*this will wipe your device.. didn't think about that..no pain no gain...)
-With device in bootloader/fastboot, run: fastboot flashing unlock
-verify with your phone to accept
-phone will reboot, just through the setup, I just skipped it all and opted for offline setup..
-renable OEM lock and USB debug
-restart back into bootloader/fastboot
-now you are ready to root
Just came here to say that this is the most genius way to go about it and thanks OP for this solution. To add your screen would flicker in TWRP but you just want to type adb reboot bootloader after you are done copying off the boot files from your phone. Thanks OP!
After performing this, I am unable to write to /system even with root?
Unable to get through with es explorer, root explorer pro, or even use a app like Titanium to move a user app to system,unable to get r/w access.
Thanks in advance
lordxcom said:
After performing this, I am unable to write to /system even with root?
Unable to get through with es explorer, root explorer pro, or even use a app like Titanium to move a user app to system,unable to get r/w access.
Thanks in advance
Click to expand...
Click to collapse
I'm having the same issue although its more tied in with removing youtube as a system app for vanced
lordxcom said:
After performing this, I am unable to write to /system even with root?
Unable to get through with es explorer, root explorer pro, or even use a app like Titanium to move a user app to system,unable to get r/w access.
Thanks in advance
Click to expand...
Click to collapse
Actually Is not possible on devices borned with android 10 or above.
giacomowrc said:
Actually Is not possible on devices borned with android 10 or above.
Click to expand...
Click to collapse
To be clear, you're saying this isn't a fault with this root method and is just a security measure since Android 10?
Mpolo87 said:
To be clear, you're saying this isn't a fault with this root method and is just a security measure since Android 10?
Click to expand...
Click to collapse
Yes of course.
Mpolo87 said:
CAVEAT
I've only tested this on my device (KB2005 / KB05AA), but it should be universally helpful as it's using your own boot.img so there's no need to find a matching package for your variant.
CREDIT
The steps were buried across a few threads, I'm posting this so it'll be easier for others to find the information. All credit goes to xb360, FullOfHell, and TheUnkn0wn.
INFOThe basic rundown is:
Use the semi-broken TWRP package to give temporary su access through adb.
Extract boot_a.img and boot_b.img to your computer.
Reboot into OxygenOS and copy boot_a.img and boot_b.img back to your phone.
Use Magisk to patch both images.
Copy the patched images back to your computer.
Use fastboot to temporarily boot using the patched image, giving you temporary root.
Use Magisk to direct install for permanent root.
Prerequisites:
ADB and Fastboot installed.
An unlocked bootloader and USB debugging enabled.
________________________________________________________
STEPS:
1. Get the semi-broken TWRP .img. This won't give you a gui but will give you su access over adb. You DON'T want to flash this, we're just booting with it temporarily.
2. Restart your phone into fastboot mode.
3. On your computer open a terminal/cmd prompt and set the directory where you want to dump the files (ex: cd /your/path/here). Run the following:
Code:
fastboot boot recovery.img
adb shell
dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
dd if=/dev/block/by-name/boot_b of=/sdcard/boot_b.img
exit
adb pull /sdcard/boot_a.img boot_a.img
adb pull /sdcard/boot_b.img boot_b.img
4. Copy the extracted files to a user accessible area of your phone.
5. Install the latest Magisk Canary release to your phone.
a. Select the Install option.b. Use Select and Patch a File on both boot_a.img and boot_b.imgc. You should rename them or make note of the new names given by Magisk. You'll need to use one or the other depending on which partition is active.
6. Copy the patched .img files back to your computer.
7. Restart your phone back into fastboot mode.
8. On your computer, run:
Code:
fastboot getvar all
9. Find which A/B partition is active on this line: (bootloader) current-slot:a/b
10. Temporarily boot with the patched image that corresponds to the active partition, DO NOT FLASH IT:
Code:
fastboot boot patched-boot-a/b.img
11. You now have temporary root access, to make it permanent open Magisk:
a. Select the Install option.b. Use Direct Install (Recommended) to root your internal boot.img
12. Reboot and verify it worked.
Click to expand...
Click to collapse
hey there! I was just about to try this method but confused with this syntax -- don't mind the quotes
"On your computer open a terminal/cmd prompt and set the directory where you want to dump the files (ex: cd /your/path/here)"
I'm painfully confused about this: cd /your/path/here. is this done during fastboot? I know fastboot commands but adb is where my brain doesn't get it. Please elaborate further and thanks.
sameog said:
hey there! I was just about to try this method but confused with this syntax -- don't mind the quotes
"On your computer open a terminal/cmd prompt and set the directory where you want to dump the files (ex: cd /your/path/here)"
I'm painfully confused about this: cd /your/path/here. is this done during fastboot? I know fastboot commands but adb is where my brain doesn't get it. Please elaborate further and thanks.
Click to expand...
Click to collapse
When you open a terminal or command prompt on your computer it is, by default, 'pointing' to a certain folder. Since we're pulling files from the phone to pc it'll dump there, so it's easiest to set the location in advance, for your own convenience. You can just make a folder on your desktop and drag it onto the terminal window to automatically input that path after typing cd, which just means 'change directory'. This isn't a fastboot or adb thing, just a feature of terminals, so you'd do this in advance.
Mpolo87 said:
When you open a terminal or command prompt on your computer it is, by default, 'pointing' to a certain folder. Since we're pulling files from the phone to pc it'll dump there, so it's easiest to set the location in advance, for your own convenience. You can just make a folder on your desktop and drag it onto the terminal window to automatically input that path after typing cd, which just means 'change directory'. This isn't a fastboot or adb thing, just a feature of terminals, so you'd do this in advance.
Click to expand...
Click to collapse
Attached are 2 photos -- the 1st photo is the "before" I dragged my intended folder into command prompt. the 2nd photo is the "after" I dragged my intended folder into command prompt. Still hella confused.
Please note: I love this guide. It's cohesive and well-written. I just need pictures to "see" on what and where to do. I'm visual.
UPDATE: I followed the tuturial to the best of my ability and I got nothing. I'm giving up and taking a step back.
PS C:\Program Files (x86)\platform-tools_r30.0.5-windows> ./fastboot boot recovery.img
Sending 'boot.img' (64964 KB) OKAY [ 1.660s]
Booting OKAY [ 0.084s]
Finished. Total time: 1.939s
PS C:\Program Files (x86)\platform-tools_r30.0.5-windows> ./adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
OnePlus8T:/ # dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
196608+0 records in
196608+0 records out
100663296 bytes (96 M) copied, 0.194981 s, 492 M/s
OnePlus8T:/ # dd if=/dev/block/by-name/boot_b of=/sdcard/boot_b.img
196608+0 records in
196608+0 records out
100663296 bytes (96 M) copied, 0.185497 s, 518 M/s
OnePlus8T:/ # exit
PS C:\Program Files (x86)\platform-tools_r30.0.5-windows> ./adb pull /sdcard/boot_a.img boot_a.img
/sdcard/boot_a.img: 1 file pulled, 0 skipped. 27.7 MB/s (100663296 bytes in 3.470s)
PS C:\Program Files (x86)\platform-tools_r30.0.5-windows> ./adb pull /sdcard/boot_b.img boot_b.img
/sdcard/boot_b.img: 1 file pulled, 0 skipped. 32.0 MB/s (100663296 bytes in 2.997s)
PS C:\Program Files (x86)\platform-tools_r30.0.5-windows> ./adb reboot
PS C:\Program Files (x86)\platform-tools_r30.0.5-windows>
sameog said:
Attached are 2 photos -- the 1st photo is the "before" I dragged my intended folder into command prompt. the 2nd photo is the "after" I dragged my intended folder into command prompt. Still hella confused.
Click to expand...
Click to collapse
You're missing the command "cd" before the path to change the directory to the new one. It should be cd C:\Users\Mr. Lew\Desktop\oneplus 8t boot image then press enter. Now you can reference any file in that folder by just the name without its entire path as a prefix being required.
A difficult method
zengin said:
Diğer yöntemden hiç de kolay değil.
Click to expand...
Click to collapse
huh?
Honestly, if there's a kind of soul out there who can share their unpatched kb2007 boot image (tmobile version), I would greatly appreciate it. I'm been banging my head on the wall with this for about 2 months with no help. I've received TONS of half-baked one liner answers but no "full-scale" tutorial. I'm giving up on this.
NOTE: I'm just frustrated guys. Not bashing the OP. It shouldn't be this hard but it became this way.
sameog said:
Honestly, if there's a kind of soul out there who can share their unpatched kb2007 boot image (tmobile version), I would greatly appreciate it. I'm been banging my head on the wall with this for about 2 months with no help. I've received TONS of half-baked one liner answers but no "full-scale" tutorial. I'm giving up on this.
NOTE: I'm just frustrated guys. Not bashing the OP. It shouldn't be this hard but it became this way.
Click to expand...
Click to collapse
While this is a temporary solution, it is also a bad solution because you can land with not being able to boot your phone every time an incremental update comes along.