Dear XDA folks,
I'm afraid that I've made a noobie error.
I successfully unlocked the boot loader, and injected a custom recovery by following the instructions at
http://forum.xda-developers.com/moto-g-lte/general/rooting-moto-g-2015-lte-xt1078-t3086069
However, I am now unable to copy files to the phone either via adb or using androidfiletransfer (I'm on a Mac) as both the internal and external SD cards are now mounted as read only. I did try adb remount and a few other mount instructions (thanks google!) but don't appear to have permissions to change the file system.
This means I can't seem to install SuperSU in order to root the phone.
XT1072, Moto G 2014 LTE.
Hopefully somebody can tell me some easy steps to fix it?
Thanks in hope,
Phil
Just in case anyone else finds this in a search, the answer appears to be that the XT1072 needs a newer version of the TWRP recovery image.
I got the later version (2.8.6.0) from here
http://forum.xda-developers.com/showpost.php?p=61430545&postcount=13
and now have read/write access.
Related
Hi all,
I am trying to flash my G1 to one of the nice custom roms. I flashed the recovery and spl just fine.
Now I cannot flash anything. I've tried different roms (cyanogen and dude's) and even tried flashing the radio. No love. The error is that it cannot find my sdcard or update.zip.
Phone is pvt and is rooted.
Any thoughts?
Thanks,
Hank
What steps did you take to root? Is your card fat32?
Did you mount the sdcard on windows? If you did, rename the file to update not update.zip on WINDOWS! Also, can you even mount your sdcard? If not, then there's your problem.
I followed the rooting instructions from this site. i do have # in the local terminal.
i can mount the sd card and i did mount in windows to transfer fikes over. i should just name them update not update.zip?
djscamper said:
I followed the rooting instructions from this site. i do have # in the local terminal.
i can mount the sd card and i did mount in windows to transfer fikes over. i should just name them update not update.zip?
Click to expand...
Click to collapse
That will probably help.. By default Windows hides the extension (the .zip part) so when you rename it to "update.zip" you actually make it update.zip.zip
Easy way to check is look at the original file.. if it says something like
Code:
update-cm-3.6.6-signed.zip
you need to rename to
Code:
update.zip
if it says
Code:
update-cm-3.6.6-signed
then just call it
Code:
update
Thanks. Getting a signature error now.
Will try a different version of the file once I am off Caltrain.
Yeah - if you have a modded recovery and get that error, it's most likely a bad download. Good luck.
That did it. It is always something so simple.
Thanks a ton. Hopefully this thread will help someone else as well.
EDIT: NEVERMIND EVERYONE, I took the plunge and flashed with odin. Good a time as any to try out froyo JP3 optimism lol
I was mucking around and made a noob mistake of copying some odex files from captivate to i9000 using root explorer. I made a similar post in the general section but please forgive me for posting here aswell (thought it might be more appropriate here +im getting desperate...)
My SGS gets stuck after boot animation ( the files are in system/app
AudioPostcard.apk
AudioPostcard.odex
SamsungWidget_FeedAndUpdate.odex)
I can't seem to delete/modify any files through adb whilst in recovery mode, nor can i seem to push an update zip onto the internel SD
seems like adb might not work properly in recovery mode?... http://androidforums.com/samsung-i7500/35532-android-internal-sd-card-partitions-dead-galaxy.html can i get it working in download mode?
I either get permission denied or other errors (director doesn't exist, or no output etc).
Some possible solutions I've thought of, but haven't been able to work as yet...
- Somehow getting clockwork recovery update.zip onto internal sd? (possible to mount the drive on windows? while in recovery. something like this http://forum.xda-developers.com/showthread.php?t=531310&page=5)
- Using adb to remove/replace files (if i can solve permission and other errors... somehow get su permission approved whilst in recovery mode).
- Using odin to flash over the files? If this is this possible without erasing rest of firmware???
- some special way/button combo to get past the freeze??
I realllllly don't want to reflash my firmware and lose all apps/data/settings/messages... I'd be so crushed...
Some extra details:
- Have adb installed on win7 32bit
- Superuser/root are present on phone, although it seems that superuser needs to set permission for adb??? Thought it had to do that for lagfix though...
-JG1 firmware with 1-click lagfix.
Forever grateful to any helpers!!!
Good Night,
First of all, I hope this will be of use to someone
I own a Z3 Compact which I rooted yesterday. I followed the steps detailed in here, and today I was getting ready to start using XPosed but I am unable to install it, since I am getting a nice :
SD Card: /storage/emulated/0/Android/data/de.robv.android.xposed.installer/files
Copying Xposed-Disabler-Recovery.zip...
Mounting /system writable...
mount: permission denied (are you root?)
Could not mount /system writable
Trying to continue anyway...
cp: can't create '/system/bin/
app_process.orig': Read-only file system
Failed to create a backup of /system/bine/app_process
Click to expand...
Click to collapse
I followed every step, even flashed the part specified at the FAQ that asks me to flash RICDefeat.zip
FAQ
- Some root apps don't work, because /system can't be remounted rw, what's up with that?
Sony has a special in kernel protection that disallow remounting /system read-write, even for root. Flash this in recovery (copy it to the sdcard and reboot in recovery with volume UP pressed, then install it): https://github.com/dosomder/SonyRICD.../RICDefeat.zip
Click to expand...
Click to collapse
So since I could not get through, even after following every step, opted for a different Installation Mode, to see if I could avoid that by flashing stuff instead
Installation Mode
Classical (write to /system directly)
Recovery (flash zip automatically)
Recovery (write zip to SD card, flash manually)
Click to expand...
Click to collapse
I've tried all three methods
- The first one throws that error
- The second reboots the phone without flashing a thing,
- The third one ... well, it says the following
SD card: /storage/emulated/0/Android/data/de.robv.android.xposed.installer/files
Copying Xposed-Disabler-Recovery.zip...
Copying Xposed-Installer-Recovery.zip...
Copying XposedBridge.jar...
Please flash Xposed-Installer-Recovery.zip from the SD card to complete the operation.
Click to expand...
Click to collapse
So then you just have to reboot in recovery, dig to that same folder and find in there the zip to flash.
Anyway, just posting this in case anyone has that same problem, because it has driven me crazy not being able to fix that /system non writable problem with Sony. geez....
Cheers
Thank you so much. It works for my Z3C Docomo (already flashed with US ROM - D5803_23.0.1.A.5.77_US.ftf).
Thanks!
I had another Z3c that broke and the installation was as smoth as possible, but i had unlocked bootloader and rooted by the old method (that needed BU).
I got a new phone from assistence and did the root without UB.. and got the same problem .. thanks for the "tutorial"
Alright so this fixes some issue you had with the actual flashing of xposed in TWRP? I'm assuming it doesn't fix the bootloop problem that happens if you don't wipe the cache between every restart?
I'm not sure I follow your original thread,or what you actually did to resolve whatever issue it is that you were having...
NeLk said:
Installation Mode
Classical (write to /system directly)
Recovery (flash zip automatically)
Recovery (write zip to SD card, flash manually)
I've tried all three methods
- The first one throws that error
- The second reboots the phone without flashing a thing,
- The third one ... well, it says the following
So then you just have to reboot in recovery, dig to that same folder and find in there the zip to flash.
Anyway, just posting this in case anyone has that same problem, because it has driven me crazy not being able to fix that /system non writable problem with Sony. geez....
Click to expand...
Click to collapse
I'm currently being driven crazy by Sony's ridiculous R/W restriction, so I'd like to be able to lift it. If I understand correctly, your thread is partially about that. I'm having trouble flashing RICDefeat from recovery.
I don't understand the difference between flashing a zip automatically and flashing it manually. The only method I know is copying to SD/internal memory, booting into recovery and install/flash zip from there. Which recovery did you use?
Thanks.
The latest XPosed Installer is missing last option, but I found the file downloaded at /sdcard/Android/data/de.robv.../cache/downloads/framework
Hello , I made a huge mistake and I'm looking for help, I accidentally wiped my internal on my HTC One and I'm looking to push a new rom on it. I've looked for tutorials but It's giving me outdated tutorials on Anddroid studio. could someone please kindly help me? I'm still rooted and have TWRP just can't figure out the Android studio bit.
Thank you 1
Made this mistake, too. Frustrating as I lost all my files and backups then.
You need a flash card with a ROM (*.zip) of your choice.
Connect the flash card to your phone over an OTG cable, reboot to recovery, go to advance/mount and mount USB OTG.
You will then see the content of your flash card, install your zip from there, or copy the zip to internal memory and install normally.
Marck527 said:
Hello , I made a huge mistake and I'm looking for help, I accidentally wiped my internal on my HTC One and I'm looking to push a new rom on it. I've looked for tutorials but It's giving me outdated tutorials on Anddroid studio. could someone please kindly help me? I'm still rooted and have TWRP just can't figure out the Android studio bit.
Thank you 1
Click to expand...
Click to collapse
Flash TWRP 2.8.5.0. It supports MTP in recovery so you can access your internal storage.
Or use adb in recovery to push a Rom to the phone. Put your Rom in your fastboot folder and rename it rom.zip. Then while in recovery
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes. Then install the Rom with recovery :good:
Greetings.
could not really find anything within this forum that would describe my problem adequately, so I will just ask here, hoping someone had the same.
I recently received this device (XT1900-7), successfully unlocked bootloader and went on to boot and install TWRP.
Booting it temporarily is childs play, but doing anything else within TWRP seems to be pointless. Flashing the TWRP installer results in a bootloop when trying to access TWRP.
To flash LineageOS 16.0 a persistent installation of TWRP is not required (right?) so I really do not care that much about it failing to install properly, I will be just fine with flashing LineageOS from the temporary TWRP.
Here comes the trouble though. I have not yet tried to wipe anything, as I suspect it of not working properly in my case.
Trying to run a backup, something I always prefer to do before wiping and flashing anything, is not possible due to permissions error - it fails to create the TWRP folder. I am also unable to push anything via adb to /sdcard and the contents of /sdcard are rather confusing. There are folders whose names contain random numbers and letters. Checking inside these folders shows that they seem to have an unlimited amount of subfolders.
Opening a terminal in TWRP (as well as adb shell) throws linker warnings (/system/etc/ld.config.txt seems to be missing for /sbin/toolbox) about it being unable to read said file. It does so with every command I submit to the shell.
When I unmount /data I am able to push to the device (though still not to /sdcard - again missing permissions).
Also when switching to slot B it gives me "Error changing bootloader boot slot to B" with "Failed to mount /vendor (invalid argument)".
Relevant data:
I have not done a firmware update, it is still running on Android 7.1.1 and I do not intend to do an update since the stock rom is to be replaced by LineageOS anyways.
As mentionend: XT1900-7, 64GB mmc, 4GB DRAM and so on...
I am able to push files to /tmp for example which allows me to flash the twrp-installer.
Edit: TWRP version is the latest available (3.3.1-0)
Is there anyone who had similar issues and might provide help?
No need to ELI5, I'm at least experienced in Linux, not that much in Android. Previous phone was a G4 Play which was pretty straightforward (unlock, fastboot flash recovery and flash away whatever I felt like).
If you need any more information I will be happy to provide it.
Thanks in advance to anybody that can give me a hint or clue to solve this.
Well. Nvm. It works flawlessly with twrp-3.2.1-1. Seems to be something with latest version. Thx anyways