Hello
I have jb 4.1 with safestrap.
I accidentaly updated SU binaries on the Stock rom. Now my root is gone, but I can flash roms just fine. I have old version safestrap where you cant install on stock rom(even roms that have root). But I want root on the stock rom.
I think I can Restore to it.
If any of you can post the safestrap Backup image of a clean rooted install of stock 4.1 that is rooted, backed up from the stock rom slot, I'd be very happy.
Thanks.
This has been solved, read last post.
I'll try modifying a backup of my own... can you guys tell me what version of SuperUser binary is good for root?
If you can post your system/xbin/su or system/bin/su file and have working root on 4.1, that'll help too.
Re: Can someone post a Safestrap 4.1 Backup
If you have a backup, why don't you flash that?
Sent from my phone.
---------- Post added at 05:37 PM ---------- Previous post was at 05:22 PM ----------
My backup has a modified build.Prop and probably a few extra apps added into the system/app folder
I don't mind uploading it, I just don't know the best site to upload it to.
Sent from my phone.
I dont have a backup, thats the problem. If you have a fast connect you can upload the whole, but only if you had it as stock_rom slot.
Looking for file share site.
https://www.wetransfer.com/
Try this and click the share button, then the link button. You dont need emails that way. Also it didnt work in firefox for me.
EDIT:
OK, he sent it, I'll try in a few.
EDIT 2:
IT WORKED!!!
so what youre saying is you flashed back ICS with safestrap?
can i get this ics rom?
aarons6 said:
so what youre saying is you flashed back ICS with safestrap?
can i get this ics rom?
Click to expand...
Click to collapse
No, I restored a rooted JB rom back because I lost it on stock JB rom.
He had an old version of safestrap that doesn't allow flashing on the stock, or safe, slot, so he was unable to simply flash a superuser zip.
But, by restoring a previously rooted safestrap system backup, root was regained.
Sent from my phone.
Is AT&T stock ROM image still available?
Markyzz said:
He had an old version of safestrap that doesn't allow flashing on the stock, or safe, slot, so he was unable to simply flash a superuser zip.
But, by restoring a previously rooted safestrap system backup, root was regained.
Sent from my phone.
Click to expand...
Click to collapse
Hi, saw this thread as a search result and while I think my issue is similar, I'm not sure, so if I need to post a new thread, I'd appreciate knowing that.
I have an Atrix HD with Batakang in slot 1 and of course the stock AT&T ROM in, well, the Stock slot. I have Safestrap 3.11. I wanted to unlock the phone for int'l use, and it simply would not give me the prompt to enter the unlock code (said "Invalid SIM" or something like that), so I left it with an AT&T dealer because the process should have been simple, but wasn't.
They couldn't do it either, but when I got the phone back, the entire 8GB ROM space was wiped! Batakang was gone, the Stock slot is empty, and unfortunately, the Safestrap backup I made of Stock (and left on the internal SD) was gone too!
I did have a Batakang backup which restored fine, I entered the unlock code OK in it (I assume that worked - there was no confirmation message), but still have an empty AT&T stock slot.
What ROM images I've found are not compatible with Safestrap, so what I'm looking for is either a Safestrap backup or a zip installer compatible with Safestrap, or any other suggestions appreciated! Thanks!
Related
I tried updating from the leaked 5.5.893 to this new 5.9.901 with no luck. Has anyone have any luck with this? If so how did you do it?
Throw it on the sd card, use stock recovery. What method did you use and what error are you getting?
I put it on the sd card. Tried from stock recovery and its failing at the verification. Tried to install as a zip.
Then I don't believe you're on 5.5.893. You're SURE you're not on 5.7.893? Cause if you're on 5.7.893 then you're stuck like the rest of us.
If you are on the leaked 5.5.893 and not the official OTA version, then it is possible that the checksums are different between the two versions and it fails the asserts in the updater-script.
The important thing to note is that the error messages are very specific and will tell you which file is failing. Then you can fix it, if at all possible, dependent on what was changed and how.
cellzealot said:
If you are on the leaked 5.5.893 and not the official OTA version, then it is possible that the checksums are different between the two versions and it fails the asserts in the updater-script.
The important thing to note is that the error messages are very specific and will tell you which file is failing. Then you can fix it, if at all possible, dependent on what was changed and how.
Click to expand...
Click to collapse
I thought someone checked the CRC's for the leaked vs OTA and they were identical?
Not sure if anyone has seen or tried this yet, but the error I get (running 5.7.893) regards two attributes in the build.prop file. Gonna try modding them to see if the update takes afterwards.
GeoMandell said:
Not sure if anyone has seen or tried this yet, but the error I get (running 5.7.893) regards two attributes in the build.prop file. Gonna try modding them to see if the update takes afterwards.
Click to expand...
Click to collapse
Don't bother. I spent a lot of time on this last night. I went so far as to put 5.5.893 *system* on and tried to flash from that. (Obviously with boot image from 5.7.893 still). It got past the build.prop error and gave me a boot error. Meaning it fails asserting the boot image. No chance for this update to work for us I'm afraid.
I am on the leaked 5.5.893. I'm on the liberty rom. Would I have to put my phone all the way back to stock? Then start from there? At one time I had restored my phoned and did the 43v3r root and my system version went from the 5.5.893 to 5.5.886. Is that my culprit right there? Even though my radio and kernel is still from 5.5.893?
djr4x4 said:
I am on the leaked 5.5.893. I'm on the liberty rom. Would I have to put my phone all the way back to stock? Then start from there? At one time I had restored my phoned and did the 43v3r root and my system version went from the 5.5.893 to 5.5.886. Is that my culprit right there? Even though my radio and kernel is still from 5.5.893?
Click to expand...
Click to collapse
Woa woa woa. Slow down. You're trying to apply this over a custom rom? Is that what you're saying? That definitely won't work. It has to be stock system for the version that the update is made for. So, in this case, you need stock 5.5.893. The kernel and radio are fine as a custom rom can't touch those. But you will need to restore stock 5.5.893 if you want to apply the update to get the new kernel and radio. Then you can put your rom back on. Hope that helps!
Do I need to reflash the original bionic stock ROM with RSD lite, then flash the leaked 5.5.893 and then flash to 5.9.901?
If you made a nandroid backup of your clean 5.5.893 installation then restoring that would be the easiest method to get the 5.5.901 to install properly.
If you have changed anything at all in your system beyond simply rooting and mount-ext3.sh for permanent root, then the update will fail.
No don't do that. For sure don't do that as it will not work. You didn't make a backup of the stock rom when you did the 5.5.893 update before putting a custom rom on?? UGH. If that's the case and you don't have a nandroid backup of 5.5.893 then this is going to be a pain. Not impossible but will cause you some headaches. First thing's first. Go make a nandroid backup of your existing rom install. I'll see if I can put some steps together that'll get you upgraded.
---------- Post added at 03:38 PM ---------- Previous post was at 03:37 PM ----------
cellzealot said:
If you made a nandroid backup of your clean 5.5.893 installation then restoring that would be the easiest method to get the 5.5.901 to install properly.
If you have changed anything at all in your system beyond simply rooting and mount-ext3.sh for permanent root, then the update will fail.
Click to expand...
Click to collapse
But not with RSD using the FXZ now that he's on 5.5.893, yea? That'd be...bad.
---------- Post added at 03:45 PM ---------- Previous post was at 03:38 PM ----------
1) http://rootzwiki.com/topic/5484-r3l...he-bionic-v21/page__view__findpost__p__127684
Get that, unzip it, run it, and choose option 1. That will put you back on 5.5.886 stock *system* but will not touch anything else. And will of course, will install permanent root.
2) http://www.multiupload.com/0ZEN69NGO2
Get that, throw it on the SD card, and boot to stock recovery. Flash it.
3) Now you are ready to try flashing 5.9.901 again
4) NANDROID THAT THING
Then restore your custom rom and you should be good to go. CZ, did I miss anything?
I've lost my nandroids backup. . I have made a new nandroid backup of this current setup incase I screw something up.. I am unable to restore back to fully stock at this time which I'm rather upset about.. Am I screwed?
djr4x4 said:
I've lost my nandroids backup. . I have made a new nandroid backup of this current setup incase I screw something up.. I am unable to restore back to fully stock at this time which I'm rather upset about.. Am I screwed?
Click to expand...
Click to collapse
Make sure you have a nandroid of your current (custom, apparently) rom. Then do the steps I outlined above.
Just to reiterate, this will not work for those of us on 5.7.893, correct?
GeoMandell said:
Just to reiterate, this will not work for those of us on 5.7.893, correct?
Click to expand...
Click to collapse
No it will not. Nothing will at this point in time.
awesome. It worked. I am now 5.9.901!!!! Thanks for the help... And I kept root!!!
Grumble grumble lucky jerk... J/K I'm sincerely glad that worked for you. *NANDROID*.
WHAT?!!
I am on 5.7.893
You guys mean to tell me that even if I nandroid back, to my clean back-up of 5.5.893... This 901 update will still fail??!!
Is it checking the kernel also? I have a nandroid that is completely stock so if I flash back to that this 901 update should go unless it checks the kernel version too.
I was attempting to flash the stock att firmware via rsd and have deleted the stock rom from safestrap recovery in the process. I would like to get back to stock rom (ATT). I can boot in safestrap and currently have golden rom on another rom slot but need to get back to stock firmware or stock rom as im selling the phone atrix HD.
Oneofonex1 said:
I was attempting to flash the stock att firmware via rsd and have deleted the stock rom from safestrap recovery in the process. I would like to get back to stock rom (ATT). I can boot in safestrap and currently have golden rom on another rom slot but need to get back to stock firmware or stock rom as im selling the phone atrix HD.
Click to expand...
Click to collapse
I can inbox you a link to my restore, note: I have personal files, so I'm going to trust you'll delete the data partition. Tell me if your interested.
Maybachiswhereitsat said:
I can inbox you a link to my restore, note: I have personal files, so I'm going to trust you'll delete the data partition. Tell me if your interested.
Click to expand...
Click to collapse
Thats amazingly generous of you, but I was able to upgrade RSD lite and flash the stock firmware. Again, i greatly appreciate your help.
No problem, glad you could fix your phone.
Sent from my DROID Atrix HD MAXX using xda app-developers app
Is your AT&T ROM image still available?
Maybachiswhereitsat said:
No problem, glad you could fix your phone.
Hi, I have an Atrix HD with Batakang in slot 1 and of course the stock AT&T ROM in, well, the Stock slot. I have Safestrap 3.11. I wanted to unlock the phone for int'l use, and it simply would not give me the prompt to enter the unlock code (said "Invalid SIM" or something like that), so I left it with an AT&T dealer because the process should have been simple, but wasn't.
They couldn't do it either, but when I got the phone back, the entire 8GB ROM space was wiped! Batakang was gone, the Stock slot is empty, and unfortunately, the Safestrap backup I made of Stock (and left on the internal SD) was gone too!
I did have a Batakang backup which restored fine, I entered the unlock code OK in it (I assume that worked - there was no confirmation message), but still have an empty AT&T stock slot.
What ROM images I've found are not compatible with Safestrap, so what I'm looking for is either a Safestrap backup or a zip installer compatible with Safestrap, or any other suggestions appreciated! Thanks!
Click to expand...
Click to collapse
Hi, I'm running Benny's 4.3 (build number 3.04.651.2) Deodexed (because i do not see any .odex files in the system folder, right?) and I want to flash the update which keeps popping up in the notifications every 24 hours after clearing app data.
I tried doing the OTA update but my phone goes into TWRP. My biggest concern is flashing the stock rooted update because my phone really isn't rooted. I have SuperSu on the phone and sometimes I get "SuperSu has been granted permission" or something like that but Root Checker app says the phone does not have proper root access. I don't really know what is going on because I took my phone to a repair center to get it unlocked shortly after i got the official OTA 4.3 update. I read that you need to downgrade to 4.1 and then unlock the phone through SimUnlockHelper apk. When I got my phone back everything was working as it should and my phone is indeed unlocked.
My biggest concern is flashing a stock rooted rom because of the fact that my phone does not have proper root access. Would you recommend doing this and are there any precautions I should be aware of because I had nothing to do with rooting or tweaking android before since this is my first phone that runs android officially.
Thanks!
Andza195 said:
Hi, I'm running Benny's 4.3 (build number 3.04.651.2) Deodexed (because i do not see any .odex files in the system folder, right?) and I want to flash the update which keeps popping up in the notifications every 24 hours after clearing app data.
I tried doing the OTA update but my phone goes into TWRP. My biggest concern is flashing the stock rooted update because my phone really isn't rooted. I have SuperSu on the phone and sometimes I get "SuperSu has been granted permission" or something like that but Root Checker app says the phone does not have proper root access. I don't really know what is going on because I took my phone to a repair center to get it unlocked shortly after i got the official OTA 4.3 update. I read that you need to downgrade to 4.1 and then unlock the phone through SimUnlockHelper apk. When I got my phone back everything was working as it should and my phone is indeed unlocked.
My biggest concern is flashing a stock rooted rom because of the fact that my phone does not have proper root access. Would you recommend doing this and are there any precautions I should be aware of because I had nothing to do with rooting or tweaking android before since this is my first phone that runs android officially.
Thanks!
Click to expand...
Click to collapse
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
jblaze10 said:
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
Click to expand...
Click to collapse
^This is the safest option @Andza195
BTW, imo, it should work, but just backup just in case. Also, if something doesn't work, the real best method is just to download the newest version of the ROM, back (everything that's important to you) up, wipe everything in TWRP except Internal Storage (because this is where the flashable .zip is at!) and flash the ROM fresh.
jblaze10 said:
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
Click to expand...
Click to collapse
Okay, thanks!
StormyNight said:
^This is the safest option @Andza195
BTW, imo, it should work, but just backup just in case. Also, if something doesn't work, the real best method is just to download the newest version of the ROM, back (everything that's important to you) up, wipe everything in TWRP except Internal Storage (because this is where the flashable .zip is at!) and flash the ROM fresh.
Click to expand...
Click to collapse
Just flashed the stock rooted kitkat rom and everything is working as it was before, thank you all for your help!
I'll try to keep this concise. I've been rooted since I first bought this phone over 3 years ago, I received the 2.3.6 OTA Bell update from 2.3.4, rooted again and it's been like that until a month ago.
I successfully installed SafeStrap, made two backups, and installed CM9 onto a slot, it didn't work well but it booted on the first try. I then tried MiniMoto 2.3.4 which worked perfectly, then a 4.0.4 "Motoblur" build in which enough things work to get by. All of these I installed using SafeStrap and they booted fine on the first try. They've even held up to me modifying them.
If I disable SafeStrap my stock 2.3.6 rom boots perfectly. If I try to restore my backup to a SafeStrap slot and boot it, it bootloops and freezes every time. I backed up my stock reset rom and tried to restore that, same result. I also tried the "Bell 2.3.6 Optimized" build I found here, which should be my stock rom only cleaned up, same result.
I've cleared caches over and over, tried copying the build.prop from my stock rom (although I'm not certain I did it correctly) and at this point I'm at a loss. I've searched and read all that I could find, but it's my phone's own default rom that I can't get to boot... Any ideas would be appreciated.
Thanks!
-Kurt
Reference:
CM9
[XT860][CM9] Working 3G data... finally!
Minimoto 2.3.4
[ROM - Stock-based] Minimoto v1.7 XT862/XT860- Less is more.
Motoblur 4.0.4
[ROM]Motoblur + Android 4.0.4 -- [Development Discontinued]
Motoblur 2.3.6 Optimized
[ROM]Stock Motoblur 2.3.6 rooted, deodexed, zipaligned, optimized[xt860]CWM
Bob_760 said:
I'll try to keep this concise. I've been rooted since I first bought this phone over 3 years ago, I received the 2.3.6 OTA Bell update from 2.3.4, rooted again and it's been like that until a month ago.
I successfully installed SafeStrap, made two backups, and installed CM9 onto a slot, it didn't work well but it booted on the first try. I then tried MiniMoto 2.3.4 which worked perfectly, then a 4.0.4 "Motoblur" build in which enough things work to get by. All of these I installed using SafeStrap and they booted fine on the first try. They've even held up to me modifying them.
If I disable SafeStrap my stock 2.3.6 rom boots perfectly. If I try to restore my backup to a SafeStrap slot and boot it, it bootloops and freezes every time. I backed up my stock reset rom and tried to restore that, same result. I also tried the "Bell 2.3.6 Optimized" build I found here, which should be my stock rom only cleaned up, same result.
I've cleared caches over and over, tried copying the build.prop from my stock rom (although I'm not certain I did it correctly) and at this point I'm at a loss. I've searched and read all that I could find, but it's my phone's own default rom that I can't get to boot... Any ideas would be appreciated.
Thanks!
-Kurt
Reference:
CM9
[XT860][CM9] Working 3G data... finally!
Minimoto 2.3.4
[ROM - Stock-based] Minimoto v1.7 XT862/XT860- Less is more.
Motoblur 4.0.4
[ROM]Motoblur + Android 4.0.4 -- [Development Discontinued]
Motoblur 2.3.6 Optimized
[ROM]Stock Motoblur 2.3.6 rooted, deodexed, zipaligned, optimized[xt860]CWM
Click to expand...
Click to collapse
you are trying to restore a stock rom slot backup, to a rom slot?I think that some modification is needed, maybe as simple as adding a file.
---------- Post added at 07:07 PM ---------- Previous post was at 06:58 PM ----------
could try an advanced restore, and just restore data over minimoto, wipe caches before booting.
---------- Post added at 07:24 PM ---------- Previous post was at 07:07 PM ----------
do you want the data or the system restored?
backups and rom.zips work differently, don't think you can restore a stock system backup on a rom slot
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
when stock rom slot is selected to boot, the safestrap's boot menu always says "disabled", that is how it works
sd_shadow said:
you are trying to restore a stock rom slot backup, to a rom slot?I think that some modification is needed, maybe as simple as adding a file.
could try an advanced restore, and just restore data over minimoto, wipe caches before booting.
do you want the data or the system restored?
backups and rom.zips work differently, don't think you can restore a stock system backup on a rom slot
when stock rom slot is selected to boot, the safestrap's boot menu always says "disabled", that is how it works
Click to expand...
Click to collapse
As separate tasks, I'd like to...
1. Restore and boot my backup and go into it to check some settings. I guess the easiest way would be to restore it back onto my stock rom? I was under the impression I could put it in a SS rom slot. If that were relatively simple I think I'd rather it in a rom slot. (adding a file?)
2. Install the Motoblur 2.3.6 Optimized rom to a SS rom slot and get it to boot.
I understand safestrap is "disabled" when you boot the stock rom, I was just pointing out that my stock 2.3.6 rom works fine, I just can't boot the backups or "optimized" versions of it.
I tried to install Motoblur 2.3.6 Optimized over top of Minimoto to no avail, but I'm not sure if I did it correctly, I'm going to try that again I guess.
Thanks
-Kurt
your Bell 2.3.6 Optimized.zip is 176.69 MB?
sd_shadow said:
your Bell 2.3.6 Optimized.zip is 176.69 MB?
Click to expand...
Click to collapse
Yeah, I got it from that Mediafire link. I see you uploaded one, I'll give it a shot but they appear to be identical.
Bob_760 said:
Yeah, I got it from that Mediafire link. I see you uploaded one, I'll give it a shot but they appear to be identical.
Click to expand...
Click to collapse
check the posted md5 checksum, thats how you verify the file is the same
https://sites.google.com/site/sdshadowscollection/home/hash-checksums
---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------
I just downloaded from the mediafire link, and uploaded it to DevHost, but didn't try it.
Bob_760 said:
Yeah, I got it from that Mediafire link. I see you uploaded one, I'll give it a shot but they appear to be identical.
Click to expand...
Click to collapse
MediaFire file was not safestrap ready
see http://forum.xda-developers.com/showpost.php?p=55372958&postcount=95
sd_shadow said:
MediaFire file was not safestrap ready
see http://forum.xda-developers.com/showpost.php?p=55372958&postcount=95
Click to expand...
Click to collapse
I thought that rootfs folder was the key, but i had only gotten that far, i didn't know how to go about adding it, i made a zip that looked the part but obvously i had no idea what i was doing xD
md5 checks out, I'll try that and report back. Thanks so much for the help!
Bob_760 said:
I thought that rootfs folder was the key, but i had only gotten that far, i didn't know how to go about adding it, i made a zip that looked the part but obvously i had no idea what i was doing xD
md5 checks out, I'll try that and report back. Thanks so much for the help!
Click to expand...
Click to collapse
the trick is added to the zip without unzipping
I use 7zip or winrar otherwise you need a zip signing program
sd_shadow said:
the trick is added to the zip without unzipping
I use 7zip or winrar otherwise you need a zip signing program
Click to expand...
Click to collapse
I'd pulled the folder from the minimoto rom and tried to make a zip that was just the folder (in the correct place in the tree) thinking I could make a "patch" but it failed when I tried to "install" it. I had even added the folder to the motoblur rom zip using winrar but I hadn't tried installing it yet. I assumed it wouldn't work since I didn't really know what I was doing...
I installed your uploaded motoblur safestrap rom and it worked perfectly first go! It took forever to boot but I'm assuming its setting things up. I was even able to restore the data from my backup and things look good so far! Well, to be honest things are painfully slow right now, but hey, this phone barely worked when I backed it up, so I was sorta expecting this. Now I at least have a good reference for how I had things set up.
Hello can anyone help me install a cwm for my 4.4.4 z1 c6903 unlocked bootloader (also rooted . version 4.4.4 with the .108 on the end) ?! I really want to flash a new custom rom for this phone and unlike samsung phones the tutorials on youtube for 4.4.4 are missing !
Drewmk20 said:
Hello can anyone help me install a cwm for my 4.4.4 z1 c6903 unlocked bootloader (also rooted . version 4.4.4 with the .108 on the end) ?! I really want to flash a new custom rom for this phone and unlike samsung phones the tutorials on youtube for 4.4.4 are missing !
Click to expand...
Click to collapse
Hi,
Check this out ...
http://prntscr.com/4ow7hp
Download file, then unzip. Run BAT file and follow screen directions. You will end up with three recoveries to choose from.
Need help
Hello, i'm newbie here, trying to learn some stuff, i searched the forum but i couldn't find it, i think this page is most appropriate to post it here.
Well i want to flash a custom rom, but my first attempt went not good for me. I've lost my imei and panicked, anyway by flashing stock sony rom i recovered it.
Now i unlocked my bootloader again (it was locked again after i flashed my stock firmware back), rooted my phone, and learned that nandroid app can make a full backup, and even i screw things up (except hard bricking i guess), that backup will save me. So i downloaded it made a full back up, but it says "back up type: clockwork or TWRP,"
And i heard that TWRP is not for Xperia Z1. Thats why i decided to not install it,
Then i installed clockwork rom manager, it said "this app requires clocwork recovery", but i couldnt find a appropriate version of clockwork recovery, the ones i found on play store were for android 4.0.4, and mine is 4.4.4
You guys probably understand that i know almost nothing about this stuff, (i have only got what i read form forums), so what should i do, which version of clockwork should i install or is there any other supported apps that i can use my nandroid backup?
Soka, i checked your link but couldnt be sure about which link should i click.
And another question, do i still need titanium backup while i have nandroid?
Thanks in advance
My device is C6903
4.4.4
14.4.A.0.157
CWM Recovery
There two methods:
1. Unlock your bootloader and flash a custom kernel (Bootloader Unlock is required for flashing custom roms which are not stock based; for example cyanogenmod)
-> with a custom kernel you have cwm and often twrp also.
2. check this out: http://forum.xda-developers.com/xperia-z1/development/newroot-z1-t2807092
maybe you have to flash .108 kernel to use newroot, after rooting you can flash the actually kernel from your firmware....
---------- Post added at 07:27 PM ---------- Previous post was at 07:23 PM ----------
Özgün Özerk said:
Hello, i'm newbie here, trying to learn some stuff, i searched the forum but i couldn't find it, i think this page is most appropriate to post it here.
Well i want to flash a custom rom, but my first attempt went not good for me. I've lost my imei and panicked, anyway by flashing stock sony rom i recovered it.
Now i unlocked my bootloader again (it was locked again after i flashed my stock firmware back), rooted my phone, and learned that nandroid app can make a full backup, and even i screw things up (except hard bricking i guess), that backup will save me. So i downloaded it made a full back up, but it says "back up type: clockwork or TWRP,"
And i heard that TWRP is not for Xperia Z1. Thats why i decided to not install it,
Then i installed clockwork rom manager, it said "this app requires clocwork recovery", but i couldnt find a appropriate version of clockwork recovery, the ones i found on play store were for android 4.0.4, and mine is 4.4.4
You guys probably understand that i know almost nothing about this stuff, (i have only got what i read form forums), so what should i do, which version of clockwork should i install or is there any other supported apps that i can use my nandroid backup?
Soka, i checked your link but couldnt be sure about which link should i click.
And another question, do i still need titanium backup while i have nandroid?
Thanks in advance
My device is C6903
4.4.4
14.4.A.0.157
Click to expand...
Click to collapse
you can install twrp on z1 as well: http://forum.xda-developers.com/showthread.php?t=2261606
for cwm check my other post in this thread
hope this will help
Thanks, ive already unlocked my bootloader and rooted my phone as a mentioned above, just needed to know if i can use TWRP and CWM, got my answer thanks, both will work fine with Nandroid backup right? Should i prefer one over another? Cause i dont want any problems
Özgün Özerk said:
Thanks, ive already unlocked my bootloader and rooted my phone as a mentioned above, just needed to know if i can use TWRP and CWM, got my answer thanks, both will work fine with Nandroid backup right? Should i prefer one over another? Cause i dont want any problems
Click to expand...
Click to collapse
Hi there bro...
In the Link ...
Check this out ...
http://prntscr.com/4ow7hp ... download the one the red arrow is pointing at. Unzip and run BAT file. When Prompted onscreen connect device to PC.
This will install recoveries and an app called NDR Utils. With this app you can choose the primary recovery of your choice.
I prefer using Philz...(CWM) based. Important rule i've always followed make backups ( Nandroid).