Hi,
I need to make an exact copy of a clean Nexus 5x motherboard's (mobo) memory. My phone was infected and I have not been able to get it clean. I know that there are many other file areas besides those copied in TWRP. I have used adb pull and push to copy /dev/block (All mmcblk0XX into mmcblk0XX.imgh files) from the clean phone mobo, and pushed them to the old infected one (mmcblk0 is supposed to be the wholeflash). It copied but it doesn't appear anything has changed. There was a bootup password on the old phone (mobo) but copying those files did not remove it. I then flashed all partitions in the google firmware download and it booted up like a clean new phone, but later went back to the password at bootup. I have had something like this happen a few times. I flash new firmware and somehow the old infected files are still there.
How can I REALLY wipe this phone (manually EVERY file from root / ) and copy over all the clean data from the new phone motherboard? I suspect that the infecter changed my bootloader and is making it persistent somehow. I have used TWRP and copied over the partitions many times. Not good enough.
Thank you.
The bootloader version is still an old one even though I have updated the firmware many times. it is BHZ10i and current one is BHZ11e!
I'M here just because of random, but maybe this unbrick method could help to fully reflash the phone?
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740/post63889395#post63889395
Use this tutorial to fix your phone.
Related
I have a problem when trying to change the lock screen sound in MIUI XJ 1.2.25.
I can copy the new lock sound to /system/media/audio/ui allright, everything seems fine.. But when i reboot, the sound (and all the files) go back to before i copied the new sound(s)..
I'm thinking it might be a "signing" problem, but i'm completely lost in how to do this... So a step by step guide would be nice, as i'm rather new to this whole rooting business
Been using root explorer and/or adb to push the files.
(Btw, when i try to change permissions for the new sound file, nothing happens after i click "ok" in roote explorer.. Any ideas?)
Oh, my device is a HTC Desire
Thanks!
Of you are S-ON, that's your problem. You must push the files via ADB, while in recovery to make them stay there after reboot.
Sent from my customized HTC Desire using TTP
Ok, I know i'm S-On.. I tried pushing the files via adb, which worked fine, but after reboot things were back to normal.. I tried to install a soundpack from a zip (via recovery), that worked well, the sounds didn't revert back to the original. But when i tried to do it manually, things get screwed up
Perhaps the zip file change some settings somewhere that i don't know of?
Guess i'll go S-off then, then i can also change the splash screen
-------
After some more research, i now understand that the soundpack zip-file i installed must have been signed, to pass the HTC security feature...thing.. Thus being able to install new system sounds without the phone reverting back to the original.. Isn't that right?
As I said, files remain there if you flash via ADB while in the custom RECOVERY! Not while the phone is booted & running. At least for me it's working.
Yeah i tried that, but with same result..
Actually, the reason i used adb in pushed the files while in recovery mode, was because i had some issues when using root explorer on the phone.
Sometimes (but not everytime!!?) i couldn't copy/paste the files from my SD card and into the system, it gave me a message about not having enough free space. Which was complpetely wrong, as i generally had about 90-100mb free space. And nothing would happen when i tried changing permissions on the files either.. I read some where that updating busybox could fix the problem with the free space issue, so i did.. Then i could copy the files, but then they wouldn't show up in the destination folder.. Really weird.. So i thought adb was the way to go..
As said, everything went fine until reboot. the files i pushed would still be there, but the originals would have come back too. Meaning i'd have 2 files with the same name, but different sizes, dates and permissions..
It makes much sense with the security feature, as you say..
I'm seriously considering to try an S-off procedure, to get full root and full control
Well then IDK, if I remove a file then push the version I want -it always stay there (via ADB in Recovery).
That's why I never tried S-Off, since I don't need resizing the NAND partitions, and copying to system via ADB always works.
Got tired of experimenting with this, so i made my phone S-off using Virtualbox method. Now everything works perfect!
I can change files and permissions in the system partition and everythings stays as i leave it when rebooting
Somehow the phone boots way faster now ?? But certainly welcome!
Thankyou for your replies
I have a LG E-971 and last night I tried removing the root but I farted up and completely formatted the internal storage, now I am completely screwed because I don't have an OS installed, and literally every attempt to unbrick it wont work, I have tried through KDZ, I have tried just installing a stock rom but unless I can get USB storage I cannot transfer a rom to the device. So is their anything else I can do to this?
JoeUber said:
I have a LG E-971 and last night I tried removing the root but I farted up and completely formatted the internal storage, now I am completely screwed because I don't have an OS installed, and literally every attempt to unbrick it wont work, I have tried through KDZ, I have tried just installing a stock rom but unless I can get USB storage I cannot transfer a rom to the device. So is their anything else I can do to this?
Click to expand...
Click to collapse
one that's not brick, you formatted the system partition thus removed the installed OS.
if you still have custom recovery cwm/twrp learn how to use adb push to send the rom.zip
basic syntax is
adb push rom-name.zip /sdcard/
also using kdz to flash the rom is another easy way out, you just need to get the kdz file that is 1GB or less
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW559386573210987654321/E97120D_00.kdz
Mods May close this now Got the device back up and running
Hi,
While my E975 has Epsilon Project v03 on it, I have decided to replace it with ARTMOD v5.2.1. After ROM installation with CWM my old files have been disappeared. I could see them all when booting recovery mode (it seems like they have been placed in a different partition), however after normal boot I could not see old files and also empty space of sdcard was ~8gb. It means they were there. (i did noting about wiping/formating/clearing cache after or before ROM installation)
What could I have done wrong?
By the way, while trying to recover my files with ADB push, I accidentally run an old batch file and installed and a cwm image designed for p970, then phone was hard bricked. . sent it for repair. LG service in my country repaired it for free by replacing F2 mainboard, since it is still under guarantee.
I am going to reinstall ARTMOD v5.2.2, any suggestion? Thx.
mibis70 said:
After ROM installation with CWM my old files have been disappeared.
Click to expand...
Click to collapse
Check /data/media and /data/media/0. I wonder how many times (hundreds? thousands?) this question has been (and will be) asked over and over again...
I deleted it. You may ask "what?". Everything.
Starting from the Rom using twrp and then every cache, backup (by mistake), etc. Everything. I downloaded the simplest version of android rom on the phone just to make the computer read the phone as an android device so I could upload stock marshmallow to it. I believe I, by mistake, replaced that super simple android with twrp so I cannot reach twrp now too.
I cannot do adb sideload because the computer wont recognize the phone. I cannot do zip flash files from sd because phone says it cannot reach the sd card (permission denied). I literally tried everything. The phone is in the most empty state right now. I will upload photos here to show. Can anyone skype me and help me out. The phone was 1 week old btw.
Hey there,
I have the Galaxy a50 SM-A505Fn and I just broke my internal storage by flashing TWRP and Multidisabler.
First, I should note that I am completely blind, so I use TWRP with ADB in CMD.
First I tried to root my phone with a patched boot image, using Magisc, but that didn't work, so I switched to TWRP.
After flashing it with Odin and booting into the recovery, my pc saw it as Galaxy A50 and the folders inside it were literal giberish and I couldn't paste anything in it, so I switched to a micro SD to flash Disabler and that worked surprisingly well.
Note, I did the wiping before that.
After the disabler worked, I rebooted into TWRP and used the command to reboot into recovery, as I was instructed, then the phone booted up just fine.
I set it up, and gained root with Magisc manager, but after connecting it to the PC to get the sound files I wanted to change it was still giberish and didn't let me make folders or paste anything into it.
The card also looked like it had the internal storage files like you would see on any phone, it had like 256 KB used on it from 2 gb it is formated at since I used it for a pi before and didn't have time to fix the capacity on it back to 64, but again you can't put anything onto it while in the phone.
Any help on how to make it work like normal?
Also apps don't see the storage properly either, so I can't use it for the reasons I rooted it for.
Thanks a lot.
After reading about it, it seems that the storage is encripted.
I managed to flash Infinity os on it, but the thing doesn't talk since it is missing text to speech, so I wanted to flash a zip to make it talking.
After rebooting into twrp, again, still encripted.
Got the zip onto my card, but doesn't flash, which is fine since that can be fixed, but I can't really do anything to fix it.
Does anyone know the command to format data?
twrp format data doesn't work like in the TWRP guide.
Any ideas?
you need to install multidisabler
yamen_tn said:
you need to install multidisabler
Click to expand...
Click to collapse
Did that already, that is how I flashed a rom on it, but was still encripted.
The rom said that there is a problem with my device, but it set up just fine.
I am back on ful stock right now and it decripted, I might try it again in some time.
The only things I want from root is to be able to change system sounds, to add haptic feedback which I already did and tweak it so it works faster.
If I could change the sounds without root and without event sound that would be awesome and would let me stay on stock.
Dragos597 said:
Did that already, that is how I flashed a rom on it, but was still encripted.
The rom said that there is a problem with my device, but it set up just fine.
I am back on ful stock right now and it decripted, I might try it again in some time.
The only things I want from root is to be able to change system sounds, to add haptic feedback which I already did and tweak it so it works faster.
If I could change the sounds without root and without event sound that would be awesome and would let me stay on stock.
Click to expand...
Click to collapse
Good thing you got it decrypted back again, i have had kind of the same issue with internal storage decreasing drastically multiple times, as far as i understood it happens when i install patched AP with magisk then install multidisabler and reboot it without formatting the whole device, maybe try that when your root next time to get past the internal storage issue. Note that mine was in android 9 and device storage was not encrypted unlike yours.
And as a suggestion, if there's someone near you who can help you with actually rooting your device with magisk rather than TWRP it will be much easier.
Regards
SuizShaw said:
Good thing you got it decrypted back again, i have had kind of the same issue with internal storage decreasing drastically multiple times, as far as i understood it happens when i install patched AP with magisk then install multidisabler and reboot it without formatting the whole device, maybe try that when your root next time to get past the internal storage issue. Note that mine was in android 9 and device storage was not encrypted unlike yours.
And as a suggestion, if there's someone near you who can help you with actually rooting your device with magisk rather than TWRP it will be much easier.
Regards
Click to expand...
Click to collapse
I've got the patched image for AP from a friend, also patched TWRP, but it did that after flashing auto disabler and wiping everything, so I still don't get it.
Anyway, it is back for now and I will have to see if it breaks next time I install twrp on it.