Can someone (who never touched it, obviously) dump his misc partition and upload it?
From H850 international variant.
I wiped mine while I was in a twrp bootloop and need to flash one back.
Open a terminal, and after su run:
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc-dump.img
Thanks
C'mon guys.
Really now, noone?
I case you were wondering at the lack of replies: people won't ever dump their misc partitions unless they're pretty naive: it includes things like bespoke MAC addresses, WiFi passwords and certificate info,so presumably a lot of other security related stuff... I know some of the stuff in there, but I'm not smart enough to scrub it before posting it around... and some of the sanitising (MAC addresses) would make it unusable for you.
What are you aiming to get to (stock ROM / LineageOS / other)??
You can just factory restore using LG Bridge on a Windows PC and then if you want LineageOS, then you can start again (re-flash the unlock.bin, sideload TWRP, etc)....
BTW - I did the same - LineageOS auto-update, bricked (here) and then recovered (back to LG stock), then tried again: unlocked it again, TWRP again... and re-installed LineageOS, only to face problems with WiFi now as my entire data partition (incl. misc) appeared encrypted - if I try to wipe it and start again, then the WiFi MAC address is all 0's and I can't seen to insert the original MAC (either via cat'ing in a replacement config file into data/misc/wifi like THIS) or via various "busybox ifconfig" commands...
Really frustrating... I can get everything, including WiFi working again if I re-apply a factory reset via LG Bridge, but I can't flash LineageOS as it seems that the data partition is unwritable (encrypted?) until I wipe it in TWRP...
BahnStormer said:
I case you were wondering at the lack of replies: people won't ever dump their misc partitions unless they're pretty naive: it includes things like bespoke MAC addresses, WiFi passwords and certificate info,so presumably a lot of other security related stuff... I know some of the stuff in there, but I'm not smart enough to scrub it before posting it around... and some of the sanitising (MAC addresses) would make it unusable for you.
What are you aiming to get to (stock ROM / LineageOS / other)??
You can just factory restore using LG Bridge on a Windows PC and then if you want LineageOS, then you can start again (re-flash the unlock.bin, sideload TWRP, etc)....
BTW - I did the same - LineageOS auto-update, bricked (here) and then recovered (back to LG stock), then tried again: unlocked it again, TWRP again... and re-installed LineageOS, only to face problems with WiFi now as my entire data partition (incl. misc) appeared encrypted - if I try to wipe it and start again, then the WiFi MAC address is all 0's and I can't seen to insert the original MAC (either via cat'ing in a replacement config file into data/misc/wifi like THIS) or via various "busybox ifconfig" commands...
Really frustrating... I can get everything, including WiFi working again if I re-apply a factory reset via LG Bridge, but I can't flash LineageOS as it seems that the data partition is unwritable (encrypted?) until I wipe it in TWRP...
Click to expand...
Click to collapse
I just need it to stop Wi-Fi MAC address from being changed on reboot and restore any other potential loss from the wiped misc.
I'll use a hex editor to search for the address and edit the one uploaded ofc.
As for security, misc is a readonly partition, no personal stuff/data are stored in it. Only the MAC address can be considered "targeted information" which is not sensitive or smth as MAC is not reachable/trackable after first router hop anyway.
If someone uploads it you'll solve your issue too.
DenyDarko said:
I just need it to stop Wi-Fi MAC address from being changed on reboot and restore any other potential loss from the wiped misc.
...
Click to expand...
Click to collapse
The guide at https://forum.xda-developers.com/lg-g5/how-to/guide-fix-wifi-mac-address-changing-t3533841 didn't help?
Under RR now I still had the issue with changing MAC addy despite the guide (all other roms like AOSiP, DU or OwnRom were fine) - but I noticed that it only ever changed it to ONE specific addy. So I used that one and set it with the guide and it's been stable since then :fingers-crossed:
Nimueh said:
The guide at https://forum.xda-developers.com/lg-g5/how-to/guide-fix-wifi-mac-address-changing-t3533841 didn't help?
Under RR now I still had the issue with changing MAC addy despite the guide (all other roms like AOSiP, DU or OwnRom were fine) - but I noticed that it only ever changed it to ONE specific addy. So I used that one and set it with the guide and it's been stable since then :fingers-crossed:
Click to expand...
Click to collapse
This is how I do it ATM but its not a permanent solution.
Well... I guess no one is willing to upload the evil misc.img xD
DenyDarko said:
This is how I do it ATM but its not a permanent solution.
Well... I guess no one is willing to upload the evil misc.img xD
Click to expand...
Click to collapse
Well that was my point - it IS permanent for me.
Under RR it kept changing the MAC back at every reboot, but always to ONE specific MAC. So I edited the config file with that MAC and it hasn't changed it back yet (roughly 12 reboots and a dirty flash later).
Related
OFFICAL TWRP RELEASED, this thread is no longer active. 3-30-2018
https://twrp.me/motorola/motorolamotox4.html
---
UNOFFICIAL BUILDS -- USE AT YOUR OWN RISK AND KNOW HOW TO GET YOURSELF OUT OF TROUBLE IF IT ARISES. I ASSUME NO RESPONSIBILITY FOR YOUR BROKEN THINGS.
UPDATED 01-11-2018
There are now 7.1 based and 8.0 based builds. Obviously, be careful to select the proper download. While I don't think flashing/booting the wrong one would permanently brick the device, let's not find out
For now I will not be attempting to make data decryption work. It is REQUIRED that you unencrypt your device by formatting userdata, so back up your stuff first.
IMPORTANT NOTES: TWRP for OREO is a bit of a pain as it currently requires manually editing your fstab. I have tried to automate this process, but it breaks stuff. So just be aware before you begin that it is a rather time consuming process.
If you make any change to your boot partition after flashing SuperSU, you will need to reflash it or you will get a bootloop.
8.0 OREO TWRP INSTALLATION:
OREO SEEMS VERY FINICKY AND DOES NOT LIKE CHANGES TO ITS FILESYSTEM -- BE PREPARED TO REFLASH STOCK.
0. FLASH OREO FACTORY IMAGE (may work otherwise, but we should be starting from fresh stock here)
1. Download FASTBOOT BOOTABLE TWRP for 8.0/OREO below
2. Download SuperSU 2.82 SR5 below
3. Move SuperSU to external SD or USB OTG
4. From bootloader, fasboot BOOT TWRP
5. Flash SuperSU (note: do not format /data now... not necessary and will cause errors on boot)
6. Reboot system
7. With any root file editor/text editor (Amaze, Total Commander, etc) open /system/vendor/etc/fstab.qcom as a text file for editing.
8. At the end of the /data partition entry, delete "fileencryption=ice" and replace it with "encryptable=footer".
9. Save fstab.qcom (and make sure it is actually saved properly!)
10. Reboot to bootloader and fasboot BOOT TWRP
11. Go to Wipe, hit the FORMAT DATA button, and type "yes" to format /data. This will erase your data, obviously:silly:
12. Reboot system (should now be unencrypted, verify in Settings>Security or by booting TWRP and checking /data with File Manager.
If you later choose to flash TWRP (not the bootable we used here!), you may need to flash SuperSU again to avoid bootloops.
7.1.1 NOUGAT TWRP INSTALLATION:
1. Download current TWRP for 7.1.1 build below
2. Download SuperSU 2.85 SR5 (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3. Move SuperSU to your external Micro SD card.
4. Fastboot flash the TWRP image.
5. Reboot to TWRP.
6. FORMAT data (not wipe...use the "FORMAT DATA" button and type "yes". OBVIOUSLY THIS WILL ERASE YOUR DATA)
7. Install SuperSU 2.85 SR5
8. Reboot to system (it WILL bootloop a couple times...don't panic!) and confirm that device is unencrypted by checking that SETTINGS>SECURITY>ENCRYPTION now prompts "encrypt" (don't do it).
DOWNLOADS:
TWRP FOR 7.1.1 (Nougat) DOWNLOAD: https://drive.google.com/open?id=1Et-AQgCNx7WDAwzihlI51euUa2ixKHEP
TWRP FOR 8.0 (Oreo) DOWNLOAD: https://drive.google.com/open?id=1WcVS_3rloF7jxPulj_jKxfsp3zy5pB5N
FASTBOOT BOOTABLE TWRP IMAGE (OREO BASED): https://drive.google.com/open?id=12ClviqtEjtflB63UQ1CZQNKEqkprBO0u **For temporary TWRP boot using "fastboot boot". Do not flash or you will be stuck in recovery!**
DEVICE TREE: https://github.com/mightysween/android_device_motorola_payton (NEEDS TO BE UPDATED WITH OREO BRANCH)
changelog:
BETA4
-reverted to 3.2.0 for current build (release candidate rebased to 3.2.1).
-fixed "format data" button
-finalized fstab for OTG/SD/INTERNAL mounting
-target is now UNENCRYPTED devices only (/data decrypt will not be fixed)
BETA3
-Rebased to TWRP 3.2.1
-USB OTG working
-all partitions mounting correctly
-considered working except for decrypt and MTP/ADB
BETA2
-fixed internal storage mount
BETA1
- updated source to TWRP 3.2.0
ALPHA3
- Fixed USB mounting (adb/mtp still nonfunctional) BROKEN IN BETA1
ALPHA2
- SD Card fixed
ALPHA1
- /system is now properly mounted.
- now plays nice with our working root method.
- ramdisk is patched to prevent first boot encryption once /data is decrypted (now requires flashable ZIP)
NOT WORKING:
adb/mtp/sideload
/data decryption (abandoned -- /data access requires unencryption)
CREDITS: @kraatus90 for kernel fix, @Chainfire for SuperSU, @jcadduono for no-verity-opt-encrypt scripts.
---
Thanks so much for all your work!
hi,
you said this is really unstable and could brick the device easily. however, you seem to be testing and experimenting with your device a lot, so i'd like to ask if you have any particual unbrick method that you use when something goes wrong.. like, a via fastboot flashable image or something simmilar...?
thanks for your work!
Thanks for you work. If you have any unbrick methods pls tell.appreciated your work ?
I am not going to provide step by step "unbrick" methods, because until the partitioning is properly set up, TWRP has potential access to things that can not be fixed.
Again, this is still highly experimental.
All that said, my entire process to protect any device remains the same: Have a backup for every partition you will be testing, make as few changes as possible at a time, test boot images before flashing (fastboot boot), and test restore methods frequently (flashing back to stock or backups), and don't do anything unless you are highly certain of the outcome.
By those standards, there is nothing to gain by installing TWRP right now, as its basic function (install/backup/restore) is not set up yet.
Found the BoardConfig flag to enable FBE (TW_INCLUDE_CRYPTO_FBE := true) but do not have the lib it is dependent on (libe4crypt) and I don't see it anywhere yet...
For reference (not sure this is most current, but it demonstrates the process)
https://github.com/nijel8/TWRP/commit/bd7492de28963b7e74e8e5d3f17ec9a5a287d9c3
I have confirmed that FBE support is present in the source, dependent on this missing module... so need to figure out where/how to enable it.
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Obvious workaround is to not be encrypted to begin with -- but that isn't a "solution".
mightysween said:
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Click to expand...
Click to collapse
This appears to be the case, unfortunately. Seems that the TWRP FBE support was built specifically for the Google implementation of FBE which was merged into kernel sources for Nexus and Pixel. Not even using the qseecomd I assumed it was... will remove on next build.
Info on FBE:
https://source.android.com/security/encryption/file-based
Will be testing options to disable forced encryption, and if necessary dm-verity...
Anyone who wants to dig through kernel for related flags and props, it would be greatly appreciated!
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Making good progress this morning.
Seem to have a build with properly decrypted /system, and working SD Card. I also have patched the boot.img to disable forced encryption on the first boot. But now, I can not find a safe way to fully format (not "wipe") the /data partition. As mentioned in the previous post, the "FORMAT DATA" button is missing. The fastboot command "fastboot format userdata" returns an error that it does not support RAW format.
Need to figure out why this is happening... and once I do, I believe I can reformat /data without encryption and then will have an almost fully working TWRP build. Obviously, the ideal solution would be to have TWRP work out of the gate with an encrypted /data, but until then this is going to be our best option.
Will post an updated test build in the OP soon.... needs further testing before I would recommend non-expert users to try it.
Getting very close now!
UPDATE: ADDED NEW BUILD TO OP
---
Also, just occurred to me that the ramdisk will need to be patched every time, so now that I have SD card support will be testing some of the existing flashable ZIPs out there that are designed specificially to prevent first-boot encryption and/or disable dm-verity.
---
mightysween said:
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Click to expand...
Click to collapse
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
mightysween said:
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
Click to expand...
Click to collapse
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
johnjingle said:
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
Click to expand...
Click to collapse
I have 3.1.1-0 (same version I am building here) on several other devices, and the button is there. It has to be triggered by something during compile, but I can't figure it out. Driving me nuts
Looking through TWRP source, and can find actions for every other button (wipe, backup, restore, install, etc) but not for format. Hmm.
I posted over on an old but semi-active TWRP flags thread, maybe someone will have some insight.
Wondering if I make a stock boot image without the encryption tag in fstab, and then wipe data and reboot... then flash my image. That may make it so the data partition is never encrypted in the first place and allow TWRP to work.
But that is an ugly, non-user friendly fix. Why can't we just format /data?
---
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
No crypto support was compiled into this build.
Click to expand...
Click to collapse
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
mightysween said:
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
Click to expand...
Click to collapse
Thanks for doing all of this! I wish I had the time and knowledge to help.
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
mightysween said:
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
Click to expand...
Click to collapse
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
vivek638 said:
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
Click to expand...
Click to collapse
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
mightysween said:
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
Click to expand...
Click to collapse
Keep searching. wish i could have helped but dont know anything about compiling n all..
I'm not much of a programmer, but I can look through the files. Is there anything in particular we're searching for?
UPDATE: I was able to debrick the phone. Read my later post for details.
----------------------
Hi All,
Thank you all for having amazing community of hackers and developers here. You guys rock.
I started my search for a new rugged rootable phone recently and I settled on Poptel P60. It is a great phone though slightly bigger than what I normally get. Nontheless, the specs are excellent and the price is fair!
I've had a limited success rooting and customizing this phone. The OEM interface is almost bearable but overall the "Customized UI" felt like a downgrade from stock Oreo. It has a very annoying feature of reverting to stock launcher on startup, even when I selected Nova as my default one. The stock launcher is not that great. This, and the lack of ability to use x.flux, Titanium Backup and other root-only apps drove me to try hacking things again.
After emailing the manufacturer they provided the firmware but it is in CPB format. I tried at least 3 different converters for CPB to MTK Scatter and they all either freeze or hang. No luck.
Instead I did a rom readback with SPFlashTool and then cut up the partitions with Wwr. Now I've finally had the recovery partition! I used CarlivImageKitchen to port TWRP from a similar device, Ulefone Armor 5. The chipset and resolution are same. After some trial and error it worked! I had to use USB-OTG for input and external sd card had a weird label, but I was able to install Magisk from the SD card to root, followed by XPosed, full package. It worked! If anyone needs my ported TWRP Recovery for Poptel P60 just ask!
However, the manufacturer UI did complain a lot about the phone being rooted. Eventually, somehow, Magisk stop receiving root requests. They never showed up and timed out! Very strange, because apps that already received root continued working. I tried a lot but could not fix the issue. I was fed up. I wanted to do a manufacturer reset (in hopes of starting from scratch and then attempting to port Lineage or something) but, as I've mentioned, I have not received a firmware compatible with SPFlashTool. I tried to make one from Armor 5. The partitions were almost the same (both are MT6763 devices). One was out of order, and offsets were different and I patched all those. To be clear, I used all the partitions and layout extracted from my rom readback that was cut up by Wwr. I only used the Armor 5 scatter as a reference for file format. I edited the layout to match everythign I saw in Wwr.
This is where the horror begins. I tried flashing (Download Only) with SPFlashTool but got some error saying something changed. "Do you want to do Format & Download instead?". Being an inexperienced idiot that I am, I said yes!
Now, the phone appears bricked. No lights. No screen output. Cannot enter fastboot. Cannot enter recovery. Cannot boot.
I have a feeling the preloader got corrupted. I'm not sure this is the case because I've omitted the preloder from download. At least the first time the phone started acting bricked. The device still shows as Mediatek USB VCOM device and flashing gets initiated but all attempts to flash result in errors. MA checksum mistmatch or something along that order. I've tried a lot of things and I'm stuck! For good or for worse I've tried flashing Ulefone Armor 5 preloader but I'm getting the same error when trying to flash it.
Here is what I have...
- Stock firmware in SPB format. I can't use it and nothing I tried worked for converting it.
- ROM dump made with SPFlashTool
- Wwr was able to extract every partition except preloader. This includes nvram, etc. I'm not sure why it was not able to extract the bootloader.
- TWRP port that worked. Seems not useful if the phone does not start.
- Preloader for Ulefone Armor 5, (same chipset and resolution)
Clearly I am an idiot for using "Format & Download" option. I've found posts later suggesting against it. I am also over my head for trying to tackle a new device by myself, though I have had a marginal success with porting TWRP and installing Magisk.
Now, I feel like idiot and I am stuck! I beg you, XDA developers, if you have any advice (besides not being an idiot in the future), please share!
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
SkylinesHD said:
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
Click to expand...
Click to collapse
That wouldn't work, heh. I bought this phone on eBay and rights now it's currently sold by a handful of sites. It is on warranty but returning it back to China would be complicated. At any rate, I live on the edge outside of warranty!
I was just about ready to give up and feel like the biggest reckless loser on Earth... Days of tinkering around with nothing but a phone brick to show for it. Poptel tech support wouldn't provide me with MTK scatter. All they gave me was this SPB firmware that nobody uses and it crashes every converter I threw at it. Useless.... No fastboot. No recovery. No functional bootloader.
The amazing GOOD NEWS is I have debricked the phone... I used a bootloader from another phone's firmware: Cubot_Power_MT6763_180607_8.1.0. Unlike Ulefone Armor 5's preloader this one worked! It seems like it's the only thing I was missing because the phone starts up and everything seems to work. I must have done a good job with all other partitions but I'll try to watch for signs of anything else broken. Right now it seems fine.
I'm not sure if the bootloader was completely gone, corrupted, or an incorrect one was used. All I know is I was able to download Cubot Power's working bootloader (also MT6763) with SPFlashTool. Nothing like a feeling of unbricking your phone!
I will post more updates if that's ok... I'm hoping to port Lineage on it (I've never tried that before) or at least find a way around the manufacturer's clunky UI. The hardware is great otherwise. If anybody wants a working ported TWRP image or the scatter I used for debricking just ask! I will make a post later if I have more success with customizing the phone. The phone is debricked and I have a scatter and images to fall back on if anything goes wrong. Woot! Thank you everyone who developed these great tools.
I have the same phone been looking for info. there's a thread on 4pda with poptel p60 that has the scatter file and firmware. Any chance you could post the twrp for this phone? having trouble trying to port myself cant figure out port 6763 from the guides available.
4pda.ru/forum/index.php?showtopic=933002
Firemware:
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
idaman0 said:
Hey man,
Was wondering if you saw my post on your thread. Looking for TWRP for the Poptel P60.
Thanks,
telegram @drmethyl
Click to expand...
Click to collapse
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
https://mega.nz/#!MNVGhaYS!63ovQeowwoP1oE3v6-_ZS8gKx_-mxOh4G4qWcKRbuiQ
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
zeromemory_wtf said:
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
Click to expand...
Click to collapse
sorry man, didn't end up using yours theres a twrp on 4pda now with a mod to flash to keep root. I'll upload for you here if you don;t have an account there.
The patch for the Light-kastomizator v.12 factory firmware.
I decided not to bother with the draining and distribution of modified firmware as a whole, easier to apply the patch, and ... you're done!
If that - the factory firmware v.12 lies with us -HERE, no problem you can return everything back, or (if there is something Kolupaev), first ask her, and then patch.
#
What is done
Будут удалены:
/system/tts
/system/app/QK_LogSystemAbroad_wm_bl
/system/app/QK_Sos
/system/app/QK_PrivacySpace
/system/app/QK_PersonalAssistScreenAbroad_V2
/system/app/BY_3RD_OperaMiniBrowser_OEMBranding
/system/app/BY_3RD_OperaNews_OEMBranding
/system/app/Drive
/system/app/Duo
/system/app/Gmail2
/system/app/GooglePrintRecommendationService
/system/app/LatinImeGoogle
/system/app/Maps
/system/app/Music2
/system/app/PartnerBookmarksProvider
/system/app/Photos
/system/app/YouTube
/system/app/Videos
/system/presetapp/BY_3RD_OperaMiniBrowser
/system/presetapp/BY_3RD_OperaNews
/ system / priv-app / MtkCellBroadcastReceiver
/ system / priv-app / ConfigUpdater
/ system / priv-app / GoogleFeedback
/ system / priv-app / FilesGo
/ system / priv-app / GooglePartnerSetup
/ system / priv-app / QK_MagazineAbroad
/ system / priv-app / Velvet
The system additionally installed:
ES_Provodnik_3.2.5.5 (graphic mode "Panatta-sport")
the SD Maid Pro - system Cleanup (Lite Mod "Breathe of fate" )
Changes:
By default the system is set to Russian language , region and time zone Russia / Moscow. Setupwizard (first assistant settings) is not cut off.
GBoard keyboard replaced by fashion Antonbeard GoogleKeyboard(with a limited access to the Internet is built dictionaries -.. English and Russian)
Google-search is replaced by the latest beta (it is possible to change the style and transparency of the widget)
have been added and changed some default sounds and ringtones, and the default there as a very sadly.
Blocked by advertising the hosts file.
Improved energy efficiency due to shutdown of background update service does not fall asleep GAPPS and downloaders (allowed these services Doze mode).
#
Setting:
1. Throws on micro SD-card this patch.
2. Downloading the last zip-installer " Magisk-v ..... the zip " and also copy it to the SD-card, turn off the phone.
3. Through the SP Flash Tool sewn recovery "TWRP" (the system can not be loaded !!!).
4. Vaypaem userdata (reset to factory settings) through better "factory mode" (volume down inc +) / select "Clear eMMC".
After reset immediately loads in the TWRP (inc + volume up), and from the sd-card in turn apply patches "LiteMod_Poptel_P60_v.12.zip" and "Magisk-v ..... zip". Reboot from the installation refuse twrp-applications.
Done, you have custom firmware!
(If twrp and Ruth is already installed,
After the completion of all the manipulations, it is desirable to flash the stock (factory) rekaveri, then no problem can be used to reset the system from the Android menu and install the firmware update OTA (over the air).
Download: LiteMod_Poptel_P60_v.12.zip
PS. Sberbank + contactless payment working properly, despite the fact that the system has been modified and installed Ruth! :derisive:
Click to expand...
Click to collapse
3.2.3 TWRP by Jemmini for "Poptel P60" ( with the phone port Blackview BV9500): Attached file recovery.img (17,27 MB)
The port used by the kernel to flash Android 8.1.0 version of "POPTEL_V12_20181030"
WARNING !! After installing recovery, subject to permit changes in the system partition, install ROOT is required, otherwise the system will not boot. if not to accept the possibility of changing the system partition and establish the patch-root subsequent restart in overwrite TWRP recovery returned drain-
Attached fileMT6763_Android_scatter.rar(1.28 kb)
#
Getting ROOT
For ROOT set out under TWRP (pre throwing off the memory card), this patch: Attached fileMagisk-v18.0.zip (3,99 MB)
#
Stokovye boot / recovery
from said EEPROM: Attached filestock.rar (22,75 MB)
#
What does not work:
1) Do not see "the internal memory" (can not decipher the "data" section and ask when starting TWRP password).
Solution:
download the patch: Attached filedisable_encryption_P60.zip (133.89 KB)
throw it on the memory card, boot into TWRP, go to the "mount" to put a checkbox on the vendor , then go to the "install" and install the patch.
After installation make data in the "cleaning" cleaning (possibly cleaning does not help but the formatting of data should definitely help)
after data manipulation TWRP be able to work with the data section
2) is not working USB / MTP mode into TWRP
#
Information for those who are "in the tank" :
When TWRP presence in the smartphone in any case and under no circumstances should you do reset through the system.
Resetting takes place only directly through TWRP (standard cleaning sections)
If you run the command via the android in the first place, it can not be executed because it does not understand the TWRP.
and secondly, you get a constant load in TWRP because it has not yet executed the command android you will always be send to recovery /
Solution for "tank": need to install flow-recovery to be completed through a reset command or cancel it.
Another solution I personally do not know
Just do not forget about gratitude : Jemmini,- for the compilation of the TWRP which served as donorUrree,- order TWRP and testing (nothing would have happened without it)Message edited Lomaster_Serg - 6.1.19, 03:02
Click to expand...
Click to collapse
rapidgator.net/file/84ccd2d612ade0256eb927895d4ed37e/LiteMod_Poptel_P60_v.12.zip.html
rapidgator.net/file/c77fec40e349f8083eda14bf7058425c/recovery.img.html
rapidgator.net/file/6621d517cef9aa10abc78b40bcdc8b26/stock.rar.html
rapidgator.net/file/7a7db29c0d35eee169b76698aac6b50b/MT6763_Android_scatter.txt.html
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
Hello guys, first of all: thank you very much for your Forum; I'm learning a lot even if I remain a complete noob!
I'm trying to use LineageOS 17.1 (lineage-17.1-20210118-UNOFFICIAL-a3y17lte, recovery OrangeFox 11.01) on Galaxy A3 2017 (SM-A320FL), and I did something really stupid trying to make Link2App work.
I had problems to format properly the miniSD using Android's apps, and I could not remove the card from the phone (the slot's opening is damaged). So then I tried to format the card using ADB + BusyBox + fdisk, BUT I did it while I was distracted by other job's issues, and I didn't realize I was working on the internal SD instead of on the removable card (yes, complete idiot...).
Result: a brand new empty partition table in my phone, permanently stuck in Download mode (impossible even to power off it).
I tried to restore the phone using this procedure, but it failed midway. By the way, I could Odin-flash TWRP and then restore the partitions using the repartion script. Eventually, I fleshed my OrangeFox and LineageOS: the system is now perfectly working, but the phone doesn't recognize any more my SIM and IMEI (dialing: *#06#) is blank.
I had a Fox's "light" backup, but it didn't solve anything.
I'm still having the original box with the IMEI number on the label, but I didn't find a suitable procedure to use it.
Kies3: the SM-A320 phone seems too old to allow the Initialization procedure described here (yes, the phone was unplugged)
There are many apps promising miracles (for instance: ToolHero, MTK Engineering Mode, IMEI Generator Pro, EFT Dongle...); however, I tried some, and they seem to me just ****ty pieces of software, requiring the original system or dubious paid services.
Dialing codes* procedure (like Method 1 here). I cannot remove SIM or battery to complete the procedure. Besides, my phone doesn't react to the code; probably they are country or SIM specific...
Line command (terminal emulator or ADB): this seems to be the most promising method; however, the line
Code:
echo 'AT +EGMR=1,7,"MY_IMEI_NUMBER"'>/dev/pttycmd1
doesn't do anything on my device
IMEI generator: I tried to generate a new MP0B_001 file using this guide. The download link is broken, then I downloaded the files from another source, and I prefer to add to my system just the MPB_001, without flashing the "repair" tool. Besides, I don't have any /nvram folder in my $root/data/ directory... (the only IMEI related folder is in $root/eps/).
Any suggestion to solve this mess? Thank you very much!
Daniele
* EDIT: after typing *#*#197328640#*#* the phone window closes.
Look inside here:
3 METHODS to restore your IMEI number on Android
Most people face a common issue with IMEI number that is losing them. Particularly, it happens when you get a locked second-hand mobile or in Mediatek devices.
www.gizmogo.com
jwoegerbauer said:
Look inside here:
3 METHODS to restore your IMEI number on Android
Most people face a common issue with IMEI number that is losing them. Particularly, it happens when you get a locked second-hand mobile or in Mediatek devices.
www.gizmogo.com
Click to expand...
Click to collapse
Thank you very much for your answer! The 2-3 methods seem promising; however, I isolated the problem and solved it before receiving your message.
The problem: after messing with the partitions, I tried to restore my system, downloading the files via Freja. However, I select the wrong CSC, using my SIM provider code (TIM) instead of the generic code for Italy (ITV).
I noticed it exploring the light backup I had done in TWRP (only System partition): a CSC_version.txt was there, pointing to A320FLOXA9CTK1 (ITV version, while I restored using A320FLTIM8CTH1, TIM carrier version). ITV was also mentioned in the file $ROOT/eps/imei/mps_code.dat (dunno if this is relevant)
Solution: Odin + the right firmware did the trick. I had my IMEI back and the phone working, then I came back flashing TWRP, Orangefox and, eventually, LineageOS.
Everything is working now, and, of course, I backed up EPS partition (now).
Many thanks!
daniele
(I posted this on the Android Mods Thread on accedent)I have a LG Nexus 5 HammerHead and tried to flash the newest Kali NetHunter using TWRP 3.5.2. After I flashed the ROM successfully, I have notice that the phone itself says no wifi networks found when swipe down to look at the wifi connections. I go to the wifi settings it says "Searching for wifi networks" with a spinning wheel of death(the loading icon). I've tried configuring it to use 2.4 Mhrz and didn't work, set it up to where it would only find good connections and still didn't work, I even did a factory reset and actually made it worse. I even reflashed it and see if that fixed it, nope. I connected it to the internet using a Ethernet adapter that is made for phones using a micro USB connection, updated the apps, updated and upgraded Kali NetHunter itself in the terminal and wifi connections is still not finding any connections at all. Could It be that Kali NetHunter doesn't support the internal wifi card that is built into my phone, could it be that twrp is having some errors on their end, or is it a bug that Offensive Security is not aware about? Please Help?
This may happen cos of wi-fi firmware. These files are called fw_bcmdhd.bin and fw_bcmdhd_apsta.bin. There are two versions of firmware:
1. https://github.com/LineageOS/androi...c531cd30abd21d93c5a04/bcmdhd/firmware/bcm4339
2. https://github.com/LineageOS/androi...5f8949fe77780d922c973/bcmdhd/firmware/bcm4339
You need to find where these files are stored in your rom, replace them with files from version 1 or version 2, restore permissions for these files if necessary and reboot your phone.
z3DD3r said:
This may happen cos of wi-fi firmware. These files are called fw_bcmdhd.bin and fw_bcmdhd_apsta.bin. There are two versions of firmware:
1. https://github.com/LineageOS/androi...c531cd30abd21d93c5a04/bcmdhd/firmware/bcm4339
2. https://github.com/LineageOS/androi...5f8949fe77780d922c973/bcmdhd/firmware/bcm4339
You need to find where these files are stored in your rom, replace them with files from version 1 or version 2, restore permissions for these files if necessary and reboot your phone.
Click to expand...
Click to collapse
Honestly, I have been trying to find these files and can't seem to find them. I even put the file name on the search bar of my windows 10 and it can't find them either. I think its just missing firmware on Offensive Security's end in this situation. I've had a troublesome experience with their kali linux products such as kali linux itself on having missing firmware after installation. Thank you for helping me out and hopefully these files should do the trick after I re-flash NetHunter with the firmware you have provided. As a matter of fact would the files belong in the firmware folder?
Martisabolt said:
Honestly, I have been trying to find these files and can't seem to find them. I even put the file name on the search bar of my windows 10 and it can't find them either. I think its just missing firmware on Offensive Security's end in this situation. I've had a troublesome experience with their kali linux products such as kali linux itself on having missing firmware after installation. Thank you for helping me out and hopefully these files should do the trick after I re-flash NetHunter with the firmware you have provided. As a matter of fact would the files belong in the firmware folder?
Click to expand...
Click to collapse
You will not find them in the search bar of your windows)
And no, firmware is not missed. Without wi-fi firmware you will be unable to enable Wi-Fi at all. In your case Wi-Fi can be enabled but you didn't see any networks.
Also /firmware - is incorrect place. It is a mount point of the /modem partition.
Wi-Fi firmware can be located at /system/firmware or /system/vendor/firmware/. Try to find them in TWRP. Boot into TWRP, mount System partition, open File Manager and review all the paths i've listed here. But i can't be sure cos i've never used Kali NetHunter.
z3DD3r said:
You will not find them in the search bar of your windows)
And no, firmware is not missed. Without wi-fi firmware you will be unable to enable Wi-Fi at all. In your case Wi-Fi can be enabled but you didn't see any networks.
Also /firmware - is incorrect place. It is a mount point of the /modem partition.
Wi-Fi firmware can be located at /system/firmware or /system/vendor/firmware/. Try to find them in TWRP. Boot into TWRP, mount System partition, open File Manager and review all the paths i've listed here. But i can't be sure cos i've never used Kali NetHunter.
Click to expand...
Click to collapse
Ok, I've been to those locations and in the system's folder, no firmware folder. However, in the sys folder, there is and does not show any firmware files in TWRP.
Give me the links to ROM files u flashed
This came directly from kali.org.
What was your base ROM before installing Kali? Stock Android 6.0.1?
yes
Well, Wi-Fi firmware in stock android 6.0.1 is located at /system/vendor/firmware/ folder. I've looked in the kali installer script and didn't find any scripts which can modify or delete this firmware. So we can try to install different firmwares into stock folders. I've attached 2 flashable zips for you. Try the -DHD version first. Flash it in TWRP and reboot your phone. If it doesn't help, then try -STOCK version.
It this will not help then i'm out of options
z3DD3r said:
Well, Wi-Fi firmware in stock android 6.0.1 is located at /system/vendor/firmware/ folder. I've looked in the kali installer script and didn't find any scripts which can modify or delete this firmware. So we can try to install different firmwares into stock folders. I've attached 2 flashable zips for you. Try the -DHD version first. Flash it in TWRP and reboot your phone. If it doesn't help, then try -STOCK version.
It this will not help then i'm out of options
Click to expand...
Click to collapse
Ok, I have tried both. Sadly I guess I'm out of luck and this is now nothing but a bricked phone in my hand. None of these files worked and actually made my phone crash when I tried to load the first file. I tried the second file as well and now I can't turn wifi on. I might as well have to build my own rom or junk this phone
Martisabolt said:
Ok, I have tried both. Sadly I guess I'm out of luck and this is now nothing but a bricked phone in my hand. None of these files worked and actually made my phone crash when I tried to load the first file. I tried the second file as well and now I can't turn wifi on. I might as well have to build my own rom or junk this phone
Click to expand...
Click to collapse
Don't hurry to kill your phone) Try to revert to complete stock 6.0.1 and re-lock bootloader by this instruction:
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
How to flash a factory image | Return to stock | Unroot your Nexus 5 Hello Nexus 5 Users! I see many users that don't know how to restore their Nexus 5 to stock. It may come in handy, either when you want to RMA your phone, or you want to...
forum.xda-developers.com
And if your wi-fi will not work then yes, something bad happened with hardware
z3DD3r said:
Don't hurry to kill your phone
Click to expand...
Click to collapse
I tried both packages and thery didn't break my ROM. Unhappily they did not help.
I use the Re4son Kernel and can set wlan0 to monitor mode. But airodump is blind then.
@r.mutt @Martisabolt
Hammerhead kernel source (Marshmallow)
These are the complete Nexmon files seperately arranged.
Either you use a proper file manager with root permission, or just use the TWRP fiile manager and insert/copy them into the according sections.Maybe set the correct permission, while you're there and of course know your stuff. :>
Martisabolt said:
Ok, I have tried both. Sadly I guess I'm out of luck and this is now nothing but a bricked phone in my hand. None of these files worked and actually made my phone crash when I tried to load the first file. I tried the second file as well and now I can't turn wifi on. I might as well have to build my own rom or junk this phone
Click to expand...
Click to collapse
Hi Mate, Sorry for the delayed reply. Now i can afford nexus 5. Faced same issue as you. Thanks @z3DD3r for the hint.
Follow below instruction If you want wifi.
*Boot to Twrp
*locate /advanced/filemanager/vendor/firmware
You are there
(Note: 100% you can't see the files as discussed in above thread. But those are hidden(while installing nexmon from nethunter store i have seen those already exists in same folder))
*At bottom you see permisson blue box
*Click the same-select chmod 755-swipe to confirm
Now reboot to system. Here you go.
Hi, few day ago I made a videos with a modded version of Google Camera 8.1,
the first one was not saved properly and was in .pending????????.mp4 state, and I erased it by mistake,
because it was first time, I was using this tool, and I didn't knew that it is a temporary file.
I tried to recover, using many tools, but I was unable to recover it, so I decided to Root my phone using Magisk,
I made some mistake and testing some FastBoot command I relocked my Unlocked phone.
I had to Unlock again by using "miflash_unlock.exe", with advertising that all my data’s will be deleted.
After I managed to patch my phone, he restarted (I don’t installed any previous apps prom store, to avoid my video to wiped by new data,
and I tried with Ult Data, Dr Phone to recover the file, but Root access was not accepted.
Then I tested lot of android tool, nothing worked, after searching a lot I found this page :
https://drfone.wondershare.com/android-recovery/phone-memory-data-recovery.html
And I tried but some command didn’t work, since I didn't have FDISK, FTPPUT on my phone file system,
after some other search I found this ancient page (2014) who seemed to be the source,
https://sudonull.com/post/108208-Recovering-data-from-internal-memory-on-Android-for-dummies
and after installing BusyBox Pro,
I managed to get missing Linux tools.
I tried the command, all worked fine,
but now I’m unable to access this one :
Code:
ftpput -v -u sally -p able -P 40 192.168.1.4 sde55.raw /cache/myfifo
because my FileZilla does not get any information.
And I receive this message :
Code:
can't connect to remote host (192.168.1.4): Connection timed out
The article is old and that guy was using U.S.B. MoDem on CyanogenMod 11.
I use Magisk pro rooting and I do not know what tool I should use to get U.S.B. link with FileZilla Server to get proper connection.
I tried many things, changing protocols, P.T.P., M.T.P., and I do not know what to do,
so I thought may be here, someone with experience could point me to a tool to use in Android 12 / 11 with my Magisk and link to FileZilla Server,
to get image of internal memory back‑up‑ed ?
Thank you in advance.
No one knows how to ?
Someone knows an other methodic to extract partition totally & perfectly ?
forum.xda-developers.com/t/guide_making_dump-files_out_of_android_device_partitions/