Hello,
I'm new to rooting a xperia z1 compact. After I rooted the device. however on the latest firmware I encounter some problems.
The camera don't work properly. It refuse to take any picture and the home and back button disappear. only way to go back to home is to lock and delock the phone
/system can not be mounted. So busybox installation by and app can not be done (yes i can flash it too but I don't believe this solves the mount problem)
Are this standard problems on the latest stock rom?
This was how I rooted. I downloaded an old firmware with xperifirm (14.2.A.1.114). After this I used flashtool to install both towelroot as supersu. Installed nut's xzdualrecovery with a .bat fille. Made a prerooted rom with the latest firmware (14.6.A.1.236) with PRFCreator_v1.1 and added superSU to flash this all with twrp on the phone (als applyed a factory reset to wipe cache ect.)
Fixed
I fix the problem already. Sorry that i opened a new topic for it.
The problem I encountered was normal for lolipop rooting. Since I found only old tutorials for rooting I found nothing about this. I solved it by flashing my pre-rooted zip file and than without an system boot I had to flash the ftf rom and exclude the PARTITION,TA and SYSTEM.
still not fixed the mount /system
Unfortunate I still not know why all root apps can't mount the /system. So all root aps can't work. Also the most important fix the writable SD card fix for app on SD card can also not be executed. Any idea what the solution might be?
Junocaen said:
Unfortunate I still not know why all root apps can't mount the /system. So all root aps can't work. Also the most important fix the writable SD card fix for app on SD card can also not be executed. Any idea what the solution might be?
Click to expand...
Click to collapse
I've never used prfs, but I have read of people having trouble. Did you flash NUT dr again? Usually that alone takes care of the r/w issue.
Thank you
You were right. I assume the pre-rooted zip does not kill the ric which might caught the problem. Nut's kills the ric fortunately during installation.
Related
I found following article: "android.stackexchange.com/questions/19286/will-a-custom-recovery-work-with-an-encrypted-device"
According to this description, it should be possible to use the ICS encryption after partitioning the SDcard. Has anyone already tried it?
Article:
"Mount one partition on /sdcard so that it could be used by system & leave other one (Clockwork Mod can do mounting too)."
How can I do this?
Bump
Nobody tried it yet???
i think is better u dont use encryption at all...
if u need encryption for security reason, then u have to stay stock (botloader locked, no root, no cwm, otherwise the encryption has no sense to be done)..in case u want leave the encryption mode, u have to factory reset the phone
clockwork mod is not able to to backup, restore or flash a zip on an encrypted rom (easy to search around to discover this, as i just did now)
Why do you think there are no point with encryption with unlocked bootloader and root?
To me it seems thats when its most important, since its then very easy to get to your data and the only way to protect them?
I am using Titanium Backup and send the backups encrypted to Dropbox, not that much work to wipe and flash ROMS. Kernels you can still flash, at least With Francos app. The only downside is that need a PC to wipe since you have to do it through fastboot.
andQlimax said:
i think is better u dont use encryption at all...
if u need encryption for security reason, then u have to stay stock (botloader locked, no root, no cwm, otherwise the encryption has no sense to be done)..in case u want leave the encryption mode, u have to factory reset the phone
clockwork mod is not able to to backup, restore or flash a zip on an encrypted rom (easy to search around to discover this, as i just did now)
Click to expand...
Click to collapse
B1ny said:
Why do you think there are no point with encryption with unlocked bootloader and root?
To me it seems thats when its most important, since its then very easy to get to your data and the only way to protect them?
Click to expand...
Click to collapse
yes, infact what i mean is that if u want protect more ur data, then stay also with the bootloader locked etc (even if the encryption should be enough)
Have thought about also locking the bootloader since you have to wipe anyways, and need a PC. Will not be much more work/time. But is it really any need?
andQlimax said:
yes, infact what i mean is that if u want protect more ur data, then stay also with the bootloader locked etc (even if the encryption should be enough)
Click to expand...
Click to collapse
if u need encryption for security reason, then u have to stay stock (botloader locked, no root, no cwm, otherwise the encryption has no sense to be done)..in case u want leave the encryption mode, u have to factory reset the phone
Click to expand...
Click to collapse
From my point of view I also think that encryption is very important for rooted devices. If you loose your phone, it's very easy to get your privat data on the sdcard and app-data (acounts,...). With an encrypted device, the data are safe and that's all what I want.
clockwork mod is not able to to backup, restore or flash a zip on an encrypted rom
Click to expand...
Click to collapse
Also if you create a seperate partition - see article in my first post ???
I would also be interested if this was possible.
Reason being - my employer requires that my phone be encrypted and unrooted. I have been investigating a dual boot setup where I could boot my unrooted, encrypted, stock android image so that I can use it for corporate email and when I need root for something like tethering I could boot off the rooted image.
This way my corporate data would be encrypted and I would be adhering to company policy but I can also enjoy the flexibility of a rooted phone when I need it without wiping my phone every time I want to switch back and fourth.
the /cache partition is the answer, i think
I found out that the stock recovery, as expected, also cannot access the /SDcard partition. However, it looks in the /cache partition for update.zip files when the phone is encrypted. I was able to copy the 4.0.4 update to the cache partition and load it from there. Seems like CWM just needs to be updated to have an option to look there for zip files and we should be able to load them up.
chhall said:
I found out that the stock recovery, as expected, also cannot access the /SDcard partition. However, it looks in the /cache partition for update.zip files when the phone is encrypted. I was able to copy the 4.0.4 update to the cache partition and load it from there. Seems like CWM just needs to be updated to have an option to look there for zip files and we should be able to load them up.
Click to expand...
Click to collapse
The problem is /cache is 100 MB, and some (most?) ROMs are way more than that.
So I don't think using /cache is a fix.
I'm not sure of how CWM mounts the external SD card, but if it uses /mnt/sdcard/external_sd then it's impossible to use the external SD card because it depends on the internal SD for the mount point.
If this isn't the case, then it should be possible to partition the external SD card... Is it?
That leaves us with the only possible solution the partitioning of the internal SD card as mentioned in the link provided by OP.
Has anyone done this?
EDIT:
According to CM9's nightlies "know issues" list, encryption has already been solved and is working. I'm wondering how did they fix it.
bump
anybody knows the answer?
ghost shell said:
According to CM9's nightlies "know issues" list, encryption has already been solved and is working.
Click to expand...
Click to collapse
Could you give me a link to this?
There is a work around for flashing in CWM recovery by using the system ram as a temp file system.
You can use the dd command in adb to backup the entire current firmware and restore it in fast boot.
You can also use the backup and restore feature in ics to backup your sdcard contents and some apks.
There is a dev who is working on a full nandroid equivalent on an encrypted system. He is half way there. It requires cm recovery which has dmcrypt support.
http://forum.xda-developers.com/showpost.php?p=25635462&postcount=54
Check out the entire thread for other info for flashing custom roms via system ram.
ghost shell said:
bump
anybody knows the answer?
Click to expand...
Click to collapse
DanderMan said:
Could you give me a link to this?
Click to expand...
Click to collapse
http://teamhacksung.org/wiki/index.php/CyanogenMod9:GT-I9100:Nightly:Known_issues
Encryption used to be on the know issues, but not anymore. I don't know the status for the Nexus.
Also: http://forum.xda-developers.com/showpost.php?p=25515675&postcount=53
@bunklung
Thanks.
I'm still digesting the information.
The sad part is that even a normal factory reset doesn't allow removing encryption. If at least that would be possible it wouldn't be that bad.
EDIT2:
I've been reading and not even the ram trick would work with me because I can't get adbd running in CWM.
adb doesn't detect any device when the phone is in CWM-recovery mode.
Anyone found a way to revert to stock with cwm already installed for an encrypted phone?
Hi...with every guide in this forum i manage to unloock my BL and rooted my play.this is my first time using costum kernel..and i installed the doomkernelv11 on my xplay and it work like charm.but only i have a problemis my link2sd.i cant recreate mount script or remove and create apps link.also in root explorer show nothing in ext2 folder.my busybox also still in /system/xbin..not /system/bin.i also tried to delete/move it manually to /system/bin but failed.was this cause me the problem?? I allready reinstall and wipe data the link2sd and root explorer.but still not work.can someone help me solve this prob..i really hope i can enjoy with my first costum kernel.
Im using r800i with stock rom and .42fw..
Sorry for my bad english..
nevermind...suddenly i tried delete busybox with root explorer..and it done??(first time i tried..it fail).install back using installer in /system/bin. wipe data in link2sd.everything work again.
Please help. My wife did the 4.4 kit kat update on her note 8 5110. Update seems to finish fine but now all her data is gone. It looks like the internal SD card is cleaned. However, I see that under storage, it says that only 1.2 gb is free so it seems that the data is still there but not mounted. I tried to root the tablet using CF root method but every time I go into the tablet, it says that SU has stopped. I install Philz CMW to try to fix root but that did not work either.
Hopefully someone is able to help me. I was hoping to be able to root and go searching for the files but no such luck. I am not too familiar with adb commands but if someone can point me in the right direction to be able to copy her personal files out and move them to the new location on the tablet. Thank you.
illego said:
Please help. My wife did the 4.4 kit kat update on her note 8 5110. Update seems to finish fine but now all her data is gone. It looks like the internal SD card is cleaned. However, I see that under storage, it says that only 1.2 gb is free so it seems that the data is still there but not mounted. I tried to root the tablet using CF root method but every time I go into the tablet, it says that SU has stopped. I install Philz CMW to try to fix root but that did not work either.
Hopefully someone is able to help me. I was hoping to be able to root and go searching for the files but no such luck. I am not too familiar with adb commands but if someone can point me in the right direction to be able to copy her personal files out and move them to the new location on the tablet. Thank you.
Click to expand...
Click to collapse
Are you letting recovery flash SuperSU for you? If so, I suggest that you try flashing the installable zip file in recovery from this page instead.
ramjet73
ramjet73 said:
Are you letting recovery flash SuperSU for you? If so, I suggest that you try flashing the installable zip file in recovery from this page instead.
ramjet73
Click to expand...
Click to collapse
Thanks for the reply ramjet. I've tried both CF-Auto-Root and just letting recovery try to fix it. I've tried flashing the file you suggested and it still did not work.
illego said:
Thanks for the reply ramjet. I've tried both CF-Auto-Root and just letting recovery try to fix it. I've tried flashing the file you suggested and it still did not work.
Click to expand...
Click to collapse
Hmmm...
Did you test for root with Root Checker? I don't understand how you could have done all that and still not be rooted.
Since you have a working recovery you might want to try backing up all your partitions to the SD card, removing the SD card, and flashing the 4.4.2 update with Odin. Then try the CF-Auto-Root again and if that completes successfully you can flash your custom recovery, insert the SD card, restore the data partition from the backup and look for the missing data.
ramjet73
Can you point me to an odin package for the 4.4? I tried searching on google and it points me to sammobile.com. Looks like you have to pay to download. It tried reflashing the cmw package with my sd card and it keeps failing. Not enough space.
I am ready at this point to wipe out everything start clean on the tablet.
Thanks.
illego said:
Can you point me to an odin package for the 4.4? I tried searching on google and it points me to sammobile.com. Looks like you have to pay to download. It tried reflashing the cmw package with my sd card and it keeps failing. Not enough space.
I am ready at this point to wipe out everything start clean on the tablet.
Thanks.
Click to expand...
Click to collapse
It is sammobile.com but you don't have to pay.
Assuming you have a GT-N5110 the firmware you need is here, including instructions on how to install it.
ramjet73
Thanks for your help ramjet. I made an account and downloading. I'll try it out and hopefully it clears my issues.
Do the files not show with My Files, or Solid Explorer, or even plugging it into a PC?
Sent from my SM-G900F using Tapatalk
No luck at all. I ended up formatting everything to clean the card then odin the official 4.4 update. Wife only had pictures (sync to dropbox) and audiobooks on there. Still could not get root. I was not able to flash any 4.4 rom either.
Guess I am going back to 4.2.2. That version rooted fine and I have a Titanium backup of her tablet before updating to 4.4. Hopefully everything is okay after 4.2.2.
Hi. I'm having issues with towelroot and link2sd.
I have a C1905 Xperia M with a locked bootloader.
When I'm on 4.1.2 firmware, I root with cydia impactor, install supersu, busybox, patch with rootfix and THEN rootremountfix ---> I can succesfully apply the remount scripts, and my SD card can mount with the 2nd partition formatted to Fat32 (haven't tried ext).
But I'd also like to use 4.3 firmware... So:
When I try this on 4.3: I apply towelroot (impactor doesn't work, signature bug not found), install superSU, busybox, patch with rootremountfix ---> I ALWAYS get a bootloop when trying to apply the remount scripts in link2sd. If I try to use "rootfixer" at any stage, my phone gets unrooted and I'd have to "make it rain" again.
What can I do? Any help is appreciated. I should also note I'm not too android savvy. Kinda just getting into this stuff (my only previous experience was installing Cyanogenmod on my Galaxy mini a couple years ago).
Thanks!
If you haven't tried this one yet, then go ahead. But if it still doesn't work, then use this instead. It roots it right away. Make sure to use CVE-2014-3153.
Running converted GPE 4.4.4, stock rooted (recently followed steps to un-root), S-off (sunshine), Unlocked stock bootloader with CID: GOOGL001.
I received the OTA for 5.0.1 last week and received an error. Is there a way for me to install the OTA without wiping my phone?
I've spent the last week looking over the forums and haven't found an answer. Any help will be appreciated as I really want to avoid wiping to get the update if possible. Thanks!
Are you on stock recovery? I realize if you did the full conversion, it would have installed stock recovery. But just wanted to make sure you didn't flash a custom recovery after that.
Also, on the topic of wiping the phone, I would recommend backing up any important data in any case, if you don't already. There is never a guarantee against data loss even with an OTA; or just losing data from day to day usage for that matter.
Yea, I'm on stock recovery still. I was hoping to be done with too much modding and wanted to stay completely stock after the conversion, with the exception of root.
I did use SDfix: Kitkat Writeable MicroSD which changes some system files so apps can write to the microSD, could this be my problem?
Jamister989 said:
Yea, I'm on stock recovery still. I was hoping to be done with too much modding and wanted to stay completely stock after the conversion, with the exception of root.
I did use SDfix: Kitkat Writeable MicroSD which changes some system files so apps can write to the microSD, could this be my problem?
Click to expand...
Click to collapse
a recovery.log would be useful here to see where the ota fails.
pure guessing : I think if you've messed with the system partition (SDfix) it is likely what is causing your problem (infamous "unexpected content" error in recovery while installing ota).
I'll post one this evening. Where is a quick explaniation of how to the report?
Jamister989 said:
I'll post one this evening. Where is a quick explaniation of how to the report?
Click to expand...
Click to collapse
what do you mean by 'how to the report?' ?
Jamister989 said:
I did use SDfix: Kitkat Writeable MicroSD which changes some system files so apps can write to the microSD, could this be my problem?
Click to expand...
Click to collapse
If any system files have been altered by root, the OTA will fail. You either need to return the files to the exact "stock" condition, or re-install the stock ROM.
Sorry, what I meant was, how do I view the Recovery.log? I did a search in root browser and turned up nothing. Cache folder is empty.
The SD fix app should have made a back up copy of the original look in /etc/permissions and it's platform.xml the original will have original pre sdfix in the file name..
I had a failed attempt of OTA and it stated that my "platform.xml " was the reason.
Like @graffixnyc said only you you will have to rename the platform.xml to platform.bak and the platform.presdfix to platform.xml as it's the unmodified xml you need.
Jamister989 said:
Sorry, what I meant was, how do I view the Recovery.log? I did a search in root browser and turned up nothing. Cache folder is empty.
Click to expand...
Click to collapse
you can :
- reboot in recovery, try to apply ota, view the recovery.log in recovery menu, adb pull it and eventually post it....
- or assuming your issue is because of the modification of platform.xml as @graffixnyc and @jball stated, switch it with its backup (same dir) and then retry the ota.