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
Related
I have searched the entire forum and haven't found the answer to my problem...I have even asked in the rom specific thread (where other people have had a similar problems) but my question (and theirs) just gets overlooked!!
So here it is.
I have both radio S-off and the End Hboot and have flashed three different custom roms on my HD (the Core Droid, Revolution HD and LeeDroid) all giving me the same problem.....I cannot set the system as r/w using apps such as Root Explorer and SUFBS!
I tried entering the mount command by itself in a terminal on the phone and I get:
# mount
mount: no etc/mtab
I can however mount the system from adb shell by inputting: mount -o remount,rw /dev/block/mmcblk0p25 /system
but that isn't really a solution!
I have a nandroid backup of my original stock rom which I have rooted and I can mount the system fine using root explorer and do not get this 'no etc/mtab' message when I type mount in the terminal.
I find it odd that it occurs with three different custom roms but not on my original stock rom so maybe it could be the way I flash the roms? ...I always use the Full_Wipe.zip with CWM recovery which formats the boot, system, data and cache partitions and then I apply the rom.
I've been pulling my hair out over this...and I know it must be something simple, but I've been stuck with this problem with no solution for a week!
Does anyone have any ideas?
EDIT: It turns out that some of the custom roms have limits in place that prevent editing the system and therefore were causing errors. Have tried the Cyanogen rom and have not encountered the errors/restrictions so it was definitely due to those custom roms. Not really a solution, but found the 'cause' of the problem.
Hmmm....looks like I'm the only one with this problem. Has no one else had anything similar?
your not the only one, i hbave had this too, this prevents you from removing apps doesnt it, now is it the 1.72 rom or the 1.34 rom
try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.
if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.
mariosraptor said:
try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.
Click to expand...
Click to collapse
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
fkofilee said:
if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.
Click to expand...
Click to collapse
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...
after doing what you have to do you can go again to Root Explorer and remount as read only.
fl4r3 said:
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...
Click to expand...
Click to collapse
mariosraptor said:
after doing what you have to do you can go again to Root Explorer and remount as read only.
Click to expand...
Click to collapse
I guess thats the best option for now...not a complete solution, but a work around that doesn't require a pc at least.
Would still be good to find the cause and fix it!
I've got the same issue! Are you sure the error you receive is 'no etc/mtab' and not 'no etc/fstab'?
Anyway I've been using the App 'Mount System (rw/ro)' as my solution for now and it works a treat. Still, as you can imagine it is not a permanent solution!
The only thing I feel may have contributed to the problem was my original root attempy via Visionary failed and I had to wait until the R13 before I could unroot and root again. Possibly something got borked along the way. Did you have any similar issues?
Will be keeping my eye on this thread and if I do find a solution I'll let you know.
Regards.
It’s definitely a ‘no /etc/mtab’ error.
When I rooted I used Visionary r14 and the only hiccup I had was that it didn’t permaroot on the first try so I had to redo it.
It’s odd that my nandroid backup of stock doesn’t give me the error and its only the custom roms that do! I have a feeling it might be something to do with an incorrect/incompatible Busybox installation with the custom roms...
sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.
cattleprod said:
sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.
Click to expand...
Click to collapse
I've tried looking for /etc/mtab in my stock rom but its not present..I don't think its a physical file thats why it can't be copied....
But I think you may be right about it being an app based problem...just tried LeeDroid V1.3 (based on 1.72 rom) out of curiosity and root explorer still wasn't working. I then wiped again but installed root explorer fresh from the market instead of titanium backup and it is now working!! YAY!!
However, SUFBS still does not work and returns 'no /etc/mtab' when I type 'mount' in its terminal and reinstalling (either from titanium backup or fresh from the market) does not make a difference. Since root explorer is now working I believe that the dev for SUFBS needs to update his app maybe?..or is there still something wrong with my system?
yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this
fkofilee said:
yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this
Click to expand...
Click to collapse
Ahhhh, if thats true then it makes sense! Thats why the custom roms were giving me trouble but not my rooted stock rom and why adb commands from a pc work. I guess its a precaution but still an inconvenience...especially when I want to make changes/do something away from the pc.
......the question is: is it true? are you 100% sure the custom roms don't allow changes?
its 100% true, well most of the new ones anyway, CM was built from open source code and is completly there creation BUT
custom roms created from stock are basically modded ROMS
Just tried Cyanogenmod rom 6.1.2 and have had no issues at all! So it seems fkofilee is right...some of the custom roms just don't allow changes to the system.
So not really a solution but atleast found the 'cause' of the problem.
I noticed you said you used the full wipe .zip has everyone else used it ??? As I did not use it the first Rom I flashed was leedroid 1.2 and then 1.3 the only thing I used was cw recovery wipe/factory reset and my root explorer never failed can toggle between the two and when I first booted all my apps synced back via market did not use titanium backup not keen on it also I've read a few posts problems with titanium not restoring apps also read somewhere the full wipe zip doesn't always work right maybe its the wipe and titanium that causing it
Just a thought
Sent from my leedroid v1.3a DhD via xda app
I use full wipe. Zip but I never have problems with root explorer. Been using more than 1 Rom. ( Modaco r 2, leedroid 1. 3, Hd revolution. And also I have modded them a lot to look aosp.
Sent from my LeeDroided Desire HD
Hi,
I was using PSFreedom PS3 jailbreaker app, which messes with the bootloader. After first reboot it was fine, I disabled it and after that reboot it was fine again.
Third time however, it went directly into the bootloader. I rebooted again and back into the white screen bootloader. It gives the option of FASTBOOT and RECOVERY etc, which I can get into fine.
I am assuming I can just reflash CM7 and fix this?
Also, is it possible for me to perform some sort of ADB command to fix this WITHOUT reflashing? The reason I ask is coz I have some save games on it that I havent backed up that I wanna keep. Or is there even a way I can back up an app from Amon-Ras recovery menu??
Thanks.
I'm actually just gonna try using ADB pull to backup the /data/data/com*.* directory of the specific games I want.
Does someone know if I do that, will it work? Coz I've installed that patch that installs APPS to the partition on the SD card, giving me more space on my phone. So do I need to "adb pull" from that other partition too?
Well usually the a2sd scripts will, not move the data-folder, so you'll only need to pull /data/data/* to backup. This will work for most apps, however some might check for this and disallow it, but it shouldn't be a problem.
And yes backing up and reflashing is the most suitable solution.
Additionally i'd like to correct you. No the ps3 bjailbreak does not mess with the bootloader. It uses a custom kernel(/boot) and activates a feature in there. Whereas the hboot is something entirely different, which the system cannot mess with in any way.
Verizon Galaxy Nexus.
I was running 4.0.4 IMM30B leak. The new leak/possible update came out, I decided to flash it. Saw that it was only good for updating from 4.0.2 (ICL53F), so I wiped, formatted, and reinstalled it. Re set up my phone (titanium backup, homescreens, android market updates for a few apps, the basics). Everything seemed fine, though I didn't try saving anything. Ran the update to the new 4.0.4, and everything seemed fine and dandy.
The next day, titanium backup runs (scheduled) and fails. Says not enough storage or something despite the fact that it also shows ~14GB free space...
Tried to take a screenshot of the issue, and I get a notification that it "Couldn't capture screenshot." "Couldn't save screenshot. Storage may be in use."
Curious, I tried to take a picture with the system camera app, and it doesn't seem to save pictures either. Though no error messages tell me such things.
Caching seems to work, updating apps seems to work, using 'most' apps seems to work, but saving data to the virtual SDcard has no such luck.
Assuming that it's a permissions issue, I went into CWM Recovery and did a 'fix permissions.' Though that has not fixed anything.
Various searches have shown me that others have experienced this problem, but I haven't seen anyone with a solution. Also, they seem to be experiencing it in various AOKP roms (specifically for the Transformer tablet).
Question: Anyone know what I can do to fix it?
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
msedek said:
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Glad to hear that there is a fix. I may end up doing this tonight... I'm hoping that a quicker, simpler fix is available (something like boot an insecure.img and change permissions of these folders via adb, or something).
Thanks for that though, as I now know that it should work.
Happening on GSM Galaxy Nexus as well. I tried a rom over milestone 5, then reinstalled milestone 5 and restored my backup, and then got this problem. Seems sdcard is not writable to at all. Gonna try out the bootloader locking stuff i guess.
I ended up using the Galaxy Nexus Toolkit (for time and automated simplicity) to wipe the device, reflash 4.0.2 (signed by Google), reroot, CWM reccovery, and restore the virtual sdcard backup saved with the toolkit.
Once the virtual sd was restored, I restored my apps (but no system apps) with titanium backup. Haven't had the time since to reupgrade to 4.0.4, but 4.0.2 seems to be working for me nicely.
I am able to screenshot, and nice things like that, but sometimes titanium backup is giving me errors about not being able to save due to insufficient space (still 14GB free). Gonna dive into that issue today.
4.0.2 works good.. What its bad about it its the lag, the ROM its laggy and also the battery life and the photo quality.. ICS now its much better than 4.0.2
Sent from my Galaxy Nexus using xda premium
No fix?
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Redscorpian said:
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Click to expand...
Click to collapse
Dat gravedig.
Just try reflashing your device from a stock image.
Beauenheim said:
Dat gravedig.
Just try reflashing your device from a stock image.
Click to expand...
Click to collapse
And do you think that'll be leaving it as it is?
I fixed this deleting the "pictures" folder with RootExplorer.
jwiegand said:
I fixed this deleting the "pictures" folder with RootExplorer.
Click to expand...
Click to collapse
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
bergmanman said:
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
Click to expand...
Click to collapse
I'm on a different phone, but I fixed this issue by clearing the defaults for the program that launched pictures. In my case, I use Gallery, so in Program Info under Settings, I reset defaults and everything worked fine. I guess this is the same thing as deleting the Pictures folder since I believe it is an issue of 'releasing' the memory that remains in use by your respective program. For all future requests as to which program should be used to launch a file (or picture in this case), I never select the option that binds future requests to one specific program. Hope that helps .
My fix: re enable the media scanner!
Like many others, I have disabled the DRM and media scanner services because of the bug that caused ridiculous cpu usage (particularly on boot). Re enabling the media scanner fixed this problem right up. If you want a free and easy utility to do this, check out: "Rescan Media ROOT"
https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
Disclaimer: I am not associated with the author of that app.
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I tried all the previous solutions without success, but manually creating the Pictures/Screenshots folder worked flawlessly on my LG 4X.
Thanks TulsaDavid!
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thanks alot! Worked for me!!
Thanks, TulsaDavid!
Making screenshots folder solved it for me aswell.
Unable to take Screenshot, USB storage maybe in use
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I have tried using home+power button, turned on swipe and had difficulty in using the S PEN to make the screenshot - still doesnt work.
I also tried making a new folder but still doesnt work.
My unit is Samsung Note 8.0
/sdcard permissions broken
Just had this happen on my Nexus 5.
The cause was using adb push to copy files to /sdcard when I was booted into recovery. All the files and folders were owned by root:root. I had to reboot to recovery, adb shell, and then
Code:
chown -R media_rw:media_rw /data/media/0
It might be possible to do this while booted in android with Connectbot or something, but I didn't try that.
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thank you TulsaDavid. This helped me tremendously. You're a deity!
Sent from my SGH-T989 using Tapatalk
Hi. I just switched from 1 custom 4.3 rom to a different one and i did a factory reset. However once i rebooted, i noticed that all my internal SD content had gone into 0/0/0/0 etc. i kept clicking but eventually file explorer on widows just froze.
I went into ES file explorer on my phone and saw the content was behind 400 0's!!!!
Anyone have any idea what i could do to recover that info? every time i try copying the files ES explorer either crashes or says that it had copied the files when it hadnt.
Any help would be greatly apreciated. I'm at my wits end... :crying:
Thanks
Bro you need to use a file explorer from recovery. TWRP custom recovery has a built-in file explorer. That should do the trick
Sent from my SGH-T999 using Tapatalk
aussie88 said:
Hi. I just switched from 1 custom 4.3 rom to a different one and i did a factory reset. However once i rebooted, i noticed that all my internal SD content had gone into 0/0/0/0 etc. i kept clicking but eventually file explorer on widows just froze.
I went into ES file explorer on my phone and saw the content was behind 400 0's!!!!
Anyone have any idea what i could do to recover that info? every time i try copying the files ES explorer either crashes or says that it had copied the files when it hadnt.
Any help would be greatly apreciated. I'm at my wits end... :crying:
Thanks
Click to expand...
Click to collapse
Also, you should update your recovery as the more recent versions have fixed that problem. It doesn't happen each time you flash with the new versions.
fingolfin14 said:
Also, you should update your recovery as the more recent versions have fixed that problem. It doesn't happen each time you flash with the new versions.
Click to expand...
Click to collapse
Yep I figured that out the hard way lol. Already upgraded to the latest version of CWM to prevent it from happening anymore. Now to get the files out from down there... :banghead:
Sent from my SGH-T999 using xda app-developers app
On Windoz, You could troll and copy out every 10 deep or 20 deep back to surface and then continue. That'd be better than crashing Explorer.
Dos Prompt is more rugged. You could write a batch script there.
Perseus71 said:
On Windoz, You could troll and copy out every 10 deep or 20 deep back to surface and then continue. That'd be better than crashing Explorer.
Dos Prompt is more rugged. You could write a batch script there.
Click to expand...
Click to collapse
I saw that somewhere and tried that. Doesnt seem to be having any effect. Unless im doing it wrong...
I'm plugging my phone into my computer, accessing the phone section when it comes up, going about 20 0s deep and copying it back to the root. It either crashes my windows explorer, or doesnt seem to be doing anything(i think because its already disconnected itself. i tried making a new folder and it wouldn't let). what am i doing wrong?
PS. how would i access my phones internal SD from DOS?
thanks
Try ADB FileExplorer that should not time out on Windows. I have also tried Android File Manager with success. If that does not work, I will look up other options.
Well i tried android file manager. Im not 100% sure exactly how these programs work, but either way its saying i dont have root access. I do and i also have chainfires adbd insecure app which should give me full root access, but its still not working.
I looked at ADB FileExplorer too, but i didnt really get it and it kept saying it couldnt find my phone and something about an incorrect path.
With the Android File Manager, when it accesses the Phone over ADB, it will ask for Root once. If you don't click SuperSU warning in that time, the File Manager will give this error. Please read its thread carefully. I have connected over ADBWIRELESS and this just fine.
Perseus71 said:
With the Android File Manager, when it accesses the Phone over ADB, it will ask for Root once. If you don't click SuperSU warning in that time, the File Manager will give this error. Please read its thread carefully. I have connected over ADBWIRELESS and this just fine.
Click to expand...
Click to collapse
It never asked for root on my phone. I've tried all the changes and everything else that people have recommended, but im still not having any luck. I guess im too much of a noob for all this lol :crying:
Try Re-mounting internal SD in Recovery and then connect to PC.
nope, still no luck. Its still saying no root and no supersu request is coming up. I guess im missing something....
EDIT: I seem to somehow be "losing" root every time i try to connect to the android file manager. i open an app that requires root and it says i dont have root. I have to reboot my phone to get root to work again. It's weird though, because SuperSU opens fine...
open the last "zero" folder on your computer, drag everything into a folder on your computer desktop, let everything copy (do something else in the mean time), delete your phone memory, copy everything back to your cleared phone memory card
Lieu10ant said:
open the last "zero" folder on your computer, drag everything into a folder on your computer desktop, let everything copy (do something else in the mean time), delete your phone memory, copy everything back to your cleared phone memory card
Click to expand...
Click to collapse
If only it was that easy. its behind 400 nested folders. Windows cant go that deep. it freezes and FC's after about 200.
Im giving my phone in to get my power button repaired, so i guess ill ask the software tech there if he can figure it out. But thank you Perseus for all your help last night. :good:
I also have this problem guys, how do i update my custom recovery please?
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.