Kali Linux Nethunter Causing Hard Brick?! - ONE Q&A, Help & Troubleshooting

SO......
The title says most of this. I am installing kali linux nethunter with the latest software.
I have tried twice with Cyanogen OS 12.1. I do a clean (factory image) installation, then install the nethunter zip directly after.
POOF! My device will not boot into the bootloader, system, or recovery. it gets stuck on both the recovery and system splash screens and i must use the Color.zip method to retrieve the device from a hard brick.
I have tried installing it over the COS 12.1 xxx2K1 version and i am currently trying to install it over the current release of CyanogenMod 13 (Not cyanogen OS 13)
Has anyone been able to successfully install nethunter on the most recent versions of software?
any help is appreciated. thank you!
Update:
Device still bricks with CyanogenMod 13 as well

Related

Soft brick, could use some help

I saw an ancient Nexus S in a random drawer in my house. I figured It would be perfect for working out with since I have a Note 5 and it's a little big to carry around. I intended to use it for running only with endomodo. When I booted I noticed Cyanogen mod was installed. It booted up just fine but there was no play store. So like an idiot, I decided to just download the latest play store APK and install it. The app installed but crashed. I rebooted and now I'm stuck in a boot loop. Any help would be greatly appreciated!
You could boot to the recovery system, here you might be able to access all files, and you could try to remove the wrong apk. Alternatively just install the latest nightly version of CyanogenMod from April 2016, thus overwriting your operating system. Then install "gapps" for Kitkat (Android 4.4). There should be instructions on the CyanogenMod website or in this forum about which ones are valid. Make sure they are suitable for Android 4.4.4. You could also consider updating the recovery, if you like, before doing anything else. The latest working version is TWRP 2.8.7. Keep in mind that the device's nickname is "crespo", and do not install any binary that was built for any other device.
Perhaps it would also be sufficient to just reinstall the gapps using the recovery system. Make sure the gapps match the Android version.
So what would I do (brute force method)?
- Start device in recovery mode.
- Check recovery version. If it's not TWRP 2.8.7.0, install this one using the fastboot method, i.e. start device to bootloader, download TWRP to computer, install adb and fastboot on the computer and use the "fastboot" method to install the Recovery system (must be "twrp-2.8.7.0-crespo.img").
- Start TWRP
- Make a factory reset of the device
- Use computer to download latest CM nightly "cm-11-20160410-NIGHTLY-crespo.zip" and copy it to the device.
- Use computer to download suitable gapps package and copy it to the device
- Use TWRP to install both CM and gapps.

Help, cannot flash in TWRP and I don't have an OS

Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
Please, help me, is it a hardware problem that can't be fixed or does it have solution?
Flash stock lollipop 5.1 ROM
later flash latest twrp recovery image file.
Later download latest lineageos from official website and nougat opengapps from official website
This should solve your problem
If you still face problem visit lineage wiki page about falcon for detailed guide to install lineage ROM
SunilSuni said:
Flash stock lollipop 5.1 ROM
later flash latest twrp recovery image file.
Later download latest lineageos from official website and nougat opengapps from official website
This should solve your problem
If you still face problem visit lineage wiki page about falcon for detailed guide to install lineage ROM
Click to expand...
Click to collapse
Hey, I tried to flash stock lollipop ROM in fastboot mode many times but it doesn't boot into the system, when it finishes I try to boot the phone but it boots me into fastboot mode again, it just can boot into fastboot, ¿what can I do?

Oneplus one bricked twrp not loading and no rom installed

Hello everyone!
I am new here and really looking forward for some answers. I own oneplus one and had a good experience with it. I had upgraded to custom rom that is lineage os 14.1
I wanted to upgrade it to 15.1 through Twrp. I followed the same procedure as i did for last flashing. I wiped the old data and everything and started to flash new rom. But this time twrp was giving an error. When I did research on that i found that i needed to upgrade to newer version of twrp to install lineage os 15.1
I did the same. And then end of it I just unselected the Supersu root and it reboots. Now when I go to the twrp recovery. The oneplus icon shows but then nothing happens. My phone now doesn't have a rom and twrp recovery won't open. When I connect it to my laptop through fastboot, cmd doesn't recognizes the device. I don't have any knowledge about tech and stuff. And I might have done something wrong. Please help me with some solutions
First of all, try to reinstall TWRP trough fastboot (boot in bootloader mode with Volume UP + power), just google a guide if you don't know how fastboot works. also be sure to use the correct twrp for bacon
After that you should be able to boot back in recovery and flash your rom
if still it doesn't work, follow this guide
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Sometimes it happens we brick our phones but No worries as long as you can go to fastboot you can always restore back to how it was before.
Either use the Program the guy above provided or this guide:
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I want to know how to flash the twrp again through fastboot, because when I connect it, phone is not detected in cmd. It says no fastboot devices are there. But then I checked and it says some android thing is connected in device manager. I hope it is my Oneplus one. How to pass this step?
It's the android drivers. Make sure you have the drivers installed.
Thank you so much. I was able to download the twrp again and flashed the 14.1 lineage os. The latest twrp is not flashing in the phone i don't know why and because of that 15.1 lineage os is not flashing and shows error. But still it's a relief that my phone is working. Also, when i switch on the camera it's not working and the flashlight icon also is dim and doesn't gets clicked and not works.

OP6 won't get past bootloader after upgrading from 16 to 17.1

I decided it was finally time to upgrade to the newer LineageOS 17.1 branch nightlies from my previous installation of 16, rebooted to recovery and sideloaded lineage-17.1-20201013-nightly-enchilada-signed.zip onto it from https://download.lineageos.org/enchilada .
After doing so it appears the recovery successfully updated, it has a new purple skin it didn't have before, however the actual ROM won't start. Instead it goes to fastboot mode and asks whether I want to Start/Restart/Recovery/etc, but I can only get into fastboot or recovery mode.
I've tried flashing older nightlies, but even with 20200922 the issue was still there. I did notice there was a ton of updates in that specific release so I wonder if anything is broken in there.. unfortunately that's also the oldest available nightly so without compiling my own there's no way I can test whether older ones are functional, unless someone here has an older version available perhaps.
I did notice doing adb sideload only makes it go to 47% before the phone goes to installing it, however maybe that's normal, I haven't used it in a while so I don't know for sure. I tried using ADB to push an image onto /tmp, however the new recovery only seems to have 'Apply from ADB' as option so I can't actually install it from there.
Does anyone have any ideas I could try, or perhaps an older LineageOS nightly from before 09-22 laying around somewhere? Any help or suggestions much appreciated!
PPS: Of course I forgot to mention but I also did a factory reset, but that did not help. unsure what else to try besides compiling a rom myself or trying other roms from the forums here, though I'd very much prefer having LineageOS..
I found the reason. I had to install the official Oneplus 6 ROM first, probably to get the right vendor binaries/kernel modules/drivers.
This is what I did:
- fastboot boot TWRP ( TWRP can be found here https://twrp.me/oneplus/oneplus6.html )
- wipe -> advanced wipe -> all the things (technically optional but if you want to get rid of GApps etc this is needed)
- adb sideload official OnePlus 6 'Oxygen' ROM ( https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156173727 )
- reboot, fastboot boot TWRP
- run the 'copy partitions' zip from https://androidfilehost.com/?fid=8889791610682929240 to copy Oxygen to the other A/B partition
- Install latest build from https://download.lineageos.org/enchilada
- reboot, optionally boot TWRP again and install GApps, also optionally install TWRP, reboot, enjoy.
PS: Please note that after this you shouldn't switch A/B partition without first flashing another nightly or something over it, i.e fastboot boot twrp and install latest lineageos again, otherwise you'll end up booting the vanilla Oxygen rom

Flashing LineageOS 18.1 after using LOS 19.1 results in fastboot loop

Hello there,
I have some sort of a problem (although my phone is still working.. yet)
I recently flashed my OnePlus 6 with LineageOS 19.1 (coming from OxygenOS 11.1.2.2).
I flashed "copy_partitions.zip" first and then the official LineageOS 19.1 ROM without GApps,
but because I wanted to use some features, which needed at least the presence of Google Services, I flashed the "LineageOS for microG" (19.1) ROM.
Which worked like a charm.. besides I was very unhappy because of the lack of customization regarding color-theming and the changes made to the QuickSettings of Android 12 in general..
So I thought I could clean flash LineageOS 18.1 / ("Lineage for microG") to get the old theming back..
So what I did was installing the official custom LineageOS recovery from 18.1 (because microG had none for 18.1),
hit "Factory Reset" and afterwards applied the Lineage 18.1 zip over adb.
A message "Update package is older than the current build, expected a build newer than timestamp [...] but package has timestamp [...] and downgrade not allowed" along with the Question to install anyway appeared right after sideloading it to the phone.
I decided to hit "Yes" because I don't needed to backup any data from the phone and wanted to wipe clean anyways... (which I thought I did with "Factory Reset)
So I installed and afterwards rebooted to recovery to flash Magisk aswell..
After rebooting to system then, the phone entered the fastboot loop.
No matter what I do, it still doesn't boot to system after installing 18.1 from LineageOS recovery (also tried with the newest microG recovery from 19.1).
I also known you would wipe system, cache and data (and maybe vendor aswell) prior to a clean custom ROM flash (via TWRP)..
So flashed TWRP 3.6.2 (latest) for enchilada and tried to wipe my system, vendor and cache, but didn't manage to find "system" or "cache" on the advanced wipe menu, so I formatted and wiped data and wiped vendor.
Then installed LOS 18.1 via TWRP also..
But same problem - fastboot only.
also after my TWRP journey, sometimes when flashing the LOS recovery and booting it, a message appears on screen:
Failed to bind mount /mnt/staging/emulated/media/0 [...]
The thing is, I can install LOS 19.1 (microG) without any problems and it would boot,
but I just want to downgrade and I found no guide for my device (or any with ramdisk and A/B slots)..
And there is also no link to MSMDownloadTools for Android 10 (because onepluscommunityserver.com is offline)..
The links from this post and some other posts I found aren't working anymore..
- Is there a way to go back to LineageOS 18.1? What would be the intended way (not doing a downgrade but flashing clean)?
- Is my phone softbricked somehow? (partitions broken or corrupt?)
- Is it a firmware problem?
(I am on security patch from November 2021)
But I don't know what exactly happened to my firmware when flashing Lineage 19.1 over OOS 11.1.2.2
This is my first post as it is my first Android phone/flashing experience in general.. so I hope I got everything right from all I found out until now..
I really appreciate any help / even if it is just saying I messed up and need to go EDL mode... (if it truly is the case)
Thanks in advance.
You people are great!
o/

Categories

Resources