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
Related
WHAT I HAVE DONE:
Backuped my rom with 3.0.0.5 to mess up with my rom.
Replaced framework-res.apk to get some new icons.
New framework-res.apk crashed my phone.
Tried to restore backup with 3.0.0.5.
Find myself stucked at "HTC".
Tried to flash MIUI rom from official MIUI website, MD5 checked.
Still stucked.
Went back to recovery 2.5.1.3.
Tried to restore backup created by 3.0.0.5.
Everything is OK now.
ORIGINAL PROBLEM:
Under 3.0.0.5 Backup restore failed+Flash MIUI ROM failed+HBOOT OK+Tested 13 times!!!!
symptom: Stuck at "HTC"
Went back to 2.5.1.3 and Flash MIUI ROM OK.
Now trying to restore backup created by 3.0.0.5...
Hope no more bricked DHD....
Want more discuss...
This recovery come with CWM Rom Manager 3.0.0.7 following recovery flash from Internet.
MD5: 5E457EDCC2CC8AF60E7B8EB10E1BBF8A
UPDATE: My DHD alive again...
Anybody would like to give it a try may follow this:
Make sure you are using version 3.0.0.5.
Backup your current rom (Make sure you have enough rom on your TF card, there won't be an warning if you failed because of lack of disk space!!! 2GB free recommend). (The backup function seemed OK...)
Mess your system up. (Delete some important files such like framework-res.apk...)
restore backup...
Here I get stucked at "HTC" (AKA first boot screen, defined by manufactor.)
RESTORING:
Boot into HBOOT, then fastboot, flash CWM Recovery 2.5.1.3. (Attached)
restore....
It's alive now...
Don´t be so paranoic...
It depends if the Rom is made for CWM 3.0.0.5. If not its not working...
And of course u can´t restore a backup with 3.0.0.5 which was done with CWM 2.5.1.3
Are you certain of this?
I need the devs and Senior Members opinion's please.
Kelthizar said:
Don´t be so paranoic...
It depends if the Rom is made for CWM 3.0.0.5. If not its not working...
And of course u can´t restore a backup with 3.0.0.5 which was done with CWM 2.5.1.13
Click to expand...
Click to collapse
I don't think recovery have anything to do with my rom. According to my 3 years android messing up history.
On the other hand, if that's true, there should be an warning when I flash my recovery through CWM Rom Manager.
CWM 3.x is fine. Been flashing roms with it since january (or december). A lot of people actually.
Edit: recovery has to do with the roms. Cwm 3 requires the updater script(edify). Also, cwm 3.0.0.5 from rom manager works fine for backup/restore. If you flashed it on your own before it was made available through rom manager, then its probably the test version which had probs restoring.
Sent from my Desire HD using Tapatalk
M_T_M said:
Are you certain of this?
I need the devs and Senior Members opinion's please.
Click to expand...
Click to collapse
The recovery works fine. Some people are just not aware that CWM 2 backups are not compatible with CWM 3 backups, and vice versa. There is also another compatibility problem, zips intended for CWM 2 do not work with CWM 3.
So there is no real issue with CWM, just some compatibility problems, and those can not / will not be fixed. It is the way software evolves..
jkoljo said:
The recovery works fine. Some people are just not aware that CWM 2 backups are not compatible with CWM 3 backups, and vice versa. There is also another compatibility problem, zips intended for CWM 2 do not work with CWM 3.
So there is no real issue with CWM, just some compatibility problems, and those can not / will not be fixed. It is the way software evolves..
Click to expand...
Click to collapse
Restored my backup created by 3.0.0.5 using 2.5.1.3, strange result according to your opinion...
It also depends on the ROM and it's filesystem, but the rule of thumb is, don't even try it.
Kelthizar said:
Don´t be so paranoic...
It depends if the Rom is made for CWM 3.0.0.5. If not its not working...
And of course u can´t restore a backup with 3.0.0.5 which was done with CWM 2.5.1.3
Click to expand...
Click to collapse
phunkycow said:
CWM 3.x is fine. Been flashing roms with it since january (or december). A lot of people actually.
Edit: recovery has to do with the roms. Cwm 3 requires the updater script(edify). Also, cwm 3.0.0.5 from rom manager works fine for backup/restore. If you flashed it on your own before it was made available through rom manager, then its probably the test version which had probs restoring.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
jkoljo said:
The recovery works fine. Some people are just not aware that CWM 2 backups are not compatible with CWM 3 backups, and vice versa. There is also another compatibility problem, zips intended for CWM 2 do not work with CWM 3.
So there is no real issue with CWM, just some compatibility problems, and those can not / will not be fixed. It is the way software evolves..
Click to expand...
Click to collapse
Post updated, a little bit long to read it through... but please...
My "ROM" is referring to the current system+user data+whatever else inside my nand, not the one in my update.zip. If you would like to know.
Once I learned recovery backup rom exactly the way it is, just like what Norton Ghost do to your hard disk, so if backup and restore not working, the files must be broken. Otherwise it's the recovery's fault.
Hello. i am new to the android family
i have a nexus s GT-9020T
i have rooted my phone but without setting the clockworkmod reovery.
today i was playing with the rom manager and downloaded one of the rom from the list. after installation i was unable to start the phone only seeing the google logo with the unlock logo.
i went back into the recovery by typing flash recovery recovery.img etc.
run a restore and restart the phone but still not work
my nexus s is 2.3.4 by the way.
please assist
What "restore" did you run?
Go here: http://forum.xda-developers.com/showthread.php?t=1056062
And download the full rom:
Model: i9020T
Full Rom: GRJ22, KD1
That'll revert your Nexus S to the latest completely stock 2.3.4
Then you can flash recovery again and go back to clockwork mod and go flash another rom or whatever.
Remember when you're flashing a new rom you need to wipe data and cache and dalvik cache.
i run an restore from the backup that i made before installing the new rom using clockwork mod recovery, its part of the option when installing the rom using the rom manager * click box - backup * etc something like that
sheunghko said:
i run an restore from the backup that i made before installing the new rom using clockwork mod recovery, its part of the option when installing the rom using the rom manager * click box - backup * etc something like that
Click to expand...
Click to collapse
Next time don't use Rom Manager to make backups or flash roms. It's stupid and can get you issues like you're having.
Anyways, try wiping data and cache then restoring the backup, do it in Clockwork Recovery.
Let it boot, first boot always takes a while, 5-10 minutes. If you see the boot animation freeze, stop and restart, then yeah it's screwed up, otherwise, just let it is.
If still not working from your backup, do what I said in previous reply, just restore to stock 2.3.4 then re flash clockwork mod and start over with the rom you want to flash.
thank your nxt. i have found the real problem. it was not my backup problem or the rom that u provided. it was the version of my clockwork mod recovery. i was using an 2.x.x.x to restore the phone which is why it doesn't work. everything work fine now after i flashed with an 3.x.x.x and restore the phone. one question thou, where can i always find the newest clockwork mod recovery release ? thank you very much
sheunghko said:
thank your nxt. i have found the real problem. it was not my backup problem or the rom that u provided. it was the version of my clockwork mod recovery. i was using an 2.x.x.x to restore the phone which is why it doesn't work. everything work fine now after i flashed with an 3.x.x.x and restore the phone. one question thou, where can i always find the newest clockwork mod recovery release ? thank you very much
Click to expand...
Click to collapse
http://mirrorbrain.cyanogenmod.com/cm/recoveries/
Or just use ROM Manager to get the latest.
That's the only thing I use ROM Manager for... getting the latest Recovery.
thanks again nxt. if you don't mind really ...i have one more question. i know the phone intend to uninstall clockwork mod recovery once its restarted. i know there is command type into the cmd to avoid the phone uninstall the clockworkmod reovery and make it permanent in another word. I didn't run those command when i root my phone because i don't know if its good to make it permanent like.... hmmm like if there will be a 2.3.5 coming next month..just saying ok... with a permanent unofficial recovery will cause a problem?
sheunghko said:
thanks again nxt. if you don't mind really ...i have one more question. i know the phone intend to uninstall clockwork mod recovery once its restarted. i know there is command type into the cmd to avoid the phone uninstall the clockworkmod reovery and make it permanent in another word. I didn't run those command when i root my phone because i don't know if its good to make it permanent like.... hmmm like if there will be a 2.3.5 coming next month..just saying ok... with a permanent unofficial recovery will cause a problem?
Click to expand...
Click to collapse
Are you running custom ROM? If you are, it's already made to not revert back to stock recovery. If you leave it stock recovery you'll get notifications for firmware updates by Google, but remember that applying those to a rooted phone might screw things up too.
the blue one is stock recovery right?
sheunghko said:
the blue one is stock recovery right?
Click to expand...
Click to collapse
Don't remember. It should only have like 3-4 options.
thanks again nxt. no i am not running an custom rom. i mean not yet. i planed to try one from the rom manager download section then my phone couldn't start after installation and now i have restored my phone from my backup using the clockwork mod recovery 3.x.x.x.
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
After the OTA 3.2.1 update, CWM Recovery would just not install. After flashing the CWM recovery image on stock 3.2.1 and rebooting into recovery, I get the android guy with the exclamation mark. I saw another person in the CWM thread having the same issue.
I did flash CWM before on HC 3.2 successfully, but for some reason it is not working after the last OTA update.
Any thoughts ?
Any luck on this? I'm trying to root my Xoom 3.2.1 and have no idea what to do and looks like the one click tool has been removed...any direction is better than no direction ;-)
Thanks!!
Faslane
I had this same issue yesterday.
Use adb and fastboot to manually install clockwork again...and then if you need to root you can use one click root.
I would give you the code for fastboot command but I'm not home.
Sent from my ADR6350 using xda premium
Do not use one click root-you'll brick it.
Use the Univetsal Xoom Root.
http://forum.xda-developers.com/showthread.php?t=1242241
okantomi said:
Do not use one click root-you'll brick it.
Use the Univetsal Xoom Root.
http://forum.xda-developers.com/showthread.php?t=1242241
Click to expand...
Click to collapse
Thank you okantomi that's what I meant.
Sent from my ADR6350 using xda premium
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Yazan76 said:
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Click to expand...
Click to collapse
That is exactly right.
Yazan76 said:
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Click to expand...
Click to collapse
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
texasez said:
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
Click to expand...
Click to collapse
these instructions seem to work
http://forum.xda-developers.com/showpost.php?p=17832798&postcount=78
texasez said:
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
Click to expand...
Click to collapse
Yes. What I did is backup everything, flash back to stock, wait for my device to download and install the 3.2.1 update, and finally flash the recovery, root my device, and install the tachi kernel. Restored all my applications after making sure that everything is fine.
I know it looks like a long a process but google market applications restore saved me a lot of time.
Yazan76 said:
Yes. What I did is backup everything, flash back to stock, wait for my device to download and install the 3.2.1 update, and finally flash the recovery, root my device, and install the tachi kernel. Restored all my applications after making sure that everything is fine.
I know it looks like a long a process but google market applications restore saved me a lot of time.
Click to expand...
Click to collapse
To save even more time and get back your app data, first back up aps and data in Titanium Backup and make sure the backup is on your external sdcard, just to be safe. Then, after wiping, and once you have rebooted, reinstall TB and then run a batch restore of missing apps and data. It is much faster and better than letting google restore the apps.
.
Yesterday just rooted my xoom but now i have a problem when i try to flash something or do something in recovery doesnt work it say cant open sd or cant mount sd any help
okantomi said:
To save even more time and get back your app data, first back up aps and data in Titanium Backup and make sure the backup is on your external sdcard, just to be safe. Then, after wiping, and once you have rebooted, reinstall TB and then run a batch restore of missing apps and data. It is much faster and better than letting google restore the apps.
Click to expand...
Click to collapse
Even simpler... fastboot flash just boot, system, and recovery stock images. Leave userdata alone. Allow the update. Don't worry about letting it fully boot.. let it.. no harm.. but no root.
Then flash CWM (using fastboot).. boot to recovery.. CWM univ root. Good to go. Or CWM a different kernel
CARLITOZ18 said:
Yesterday just rooted my xoom but now i have a problem when i try to flash something or do something in recovery doesnt work it say cant open sd or cant mount sd any help
Click to expand...
Click to collapse
You need to have an exernal sdcard for the recovery images to work.
Chipster0 said:
... Fastboot flash just boot, system, and recovery stock images.
Click to expand...
Click to collapse
Do you (or anyone else) have any (US VZ 3G MZ600) stock images later than HMJ37? Moto stopped carrying at HRI66 for some reason
hey
I got galaxy s4 i9500 running android 5.0.1 original rom, cwm recovery, I tried flashing a new system ui without backing up the stock one.
now as the phone starts up an error shows up: system ui stopped. I dont want to wipe my phone, please make me a flashable zip for the original system ui.
thank you guys.
Please... some body help....
rezabx said:
hey
I got galaxy s4 i9500 running android 5.0.1 original rom, cwm recovery, I tried flashing a new system ui without backing up the stock one.
now as the phone starts up an error shows up: system ui stopped. I dont want to wipe my phone, please make me a flashable zip for the original system ui.
thank you guys.
Click to expand...
Click to collapse
please hep me quickly
Bumping threads under 24hrs old is against xda rules
Download a stock ROM from sammobile and flash it using Odin. Odin doesn't wipe anything so your data will remain intact.
Strephon Alkhalikoi said:
Download a stock ROM from sammobile and flash it using Odin. Odin doesn't wipe anything so your data will remain intact.
Click to expand...
Click to collapse
is there any way to take out the system ui from stock rom and make a flashable zip?
actualy I made a flashable zip of my rom with cwm, might it work If I flash this zip of stock rom ?
rezabx said:
Is there any way to take out the system ui from stock rom and make a flashable zip?
Click to expand...
Click to collapse
Sure, but you would have to get the right SystemUI file, make sure the commands are correct, and then hope that it works. Downloading the stock ROM from sammobile is easier since you simply install it using Odin, and you're done. Besides, you should ALWAYS have a copy of your stock ROM on your hard drive, just for these types of problems.
rezabx said:
Actually I made a flashable zip of my rom with cwm, might it work If I flash this zip of stock rom ?
Click to expand...
Click to collapse
Well first of all, you should be using TWRP as Clockworkmod is no longer maintained and cannot handle some ROMs. Secondly, TWRP allows you to make the backups on the MicroSD card, unlike Clockworkmod. That said, how did you make a flashable zip of your ROM using Clockworkmod? That's not a feature of any recovery I know of. Making a nandroid backup, on the other hand, IS a feature of custom recoveries, and if you did make a nandroid backup, you simply restore that and you're good to go.
thanks bro
Strephon Alkhalikoi said:
Sure, but you would have to get the right SystemUI file, make sure the commands are correct, and then hope that it works. Downloading the stock ROM from sammobile is easier since you simply install it using Odin, and you're done. Besides, you should ALWAYS have a copy of your stock ROM on your hard drive, just for these types of problems.
Well first of all, you should be using TWRP as Clockworkmod is no longer maintained and cannot handle some ROMs. Secondly, TWRP allows you to make the backups on the MicroSD card, unlike Clockworkmod. That said, how did you make a flashable zip of your ROM using Clockworkmod? That's not a feature of any recovery I know of. Making a nandroid backup, on the other hand, IS a feature of custom recoveries, and if you did make a nandroid backup, you simply restore that and you're good to go.
Click to expand...
Click to collapse
its a philz recovery, based on cwm i guess