Database Info

Kali Linux Nethunter Causing Hard Brick?!

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

CM 13 on XT1031 -- boot loop

I'm trying to install Cyanogenmod 13 on a Moto G -- according to the person who sold me the device, it was a XT1031, but I haven't actually verified this is the correct model. (Edit: I took off the rear case and verified that it was the XT1031 model.)
I'm using these instructions: https://wiki.cyanogenmod.org/w/Install_CM_for_falcon
I have adb and fastboot installed and working properly on OS X.
I used the Motorola Bootloader Unlock process to unlock the bootloader.
I installed the TWRP recovery image and am able to enter that recovery app. Specifically, twrp-3.0.2-0-falcon.img
The first time I tried to install Cyanogenmod from TWRP, I got error code 7 saying that my bootloader version, 4113, was not correct.
script aborted: This package supports bootloader(s): 0x4118, 0x4119, 0x411A; this device has bootloader 0x4113.
This package supports bootloader(s): 0x4118, 0x4119, 0x411A; this device has bootloader 0x4113.
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard/cm-13.0-20161006-NIGHTLY-falcon.zip'
Click to expand...
Click to collapse
Subsequently, I downloaded (https://www.mediafire.com/folder/nd7xvjndir52j/motoboot#tf9bzbdkxwkn3) and installed motoboot_4118.zip successfully, allowing the CM13 installation to complete.
However, when I reboot normally, the device is permanently stuck at the animated Cyanogenmod logo screen. (I left the device in that state overnight with no changes, so it's not just being slow.) This is consistent for the latest nightly build of CM13 and the latest stable build.
This comment (http://forum.xda-developers.com/showpost.php?p=65319505&postcount=7) suggested going into Recovery and wiping some stuff before installing CM, so I tried this by going into TWRP, choosing Advanced Wipe, and selecting the System, Data, and Cache checkboxes, and wiping, and then re-installing CM. However, this did not resolve my boot loop problem.

urjhnbnreaf said:
I'm trying to install Cyanogenmod 13 on a Moto G -- according to the person who sold me the device, it was a XT1031, but I haven't actually verified this is the correct model. (Edit: I took off the rear case and verified that it was the XT1031 model.)
I'm using these instructions: https://wiki.cyanogenmod.org/w/Install_CM_for_falcon
I have adb and fastboot installed and working properly on OS X.
I used the Motorola Bootloader Unlock process to unlock the bootloader.
I installed the TWRP recovery image and am able to enter that recovery app. Specifically, twrp-3.0.2-0-falcon.img
The first time I tried to install Cyanogenmod from TWRP, I got error code 7 saying that my bootloader version, 4113, was not correct.
Subsequently, I downloaded (https://www.mediafire.com/folder/nd7xvjndir52j/motoboot#tf9bzbdkxwkn3) and installed motoboot_4118.zip successfully, allowing the CM13 installation to complete.
However, when I reboot normally, the device is permanently stuck at the animated Cyanogenmod logo screen. (I left the device in that state overnight with no changes, so it's not just being slow.) This is consistent for the latest nightly build of CM13 and the latest stable build.
This comment (http://forum.xda-developers.com/showpost.php?p=65319505&postcount=7) suggested going into Recovery and wiping some stuff before installing CM, so I tried this by going into TWRP, choosing Advanced Wipe, and selecting the System, Data, and Cache checkboxes, and wiping, and then re-installing CM. However, this did not resolve my boot loop problem.
Click to expand...
Click to collapse
I have the exact same problem on the same phone (XT1031) and have gone through the same steps except I'm still at the 41.1A boot loader.
The other thing worth mentioning is now the phone shows up with "fastboot devices" but adb can not find it so I had to load different firmware using USB OTG flash drive.
===
I got it booting. I think the issue was I had to install the CyanogenMod Recovery from https://download.cyanogenmod.org/?device=falcon. Once I installed CyanogenMod Recovery ( cm-13.0-20161008-NIGHTLY-falcon-recovery.img) in place of TWRP and then installed cm-13.0-20161008-NIGHTLY-falcon.zip via USB OTG it booted up.

nooky1 said:
I have the exact same problem on the same phone (XT1031) and have gone through the same steps except I'm still at the 41.1A boot loader.
The other thing worth mentioning is now the phone shows up with "fastboot devices" but adb can not find it so I had to load different firmware using USB OTG flash drive.
===
I got it booting. I think the issue was I had to install the CyanogenMod Recovery from (snip). Once I installed CyanogenMod Recovery ( cm-13.0-20161008-NIGHTLY-falcon-recovery.img) in place of TWRP and then installed cm-13.0-20161008-NIGHTLY-falcon.zip via USB OTG it booted up.
Click to expand...
Click to collapse
Can you explain how you installed CM from CM Recovery? I can't seem to find an appropriate option. When I select Apply Update => Apply from ADB, it won't let me select the "ADB Sideload" option, and adb says that my device is offline.
Note: Whenever I flash the "recovery" partition with the nightly or stable build of CM13 Recovery while in Fastboot Flash Mode, I get a "Mismatched partition size (recovery) message" in the console window.

I was able to get CM13 installed and started finally.
One change I made was to install CM13 Recovery, do a factory reset from there. Stuff broke, including the ability to use adb, so I went back to twrp-3.0.2-0-falcon.img. There I tried installing CM13 one more time, and it worked this time.
Unfortunately, I can't say exactly what made it work this time around, but I'd speculate that it was the "factory reset" operation that did it.

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.

[SOLVED] Installing ANY custom ROM bricks Oneplus 6

Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
INSTALLATION TUTORIAL
Italic = recommended, but not mandatory. Do it if something doesn't work properly
0) DON'T RESTORE your apps until everything is set up, otherwise you'll have issues with GCM (getting instant notifications from messaging apps for example)
1) Reboot to blu spark TWRP
2) step deleted
3) Flash OOS
4) Flash TWRP
5) Reboot to recovery
6) Flash OOS
7) Flash TWRP
8) Reboot to recovery
9) Flash your custom ROM + TWRP + reboot to TWRP
10) Flash again your custom ROM + TWRP
11) Reboot to recovery
11 bis) Wipe data ("factory reset")
12) Flash Magisk
13) Reboot to system. It's just to make sure the installation worked.
... more on link
Click to expand...
Click to collapse
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.​- reboot, let it complete​- apply again​2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 7​14 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery​[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.​16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.

This is a bad phone .. I have it too
تم الإرسال من ONEPLUS A6003 باستخدام Tapatalk

But you seem (from post history) to be able to install ROMs :crying:
As most of those who try i guess.
Maybe my phone is somehow damaged

What some guides miss out is that you have to install everything twice. Once on slot A and once on slot B and after each install, verify what slot you are on before reboot and then check what slot you are on after reboot. I ran into issues flashing Havoc OS onto my phone too and figured it out in the end after so many times that I was in fact installing stuff twice on the same slot because it never switched over. I'll run you through the order I did things so hopefully you can follow.
-Use MSM Tool to revert everything back to stock and once the phone is booted, update to 9.0.9 either by downloading the update through the phone or by local upgrade if you have the file to hand. (remember to only have the OOS file present as any other OS in zip form crashes the local updater). You don't need to do this if you are already rocking stock Oxygen OS.
-Once the phone has restarted after the upgrade, let the post update procedure finish before continuing.
-Enter developer mode and enable OEM unlocking, Advanced Restart and USB Debugging. From here, reboot to bootloader.
-Plug your phone into the PC now and assuming you have fastboot setup ready on your PC, type 'fastboot oem unlock' and use the volume keys to select the option to unlock and press the power button to select.
-After the phone has completed it's wipe cycle, re-enable Advanced Restart and USB Debugging. The OEM unlock option should be greyed out as it's already been enabled. Make sure you don't add a pin code or password just yet as you will enable encryption which will make the next steps harder than it should be.
-Boot back to bootloader and type 'fastboot boot twrp.img' (or whatever you named it. Make sure that the image file is in the same folder you initiated cmd or powershell)
-Once booted into TWRP, flash blu_spark TWRP as that supports encryption apparently and is more stable than any other. To make sure that the script executed on both slots, hit reboot and check what slot you are on and tap the button for the other slot. Now reboot back to recovery, check you are on the other slot and flash it again.
-Now flash your 9.0.9 OOS zip followed by TWRP once on slot A and once on slot B while making sure you are on the other slot when doing it a second time. Remember that you have to re-flash TWRP after any flashable file that alters the boot partition before you reboot or you will undo all your work. Just make it habit that you re-flash it every time and you should be good.
-Once OOS and TWRP have been flashed on BOTH slots, reboot back to recovery and do the whole process again with your custom ROM (Remembering to flash TWRP before you reboot and checking which slot you are one before and after each flash).
-Once that has completed, reboot back to recovery and flash Magisk on each slot and GApps or MicroG if your ROM supports it. You don't need to re-flash TWRP after this but I do anyway to keep the habit lol.
-Entirely up to you, but before you reboot to your fresh new OS, you can wipe internal storage ONLY if you want all traces of your previous OS gone, but this will also remove personal files etc. I generally just head into TWRP file manager and delete the Android folder and keep the rest.
If you run into issues like crashes on your new OS, reboot to recovery and do a factory reset, but you will also need to re-flash Magisk again. GApps installs itself to system, so you won't need to re-flash that. MicroG does not and will need setting up again. One thing that took me a while to realise is that if you try rebooting while your USB is plugged into your PC, you will sometimes enter download mode, so only keep it plugged in when you need it for MSM Tool or to transfer files across.
I'm pretty sure I put everything down the way I did it and didn't miss anything, but it is late and I am half asleep. Will check back in the morning and double check with a fresh brain.

Many thanks for your exhaustive reply!
Will follow this tomorrow morning with a fresh brain

Fixed!
Now I'll write a guide for those in the same situation.

franticboe said:
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.​- reboot, let it complete​- apply again​2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 7​14 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery​[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.​16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
Click to expand...
Click to collapse
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.

i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
Click to expand...
Click to collapse
If you are stuck on fastboot try
fastboot set_active other
then try rebooting recovery if fails try
fastboot boot pc-stored-twrp
I found changing the active slot via fastboot may unbrick it without msm. It all depends on what steps you actually take during installation.
For installing LOS try not flashing twrp after installation. Los comes with its own recovery. Anyway if it says no OS installed you HAVE to fix recovery bootloop.

[Q] Kind of bricked tablet but works oO : no gapps and restricted by Family Link

Hi,
[first post here]
I just flashed Omnirom 7.1 on a Nexus 10 because it was lagging with Omnirom 6.1 using the TWRP recovery that was present.
[NOTE : I don't think the ROM or the tablet are relevant to my issues]
I made a mistake and tried to flash the nano gapps (instead of pico) and it failed. I thought I'll do that later, wiped cache and rebooted.
It rebooted OK. The system works much better.
Unfortunately, the tablet is supervised by Family Link (and I did not allow my son to get into developper mode).
Now are the issues...
I'm no longer root (as I can not enter any parental code) and I can not enter developer mode (forbidden by Family link), so no USB debugging.
Family Link app crashes (I guess because of gapps is not installed properly).
Recovery got dead in the process (no more TWRP recovery or any recovery).
Bootloader is 'waiting for download' only (download what ?).
I have the official TWRP app and sometimes I can run it without crash but as the user is not root (the system is rooted, though) it seems like a dead end.
I have a Termux app but, again, it does not run as root so I can not edit the system file that would enable me to flash a new recovery...
I tried to activate adb over TCIP on the tablet but it needs 'UDB debugging enabled' oO.
I understand that I made a few mistakes (gapps, not allowing to enter developper mode in Family Link,...)...
If someone has an idea to allow me to flash anything (ROM, TWRP, gapps,...), I'd be quite grateful... as I feel I now have a soft brick...
Thanks,
Z

have you tried flashing a custom rom or a stock rom trough odin?

Thanks for taking the time to answer.
Since my post, I've read that, in bootloader mode, the device does not need to be 'USB debugging enabled' (that's a relief).
With the device in bootloader mode ('Downloading' and no choice other than 'start'), I'm now trying various tools (adb/fastboot/Nexus Root Toolkit, but not Odin yet) to flash something and I suspect that I don't have the correct USB drivers for it. My PC does detect the USB device but the flashing tools don't (yet).
At least, I now have a lead I can follow...
Thanks for your help and sugestion.
I'll report back when I get something interesting...

Hi Again,
I managed to flash TWRP via Odin... Pretty straightforward tool (despite a cryptic interface)... Thanks a lot for suggesting it.
I was then able to get into TWRP (from the boatloader, that proposes other options than just 'start')...
I then flashed the gapps. The tablet rebooted during the flashing (?)...
I'll have another try... There's hope !
Thanks again !

Hi,
I retried flashing gapps thru TWRP and it now works...
Thanks