Related
[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.5 BETA
Current FW version: 10.1.A.1.350, 10.1.A.1.434, 10.1.1.A.1.253 or 10.1.1.A.1.307 all can be updated!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.5 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check this post for it! Thanks m8!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6602: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6602: Download C6602.flashable.423.zip (Bittorrent: 686MB) and C6602_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6602.flashable.423.zip' on (the external) SDcard1;
Put 'C6602_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6602.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6602_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
C6603: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6603: Download C6603.flashable.423.zip (Bittorrent: 719MB) and C6603_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6603.flashable.423.zip' on (the external) SDcard1;
Put 'C6603_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6603.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6603_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
After updating your NFC firmware and some update information has been displayed, all is done!
I have done this myself, using my own method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.14
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperSU (default in this ROM) to SuperUser (Be careful, SuperUser is incompatible with 4.2.2!) you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the latest patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
Thanks go to @Androxyde for the FTF creation, cheers m8!
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Ya, I need manual install dual boot to access back to CWM/TWRP then just can install but the preinstall superuser root is not working at all.
Root working back by installing DooMLoRD Easy Rooting Toolkit (v15) - http://forum.xda-developers.com/showthread.php?t=2327472
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
I got into the same problem, and cannot get out. Anyone has any advice?
please fix dead links
dopeee said:
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
Click to expand...
Click to collapse
I found out with the leak by doomlord that it would be possible to update, no need to wipe, the official update works even better
lysp said:
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Click to expand...
Click to collapse
It's meant as an update process and not wiping anything will make the ROM treat your phone as one that just got updated
Faelz said:
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Click to expand...
Click to collapse
Yes, you need a stock ROM before you can flash this, I would not recommend updating your phone from PAC...
bungknees said:
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Click to expand...
Click to collapse
&
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
&
chuazy said:
I got into the same problem, and cannot get out. Anyone has any advice?
Click to expand...
Click to collapse
I have modified the guide a bit as i should have done before i posted it...
Restore the kernel to anything other then the 4.2.2 one and then try to flash the update package, after flashing the update, re-flash the kernel.
I made one error in my guide: If someone is not using the correct version of XZDualRecovery (2.5 BETA) then you lose recovery when on the 4.2.2 kernel. The correct steps order to prevent this from happening are now in the OP.
please fix dead links
calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
+1
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
buciupetru said:
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
Click to expand...
Click to collapse
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
lethalfriend said:
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
Click to expand...
Click to collapse
No need: /data/media IS the 'new' location.
[NUT] said:
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
Click to expand...
Click to collapse
thanks:good:efficient
[NUT] said:
No need: /data/media IS the 'new' location.
Click to expand...
Click to collapse
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
lethalfriend said:
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
Click to expand...
Click to collapse
Ooh... i now see what you mean... you are correct. I'll patch up the flashable package to do it automatically.
For you, use a file explorer to move the contents (skipping the 0 folder) of /data/media to /data/media/0/. Sorry man, i missed that completely on my phone
server stilll unreachable.
Hi All,
Last week I bought this HTC one, after using iphones for many years. First I loved the phone and I was so annoyed after realizing that it doesn't support my native language "Sinhalese".
So after some trouble, I rooted the phone and replaced the DroidSansFallback-htc.ttf with a Sinhala ttf file which I took from a Samsung phone. I was using Root Explorer App. Wallah!! it was rendering everything fine. :laugh:
The happiness did not last long, after I realized that every time I restart the phone DroidSansFallback-htc.ttf gets replaced with the original. So everytime I restart, I have to replace the file.
Would anyone be able to give a solution for this? Top of my head, would flashing the phone by clockworkmod with a .zip with my DroidSansFallback-htc.ttf fix my problem?
Also what's the reason for this? My friend's got a Samsung S4 with fresh Kit Kat installed in it. And it doesn't do this.
Thanks in advance for your opinion guys.
uadissa
(HTC One; Android 4.3; Rooted)
uadissa said:
Hi All,
Last week I bought this HTC one, after using iphones for many years. First I loved the phone and I was so annoyed after realizing that it doesn't support my native language "Sinhalese".
So after some trouble I rooted the phone and replaced the DroidSansFallback-htc.ttf with a Sinhala ttf file which I took from a Samsung phone. Wallah!! it was rendering everything fine. :laugh:
The happiness did not last long, after I realized that every time I restart the phone DroidSansFallback-htc.ttf gets replaced with the original. So everytime I restart, I have to replace the file.
Would anyone be able to give a solution for this? Top of my head, would flashing the phone by clockworkmod with a .zip with my DroidSansFallback-htc.ttf fix my problem?
Also what's the reason for this? My friend's got a Samsung S4 with fresh Kit Kat installed in it. And it doesn't do this.
Thanks in advance for your opinion guys.
uadissa
(HTC One; Android 4.3; Rooted)
Click to expand...
Click to collapse
how are you 'installing' the sinhala font?
Re
cr1960 said:
how are you 'installing' the sinhala font?
Click to expand...
Click to collapse
Used the Root explorer app to copy and replace the file.
uadissa said:
Used the Root explorer app to copy and replace the file.
Click to expand...
Click to collapse
in system>fonts?
Re
cr1960 said:
in system>fonts?
Click to expand...
Click to collapse
Correct.
uadissa said:
Correct.
Click to expand...
Click to collapse
which rom are you running?
I find easiest way for me is to change the font in the rom zip before flashing the rom. no problems with things not 'sticking'.
Flash the entire ROM?
cr1960 said:
which rom are you running?
I find easiest way for me is to change the font in the rom zip before flashing the rom. no problems with things not 'sticking'.
Click to expand...
Click to collapse
I'm still using the stock ROM with OS ver 4.3. You mean flash the entire rom after changing the DroidSansFallback-htc.ttf in the ROM zip file?
Can't I just flash the Fallback font without flashing the entire ROM?
uadissa said:
I'm still using the stock ROM with OS ver 4.3. You mean flash the entire rom after changing the DroidSansFallback-htc.ttf in the ROM zip file?
Can't I just flash the Fallback font without flashing the entire ROM?
Click to expand...
Click to collapse
did you unlock bootloader and flash a custom rom, or just unlock bootloader?
you need to have a rooted rom to change stuff like fonts etc. if you want the changes to stick.
Flash with a fresh new ROM
Since still I'm only one week after buying the phone, bit reluctant to flash it with a fresh new ROM
Phone is rooted
cr1960 said:
did you unlock bootloader and flash a custom rom, or just unlock bootloader?
you need to have a rooted rom to change stuff like fonts etc. if you want the changes to stick.
Click to expand...
Click to collapse
Yes I have unlocked the phone and rooted the phone after installing TeamWin Recovery. So now my rom is rooted. But it still has the stock ROM in it.
would you be able to explain me bit more on what you meant by
change the font in the rom zip
Click to expand...
Click to collapse
.
you meant download a customer ROM. edit it with my new font and flash entire ROM? or correct me if I'm wrong.
thanks
RESOLVED
I was able to resolve this issue easier than expected. This is what I did.
1. Boot the phone in to the Recovery mode( I have TWRP recovery installed)
2. Connected the phone to PC
3. From PC command prompt access a phone shell using I]adb shell[/I]
4. mount /system
5. Changed the properties like user, group and access permissions of my DroidSansFallback-htc.ttf to match the file in ROM's /system/fonts
6. Copy my DroidSansFallback-htc.ttf which has sinhala to /system/fonts( I made sure my original file was backed up)
7. umount /system
8. Exit from recovery and reboot
All works well :laugh::laugh:
uadissa said:
I was able to resolve this issue easier than expected. This is what I did.
1. Boot the phone in to the Recovery mode( I have TWRP recovery installed)
2. Connected the phone to PC
3. From PC command prompt access a phone shell using I]adb shell[/I]
4. mount /system
5. Changed the properties like user, group and access permissions of my DroidSansFallback-htc.ttf to match the file in ROM's /system/fonts
6. Copy my DroidSansFallback-htc.ttf which has sinhala to /system/fonts( I made sure my original file was backed up)
7. umount /system
8. Exit from recovery and reboot
All works well :laugh::laugh:
Click to expand...
Click to collapse
glad you got it sorted.
there is a difference between being unlocked and running a rooted rom. unlocked means you can install a custom recovery which then means you can flash roms. the rom contains 'files' which provide the ability to change things, which unlocking the bootloader and flashing a custom recovery do not. if you were running a custom rom, simply replacing the font using root explorer would have worked the way you wanted without having to use adb commands.
I believe the phone is rooted.
cr1960 said:
glad you got it sorted.
there is a difference between being unlocked and running a rooted rom. unlocked means you can install a custom recovery which then means you can flash roms. the rom contains 'files' which provide the ability to change things, which unlocking the bootloader and flashing a custom recovery do not. if you were running a custom rom, simply replacing the font using root explorer would have worked the way you wanted without having to use adb commands.
Click to expand...
Click to collapse
thanks for your comment. from all these I'm learning because i'm little new to android.
However I still believe my ROM OS is rooted. Because
1. After installing the TWRP custom recovery I installed SuperUser.zip by Koush to root the ROM
2. When I run root explorer it allows me to replace files into System folders with root access( Super User).
HTC has their own HTC Sense thing running on top of Android. Can that be replacing the system folders every-time it restarts? which is not happening in other phones.
if you were running a custom rom, simply replacing the font using root explorer would have worked
Click to expand...
Click to collapse
Yes I would have fixed but I was only running my stock OS rooted.
uadissa said:
thanks for your comment. from all these I'm learning because i'm little new to android.
However I still believe my ROM OS is rooted. Because
1. After installing the TWRP custom recovery I installed SuperUser.zip by Koush to root the ROM
2. When I run root explorer it allows me to replace files into System folders with root access( Super User).
HTC has their own HTC Sense thing running on top of Android. Can that be replacing the system folders every-time it restarts?
Click to expand...
Click to collapse
you need an insecure kernel .. thats why he's recommending you just flash a rom, it's much simpler
Thanks
clsA said:
you need an insecure kernel .. thats why he's recommending you just flash a rom, it's much simpler
Click to expand...
Click to collapse
But I had a insecure kernal. That's why I had root access when I was in adbd shell and it allowed me to replace files into /system.
uadissa said:
But I had a insecure kernal. That's why I had root access when I was in adbd shell and it allowed me to replace files into /system.
Click to expand...
Click to collapse
nope
this is from ARHD
ROM details:
Removed software (CPU) rendering - full Snapdragon 600 (GPU) rendering
Fully optimized and tweaked
Root access
Unsecured boot.img
Newest BusyBox
RAM optimizations
System signatures check enabled for system security and safety
Improved virtual memory management
Speed optimizations
Enabled GPU UI rendering
Data, cache and system partitions mounting tweaks
Bloatware applications removed
All /system applications updated to latest available
All /data applications updated to latest available
Improved CPU governors performance
Most optimal system scheduler
Disabled kernel debugging for better performance
Zipaligned (Improved RAM management)
Zipalign on boot (for user applications on data partition)
Fully de-odexed
init.d scripts (BusyBox run-parts) support
Auto init.d permissions set on boot
sysro/sysrw commands support
Excellent battery life!
Improved EXT4 performance
OpenVPN support
Most up-to-date system files permissions
Adobe Flash Player support
Support almost 24h a day
...and many more!
Click to expand...
Click to collapse
you don't get all those things just by being Root
I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
i'll try this
kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Seems that disabler zip did not work.
Any other brilliant ideas................
Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk
kingvortex said:
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.
Rooks said:
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.
Click to expand...
Click to collapse
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.
Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Only brilliant idea here was flashing something before backing up your rom.
Sent from my Nexus 5 using Tapatalk
GermainZ said:
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.
Click to expand...
Click to collapse
I did not mean to be rude or ANY disrespect.
So guys, PLEASE point me to right direction so that i can bring back my device.
rovo89 said:
In case you get into a boot loop:
First, try using the safemode by pressing any hardware key repeatedly. You can find a short explanation how it works here.
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
rovo89 said:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Where can i find disabler zip file?
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Rooks said:
Where can i find disabler zip file?
Click to expand...
Click to collapse
From the linked post:
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
Rooks said:
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
GermainZ said:
From the linked post:
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
Click to expand...
Click to collapse
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.
Rooks said:
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.
Click to expand...
Click to collapse
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.
Rooks said:
Yes i've tried three different files, all failed to install.
Click to expand...
Click to collapse
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?
Rooks said:
Where can i find disabler zip file?
I downloaded some file from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.
GermainZ said:
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.
Click to expand...
Click to collapse
I'll try to get logcat for this issue.
rovo89 said:
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?
Click to expand...
Click to collapse
Yes, it's the stock recovery and i've tried several times with hardware keys but safe mode did not work in my scenario.
esgie said:
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.
Click to expand...
Click to collapse
I've tried three different file with different sizes (143kb, 121kb and 145kb), all these files include the same script ("updater-script" file) by Tungswenty.
ui_print("");
ui_print("");
ui_print("------------------------");
ui_print(" Xposed disabler tool ");
ui_print(" by Tungswenty ");
ui_print("------------------------");
ui_print("");
ui_print("Mounting system partition");
ifelse(!is_mounted("/system"),
run_program("/sbin/busybox", "mount", "/system"));
assert(is_mounted("/system"));
ifelse(run_program("/system/bin/sh", "-c", "test -f /system/bin/app_process.orig") == 0,
(
ui_print("Restoring the original app_process file");
assert(run_program("/sbin/busybox", "cp", "-a", "/system/bin/app_process.orig", "/system/bin/app_process"));
set_perm(0, 2000, 0755, "/system/bin/app_process");
ui_print("Restore complete.");
ui_print("You should now be able to boot normally and remove all traces of Xposed from within the Installer app.");
),
(
ui_print("No backup found for app_process, nothing to be performed!");
));
ui_print("");
ui_print("Done.");
ui_print("");
Click to expand...
Click to collapse
Rooks said:
Yes, it's the stock recovery
Click to expand...
Click to collapse
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).
rovo89 said:
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).
Click to expand...
Click to collapse
I've stock rom and recovery, there is no custom rom or recovery available for my device (Toshiba Excite 10 SE aka AT300SE).
So with stock rom and recovery it won't accept any zips and i can't format system partition with stock recovery. And about adb, i don't know where to start. In recovery there is an option to push a file through adb but when i connect my device while this option, my pc does not recognize the device, neither i can update the adb drivers.
Rooks said:
I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.
Click to expand...
Click to collapse
HOW YOU ROOT...???!!!
PLEASE TELL ME
I CANT FIND IN WEB....
Give me a links if you can ....
THANKS
i have did adb remount and also mount -o rw,remount,rw /system on terminal in my phone....did mounted the system partion in twrp ( but it jus goes off again after i turn on my phone ) someone please help me
same here. anyone please help us
quiks11ver said:
i have did adb remount and also mount -o rw,remount,rw /system on terminal in my phone....did mounted the system partion in twrp ( but it jus goes off again after i turn on my phone ) someone please help me
Click to expand...
Click to collapse
delete unneeded system apps from /system/app/ then reboot and try again
simms22 said:
delete unneeded system apps from /system/app/ then reboot and try again
Click to expand...
Click to collapse
Hi when i try to delete, it shows a read only message, and i went root explorer to turn RW it automatically turn it off
quiks11ver said:
Hi when i try to delete, it shows a read only message, and i went root explorer to turn RW it automatically turn it off
Click to expand...
Click to collapse
ok, i understand whats happening now.. youre going to have to reroot. just boot into twrp and flash supersu 2.6x again.
simms22 said:
ok, i understand whats happening now.. youre going to have to reroot. just boot into twrp and flash supersu 2.6x again.
Click to expand...
Click to collapse
Hi, jus a simple question..will my phone be wiped?
quiks11ver said:
Hi, jus a simple question..will my phone be wiped?
Click to expand...
Click to collapse
if you just flash the latest SuperSU, then no. I flashed SuperSU 2.65 today, that works if you don't see a newer version.
simms22 said:
if you just flash the latest SuperSU, then no. I flashed SuperSU 2.65 today, that works if you don't see a newer version.
Click to expand...
Click to collapse
Ty simms22, i just realise my phone has no supersu, but quite odd, kernel auditor works haha...using elite kernel, i may flash later and try
okay, so i flashed the supersu 2.46 into my phone and it still doesnt show the supersu in apps drawer, but in setting/apps there is supersu and i still cannot manage to change write to system, in root explorer of es file manager after changing to RW, it automatic reset to Read only again
quiks11ver said:
okay, so i flashed the supersu 2.46 into my phone and it still doesnt show the supersu in apps drawer, but in setting/apps there is supersu and i still cannot manage to change write to system, in root explorer of es file manager after changing to RW, it automatic reset to Read only again
Click to expand...
Click to collapse
2.46 is very old now, you want 2.65 or above. google SuperSU 2.65, and you'll get it.
Okay bro, i already flash a supersu 2.66 but in my apps drawer i find no supersu apps and i still cant write to system
quiks11ver said:
Okay bro, i already flash a supersu 2.66 but in my apps drawer i find no supersu apps and i still cant write to system
Click to expand...
Click to collapse
wtf? lol! you can try to start over and reroot. thats what i would recommend, and its probably the right thing to do as well.
How to reroot? I oledi reflash but still cant
simms22, is it that i have a kernel or rom that resists me from writing to system, i can do it last time but i keep reflashing kernel making my system crash, then i restore from last backup afterward i cant write to system anymore
quiks11ver said:
simms22, is it that i have a kernel or rom that resists me from writing to system, i can do it last time but i keep reflashing kernel making my system crash, then i restore from last backup afterward i cant write to system anymore
Click to expand...
Click to collapse
what kernel are you trying? try elementalx.
---------- Post added at 01:40 AM ---------- Previous post was at 01:38 AM ----------
oh, BTW, reroot = flash factory image via fastboot, flash twrp via fastbpot as well. then flash SuperSU 2.65 and boot up.
i'm using elite kernel, what is factory image?? i'm kind of a newbie just unlocking and rooting watching youtube videos. please help me!!
where can i find factory image??
okay, i will try elementalX kernel, but 1 question...do i have to do anything before i flash another kernel? cause i used to flash many kernel after and after each1, then my phone keep restarting...so i restored the 1 i backed up
quiks11ver said:
okay, i will try elementalX kernel, but 1 question...do i have to do anything before i flash another kernel? cause i used to flash many kernel after and after each1, then my phone keep restarting...so i restored the 1 i backed up
Click to expand...
Click to collapse
factory images https://developers.google.com/android/nexus/images?csw=1#yakju
you have a nexus 6, so you need a factory image for shamu
hey i have an problem too everytime i try to push files in my system folder (like bootanimations) the es explorer sais i havent enough space every other explorer too, or when i try to change my density from 560 to 493 it sais the same, not enough space; i dont understand that... the phone is unlocked its rooted, i wiped everything a few times but nothing helps... :crying:
x-530 said:
hey i have an problem too everytime i try to push files in my system folder (like bootanimations) the es explorer sais i havent enough space every other explorer too, or when i try to change my density from 560 to 493 it sais the same, not enough space; i dont understand that... the phone is unlocked its rooted, i wiped everything a few times but nothing helps... :crying:
Click to expand...
Click to collapse
delete whatever system apps you don't need from /system/app/ then reboot. it will clear up enough space. google did that on purpose, made it read that its full, this will clear up the space.
Ok guys here is a custom recovery for the metro 2016 variant of the Galaxy J700t1 (Metro PCS) Flash with FlashFire or with Odin. Custom recovery but it won't mount the internal sd yet. Can't flash or backup.. so its still a work in progress, but its a working recovery other than that lol. Must be rooted first. Make sure that you download root file explorer and ensure you have a copy of su and busybox in your /system/bin and /system/xbin folders. Make sure you have USB debugging on, OEM on, and unknown sources on in System-Developer options. Thanks to Paco for the root exploit! But we needed a recovery for this fine device. Enjoy!
EDIT: SOME CLARITY FOR EVERYONE... ok, so here's the deal. In marshmallow the system is write protected after you trip KNOX 0x1. The system will persist and will lose integrity if the stock kernel's "CASHE" gets changed. hmmm.... so. this is what you need your system to be at if you want to flash a custom kernel or recovery with flashfire or flashify: After you root with Paco's method, you should be on stock rooted rom with stock recovery. when you flash with flashfire DO NOT WIPE CASHE OR DALVIK CASHE OR FORMAT CASHE in ANY WAY ... IT WILL SEND YOU INTO THE "RESET MODE"... NO worries tho. If this happens to you , ODIN this stock kernel CASHE that i'm posting below and you should boot back up. Keep in mind what you're doing as well... if for some reason you hit the "RESET" SCREEN, don't flip... just ODIN the partition you changed back to stock whether it be the kernel or in this case the RECOVERY. ... also, try not to use ever root in flashify/ flashfire because it lowers the permissions for the SU binaries and removes SU from some of the system folders.
INSTRUCTIONS:
1. start from stock if you can.
2.root via paco's method HERE
3.I would make sure you have a stock copy of the stock firmware (ROM KERNEL RECOVERY) on your computer just in case
HERE
4.download my cwm port for the j700t1 below and put it on the root of your drive or anywhere on your phones internal memory (not your external sd card)
5. Download root browser from the playstore as well as flashfire or flashify or both.
6.rename the cwm.img to recovery.img with root browser and ensure that you have SU and Busybox in /system/bin , /system/xbin , and it wouldn't hurt to have it in ~#/sbin as well..... AND check the permissions with root browser to make sure the permissions are set to 0777 (rwrwrwrw)
7. In "Flashfire" click the "+" symbol - click "Flash firmware package" -- Go to the cwm "recovery" file you put on your internal sd card and select the file. Fireflash will bring a screen up saying "Partitions" at the top showing the package. Click the check mark at the top right. FlashFire will go back to the "Actions" screen. Click"reboot" toward the bottom. Under the "reboot" screen, click recovery to boot directly into your new recovery after the flash. Uncheck Preserve recovery- click the check mark at the top right again. Click "Flash" at the bottom. --- wait. Device will reboot... flashfire will take over and your loading screen willl flash by... phone will boot back up into CWM....
To Flash ODIN tars --- Rename the perspective tar to the partition it goes to before trying to odin. Example: rename "cwm.recovery.img." to just "recovery.img" ... Same with the stock kernel tar below. . rename to "boot.img" then ODIN.
Sideload apps or ROMS or ZIPS just don't wipe any cashe partitions until we can get a good custom kernel. I could use the help with the kernel I will be honest. I can get it done but with a lot of trial and error. Anyone who can remove the SELinux write protection from the kernel please contact me.. I'm working on it. I was able to get a custom kernel to boot. but still no r/w mount for the USB yet. Just keep the CASHE lol. One more thing.. if your'e testing kernels, everytime you have to odin a stock kernel you will LOSE ROOT, so go ahead and re-root again.
https://drive.google.com/file/d/0B_WsJ57QBykaQ3ROeFZnajNzbmc/view?usp=sharing --- CWM img
CWM.TAR-- (new
--Stock Kernel CASHE.tar
Stock KERNEL
Team Rejectz
removed as it was reported not working by @timmetal6669
messi2050 said:
I worked on the kernel you asked for , i hope that it will help you getting a working twrp for your phone
Permissive kernel
https://www.mediafire.com/download/gd51y458vkzwmve
Completely disabled selinux kernel
https://www.mediafire.com/download/ui6udkamk1dkqq4
Click to expand...
Click to collapse
thank you!! the one I sent you? will flash right away
timmetal6669 said:
thank you!! the one I sent you? will flash right away
Click to expand...
Click to collapse
You are welcome ! No i didn't recieve anything , I compiled this one
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-j700t
messi2050 said:
I worked on the kernel you asked for , i hope that it will help you getting a working twrp for your phone
Permissive kernel
https://www.mediafire.com/download/gd51y458vkzwmve
Completely disabled selinux kernel
https://www.mediafire.com/download/ui6udkamk1dkqq4
Click to expand...
Click to collapse
not working...
do not flash this
Here is an odin flashable copy of the j700t1 stock kernel to get you booting again. just go into download mode, open odin and flash this if you happened to flash one of the kernels above
https://drive.google.com/open?id=0B_WsJ57QBykaSDRlQXlXSnpSd28
messi2050 said:
You are welcome ! No i didn't recieve anything , I compiled this one
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-j700t
Click to expand...
Click to collapse
No wonder it looped, we are the j700t1 variant.... Grab this stock boot.img i just posted above and see what you can do it with this instead lol.:good:
timmetal6669 said:
No wonder it looped, we are the j700t1 variant.... Grab this stock boot.img i just posted above and see what you can do it with this instead lol.:good:
Click to expand...
Click to collapse
Hmmm.... 2 members tested the first one and the phone booted up correctly , i can't disable selinux from the bootimage as Samsung is forcing selinux in the kernel , i need to build the kernel from source to do that
messi2050 said:
Hmmm.... 2 members tested the first one and the phone booted up correctly , i can't disable selinux from the bootimage as Samsung is forcing selinux in the kernel , i need to build the kernel from source to do that
Click to expand...
Click to collapse
Sent me into a loop... but I'm the metro pcs variant
Oh update... If anyone uses that odin flashable stock boot.img .. remember it IS a stock boot img. you will lose root. but you won't lose your system and your apps.. so just re root using paco's CF autroot exploit.
messi2050 said:
Hmmm.... 2 members tested the first one and the phone booted up correctly , i can't disable selinux from the bootimage as Samsung is forcing selinux in the kernel , i need to build the kernel from source to do that
Click to expand...
Click to collapse
might just be what i'll have to do.. the boot image is its own source
So no progress on the recovery to backup or flash yet?
Krumplife4400 said:
So no progress on the recovery to backup or flash yet?
Click to expand...
Click to collapse
Im working on it. the recovery is flashable and it works... just won't mount the SD right now... I have to right a script or look for a work around.. give me a bit...might take a few days. I'm a single dad and im' in school. I do this cuz i love it and I just bought this phone... Don't worry.,.. I'll be making ROMs before you know it... lol... mods everything... look up my threads lol
Thanks keep up the good work
Are you able to mount USB-OTG?? I am about to leave work so I haven't had a chance to play yet!
I can confirm it boots on j700t as well. I haven't flashed anything but it's there. I got twrp to boot and stay for roughly 5 minutes but still cannot mount anything either.
Sent from my SM-J700T using XDA-Developers mobile app
Verification Failed
I got this after flashing the cwm.img in FF. I did rename it to recovery.img is that why it failed? I could not get odin or FF to actually attempt a flash otherwise. Odin failed attempt NANDWRITE and FF complains about partition matching. I did have su and BB in the /system/bin and /system/xbin folders. Busybox permissions were 0777 and su permissions were 0755
Edit: i just rebooted the device and it booted right up. I tried to reboot recovery and it was back to stock so idk . I am definitely missing a step somewhere..
!Led*Eyes! said:
I got this after flashing the cwm.img in FF. I did rename it to recovery.img is that why it failed? I could not get odin or FF to actually attempt a flash otherwise. Odin failed attempt NANDWRITE and FF complains about partition matching. I did have su and BB in the /system/bin and /system/xbin folders. Busybox permissions were 0777 and su permissions were 0755
Edit: i just rebooted the device and it booted right up. I tried to reboot recovery and it was back to stock so idk . I am definitely missing a step somewhere..
Click to expand...
Click to collapse
Start over.
Set up phone like day one
Re-root with cf auto root
Update su binaries
Install BusyBox
Install flashify
Download IMG from op
After download, tap on IMG file should bring up flashify as an option
Flash IMG and reboot
Profit.
- I see you're good but no cwm? Skip start over root part and use flashify.
-sent from this device using this app.
So flashify over flashfire ? Ill give it a shot. Thanks
!Led*Eyes! said:
So flashify over flashfire ? Ill give it a shot. Thanks
Click to expand...
Click to collapse
No problem
sent from the interwebs using dis here application an m'digits....
I decided to just try it with flashify without reverting everything back to stock and voila! I chose the google drive option when searching for the file so it did download it again.... i re member reading something a while back about about a similar issue with not being able to mount the sdcard because the fs was encrypted and the recovery couldnt read it. I think they overcame by formatting the sdcard but i do not know .. i realize that simply formatting the sd in recovery and trying to mount would be fruitless but could the trouble be in the "expected recovery key" ? Just a thought. Thanks again timmetal6669 & OriginalShinken1 for the beta and the help. You guys are so close!
Has anyone tried to sideload a ROM yet since we can't flash?