• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Sleipnir v2.4.0.5 - 10/24/13 - VM & SPRINT

Nope no system apps are being restored. And no busybox or ministro. All user apps, some root apps, I assumed maybe restoring the root apps would screw something up if I restored the data on them as that might also restore what I put in the /system using them. So I didn't restore any of those. And mt phone doesn't bootloop until I use TB to restore. Like I said I've even restores just games even. Like angry birds and sentinel 3: homeworld. Still bootloops after restoring. I even tried restoring just the app. Still bootloops. Even tried backing up the /data manually from the /data partition of my apps and then moving it back there manually after rom install. It will work just fine until I reboot then it will only boot for a few minutes each time and then soft reboot. My TB is the donate version I got for free cracked by the develiper of the app, he let ppl use older versions without paying for them and included an apk for Lucky Patcher for it. It's version 5.1.0.3. I usually format everything I can except my internal/external sd card. I format dalvik, cache, battery stats, system, data, and I do all of those 3 times. Is it maybe a permissions issue with TB setting my apps for wrong permissions?
 
HackADevice said:
ohhhhh you don't have to restore data only app?
Click to expand...

HackADevice said:
also how do you do that titanium backup flash that you were talking about ??Artine??
Click to expand...

For stability reasons I never restore any app data or system apps, just apps alone. When you select a batch restore you can deselect app data at the top, then select the apps to restore. Even restoring app data between updates can cause issues, especially if switching ROMs.

The paid version of tibu has an option to create an update.zip that you can flash in cwm.
 
sneaky_1 said:
For stability reasons I never restore any app data or system apps, just apps alone. When you select a batch restore you can deselect app data at the top, then select the apps to restore. Even restoring app data between updates can cause issues, especially if switching ROMs.

The paid version of tibu has an option to create an update.zip that you can flash in cwm.
Click to expand...

I thought it was on the free one as well.

HaTrEd360 said:
Nope no system apps are being restored. And no busybox or ministro. All user apps, some root apps, I assumed maybe restoring the root apps would screw something up if I restored the data on them as that might also restore what I put in the /system using them. So I didn't restore any of those. And mt phone doesn't bootloop until I use TB to restore. Like I said I've even restores just games even. Like angry birds and sentinel 3: homeworld. Still bootloops after restoring. I even tried restoring just the app. Still bootloops. Even tried backing up the /data manually from the /data partition of my apps and then moving it back there manually after rom install. It will work just fine until I reboot then it will only boot for a few minutes each time and then soft reboot. My TB is the donate version I got for free cracked by the develiper of the app, he let ppl use older versions without paying for them and included an apk for Lucky Patcher for it. It's version 5.1.0.3. I usually format everything I can except my internal/external sd card. I format dalvik, cache, battery stats, system, data, and I do all of those 3 times. Is it maybe a permissions issue with TB setting my apps for wrong permissions?
Click to expand...

Well, there's your problem. Lucky Patcher has some issues with our phones and others as well, and I would never use a pirated version of one of the best apps out there. More than likely, it's because it's pirated - more specifically, because it's cracked. TiB is probably developed well enough that if it's cracked, it doesn't have everything it needs to act as the full version does (properly) and gets confused as to whether or not it's free or paid, and without having everything it needs it probably screws up in the restoring phase, or writes the wrong data somewhere, which is my guess as to why there are bootloops. The description alone of the problem - that it's happened with every ROM - sounds like it might be the app if there's no problems until using it. Were you using a cracked version the entire time?
 
I used to just use the free version from the Play Store. It did all the same things. Only reason I got the cracked donate version was so I didn't have to manually hit install on every app upon restoring them. That took hours to restore 86 user apps. But I'll try doing the app only option to see if it works. And it wasn't cracked by a random person tho, it was cracked by the developer of TitaniumBackup so I don't see why there would be any problems. He gave it away as donate version so others could try before they buy.
 
HaTrEd360 said:
I used to just use the free version from the Play Store. It did all the same things. Only reason I got the cracked donate version was so I didn't have to manually hit install on every app upon restoring them. That took hours to restore 86 user apps. But I'll try doing the app only option to see if it works. And it wasn't cracked by a random person tho, it was cracked by the developer of TitaniumBackup so I don't see why there would be any problems. He gave it away as donate version so others could try before they buy.
Click to expand...

Then that would be different, as he would have made sure it's done correctly. While doing a batch restore, try only doing the app portion of your user apps first. Then try restoring the data for each one. It could be that doing both data and app is causing something to go amiss and render it unto a bootlooping state.

I don't know if this is available on the free version, but under Preferences there is "App processing mode", try changing this to see if there is an improvement. Also, if you've changed TiB's compression of backups, I would try setting it back to GZIP. There may be something in the settings that could be changed to avoid the bootloops.
 
I went back to 2.0.6 after noticing that some widgets were gone such as picture frame which I use, so I may be off but, when do you think you'll be able to fix the screenshot feature Artine?
 
DraeHD said:
I went back to 2.0.6 after noticing that some widgets were gone such as picture frame which I use, so I may be off but, when do you think you'll be able to fix the screenshot feature Artine?
Click to expand...


My picture frame works just fine on 2.0.9
 
DraeHD said:
I went back to 2.0.6 after noticing that some widgets were gone such as picture frame which I use, so I may be off but, when do you think you'll be able to fix the screenshot feature Artine?
Click to expand...

The 2.0.9 test build has a perfectly functional picture frame - I'm using it right now. Deskclock was removed because it's unnecessary, but I can add it back in.

As of right now, I can't even boot ICSE to verify that it works at all (the screenshot feature). ASJ80 and I are looking to how to get scripts to work properly - it doesn't seem as though they will once the phone boots. Which isn't helpful. I'm confident that once there's a fix for the scripts, screenshot and the search button remap will both work properly upon install with a ROM (which is the problem with the search button remap, it seems to work fine if you're already on a ROM and add it then, but I'm trying to get it included with the ROM itself, not to be installed post-ROM-install). If anyone else has any ideas, feel free to PM me - we have init.d scripting support, but it doesn't seem to actually run the scripts on boot. And it may not be running them at all.
 
Artine said:
The 2.0.9 test build has a perfectly functional picture frame - I'm using it right now. Deskclock was removed because it's unnecessary, but I can add it back in.

As of right now, I can't even boot ICSE to verify that it works at all (the screenshot feature). ASJ80 and I are looking to how to get scripts to work properly - it doesn't seem as though they will once the phone boots. Which isn't helpful. I'm confident that once there's a fix for the scripts, screenshot and the search button remap will both work properly upon install with a ROM (which is the problem with the search button remap, it seems to work fine if you're already on a ROM and add it then, but I'm trying to get it included with the ROM itself, not to be installed post-ROM-install). If anyone else has any ideas, feel free to PM me - we have init.d scripting support, but it doesn't seem to actually run the scripts on boot. And it may not be running them at all.
Click to expand...

Ah alright well I'll be sure to try out 2.0.9 - - And understandable I've read that troubles regarding the screenshot and search button functions are also pain, no worries, just hope eventually all works 100%. :)
 
DraeHD said:
Ah alright well I'll be sure to try out 2.0.9 - - And understandable I've read that troubles regarding the screenshot and search button functions are also pain, no worries, just hope eventually all works 100%. :)
Click to expand...

Yep. If only the phone were actually running the scripts like we want it to, screenshot should work. It has everything it needs to work, as far as I can tell, aside from the fact that it's not being run. And I'm aware of Smanager, for anyone wondering, but the problem is getting them to install on ROM install, and run on boot (ergo, not manually but automatically), as opposed to them not running at all.
 
Well, I tried a few more things in the little bit of free time I had today.

I thought maybe one of the scripts might have been failing and somehow causing the ones after it not to run, so I deleted everything but the SD fix script in init.d and powered my phone off and back on.

Still nothing. Although I did find a problem in one of the scripts.

13citbun is missing fi on its last if statement. There also seems to be a stray "s" after the semicolon on the line inside of that if statement.
 
Swagroid said:
Also which android/cwm thing do I choose in the update.zip maker? I am running the v5.0.8 of the cwm
Click to expand...

I believe that's the version included in the guide. And if you mean the update.zip maker in TiB, go to Batch Mode and scroll down to the Recovery Mode category. The only entry should be "Create 'update.zip' from app+data backups". Use that one.

ASJ80 said:
Well, I tried a few more things in the little bit of free time I had today.

I thought maybe one of the scripts might have been failing and somehow causing the ones after it not to run, so I deleted everything but the SD fix script in init.d and powered my phone off and back on.

Still nothing. Although I did find a problem in one of the scripts.

13citbun is missing fi on its last if statement. There also seems to be a stray "s" after the semicolon on the line inside of that if statement.
Click to expand...

I looked at 97loopy_smoothness_tweak and cleaned it up some prior to the 2.0.9 test build. Now I have 13citbun cleaned up as well. Thank you.

At least now we know that the scripts aren't causing the initial issue of them not running. So we can cross that potential causality off the list. Now it's on to figure out why they're not even being started in the first place.

I appreciate the feedback and the testing, though, thank you.

EDIT: I've redone the init.d support and I'm going to test something out, be back within a half hour with the results, provided I don't get distracted by Game Grumps, ACR, and Dr. Pepper.

EDIT: No dice. But, thankfully, permissions are set correctly after rewriting the installer a bit - so at least that's taking place. So, we know it's not a permissions issue, nor a scripting error nullifying the scripts that proceed it. I could be reading it wrong, but on XDA it looks like init.d support requires the install-recovery.sh file, which doesn't make sense because having that file gets rid of CWM, which in effect eliminates the ability to have a custom ROM, which is exactly what we're building here and trying to make init.d support work for it via install alone. So that's a confusing paradox of nonsense. Here's the current build.
 
ASJ80 said:
I tried putting the install-recovery.sh back and editing it to only log.

That didn't work either.
Click to expand...

Then, from what I've read, that leaves two candidates remaining: the kernel, or the actual init.d support (the files that give the phone the init.d support) itself. Unless you've got any other candidates in mind.

EDIT: Also, for anyone who has seen the features list in the OP, if you noticed something about the/a "hosts" file - it means you won't have ads, or that you'll have fewer ads, while browsing the interwebs looking for pictures of kittens.
 
I can't think of anything else to try at the moment.

Hopefully I can find time when I get some time off work in a few weeks to get much more involved in doing things on this phone.
 
Also like to point out how incredibly blazing fast my phone charges with this ROM. I went from 23 to 100% in less than an hour.
 
OptimusV123 said:
Also like to point out how incredibly blazing fast my phone charges with this ROM. I went from 23 to 100% in less than an hour.
Click to expand...

Yep. That's one of my favorite parts is being able to do that in under an hour, and get up to 52 hours of life from it. Talk about efficiency, man. :D

Now if only I could that with regard to charging my own batteries...
 
Updated to 2.0.8 or the latest build rather, and I seem to be missing my camera, camcorder, and clock shortcuts / functions. I checked widgets and the like looking for them but they are not there. Curious as to where they went.
 
DraeHD said:
Updated to 2.0.8 or the latest build rather, and I seem to be missing my camera, camcorder, and clock shortcuts / functions. I checked widgets and the like looking for them but they are not there. Curious as to where they went.
Click to expand...

Try the download in the OP from SendSpace, and be sure to download via a computer or, if through your phone, using any browser other than what came with the phone. The apps required are there, and it could be a compression issue. I'll redownload Aeneas and ICS Elite and see what I can do if the problem persists (but other have reported that this isn't the case, so who knows, we'll find out soon).
 
You must log in or register to reply here.
Back
Top Bottom