Related
May have been asked before, but I tried searching and didnt find much luck.
I think my SDCard slot finally gave up, it just will not be read (tried two different 8gb cards that both worked fine on the computer). On Cyan 4.2.9.1.
Anyway, is there a way to flash the phone without the sdcard? I was trying to think how that would be possible, but I think its not right?
Just looking for a quick def. answer so I can know if i need to go phone hunting . Or do something different , which would be much better.
Appreciate it .
Happy holidays btw
You should be able to using ADB, not sure the command lines for that. As well, you might want to try getting a can-o-air and blowing out the SD card slot on your phone.
Lastly, this is the wrong section, should of been posted in Q&A.
pjcforpres said:
You should be able to using ADB, not sure the command lines for that. As well, you might want to try getting a can-o-air and blowing out the SD card slot on your phone.
Lastly, this is the wrong section, should of been posted in Q&A.
Click to expand...
Click to collapse
I didnt really think of adb, yeah that might work. Maybe someone knows them?
Maybe
adb shell recovery flash location/zip ?
Tried the canned air, didnt change. Good thinking though.
And lastly, I did debate which place, but I was thinking I saw a utility here or I am looking for the command lines and thought maybe alittle more technical than a general question? It will fall shortly anyway (hopefully after the commands ) or get moved/deleted.
If someone nandroided, they could just send you their system.img and you could fastboot it onto the phone. Provided you have the engineering/danger SPL.
persiansown said:
If someone nandroided, they could just send you their system.img and you could fastboot it onto the phone. Provided you have the engineering/danger SPL.
Click to expand...
Click to collapse
Thats a pain, and I dont think there are many of those out there...
No adb commands? Ive been searching but it seems scarce
EDIT:
Ok I tried my idea anyway,
adb shell recovery flash update.zip
And it just hangs (no errors though)...probably missing something?
Are you able to warranty your phone for the bad SDCard Reader??
If so, I started this thread and came up with an answer, but it will bring you back to fully stock cupcake
http://forum.xda-developers.com/showthread.php?t=560254
Search for a webpage , how to root/flash/hack g1. It's has everything you need.
You need to go into fastboot
Fastboot update update.zip. somthing like that or do like the website shows 1 at a time.
There might be an adb for it, but I've never used it. Fastboot only option I believe.
bildo said:
Search for a webpage , how to root/flash/hack g1. It's has everything you need.
You need to go into fastboot
Fastboot update update.zip. somthing like that or do like the website shows 1 at a time.
There might be an adb for it, but I've never used it. Fastboot only option I believe.
Click to expand...
Click to collapse
That is the better answer, thanks for continuing. If you just left that first sentence I would have said re-read my problem, I cannot use my sdcard (the normal way rom is flashed).
As for the fastboot, I will look into that. I appreciate it, thanks.
Im getting
No android-info.txt
No android-product.txt
In the package when i try to do this command while in fastboot:
fastboot update update.zip
I found android-info in the update file from htc, but I cannot resign right now. Im also guessing it will still yell about the android-product.txt anyway, so any ideas where to get that file?
If all you're trying to do is flash a .img (system.img, userdata.img, recovery.img) and you have a developer, or hardspl, you can flash using fastboot.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
flashing an update.zip is only possible through recovery mode, but can still be accomplished using the /cache partition
Code:
adb push update.zip /cache
and you should be able to do the update from cache.
haykuro said:
flashing an update.zip is only possible through recovery mode, but can still be accomplished using the /cache partition
Code:
adb push update.zip /cache
and you should be able to do the update from cache.
Click to expand...
Click to collapse
Using you're SPL, is it still possible to place an update.zip into /cache with the partition table having been re-written??''
I'm assuming yes, since you jumped in and posted that method, I was just curious
jackslim said:
Using you're SPL, is it still possible to place an update.zip into /cache with the partition table having been re-written??''
I'm assuming yes, since you jumped in and posted that method, I was just curious
Click to expand...
Click to collapse
Well you're cache partition should have 30720K (about 30MB)
the last cyanogen rom was 37 MB =[
my other recommendation for you is to push the updates to your sdcard through your phone. (just re-read your post and noticed the SD card is functional in your phone)
Code:
adb push update.zip /sdcard/update.zip
then just proceed as usual.
@theslam08
Your signature say's your using the "Danger SPL" Judging by that you could reflash your spl from fastboot to the hard spl
Code:
fastboot flash hboot spl.bin
Then use the method described above by Haykuro pushing updates to /cache with adb
Thanks for the responses guys .
As for pushing to sdcard while in phone, thats where the problem remains. The sd reader IN the phone is busted it would seem as it just says no sd card found (cannot mount) with 3 different cards I tried (all working on the computer).
Ok so if I flash back the spl will I have more than 40mb free on the cache partition? Because yeh, the most recent update from CM is ~40mb, so it wont fit currently.
ANd once pushed to /cache, how would I go about doing the actual update? You said "you should be able to do the update from the cache part.), not sure how, just give the location?
console: flash update /cache/update.zip ?
Thank you.
theslam08 said:
Thanks for the responses guys .
As for pushing to sdcard while in phone, thats where the problem remains. The sd reader IN the phone is busted it would seem as it just says no sd card found (cannot mount) with 3 different cards I tried (all working on the computer).
Ok so if I flash back the spl will I have more than 40mb free on the cache partition? Because yeh, the most recent update from CM is ~40mb, so it wont fit currently.
ANd once pushed to /cache, how would I go about doing the actual update? You said "you should be able to do the update from the cache part.), not sure how, just give the location?
console: flash update /cache/update.zip ?
Thank you.
Click to expand...
Click to collapse
i forgot the exact command to force a boot-recovery and have it flash through cache (the traditional method)
but if your on cyanogen's recovery you can do
Code:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
this should mount cache into /sdcard, allowing you to flash.
haykuro said:
i forgot the exact command to force a boot-recovery and have it flash through cache (the traditional method)
but if your on cyanogen's recovery you can do
Code:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
this should mount cache into /sdcard, allowing you to flash.
Click to expand...
Click to collapse
Excellent, that seemed to be the trick (after going back to HSPL because yeah, I didnt have enough room with haykuro's). Though some bugs with that.
I got it to copy once after making that partition mount, and I was able to see the update file. I updated, and everything went well (even though I wondered how in the middle of the update it says formatting cache, yet it still worked).
Now, I went to put on a theme file and it says out of room. I hit 'update from sdcard' in recovery and it says E: No zip files found or something like that, just no files. So if it gets 'wiped' how is there no space? Is there a manual format I should do?
And I dont think this has happened to anyone yet, so thanks for going through this , im sure others down the road will find it helpful.
Not to get off-topic or picky about anything, but having the phone without an SD card being able to be read seems kind of pointless.
After all, you won't be able to run A2SD, or move the cache. The phone's going to run as if it was "stock."
akapoor said:
Not to get off-topic or picky about anything, but having the phone without an SD card being able to be read seems kind of pointless.
After all, you won't be able to run A2SD, or move the cache. The phone's going to run as if it was "stock."
Click to expand...
Click to collapse
Not being blunt but, thats the point. I have 'no' other choice right now, I cannot get a new phone for a while (and warranty is over, its a yr and 3 months since pur)
I obviously know I cannot use A2SD, so I need to get it to run 'stock', and thats proving to be a trick (stock but not). I almost have it, but cache doesnt seem to wipe on its own, which is the new problem. Once that is cleared, then I should be all set .
theslam08 said:
Not being blunt but, thats the point. I have 'no' other choice right now, I cannot get a new phone for a while (and warranty is over, its a yr and 3 months since pur)
I obviously know I cannot use A2SD, so I need to get it to run 'stock', and thats proving to be a trick (stock but not). I almost have it, but cache doesnt seem to wipe on its own, which is the new problem. Once that is cleared, then I should be all set .
Click to expand...
Click to collapse
Ah, okay - now it makes sense. I didn't understand the purpose at first.
there are a number of problems with the recovery in the just leaked
Froyo ROM.
1. signature checking
2. passing API version 3 to the updater binary
3. forced wipe after installing an update.zip
the attached zip has a 3e recovery modified to disable signature checking
report API version 2 for backwards compatibility with clockwork mod recovery
and disable the forced wipe after installing any update.
I don't know of any reason to run this version over 2e but it
might be useful to someone.
Installing:
1. turn on USB debugging
2. plug into computer
3. run script and follow on screen prompts.
UPDATED 01/23/2011
fixed path error when space in user name
UPDATED 01/22/2011
compressed the rageagainstthecage resource to prevent anti-virus detection
new anti-virus report
http://virscan.org/report/8e83f338fd7b8631c6b0bc0679efbd29.html
the /system file system is full on the newer ROM's
use the attached update.zip to root then install clockwork
Nice
Sent from my SGH-T959 using XDA App
ummmm... what attached zip?
kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
forgot to upload it.
kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
The one attached to the message(?)
fearmonkey said:
The one attached to the message(?)
Click to expand...
Click to collapse
yeah, he attached it after that post lol
how do you use this?
ok i wil bite. how do you use/flash this it cw is not accesible?
rename to update.zip i assume...... i mean thats how u flash everythign thats zip file if u cant get into clockwork.....
you cant flash this you will have to put the files on the internal sdcard
then use root explorer or adb to move the files into place, recovery goes to
/system/bin and the keys to /efs, update.zip is the clockwork recovery and
stays on the sdcard.
when you boot into recovery and choose re-install packages clockwork will
be able to do its thing.
I do like the sig verification but it's a PITA and may disable it, this is a temp
fix until I can finish hacking on recovery there is very little clues as to where
the functions are so it may be a few days.
forgot to mention to you also have to remount /system rw
mount -o rw,remount /dev/block/stl9 /system
Be-ware. Doing so on the ODIN 2E version will break Recovery all together.
Fine to replace on the Stock 2.2 ..
Ps.
Another Awesome Job untermensch
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
option94 said:
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
Click to expand...
Click to collapse
I haven't tried just replacing 3e with 2e, I doubt there is any advantage to
3e, to us anyway. but it is always worth while to find ways around these
things.
EDIT:
just replacing 3e with 2e did not work cant find the update.zip
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Thanks man i rreally appreciate this like i said before. Working perfect snd no issues. Loving being able to CWM again ha. Anyway thank you again sir keep it up!
TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
Thanks untermensch for your work and thanks to the TJD319 for the clear step by step instructions.
Getting can't mount partition after I select a zip file to flash. I can get to cwr fine and it sees the sdcard (internal) fine since I can navigate and select the file I want. The error comes when I try flash. All the files in the zip are in the root of the sd internal, except for recovery and keys that are in the directory /system/bin and /efs respectively. Any advice?
untermensch said:
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Click to expand...
Click to collapse
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
eugene373 said:
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
Click to expand...
Click to collapse
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
untermensch said:
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
Click to expand...
Click to collapse
Yo man i really appreciate your work. Froyos been great to me Stock 2.2 and this is perfect man. Working flawlessly for me and Im just happy to be able to nandroid.
Running 2.3.3, build number is CL 49208, using a Mac. Unlocked bootloader with fastboot. Used recovery-RA-passion-v2.2.1. Put the su-2.3.6.1 on my phone. Finally got it to reboot in recovery. Installed CM7.0.3. Oh, and I bought this phone in China (it's legit). Also, I used info from lots of sources before I finally found a recent post here that suggested the su zip file. One of those things I put in my sdcard is Radio_20100203_2_Signed_PASSION.img. Don't know if that helps. I couldn't find a more updated radio image.
The plan is to install CM7 so I can run openvpn.
It stops and cycles through the CM7 load screen -- turquoise android on a skateboard with an arrow circling around. Goes no further.
What did I miss? How do I fix it? Thanks.
Sounds like your in a bootloop.
Did you flash GAPPS also?
Here's more infos for radio, ect...
http://forum.xda-developers.com/showthread.php?t=744605
Has happened to me before. I removed the SD card and scanned it for errors on my PC. Worked after that. HTH.
Sent from my Nexus One using XDA App
Uhh...I can't put a microsd card in my computer -- I don't think.
Would you recommend updating the radio image? I'm thinking the 5.12.00.08, since my phone is in fact Korean. Do I still need the GAPPS image? Can I flash that image into my phone, or do I need to put it on the root of the sdcard?
cat3rpill3r said:
Uhh...I can't put a microsd card in my computer -- I don't think.
Would you recommend updating the radio image? I'm thinking the 5.12.00.08, since my phone is in fact Korean. Do I still need the GAPPS image? Can I flash that image into my phone, or do I need to put it on the root of the sdcard?
Click to expand...
Click to collapse
They make an adapter for micro sd card t ofit a USB port.
You can try new radio but If it's bootlooping I think your problem is elsewhere.
Did you check MD5SUM of the ROM before flashing?
Fortunately, my neighbor has a plethora of microsd adapters.
I did not check the sum. I read a few suggestions about doing that, but I couldn't figure out how, so I just trusted that what I had was fine. Lesson learned.
Let me get this straight: I need to put the GAPPS image on the sdcard AND flash the GAPPS image from fastboot? If I do update the radio image, do I need to reinstall CM7?
Put cm7 rom and gapps on sd card,
boot into recovery and flash rom then gapps, reboot.
Its highly recommends you do radio via fastboot.
To check md5sum, you can use one of the many free app from market.
Ok, ran checksum in fastboot. Not really sure what I'm looking for, so I'll just post what happened. In every case except gapps and su, the numbers returned were the same on the sdcard as in the tools file on my mac. Gapps and su are only on the sdcard.
For the CM7 zip, it returned: MD5(pathtofile)= 98d06d6a58c7de87d40269bfe0ae0e7b
For the RA img: 3def709ab1c9e051a92a1c8b1504a36a
For the Radio img: 310d85c4998163818f7dcdef730c2a12
For the gapps zip: 2f6a93654d1cfe191ff709b360ad60fc
For the su zip: b23147cb55eba3ae32a996a913fa54ea
I'm too new to the forum to post the link where I'm getting my instructions.
The CM7 version is update-cm-7.0.3-N1-signed, the RA is recovery-RA-passion-v2.2.1, the radio img is Radio_20100203_2_Signed_PASSION (the updated radio link you posted had removed the radio img because of some sort of violation), and gapps zip is gapps-passion-ERE36B-2-signed.
Still having the bootloop problem. I tried to find the most updated versions of everything I could. Is there a compatibility issue somewhere?
Another thought:
Do I need to flash the su zip from my sdcard in recovery? I don't know what that will do, so I haven't tried it yet.
There are a couple of files that Amon-RA suggests I delete in order to prevent calling the stock recovery:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Any idea how I can check for and delete these using fastboot via mac terminal?
You can't delete them from fastboot. Use fastboot to boot off the new recovery and delete them in there through adb.
Code:
fastboot boot recovery "c:\location\to\recovery.img"
Can you be more specific? I use fastboot to flash the recovery image, and when I'm in recovery on the phone, I use adb from my computer? Or I can access a command line in the phone?
Well, you use fastboot to flash the recovery. Then you use the command I posted below so you can boot directly into that recovery. Once in there, you use adb on the computer to go into the phone, mount the system partition (which can be done under the mounts and storage menu in recovery) and then find those files and remove them.
But you really only need to delete those files if you want to stay running stock Android. If you have a custom recovery on the phone, that is all you need to install CM, and CM doesn't contain the files that revert the recovery back to stock.
Just got it to work. It was, in fact, a compatibility issue. The gapps zip was for a different version. I found a different zip (for Gingerbread) at: http://goo-inside.me/gapps. If you have Gingerbread, choose a zip with gb in the name.
Does anyone know when the new ruu for the HTC One comes out? I went to unroot my phone, locked the bootloader, and went to run the ruu, only to realize I did the system update a few days before. So now I'm stuck in a bootloop and I can't mount my sd card ( I think it's corrupted ) So I'm pretty much out of a phone till then, correct?
Thank you in advance guys.
If you can unlock again, and somehow get adb to work, you can s-off using revone. Then you can flash any RUU. Otherwise, I dunno
Sent from my HTCONE using xda premium
propjockey said:
If you can unlock again, and somehow get adb to work, you can s-off using revone. Then you can flash any RUU. Otherwise, I dunno
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I re-unlocked the phone again but I have no clue how to do the rest.
If you can get files to your sd, you can run revone or moonshine to get s-off. Look in original development for the corresponding threads and instructions. Once you have that, you can RUU old firmware or unsigned.
Sent from my HTCONE using xda premium
I can't mount my internal storage. Even in TWRP recovery it shows nothing on the sd card. I think some how the internal sd card got corrupted, so I can't mount it.
Chloroform said:
I can't mount my internal storage. Even in TWRP recovery it shows nothing on the sd card. I think some how the internal sd card got corrupted, so I can't mount it.
Click to expand...
Click to collapse
I'm having a similar problem and need some help too!!
tx_jaycee said:
I'm having a similar problem and need some help too!!
Click to expand...
Click to collapse
I think the only thing that will fix our problem is a new version of the ruu. I knowledge on adb is very limited, I'm sure someone that knows what their doing can fix it 1,2,3, but that person isn't me. :crying:
ADB should not be your tool of choice. Fastboot would be your friend here, since it's a lot more direct in its method. If your internal card isn't completely hosed, you should be able to restore using the fastboot flash commands to reflash your /system and /boot and /recovery, at which point you should be fine. There are several threads on how to do this.
Rirere said:
ADB should not be your tool of choice. Fastboot would be your friend here, since it's a lot more direct in its method. If your internal card isn't completely hosed, you should be able to restore using the fastboot flash commands to reflash your /system and /boot and /recovery, at which point you should be fine. There are several threads on how to do this.
Click to expand...
Click to collapse
Can you point me in the right direction?
I tried the all in one kit, tells me device not found. I know it's found by my computer, it's in the device manager, plus I hear the noise that confirms a device is found. I can reboot my phone thru the all in one kit. I think it's best to wait for the newest ruu in my case.
Chloroform said:
Can you point me in the right direction?
Click to expand...
Click to collapse
Download the image of your choosing from this thread: http://forum.xda-developers.com/showthread.php?t=2368907.
Download TWRP 2.5 from this thread: http://forum.xda-developers.com/showthread.php?t=2236620.
Put your phone into fastboot mode (power + volume up + volume down). Plug the phone into your computer.
Install fastboot/ADB. You may need to search the web for the platform tools, or there are some toolkits that can help.
Open a command prompt and run "fastboot flash recovery <path-to-recovery.img>".
Go to Advanced -> ADB sideload, then run "adb install <path-to-downloaded-image.zip>".
If that doesn't work, open the zip and run:
fastboot flash system <path-to-system.img>
fastboot flash recovery <path-to-recovery.img>
Bottom line is if you're not willing to learn a bit about fastboot and ADB, then you shouldn't be using a toolkit because you won't be able to fix your device if something goes wrong.
So I pretty much tried everything with no luck BUT I flashed the boot.img and now I'm getting some where. Now it's showing my internal storage but the rom I had installed I guess erased. I've been searching around people saying flash system.img but how can I flash a system.img? All the files I've been finding are .zip and there any .img roms that I can flash?
Chloroform said:
I can't mount my internal storage. Even in TWRP recovery it shows nothing on the sd card. I think some how the internal sd card got corrupted, so I can't mount it.
Click to expand...
Click to collapse
I've had this problem. To correct it, I put everything I need to flash in /sdcard/0. TWRP sometimes only sees stuff within a 0 folder placed inside root.
If you haven't tried already, make a 0 folder on the sdcard, then copy it and see what TWRP shows.
Thank you to @Indirect for fixing my problem.
Chloroform said:
So I pretty much tried everything with no luck BUT I flashed the boot.img and now I'm getting some where. Now it's showing my internal storage but the rom I had installed I guess erased. I've been searching around people saying flash system.img but how can I flash a system.img? All the files I've been finding are .zip and there any .img roms that I can flash?
Click to expand...
Click to collapse
In the future, try extracting your downloaded .zip files.
OTA packages and recovery-flashable ROMs are provided as .zip files. Each archive contains the necessary .img files and a script that tells the recovery where to put them. You can extract these .img files and flash them with fastboot if you don't have recovery access.
Fastboot factory images generally are .img files compressed as .tar files. You'd better have a tool like 7zip onboard so you can deal with the many archive formats you'll find on the net.
Closed per OP request
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