Related
Recovery BootStrap (TWRP) - Motorola Defy\Bravo
Version: 4.0
Install Recovery BootStrap (TWRP) for Motorola Defy\Bravo via a USB cable. For computers running the Windows\Linux (port version) operating system.
Download: (Windows: MEGA / Google Drive) | (Linux: port by nastys post>>)
Install Recovery BootStrap (TWRP) you can right out stock firmware (without custom recovery) with superuser.
Recovery BootStrap (TWRP) - for the recovery say thank Quarx, after installation, you can install the rom CyanogenMod from Quarx for December 2014 (but do not forget about resize.zip).
Can be installed on Defy (MB525), Defy Plus (MB526), Bravo (MB520).
Requirements for smartphone:
Enable USB debugging
Superuser (ROOT)
Free space on the memory card of 100 megabytes
Instructions:
1. Download the archive
2. Unpack it somewhere else with a short path, for example D:\andro
3. Connect your phone via USB cable ("debugging on USB" should be included)
4. Run the install_bootstrap.cmd
5. When you see the label "Let's Start? =)", press any key
6. If the superuser ask permission for full access "ADB Shell", allow.
7. After installing the smart phone will automatically restart
!IMPORTANT! after restarting the Stock firmware will not start!, but you will have BootStrap (TWRP) so you can safely install custom firmware\rom
Change log:
V3:
Changed how the script
Fixed installation errors recovery on Android 4.x and later
V4:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and later)
Made for normal (mortals) users , before you start the installation script checks (by model) which smartphone connected to the computer, if your smartphone is not supported script report it and stop installation, if supported will give something "Device: MB525".
Serviceability checked on the Chinese 231 (Defy) firmware with superuser (what say thank borndead), and on the Asian 231 (Defy)
Questions\FAQ:
Error "[ERROR] Verify device!", what to do?
Error "[ERROR] Verify device!", it is may mean the following:
1. You have not enabled USB debugging
2. Your smartphone does not support this Recovery. (only for MB525, MB526, MB520)
3. You need to confirm the action ADB on your smartphone
4. Or you have some other connection problems
Stock transition to CyanogenMod 11 of Quarx
Stock transition to CyanogenMod 11 (firmware and find all necessary files can be here) of Quarx in short (generally as described on the website Quarx, only simpler and under Windows)
1. Install Recovery BootStrap (TWRP) via USB
2. Enter Recovery install resize.zip
3. Restart your smartphone
4. Install CyanogenMod 11 and GApps
Good work, comrade! I flashed CM11 on the Moto Defy - everything works!
We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.
Does this mean, it is possible to recover TWRP from PC? That would be a step a head!
This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...
Unfortunately I don't use Windows...
@Octanium91 Would you mind if I port your script to GNU/Linux?
starbright_ said:
We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.
Does this mean, it is possible to recover TWRP from PC? That would be a step a head!
Click to expand...
Click to collapse
I tried to do something like that, is not yet happened. Perhaps in the future even try
nastys said:
This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...
Unfortunately I don't use Windows...
@Octanium91 Would you mind if I port your script to GNU/Linux?
Click to expand...
Click to collapse
Maybe. If Iunderstand with GNU/Linux scripts
The new version, V4
The new version, V4
Changes:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and higher)
More debugging: Now the script itself is not closed, and tells the user exactly what happened.
Sorry debris removal only works on Android 4.x and later.
Linux port done!
@Octanium91 I ported it to C++ (for Linux only at the moment). Please add it to the first post . Here is the link: MediaFire | MEGA
On Ubuntu just mount the ISO as image (not archive) then click 'Run' (or you can also extract the ISO and run the executable directly). It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included in the ISO. Tested on Ubuntu 14.10 and 16.04 (64 bit).
I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine
Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code. EDIT: they are the same file with different names. I updated my version to support MB520.
After run the command script, when i boot in TWRP SDcard shows 0mb.
Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.
With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.
Any help?
Thanks!
evilinheaven said:
After run the command script, when i boot in TWRP SDcard shows 0mb.
Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.
With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.
Any help?
Thanks!
Click to expand...
Click to collapse
Format your SD card (to FAT32) or use another one.
Octanium91 said:
The new version, V4
Changes:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and higher)
More debugging: Now the script itself is not closed, and tells the user exactly what happened.
Sorry debris removal only works on Android 4.x and later.
Click to expand...
Click to collapse
nastys said:
@Octanium91 I ported it to C++ (for Linux only at the moment). Please add it to the first post . Here is the link: https://www.mediafire.com/folder/candnhxj8aovj/Defy_Bootstrap_Installer_for_Linux
On Ubuntu just mount the ISO as image (not archive) then click 'Run'. It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included. Tested on 14.10 x86_64.
I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine
Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code.
Click to expand...
Click to collapse
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.
I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?
I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol. I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!
answer
Aceofzeroz said:
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.
I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?
I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol. I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!
Click to expand...
Click to collapse
Hi!
flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).
If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)
Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap
Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try
Octanium91 said:
Hi!
flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).
If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)
Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap
Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try
Click to expand...
Click to collapse
Many thanks for the prompt and well ordered reply! I'll look into your suggestions and I'm aware that there aren't many available recovery software for our locked bootloader phones.
We were actually trying to get Safestrap working on our device since last month, but it's failing to work correctly in booting our kexec roms. So I thought I'd ask here since the Defy works by using the 2nd boot like us, but it's still under investigation. Thanks again for your assistance, we're not out of the game yet and we'll get things rolling eventually. Take care!:thumbup:
Sent from the Ace's MB865 using Tapatalk
Error. More than one device and emulator
what am i doing wrong?
LoeWn said:
Error. More than one device and emulator
what am i doing wrong?
Click to expand...
Click to collapse
Perhaps you have not enabled USB debugging
Requirements for smartphone:
Enable USB debugging
Superuser (ROOT)
Free space on the memory card of 100 megabytes
I did enable usb debugging
LoeWn said:
I did enable usb debugging
Click to expand...
Click to collapse
You can send us a screenshot?
I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?
Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.
Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all .
Any idea where could be the problem or what I'm doing wrong?
Edit: maybe its related to the bootloader version, which is 09.10
Haldy said:
Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.
Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all .
Any idea where could be the problem or what I'm doing wrong?
Edit: maybe its related to the bootloader version, which is 09.10
Click to expand...
Click to collapse
Based on first screenshots, Recovery installed. Now you need to install system.
Than display goes black and thats all - maybe have to wait
marcooleo said:
I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?
Click to expand...
Click to collapse
In principle it is possible, but it does not make sense.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer: I'm in now way, shape or form a developer. The following steps are to be used as a guideline for installing nethunter onto your device. If something goes wrong during the install/set up process, I won't be held responsible. By installing the roms/nethunter zips you're voiding your warranty so do so at your own risk.
Click to expand...
Click to collapse
Nethunter is in short a set of apps for network penetration testing, you should only use these tools for testing your own network security or other networks YOU HAVE PERMISSION FOR! If you get caught using these tools illegally, do not come crying to me, I'll laugh in your face and point you to this thread.... That being said, let's get on with it.
You're going to need a rooted device for this to work, this thread isn't about rooting, if you're not yet rooted check out the other threads on XDA. Great community with plenty of topics showing you how to root. You have the options of:
cm-13.0 running on Marshmallow with kernel 3.4.111
Lineage-14.1 running on Nougat 7.1.2 with kernel 3.4.113
Both have fully patched kernels and whilst they all have a few issues (not related to the kernels or the first rom you install, check known issues below for updates), you should be able to use 99% of the functions. I'll list the issues at the bottom of this post and the steps to try and fix them if any.
Links
Cm-13.0 links:
CM-13.0: https://www.androidfilehost.com/?fid=817550096634766544
Nethunter: https://www.androidfilehost.com/?fid=529152257862723757
Lineage-14.1 7.1.2 links:
Lineage14.1:https://www.androidfilehost.com/?fid=529152257862728021
Nethunter:https://www.androidfilehost.com/?fid=529152257862723623
Install
Download and copy both of the above files to the root of your device along with the Gapps of your choice.
Reboot into recovery and wipe Dalvik, Data and Cache
Install the CM-13.0/Lineage-14.1 rom
Install Gapps
If you're S-off then reboot into your phone.
If you're S-on, extract the boot.img from the CM-13 file and place it in your fastboot folder.
Run the following command and reboot: fastboot flash boot boot.img
After the boot.img has flashed, run the following command: fastboot reboot
After you've allowed your phone to boot fully, reboot back into recovery and install the nethunter file.
Be PATIENT!! The install can take up to half hour! Once the install has finished, reboot system and you should be golden.
If at any point during the install process TWRP asks you if you want it to install root, select the "Do not install" option. Nethunter will handle this for you.
That's it, you should be fully loaded with nethunter.
Features
HID is fully functioning on both versions.
Supported external wireless drivers are fully functioning. Check the useful links below to find supported devices.
Csploit
DroidDrive
Hackers Keyboard (This comes in so handy when using terminal)
Nethunter VNC
Nethunter Terminal
OpenVPN
Shodan
USB Keyboard
Known issues
Unless stated otherwise, any issue related to lineage-14.1 applies to both the android 7.1.1 version and the 7.1.2 version
Csploit on CM-13.: For some reason, nethunter installs an outdated cSploit for the marshmallow build. If you constantly receive an error message saying "No exploits found", uninstall cSploit and install the latest version from here: http://www.csploit.org/downloads/
cSploit arp poisoning on both cm13 and lineages14: Arp poisoning exploits aren't working for any MITM attacks, I've spoke to the devs and they've confirmed it is a bug, as soon as it's fixed, I'll update this thread.
HID Interface on both cm13 and lineage14: If you have no HID interfaces showing in the nethunter home panel. Open an exploit that uses HID (rubberduck will suffice) and launch an attack, don't worry about plugging your phone into your computer. It's sheerly for forcing nethunter to check the relevant directories for HID interfaces. Once you've launched an attack, they should appear.
Terminal crashing on Lineage14: If your terminal keeps crashing when you try to start it, long press your home screen to bring up the active apps tabs. Close the terminal, open the main nethunter app and wait for it to be granted root privileges, now minimize and try opening the terminal again. For some reason, the terminal requires the nethunter app to be open and with root.
Rubberduck HID not launching attacks: Connect to your target computer, change the USB connection to MTP for file transfer and also enable ADB via the developer menu. Try again
Useful links
Official nethuner wiki: https://github.com/offensive-security/kali-nethunter/wiki
There's a link on there titled "known working hardware" that's where you can check if your wireless card is supported.
Official cSploit wiki: https://github.com/cSploit/android/wiki
Again, links on the page full of useful information.
Kernels:
For some reason, trying to just flash the kernel to an already installed rom doesn't work, so if you'd like to try and build the zImage into your boot.img fell free to.
3.4.111: https://www.androidfilehost.com/?fid=457095661767158370
3.4.113: https://www.androidfilehost.com/?fid=529152257862724031
Thanks and credits
@9Lukas5 for letting me use his kernel
@AndroGeek974 both the cm-13 and lineage-14.1 roms are his, with my kernels and nethunters.
@ZpanicZ The cm-13 nethunter build is his.
Screenshots
Can i use only internal card wireless for airmon-ng start wlan0 ? Or i need external one with otg cable
99% certain the answer will be no if you intend to use it in monitor mode. There's a device that does support monitor mode on the internal card but can't remember what one it was. You can always try it by opening a terminal and typing the following:
Airmon-ng start wlan0
If it works then you'll see a new interface pop up called:
Wlan0mon
I wouldn't hold my breath though, you're better of getting a cheap otg off eBay for a couple of quid and get an external wireless card. There's a link in the first post to the nethunter wiki, they have a list of devices that have been confirmed as working.
Just for your reference. The may unofficial CM14.1 based off 7.1.2 is at https://www.androidfilehost.com/?fid=529152257862723521
Maybe I can dirty flash it?
mobileman88 said:
Just for your reference. The may unofficial CM14.1 based off 7.1.2 is at https://www.androidfilehost.com/?fid=529152257862723521
Maybe I can dirty flash it?
Click to expand...
Click to collapse
Perfect, cheers, downloading it now. May try it out tonight, prob be tomorrow though.
Update
Updated to include the latest lineage-14.1 build running on android 7.1.2, I'm still testing it but the same issues listed in the first post seem to be present with no other issues appearing!
michael8t6 said:
Update
Updated to include the latest lineage-14.1 build running on android 7.1.2, I'm still testing it but the same issues listed in the first post seem to be present with no other issues appearing!
Click to expand...
Click to collapse
Awesome to hear that. Take your time dude. Understand this fixes many rom issues except for Bluetooth which is still funky. Left my m7 at work so can't do anything this weekend. Bummer.
Sent from my Nexus 6P using Tapatalk
mobileman88 said:
Awesome to hear that. Take your time dude. Understand this fixes many rom issues except for Bluetooth which is still funky. Left my m7 at work so can't do anything this weekend. Bummer.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
haha unlucky!! I'd be tempted to drive back and get it
Yeah the bluetooth doesn't like my headset on this build, doesn't find it in pairing mode at all! The rom does seem a lot more stable for sure though.
michael8t6 said:
haha unlucky!! I'd be tempted to drive back and get it
Yeah the bluetooth doesn't like my headset on this build, doesn't find it in pairing mode at all! The rom does seem a lot more stable for sure though.
Click to expand...
Click to collapse
Haha. Work is too much of a drive for me over the weekend. Should I dirty flash from your earlier release? Or spotless I do a full wipe and start anew?
Sent from my Nexus 6P using Tapatalk
mobileman88 said:
Haha. Work is too much of a drive for me over the weekend. Should I dirty flash from your earlier release? Or spotless I do a full wipe and start anew?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
One of the perks of working from home, I only have to drive to the storage unit to collect my eBay orders, other than that I get to spend the rest of my time at home.
Think you have to do a clean flash mate, I tried a dirty flash when I was testing the kernels and although it said it went fine with no errors, when I flashed the nethunter build, none of the apps were showing. I then done a clean flash and everything was working fine. Although, if you do try a dirty flash and it works, let me know please :good:
Some one help me step by step .
i have htc s-on hboot 1.61
When i flash rom i reboot full boot phone
And coming back to recouvery and flashing nethunter . but when i run nethunter app terminal cruch .. Please some one telp hiw to make it true step by step and sorry for my bad english
michael8t6 said:
One of the perks of working from home, I only have to drive to the storage unit to collect my eBay orders, other than that I get to spend the rest of my time at home.
Think you have to do a clean flash mate, I tried a dirty flash when I was testing the kernels and although it said it went fine with no errors, when I flashed the nethunter build, none of the apps were showing. I then done a clean flash and everything was working fine. Although, if you do try a dirty flash and it works, let me know please :good:
Click to expand...
Click to collapse
Thanks for trying it out first. I have also tried dirty flash . It's the same, no go. Everything boots up fine but none of the nethunter apps are showing although the kernel is able to show the hidg devices as checked using adb. The apps are all not showing. Bummer. Doing a full flash now. Hopefully we can easily update to the new daily builds so I don't have to do a full wipe of the device each time. Let me know if there's anything else I can help test it with.
Btw how did you modify the 0501 unofficial build to your 0.0.1 file?
---------- Post added at 10:41 AM ---------- Previous post was at 10:39 AM ----------
Tafabil said:
Some one help me step by step .
i have htc s-on hboot 1.61
When i flash rom i reboot full boot phone
And coming back to recouvery and flashing nethunter . but when i run nethunter app terminal cruch .. Please some one telp hiw to make it true step by step and sorry for my bad english
Click to expand...
Click to collapse
There are steps in the OP for S-ON devices . You need to do a few more steps to get it going
-----
If you're S-on, extract the boot.img from the CM-13/14 file and place it in your fastboot folder.
Run the following command and reboot: fastboot flash boot boot.img
After the boot.img has flashed, run the following command: fastboot reboot
After you've allowed your phone to boot fully, reboot back into recovery and install the nethunter file.
After flashing rom 7.1.1 should i go back to fastboot imidiatly and flashing boots.img or let the phone boot fully and then going back to fastboot and flash boot.img ?
mobileman88 said:
Thanks for trying it out first. I have also tried dirty flash . It's the same, no go. Everything boots up fine but none of the nethunter apps are showing although the kernel is able to show the hidg devices as checked using adb. The apps are all not showing. Bummer. Doing a full flash now. Hopefully we can easily update to the new daily builds so I don't have to do a full wipe of the device each time. Let me know if there's anything else I can help test it with.
Btw how did you modify the 0501 unofficial build to your 0.0.1 file?
Click to expand...
Click to collapse
aye, I'm not quite sure why we're not able to dirty flash, I know when the nethunter app updates you'll get a message next time you open the nethunter main app asking if you want to update, it then downloads the latest apk so you're able to update the nethunter apps. But for some reason, you're not able to just flash the boot.img over a existing install or dirty flash! Annoying I know but I'm not a developer so am stuck on that bit.
As for renaming the build, after I built the kernel, I used a program called android kitchen, extracted the boot.img from the build, then extracted the zImage and ramdisk file, replaced the zImage with mine, repacked and rebuilt the rom whilst renaming.
Tafabil said:
After flashing rom 7.1.1 should i go back to fastboot imidiatly and flashing boots.img or let the phone boot fully and then going back to fastboot and flash boot.img ?
Click to expand...
Click to collapse
Go back to fastboot immediately, once the rom and gapps have finished installing, DO NOT BOOT INTO SYSTEM! Boot into bootloader and run the following commands:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Once it's done flashing the boot image, run the next cmd:
fastboot reboot
Click to expand...
Click to collapse
if at any point during the install process, twrp or your other custom recovery asks if you want it to root, select DO NOT INSTALL..
Wait for the phone to have one full boot after issuing the reboot command before install nethunter.
michael8t6 said:
aye, I'm not quite sure why we're not able to dirty flash, I know when the nethunter app updates you'll get a message next time you open the nethunter main app asking if you want to update, it then downloads the latest apk so you're able to update the nethunter apps. But for some reason, you're not able to just flash the boot.img over a existing install or dirty flash! Annoying I know but I'm not a developer so am stuck on that bit.
As for renaming the build, after I built the kernel, I used a program called android kitchen, extracted the boot.img from the build, then extracted the zImage and ramdisk file, replaced the zImage with mine, repacked and rebuilt the rom whilst renaming.
Go back to fastboot immediately, once the rom and gapps have finished installing, DO NOT BOOT INTO SYSTEM! Boot into bootloader and run the following commands:
Once it's done flashing the boot image, run the next cmd:
if at any point during the install process, twrp or your other custom recovery asks if you want it to root, select DO NOT INSTALL..
Wait for the phone to have one full boot after issuing the reboot command before install nethunter.
Click to expand...
Click to collapse
Cool to know that. I am quite familiar with Kali Linux but am not as familiar with the internals of Android. Learning something new everyday. There are tons of Y-cables on Amazon, not sure if they are all the same and I should simply buy the cheapest one. Definitely need one to power mouse/keyboard/hdd
mobileman88 said:
Cool to know that. I am quite familiar with Kali Linux but am not as familiar with the internals of Android. Learning something new everyday. There are tons of Y-cables on Amazon, not sure if they are all the same and I should simply buy the cheapest one. Definitely need one to power mouse/keyboard/hdd
Click to expand...
Click to collapse
I paid £12.99 for mine from maplins just because I wanted it that day haha, my patience is non existent when it comes to waiting on things in the post. To be honest though I suppose as long as it does what it says on the tin then I'd get the cheapest.
I've got kali and windows 7 as a dual boot, bit of a strange one with kali though, when I installed it with my external graphics card, it would crash and kill my session as soon as I tried to do anything graphic intensive! Worked out it was the external graphics card, so removed it, went to download and install the drivers for it, soon as I tried to install it, the GUI said that it couldn't detect a card (obviously it wasn't plugged in). I tried to plug it back in and install the driver again, then it just killed my session and logged me out like it was before so I'm now having to run onboard graphics! No idea why it was doing that but meh, both windows and kali are running fine with onboards so not to bothered!
I was using kali back when it was called backtrack 4!! Great little distro for testing networks, currently studying for the CEH exams, dream job to be a certified pen tester. Suppose that's why it only took the week to learn all about kernel compiling with toolchains and so on, always been a quick learner, especially when it comes to technology! A computer will only do what it's told to do, so if somethings not working then you just have to find out what went wrong, 99% of the time the developers always code in a escape to a debug log so you can find a fix and apply it!!
If you want any help with kernel compiling, feel free to drop me a pm and we can sort out adding each other on Skype or something, make it a bit easier to communicate. Now I've learnt the basics of it, it's a lot lot easier than it sounded!
This was a great video that explained kernels in a really good informative way!
[YOUTUBE]
https://www.youtube.com/watch?v=AheWTTFwV6k[/YOUTUBE]
michael8t6 said:
I paid £12.99 for mine from maplins just because I wanted it that day haha, my patience is non existent when it comes to waiting on things in the post. To be honest though I suppose as long as it does what it says on the tin then I'd get the cheapest.
I've got kali and windows 7 as a dual boot, bit of a strange one with kali though, when I installed it with my external graphics card, it would crash and kill my session as soon as I tried to do anything graphic intensive! Worked out it was the external graphics card, so removed it, went to download and install the drivers for it, soon as I tried to install it, the GUI said that it couldn't detect a card (obviously it wasn't plugged in). I tried to plug it back in and install the driver again, then it just killed my session and logged me out like it was before so I'm now having to run onboard graphics! No idea why it was doing that but meh, both windows and kali are running fine with onboards so not to bothered!
I was using kali back when it was called backtrack 4!! Great little distro for testing networks, currently studying for the CEH exams, dream job to be a certified pen tester. Suppose that's why it only took the week to learn all about kernel compiling with toolchains and so on, always been a quick learner, especially when it comes to technology! A computer will only do what it's told to do, so if somethings not working then you just have to find out what went wrong, 99% of the time the developers always code in a escape to a debug log so you can find a fix and apply it!!
If you want any help with kernel compiling, feel free to drop me a pm and we can sort out adding each other on Skype or something, make it a bit easier to communicate. Now I've learnt the basics of it, it's a lot lot easier than it sounded!
Click to expand...
Click to collapse
I have already dropped you a PM about the rom packaging and kernel compiles. No hurry. Let me know when's a good time for us to get something going. Btw a new unofficial build just dropped for 0506 . Seems to have been reported to fix the bluetooth issues we are getting.
https://androidfilehost.com/?fid=457095661767159226
---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------
michael8t6 said:
This was a great video that explained kernels in a really good informative way!
[YOUTUBE]
https://www.youtube.com/watch?v=AheWTTFwV6k[/YOUTUBE]
Click to expand...
Click to collapse
Can't seem to get the Youtube link working. (Embedded one does not work, but it works using a separate browser tab, so it's ok)
New 0515 unofficial build out. https://www.androidfilehost.com/?fid=745425885120732208
New User, so apologies if this post is in the incorrect format :fingers-crossed:
Sorry if TL,DR: but the more information on my issue I give you the less chance your advice encounters any variables.
Recently got into ethical Hacking / pentesting.
Wanting to use a nethunter ROM on my Nexus 5 so when I inevitably break something its replaceable and not my gaming rig.
I did the following:
- Installed Nexus Root Toolkit on my laptop.
-Unlocked the boot loader from this first.
-Then installed Root Permissions and TWRP
These initial steps seemed to have worked.
Boot loader marked as unlocked, SU app installed upon booting new ROM, checks as rooted, and TWRP was being interacted with on the next step.
I then selected the 'advanced' menu in the Nexus Root Toolkit.
And flashed the .zip file for the hammerhead nethunter build version 3.0
There was advice to do several things during this step which I have ignored due to not understanding the process.
- installing gapps. I believe the gapps version for hammerhead is 6.0 however it's listed purpose was to allow access to Google play apps which I have so I discarded this step.
- installing over cryogenmod 14.1 as my Android build is marshmallow 6.0.1. This is the advice I received on the official Kali site, that Nethunter was designed to be used over CM, and perhaps my issue as I flashed it over the stock OS for the phone.
Once the nethunter zip file was flashed through the root Toolkit, I rebooted my phone and logged on. After the initial setup I had all of the applications and the background for the KL Nethunter build, however I encounter a major issue trying to set them up.
When I go to set up the Chroot. I select download option, and then "full Chroot install".
I am then prompted with a message saying bad handshake / server error and I am unable to get past this stage.
The error message is " javax.net.sslSSL handshake exception" no valid pins found in chain.
I am not using a mobile carrier only Wi-Fi.
This is killing me because obviously it means I basically don't have nethunter lmao :laugh: really not funny but any human input you guys can offer with this challenge would be immensely appreciated. I want to begin hooking this up to a TP Link Wi-Fi receiver and I'm extremely demoralised by the fact I can't complete what is essentially " the easy bit ".
Disclaimer - I will follow any suggested links to the letter but for the record. I have combed YouTube. Google. XDA and several other sources for a fix to this. I am aware I need a Kali " arm-hf" file however can't find a repository for such a download or I would download it to the Sd and try to mount it manually!
I just pretty much completed the same process on my nexus 7 (2012) which resulted in me being stuck at the same point. Doing a search has lead me here for possible resolution to our issues.
"The error message is " javax.net.sslSSL handshake exception" no valid pins found in chain."
UPDATE:
I was able to locate the file within the zip file we had flashed to install kali.
Full path was /data/local/kalifs-full.tar.xz
I manually extracted and copied to /emulated/sdcard and ran the chroot wizard and chose to install from sd, it's extracting now.
I'll update once extraction has completed (this tablet has the slowest writes, ever..)
Here is the link to kali chroot.
8point6 said:
I just pretty much completed the same process on my nexus 7 (2012) which resulted in me being stuck at the same point. Doing a search has lead me here for possible resolution to our issues.
"The error message is " javax.net.sslSSL handshake exception" no valid pins found in chain."
UPDATE:
I was able to locate the file within the zip file we had flashed to install kali.
Full path was /data/local/kalifs-full.tar.xz
I manually extracted and copied to /emulated/sdcard and ran the chroot wizard and chose to install from sd, it's extracting now.
I'll update once extraction has completed (this tablet has the slowest writes, ever..)
Click to expand...
Click to collapse
build.nethunter.com/kalifs/kalifs-latest/kalifs-i386-full.tar.xz
I see they dropped support for the nexus 7 2012, likely due to lack of space. I was able to get a full extract done, but hope enough info has been relayed to get you and anyone else past the error we had received. If I pick up where I left off, I'll try to provide an update on this, tabled for now.
Hi Fellows,
First of all, I’m newbie to flashing (or so-called) phones. I want to change my phone for de-googled one. I’m thinking about POCO X3 Pro with LineageOS 18.1.
I’ve been recently reading a lot about changing OS, but I feel completely overwhelmed by how complex knowledge it is. Even on the forum there is so much info, so much specific vocabulary/acronyms
Can you advise me, how to start?
Or maybe different way... do you know any reliable service/somebody in the UK, who could help? I've already checked services in my town - no one does software modifications
kamien8 said:
Hi Fellows,
First of all, I’m newbie to flashing (or so-called) phones. I want to change my phone for de-googled one. I’m thinking about POCO X3 Pro with LineageOS 18.1.
I’ve been recently reading a lot about changing OS, but I feel completely overwhelmed by how complex knowledge it is. Even on the forum there is so much info, so much specific vocabulary/acronyms
Can you advise me, how to start?
Or maybe different way... do you know any reliable service/somebody in the UK, who could help? I've already checked services in my town - no one does software modifications
Click to expand...
Click to collapse
You don´t need to pay someone else for that, you can do it by your own.
I will give you the topics in order, one by one, and just search for the info till understand what you are want to achieve.
1-Unlocking bootloader.
2-Flashing a custom recovery.
3-Rooting (optional)
4-installing a custom ROM (like LineageOS)
Search for these topics in your own forum, read carefully and apply them when you are sure what you are doing.
Copied these from my old post in other forums, I updated a little but still might be a little outdated
Spoiler: How to unlock bootloader
Link your poco x3 pro to your MI account
Activate "Find my device" for Mi account
Settings > About Phone > Tab "MIUI version (For POCO)" until developer mode unlocked
Settings > Additional Settings > Developer Options
OEM unlocking - Checked
Mi Unlock status > Add account and device - Do only once, anymore will reset 168 hours unlock counter
Go to https://en.miui.com/unlock/and download the mi unlock software
Latest version to date of this post is https://miuirom.xiaomi.com/rom/u1106245679/5.5.224.55/miflash_unlock-en-5.5.224.55.zip
Prepare for future unlock
Turn off your mobile
Boot into fastboot mode - Volume Down + Power
Run "MiUsbDriver.exe" located in the miflash_unlock_en zip
Connect mobile to PC or laptop
Poco X3 Pro driver should be installed
Run "miflash_unlock.exe" and proceed through the software
If you yet to apply for permission to unlock, you can apply from there (I think, the last I applied was years ago, not sure still a thing now or not)
The software will tell you the countdown which is 168 hours aka 1 week.
Exit fastboot mode on phone by holding the power button.
A week later, time to unlock.
Backup your file, if you have used the phone intensively, unlocking will result in factory reset.
Turn off mobile
Boot into fastboot mode - Volume Down + Power
Run "miflash_unlock.exe"
Connect mobile to PC
Proceed through "miflash_unlock.exe"
Unlocked
Spoiler: How to Flash Custom Recovery
Download google platform tool from https://developer.android.com/studio/releases/platform-tools
Extract the tool
In the tool folder, type "cmd" at "Address bar" to open command prompt to that folder
Press enter after you type "cmd", if it isn't obvious.
Turn off mobile
Boot into fastboot mode - Volume Down + Power
Connect mobile to PC
Go to command prompt window, type "fastboot devices".
Your phone will be shown if detected, otherwise, fix your driver.
Download Custom Recovery
OrangeFox - https://orangefox.download/device/vayu
TWRP - https://forum.xda-developers.com/t/recovery-unofficial-teamwin-recovery-project.4269551/
Lineage OS Recovery - https://download.lineageos.org/vayu
Don't use LOS recovery if you are rooting, it doesn't support OTA data decryption thus magisk need to be reflashed everytime during OTA.
Extract the "img" recovery file to the tool's folder
Type "fastboot flash recovery <filename>"
Done, type "fastboot reboot recovery" or Volume Up + Power on mobile to enter recovery
Spoiler: How to Flash Custom Rom
Connect mobile to PC
Copy files to mobile
Firmware - https://xiaomifirmwareupdater.com/firmware/vayu/
Rom
XDA Roms - https://forum.xda-developers.com/f/xiaomi-poco-x3-pro.12163/?prefix_id=33
Xiaomi EU Rom - https://xiaomi.eu/community/forums/miui-rom-releases.103/
Gapp (if you want)
MindtheGapps
NikGapps
FlameGapps
OpenGapps (Personally Recommended)
Magisk (If rooting) - https://github.com/topjohnwu/Magisk/releases
Boot into recovery - Vol up + Power
install in order
Firmware
Rom
Gapps (if you want)
Magisk (if rooting)
Format data in recovery
Wipe Cache and Dalvik/Art Cache (If the recovery support it)
Reboot into system
Done
If you mess up the format data sequence, don't worry, you can always use "adb sideload". Also, if you use LOS recovery, you need to use sideload.
Look for sideload in recovery
Open command prompt in your tool folder, type "adb sideload <filename>" to install the things you want.
Spoiler: How to flash back or to official rom along with official recovery
Download xiaomi flash tool - https://xiaomiflashtool.com/
Download fastboot package - https://xiaomifirmwareupdater.com/archive/miui/vayu/
Extract xiaomi flash tool, run "XiaoMiFlash.exe"
Extract fastboot package to somewhere, preferably root subfolder of c:\ or whatever drive
Long pathname can cause "XiaoMiFlash.exe" to run into error
Boot mobile into fastboot - Vol down + power
Connect mobile to pc
In "XiaoMiFlash.exe", select folder of fastboot package
Bottom right of the software, choose "clean all" or "clean and lock (bootloader)"
Click flash
Once done, it will auto reboot into MIUI
Spoiler: How to pass safetynet for custom rom
At the moment of this post, most custom roms fail safetynet. It is not absolutely necessary to get safetynet to work. Only do this if the gapps you want to install require it.
Install magisk (No way around it)
Install props config module
Reboot
Run any terminal app - https://play.google.com/store/apps/details?id=com.termux
Type "su" and enter
Grant super user rights to it
Type "props" and enter
Type "1" and enter
Type "f" and enter
Type "22" and enter
Type "6" and enter
Basically, you are choosing "Poco X3 Pro (Global)"
Type "y"
Reboot and test your safetynet
Spoiler: How to make Nasty Anti-Root Apps work with Magisk
In magisk, install Riru module
Download Unshare - https://github.com/vvb2060/riru-unshare/releases
In magisk, install Unshare
In magisk, enable "Magisk Hide" in settings
In magisk, "hide Magisk" in settings, choose some really unpredictable name
In magisk, press "Shield", hide all options (dropdown) for the targetted App
Reboot
Try run the apps multiple times
If fail
Install App Manager - https://f-droid.org/en/packages/io.github.muntashirakon.AppManager/
In App Manager, look for the apps, go to "Services", disable that one "(Isolated)" service.
Double make sure it is applied
Reboot
Try run the apps multiple times
Still fail
Try this, some say it worked
In magisk, install LsPosed module
Install XPrivacyLua - https://repo.xposed.info/module/eu.faircode.xlua
In LsPosed, enable XprivacyLua and Singpass in that same list
Reboot
In XPrivacyLua, look for the app, enable restrict on "Get Applications"
Reboot
Try run the apps multiple times
this is the last resort
Install Shelter - https://play.google.com/store/apps/details?id=net.typeblog.shelter
Clone the App in Shelter
In shelter, under work profile, make sure no rooted apps in there
Reboot
Try run the App in work profile multiple times
SubwayChamp said:
You don´t need to pay someone else for that, you can do it by your own [...]
Click to expand...
Click to collapse
Thanks a lot. It makes sense.
I was also told, that before flashing it is esential to do a backup.
What's your opinion? How to do so?
kamien8 said:
Thanks a lot. It makes sense.
I was also told, that before flashing it is esential to do a backup.
What's your opinion? How to do so?
Click to expand...
Click to collapse
About backup the first important is what is important for one, I mean personal information like messages, call, WhatsApp and so on.
But the most important in other sense is about the well functioning of the device itself, for example EFS where is stored the IMEIs, sometimes vendor, dtbo and persist images depending on the custom recovery if it includes these options.
Particularly, I never need any other partition from recovering eventually my device/s.
I would like to suggest you to try flashing some roms on any other device which you don't use(for ex. an old abandoned phone) and gain some experience before trying on your poco x3 pro.
dey18 said:
I would like to suggest you to try flashing some roms on any other device [...]
Click to expand...
Click to collapse
That was my idea. Unfortunately the only 'old' phone I've got is Huawei P9 Lite 2017 with Android 7. I haven't found any information, that there is a way to install LineageOS on the device.
However, for training purposes I could install any different OS, suitable for the device. Do you know any?
By the way, is the following link the only valid repository for the OS?
LineageOS Downloads
download.lineageos.org
kamien8 said:
That was my idea. Unfortunately the only 'old' phone I've got is Huawei P9 Lite 2017 with Android 7. I haven't found any information, that there is a way to install LineageOS on the device.
However, for training purposes I could install any different OS, suitable for the device. Do you know any?
By the way, is the following link the only valid repository for the OS?
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
yes, thats the official site
kamien8 said:
That was my idea. Unfortunately the only 'old' phone I've got is Huawei P9 Lite 2017 with Android 7. I haven't found any information, that there is a way to install LineageOS on the device.
However, for training purposes I could install any different OS, suitable for the device. Do you know any?
By the way, is the following link the only valid repository for the OS?
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
If you had no experience of flashing a phone, read and follow this guide with Pictures :
https://forum.xda-developers.com/t/4288121/post-85137963
It should be sufficient to help you flash a ROM.
No tutorial about backup data from phone in that guide, you have to do it on your own.
pl1992aw said:
If you had no experience of flashing a phone, read and follow this guide with Pictures :
https://forum.xda-developers.com/t/4288121/post-85137963
It should be sufficient to help you flash a ROM.
No tutorial about backup data from phone in that guide, you have to do it on your own.
Click to expand...
Click to collapse
I like this method, and this specific guide is what helped me flash custom rom on my X3 pro.
It is detailed and even gives notice if in case we get lost in a step.
I hope the OP can read this as the guide was really helpful. I know they used arrowOS for example, but I applied the method with different rom.
kamien8 said:
That was my idea. Unfortunately the only 'old' phone I've got is Huawei P9 Lite 2017 with Android 7. I haven't found any information, that there is a way to install LineageOS on the device.
However, for training purposes I could install any different OS, suitable for the device. Do you know any?
By the way, is the following link the only valid repository for the OS?
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
I suggest you to try any other roms available for your device and not just lineage.
Try flashing multiple roms one by one and identify and rectify your errors.
And don't forget to read documentation provided by the wiki completely and also check out some vids on youtube(people on telegram would tell you to watch yt channel named "Munchy" because he has got this phone).
I wouldn't try and flash an old p9 lite. I remember when I had a p9 and tried to flash it it was a nightmare and was an unorthodox method. If you could grab an old Moto like the Moto g as that would be ideal for a practise flash.
Warren_Orange said:
[...] Moto g [...]
Click to expand...
Click to collapse
I've never used Motorola before. Which G would be good to start gaining an experience?
I'll try to find a pre-owned one.
I'd go for a moto g 2nd or 3rd Gen. You can get them for peanuts on eBay and there is still development for them even now.
I recommend Moto G5.. pretty active community on xda, replacable battery and should be very cheap
k3lcior said:
I recommend Moto G5.. pretty active community on xda, replacable battery and should be very cheap
Click to expand...
Click to collapse
Moto G5
Warren_Orange said:
I'd go for a moto g 2nd or 3rd Gen. You can get them for peanuts on eBay and there is still development for them even now.
Click to expand...
Click to collapse
Do you mean something like this?
gsmarena_moto_g
Will it be possible to go with LineageOS 18.1 on such an old phone?
kamien8 said:
Moto G5
Do you mean something like this?
gsmarena_moto_g
Will it be possible to go with LineageOS 18.1 on such an old phone?
Click to expand...
Click to collapse
Yes that's the one. After having a quick look at the forums I don't think you'd get 18.1 on it. There is a micro g 17.1 rom that seems active.
Is this for practice or for use as well? If it's for using I'd probably go with the g5 for a few bucks extra as the Moto g is quite old but it's not a bad spare spare phone. I picked one up as a backup and I liked the feel of it (if your into small phones) . It reminded me of the first Moto X.
I want to repurpose my old S7 (Exynos) as a Server. From what i read, PostmarketOS is the only way to run pure Linux on the S7. Sadly, i have not been successful at booting.
I followed the Installation "guide" from this wiki page.
The installation process in itself works fine. I first flash the kernel using
Bash:
pmbootstrap flasher flash_kernel
while in download mode, then i switch into TWRP (ADB Sideload) and run
Bash:
pmbootstrap install --android-recovery-zip && pmbootstrap flasher --method=adb sideload
The image should be installing correctly, atleast there are no errors and everything seems to look "normal".
Although, when booting, it gets stuck at the PostmarketOS Loading screen and is not booting (SSH over USB does not work)
Going back into TWRP reveals that it has problems mounting the /system partition
"Failed to mount '/system' (Device or Resource is busy)"
I've been trying so many things, but the outcome is always the same
I tried:
* WSL2 Ubuntu
* VirtualBox XUbuntu
* Debian Live Install
* Sending the recovery zip on my phone using USB and then installing it from there
I've been stuck at this for 3 days now, and i have no idea what else i could try...
Any help would be appreciated.
Here's my last_kmsg
I have the same device, but I''ve been stuck for 5 days Also same cryptic-nothing-to look-at last_kmesg, it just stops. Did you make any progress? Most people here are more familiar with Android ROMs. I think we're better off taking this to postmarketOS's Gitlab issues.
I can install Lineage OS 18.1 from some post here on XDA just fine. But I don't want Android on the device, I want to build it as a LAMP server to serve Moodle. Internet and electric power are a mess here, distributed is the way to go. But I'm not going anywhere if I can't show some POC.
I think it's something to do with DM-Verity being tripped, or is it no-verity? I'm following this to restore it to stock and start over with the postmarketOS howto.. The install logs look clean, I must have done this more than 50 times now.. from what I understand reading the logs, seems like it's a partition issue. Kernel just stops ... I confirm the kernel is booting successfully by making it continuously vibrate with :: pmbootstrap initfs hook_add maximum-attention
I'm trying this download PIT part now:
How To Use PIT Files On Odin For Flashing Samsung Device - MTKArena
If you need to change the partition of the firmware and want to use the PIT files for your device, you are in the place. We will share how to use PIT files on
mtkarena.com
any prog @nonick @Xirado ?