So today I wanted to try something as I had issues with an app.
I made a full nandroid backup with twrp.
After setting up my phone and try the new app I wanted to restore to the old situation.
When restoring I got the error
createTarFork() process ended with ERROR: 255
After a reboot, no decryption password is asked, all files and folders have strange names.
As a result the phone doesn't boot any more except into recovery.
I'm on oxigen os 9.0.8, latest twrp.
Any clues on how I can fix this.
Phone is a brick now...
yelti said:
So today I wanted to try something as I had issues with an app.
I made a full nandroid backup with twrp.
After setting up my phone and try the new app I wanted to restore to the old situation.
When restoring I got the error
createTarFork() process ended with ERROR: 255
After a reboot, no decryption password is asked, all files and folders have strange names.
As a result the phone doesn't boot any more except into recovery.
I'm on oxigen os 9.0.8, latest twrp.
Any clues on how I can fix this.
Phone is a brick now...
Click to expand...
Click to collapse
Some treads below yours is the possible solution https://forum.xda-developers.com/oneplus-5/help/createtarfork-process-error255-t3727673
And: you should always remove pin/security before restore or before backup
strongst said:
Some treads below yours is the possible solution https://forum.xda-developers.com/oneplus-5/help/createtarfork-process-error255-t3727673
And: you should always remove pin/security before restore or before backup
Click to expand...
Click to collapse
Thx,
I checked but not really my situation.
I don't have the 999 users issue.
I have made a screenshot of my /sdcard folder:
{
"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"
}
* it seem that my picture is not comming through, so a link to it imgur
Hopes this sheds some light.
What I got from those threads:
My backup was pretty large, 22GB.
I think I will try to flash the stock rom and see where that gets me.
yelti said:
Thx,
I checked but not really my situation.
I don't have the 999 users issue.
I have made a screenshot of my /sdcard folder:
* it seem that my picture is not comming through, so a link to it imgur
Hopes this sheds some light.
What I got from those threads:
My backup was pretty large, 22GB.
I think I will try to flash the stock rom and see where that gets me.
Click to expand...
Click to collapse
So I tried a sideload of the factory images.
Flashing is successfull, next I reboot the phone.
It shows me the oneplus logo and reboots to recovery.
I tried installing the stock recovery, but then when I try to sideload the firmware, the usb device is not recognized.
I have an idea, but I don't know if is doable.
I would want to backup the data partition, (adb pull /dev/block/sda13 data_encrypted.img).
Next I would wipe the phone completely, setup encryption with the same pincode.
Next I would like to restore the old data, but I don't know how.
I hope this way I will ask to decrypt my data partition again.
Anyone an idea?
So an update:
I dumped the data and recovery partition.
Code:
adb pull /dev/block/sda13 data_encrypted.img
adb pull /dev/block/sde22 recovery.img
5494 KB/s (67108864 bytes in 11.927s)
Next I wiped the data partition, phone started normally.
I encrypted the phone again with the same pin code.
Next I tried a nandroid backup and restore while the phone was encrypted, no issues there.
Next I flashed an older recovery to the phone.
Now the test to restore the recovery from the image.
On the phone with an adb sheel:
Code:
dd of=/dev/block/sde22 | nc -l -p 9999
On the pc:
Code:
adb forward tcp:9999 tcp:9999
nc 127.0.0.1 9999 < recovery.img
On the phone I get a lot of data on the screen and the message
Code:
8+0 records in
8+0 records out
4096 bytes transferred in 64.155 secs (63 bytes/sec)
First thing I noticed: number of bytes transferred where not the same as the original recovery.
Next I dumped the recovery partition again to disk and compared the md5 hashes, not the same.
Rebooted the phone and it did not go into recovery.
So this process did not work.
Any ideas?
So, It didn't work with netcat, so I did the following:
connect an usb-c to usb-a coverter to the phone, and connected the external drive with the "bad" image on it.
Then dd-ed the image to the data partition.
When I rebooted the phone, it didn't ask for a pin code and the file and folders where gibbirish again.
So I was back to the starting position.
I'm affraid my data is lost forever :s.
Hello @yelti , I know it's been a long time but I'm kinda into the same issue. Have you been able to fix yours? Do you remember how? Thanks.
Related
I'm trying to side load the OTA for Lollipop using adb and the files available from Google. My device is unlocked and rooted.
I run the commands to sideload the zip file and everything seems to be working fine until I get 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"
}
I've cleared the cache partition but to no avail.
Does anyone have any insight or am I going to have to wipe everything?
Well I went ahead and did a Flash Stock + Unroot and now it's worse. No error messages. Just the android with the red triangle exclamation mark.
I'm getting fed up with this crap. Every time there is an OTA I have to jump through hoops to get it running again.
Anyone have clues about what to do now?
Skullpuck said:
Well I went ahead and did a Flash Stock + Unroot and now it's worse. No error messages. Just the android with the red triangle exclamation mark.
I'm getting fed up with this crap. Every time there is an OTA I have to jump through hoops to get it running again.
Anyone have clues about what to do now?
Click to expand...
Click to collapse
If you already flashed stock and lost you user data plus can still get into the bootloader, then I suggest using a factory image to upgrade to Lollipop. I've ignored OTA's and have been applying the factory image for a while.
Not in this case but for next time, with the aid of root, a custom recovery to make a nandroid backup, Titanium backups for apps and user data. Prior to applying a factory image save a copy of the Titanium Backup directory, the nandroid backup plus any sundry files that were not backed up to a OTG SDCard (an OTG cable plus USB SDCared reader), getting back to your specific set up is not all that complicated. Plus you get to "spring clean" any old cruft that has built up wasting internal storage.
See: How to install Android Lollipop factory image on Nexus 5, 7 and 10 (and keep your data)
I have the same problem
I had system partition full after L update. I did it with factory image. I had to remove some apps from system to get adaway, busybox and so on working.
How to get more system space??
veepee78 said:
I had system partition full after L update. I did it with factory image. I had to remove some apps from system to get adaway, busybox and so on working.
How to get more system space??
Click to expand...
Click to collapse
Deleting apps from /system is the only option that I've heard of. You cannot change the /system partition size even if you have spare internal storage. If you're rooted then this sounds worse than it is because there is plenty of apps you likely do not use (e.g. some of the google apps like news). You're also unlikely to use some of the foreign language apps. Even some of the main Google aps get updated out side of /system making the the /system apks redundant.
Without even trying hard I removed 86MBs worth then installed all I wanted (e.g. busybox, Viper4Android ... etc) and still have 54Mg free. So I could have left a lot of apps installed but I'd never use them anyway.
You can delete /system apks if your rooted with a number of different apps:
- Titanium Backup
- A Root enabled file manager like ES File Explorer
- My personal favourite System app remover (ROOT)
Lots of options.
Skullpuck, did you find a solution?
Did you guys try ADB version 1.0.32 or newer? Something has changed in the sideload command (could be only when using TWRP, not sure)
Hello.
I've repaired a nexus 4 screen and digitizer but I got it back because my friend can't recover access from a forgotten pattern lock.
He is running stock android 5 lollipop and he doesn't get the email recovery option when he inputs wrong pattern. I've searched even in google support but I didn't find a solution to recover his photos.
My main concern is to recover files and photos!!! There isn't a reason to suggest a factory reset....
--Phone Status---
Boot loader seems unlocked "Locked state is marked as unlocked in bootloder in red letters" while secure boot is enabled in green letters
USB debugging seems OFF: There is no android device listed in device manager. I only get a music player in disk drives which is empty.
adb devices command in bootloader recognises it
When entering to recovery I get the message "no command" along with the icon of an android under repair.
No dropbox no google+ photos backup
---What I've tried---
UPDATE: Managed to flash TWRP 2.7.1.0 I can see the files but since usb flash drive doesn't work I can't copy the files...
Android Device manager: Returns error that the phone is already locked and there is no need to apply new password.
Tried about 30 wrong patterns and it didn't came up the google mail recovery option.
Tried during a phone call to see the files but I only managed to turn on WiFi.
{
"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"
}
When you say the USB flash drive doesn't work, do you mean the USB port in the phone?
MTP doesn't always work in TWRP, meaning it won't show up as a normal usb drive on a pc. ADB will still work though, you have to set up ADB on your computer, boot into twrp on the phone and use 'adb pull' to copy the files to the computer. On windows you will need to download adb and the drivers, I use http://www.koushikdutta.com/post/universal-adb-driver
I'm trying to install the drivers for adb but I cannot find the right one.
Edit: Also it cannot be detected from boot loader now. I'll try in a pc that already has been connected and worked.
I have adb and fastboot installed already and worked with this and my own phones.
Edit: It seems to be a lost cause the phone fell down many times. Don't bother maybe I'll solder a usb port first... if it is possible with my less than basic equipment.
There are many methods on the following page,
http://forum.xda-developers.com/showthread.php?t=2620456
The way I did it was an alternative version of method 5 while in twrp.
Method 5 - alternatively, Mount system in twrp and delete the file /data/system/gesture.key
If it asks for a pattern on boot just try any random pattern it should let you in. I did this when a version before lollipop was installed but there is no reason it shouldn't work on lollipop as the same file is saved in the same location, just checked.
Using adb
adb shell rm /data/system/gesture.key
Click to expand...
Click to collapse
Hello guys.
I am really tired of looking for a fix for my problem. I am asking for help rarely and today is that day that I need your fast help with fixing my phone.
So...
I wanted to create a backup of 2 partitions - modemst1 and modemst2.
I have used the command "reboot nvbackup" - phone restarted, but no files created in backup and restarted already without IMEI code, and then I realized that phone is not recognizing SIM card.
First thing I have thought of - okay, lets reflash this thing. That's what I did, never with a success. I have tried flashing the original Samsung software into my phone, no help.
Tried to enter to service mode to fix it - nope - just blank window with rows, probably because SIM is not recognized.
Full wipe? Didn't help. Busybox and GSII_Repair neither.
Then by browsing root stuff I found out that I am missing 2 files:
- /dev/block/mmcblk0p10
- /dev/block/mmcblk0p11
I think that might be a problem which needs to be fixed. (I have tried to backup those two files, with no success, and as it seems, I have probably deleted the accidentally)
I was thinking if someone can back those blocks up and send the images to me so I can somehow recover those two files (Lollipop)
I have no backup of EFS folder.
I have tried to flash the modem.bin from stock firmware, no luck, no fix.
So I am looking for help from you guys, you are my last hope to get that thing fixed.
Problems to fix:
No SIM detected
No GSM signal
Unknown Modem version
Null IMEI
Missing files in /dev/block folder
EDIT: I promise that I will create a guide if I will fix it. But I need to fix it by tomorrow.
It will be nice if somebody can make an image of working EFS partition of his/her Note 3 and send it to me. After that I will check out if it works.
Almost 100 views, and still no answer? Is it that bad?
You need download file PIT and flash fw
JustCinek1 said:
Hello guys.
I am really tired of looking for a fix for my problem. I am asking for help rarely and today is that day that I need your fast help with fixing my phone.
So...
I wanted to create a backup of 2 partitions - modemst1 and modemst2.
I have used the command "reboot nvbackup" - phone restarted, but no files created in backup and restarted already without IMEI code, and then I realized that phone is not recognizing SIM card.
First thing I have thought of - okay, lets reflash this thing. That's what I did, never with a success. I have tried flashing the original Samsung software into my phone, no help.
Tried to enter to service mode to fix it - nope - just blank window with rows, probably because SIM is not recognized.
Full wipe? Didn't help. Busybox and GSII_Repair neither.
Then by browsing root stuff I found out that I am missing 2 files:
- /dev/block/mmcblk0p10
- /dev/block/mmcblk0p11
I think that might be a problem which needs to be fixed. (I have tried to backup those two files, with no success, and as it seems, I have probably deleted the accidentally)
I was thinking if someone can back those blocks up and send the images to me so I can somehow recover those two files (Lollipop)
I have no backup of EFS folder.
I have tried to flash the modem.bin from stock firmware, no luck, no fix.
So I am looking for help from you guys, you are my last hope to get that thing fixed.
Problems to fix:
No SIM detected
No GSM signal
Unknown Modem version
Null IMEI
Missing files in /dev/block folder
EDIT: I promise that I will create a guide if I will fix it. But I need to fix it by tomorrow.
Click to expand...
Click to collapse
one more solution.
You need download firmware have 5 files. inside have file .pit and flash it using Odin. Step-by-step flash it. this is wrong/error partition EFS. or you need download file .pit for your device exp: .pit N9005 using only for N9005, you choose PIT location on odin. Remember you need tick to Re-Patition.
Good Luck!
{
"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"
}
Your stuff didn't help me at all, sorry. It was the same after these things which You told me. But I have fixed it and you can mark this thread as solved. I am currently writing a guide what to do to fix that stuff.
Hello experts!
After updating to OOS 2.2.1 through stock updater, after reboot I get:
Code:
OEM_NV_BACKUP The NV partition is invalid!
Of course, no IMEI, no network on both SIMs.
Been googling all day, to no avail.
No root, stock recovery, EFS available.
I have tried:
This one:
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
And this one, similar to first one:
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21 (Oneplus Two - Solution for Hard Bricked Device).
Is there a hope or I need to send it to repair center?
Tagging @Zyxxeil @Lord Boeffla, maybe some ideas will pop up.
EDIT:
EFS backup restoration in TWRP does not fix it.
Thanks in advance!
Juraj
do you have any back up of your EFS partition in twrp backup?? if you have restore that partition and see.
chintu1234 said:
do you have any back up of your EFS partition in twrp backup?? if you have restore that partition and see.
Click to expand...
Click to collapse
As said....no.
TWRP did not backed it up.
Any other method/idea, ayone?
EDIT:
Just figured out that I have EFS backed up (oem_stanvbk.emmc.win). I will restore it from twrp, lets see how it goes.
jukyO said:
Hello experts!
After updating to OOS 2.2.1 through stock updater, after reboot I get:
Code:
OEM_NV_BACKUP The NV partition is invalid!
Of course, no IMEI, no network on both SIMs.
Been googling all day, to no avail.
No root, stock recovery, EFS available.
I have tried:
This one:
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
And this one, similar to first one:
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21 (Oneplus Two - Solution for Hard Bricked Device).
Is there a hope or I need to send it to repair center?
Tagging @Zyxxeil @Lord Boeffla, maybe some ideas will pop up.
EDIT:
EFS backup restoration in TWRP does not fix it.
Thanks in advance!
Juraj
Click to expand...
Click to collapse
Any further ideas, as EFS restore from TWRp doeas not work.
Can someone please check what files are inside TWRP EFS backup?
Sent from my A0001 using XDA-Developers mobile app
jukyO said:
Can someone please check what files are inside TWRP EFS backup?
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
{
"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"
}
here is the file that have in my EFS backup from TWRP
lockmunk said:
View attachment 3729740
here is the file that have in my EFS backup from TWRP
Click to expand...
Click to collapse
I have exactly the same.
Why restoration of it does not solve it?
If I pull
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
with dd:
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
to sdcard, they have 1M each, whilst backup is 10M.
Can anyone try the same?
EDIT:
above mmcblk is for OPO, OPT has /dev/block/mmcblk0p20.
And size is ok if I do dd with it.
bump, anyone?
jukyO said:
bump, anyone?
Click to expand...
Click to collapse
bump #2.
got the same issue, damn x) need help, tried the 100% restore backup with qualcomm drivers etc, didnt restore 100%
bump..please help to share your modemst1 & modemst2 please......
androidbrick.com
Nothing on androidbrick...
Hello! Here is everything i did to get to this point:
• Unlocked the bootloader
• Installed TWRP
• Took nandroid backup
• Wiped everything (excluding USB-OTG)
• Tried to move files to the phone, and it created a no-name file with the windows drive icon
• Tried to delete the file, couldn't.
• Disconnected from PC, tried to wipe Internal Storage again, said " Error opening: '/data/media' (No such file or directory) "
{
"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"
}
And it still continues to say "Error opening: '/data/media' (No such file or directory)" every time i try to wipe the Internal Storage, doesn't matter if MTP enabled/disabled or if connected to PC or not.
So now i cannot move any files or folders to the phone, when i try, it does nothing.
When i try to create a directory on the phone, just says this (see image below) or hangs Windows Explorer.
I did all of this following this guide: https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
TWRP IMG used: Bluspark TWRP
I did NOT flash supersu or magisk, because i was going to install ResurrectionRemix ROM on the phone after all this. Also i did not reboot to OOS after installing TWRP, just wiped everything and i cannot move anything to the memory now.
[EDIT] When i go to Wipe>Advanced Wipe>Select Internal Storage>Click Repair or Change File System it says "Invalid partition selection"
What should i do? I hope i didn't somehow brick my brand new phone :crying:
did you try flash TWRP recovery "again" via fastboot? so restart phone in fastboot mode> flash recovery via ADB (or just copy TWRP recovery.img to your excisting TWRP and flash again as "recovery">reboot) You should than have a clean recovery. Than wipe everything also (incl. format data.) Than reboot in recovery and copy ROM file, Gapps, Magisk etc..etc.. from pc and start from a clean "scratch"
Edit: i had this kind of issue also while flashing unofficial Oreo LOS build. I ****ed it up also. Keep in mind as long as your PC reconize your device you are totally NOT bricked. So don't worry!!!
I solved it myself somehow...
Sorry about this whole post, i just somehow got this working when i tried to sideload an img file (ik, i'm a genious) it said "corrupted zip file" and now i can see everything again on the Internal Storage... wow.. How do i close a thread now?
Glad it worked out!
I think only a Forum Moderator can close threads.
Oh, ok. Do i need to contact one or do something so they can remove/close the thread? Thanks for the fast response anyways!
lekiaM said:
Glad it worked out!
I think only a Forum Moderator can close threads.
Click to expand...
Click to collapse
Mwah, no need. Mostly they keep the threads "open" so that other users with "similar" issues can learn or reply in your thread for help.
Ok. This just made no sense to me. Ty
lekiaM said:
Mwah, no need. Mostly they keep the threads "open" so that other users with "similar" issues can learn or reply in your thread for help.
Click to expand...
Click to collapse