[STOCK][C6502&C6503&C6506] Update to 10.1.1.A.1.253 [Root&XZDualRecovery][LB/UB]
After my release for the Z and the success stories on it, i had some requests to do the same for the ZL. Finally I'm ready for it's release! :victory:
Thanks go to @butatx for his invaluable testing contribution and taking one for the team.
Requirements:
Flashtool
A recovery (can be both CWM and TWRP)
NOTE: As some people have problems flashing the update, please update your existing recovery to the latest (BETA) recovery with XZDualRecovery
Current FW version: 10.1.A.1.350 or 10.1.A.1.434: maybe others too, try and let me know!
From the users in the original thread I noticed people using CWM running into trouble because their cache partition is gone. See the 'Known Issues' in the OP of the XZDualRecovery link above for more info and links to a fix. Fix that first before you attempt this update using CWM!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.3 RELEASE (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 his post for it! Thanks m8!
TIP: This ROM is compatible with the shutdown/reboot MOD by @niaboc79
TIP: This ROM and the integrated recovery are compatible with the reboot wrapper by @DooMLoRD, get it here!
C6502: How to update to 10.1.1.A.1.253:
For C6502: Download C6502.flashable.253.zip (Bittorrent: 752MB) and Xperia_Z_10.1.1.A.1.253_C6502-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6502.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6502-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 everything in 'Xperia_Z_10.1.1.A.1.253_C6502-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6602.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
C6503: How to update to 10.1.1.A.1.253:
For C6503: Download C6503.flashable.253.zip (Bittorrent: 715MB) and Xperia_Z_10.1.1.A.1.253_C6503-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6503.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6503-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 everything in 'Xperia_Z_10.1.1.A.1.253_C6503-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6503.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
C6506: How to update to 10.1.1.A.1.253:
For C6506: Download C6506.flashable.253.zip (Bittorrent: 730MB) and Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6506.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6506-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 everything in 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6506.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
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, It will update your NFC with a firmware and after that, all is done!
IMPORTANT NOTE:
For some devices the first or second reboot after the successful upgrade may be used by the ROM/Kernel to upgrade some low-level firmware. This will be done from the screen which normally shows you the kernel logo. This upgrade flash will also happen when on a custom kernel by @DooMLoRD. DO NOT INTERRUPT THAT WHATEVER YOU DO OR HOWEVER LONG IT TAKES! Just let it do it's thing and wait, your phone will continue boot as soon as it's done.
I have done this myself, using my own method on the Z and I have not found any problem yet. :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
All known issues in TWRP and CWM on locked boot loaders apply, see their respective threads for more information.
Be especially careful with the cache partition when using CWM. Hopefully version 2.0 solved the cache issues but in case of problems with /cache use the FTF in my files to restore the cache partition if yours ever stops mounting due to the CWM issues, read this and this for more info on that. This FTF was created for .434 but as the cache did not change between .350, .434 and .253 you can still use it to fix the cache partition.
CWM Usage warning: Root can be lost (almost worst case), a bootloop can be experienced (worst case) or a reboot upon remounting /system to be able to write to it (most cases, relatively harmless) when using CWM and before a reboot out of recovery the 'ROM may flash recovery, fix it?' question is answered with 'yes'. This can be recovered from by opening a terminal app and typing the following commands:
Code:
su
/system/bin/stop ric
mount -o remount,rw /system
chmod 755 /system/etc/install-recovery.sh
Alternatively you can boot in to TWRP and go to the Advanced menu -> File manager and look for /system/etc/install-recovery.sh to set permissions 755 on it.
If even that is too much to handle for you, see the patch at the bottom of the OP to flash the fix.
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 .434 /system ONLY using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
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.13
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 SuperUser (default in this ROM) to SuperSU 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 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.
Reserved, just in case
There seems some error with the instructions why you created a stripped file as a zip as it is nota ftf file which cannot be used with flashtool.
I just waiting for the other file currently downloading to finish so I assume you mean used the .253 zip file inside moved to the sdcard of smartphone and the ftf firmware inside of it to the flashtool/firmware folder to flash so I seem confusion on your part.
That will be big help for us
Thank you
Just downloaded both files the stripped file in a zip file not an ftf so what do I do this please as it will need to be convert into a ftf file somehow?
Can you create a stripped ftf file please.
Darkfunnyguy said:
Just downloaded both files the stripped file in a zip file not an ftf so what do I do this please as it will need to be convert into a ftf file somehow?
Can you create a stripped ftf file please.
Click to expand...
Click to collapse
paullu said:
That will be big help for us
Thank you
Click to expand...
Click to collapse
There was a small issue with the download site, which now has been fixed. You can rename the ZIP file you downloaded and change the extension from .zip to .ftf
From there on you can flash it using flashtool.
Sorry guys
Hi NUT, tested your rom, it work flawlessly + rooted , thanks for your work :good:
confused
Is it right that the file called in instruction as"C6506.flashable.253.zip " in real is C6603??:
C6506: How to update to 10.1.1.A.1.253:
For C6506: Download C6506.flashable.253.zip (730MB) and Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6506.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6506-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 everything in 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6603.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
the total confusion with what file has to be renamed and used by Flash tool and which one with CWM. In order to avoid misinterpretation may be NUT closes this thread and open a new one with all corrections.
Successfully updated to 10.1.1.A.1.253 with everything intact including roots and recovery.
Hi, NUT. It works fine. Thanks for your work!
rfg13 said:
Is it right that the file called in instruction as"C6506.flashable.253.zip " in real is C6603??:
C6506: How to update to 10.1.1.A.1.253:
For C6506: Download C6506.flashable.253.zip (730MB) and Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6506.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6506-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 everything in 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6603.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
the total confusion with what file has to be renamed and used by Flash tool and which one with CWM. In order to avoid misinterpretation may be NUT closes this thread and open a new one with all corrections.
Click to expand...
Click to collapse
Whups, i might have linked to the wrong file then... Check my download link in my signature in case you get the wrong file, my bad
Sent from my C6603 using xda app-developers app
-- EDIT --
Fixed links in the OP and a typo. Sorry for the confusion!
Thanks Mr. NUT...i'm downloading it now
Kylez said:
Thanks Mr. NUT...i'm downloading it now
Click to expand...
Click to collapse
did i lose everything in phone if i flash this zip?
daniLaLaLaLaLa said:
did i lose everything in phone if i flash this zip?
Click to expand...
Click to collapse
No. Data, programs and settings will be saved.
Bird40 said:
No. Data, programs and settings will be saved.
Click to expand...
Click to collapse
Good, i tried it tomorrow after i wake up from sleep .:thumbup:
Sent from my C6502 using xda app-developers app
Hi,
I seemed to have run in a little trouble with this. Heres what happened - I was running a stock but rooted build 434 before attempting this. My BL cannot be unlocked so also stock Kernel. I wasnt running any recoveries. So I followed the steps in the post to install recovery "XZDualRecovery" which ran the bat file successfully and then rebooted my phone into the CWM recovery for the first time. I then tried to go back to recovery with no luck... tried several times wether with Vol+ (CWM) or Vol- (TWRP). I then followed a different post to install a single recovery which installed properly and I was able to boot my phone in CWM all the time... So Success!!
So i then copied the ZIP to my EXT Card and flashed my phone with the Stripped FTF file, I then rebooted straight to CWM and installed the ZIP from SD Card. Perfect, it rebooted, Android was upgrading x out of 293 apps... That was successfull and I was rooted and inside the ROM. The Gmail app kept crashing so I decided to reboot. Here is the problem, The Sony logo appears followed by the wrench in the white triangle. I wasnt even able to turn off my phone by holding Vol+ and Power. I could only reset with little yellow button next to the SD Card.
I tried to flash my phone with the stock FTF file using flashtool but no luck (Nearly crapped my pants)
Anyway after several attempts, I finally managed to get into flashmode and I am now with build 253 and no root.
Ill flash back to 434 later but would really like to know what I did wrong?
Geez, I think I just wrote a book but I wanted to be clear with everything I did..
Thanks
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash everything in 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' to your phone and boot the phone straight to recovery after that;
Click to expand...
Click to collapse
You are steller [NUT], great work here.
as quested above is the cwm backup for safety in case there are issues?
and flash everything, as i have not tried yet do we need to un check wipe, data, cache, appslog?
or does the ftf have the wipe options already unchecked?
Thanks again for the great work.
HackitZ said:
and flash everything, as i have not tried yet do we need to un check wipe, data, cache, appslog?
or does the ftf have the wipe options already unchecked?
Click to expand...
Click to collapse
Yes, when I flash the ftf-file, there were no wipe options.
Crash338 said:
Hi,
I seemed to have run in a little trouble with this. Heres what happened - I was running a stock but rooted build 434 before attempting this. My BL cannot be unlocked so also stock Kernel. I wasnt running any recoveries. So I followed the steps in the post to install recovery "XZDualRecovery" which ran the bat file successfully and then rebooted my phone into the CWM recovery for the first time. I then tried to go back to recovery with no luck... tried several times wether with Vol+ (CWM) or Vol- (TWRP). I then followed a different post to install a single recovery which installed properly and I was able to boot my phone in CWM all the time... So Success!!
So i then copied the ZIP to my EXT Card and flashed my phone with the Stripped FTF file, I then rebooted straight to CWM and installed the ZIP from SD Card. Perfect, it rebooted, Android was upgrading x out of 293 apps... That was successfull and I was rooted and inside the ROM. The Gmail app kept crashing so I decided to reboot. Here is the problem, The Sony logo appears followed by the wrench in the white triangle. I wasnt even able to turn off my phone by holding Vol+ and Power. I could only reset with little yellow button next to the SD Card.
I tried to flash my phone with the stock FTF file using flashtool but no luck (Nearly crapped my pants)
Anyway after several attempts, I finally managed to get into flashmode and I am now with build 253 and no root.
Ill flash back to 434 later but would really like to know what I did wrong?
Geez, I think I just wrote a book but I wanted to be clear with everything I did..
Thanks
Click to expand...
Click to collapse
The triangle showing is your phone flashing a new update to a low level device, NEVER interrupt that process, I believe it's not even possible to skip it.
XZDualRecovery not working is related to a 2.1 incompatible method of reading the keypress. You could have noticed it was already superseded by a BETA release fixing that. It's even included in this Rom release
Your Gmail app crashing can be fixed by clearing its cache from the apps menu. If that doesn't help you can remove it using a root app like titanium backup. Then install it again from play store.
HackitZ said:
You are steller [NUT], great work here.
as quested above is the cwm backup for safety in case there are issues?
Click to expand...
Click to collapse
Exactly, it is just a precaution, a case of better safe then sorry. Your other question got answered by @Bird40.
Sent from my C6603 using xda app-developers app
[NUT] said:
The triangle showing is your phone flashing a new update to a low level device, NEVER interrupt that process, I believe it's not even possible to skip it.
XZDualRecovery not working is related to a 2.1 incompatible method of reading the keypress. You could have noticed it was already superseded by a BETA release fixing that. It's even included in this Rom release
Your Gmail app crashing can be fixed by clearing its cache from the apps menu. If that doesn't help you can remove it using a root app like titanium backup. Then install it again from play store.
I actually started everything over by flashing a clean 434 FTF. Mine was a mess, I had played a lot with the system files. So this second try, the phone reboots properly, no triangle, no app crash but the Recovery still doesn't work and I also tried with the latest 2.2 BETA (same result). I also re-installed Root Explorer and when going from R/W to R/O, it reboots the phone, so I switched from SuperUser to SuperSU but same result.
Any suggestions?
Click to expand...
Click to collapse
Related
hei everyone,
i need help, how to install CynogenMod for xperia arc s. I try install but always stuck in(touchscreen can't function). Now i frustation about it!!! many things i try to fix and many way to solved, but the problem stay the same...
Any can help me.....
For the Info
Type : Lt8i
Baseband :LT18i BB77
ROM : Stock LT18i 4.1.B.0.587
Kernel : ArcKnight
Unlock Bootloader
use fxp kernel
ArcKnight will only work on Stock Roms and CM9 needs it's own kernel due to it being made from the aosp
SevenD2 said:
ArcKnight will only work on Stock Roms and CM9 needs it's own kernel due to it being made from the aosp
Click to expand...
Click to collapse
i try....... but, after install tochscreen cant fuction and reboot(the light purple always purple). i use FXP140 for try install...
arc_n_krizt said:
i try....... but, after install tochscreen cant fuction and reboot(the light purple always purple). i use FXP140 for try install...
Click to expand...
Click to collapse
Did you unzip the file because the Kernel is in there...
SevenD2 said:
Did you unzip the file because the Kernel is in there...
Click to expand...
Click to collapse
do you mean, I have to unzip first and then zip again without participating kernel?? or I fastboot the kernel first. if the question is fastboot kernel first, that I did it.
all the instructions to install CM09 I've already done. the problem is when on the homescreen after install touchscreen cant functionand after that reboot.....
arc_n_krizt said:
do you mean, I have to unzip first and then zip again without participating kernel?? or I fastboot the kernel first. if the question is fastboot kernel first, that I did it.
all the instructions to install CM09 I've already done. the problem is when on the homescreen after install touchscreen cant functionand after that reboot.....
Click to expand...
Click to collapse
Open the zip, just extract the kernel, leave the zip like it is in original way.
Then install the kernel and ROM.
I have. So, what the problem I've done. My arc getting freeze (touchscreen not responsible) after install.
Mate, please correction if I wrong install :
1. Flash kernel ( kernel get from zip ROM). I use flashtool for fastboot kernel
2. After that I trying press volume down for CWM. Wipe all (data,partision, and dalvik).
3. Install Rom and gaps.
4. Reboot..
In my case. My touchscreen freeze and reboot after that's....
Sent from my LT18i using xda app-developers app
arc_n_krizt said:
I have. So, what the problem I've done. My arc getting freeze (touchscreen not responsible) after install.
Mate, please correction if I wrong install :
1. Flash kernel ( kernel get from zip ROM). I use flashtool for fastboot kernel
2. After that I trying press volume down for CWM. Wipe all (data,partision, and dalvik).
3. Install Rom and gaps.
4. Reboot..
In my case. My touchscreen freeze and reboot after that's....
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
Reboot before installing gapps.
Still not working for me...
Sent from my LT18i using xda app-developers app
Does this happen on Stock rom? If it does then your phone might be defective
maybe... So frustrated and always sucks when I use ics... So many problem.... Try to Gb back.
Can I communicate from FXP dev to solved this problem... Trying get CM in my arc s... ;_
Sent from my LT18i using xda app-developers app
Did you format only /data?
You have to wipe /system also.
So
flash kernel
go to CWM
format, /cache, /data, /system
flash CyaongenMod .zip
reboot (not necessary)
flash gapps
boot to system
Always works for me.
michel_666 said:
Did you format only /data?
You have to wipe /system also.
So
flash kernel
go to CWM
format, /cache, /data, /system
flash CyaongenMod .zip
reboot (not necessary)
flash gapps
boot to system
Always works for me.
Click to expand...
Click to collapse
not work for me..... This also happens when the install panaroid android and CAMPS...
arc_n_krizt said:
not work for me..... This also happens when the install panaroid android and CAMPS...
Click to expand...
Click to collapse
this happens on every non-stock based rom. i have the same problem. if you search this forum for "touchscreen" you will find a lot of threads with this problem.every time without a solution.
FXP said in the cm10 thread "flash latest stock rom (ftf) and let it boot. this will update the touchscreendriver." but even this didn't worked for me or the one who asked.
the problem is, that the touchscreen works normaly in 1 of 20 boots, its randomly, then everything is perfect till i have to reboot...
maybe the kernel do not load our touchscreen driver correctly but why it works sometimes?
if any developer (from germany/berlin) wants to see this problem he can contact me. cause i dont think that anyone can find a solution without being able to reproduce the problem.
m4rh3l said:
this happens on every non-stock based rom. i have the same problem. if you search this forum for "touchscreen" you will find a lot of threads with this problem.every time without a solution.
FXP said in the cm10 thread "flash latest stock rom (ftf) and let it boot. this will update the touchscreendriver." but even this didn't worked for me or the one who asked.
the problem is, that the touchscreen works normaly in 1 of 20 boots, its randomly, then everything is perfect till i have to reboot...
maybe the kernel do not load our touchscreen driver correctly but why it works sometimes?
if any developer (from germany/berlin) wants to see this problem he can contact me. cause i dont think that anyone can find a solution without being able to reproduce the problem.
Click to expand...
Click to collapse
is that true? but I am still curious as to how CynogenMod can work in my arc. before upgrading to ICS I believe how GB works on my arc (no lags, and a bit of a problem when custom rom and modify).
like i said, there is no solution yet. you will find threads with the same problem. e.g.;
http://forum.xda-developers.com/showthread.php?t=1876341
http://forum.xda-developers.com/showthread.php?t=1828175
http://forum.xda-developers.com/showthread.php?t=1741147
http://forum.xda-developers.com/showthread.php?t=1556331
http://forum.xda-developers.com/showthread.php?t=1356406
you will find more, if you search for "touchscreen" in the developer threads of each rom. i also got pm's from somebody with the same problem.
e.g. cm10:
http://forum.xda-developers.com/search.php?searchid=114967771
m4rh3l said:
like i said, there is no solution yet. you will find threads with the same problem. e.g.;
http://forum.xda-developers.com/showthread.php?t=1876341
http://forum.xda-developers.com/showthread.php?t=1828175
http://forum.xda-developers.com/showthread.php?t=1741147
http://forum.xda-developers.com/showthread.php?t=1556331
http://forum.xda-developers.com/showthread.php?t=1356406
you will find more, if you search for "touchscreen" in the developer threads of each rom. i also got pm's from somebody with the same problem.
e.g. cm10:
http://forum.xda-developers.com/search.php?searchid=114967771
Click to expand...
Click to collapse
wow...
I tried to read carefully the install Cynogenmod. maybe this is a stupid question. purpose of
"Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps. Zip on the root of the SD card also. "
whether this is related to the inability of the touchscreen driver.
The next stupid question. is there a difference flashing kernel using flashtool and fastboot comand prompt ... most of the day, I tried different ways to install it and try to see the bugg in cyanogen forum.
Flashing CyanogenMod
If the Sony Ericsson Xperia Arc has been rooted, unlocked, etc. through steps other than the method described above or running a custom ROM other than CyanogenMod and you are having issues flashing or booting CyanogenMod, it is recommended the Sony Ericsson Xperia Arc be returned to stock & start over with the full instructions provided above.
Download the latest version of CyanogenMod.
Optional: Download the Google Apps for the device.
Extract the boot.img from the CyanogenMod update.zip and copy it to the same folder as fastboot (the /platform-tools folder within the Android SDK folder).
Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps .zip on the root of the SD card also.
Disconnect the Sony Ericsson Xperia Arc from the computer and power it off.
Press & hold the Menu button while connecting the Sony Ericsson Xperia Arc to the computer.
On the computer, open terminal and run the following command:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
While the device is reboot press the Volume Rockers a few times to boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side Volume Rocker to move around. Use the Power or Camera button to select.
Optional: Select backup and restore to create a backup of current installation on the Sony Ericsson Xperia Arc.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 11 - 12 again and choosing the Google Apps update.zip.
Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The Sony Ericsson Xperia Arc should now boot into CyanogenMod. If you don't see a menu item named +++++Go Back+++++ then try the back key of the device.
arc_n_krizt said:
wow...
I tried to read carefully the install Cynogenmod. maybe this is a stupid question. purpose of
"Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps. Zip on the root of the SD card also. "
whether this is related to the inability of the touchscreen driver.
The next stupid question. is there a difference flashing kernel using flashtool and fastboot comand prompt ... most of the day, I tried different ways to install it and try to see the bugg in cyanogen forum.
Flashing CyanogenMod
If the Sony Ericsson Xperia Arc has been rooted, unlocked, etc. through steps other than the method described above or running a custom ROM other than CyanogenMod and you are having issues flashing or booting CyanogenMod, it is recommended the Sony Ericsson Xperia Arc be returned to stock & start over with the full instructions provided above.
Download the latest version of CyanogenMod.
Optional: Download the Google Apps for the device.
Extract the boot.img from the CyanogenMod update.zip and copy it to the same folder as fastboot (the /platform-tools folder within the Android SDK folder).
Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps .zip on the root of the SD card also.
Disconnect the Sony Ericsson Xperia Arc from the computer and power it off.
Press & hold the Menu button while connecting the Sony Ericsson Xperia Arc to the computer.
On the computer, open terminal and run the following command:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
While the device is reboot press the Volume Rockers a few times to boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side Volume Rocker to move around. Use the Power or Camera button to select.
Optional: Select backup and restore to create a backup of current installation on the Sony Ericsson Xperia Arc.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 11 - 12 again and choosing the Google Apps update.zip.
Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The Sony Ericsson Xperia Arc should now boot into CyanogenMod. If you don't see a menu item named +++++Go Back+++++ then try the back key of the device.
Click to expand...
Click to collapse
and thanks m4rh3l for your time to give example for me....
Flashing kernel using flashtool or fastboot does not make a difference. Neither does where the file is located, but I leave it in the root to find it easily.
Sent from my lt18 using xda premium
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Any suggestions on how I can get access back to my device so I can repair/replace the platform.xml file and restore functionality to my phone?
Thank you very much!
Deozaan said:
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Click to expand...
Click to collapse
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
enryea123 said:
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
Click to expand...
Click to collapse
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Deozaan said:
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Click to expand...
Click to collapse
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
enryea123 said:
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
Click to expand...
Click to collapse
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Deozaan said:
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Click to expand...
Click to collapse
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
having a backup of the sdcard is always a good idea :good:, i have 2 backups of mysdcard on 2 different hard drives of my computer and the pictures i take with the camera are automatically uploaded on my dropbox .
enryea123 said:
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
Click to expand...
Click to collapse
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Deozaan said:
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Click to expand...
Click to collapse
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
enryea123 said:
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip
Click to expand...
Click to collapse
I was in CWM Recovery. I was using the zip file that I extracted from the link you gave me for Google's stock ROMs (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
enryea123 said:
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
Click to expand...
Click to collapse
Try this one
Deozaan said:
I was in CWM Recovery. I was using the zip file that I extracted from here the link you gave me (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
Click to expand...
Click to collapse
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
enryea123 said:
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
Click to expand...
Click to collapse
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
I got it working again. The ROM you gave me failed signature verification in CWM Recovery, but I told it to install anyway and it worked. Thank you.
The problem I was having with Gmail not syncing was that I used Titanium Backup to restore my data, but because all the data from my "SD card" got erased, Titanium Backup itself lots its settings, so my Device ID was different. I guess Gmail relies on the device ID for syncing.
Thank you so much for your help! I learned a lot from the experience.
Glad i helped you. well this is one of the reasons why i don't restore data with titanium (especially system data).
and by the way:
Deozaan said:
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
Click to expand...
Click to collapse
To fully reset and install a clean rom using fastboot you have to extract the bootloader-blabla.img and radio-blabla.img files from the tar.gz archive and then extract the 4 .img files inside the zip (that is inside the tar.gz) and flash this 6 .img files connetting your phone in bootloader mode to your computer and using fastboot in terminal (in fact this procedure reinstall the recovery too).
hi
i already unlock the bootloader, install custom recovery TWRP, and done a backup
i also copy my backup to PC
now i'm confuse
- i need to root the phone or can i just flash the new room?
- if i need to root the phone i found an italian guide on 4.0 and attach file, can i use that? i have 4.1.1 on mine now
i'm not interested to have HTC stock with root but what i want is to install MIUI ROM
this is the only guide i found in english that explains how to install the rom
external link (i can't post it) miuiandroid.com/community/threads/installing-the-htc-one-x-required-s-on-steps.16592/
what i understand is:
- boot my device power + menu down, to see the FASTBOOT USB i have to select FASTBOOT
- flash the boot.img
- press the power button once (HBOOT i guess), click volume down, highlight recovery & press power
- Flash the downloaded ROM via recovery normally and it followup at this link
external link (i can't post it) miuiandroid.com/community/threads/how-to-update-upgrade-miui.15424/
i need to copy the img rom in SD ROOT before starting with all this process
- now i need to Wipe data/factory reset, Cache Wipe & Dalvik Cache Wipe in all tutorial i found this is done with clockworkmod
in TWRP under menu WIPE i guess are System, Cache, Dalvik buttons
after that i'm note sure if i need to flash italian language, if i don't need and i can just download it later i tihink is not a big deal
unless is all in chinese
is the metod correct?
do i have to copy ROM file in .zip format as i download?
here where i found ROM
from official site grey button miui.com/download-7.html
OR
from UK web site miuiandroid.com/community/threads/3-4-28.20232/
the boot.img is here
point 3 miuiandroid.com/community/threads/installing-the-htc-one-x-required-s-on-steps.16592/
i'm not sure if would be better to use clockworkmod, since most tutorials use that..
thanks
Doesn't matter which recovery you use. Yes just place the zip file on your sd card. Flash boot.img as you already said. Perform a full wipe and then flash the Rom zip. Reboot and its done.
The Roms are pre-rooted so you dont need to worry about that. Italian language should be included i guess.
Sent from my HTC One X using xda app-developers app
Heres what i do :
1) Put Rom.zip on SD card
2) Put boot.img in fastboot folder
3) fastboot erase cache
4) fastboot flash boot boot.img
5) fastboot erase cache
6) Reboot into recovery
7) Full wipe (except sd card)
8) Install rom
9) Enjoy new rom
Andy
i did my first mess but fortunally i could restore since i had copy the backup on my mac too
i don't know what went wrong but this is what happened:
- i did how was told before, but actually i download boot.img and rom from 2 different sites
- after reboot it didn't move from first screena waited for 15 minutes almost, so i did reboot in recovery tri to wipe but nothing happened
- so i decide to restore... but it did boot even if it was successful
- i thought that if i flashed the boot.img first time i may need to do it again, i found boot.emmc.win, rename it to boot.img, flash it and then i restored successfully
:victory:
now, to try a different rom i need to restore (maybe is safer)? can i copy the rom from recovery or fastboot?
what can it be wrong with my miui rom? could it be boot.img and rom file mismatch? can't find where to download both
al404 said:
i did my first mess but fortunally i could restore since i had copy the backup on my mac too
i don't know what went wrong but this is what happened:
- i did how was told before, but actually i download boot.img and rom from 2 different sites
- after reboot it didn't move from first screena waited for 15 minutes almost, so i did reboot in recovery tri to wipe but nothing happened
- so i decide to restore... but it did boot even if it was successful
- i thought that if i flashed the boot.img first time i may need to do it again, i found boot.emmc.win, rename it to boot.img, flash it and then i restored successfully
:victory:
now, to try a different rom i need to restore (maybe is safer)? can i copy the rom from recovery or fastboot?
what can it be wrong with my miui rom? could it be boot.img and rom file mismatch? can't find where to download both
Click to expand...
Click to collapse
extract the boot image from the rom you are going to use
ok, i tryed again but now it get stack on Mi black screen
i waited 8 minutes but nothing happens, i also tried to wipe cache and davik, nothing happens
at list i get to black Mi screen
do i need to delete the boot.img from ROM zip?
what could it be?
1st u didn't mention which phone u r using
2nd dn't get confuse while downloading rom n .img file
Type in google
(Ur phone model) android development xda
U'll find all the stuffs related to ur phone
So try this 1 n remember before updating or rooting or anythg related to ur which can mess ur phone or can brick ur phone
I suggest u read twice the thread n procedures n also check thrice the stuff which u gonna need to perform ur act.
Sent from my GT-N7100 using xda premium
al404 said:
ok, i tryed again but now it get stack on Mi black screen
i waited 8 minutes but nothing happens, i also tried to wipe cache and davik, nothing happens
at list i get to black Mi screen
do i need to delete the boot.img from ROM zip?
what could it be?
Click to expand...
Click to collapse
i would try a different rom for now, viperx perhaps. and the boot image is in the rom zip, extract the boot img from the rom and put it in your fastboot folder then copy the rom to your sdcard. once you have done that, fastboot erase cache, flash the boot image, fastboot erase cache again, then back into recovery, wipe cache and dalvik just to be sure then use recovery to flash the rom and hey presto. all of the above is assuming you have the one x international tegra 3
I have htc one x european terga 3, as far as I know mini is only for tegra 3
what you describe is exactly what I did:
- I leave the rom zip ad it is, I didn't remove boot.imf that I extract, correct?
- when I flash I hit hoot fastboot, connect USB and fastboot change in fastboot USB, to go back I select Hboot and and hit power, prom there recovery
- I did unlock bootloader but did not get rooted my phone, could it be that?
al404 said:
I have htc one x european terga 3, as far as I know mini is only for tegra 3
what you describe is exactly what I did:
- I leave the rom zip ad it is, I didn't remove boot.imf that I extract, correct?
- when I flash I hit hoot fastboot, connect USB and fastboot change in fastboot USB, to go back I select Hboot and and hit power, prom there recovery
- I did unlock bootloader but did not get rooted my phone, could it be that?
Click to expand...
Click to collapse
read this post. at least twice!! http://forum.xda-developers.com/showthread.php?t=2069904 do not do the "unlock bootloader" section as you already did that
@nogotaclue sorry i read so many, and some of them sayed that root was not necessary if you flash a new rom, other sayed it could still be necessary... now i rooted with the app and did a new backup that i'm coping on PC
reading further it says: to wipe, install rom, and flash boot.img after
"Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it."
al404 said:
@nogotaclue sorry i read so many, and some of them sayed that root was not necessary if you flash a new rom, other sayed it could still be necessary... now i rooted with the app and did a new backup that i'm coping on PC
reading further it says: to wipe, install rom, and flash boot.img after
"Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it."
Click to expand...
Click to collapse
yes you can do it that way, i usually flash first but sometimes it does not work, so just flash it last as it says in the tutorial
after root, with the same steps, the ROM starts... but
touch screen is not working :crying:
now i'm gonna look arond to see if i found some post about that
this (kernel patch) solved my last issue
http://miuiandroid.com/community/threads/hox-miui-v5-official-release.20215/page-2
al404 said:
this (kernel patch) solved my last issue
http://miuiandroid.com/community/threads/hox-miui-v5-official-release.20215/page-2
Click to expand...
Click to collapse
So everything working now ?
Sent from my underpants using Daz and Lenor summertime
YES :good: without that path touchscreen wasn't working :victory:
hope is not going to mess all up with first update
Hi,
I need serious help.
I tried to install Vanilla RootBox rom on my Ace 2 NFC (i8160P) CZ.
So i did wipe data, cache, dalvik.
Then i add my Tee folder into rom (tee hack for P version) and i deleted the device model verification from updater-script because it is for non P version.
But when i try to flash the rom via cwm temporary, i stuck at this errors:
cant format unknown volume: /external_sd
cant partition unsafe device: /dev/block/mmcblk0p8
Click to expand...
Click to collapse
But my sdcard is working good (adata microsdhc class10 32GB)
Any solutions?
EDIT: I am using this http://forum.xda-developers.com/showthread.php?t=2389395 patch but not Version 2, but V1 flashed from CWM. This could be the problem. Or not?
EDIT2: I am doing downgrade with repartition to GB an then flash JB... Nicely Done.. but when i try to flash other ROM, still gets the error. OMFG.
EDIT3: So it looks like i need to repartition or do something with mmcblk0p8 partition but what? OMFG, help me please!!!
...
it seem great problem ask from rom creater i thinck they can help you
majid92 said:
it seem great problem ask from rom creater i thinck they can help you
Click to expand...
Click to collapse
Supposedly the mmcblk0p8p partition is the internal storage, named UMS --> Usb Mass Storage
So best check if that reads properly in android (file explorer) and/or when u connect it to your computer.
Seeing as your external SD works good and it complains about that too tho, I don't expect your internal SD to be faulty either.
As for the memory fix you flashed, when u reverted back to GB and then re upgraded to JB, was there a param.lfs.md5 file present in the package (assuming u used odin, u should be able to verify this by opening the tar.md5 in 7zip or winrar)
If yes, then any harm caused by the memory fix will have been undone and that isn't the cause either.
Carpe-Dimi said:
Supposedly the mmcblk0p8p partition is the internal storage, named UMS --> Usb Mass Storage
So best check if that reads properly in android (file explorer) and/or when u connect it to your computer.
Seeing as your external SD works good and it complains about that too tho, I don't expect your internal SD to be faulty either.
As for the memory fix you flashed, when u reverted back to GB and then re upgraded to JB, was there a param.lfs.md5 file present in the package (assuming u used odin, u should be able to verify this by opening the tar.md5 in 7zip or winrar)
If yes, then any harm caused by the memory fix will have been undone and that isn't the cause either.
Click to expand...
Click to collapse
So, yes it is the USB storage, and its working well too. param.lfs.md5 was there. I dont know what to do now.
you are using the temporary CWM tho right? which needs to be flashed via stock recovery? and stock recovery doesn't complain about your mmcblk0p8 partition?
if this is the case, then you can root the stock rom via stock recovery --> http://forum.xda-developers.com/showthread.php?t=2139263
download this kernel for stock rom --> http://forum.xda-developers.com/showthread.php?t=2171054 -extract the zip and place the kernel.bin.md5 file on the root of your internal sdcard
install any terminal emulator, open it and and enter/type su -click accept when prompted for superuser permissions
with that all done enter "dd if=/sdcard/kernel.bin.md5 of=/dev/block/mmcblk0p15" make no typo's on that one, it's lethal.
If done right, it will replace stock kernel with D kernel. which will contain the same version of cwm as in the temporary cwm zip, but with a bit of luck it will not return the error anymore then
if the problem does persist tho, you can also try both touch and regular versions of this kernel -> http://forum.xda-developers.com/showthread.php?t=2424964
extract and rename to kernel.bin.md5, place on internal sd and flash them the same way again via terminal emulator.
there is more hope for this kernel as both versions run different versions of cwm than D-kernel (and eachother), but if this does not solve the problem, you will not be able to boot as that kernel is incompatible with stock rom and you will have to reflash via odin.
Carpe-Dimi said:
you are using the temporary CWM tho right? which needs to be flashed via stock recovery? and stock recovery doesn't complain about your mmcblk0p8 partition?
if this is the case, then you can root the stock rom via stock recovery --> http://forum.xda-developers.com/showthread.php?t=2139263
download this kernel for stock rom --> http://forum.xda-developers.com/showthread.php?t=2171054 -extract the zip and place the kernel.bin.md5 file on the root of your internal sdcard
install any terminal emulator, open it and and enter/type su -click accept when prompted for superuser permissions
with that all done enter "dd if=/sdcard/kernel.bin.md5 of=/dev/block/mmcblk0p15" make no typo's on that one, it's lethal.
If done right, it will replace stock kernel with D kernel. which will contain the same version of cwm as in the temporary cwm zip, but with a bit of luck it will not return the error anymore then
if the problem does persist tho, you can also try both touch and regular versions of this kernel -> http://forum.xda-developers.com/showthread.php?t=2424964
extract and rename to kernel.bin.md5, place on internal sd and flash them the same way again via terminal emulator.
there is more hope for this kernel as both versions run different versions of cwm than D-kernel (and eachother), but if this does not solve the problem, you will not be able to boot as that kernel is incompatible with stock rom and you will have to reflash via odin.
Click to expand...
Click to collapse
Ok, Yes I have rooted stock ROM and temporary CWM, so i am going to try the D-kernel. Hope is compatible with P version.
EDIT:I did the steps, and now, succesfully hardbricked Lol Checksum was ok, command too. OMFG
PC is showing "U8500 USB ROM" in device manager when I connect the USB cable so.. thanks
mybe there is problem that the kernel is build on the me7 or mf1 software.
Guys for everyone who has P version Never flash normal version officiel fw like me7 mf1 via odin on P version of ace 2 it will hardbrick you device that they have to change the motherboard so be carefully
Click to expand...
Click to collapse
EDIT2: LOL i putted battery out for a while and now can go to download mode. But i am at school so now i´ll go home and try odin... AGAIN
EDIT3: I am online again, phone is running well on the stock rooted JB again.. still cannot flash roms, but whatever...
Heya, sorry for the lack of response I've been a lil busy.
I thought that kernel would work on P version as well tho, sorry about that :crying:
Glad to see that you recovered your phone from that atleast.
Last thing i can think of then is to use this kernel --> http://forum.xda-developers.com/showthread.php?t=2072872
It's built for gingerbread, so your phone will again not boot after flashing, but the 8160Pxxlk3 version will for sure be compatible with your phone, and it has yet another version of CWM you might be able to use for flashing
If that doesn't work tho, I really am out of options
gapps-jb-20131011
Hi. I am using Sony Xperia NEO L and managed to upgrade to JB. I followed the steps until i hot a noticed saying that the Installation aborted. What went wrong? Please help! I'm stuck here and cannot going anywhere :crying:
Hi,
Everytime I try to OTA update de weekly rom, I get the message that says that my memory is encrypted and directs me to recovery.
In recovery when I select the ROM, it returns ERROR 7, I know that it is related with 2 command lines in the updater script.
My question is, how can I fix this problems so I can normally OTA update?
Xiaomi MI 9 SE
TWRP 3.5.0_9-0
xiaomi.eu weekly (it happens in all versions)
Thanks
Hi please be specific are you using custom rom (twrp,cynogen...?)
Which phone are you using?
otherwise no one will help you (just edit the first message with the necessary info
flairepathos.info said:
Hi please be specific are you using custom rom (twrp,cynogen...?)
Which phone are you using?
otherwise no one will help you (just edit the first message with the necessary info
Click to expand...
Click to collapse
You're right, I think this is a generic problem, that's why I've not specified the model.
vmlc said:
You're right, I think this is a generic problem, that's why I've not specified the model.
Click to expand...
Click to collapse
Ahh I see now,some phones are built with a custom recovery failsafe so updating straight from the phone won't work
Youre going to have to download the update file to the phone (usually ota.zip)
copy it to pc
Unzip it and check the code (installscript.sh, build.prop... all of them(use Notepad++)) and remove recovery what nots (mine had expect recoveryxa84883,and some other recovery partition nonsense) - this is so you dont lose your twrp
compress all the files and name the zip (anything you want)
copy the zip to your adb fastboot folder
Then make sure usb debugging is enabled and
on pc type in adb: adb reboot recovery
after twrp open select the sideload option and use the method of flashing update then your update will flash easy
or
flash your stock firmware recovery image from extsdcard (external sd card) recovery.img as recovery in twrp (surely you know how to tranfer files from pc to microsddard ..)
reboot to system when done and do normal update should work fine
then flash twrp image from pc flashing software into recovery
flairepathos.info said:
Ahh I see now,some phones are built with a custom recovery failsafe so updating straight from the phone won't work
Youre going to have to download the update file to the phone (usually ota.zip)
copy it to pc
Unzip it and check the code (installscript.sh, build.prop... all of them(use Notepad++)) and remove recovery what nots (mine had expect recoveryxa84883,and some other recovery partition nonsense) - this is so you dont lose your twrp
compress all the files and name the zip (anything you want)
copy the zip to your adb fastboot folder
Then make sure usb debugging is enabled and
on pc type in adb: adb reboot recovery
after twrp open select the sideload option and use the method of flashing update then your update will flash easy
or
flash your stock firmware recovery image from extsdcard (external sd card) recovery.img as recovery in twrp (surely you know how to tranfer files from pc to microsddard ..)
reboot to system when done and do normal update should work fine
then flash twrp image from pc flashing software into recovery
Click to expand...
Click to collapse
Thanks for your reply.
Your first method is what I have to do to update manually, delete the model verification in updater-script. But I have to do this every time I want to update. How can this prevent from happening next times?
The second method, I haven't understood, have to flash stock recovery every time I want to update?
My point is to prevent this from happening, I want to OTA update normally, without having to do this procedures every time.
Regards
vmlc said:
Thanks for your reply.
Your first method is what I have to do to update manually, delete the model verification in updater-script. But I have to do this every time I want to update. How can this prevent from happening next times?
The second method, I haven't understood, have to flash stock recovery every time I want to update?
My point is to prevent this from happening, I want to OTA update normally, without having to do this procedures every time.
Regards
Click to expand...
Click to collapse
Yes
and the second method, yes, flash stock recovery to OTA update (it'll think that everthing is fine)
you can keep stock update if dont need twrp anymore
to update normally you would have to modify your stock recovery to have an intergrated twrp
basically making "stock twrp recovery" mod
Or in the same manner add a partition or boot option for twrp in boot image in maybe boot to [normal, recovery, bootloader"fastboot", and twrp]
with enough dedication it is definitely possible
flairepathos.info said:
Yes
and the second method, yes, flash stock recovery to OTA update (it'll think that everthing is fine)
you can keep stock update if dont need twrp anymore
to update normally you would have to modify your stock recovery to have an intergrated twrp
basically making "stock twrp recovery" mod
Or in the same manner add a partition or boot option for twrp in boot image in maybe boot to [normal, recovery, bootloader"fastboot", and twrp]
with enough dedication it is definitely possible
Click to expand...
Click to collapse
So this is not fixable, keep TWRP and have OTA update?
vmlc said:
So this is not fixable, keep TWRP and have OTA update?
Click to expand...
Click to collapse
Yes but now that you mention if you could edit the twrp recovery_id to match that of the stock recovery ,it might work because the system/ ota file calls for a specific recovery_id