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!
Related
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:
So I decided to try and flash Ubuntu last night... I booted into recovery made a backup 15min and 2.5 GB later it was done... wiped flashed no go would not boot... so back to recovery I choose my restore file... system says it was successful but when restoring the data it fails... I'm on twrp 2.5 ...then I tried to just restore the system when booting up I get that static image you see on cm flash every 5 sec but never boot nor goes inyo the boot animation...is there anyway to use this restore file... I just need the data part.. I have messages that i need to show my lawyer and numbers that I need... TiB won't restore my messages either....
Sent from my XT907 using xda app-developers app
You will need TWRP 2.6.3 / PhilZ / or a newer CWM that supports adb in recovery (not sure is 2.5 does)
First off, all of your pictures and other stuff are stored at "/data/media" or "/data/media/0" and are not "wiped" unless picked. These are both accessible in recovery, and you could do an "adb pull ....." to get those files to a PC. At this point you should have your pictures.
Sounds like Ubuntu messed some things up, and when you restored "/system" only it won't boot because of missing data. I once had a problem like this bouncing back and forth between 4.3 and 4.2. Assuming you were on a custom ROM, maybe try wiping completely including "/data/media" DO NOT WIPE "/DATA/MEDIA" IF YOU HAVEN"T BEEN ABLE TO PULL THE FILES VIA ADB IN RECOVERY!!! YOUR PHOTOS WILL BE GONE!!! Sorry for the bold caps, I just didn't want you to miss it. Next install your custom ROM, boot, and do enough setup to get to the home screen. Now go back to recovery and your backup should restore. From here you could "adb push ..." your files back.
Updating TWRP is one way to solve this in the future, like JB already posted. However, to remedy on 2.5, do a clean wipe prior to restore, mounting system prior. Then, restore only the boot.img from the ROM you want and then restore the full ROM you want. This is how I was able resolve this same issue. Hopefully, it will work for you.
I was on stock deodexed debloated prior to all this... after a few tries at the restore I just flashed that same ROM and used TiB to restore what I had on last back up... tonight I'll try and restore that twrp backup ... but either way I guess I'll be updating my recovery... I'm not worried about all my pics n what not I keep all that on the external SD card now...
Sent from my XT907 using xda app-developers app
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/
Hello,
since one week my device, a samsung galaxy s4 i9505, is software bricked and stuck on bootlogo and I've been tryin to save my internal storage, but I'm close to giving up. I hope someone here can help me.
My situation:
1. Updated my TWRP to version 3.0.1-0-jfltexx with odin 3.10.0
2. Flashed new ROM "OMEGA ROM", that worked good.
3. Backup with TWRP, successfull, reboot, galaxy logo appears, flash, again -> bootloop
4. Flashed firmware "i9505XXUHOB8" BL and modem, with odin 3.10.0 in BL and CP
5. No bootloop anymore, but stuck on ROM Logo with normal start and with recovery start blue text "recovery booting..." on galaxy screen but nothing happens.
6. Saw that TWRP 2.8.7.0-i9500 is the recommended TWRP for the i9505, flashed the .img.tar with odin 3.09 in AP (is the .img a problem?) but still same problem, with TWRP 2.8.6.0-i9500.tar too.
6. Tried different firmwares: i9505XXUHOB7, i9505XXUHOF2, i9505XXUHOJ4 -> I thought the problem is the bootloader -> odin error: complete (write) operation failed or NAND write error (->problem was usb port)
7. Tried different odin versions: 1.85, 3.10.6, 3.09
8. Tried different usb cables
9. Flashed cf-auto-root to mount the data partition, but theres no option. Recovery mode is now working, but the samsung recovery, not TWRP.
10. Tried to copy internal storage with ADB, can navigate the directory but can't pull or cd /storage/sdcard0 -> no such file or directory, same with /mnt/sdcard (ADB only works during the ROM logo)
11. Flashed stock samsung firmware "i9505XXUHOJ2_i9505AUTHXXUHOJ1_i9505XXUHOJ2" with odin 3.09 -> now stuck on samsung boot logo. My ROM is now deleted, right?
12. Wipe cache don't help
13. Could wipe data/factory reset or repartition with odin but then I will lost my internal storage.....
I have a backup from the successfull backup with TWRP, but can't open the data.ext4.win001 after rename it (the .win000 is ok)....
Can anyone help me or have an idea how can I save my data and repair the system?
-Mr.Tea
use TWRP to copy files from internal storage over to external SDcard for stuff you wanna keep.
if you manage to backup the data partition you're supposed to be able to extract apps and data from a nandroid with titanium backup pro (never tried it though).
this data you wanna save, if it wasn't created while running omega rom then it wasn't likely to work with it anyway. that could be the source of your bootloops. if that data came from a previous custom rom then try to go back to it, and if successful backup apps with titanium and files to SDcard. you can't keep your data partition and go into a new rom with it.
if the data came from a stock rom you'll loose it trying to go back so extracting from a nandroid is probably your best bet there or restoring once back to stock.
3mel said:
use TWRP to copy files from internal storage over to external SDcard for stuff you wanna keep.
if you manage to backup the data partition you're supposed to be able to extract apps and data from a nandroid with titanium backup pro (never tried it though).
this data you wanna save, if it wasn't created while running omega rom then it wasn't likely to work with it anyway. that could be the source of your bootloops. if that data came from a previous custom rom then try to go back to it, and if successful backup apps with titanium and files to SDcard. you can't keep your data partition and go into a new rom with it.
if the data came from a stock rom you'll loose it trying to go back so extracting from a nandroid is probably your best bet there or restoring once back to stock.
Click to expand...
Click to collapse
TWRP is not working anymore -> blue text "Recovery booting..." on galaxy logo
In many forums they mean TWRP backup not includes the internal storage (/sdcard partition)?!
Can extract my "data.ext4.win000" and "data.ext4.win001" but not find the /sdcard location or my userdata.
Mr.Tea said:
TWRP is not working anymore -> blue text "Recovery booting..." on galaxy logo
In many forums they mean TWRP backup not includes the internal storage (/sdcard partition)?!
Can extract my "data.ext4.win000" and "data.ext4.win001" but not find the /sdcard location or my userdata.
Click to expand...
Click to collapse
try TWRP 3.0.0 by JDCteam, hundreds of happy users there. if it works first time make sure to try backing up your data partition and then wiping it. you can copy your media storage with the built-in file browser as mentioned.
you've got bigger problems if it's not data causing your problems...
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!