formatted and repaired everything in TWRP
I thought I was having problems with my USB c otg so I took it back. Now I'm getting this message just trying to copy and paste the twrp backup on my internal storage as well. When I move it with a file explorer app it fails. When I move it with the built in storage explorer it moves it but its a 0 byte file. Is it a TWRP issue or a CM13 issue or OnePlus issue?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Using the file manager in twrp I can copy and paste the file just fine. I'm on my second different USB c OTG and it's the same problem. boot.emmc.win from my TWRP backup just won't copy over and it even erases everything off my flash drive when failing to transfer. Anyone else have this issue?
I have that issue, too.
Cant find any solution
belek1979 said:
I have that issue, too.
Cant find any solution
Click to expand...
Click to collapse
Me either it's scary enough to stop me from even plugging in my otg storage completely. 1 cable OK maybe, 2 cables, now we have a serious problem and I'm not trying to lose anymore data.
It's a bug in TWRP that makes the file get created with the wrong permissions. (You don't see this if you look at the permissions in the normal place because of how mounting works on Android.) See https://github.com/TeamWin/Team-Win-Recovery-Project/issues/749 for details.
Any chance it gets fixed? That message was 5 months ago. It would be nice to be able to backup to USB otg without everything getting erased.
954wrecker said:
It would be nice to be able to backup to USB otg without everything getting erased.
Click to expand...
Click to collapse
This never leads to anything being erased, and you can easily work around it by fixing the permissions in TWRP.
When Im moving it with the built in file manager or fx explorer it erases everything off my otg flash storage. 50% of the time it erases everything the other 50% of the time it simply copies it as a 0 byte file.
954wrecker said:
When Im moving it with the built in file manager or fx explorer it erases everything off my otg flash storage.
Click to expand...
Click to collapse
That sounds like an unrelated issue.
I think it's the exact same issue I don't think it's a coincidence its always after it gets to that exact file everytime
I was just hoping I didn't have to manually change permissions in recovery, just to be safe in case I ever forgot.
In recovery > ADB I can copy that file to PC without any problems
Yeah I can do it anyplace but when booted into the phone system. It's getting fixed soon so I won't have to worry anymore.
Related
I got a used phone i537UCUCOC7 android 5.0.1. What do i do to downgrade and can i when security patch?
cell2011 said:
I got a used phone i537UCUCOC7 android 5.0.1. What do i do to downgrade and can i when security patch?
Click to expand...
Click to collapse
To downgrade to KitKat, download the following file to your PC and extract with 7zip or WinRar: https://www.androidfilehost.com/?fid=23991606952608110
Boot your phone into download mode. This is done by powering the phone off, then holding down vol- and power at the same time. Connect the phone to PC with USB. You have to flash all four files with Odin as shown in the following image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please be aware that this process will erase any settings, data, and media saved to your phone's internal storage and restore it to its original factory condition, now on KitKat. This process also takes a long time (at least 5 or 10 minutes) and will cause your phone to reboot on its own, and to boot into stock recovery at least once. It is important you leave your phone alone while it is doing so, and definitely do not disconnect it until it boots into the KitKat setup wizard screen.
To apply the security patch, you will now have to flash two files in stock recovery (vol+ and power). First download and extract this file: https://www.androidfilehost.com/?fid=96042739161891196 it should be named 2400258.cfg. You need to rename it update.zip (yes, this involves changing the file type) and save update.zip to your external SD card (it will not work if it's on internal storage).
Finally, you need to download this file to your external storage and flash in stock recovery: https://www.androidfilehost.com/user/?w=settings-dev-files&flid=37222 Please note this file has already been renamed update.zip. They must both be named update.zip for them to work; since this can be potentially confusing I'd advise you to either save them to different folders, or delete the first one after you're done with it.
Follow these steps and you'll be back on KitKat, with that all important security patch. Good luck :good:
I've shut my phone off before going to bed a few nights ago, then when i woke up, i turned my phone on and all i after a default lockscreen is this message :
"Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone , you must perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
( i just borrowed this image from another forum as i cant get a screenshot of mine)
if i stay on this screen i can shut my phone off an on and the volume rocker still works, but the only other option i have is to click the RESET PHONE button.
doing so however only gives me the Android System Recovery mode with the ff options and results i get:
1. reboot : if i choose this, the dead android guy just flashes off and on and i can no longer shut my phone down. have to drain the built in battery to shut it down and try another option.
2. apply update from adb: prompts me to sideload a file.. no idea how to do this.. and i believe usb debugging might be required and i recall my usb debugging mode was off before this issue happened.
3. apply update from external storage : the htc one has a built in sd card (apart from the internal phone storage), and i have no update file on it, nor do i have a way of copying one onto it.
4. wipe data/reset : did so, after which, will need to select reboot option, and will just give same result for option # 1 as above..
5. wipe cache partition : same results as #4.
6. apply update from cache: no idea how to do this either.
i would desperately want to recover my files from the built in external storage. but i'm crossing my fingers anyone can help me get the phone fully functional. factory state will be fine. help please..
Anyone who can help? Thanks
Hey guys, ased this is osm0sis's thread and he advised me to post here - copy paste incoming with link to original post and screenshot included to show what dirs look like. Issue:
Hey guys - hoping there may be a script or something that can be done to fix my Nexus 6 nightmare. I totally messed perms up for /root dirs in recovery - tried both the perm fix zip from here and TWRP fix perms, no luck. Nandroid no luck either. I literally cannot wipe internal - no USB connectivity, Qi charger is all I can use. Is there absolutely any script or anything that can be done to fix my Shamu? SS attached to show a few dirs. I'd be more than appreciative of any help - desperate here, not gonna lie.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Original post in osm0sis's thread http://forum.xda-developers.com/showpost.php?p=68465219&postcount=837
Any help at all would be most appreciated - desperate here guys!
No USB is bad, very bad. Suggestive of something bigger gone wrong bad. Like you corrupted the bootloader or something since fastboot doesn't work.
My only thought is this: So you've probably got root? FlashFire stock boot.img and system.img from the latest factory image and have it format data and cache. Allow FlashFire to do its EverRoot thing to retain root for the case it doesn't work. Since it's a Nexus, if that doesn't work you could try FlashFire to reflash the latest bootloader as well. Nothing really to lose at this point.
Whats about the USB port, did you try to fix it ? Its easy to get to the motherboard, may its enough, if you very carefully try to compress the port.
osm0sis said:
No USB is bad, very bad. Suggestive of something bigger gone wrong bad. Like you corrupted the bootloader or something since fastboot doesn't work.
My only thought is this: So you've probably got root? FlashFire stock boot.img and system.img from the latest factory image and have it format data and cache. Allow FlashFire to do its EverRoot thing to retain root for the case it doesn't work. Since it's a Nexus, if that doesn't work you could try FlashFire to reflash the latest bootloader as well. Nothing really to lose at this point.
Click to expand...
Click to collapse
I flashed an N system image that doesn't wipe data, seemed to fix perms up mostly. Not having issues accessing things, but some displays odd in /root still. Things are all working now, though. I restored Nandroid from before messing up perms and rolled back to my MM AOSiP backup after lettting system image do its thing. As for USB - it's actually hardware failure. The port goes in and out. It's been getting bad a while but recently it's unusable most of the time. I can charge if I let phone sit upside down, but data connectivity doesn't work on computer anymore obviously. Does that indicate anything more than actual USB port itself being messed up? I hope not haha. Thanks for the reply!
coremania said:
Whats about the USB port, did you try to fix it ? Its easy to get to the motherboard, may its enough, if you very carefully try to compress the port.
Click to expand...
Click to collapse
Thanks to @rignfool I am looking into getting a USB port replacement possibly here soon and installing... seems easy enough. Thanks for responding!
Oh, that's good bad news with your port, there's an youtube replacement video. And if your USB port only goes in and out, it should be easy to fix it back to the logic board
Hello, I am a owner of a ZUK Z2 Pro from Brazil, apologies for my english.
I tried to update the mooke rom to pie, but it wasn't working via central mooke, so I downloaded and tried to flash on TWRP, but I was possesed by a demon and instead of not deleting the internal storage, I delete all files. The problem now is that the mobile isn't reconigze in the computer and the device manager shows this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The USBView show this:
Maybe it's something related to the vendor folder that can't be mount on TRWP. I tried adb push, but don't display my device and I don't have acess to allow the usb debugging. I tried USB OTG, but the pendrive is unrecognized. I don't know what to do anymore, but I don't think the mobile is bricked. May day may day!
In twrp you have to click mount otg to make it visible in the file system (if you already did this you can try different adapters/usb sticks). If you deleted the vendor partition I think you should be able to fix it by going back to stock or finding a vendor image/backup. If the only problem is that you ran the vendor to factory script and now twrp dies not find it you can just update twrp. Updating twrp could also help with the unrecognized usb issue.
craftandbuild said:
In twrp you have to click mount otg to make it visible in the file system (if you already did this you can try different adapters/usb sticks). If you deleted the vendor partition I think you should be able to fix it by going back to stock or finding a vendor image/backup. If the only problem is that you ran the vendor to factory script and now twrp dies not find it you can just update twrp. Updating twrp could also help with the unrecognized usb issue.
Click to expand...
Click to collapse
I can't mount otg because twrp don't let me selected the option, I had install all drivers I found of zuk, lenovo and qualcomm and still unrecognizable on the computer, therefore I can flash stock or the vendor image/backup, the version of my twrp is the 3.3.0.0, the most updated. You know if there is a way to force the computer to recognize the device?
Solved doind this.
Hi,
My Huawei P20 Pro broke, but earlier I did an backup of Pictures on it using Huawei HiSuite if I remember correctly. Now I tried to open those pictures on my computer but got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I tried to open using ImageGlass but got this:
Then I checked if Linux file command can identify if it's an jpg file and it can't.
file IMG_20190428_115443.jpg
IMG_20190428_115443.jpg: data
This is because Magic bytes of the file starts with 6425 b4a7 which doesn't match JPG magic bytes https://en.wikipedia.org/wiki/List_of_file_signatures
It does not match file on that page.
So what kind of images are these?
Have you been asked to set a password before you did the backup?
adamdvd said:
Have you been asked to set a password before you did the backup?
Click to expand...
Click to collapse
Nope not from what I remember.
When was that backup done and what was the HiSuite version? It used to create the backup by just copying the files from the phone, but since some time (I believe few years now), every time when you start creating a backup, it is asking to set the password and then all the files are being encrypted.
adamdvd said:
When was that backup done and what was the HiSuite version? It used to create the backup by just copying the files from the phone, but since some time (I believe few years now), every time when you start creating a backup, it is asking to set the password and then all the files are being encrypted.
Click to expand...
Click to collapse
The backup was done 2022-07-26 and I used HiSuite version that was used at that point since I downloaded it when I backed it up. So I don't exactly which version it was.
If you've downloaded the newest version at that time, it was surely the version, which is always asking to set a password, when the backup is done. Your files are encrypted and you need to decrypt them (if it's even possible) or rather restore a backup on your phone (but you need to know that password anyway).
adamdvd said:
If you've downloaded the newest version at that time, it was surely the version, which is always asking to set a password, when the backup is done. Your files are encrypted and you need to decrypt them (if it's even possible) or rather restore a backup on your phone (but you need to know that password anyway).
Click to expand...
Click to collapse
I see. But yeah since the phone broke, I can't connect a phone to HiSuite on my computer and restore them. I would need to have the phone for it which sucks..
I tried downloading HiSuite on my computer but can't import the folders I have from the backup into it because it wants to connect to a phone first..