Related
This is quite a story I've got here, but just bear with me while I tell it.
Two days ago, I spotted a fps unlock kernel on the Development board here on XDA. I was feeling a bit reckless, so I decided to flash the kernel without doing a Titanium backup. At this point, I was running Fresh 0.5.3. After installing the kernel and rebooting the device, I was greeted with a looping boot animation. Needless to say, I wasn't a happy camper. I flashed every previous version of this kernel, as well as the original kernel, with no success. A Nandroid restore proved to be futile as well. I also tried flashing a fresh copy of the rom onto my phone without doing a complete wipe. No go on that attempt. Finally, I did the stupidest thing I've done with this device and did a complete wipe (data/cache/dalvik,sd:ext), followed by a fresh flash of Fresh (har har). That did the trick. Keep in mind that before performing this last step, I copied the app and app-private folders from my SD card in case of anything.
However, it was then that I realized that my stupid ass had no way of restoring the apps! You see, at least a hundred of the apps on my phone are non-market apk files that would take FAR too long to reflash individually. With that in mind, I installed a bootable version of Ubuntu onto my flash drive, which I used with my netbook in order to access the ext3 partition on my Evo. Afterward, I copied over all of the data from app and app-private onto my SD card. I thought I had finally succeeded in doing something that could have been done so much more easily had I waited to back my **** up previously!
Anyway, that last part occurred about an hour ago. After the files had copied, I exited recovery mode and restarted my phone. I was greeted with the glorious 'FRESSSSHHHHH' boot animation. And then it greeted me again. And again. AND AGAIN AND AGAIN AND AGAIN AND AGAIN RAAARRGH. Anyway, that's where I'm currently at in this whole dilemma. I thought the boot loop meant that the apks in the two app folders were being installed, but an hour is an awfully long time for that to happen.
So now, I am here begging for help from you, the fine people at XDA developers. Is this boot loop animation normal when I've just copied all those files over to the app and app private folder? If not, is there any way to restore my apps without installing them individually through adb or the phone itself?
i don't have fresh, but i use dc 3.2.3 and had a similar issue. i don't honestly remember exactly what i did, but i do know i did a bunch of stuff without backing up and got the boot loop.
here's my thread on it:
http://forum.xda-developers.com/showthread.php?t=722072
i'd link you to the solution we found, but as it's not the exact rom, maybe the troubleshooting steps will resolve your issue. i ended up flashing the engineering build to get access to android, and then flashing dc again to get up to speed.
good luck and let us know how it goes!
shift_ said:
i don't have fresh, but i use dc 3.2.3 and had a similar issue. i don't honestly remember exactly what i did, but i do know i did a bunch of stuff without backing up and got the boot loop.
here's my thread on it:
http://forum.xda-developers.com/showthread.php?t=722072
i'd link you to the solution we found, but as it's not the exact rom, maybe the troubleshooting steps will resolve your issue. i ended up flashing the engineering build to get access to android, and then flashing dc again to get up to speed.
good luck and let us know how it goes!
Click to expand...
Click to collapse
It's not so much fixing the bootloop that I'm worried about. I've already experienced it three times this week, and that can be fixed by wiping the phone clean. What I'm wondering is whether I can install the apps I have backed up by copying over the files from app and app-private
Needless to say, I'll read the thread you linked me to. It might have some useful information .
Just to preface, I have been flashing ROMs for 2 years now, and am by no means new to the game. However, I'll be the first to say that I'm not immune to making stupid mistakes. So if I'm being stupid, you can tell me and not hurt my feelings
I will give a history of what I have done with my phone since Monday after I picked it up, and some quirks I have noticed.
- Set up my phone, accounts etc
- Let Google backup/restore download and install all of my apps
- Installed OTA to ALJC
- Installed Note2 Toolkit on my PC, drivers load, adb recognizes.
- Rooted & Installed CWM recovery
- Flashed stock de-odexed ALJC
- Installed 5x6 launcher & ALJC 4x1 reboot options (rebooted and proceed to setup my homescreens, icons, etc.) (I noticed when trying to flash items from "internal" sd card, it says there are not any
- inserted my SD Card from my OG Epic (Titanium backups in place)
- Restored text messages from .xml file via TB
- None of the games I wanted to transfer data from would run after restoring data from my TB backups, had to clear data and apps run fine, except for NBA Jam (guessing b/c they were from a CM10 ROM and a different device)
-Got all my apps setup, wiped all the bogus data I got from my prior TB backups. After playing with the phone, running apps for several hours, did a full Titanium backup of my phone
- Booted to CWM & Saved a nandroid backup to external SD Card
- Flashed (dirty) ULE 1.0 ALJC Rom (I thought by flashing dirty, it would preserve all my data, apps, etc. = I was wrong)
- Attempted to restore all of my Titanium backups (only ~60% would restore...still trying to figure this out).
- Attempted to restore the backed up 5x6 launcher (with my screens/icons setup intact) via TB. This kind of worked, it definitely changed the icon setup, but it was NOT 5x6, and it did not have my previous layout (probably b/c it was trying to fit a 5x6 on a 4x4).
- Figured that the dirty flash screwed things up, so I would restore my nandroid and go back to square one, where I had stock deodexed with 5x6 & reboot options, and launcher screens intact. So I booted CWM and restored that nandroid.
- After restoring and rebooting, I'm not sure if anything happened at all. I had a 4x4 launcher, no reboot options, and several of my apps were missing (particularly, the ones that would not restore from TB before)
- Figured I aught to factory reset and then restore, same result as above.
- Currently downloading stock ALJ1 tar so I can start all over again
Click to expand...
Click to collapse
I know this is long-winded, but I wanted to put it all out there in case I am doing something categorically wrong with my Note II, so I do not replicate this problem. It has always been the case that a nandroid backup gets me back EXACTLY where I was when I made it (on both my Touchpad & Epic). For whatever reason, this did not happen in this case, even after a factory reset/wipe.
Perhaps CWM isn't working properly? Perhaps I need to try TWRP so that I can manually wipe /system (as far as I can tell you can't manually do that in CWM, but if I understand correctly, this is done when you flash a ROM or restore a nandroid).
Am I doing something wrong? Also, why won't CWM see any of the files I downloaded to the internal memory? Several times now I have booted CWM and when I try to flashing things I downloaded, I have to reboot and move them to my external SD card so that CWM can see them.
Are there settings that are being saved to my external SD card that are causing problems (I highly doubt it)?
Thanks to any and all suggestions/guidance/advice.
Looking forward to learning more and more about these awesome devices.
MeetFace said:
Just to preface, I have been flashing ROMs for 2 years now, and am by no means new to the game. However, I'll be the first to say that I'm not immune to making stupid mistakes. So if I'm being stupid, you can tell me and not hurt my feelings
I will give a history of what I have done with my phone since Monday after I picked it up, and some quirks I have noticed.
I know this is long-winded, but I wanted to put it all out there in case I am doing something categorically wrong with my Note II, so I do not replicate this problem. It has always been the case that a nandroid backup gets me back EXACTLY where I was when I made it (on both my Touchpad & Epic). For whatever reason, this did not happen in this case, even after a factory reset/wipe.
Perhaps CWM isn't working properly? Perhaps I need to try TWRP so that I can manually wipe /system (as far as I can tell you can't manually do that in CWM, but if I understand correctly, this is done when you flash a ROM or restore a nandroid).
Am I doing something wrong? Also, why won't CWM see any of the files I downloaded to the internal memory? Several times now I have booted CWM and when I try to flashing things I downloaded, I have to reboot and move them to my external SD card so that CWM can see them.
Are there settings that are being saved to my external SD card that are causing problems (I highly doubt it)?
Thanks to any and all suggestions/guidance/advice.
Looking forward to learning more and more about these awesome devices.
Click to expand...
Click to collapse
Well I personally use twrp and have had no issues so I cannot speak on your nandroid issues...I do know however that in twrp after selecting internal or external sd card, you sometimes have to manually navigate to the respective sdcard...as for your TB not seeing your back ups from your prior device, go to preferences< backup location< detect and select scan whole device
Sent from my SPH-L900 using xda app-developers app
Just to clarify your remarks to avoid confusion. I can clearly see my TB backups.
I did have to go and do those steps first. About only half of them would restore though. Kind of odd. Maybe some data corruption? Didn't matter if I did them one at a time or during batch mode. Also didn't matter which of the 3 processing modes I selected in TB. Once one of the offending backups was being processed in batch mode, the restore process would hang until I force stopped TB or rebooted.
How much free storage does your internal sd have remaining? I ask because my wife's s3 would do the same when it was below 1gig
Multiple GB, probably 7 or 8. I store everything on my external, music, pics, etc. Haven't had that much chance to fill up the internal yet =]
I don't know. ..Very irritating isn't
It is indeed. But that's the risk of being a flashaholic
...and of being a first-mover on a brand new device =]
Beginning to wonder if me rooting with SuperSu, and then flashing (dirty) ULE which uses superuser, may have caused any problems. Perhaps binaries were conflicting?
MeetFace said:
Just to clarify your remarks to avoid confusion. I can clearly see my TB backups.
I did have to go and do those steps first. About only half of them would restore though. Kind of odd. Maybe some data corruption? Didn't matter if I did them one at a time or during batch mode. Also didn't matter which of the 3 processing modes I selected in TB. Once one of the offending backups was being processed in batch mode, the restore process would hang until I force stopped TB or rebooted.
Click to expand...
Click to collapse
Oh okay I see what you mean now...I have no idea whats going on there lol. ..I hope you can somehow get that figured out because I know how much it sucks to lose app Data
Sent from my SPH-L900 using xda app-developers app
I am really puzzled now, I just odined back to stock and then up through all rooting/etc to get to ULE again. Totally wiped everything. TB is still giving me fits. I'm assuming they backups were bad. Half work, half don't.
I was able to restore apps from a nandroid I made on my OG Epic a month ago. So that's helpful. I'm going to delete all my TB backups once I get everything situated and start fresh (possibly b/c I made backups while on an odexed ROM and restored them on a deodexed ROM?).
I think I'm going to stick with TWRP for now. I don't know if CWM was working properly at all, and TWRP has a few more features. TB wasn't able to see a single app to restore from the two CWM nandroids I made. Not sure what's up with that.
I was going to mention the codex stuff but it really shouldn't matter as you are backing up the data portion not the system. Still you might have a look at setting/storage. USB debug on ...all that jazz
Sent from my Nexus 7 using xda premium
Hi. I managed to root my S3 and remove Knox. At first, TWRP was working fine, but after a few unsuccessful attempts to flash CM, I think i screwed it up. My backup files are gone, and it won't make a new one as it "cannot access storage." It also takes up about 6 gigs of storage on the phone per applications manager, which seems like a lot.
Is there a way to delete it and do a fresh install? now that I am rooted, would another backup/recovery be better?
I have tried searches, nothing seems to be on oint. Perhaps I was casting my net too wide or too narrow.
THANKS
Probably has to do with the /0/0/0 folders. Every time you flashed something, itd create a new /0 directory. Your stuff is still there but the path is messed up so it doesn't know where to look. In twrp file manager look for /storage/0/0/0 or something/somewhere like that. (It's been a while so I may not be remembering exactly right) this is a well documented issue though, so if im wrong just Google it and you're sure to find the right info. I believe it may be covered in one of the sticky threads too.
Sent from my SM-N900T using Tapatalk
Idk if this is your issue or not but I had a problem where recovery couldn't find the files or access storage I had the wrong version of recovery flashed and it wouldn't read anything I originally had the right one but somehow I lost recovery and ended up flashing the wrong one and it did what you are describing I'm on cwm so I'm not sure which is the right twrp but I'd just make sure you have the right one for your model. Good luck figuring it out though I know you will if you do your homework you will get it.
I went in and looked at the files, I had several named backups. I deleted all but one.
Goo Manager wouldn't load the newest TWRP, so I went to the app store and downloaded the app.
Now it takes far less space and recognizes the one backup.
THANKS for bearing with me.
I put a copy of the backup on my computer, just in case. Going to try flashing CM again, hope I can get it to work.
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!
Cannibal Open Touch 3.0 Alpha 9
Disclaimer:
While we try to test our work as much as possible, it is always a possibility that something could go wrong and screw up your phone. We are not responsible for any damage that is done to your device, either directly or indirectly, as a result of using Cannibal Open Touch or any other Project Open Cannibal projects. Any damage done to your device is your responsibility and your responsibility only. We do this for fun, and we simply like to share our work.
What is Cannibal Open Touch?
Cannibal Open Touch is a custom recovery (like ClockworkMod or TWRP), created purely out of love for the platform and the desire to contribute something cool to the community. The name embodies everything that Cannibal Open Touch is. We take what we believe are the best features of popular recoveries like TWRP and ClockworkMod and, well, cannibalize them along with rolling out our own features.
Features:
Full Touch UI
Complete theme support, including app for management of themes (we'll get to that in a sec)
On-device backup and restore
Backup and restore via ADB
Much much more planned!
Bugs:
During installation, the standard Android installing icon gets displayed instead of the custom dialog box.
If you find a bug, please do not report it here! Instead, report it in the GitHub repository!
Screenshots
See the Screenshots tab above. (Or click me if you're using Tapatalk!)
Nandroid has been replaced!
Nandroid is in fact gone, and has been replaced with a much more robust backup solution. Backups can now be made either with ADB (the recommended way) or via the new Backup and Restore item in the main menu. Backups made via the built-in menu can be copied to a PC and restored via ADB, and backups made via ADB can likewise be copied to your device and restored using the Backup and Restore menu.
Code:
adb backup -f mybackupfilename.ab boot system data cache
You can also restore said backup by using adb, like so:
Code:
adb restore mybackupfilename.ab
Downloads:
Cannibal Open Touch hlte builds (latest: CannibalOpenTouch-2.99.9a_hlte.img)
How to install:
Download the latest Alpha image
Copy the image to your sdcard
Flash the image with dd using adb shell or a terminal emulator
Code:
dd if=/sdcard/<path to image> of=dev/block/platform/msm_sdcc.1/by-name/recovery
(may require entering su prior to running dd depending on rom and configuration)
Boot into recovery mode
Alternatively, you may flash using the zip option (available at the same download location) from pre-existing recovery.
Changelog:
3.0 Alpha 9 (2.99.9)
Real menu scrolling! (but volume keys still work)
All backup/restore operations now verify that you want to take action
Resized UI to be more usable on all device resolutions
Themes can now display a battery charge indicator (depends on individual theme settings)
3.0 Alpha 8 (2.99.8)
Not released
3.0 Alpha 7 (2.99.7)
On-device backup and restore
3.0 Alpha 6 (2.99.6)
Complete theme support
Recovery settings (Theme settings and Unsigned ZIP flashing)
The preceding list is not 100% complete. See the project source code page for the full commit list.
Cannibal Open Touch themes app:
We are currently seeking Alpha testers for an app that will let users download and choose themes without rebooting to recovery mode. Currently there are 20 slots open. If you wish to join please PM me. The only requirement is you must have a Google+ account and are willing to submit proper bug reports, should any arise.
Cannibal Open Touch Themes:
You can now make your own themes for Cannibal Open Touch! See the example themes (it's pretty self-explanatory). Themes must be installed in /sdcard/cot/themes/theme_name (or /data/media/cot/themes/theme_name) in order to work. Please feel free to submit pull requests to have your custom themes added to the theme repository. They will also be packaged and made available to download via the Cannibal Themes app (mentioned above)!
Contribute to Project Open Cannibal
If you like our work and want to see more, consider a donation to the project!
Project Open Cannibal gerrit: http://review.projectopencannibal.org
Credits:
tdm, for the superb touch code (and lots more)
drewwalton19216801, for helping to spearhead the project and forward porting most of our old functions
thenameisnigel, for picking up our webhosting while Drew was gone and assisting with device ports
anyone else who has ever contributed to any Android-related project
XDA:DevDB Information
Cannibal Open Touch, Tool/Utility for the T-Mobile Samsung Galaxy Note 3
Contributors
Sblood86, drewwalton19216801, thenameisnigel, tdm, CyanogenMod, Koush and many others
Version Information
Status: Alpha
Created 2014-10-28
Last Updated 2014-10-27
You will notice the image and zip are marked with an a after 2.99.9, this is because I had to re-enable overlays for qualcomm devices to display a screen (they were disabled for screenshots), the version is still 2.99.9
I'm not opposed to uploading an odin package but honestly do not know how to create one (not being an odin person) if someone would like to assist with this I'm available.
Heimdall could also be used to flash the image, if someone has the exact syntax I will add this to the OP.
I understand gsm builds for the Note3 are unified so I would expect this will work on other versions but am not posting it to the others until someone can confirm this. I only have a tmo tester at this time.
Looks interesting will test later
Did anyone test?
So far it made a backup on my sprint note 3 but didn't restore the data correctly. I had to reboot recovery after wiping the phone for the backup to show up
Sent from my SM-G900P using Tapatalk
wormy987123 said:
So far it made a backup on my sprint note 3 but didn't restore the data correctly. I had to reboot recovery after wiping the phone for the backup to show up
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Yeah I saw Drew and Ryan were discussing this in our dev hangout earlier. Not sure if they figured anything out yet or not; will catch up here in a bit. Sorry for the delay on my part, I was sleeping.
Edit:
Just spoke with Drew, we need a backup log to troubleshoot this (for some reason I thought they got one already).
After running a backup, before rebooting you can pull the log using adb.
Connected to your computer (with working adb drivers) please run the following
Code:
adb pull /tmp/bu.log
Since the logs are stored in tmp you have to pull it before rebooting or it will get erased.
Ok I'll do that when I get home
Sent from my SM-G900P using Tapatalk
I can confirm that it works on the international version (N9005).
Didn't play around much. But it successfully flashed a couple of zips I tried.
I like this a lot. Really great job you guys did
Sent from my SM-N900T using XDA Free mobile app
Fantastic job guys! I'm intrigued... making some quick backups now (just to be safe), then I'll be trying this out. I wish I had the dedication to make something like this, but sadly, all my projects seem to end up half-finished and forgotten lol.
Just to be sure, since it is an Alpha, this is reversible, right? No permanent changes, can always go back to another Recovery? Not that I doubt you guys or the work you've put into this, just gotta ask....
edit: "Created 2014-10-28, Last Updated 2014-10-27".....
This Recovery can time travel??? [emoji15]
Now I'm really impressed! Lol
~★astra petas★~
Morningstar said:
Just to be sure, since it is an Alpha, this is reversible, right? No permanent changes, can always go back to another Recovery?
Click to expand...
Click to collapse
Flash Cwm recovery via ODIN and you are good to go
joluke said:
Flash Cwm recovery via ODIN and you are good to go
Click to expand...
Click to collapse
Figured as much, just had to make sure. Downloading now...
~★astra petas★~
Well, it looks like a decent Recovery, but unfortunately I ran into a serious problem, which I'm still trying to recover from (an hour and a half in). Here's what happened....
I flashed Cannibal, no problems there, booted into it and was just kind of poking around. Then I figured I'd go ahead and do a quick backup/restore, just to see how well it worked. In hindsight, I'm almost positive there wasn't enough open space on my internal storage to back up my Data partition (which is approaching 5gb), so I'm thinking that may have been the cause of things. That's just a guess though.
Anyway, it seemed to be backing up just fine. I watched it go all the way from 0% to 100% on System, and from 0% to 18% on Data, at which point I set the phone next to me and went to work on something on my computer. Around 30 seconds later I noticed the screen flash out of the corner of my eye, so I looked at it and it was back to the main Cannibal screen, even though it should've taken 8-10 more minutes, assuming the percentage rate shown is accurate. I didn't see any sort of errors or warnings or anything, so I figured what the hell, and started to restore the backup I had just made.
System seemed to restore just fine, but as soon as it started restoring Data, the phone reboot itself back into Recovery. Trying to restore the backup again had the same results, so next I tried just booting normally. It looked like it was booting alright for a minute, my boot animation played, and the LED was doing it's thing (gotta love Shinto kernel), but that's as far as it went. It just kept replaying the boot animation, never actually booting into Android (and the LED stopped doing it's thing). Let it sit like that for 15 minutes, then gave up.
Next thing I did, was Odin'ed TWRP back on, figuring I'd just restore one of my TWRP backups (I have 2 recent ones that I've restored more than once, so I know they're good). It flashed fine, booted up into Recovery, did a factory reset, since it was now saying I had 0mb free on my internal storage, and did a restore. Things looked alright, watched my boot animation play through then on to the 'Android is updating' screen, which went through all my apps, only to flash that SystemUI force closed for a fraction of a second, then went back into my boot animation, did the updating thing again (showing 13 fewer total apps this time), rinse and repeat. As I said, I'm positive the backup is good, as I've restored from it 4 or 5 times.
So...back to Recovery (TWRP now), and everything I try to do fails; install a clean ROM, fix permissions, wipe, you name it. Finally, after dicking around with various things in TWRP, trying to restore partial backups, manually copying system files, etcetera, I was able to get a ROM to install. Now I'm just in the long, arduous process of putting the ROM I was using back, and restoring things item by item to make sure nothing else funky is going on.
I'm not new to this, by any means, so I know it wasn't due to something stupid I might have done. The only thing I can figure that might've caused it is trying to do a backup without having enough free space on my internal storage, which, ok, is kind of stupid of me, but I would've expected an error or a failure or something, rather than the almost 2 hour debacle I've now been through. lol
Anyhoo, sorry for the novel. I figure'd it would be best just to describe everything thoroughly, in the hopes that someone might read it and figure out what caused it, so others don't have to go through the same thing.
Morningstar said:
Well, it looks like a decent Recovery, but unfortunately I ran into a serious problem, which I'm still trying to recover from (an hour and a half in). Here's what happened....
I flashed Cannibal, no problems there, booted into it and was just kind of poking around. Then I figured I'd go ahead and do a quick backup/restore, just to see how well it worked. In hindsight, I'm almost positive there wasn't enough open space on my internal storage to back up my Data partition (which is approaching 5gb), so I'm thinking that may have been the cause of things. That's just a guess though.
Anyway, it seemed to be backing up just fine. I watched it go all the way from 0% to 100% on System, and from 0% to 18% on Data, at which point I set the phone next to me and went to work on something on my computer. Around 30 seconds later I noticed the screen flash out of the corner of my eye, so I looked at it and it was back to the main Cannibal screen, even though it should've taken 8-10 more minutes, assuming the percentage rate shown is accurate. I didn't see any sort of errors or warnings or anything, so I figured what the hell, and started to restore the backup I had just made.
System seemed to restore just fine, but as soon as it started restoring Data, the phone reboot itself back into Recovery. Trying to restore the backup again had the same results, so next I tried just booting normally. It looked like it was booting alright for a minute, my boot animation played, and the LED was doing it's thing (gotta love Shinto kernel), but that's as far as it went. It just kept replaying the boot animation, never actually booting into Android (and the LED stopped doing it's thing). Let it sit like that for 15 minutes, then gave up.
Next thing I did, was Odin'ed TWRP back on, figuring I'd just restore one of my TWRP backups (I have 2 recent ones that I've restored more than once, so I know they're good). It flashed fine, booted up into Recovery, did a factory reset, since it was now saying I had 0mb free on my internal storage, and did a restore. Things looked alright, watched my boot animation play through then on to the 'Android is updating' screen, which went through all my apps, only to flash that SystemUI force closed for a fraction of a second, then went back into my boot animation, did the updating thing again (showing 13 fewer total apps this time), rinse and repeat. As I said, I'm positive the backup is good, as I've restored from it 4 or 5 times.
So...back to Recovery (TWRP now), and everything I try to do fails; install a clean ROM, fix permissions, wipe, you name it. Finally, after dicking around with various things in TWRP, trying to restore partial backups, manually copying system files, etcetera, I was able to get a ROM to install. Now I'm just in the long, arduous process of putting the ROM I was using back, and restoring things item by item to make sure nothing else funky is going on.
I'm not new to this, by any means, so I know it wasn't due to something stupid I might have done. The only thing I can figure that might've caused it is trying to do a backup without having enough free space on my internal storage, which, ok, is kind of stupid of me, but I would've expected an error or a failure or something, rather than the almost 2 hour debacle I've now been through. lol
Anyhoo, sorry for the novel. I figure'd it would be best just to describe everything thoroughly, in the hopes that someone might read it and figure out what caused it, so others don't have to go through the same thing.
Click to expand...
Click to collapse
Easiest solution is to odin back to stock then flash twrp via odin. Then restore your backup. Would have been much faster.
pyraxiate said:
Easiest solution is to odin back to stock then flash twrp via odin. Then restore your backup. Would have been much faster.
Click to expand...
Click to collapse
As I have quated from his post, he did do that.
Morningstar said:
Next thing I did, was Odin'ed TWRP back on, figuring I'd just restore one of my TWRP backups (I have 2 recent ones that I've restored more than once, so I know they're good).
Click to expand...
Click to collapse
That was quite an interesting read, man.
Glad you got out of it.
I would personally have just got fed up and flashed a stock rom through odin.
FeralFire said:
As I have quated from his post, he did do that.
That was quite an interesting read, man.
Glad you got out of it.
I would personally have just got fed up and flashed a stock rom through odin.
Click to expand...
Click to collapse
I would've too, but didn't feel like downloading a stock ROM, and thought it would be a fairly quick fix. I've messed things up plenty of times, but I've never had anything quite like that happen.
And just to be clear, I'm not saying it was due to any problem or bug in Cannibal, nor do I want to dissuade anyone else from using it. As far as I can tell though, the only "mistake" I made was trying to do a backup to the internal storage without having enough free space, so the devs may want to take a look at things just to be sure there isn't some nasty bug lurking there. :good:
Morningstar said:
I would've too, but didn't feel like downloading a stock ROM, and thought it would be a fairly quick fix. I've messed things up plenty of times, but I've never had anything quite like that happen.
And just to be clear, I'm not saying it was due to any problem or bug in Cannibal, nor do I want to dissuade anyone else from using it. As far as I can tell though, the only "mistake" I made was trying to do a backup to the internal storage without having enough free space, so the devs may want to take a look at things just to be sure there isn't some nasty bug lurking there. :good:
Click to expand...
Click to collapse
They are aware of the bug and I believe are working with a dev up stream to fix it. I to encountered the same error
Sent from my SM-N900P using Tapatalk
no update?
It is in T-mobile forum but download link says HLTE... Can i flash this to HLTE? i mean international hlte SM-N9005?
Also, i saw it an .iso file, whereas other recoveries i flashed like cwm and philz are .zip file (like all flashable android files i've flashed till now).
Can you enlighten me, plz?
ryanrazer said:
It is in T-mobile forum but download link says HLTE... Can i flash this to HLTE? i mean international hlte SM-N9005?
Also, i saw it an .iso file, whereas other recoveries i flashed like cwm and philz are .zip file (like all flashable android files i've flashed till now).
Can you enlighten me, plz?
Click to expand...
Click to collapse
The .IMG file you would use while the phone is booted up. Using an app like Flashily
Sent from my SM-G900P using Tapatalk