Hello I've haven't done any rooting or roms since the samsung s3 days. I was attempting to root my google pixel and when I wiped the phone in the TWRP recovery I made the mistake of ticking every box meaning the phone now has no os on it at all. I tried installing a factory rom from googles site but I only get an error saying the zip is an invalid file type.
Any help would be greatly appreciated.
I think,,,and I am not sure but if you wiped everything you will have to fastboot flash stock image then re-install TWRP and go from there.
Unzip the factory ROM zip on your computer, have the latest drivers and ADB/Fastboot installed/downloaded from Google's site, connect the phone in whichever mode it has to be in (Bootloader?) I forget but the information is plenty available in various threads here, there are only a couple of options anyway, then run the Flash-All.bat or .sh, depending on what OS you're running (Windows, Linux/Mac?).
If you can connect via MTP while in TWRP (if that's not wiped as well, or if you did if you haven't booted out of TWRP), then maybe you can copy the files over to flash a ROM and vendor image, and TWRP RC1 too so you can flash it again, although I would opt for starting back from scratch with the fully stock ROM/firmware flashed from a PC myself.
Flash the factory image and remain stock until you learn how to use recovery/restore a phone.
Sent from my Pixel using Tapatalk
Run flash all from PC to get back to stock. Then do a lot of reading.
Sent from my Pixel using Tapatalk
Related
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
ackerchez said:
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
Click to expand...
Click to collapse
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
thejosh86 said:
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
Click to expand...
Click to collapse
Hey!
Thanks a ton for your reply! I managed to get the phone to install a new ROM (AOKP V5) and it seems to boot up. Now when I get into that rom, I see all kinds of things crashing on me. The "Settings" app crashes, the keyboard crashes..any idea?
Did you wipe system, factory reset, davlik and cache from within TWRP before flashing?
Try that otherwise if you're still running into issues post in the thread.
You flashed the 11/10 JB gapps?
Sent from my Nexus 7 using xda premium
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
ackerchez said:
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
Click to expand...
Click to collapse
Did u wipe everything? (davlik, cache)
Sent from my HTC One XL using xda premium
I believe I have bricked my phone. I was running a rooted HTC One X AT&T with an odex Jellybean/HTC Sense 4+ ROM. I wanted to test out a Cyanogenmod. Big mistake. I tried to flash it from TWRP recovery, after backing up my previous ROM, however, it was stuck in an endless boot loop. I took advice from some people online and reflashed it/ wiped caches/dalvik cache etc... When I realized it would not work unless I fastbooted it myself using USB debugging I tried to reinstall the old ROM, of course, after wiping the Cyanogenmod. Long story short there was no backup even though I backed up the phone! I now have no ROM and everything on my system is gone! My SD card folder only has a TWRP recovery and I can't install any .zip files. TWRP isn't even allowing me to mount my SD card so putting any files are out of the question. I believe, however, that usb debugging was on the whole time (is it on if on the boot loader it says fastboot usb when I plug in a USB?). Is there anyway to fix this?? I'm really screwed if I can't and please don't direct me to another thread because I need personalized help. I'm doing this on a mac by the way so anyone who knows how to use the terminal would help a lot. I can get access to windows though if needed. Just please help.
Have you tried to flash the boot.img from the zip file in fastboot?
Do you know what a brick is? When your phone does NOTHING... Similar to a brick.
What happened to you is you didn't flash the boot.img through fastboot, which caused your first problem, the bootloop..
Second thing you did incorrect was perform a factory reset in boot loader... Which completely wipes your SD card and corrupts it, and which just so happened to contain your backup no worries, easily fixable...
Download a rom on your computer. While its downloading, enter recovery and choose mount. Navigate to my computer and right click the removable storage option. Choose format. Once its done, drag rom onto phone.. Flash rom in twrp.
Extract rom on your computer, grab the boot.img and flash with fastboot.
Fastboot flash boot boot.img
Reboot phone and profit
EDIT: sorry but I hastily skimmed through your post... Those are half-assed instructions for windows, I have no clue what to do on a mac
Sent from my One X using Tapatalk 2
What he said. Toolkits are easily found too
I just flashed many different versions of TWRP downloaded from their site(I got only the ones compatible with my P5100). After successfully flashing them all through Odin, I can't boot into recovery. The TWRP logo screen is shown and after 2 seconds the device reboots. I followed many guides, and they were all similar in this particular process. Am I missing something, or could there be anything wrong with my unit?
light401 said:
I just flashed many different versions of TWRP downloaded from their site(I got only the ones compatible with my P5100). After successfully flashing them all through Odin, I can't boot into recovery. The TWRP logo screen is shown and after 2 seconds the device reboots. I followed many guides, and they were all similar in this particular process. Am I missing something, or could there be anything wrong with my unit?
Click to expand...
Click to collapse
did you also installed a rom??
No. I'm running the stock rom, no root. I just wanted to get the twrp installed because I need to copy my personal files to an sd card. My stock rom is rebooting itself after completing the normal system startup. I can barely open any app. So I need to backup my files and do a factory reset. Any ideas? Thanks!
I think you need to get rid of TWRP and root the stock ROM, then flash TWRP using an app running on your tablet. Do not use a PC to flash the recovery. Also, if you are installing a zip, you must do it on the device, not through your PC.
Ka-B00M said:
I think you need to get rid of TWRP and root the stock ROM, then flash TWRP using an app running on your tablet. Do not use a PC to flash the recovery. Also, if you are installing a zip, you must do it on the device, not through your PC.
Click to expand...
Click to collapse
That doesn't make sense. Odin exists for the exact purpose of flashing through a PC, in case your recovery or anything gets damaged.
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.
Why nobody use orangefox?
is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable
joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.
CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?
I wanna start by saying that I tried all kinds of Googling and searching this site, and kept finding answers that are really close to my question, but not.
So I got my old Nexus 6P out, unlocked the bootloader (did that years ago for some reason but don't recall why), installed TWRP, formatted, installed stock image from Google Devs or whatever, installed TWRP again, rooted, installed SuperSU, Termux, TWRP app, and a few others to make sure that I have root (I have root), and everything was cool up to that point.
I used TWRP to make a backup at that point, flashed the NetHunter zip for my phone (Nexus 6P Angler), and now it won't boot the OS. It will stop at the bootloader. TWRP recovery still works.
When flashing the NetHunter ZIP, I got success messages. For giggles, I tried installing the NetHunter ZIP twice in a row, and the status messages indicated that it detected some components were already there, so it seems like it is installing, but just not booting.
If this were a computer, I would see if the boot config or partitions needed adjustment, but I'm not sure how to do this from TWRP.
Also, I have the phone in dev mode, usb debug mode, and have ADB and FASTBOOT installed on my computer (Linux Mint something from 2019 or 2020) and all the hardware IDs for FASTBOOT installed and both ADB and FASTBOOT seem to be working perfectly.
When I restore the backup, it takes me back to a working phone, sans NetHunter.
I really want the full install to take advantage of the custom kernel that a allows for WiFi and USB stuff.
I'm sure I'm making at least one silly mistake. Any help would be wonderful!
[email protected] said:
I wanna start by saying that I tried all kinds of Googling and searching this site, and kept finding answers that are really close to my question, but not.
So I got my old Nexus 6P out, unlocked the bootloader (did that years ago for some reason but don't recall why), installed TWRP, formatted, installed stock image from Google Devs or whatever, installed TWRP again, rooted, installed SuperSU, Termux, TWRP app, and a few others to make sure that I have root (I have root), and everything was cool up to that point.
I used TWRP to make a backup at that point, flashed the NetHunter zip for my phone (Nexus 6P Angler), and now it won't boot the OS. It will stop at the bootloader. TWRP recovery still works.
When flashing the NetHunter ZIP, I got success messages. For giggles, I tried installing the NetHunter ZIP twice in a row, and the status messages indicated that it detected some components were already there, so it seems like it is installing, but just not booting.
If this were a computer, I would see if the boot config or partitions needed adjustment, but I'm not sure how to do this from TWRP.
Also, I have the phone in dev mode, usb debug mode, and have ADB and FASTBOOT installed on my computer (Linux Mint something from 2019 or 2020) and all the hardware IDs for FASTBOOT installed and both ADB and FASTBOOT seem to be working perfectly.
When I restore the backup, it takes me back to a working phone, sans NetHunter.
I really want the full install to take advantage of the custom kernel that a allows for WiFi and USB stuff.
I'm sure I'm making at least one silly mistake. Any help would be wonderful!
Click to expand...
Click to collapse
Get rid of SuperSU and use Magisk root instead. SuperSU is old news and no longer supported. Magisk is the current and most reliable rooting method these days.
Flash the stock image, install TWRP, then flash the Magisk.zip and you'll be rooted. Then continue from there.
Sent from my SM-S767VL using Tapatalk
I formatted, installed factory image, installed TWRP, flashed Magisk, confirmed root, flashed NetHunter ZIP, same result
Droidriven said:
Get rid of SuperSU and use Magisk root instead. SuperSU is old news and no longer supported. Magisk is the current and most reliable rooting method these days.
Flash the stock image, install TWRP, then flash the Magisk.zip and you'll be rooted. Then continue from there.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
So if anyone else is facing the same issuing of wanting to install this old(ish) software onto this old(ish) hardware, and got stuck in the same place as me, here are the three steps that I had to take to succeed that were not in official documentation:
1)When flashing the factory Android image, make sure that you are using the newest version that is supported by NetHunter. At time of writing, this is not the same as the newest version of Android.
2)Remove the -w option from the installation script
3)Be sure to install a compatible kernel from builds.nethunter.com
Thanks again to @Droidriven for the tip on using Magisk