I am not sure why but when I backup using TWRP Recovery it completes successfully but there is nothing written to the Data partitions. If I try to backup just the data I get a 25 MB file. It should be nearer to 6 GB. Whats more weird is the backup did work a while back and if I restore to that one I can make one more backup with Data included. After that one it stops backing up the Data partition again. Has anyone had an issue where Data is not actually being backed up even though it is selected and shows successful? Any thoughts?
I have a stock rooted Sprint Galaxy S4 on NAE. I have not taken the update.
Update: I tried updating from TWRP 2.6.3.1 to 2.8.0.1. That did seem to resolve the problem but left a new issue. After the backup is complete I always go to the file explorer in TWRP and make sure its there, which is was. But with 2.8.0.1 after I reboot the backup is gone. So I backed up again, and again checked the file explorer and it was there, powered the phone off and put the sd card in my pc and I can see the backup is there. Put the card back in my phone and turn it on, and the backup is gone. ???????
So I tried a different version of TWRP recovery. I installed 2.7.1.0 this time and now I'm back to the original issue. The backup is made, and I can see it again after the phone reboots but there is no data partitions being backed up even though during the process it says it is.
I have attached the TWRP log for assistance. The log shows it wrote quite a bit to data.ext4.win000 but this is 0 bytes in the backup directory. At the top of the log it says "Total size of all data: 7438MB" which I believe is accurate since my last good backup with data was 6.5GB. At the end of the log it says "Data backup size is 5052MB" but the directory properties show the backup size is really 2.2GB. This is because nothing is written to the data archive.
Could someone please help?
Anyone?
I noticed this same thing of 0 byte with data.ext4.win000 file in my TWRP backup 2.7
Viper41086 said:
Update: I tried updating from TWRP 2.6.3.1 to 2.8.0.1. That did seem to resolve the problem but left a new issue. After the backup is complete I always go to the file explorer in TWRP and make sure its there, which is was. But with 2.8.0.1 after I reboot the backup is gone. So I backed up again, and again checked the file explorer and it was there, powered the phone off and put the sd card in my pc and I can see the backup is there. Put the card back in my phone and turn it on, and the backup is gone. ???????
So I tried a different version of TWRP recovery. I installed 2.7.1.0 this time and now I'm back to the original issue. The backup is made, and I can see it again after the phone reboots but there is no data partitions being backed up even though during the process it says it is.
I have attached the TWRP log for assistance. The log shows it wrote quite a bit to data.ext4.win000 but this is 0 bytes in the backup directory. At the top of the log it says "Total size of all data: 7438MB" which I believe is accurate since my last good backup with data was 6.5GB. At the end of the log it says "Data backup size is 5052MB" but the directory properties show the backup size is really 2.2GB. This is because nothing is written to the data archive.
Could someone please help?
Click to expand...
Click to collapse
I noticed this same thing of 0 byte with data.ext4.win000 file and similar other conditions in my TWRP backup 2.7 on N7100 DN3 5.5. I am worried there's some corruption with data partitions. I have then redone the TWRP backup without compression and now the file is of reasonable size. Earlier my phone had gone into sudden bootloops for no apparent reason. Only after I changed the battery (which I had thought was the lamest thing to try) did it come back to normal. My phone however seems very slow and wonky. Now I am going back to dealing with those more serious issues.
I had problems with TWRP also not backing up correctly. I'm not sure why that is the problem, but I use Clockworkmod due to this issue. TWRP was not backing up Touchwiz roms correctly so my restores never worked. It seemed to work fine for ASOP roms though. At any rate, I never found TWRP reliable and I recommend anyone I know to use old school CWM instead.
I had a problem with TWRP a long time ago. Can't remember exactly what it was. I just like TWRP because it's touch but I went with Philz recovery and it never fails and is also touch or you can use the volume keys to navigate along with customize the look. It's the best recovery in my opinion. You should flash Philz recovery.
Here's the link for the Sprint Galaxy S4
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltespr/
Related
Hi, today i wanted to do a factory reset and clean install my phone
im using TWRP 2.3.3.3
after factory reset in the wipe menu, at the end i see a line E:/error opening '/data/lost+found'
basically i know what does lost+found folder does in linux, but i forgot whether i have seen such error line before when i do factory resets.
in the file manager of TWRP i then see /media and /lost+found in the /data partition. when pressing into /lost+found, TWRP cannot open it
after this, wiping /system will also give me the same message at the end even it is "Done", as well as cache and dalvik, etc
then i go on flash rom, gapps, kernel, after 1 or 2 boots i go back to recovery and wipe cache, there are no such line anymore
however there is now TWO /lost+found folder in my /data partition
is this a normal behaviour? i didnt pay attention but are there 2 lost+found folders in /data partition for everyone else too?
i have backed up my sdcard and is ready for a /data wipe, any advice is appreciated. thanks in advance!
update: well really hasnt seen it anywhere tried very hard searching on google
maybe just **** happens sometime as i rushed updating the su binary together with restoring android ID in titanium backup altogether without carefully rebooting etc.
factory reset, formating every partition for N times didnt help. returned to completely stock (unlocked bootloader ofcourse), flash twrp 2.3.3.3 clean and no more that line anymore after factory reset. hell gonna start my sdcard restore now...
Miasmic said:
update: well really hasnt seen it anywhere tried very hard searching on google
maybe just **** happens sometime as i rushed updating the su binary together with restoring android ID in titanium backup altogether without carefully rebooting etc.
factory reset, formating every partition for N times didnt help. returned to completely stock (unlocked bootloader ofcourse), flash twrp 2.3.3.3 clean and no more that line anymore after factory reset. hell gonna start my sdcard restore now...
Click to expand...
Click to collapse
I was researching google for this same exact error message, when I came across your thread. I doubt you are still having this issue, but I wanted to reply with the solution in case anyone else comes across this post. I was able to solve this error message by installing a new ROM. It doesn't matter which one you install, any will do. Then open your file manager of choice, of course one which can go up to root level. Browse to /data, and then you should notice that you do not have a lost+found folder. However, you should see a lost+found file, all the way at the bottom. I renamed this file to lost+foundOLD, and then created a new folder called lost+found. Next, reboot into recovery and once again wipe both caches, system and factory reset. You should no longer get the lost+found error. Make sure to fix permissions as well to make sure.
just had this issue and was solved by dropping back to twrp 2.4.x.x and doing data format.
misspost
mitchallica said:
I was researching google for this same exact error message, when I came across your thread. I doubt you are still having this issue, but I wanted to reply with the solution in case anyone else comes across this post. I was able to solve this error message by installing a new ROM. It doesn't matter which one you install, any will do. Then open your file manager of choice, of course one which can go up to root level. Browse to /data, and then you should notice that you do not have a lost+found folder. However, you should see a lost+found file, all the way at the bottom. I renamed this file to lost+foundOLD, and then created a new folder called lost+found. Next, reboot into recovery and once again wipe both caches, system and factory reset. You should no longer get the lost+found error. Make sure to fix permissions as well to make sure.
Click to expand...
Click to collapse
No his error and mine are different. We have two lost+found dir and no file. If i delete them and make new lost+found folder. It automatically makes 2.
I am having this same problem. I just did a restore to my last backup, but it in TWRP it says mentions the error over and over again. I looked in /data and I found about 10 files called lost+found, but I do not have any folders. Any suggestions?
Full Format data worked for me
NVijapura said:
I am having this same problem. I just did a restore to my last backup, but it in TWRP it says mentions the error over and over again. I looked in /data and I found about 10 files called lost+found, but I do not have any folders. Any suggestions?
Click to expand...
Click to collapse
I just encountered this problem after updating a CM nightly and it bricked my phone. Restoring from a nandroid backup would ultimately fail and I was getting all kinds of weird problems (stuck in boot loop, graphics appearing garbled, etc). After looking closer at the logs during restore, I noticed E:/error opening '/data/lost+found' appearing several times, an then it would indicate 'done' and restart but would end up with the same problems.
Even after doing a factory reset, I had no luck in restoring my phone. So I did a factory reset again and installed a CM stable release thinking maybe my ROM / backup was messed up but noticed the same E:/error opening '/data/lost+found' message. However, this time around I managed to get booted far enough where I could connect via USB and backup files from my internal memory to my computer.
At this point I booted into recovery (TWRP 2.5.0.0) and did a full wipe including internal SD using the Format Data option, whereupon I was able to install the CM stable release without issue - no more lost+found error! I then upgraded to the nightly version of my backup and restored with success. Long and stressful night...
szurheal said:
I just encountered this problem after updating a CM nightly and it bricked my phone. Restoring from a nandroid backup would ultimately fail and I was getting all kinds of weird problems (stuck in boot loop, graphics appearing garbled, etc). After looking closer at the logs during restore, I noticed E:/error opening '/data/lost+found' appearing several times, an then it would indicate 'done' and restart but would end up with the same problems.
Even after doing a factory reset, I had no luck in restoring my phone. So I did a factory reset again and installed a CM stable release thinking maybe my ROM / backup was messed up but noticed the same E:/error opening '/data/lost+found' message. However, this time around I managed to get booted far enough where I could connect via USB and backup files from my internal memory to my computer.
At this point I booted into recovery (TWRP 2.5.0.0) and did a full wipe including internal SD using the Format Data option, whereupon I was able to install the CM stable release without issue - no more lost+found error! I then upgraded to the nightly version of my backup and restored with success. Long and stressful night...
Click to expand...
Click to collapse
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
scwied17 said:
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
Click to expand...
Click to collapse
That worked perfectly. Thanks!!!
scwied17 said:
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
Click to expand...
Click to collapse
Worked perfect for me. Very easy to miss that simple "Format Data" button in TWRP. Simply type 'yes' and problem solved.
I think I got this error when I flashed SlimKAT 4.4 over on my P880 and I had the USB cable plugged in and the partitions mounted (as I had just transferred the install.zip to my phone)
leijonasisu said:
Worked perfect for me. Very easy to miss that simple "Format Data" button in TWRP. Simply type 'yes' and problem solved.
I think I got this error when I flashed SlimKAT 4.4 over on my P880 and I had the USB cable plugged in and the partitions mounted (as I had just transferred the install.zip to my phone)
Click to expand...
Click to collapse
Can i get some help please. I cant format data via TWRP, it says "E: unable to wipe data, unknow fle system, auto, unable to format to remove encryption". I did not put any encryption. What to do?
Hey all,
I have an S4 i337m model. I've installed a custom ROM that is essentially a rooted stock ROM (I do not remember the exact build/version of the ROM). I realize having this info would be useful, but at the moment, I cannot access this info.
While running this ROM, everything was fine. Last week Friday, I attempted to install FoxHound 1.6. Had to play around with the installation options, but I got FoxHound to work. However, I need to get back on my old ROM as I needed some files that were deleted during the FoxHound install. So I wiped my phone, and restored my nandroid backup of my rooted stock ROM. again, everything was fine. No issues.
Here is where the problem is; after restoring my rooted stock ROM, I could boot into the phone and access the files needed. However, when I reboot/shut down phone, upon restarting/powering up, my phone is stuck at the 'Samsung Galaxy S4' logo right after power on. So, I boot into recovery (the latest version of TWRP) and I navigate to 'file manager' to take a look at my storage/files. And this is where I believe the issue to be; I see virtually no files at all. I can see many folders/partitions, but there are virtually no files anywhere (i.e. the system and data partitions are empty). I am assuming this is the reason why my phone doesn't boot past the Samsung Galaxy S4 logo. Now, when this happens, I wipe my phone again and restore my working nandroid backup. Everything works fine. I can get back into Android without issues. Until I reboot/power off my phone. Then this happens all over again.
I believe I may have damaged(?) the partition(s). When I installed FoxHound, I also installed an option during installation titled 'EXT4'. I know linux uses ext2/3/4 partition tables. Did I damage my storage/partition by installing EXT4 from FoxHound? Do I need to repartition my phone via Odin PIT file or something similar? Am I totally wrong with my analysis? Any help/advise/insight would be very welcomed.
Thanks
Additional info
Baseband: I337MVLUAMG1
Build number: JDQ39.I337MVLUAMG1
ROM: Rooted stock ROM 4.2.2 (with some bloatware removed)
While my phone was in the it's 'logo stuck' state, I entered into TWRP and selected the Wipe option, then Format Data. I must select 'Format Data' in order for my phone to work on it's next boot. Manually formatting System, Data, etc... will not allow my phone to boot up at next boot. And, my phone will only work on the next boot. If I power off/restart phone, it will get stuck at the logo again. So my phone is only good for 1 boot up after a wipe.
And, after I restore a working backup and boot into the phone, everything works until next power down/reboot. Once I power down/reboot phone, I must go into recovery since it will not boot into Android. When I get into TWRP, I see that my Internal Storage has 0MB free and I am unable to see any files. I can see folders/partitions, but there is nothing in any folder/partition. My external SD card shows nothing as well. My external SD card however is unaffected as all the data is still there once I get into Android and look around.
Also, I just restored a backup I had before I was having this issue. After restoring and rebooting, the same thing happens. I get stuck at the 'Samsung Galaxy S4' logo.
So I'm guessing there is some partition troubles here. Maybe I'm wrong, but I'm scratching my head as to the cause of this problem.
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
jd1639 said:
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
Click to expand...
Click to collapse
I thought the same thing. I'm downloading the stock ROM now and will give it a try.
One other thing I noticed during my last restore/fix attempt... After I perform a wipe -> Format Data (from TWRP), I notice that it reverts to my rooted stock ROM without me restoring anything. So, after I do a full wipe/format, and reboot my phone immediately after the full wipe/format, my phone will boot into the rooted stock ROM. I thought that wiping/formatting via TWRP totally cleans the internal storage of all data. So how can I be booting into any ROM after a wipe?
Unless I'm mistaken in my thinking and the full wipe/format option in TWRP just reverts back to the stock ROM I had installed prior to installing further custom ROMs?
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Do not format data in twrp.
jd1639 said:
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Click to expand...
Click to collapse
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
xBeerdroiDx said:
Do not format data in twrp.
Click to expand...
Click to collapse
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Talabis said:
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Click to expand...
Click to collapse
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
jd1639 said:
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
Click to expand...
Click to collapse
Is TWRP 2.5.0.0 ok to use?
Ok... It's really starting to look like my partition table has been damaged. Every time I flash a new ROM or restore a nandroid backup successfully, and then restart my phone, I get stuck at the S4 logo. Upon starting recovery, my internal storage reads 0MB free. It seems like my partition table is becoming corrupt after a reboot, or it has already been corrupted.
I tried flashing the stock ROM for my phone (I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar is the one I used), but that didn't help at all. After installing this stock ROM, and I go into stock recovery, I get an error: E:failed to mount /data (invalid argument).
This really is looking like a partition problem. Is there some way to re-partition my phone? I remember a PIT file was used to partition my old Galaxy S i9000. Is there a PIT file for the S4 i337m?
I would also like to try CWM but I am having a hard time finding a ODIN flashable version.
I wouldn't mess with a pit file and I haven't seen one anyway. It's sounding more and more like your memory is bad. I'd keep it stock and see if you can get an exchange on the phone under warranty.
Further investigation has lead me to the culprit... sorta. It's my /data partition that is screwing everything up. If I format /data and then reboot, I can get into my phone. But if I reboot again, then my /data partition becomes corrupt and my phone hangs at the S4 logo. And then if I go into recovery, I can see that my internal storage is at 0MB free.
However, after formatting/restoring /data partition and rebooting into android successfully, everything works fine. If I reboot from this point and enter recovery, I am still able to see my /data partition and files. At this point, everything seems to be fine. Once I reboot out of recovery and let the phone boot into Android, I get stuck at the S4 logo and my /data partition screws up/becomes corrupt. It looks like my /data partition is only becoming corrupt after the 1st successful boot into Android. If I enter recovery after the 1st successful android load, I am still able to see all files and partitions. It is only trying to load android after the 1st boot that my /data partition becomes corrupt. Very strange...
So, I can always boot into my phone as long as I format my /data partition prior to loading Android. Anyone experience this before? Any ideas? I realize my memory may be damaged, but I'm leaving that as a last resort possibility since my phone was working fine up until I started installing FoxHound with the EXT4 option as well as installing 1 or 2 of the kernel's FoxHound provides. Namely Adam kernel is the one I tried.
All good... I think/hope
Well, I think I got the problem solved. After toying with this thing all day. It seems like TWRP 2.6 was the problem in some sense. Looks like TWRP 2.6 does not format the /data partition correctly. I had to get restore/install a working ROM, boot into my phone and install ClockworkMod Recovery via ROM Manager. I then used CWM to format /data. Once I did this, and loaded back into my phone, and went through the setup process since /data was formatted, everything was working fine. I just rebooted 5 times and shut down twice and my phone booted back up into android without issue.
So as one user in this thread had mentioned, formatting /data with TWRP 2.6 was the problem.
Hope this helps others avoid a similar issue.
Thanks everyone for all the help. It pointed me in the right direction.
Glad you got it fixed.
I'll be giving these steps a try, having somewhat of the same problem!
i've been having this exact same problem but with TWRP 2.5.0.2 since July. Its been driving me insane and I have not been able to find any one else having this issue until now. I think i might finally try CWM instead as a last measure before I finally give up!
Try TWRP 2.6.3.1 version. It works pretty well even though it's unofficial http://forum.xda-developers.com/showthread.php?t=2262996
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Hi
When I attempt to make a backup using TWRP v2.3.2.3 from Matt's 1.20 Utility I get this message:
"[BACKUP STARTED]
* Backup Folder: /external_sd/TWRP/
E: Unable to locate sd-ext partition.
Updating partition details..."
It finishes almost instantly and under the white text "Backup Complete" at the top of the screen it displays in red Failed.
I have 100% battery charge
Stock 4.1.2 with out the latest OTA
I already made one successful backup right after installing TWRP v2.3.2.3 on my phone from Matt's Utility the other day.
Phone is Rooted utilizing Matt's Utility
Bootloader is unlocked (Matt's Utility)
Under Settings I have checked Force MD5 check on all zips. and Enable MD5 verification on backup files.
Under Mount Menu all but Mount System are checked.
I am attempting to save the backup to my External SD. But it also fails when I try the internal storage
I don't know if this is a major issue but my time zone doesn't select the proper time.
Under the Advanced tab I selected Fix Permissions and it still fails.
I haven't messed with much else because I'm not sure what they will do. ADB Sideload, Reload Theme etc,...
I find this extremely odd. I have used Hash-code's Safestrap 3.12 for nearly a year with flawless performance always made a back up when I needed it to. when I unlocked my bootloader i was under the impression that TWRP was way better than SS, but here I am having problems the second attempt at making a backup?
Does it only save one backup at a time?
Is there a setting that I need to adjust?
Do I need to update/Upgrade to a new version?
Is there a version of Safestrap users like me with an unlocked bootloader?
Why cant it find the ext partition the TWRP folder is there and even tho it fails it places an empty folder in the proper location with the name I gave to my failed backup?
My SD card is partitioned for use with Link2SD. But that was never an issue with SS or the first TWRP backup I made the other day.
I have plenty of space (42 GB) on my external. so that shouldn't be the issue.
I'm starting to miss Safestrap. But I really want this to work. Help please. Thank you.
SARM1084 said:
Hi
When I attempt to make a backup using TWRP v2.3.2.3 from Matt's 1.20 Utility I get this message:
"[BACKUP STARTED]
* Backup Folder: /external_sd/TWRP/
E: Unable to locate sd-ext partition.
Updating partition details..."
It finishes almost instantly and under the white text "Backup Complete" at the top of the screen it displays in red Failed.
I have 100% battery charge
Stock 4.1.2 with out the latest OTA
I already made one successful backup right after installing TWRP v2.3.2.3 on my phone from Matt's Utility the other day.
Phone is Rooted utilizing Matt's Utility
Bootloader is unlocked (Matt's Utility)
Under Settings I have checked Force MD5 check on all zips. and Enable MD5 verification on backup files.
Under Mount Menu all but Mount System are checked.
I am attempting to save the backup to my External SD. But it also fails when I try the internal storage
I don't know if this is a major issue but my time zone doesn't select the proper time.
Under the Advanced tab I selected Fix Permissions and it still fails.
I haven't messed with much else because I'm not sure what they will do. ADB Sideload, Reload Theme etc,...
I find this extremely odd. I have used Hash-code's Safestrap 3.12 for nearly a year with flawless performance always made a back up when I needed it to. when I unlocked my bootloader i was under the impression that TWRP was way better than SS, but here I am having problems the second attempt at making a backup?
Does it only save one backup at a time?
Is there a setting that I need to adjust?
Do I need to update/Upgrade to a new version?
Is there a version of Safestrap users like me with an unlocked bootloader?
Why cant it find the ext partition the TWRP folder is there and even tho it fails it places an empty folder in the proper location with the name I gave to my failed backup?
My SD card is partitioned for use with Link2SD. But that was never an issue with SS or the first TWRP backup I made the other day.
I have plenty of space (42 GB) on my external. so that shouldn't be the issue.
I'm starting to miss Safestrap. But I really want this to work. Help please. Thank you.
Click to expand...
Click to collapse
first, I would recommend to uninstall SS via the app (not using the OS manage apps interface). secondly, I almost always mount system prior to making a backup - not sure if that makes a difference or not. thirdly, I have gotten the "failed" message before - and that usually happens when I have 3+ backups and/or running out of room on my external SD card. typically, I will delete one of the backups, and then it will back up. also, the process takes about 20 minutes, so I usually plug in my phone during this time (sometimes when the phone is plugged in, it performs better).
another issue could be that you are using 2.3.2.3 with the latest OTA - you mean the latest TWRP version. however, that said, I'm still using 2.3.2.3
hope this helps.
jco23 said:
first, I would recommend to uninstall SS via the app (not using the OS manage apps interface). secondly, I almost always mount system prior to making a backup - not sure if that makes a difference or not. thirdly, I have gotten the "failed" message before - and that usually happens when I have 3+ backups and/or running out of room on my external SD card. typically, I will delete one of the backups, and then it will back up. also, the process takes about 20 minutes, so I usually plug in my phone during this time (sometimes when the phone is plugged in, it performs better).
another issue could be that you are using 2.3.2.3 with the latest OTA - you mean the latest TWRP version. however, that said, I'm still using 2.3.2.3
hope this helps.
Click to expand...
Click to collapse
jco23
Thanks for the help brother. I appreciate it. But I found the answer on an older post on another forum. What corrected my issue was going to settings and pressing restore defaults. That's it! lol but after that it worked like a charm. thanks again.
respectfully:victory:
I am stuck on the start up screen which shows Samsung Note 3 and Custom. I have an old nandroid file but how do I put the file somewhere where TWRP can find it. It will not show up on the micro sd card. I cannot access anything on the phone by plugging it in to the computer. I dont know how I got in this mess but I did the full wipe on twrp and I could never get past the start up screen after that. I have tried to flash alliance 2 but it never gets past the start up screen. I cannot flash a custom kernel. I show it failed.
Any suggestions. Again this is developer edition.
texasez said:
I am stuck on the start up screen which shows Samsung Note 3 and Custom. I have an old nandroid file but how do I put the file somewhere where TWRP can find it. It will not show up on the micro sd card. I cannot access anything on the phone by plugging it in to the computer. I dont know how I got in this mess but I did the full wipe on twrp and I could never get past the start up screen after that. I have tried to flash alliance 2 but it never gets past the start up screen. I cannot flash a custom kernel. I show it failed.
Any suggestions. Again this is developer edition.
Click to expand...
Click to collapse
When TWRP makes a nandroid backup, whether on sd card or on the internal storage, it creates it inside several folders like /[storage]/twrp/serial_number_folder/... , the backup you made, is it still inside that level of storage folders? if you can get to twrp / recovery mode, it should let you search for the path of the nandroid backup. If that doesn't work, go to beans' file collection thread in the Development forum, there he has a MJE full restore tar file for the dev edition, make sure you use that one and not one of the retail edition tars. Flash the MJE dev edition full tar file through Odin, and it should put you back at an almost fully stock dev edition setup, then from there you should be able to get into your phone and find your nandroid backup and restore in twrp, or you can install other roms. Make sure you DON't restore /efs in twrp, it'll mess up your phone's nv partition and then there's almost no way to fix that, so when restoring in twrp, always make sure the check mark next to efs is OFF, do not restore /efs from twrp. Good luck!
Hello,
Today I tried to root my Nova and somehow I managed to delete the system while doing that. I don't know how or when, I did wipe the phone at some point, but left system unchecked. So now it is stuck in an endless boot, I just see the orange "Your phone is unlocked and not safe etc" message, nothing more. I can access TWRP and fastboot, and tried to use the LineageOS 13. But it failed, it told me I need a CAN-model, and mine is "generic_a53". So I figured I'll just put EMUI back on it, but I can't seem to find a working version for my phone. The huawei-website is pretty useless in that regard, they don't offer it. And the HiSuite-recovery just said that my model is not supported anymore.
So.. help? I know I screwed up and should have made a full backup, but I never figured I'd screw this up so spectacularly.
EDIT: Okay, I just clicked on "Backup" in TWRP, out of curiosity, and it said that "System" is 2516mb, but "Data" is 0mb, so maybe that's what's lacking?
Seems you are using the wrong TWRP. Use the one made for lineage. Also, what is your exact model number, you should be able to recover that way. My guess is you wiped data, factory reset, or formatted data. You could try using the backup made by bluesmoothie to restore data. You will have to search around this forum as I can't remember exactly which thread it is in.
fragee said:
Hello,
Today I tried to root my Nova and somehow I managed to delete the system while doing that. I don't know how or when, I did wipe the phone at some point, but left system unchecked. So now it is stuck in an endless boot, I just see the orange "Your phone is unlocked and not safe etc" message, nothing more. I can access TWRP and fastboot, and tried to use the LineageOS 13. But it failed, it told me I need a CAN-model, and mine is "generic_a53". So I figured I'll just put EMUI back on it, but I can't seem to find a working version for my phone. The huawei-website is pretty useless in that regard, they don't offer it. And the HiSuite-recovery just said that my model is not supported anymore.
So.. help? I know I screwed up and should have made a full backup, but I never figured I'd screw this up so spectacularly.
EDIT: Okay, I just clicked on "Backup" in TWRP, out of curiosity, and it said that "System" is 2516mb, but "Data" is 0mb, so maybe that's what's lacking?
Click to expand...
Click to collapse
Just like @wangdaning said, you're using wrong TWRP.
If you wanna flash LOS13, you gotta flash the TWRP mentioned at requirements.
It told you that your model is "generic_a53" because you're using "twrp_huawei_generic_a53.img".
To restore your phone, try to restore the backup made by bluesmoothie.
1) Download the TWRP backup (emui 4.1) made by @bluesmoothie from here: https://www.dropbox.com/sh/qrk0fbpn...ffYdia7raa/TWRP/BACKUPS/FPFDU16930014596?dl=0 . I had to download the files one by one, as I couldn't download the whole folder because dropbox was telling me that it's too big. After you've downloaded all the files from backup, put them in a folder named 1970-03-18--16-40-58_CANC432B100.
2) Download this recovery: https://www.androidfilehost.com/?fid=745425885120713827 , which is made by @Grarak.
3) Make a backup of boot.img so a folder will be created at TWRP > BACKUPS (e.g. FPFDU16A20001907).
4) Place the TWRP backup folder into the folder created at step 3). So, it'll be like this: TWRP > BACKUPS > FPFDU16A20001907 > 1970-03-18--16-40-58_CANC432B100.
5) Restore the backup.
Okay, it was the wrong TWRP, now that I flashed the recommended one, I was able to install LOS13, and now everything is working again. Thank you very much guys!