Database Users

Rooted my GF's Fascinate, Need Help Nandroiding

I just rooted my girlfriend's year old fascinate that was bone stock from day 1. In CWM I am unable to make a nandroid (I get an error). I've heard I need a modded stock kernel in order to successfully make a backup in CWM 3.x or something along those lines.
I looked in the developer forum under the sticky with the list of everything, but it only shows three or so kernels (none of which hint at stock).
I have a Thunderbolt and before that a Droid 2 so I know a lot about rooting and flashing with those two devices, but I am new to the Fascinate. I messed around a bit with Odin when I rooted the phone, but I'm still learning.
Any help is greatly appreciated.

Older recoveries supported amend scripting (2.x.x) while newer ones support edify scripting (3.x.x)...depending on which rom your running it may cause problems with backups and restores if you don't have the right recovery...unless you plan on going to an Mtd build (cm7, Miui, ect) I would recommend using the (2.5.1) recovery also called the 3/30 fix all recovery because this version supports both amend and edify scripting..so you make a nandroid with out issues....if you can get to recovery still I would install this zip and then select reboot recovery...it will bring you to the 3/30 fix all recovery where you should be able to backup and restore your nandroid...link to follow shortly...
Scroll down in the first page to the .zip file, download and continue with the steps I listed...I know its confusing at first mainly because development has happens rather quickly which is a good thing! its just a lot to catch up on!
http://forum.xda-developers.com/showthread.php?t=942021
Sent from my SCH-I500 using XDA App

What would you recommend if my plan was to install MIUI or OMFGB?
I'm deciding between those two because I use OMFGB on my Thunderbolt all the time, but MIUI is very good for my girlfriend I think because it's very straight forward and simplistic.

http://forum.xda-developers.com/showthread.php?t=1124391
Its not hard to get in to these roms, but you must be sure if you have problems or want to go to anything non Mtd you will have to Odin an official VZW tar and pit file to repartition before going to any non Mtd rom
http://forum.xda-developers.com/showthread.php?t=1124391
Sent from my SCH-I500 using XDA App

So basically:
1. Flash the CWM you posted in your original reply
2. Nandroid her current stock setup
3. Flash MIUI
4. If I ever want to return to stock or a non-mtd rom I have to do what's posted in your second reply?
If all that is correct please let me know. Also lets say she doesn't like MIUI, can I simply flash that nandroid or will I have to do what's posted in the second reply?

When I try to flash that older CWM in CWM I get this message:
http://i.imgur.com/3QiwQ.jpg

want a droid said:
So basically:
1. Flash the CWM you posted in your original reply
2. Nandroid her current stock setup
3. Flash MIUI
4. If I ever want to return to stock or a non-mtd rom I have to do what's posted in your second reply?
If all that is correct please let me know. Also lets say she doesn't like MIUI, can I simply flash that nandroid or will I have to do what's posted in the second reply?
Click to expand...
Click to collapse
Yes you will have to do what's in the second reply.
You have it all correct, if you nandroid her current stock setup you can only restore it on a non Mtd build you would have to do what I linked to in the second post to use a vzw rom with pit file to repartition...boot fully, flash recovery then you could restore her stock nandroid..for example you get her on Miui you can only do a nandroid with the recovery that comes with it...I think its a 4.x.x recovery...trying to restore the stock nandroid before repartitioning back to stock will cause problems...so basically you only want to restore a nandroid on the same build (Mtd to Mtd nandroid, or ext4/rfs to ext4/rfs nandroid) and if all else fails and you run into big problems, doing the VZW restore (although can be a lengthy process) will get the phone back running to start over!
Sent from my SCH-I500 using XDA App

Did you see my reply before this? I was unable to get CWM 2.x to flash so I'm still on CWM 3.x.

want a droid said:
Did you see my reply before this? I was unable to get CWM 2.x to flash so I'm still on CWM 3.x.
Click to expand...
Click to collapse
I did see it after I replied, is her phone on ed05? I'm surprised that neither the 3/30 fix all or 3.x.x is working
Edit after looking at the pick again you're using times infinity's recovery....you would need to Odin the 3/30 fix all recovery and immediately three finger boot into recovery without letting the phone boot or if you installed the 3/30 fix all via .zip file, you need to choose reboot recovery to enter the fix all one, it should be 2.5.1 I believe
Sent from my SCH-I500 using XDA App

Here's a picture of her phone info:
http://i.imgur.com/rs1Jd.jpg
And as you can tell from the other photo, both making a backup and flashing the CWM 2.x doesn't work.
Trying a backup results in: "Error while backing up boot image!"
Trying to flash CWM 2.x results in that long information message.

That sucks man i'm sorry I've never been on ed05 so I don't know if that why your having problems my suggestion...back up all her contacts by exporting them to sd card, download titanium backup its free in the market, backup all of her apps and screw the nandroid, flash what you want, restore her apps with titanium, but do not restore data, restore get contacts and then boot into the recovery that comes with the rom/kernel and then do a nandroid and that WILL work..again sorry for the trouble, just trying to help.
Sent from my SCH-I500 using XDA App

I appreciate all your help. I'll let you know how it goes.

ed05 is not the problem...You have to use cwm 2.5.1.x if your trying to nandroid backup a stock rom. This version of cwm works on all froyo roms and powerwashed gingerbread. After you make a nandroid with cwm2.5.1.x, then flash cwm4 and proceed to installing miui.
Read this link for flashing mtd based roms such as miui, cm7, vgb...etc
http://forum.xda-developers.com/showthread.php?t=1212239

That was my first reply to him...to use 2.5.1 but he said he still got errors? I don't have a clue what the problem is...he's said he's used ti's 3x.x, and the 3/30 fix all still with errors? confused?
Sent from my SCH-I500 using XDA App

droidstyle said:
ed05 is not the problem...You have to use cwm 2.5.1.x if your trying to nandroid backup a stock rom. This version of cwm works on all froyo roms and powerwashed gingerbread. After you make a nandroid with cwm2.5.1.x, then flash cwm4 and proceed to installing miui.
Read this link for flashing mtd based roms such as miui, cm7, vgb...etc
http://forum.xda-developers.com/showthread.php?t=1212239
Click to expand...
Click to collapse
I guess you skipped the entire thread, but we already went through all that.

want a droid said:
I guess you skipped the entire thread, but we already went through all that.
Click to expand...
Click to collapse
I think you skipped a step... Are you flashin cwm via the PDA function in ODIN?
If not you need to:
ODIN the cwmAll.tar here: http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1238070&v=1&libid=1316306736482&out=http%3A%2F%2Fwww.mediafire.com%2F%3F6x5utoca59et7o9&title=%5BGUIDE%5D%20Installing%20a%20rom%2F%20cwm%20recovery%2F%20or%20going%20back%20to%20stock%20for%20NEWBIES!%20-%20xda-developers&txt=http%3A%2F%2Fwww.mediafire.com%2F%3F6x5utoca59et7o9&jsonp=vglnk_jsonp_13163071702031
make a nandroid back up of the stock rom.
go back to odin and flash the jt's cwm4
boot into recovery
wipe data, cache, dalvik
install miui.zipfrom sd card
Follow the rest of the directions in the link I provided

+1 there ya go. Beat me to it.
Plus, I wouldn't even worry about backing up your stock ROM. Just flash the full official package. This will wipe your slate clean if you run into problems. Restoring nandroid backups leads to glitches eventually from what I've seen.
Sorry, I didn't see there was a second page here...I'm a bum.

want a droid said:
I guess you skipped the entire thread, but we already went through all that.
Click to expand...
Click to collapse
Should probably try not being a **** when you're begging for help from people.
Sent from my SCH-I500 using XDA App

Personally, I thought his reply was honest and effective. I commend him on his frankness, and respect him for his boldness.

grenade01 said:
Personally, I thought his reply was honest and effective. I commend him on his frankness, and respect him for his boldness.
Click to expand...
Click to collapse
Really? Snide, snarky comments are respectable? At the very least, they shouldn't be coming from the person asking for help.
Sent from my SCH-I500 using XDA App

[Q] Problems with stock rooted rom when flashed from recovery.

Let me give you the timeline. A few days ago I rooted the device using the method outlined in this video. I verified my root status with Root Checker and my device was indeed successfully rooted. I installed BusyBox (basic) and TitaniumBackup Pro. Made a backup of my user apps+data to the external SD. I then downloaded Goomanager and used it to install the latest version of TWRP.
All of this was successful. I went into TWRP and created a NAND backup. I backed up: Boot, System, and Data. I did not back up EFS, Preload, Cache, or Recovery.
I performed a wipe and format of user data. Flashed to SlimBean, had some issues. Wiped. Flashed CM10.1. Again, some issues. I decided I'm going to wait a while for these roms to stabilize a bit before I try using any of them on a regular basis. I wiped and restored my original NAND backup of my stock rooted ROM. The restore appeared to go fine. I don't know if this will have anything to do with anything but I went ahead and ran a PRL and Profile update. The device was functioning okay until...
I noticed that the time was off. The lockscreen time was correct but the time in the upper right status bar was stuck at about an hour before. I decided I'd just try restarting the device to see if that fixed anything. Well when I did it wouldn't boot. I'd get stuck on the first Samsung Galaxy S4 logo screen. Took the battery out, waited, put it back in, restarted. Still... stuck on the logo screen. I tried booting into recovery (Vol. Up + Power). The black SGS4 logo would come up with a tiny blue notification in the upper left corner (Recovery Boot). Then the device would restart and get stuck at the SGS4 logo screen again.
Eventually I was able to get it to boot to TWRP (maybe I was just holding the power button too long?)
I wiped. It failed. I tried again. It worked. I recovered my CM10.1 setup and it's been working "okay" on CM10.1 ever since.
I want to get back to my stock rooted rom but I want to understand what happened first.

Anyone? Please?

Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
What version of TWRP were you on? If it was 2.5.0.3 then there's your culprit. That version of TWRP is known to have issues. You need to flash version 2.5.0.2 found here.......http://forum.xda-developers.com/showthread.php?t=2277480. Scroll down to install Alternate recovery and download the 2.5.0.2 .img file.
Once you've downloaded the file, go to your Goo Manager folder and delete the file there. Then paste the file you downloaded from the above link into that same folder. After that, open Goo Manager and go to Install Recovery Script. It should see the file you have in your folder and then download it from their server. Make SURE it says you are downloading 2.5.0.2. Once Goo does its thing, reboot into Recovery and make sure you're running the 2.5.0.2 version of TWRP. Now you can flash all you want because it will function properly. I would first download a stock rom and clear out any skeletons in the closet. Then go into TWRP and wipe EVERYTHING. This includes data, dalvik cache, cache, system and then factory reset as well 3 times each. MAKE SURE you don't delete the internal or external sd cards. Flash the stock rom, set it up how you wish, make a nand of that file( Include EFS and Preload because it can't hurt to be safe) and then flash whatever you like. You should be good to go.
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
Another question I have is what version of software/firmware are you on? Go to Settings/More/About Phone and check what your software and baseband versions are? If its MDC, then rooting via MotoChopper was a good method to use. If it says MDL, that could also be the reason why the phone was acting so quirky. There is a new method to rooting if you are on MDL and it's also found in Mudavo's thread found here...http://forum.xda-developers.com/showthread.php?t=2277480

For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.

Stu_Gots said:
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Click to expand...
Click to collapse
Honestly, at this point, you need to unroot and reroot again using the method in Mudavo's post. You used the wrong method to root with motochopper. Motochopper was only for the MDC version. That could be why you are having the issues that you are. That's all I can suggest at this point. Start with a clean slate and try it again. Trust me you aren't the only one to do this. I've done it a few times myself. It sucks but at least you know you did everything right. You're going to have to flash a stock MDC rom that came shipped with the phone via Odin. Then take the OTA to update your phone to MDL and then just follow Mudavo's post to root the proper way when you're on the MDL version.

What about the TWRP recovery I have installed? Am I going to have to deal with that in some way?
What are the advantages of Odin over TWRP? I'm not trying to question your judgment btw. I'm legit curious because I've only ever used TWRP to
Flash roms.
Sorry for all the dumb questions.
Btw . While I was waiting for your reply I tried trouble shooting a bit myself. To see if I could fix my own problem. I found a thread with MDL stock rooted and a bunch of firmware and kernel files. I flashed to it in TWRP and it's working reasonably well so far. I'm still dtf for other methods if mine is somehow flawed.

My method didn't work. When I restarted from TWRP (after no other issues) the phone for stuck.
The phone was restarted several times and booted fine. It wasn't until I restarted into TWRP then and then back into normal boot that I had issues
this time. So I'm going to do what you suggested. I just have a couple questions.
If my rom/recovery is corrupted how do I fix my problem. I would need a working rom AND recovery to flash stock rom. I'm not sure where to start since everything is all messed up.
Thank you so much for your help. You're the best!

You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261

gharlane00 said:
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
Click to expand...
Click to collapse
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!

Stu_Gots said:
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Click to expand...
Click to collapse
download Odin 1.85 or 3.07 on your PC don't use mobile version for something like this
Sent from my SPH-L720 using xda premium

Do I need to flash the stock kernal too? Will this eliminate my TWRP recovery installation as well?

If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium

devoureddreams said:
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Alright... so another problem. I need the latest Samsung USB driver right? Unfortunately...
1.5.25.0 as linked to in this thread cannot be downloaded because uploaded.com or whatever says I've exceeded my allowance. Trouble is... I haven't downloaded anything from them ever. I have this problem all the time because of my ISP (Satellite Internet).
Is there a rehost? Do these drivers not install themselves automatically when the device is plugged into the PC?

http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Sent from my SPH-L720 using xda premium

I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.

Stu_Gots said:
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Click to expand...
Click to collapse
Follow this tutorial here
http://www.sxtpdevelopers.com/showthread.php?p=2599
Sent from my SPH-L720 using xda premium

Alright guys. I got it done a while back. Phone is back to normal stock.
Perusing the internet I found this video.
http://www.youtube.com/watch?v=s_hXUJ-u-cw
As it happens I linked to the wrong video in my OP. The method in that video is exactly what I did to root in the first place. The proper way. I installed TWRP from GooManager.
So if I rooted correctly and I installed TWRP correctly what do you suppose caused my problem? I want to root and install custom recovery again!

If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?

Stu_Gots said:
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Click to expand...
Click to collapse
thats all there is to it.

sprint s4 get stuck on samsung logo on 2nd boot

not sure what is going on but i have twrp recovery and running the triforce rom at the moment. though every rom has done same thing that i have tried. i swap batteries alot rather then charge the phone so this is a pain since the only fix i have found is reboot to recovery which also sometimes freezes on the twrp logo and do complete wipe. then it will boot up fine. but of course everything is gone.

excessive81 said:
not sure what is going on but i have twrp recovery and running the triforce rom at the moment. though every rom has done same thing that i have tried. i swap batteries alot rather then charge the phone so this is a pain since the only fix i have found is reboot to recovery which also sometimes freezes on the twrp logo and do complete wipe. then it will boot up fine. but of course everything is gone.
Click to expand...
Click to collapse
Which twrp recovery you using?
Sent from my SPH-L720 using xda app-developers app

openrecovery-twrp-2.6.0.0-jfltespr

excessive81 said:
openrecovery-twrp-2.6.0.0-jfltespr
Click to expand...
Click to collapse
Twrp version 2.6.0.0 seems to be buggy either try 2.5.0.2 or 2.6.0.3 they seem to be working for people the most
Sent from my SPH-L720 using xda app-developers app

excessive81 said:
not sure what is going on but i have twrp recovery and running the triforce rom at the moment. though every rom has done same thing that i have tried. i swap batteries alot rather then charge the phone so this is a pain since the only fix i have found is reboot to recovery which also sometimes freezes on the twrp logo and do complete wipe. then it will boot up fine. but of course everything is gone.
Click to expand...
Click to collapse
This has been a problem for me as well. I've used TWRP 2.5.0.2 and the 2.6.x.x versions with the same issue. Typically only happens after flashing an AOSP based ROM then restoring a TW nandroid. For me, one of the partitions gets corrupted, I've had /data and /system both get borked. Formatting in TWRP and CWM does nothing to fix the problem. My only solution so far has been to ODIN crawjs rooted stock MF9 .tar and factory reset in stock recovery. This seems to restore the partition. After that, reboot into download again and flash TWRP 2.5.0.2 .tar. Only then can I successfully restore a previous Nandroid.
It's weird, the first boot always works. Haven't heard a definitive answer to why this happens. I may experiment flashing an AOSP with CWM and see if the same issue persists.

smizak said:
This has been a problem for me as well. I've used TWRP 2.5.0.2 and the 2.6.x.x versions with the same issue. Typically only happens after flashing an AOSP based ROM then restoring a TW nandroid. For me, one of the partitions gets corrupted, I've had /data and /system both get borked. Formatting in TWRP and CWM does nothing to fix the problem. My only solution so far has been to ODIN crawjs rooted stock MF9 .tar and factory reset in stock recovery. This seems to restore the partition. After that, reboot into download again and flash TWRP 2.5.0.2 .tar. Only then can I successfully restore a previous Nandroid.
It's weird, the first boot always works. Haven't heard a definitive answer to why this happens. I may experiment flashing an AOSP with CWM and see if the same issue persists.
Click to expand...
Click to collapse
the 2.6.3 worked thanks

excessive81 said:
the 2.6.3 worked thanks
Click to expand...
Click to collapse
That one still gets stuck on team win curtain,,, This one has been the best yet and I've flashed a ton with it :beer::thumbup:
http://www.androidfilehost.com/?fid=23159073880933366
Sent from my SPH-L720 using xda app-developers app

ParkerParker said:
That one still gets stuck on team win curtain,,, This one has been the best yet and I've flashed a ton with it :beer::thumbup:
http://www.androidfilehost.com/?fid=23159073880933366
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
that file for 2.6.3.1 is not a tar file how do you flash it?
also i dont have freezing issues anymore but now after rebooting sd card no seen/working. it is there you can see it in settings menu which says it is mounted but the apps i moved to it dont work and the music is gone. if i unmount the card i can not remount it.

excessive81 said:
that file for 2.6.3.1 is not a tar file how do you flash it?
also i dont have freezing issues anymore but now after rebooting sd card no seen/working. it is there you can see it in settings menu which says it is mounted but the apps i moved to it dont work and the music is gone. if i unmount the card i can not remount it.
Click to expand...
Click to collapse
stock recovery, factory reset. trust me.

excessive81 said:
that file for 2.6.3.1 is not a tar file how do you flash it?
also i dont have freezing issues anymore
Just give it some time you will have curtain hangs... If you flash a lot.. But onto the zip, just flash in recovery, done
Heres the twrp thread if you feel like a read, http://forum.xda-developers.com/showthread.php?t=2262999
Click to expand...
Click to collapse

TWRP being a noob and factory resetting my G2

Hey errbody, sorry if this has been asked somewhere already but it's hard to sift through the hundreds of pages of good questions! But I seem to have a slightly handicapped TWRP thing going on in that it successfully makes backups but upon restoring then when needed, it says failed and then factory resets my phone when I boot into system...Anybody getting this weird vibe?

I've never experienced that before. Are you using the correct TWRP for your phone? Have you tried CWM recovery? Use flashify and flash an older version of TWRP... you should not be having this issue.

I'm unable to restore from Nandroid backups either. No idea how to remedy the problem. This is the 5th phone I've successfully rooted and put a recovery on so I'm not a noob, just can't figure this one out. Have you found a solution yet?
Sent from my LG-D801 using xda app-developers app

andy10259 said:
I've never experienced that before. Are you using the correct TWRP for your phone? Have you tried CWM recovery? Use flashify and flash an older version of TWRP... you should not be having this issue.
Click to expand...
Click to collapse
Hey I've used flashify to flash the newest version of twrp, never tried cwm on the g2 saw twrp was the more reccomebd recov. No idea why its going down like this. I'm running pa 4 so don't I need to keep my new version of twrp?

Backups on Phillz Recovery

Im having 2 issues with phillys recovery n not sure wut im doin wrong. I did a backup and when I restored it gapps forceclosed and phone wouldnt let me do anything. Secondly ive tried doing he create custom rom. It flashs fine but wont pass bootloader s4 screen. Need help. Would love to be able to make a flashable rom with my ultra slim rom n possibly have my xposed tweets built in.
TeamBlaze

Got backup to work. But still unable to get custom rom aka update.zip to get past bootloader. Anyone kno how to fix this.
TeamBlaze

If you're talking about the update.zip made from Titanium, it is NOT a custom ROM.
It is simply a backup of your applications (and some settings) you can use to flash after flashing a ROM to 're-load' all your stuff.
If you get your current ROM configured the way you like it you can then create a nandroid to restore it later if that is what you want. And without any info on what version of Android you're on, what ROM you're on, or what version of the recovery you're on there is no way to tell you where to go from here.

leaderbuilder said:
If you're talking about the update.zip made from Titanium, it is NOT a custom ROM.
It is simply a backup of your applications (and some settings) you can use to flash after flashing a ROM to 're-load' all your stuff.
If you get your current ROM configured the way you like it you can then create a nandroid to restore it later if that is what you want. And without any info on what version of Android you're on, what ROM you're on, or what version of the recovery you're on there is no way to tell you where to go from here.
Click to expand...
Click to collapse
No. From philz touch recovery. In the custom backups you can selete create a custom rom from backup and I can't get tht to flash right after makin. Clean install n everything.
TeamBlaze

yotaking said:
No. From philz touch recovery. In the custom backups you can selete create a custom rom from backup and I can't get tht to flash right after makin. Clean install n everything.
TeamBlaze
Click to expand...
Click to collapse
Never tried that (make ROM from recovery in philz) myself.
I just make and restore loads of backups using Philz and TWRP. I consider a full backup (complete image(s) of all phone partitions) to be my ROM(s).
I would bet that with what you're doing that if, after you flash your custom made zip (and before rebooting) you stayed in recovery and then flashed (install zip) of the same recovery, rebooted back to recovery and flashed the kernel it may work.
Rebooting the recovery (or a battery pull) often clears out hangs.

Did you tried enabling se linux context from backup settings?
Sent from my GT-I9505 using xda app-developers app

do you have 4.3 compatability checked off?

same issue
yotaking said:
Im having 2 issues with phillys recovery n not sure wut im doin wrong. I did a backup and when I restored it gapps forceclosed and phone wouldnt let me do anything. Secondly ive tried doing he create custom rom. It flashs fine but wont pass bootloader s4 screen. Need help. Would love to be able to make a flashable rom with my ultra slim rom n possibly have my xposed tweets built in.
TeamBlaze
Click to expand...
Click to collapse
I had similair issues with philz. idid a very improtnact nandroid backup and when iwent ot restore it didnt work. I definately like TWRp the best. Best UI and never any issues for me.

androidaddicted said:
I had similair issues with philz. idid a very improtnact nandroid backup and when iwent ot restore it didnt work. I definately like TWRp the best. Best UI and never any issues for me.
Click to expand...
Click to collapse
I like twrp as well but dnt wrk on 4.3
TeamBlaze

dewrust said:
do you have 4.3 compatability checked off?
Click to expand...
Click to collapse
Conito11 said:
Did you tried enabling se linux context from backup settings?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Imma look into these
TeamBlaze