Just wanted to share my moment of "boy am i stupid". So i just got the new Note 5 and was super stoked to get it rooted and loaded up with a custom rom. This was my first android since i switched back from iOS. Trying to be very careful not to brick/soft brick my phone i made sure to get all kinds of backups and stock roms/kernels so if need be i can start all over. So i made a CWM backup of my data to restore after i flash the new rom. I had to pull all of my backups off the phone to make space and figured i would just load them back on once the OS is up and running. I get everything going and proceed to do my data recovery. BOOM No files found. I heart dropped out of my chest. What did i do wrong, what did i mess up, how am i going to get all my data back? Well I went right to DuckDuckGo (turned away from google) and started searching for answers. No less then 2 hours later i still have no luck. Well messing around in the recovery system i managed to soft brick my phone and had to fix that first. Well thanks to jovy23 putting aroma in his Rom i stumbled across a file browser and decided to peek around to find my backup file and see if it would help. Low and Behold i found my problem... a simple file location mis match. I had moved my backup from the computer into /sdcard/0/clockworkmod/backup where it should have just been in /sdcard/clockworkmod/backup. I felt so dumb i did not even think that the recovery software would not use the emulated sdcard. So i felt very silly and am now restoring all my data.
Related
Let me start by saying that I am not new to rooting and flashing firmware, its just been a while since I last did it. I've had a nexus 5 for a few months with sprint in the US. I continually have reception issues and dropped calls so I took the phone in to a store. Before I could do that I had to reset everything to stock. I had no trouble doing any of that. I made a complete backup of my ROM before I did all that using TWRP. I went to the store and they told me to turn off lte in order to reduce dropped calls. After the I got home I set to work re-rooting and unlocking my bootlaoder. However when I went to restore in TWRP it would not recognize the backup even though it had been made only a few hours before. I spent several hours trying to get TWRP to recognize the backup. Whenever I navigated to the directory containing the backup the directory was always empty. I even tried zipping the backup and flashing it but it did not work. Eventually I decided to cut my losses and move on. I plan on taking the phone back to sprint tomorrow because I still have horrible reception issues. I really want to avoid having to go through the whole ordeal again but I am not sure what I did wrong. The only thing I can think of is that immediately after making the backup I moved it off the device onto my laptop but did not modify it in any way. I had some experience with CWM back when I had my old HP touchpad but none with TWRP, however they don't seem that different. Any help is greatly appreciated.
UserNumberZero said:
Let me start by saying that I am not new to rooting and flashing firmware, its just been a while since I last did it. I've had a nexus 5 for a few months with sprint in the US. I continually have reception issues and dropped calls so I took the phone in to a store. Before I could do that I had to reset everything to stock. I had no trouble doing any of that. I made a complete backup of my ROM before I did all that using TWRP. I went to the store and they told me to turn off lte in order to reduce dropped calls. After the I got home I set to work re-rooting and unlocking my bootlaoder. However when I went to restore in TWRP it would not recognize the backup even though it had been made only a few hours before. I spent several hours trying to get TWRP to recognize the backup. Whenever I navigated to the directory containing the backup the directory was always empty. I even tried zipping the backup and flashing it but it did not work. Eventually I decided to cut my losses and move on. I plan on taking the phone back to sprint tomorrow because I still have horrible reception issues. I really want to avoid having to go through the whole ordeal again but I am not sure what I did wrong. The only thing I can think of is that immediately after making the backup I moved it off the device onto my laptop but did not modify it in any way. I had some experience with CWM back when I had my old HP touchpad but none with TWRP, however they don't seem that different. Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you put your backups in the correct sub-directory?
Should be something like: TWRP/BACKUPS/87095jgjg9034/nameofyourbackup
upndwn4par said:
Did you put your backups in the correct sub-directory?
Should be something like: TWRP/BACKUPS/87095jgjg9034/nameofyourbackup
Click to expand...
Click to collapse
Yes, I did. I even tried renaming the backup to "backup" and still had no luck.
Well, this is interesting. I went to Sprint today and they weren't much help but before I went there I reset everything back to stock. I made a backup yesterday and when I got home I put it on my phone and it was recognized immediately by TWRP and I was able to restore it. Not sure what I did wrong last time, if I did anything wrong at all.
UserNumberZero said:
Well, this is interesting. I went to Sprint today and they weren't much help but before I went there I reset everything back to stock. I made a backup yesterday and when I got home I put it on my phone and it was recognized immediately by TWRP and I was able to restore it. Not sure what I did wrong last time, if I did anything wrong at all.
Click to expand...
Click to collapse
Yeah, that's a bit odd. Glad you got it working now.
Sent from some device using XDA Premium mobile app
Hi guys, wasn't sure where to post this and I've been searching the web for hours without coming up with an answer with the best way to fix the problem I've got.
So yesterday my sister gave me her phone saying it was shat and slow and generally rubbish (S4 i9505 running 4.4.2). So I had a brief look at it and she had absolutely no room on the phone at all, it was completely clogged. So I deleted all the cache data (4 gigs!!), as soon as I did this the phone came back to life and started updating everything it could, then made a backup in CWM. Thought while I'm here I may as well put the official Lollipop firmware on it from Sammobile. All was good until I realised that she has never backed anything up to google or any other cloud storage (pretty dumb!) and all of her important stuff I couldn't get back.
So I then had to try and extract some data from the CWM backup... couldn't do it. I just couldn't find the files that she wanted restored. Mainly whatsapp messages and pictures and also Smemo. These are all she needs, there's really important memos apparently, why the hell she never backed them up or had another copy of them is beyond me if they were that important!
So I tried restoring just the data part of the 4.4 CWM restore to the 5.0 rom, looking back now I see this is where I went wrong and was asking for trouble.
So I then tried rolling back to the full CWM backup, all went well so I assumed and it said it was successful. This was until the phone booted. Constant spamming of gapps has stopped working, and no matter what I did I couldn't get it to stop, the phone was unusable with it constantly pinging up, every app was failing, and then it would turn itself off and reboot.
So I Factory reset again and wiped everything, installed the backup again, same thing happened again. Even tried flashing the latest version of gapps, but nothing had any effect.
So now I'm thinking oh feck... I didn't make a backup of the Lollipop install as I thought the rollback would have just cured it, and she had already started messing about with it, making it look pretty and getting people to send her some of the important files she had.
So I thought balls, tough luck and you'll have to start again, your fault for never backing anything up. So I reflashed Lollipop, and for some reason it wouldn't boot. Would just hang at the Samsung logo, this was 4am, I was panicking as I'd effectively bricked her phone. So after lots of boot loops and countless flashes I was looking on ebay for a new phone for her, then suddenly it finally boots on one of the flashes.
Anyway after a lot of faffing about, flashing 4.4 which worked, so flashed 5.0 again, and luckily it booted, I don't know what happened, maybe I missed something as I was so tired, so I signed her into google and let all the apps download while I slept.
Now the question is, I seem to have found a site that explains how to extract individual files vaguely, I just need to get the smemos and whatsapp files and I'm not entirely sure where to look and extract these files. Also, will they corrupt if I try to install them on the 5.0 firmware?
Any help would be much appreciated as I'm really in the stinky brown stuff.
Morning bump if anyone can shed some light on this :crying:
Hi
Thanks for writing to us at XDA Assist. Have you tried using this tool?
[Tool] Cwm nandbackup file Extractor ( .img/ .tar files )
It should extract exactly what you need. If you're only reinstalling those specific apps with their data you should have no issues, just don't restore any system data, that's what caused your problems after restoring the KitKat backup on top of the Lollipop ROM.
No response in two days, thread closed, thanks.
Hello I'm sending this post now because I'm going to need somebody's assistance. A quick story I have been doing this for about 3 months as far as my first root to a flashaholic. I have successfully got around my bootloader. The problem is I'm not 100% sure how. I have a good idea of what I did but I don't know exactly as I am NOT a dev and I am new to this. I catch on rather quickly though and have found a passion for modifying my android and this site has been my number one contributor. My goal is to give back and help others out as well. I started off by editing permissions in my system file along with floating feature, csc, features and the customer XML. It was somewhere right in one of those files that I did this.. I simply changed the permission or function and immediately when I did I was prompted by super user to let boot animations by JRummy apps creator of the toolbox to allow permission which I did. The problem is as I didn't realize what I did at the time until I reset it as I changed about 10 different things. About a week prior I tried installing the boot animation into different file folders which was the two options that they suggest. Nothing happened of course my bootloader is locked and i wasn't surprised. Well I changed the permissions that shouldn't have in the calling feature section and I got stuck with force close force close so I hard reset into the factory recovery and trief to clear the cache partition which was unsuccessful. I then decided to install philz custom recovery so I could do a good clean out because obviously the factory recovery is garbage but every time I tried to change it it would stick me in a boot loop after being successfully flashed and in use for at least 24 hours. After I wiped the dalvik cache and the cache partition with Phils I then decided to try one last flash with a custom ROM and everything flashed fine. But once it rebooted I noticed a completely different boot animation and to my amazement it ended up booting and upgrading all my apps it started up normal. The rom I installed was real rwilco's mostly stock version 1.2 G900PVPU3BOG1. After that I decided I was going to take another chance and flash a few modification files. Once again succesfull. This morning I decided I was going to try to do a backup and restore. I backed it up with Phil's recovery and then I restored it. Restoring gave me a bit of a problem as I had to delete the cache and the dalvik cache. I then restarted the system the first time it didn't work or I didn't wait long enough I'm not sure. The second time I hard reset it introduced a normal boot and it started back up and was upgrading all 590 something after they have. Before I did any of this I was working away at a stock rom that I managed to modify a file in. This would be the aboot.mdn i believe. I was able to open it up into a notepad and replace it with the older version in the text part only so the file name itself stayed the same. I don't know if that played a major part to it or not. But I have sense flash recovery and files without getting stuck into a bootloop and with this new firmware almost every time I turned it off and on it would put me in a boot loop just because I was rooted. I attempted to simply change a new battery that I ordered powered off replace battery powered back on and was stuck in a boot loop. I have been making it my goal to somehow crack this thing. This is where I need help because I am still a noob I always just happened to poke in the right places I could care less about reaching 10 posts so I can post links if you like after I upload my information you can go ahead and reset that. I am here because I can seriously help and this website has been a major contributor to me becoming a flashaholic. I am at work right now and have already attempted but I'll go down to a 3G signal if that. I have absolutely no reliable internet here but within 5 hours I will be home uploading to my Google Drive a copy of my manifest and CSC, permissions, and features files. I have also created a clockwork recovery which I am going to upload as well I need somebody to help me go through these and pinpoint exactly what I did so we can get a legit thread with the fix. I somehow basically flashed a new boot animation which i think is blocking my other boot. I have confirm this working I have 2 screenshots I'm going to upload. Anybody with real experience and actually knows what they're doing I would appreciate your help in this matter.. And actually knows what they're doing I would appreciate your help in this matter. I just need to get home to my laptop to upload. Thanks xda you guys are awesome and I hope this is finally my opportunity to contribute and give back.
i ran out of time and couldnt proofread. sorry about that lol'
in my drive account i have a 1) factory rom that i modded aboot.mbn. 2) The backup "philz" cwm recovery. its my full backup apps and all down to the boot image that replaced the sprint yellow screen and the samgsung boot logo. 3) The system files that i have modified.. csc, features, floating feature, customer xml... 3) screenshots of rom info and adding others of some of the mods as we speak. still need 15 mins to finish uploading the sys files
if someone can figure out exactly what i did we have a fix. i have since flashed 30+ mods with no bootloop. email is [email protected] just incase for contact purposes
h t t p s: // drive. google. com / drive / folders / 0B5AfudcH1XDQMVFZdFhVTFdYQ0U---has many spaces only way to fit link
the system files have been diificult to et into my drive. most did not want to copy and the size themself. the full custom restore is in my drive already along with some screens. i have also set my boot animations to random and have about 20 or so cycling. also after restore make sure to wipe dalvick cache and cache. also some of the apps might fc i didnt have them fully restored when i created backup. i added a backup file in drive that has full copy.
Edit: Solved, see bottom
ROM (D6633_Customized HK_1290-5630_23.4.A.0.546_R6C_HK_SuperSU2.46_XZDR2.8.21-signedv2)
Bit of a dumb move on my part. It all started when my snapchat stopped working, I updated, and then Titanium Backup wouldn't restore the data properly (giving me "parse error"). I was trying to fix that and read online that sometimes this is caused by improper permissions, so I booted into recovery mode, couldn't find the option, but somehow decided "hey, maybe my root permission (?) is wrong slash it's 6am and I just watched a wild 2016 election end" and I hit the button. Now my phone is stuck in a bootloop.
So my question:
1) What exactly does re-root phone do (in CWM), and why would that have messed me up? Is it because I have a pre-rooted rom?
2) I wiped cache and delvik and it doesn't help
3) How do I fix this? I was thinking of loading a SuperSU zip on the SD card from my computer and flashing that, assuming somehow a corrupted root is at fault. I can't seem to get the thing in ADB mode as a side note.
3b) If that seems like a good idea, does it matter what one I use?
4) If I reflash the ROM, it should keep my apps and stuff, ya? I don't actually care if my phone is crippled, I just need it to work long enough to properly back up some media, and mainly get my whatsapp over to my new SIM card. If I can't get in it's forever stuck on my old number which I don't have the SIM for anymore.
Any help would be GREATLY appreciated.
Edit: I don't know how to delete this. Anyways, with other resources I found out that because I used a pre-rooted ROM, there were issues with using CWM to try to do the rooting with its built in functions, softbricking the phone. Reflashing the original pre-rooted ROM worked fine.
Hey all,
I've got a question. Most likely a question I know the answer to and I'm in denial. My phone crashed on vacation and wouldn't boot anymore. Not sure how it append but it did. A software failure. After many attempts I've tried to recover some of my vacation photo's an video's. (luckily I've added a cloud sync before going on vacation in case of theft and havn't lost all) In the restore attempts I've soft bricked my phone (from bad to worse) And had to make a clean install with odin. I've installed a clean Stock Rom and rooted it with Magisk (supersu resulted in bootloop). I've tried a few recovery programs from the first page googleling. But no results.
I'm pretty sure the previous version was encrypted and I'm hitting a dead end here.
As for my question: Have I've really given myself the answer not getting it back because of the (possible) encryption or are there better recovery options?
As soon as you started writing over everything with a new flash, you effectively became SOL. There's likely nothing left to recover.
Even before that, while recovery might have been possible, you wouldn't have liked the price tag.
Yeah, thanks. I've figured that. By now I've accepted the fact that I've lost the content and moved on.